Having talked to IBM (who were as usual amazingly helpful, thankyou Jonathan and Leroy), their conclusion was that when a blink error occurs in a file, the action taken will depend on the type of file corruption that has occured:

When a READ is performed and a group is dicovered to have a blink error but the group is otherise OK, the ON ERROR clause will be followed and the error number can be accessed using STATUS()

If however the entire group header is wrong, UV sends a warning to stderror but because there is no group header, the record cannot be found so UV decides the record does not exist and takes the ELSE branch -- no further warnings or STATUS() code available.

When our files were being corrupted, the corruption overwrote the group header with an error message (trashing the entire group header), hence the ELSE clause was taken.

If you wish to follow this problem, the case number is 373556*AUS. IBM had not determined the effort required to correct the problem and could not give me a time frame in which it might be fixed.


hope you never come across this,



Craig
-------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to