I think you have to start the GSKSRVR first before starting the GSK writer. We had to do an SSL trace per IBM's request and the following was the process they gave to us. Note, this was for a CICS trace so your reply may be different.
1) Start the GSKSRVR started task: S GSKSRVR 2) Start the trace writer proc with the console command: TRACE CT,WTRSTART=GSKWTR 3) Start SSL CTRACE with the console command: TRACE CT,ON,COMP=GSKSRVR 4) Reply to the outstanding reply: (yourjob is the name of the CICS region to be traced) R xx,JOBNAME=(yourjob),OPTIONS=(LEVEL=255),WTR=GSKWTR,END 4a) D TRACE,COMP=GSKSRVR,SUB=(jobname) to verify trace is active 4b) Refresh the SSL environment using CEMT PERFORM SSL REBUILD 5) Establish a connection to CICS 6) Stop SSL CTRACE with the console command: TRACE CT,OFF,COMP=GSKSRVR 7) Stop the trace writer proc with the console command: TRACE CT,WTRSTOP=GSKWTR,FLUSH 8) Stop the GSKSRVR started task: P GSKSRVR -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Smith III, Phil (HPE Data Security (Voltage)) Sent: Friday, August 18, 2017 6:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: GSKSRVR trace Ok, I'm hopelessly ignorant about z/OS tracing, so please don't laugh (too hard). I'm trying to follow the instructions on https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gska100/sssl2dia1023728.htm to learn about SSL tracing. Yes, this is a test system. I copied the GSK.SGSKSAMP(GSKWTR) member to the PROCLIB and customized it: //GSKWTR PROC //IEFPROC EXEC PGM=ITTTRCWR,REGION=32M //TRCOUT01 DD DSN=PHS.GSK.TRACE1,DISP=(NEW,CATLG), // SPACE=(CYL,(10)),UNIT=SYSDA Then I issued: TRACE CT,WTRSTART=GSKWTR which got: ITT038I ALL OF THE TRANSACTIONS REQUESTED VIA THE TRACE CT COMMAND WERE SUCCESSFULLY EXECUTED. IEE839I ST=(ON,0001M,00004M) AS=ON BR=OFF EX=ON MO=OFF MT=(ON,064K) 451 ISSUE DISPLAY TRACE CMD FOR SYSTEM AND COMPONENT TRACE STATUS ISSUE DISPLAY TRACE,TT CMD FOR TRANSACTION TRACE STATUS IEF196I 1 //GSKWTR JOB MSGLEVEL=1 IEF196I 2 //STARTING EXEC GSKWTR IEF196I STMT NO. MESSAGE IEF196I 2 IEFC001I PROCEDURE GSKWTR WAS EXPANDED USING SYSTEM IEF196I LIBRARY VENDOR.PROCLIB IEF196I 3 XXGSKWTR PROC IEF196I 4 XXIEFPROC EXEC PGM=ITTTRCWR,REGION=32M IEF196I 5 XXTRCOUT01 DD DSN=PHS.GSK.TRACE1,DISP=(NEW,CATLG), IEF196I XX SPACE=(CYL,(10)),UNIT=SYSDA IEF196I IEF236I ALLOC. FOR GSKWTR GSKWTR IEF196I IGD100I 0D39 ALLOCATED TO DDNAME TRCOUT01 DATACLAS ( ) IEF196I AHL906I THE OUTPUT BLOCK SIZE OF 27998 WILL BE USED FOR IEF196I OUTPUT IEF196I DATA SETS: IEF196I PHS.GSK.TRACE1 AHL906I THE OUTPUT BLOCK SIZE OF 27998 WILL BE USED FOR OUTPUT 463 DATA SETS: PHS.GSK.TRACE1 ITT110I INITIALIZATION OF CTRACE WRITER GSKWTR COMPLETE. So far so good. Then I issue: TRACE CT,ON,COMP=GSKSRVR and I get: ITT001I TRACE COMP=GSKSRVR 472 IS NOT DEFINED. ITT038I NONE OF THE TRANSACTIONS REQUESTED VIA THE TRACE CT COMMAND WERE SUCCESSFULLY EXECUTED. IEE839I ST=(ON,0001M,00004M) AS=ON BR=OFF EX=ON MO=OFF MT=(ON,064K) 474 ISSUE DISPLAY TRACE CMD FOR SYSTEM AND COMPONENT TRACE STATUS ISSUE DISPLAY TRACE,TT CMD FOR TRANSACTION TRACE STATUS OK, I'm missing something basic (and probably obvious). Any idea what? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN