Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# RDISP={SHR | OLD | DNEW | MOD | NEW | NEWR | NEWA},{KEEP | CATL | DELETE},{KEEP | CATL | DELETE}

This parameter defines the disposition of the dataset on the remote Platform Server system. This parameter is only supported on transfer requests to other z/OS systems. The parameter is divided into three parameters.

The following table lists the dataset status options:

`SHR` | Requests shared access to the dataset.
`OLD` | Requests exclusive access to the dataset.
`DNEW` | Deletes the file if it already exists, then re-creates the file; creates the file if the file does not exist.
`MOD` | Appends data to the end of the dataset.
`NEW` | Creates dataset. If the dataset already exists, returns error.
`NEWR` | Creates dataset. If the dataset already exists, replaces the dataset.
`NEWA` | Creates dataset. If the dataset already exists, appends data to the end of the dataset.

The following table lists the normal deposition options:

`KEEP` | Keeps the dataset after the transfer is completed successfully. If a dataset is created, do not catalog the dataset. Note: Use this option with great care.
`CATL` | If a dataset is created, catalogs the dataset. If a dataset is not created, keeps the dataset.
`DELETE` | Deletes the dataset after the transfer is completed successfully.

The following table lists the error deposition options:

`KEEP` | Keeps the dataset after the transfer is completed unsuccessfully. If a dataset is created, do not catalog the dataset. Note: Use this option with great care.
`CATLG` | If a dataset is created, catalogs the dataset. If a dataset is not created, keeps the dataset.
`DELETE` | Deletes the dataset after the transfer is completed unsuccessfully.

The RDISP parameter works like the mainframe RDISP parameter.

The EFFECT parameter might override the RDISP and LDISP parameters. Whichever parameter defined last in the batch job takes precedence.

Note: In some conditions, the error disposition of `DELETE` cannot be processed. The dataset deletion is performed in the Dynamic deallocation routine. If the dataset is not allocated, the delete operation cannot be performed. For example, if a request fails because the dataset is not available, the dynamic allocation fails; therefore, the dataset cannot be deleted because it is not allocated. Another good example is if the request fails with a network error because the remote system is not available; obviously, the dataset cannot be deleted because communication with the remote system is not established.

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.