AMAPDUPL: Problem Documentation Upload Utility

The IBM® z/OS® Problem Documentation Upload Utility (PDUU) is a utility that sends large amounts of documentation in a more efficient manner than using File Transfer Protocol (FTP) to send one large data set to IBM FTP sites. This utility sections the input data set (such as stand-alone dump data set) into smaller data sets that are compressed and sent in parallel using multiple, simultaneous FTP sessions. This results in shorter transmission time for very large data sets. You can also encrypt the data sets.

There are two work files for each FTP session (the "A" file and the "B" file). Each "A" work file is filled by copying records from the input file. When the "A" file is full, the FTP sessions are started in parallel. At the same time, each "B" work file is filled by copying records from the input file. When the "B" file is full and the transfer of the "A" file is complete, transfer of the next "B" file starts. This process continues between the "A" and the "B" files, until everything in the input file is sent.

You can have up to 20 FTP sessions running simultaneously. The work data sets are dynamically allocated and can range in size from 1 MB to 9,999 MB. You can experiment to see what works best in your environment, but here are some guidelines:

Start with three or four parallel FTP sessions. Too many parallel FTP sessions can saturate the network link.
Use medium size work data sets.

Start of change If the work data sets are very small in relationship to the input data set, you can end up with too many files on the IBM FTP sites. For example, if you are sending a 100 GB z/OS stand-alone dump and make the work data set size 1 MB, you create 100,000 files on the IBM FTP site, which exceeds the IBM limit of 99,999 files. This also causes a lot of delay by starting and stopping the FTP sessions for each file. End of change

If the work data sets are very large in relationship to the input file size, the amount of overlap time is decreased. When the program first starts, it must fill the "A" work files before it starts transmitting any data, which means the copy time is not overlapping with data that needs to be sent through FTP. For example, if you were sending a 1 GB dump and you set the work data set size to 1 GB (1,000 MB), there is no overlap between copying the records and sending the work files.

If the input data set is a partitioned data set (PDS/PDSE), the PDUU unloads it first into a sequential data set using the IEBCOPY utility.

The PDUU Start of change typically End of change compresses the input data before it is written to the work data sets, therefore it is not necessary to use a tool such as AMATERSE or TRSMAIN to compress the input data set before using the PDUU to send it to the IBM FTP site. If a file is tersed, PDUU will copy and send the files without further compression. Overall performance of using AMATERSE with PDUU to send the file takes longer than if an untersed file is compressed and sent using PDUU. End of change In addition, 192-bit triple Data Encryption Standard (DES) can be requested by using the CIPHER_KEY keyword. Without the keyword, the data is just compressed. With the keyword, the data is compressed, and then encrypted.

Encryption is provided by the CP Assist for Cryptographic Functions (CPACF), DES/TDES Enablement (feature 3863) and is available on all processors starting with the z990 (2084) and z890 (2086). CPACF, feature 3863 enables clear key DES and TDES instructions on all supported CPs. The encryption algorithm used for 3DES is documented in z/Architecture® Principles of Operation..