The Batch Interface › XCOMJOB DD Statements › LCLDS01

LCLDS01

Defines the local data set available for the transfer request.

The preferred alternative to using the LCLDS01 DD statement is to define the data set using the LFILE parameter in the SYSIN01 DD statement (see below). If you enter both the LCLDS01 DD statement and the SYSIN01 LFILE parameter, the LFILE parameter takes precedence.

You should use the LFILE SYSIN01 keyword parameter to specify the local file name for TYPE=SCHEDULE transfers. While you can specify the local file name using the LCLDS01 DD statement even for TYPE=SCHEDULE transfers, there are several potential complications to consider:

• When LCLDS01 is used to reference a local file for a transfer, the z/OS JCL processor is involved in the data set allocation process for the transfer. It is possible to encounter problems with data set enqueues being held by z/OS allocation routines while the transfers are being scheduled.
• If the transfer begins to run on the started task before the job scheduling transfer ends, the data set may not be available for exclusive use by the CA XCOM Data Transport started task. This may cause the transfer to fail due to an unavailable exclusive enqueue.
• Using LCLDS01 to reference a local file for a transfer may also lead to the creation of dummy GDGs.

  If the LCLDS01 DD is used to create a +1 GDG version for a TYPE=SCHEDULE transfer there are additional potential problems:

  • When the z/OS JCL performs the allocation of the LCLDS01 DD, it allocates and potentially catalogs the new version, depending on the value of the DISP parameter in the JCL. This new version does not have an end‑of‑file mark because it has not yet been opened and closed by a program.
  • When the transfer begins on the CA XCOM Data Transport started task, it allocates a new +1 version of the GDG. In cases where the transfer is successful, this results in the creation of two new generations of the GDG. The first version contains garbage because it was allocated by the z/OS JCL processor and was never opened or closed by a program to write an end‑of‑file mark. If the transfer fails, under certain conditions the version allocated by the CA XCOM Data Transport started task may be deleted. This leaves the version of the GDG allocated by the z/OS JCL processor as the current version.

All of these potential problems can be avoided if the LOCAL FILE name is specified on the LFILE SYSIN01 parameter, rather than with the LCLDS01 DD statement for TYPE=SCHEDULE transfers.

The LCLDS01 DD statement permits sequential data sets to be concatenated for TYPE=EXECUTE requests. Other types of data sets cannot be concatenated.

If it is necessary to send more than one data set to the same remote file using non‑sequential data sets or if the transfer is a TYPE=SCHEDULE request, the CA XCOM Data Transport Transfer Control (XTC) facility should be used (see the sections SYSIN01 Transfer Control (XTC) Parameters and Coding Interdependent Transfers).

Note: The SYSOUT keyword cannot be used in this DD statement.