Fault Analyser

FauIt AnaIyzer Mentor Workshop zSeries AD Tools 1
2003 BM Corporation
November 4, 2003
BM Fault Analyzer
Version 4
Program Number 5655-L25
Mentor Workshop
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
Fault Analyzer Files, Setup, and Options
Real-Time Fault Analysis Report
Using the Online nterface
Fault Re-analysis
CCS, DB2, & MS Support
Preparing programs for Fault Analysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
at IS Fault Analyzer ?
Fault Analyzer is a tool that helps you
determine the cause of an application abend
O so you can more quickly identify and resolve
the problem
Delivers information about an application
when it has abended, to help you assess:
O What happened, and why?
O What program?
O What line of source code?
O What source variables were involved?
2003 BM Corporation
November 4, 2003
anguages and Environments Supported
COBOL
PL/
Assembler
C/C++
z/OS
OS/390
LE (Language Environment)
CCS
MS
DB2
MQSeries
UNX System Services
2003 BM Corporation
November 4, 2003
at Functions does Fault Analyzer ave ?
Real-Time Analysis
O Automatic generation of an analysis report when
an application abends
O Captures and saves detailed information about
the application and its environment
Online nterface
O View an analysis report
O Perform a Reanalysis
O Manage saved abend entries
nteractive Reanalysis
O Point-and-shoot navigation of an abend
O Apply program source data
Batch Reanalysis
O Run a batch job to generate a new analysis report
O Apply program source data
2003 BM Corporation
November 4, 2003
#eal-Time Analysis . ow it works
An application abends
The system intercepts
the abend and calls one
of the Fault Analyzer
system exits The exit
invokes FA
2 FA reads options that
control whether it will
analyze the abend, how
to process, and which
Fault History file to use
nstallation options are
specified for the system
Options can be overridden
for a job step or online
region
8|de F||es
z/OS
Fau|t
Ana|yzer
App||cat|on
Fau|t h|story F||e
Fault
Entry
omp||er L|st|ngs
0pt|ons
FA |nvocat|on Ex|t
Abend
Ana|ys|s
Report
|oalcr app||cal|or)
#eaI-Time AnaIysis
8|de F||es
2003 BM Corporation
November 4, 2003
z/OS
Fau|t
Ana|yzer
App||cat|on
Fau|t h|story F||e
Fault
Entry
omp||er L|st|ngs
0pt|ons
FA |nvocat|on Ex|t
Abend
Ana|ys|s
Report
|oalcr app||cal|or)
#eaI-Time AnaIysis
3 Fault Analyzer examines
application programs
and their environment
4 FA gets source
information for
application programs by
reading compiler listings
and side files
Compiler listings and side
files are stored in PDS or
PDSE data sets
Multiple data sets can be
scanned
f a listing / side file is not
found, the report will not
show source information for
that program
2003 BM Corporation
November 4, 2003
z/OS
Fau|t
Ana|yzer
App||cat|on
Fau|t h|story F||e
Fault
Entry
omp||er L|st|ngs
0pt|ons
FA |nvocat|on Ex|t
Abend
Ana|ys|s
Report
|oalcr app||cal|or)
#eaI-Time AnaIysis
5 A new Fault Entry is written
to a Fault History File
Options control which
History File is used The
entry contains:
nfo about the application
The Analysis Report
A "mini-dump of the
application (this enables
reanalysis)
6 The Analysis Report is
written to SYSOUT
(batch jobs only)
7 SYSMDUMP output is
suppressed
You can specify FA options if
you want to get SYSMDUMP
output
2003 BM Corporation
November 4, 2003
'iew a #eal-Time Analysis #eport
For all abends, FA stores
the Real-Time Analysis
report in a Fault Entry
Use the online interface to
view the report from the
Fault Entry
For batch jobs, FA also
sends the report to
SYSOUT
O Default is SYSOUT=*
DD name is DREPRT
Fau|t
Ana|yzer
0n||ne
|nterface
|8PF
Fau|t h|story F||es
Fault
Entry
8Y80UT
Ana|ys|s
Report
!7|rled
oulpul
For batch abends onIy
For any abend
2003 BM Corporation
November 4, 2003
Te #eal-Time Analysis #eport
Synopsis and the
suspected cause of a
failure
O abending program
O executing line of source
code
O active variables
Explanation of error
messages / codes
File and Database detail
Detailed information about
programs:
O Values of all program variables / storage
O compile, link, load, and entry point information
System information:
O z/OS, CCS, DB2, MS
2003 BM Corporation
November 4, 2003
Interactive #eanalysis
Online screens to research
abend information
Apply source information,
even if the source info was
not available during Real-
Time analysis
Options can be specified to
control processing and
locate source listings
f a compiler listing does not
not already exist, it can be
re-created after the abend
You do NOT have to
recreate the abend
Fau|t
Ana|yzer
0n||ne |nterface
Fau|t h|story F||e
Fault
Entry
omp||er L|st|ngs
8|de F||es
pl|ors
|8PF
Corp||e7
!7od7ar
3ou7ce
pl|ora|
The Fault Entry was saved by FA
when the application abended
The Fault Entry was saved by FA
when the application abended
For any abend
2003 BM Corporation
November 4, 2003
Interactive #eanalysis
O Synopsis
O Any program in the caII chain
O Program variabIes and their vaIues
O FiIe and database detaiI
O CCS, DB2, and MS info
O Browse program source Iisting
O Browse storage
Point and
Shoot
navigation
nfo shown in
the Real-time
report
Quickly
navigate to:
2003 BM Corporation
November 4, 2003
atc #eanalysis
Batch utility to
generate a new
analysis report
Apply source
information, even if the
source info was not
available during Real-
Time analysis
Fault Analyzer
generates JCL
JCL can be edited,
submitted, and/or
saved
Fau|t
h|story F||e
Fault
Entry
omp||er L|st|ngs
8|de F||es
|8PF
Corp||e7
!7od7ar 3ou7ce
pl|ora|
&se the FA onIine
interface to generate
and submit JCL for the
batch reanaIysis job
&se the FA onIine
interface to generate
and submit JCL for the
batch reanaIysis job
Fau|t Ana|yzer
atch
Reana|ys|s Job
Ana|ys|s
Report
|3Y3&%)
2003 BM Corporation
November 4, 2003
ow Fault Analyzer gets Source InIormation
Fault Analyzer looks for program source info during:
O Real-Time Analysis
O Re-analysis
To get source information about programs, Fault
Analyzer scans PDS or PDSE data sets containing:
O CompiIer Listings (the report output of compilers)
O DLANGX Side FiIes
Produced by processing a compiler listing through
utility program DLANGX t is smaller than a
compiler listing
O COBOL SYSDEB&G Side FiIes
Produced by COBOL compilers when the
TEST(.,.,SEPARATE) compiler option is specified
f a program listing is not found, the Analysis Report is
produced without source information for that program
2003 BM Corporation
November 4, 2003
ow Fault Analyzer gets Source
InIormation
Fault Analyzer looks for a member name that matches
the program's entry point name f not found, then .
2 the CSECT name
f multiple versions of compiler listings or side files are
found, FA compares:
O the timestamp in each Iisting / side fiIe
- - - against - - -
O the timestamp in the Ioad moduIe
the matching version of the listing / side file is used
f no version has a matching timestamp, then:
The compiler listing / side file with a timestamp nearest
the load module timestamp is used
A warning message is written to the Analysis Report
Multiple data sets can be searched
O Test, QA, Production, and other compiler listings and
side files can all be searched together
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
FauIt AnaIyzer FiIes, Setup, and Options
Fault Re-analysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
Fault Analyzer Setup
To get the most from Fault Analyzer, there should be:
One or more Fault History Files required)
Processes for generating and storing Compiler Listings
or Side Files
Fault Analyzer Options customized for your system
2003 BM Corporation
November 4, 2003
Fault istory Files
Fault History Files are used by Fault Analyzer to store
abend information
File type is PDSE (recommended) or PDS
O nitialized with utility program DUTL
One entry is stored for an abend
Each entry includes:
O nformation about the
abend
O a copy of the Real-Time
Analysis report
O a "minidump" of the
application
Fau|t h|story
F||e
Fault Entries
Fau|t
Ana|yzer
App||cat|on
0pt|ons
FA |nvokat|on Ex|t
Abend
Ana|ys|s Report
omp||er L|st|ngs | 8|de F||es
2003 BM Corporation
November 4, 2003
Fault istory Files
A History File can be set up to wrap around
(recommended)
"Duplicate" entries can be suppressed to save space
O an abend is a duplicate if it has the same:
program name, compile timestamp, abend code,
and offset
O controlled by the age of an entry
for example. no duplicates stored for hour after
the first abend
How long does a fault entry stay in the history file ?
O t depends on:
the size of the file (how many entries it can hold)
application size
how frequently applications abend
2003 BM Corporation
November 4, 2003
Fault istory Files
One or Multiple History Files can be used
O consider creating separate files for:
production vs test
So test abends won't cause production info to roll off
by department or application group
For security, if program or file information is a concern
To automatically select a Fault History File, code a Fault
Analyzer "Analysis Control user exit
O Choose a Fault History File based on Jobname, Tran D,
User D, etc
O Typically done by the nstaller / Systems Programmer
2003 BM Corporation
November 4, 2003
Fault Analyzer Options
FA uses default options customized for your system
You can also specify options to override the defaults, to
tell Fault Analyzer:
O where program source listings are stored
O the name of the Fault History File to use
O to include or exclude certain applications for processing
O To collect a SYSMDUMP or SYSUDUMP
O The level of detail to show in Analysis Reports
O And more
FA accepts override options during:
O Real-time Analysis
Specify options in JCL
O Re-analysis
Specify your options interactively
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
#eaI-Time FauIt AnaIysis #eport
Fault Re-analysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
#eal Time Analysis #eport
Can be viewed one of two ways:
O View any Real-Time report with the Online nterface
displayed from the Fault History File
O For a batch job, view the generated report
FA dynamically allocates DD "DREPRT "
Contents:
O Synopsis
O Event Summary
O Event Details
Point of Failure
Associated Messages
Open Files
Associated Storage Areas
O Abend Job nformation
O Fault Analyzer Options in Effect
2003 BM Corporation
November 4, 2003
#eal-Time Analysis #eport
********************************************************************************
* IBM Fault Analyzer for z/OS and OS/390 V3R1M0 (UQ73759 2003/02/17) *
* *
* (C) Copyright IBM Corp. 2000, 2002. All rights reserved. *
********************************************************************************
JOBNAME: DBSTOUTY SYSTEM ABEND: 0CB DEMOMVS 2003/06/08 13:06:13 Page 001
<H1> I B M F A U L T A N A L Y Z E R S Y N O P S I S
A system abend 0CB occurred in module SAM1 program SAM1 at offset X'67C'.
A program interruption code 000B (Decimal-Divide Exception) is associated with
this abend and indicates that:
The divisor was zero in a signed decimal division.
The cause of the failure was program SAM1 in module SAM1. The COBOL source code
that immediately preceded the failure was:
Source List
Line # Stmt #
------ ------
000108 n/a COMPUTE UNIT-PRICE ROUNDED =
000109 n/a ORD-SALE-AMOUNT / ORD-NUM-ITEMS
The COBOL source code for data fields involved in the failure:
Source List
Line # Stmt #
------ ------
000040 n/a 05 ORD-NUM-ITEMS PIC 9(5).
000042 n/a 05 ORD-SALE-AMOUNT PIC 9(5)V99.
000057 n/a 05 UNIT-PRICE PIC S9(5)V99 COMP-3.
Data field values at time of abend:
ORD-NUM-ITEMS = 00000 *** Cause of error ***
ORD-SALE-AMOUNT = 0002000
UNIT-PRICE = X'0000100C'
2003 BM Corporation
November 4, 2003
<H1> I B M F A U L T A N A L Y Z E R E V E N T S U M M A R Y
The following events are presented in chronological order.
Event Fail Module Program EP Source List
# Type Point Name Name Name Line # Stmt # Offset Module Origin
-- ------------ ----- -------- -------- -------- ------ ------ -------- ------------------------------------
1 Abend S0CB ***** SAM1 SAM1 SAM1 000108 n/a 67C DNET074.ADLAB.LOAD
<H1> I B M F A U L T A N A L Y Z E R E V E N T D E T A I L S
================================================================================
<H2> EVENT 1 OF 1: ABEND S0CB
********************************************************************************
*********************** P O I N T O F F A I L U R E **********************
********************************************************************************
Abend Code. . . . . . . . . : S0CB
Program Interruption Code . : 000B (Decimal-Divide Exception)
Source List
Line # Stmt #
------ ------
COBOL Source Code . . . . . : 000108 n/a COMPUTE UNIT-PRICE ROUNDED =
000109 n/a ORD-SALE-AMOUNT / ORD-NUM-ITEMS
Source List
Line # Stmt #
------ ------
Data Field Declarations . . : 000040 n/a 05 ORD-NUM-ITEMS PIC 9(5).
000042 n/a 05 ORD-SALE-AMOUNT PIC 9(5)V99.
000057 n/a 05 UNIT-PRICE PIC S9(5)V99 COMP-3
2003 BM Corporation
November 4, 2003
Data Field Values . . . . . : ORD-NUM-ITEMS = 00000 *** Cause of error ***
ORD-SALE-AMOUNT = 0002000
UNIT-PRICE = X'0000100C'
The listing or side file used for the above was found in
DNET074.ADLAB.LISTING(SAM1).
Load Module Name. . . . . . : DNET074.ADLAB.LOAD(SAM1)
At Address. . . . . . . . : 19300418
Load Module Length. . . . : X'1BE8'
Link-Edit Date and Time . : 2003/06/08 13:00:03
Program and Entry Point Name: SAM1
At Address. . . . . . . . : 19300418 (Module SAM1 offset X'0')
Program Length. . . . . . : X'FA0'
Program Language. . . . . : COBOL (Compiled using IBM Enterprise COBOL for
z/OS and OS/390 V3 R2 M0 on 2003/06/08 at
13:00:03)
Service Level . . . . . . : n/a
Machine Instruction . . . . : FD72D120D128 DP 288(8,R13),296(3,R13)
At Address. . . . . . . . : 19300A94 (Program SAM1 offset X'67C')
AMODE . . . . . . . . . . : 31
Failing Operand . . . . . : Second operand
First Operand Address . . : 0000D150 (204464 bytes of storage addressable)
First Operand Length. . . : 8
First Operand Storage . . : 00000000 0020000F *........*
Second Operand Address. . : 0000D158 (204456 bytes of storage addressable)
Second Operand Length . . : 3
Second Operand Storage. . : 00000F *...*
Program Status Word (PSW) . : 078D1000 99300A9A
General Purpose Registers:
R0: 0000D168 (204440 bytes of storage addressable)
R1: 19393DA0 (Module SAM1 program SAM1 FILE SECTION BLF=0000 + X'0', symbol
ORDER-RECORD, source line # 29)
R2: 193009F6 (Module SAM1 program SAM1 + X'5DE', source line # 98)
R3: 19384038 (5423048 bytes of storage addressable)
2003 BM Corporation
November 4, 2003
R4: 193805E0 (5437984 bytes of storage addressable)
R5: 99300A40 (Module SAM1 program SAM1 + X'628', source line # 104)
R6: 193AFFB0 (Module SAM1 program SAM1 FILE SECTION BLF=0001 + X'0', symbol
REPORT-LINE, source line # 48)
R7: 19393DA0 (Module SAM1 program SAM1 FILE SECTION BLF=0000 + X'0', symbol
ORDER-RECORD, source line # 29)
R8: 193840B8 (Module SAM1 program SAM1 WORKING-STORAGE SECTION BLW=0000 +
X'0', symbol PROGRAM-WORK-FIELDS, source line # 52)
R10: 19300540 (Module SAM1 program SAM1 + X'128')
R12: 19300514 (Module SAM1 program SAM1 + X'FC')
R14: 800328F0 (Module IGZEQBL + X'2170')
R15: 00B1A0D0 (Module IGG019AA + X'0')
--------------------------------------------------------------------------------
<H3> Associated Messages
CEE3211S The system detected a decimal-divide exception (System Completion
Code=0CB).
CEE3211S
Code=0CB).
Explanation: Your program attempted to perform a mathematical operation
where, in decimal division, the divisor is zero or the quotient exceeds
the specified data-field size. See a Principles of Operation manual for a
full list of decimal-divide exceptions.
Programmer Response: You can use a condition handling routine to correct
the data values and resume the application.
System Action: The thread is terminated.
Symbolic Feedback Code: CEE34B
--------------------------------------------------------------------------------
2003 BM Corporation
November 4, 2003
<H3> Open Files
File Name . . . . . . . . . : ORDERS
Data Set Name . . . . . . : DNET074.ADLAB.DATA
File Attributes . . . . . : ORGANIZATION=SEQUENTIAL, ACCESS MODE=SEQUENTIAL,
RECFM=FIXED
Last I/O Function . . . . : READ
Open Status . . . . . . . : INPUT
File Status Code. . . . . : 0
Previous Record . . . . . : Record data length 80
Address Offset Hex EBCDIC
-------- --------- ----------------------------------- ------------------
19393D50 F0F0F0F0 F34040F9 4040F0F1 F0F540D1 *00003 9 0105 J*
19393D60 +10 D6C8D5E2 D6D54040 40F0F0F0 F2F040F0 *OHNSON 00020 0*
19393D70 +20 F0F0F2F0 F0F04040 40404040 40404040 *002000 *
19393D80 +30 40404040 40404040 40404040 40404040 * *
Line 19393D90 same as above
Current Record. . . . . . : Record data length 80
-------- --------- ----------------------------------- ------------------
19393DA0 F0F0F0F0 F44040F9 4040F0F1 F0F340C4 *00004 9 0103 D*
19393DB0 +10 C1E5C9E2 40404040 40F0F0F0 F0F040F0 *AVIS 00000 0*
19393DC0 +20 F0F0F2F0 F0F0404C 7E7E7DF0 F0F0F0F0 *002000 <=='00000*
19393DD0 +30 7D40C9D5 407BC9E3 C5D4E240 C3C1E4E2 *' IN #ITEMS CAUS*
19393DE0 +40 C5E240E2 F0C3C240 C9D540E2 C1D4F140 *ES S0CB IN SAM1 *
Next Record . . . . . . . : Record data length 80
-------- --------- ----------------------------------- ------------------
19393DF0 F0F0F0F0 F54040F9 40407C50 7C5040E2 *00005 9 @&@& S*
19393E00 +10 E3D6E4E3 40404040 40F0F0F0 F0F140F0 *TOUT 00001 0*
19393E10 +20 F0F0F1F0 F0F0404C 7E7E7D7C 507C507D *001000 <=='@&@&'*
19393E20 +30 40C9D540 C9E3C5D4 C3D6C4C5 40C3C1E4 * IN ITEMCODE CAU*
19393E30 +40 E2C5E240 E2F0C3F7 40C9D540 E2C1D4F2 *SES S0C7 IN SAM2*
2003 BM Corporation
November 4, 2003
File Name . . . . . . . . . : SUMMARY
Data Set Name . . . . . . : DNET074.DBSTOUTY.JOB09683.D0000103.?
RECFM=FIXED
Last I/O Function . . . . : WRITE
Open Status . . . . . . . : OUTPUT
No record buffers available.
--------------------------------------------------------------------------------
<H3> Associated Storage Areas
FILE SECTION at Address 19393DA0 (File ORDERS):
Source (Starting at Line # 000029) EBCDIC Value Hex Value
------------------------------------------------------------------------ ------------------ ----------------
01 ORDER-RECORD.
05 ORD-NUMBER PIC 9(5). *00004 * F0F0F0F0 F4
05 FILLER REDEFINES ORD-NUMBER.
10 ORDER-REC-COMMENT PIC X. *0 * F0
10 FILLER PIC X(4). *0004 * F0F0F0F4
05 FILLER PIC XX. * * 4040
05 ORD-LOCATION-CODE PIC 9. *9 * F9
05 FILLER PIC XX. * * 4040
05 ORD-ITEM-CODE PIC 9(4). *0103 * F0F1F0F3
05 FILLER PIC X. * * 40
05 ORD-CUST-ID PIC X(10). *DAVIS * C4C1E5C9 E240404
05 ORD-NUM-ITEMS PIC 9(5). *00000 * F0F0F0F0 F0
05 FILLER PIC X. * * 40
05 ORD-SALE-AMOUNT PIC 9(5)V99. *0002000 * F0F0F0F2 F0F0F0
FILE SECTION at Address 193AFFB0 (File SUMMARY):
------------------------------------------------------------------------ ------------------ ----------------
01 REPORT-LINE PIC X(80). *JOHNSON DB99* D1D6C8D5 E2D6D54
*9 - BLUE * F9406040 C2D3E4C
*20 $ 20.00 * F2F04040 405B404
* $ 1.00 * 405B4040 404040F
* * 40404040 4040404
2003 BM Corporation
November 4, 2003
WORKING-STORAGE SECTION at Address 193840B8:
------------------------------------------------------------------------ ------------------ ----------------
01 PROGRAM-WORK-FIELDS.
05 WS-START PIC X(29)
VALUE '<WORKING-STORAGE-STARTS-HERE>'. *<WORKING-STORAGE* 4CE6D6D9 D2C9D5C
*-STARTS-HERE> * 60E2E3C1 D9E3E26
05 TOTAL-SALES-AMOUNT PIC S9(7)V99 COMP-3. *..... * 00002375 0C
05 NUMBER-OF-ORDERS PIC S9(7) COMP-3. *.... * 0000003C
05 UNIT-PRICE PIC S9(5)V99 COMP-3. *.... * 0000100C
05 TOT-DISC-AMOUNT PIC S9(5)V99 COMP-3. *.... * 00000000
05 RETURNED-DESCRIP PIC X(15). *DB999 - BLUE * C4C2F9F9 F940604
01 REPORT-TEXT.
05 DETAIL-HDR-1.
10 FILLER PIC X(36) VALUE
'CUST ID ITEM DESCRIP QUANT '. *CUST ID ITEM* C3E4E2E3 40C9C44
* DESCRIP QUA* 40C4C5E2 C3D9C9D
*NT * D5E34040
'SALE AMOUNT UNIT PRICE'. *SALE AMOUNT UNI* E2C1D3C5 40C1D4D
*T PRICE * E340D7D9 C9C3C5
05 DETAIL-HDR-2.
'---------- --------------- ----- '. *---------- ----* 60606060 6060606
*----------- ---* 60606060 6060606
*-- * 60604040
'----------- ----------'. *----------- ---* 60606060 6060606
*------- * 60606060 606060
05 DETAIL-LINE.
10 RPT-CUST-ID PIC X(10). *JOHNSON * D1D6C8D5 E2D6D54
10 FILLER PIC XX VALUE SPACES. * * 4040
10 RPT-ITEM-DESCRIP PIC X(15). *DB999 - BLUE * C4C2F9F9 F940604
10 RPT-QUANTITY PIC ZZZZ9. * 20 * 404040F2 F0
10 FILLER PIC XXX VALUE SPACES. * * 404040
10 RPT-SALE-AMOUNT PIC $ZZ,ZZ9.99. *$ 20.00 * 5B404040 40F2F04
10 RPT-UNIT-PRICE PIC $ZZ,ZZ9.99. *$ 1.00 * 5B404040 4040F14
2003 BM Corporation
November 4, 2003
05 SUMMARY-LINE-1.
10 FILLER PIC X(21)
VALUE 'ORDERS PROCESSED = '. *ORDERS PROCESSED* D6D9C4C5 D9E240D
* = * 4040407E 40
10 RPT-NUM-ORDERS PIC ZZZZ9. *..... * 00000000 00
05 SUMMARY-LINE-2.
10 FILLER PIC X(14)
VALUE 'TOTAL SALES = '. *TOTAL SALES = * E3D6E3C1 D340E2C
10 RPT-TOTAL-SALES PIC $Z,ZZZ,ZZ9.99. *............. * 00000000 0000000
01 PROGRAM-SWITCHES.
05 END-OF-ORDERS PIC X. *. * 10
NOTE: BLL=0000 has not been assigned an address.
<H1> I B M F A U L T A N A L Y Z E R A B E N D J O B I N F O
IBM Fault Analyzer Abend Job Information:
Abend Date. . . . . . . . : 2003/06/08
Abend Time. . . . . . . . : 13:06:13
System Name . . . . . . . : DEMOMVS
Job Type. . . . . . . . . : Batch
Job Name. . . . . . . . . : DBSTOUTY
Job Step Name . . . . . . : RUNSAM1
Job Class . . . . . . . . : A
EXEC Program Name . . . . : SAM1
User ID . . . . . . . . . : DNET074
Data Sets:
DDname Data Set or Path Name
-------- --------------------------------------------
STEPLIB DNET074.ADLAB.LOAD
2003 BM Corporation
November 4, 2003
Event-Related Application Programs:
The following list of event-related application programs is sorted by module
link-edit date/time and program compilation date/time in reverse chronological
order.
Module Link-Edit Program Compilation
Name Date Time Name Date Time
-------- ---------- -------- -------- ---------- --------
SAM1 2003/06/08 13:00:03 SAM1 2003/06/08 13:00:03
Execution Environment:
Operating System. . . . . : z/OS V1R4M0
Data Facility Product . . : DFSMS z/OS V1R3M0
Job Entry Subsystem . . . : JES2 z/OS 1.4
Language Environment. . . : V1 R4.0
CPU Model . . . . . . . . : 2064
<H1> I B M F A U L T A N A L Y Z E R O P T I O N S
IBM Fault Analyzer Options in Effect:
DETAIL(MEDIUM)
LISTSEARCH(BEST)
MAXMINIDUMPPAGES(256)
Data Sets:
The following Fault Analyzer data set or path names were either
preallocated, specified via DATASETS options, or provided as defaults.
-------- --------------------------------------------
IDIBOOKS FAULTANL.V3R1.SIDIBOOK
IDICACHE FAULTANL.V3R1.CACHE
IDIDOC FAULTANL.V3R1.SIDIDOC1
IDIHIST FAULTANL.V3R1.HIST
IDILCOB DNET074.ADLAB.LISTING
2003 BM Corporation
November 4, 2003
IDIMAPS FAULTANL.V3R1.SIDIMAPS
Fault Analyzer was invoked via the LE CEEEXTAN exit (IDIXCEE) and used a maximum
of 0.81 megabytes of allocated storage for analysis.
End of Fault Analyzer report (2003/06/08 13:06).
When this analysis report was generated, Fault
Analyzer found source listings for the programs
The report starting on the next page shows the
same application abending in the same way, but
the listings were not available to Fault Analyzer
2003 BM Corporation
November 4, 2003
#eal-Time #eport itout Source
********************************************************************************
* IBM Fault Analyzer for z/OS and OS/390 V3R1M0 (UQ73759 2003/02/17) *
* *
* (C) Copyright IBM Corp. 2000, 2002. All rights reserved. *
********************************************************************************
JOBNAME: DBSTOUTN SYSTEM ABEND: 0CB DEMOMVS 2003/06/08 13:05:18 Page 001
<H1> I B M F A U L T A N A L Y Z E R S Y N O P S I S
A system abend 0CB occurred in module SAM1 program SAM1 at offset X'67C'.
A program interruption code 000B (Decimal-Divide Exception) is associated with
this abend and indicates that:
The abend was caused by machine instruction FD72D120D128 (DP).
Most recently referenced data items:
Data Item . . . . . . . . : BLF=0000+019
At Address. . . . . . . : 19393DB9
Length. . . . . . . . . : X'5'
Data Item Storage . . . : F0F0F0F0 F0 *00000*
Data Item . . . . . . . . : BLF=0000+01F
At Address. . . . . . . : 19393DBF
Length. . . . . . . . . : X'7'
Data Item Storage . . . : F0F0F0F2 F0F0F0 *0002000*
NOTE: Source code information could not be presented because the search for a
compiler listing or side-file was unsuccessful for program SAM1.
2003 BM Corporation
November 4, 2003
<H1> I B M F A U L T A N A L Y Z E R E V E N T S U M M A R Y
The following events are presented in chronological order.
Event Fail Module Program EP Source List
# Type Point Name Name Name Line # Stmt # Offset Module Origin
-- ------------ ----- -------- -------- -------- ------ ------ -------- ------------------------------------
1 Abend S0CB ***** SAM1 SAM1 SAM1 n/a n/a 67C DNET074.ADLAB.LOAD
<H1> I B M F A U L T A N A L Y Z E R E V E N T D E T A I L S
================================================================================
<H2> EVENT 1 OF 1: ABEND S0CB
********************************************************************************
*********************** P O I N T O F F A I L U R E **********************
********************************************************************************
Abend Code. . . . . . . . . : S0CB
Program Interruption Code . : 000B (Decimal-Divide Exception)
Most recently referenced data items:
Data Item . . . . . . . . : BLF=0000+019
At Address. . . . . . . : 19393DB9
Length. . . . . . . . . : X'5'
Data Item Storage . . . : F0F0F0F0 F0 *00000*
Data Item . . . . . . . . : BLF=0000+01F
At Address. . . . . . . : 19393DBF
Length. . . . . . . . . : X'7'
Data Item Storage . . . : F0F0F0F2 F0F0F0 *0002000*
NOTE: Source code information could not be presented because the search for a
compiler listing or side-file was unsuccessful for program SAM1.
2003 BM Corporation
November 4, 2003
Load Module Name. . . . . . : DNET074.ADLAB.LOAD(SAM1)
At Address. . . . . . . . : 19300418
Load Module Length. . . . : X'1BE8'
Link-Edit Date and Time . : 2003/06/08 13:00:03
Program and Entry Point Name: SAM1
At Address. . . . . . . . : 19300418 (Module SAM1 offset X'0')
Program Length. . . . . . : X'FA0'
Program Language. . . . . : COBOL (Compiled using IBM Enterprise COBOL for
z/OS and OS/390 V3 R2 M0 on 2003/06/08 at
13:00:03)
Service Level . . . . . . : n/a
Machine Instruction . . . . : FD72D120D128 DP 288(8,R13),296(3,R13)
At Address. . . . . . . . : 19300A94 (Program SAM1 offset X'67C')
AMODE . . . . . . . . . . : 31
Failing Operand . . . . . : Second operand
First Operand Address . . : 0000D150 (204464 bytes of storage addressable)
First Operand Length. . . : 8
First Operand Storage . . : 00000000 0020000F *........*
Second Operand Address. . : 0000D158 (204456 bytes of storage addressable)
Second Operand Length . . : 3
Second Operand Storage. . : 00000F *...*
Program Status Word (PSW) . : 078D1000 99300A9A
General Purpose Registers:
R1: 19393DA0 (Module SAM1 program SAM1 FILE SECTION BLF=0000 + X'0')
R2: 193009F6 (Module SAM1 program SAM1 + X'5DE')
R4: 193805E0 (5437984 bytes of storage addressable)
R5: 99300A40 (Module SAM1 program SAM1 + X'628')
R6: 193AFFB0 (Module SAM1 program SAM1 FILE SECTION BLF=0001 + X'0')
R7: 19393DA0 (Module SAM1 program SAM1 FILE SECTION BLF=0000 + X'0')
R8: 193840B8 (Module SAM1 program SAM1 WORKING-STORAGE SECTION BLW=0000 +
X'0')
2003 BM Corporation
November 4, 2003
R12: 19300514 (Module SAM1 program SAM1 + X'FC')
R14: 800328F0 (Module IGZEQBL + X'2170')
R15: 00B1A0D0 (Module IGG019AA + X'0')
--------------------------------------------------------------------------------
<H3> Associated Messages
Code=0CB).
CEE3211S
Code=0CB).
Explanation: Your program attempted to perform a mathematical operation
where, in decimal division, the divisor is zero or the quotient exceeds
the specified data-field size. See a Principles of Operation manual for a
full list of decimal-divide exceptions.
Programmer Response: You can use a condition handling routine to correct
the data values and resume the application.
System Action: The thread is terminated.
Symbolic Feedback Code: CEE34B
--------------------------------------------------------------------------------
<H3> Open Files
File Name . . . . . . . . . : ORDERS
Data Set Name . . . . . . : DNET074.ADLAB.DATA
RECFM=FIXED
Last I/O Function . . . . : READ
2003 BM Corporation
November 4, 2003
Open Status . . . . . . . : INPUT
Previous Record . . . . . : Record data length 80
-------- --------- ----------------------------------- ------------------
19393D50 F0F0F0F0 F34040F9 4040F0F1 F0F540D1 *00003 9 0105 J*
19393D60 +10 D6C8D5E2 D6D54040 40F0F0F0 F2F040F0 *OHNSON 00020 0*
19393D70 +20 F0F0F2F0 F0F04040 40404040 40404040 *002000 *
19393D80 +30 40404040 40404040 40404040 40404040 * *
Line 19393D90 same as above
Current Record. . . . . . : Record data length 80
-------- --------- ----------------------------------- ------------------
19393DA0 F0F0F0F0 F44040F9 4040F0F1 F0F340C4 *00004 9 0103 D*
Next Record . . . . . . . : Record data length 80
-------- --------- ----------------------------------- ------------------
19393DF0 F0F0F0F0 F54040F9 40407C50 7C5040E2 *00005 9 @&@& S*
19393E10 +20 F0F0F1F0 F0F0404C 7E7E7D7C 507C507D *001000 <=='@&@&'*
File Name . . . . . . . . . : SUMMARY
Data Set Name . . . . . . : DNET074.DBSTOUTN.JOB09682.D0000103.?
RECFM=FIXED
Last I/O Function . . . . : WRITE
Open Status . . . . . . . : OUTPUT
No record buffers available.
2003 BM Corporation
November 4, 2003
<H3> Associated Storage Areas
Task Global Table (TGT) at Address 19380448:
-------- --------- ----------------------------------- ------------------
19380448 00000000 00000000 00000000 00000000 *................*
Lines 19380458-19380478 same as above
19380488 +40 00000000 00000000 F3E3C7E3 00000000 *........3TGT....*
19380498 +50 06000000 64020260 19380100 000077FC *.......-........*
193804A8 +60 193805A8 00000002 00000129 00000000 *...y............*
193804B8 +70 00000000 0002D1C0 00000000 00000000 *......J{........*
193804C8 +80 1930CBE8 0000015C 00000000 00000000 *...Y...*........*
193804D8 +90 00000000 00000001 E2E8E2D6 E4E34040 *........SYSOUT *
193804E8 +A0 C9C7E9E2 D9E3C3C4 00000000 00000000 *IGZSRTCD........*
193804F8 +B0 00000000 00000000 00000000 00000000 *................*
Lines 19380508-19380518 same as above
19380528 +E0 00000000 00000000 19300514 00000000 *................*
19380538 +F0 19380590 193803F0 19300640 00000000 *.......0... ....*
19380548 +100 19300418 19300558 19380588 1930053C *...........h....*
19380558 +110 19380588 193840B8 00000000 00000000 *...h.. .........*
19380568 +120 00000000 00000000 19384038 193840B8 *.......... ... .*
19380578 +130 00000000 19393DA0 193AFFB0 19381500 *................*
19380588 +140 193805E0 193806F8 40000000 00000000 *...\...8 .......*
19380598 +150 00000000 19380810 00000001 *............ *
FILE SECTION BLF=0000 at Address 19393DA0 (File ORDERS):
-------- --------- ----------------------------------- ------------------
19393DA0 F0F0F0F0 F44040F9 4040F0F1 F0F340C4 *00004 9 0103 D*
19393DF0 +50 F0F0F0F0 F54040F9 40407C50 7C5040E2 *00005 9 @&@& S*
19393E10 +70 F0F0F1F0 F0F0404C 7E7E7D7C 507C507D *001000 <=='@&@&'*
2003 BM Corporation
November 4, 2003
19393E40 +A0 F0F0F0F0 F64040F9 4040F0F1 F0F440E2 *00006 9 0104 S*
19393E50 +B0 C5D5D540 40404040 40F0F0F2 F5F040F0 *ENN 00250 0*
19393E60 +C0 F2F0F0F0 F0F04040 40404040 40404040 *200000 *
19393E70 +D0 40404040 40404040 40404040 40404040 * *
Line 19393E80 same as above
19393E90 +F0 00000000 00000000 00000000 00000000 *................*
Lines 19393EA0-19394D90 same as above
FILE SECTION BLF=0001 at Address 193AFFB0 (File SUMMARY):
-------- --------- ----------------------------------- ------------------
193AFFB0 D1D6C8D5 E2D6D540 40404040 C4C2F9F9 *JOHNSON DB99*
193AFFC0 +10 F9406040 C2D3E4C5 40404040 40404040 *9 - BLUE *
193AFFD0 +20 F2F04040 405B4040 4040F2F0 4BF0F040 *20 $ 20.00 *
193AFFE0 +30 405B4040 404040F1 4BF0F040 40404040 * $ 1.00 *
193AFFF0 +40 40404040 40404040 40404040 40404040 * *
193B0000 +50 00000000 00000000 00000000 00000000 *................*
Lines 193B0010-193B0AF0 same as above
193B0B00 +B50 00000000 00000000 47F0F028 00C3C5C5 *.........00..CEE*
193B0B10 +B60 000001B8 00000014 47F0F001 98CEAC00 *.........00.q...*
193B0B20 +B70 193B0BBE 00000000 00000000 00000000 *................*
193B0B30 +B80 90ECD00C 4110F038 98EFF04C 07FF0000 *..}...0.q.0<....*
193B0B40 +B90 193B0B08 00000000 193B1180 193B0BB6 *................*
193B0B50 +BA0 193B0B08 193B0DFA 193B14A8 193B0BD2 *...........y...K*
193B0B60 +BB0 00104001 00000008 E2C1D4F2 40404040 *.. .....SAM2 *
193B0B70 +BC0 F2F0F0F3 F0F6F0F8 F1F2F5F9 F1F2F0F3 *2003060812591203*
193B0B80 +BD0 F0F2F0F0 04740000 0000076C A4E87CCC *0200.......%uY@.*
193B0B90 +BE0 20000000 4000000D 05000002 08000000 *.... ...........*
193B0BA0 +BF0 00008000 00000013 0000001B 00008200 *..............b.*
193B0BB0 +C00 40404040 0004E2C1 D4F24040 40400500 * ..SAM2 ..*
193B0BC0 +C10 0001193B 13F80000 0000FFFF FFB2193B *.....8..........*
skip u few Iines
193B0F40 +F90 47F0B34C D2039164 A030F230 D1087007 *.0.<K.j...2.J...*
193B0F50 +FA0 960FD10B FC32D108 A0D2F822 802ED109 *o.J...J..K8...J.*
193B0F60 +FB0 F223D108 700A960F D10AFA22 D108802E *2.J...o.J...J...*
193B0F70 +FC0 F3428029 D10896F0 802D58B0 C02847F0 *3...J.o0....{..0*
193B0F80 +FD0 B1FA5820 91644A20 A0265020 91645820 *....j....&.j...*
193B0F90 +FE0 A0285920 916447B0 B21AD20B 6000A091 *....j.....K.-..j*
193B0FA0 +FF0 D202600C C00458B0 C02847F0 B24C5820 *K.-.{...{..0.<..*
2003 BM Corporation
November 4, 2003
WORKING-STORAGE SECTION BLW=0000 at Address 193840B8:
-------- --------- ----------------------------------- ------------------
193840B8 4CE6D6D9 D2C9D5C7 60E2E3D6 D9C1C7C5 *<WORKING-STORAGE*
193840C8 +10 60E2E3C1 D9E3E260 C8C5D9C5 6E000023 *-STARTS-HERE>...*
193840D8 +20 750C0000 003C0000 100C0000 0000C4C2 *..............DB*
193840E8 +30 F9F9F940 6040C2D3 E4C54040 40000000 *999 - BLUE ...*
193840F8 +40 C3E4E2E3 40C9C440 40404040 C9E3C5D4 *CUST ID ITEM*
19384108 +50 40C4C5E2 C3D9C9D7 40404040 40D8E4C1 * DESCRIP QUA*
19384118 +60 D5E34040 E2C1D3C5 40C1D4D6 E4D5E340 *NT SALE AMOUNT *
19384128 +70 40E4D5C9 E340D7D9 C9C3C560 60606060 * UNIT PRICE-----*
19384138 +80 60606060 60404060 60606060 60606060 *----- ---------*
19384148 +90 60606060 60604040 60606060 60404060 *------ ----- -*
19384158 +A0 60606060 60606060 60604040 60606060 *---------- ----*
19384168 +B0 60606060 6060D1D6 C8D5E2D6 D5404040 *------JOHNSON *
19384178 +C0 4040C4C2 F9F9F940 6040C2D3 E4C54040 * DB999 - BLUE *
19384188 +D0 40404040 4040F2F0 4040405B 40404040 * 20 $ *
19384198 +E0 F2F04BF0 F040405B 40404040 40F14BF0 *20.00 $ 1.0*
193841A8 +F0 F0D6D9C4 C5D9E240 D7D9D6C3 C5E2E2C5 *0ORDERS PROCESSE*
193841B8 +100 C4404040 7E400000 000000E3 D6E3C1D3 *D = .....TOTAL*
193841C8 +110 40E2C1D3 C5E2407E 40000000 00000000 * SALES = .......*
193841D8 +120 00000000 00000000 D5 *........N *
NOTE: BLL=0000 has not been assigned an address.
<H1> I B M F A U L T A N A L Y Z E R A B E N D J O B I N F O
IBM Fault Analyzer Abend Job Information:
Abend Date. . . . . . . . : 2003/06/08
Abend Time. . . . . . . . : 13:05:18
System Name . . . . . . . : DEMOMVS
Job Type. . . . . . . . . : Batch
Job Name. . . . . . . . . : DBSTOUTN
Job Step Name . . . . . . : RUNSAM1
Job Class . . . . . . . . : A
2003 BM Corporation
November 4, 2003
EXEC Program Name . . . . : SAM1
User ID . . . . . . . . . : DNET074
Data Sets:
-------- --------------------------------------------
STEPLIB DNET074.ADLAB.LOAD
Event-Related Application Programs:
The following list of event-related application programs is sorted by module
link-edit date/time and program compilation date/time in reverse chronological
order.
Module Link-Edit Program Compilation
Name Date Time Name Date Time
-------- ---------- -------- -------- ---------- --------
SAM1 2003/06/08 13:00:03 SAM1 2003/06/08 13:00:03
Execution Environment:
Operating System. . . . . : z/OS V1R4M0
Data Facility Product . . : DFSMS z/OS V1R3M0
Job Entry Subsystem . . . : JES2 z/OS 1.4
Language Environment. . . : V1 R4.0
CPU Model . . . . . . . . : 2064
<H1> I B M F A U L T A N A L Y Z E R O P T I O N S
IBM Fault Analyzer Options in Effect:
DETAIL(MEDIUM)
LISTSEARCH(BEST)
MAXMINIDUMPPAGES(256)
2003 BM Corporation
November 4, 2003
Data Sets:
The following Fault Analyzer data set or path names were either
preallocated, specified via DATASETS options, or provided as defaults.
-------- --------------------------------------------
IDIBOOKS FAULTANL.V3R1.SIDIBOOK
IDICACHE FAULTANL.V3R1.CACHE
IDIDOC FAULTANL.V3R1.SIDIDOC1
IDIHIST FAULTANL.V3R1.HIST
IDIMAPS FAULTANL.V3R1.SIDIMAPS
Fault Analyzer was invoked via the LE CEEEXTAN exit (IDIXCEE) and used a maximum
of 0.70 megabytes of allocated storage for analysis.
End of Fault Analyzer report (2003/06/08 13:05).
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
&sing the OnIine nterface
Fault Re-analysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
Te Online InterIace
Use the SPF interface
(in TSO) to:
O View reports
O Perform reanalysis
O Display and delete
fault entries
Fau|t
Ana|yzer
Fau|t h|story F||es
Fault
Entries
omp||er
L|st|ngs
0pt|ons
8|de F||es
|8PF
2003 BM Corporation
November 4, 2003
Te Online InterIace
Name of a Fault
History File
(or View)
O Overtype the
name to open a
different file
Available line
commands are
shown here.
O and entered here
2003 BM Corporation
November 4, 2003
Select from a list of
History Files you
have used before
So you don't have to
remember the file
names
2 Select from a list of
Fault Entries you
have recently
accessed
Some elpIul tings to do on te
FIE menu
4 Select from a list of "Views
A View is a shortcut a a History File, or
A view can be a concatenation of History files
They can be defined to Fault Analyzer (usually by a Systems
Programmer)
2003 BM Corporation
November 4, 2003
-2 Add or remove
blank lines from the
display
Add for easier
reading, remove to
conserve screen
space
3-6 Add or remove
detail and help info
'IE menu
Customize columns shown in the list of Fault Entries
Add or remove columns from the list
Same as the COLS command
2003 BM Corporation
November 4, 2003
Look up a
message
Bookmanager lookup
of messages
received form the
system
2 Copy to a file
Copy the entire
scrollable area to a
sequential file or PDS
member
SE#'ICES menu
2003 BM Corporation
November 4, 2003
View the Fault
Analyzer User's
Guide online
2 Get info about
Fault Analyzer
version and
maintenance level
E! menu
2003 BM Corporation
November 4, 2003
ine Commands
? Query summary info for a Fault Entry
V View (browse) a Real-Time Report
B Batch Reanalysis
D Delete an Entry
2003 BM Corporation
November 4, 2003
ine Commands
Use the V line
command to
view a Real-
Time report
Navigation is
similar to a
Browse
session
Use Collapse
and Expand
for easier
navigation
Enter
2003 BM Corporation
November 4, 2003
ine Commands
Use the ? line
command to
see more
information
about a fault
entry
Enter
2003 BM Corporation
November 4, 2003
Fault Analyzer Commands
Commands
Use help (PF) to get descriptions
COLS Brings up the Column Configuration panel
COPY osname Copies the current display to a file
FND aroumenr Finds argument in the list of Fault Entries
LOOK&P messaoe-|o Looks up a message
MATCH .4umn aroumenr Displays only entries that match argument
#EF#ESH Refreshes the display to show new entries
VEWS Displays a list of Views that can be selected
2003 BM Corporation
November 4, 2003
orking wit te list oI Entries
Two ways to find the entry you are looking for:
Use the FND command to locate an entry
Use the MATCH command to limit the list of
displayed entries
2003 BM Corporation
November 4, 2003
ocate a Iault entry wit te Find command
Use the Find
command to
locate any
character
string
Enter
2003 BM Corporation
November 4, 2003
ocate a Iault entry wit te Matc command
Use the Match
command to
display only
entries that
match your
criteria
The * wildcard
can be used
anywhere in
the search
argument
Enter
Now only jobs that start
with D are displayed
Now only jobs that start
with D are displayed
A Match command is entered .
2003 BM Corporation
November 4, 2003
Multiple Matc commands
Enter the
Match
command
more than
once to specify
multiple criteria
Entries must
meet ALL of
your Match
conditions
. and then another Match command is entered
Now only entries are shown
that match both:
Job/Tran = D*
and
&ser_D = DNET074
Now only entries are shown
that match both:
Job/Tran = D*
and
&ser_D = DNET074
Enter
2003 BM Corporation
November 4, 2003
Matc All command
The
MATCH ALL
command
displays all
entries again
Enter
All entries
are shown
All entries
are shown
2003 BM Corporation
November 4, 2003
Te COS command
Columns can
be customized
You can also
get here from
the View menu
Settings are
stored in your
profile
Enter
2003 BM Corporation
November 4, 2003
Column Customization
Specify which columns you want to see PF3 to return
%pe ze7o lo 7erove a
co|urr l7or ou7 d|sp|a
%pe ze7o lo 7erove a
co|urr l7or ou7 d|sp|a
rle7 a ror-
ze7o ruroe7 lo
ra|e a co|urr
appea7
rle7 a ror-
ze7o ruroe7 lo
ra|e a co|urr
appea7
PF8
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
FauIt #e-anaIysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
y do #e-analysis ?
The abending program's source listing was not
available to Fault Analyzer when the abend occurred
O n the Real-Time Report, we got:
Apply program source information
O So with Reanalysis, we get:
Also, interactive Reanalysis lets you navigate online
and view program source
A system abend 0C7 occurred in module IDISCBL1
CSECT IDISCBL1 at offset X'3D0'.
The abend was caused by machine instruction FD73D0B8D0A8(DP)
A system abend 0C7 occurred in module IDISCBL1
CSECT IDISCBL1 at offset X'3D0'.
The abend was caused by machine instruction FD73D0B8D0A8(DP)
The cause of the failure was program IDISCBL1.
The COBOL source code that immediately preceded the failure was:
Source
Line #
------
000051 DIVIDE NUMBERX BY ERROR_COUNT GIVING BAD_RESULT
The cause of the failure was program IDISCBL1.
The COBOL source code that immediately preceded the failure was:
Source
Line #
------
000051 DIVIDE NUMBERX BY ERROR_COUNT GIVING BAD_RESULT
2003 BM Corporation
November 4, 2003
Interactive #eanalysis Quick Tour
Walkthrough: Start an nteractive Reanalysis session and
step through basic navigation
Set up Fault Analyzer to automatically prompt for
options when nteractive Reanalysis is started
I command to start Re-analysis
Specify options to tell Fault Analyzer where to find
program Source Listings
Step through the basic navigation features
2003 BM Corporation
November 4, 2003
Interactive #eanalysis Tour (1 oI 25)
The I line command starts an nteractive Reanalysis session.
Enter
2003 BM Corporation
November 4, 2003
interactive reanalysis options
Any FA
option can
be specified
Use the
"datasets
option to tell
FA where to
find compiler
listings
Any FA
option can
be specified
Use the
"datasets
option to tell
FA where to
find compiler
listings
"Y here makes this screen appear automatically
whenever you start an nteractive Reanalysis
You can get to this screen the first time from the
"Options pull-down menu, then select "nteractive
Reanalysis Options
"Y here makes this screen appear automatically
whenever you start an nteractive Reanalysis
You can get to this screen the first time from the
"Options pull-down menu, then select "nteractive
Reanalysis Options
PF3
2003 BM Corporation
November 4, 2003
main navigation screen. go to the program listing
"Point and shoot fields are
highlighted
Use tab and Enter to navigate
"Point and shoot fields are
highlighted
Use tab and Enter to navigate
Enter
2003 BM Corporation
November 4, 2003
program listing . return to the main navigation screen
Browse program source
information from the
compiler listing here
Use standard browse
commands and PF Keys
Browse program source
information from the
compiler listing here
Use standard browse
commands and PF Keys
PF3
2003 BM Corporation
November 4, 2003
main navigation screen . go to synopsis information
to select Synopsis to select Synopsis
Enter
2003 BM Corporation
November 4, 2003
synopsis shows high-level information about the abend
Abend explanation Abend explanation
Program Program
Executing statement Executing statement
Variables used by the executing statement Variables used by the executing statement
PF3
2003 BM Corporation
November 4, 2003
main navigation screen . go to Events information
select Events select Events
Enter
2003 BM Corporation
November 4, 2003
events summary . go to program (event) detail
The Event Summary shows
the call chain and the
abending program
Any program or Event can
be examined for more detail
The Event Summary shows
the call chain and the
abending program
Any program or Event can
be examined for more detail
Enter
2003 BM Corporation
November 4, 2003
program (event) detail . go to abend code description
The abend code is a
Point and Shoot field
The abend code is a
Point and Shoot field
Enter
2003 BM Corporation
November 4, 2003
a description of the abend
PF3
2003 BM Corporation
November 4, 2003
program (event) detail . page forward
PF8
2003 BM Corporation
November 4, 2003
program (event) detail . point-and-shoot to a Address
Tab to go to an address
Many of the addresses are
Point and Shoot fields
Tab to go to an address
Many of the addresses are
Point and Shoot fields
Enter
2003 BM Corporation
November 4, 2003
storage display and browse
%pe ar add7ess ard rle7 lo do
lo ar ava||ao|e slo7ade.
%pe ar add7ess ard rle7 lo do
lo ar ava||ao|e slo7ade.
. o7 lao lo ar va||d
add7ess va|ue ard
rle7 lo do lre7e
. o7 lao lo ar va||d
add7ess va|ue ard
rle7 lo do lre7e
PF3
2003 BM Corporation
November 4, 2003
back to program (event) detail. page forward
Registers are
Point and
Shoot fields
Registers are
Point and
Shoot fields
PF8
2003 BM Corporation
November 4, 2003
more program (event) detail. page forward
Descriptions of the areas
pointed to by each register
Descriptions of the areas
pointed to by each register
The SQLCA is shown
(DB2 programs only)
The SQLCA is shown
(DB2 programs only)
PF8
2003 BM Corporation
November 4, 2003
end of program detail . go to Associated Storage Areas
Tab to select Storage
Areas associated with
the program
Tab to select Storage
Areas associated with
the program
Enter
2003 BM Corporation
November 4, 2003
Associated Storage Areas . go over to the right
Variables defined to the
program are shown here in
Use normal Browse commands
and PF Keys to navigate:
- Up, Down, Left, Right
- Top, Bottom, Max
- Find
Variables defined to the
program are shown here in
Use normal Browse commands
and PF Keys to navigate:
- Up, Down, Left, Right
- Top, Bottom, Max
- Find
PF11
2003 BM Corporation
November 4, 2003
Associated Storage Areas (on the right side of the display)
Variable
values are
shown in
character
and hex
Variable
values are
shown in
character
and hex
PF3
2003 BM Corporation
November 4, 2003
back to program (event) detail
PF3
2003 BM Corporation
November 4, 2003
back to events summary
PF3
2003 BM Corporation
November 4, 2003
back to main navigation screen . get System-Wide nfo
select System-Wide nformation select System-Wide nformation
Enter
2003 BM Corporation
November 4, 2003
system-wide info . get DB2 info
On this screen there may be links for:
- DB2 nformation
- CCS nformation
- MS nformation
On this screen there may be links for:
- DB2 nformation
- CCS nformation
- MS nformation
select DB2 nformation select DB2 nformation
Enter
2003 BM Corporation
November 4, 2003
DB2 information
PF3
2003 BM Corporation
November 4, 2003
back to system-wide info
PF3
2003 BM Corporation
November 4, 2003
back to the main navigation screen
2003 BM Corporation
November 4, 2003
Interactive #eanalysis Analyze an Abend
Walkthrough: Use nteractive Reanalysis to determine
the cause of an abend
I command to start Re-analysis
Navigate to understand why the application abended
2003 BM Corporation
November 4, 2003
Analyze an Abend (1 oI 19)
Enter
2003 BM Corporation
November 4, 2003
Any FA
option can
be specified
Use the
"datasets
option to tell
FA where to
find compiler
listings
Any FA
option can
be specified
Use the
"datasets
option to tell
FA where to
find compiler
listings
"Y here makes this screen appear automatically when you
start an nteractive Reanalysis
Get to this screen the first time from the "Options pull-down
menu, then select "nteractive Reanalysis Options
"Y here makes this screen appear automatically when you
start an nteractive Reanalysis
Get to this screen the first time from the "Options pull-down
menu, then select "nteractive Reanalysis Options
PF3
2003 BM Corporation
November 4, 2003
go to Synopsis
Debuq CIues:
Abended in
proqrom SAMZ
becouse of o dofo
excepfion
Whof is
FouIf
AnoIyzer's
Synopsis7
select Synopsis select Synopsis
Enter
2003 BM Corporation
November 4, 2003
page forward to see the active variables
Debuq CIues:
Abended in
proqrom SAMZ
whiIe execufinq
on ADD
sfofemenf
becouse of o dofo
excepfion
Here's a clue What can
cause a data exception?
Here's a clue What can
cause a data exception?
PF8
2003 BM Corporation
November 4, 2003
return to the menu
Debuq CIues:
Abended in
proqrom SAMZ
whiIe execufinq
on ADD
sfofemenf
becouse of o dofo
excepfion
Lef's qo Iook
of fhe bod
voriobIe
What variable contained the
bad data?
What variable contained the
bad data?
PF3
2003 BM Corporation
November 4, 2003
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hod bod
numeric dofo
Lef's qo Iook
of fhe bod
voriobIe,
OPD-ITEM-
CODE
select Events select Events
Enter
2003 BM Corporation
November 4, 2003
go to detail for program SAM
What is the relationship
between programs
SAM and SAM2?
What is the relationship
between programs
SAM and SAM2?
Enter
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hod bod
numeric dofo
Lef's qo Iook
of fhe bod
voriobIe,
OPD-ITEM-
CODE
2003 BM Corporation
November 4, 2003
go to the bottom of the program detail display
Enter
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hod bod
numeric dofo
Lef's qo Iook
of fhe bod
voriobIe,
OPD-ITEM-
CODE
2003 BM Corporation
November 4, 2003
Enter
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hod bod
numeric dofo
Lef's qo Iook
of fhe bod
voriobIe,
OPD-ITEM-
CODE
What will we see here? What will we see here?
2003 BM Corporation
November 4, 2003
find the variable name or value
Enter
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hod bod
numeric dofo
Lef's qo Iook
of fhe bod
voriobIe,
OPD-ITEM-
CODE
2003 BM Corporation
November 4, 2003
return to Program Detail
t is in Linkage Section
What does that mean?
t is in Linkage Section
What does that mean?
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hod bod
numeric dofo (if
is porf of
OPDEP-PECOPD)
Here is fhe
fhe bod
voriobIe,
OPD-ITEM-
CODE
PF3
The bad data The bad data
2003 BM Corporation
November 4, 2003
return to the Events list
PF3
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of
OPDEP-
PECOPD), which
wos possed from
o coIIinq proqrom
Lef's qo Iook
of fhe
possed dofo
2003 BM Corporation
November 4, 2003
go to detail for the calling program
The bad data was passed from a calling program
SAM called SAM2
The bad data was passed from a calling program
SAM called SAM2
Enter
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of
OPDEP-
PECOPD), which
wos possed from
o coIIinq proqrom
Lef's qo Iook
of fhe
possed dofo
2003 BM Corporation
November 4, 2003
detail for program SAM . go to the bottom
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of order-
record), which
wos possed from
o coIIinq proqrom
SAMI coIIed
SAMZ
Lef's qo Iook
of fhe
possed dofo
Enter
What passed variable
contained the bad data?
What passed variable
contained the bad data?
clue clue
2003 BM Corporation
November 4, 2003
go to see variables and storage for this program
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of order-
record), which
wos possed from
o coIIinq proqrom
SAMI coIIed
SAMZ
SAMI possed
bod dofo in
OPDEP-PECOPD
Lef's qo Iook
of OPDEP-
PECOPD
Enter
2003 BM Corporation
November 4, 2003
return to program detail
The bad data The bad data
t is in File
Section
What does
that mean?
t is in File
Section
What does
that mean?
What is the file
DD name?
What is the file
DD name?
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of order-
record), which
wos possed from
o coIIinq proqrom
SAMI coIIed
SAMZ
SAMI possed
bod dofo in
OPDEP-PECOPD
Here is
OPDEP-
PECOPD
PF3
2003 BM Corporation
November 4, 2003
go to Orders file info
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of
order-record)
SAMI coIIed
SAMZ
SAMI possed
bod dofo in
OPDEP-
PECOPD
The bod dofo
wos reod from
fiIe OPDEPS
Enter
2003 BM Corporation
November 4, 2003
page forward to see current record
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of
order-record)
SAMI coIIed
SAMZ
SAMI possed
bod dofo in
OPDEP-
PECOPD
The bod dofo
wos reod from
fiIe OPDEPS
What is the full name of
the ORDERS file?
What is the full name of
the ORDERS file?
PF8
2003 BM Corporation
November 4, 2003
Debuq CIues:
Abended in
proqrom SAMZ
becouse:
OPD-ITEM-
CODE hos bod
numeric dofo (if
is porf of
order-record)
SAMI coIIed
SAMZ
SAMI possed
bod dofo in
OPDEP-
PECOPD
The bod dofo
wos reod from
fiIe OPDEPS
Here is the
bad data in
the record
Here is the
bad data in
the record
2003 BM Corporation
November 4, 2003
Program
8AH1
F||e
0NET074.A0w0RK.0ATA
Analyze an Abend . wat appened:
SAM read a record from
an input file that contained
bad data in the ORD-
TEM-CODE field
2 Program SAM called
SAM2, passing the bad
data
3 SAM2 abended when it
tried to calculate using the
bad data
Program
8AH2
Abend
2003 BM Corporation
November 4, 2003
atc #eanalysis
What is BATCH reanalysis?
A Fault Analyzer utility that runs as a batch job and
generates an Analysis report
Why do Batch reanalysis?
To generate a new Analysis report
Possibly to:
O Apply compiler listing information
O Create a printable report for a CCS abend
O Generate a new reanalysis report that you can print
Or download and email it to someone
2003 BM Corporation
November 4, 2003
atc #eanalysis
Walkthrough: Batch Reanalysis
B command to start Re-analysis
Navigate to understand why the application abended
2003 BM Corporation
November 4, 2003
atc #eanalysis
The B line command starts a Batch Reanalysis session.
Enter
2003 BM Corporation
November 4, 2003
atc #eanalysis
batch options can be specified
PF3
2003 BM Corporation
November 4, 2003
atc #eanalysis
JCL is generated . submit and/or save
Enter
Use the Edit 'Create' or 'Replace' command if
you want to save the JCL in your own file
Use the Edit 'Create' or 'Replace' command if
you want to save the JCL in your own file
2003 BM Corporation
November 4, 2003
atc #eanalysis
report generated by batch reanalysis
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
Fault Re-analysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
CICS Transaction Support
Additional information available for CCS applications
O CCS control blocks
O Transaction storage
O Last Screen Buffer
O CCS Trace Table
O CCS abend code explanation
View in Real-Time report or with Reanalysis
2003 BM Corporation
November 4, 2003
CICS Transaction Analysis
2003 BM Corporation
November 4, 2003
Enter
2003 BM Corporation
November 4, 2003
Enter
Control Blocks:
OCommarea
OCSA
OTCA
OES
OEUS
OTCTTE
2003 BM Corporation
November 4, 2003
Enter
Transaction
Storage
2003 BM Corporation
November 4, 2003
Enter
Last CCS
3270 Screen
Buffer
2003 BM Corporation
November 4, 2003
CCS Trace
Table
Enter
2003 BM Corporation
November 4, 2003
get the CCS Abend Code description . first go to Events
2003 BM Corporation
November 4, 2003
select the abend event
2003 BM Corporation
November 4, 2003
select the abend code
2003 BM Corporation
November 4, 2003
abend description
2003 BM Corporation
November 4, 2003
2 Analysis
Additional information available for DB2 applications
O DB2 Subsystem
O Plan information
O Owner and Authorization Ds
O Last Executed SQL Statement
O Host Variables
O SQL Communications Area
O SQLCode and SQLState explanations
2003 BM Corporation
November 4, 2003
2 Analysis
Enter
2003 BM Corporation
November 4, 2003
2 Analysis
Enter
2003 BM Corporation
November 4, 2003
page forward through DB2 information
DB2 subsystem, plan,
Ds
DB2 subsystem, plan,
Ds
Last SQL statement Last SQL statement
Host variables Host variables
PF8
2003 BM Corporation
November 4, 2003
2 Analysis
Select SQLCode
SQL Communications Area SQL Communications Area
Enter
2003 BM Corporation
November 4, 2003
2 Analysis
SQLCode explanation
PF3
2003 BM Corporation
November 4, 2003
2 Analysis
Select SQLState
Enter
2003 BM Corporation
November 4, 2003
2 Analysis
SQLState explanation
2003 BM Corporation
November 4, 2003
IMS Analysis
Additional information available for MS applications
O MS Subsystem
O Region Type
O PSB
O OPCB
O Database PCBs
Segment
Key feedback area
Call trace
O Call counts
O MS abend code explanations
2003 BM Corporation
November 4, 2003
IMS Analysis
select System-Wide nformation
Enter
2003 BM Corporation
November 4, 2003
IMS Analysis
select MS information
Enter
nformation about database
datasets (DL region)
nformation about database
datasets (DL region)
2003 BM Corporation
November 4, 2003
IMS Analysis
page forward through MS information
connection info connection info
Database
PCB
Database
PCB
PF8
2003 BM Corporation
November 4, 2003
IMS Analysis
Key feedback area Key feedback area
Call trace Call trace
Second
Database PCB
Second
Database PCB
PF8
2003 BM Corporation
November 4, 2003
IMS Analysis
Call counts Call counts
PF8
2003 BM Corporation
November 4, 2003
IMS Analysis
Call counts Call counts
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
Fault Re-analysis
Preparing programs for FauIt AnaIysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
etting your Application #eady
Fault Analyzer reads compiler listings and/or side files
to get source information
Specific compiler options are needed
Save compiler listings or side files to a PDS or PDSE
O or be able to recompile your program to re-create a
listing
2003 BM Corporation
November 4, 2003
enerating Source inIo Ior Fault Analyzer
There are three ways to store Program Source data that
Fault Analyzer will use:
Save the compiler listing
O for assembler, save the SYSADATA file instead
2 or process the compiler listing through FA utility program
DLANGX to create an DLANGX "side file
O t has the same info as the compiler listing, but takes less
space
3 or (for COBOL only), save the SYSDEBUG side file
generated by the compiler
O specify the TEST(. , . ,SEPARATE) compiler option to
create a SYSDEBUG file
2003 BM Corporation
November 4, 2003
Save source inIo. Metod 1
!7od7ar
3ou7ce
L|nk Ed|t omp||er
Compile and link
the application
program
Save the compiler
listing in a PDS
member
Use FA options to
point FA to the
listings PDS
Use different
Listings files for
different
compilers
oad rodu|e
Fau|t
Ana|yzer
App||cat|on
FA |nvokat|on Ex|t
Abend
omp||er
L|st|ngs
P08
FauIt AnaIyzer options:
DATASETS(DLCOB(.),DLCOBO(.),
DADATA(.),DLPL(.),DLPLE,DC(.))
2003 BM Corporation
November 4, 2003
!7od7ar
3ou7ce
L|nk Ed|t omp||er
Compile and link
the application
program
Process the listing
with the DLANGX
utility
Save the output of
DLANGX in a
PDS member
Use FA options to
point FA to the
DLANGX side file
oad rodu|e
Fau|t
Ana|yzer
App||cat|on
FA |nvokat|on Ex|t
Abend
|0|LANCX
s|de f||e
P08
FauIt AnaIyzer options:
DATASETS(DLANGX(.))
%erpo7a7
dala sel
|0|LANCX
2003 BM Corporation
November 4, 2003
!7od7ar
3ou7ce
L|nk Ed|t
00L
omp||er
For COBOL only
(not OS/VS COBOL
or COBOL )
Specify the TEST
compiler option
with SEPARATE
Save the
generated
SYSDEBUG file
in a PDS member
FA uses the
dataset name
stored in the load
module to locate
the side file
oad rodu|e
Fau|t
Ana|yzer
App||cat|on
FA |nvokat|on Ex|t
Abend
8Y80EUC
8|de F||e
P08
TE8T[. , . ,8EPARATE} comp||er opt|on
2003 BM Corporation
November 4, 2003
Options to write
info needed by FA
in the listing
#equired Compiler Options
f a compiler listing or DLANGX side file will be used, these
compiler options must be specified:
ASSEMBLER
O ESD
O LST or ADATA
C/C++
O AGGREGATE
O LST
O SOURCE
O XREF
COBOL
O LST
O MAP
O SOURCE
O XREF
PL/
O AGGREGATE
O ATTRBUTES
O ESD
O LST
O MAP
O SOURCE
O STMT
O XREF
Don't use
O OFFSET
O LONGNAME
%rese C opl|ors a7e N% reeded |l sou7ce |rlo |s
slo7ed |r a 3Y3& s|de l||e |rslead ol a ||sl|rd
%rese C opl|ors a7e N% reeded |l sou7ce |rlo |s
slo7ed |r a 3Y3& s|de l||e |rslead ol a ||sl|rd
2003 BM Corporation
November 4, 2003
COO Compile JC save isting
Store the listing in
a PDS or PDSE
a PDS or PDSE
Specify compiler
options needed by FA
Specify compiler
options needed by FA
Sample COBOL compile JCL to generate and save a compiler listing
Source Source
2003 BM Corporation
November 4, 2003
!I Compile JC save isting
a PDS or PDSE
a PDS or PDSE
Ensure that compiler options
needed by FA are all on
Ensure that compiler options
needed by FA are all on
Sample PL compile JCL to generate and save a compiler listing
Source Source
2003 BM Corporation
November 4, 2003
istings atasets
Store Listings in a PDS or PDSE dataset
COBOL SYSPRNT:
O RECFM=FBA
O LRECL=33
PL SYSPRNT:
O RECFM=VBA
O LRECL=25 minimum
Enterprise PL SYSPRNT:
O RECFM=VBA
O LRECL=37
Assembler
O SYSADATA:
RECFM=VB
LRECL=
2003 BM Corporation
November 4, 2003
COO Compile JC save SYSE&
The compiIer
"TEST" option
with SEPA#ATE is
specified
The compiIer
"TEST" option
with SEPA#ATE is
specified
The SYSP#NT
DD is the Iisting
The SYSP#NT
DD is the Iisting
The SYSDEB&G
DD is the side fiIe
The SYSDEB&G
DD is the side fiIe
n this example,
Source and
Symbolics data
are stored in the
side file
Sample COBOL compile JCL to generate and save a SYSDEBUG file
Source Source
2003 BM Corporation
November 4, 2003
COO Compiler SYSE& ataset
Contains Symbolics information generated by the
compiler
t is created only if TEST with SEPARATE option is
specified
t is saved as a PDS or PDSE member
O The member name is the same as program D
Format:
O Record format FB
O Logical record length between 0 and 024
2003 BM Corporation
November 4, 2003
ow FA locates SYSE& datasets
FA locates SYSDEBUG datasets differently than compiler
listings and DLANGX side files
The compiler stores the name of the SYSDEBUG dataset
in the load module
f the file is copied or renamed after the compile, FA will
not be able to locate it
Load L|brary
Load Hodu|e '8AH1'
'HY.L|8T[8AH1}'
'HY.L|8T'
member
'8AH1'
8Y80EUC P08
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
Fault Re-analysis
&sing Options
Hints & Tips
2003 BM Corporation
November 4, 2003
Fault Analyzer Options
System-wide options for your system are customized as part
of the Fault Analyzer installation process
O stored in PARMLB member DCNF00 by default
You can specify options to override the defaults:
O For a batch job step
O For online functions
To override Batch job step options:
O Specify in JCL
To override Online options:
O Specify from the OPTONS pull-down menu for
Batch Reanalysis
2003 BM Corporation
November 4, 2003
Te 'atasets Option
The DATASETS option specifies data sets that are to be
dynamically allocated by Fault Analyzer
t is most commonly used to specify the name of files where
program compiler listings are stored
2003 BM Corporation
November 4, 2003
Some oter useIul Fault Analyzer Options
#ETAND&MP
Fault Analyzer is to retain the SYSABEND
dump, SYSMDUMP, or SYSUDUMP
NCL&DE
Real-time analysis should be performed if an
abend occurs
EXCL&DE
Real-time analysis should not be performed if
an abend occurs
DETAL
The level of detail that should be included in
the report as either SHORT, MEDUM, or
LONG
P#EFE##EDFO#-
MATTNGWDTH
The report line width for flowing paragraph
text and hexadecimal storage formatting
Other parts of the report are not affected
MAXMND&MP-
PAGES
The maximum size of a minidump that will be
stored in a Fault History file
NOD&P
Controls if an entry for a duplicate abend is
captured in a Fault History File
2003 BM Corporation
November 4, 2003
ow to override Options atc Jobs
n most cases, no changes to run-time JCL are needed
f you have to make changes to many batch jobs,
discuss with your Systems Programmer to see if default
options or setup can be improved
To override default options, code an DOPTS DD
statement in the step
Refer to a file containing
options, or.
Refer to a file containing
options, or.
.code options
in-stream
.code options
in-stream
2003 BM Corporation
November 4, 2003
ow to override Options atc Jobs
Another way to override options is to preallocate files used
by Fault Analyzer with DD statements
O This has the same effect as specifying the DATASETS option
in DOPTS
Each DD statement must reference PDS or PDSE
dataset(s):
//IDIHIST DD . Fault History File
//IDILC DD . C compiler listings
//IDILCOB DD . COBOL compiler listings (not OS/VS)
//IDILCOBO DD . OS/VS COBOL compiler listings
//IDILPLI DD . PL/ compiler listings
//IDIADATA DD . Assembler SYSADATA
//IDILANGX DD . side files for all languages
f a job step does NOT abend, FA options are ignored
2003 BM Corporation
November 4, 2003
ow to override Options #eanalysis
Similar
process for
nteractive
vs Batch
reanalysis
settings are
remembered
for your
TSO D
Enter
a Select the Options menu
b Select Batch or
nteractive reanalysis
a Select the Options menu
b Select Batch or
nteractive reanalysis
enter
options.
enter
options.
.or refer to a
file containing
options
.or refer to a
file containing
options
2003 BM Corporation
November 4, 2003
Tip: &se a Iile Ior options
f you have a lot of options to specify, put them in a file
Point to the file:
O in a batch step, with an //IDIOPTS DD statement
O for an online function, from the options panel
2003 BM Corporation
November 4, 2003
Options and Exits Setup
n addition to the default options, other customization
is available
O These are typically set up by a Systems Programmer
Exit programs can be written to:
O Dynamically override options
For example, f your system has more than one Fault
History File, an exit is used to select one during Real-
Time analysis
O Control report formatting, message lookup, and
notification
User options module DCNFUM can be used to:
O Point to a non-parmlib default options file
O Specify unique defaults for different groups or
applications
2003 BM Corporation
November 4, 2003
Agenda
ntroduction
Fault Re-analysis
Using Options
Hints & Tips
2003 BM Corporation
November 4, 2003
y didnt Fault Analyzer Iind
my compiler listing ?
Add an DTRACE DD to your job to get trace information about
why a particular compiler listing or side file was selected or rejected
//IDITRACE DD SYSOUT=*
Sample output:
Listing/Side-file search trace for COBMST5
LE compile date 2002-2-7 time 6--0
DAWDBLANGX
Rejected - Member not found
Rejected - Member not found
PATRCKLSTNGCOBOL
Accepted - Timestamp valid, size test valid
- Timestamp date 2002-2-7 time 60
DALSTNGCOBOL
- Search not required LSTSEARCH(BEST) satisfied
- Search not required LSTSEARCH(BEST) satisfied
2003 BM Corporation
November 4, 2003
Make a copy oI your Fault Entry
Fault Entries will roll off of a Fault History file eventually
O You can keep a copy of a FauIt Entry in your own fiIe
First, allocate your own Fault History file
O Make it a PDS or PDSE, with the same attributes as the original Fault
History File (but probably a lot smaller!)
Method : just copy your Fault Entry from from the original Fault
History file to yours
O The Fault Entry is a PDS member, the member name is the Fault D
O Note: DO NOT delete or rename Fault Entries in the original file!
Method 2: use the DUTL utility to "import the entry
O This will also delete the entry from the original file
2003 BM Corporation
November 4, 2003
Take a 'snapsot Irom a program
DSNAP is a program supplied with Fault Analyzer
To use it, code a call to program DSNAP in your program
When DSNAP is called, FA collects info and stores a Fault Entry
O Apart from the way in which Fault Analyzer is invoked, there is
no difference between this type of analysis and any other real-
time analysis caused by an abend
After the snapshot is taken, control is restored to the calling
program
COBOL example
.
.
01 SNAP-PROGRAM PIC X(8) VALUE 'IDISNAP '.
PROCEDURE DIVISION.
.
.
CALL SNAP-PROGRAM.
.
.
2003 BM Corporation
November 4, 2003
&se 'IEs
to access Fault istory Files
f you have more than one Fault History File, "VEWs can be defined to
simplify access
A VEW can be:
O A shortcut to a Fault History File
O A concatenation of Fault History Files
Advantages:
O You don't have to know full names of the Fault History Files
O A view can concatenate multiple files, so you don't have to look in several files
one at a time
Access VEWs from the FLE->LST VEWS menu
Some example VEW names:
O PROD
O TEST
O CCS
O DEPT0
O ALL
VEWs can be set up by a Systems Programmer as part of FA installation
2003 BM Corporation
November 4, 2003
ook up Messages and Codes
on IMs 'OOKAT web site
www-ibmcom/servers/s390/os390/bkserv/lookat
Or wwwibmcom, and search for "LOOKAT
2003 BM Corporation
November 4, 2003
#eIerence
The User's Guide is available from the HELP menu from the
Fault Analyzer online screens
Fault Analyzer manuals are available on the web (see next
page)
Redbook: ntroduction to the BM Application Development Tools
on z/OS and OS/390
O http://www.redbooks.ibm.com/
and search for "AD Tools
O describes the BM Application Development Tools for z/OS and
OS/390 and includes scenarios that show how to use the tools to
recognize, locate, and fix errors in application programs
BM Fault Analyzer
BM File Manager
BM Debug Tool
BM Application Monitor
BM Workload Simulator
2003 BM Corporation
November 4, 2003
Fault Analyzer on te web
O http://wwwibmcom/software/awdtools
then click on BM Application Development Tools
O Browse / Download product manuals

Fault Analyser

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Fault Analyser

Diunggah oleh

Hak Cipta:

Format Tersedia

FauIt AnaIyzer Mentor Workshop zSeries AD Tools 1

Anda mungkin juga menyukai