We are in the process of working our way out of S36 enviromnent with RPGii and flat files. (Don't ask).
We had a flat file that has 2 record types. One is data we need, the other is free form text data that overlays numeric data on the first record type.
We have created an external definition and copied all the data into it. If the record code is 1, we have valid data. If the record code is 2, we ignore the record because it is putting text data into numeric fields.
When using SQL, as long as we seleted record type 1 first, SQL works correctly. (if we accidentally include type 2, we get invalid data errors).
We are using embedded SQL and today we got invalid data errors. We changed the order of the selects so that record type =1 is first and that fixed the problem.
But somehow, SQL changed the member name to M181130. (today's date) Well, we're pretty sure it's SQL as we have no other processing that would change the member name.
Has anyone run accross SQL changing a member name? Or are we completly off base here and the member name is being changed somewhere else?
And yes, I am aware that having 2 records types in one externally defined file does not work well with DDS and SQL. But I am doing a delicate dance here to to keep things running while we move from the stone age to the bronze age, let alone the modern age.
We had a flat file that has 2 record types. One is data we need, the other is free form text data that overlays numeric data on the first record type.
We have created an external definition and copied all the data into it. If the record code is 1, we have valid data. If the record code is 2, we ignore the record because it is putting text data into numeric fields.
When using SQL, as long as we seleted record type 1 first, SQL works correctly. (if we accidentally include type 2, we get invalid data errors).
We are using embedded SQL and today we got invalid data errors. We changed the order of the selects so that record type =1 is first and that fixed the problem.
But somehow, SQL changed the member name to M181130. (today's date) Well, we're pretty sure it's SQL as we have no other processing that would change the member name.
Has anyone run accross SQL changing a member name? Or are we completly off base here and the member name is being changed somewhere else?
And yes, I am aware that having 2 records types in one externally defined file does not work well with DDS and SQL. But I am doing a delicate dance here to to keep things running while we move from the stone age to the bronze age, let alone the modern age.
Comment