I have considerable experience in hacking FTP into doing unnatural acts but not enough of a UNIX person to be totally up-to-speed on using environment variables.
What is it that you are trying to get FTP to do that PARM= + SYSFTPD DD * + INPUT DD * will not accomplish? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Wendell Lovewell Sent: Thursday, September 10, 2020 2:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Passing STDENV DD to FTP via SYSIN Hello, I'm setting up a batch job to access our FTP server using FTPS and TLS 1.2. (Forgive me if that nomenclature is less than perfect.) I've imported certficates, built a keyring, and come up with a combination of FTP client parameters that will allow me to connect to the server and upload a file: //FTPXFER EXEC PGM=FTP,REGION=4292K, // PARM=('POSIX(ON) ALL31(ON)', // 'ENVAR("_CEE_ENVFILE=DD:STDENV")/(EXIT') //OUTPUT DD SYSOUT=* //STDENV DD DISP=SHR,DSN=WRL1.FTPS.STDENV //* //* //STDENV DD * //* GSK_PROTOCOL_TLSV1_2=ON //* //SYSFTPD DD * CLIENTERRCODES EXTENDED EPSV4 TRUE EXTENSIONS AUTH_TLS FWFRIENDLY TRUE KEYRING TCPIP/FTP.KEYRING PASSIVEIGNOREADDR TRUE SECUREIMPLICITZOS FALSE SECURE_FTP REQUIRED SECURE_MECHANISM TLS SECURE_DATACONN PRIVATE SECURE_CTRLCONN PRIVATE SECURE_HOSTNAME REQUIRED TLSMECHANISM FTP TLSRFCLEVEL CCCNONOTIFY /* //INPUT DD * I'm trying to make this as self-contained as possible, and would like to supply the variables via SYSIN rather than require the PS file named on the un-commented version of the STDENV DD. BPXBATCH is the only program I can find documented that says "//STDENV DD *" is supported. FTP, at least with the PARM I'm using, seems to ignore it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
