The RAD Editor program outputs error messages on OC and DO. If OC and DO are assigned to the same device, duplication of messages on DO is suppressed. The warning messages in Table 20 are written on the OC and DO devices to provide a record of operations not performed or
The error messages output by the RAD Editor and their mean-ings are given in Table 19. The messages in Table 20 are written on the keyboard/printer during RAD restoration via the bootstrap loader produced by SAVE. Any error output causes the computer to go into a wait state after writing the appropriate message.
Table 19. RAD Editor Error Messages
Message Meaning
OVERFLOW: area, Allocation of the amount of storage indi cated by the fi Ie parameter on the ! # ADD command filename or restoration of a file not currently allocated would cause the permanent area to overflow,
or a library file has overflowed during execution of a !#ADD command. RAD Editor reads the next command from CC.
ASSIGN ERR: area, The RAD Editor was unable to assign an operational label to a filename because the number filename of avai lable RAD or disk pack device-fi Ie numbers is insuffi cient or because the specified
fil e does not ex ist. RAD Editor aborts.
CKSM ERR The last record in the object module being read from BI has a checksum error. If the job is ATTENDed, operator response is solicited; an operator response of S causes the Editor to read the next record from BI. RAD Editor aborts.
CHCK WRITE ERR A check write error occurred (that is, data recorded on the RAD or disk pack could not be verified).
CORE OVERF lOW The last command cannot be processed for lack of background space. The RAD Editor aborts.
DUP IDENT The last object module read from BI cannot be added to the library with a ! #lADD com-mand because it is already in the library. RAD Editor aborts.
I DUPLICATE: area,
I An attempt was made to add a fi!e whose name already exists for this area. The RAD Editor fiiename reads the next command from CC.
EDIT ERR Data on the RAD or disk pack has been rendered invalid. RAD Editor aborts.
96 RAD Editor Error Messages
Table 19. RAD Editor Error Messages (cont.)
Message Meaning
EMPTY oplb The devi ce assi gned to the operationa I label is in manual mode.
EOF oplb An unexpected end-of-fi Ie was encountered on the devi ce having the opetational label oplb. RAD Editor aborts.
EOF READ FILE An EOF has been encountered on the input file. Copying wi" continue unti I EOT on the Read file or EOT on the Write file is encountered.
EOT oplb An unexpected end-of-tape was encountered on the device having the operational label oplb. RAD Editor aborts.
EOT WRITE FILE An unexpected EOT occurred on the fi Ie currently receiving data. This is a warning to the user that the output file is smaller than the input file (as in !#FCOPY) but that the data already written is correct. The RAD Editor reads the next command from CC.
CALL SEQ ERR oplb A call ing sequence error occurred for input/output on the device having the operational label oplb. RAD Editor aborts.
FORMAT CONFICT: The fi lename being restored to the area confl i cts in format or record size with the existing area,filename fi lename in the area.
I
If it is not possible to add a fi Ie during the execution of the! # ADD command or a fi Ie in OVERFLOW: area,
filename I i the I ibrary area has overflowed during execution of the ! #LADD command. If operator response is S, the next command is read.
ILLEG BIN An illegal binary record (first byte not X'FF' or X ' 9F') has been read with an object module on BI. RAD Editor aborts.
INV CTRL Control command is invalid. It cannot be recogn i zed by RAD Editor or has incorrect syntax. If operator response is S, the next command is read.
INV I/O OP oplb An invalid input/output operation was attempted on the device having the operational label oplb. RAD Editor aborts.
LENGTH ERR oplb A record of incorrect length was read from or written on the device having the operational labeloplb. RAD Editor aborts.
LOAD ERR
I
The required RAD Editor overlay cannot be loaded. RAD Editor aborts.
!
!#BDTRACK command.
NO ALTERNATE An alternate track is not available for execution of the The RAD Editor reads the next command from CC.
NO BLOCK oplb No blocking buffer is avai lable for the fi Ie assigned to the operational label oplb. RAD Editor aborts.
BADIDENT The object module on BI does not have the same "identification" in the start module item.
RAD Editor Error Messages 97
Table 19. RAD Editor Error Messages (cont.)
Message Meaning
NO IDENT The identification in start module item is blank, or there is no object module on BI. RAD Editor aborts.
C.AN'T FIND area,
I
An attempt was made to save, clear, truncate, or delete a file whose name does not exist filename in the specified area, or the specified area does not exist. The RAD Editor reads the next
command from CC.
PARAM ERR Control command has a parameter error. A parameter has incorrect content, has been omitted, or is not consistent with the other parameters. A parameter error also occurs for
I
dupl icate Editor commands; that is, when an already-existing file is created via the! # ADDI ,.., I
,
I,
I Icommana or wnen a nonexlstmg Tile IS aeletea VIC tne : #DELETE command. If operator
res ... " , , _ 1 . .,'"SO : , , ' _ . " " _ I tho nevt 1 1 1 - I I ... r""mmnnrl _ _ I "' , _ . _ . _ . _ _ i c: r~arl ..
SEQ ERR The last record in the object module being read from BI has a sequence error. If the job is attended, an operator response of S causes the Editor to read the next record from BI. If the
job is not attended, RAD Editor aborts.
SZ ERR The object module on BI cannot be placed in the library because it has more than 61 ex-ternal definitions and references. RAD Editor aborts.
U NRECOVER I/O oplb An irrecoverable I/O error occurred on the device assigned to the operational labeloplb.
RAD Editor aborts.
WRITE PRO oplb The fi I e name assi gned to the operational label oplb is SY or FG write protected and an SY keyin is not in effect.
{~~}
PROTECTED: The specified area or filename has an SY or FG write protect code and an SY keyin is not area, filename in effect.Table 20. RAD Editor Warning Messages
lA AA
IVlessage IVleaning
CLEARING } RESTORING
These messages are output whenever the indi cated operation is started.
SQUEEZING area
TRUNCATING
DONE Message is output when the operation is completed.
SAVE TAPE NOT The save tape was not at load point when the ! #SAVE command was encountered and ex-AT LOAD POINT ecution commenced.
98 RAD Editor Error Messages
9. UTILITY
INTRODUCTION
The Uti I ity program operates in the background under the Real-Time Batch Monitor. It contains routines that:
• Copy variable-length binary or EBCDIC records from one medium to another (Copy).
• Dump records onto an output device in either hexa-decimal or EBCDIC format (Dump, known as Paper Tape Dump in the BCM system).
• Generate or update fi les that contain Standard Si gma Object language modules (Object Module Editor).
• Generate or update symboli c fi les (paper or magneti c) that contain source data (Record Editor, known as Paper Tape Editor in the BCM system).
• Edit card images by sequence number (Sequence Editor).
Routines in the Utility program are device-independent.
Utility handles any blocked or unblocked, sequential-access RAD file. Use of a sequential-access RAD file is similar to that of a magneti c tape, as it has a beginning-of-tape, an end-of-file (if one has been written), and an end-of-tape.
Note, however, that a sequential-access RAD file cannot be forward-spaced or backspaced over more than one fi Ie mark. A rewound sequential-access RAD file is positioned at beginning-of-tape. For both blocked and unblocked files, a record skip is a logical record skip.
UTILITY PROGRAM ORGANIZATION
The Utility program consists of two major sections: the Util-ity Program Control routine (always resident when the UtilUtil-ity program is operating), and the currently operating Uti lity subroutine. The Utility Program Control routine contains four interdependent elements:
1. The Program Executive~ which initializes the program (upon entry from RBM), interprets the !UTILITY con-trol command (explained in "Call ing Uti lity"), exer-cises control over the flow of control commands, handles normal and abort exits to the Monitor, and performs a"
II
0 checki ng for the Uti I i ty program.2. The Source Input Interpreter, which reads and scans Uti lity control commands for the Control Function Pro-cessor and the current Uti lity subroutine.
3. The Control Function Processor, which executes con-trol function commands common to all Uti I ity subroutines.
4. The Operator Communication routine, which outputs messages to OC and DO and receives key-in responses.
UTI UTY EXECUTIVE PROGRAM
When RBM reads a ! UTI UTY control command control is transferred to the Program Executive routine. The !UTI UTY control command is then scanned for parameters. If the name parameter is omitted (see "Calling Utility" below), it is assumed that on I y the Control Functi on Processor wi"
be used. Uti I ity control commands are read from the source input (SI) device.
If a specific Utility subroutine is requested, the Program Executive verifies that the subroutine is in storage; if not, an error message is written and an exit to RBM is taken, terminating the background operation. If the subroutine is present, initial ization of tables and flags occurs.
The Program Executive then transfers control to the requested Utility subroutine. The Utility subroutine uses the Source Input Interpreter to read all commands, and uses the Control Functi on Processor to execute control functi ons. All other control commands are interpreted and executed by the Uti-lity subroutine itself.
SOURCE IN PUT INTERPRETER
The Source Input Interpreter, which is called by the Program Executive routine, processes all control commands that are read by the Utility program. Utility control commands are input from the SI device and listed on the DO device as they are interpreted.
Upon reading a command, the Source Input Interpreter de-termines whether the command is valid. If the syntax for a command is invalid, the following message is written on OC and DO:
INV CTl
! IUKEYIN
The operator response, either an S to continue or an X to abort, determines whether or not the Utility program continues.
If the response is S, the Source Input Interpreter reads the next control command from SI. If the command is valid, it may be interpreted and executed either by the Utility sub-routine or by the Control Function Processor.
CONTROL FUNCTION PROCESSOR
The Control Functi on Processor interprets and executes com-mands that are common to a" Uti I i ty subrouti nes. If any of
Utility 99
the control commands interpreted and executed by the Control Function Processor contains an invalid operational label, the following message is output: by the Operator Communication routine.
If a response is required from the operator, the Operator Communication routine types the following message:
! UKEYIN
The Program Control routine performs all input/output checking for the Uti I ity program. Messages regardi ng input/
output errors are written on both the OC and DO devices.
CONTROL ROUTINE OPERATIONAL LABELS
Four operational labels are reserved for the Program Control routine. Their use is restricted to the functions below; they may not be used in place of the labels required by the vari-ous Utility subroutines explained later.
Label Explanation SI
DO
Device for RBM control command input, Utility program control commands, and various modifica-tion source inputs.
Device for listing of control commands (as they are interpreted), messages, error conditions, op-erator responses, etc. DO provides a permanent log of th~ contr~1 command "flow. This' is the only operational label for the Program Control routine that can be assigned to device-file number
a
re-sponses from the operator (always via the keyboard/printer).
Temporary RAD fi I e used for pres tori ng commands read from SI.
Utility functions are generally executed dynamically; that is, control commands are interpreted and executed as they pa-rameter, the! *PRESTORE control command allows the user the option of prestoring SI input until an EOD card image is encountered. For RBM Utilities, prestored commands are written on a temporary RAD file {using operational label X5}
and read from the RAD for interpretation and execution.