Posted by Barbara Brazil on April 23, 2014 at 08:18:07:
In Reply to: Re: Some questions about E9A errors posted by Bob A on April 23, 2014 at 07:49:36:
If you specify KEY= on a WRITE to an extended keyed file, the file system will copy the KEY= data into the record at the primary key position and then write the record. You should not be able to get a key tree/record mismatch!
This looks like another case of CometExplorer not checking the error returned from a file server call that it expects to succeed. It gets the next key, then does an INQUIRE to read what should be the matching record, but doesn't specify the key it just got. Then it prints the results of both to your output file. It looks like the key inquiry succeeded (got key with 77880 in it), but the INQUIRE failed so it just dumped the buffer that still had the previous record in it. Bad, bad, bad!
Let me try adding an error check to the INQUIRE and let's see what happens.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.