|
Richard,
It's difficult to say what is happening, but here's some answers :
>>31-MAY-1994 02:09:15.06 Server: AOS03::"73=" Error: %OAFC-E-INTERR, Internal
>> error in File Cabinet Server Message:CsiOpenDrawer; DOCDB file/dev id does
>> not match IUID in partition, continuing
What this means is that a user's DOCDB.DAT file has got moved
(by DCL COPY, CONVERT etc) and so has a new RMS field. The FCS stores the
fields as it's a more efficient way to access files, but it detects when
they are incorrect and updates its record of the new field (after opening
DOCDB.DAT by name) so it won't happen again for that user (until the
file moves again). So this is something that is fixed on the fly, and
should be transparent to the user.
>>31-MAY-1994 02:29:29.02 Server: AOS03::"73=" Error: %MCC-A-ALERT_TERMREQ,
>> thread termination requested Message SrvBufferProcess; receive alert to
>> terminate thread
For some reason the server is disconnecting a thread (and possibly a
user). In earlier versions of the server you could see a number of
%MCC-A-ALERT_TERMREQ messages when a server is being shutdown, as then
all the threads are being disconnected.
>>31-MAY-1994 02:29:39.02 Server: AOS03::"73=" Error: %MCC-A-ALERT_TERMREQ,
>> thread termination requested Message SrvTimeoutSysMan; receive alert to
>> terminate thread
System Management connections to the server remain open for a set
period of time. This message purely indicates that the timeout period
for a system management connections has been exceeded, and so the
thread is disconnected.
>>The first of the error fills up many pages. Does anyone have any ideas,
That would seem to indicate that a housekeeping job has run to update
the DOCDBs, but the server remained up and running, and so had to
adjust to the new RMS fields (????).
Although you now know what the messages mean, it does not help
understand what the cause of the problem is. However, I would suggest
that the customer upgrades to MUPA ASAP. MUPA contains MANY FCS fixes
which would be encountered on a fairly heavily used system. My first
plan of attack would be to upgrade and take it from there.
Hope this helps,
Kevin.
|
|
I think you'll find that all but the first error you posted
were in fact related to stopping and starting the server.
MUP server's used to stop slightly 'messily' leaving a few
untidy messages in the log file.
The thread termination request is just the server telling it's
background processing threads to go away, and shortly after
the server itself stops. The last message saying the server
has started up, just a few seconds after the last 'error' msg
would suggest that these have all been logged around a STO/STA
operation.
Pete.
|