where ALL incl udes all RAD areas except Background, Temporary, and Checkpoint.
Examples:
1. Dump spec i fi ed areas to secondary storage:
(,SAVE S',Be,D'
This example specifies that RAD areas SP, BP, and D2, with a preceding bootstrap loader, are to be saved on the BO device for subsequent reloading.
2. Dump all RAD areas to secondary storage:
This example specifies that all RAD areas, with a pre-ceding bootstrap, are to be saved on the BO device for subsequent reloading.
88 RAD Editor Commands
:RESTORE The :RESTORE command restores the specified permanent RAD areas that were saved by the :SAVE command.
Input is read from the BI device (using the M:BI DCB), and the bootstrap is ignored. Read after write is employed to verify the data restored.
The form of the command is
(RESTORE ZZ,", ...
Example:
(RESTORE S',BP,D'
This example specifies that the RAD areas SP, BP, and D2 (previously saved with a :SAVE directive) are to be restored.
:BDTRACK The :BDTRACK command specifies the RAD and the hexadec ima I track numbers that are not to be used by the RAD Editor. A track containing a sector of the file directory is not permitted to be removed from use.
The form of the command is
:BDTRACK yyndd,number~numberJ.
Example:
(BDTRACK DCAFO, 10, II
This example specifies that the RAD Editor is to be inhibited from usi ng tracks 10 and 11 on the RAD DCAFO.
:GDTRACK The :GDTRACK command specifies the RAD and the hexadecimal track numbers that now can be used by the RAD Editor. The tracks were previously removed from use by the :BDTRACK command.
The form of the command is
:GDTRACK yyndd,number[, number].
Example:
(GDTRACK
DCAFO, 10, 11This example specifies that previously inhibited tracks 10 and 11 are to be restored for use by the RAD Editor.
•
ERROR MESSAGES
If the Editor aborts because of an irrecoverable I/O error, the physical device name is included in the abort message.The RAD Editor outputs error messages on the OC and LL devices. If OC and LL are assigned to the same device, duplication of messages on LL is suppressed. If an operator response is required, the RAD Editor will call the Monitor
"WAIT" routine. The operator initiates a console interrupt and keys in one of the following commands to the Monitor.
The error messages output by the RAD Editor and their mean-ings are given in Table 15.
C Continue and read next record from theC device.
RAD RESTORATION MESSAGES
X Abort RAD Editor and return control to Monitor.
cae
Continue and read a record from the OCde-The messages itemized in Table 16 are written on the keyboard/printer during RAD restoration via the bootstrap loader produced by SAVE. Unless otherwise specified, the computer will go into a WAIT after writing a message.
vice (used only in conjunction with the error mes-sage "ERROR ITEM xx").
Table 15. RAD Editor Error Messages
Message Meaning
AREA xx CANNOT CONTAIN Illegal area specified. Only the FP A RESIDENT FOREGROUND area can contain a resident foreground
PROGRAM program
AREA xx CKSM ERROR A checksum error exists on the RAD SAVE tape in the specified area.
AREA xx CONTAINS NO Speci fied area contains no fi I es.
FILES
AREA xx INCOMPATIBILITY Attempting to restore specified area onto a different type of RAD from which it was saved, or the area to be restored is too I arge for the same area using the current Master Directory.
AREA xx IS NOT ALLOCATED Specified area was not allocated at SYSGEN.
AREA SPECIFIED DOES NOT An area other than SP or FP was speci-CONTAIN A LIBRARY fied that does not contain a library.
AREA SPECIFIED IS NOT An attempt has been made to use area MAINTAINED BY THE RAD CK, XA, or BT which is not maintained
EDITOR by the RAD Editor.
AREA xx TRUNCATED Specified area being restored is larger than the same area using the current Master Directory, but the data that was lost contained all zeros.
BUFFER SMALLER THAN Data read exceeds the amount of avai
1-DATA READ abl e buffer space.
CKSM ERR ON SAVE A checksum error has been
encoun-TAPE tered while verifying the RAD SAVE
tape.
Action Taken Operation is aborted.
Operation is aborted.
Edi tor continues.
Operation is aborted.
Operati on is aborted.
I Operation is aborted.
Operation is aborted.
Operation continues.
Operation is aborted.
Operation is aborted.
Error Messages/RAD Restoration Messages 89
•
Table 15. RAD Editor Error Messages (cont.)
•
Message Meaning Action Taken
CKSM ERROR Last record in the object module If the operator response is C, the being read has a checksum error. Editor reads the next record from the
specified device.
DUPLICATE DEF xxxxxxxx Relocatable Object Module being RAD Editor skips to the end of the copied to the library contai ns dup- module. A key-in of C causes the I icate defi nit ions. Editor to read the next record from
the specified device.
DUPLICATE FILE An attempt has been made to allocate Operation is aborted.
a file using a name which already exists.
EOT on {yyndd Unexpected end-of-tape was encoun- Operation was aborted area, name tered on the specified device or file.
ERROR ITEM xx Item number xx on the command is If the operator response is C, the
in error. Editor reads the next record from
the C device. If the operator response is COC, the next record is read from the OC device. This will enable operator to rectify a directive error.
FILE xxxxxxxx WAS NOT Fi Ie was not truncated because fi Ie Editor continues TRUNCATED. FSIZE = 0 size being 0 suggests either a direct
access fi Ie or a fi Ie with 0 records.
ILLEGAL BINARY RECORD An illegal binary record (first byte If the operator response is C, the not X'lC', X'3C') has been read Editor reads the next record from the with an object module. specified device.
ILLEGAL FILE NAME An attempt has been made to allocate Operation is aborted.
a file using GO, OV, or X1-X9 as a file name.
ILLEGAL LOAD ITEM xx I Re locatable Object Module to the RAD Editor skips to the end of the library contains an illegal load module. A key-in of C causes the
item. Editor to read the next record from
the specified device.
ILLEGAL OPTION xxx Option specified is not permitted on Operation is aborted.
a :COPY command.
ILLEGAL USE OF :COPY The specified combination of input Operation is aborted.
and output devices on the :COPY command is prohibited.
INVALID RSIZE. UNBLOCKED Maximum record size for a blocked Editor continues.
ORGANIZATION GIVEN fi Ie has been exceeded. Unblocked orgnization given.
KEY ERR Operator key-in is erroneous. Key-in has to be either C, COC,
or X.
NOT ENUF BACKG SPACE Insufficient background space to Operation is aborted.
perform the requested operation.
90 Error Messages
Table 15. RAD Editor Error Messages (cont.)
•
Message Meaning Action Taken
RAD OVERFLOW Allocating the amount of RAD storage Operation is aborted.
indicated by the "file" parameter on the :ALLOT command would cause the permanent RAD area indicated by the
"directory" parameter to overflow.
RECORD SIZES DIFFER ON Record sizes differ on copying from RAD Operation is aborted.
INPUT AND OUTPUT FILES fi Ie to RAD fi Ie.
REFERENCES TO F4:COM An external definition or reference RAD Editor skips to the end of the NOT ALLOWED F4:COM encountered in a Relocatable module. A key-in of C causes the
Object Module being copied to the Editor to read the next record from
library. the specified device.
ROM DOES NOT CONTAIN Relocatable Object Module being A key-in of C causes the Editor to A DEF copied does not contain an external read the next record from the
speci-definition. fied device.
SAVE TAPE OK RAD SAVE tape has been verified No action.
correctly.
SEQ ERROR Last record in the object module If the operator response is C, the being read has a sequence error. Editor reads the next record from
the specified device.
SPECIFIED FILE DOES File does not exist within the speci- Operation is aborted.
NOT EXIST fied area.
SPECIFIED ROM DOES NOT Relocatable Object Module does not Operation is aborted.
EXIST exist within the specified library.
SREC VALUE GREATER THAN Parameter error on the :DUMP com- Operation is aborted.
EREC VALUE mand. The last record to be dumped
precedes the initial record to be dumped.
TRACT xxxxx CANNOT BE Illegal attempt to remove a track from Operation is aborted.
DELETED use containing a sector of the file
directory. Removal would prevent accessing of fi les or other sectors of the directory.
UNABLE TO FIND AREA xx Specified area cannot be found on the Operation is aborted.
RAD SAVE tape during a :RESTORE operation.
yyndd WRT PROT Specified RAD is write-protected. Operator shou Id take appropriate action: interrupt and key in "SYC"
or reset the appropriate RAD pro-tection switches. Or, if the job is not allowed to write on protected areas of the RAD, interrupt and key in "X" to abort.
Error Messages 91
•
Table 16. RAD Restoration Messages
Message Meaning Resulting Action
CKSM ERROR A checksum error has occurred in If the WAIT condition is cleared, the reading the SAVE tape. bootstrap loader continues and accepts
the bad record.
RAD RESTORED OK The RAD restoration has been suc- Control is transferred from the RAD
cessfu II y compl eted. bootstrap.
TRK = xxxx Specifies the contents of the RAD If the data being written contains all DATA = ALL ZEROS controller address register in hexa- zeros, this information is output. If dec i mal at the ti me of a check wri te the WAIT condition is cleared, the
error. bootstrap loader continues.
yyndd ERROR, A parity or transmission error has oc- There is no recovery.
SB = xxxx curred on devi ce yyndd. Both the device status byte and operational status byte are displayed following 11 SB =" •
yyndd UNRECOG., An unrecognized status has been re- Upon clearing the WAIT condition, SB = xxxx turned from the indicated device. Both the operation is retried.
the device status byte and operational status byte are displayed followi ng "SB=".
yyndd UNUS. END, i An unusua I end status has been returned There is no recovery on a read op-TDV = xxxx from the specified device. Both the TDV erati on. On a write operation, the
status byte and operational status byte write is tried again after the WAIT is are displayed following "SB=". cleared.
yyndd WRT PROT The RAD is write-protected. Program wi II attempt the RAD write after an SY key-in.
92 RAD Restoration Messages
8. PREPARING THE PROGRAM DECK
The following examples show some of the ways program decks may be prepared for RBM operation. Un less stated otherwise, standard default cases for device assignments are assumed.