JAK, Further to BobW's post, do you have INCLUDE statements in the program with in-line comments attached ie $INCLUDE INC.FILE INC.RECORD ;* Comment here
As this will corrupt the line numbers, that is you need to add the number of include lines with in-line comments to the line number reported to get to the correct line. Regards, Stew -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward Sent: Wednesday, 8 February 2006 10:38 To: [email protected] Subject: RE: [U2] SYS.MESSAGE file being corrupted I've not run into this before but from what you have listed, I'd be looking at what file the write attempt is being performed on. If it's not the SYS.MESSAGE file, which it probably is not, then I'd be looking at how the file open's are being done. I'd suspect the file handle variable being used on line 317 and 382 is no longer the file you think it is. Something to check for, anyway. You might be able to do a display of the file handle variable in the ON.ABORT segment of your program. BobW -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kent Sent: Tuesday, February 07, 2006 2:58 PM To: [email protected] Subject: [U2] SYS.MESSAGE file being corrupted Has anyone experienced the above and have an explanation I have seen some postings at indexinfocus but no resolution. There doesnt appear to be any 3rd part software involved and the application software doesnt ever reference this file but its occurred 3 times in the last 3 months. The quick fix was to make the file read only. A few days later i start getting errors messages from an edi update program initiated via a script complaining that... Program "*SOE.SCHAGE": Line 382, WRITE attempt on read-only file. Program "*SOE.SCHAGE": Line 317, WRITE attempt on read-only file. Program "*SOE.SCHAGE": Line 317, WRITE failure. program executes ON.ABORT I cant reproduce this error and the same update can be run from the menu immediatiatly after the error without a problem. I have started adding in ON ERROR and LOCKED options on the file writes to capture a STATUS() but no results as yet. Have also physically moved the file but made no difference. Plus there was mention of problems of high pid numbers but i dont think this is likely Any suggestions appreciated jak ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ********************************************************************** This email and any attachments are confidential. They may contain legally privileged information or copyright material. You should not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete the original message and all copies. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. ********************************************************************** ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
