Conference csc32::consolemanager

1244.0. "Console Archive file locked problem" by 42441::JUDD (Geoff Judd. UK TSC. Viables, Basingstoke) Fri Mar 15 1996 08:47

Hi,
  This problem was reported in note 394 on V1.5 but I cannot see any other 
reports of this problem since then. The customer is currently running V1.6-125 
on OpenVMS VAX V6.1 which they received to fix a Console Archive hang problem.
This PCM node has 35 console systems and the customer issued the command
CONSOLE ARCHIVE ALL/BEFORE=1-JAN-1996 to archive all of the nodes. The first
16 nodes (presumably the systems connected to the first controller process)
archived successfully but the remaining 19 nodes failed with the following type
of error :

Starting archive procedure for system SATURN
Timefile  Pass 1: Working ... done.
Timefile  Pass 2: Working ... done.
Logfile   Pass 1: Working ... done.
Logfile   Pass 1: Working ... done.
Eventfile Pass 1: Working ... done.
Updating  Pass 1: Working ... -
%COPY-E-OPENOUT, error opening CONSOLE$ROOT:[LOG]SATURN.TIMES; as output
-RMS-E-FLK, file currenly locked by another user
%COPY-W-NOTCOPIED, DISK$CONSOOLE_3:[CONSOLE_ARCHIVE]SATURN_NEW.TIMES;1 not copied
%COPY-E-OPENOUT, error opening CONSOLE$ROOT:[LOG]SATURN.LOG; as output
-RMS-E-FLK, file currenly locked by another user
%COPY-W-NOTCOPIED, DISK$CONSOOLE_3:[CONSOLE_ARCHIVE]SATURN_NEW.LOG;1 not copied
%COPY-E-OPENOUT, error opening CONSOLE$ROOT:[LOG]SATURN.EVENTS; as output
-RMS-E-FLK, file currenly locked by another user
%COPY-W-NOTCOPIED, DISK$CONSOOLE_3:[CONSOLE_ARCHIVE]SATURN_NEW.EVENTS;1 not
copied
done.
Archive procedure for system SATURN completed successfully.

When the customer archived these nodes individually they completed successfully.

Note 394 states this problem is caused by the controller processes are not
releasing the files as they should when an archive is in progress. Does
anyone know whether there are any known problems that can cause this ? If so
will it be fixed in ECO2 ?

Thanks in advance,

Geoff Judd.