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 - get into IPCS - update *0 DEFAULTS - Specify default dump and options* with GSKWTR produced trace data set - *2 ANALYSIS - Analyze dump contents* - *7 TRACES - Trace formatting* - *1 CTRACE - Component trace* - *D DISPLAY - Specify parameters to display CTRACE entries* - update *component* with *GSKSRVR*, update *Report type* with *full*, and issue *"S"* to start the analysis Rob Schramm Senior Systems Consultant Imperium Group On Thu, Sep 20, 2012 at 8:43 AM, John Chase <[email protected]> wrote: > On Fri, 14 Sep 2012 17:08:04 -0700, Charles Mills <[email protected]> > wrote: > > >My bad -- DEBUG, not TRACE. > > > >Try > > > >DEBUG FLO > >DEBUG INT > >DEBUG ACC > >DEBUG SEC > > > >Charles > > > >-----Original Message----- > >From: IBM Mainframe Discussion List On Behalf Of John Chase > >Sent: Thursday, September 13, 2012 11:05 AM > > > >On Thu, 13 Sep 2012 06:44:53 -0700, Charles Mills <[email protected]> > wrote: > > > >>Turn on some FTP tracing. You can do it in FTP.DATA. Take a look at the > TRACE (?) statement in the CS configuration manuals and pick some plausible > options. > >> > >>Charles > > > >Not much new with TRACE in the FTP.DATA: > [ snip ] > > OK, the DEBUG options "write a book" now. :-) > > Our firewall guys tried a couple different things, and I guess we made > some "progress": Now the failure is "FC0994 authServer: secure_socket_init > failed with rc = 8 (Certificate validation error)". > > Time to call Shopz Support, since we're trying to use the certificate they > issued. The certificate works fine for RECEIVE ORDER over a non-SSL > connection. > > Thanks for all your help and suggestions. > > -jc- > > ---------------------------------------------------------------------- > 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
