The example in
Figure 1 uses the proxy login
and password stored in the userid.NETRC data set (you can submit this
as a surrogate job where the userid.NETRC data set is invisible to
the job originator). Use of the userid.NETRC data set requires NETRCLEVEL=2,
which is set in the FTP.DATA data set. Using the
-f parameter
on
TARGET_SYS control statement specifies which FTP.DATA
data set to use.
Figure 1. FTP
using a userid.NETRC data set//FTP EXEC PGM=AMAPDUPL
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=H44IPCS.WESSAMP.TRKS055K
//SYSIN DD *
TARGET_SYS=-f"//'WES.MYFTP.DATA'" testcase.boulder.ibm.com
PMR=99999.999.000
DIRECTORY=/toibm/mvs/
TARGET_DSN=wes.gb01tst
work_dsn=wes.ftpout
cc_ftp=03
WORK_DSN_SIZE=500
//
For this instance, the userid.NETRC datas et consists of one line:
machine testcase.boulder.ibm.com login anonymous password ibmusr@ibm.com
The FTP.DATA data set contains:
;***********************************************************************
;*
NETRCLEVEL 2
;*