A gsktrace is pretty easy to get and format. If it's an LE application, then in your LE options you can put: ENVAR(GSK_TRACE=0XFFFF,GSK_TRACE_FILE=/u/fred/myssltrace.file)
Otherwise I assume just setting those environment variables should work. Then after you run the thing (and it fails) you'll see a file in that location. Issue: gsktrace /u/fred/myssltrace.file > /some/location/ssltrace.txt And you should wind up with a nice, moderately readable trace file. I've been learning a lot about various TLS errors from tracing our stuff, would be interested in seeing yours since I might learn something. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
