Trailing-Edge
-
PDP-10 Archives
-
BB-M856A-BB
-
tpemsg.spe
There are no other files named tpemsg.spe in the archive.
Tape Subsystem Report Formats
-----------------------------
@@TM0X_SUMM
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* Tape Subsystem Error Summary *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tape Subsystem TM02/03 Error Entries Summarized by Error Type.
Entries Error Type
------- ----------
%%%%%% Read Data Errors
%%%%%% Read Device Errors
%%%%%% Read Software Errors
%%%%%% Write Data Errors
%%%%%% Write Device Errors
%%%%%% Write Software Errors
%%%%%% Other errors
%%%%%% Massbus (control bus) Parity Errors
%%%%%% Massbus (data bus) Parity Errors
@@TX0X_SUMM
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* Tape Subsystem Error Summary *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Tape Subsystem TX02/01 Error Entries Summarized by Error Type.
Entries Error Type
------- ----------
%%%%%% Read Data Errors
%%%%%% Read Device Errors
%%%%%% Read Software Errors
%%%%%% Write Data Errors
%%%%%% Write Device Errors
%%%%%% Write Software Errors
%%%%%% Other errors
%%%%%% Massbus (control bus) Parity Errors
%%%%%% Massbus (data bus) Parity Errors
@@
-------------------------Common Report Elements-------------------------
@@TIME_STAMP_MSG1
Time: ## To ## Span: ##
@@TIME_STAMP_MSG2
Time of Error: ##
@@INT_ARR_DSTRN1
%%%%%%%%% %%%%%%%%%%% %%%%%% %%%%%% %%%%%%%%%%%% %%%%%%
@@USER_MSG
User Id : ##
@@USER_ID
##
@@PGM_MSG
Pgm Id : ##
@@PGM_ID
##
@@MED_MSG
Media id : ##
@@MED_ID
##
@@OP_MSG
Operation : ##
@@OPERATION
##
@@OPR_MSG
Operation : ##
Media
ID Unit ID
----- -------
@@UNIT_ID
## (##, SN: ##) with ## errors.
Additional Data:
@@UNITMSG
## (##, SN: ##) reports:
@@HISTOGRAM
%%%%% - %%%%% ! %%%% ##
@@RD_DATA_UNIT_MSG1
Read Data - DATA TRACK / READ AMPLIFIER Theory ... ##
## (##, SN: ##) reports:
## Read Data Errors.
Physical Track / Data Track
Possible multi
1/5 2/7 3/3 4/P 5/2 6/1 7/0 8/6 9/4 Track Failures
--- --- --- --- --- --- --- --- --- --------------
%%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%%%%
Note: Use this template for 7 track drives (1/5 2/4 3/3 4/2 5/1 6/0 7/P)
@@TIE_MSG
We suspect that track ## is failing.
@@INT_TIM_DSTRN
Time Between Number of
Consecutive Characters Track in Media User Program
Errors Transfered Error I.D. I.D. I.D.
------------ ---------- -------- ----- ---- --------
@@RD_DATA_UNIT_MSG2
Read Data - Error Rate Greater Than 1 per Million Transfers ##
##(##, SN:##) reports:
## Read Data Errors.
Physical Track / Data Track
Possible Multi
1/5 2/7 3/3 4/P 5/2 6/1 7/0 8/6 9/4 Track Failures
--- --- --- --- --- --- --- --- --- --------------
%%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%%%%
Note: Use this template for 7 track drives (1/5 2/4 3/3 4/2 5/1 6/0 7/P)
@@RD_DATA_UNIT_MSG3
Read Data - Error Rate Less Than 1 per Million Transfers ... ##
##(##, SN:##) reports:
## Read Data Errors
Physical Track / Data Track
Possible Multi
1/5 2/7 3/3 4/P 5/2 6/1 7/0 8/6 9/4 Track Failures
--- --- --- --- --- --- --- --- --- --------------
%%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%%%%
Note: Use this template for 7 track drives (1/5 2/4 3/3 4/2 5/1 6/0 7/P)
@@RD_DATA_UNIT_MSG4
Read Data - Data Error Summary by Data Track ... ##
##(##, SN:##) reports:
## Read Data Errors
Physical Track / Data Track
Possible Multi
1/5 2/7 3/3 4/P 5/2 6/1 7/0 8/6 9/4 Track Failures
--- --- --- --- --- --- --- --- --- --------------
%%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%% %%%%%%
Note: Use this template for 7 track drives (1/5 2/4 3/3 4/2 5/1 6/0 7/P)
@@RD_DATA_MED_MSG5
Read Data - Media BAD SPOT Theory ... ##
Media I D: ## Recording Mode: ## was identified with
read errors as noted against the following drives:
@@
@@RD_DATA_MED_MSG6
Media I D: ## Recording Mode: ## was identified with
read errors as noted against the following drives:
@@
-----------------TM0X error formats--------------------------------------
@@TM_RD_DATA_SUM
Read Data - Data Error Summary ... [2.1.1.6]
@@1TM_RD_DATA_MSG
##(##, SN:##) reports:
Media Mode Number of
I.D. PE/NRZI CS/ITM COR/CRC PEF/LRC INC/VPE Occurrences
----- ------- ------ ------- ------- ------- -----------
@@2TM_RD_DATA_MSG
%%%%%% %%%% %% %% %% %% %%%%
@@RD_DATA_MED_SUM
+----------------------------------------------------------------------+
! The following is the SUMMARY of read data errors in media. Note the !
! errors indicate the number of bad spots as seen by the drive on which !
! the media was mounted. !
+-----------------------------------------------------------------------+
Read Data - Media BAD SPOT Summary ... ##
@@1TM0X_RD_PWR_MSG
Read Data - POWER SUPPLY Theory ... [2.1.2.1]
##(##, SN:##) reports:
## Unsafe Errors that are most likely POWER SUPPLY failures.
@@2TM0X_RD_OFFLIN_MSG
Read Data - Drive OFFLINE Theory ... [2.1.2.2]
##(##, SN:##) reports:
## Unsafe Errors that are most likely off line errors.
@@3TM0X_RD_DEV_BLNK_MSG
Read Data - OPI Blank Tape Theory ... [2.1.2.3]
Media I D: ## was associated with
## OPI errors on the following drives:
Errors Drive
@@BLANK_MSG_DRIVE_LINE
%%%%%% ##(##, SN:##)
@@4TM0X_RD_DEV_SUM
Read Data - Device Error Summary ...[2.1.2.4]
## (##, SN: ##) reports:
Error bit Number of Span
Combinations Occurrences Window HH:MM:SS
D N F N F R I I
T E C S M M L L
E F E G T R R F
@@5TM0X_DEV_MSG
%% %% %% %% %% %% %% %% %%%% %%%%%%%%%%%%%%%_%%%%%%%%%%%%%%% %%%%%%%%%
@@6TM0X_DEV_MSG
%% %% %% %% %% %% %% %% %%%% %%%%%%%%%%%%%%%
@@1WR_DATA_MSG
Write Data - Bad Media Theory ... ##
Media I D: ## was associated with
## Write errors while mounted on the following drives:
## (##, SN: ##)
Additional Data:
@@1TM0X_WR_PWR_MSG
Write Data - POWER SUPPLY Theory ... [2.1.5.1]
##(##, SN:##) reports:
## Unsafe Errors that are most likely POWER SUPPLY failures.
@@2TM0X_WR_OFFLIN_MSG
Write Data - Drive OFFLINE Theory ... [2.1.5.2]
##(##, SN:##) reports:
## Unsafe Errors that are most likely off line errors.
@@3TM0X_WR_OPI_MSG
Write Data - OPI Write Timing Theory ... [2.1.5.3]
##(##, SN:##) reports:
## OPI errors while performing write operations.
@@4TM0X_WR_DEV_SUM
Write Data - Device Error Summary ...[2.1.5.4]
##(##, SN:##) reports
Error bit Number of Span
Combinations Occurrences Window HH:MM:SS
------------ ----------- ------ --------
D N F N F R I I
T E C S M M L L
E F E G T R R F
@@
----------------------TX0X Error formats----------------------------------
@@1TX_RD_DEV_VEL_MSG
Read Data - TAPE SLIPPAGE Theory ... [2.2.2.1]
##(##, SN:##) reports:
## Velocity Checks which indicate a possible CAPSTAN misadjustment
Additional Data:
@@2TX_RD_DEV_VEL_MSG
Read Data - TAPE SLIPPAGE Summary ... [2.2.2.2]
##(##, SN:##) reports:
## Velocity Checks which indicate a possible dirty CAPSTAN.
Additional Data:
@@3TX_RD_DEV_COL_MSG
Read Data - VACUUM COLUMN SENSOR Summary ...[2.2.2.3]
## (##, SN: ##) reports:
Left Right
Top/Bottom col. col. No. of Times Occurred
---------- ---- ---- ---------------------
@@4TX_RD_DEV_SUM
Read Data - Device Error Summary ... [2.2.2.4]
##(##, SN:##) reports:
@@5TX_RD_DEV_SUM
%%% Buss Out Check
%%% Overruns
%%% C/P Comp
%%% Reject TU
%%% Reset Key
%%% Cmnd Stat Reject
%%% Tach Start Fail
with %%%% occurrences in
---- Time of Error: ## ----
@@6TX_RD_DEV_SUM
%%% Buss Out Check
%%% Overruns
%%% C/P Comp
%%% Reject TU
%%% Reset Key
%%% Cmnd Stat Reject
%%% Tach Start Fail
with %%%% occurrences in
----Time: ## To ## Span: ## ----
@@1TX_WR_DEV_VEL_MSG
Write Data - TAPE SLIPPAGE Theory ... [2.2.5.1]
##(##, SN:##) reports:
## Velocity Checks which indicate a possible CAPSTAN misadjustment
Additional Data:
@@2TX_WR_DEV_VEL_MSG
Write Data - TAPE SLIPPAGE Summary ... [2.2.5.2]
##(##, SN:##) reports:
## Velocity Checks which indicate a possible dirty CAPSTAN.
Additional Data:
@@3TX_WR_DEV_COL_MSG
Write Data - VACUUM COLUMN SENSOR Summary ... [2.2.5.3]
##(##, SN:##) reports:
Left Right
Top/Bottom col. col. No. of Times Occurred
---------- ---- ---- ---------------------
@@4TX_WR_DEV_SUM
Write Data - Device Error Summary ... [2.2.5.4]
##(##, SN:##) reports:
@@5TX_WR_DEV_SUM
%%% Overruns
%%% C/P Compare
%%% Reject TU
%%% Write Trg VRC
%%% Write Current Fail
%%% DSE Failure
%%% Erase Hd. Failure
%%% Cmnd Stat Reject
%%% Record Not Detected
%%% Tach Start Fail
with %%%% occurrence in
---- Time : ## ----
@@6TX_WR_DEV_SUM
%%% Overruns
%%% C/P Compare
%%% Reject TU
%%% Write Trg VRC
%%% Write Current Fail
%%% DSE Failure
%%% Erase Hd. Failure
%%% Cmnd Stat Reject
%%% Record Not Detected
%%% Tach Start Fail
with %%%% occurrences in
---- Time : ## - ## span ##---
@@
@@CHAN_MSG
DX10 Data Channel Summary ... [2.2.7.9]
## (##, ##, SN: ##) reports:
## Channel Errors.
@@2TX0X_WR_DEV_CHAN_MSG
Write Device Error - DX20 Channel Error Theory ... [2.2.7.10]
## (##, SN: ##) reports:
## Channel Errors
@@
---------------------Some More Common Error Formats-----------------------
@@1RAE_THEORY
RAE(MCPE) Error - Massbus(control bus) controller theory ##
There were %%% Massbus (control bus) Parity Errors detected by
Controller(Adapter) no: ## (##) connected to channel ## (##).
@@2RAE_THEORY
RAE(MCPE) Error - Massbus (control bus) RH theory ... ##
RH No: ## (##) reports:
%%%% Massbus (control bus) Parity Errors associated with the
following controllers(adapters):
@@3RAE_THEORY
## Errors associated with ## number ##
@@RAE_THEORY_TM
+----------------------------------------------------------------------+
! If a tape subsystem reports Massbus (control bus) Parity Errors or !
! Control Bus Timeout Errors and if more than one TM02/03 detected the !
! errors, then suspect that RH or Massbus Cable. !
! If only one TM02/03 is involved, then suspect that TM02/03 !
! or Massbus Cable connected to that TM02/03. If there is only one !
! TM02/03 on the massbus, the problem could be RH, Massbus Cable or !
! TM02/03. !
+-----------------------------------------------------------------------+
@@RAE_THEORY_TX
+----------------------------------------------------------------------+
! If a tape subsystem reports Massbus (control bus) Parity Errors or !
! Control Bus Timeout Errors and if more than one DX20 detected the !
! errors, then suspect that RH or Massbus Cable. !
! If only one DX20 is involved, then suspect that DX20 or Massbus !
! Cable connected to that DX20. If there is only one DX20 on the !
! massbus, the problem could be RH, Massbus Cable or DX20. !
+-----------------------------------------------------------------------+
@@DPAR_RD_THEORY_TM
+-----------------------------------------------------------------------+
! If a tape subsystem reports Massbus (data bus) Parity Errors during !
! Data Reads and if the errors involve multiple controllers(TM02/O3), !
! then chances are the fault lies in the RH controller or cable. If, !
! however, the errors involve a single controller(TM02/03), then !
! chances are the fault lies in the controller(TM02/03) and has !
! something to do with the Massbus Interface Logic or controller cable. !
+-----------------------------------------------------------------------+
@@DPAR_RD_THEORY_TX
+-----------------------------------------------------------------------+
! If a tape subsystem reports Massbus (data bus) Parity Errors during !
! Data Reads and if the errors involve multiple controllers(DX20), !
! then chances are the fault lies in the RH controller or cable. If, !
! however, the errors involve a single controller( DX20 ), then !
! chances are the fault lies in the controller( DX20 ) and has !
! something to do with the Massbus Interface Logic or controller cable. !
+-----------------------------------------------------------------------+
@@1DPAR_RD_THEORY
RH DPE Error - Data Read/Massbus (data bus) RH theory ... ##
RH No: ## (##) reports:
%%%% Massbus (data bus) Parity Errors associated with the
following controllers(adapters) and their drives:
@@2DPAR_RD_THEORY
RH DPE Error - Data Read/Massbus(data bus) controller theory ##
## (##, SN: ##) was identified with
%%% Massbus (data bus) Parity Errors detected by
Controller(Adapter) no: ## (##) connected to channel ## (##).
@@3DPAR_RD_THEORY
## Errors in ## (##: ##, ##, SN: ##)
@@DPAR_WR_THEORY_TM
+-----------------------------------------------------------------------+
! If a tape subsystem reports Massbus (data bus) Parity Errors during !
! Data Writes and if the errors involve multiple RH controllers, then !
! chances are the fault has to do with the memory controller or the !
! channel. If, however, the errors involve a single RH controller !
! and multiple drive controllers, then chances are the fault lies in !
! the RH controller or the massbus. Finally, if the errors involve a !
! single TM02/03 controller then the fault is probably in the TM02/03 !
! controller and has something to do with the Massbus Interface Logic !
! or TM02/03 massbus cable. !
+-----------------------------------------------------------------------+
@@DPAR_WR_THEORY_TX
+-----------------------------------------------------------------------+
! If a tape subsystem reports Massbus (data bus) Parity Errors during !
! Data Writes and if the errors involve multiple RH controllers, then !
! chances are the fault has to do with the memory controller or the !
! channel. If, however, the errors involve a single RH controller !
! and multiple drive controllers, then chances are the fault lies in !
! the RH controller or the massbus. Finally, if the errors involve a !
! single DX20 controller then the fault is probably in the DX20 !
! controller and has something to do with the Massbus Interface Logic !
! or DX20 massbus cable. !
+-----------------------------------------------------------------------+
@@1DPAR_WR_THEORY
RH DPE Error - Data Write/Massbus(data bus) MBOX (UBA) theory ##
%%% different RH controllers report: (during data Write operations)
%%% Massbus (data bus) Parity Errors.
Additional Data:
@@2DPAR_WR_THEORY
RH DPE Error - Data Write/Massbus(data bus) RH theory ... ##
RH No: ## (##) reports (during Data Write operations)
%%% (RH detected) Massbus (data bus) Parity Errors.
@@3DPAR_WR_THEORY
RH DPE Error - Data Write/Massbus(data bus) RH theory ... ##
RH No: ## (##) reports (during Data Write operations)
%%% Massbus (data bus) Parity Errors as detected by the
following drive controllers(adapters):
@@4DPAR_WR_THEORY
RH DPE Error - Data Write/Massbus(data bus)DR. controller theory ##
## (##, SN: ##) reports: (during Data Write operations)
%%% (drive controller detected) Massbus (data bus) Parity Errors.
@@5DPAR_WR_THEORY
## Errors detected by ## (##: ##,##, SN: ##)
@@6DPAR_WR_THEORY
RH NO: ## (##) reports (during Data Write operations)
%%% (RH detected) Massbus (Data Bus) Parity Errors.
@@7DPAR_WR_THEORY
## (##: ##,##, SN: ##) reports: (during Data Write operations)
%%% (drive Controller detected) Massbus (data bus) Parity Errors.
@@UNIT_MED_MSG
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* SUMMARY of all Errors sorted by Media and Drive by *
* Operation. *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
@@
@@1UNIT_MSG
%%%%%% ##
@@2UNIT_MED_MSG
%%%%%% %%%%%% %%%%%
@@3UNIT_MED_MSG
%%%%%% %%%%%
@@WR_DATA_MSG3
+---------------------------------------------------------------------+
! The following is the SUMMARY of bad spots in the respective media !
! as reported by the respective drives on which the media was mounted.!
! Note no. of errors here means number of bad spots in the media if !
! the media was written upon only once. !
+---------------------------------------------------------------------+
Write Data - Media BAD SPOT Summary ... ##
@@DATA_MSG
Media No. of SPAN Program
ID Errors Window HH:MM:SS ID
----- ------ ------ -------- -------
@@1MED_ID
%%%%%% %%%%% %%%%%%%%%%%%%%% %%%%%%
@@2MED_ID
%%%%%% %%%%% %%%%%%%%%%%%%%% TO %%%%%%%%%%%%%%% %%%%%%%%% %%%%%%
@@PROG_MSG
%%%%%%
@@TX0X_COL_MSG
%% %% %% %%%
@@MB_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of errors in: !
! Subsystem: TX02/01 related massbus/channel, Operation: READ/WRITE !
! related, error type: MASSBUS/CHANNEL ERROR !
+-----------------------------------------------------------------------+
@@SOFT_MSG
Error Media No. of SPAN
Register ID Errors Window HH:MM:SS
-------- ----- ------ ------ --------
@@ERROR_REG1
%%%%%% %%%%%% %%%% %%%%%%%%%%%%%%%
@@ERROR_REG2
%%%%%% %%%%%% %%%% %%%%%%%%%%%%%%% - %%%%%%%%%%%%%%% %%%%%%%%%
@@SENSE_BYTE1
%%% %%%%%% %%%% %%%%%%%%%%%%%%%
@@SENSE_BYTE2
%%% %%%%%% %%%% %%%%%%%%%%%%%%% - %%%%%%%%%%%%%%% %%%%%%%%%
@@SENSE_MSG
Sense Byte Media No. of SPAN
0 ID Errors Window HH:MM:SS
---------- ----- ------ ------ --------
@@OTHER_MSG
Function No. of SPAN
code Errors Window HH:MM:SS
-------- ------ ------ --------
@@FUNC_MSG
Error bits set in the sense bytes:
@@FUNCTION_CODE
##
@@1FUNCTION_CODE
%%% %%%% %%%%%%%%%%%%%%%
@@2FUNCTION_CODE
%%% %%%% %%%%%%%%%%%%%%% - %%%%%%%%%%%%%%% %%%%%%%%%
@@TM0X_OTHER_MSG
+-----------------------------------------------------------------------+
! REPORT of Errors related to CONTROL Operation. !
+-----------------------------------------------------------------------+
Control Operation - Control Operation error summary ... [2.1.8.1]
Note: Function code is in octal and assumes the GO bit is set.
@@TX0X_OTHER_MSG
+-----------------------------------------------------------------------+
! REPORT of Errors related to CONTROL Operation. !
+-----------------------------------------------------------------------+
Control Operation - Control Operation error summary ... [2.2.8.1]
Note: Function code is in octal and assumes the GO bit is set.
@@UNIT_MSG1
%%%%%% %%%%%
@@UNIT_MSG2
%%%%%% %%%%%% %%%%%
@@UNIT_MSG3
%%%%%% %%%%%% %%%%%% %%%%%
@@UNIT_MSG4
%%%%%% %%%%%% %%%%%% %%%%%% %%%%%
@@UNIT_MSG5
%%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%
@@UNIT_MSG6
%%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%
@@UNIT_MSG7
%%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%
@@UNIT_MSG8
%%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%% %%%%%
@@TM0X_RD_DEV_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of READ related DEVICE Errors !
+-----------------------------------------------------------------------+
@@TM0X_WR_DATA_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of WRITE related DATA Errors. !
+-----------------------------------------------------------------------+
@@TM0X_WR_DEV_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of WRITE related DEVICE Errors. !
+-----------------------------------------------------------------------+
@@TX0X_RD_DATA_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of READ related DATA Errors. !
+-----------------------------------------------------------------------+
@@TX0X_RD_DEV_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of READ related DEVICE Errors. !
+-----------------------------------------------------------------------+
@@TX0X_WR_DATA_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of WRITE related DATA Errors. !
+-----------------------------------------------------------------------+
@@TX0X_WR_DEV_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of WRITE related DEVICE Errors. !
+-----------------------------------------------------------------------+
@@TM0X_RD_DATA_MSG
+-----------------------------------------------------------------------+
! REPORT from analysis of READ related DATA Errors. !
+-----------------------------------------------------------------------+
@@TM0X_RD_SOFT_MSG
+-----------------------------------------------------------------------+
! REPORT from READ related SOFTWARE Errors. !
+-----------------------------------------------------------------------+
Read Data error - Software error summary ... [2.1.3.1]
Note: Error register contents are in octal.
@@TM0X_WR_SOFT_MSG
+-----------------------------------------------------------------------+
! REPORT from WRITE related SOFTWARE Errors. !
+-----------------------------------------------------------------------+
Write Data Error - Software error summary ... [2.1.6.1]
Note: Error register contents are in octal.
@@TX0X_RD_SOFT_MSG
+-----------------------------------------------------------------------+
! REPORT from READ related SOFTWARE Errors. !
+-----------------------------------------------------------------------+
Read Data Error - Software error summary ... [2.2.3.1]
Note: Sense Byte 0 is in octal.
@@TX0X_WR_SOFT_MSG
+-----------------------------------------------------------------------+
! REPORT from WRITE related SOFTWARE Errors. !
+-----------------------------------------------------------------------+
Write data Error - Software error summary ... [2.2.6.1]
Note: Sense Byte 0 is in octal.
@@TM0X_CHAN_MSG
+-----------------------------------------------------------------------+
! The following are errors that are not either drive or media related. !
! They are channel or massbus related. These errors are not analyzed !
! fully in release 1 of SPEAR. They occurred in subsystem TM02/03. !
+-----------------------------------------------------------------------+
@@TX0X_CHAN_MSG
+-----------------------------------------------------------------------+
! The following are errors that are not either drive or media related. !
! They are channel or massbus related. These errors are not analyzed !
! fully in release 1 of SPEAR. They occurred in subsystem TX02/01. !
+-----------------------------------------------------------------------+
@@TOTAL
%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@HIST1
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* *
* Tape Subsystem Histogram *
* *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
NOTE
Each asterisk (*) represents two errors. If there
are more than 100 errors during a single period,
then only the first 50 asterisks will be printed.
Time Total
Period Errors Histogram
------ ------ ---------
@@HIST2
! ---1---1---1---1---1---1---1---1---1---1---1---1--
8 16 24 32 40 48 56 64 72 80 88 96
Number of Errors
@@