|
|
|
Source: BATPGM file at the DETAIL timespan
BATJOB file at the DETAIL timespan
BAT_JS file at the DETAIL timespan
Function: This report helps to identify users or departments
that are receiving batch job abends related to
DASD space shortages. These problems can be
caused by poor JCL parameters, fragmented DASD
space, or by a shortage of free space. This
report helps the Storage Administrator investigate
space-related problems, and identify users that
require JCL changes or more DASD space. This
report helps the Capacity Planner calculate the
amount of human and machine resources wasted in
recovery activities.
Features: The left side of the report gives specific
information about each abend, and is useful for
doing detailed problem investigation. The right
side of the report gives information about the
recovery activities that occurred to correct the
problem, which can save much time-consuming manual
research. A wide variety of filtering and
reporting options allow many views of the data,
such as a broad system-wide view, or a narrow view
related to an individual time or department.
SMS
Issues: Users implementing SMS may want to identify
departments having space-related abends as
potential candidates for movement to SMS Storage
Groups. After SMS is implemented, this report can
be used to make sure abends are not occurring for
managed users, and to alter SMS parameters if
necessary.
COLUMN DESCRIPTIONS
Jobname
The jobname of each batch job found within the
input data that ended abnormally due to a
space-related error.
Job Number/Class
The JES job number assigned to the failing job,
and also the job class in which the job executed.
One or both of these values may be blank if the
job number or class cannot be determined.
Step Start Date/Time
The date and time the failing step began.
Step Name
The step name from the EXEC JCL statement for the
step that failed.
Program Name
The program name from the EXEC JCL statement that
was executing when the failure occurred.
Step No.
The step number of the specified job within which
the failure occurred.
Abend Code
The specific abort code that was received by the
failing step. Refer to the IBM System Codes
manual for an explanation of the meanings of each
code.
Recovery Ended Time
The time at which recovery for the space-related
error was completed. This is the time when the
recovery step for the error started execution.
The report defines a recovery step as a step
having the same jobname, stepname, and program
name as the originally abending step, which
executes after the original failure within the
time frame of the selected data cycles for this
report. If a recovery step was not found, this
time will be the same as the Step Start Date/Time.
Comments
This column will contain one of three values. If
the value 'NO RECOVERY FOUND' is present, this
means that no recovery step was found to recover
from this error. The report defines a recovery
step as a step having the same jobname, stepname,
and program name as the originally abending step,
which executes after the original failure. If the
value 'SECONDARY ABEND' is present, it means that
a recovery step was found, but that recovery step
also received a space- related failure. Recovery
for the original abend is considered complete when
the secondary job begins, and recovery for the
secondary abend will be reported in a future entry
on the report. If the value 'RESTART STEP:name'
is present, this means that recovery was completed
for this failure, and the stepname of the first
step to run as part of the recovery process is
listed in the comment.
Recovery Elapsed Time
The amount of time necessary for the recovery
process to complete for this job. This is defined
as the difference between the start time of the
original failing step (Step Start Date/Time
column) and the start time of the recovery step
(Recovery Ended Time column). If no recovery step
was found for this job, a value of zeros will be
present. For jobs that experience a secondary
abend during recovery, this will be the step start
time for the recovery step that received the
secondary abend.
Rerun Steps
The number of job steps (program executions) that
had to occur to effect the recovery process for
this job. This does not include the original step
that received the abend, but does include the
recovery step, plus any steps that ran during the
recovery period with the same jobname as the
original failing job. This will have a value of
zero if no recovery step was found. When a
secondary abend occurs, one will be added to this
value to represent that step.
Rerun CPU Time
The amount of processor time (TCB plus SRB CPU
time) required to perform recovery for this step.
This includes the CPU time of the failing step,
and the CPU time used by any steps running under
the same job name during the recovery period. It
does not include the CPU time used by the recovery
step. If no recovery step is found, this only
includes the CPU time used by the original failing
step.
Rerun EXCPs
The number of I/O requests issued to perform
recovery for this step. This includes the I/O
counts of the failing step, and the I/O used by
any steps running under the same job name during
the recovery period. It does not include the I/O
used by the recovery step. If no recovery step is
found, this only includes the I/O counts used by
the original failing step.
ALLOCATION PROBLEMS (STGECB) 1 CA MICS StorageMate - DETAIL ABC CORPORATION ------------------------------------------------- System Identifier=SYSA Jobclass=A ------------------------------------------------ Jobname Job Step Start Step Program Step Abend Recovery Comments | Recovery Rerun Rerun Rerun Number Date/Time Name Name No. Code Ended | Elapsed Steps CPU EXCPs /Class Time | Time Time LNR231$D 7231/A 18MAY07:10:36:00 MICS SASLPA 11 SB37 11:27:41 RESTART STEP:MICS | 0:51:41 1 0:02:57 38839 LNR298A 7394/A 18MAY07:16:04:22 C IEV90 1 SE37 16:08:57 RESTART STEP:C | 0:04:35 1 0:00:10 2960 LNR231$D 7741/A 18MAY07:17:46:19 MICS SASLPA 11 SB37 17:54:59 RESTART STEP:MICS | 0:08:40 1 0:02:51 38843 -------- -------- --- -------- ------- JOBCLASS 1:04:56 3 0:05:58 80642 N= 3 ------------------------------------------------ System Identifier=SYS7 Jobclass=B ------------------------------------------------- Jobname Job Step Start Step Program Step Abend Recovery Comments | Recovery Rerun Rerun Rerun Number Date/Time Name Name No. Code Ended | Elapsed Steps CPU EXCPs /Class Time | Time Time LNR118U1 7349/B 18MAY07:13:24:05 SAS SASLPA 1 SB37 13:26:53 SECONDARY ABEND | 0:02:48 1 0:00:03 2899 LNR118U1 7354/B 18MAY07:13:26:53 SAS SASLPA 1 SB37 13:26:53 NO RECOVERY FOUND | 0:00:00 0 0:00:02 2037 LNR050XZ 7554/B 18MAY07:15:46:11 COPY IEBCOPY 1 SE37 15:46:52 SECONDARY ABEND | 0:00:40 1 0:00:01 269 LNR050XZ 7556/B 18MAY07:15:46:52 COPY IEBCOPY 1 SE37 15:50:03 RESTART STEP:COPY | 0:03:11 1 0:00:01 272 LNR212CL 7636/B 18MAY07:16:53:22 SAS SASLPA 1 SB37 17:39:06 RESTART STEP:SAS | 0:45:44 3 0:04:25 53584 -------- -------- --- -------- ------- JOBCLASS 0:52:24 6 0:04:31 59061 SYSID 1:57:20 9 0:10:29 139703 ======== === ======== ======= 1:57:20 9 0:10:29 139703 N= 5
Figure 4-14. Allocation Problems / Detail
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |