[hercules-390] Problem reading GTF trace output

[[e-mail] [hercules-390]]

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


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:


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:


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:


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 ?

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

The Hercules-390 emulator has several different focused (specialized) support forums:

https://fish-git.github.io/html/hercsupp.html


This is the Hercules emulator support forum. It is *not* an MVS or z/OS support forum. The Hercules-390 support forum is for help with hercules-390 emulator issues, *not* for help with the operating system you happen to be running on it.

Your question (request for help) might be better served if you would post it to the correct forum. (e.g. H390-MVS perhaps?)

[Tony Harminc [e-mail] [hercules-390]]

On 15 March 2017 at 11:21, ''Fish' (David B. Trout)'

Post by '\'Fish\' (David B. Trout)' ***@gmail.com [hercules-390]
Your question (request for help) might be better served if you would post it to the correct forum. (e.g. H390-MVS perhaps?)

Or to IBM-MAIN, since it seems to have nothing to do with Hercules or MVS/370.

Tony H.

[[e-mail] [hercules-390]]

If you are certain this error has nothing to do with the emulator then I will post the question elsewhere. Thanks.

['\'Fish\' (David B. Trout)' [e-mail] [hercules-390]]

Post by ***@yahoo.com [hercules-390]
If you are certain this error has nothing to do with the
emulator then I will post the question
elsewhere. Thanks.

Do you have reason to suspect it is the emulator that is causing the problem? (whatever that problem is)

If you do, then please state what that reason is and please provide the evidence and we will certainly look into the problem.