z/OS trace processing data
This appendix contains trace processing data information and information related to z/OS trace capabilities.
The trace output data sets must be specific to each instance of GTF and can be defined in the cataloged procedure. Each instance of GTF to be started must have a separate cataloged procedure, or if the same cataloged procedure is used, then a different trace data set must be supplied with the GTF START command.
C.1 GFS trace information
GFS trace is a diagnostic tool that collects information about the use of the GETMAIN, FREEMAIN, or STORAGE macro. You can use GFS trace to analyze the allocation of virtual storage and identify users of large amounts of virtual storage.
You must use the generalized trace facility (GTF) to get the GFS trace data output.
C.1.1 DIAGxx parmlib member syntax
When creating a DIAGxx parmlib member, enter data only in columns 1 through 71. Do not enter data in columns 72 through 80; the system ignores these columns.
If the system finds a syntax error in DIAGxx, it issues an error message, and then attempts to continue processing the next keyword.
The syntax for the DIAGxx parmlib member is as follows:
[VSM TRACE ]
[ {GETFREE(ON)|GET(ON|OFF) FREE(ON|OFF) } ]
[ [ASID({asid1|asid1-asidx}[,{asid2|asid2-asidx}]...)] ]
[ [DATA(data1[,data2]...) ]
[ [KEY({key1|key1-keyx}[,{key2|key2-keyx}]...)] ]
[ [LENGTH({len1|len1-lenx}[,{len2|len2-lenx}]...)] ]
[ [SUBPOOL({sub1|sub1-subx}[,{sub2|sub2-subx}]...)] ]
[ [JOBNAME([job1,job2...]) ]
[ [ADDRESS([addr1|addr1-addrx][,addr2-|addr2-addrx..)] ]
[ [LOCREAL(loc1[,loc2]...) ]
[ {GETFREE (OFF) } ]
[VSM TRACK ]
[ {CSA (ON|OFF) } ]
[ {SQA (ON|OFF) } ]
[ {CSA (ON|OFF) SQA (ON|OFF) } ]
[VSM CHECKREGIONLOSS(bbb{K|M},aaa{K|M}) ]
C.1.2 GFS trace data
When GTF writes trace data in a data set, format and print the trace data with the IPCS GTFTRACE subcommand.
When GTF writes trace data only in the GTF address space, use a dump to see the data. Request the GTF trace data in the dump through the SDATA=TRT dump option.
Issue the IPCS GTFTRACE subcommand to format and see the trace in an unformatted dump. An example of formatted GETMAIN/FREEMAIN (GFS) trace data, which is output from IPCS in GTFTRACE format, is shown in Figure C-1 on page 363.
IPCS
GTFTRACE DA(‘MY.GTF.TRACE’) USR(F65)
IKJ56650I TIME-03:42:20 PM. CPU-00:00:01 SERVICE-52291 SESSION-00:00:20
BLS18122I Initialization in progress for DSNAME(¢ MY.GTF.TRACE¢ )
IKJ56650I TIME-03:42:21 PM. CPU-00:00:01 SERVICE-54062 SESSION-00:00:20
**** GTFTRACE DISPLAY OPTIONS IN EFFECT ****
USR=SEL
 
**** GTF DATA COLLECTION OPTIONS IN EFFECT: ****
USRP option
 
**** GTF TRACING ENVIRONMENT ****
Release: SP6.0.6 FMID: HBB6606 System name: CMN
CPU Model: 9672 Version: FF Serial no. 270067
 
USRDA F65 ASCB 00FA0800 JOBN MYGTF2
Getmain SVC(120) Cond=Yes
Loc=(Below,Below) Bndry=Dblwd
Return address=849CA064 Asid=001A Jobname=MYGTF2
Subpool=229 Key=0 Asid=001A Jobname=MYGTF2 TCB=008DCA70 Retcode=0
Storage address=008D6768 Length=10392 X¢2898¢
GPR Values
0-3 00002898 00000000 7FFFC918 0B601E88
4-7 01FE3240 008FF830 849CA000 00FA0800
8-11 00000000 00000DE8 049CBFFE 849CA000
12-15 049CAFFF 0B601A9C 00FE9500 0000E510
GMT-01/06/1998 21:15:43.111628 LOC-01/06/1998 21:15:43.1
 
USRDA F65 ASCB 00FA0800 JOBN MYGTF2
Freemain SVC(120) Cond=No
Return address=8B2D608A Asid=001A Jobname=MYGTF2
Subpool=230 Key=0 Asid=001A Jobname=MYGTF2 TCB=008DCA70 Retcode=0
Storage address=7F73DFF8 Length=8 X¢ 8 ¢
GPR Values
0-3 00000000 7F73DFF8 008D82D8 008D7BC0
4-7 008D8958 008D6B08 008D85C8 0B335000
8-11 00000002 00000000 7F73DFF8 008D862C
12-15 8B2D6044 008D8C98 849D242A 0000E603
GMT-01/06/1998 21:15:43.111984 LOC-01/06/1998 21:15:43.1
Figure C-1 Output from IPCS GTFTRACE
C.1.3 IPCS MVS dump component data analysis panel
This panel is displayed by entering Option 2.6 on the IPCS primary option menu panel. You then see displayed the Dump Component Data Analysis panel, bypassing the Analysis of Dump Contents Menu panel. The panel is shown in Figure C-2 on page 364.
To display information, specify “S option name” or enter S to the left of the option desired. Enter a ? to the left of an option to display help regarding the component support.
S Name Abstract
------------------------------------------------
_ IMSDUMP IMS analysis
_ IOSCHECK Active input/output requests
_ IPCSDATA IPCS control data
_ IPHDR TCP/IP IP Header Formatter
_ IRLM IMS Resource Lock Manager analysis
_ JESXCF JESXCF Address Space Analysis
_ JES2 JES2 analysis
_ JES3 JES3 analysis
_ LEDATA Language Environment formatter
_ LISTEDT Format eligible device table
_ LLATRACE Library Lookaside trace
_ LOGDATA LOGREC formatter
_ LOGGER System logger formatter
_ LPAMAP Map link pack area
_ MERGE Merge GTF/CTRACE output
_ MMSDATA MMS control block analysis
_ MTRACE Master TRACE formatter
_ NUCMAP Nucleus CSECT Map
_ OAMDATA OAM Control Block Analysis
_ OMVSDATA OpenMVS analysis
_ RESOLVER TCP/IP Resolver Analysis
_ RMMDATA RMM Control Block Analysis
_ RMMPDA RMM PDA Trace Analysis
_ RSMDATA Real storage manager summary
_ SADMPMSG Format SADMP console messages
_ SKMSG TCP/IP Streams Message Formatter
_ SMSDATA SMS control block analysis
_ SMSXDATA SMSX Control Block Formatter
_ SRMDATA SRM control block analysis
_ SSIDATA Subsystem Interface analysis
_ STRDATA Coupling Facility Structure Data
_ SUMDUMP Format summary dump data
_ SYMDEF Static Symbol Table Formatter
_ SYMPTOMS Format symptoms
_ SYSTRACE Format system trace
_ TCAMMAP TCAM control block analysis
_ TCPHDR TCP/IP TCP Header Formatter
_ TCPIPCS TCP/IP Analysis
_ TSODATA TSO analysis
_ UDPHDR TCP/IP UDP Header Formatter
_ VLFDATA Virtual Lookaside Facility data
_ VLFTRACE Virtual Lookaside Facility trace
_ VSMDATA VSM control block analysis
_ VTAMMAP VTAM control block analysis
_ XESDATA XES analysis
Figure C-2 Dump Component Data Analysis panel
C.1.4 SUMMARY subcommand parameters
Use the SUMMARY subcommand, shown in Figure C-3 on page 365, to display or print dump data associated with one or more specified address spaces.
SUMMARY produces different diagnostic reports depending on the report type parameter, FORMAT, KEYFIELD, JOBSUMMARY, and TCBSUMMARY, and the address space selection parameters, ALL, CURRENT, ERROR, TCBERROR, ASIDLIST, and JOBLIST. Specify different parameters to selectively display the information you want to see.
{ SUMMARY }
{ SUMM }
-------- Report Type Parameters ----------------------------
[ KEYFIELD [REGISTERS | NOREGISTERS] ]
[ FORMAT ]
[ TCBSUMMARY ]
[ JOBSUMMARY ]
-------- Address Space Selection Parameters ----------------
[ ALL ]
[ CURRENT ]
[ ERROR ]
[ TCBERROR | ANOMALY ]
[ ASIDLIST(asidlist) ]
[ JOBLIST(joblist) | JOBNAME(joblist) ]
-------- SETDEF-Defined Parameters -------------------------
 [ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ FLAG(severity) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
Figure C-3 SUMMARY command parameters
C.1.5 VERBEXIT subcommand
Use the VERBEXIT subcommand, shown in Figure C-4 on page 366, to run an installation-supplied or IBM-supplied verb exit routine.
{ VERBEXIT } { pgmname }
{ VERBX } { verbname }
[ 'parameter [,parameter]...' ]
[ AMASK(mask) ]
[ SYNTAX | NOSYNTAX ]
              [ TOC | NOTOC ]
-------- SETDEF-Defined Parameters -------------------------
              [ ACTIVE | MAIN | STORAGE ]
[ DSNAME(dsname) | DATASET(dsname) ]
[ FILE(ddname) | DDNAME(ddname) ]
[ PATH(path-name) ]
[ PRINT | NOPRINT ]
[ TERMINAL | NOTERMINAL ]
[ TEST | NOTEST ]
Figure C-4 VERBEXIT subcommand parameters
C.1.6 VERBX VSMDATA subcommand
Specify the VSMDATA verb name and optional parameters on the VERBEXIT subcommand, shown in Figure C-5, to format diagnostic data from virtual storage management (VSM).
VERBEXIT VSMDATA [ 'parameter [,parameter]...' ]
The parameters are:
[CONTROLBLOCKS] [ALL] [DETAIL]
[SUMMARY]
[CURRENT]
[ERROR]
[TCBERROR]
[NOASIDS]
[ASIDLIST(asidlist)]
[JOBNAME(joblist) | JOBLIST(joblist)]
[GLOBAL|NOGLOBAL]
[OWNCOMM [([CSA] [SQA])]
[SUMMARY ]
[DETAIL ]
[ALL]
[ASIDLIST(asidlist)]
[SYSTEM]
[SORTBY(ASIDADDR|ASIDLEN|ADDRESS|TIME|LENGTH)]
[CONTENTS(YES|NO)]
Figure C-5 VERBX VSMDATA subcommand parameters
C.1.7 STATUS FAILDATA subcommand
* * * DIAGNOSTIC DATA REPORT * * *
SEARCH ARGUMENT ABSTRACT
PIDS/5752SC1B6 RIDS/IEFSD060#L RIDS/IEFSD060 AB/S023E PRCS/00000008 REGS/0E0
REGS/06110 RIDS/IEFIB620#R
Symptom Description
------- -----------
PIDS/5752SC1B6 Program id: 5752SC1B6
RIDS/IEFSD060#L Load module name: IEFSD060
RIDS/IEFSD060 Csect name: IEFSD060
AB/S023E System abend code: 023E
PRCS/00000008 Abend reason code: 00000008
REGS/0E018 Register/PSW difference for R0E: 018
REGS/06110 Register/PSW difference for R06: 110
RIDS/IEFIB620#R Recovery routine csect name: IEFIB620
OTHER SERVICEABILITY INFORMATION
Recovery Routine Label: IEFIB620
Date Assembled: 04328
Module Level: HBB7720
Subfunction: INITIATOR JOB PROCESS
Time of Error Information
PSW: 070C1000 81329D48 Instruction length: 02 Interrupt code: 000D
Failing instruction text: 00181610 0A0D50E0 D0049180
Registers 0-7
GR: 84000000 8423E000 7FFEFF0C 007FF3D0 007FF448 00000BE0 81329C38 007C9E1C
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Registers 8-15
GR: 00000000 0167BFA0 7F775A68 00000B80 00000BD8 007FDB28 81329D30 00000008
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000C05
Home ASID: 008A Primary ASID: 008A Secondary ASID: 008A
PKM: 8040 AX: 0000 EAX: 0000
RTM was entered because an SVC was issued in an improper mode.
The error occurred while a locked or disabled routine was in control.
No locks were held.
No super bits were set.
STATUS FROM THE RB WHICH ESTABLISHED THE ESTAE EXIT
PSW: 070C3000 840F55D8 Instruction length: 02 Interrupt code: 003E
Registers 0-7
GR: 840F48A2 007F0B18 00000020 007FF708 007CA9B0 007FF448 007F0DC4 007EAEC1
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Registers 8-15
GR: 007F0B18 840F5372 00FC0200 007FF448 840F48A2 007CAA18 840F55C0 00000000
AR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000C05
Figure C-6 Output from a STATUS FAILDATA subcommand
RECOVERY ENVIRONMENT
Recovery routine type: ESTAE recovery routine
Recovery routine entry point: 040EC0F0
The RB associated with this exit was not in control at the time of error.
User requested no I/O processing.
VARIABLE RECORDING AREA (SDWAVRA)
+000 Key: 22 Length: 14
+002 C9D5C9E3 C9C1E3D6 D940C6D6 D6E3D7D9 |INITIATOR FOOTPR|
+012 C9D5E3E2 |INTS |
+016 Key: 23 Length: 50
+018 C9D5C9E3 C6D7D5E3 80BF00C0 00CCE3F0 |INITFPNT...{..T0|
+028 E0000EEC 80000080 C000F0C0 EE3FC000 |.......{.0{..{.|
+038 00000000 E63C0300 000000E0 E068009F |....W......\...|
+048 EFFE8000 00A0B87F E3003C00 0017FFFF |......."T.......|
+058 80000000 FFE0A000 00000000 00000000 |...............|
+068 Key: 50 Length: 02
+06A 0023 |.. |
+06C Key: 53 Length: 00
IEA24013I FORMATTING COMPLETED SUCCESSFULLY.
Figure C-7 Completion of STATUS FAILDATA output
 
 
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.143.5.15