Previous Topic: Authority for APPCLUNext Topic: Change Data in the APPCLU Record


Define Data to the APPCLU Record

To add a link to the APPCLU record, enter:

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

The LINKID keyword identifies which LUs can be used for APPC conversation processing.

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

Identifies the name of the local LU.

remotelu

Identifies the partner LU.

Prefixing is supported; masking is not.

The Network Qualified Names (NQN) option, introduced with VTAM 4.1, requires the LINKID to include a remote netid qualifier. The format of such a LINKID is:.

	localnetid.locallu.remotenetid.remotelu

This format must be used if NQN is on. If NQN is off, the original three‑qualifier format should be used.

SESSKEY

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

INTERVAL

Identifies the number of days for which the SESSKEY is valid. Zero indicates that the SESSKEY will not need to be changed.

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

Indicates security information is required. A userid and password need to 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.

Examples: establish LINKIDs

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 and the SESSKEY must be changed every 30 days:

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

This example establishes a similar task with NQN:

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