DFS62DTx member of the IMS PROCLIB data set

Use the DFS62DTx member of the IMS PROCLIB data set to store the LU 6.2 device descriptors that are built during IMS initialization.

In the DFS62DTx member of the IMS PROCLIB data set, x is the IMS nucleus suffix. LU 6.2 device descriptors specify an LTERM that associates an output destination with an LU 6.2 device. The system administrator can additionally change applications that use alternate PCBs into applications that use LU 6.2 devices, without application coding changes.

No IMS definition or system definition changes are required to use an LU 6.2 device.

The record format is:

Position: Contents
1: Descriptor type (U for user descriptor)
Although this column is not required for an LU 6.2 descriptor, it is included for consistency with ETO descriptors. It is not checked, and no error message is issued if it is omitted.
2: Blank
3-10: Contains the eight-character LTERM name, left-justified and padded with blanks, if necessary. This positional parameter is required, and is used as the descriptor name. A descriptor definition can be continued by repeating the descriptor name in subsequent records. Each individual descriptor can contain up to 50 records (excluding comment records).
11: Blank
12-72: Contains the parameter sets for the descriptor.
73-80: Ignored

DFS62DTx descriptor format

This is the format for the DFS62DTx descriptor. Do not code a parameter in the descriptor and then leave it blank such as (SIDE=␢). If you do this, an error message is issued. Instead, omit it completely if you do not need to specify a DFS62DTx descriptor. A descriptor definition can be continued by repeating the descriptor name in subsequent records.

U ltermname parm1 parm2 parmn

In this example:

U: Indicates user descriptor.
ltermname: The LTERM name.
parm (1...n): Can be any of the following parameters: SIDE=, MODE=, TPNAME=, SYNCLEVEL=, CONVTYPE= , OUTBND=.

The following is an example of a DFS62DTx descriptor:

Column   Column                                               Column
1        12                                                       72
U L62TERM1 LUNAME=L62IMS1 TPNAME=CPICTRN1 MODE=L62MDE02   
U L62TERM1 SYNCLEVEL=N OUTBND=MYLU02

Separate the parameters with a blank.

DFS62DTx keyword descriptions

CONVTYPE=: Specifies whether the conversation type is basic (B) or mapped (M). The default value is M.
LUNAME=: Is a 1- to 17-alphanumeric character (uppercase) name of the destination LU 6.2 application program, which can be a 1- to 17-byte network-qualified LU name. An example of a network-qualified LU name is netid1.luname1. If SIDE= is specified, LUNAME overrides the LUNAME in the side information entry. The default is DFSLU.
Do not specify a network name for a dependent LU.
MODE=: Is a one- to eight-character name of the VTAM® mode table entry to be used. If SIDE is specified, MODE overrides the mode name in the side information entry. The default is DFSMODE.
OUTBND=: Identifies a local LU to be used for outbound message processing.
SIDE=: Is a one- to eight-character alphanumeric name identifying side information entry. (Side information refers to the system-defined values for CPI communications initialization.) If you specify an entry name on this keyword, the LUNAME, TPNAME, and MODE keywords are blank unless you also specify an overriding LUNAME, TPNAME, or MODE. If you do not specify an entry name, the default values apply to the LUNAME, TPNAME, and MODE keywords.
SYNCLEVEL=: Specifies whether the APPC/IMS sync level is confirmed (C) or not (N). The default value is C.
TPNAME=: Is a 1- to 64-character name of the transaction program to be scheduled. The default is DFSASYNC. If SIDE= is specified, TPNAME overrides the TPNAME in the side information entry.
Recommendation: Use upper-case characters for TPNAMES so that the /ALLOCATE and /CHANGE commands can operate on the resulting messages and descriptors.