Guys:
I need some help I want to do a GFS trace on our 1.13 system and have done the
following:
1. Build a DIAGxx member , it is below:
BROWSE ADCD.Z113S.PARMLIB(DIAG04) - 01.08 Line 00000018 Col 001 080
/* To use this member specify DIAG=00 in SYS1.PARMLIB(IEASYSxx), */ 00900000
/* or in response to the message that says "Specify System */ 00950000
/* Parameters", or enter the operator command "SET DIAG=00". */ 01000000
/* */ 01050000
/* change-activity = */ 01100000
/* $L0=DKB0029 ,HBB4430,920212,PDF5: Add defaults for */ 01150000
/* CSA tracking and GFS trace. */ 01200000
/* $P1=PWY0499 ,HBB6609,990528,PDXB: CS tracking defaults to ON */ 01225000
/* */ 01250000
/********************************************************************/ 01300000
VSM TRACK CSA(ON) SQA(ON) 01350000
VSM TRACE GETFREE(ON) 01400002
JOBNAME(VOYAGER) 01410008
DATA(ALL) 01440004
******************************** Bottom of Data ********************************
2. Here is my GTF proc and member
//GTFNEW PROC MEMBER=GTFPARM
00050005
//IEFPROC EXEC PGM=AHLGTF,REGION=32M, 00083301
// PARM='MODE=EXT,DEBUG=NO,TIME=YES,BLOK=40K,SD=0K,SA=40K' 00083401
//IEFRDER DD DSNAME=SYS1.TRACE,UNIT=SYSDA,SPACE=(CYL,20), 00150001
// DISP=(NEW,KEEP) 00200004
//SYSLIB DD DSNAME=SYS1.PARMLIB(&MEMBER),DISP=SHR 00210006
TRACE=SYSM,USRP,TRC,DSP,PCI,SRM
3. I activate DIAG04 from STEP #1 ,,,,'T DIAG=04'
4. S GTF
5. enter 'U'
6. Start my STC called Voyager..
7. P xxx (gtf)
8. T DIAG=05 (our normal diag member)
9. there is data in sys1.trace
10. I try IPCS with GTFTRACE da('sys1.trace') usr(f65)
IPCS - gtf says no use able data for USR=SEL ...
11. I tried GTF with TRACE=USRP, USR=(F65)
12. No matter what I try I seem to receive no usable trace output ...
What did I goof on guys and gals...
Regards,
Scott J Ford
Software Engineer
http://www.identityforge.com/
________________________________
From: Scott Ford <[email protected]>
To: [email protected]
Sent: Monday, May 27, 2013 11:36 AM
Subject: Re: ECSA
Yeah, I have too look at what has happened ....their trace was unreadable so I
will try the same code on our test system with a gfs trace ..I just want to
solve the mystery and make sure we don't have an issue
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite means'
On May 27, 2013, at 10:23 AM, "Shmuel Metz (Seymour J.)"
<[email protected]> wrote:
> In <[email protected]>, on 05/26/2013
> at 06:08 PM, Charles Mills <[email protected]> said:
>
>>> you need to save the key prior to the MODESET KEY=ZERO invocations
>
>> Are you sure?
>
> Yes.
>
>> MODESET KEY=NZERO,... won't "remember" for you?
>
> The crystal ball on channel 3 is broken. From z/OS MVS Programming:
> Authorized Assembler Services Reference, Volume 3 (LLA-SDU).
> SA22-7611-11:
>
> KEY=NZERO
> Specifies that the PSW key (bits 8-11) is to be either set to
> zero
> (ZERO) or set to the value in the caller's TCB (NZERO).
>
> If the code switches among multiple keys, MODESET has no information
> on the preceding key. Now, there are options in the inline form to
> save and restore, but Scott is using the SVC form.
>
> --
> Shmuel (Seymour J.) Metz, SysProg and JOAT
> Atid/2 <http://patriot.net/~shmuel>
> We don't care. We don't have to care, we're Congress.
> (S877: The Shut up and Eat Your spam act of 2003)
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
