Keywords › LINKID Keyword—Identify LUs for APPC Conversation

LINKID Keyword—Identify LUs for APPC Conversation

Valid on z/OS, ESA 4.2.0 and above only.

Use the LINKID keyword to identify which LUs can be used for APPC conversation processing.

This keyword has the following format:

TSS ADDTO(APPCLU) LINKID(netid.locallu.remotelu)
                  SESSKEY(nnnnnnnn)
                  INTERVAL(nnnnn)
                  CONVSEC(NONE|ALREADYV|CONV|PERSISTV|AVPV)
                  [SESSLOCK]

netid

Identifies the network on which the local LU resides. This value should be derived from the value specified in the “netid=“ statement of the VTAM ATCSTR member.

locallu

The name of the local LU.

remotelu

The partner LU.

Prefixing is supported. Masking is not.

Note: If you have the network qualified names feature active in VTAM, use the four-level name or a prefix. For example:

local—netid.luid1.remote—netid.luid2

If you do not have the network qualified names feature active in VTAM, use the three-level name. For example:

netid.localLU.remoteLU

The following keywords are used with LINKID:

SESSKEY

A 16‑byte hexadecimal “password” used to verify the link when security is in effect.

INTERVAL

Indicates the number of days for which the SESSKEY is valid. When a value for INTERVAL is not supplied and SESSKEY is supplied, the default for INTERVAL is INTERVAL(0) and the SESSKEY does not expire.

Range: 0 to 32767

CONVSEC

Determines what security information needs to be validated when a conversation request is received. The following operands are used with the CONVSEC keyword:

• NONE—Indicates that no security validation is performed.
• ALREADYV—Indicates that security validation has already occurred. A valid userid and password, however, are still required.
• CONV—Security information is required. A userid and password must be verified.
• PERSISTV—Indicates that a userid and password must be verified on the first request, on subsequent requests only the userid is verified.
• AVPV—Supports both ALREADYV and PERSISTV values. The security type used depends on the incoming request.

SESSLOCK

Indicates that these particular LUs are not authorized to be used for APPC conversations.

The SESSKEY, INTERVAL, and CONVSEC keywords cannot be used with the REMOVE command function. Use the the REPLACE function and specify keyword() to remove the field from the APPCLU Record.

This keyword is used with:

• The commands ADDTO, REMOVE, LIST, and REPLACE
• The APPCLU ACID only
• MISC2(APPCLU) authority

Examples: LINKID keyword

This example establishes a link between LU01 and LU02. When a TP on LU01 initiates a conversation request with a TP on LU02, the SESSKEY and the initiating ACID must be validated. The SESSKEY must be changed every 30 days:

TSS ADDTO(APPCLU) LINKID(SYS1.LU01.LU02)
                  CONVSEC(CONV)
                  SESSKEY(1234)
                  INTERVAL(30)

This example removes ownership:

TSS REMOVE(APPCLU) LINKID(SYS1.LU01.LU02)

This example indicate that the SESSKEY provided for the LU01‑LU02 link must be changes every 14 days:

TSS ADDTO(APPCLU) LINKID(SYS1.LU01.LU02)
                  SESSKEY(1234)
                  INTERVAL(14)