ERR:FIL PROGRAM
ERRFILE FORMATS
ERRORS
J
LIST SUMMARY - - - ,
ERRORS AND SUMMARY
L . . - - TO M : D O
-[{
ON
1 (~~Lol]
OVER M.EO
INTO fn~me
[ (
AFTER
1
BEGINNING
L - SINCE
STARTING FROM
{ ~~~~/yy
hh:mm}] [AND END]mm/dd/yy :
ERR:FIL PROGRAM
ERR:FIL copies the special file created by ERRLOG onto a normal keyed file (ERRFILE) that is more readily availabJe to diagnostic programs. While copying ERRLOG's file, ERR:FIL compi les a summary of the errors copied. A fi Ie of these summaries (SUMFILE), which contains a summary of errors for each hour of operation and a master summary of all errors, is also maintained by ERR:FIL.
. ERR:FIL is a ghost j.ob that is awakened by ERRLOG when-ever five errors have been recorded. ERR:FIL may also be awakened by a program with diagnostic privilege by using the initiate job CAL (CALl,6 FPT)or by an operator key-in qf GJOB ERR:FIL. ERR:FIL may also be run by an on-line user running under account :SYS with diagnostic privilege by typing ! ERR:FIL.
Description
Terminates the ERR: LIST program and returns control to the executive level.
Prints a sample of the correct format for the LIST command.
Lists the error records in the ERRFILE and/or a sum-mary of records after a specified starting time and/or date.
ERRORS specifies a I isting of errors.
SUMMARY specifies a summary by type and device.
ME specifies the on-I ine terminal.
M: LO specifies output to the device assigned to the LO DCB.
M:DO specifies output to the device assigned to the DO DCB.
M:EO specifies output to the device assigned to the EO DCB.
fname specifies the name of a file into whi ch the errors and/or summary are to be written.
mm/dd/yy specifies month, day, and year the list is to start.
hh:mm specifies the time the list is to start.
AND END specifies the program is to termi-nate after the listing is complete.
The special fi Ie written by ERRLOG and the core buffers of ERRLOG, which are also input to ERR:FIL, are described in the following sections.
ERRFILE FORMATS
ERRFILE is a keyed file built and updated by ERR:FIL for use by diagnostic programs. The file contains one record for each error entry in the fi Ie created by ERRLOG .
The format of each record is identical to the format of the error entrie·s in ERRLOG's file (ERRFILE). The keys for this file contain the Julian date in packed decimal, the time of the error in EBCDIC, and a sequence number for errors with
ERR:FIL Program 177
the same time tag. This sequence number is reset to zero for eacn entry with a new time tag. The format of the key is
hhmm, is the time (hours and minutes) in E8CDIC.
n is the sequence number.
08 yy
h h
n where
Od m
dd m
The first record of ERRfllE is the key of the Jast record in ERRFI LE and has a key of zero.
08 is the number of bytes in the key.
While copying records into ERRFILE, consistency and error checks are made on the input data. If any errors or in-consistencies are found, "copy error" records ani!! written and a "copy error II counter in the summary record is in-cremented. The error and consistency checks, recovery actions taken, and the format of the copy error records are described below. The terminology used in the error record formats is defined in Table 59.
yyOddd is the Julian date in packed decimal.
Term Account AIO CC
AIO Status
Alternate I/O Address
Bytes Rema i n i ng
Consecutive, Keyed, Random
Count of Entries Identical to Prev i ous Entry
Count of Entries Lost
Current Command Doubleward
Caller's Address
OCT Index
OCT Index of Symbiont Device
Effective Address
Error Subcode
178 ERR:FIL Program
Table 59. Error Record Terminology Meaning
The doubleword used to identify a user's collection of files.
A 4-bit field representing the condition codes as returned by the hardware in response to an AIO instruction.
A 16-bit field representing the status as returned by the hardware in response to an'AIO instruction.
A 16-bit value representing an alternate physical I/O address by which a dual-access device can be referenced.
A 16-bit field representing the Remaining Byte Count (RBC) field as returned by the hardware in response to a TDV instruction.
Methods of organizing user fi les in CP-V (refer to the CP-V IBP Reference Manual, 90 1764).
The number of error log records wh ich are identical to one previously logged for identical reasons (excludes time records).
The number of error log records lost when logging becomes temporari Iy im-possible for any reason.
A 64-bit value representing the command doubleword currently being pro-cessed for a device (indicated by the TDV status OW).
The address back to which the error logging routine is returned when logging is complete; used in isolating software faults.
The 8-bit value indicating the order in which the device is configured into the system (at SYSGEN).
The 8-bit value indicating the order in which the device associated with the symbiont is configured into the system (at SYSGEN).
A 32-bit value representing the final address computed for the instruction pointed to by the instruction addr~ss (IA) in the PSD.
An 8-bit field indicating which of several types of file inconsistencies has occurred (see CP-V/BP Reference Manual, 90 1764).
Term File Name
Granule HIO CC
HIO Status
I/O Address I/O Count
Julian Day
Length
Memory Status Words (Sigma 9 only)
MFI (Sigma 6 or 7 only)
Mode
Model Number
Number of Parity Errors
Primary I/o Address
PSD
Rea I Address
Recovery Count
Relative Sector Address
Relative Time
Table 59. Error Record Terminology (cont.) Meaning
The TEXTC name used to identify a collection of user data on secondary storage.
The unit of secondary storage allocation equal to 2048 bytes (usually 2 sectors).
A 4-bit value (bits 0 - 3 of designated byte) representing the condition codes as returned by the hardware in response to an HIO instruction.
A 16-bit value representing the status as returned by the hardware in response to an HIO instruction.
A 16-bit value representing the physical I/o address.
A 32-bit value representing twice the number of SIO instructions executed for the device.
A 16-bitvalue representing the Julian day of the year (e.g., March 1 would be represented as X 13D I) when the error was logged.
An 8-bit value in the second byte of the error log record representing the number of useful 32-bit words contained in the error log record. It includes the first word in the count.
Each word is a 32-bit value representing data returned by the hardware in response to an LMS instruction.
A 4-bit value representing the current state of the memory fault indicators returned by the hardware in response to an RD instruction. All memory fault indicators wi II be reset.
A 16-bit value representing the manner in which the file was last referenced (see Cp-V/Sp Reference Manual, 90 1764).
A 16-bit value representing the conversion of a number (assigned by Field Engineering to uniquely identify peripheral devices) to a binary value (e.g., 7242 would be represented as X 11 CA I).
A 16-bit value representi:1g the number of bad locations causing memory parity errors (only the first 14 bad locations are entered in the log if the number of errors is greater than 14).
A 16-bit value representing the physical I/o address by which a device can be referenced (see AI ternate I/o Address).
A 64-bit value representing the program status doubleword.
A 32-bit value representing the actual memory address (in a mapped system, this is the same as the address in the IA field of the PSD).
An 8-bit value initialized to zero at system initialization and incremented by the value one for every system recovery.
A sector is 256 words. Each sector on a given device is numbered zero through device end. CP-V maintains file pointers by relative sector number, thereby simplifying the logic necessary to address different devices.
A 32-bit value representing milliseconds since midnight. Resolution is 2 msec.
ERR:FIL Program 179
Term
Re'Qtive Time Resolution
Retries Remaining
Retry Request
Screech Code Screech Subcode
Seek Address
$en5e Information
SIO CC
SIO Status
Site Identification
Startup Type
Subchannel Status
Symbiont Fi Ie
TOV CC
TOV Current Command DA
TOV Status Ooubleword
TIO CC
TIO Status
Trap CC
180 ERR:FIL Program
Table 59. Error Record Terminology (cont.) Meaning
An a-bit value, n, such that actual relative time resolution == 2 msec. (e.g., n = 1 for a resol ution of 500HZ or 2 msec.).
An a-bit value representing Retry Request minus the number of entries ot ...
tempted. The range is between Retry Request and .. 1. A value of -1 indieates the operation was terminated due to retry count rundown.
An B ... bit value representing the maximum number of retries after which a device error is returned to the requester. This value is obtained from the requester's DCB.
The code used by CP-V to identify the system failure which has occurred.
An a-bit field identifying which type of a specific and similar set of system failures has occurred. (See Software check codes in the CP-V/OPS Reference Manual, 90 1675.)
The physical disk address last used to access th is device.
The diagnostic information returned from the device as a result of sending a
"sense" order to the device.
A 4-bit value (bits 0 - 3 of designated byte) representing the condition codes as returned by the hardware in response to an SIO instruction.
A 16-bit value representing the status as returned by the hardware in response to an SIO instruction.
A 64-bit field; the first 32 bits contain the EBCOIC representation of the SYSGEN input parameter for version; the second 32 bits contain blanks (X'40').
An a-bit field indicating which of several types of system initialization was used.
The status of the I/O subchannel received from the hardware as a result of a TDV instruction.
A CP-V system special file for buffering data between the CPU and slower speed line printers, card punchers, etc.
A 4-bit value (bits 0 - 3 of designated byte) representing the condition codes as returned by the hardware in response to a TIO instruction.
A 24-bit field representing the current command doubleword address used in obtaining the device status with a TDV instruction.
A 24-bit field representing the subchannel status, as current command double-word, device status, and byte count as returned by the hardware in response to a TOV instruction.
A 4-bit value (bits 0 - 3 of designated byte) representing the condition codes as returned by the hardware in response to a TIO instruction.
A 16-bit value representing the status as returned by the hardware in response to a TIO instruction.
A 4 ... bit value (bits 0 - 3 of designated byte) representing the condition codes as returned by the hardware when certain traps occur.
Term
Trapped Instruction
Type
Unit Address
Unit Type
User ID
User Number
Version
Volume Serial Number
Year
READ ERROR
Table 59. Error Record Terminology (cont.) Meaning
A 32-bit va~ue representing the contents of the location pointed to by the instruction address (IA) in the PSD.
An 8-bit value in the first byte of the error record which identifies the type of record.
A 6-bit value (bits 2 - 7 of designated byte) representing the address by which a processor can be referenced; the value is composed of a 3-bit cluster number followed by a 3-bit unit number.
An 8-bit value specifying the type of processor. Bit 0 of the designated byte indicates the presence of the processor in the current operational configuration (0
=
present, 1=
not present).A 16-bit value which is a unique number assigned by the system to the partic-ular job or on-line session.
An 8-bit value which is the index into internal system tables used to access user specific information.
The version identifier of the system running (i .e., AOO, BOO, etc.). This field is one byte in length. The letter of the version is stored in the first four bits and the number of the version is stored in the second four bits.
A 4- or 6-byte field supplied by a user to identify either a tape or private pack.
A 16-bit binary value representing the current year minus 1900 (e.g., 1973 is represented as X 149 1).
End Read Error If the condition codes set by T :RDERLOG indicate a read
error, a copy error record (Read Error) is written and copy-ing of the record is attempted. If inconsistencies are found in the record, a copy of the bad record is placed in the ERRFILE file, followed by the End Read Error record. If no inconsistencies are found, the record is processed normally and the Read Error record remains in the ERRFILE fi Ie. The record formats are
word 0
word 1
Read Error word 0
word 1
ERRLOG RECORD LENGTH ERROR
If the length of the ERRLOG record is greater than 256, a copy error record followed by the ERR LOG record is written on ERRFILE. No attempt is made to copy this record in the detai I ed format. The record format is
word 0
ERR:FIL Program 181
word 1
word 2
s r 2
INCORRECT TIME
If the time of an entry is out of sequence, i. e. I if it is earlier than the time of the rost record and the data has not changed, a copy error record is written on ERRFILE followed by the ERRLOG record. The time of this entry is then used for thet key and processing continues. The record format is word 0
word 1
word 2
where index is the displacement within the ERRLOG record of the first word of erroneous entry.
ILLEGAL ENTRY TYPE
If the entry type is not one of the legal types, a copy error record followed by the ERR LOG record is written on ERRFILE.
No attempt is made to copy the remainder of the record.
The record format is
word 0
word 1
word 2
where index is the displacement within the ERRLOG record of the first word of erroneous entry.
182 ERR:FIL Program
~ Errors that occur while booting have a time tag of 24XX but the keys of these records contain the cur-rent date and 0011 for the time.
If read or write errors are detected whi Ie reading or writing ERRFILE and SUM FILE, they are ignored.
'M1enever I/o errors or certain unusual condition$ occur, an entry will be made into the ERRLOG file. Thtsentry will contain any information pertinent to the condition.
Word 0 of each entry wi II have a code indicating whiGh error or unusual condition is present along with the number of words in the entry (inc luding word 0). Time (hhmm) and
Device Name (yyndd) are in EBCDIC.
There or. no error log entries for the following two interrupts.
MEMORY FAULT INTERRUPT
The Memory Fault Interrupt (MFI) is triggered when an error is detected during 0 memory access by either the CPU or an lOP. If the MFI is triggered by the CPU, a parity error trap will also occur unless the error is a Loop Check Parity error or Overtemperature condition. The parity error trap routine performs error recovery, logs the error, and clears the MFI to ovoid duplicate processing. The MFI service routine therefore expects to only handle errors detected during on lOP memory access and Loop Check and Overtemperature errors. The Loop Check and Overtemperature errors are processed by the memory parity program and the system re-covery program is entered with code X'231• The other er-rors are logged by the device handler, which also performs the required recovery.
PROCESSOR FAULT INTERRUPT
The Processor Fault Interrupt is not enabled in CP-V. Errors that couse this interrupt in a monoprocessor system are han-dled by the I/O Interrupt Routines.
SIO FAILURE
This record is logged when CC 1 and/or CC2 are set after execution of the SIO instruction.
word 0
word 1
word 2
word 3
word 4
word 5
TIME OUT
This record is logged when the I/O interrupt does not occur within a specified time period in response to an I/o instruc-tion. The format for time out (type XI12') is identical to that for device error (type XI15 ') except that HIO CC and status replaces AIO CC and status.
UNEXPECTED INTERRUPT
This record is logged when an interrupt, other than an at-tention interrupt, is received from a known device for which no I/O operations have been started by the system.
word 0
word 1
word 2
word 3
DEVIC E ERROR
This record is logged when general analysis of the status re-ceived from an Ala, TDV, or
no
lindicates an error which resu I ted from the I/o ope.-ation.word 0
word 1
word 2
word 3
word-4
word 5
words 6 and 7
Current command doubleword
o I 2 3 1 4 5 6 7 1 8 9 1 0 11112 13 14 15116 17 18191202122 2312425 2t 2:12f 29 3031
word 8
word 9
words 10 and 11
Volume serial number
(Six characters for
I
OriginalI
CurrentANS tapes) function code function code
o I 2 314 5 6 718 9 10 11112 13 14 15116 17 18 19120 21 22 23124 25 26 2712629 30 31
word 12
ERR:FIL Program 183
The format for device error (type X'15') is identical to that for devi.ce timeout (type X'12') except that HIO CC and status isvsed in place of AIO CC and status.
SECONDARY RECORD FOR DISK PACK, RAD, TAPE, AND R8f DEVICE ERRORS
This re(:ord is generated as a result of a previous device error and contains device status which corresponds to the information contained in the Device Error record (type X '15') preceding this record.
word 0
word 1
words 2 and following
Sense information (left justified) Device Len~th (in b~tes)
7242 10
Disk A, B 16 1600 bpi tape 6
9T tape 1
RAP 3
7670 RBT 1
0 1 2 3 14 5 6 71·8 9 10 IIn2 13 14 15116 17 18 1912021-221:311425 26 27f28 29 30 31
The
II
0 address links the seconda ry record to the cor-responding device error entry.HARDWARE ERROR
This record is logged when a hardware error has been de-tected, the type of error being indicated by the Trap CC.
For Sigma 6 and 7, this record is generated as a result of the memory parity interrupt associated with location X'56'.
For Sigma 9, this record is generated as a result of the par-ity error trap associated with location X'4C'.
word 0
word 1
184 ERR:FIl Program
words 2 and 3
PSP word 1 PSD word 2
0 1 2 3 T4 5 "·7 8 9 10 11112 13 14 15116 17 18 19120 21 22 23124 25 26 27128 29 30 31
words 4 a.nd 5
Reserved for future use
I f T"T ~Ti 5 6 7 8 9 10 11112 13 14 15116 17 18 19120 21 22 2:H24 25 26 2712829 30 31
word 6
word 7
word 8
4 5 6 8 9
Effective address of trapped instruction;
o
if indeterminateSYSTEM STARTUP
This error is logged at system initialization and at every recovery •
word 0
word
Relativ~
time : .I
5 6 718 9 10 11112 13 1415161718191202122 23 24 25 2627128293031
word 2
Year !Iast two digits;
In binary) word 3
where
screech code and screech subcode are defined in the CP-V/OPS Reference Manual, 90 1675.
recovery count is set to 0 for initial startvp as de-fined by startup types 1, 2, or 3 below.
startup type specifies the type of startup.
1 - Initial PO boot 2 - PO boot with fi les
3 - System device boot (no recovery) 4 - System recovery
5 - Operator recovery