On Thu, 20 Sep 2012 09:56:51 -0400, Rob Schramm <[email protected]> wrote:
>If it is a certificate related issue.. you can run a GSKSRVR trace. It's a
>bit verbose... but gives you pretty specific information as to the real
>issue.
>These instructions were for CICS.. but it'll work for ftp just the same.
>
> - S GSKSRVR
> - Restart CICS.
> - Update GSKWTR PROC to add a dataset to hold the trace.
> - TRACE CT,WTRSTART=GSKWTR
> - TRACE CT,ON,COMP=GSKSRVR
> - R n,JOBNAME=(yyy),OPTIONS=(LEVEL=255),WTR=GSKWTR,END where yyy is the
> name of CICS.
> - Recreate the problem.
> - TRACE CT,OFF,COMP=GSKSRVR
> - TRACE CT,WTRSTOP=GSKWTR
OK, everything APPEARED to work, but the output trace dataset did not get
created. Here's what our GSKWTR proc looks like:
//GSKWTR PROC
//*-----------------------------------------------------------------*//
//* Component trace external writer for the System SSL started *//
//* task. Up to 16 trace datasets (TRCOUT01 - TRCOUT16) may *//
//* be specified. *//
//*-----------------------------------------------------------------*//
//IEFPROC EXEC PGM=ITTTRCWR,REGION=32M
//TRCOUT01 DD DSN=TECH.SYSSSL.CTRACE,DISP=(NEW,CATLG),
// SPACE=(CYL,(100)),UNIT=SYSDA
That's "as delivered by IBM" except for the output dataset name.
Now, for the JOBNAME in the WTOR I specified the batch job name that I
submitted. Should I specify FTPDn there instead? I.e., should I specify the
job name of the FTP Daemon? Seems counter-intuitive if true, since my batch
job is the client, not the server, in context.
-jc-
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
