On 2013-03-17 12:56, Mark Benson wrote:
More info on that dump:
* Please enter time and date (Default:17-MAR-2013 11:54) [S]:
ACS SY:/BLKS=1024.
CON ONLINE ALL
ELI /LOG/LIM
CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
INS $QMGCLI
INS $QMGCLI/TASK=...PRI
INS $QMGCLI/TASK=...SUB
QUE /START:QMG
INS $QMGPRT/TASK=PRT.../SLV=NO
QUE LP0:/CR/NM
START/ACCOUNTING
11:54:17 STAT0 -- 73. *ERROR* on scan file open
11:54:17 STAT0 -- 4. FCS I/O error code = 334
file: DU0:[???,???]SYSSCAN.TMP;1
CON ESTAT LP0:
QUE BAP0:/BATCH
QUE BAP0:/AS:BATCH
@ <EOF>
That happened at reboot - maybe something to do with the system accounting (not that I
have much of an idea what that is)?
By the way:
.err 334
000334 (-36): %I/O-F-IE.SQC, file ID, sequence number check
Just in case you want to know. :-)
System accounting is essentially the keeping track of how much CPU time each user
consumes, how many pages printed, how many I/Os done, and so on...
And yes, the error have everything to do with accounting. The accounting subsystem keeps a
snapshot on a temporary file while running. The idea is that in case of a system crash,
you'll have a fairly accurate snapshot to pick up after reboot. But occasionally,
you'll get unlucky, and the file has been deleted, but the directory entry is still
there.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic
trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" -
B. Idol