After extensive effort, creating an example to send to IBM we believe we
have found the problem.
One of our files had a trigger. Due to this the big/little endian
conversion, using CONVERT.FORMAT did not seem to completely work. However
this was not obvious. We thought we had reconverted all files with
triggers, but maybe we missed this one.
The following commands worked without obvious problems.
CT BAD.FILE *
However FILE.STAT BAD.FILE failed with a message, but did not terminate the
uvfixfile did not appear to do anything. No error, just nothing.
ACCOUNT.FILE.STATS worked without obvious error but the output in STAT.FILE
showed incomplete information.
The result of this was that basic programs failed intermittently which made
this very, very difficult to track down.
I will be raising this with IBM as I believe it is a bug.
Sara Burns (SEB)
Development Team Leader
Phone: +64 (04) 474-3841 (DDI)
Mobile: 027 457 5974
Information contained in this communication is confidential. If you are not
the intended recipient the information should not be used, disclosed, copied
or commercialised. The information is not necessarily the views nor the
official communication of Public Trust. No guarantee or representation is
made that the communication is free of errors, virus or interference.
u2-users mailing list