APPLID template

Syntax:

APPLID template=template

Parameters:

template

A string with optional substitution tokens {0} and/or {1}

Properties:

Default:	empty (equivalent to `{0}`)
Values:	See below

Comments:

This setting can be used to control the APPLID passed to DCAS for ELF requests. This is useful if the optional PTKTDATA authorization check is enabled in DCAS. See check client authorization under DCAS conversation type for more information about this feature.

The template parameter is used to format the APPLID for the DCAS request. It may contain the following substitution tokens:

Token	Replaced with
`{0}`	The APPLID string supplied by the TN3270 client using the Telnet NEW-ENVIRON command. If the client did not specify an APPLID, the region name is used.
`{1}`	The region name.
`{n}` (n any other digit)	An empty string.

Note: If the client does send an APPLID using the TN3270 NEW-ENVIRON command, the TN3270 listener will force it to conform to the IBM VSAM name rules:

All characters not in the permitted character set are removed. The permitted characters are ASCII letters, digits, and the punctuation characters "@", "#", and "$".
Letters are folded to uppercase.
The resulting name is truncated to 8 characters.

The APPLID template can include characters not permitted in VSAM names, such as "-". This makes it impossible for a client to forge an APPLID that matches one produced by the template.

Examples:

The following setting:

[DCAS]
APPLID template={1}

would ignore the APPLID sent by the client and always use the region name as the APPLID for the DCAS request. This would be useful if the PTKTDATA resource class has been configured to control DCAS access by region name.

The following setting:

[DCAS]
APPLID template={1}-{0}

would make TN3270 use an APPLID formed from the region name and then the APPLID sent by the client. So, for example, if the region were named "PROD" and the client sent an APPLID of "CUST", the DCAS request would receive an APPLID of PROD-CUST. More complex APPLID templates like this may be useful for sites where APPLIDs are already in use to access different mainframe applications.