|
|
|
|
The SNAP-IX configuration file, which is set up and maintained by the System Administrator, contains information that is required for TPs to communicate. For additional information about configuration, refer to the SNAP-IX Administration Guide.
Before writing an invoked TP, you must coordinate the local TP name with the System Administrator. The name can contain up to 64 characters.
If you intend to use the extended form of the RECEIVE_ALLOCATE verb, in which the application can specify a local LU from which to accept incoming conversation requests, you must also coordinate the local LU alias (the name by which the local LU is known to the local TP) with the System Administrator. This alias can contain up to eight characters.
For more information, see the RECEIVE_ALLOCATE verb in APPC Control Verbs.
The following list summarizes the information you need to obtain from (or coordinate with) your System Administrator before writing an invoking TP:
Name by which the local LU is known to the local TP. This name can contain up to eight characters. For more information, see the description of the TP_STARTED verb in APPC Control Verbs.
This name can contain up to 64 characters. For more information, see the description of the [MC_]ALLOCATE verb in APPC Conversation Verbs.
Name by which the partner LU is known to the local TP. This name can contain up to eight characters. For more information, see the description of the [MC_]ALLOCATE verb in APPC Conversation Verbs.
Set of characteristics to be used in an LU-to-LU session. This name can contain up to eight characters. For more information, see the description of the [MC_]ALLOCATE verb in APPC Conversation Verbs.
If conversation security is to be used, a valid combination of user ID and password is required to access the invoked TP. The user ID and password can contain up to 10 characters. Both parameters are case-sensitive; the system distinguishes between uppercase and lowercase letters. Security information is stored in a security file. For more information, see Overview of Conversation Security.
|
|
|
|
|