JCL statements for PDUU

The JCL statements for the PDUU are:

SYSPRINT

The data set can be either SYSOUT or a sequential data set. The data set must be RECFM=FB, LRECL=134. For additional details, see Prerequisites and restrictions for PDUU.

SYSUT1

The sequential Start of change

or partitioned End of change

data set to transfer to IBM®. For additional details, see Prerequisites and restrictions for PDUU.

SYSUT2

This data set is optional and can be used only when transferring partitioned data sets (PDS/PDSE). It defines a sequential unload data set for IEBCOPY output produced during the unload operation. If the SYSUT2 statement is omitted the unload data set will be allocated dynamically. This parameter can be used if you want to directly control the allocation of the unload data set, for example, to specify a particular volume or certain amount of volume space. For additional details about usage and allocation parameters of the unload data set see the topic on Unloading (Backing up) Data Sets in z/OS DFSMSdfp Utilities . See also Example 9: Using SYSUT2 to allocate an unload data set. End of change

SYSIN

A sequential data set that uses the following control statements. The data set must be RECFM=FB, LRECL=80. For additional details, see Prerequisites and restrictions for PDUU.

PDUU is managed through the following SYSIN statements with these guidelines:

Use an asterisk (*) in the first column of each comment line to indicate comments.
Keywords must start in column one.
Use control statements that are in form VERB=OPERAND.
Mixed case verbs and operands are allowed.
The operand starts in the column after the equal sign and goes to the first blank column except TARGET_SYS, DIRECTORY, CIPHER_KEY, ACCOUNT, USERID, and PASSWORD, which can contain blanks.
Anything after the first blank is ignored except for any operands that can contain blanks. In those cases, do not use blanks from column one to the end of the operand.
Control statements can be coded on one or more (up to 6) consecutive records. Control statements with operands that allow blanks must not extend beyond column 71, but can continue on the following record in columns 16 through 71. Columns 1 through 15 of the continuation record must be blank. See Example 10: Using a multiple record control statement in SYSIN. Control statements with operands that do not allow blanks can occupy columns 1 through 80.

TARGET_SYS

The name of the TCP/IP system to transfer the files to using FTP. One through Start of change

256

characters, dotted decimal format is allowed, no default value, can contain blanks, and it must be specified.

If using a proxy server, this should be the name of the proxy server.

You can include additional FTP command parameters on the TARGET_SYS parameter by using the z/OS® UNIX specifications as shown in the topic FTP command -- Entering the FTP environment in z/OS Communications Server: IP User's Guide and Commands. For example, to trace output (-d) and use a specific ftpdata_filename (-f"//'WES.MYFTP.DATA'"):

TARGET_SYS=-d -f"//'WES.MYFTP.DATA'" testcase.boulder.ibm.com

Use the -p parameter to specify an alternate IP stack.

USERID

The user ID on the target system that is used to send the files. One through 64 characters, no default value, does not have to be specified, and can contain imbedded blanks. If USERID and PASSWORD are not supplied and NETRCLEVEL=2, the values from the NETRC data set is used for the FTP sessions.

If using a proxy server, this can be the full login to the remote system in the format userid@remote.system.name.

PASSWORD

The password for the USERID on the target system. One through 64 characters and the default value is blanks.

If using a proxy server, this can be the USERID and PASSWORD for the proxy server in the format userid@password.

ACCOUNT

The account data that is sent when an FTP session is started. Start of change

One through 64 characters with no default value. End of change

TARGET_DSN

The variable (descriptive) portion for the file names on the target system. One through 64 characters, no default value, and it must be specified.

WORK_DSN

The prefix for the data set names of work files on the sending system. One through 40 characters, no default value, and it must be specified. The work data sets are large format, sequential, data sets and cannot have the compaction attribute.

Note: Because work files are dynamically allocated with large format and do not support compressed format, if you specify data class for work files with the compaction attribute or N, the following message is issued for all work files:

IGD17163I COMPRESSION REQUEST NOT HONORED FOR DATA SET
work_file_dsname BECAUSE DATA SET CHARACTERISTICS 
DO NOT MEET COMPRESSION CRITERIA, ALLOCATION CONTINUES

WORK_DSN_SIZE

The maximum size of the work files in megabytes. One through four decimal digits and the default is 100 MB.

KEEP_WORK

The parameter to save the work data sets that are dynamically allocated for each FTP session. If you omit the KEEP_WORK parameter, the program does not save the work data sets. Y is the only value for the KEEP_WORK parameter.

Note: Only specify this parameter when debugging a problem.

DATACLAS

The data class to use when allocating the work files on the sending system. One through eight characters with no default value.

STORCLAS

The storage class to use when allocating the work files on the sending system. One through eight characters with no default value.

CC_FTP

The number of parallel FTP sessions to use when transmitting the files. One or two decimal digits, the value must be between one and 20, and the default is two.

DIRECTORY

The directory on the target system where the files will be sent with FTP. One through 32 characters, with no default, can contain blanks, and you must specify the directory.

PMR

The PMR number with which this file is associated. This field must be 13 numeric or uppercase characters, specify in the form xxxxx.yyy.zzz, and define the variables as:

Table 1. PMR number variables for PDUU
Field	Explanation	Example
XXXXX	PMR Number	`34143`
YYY	Branch office	`055`
ZZZ	IBM Country Code	`724`

CIPHER_KEY

The encryption key to use for 192-bit triple DES encryption. The 24 characters following CIPHER_KEY= are used as the key. The key can include imbedded and/or trailing blanks. For example, CIPHER_KEY=HERE IS CIPHER KEY IN 24 or CIPHER_KEY=Shortkey. If you do not specify CIPHER_KEY=, no encryption is performed. If you encrypt the data set using CIPHER_KEY, you must provide IBM with the encryption key so they can perform problem diagnosis.

Note: If CIPHER_KEY= is followed by 24 blanks, the file will be encrypted with a key of 24 blanks.

DEBUG

An optional DD statement that gathers debug information such as messages issued to the SYSPRINT data set and the FTP protocol messages. The data set must be RECFM=FB, LRECL=134.

FTPCMDS

An optional DD statement that provides additional flexibility for traversing firewall or proxy servers. When this DD statement is provided, after the initial USERID and PASSWORD are sent, the specified sequential data set is read by the application and the commands contained in the data set are included as FTP commands. The data set must be RECFM=FB and LRECL=80.