Hal Merritt wrote: > Ok, I have slogged through the FM and followed the instructions. The > trace file is empty. > > My guess is that I guessed wrong on the job name. I traced TCPIP. Any > clues? > > By the way: thanks to the other posters and my comments to them: > > 1. That *is* verbose. Still no clues. > 2. The return code 8 (CA issue) does not compute because the cert works > in some cases, just not all. >
Is this the z/OS FTP client or server? If it's the client, try adding -d to get more diagnostic messages. from TSO: FTP -r TLS -d host from batch EXEC PGM=FTP,PARM='-r TLS -d' The client does not like self signed certs. If it's the server, there are debug parms you can specify in your FTP.DATA file. DEBUG SEC gives some SSL tracing, others may help as well. I think these are listed in the customization reference. It's been awhile since I used this, but I think the outout goes to syslogd or SYSLOG. There is also SSL tracing documented in the SSL programming book, but I have never had to use it. Richard ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
