Export an IODF (CBDSEXP)

This HCD function sends an IODF to another system, either z/VM or z/OS. To export an IODF on z/VM, use the REXX utility CBDSEXP, as shown in Example 1 of the Utility CBDSEXP.

If you want to send an IODF to an unattended z/OS system, you have to allocate a file with DD name HCDCNTL. From this file, HCD extracts information to set up the JCL to run on the unattended target system. You have to modify or adapt the JOB statement, JES routing statement(s), and JOBLIB information in this file before you call the export utility.

This function is invoked by passing the following parameter string.

user id

Specifies the user ID of the target, or a nickname (nickname only if the IODF is not sent to an unattended z/OS system).

node id

Specifies the node ID of the target system, but only if the IODF is not sent to an unattended target system (otherwise it is ignored in favor of information provided by the JCL).

IODF name

Specifies the name of the target IODF. Default is the name of the source IODF prefixed with the specified target user ID. This parameter is only applicable if the IODF is sent to an unattended z/OS system, otherwise it is ignored.

volume

Specifies the volume serial number of the DASD on which the target IODF is created if it does not exist. This parameter is only applicable if the IODF is sent to an unattended z/OS system, and the IODF file is not managed by SMS, otherwise it is ignored.

ACTLOG

Specifies that the appropriate activity log file should also be sent. If this parameter is missing, or the target is an unattended MVS system, it is not sent.

NOREPLACE

For unattended exports, this keyword provides overwrite protection for an IODF at the target system with the same name as the IODF to be exported.

FILEDEF statements are required for the following files when invoking HCD: