Bob/Kevin
the platform is Windows 2000 and its a dynamic file passed in through a subroutine.
ie CALL *SUB(FILE1,FILE2)

I have checked for it being clobbered and we do not refer to SYS.MESSAGE so i cant see how this could happen

I have tried writing test programs to get the same error message but without success

jak
----- Original Message ----- From: "Bob Woodward" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, February 08, 2006 11:08 AM
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/


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 7/02/2006
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to