When events take place in the system that require operator intervention, or when one job is completed and another job begins, RBM informs the operator of these conditions by messages on the keyboard/printer. All such messages from the Monitor begin with two exclamation marks (! !).
is defined as a change from manual to automatic, or from automati c to manual and back to automatic, depending on the initial condition.) When the change of state is sensed, the operation is retried. Thus, if the devi ce is EMPTY, it need only be placed in the automati c mode. If there is a PUNCHES error or a FAULT on the card reader, the reader is unloaded, the bad card is corrected and replaced, and the reader is returned to the automati c mode.
Generally, these messages require no operator response on the keyboard/printer but may indi cate that some peripheral device needs attention. In some cases, the operator must interrupt and key in a response after correcting the speci-fied problem.
MONITOR MESSAGES
The messages itemized in Table 6 are output on the OC de-vi ceo They are primari Iy for background program use but can be used by foreground by specifying standard error re-coveryand "initiate and wait" in the M:REAO, M:WRITE, or M:CTRL calling sequence.
1/0 RECOVERY PROCEDURE
If a message concerns an I/O error condition, the Monitor I/O routines that generated the message wi II be waiting to sense, a change of state in the devi ceo (A change of state
Real-time programs with special requirements can inform the operator of special conditions and wait for an oper-ator response.
Message
, 'AL 10 ERRORt , !BEGIN WAIT
'!AL OVERFLOWt
"BEGIN WAIT
Table 6. Monitor Messages Meaning
An irrecoverable I/O error has occurred while accessing the ac-counting file, normally because of a hardware failure or unavaila-bit ity of operational label AL. The correct assignment of this operational label is to RBMAL, SO. An attempt should be made to recover the contents of the accounting file as stated above. If this recovery fai Is~ the operator may gain control through a KP key-in and then as FG key-in to allow foreground modifications;
the foreground operational label AL may then be reassigned (e. g. , 'ASSIGN AL = RBMAL, SO, F or ! ASSIGN AL = 0, F).
Note: Assignment of the foreground operational label AL to zero will inhibit the logging of job stack entries into the accounting fi Ie.
The accounting file (RBMAL) cannot accept another entry. The accounting file is allocated at SYSGEN and accommodates 74 entries. (The user may increase or decrease this capacity via the RAO Editor.) At this point, normal error recovery will be a key-in of KP to gain keyboard/printer control. Next, a key-in of SY will permit access to the accounting file. The operator should now assign the background operational label LO to a hard-copy device (e. g., paper tape, card punch). Input of a 'PURGE control command specifying the clear option (i.
e.,
'PURGE C) causes the contents of the accounti ng fi I e to be copi ed onto thatI
device and clears the accounting file. The job stack causing the overflow can now be reentered.i
tThis alarm occurs only if the RBM accounting option has been exercised at SYSGEN.
20 Operator Commun i cati on
Message
! !ATTEND ERROR xx
! !BEGIN IDLE
!BEGIN WAIT
! !BKG CKPT
! !BK RELEASE,dtnn
! !BKG RESTART
! !BKGD xx ABORT, LOC yyyy
! !CCI
! !dtnn EMPTY
! !dtnn ERROR [, TRK xxxx]
Table 6. Monitor Messages (cont.) Meaning
JCP has read an erroneous control command whi Ie operating in the ATTEND mode, in which case RBM goes into a wait state after typing this message. After a subsequent S key-in, RBM wi II pro-cess the next control command.
JCP has just read a ! FIN card (whi ch completes a job stack) and background has gone into an idle state. Processing will resume on a new job stack following an unsoli cited S key-in.
The background has executed a WAIT request. An unsolicited S key-in wi II continue background processing.
Background has been checkpointed as a result of a foreground pro-gram request.
The specified device has been released for background use.
Background has been restarted from its point of interruption.
The background job has aborted at location yyyy for the reason specified by abort code xx. If the Job Control Processor initiated the abort, a detai led explanation wi II be written on the back-ground DO devi ceo
If the system is operating in the lIattend ll mode (see !ATTEND), RBM wiil perform any required postmortem dumps and then go into a wait state after an abort. After a subsequent S key-in, RBM wi II attempt to process the next control command from the CC device.
If the system is not operating in the lIattend ll mode, RBM will not go into the wait state but wi II perform any required postmortem dumps and immediately begin reading from the CC device. All data cards and control commands will be skipped until a !JOB,
! PAUSE, or ! FIN card is found. Only a ! JOB card will clear the IIskipll mode. All control commands are I isted on the LL de-vice with an indication (> character) preceding the command to show that they are being ignored.
JCP has begun to read control commands. This message occurs at the beginning of a job and between steps within a job (e. g. , when an assembly is completed). If CC is assigned to the keyboard/
printer (as a standard assignment, or after a KP key-in), the input light on the keyboard/printer will indicate that RBM is ready for input of a control command.
The devi ce specified is in the manual mode and may be out of paper, cards, or tape.
There has been a parity or transmission error on the device. If any automatic retries were specified, they will have been performed before this message is output. A CR device will indicate that an error card is in the output stacker. Recovery procedure is described above under III/O Recovery Procedure ll . If it is RD, xxxx will be the errored track number.
System Communi cation 21
I I
I
IMessage
! !dtnn FAULT
! !dtnn PU NCHES
! !dtnn DATA RATE
! !dtnn UNROCOG
! !dtnn WRT PROT
! !END IDLE
! ! FG REQU EST, dtnn
! ! FG RESERVE, dtnn
! !FRGD xx ABORT, LOC yyyy TCB zzzz
! ! KEY ERROR, comments
22 System Communication
Table 6. Monitor Messages (cont.) Meaning
Some condition on device type dt with physical device number nn (hexadecimal) has caused this device to become nonoperational.
The recovery procedure is described above (in the discussion under change of state). The operation is automatically retried when the device goes into the automatic mode; it is neither necessary nor possible for the operator to type in a response.
An invalid punch combination has been sensed on an EBCDIC image.
I
A data rate overrun has occurred If any automatic retries were specified, they will be performed after this message is output.I
I
Device type dt with device number nn (hexadecimal) is not recog-nized by the I/O routines. If the device is a magnetic tape unit, the requested drive may not be dialed in properly or power may be off in either the unit or the contoller.
The RAD or magnetic tape is physically write-protected. If a RAD file is logically write-protected, this message will not ap-pear but appropriate status will be returned.
RBM has gone out of the idle state and wi II begin readi ng control commands from the CC device. Control commands will be ignored until a !JOB command is input.
A request has been made to reserve the specified device. The operator should prepare the device and then reserve it through use of the FR key-in.
The specified devi ce has been reserved for foreground use.
The foreground task with a TCB at location zzzz has aborted at location yyyy for the reason specified by abort code xx. The corresponding interrupt level will be disabled and if the task occupied nonresident foreground, an unload operation will be initiated. Background processing will continue. Because this message is written at the monitor priority level, only the abort message for one foreground task (the lower priority level task) will appear if two foreground tasks abort consecutively.
The Monitor could not process an unsolicited key-in response.
The message usually indicates a format error on the key-in, where comments may be one of the following:
NO AR
DEVICE
The wrong disk pack was mounted for an M key-in and the area could not be found.
The channel for the device specified was II not defined at SYSGEN or this device is not defined. Applies to M and BT key-ins.
Message
1 1 KEY ERRo.R, comments {cont.}
1 lMESSAGE comments
1 1 PAUSE comments
1 lPo.WER o.N
1 ldtnn No.ISE REC
1 1 dtnn BAD TAPE