RE: [U2] SYS.MESSAGE file being corrupted
John, Pardon me, but I want to be sure I understand this exactly. I want to be clear whether you I saw the same thing or the opposite. I saw: - corrpuption in my data file, with text from SYS.MESSAGES written in my data file. - SYS.MESSAGES iteslf was NOT written to was NOT corrupt. You saw: - corruption in UV's SYS.MESSAGES. SYS.MESSAGES itself WAS written to and WAS corrupted. - Your own data files were not corrupted. (but were expected updates missing?) Did I get your half right? If so, can you tell what data was written to SYS.MESSAGES? Was it something that was supposed to be written to your own data file? From: John Kent we dont run transaction logging. ...I am guessing that its the edi routine thats causing this problem And I figured it was TxLg. Now I'm thinking yours mine are related and its neither edi nor txlg. Your edi my como corruption probably both involve i/o to OS flat files, fwiw. but the error message suggests that and there is only one read only file on the system that i know of.. If anyone knows how to reproduce those error message i would like to know as i have tried everything i can think of me too. CDS --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted
Charles, when SYS.MESSAGE was not read only it was being written to by Universe (say IBM) and corrupted and the box fell over. The times were between between 6am - 10am, which would not be a busy period . I have sent all 3 copies of the corrupted file to IBM This file was identified because the date/time stamp had been modified. The file was replaced with a good one the box rebooted and all ok. No other problems. This happened 3 times in 3 months so IBMs suggestion was to make the file read only. After that the edi script process started playimg up with those cant write to a read only file messages that i cant reproduce. However this is happening more regularly than the above. All the above only started happening in the last 3 months and the system has been in place for many years. Thanks for the interest shown. Here are some comments from IBM There is a pattern, I just don't know how to interpret it. Best guess would be something (backup?) blocking access to 'C:\UV\UV\UVtemp' directory. Possibly a process that doesn't have write access to the directory. Maybe a defect where universe creates the temporary file with one name then tries to access using another key. Might ask the customer to check for capture04380aa and capture04948aa in 'C:\UV\UV\UVtemp' directory. I remember a problem long ago where the SYS.MESSAGE file was corrupted each evening. That was diagnosed to processes being spawned from cron. When the customer modified the job stream to instead of executing universe from cron to instead use cron to start phantoms, the problem went away. That was back at either release 7 or 8 of universe. The pattern is that all three files have corruption starting at address 0x0001B800 which would be group 55 of the SYS.MESSAGE file. In all three cases the error begins with There are currently 37 users logged on the system. (37 in second case is '2', and '16' for third case). This most likely is SYS.MESSAGE '001739' CT SYS.MESSAGE 001739 0001 There are currently %i users logged on the system. 0002 Where it gets interesting is that group 55 is always the beginning of the corruption, and this record hashes to group 54. RECORD SYS.MESSAGE 001739 Record 001739 hashes to group 54 and was found. The most common use of this message record would be with the USERS command: USERS There are currently 2 users logged on the system. The fact the SYS.MESSAGE file is being corrupted is due to a defect in UniVerse. The defect being a situation that universe isn't dealing with. Were this my case, I would probably concentrate first on trying to isolate a routine that was doing a EXECUTE 'USERS' CAPTURING RESULTS Would expect something unusual with regard to the routine. Started by 'at', started as a 'batch' job etc.. Would check to see if the pid numbers being assigned to processes might be impacting the problem. There have been some strange things with regard to large pid numbers. Windows uses these though it usually takes weeks between boots to get into the high numbers. jak - Original Message - From: Stevenson, Charles [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, February 09, 2006 4:58 AM Subject: RE: [U2] SYS.MESSAGE file being corrupted John, Pardon me, but I want to be sure I understand this exactly. I want to be clear whether you I saw the same thing or the opposite. I saw: - corrpuption in my data file, with text from SYS.MESSAGES written in my data file. - SYS.MESSAGES iteslf was NOT written to was NOT corrupt. You saw: - corruption in UV's SYS.MESSAGES. SYS.MESSAGES itself WAS written to and WAS corrupted. - Your own data files were not corrupted. (but were expected updates missing?) Did I get your half right? If so, can you tell what data was written to SYS.MESSAGES? Was it something that was supposed to be written to your own data file? From: John Kent we dont run transaction logging. ...I am guessing that its the edi routine thats causing this problem And I figured it was TxLg. Now I'm thinking yours mine are related and its neither edi nor txlg. Your edi my como corruption probably both involve i/o to OS flat files, fwiw. but the error message suggests that and there is only one read only file on the system that i know of.. If anyone knows how to reproduce those error message i would like to know as i have tried everything i can think of me too. CDS --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted
As a suggestion, John, maybe you could put a trigger on the SYS.MESSAGE file to capture what's being written. Be sure to put it on the BEFORE UPDATE and BEFORE WRITE steps. In the trigger, write the data, including record key, to a file in the accounts main data location or maybe even on another disk partition. All depends on how much work you're wanting to put into tracking down the problem. Good luck, BobW -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kent Sent: Wednesday, February 08, 2006 2:04 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] SYS.MESSAGE file being corrupted Charles, when SYS.MESSAGE was not read only it was being written to by Universe (say IBM) and corrupted and the box fell over. The times were between between 6am - 10am, which would not be a busy period . I have sent all 3 copies of the corrupted file to IBM This file was identified because the date/time stamp had been modified. The file was replaced with a good one the box rebooted and all ok. No other problems. This happened 3 times in 3 months so IBMs suggestion was to make the file read only. After that the edi script process started playimg up with those cant write to a read only file messages that i cant reproduce. However this is happening more regularly than the above. All the above only started happening in the last 3 months and the system has been in place for many years. Thanks for the interest shown. Here are some comments from IBM There is a pattern, I just don't know how to interpret it. Best guess would be something (backup?) blocking access to 'C:\UV\UV\UVtemp' directory. Possibly a process that doesn't have write access to the directory. Maybe a defect where universe creates the temporary file with one name then tries to access using another key. Might ask the customer to check for capture04380aa and capture04948aa in 'C:\UV\UV\UVtemp' directory. I remember a problem long ago where the SYS.MESSAGE file was corrupted each evening. That was diagnosed to processes being spawned from cron. When the customer modified the job stream to instead of executing universe from cron to instead use cron to start phantoms, the problem went away. That was back at either release 7 or 8 of universe. The pattern is that all three files have corruption starting at address 0x0001B800 which would be group 55 of the SYS.MESSAGE file. In all three cases the error begins with There are currently 37 users logged on the system. (37 in second case is '2', and '16' for third case). This most likely is SYS.MESSAGE '001739' CT SYS.MESSAGE 001739 0001 There are currently %i users logged on the system. 0002 Where it gets interesting is that group 55 is always the beginning of the corruption, and this record hashes to group 54. RECORD SYS.MESSAGE 001739 Record 001739 hashes to group 54 and was found. The most common use of this message record would be with the USERS command: USERS There are currently 2 users logged on the system. The fact the SYS.MESSAGE file is being corrupted is due to a defect in UniVerse. The defect being a situation that universe isn't dealing with. Were this my case, I would probably concentrate first on trying to isolate a routine that was doing a EXECUTE 'USERS' CAPTURING RESULTS Would expect something unusual with regard to the routine. Started by 'at', started as a 'batch' job etc.. Would check to see if the pid numbers being assigned to processes might be impacting the problem. There have been some strange things with regard to large pid numbers. Windows uses these though it usually takes weeks between boots to get into the high numbers. jak --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted {Unclassified}
John, -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward Sent: Thursday, 9 February 2006 12:39 To: u2-users@listserver.u2ug.org Subject: RE: [U2] SYS.MESSAGE file being corrupted As a suggestion, John, maybe you could put a trigger on the SYS.MESSAGE file to capture what's being written. Be sure to put it on the BEFORE UPDATE and BEFORE WRITE steps. In the trigger, write the data, including record key, to a file in the accounts main data location or maybe even on another disk partition. And CALL SYSTEM(9001) and write the call stack into this log file so you know for sure how you got there. The descriptions you sent us from IBM seem to imply that they think there might be a problem with EXECUTE ... CAPTURING. I think that rings a bell with me somewhere, maybe something to do with CAPTURING using temporary files with names formed out of the PID and not enough digits being used or something. Have a look in the README files (on the Product Matrix at IBM U2 web site) with the 'fixed bugs' in them. Maybe something in the list archives, too (I think they're down at the moment, though?) Good luck Mike All depends on how much work you're wanting to put into tracking down the problem. Good luck, BobW The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted {Unclassified}
Mike,
thanks for the suggestions
I am not aware of using a CAPTURING anyware but the eod process run just
after midnight does a ...
EXECUTE 'LISTU ', OUT UARRAY
from which i derive who is logged on and where and send them a message to
log out as the eod is about to start.
If they are not off within a few minutes they are force logged off
This program has been runnig for many years
jak
- Original Message -
From: HENDERSON MIKE, MR [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, February 09, 2006 12:13 PM
Subject: RE: [U2] SYS.MESSAGE file being corrupted {Unclassified}
John,
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward
Sent: Thursday, 9 February 2006 12:39
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] SYS.MESSAGE file being corrupted
As a suggestion, John, maybe you could put a trigger on the
SYS.MESSAGE file to capture what's being written. Be sure to
put it on the BEFORE UPDATE and BEFORE WRITE steps. In the
trigger, write the data, including record key, to a file in
the accounts main data location or maybe even on another disk
partition.
And CALL SYSTEM(9001) and write the call stack into this log file so you
know for sure how you got there.
The descriptions you sent us from IBM seem to imply that they think
there might be a problem with EXECUTE ... CAPTURING. I think that
rings a bell with me somewhere, maybe something to do with CAPTURING
using temporary files with names formed out of the PID and not enough
digits being used or something.
Have a look in the README files (on the Product Matrix at IBM U2 web
site) with the 'fixed bugs' in them.
Maybe something in the list archives, too (I think they're down at the
moment, though?)
Good luck
Mike
All depends on how much work you're wanting to put into
tracking down the problem.
Good luck,
BobW
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence
Force.
If you are not the intended recipient you must not use, disclose, copy or
distribute this message or the information in it.
If you have received this message in error, please Email or telephone
the sender immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
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.3/254 - Release Date: 8/02/2006
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
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: u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted
1) What is the platform - *nix or Windows? 2) If *nix, what are the owner/group/permissions on the file? Proper for all users of this program? 3) Is the file distributed? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kent Sent: Tuesday, February 07, 2006 3:58 PM To: u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org 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/252 - Release Date: 2/6/2006 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted
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: u2-users@listserver.u2ug.org 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: u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted
Hi John, In our system, we have a subroutine that opens files and places the file handle information in a dimensioned array. When the subroutine is called, it first checks the array to see if it's already been opened. If it has, the handle information is passed back without having done an actual open. If the file is not already in the list, an open is done and it's added to the array then the newly opened handle information is passed back to the calling subroutine. If you have this same type of environment, then my comments would be in reference to the array getting clobbered and passing back bad information for a file which is a pointer that ends up going to the SYS.MESSAGES file instead of the intended file. Normally I would assume that this would only end up with records being written but it's something to check for. BobW -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kent Sent: Tuesday, February 07, 2006 4:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] SYS.MESSAGE file being corrupted 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 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted
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: u2-users@listserver.u2ug.org 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: u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted
Bob, i dont have anything as sophisticated as that. I am opening up the file in the main program and passing it through to the subroutine. I dont understand how a file pointer could end up referencing SYS.MESSAGE though when the application software never references it. Thanks for the suggestion though. jak - Original Message - From: Bob Woodward [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, February 08, 2006 12:15 PM Subject: RE: [U2] SYS.MESSAGE file being corrupted Hi John, In our system, we have a subroutine that opens files and places the file handle information in a dimensioned array. When the subroutine is called, it first checks the array to see if it's already been opened. If it has, the handle information is passed back without having done an actual open. If the file is not already in the list, an open is done and it's added to the array then the newly opened handle information is passed back to the calling subroutine. If you have this same type of environment, then my comments would be in reference to the array getting clobbered and passing back bad information for a file which is a pointer that ends up going to the SYS.MESSAGES file instead of the intended file. Normally I would assume that this would only end up with records being written but it's something to check for. BobW -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Kent Sent: Tuesday, February 07, 2006 4:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] SYS.MESSAGE file being corrupted 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 --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted
From: John Kent Has anyone experienced the above and have an explanation Maybe. Except SYS.MESSAGE wasn't being corrupted, but rather text from SYS.MESSAGE was corrupting other data files. It this what you mean? I think I have the dubious honour of finding it first (at least IBM seemed to not know about it yet), about two years ago. Nov 23, 2005 release notes for 10.1.16 say it has a fix: 7883 In certain circumstances, UniVerse may have incorrectly written information from the SYS.MESSAGE file into other files. This may have caused the header or a primary group of the file to be overwritten, resulting in file corruption. This problem has been fixed. I was running Transaction Logging (TxLg) on UV 10.0.16, HPUX 11i when logging crashed. In it's aftermath, IBM found a piece of SYS.MESSAGES in a broken data file. Another TxLg crash yielded a piece of what should have been written to a COMO file (from a job that recycled used TxLg logfiles). I have assumed the two are related. I have seen some postings at indexinfocus but no resolution. I whined and complained on this list in Summer 2004, and at the IBM Las Vegas conference. John, did you find other postings besides mine? The above release note, is the next I heard of any progress on the subject. 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. Were you using TxLg? The quick fix was to make the file read only. My quick fix was to turn of TxLg. (It is supposed to make the system more robust, but we experienced our only crashes because of Transaction Logging. My humourless management was not consoled by the irony.) [snip] I cant reproduce this error and the same update can be run from the menu immediatiatly after the error without a problem. I could not reproduce the problem on our test system and we turned off TxLging in production. [snip] Any suggestions appreciated jak I need to find out if they think the COMO write to the wrong file is also solved. Before your post no one has ever mentioned to me that anyone else has ever experienced this. The release notes say nothing about TxLg. The release notes say nothing about COMO or other files besides SYS.MESSAGES. Has anyone seen anything like this with other files? Charles Stevenson --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] SYS.MESSAGE file being corrupted
That's the UV message file, right? You're actually seeing the message corrupted? Or do you have a program that is doing like a STOP 201 ?? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted
Kevin, thats correct. You replace the file with a copy and all is ok. I sent 3 copies of the corrupted file to IBM and they confirmed that it is Universe writing to the file but i dont know why. jak - Original Message - From: Kevin King [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, February 08, 2006 12:47 PM Subject: RE: [U2] SYS.MESSAGE file being corrupted That's the UV message file, right? You're actually seeing the message corrupted? Or do you have a program that is doing like a STOP 201 ?? --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted
Stew, we have a large named common in an include but no inline comments and this hasnt been modified for years jak - Original Message - From: Mitchell, Stewart [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, February 08, 2006 12:23 PM Subject: RE: [U2] SYS.MESSAGE file being corrupted 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: u2-users@listserver.u2ug.org 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: u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] SYS.MESSAGE file being corrupted
Charles, we dont run transaction logging. THe has been corrupted 3 times in 3 months. I didnt take a copy of the indexinfocus problems but will look again when its up and running. I am guessing that its the edi routine thats causing this problem but the error message suggests that and there is only one read only file on the system that i know of.. If anyone knows how to reproduce those error message i would like to know as i have tried everything i can think of jak - Original Message - From: Stevenson, Charles [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Cc: John Kent [EMAIL PROTECTED]; Bob Woodward [EMAIL PROTECTED] Sent: Wednesday, February 08, 2006 12:45 PM Subject: RE: [U2] SYS.MESSAGE file being corrupted From: John Kent Has anyone experienced the above and have an explanation Maybe. Except SYS.MESSAGE wasn't being corrupted, but rather text from SYS.MESSAGE was corrupting other data files. It this what you mean? I think I have the dubious honour of finding it first (at least IBM seemed to not know about it yet), about two years ago. Nov 23, 2005 release notes for 10.1.16 say it has a fix: 7883 In certain circumstances, UniVerse may have incorrectly written information from the SYS.MESSAGE file into other files. This may have caused the header or a primary group of the file to be overwritten, resulting in file corruption. This problem has been fixed. I was running Transaction Logging (TxLg) on UV 10.0.16, HPUX 11i when logging crashed. In it's aftermath, IBM found a piece of SYS.MESSAGES in a broken data file. Another TxLg crash yielded a piece of what should have been written to a COMO file (from a job that recycled used TxLg logfiles). I have assumed the two are related. I have seen some postings at indexinfocus but no resolution. I whined and complained on this list in Summer 2004, and at the IBM Las Vegas conference. John, did you find other postings besides mine? The above release note, is the next I heard of any progress on the subject. 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. Were you using TxLg? The quick fix was to make the file read only. My quick fix was to turn of TxLg. (It is supposed to make the system more robust, but we experienced our only crashes because of Transaction Logging. My humourless management was not consoled by the irony.) [snip] I cant reproduce this error and the same update can be run from the menu immediatiatly after the error without a problem. I could not reproduce the problem on our test system and we turned off TxLging in production. [snip] Any suggestions appreciated jak I need to find out if they think the COMO write to the wrong file is also solved. Before your post no one has ever mentioned to me that anyone else has ever experienced this. The release notes say nothing about TxLg. The release notes say nothing about COMO or other files besides SYS.MESSAGES. Has anyone seen anything like this with other files? Charles Stevenson --- u2-users mailing list u2-users@listserver.u2ug.org 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
