Re: HOWTO Trace TSO/VTAM

--- In turnkey-mvs@..., "Mike Rayborn" <mrayborn <at> b...> wrote:
>Just in case anyone else is interested in traceing TSO/VTAM
>buffers.  How to trace TSO buffers
>0) Prereq: You'll need to apply the ZP60007 PTF before
>attempting to trace TSO/VTAM buffers. See
> http://www.prycroft6.com.au/vs2mods
> After that you'll need to add the following to
>SYS1.PARMLIB(TSOKEY00):
>CONFTXT=NO,          /* CONFIDENTIAL TEXT                */
>Shutdown MVS and reipl with CLPA option.
>1) Modify the GTF proc in SYS1.PROCLIB to create a
>cataloged dataset.  I recommend using DSN=HERC01.TRACE
>for the IEFRDER dataset.
>//GTF     PROC MEMBER=GTFPARM

   I assume that SYS1.PARMLIB(GTFPARM) has:
 TRACE=USR
 so you don't have to repeat it on the console.

    I call mine SYS1.PARMLIB(GTFVTAM) and have something
 else in my GTFPARM.

>//IEFPROC EXEC PGM=AHLGTF,PARM='MODE=EXT,DEBUG=NO,TIME=NO',  *
>// TIME=1440,REGION=2880K
>//IEFRDER DD   DSNAME=HERC01.TRACE,UNIT=SYSDA,SPACE=(4096,20),  *
>//             DISP=(NEW,CATLG)
>//SYSLIB  DD   DSNAME=SYS1.PARMLIB(&MEMBER),DISP=SHR

    I would suggest TIME=YES and TIME=1439 and more disk space.

    Here is another sample PROC:

//GTF     PROC MEMBER=GTFVTAM
//DELETE  EXEC PGM=IEFBR14
//DELETE   DD  DSN=SYS1.TRACE,DISP=(MOD,DELETE),UNIT=SYSDA,
//             SPACE=(TRK,0)
//IEFPROC EXEC PGM=AHLGTF,PARM='MODE=EXT,DEBUG=NO,TIME=YES',
//             REGION=2880K,DPRTY=(15,15),TIME=1439
//IEFRDER  DD  DSNAME=SYS1.TRACE,UNIT=SYSDA,
//             SPACE=(TRK,(750,750),RLSE),DISP=(NEW,CATLG)
//SYSLIB   DD  DSNAME=SYS1.PARMLIB(&MEMBER),DISP=SHR

    You could also add a print step to the PROC.
 Get real fancy and print to a Generation Data Set ( GDS ).

>2) At the console enter:
>S GTF.GTF
>R nn,TRACE=USR
>R nn,U
>3) Note the terminal at which you are signed on TSO,
>usually CUU0C0.
> At the console enter:
> F NET,TRACE,TYPE=BUF,ID=CUU0C0
>4) At the TSO terminal, do whatever you want traced.
> When done, return to the system console and enter:
> F NET,NOTRACE,TYPE=BUF,ID=CUU0C0
> P GTF.GTF
> 5) Submit the follow job to print the trace data.
> //PRTTRACE JOB
> //PRTTRACE EXEC PGM=AMDPRDMP
> //SYSPRINT DD SYSOUT=*
> //PRINTER  DD SYSOUT=*
> //TAPE     DD DISP=OLD,DSN=HERC01.TRACE  <== TRACE DATA
> //SYSIN    DD *
>   EDIT DDNAME=TAPE,USR=FEF

    My preference would be: USR=ALL

>   END
> /*
> //
>You'll only be able to see the first 179 bytes of the
>data stream but that's better than nothing.  If anyone
>knows how to increase this I'd like to hear about it.

     I mentioned that in a previous post.  GTF only
 traces a maximum of 255 bytes for user data.  To fix it,
 either use a small RU size like 200 ( or 160 ) or ZAP
 both TRACE to allow larger user trace data and VTAM to
 send more trace data.  ZAPping should be just disabling
 code both places.  i.e. Remove length check and remove
 length reduction.

> -- Mike

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/fXFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
turnkey-mvs-unsubscribe@...

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/