Re: Format Level ID

Kurt,

Are there and date or time fields in the file(s) - I seem to remember they
can cause differences between files that are otherwise the same in SQL and
DDS.

Can you just recreate the TAXSTMTP file in DDS and be done with it?

Rory

On Tue, Jan 31, 2012 at 2:49 PM, Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx

wrote:

It's kind of embarrassing that I've been working with the machine (Power,
iSeries, etc) for over 10 years, but apparently missed mastering
file/format level IDs and when they change, etc.

I'm sure there's some reading I can do, but I have one situation that I
wanted to get input on.

We have a SQL file, TAXSTMTP. We also have a DDS file, CURTAXP. CURTAXP
is like a history/save file of TAXSTMTP. Our "cur" files are multi-member,
so they can't be created via SQL, which is why they are created using DDS
source.

These two files, compiled at 'the same time', one after the other, results
in the following format IDs:
TAXSTMTP: 43856FE31EAC4
CURTAXP: 43856FE31EAB4

The only difference being the 2nd to last digit. Is the difference due to
one being SQL and the other DDS, or is that a red herring?

It's coming up b/c we have a program that runs with either CURTAXP or
TAXSTMTP, but it complains (level check) when trying to run over the file
it wasn't compiled over.

Our "cur" files are mostly history files, but there are some used by
programs, which is why I'm hesitant to change the file to lvlchk(*no).

Thanks,
Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems