It does matter.  Those parameters only work when FTP is calling System SSL 
directly.  When using AT-TLS/pagent FTP is not involved in the SSL process so 
it can't trace

I wish I had the details and could be of more help (just learning 
AT-TLS/pagent) , but in one of the pagent parameters that your FTP client is 
setup to use there is a trace option and that needs to be changed to enable the 
traces level/options you want.

The trace output is written to where syslogd is configured to write the pagent 
log entries. 

On Tue, 10 Oct 2023 17:34:01 -0500, Charles Mills <[email protected]> wrote:

>@Peter, thanks.
>
>> This example uses TLSMECHANISM FTP but it should not matter.
>
>Perhaps it should not, but it does, and that is the problem.
>
>Working with my existing JCL, not yours (but it should not matter <g>):
>
>My JCL uses
>
>//STEP1   EXEC  PGM=FTP,PARM=(,                                    
>//   'ENVAR("GSK_TRACE=0xffff","GSK_TRACE_FILE=/tmp/ssl.trace")',  
>//   '/public.dhe.ibm.com 21')                                     
>
>If my FTPDATA file reads (among other stuff, of course)
>
>; TLSMECHANISM        ATTLS                      
>  TLSMECHANISM        FTP                        
>  KEYRING             xxxxxx/xxxxxx.DEMO.RING  
>
>then a gsk trace file is created in ssl.trace. OTOH if it reads (with 
>absolutely no other changes)
>
>  TLSMECHANISM        ATTLS                      
>; TLSMECHANISM        FTP                        
>; KEYRING             xxxxxx/xxxxxx.DEMO.RING  
>
>then no trace file is created. THAT is the problem I am trying to solve.
>
>Charles
>
>
>On Tue, 10 Oct 2023 09:06:26 -1000, Peter Vels <[email protected]> wrote:
>
>>I made some mistakes editing this on my phone, sorry.
>>
>>You don't need the ",SYMBOLS=(JCLONLY)"
>>
>>You do need ",SYMBOLS=(EXECSYS)" after INPUT DD*
>>
>>
>>On Mon, 9 Oct 2023, 19:06 Peter Vels, <[email protected]> wrote:
>>
>>> I use this:
>>>
>>> //FTPS     EXEC PGM=FTP,REGION=4M,
>>> // PARM=('ENVAR("_CEE_ENVFILE_S=DD:STDENV")/ftpservr 21 -e')
>
>----------------------------------------------------------------------
>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

Reply via email to