Configuring an Invokable TP Using snaptpinstall

File Format for snaptpinstall

TP (unless the application overrides it by specifying a full path). If the application specifies a file name without a path, SNAplus2 searches for the file in this home directory; if the application specifies a file name with a relative path, SNAplus2 searches for the file in the specified directory relative to this home directory. This line is required, and must be specified. The ID must be a valid HP-UX login ID on the SNAplus2 computer; it can be up to 64 characters, unless your HP-UX configuration restricts user names to fewer characters.

The executable file for the TP, specified by the PATH parameter, must have execute permission for the specified user. In addition, if USERID is set to root, the file must be owned by root and must have setuid and setgid permission in order to be started automatically by SNAplus2.

GROUP

Specify the group ID that SNAplus2 uses to start the TP. This must be a valid HP-UX group ID on the SNAplus2 computer; it can be up to 64 characters, unless your HP-UX configuration restricts group names to fewer characters.

This line is optional; if it is not included, the default is other.

LUALIAS

Specify the local LU alias from which the TP is to accept incoming Attaches. This is an eight-character name that must match the name of a SNAplus2 local

APPC LU.

To indicate that the TP accepts incoming Attaches from any local LU, set this parameter to two double quotation mark characters, "", indicating a blank LU alias. If the invokable TP data file contains more than one entry for the same TP name, only one of these entries can specify a blank LU alias; each of the others must specify a different explicit LU alias. SNAplus2 matches an incoming Attach for this TP name to a TP specifying the appropriate LU alias, if possible, or to a TP specifying a blank LU alias if no LU alias match can be found.

Appendix C

349