openFT can transfer an entire PO or PDSE data set to another z/OS computer in a single transfer request. This is only possible, however, if openFT is "APF authorized"; please consult your FT administrator regarding this authorization. In the absence of APF authorization, any attempt to transfer a complete PO or PDSE data set is rejected.
If you want to transfer an entire PO or PDSE data set and an openFT version < V10 is running on one of the partners, you must prefix the file name with one of the character strings ":L:", ":O:" or ":E:" in the NCOPY command as follows:
for any data set (PO or PDSE):
fully qualified file name: ':L:data-set-name'
partially qualified file name: :L:data-set-namefor access to a specific PO data set:
fully qualified file name: ':O:data-set-name'
partially qualified file name: :O:data-set-namefor access to a specific PDSE data set:
fully qualified file name: ':E:data-set-name'
partially qualified file name: :E:data-set-name
When transferring entire PO or PDSE data sets, you can only specify *NEW-FILE or *REPLACE-FILE as the WRITE-MODE. These specifications have the following meaning:
*REPLACE-FILE:
If a data set with the same name already exists, it is overwritten in its entirety.
*NEW-FILE:
Transfer takes place only if no data set of the same name already exists.
The transfer of complete PO or PDSE data sets with WRITE-MODE=*EXTEND-FILE is aborted with an following message.
openFT uses the IBM utility IEBCOPY for transferring entire PO or PDSE data sets. File transfer takes place as follows:
The send file identified as a PO or PDSE data set is transferred to a temporary PS data set by means of IEBCOPY-Unload.
This temporary PS data set is transferred to the remote system.
The receive file identified as a PO or PDSE data set is generated from this temporary PS data set by means of IEBCOPY-Load in the remote system. You can specify the type of the data set (PO or PDSE) using the prefixes mentioned above (":O:" for PO, ":E:" for PDSE). If you do not specify a prefix, or you specify the prefix ":L:", the dataset type of the send file (PO or PDSE) is used as the type of the newly created dataset if openFT as of V10 is running on the z/OS partner system, otherwise the default value specified by the FT administrator (prefix ":L:") is used.
The temporary PS data sets are then deleted from both systems.
This procedure ensures that, when transferring entire PO or PDSE data sets, all the structure information is also transferred. This information is also retained when copying a PO or PDSE data set using IEBCOPY. Files containing load modules can also be transferred in this way.
When a PO or PDSE data set is transferred using IEBCOPY, a temporary PS data set is created in the send and receive system as a buffer for the file in "unloaded" format. This PS data set has the following attributes:
File name: 'transuid.podsname.U' where
transuid
is the user ID which was specified in the TRANSFER-ADMISSION for the system involved. This also applies if the name of the PO or PDSE data set was specified in its fully qualified form in the NCOPY command. In this case, the "first level qualifier" for the temporary PS data set is replaced by this user ID.
pdsname
Partially qualified name of the PO or PDSE data set.
.U
This suffix identifies the temporary PS data set. For this reason, the length of the PO or PDSE data set itself may not exceed 42 characters (fully qualified) or 34 characters (partially qualified).
Volume:
openFT creates the temporary PS files on a volume specified by the
FT administrator (the same volume is used for all transfer requests). If the FT administrator has not specified a volume, the default volume defined for new files on the system involved applies.
Storage requirements:
About the same as for the associated PO or PDSE data set
Other attributes:
Default values generated by IEBCOPY, i.e.: RECFORM= VS,
BLKSIZE= max(284, PO-DS-BLKSZIZE + PO-KEYLEN + 20),
RECSIZE= BLKSIZE - 4
Please refer to the note on data protection on "Note on data protection".