Noticed the following in your D DIAG output:
0090  VSM TRACE GET(ON) FREE(ON)
0090    ASID(10-60)
0090    DATA(REGS)

If VOYAGER is not running in an address space with ASID in the range 10 through 60 you will not get any GFS trace information. Note that the ASIDs in this case are hexadecimal numbers.


--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507

On 2013-05-28 14:12, Scott Ford wrote:
DASDBILL2:

I was using :

gtfparm:  TRACE=SYSM,USRP,TRC,DSP,PCI,SRM

but when I start GTF look:

0290  T DIAG=04
0290  IEE252I MEMBER DIAG04   FOUND IN ADCD.Z113S.PARMLIB
0090  IEE536I DIAG     VALUE 04 NOW IN EFFECT
0290  D DIAG
0090  IGV007I 11.51.22 DIAG DISPLAY 750
0090  VSM TRACK CSA(ON) SQA(ON)
0090  VSM TRACE GET(ON) FREE(ON)
0090    ASID(10-60)
0090    DATA(REGS)
0090  VSM ALLOWUSERKEYCSA(NO)
0090  VSM BESTFITCSA(NO)
0090  VSM USEZOSV1R9RULES(YES)
0090  TRAPS NAME()
0090  CBLOC
0090    VIRTUAL24()
0090    VIRTUAL31()
0090  REUSASID(YES)

0290  S GTF
0281  $HASP100 GTF      ON STCINRDR
0290  IEF695I START GTF      WITH JOBNAME GTF      IS ASSIGNED TO USER START2
        , GROUP SYS1
0090  $HASP373 GTF      STARTED
0281  IEF403I GTF - STARTED - TIME=11.53.28
0090  AHL121I  TRACE OPTION INPUT INDICATED FROM MEMBER GTFPARM  OF PDS
       SYS1.PARMLIB
0090  TRACE=SYSM,USRP,TRC,DSP,PCI,SRM
       00050002
0090  AHL103I  TRACE OPTIONS SELECTED --SYSM,USR,TRC,DSP,PCI,SRM
0090 *62 AHL125A  RESPECIFY TRACE OPTIONS OR REPLY U
0290  R 62,TRACE=USRP
0090  IEE600I REPLY TO 62 IS;TRACE=USRP
0090  TRACE=USRP
0090 *63 AHL101A  SPECIFY TRACE EVENT KEYWORDS --USR=
0290  R 63,USR=(F65)
0090  IEE600I REPLY TO 63 IS;USR=(F65)
0090  USR=(F65)
0090 *64 AHL102A  CONTINUE TRACE DEFINITION OR REPLY END
0290  R 64,END
0090  IEE600I REPLY TO 64 IS;END
0090  END
0090  AHL103I  TRACE OPTIONS SELECTED --USR=(F65)
0090 *65 AHL125A  RESPECIFY TRACE OPTIONS OR REPLY U
0290  R 65,U
0090  IEE600I REPLY TO 65 IS;U
0090  U
0090  AHL906I THE OUTPUT BLOCK SIZE OF    27998 WILL BE USED FOR OUTPUT 800
0090          DATA SETS:
0090            SYS1.TRACE
0090  AHL080I GTF STORAGE USED FOR GTF DATA: 801
0090          GTFBLOCK STORAGE       82K BYTES (BLOK=        40K)
0090          PRIVATE STORAGE      1038K BYTES (SIZE=      1024K)
0090          SADMP HISTORY          54K BYTES (SADMP=       40K)
0090          SDUMP HISTORY           0K BYTES (SDUMP=        0K)
0090          ABEND DUMP DATA         0K BYTES (ABDUMP=       0K)
0090  AHL031I GTF INITIALIZATION COMPLETE
0290  S VOYAGER
0281  $HASP100 VOYAGER  ON STCINRDR
0290  IEF695I START VOYAGER  WITH JOBNAME VOYAGER  IS ASSIGNED TO USER START2
        , GROUP SYS1
0090  $HASP373 VOYAGER  STARTED
0281  IEF403I VOYAGER - STARTED - TIME=11.55.04
0090  IDMV000I - VOYAGER RECONCILATION  AGENT STARTING
0090  IDMV000I - VOYAGER IS EXECUTING  FROM AN APF AUTHORIZED LIBRARY
0090  IDMV000I - VOYAGER FOUND          RACF SECURITY SUBSYSTEM
0090  IDMV202E - VOYAGER NO STORAGE TOKEN     FOUND
0090  IDMV000I - VOYAGER SUBPOOL  INITIALIZATION OK
0090  IDMV003I - VOYAGER SP231  ALLOCATED OK
0090  IDMV001I - VOYAGER SUBPOOL  SIZE IS:     500 K
0090  IDMV002I - VOYAGER SUBPOOL  WILL HOLD :     5120 MESSAGES
0090  IDMV004I - VOYAGER STORAGE TOKEN BUILT OK
0090  IDMV152I - VOYAGER IP CONNECT REQUEST 71.81.28.57
0090  IDMV006I - VOYAGER BUILD          LEVEL IS AT        201305092141-5.0.0.
       0
0090  IDMV007I - ORACLE BUILD           LEVEL IS AT        09.00.04.22.F
0090  IDMV008I - VOYAGER SUBPOOL        100 BYTE VERSION
0090  IDMV009I - VOYAGER DETECTS       (TCPIP)JOBNAME      TCPIP
0090  IDMV010I - VOYAGER DETECTS       (TCPIP)IP ADDRESS   71.81.28.57
0090  IDMV011I - VOYAGER DETECTS       (TCPIP)IP PORT      5097
0090  IDMV019I - VOYAGER DETECTS        DEBUGGING IS       OFF
0090  IDMV020I - VOYAGER DETECTS        MVS RETCODES IS
0090  IDMV021I - VOYAGER DETECTS        COUNTRY CODE OF    US
0090  IDMV012I - VOYAGER DETECTS        ENCRYPTION IS      ON
0090  IDMV016I - VOYAGER COMPUTING      CACHE TIMER DELAY  SUCCESSFUL
0090  IDMV013I - VOYAGER DETECTS        CACHE DELAY SET TO 000 SECS
0090  IDMV014I - VOYAGER DETECTS        CACHE READ DELAY   000 SECS
0090  IDMV017I - VOYAGER DETECTS        ENCRYPTION KVER    200610261425
0090  IDMV024I - VOYAGER INITIALIZATION OF GET CLIENTID WAS SUCCESSFUL
0090  IDMV026I - VOYAGER INITIALIZATION OF PTON WAS SUCCESSFUL
0090  IDMV201I - VOYAGER CONNECTION TO GATEWAY FAILED

The sys1.trace has data and when I issue a gtftrace da('sys1.trace') usr(F65) 
heres the output:

  IPCS OUTPUT STREAM ------------------------------------------ Line 0 Cols 1 78
   ****************************** TOP OF DATA 
***********************************
      **** GTFTRACE DISPLAY OPTIONS IN EFFECT ****
    USR=SEL
   BLS18185I Dump directory describes some other trace
   AHL10009I No records of the requested type were found.
   ****************************** END OF DATA 
***********************************

I am lost here

Scott J Ford
Software Engineer
http://www.identityforge.com/



________________________________
  From: DASDBILL2 <dasdbi...@comcast.net>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, May 28, 2013 1:08 PM
Subject: Re: ECSA


Make sure that when you start your IPCS session that there is not already 
another system dump in IPCS's dump directory that it is browsing by default.  
You should list all the dump data sets in the dump directory and also check the 
data set name that IPCS is using as its current default.  I always look in the 
directory and delete all dumps in there, if any, before I start browsing a new 
dump data set.  I also try to remember to delete the dump data set that I 
browsed from the directory when I have finished browsing it, but I don't always 
remember, which is why I always display the directory before doing anything 
else after starting IPCS.


Bill Fairchild
Franklin, TN

“Political language is designed to make lies sound truthful and murder 
acceptable, and to give the appearance of solidity to pure wind.” [George 
Orwell]

----- Original Message -----
From: "Scott Ford" <scott_j_f...@yahoo.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, May 28, 2013 10:46:00 AM
Subject: Re: ECSA

Shmuel:

yes sir it was, there is data in 'sys1.trace' what I see is IPCS - subcommand 
GTFTRACE not recognizing or formatting if that's wthe workd you want to use the 
data ...its doesn't see the usr(F65)  and I think that is odd. I went right out 
of the MVS diag manual ....



Scott J Ford
Software Engineer
http://www.identityforge.com/



________________________________
  From: Shmuel Metz (Seymour J.) <shmuel+...@patriot.net>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Tuesday, May 28, 2013 10:46 AM
Subject: Re: ECSA


In <1369698915.60307.yahoomail...@web126201.mail.ne1.yahoo.com>, on
05/27/2013
    at 04:55 PM, Scott Ford <scott_j_f...@yahoo.com> said:

//IEFRDER DD
DSNAME=SYS1.TRACE,UNIT=SYSDA,SPACE=(CYL,20),             00150001
//             DISP=(NEW,KEEP)

Try DISP=(,CATLG)

10. I try IPCS with GTFTRACE da('sys1.trace') usr(f65)
       IPCS - gtf says no use able data for USR=SEL ...

Was IPCS looking at the same SYS1.TRACE?


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to