Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Problem reading GTF trace output

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging
View previous topic :: :: View next topic  
Author Message
danik56

New User


Joined: 08 Mar 2017
Posts: 13
Location: Israel

PostPosted: Thu Mar 16, 2017 1:02 pm    Post subject: Problem reading GTF trace output
Reply with quote

I have activated GTF trace to capture RACF trace for RACROUTE calls.
Here is the syslog output:

Code:
08.38.28           START GTFRACF.GTF,,,NOPROMPT                     
08.38.29 STC00107  $HASP373 GTFRACF  STARTED                         
08.38.39 STC00107  AHL121I  TRACE OPTION INPUT INDICATED FROM MEMBER
 GTFPRM#O OF PDS SYS1.PARMLIB                                       
08.38.39 STC00107  TRACE=USRP                                       
                  00010000                                           
08.38.39 STC00107  USR=(F44),END                                     
                  00020000                                           
08.38.39 STC00107  AHL103I  TRACE OPTIONS SELECTED --USR=(F44)       
08.38.39 STC00107  AHL080I GTF STORAGE USED FOR GTF DATA:           
        GTFBLOCK STORAGE       68K BYTES (BLOK=        40K)         
        PRIVATE STORAGE      1031K BYTES (SIZE=      1024K)         
        SADMP HISTORY          45K BYTES (SADMP=       40K)         
        SDUMP HISTORY          45K BYTES (SDUMP=       40K)         
        ABEND DUMP DATA         0K BYTES (ABDUMP=       0K)         
08.38.39 STC00107  AHL031I GTF INITIALIZATION COMPLETE               
08.38.59           #SET TRACE(RACROUTE(TYPE(5)) JOBNAME(DANI))       
08.38.59 STC00025  IRRH004I (#) RACF SUBSYSTEM SET COMMAND HAS COMPLE
 SUCCESSFULLY.                                                       
08.39.18 TSU00108  $HASP373 DANI     STARTED                         
08.39.37           stop gtf                                         
08.39.37 STC00107  AHL006I GTF ACKNOWLEDGES STOP COMMAND             
08.39.37 STC00107  AHL904I THE FOLLOWING TRACE DATASETS CONTAIN TRACE
 DATA :                                                             
          SYS1.TRACE                                                 
08.39.38 STC00107  IEF404I GTFRACF - ENDED - TIME=08.39.38


When I try to format the trace in IPCS the following error is received:

Code:
BLS21082I DSNAME('SYS1.TRACE')    I/O error                     
BLS21081I 0AB1,D,SYS00010,READ,OUT OF EXTENT,TTR UNKNOWN,BSAM   
AHL10004I Input is not a GTF trace dataset.                     
AHL10009I No records of the requested type were found.


In TSO the dataset looks like this:

Code:
Data Set Name . . . . : SYS1.TRACE                                       
                                                                         
General Data                           Current Allocation               
 Management class . . : **None**        Allocated tracks  . : 100       
 Storage class  . . . : **None**        Allocated extents . : 1         
  Volume serial . . . : USR002                                           
  Device type . . . . : 3390                                             
 Data class . . . . . : **None**       Current Utilization               
  Organization  . . . : PS              Used tracks . . . . : 1         
  Record format . . . : VB              Used extents  . . . : 1         
  Record length . . . : 23472                                           
  Block size  . . . . : 23476                                           
  1st extent tracks . : 100                                             
  Secondary tracks  . : 0                                               
  Data set name type  :                 SMS Compressible  :   NO         
                                                                         
  Creation date . . . : 2017/03/15      Referenced date . . : 2017/03/15
  Expiration date . . : ***None***                                       



and I can browse the contents:

Code:
 BROWSE    SYS1.TRACE                                 Line 00
 Command ===>                                               
********************************* Top of Data ***************
.....KK.7zÞ- .........GTS .. .SP7.1.0 HBB7750 ADCD    ..y¤.dØ
.ïK.7­à.&.Õà.Üï.DANI    ....RTRACE  RACFPRE .................
.ïK.7­àÎ^.Õà.Üï.DANI    ....RTRACE  RACFPOST.................
.ïK.7óá©..Õà.Üï.DANI    ....RTRACE  RACFPRE .................
.ïK.7óåÓ\.Õà.Üï.DANI    ....RTRACE  RACFPOST.................
.ïK.7óy...Õà.Üï.DANI    ....RTRACE  RACFPRE .................
.ïK.7óyð°.Õà.Üï.DANI    ....RTRACE  RACFPOST.................
.ïK.7ó©Ü..Õà.Üï.DANI    ....RTRACE  RACFPRE .................
.ïK.7ó§.^.Õà.Üï.DANI    ....RTRACE  RACFPOST.................
******************************** Bottom of Data *************


Can anyone suggest what is causing the problem in IPCS ?

Thanks....Dani

Coded
Back to top
View user's profile Send private message

Willy Jensen

Active User


Joined: 01 Sep 2015
Posts: 128
Location: Switzerland

PostPosted: Thu Mar 16, 2017 2:30 pm    Post subject:
Reply with quote

Maybe if you showed us your job.
This link might help: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ichb200/tcs.htm
Back to top
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 13
Location: Israel

PostPosted: Thu Mar 16, 2017 3:53 pm    Post subject:
Reply with quote

Willy Jensen wrote:
Maybe if you showed us your job.
This link might help: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ichb200/tcs.htm


What job ? the GTF capture job ?
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8086
Location: East Dubuque, Illinois, USA

PostPosted: Thu Mar 16, 2017 5:01 pm    Post subject: Reply to: Problem reading GTF trace output
Reply with quote

In order for IPCS to do anything with the data set, it MUST be defined as RECFM=F,LRECL=4160 or RECFM=FB,LRECL=4160 (although FBS is also allowed, but rarely seen) -- VB,23472,23476 will not allow IPCS to process the GTF trace (or any dump, for that matter).
Back to top
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 13
Location: Israel

PostPosted: Thu Mar 16, 2017 5:39 pm    Post subject:
Reply with quote

I need to figure out why GTF allocates the file as VB although the DCB in JCL say RECFM=FB.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8086
Location: East Dubuque, Illinois, USA

PostPosted: Thu Mar 16, 2017 6:30 pm    Post subject:
Reply with quote

Quote:
I need to figure out why GTF allocates the file as VB although the DCB in JCL say RECFM=FB.
I'd look at your ACS routines first.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 523
Location: The Universe

PostPosted: Thu Mar 16, 2017 8:13 pm    Post subject:
Reply with quote

danik56 wrote:
I need to figure out why GTF allocates the file as VB although the DCB in JCL say RECFM=FB.
My guess is the DCB macro within GTF overrode the RECFM=FB in the JCL. This is discussed in JCL reference, and elsewhere.

In terms of personal involvement the last time I used GTF was sometime in the 1980s when I did a CCW trace. I have no memory of what the DCB attributes of the data set were, nor do I recall how I analyzed the data set.

Mr. Sample's statement that RECFM=FBS is rarely seen I do not believe is correct. In my personal involvement it is by far the most common. It appears this is the default when SYSMDUMP is used. I use SYSMDUMP quite a lot in preference to paper SYSUDUMP / SYSABEND dumps as IPCS is far more usable than trying to analyze paper dumps through SDSF.

As a test, I ran this -
Code:
//A       EXEC PGM=IEFBR14
//DUMP     DD  DISP=(MOD,DELETE),UNIT=SYSDA,SPACE=(TRK,0),
//             DSN=&SYSUID..TESTIPCS.DUMP
//B       EXEC PGM=ASMA90,PARM='OBJECT,NODECK'
//SYSPRINT DD  SYSOUT=*
//SYSLIB   DD  DISP=SHR,DSN=SYS1.MACLIB
//SYSLIN   DD  DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(1,1)),
//             DCB=(RECFM=FB,LRECL=80,DSORG=PS)
//SYSIN    DD  *
XOC1     CSECT
         DC    H'0'
         END   X0C1
//C       EXEC PGM=IEWL
//SYSPRINT DD  SYSOUT=*
//SYSLMOD  DD  DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(1,1,1)),DSN=&&G(G)
//SYSLIN   DD  DISP=OLD,DSN=*.B.SYSLIN
//D       EXEC PGM=*.C.SYSLMOD
//SYSMDUMP DD  DISP=(,DELETE,CATLG),UNIT=SYSDA,SPACE=(CYL,(50,20)),
//             DSN=*.A.DUMP
In this example, the TESTIPCS.DUMP data set used 249 tracks with DCB=(RECFM=FBS,LRECL=4160,BLKSIZE=24960). At first glance this DCB looks pretty sad, but you're not going to do any better. Still, it's better than RECFM=FS, LRECL=4160, BLKSIZE=4160.
Back to top
View user's profile Send private message
danik56

New User


Joined: 08 Mar 2017
Posts: 13
Location: Israel

PostPosted: Thu Mar 16, 2017 9:26 pm    Post subject:
Reply with quote

After issuing the following command in IPCS:

DROPD DA('SYS1.TRACE')

Followed by:

GTFTRACE DSNAME('SYS1.TRACE') USR

The trace dataset was read without error despite RECFM=VB:

**** GTFTRACE DISPLAY OPTIONS IN EFFECT ****
USR=ALL

**** GTF DATA COLLECTION OPTIONS IN EFFECT: ****
USRP option

**** GTF TRACING ENVIRONMENT ****
Release: SP7.1.0 FMID: HBB7750 System name: ADCD
CPU Model: 2084 Version: 00 Serial no. 01A89F


USR57 F44 ASCB 00FC5700 JOBN DANI


Following is a formatted R_TRACE record.
This trace record was generated by IRRTRC00 with IDENT(R_TRACE).

Here is the current format of the trace file:

Data Set Name . . . . : SYS1.TRACE

General Data Current Allocation
Management class . . : **None** Allocated tracks . : 100
Storage class . . . : **None** Allocated extents . : 1
Volume serial . . . : USR002
Device type . . . . : 3390
Data class . . . . . : **None** Current Utilization
Organization . . . : PS Used tracks . . . . : 1
Record format . . . : VB Used extents . . . : 1
Record length . . . : 4156
Block size . . . . : 4160
1st extent tracks . : 100
Secondary tracks . : 0
Data set name type : SMS Compressible : NO

Creation date . . . : 2017/03/16 Referenced date . . : 2017/03/16
Expiration date . . : ***None***
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Trace in CLIST PANEL cvnlynn CLIST & REXX 0 Thu Jun 22, 2017 11:06 pm
No new posts Dynamic output file creation in cobol... smileheal COBOL Programming 7 Thu Jun 15, 2017 10:53 pm
No new posts getting three output files out of JOI... migusd SYNCSORT 4 Mon Jun 05, 2017 11:30 pm
No new posts find RACF group for access to spooled... jzhardy JCL & VSAM 1 Mon May 08, 2017 11:46 am
No new posts Need help in reading and validating a... ABINAYATHULASI COBOL Programming 8 Tue Apr 18, 2017 11:42 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us