Previous Topic: Unicode and Multi-Byte Character Set Support for Data Transfer

Next Topic: Deprecated or Obsolete Features


XCOMRRDS Transfer Queue Startup Option

A new parameter has been added to provide greater control of the CA XCOM Data Transport server startup.

This section contains the following topics:

New Parameter

New Message

New Parameter

This section describes the new PARM and CONFIG parameter.

QSTART

This parameter specifies the handling of the XCOMRRDS transfer queue during initialization of the CA XCOM Data Transport server.

WARM

This option performs a WARM start of the server in normal mode, as for previous releases. The XCOMRRDS transfer queue is read and requests are queued for pending work in the XCOMRRDS data set.

COLD

This option performs a COLD start of the server. It removes all pending work from the RRDS. (This is roughly the equivalent of deleting and defining the XCOMRRDS data set, with the exception that the next transfer request number is not reset to 1000.)

HOLD

This option performs a HOLD start of the server. It reads the XCOMRRDS transfer queue data set and builds requests for all pending work. The difference between HOLD and WARM is that all LOCALLY initiated transfer requests are placed in a HOLD status.

Default: WARM

New Message

This section describes the new message.

0479I

TRANSFER QUEUE BEING xxxx STARTED

Reason:

The CA XCOM Data Transport server is being started with the xxxx parameter for the QSTART option. The following explains the meaning of each possible QSTART option.

WARM: The XCOMRRDS transfer queue data set is being read sequentially, and all transfer requests that were pending when the server was last shutdown will be queued for execution with the same status values at the time the server was terminated.

COLD: All XCOMRRDS transfer request entries in the queue will be deleted, regardless of status. This has the same basic effect as reinitializing the XCOMRRDS data set.

HOLD: The XCOMRRDS transfer queue data set is being read sequentially, and all LOCALLY initiated transfer requests that were pending when the server was last shutdown will be placed in the server queue with a HOLD status.

Action:

None