Previous Topic: Examples of Destination Definitions

Next Topic: Group Destination Member


Single LU Destination Member

....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
********************************************************************************
*                                                                              *
*CA XCOM Data Transport r11.6                                                  *
*                                                                              *
*FUNCTION:CA XCOM Data Transport r11.6 to UNIX system                          *
*                                                                              *
********************************************************************************
TYPE=DEST                    *This is a destination definition
LU=LU2310
WRITER=UNIX                  *Name of JES writer for PSO support
GETSESS=NO                   *Session must be operator/remotely activated
ACCSEC=NO                    *Access security fields not used
PSOWAIT=YES                  *JES spool scan delay is on
PARSESS=NO                   *Parallel session support not required
SETUP=NO                     *Do not pass FORMS etc.
LOGMODE=XCOMMODE             *Logon mode table entry
SRPACE=5                     *Secondary receive pacing/NCP (PACING)
SSPACE=5                     *Secondary send pacing/no NCP/VTAM
PRPACE=5                     *Primary to VTAM/NCP receive pacing/VPACING
PSPACE=5                     *Primary to VTAM/NCP send pacing/VPACING

The first two lines in the above destination definition indicate that a single LU (LU2310) is being defined as a destination. Following the definition of the destination type is a series of statements that associate a set of communication characteristics with LU2310. These characteristics take effect as soon as the control library member containing the definition of LU2310 is enabled. Once enabled, they remain in effect until a command disabling them is issued (the commands for enabling and disabling control library members are described later in the section How to Enable and Disable a Destination Member).

Note: When the destination member for an LU is not enabled (or no destination member exists), CA XCOM Data Transport uses the parameters defined in the Default Options Table for any transfers to that LU.