PDS Support

The following functions for library transfers are supported:

Transfer of individual members.
Transfer of complete libraries.
Transfer of members with wildcard.
Renaming of members that are transferred.
Transfer of members between PDS and PDS/E data sets.
Transfer of LOADLIBs between PDS data sets.
All member directory information is sent along with the member.
Alias members are fully supported.
Data set allocation attributes are sent to the receiving system.
Data set allocation attributes can be overridden.

Restrictions to PDS Support

See the following two restrictions to platform server PDS support:

The platform server will not write data to a PDS/E program library.
The platform server will not send an alias alone without the actual member.

Additional Batch Parameters for Library Support

The following two additional batch parameters are added for library support:

DATASET_TYPE=LIBRARY

Informs the receiver of the file that if a data set is to be created, a PDS/E must be created. If this parameter is not set, a PDS is created at the remote end.
ALLOC_DIR=directory_block_number

Defines the number of directory blocks that will be allocated when a file is created. This parameter overrides the local data set attributes that are sent to the system which creates the data set.

Generic/Wildcard Support for Members

The asterisk (*) denotes a generic member.
If a PDS is specified without a member name, all members are sent.
FILE=MY.PDS is the same as MY.PDS(*).
Question mark (?) is the wildcard character. It can be used with characters of a member and with the generic character (*).

See the following examples of generic member or wildcard support:

Example 1:

FILE=MY.PDS(abc*)

REMOTE_FILE=YOUR.PDS(WXYZ*)

All files starting with ABC will be sent to the remote system. When the files are written, the first 4 characters are replaced by WXYZ.

Example 2:

FILE=MY.PDS(???TEST?)

REMOTE_FILE=YOUR.PDS

Members in which characters 4 to 7 are TEST will be sent. The member names on the remote system are the same as on the local system.

Alias Support

When a full library, or partial library transfer is specified, all members and aliases that match the selection criteria will be sent to the remote system.
When a specific member is sent, that member, and all aliases of that member will be sent to the remote system.

Examples of Sending PDS Files

PROCESS SEND
		DSN=MY.LOCAL.PDSS(ABC)
		REMOTE_FILE=YOUR.PDSS
		NODE=REMOTE

Sends member ABC to node REMOTE member ABC.

PROCESS SEND
		DSN=MY.LOCAL.PDS(ABC)
		REMOTE_FILE=YOUR.PDS(XYZ)
		NODE=REMOTE

Sends member ABC to node REMOTE member XYZ.

PROCESS SEND
		DSN=MY.LOCAL..PDS
		REMOTE_FILE=YOUR..PDS
		DATASET_TYPE=LIBRARY
		NODE=REMOTE

Sends all members of a PDS to a PDSE on node REMOTE.

```
PROCESS SEND
		DSN=MY.LOCAL.PDS(???PROD*)
		REMOTE_FILE=YOUR.PDS(???TEST)
		DATASET_TYPE=LIBRARY
		NODE=REMOTE
```
Sends selected members of a PDS to a PDSE on node REMOTE. Changes characters 3 to 6 from PROD to TEST when writing the members.

Note: When you send libraries to a non-z/OS system, or an earlier release of TIBCO MFT Platform Server for z/OS, if you attempt to send or receive a library, and the remote computer does not support library transfers, the platform server will end the transfer and display a message on both the local and remote computer which indicates that the remote computer does not support library transfers. The transfer request is purged from the request queue afterwards.

Contents