Posted by Carl Haaser on July 25, 2011 at 05:31:59:
I had a problem locating an error 46. The system is compiled under Comet 16 but runs under 32. It showed the error as an Error 32 with no lun or any information that is actually useful. I looked at the last statements but the ERRORTO command takes the program to enough statements that the last few addresses only showed the ERROR routine instead of the initiating error. I ended up putting my own lun information at every read statement along with the actual EXCP code. It was an update program so it took a long time. TRACE also showed the error as a 32 and just the termination, again with no valuable information. The new error report showed the error 32 with lun 100! I know 46 is not a "normal" error but when somethings gets messed up it is VERY difficult to locate the problem when the OS is giving false readings.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.