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/
