4. EXCEPTIONS › 4.3 Detailed Exception Descriptions
4.3 Detailed Exception Descriptions
This section provides an in-depth description of each System
Reliability Analyzer standard exception available in the
exception report process. The exceptions are organized by
number and appear sequentially, starting with exception
07000.
The description format provides the title, the number,
statements on the purpose and rationale, and a definition for
each exception to give some insight as to the meaning and use
of the information. Finally, SAS code is listed, with a
short explanation on modifying the exception threshold
values.
07001: Software Failure in Critical System Task
FILE: System Software Diagnostic File
SAS FILE NAME: DETAIL.SRLSSD01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Software Failures in Critical System
Functions
RATIONALE: Software failures in critical system
functions may result in costly interruptions to online
services and reruns of batch systems. A failure in a system
function usually results in degradation or loss of the
services provided by the function. The entire system may or
may not be affected by the failure. By tracking critical
functions, you may be able to identify, isolate, and resolve
problems that are impacting the services provided by your
installation.
DEFINITION: This exception is created when a failure is
detected in any system function identified as being
critical to the system. A critical function is specified
with a job name in the CJOB statement as part of the
System Reliability options and is described in
Chapter 7.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07001
** SOFTWARE FAILURE IN CRITICAL SYSTEM TASK
*;
IF SSDCJOB = 'C'
THEN DO;
EXCCODE='07001'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='SOFTWARE FAILURE IN CRITICAL SYSTEM FUNCTION';
EXCDESC2='FUNCTION= ' || SSDJOB;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
To change the system functions identified as being
critical, modify the CJOB statements specified as part of
SRLOPS. This is described in Chapter 7.
07002: Software Failure in Critical System Module
FILE: System Software Diagnostic File
SAS FILE NAME: DETAIL.SRLSSD01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Software Failures in Critical System
Modules
RATIONALE: Software failures in critical system modules
may result in costly interruptions to online services and
reruns of batch systems. A failure in a system module
may result in degradation or loss of the services
provided by the entire function. The system may or may
not be affected by the failure. By tracking critical
modules, you may be able to identify, isolate, and
resolve problems that are impacting the services provided
by your installation.
DEFINITION: This exception is created when a failure is
detected in any system module identified as being
critical to the system. A critical module is specified
with a program name in the CMOD statement as part of the
System Reliability options and is described in Chapter 7.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07002
** SOFTWARE FAILURE IN CRITICAL SYSTEM MODULE
*;
IF SSDCMOD = 'C'
THEN DO;
EXCCODE='07002'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='SOFTWARE FAILURE IN CRITICAL SYSTEM MODULE';
EXCDESC2='MODULE=' || MODULE;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
To change the system modules identified as being
critical, modify the CMOD statements specified as part of
SRLOPS. This is described in Chapter 7.
07051: Software Failure in Critical User Function
FILE: User Software Diagnostic File
SAS FILE NAME: DETAIL.SRL_UD01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Software Failures in Critical User
Functions
RATIONALE: Software failures in critical user functions
may result in costly interruptions to online services or
reruns of applications systems. The failures usually do
not affect the entire system but may have serious impact
on business operations. By tracking critical user
functions, you may be able to identify, isolate, and
resolve problems impacting the services provided by your
installation.
DEFINITION: This exception is created when a failure is
detected in any user function identified as being
critical to the installation. A critical function is
specified with a job name in the CJOB statement as part
of the System Reliability options and is described in
Chapter 7.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07051
** SOFTWARE FAILURE IN CRITICAL USER FUNCTION
*;
IF SSDCJOB = 'C'
THEN DO;
EXCCODE='07051'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='SOFTWARE FAILURE IN CRITICAL USER FUNCTION';
EXCDESC2='FUNCTION= ' || SSDJOB;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
To change the user functions identified as being
critical, modify the CJOB statements specified as part of
SRLOPS. This is described in Chapter 7.
07052: Software Failure in Critical User Module
FILE: User Software Diagnostic File
SAS FILE NAME: DETAIL.SRL_UD01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Software Failures in Critical User
Modules
RATIONALE: Software failures in critical user modules may
result in costly interruptions to online services or
reruns of applications systems. The failures usually do
not affect the entire system but may have serious impact
on business operations. By tracking critical user
modules, you may be able to identify, isolate, and
resolve problems impacting the services provided by your
installation.
DEFINITION: This exception is created when a failure is
detected in any user module identified as being critical
to the installation. A critical module is specified with
a program name in the CMOD statement as part of the
System Reliability options and is described in Chapter 7.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07052
** SOFTWARE FAILURE IN CRITICAL USER MODULE
*;
IF SSDCMOD = 'C'
THEN DO;
EXCCODE='07052'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='SOFTWARE FAILURE IN CRITICAL USER MODULE';
EXCDESC2='MODULE=' || MODULE;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
To change the user modules identified as being critical,
modify the CMOD statements specified as part of SRLOPS.
This is described in Chapter 7.
07053: Job Cancelled by Loader Failure - Possible DASD Error
FILE: User Software Diagnostic File
SAS FILE NAME: DETAIL.SRL_UD01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Warning (SEVERITY='W')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Possible DASD Errors Based on Errors
Encountered by the Program Loader
RATIONALE: When an uncorrectable I/O error or an error in
the load module is encountered by the control program while
attempting to fetch a program into virtual storage, a 106-F
ABEND is issued. This can be an indication of a direct access
error on a volume containing one or more program libraries.
DEFINITION: This exception is created when a 106-F system
ABEND is detected in any program being loaded for processing
by the system.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07053
** JOB CANCELLED BY LOADER FAILURE - POSSIBLE DASD ERROR
*;
IF SSDSCMPC = '106' AND SSDGR15 = '0000000F'X
THEN DO;
EXCCODE='07053'; SEVERITY='W'; MGMTAREA='AVAILABILITY';
EXCDESC1='JOB CANCELLED BY LOADER FAILURE -
- POSSIBLE DASD ERROR';
LINK HIT;
END;
THRESHOLD MODIFICATION: The user may wish to restrict
this exception to a specific task. In this case, the
following can be added before the THEN of the IF statement:
name-1 - the name of the specific task or function to be
included in the exception is specified. A task named GRP400
would appear as:
AND SSDJOB = 'GRP400'
You may also wish to add the statement:
EXCDESC2='JOB NAME= ' || SSDJOB;
to allow the specific jobname having the failure to appear
when full exceptions are requested.
07200: System Terminated Due To Machine Check
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify System Failures and Outages Due To
Machine Checks
RATIONALE: System failures and outages result in costly
interruptions to online systems and reruns of batch
system. By examining all data related to a system
failure, you may be able to identify, isolate, and
resolve problems which are impacting the services
provided by your installation. This exception indicates
that an overall system failure has taken place and
provides a starting point for your problem analysis.
DEFINITION: This exception is created when a value
greater than zero is found in the system terminated
indicator within a machine check record.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
***********************************************************;
*
** 07200
** SYSTEM TERMINATED DUE TO MACHINE CHECK
*;
IF PRLSYST
THEN DO;
EXCCODE='07200'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM TERMINATED DUE TO MACHINE CHECK';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07201: Soft Machine Check Has Occurred
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Interruptions or System Degradation
Caused by Recoverable Machine Checks
RATIONALE: Machine checks which are recovered by the
system can cause costly interruptions and delays in
services provided to online users and the execution of
batch systems. By examining all data related to
recoverable failures, you may by able to identify,
isolate, and resolve problems which are impacting the
services provided by your installation. This exception
indicates that a recoverable machine failure has taken
place and provides a starting point for your problem
analysis.
DEFINITION: This exception is detected when the system
terminated indicator is zero, indicating that a machine
check has occurred which was recovered by the system.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07201
** SOFT MACHINE CHECK HAS OCCURRED
*;
IF PRLSYST = 0
THEN DO;
EXCCODE='07201'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SOFT MACHINE CHECK HAS OCCURRED';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07203: Failure Has Occurred in Clock Comparator
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='Reliability')
PURPOSE: Identify System Errors and Interruptions Due To
Failures in the Clock Comparator
RATIONALE: The IBM 370 processors include four facilities
for measuring time: the time of day clock, the clock
comparator, the CPU timer, and the interval timer. The
clock comparator is used to indicate that the time of day
clock value has exceeded a value stored in the clock
comparator. This allows an interrupt to be generated
when a certain time has been reached by the time of day
clock. Any failure or error which causes loss of the
ability to measure time units may impact your ability to
provide services in your installation.
DEFINITION: This exception is detected when a value
greater than zero is found in the clock comparator error
indicator and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07203
** FAILURE HAS OCCURRED IN CLOCK COMPARATOR
*;
IF PRLSYST = 0 AND PRLICKC
THEN DO;
EXCCODE='07203'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='FAILURE HAS OCCURRED IN CLOCK COMPARATOR';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07204: Failure Has Occurred in CPU Timer
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify System Errors and Interruptions Due To
Failures in the CPU Timer
RATIONALE: The IBM 370 processors include four facilities
for measuring time: the time of day clock, the clock
comparator, the CPU timer, and the interval timer. The
CPU timer is used to measure elapsed CPU time and for
indicating that a specified amount of time has elapsed.
Any failure or error which causes loss of the ability to
measure time units may impact your ability to provide
services in your installation.
DEFINITION: This exception is detected when a value
greater than zero is found in the CPU timer error
indicator and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07204
** FAILURE HAS OCCURRED IN CPU TIMER
*;
IF PRLSYST = 0 AND PRLICTM
THEN DO;
EXCCODE='07204'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='FAILURE HAS OCCURRED IN CPU TIMER ';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07205: Failure Has Occurred in Time-of-Day Clock
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify System Errors and Interruptions Due To
Failures in the Time-of-Day Clock
RATIONALE: The IBM 370 processors include four facilities
for measuring time: the time of day clock, the clock
comparator, the CPU timer, and the interval timer. The
time of day clock provides a high resolution measure of
real time and is normally used for very accurate
measurements of elapsed time. Any failure or error which
causes loss of the ability to measure time units may
impact your ability to provide services in your
installation.
DEFINITION: This exception is detected when a value
greater than zero is found in the time-of-day clock error
indicator and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07205
** FAILURE HAS OCCURRED IN TIME-OF-DAY CLOCK
*;
IF PRLSYST = 0 AND PRLITOD
THEN DO;
EXCCODE='07205'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='FAILURE HAS OCCURRED IN TIME-OF-DAY CLOCK';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07206: System Degraded by High Speed Buffer Failure
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Degradation to the System Caused By
Failures in the High Speed Buffer
RATIONALE: All IBM System/370 processors equipped with a
high speed buffer will automatically delete portions of
the buffer should a recoverable failure occur. Loss of
portions of the high speed buffer causes degradation in
the performance of the system, depending on how much of
the buffer is disabled.
DEFINITION: This exception is detected when a value
greater than zero is found in the 'buffer is in error'
indicator and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07206
** SYSTEM DEGRADED BY HIGH SPEED BUFFER FAILURE
*;
IF PRLSYST = 0 AND PRLSBUF
THEN DO;
EXCCODE='07206'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM DEGRADED BY HIGH SPEED BUFFER FAILURE';
LINK HIT;
END;
THRESHOLD MODIFICATION: The user may wish to restrict
this exception to prime time. In which case, the
following can be added before the THEN of the IF
statement:
Prime Time - The hour range and days of the week to be
included in the exception are specified. The hour
of the day must be within the hh1 through hh2 range.
Prime time specified as 8am through 6:59 pm (18:59)
would appear as:
AND ( 8 <=HOUR AND HOUR<= 18 )
The days of the week are represented by the first
three characters of their names. They must be
enclosed in quotes, separated with OR's. Prime time
specified as MONDAY through FRIDAY would appear as:
AND (DAYNAME='MON' OR DAYNAME='TUE' OR DAYNAME='WED'
OR DAYNAME='THU' OR DAYNAME='FRI' )
07207: System Degraded by External Damage
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Degradation to the System Caused By
Failures in Components Other than the Processor
RATIONALE: Failures which result in system degradation
can lead to missed objectives for batch and online
services. By tracking failures which cause degradation
to the system, you may be able to identify, isolate, and
resolve problems which are impacting the services
provided by your installation. External damage is caused
by an error in some component of the system other than
the processor itself (for example, the channels). Note
that the failures may result in more than one error being
logged to the SYS1.LOGREC dataset.
DEFINITION: This exception is detected when a value
greater than zero is found in the 'external damage
indicator' and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07207
** SYSTEM DEGRADED BY EXTERNAL DAMAGE
*;
IF PRLSYST = 0 AND PRLSEXD
THEN DO;
EXCCODE='07207'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM DEGRADED BY EXTERNAL DAMAGE';
LINK HIT;
END;
THRESHOLD MODIFICATION: The user may wish to restrict
this exception to prime time. In which case, the
following can be added before the THEN of the IF
statement:
Prime Time - The hour range and days of the week to be
included in the exception are specified. The hour of
the day must be within the hh1 through hh2 range.
Prime time specified as 8am through 6:59 pm (18:59)
would appear as:
AND ( 8 <=HOUR AND HOUR<= 18 )
The days of the week are represented by the first
three characters of their names. They must be
enclosed in quotes, separated with OR's. Prime time
specified as MONDAY through FRIDAY would appear as:
AND (DAYNAME='MON' OR DAYNAME='TUE' OR DAYNAME='WED'
OR DAYNAME='THU' OR DAYNAME='FRI' )
07208: System Degraded by Hardware Instruction Retry
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Degradation to the System Caused By
Instruction Retry
RATIONALE: Failures which result in system degradation
can lead to missed objectives for batch and online
services. By tracking failures which cause degradation
to the system, you may be able to identify, isolate, and
resolve problems which are impacting the services
provided by your installation. Instruction retry allows
a processor to recover from intermittent failures in the
hardware. An operation may be retried from the beginning
or from some other point in the processing of the
instruction that is known to be correct. When retry
takes place many times, system degradation can occur.
DEFINITION: This exception is detected when a value
greater than zero is found in the 'hardware instruction
retry' indicator and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07208
** SYSTEM DEGRADED BY HARDWARE INSTRUCTION RETRY
*;
IF PRLSYST = 0 AND PRLSHIR
THEN DO;
EXCCODE='07208'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM DEGRADED BY HARDWARE INSTRUCTION RETRY';
LINK HIT;
END;
THRESHOLD MODIFICATION: The user may wish to restrict
this exception to prime time. In which case, the
following can be added before the THEN of the IF
statement:
Prime Time - The hour range and days of the week to be
included in the exception are specified. The hour of
the day must be within the hh1 through hh2 range.
Prime time specified as 8am through 6:59 pm (18:59)
would appear as:
AND ( 8 <=HOUR AND HOUR<= 18 )
The days of the week are represented by the first
three characters of their names. They must be
enclosed in quotes, separated with OR's. Prime time
specified as MONDAY through FRIDAY would appear as:
AND (DAYNAME='MON' OR DAYNAME='TUE' OR DAYNAME='WED'
OR DAYNAME='THU' OR DAYNAME='FRI' )
07209: System Wait State Due To CHECK STOP Switch
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify System and Service Interruptions Due To
Wait States Caused by the CHECK STOP Switch
RATIONALE: System failures and outages result in costly
reruns and missed service objectives for batch and online
services. The CHECK STOP switch or test is used to stop
the processor when some hardware error or event takes
place. This is usually done to isolate and resolve an
intermittent hardware problem. CHECK STOP should not be
used in normal operations and its use can indicate the
presence of one or more hardware errors that require
management involvement in their resolution.
DEFINITION: This exception is detected when a value
greater than zero is found in the CHECK STOP indicator
and the system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07209
** SYSTEM WAIT STATE DUE TO CHECK STOP SWITCH
*;
IF PRLSYST = 0 AND PRLTCKS
THEN DO;
EXCCODE='07209'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM WAIT STATE DUE TO CHECK STOP SWITCH';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07210: System Wait State Due To Machine Check
FILE: Processor Reliability File
SAS FILE NAME: DETAIL.SRLPRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify System Interruptions Due to Wait States
Caused by Machine Checks
RATIONALE: System failures and outages result in costly
reruns and missed service objectives for batch and online
services. System wait states can result in both delays
and interruptions to services. If the wait state is
restartable, services are delayed until some operator
action takes place to restart the system. If the wait
state is not restartable, the system must be re-IPLed and
all services are interrupted for some period of time.
DEFINITION: This exception is detected when a value
greater than zero is found in the wait state code and the
system has not been terminated.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07210
** SYSTEM WAIT STATE DUE TO MACHINE CHECK
*;
IF PRLSYST = 0 AND PRLWSC NE ' '
THEN DO;
EXCCODE='07210'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM WAIT STATE DUE TO MACHINE CHECK';
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07300: System Degraded by Storage Error(s)
FILE: Storage Reliability File
SAS FILE NAME: DETAIL.SRLSTR01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify System Degradation Caused by Storage
Errors
RATIONALE: Failures which result in system degradation
can lead to missed objectives for batch and online
services. By tracking failures which cause degradation
to the system, you may be able to identify, isolate, and
resolve problems which are impacting the services
provided by your installation. Recoverable storage
errors may result in higher channel activity for direct
access devices due to the need to refresh portions of
programs which are executing. If a failure occurs which
can not be recovered by refreshing portions of a program,
the program may be abnormally terminated. This may cause
interruptions to online services or may require that
batch programs be rerun.
DEFINITION: This exception is detected when a storage
failure is encountered which did not result in the system
being terminated by the machine check handler.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07300
** SYSTEM DEGRADED BY STORAGE ERROR(S)
*;
IF STRFSC > 0 AND STRSYST
THEN DO;
EXCCODE='07300'; SEVERITY='I'; MGMTAREA='AVAILABILITY';
EXCDESC1='SYSTEM DEGRADED BY STORAGE ERROR(S)';
LINK HIT;
END;
THRESHOLD MODIFICATION: The user may wish to restrict
this exception to prime time. In which case, the
following can be added before the THEN of the IF
statement:
Prime Time - The hour range and days of the week to be
included in the exception are specified. The hour of
the day must be within the hh1 through hh2 range.
Prime time specified as 8am through 6:59 pm (18:59)
would appear as:
AND ( 8 <=HOUR AND HOUR<= 18 )
The days of the week are represented by the first
three characters of their names. They must be
enclosed in quotes, separated with OR's. Prime time
specified as MONDAY through FRIDAY would appear as:
AND (DAYNAME='MON' OR DAYNAME='TUE' OR DAYNAME='WED'
OR DAYNAME='THU' OR DAYNAME='FRI' )
07400: Recoverable Channel Check(s) Occurred
FILE: Channel Reliability File
SAS FILE NAME: DETAIL.SRLCRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Channel Failures which did not Result
In System Termination
RATIONALE: Channel failures which are recovered by the
channel check handler may result in degradation to the
system. This degradation can cause delays or
interruptions to online services or batch jobs in
execution. By tracking recoverable channel failures, you
may be able to identify, isolate, and resolve problems
which are impacting the services provided by your
installation.
DEFINITION: This exception is created when any channel
check record is found in the channel reliability file.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07400
** RECOVERABLE CHANNEL CHECK(S) OCCURRED
*;
IF CHANNEL NE ' '
THEN DO;
EXCCODE='07400'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='RECOVERABLE CHANNEL FAILURE(S) OCCURRED';
EXCDESC2='CHANNEL= ' || CHANNEL;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07500: Permanent Error(s) Occurred - Critical DASD
Device
FILE: DASD Device Reliability File
SAS FILE NAME: DETAIL.SRLDRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Permanent Errors Occurring on Critical
Direct Access Devices
RATIONALE: Direct access devices are used to store
libraries containing programs and data sets containing
information used by online systems and batch applications.
In some installations, one or more direct access devices may
be dedicated to a critical application. Permanent errors that
occur on these devices may cause failures in the online
systems or batch programs using the libraries and data sets.
By examining all permanent errors that occur on these
critical devices, you may be able to identify, isolate, and
resolve problems that are impacting the services provided by
your installation.
DEFINITION: This exception is created when a permanent
error is detected on any direct access device identified as
being critical to the installation. Note that any error
producing a 07500 exception will also create a 07501
exception, though the reverse is not true. Exception 07500
identifies permanent errors ONLY if they occur on a CRITICAL
DASD Device. Exception 07501 identifies ALL permanent
errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07500
** PERMANENT ERROR(S) OCCURRED - CRITICAL DASD DEVICE
*;
IF DRLPRMCT AND
(DEVNUM = 0000x)
THEN DO;
EXCCODE='07500'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED - CRITICAL DASD
DEVICE';
EXCDESC2='ADDRESS= ' || PUT(DEVNUM,HEX4.) || ', VOLSER= '
|| VOLSER || ', ERROR COUNT= ' || DRLPRMCT ;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the
address of the critical direct access device according to the
following convention:
cuuu - is the channel and unit address of the direct
access device. For a device with access through more
than one channel address, the address should be the
lowest address that can be used. For example, a
device with addresses 240 and 440 would appear as
DEVNUM = '0240x'
NOTE: For direct access devices having movable address
plugs, you may wish to track permanent errors
using the volume serial number. In this case, you
should replace the DEVADDR = '0000x' expression
with the expression VOLSER = 'volname'. This
technique may also be used for permanently mounted
volumes such as the IBM 3350 so that the exception
tracking is not dependent on the actual hardware
address being used. The following convention
would be used:
volname - is the 6 character volume serial number of the
direct access volume. The volume GRP400 would appear
VOLSER = 'GRP400'
07501: Permanent Error(s) Occurred on DASD Device
FILE: DASD Device Reliability File
SAS FILE NAME: DETAIL.SRLDRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Permanent Errors Occurring on Direct
Access Devices
RATIONALE: Direct access devices are used to store
libraries containing programs and data sets containing
information used by online systems and batch applications.
Permanent errors that occur on direct access devices may
cause failures in the online systems or batch programs using
the libraries and data sets. By examining permanent errors
that occur on direct access devices, you may be able to
identify, isolate, and resolve problems that are impacting
the services provided by your installation.
DEFINITION: This exception is created when a permanent
error is detected on any direct access device. Note that any
error producing a 07500 exception will also create a 07501
exception, though the reverse is not true. Exception 07500
identifies permanent errors ONLY if they occur on a CRITICAL
DASD Device. Exception 07501 identifies ALL permanent
errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07501
** PERMANENT ERROR(S) OCCURRED ON DASD DEVICE
*;
IF DRLPRMCT
THEN DO;
EXCCODE='07501'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED ON DASD DEVICE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', VOLSER= ' || VOLSER
|| ', ERROR COUNT= ' || DRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07502: Temporary Error(s) Exceed Maximum for DASD Device
FILE: DASD Device Reliability File
SAS FILE NAME: DETAIL.SRLDRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Warning (SEVERITY='W')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Temporary Errors on Direct Access
Devices which Exceed A Maximum Threshold
RATIONALE: Temporary errors on direct access devices may
be an indication of permanent errors at some future time.
They may also cause performance problems due to the need to
recover from the errors. This exception provides a warning
when the number of temporary errors exceed an installation
defined maximum.
DEFINITION: This exception is produced when the number of
temporary errors on a direct access device exceeds a defined
maximum number.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07502
** TEMPORARY ERROR(S) EXCEED MAXIMUM FOR DASD DEVICE
*;
IF DRLTMPCT > err-ct
THEN DO;
EXCCODE='07502'; SEVERITY='W'; MGMTAREA='RELIABILITY';
EXCDESC1='TEMPORARY ERROR(S) EXCEED MAX FOR DASD DEVICE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', ERROR COUNT= ' ||
DRLTMPCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the value
of the number of temporary errors which are acceptable on a
direct access device according to the following convention:
err-ct - is the maximum number of acceptable temporary
errors on a direct access device. The value 256
would be specified as
DRLTMPCT > 256
07600: Permanent Error(s) Occurred - Critical Tape
Device
FILE: Magnetic Tape Device Reliability File
SAS FILE NAME: DETAIL.SRLMRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Permanent Errors Occurring on Critical
Magnetic Tape Devices
RATIONALE: Magnetic tape devices are used to store large
amounts of data generally used by batch application programs.
They are also used as logging devices for online systems such
as IMS or CICS. Permanent errors that occur on these devices
may cause failures in the online systems or batch programs
using the devices. By examining all permanent errors that
occur on these critical devices, you may be able to identify,
isolate, and resolve problems impacting the services provided
by your installation.
DEFINITION: This exception is created when a permanent
error is detected on any magnetic tape device identified as
being critical to the installation. Note that any error
producing a 07600 exception will also create a 07601
exception, though the reverse is not true. Exception 07600
identifies permanent errors ONLY if they occur on a CRITICAL
magnetic tape device. Exception 07601 identifies ALL
permanent errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07600
** PERMANENT ERROR(S) OCCURRED - CRITICAL TAPE DEVICE
*;
IF MRLPRMCT AND
(DEVNUM = '0000x')
THEN DO;
EXCCODE='07600'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED - CRITICAL TAPE DEV';
EXCDESC2='ADDRESS= ' || PUT(DEVNUM,HEX4.) ||
', ERROR COUNT= ' || MRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the
address of the critical magnetic tape device according to the
following convention:
cuu - is the channel and unit address of the magnetic
tape device. A device with address 572 would appear
as
DEVNUM = '0572'
07601: Permanent Error(s) Occurred on Tape Device
FILE: Magnetic Tape Device Reliability File
SAS FILE NAME: DETAIL.SRLMRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Permanent Errors Occurring on Magnetic
Tape Devices
RATIONALE: Magnetic tape devices are used to store large
amounts of data generally used by batch application programs.
They may also be used as logging devices for online systems
such as IMS or CICS. Permanent errors that occur on magnetic
tape devices may cause failures in the online systems or
batch programs using the devices. By examining permanent
errors that occur on magnetic tape devices, you may be able
to identify, isolate, and resolve problems impacting the
services provided by your installation.
DEFINITION: This exception is created when a permanent
error is detected on any magnetic tape device. Note that any
error producing a 07600 exception will also create a 07601
exception, though the reverse is not true. Exception 07600
identifies permanent errors ONLY if they occur on a CRITICAL
magnetic tape device. Exception 07601 identifies ALL
permanent errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07601
** PERMANENT ERROR(S) OCCURRED ON TAPE DEVICE
*;
IF MRLPRMCT
THEN DO;
EXCCODE='07601'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED ON TAPE DEVICE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', VOLSER= ' || VOLSER
|| ', ERROR COUNT= ' || MRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07602: Temporary Read Error(s) Exceed Maximum for Tape
FILE: Magnetic Tape Device Reliability File
SAS FILE NAME: DETAIL.SRLMRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Warning (SEVERITY='W')
MANAGEMENT AREA: Reliability (MGMTAREA='Reliability')
PURPOSE: Identify Temporary Read Errors on Magnetic Tape
Devices which Exceed A Maximum Threshold
RATIONALE: Temporary read errors on magnetic tape devices
may be an indication of permanent errors at some future
time. This exception provides a warning when the number
of temporary read errors exceed an installation defined
maximum.
DEFINITION: This exception is produced when the number of
temporary read errors on a magnetic tape device exceeds a
defined maximum number.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07602
** TEMPORARY READ ERROR(S) EXCEED MAXIMUM FOR TAPE
*;
IF MRLTEMPR > value
THEN DO;
EXCCODE='07602'; SEVERITY='W'; MGMTAREA='RELIABILITY';
EXCDESC1='TEMPORARY READ ERROR(S) EXCEED MAXIMUM FOR TAPE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', ERROR COUNT= ' ||
MRLTEMPR;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should specify the value
for the number of acceptable temporary read errors on a
magnetic tape device according to the following
convention:
value - is the maximum number of acceptable temporary
read errors for a magnetic tape device. The value
16 would be specified as
MRLTEMPR > 16
07603: Temporary Write Error(s) Exceed Maximum for Tape
FILE: Magnetic Tape Device Reliability File
SAS FILE NAME: DETAIL.SRLMRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Warning (SEVERITY='W')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Temporary Write Errors on Magnetic Tape
Devices which Exceed A Maximum Threshold
RATIONALE: Temporary write errors on magnetic tape
devices may be an indication of permanent errors at some
future time. This exception provides a warning when the
number of temporary write errors exceed an installation
defined maximum.
DEFINITION: This exception is produced when the number of
temporary write errors on a magnetic tape device exceeds a
defined maximum number.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07603
** TEMPORARY WRITE ERROR(S) EXCEED MAXIMUM FOR TAPE
*;
IF MRLTEMPW > value
THEN DO;
EXCCODE='07603'; SEVERITY='W'; MGMTAREA='RELIABILITY';
EXCDESC1='TEMPORARY WRITE ERROR(S) EXCEED MAX FOR TAPE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', ERROR COUNT= ' ||
MRLTEMPW;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should specify the value
for the number of acceptable temporary write errors on a
magnetic tape device according to the following convention:
value - is the maximum number of acceptable temporary
write errors for a magnetic tape device. The value
2 would be specified as
MRLTEMPW > 2
07700: Permanent Error(s) Occurred - Critical U/R Device
FILE: Unit Record Device Reliability File
SAS FILE NAME: DETAIL.SRLXRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Permanent Errors Occurring on Critical
Unit Record Devices
RATIONALE: Unit record devices include card readers, card
punches, and printers and a number of other devices such as
optical scanners and magnetic ink character readers.
Permanent errors that occur on these devices may impact the
functions or services being provided by the devices, such as
the printing of reports or capture of magnetically encoded
documents. By examining all permanent errors that occur on
these critical devices, you may be able to identify, isolate,
and resolve problems impacting the services provided by your
installation.
DEFINITION: This exception is created when a permanent
error is detected on any unit record device identified as
being critical to the installation. Note that any error
producing a 07700 exception will also create a 07701
exception, though the reverse is not true. Exception 07700
identifies permanent errors ONLY if they occur on a CRITICAL
unit record device. Exception 07701 identifies ALL permanent
errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07700
** PERMANENT ERROR(S) OCCURRED - CRITICAL U/R DEVICE
*;
IF XRLPRMCT AND
(DEVNUM = 0000x )
THEN DO;
EXCCODE='07700'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED - CRITICAL U/R DEV';
EXCDESC2='ADDRESS= ' || PUT(DEVNUM,HEX4.) ||
', ERROR COUNT= ' || XRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the
address of the critical unit record device according to the
following convention:
cuuu - is the channel and unit address of the unit record
device. A device with address 042E would appear as
DEVNUM = '042E'
07701: Permanent Error(s) Occurred on U/R Device
FILE: Unit Record Device Reliability File
SAS FILE NAME: DETAIL.SRLXRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Permanent Errors Occurring on Unit
Record Devices
RATIONALE: Unit record devices include card readers, card
punches, and printers and a number of other devices such as
optical scanners and magnetic ink character readers.
Permanent errors that occur on these devices may impact the
functions or services being provided by the devices, such as
the printing of reports or capture of magnetically encoded
documents. By examining permanent errors that occur on these
devices, you may be able to identify, isolate, and resolve
problems impacting the services provided by your
installation.
DEFINITION: This exception is created when a permanent
error is detected on any unit record device. Note that any
error producing a 07700 exception will also create a 07701
exception, though the reverse is not true. Exception 07700
identifies permanent errors ONLY if they occur on a CRITICAL
unit record device. Exception 07701 identifies ALL permanent
errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07701
** PERMANENT ERROR(S) OCCURRED ON U/R DEVICE
*;
IF XRLPRMCT
THEN DO;
EXCCODE='07701'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED ON U/R DEVICE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', ERROR COUNT= ' ||
XRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07800: Permanent Error(s) Occurred - Critical TP Device
FILE: TP Device Reliability File
SAS FILE NAME: DETAIL.SRLTRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Critical (SEVERITY='C')
MANAGEMENT AREA: Availability (MGMTAREA='AVAILABILITY')
PURPOSE: Identify Permanent Errors Occurring on Critical
Teleprocessing Devices
RATIONALE: Teleprocessing devices are the control units
and terminals that are used to provide online services to
various users. They include the TP control unit, terminal
devices for the remote input and output of data, and many
specialized devices such as automated teller machines in the
banking industry. Permanent errors that occur on these
devices may cause failures in the online systems or batch
programs using the devices. By examining all permanent
errors that occur on these critical devices, you may be able
to identify, isolate, and resolve problems impacting the
services provided by your installation.
DEFINITION: This exception is created when a permanent
error is detected on any teleprocessing device identified as
being critical to the installation. Note that any error
producing a 07800 exception will also create a 07801
exception, though the reverse is not true. Exception 07800
identifies permanent errors ONLY if they occur on a CRITICAL
teleprocessing device. Exception 07801 identifies ALL
permanent errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07800
** PERMANENT ERROR(S) OCCURRED - CRITICAL TP DEVICE
*;
IF TRLPRMCT AND
(DEVNUM = 0000x )
THEN DO;
EXCCODE='07800'; SEVERITY='C'; MGMTAREA='AVAILABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED - CRITICAL TP DEV';
EXCDESC2='ADDRESS= ' || PUT(DEVNUM,HEX4.) ||
', ERROR COUNT= ' || TRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the
address of the critical teleprocessing device according to
the following convention:
cuuu - is the channel and unit address of the
teleprocessing device. A device with address 0A10
would appear as
DEVNUM = '0A10'
07801: Permanent Error(s) Occurred on TP Device
FILE: TP Device Reliability File
SAS FILE NAME: DETAIL.SRLTRL01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Impacting (SEVERITY='I')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Permanent Errors Occurring on
Teleprocessing Devices
RATIONALE: Teleprocessing devices are the control units
and terminals that are used to provide online services to
various users. They include the TP control unit, terminal
devices for the remote input and output of data, and many
specialized devices such as automated teller machines in the
banking industry. Permanent errors that occur on these
devices may cause failures in the online systems or batch
programs using the devices. By examining permanent errors
that occur on these devices, you may be able to identify,
isolate, and resolve problems impacting the services provided
by your installation.
DEFINITION: This exception is created when a permanent
error is detected on any teleprocessing device. Note that any
error producing a 07800 exception will also create a 07801
exception, though the reverse is not true. Exception 07800
identifies permanent errors ONLY if they occur on a CRITICAL
teleprocessing device. Exception 07801 identifies ALL
permanent errors.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07801
** PERMANENT ERROR(S) OCCURRED ON TP DEVICE
*;
IF TRLPRMCT
THEN DO;
EXCCODE='07801'; SEVERITY='I'; MGMTAREA='RELIABILITY';
EXCDESC1='PERMANENT ERROR(S) OCCURRED ON TP DEVICE';
EXCDESC2='ADDRESS= ' || DEVADDR || ', ERROR COUNT= ' ||
TRLPRMCT;
LINK HIT;
END;
THRESHOLD MODIFICATION: No modifications are required.
07950: Temporary Read Error(s) Exceed Maximum for Tape
Volume
FILE: Magnetic Tape Media Reliability File
SAS FILE NAME: DETAIL.SRLMMR01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Warning (SEVERITY='W')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify Temporary Read Errors on Magnetic Tape
Volumes which Exceed A Maximum Threshold
RATIONALE: Temporary read errors on magnetic tape volumes
may be an indication of permanent errors at some future time.
This exception provides a warning when the number of
temporary read errors exceed an installation defined maximum.
DEFINITION: This exception is produced when the number of
temporary read errors on a magnetic tape device exceeds a
defined maximum number.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are stored
in the source member named in SOURCE LOCATION and are
described below:
************************************************************;
*
** 07950
** TEMPORARY READ ERROR(S) EXCEED MAXIMUM FOR TAPE VOLUME
*;
IF MMRTEMPR > err-value
THEN DO;
EXCCODE='07950'; SEVERITY='W'; MGMTAREA='RELIABILITY';
EXCDESC1='TEMP READ ERROR(S) EXCEED MAX FOR TAPE VOLUME';
EXCDESC2='VOLUME= ' || VOLUME || ', ERROR COUNT= ' ||
PUT(MMRTEMPR,6.);
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the value
used for the number of temporary read errors according to the
following convention:
err-value - the threshold value for number of temporary
read error(s) for a single magnetic tape
volume. A value of 8 would appear as:
MMRTEMPR > 8
07951: Temporary Write Error(s) Exceed Maximum for Tape Vol.
FILE: Magnetic Tape Media Reliability File
SAS FILE NAME: DETAIL.SRLMMR01
SOURCE LOCATION: prefix.MICS.USER.SOURCE(DYSRLEXC)
SEVERITY: Warning (SEVERITY='W')
MANAGEMENT AREA: Reliability (MGMTAREA='RELIABILITY')
PURPOSE: Identify temporary write errors on magnetic tape
volumes which exceed a maximum threshold
RATIONALE: Temporary write errors on magnetic tape
volumes may be an indication of permanent errors at some
future time. This exception provides a warning when the
number of temporary write errors exceed an installation
defined maximum.
DEFINITION: This exception is produced when the number of
temporary write errors on a magnetic tape volume exceeds
a defined maximum number.
EXCEPTION STATEMENTS: The SAS statements identifying the
exception situation and describing the condition are
stored in the source member named in SOURCE LOCATION and
are described below:
************************************************************;
*
** 07951
** TEMPORARY WRITE ERROR(S) EXCEED MAXIMUM FOR TAPE VOLUME
*;
IF MMRTEMPW > err-value
THEN DO;
EXCCODE='07951'; SEVERITY='W'; MGMTAREA='RELIABILITY';
EXCDESC1='TEMP WRITE ERROR(S) EXCEED MAX FOR TAPE VOLUME';
EXCDESC2='VOLUME= ' || VOLUME || ', ERROR COUNT= ' ||
PUT(MMRTEMPW,6.);
LINK HIT;
END;
THRESHOLD MODIFICATION: The user should modify the value
used for the number of temporary write errors according
to the following convention:
err-value - the threshold value for number of temporary
write error(s) for a single magnetic tape volume. A
value of 15 would appear as:
MMRTEMPW > 15
Copyright © 2014 CA.
All rights reserved.
|
|