IBM System/370 145 Manual page 209

are, therefore, compatible for System/310 models operating in BC mode,
for system/360 Models 65 and up, and for MP/65 systems.
Figure 50. 10.6 at the end of t:his subsection shows the general flow
of programmed error recovery proc:edures after an I/O interruption.
ERROR RECOVERY PROCEDURES (ERP'S) FOR OS
These device-dependent error
~:outines
are a standard part of the
control program generated fo~ anlr OS environment. OS ERP's are modified
to accept and use limited channel logout data formatted by the CCH
routine after a channel error.
When a channel or an I/O device error occurs on a Model 145, the
appropriate ERP is scheduled to ~erform recovery procedures. If the
error is corrected, operations continue normally. If the error cannot
be corrected (it is permanent), error recording occurs. If I/O RMS or a
user-written permanent error hand,ling routine is not present, the
affected task is abnormally terminated. The operator is notified of
permanent I/O errors. (See Figure 50.10.6.)
STATISTICAL DATA RECORDER (SDR) AND OUTBOARD RECORDER (OBR) FOR OS
OBR and SDR routines are included in alIOs control programs. These
routines are requested by the ERP routines during their processing of
error conditions. The SOR routine is requested when one of the error
statistics counters becomes fu11. counters are maintained in the
resident
cont~ol
program storage ,area for each I/O device in the system
configuration. SDR records error statistics in the appropriate SDR
summary record for a device that is contained in the error log data set
(SYS1.LOGREC). This ensuresreco:~din9 of temporary I/O device error
data. The OBa routine records bo,th temporary and permanent channel
errors and writes an outboard record containing pertinent status data
whenever a permanent error occurs for a device. SOR is also executed to
write accumulated' statistics for 1that device when a permanent error
occurs. (see Figure 50.10.6.)
ENVIRONMENT RECORDING, EDIT, AND ]l?RINT PROGRAM (EREP) FOR OS
OS EREP is a standard system u1t:ili ty that can be initiated as a job
step via standard job control sta1:.ements at any time. It is designed to
edit and print the error records
1~itten
by System/370 OS RMS routines.
EREP contains model-dependent rou1t:.ines and, therefore, an EREP program
that handles error records for on4~ System/370 model in BC mode cannot be
used to handle the error records for another System/310 model. It
performs the following:
1. Edits and prints all error records contained in SYS1.LOGREC.
These records have been constructed and/or written by MCH, CCH,
OBR, and SOR routines.
2. Accumulates a history of specified record types from SYS1.LOGREC
by creating or updating an accumulation data set
3. Edits and prints a summary of selected records from SYS1.LOGREC
or an accumulation data set:
I/O RMS FOR OS
I/O RMS routines are optiona1, model-independent routines in MFT and
MVT environments. These reconfi9u~ation procedures attempt to minimize
A Guide to the IBM System/310 Mode~l 145 199