Configuring APPC Communication

Defining TPs

The local LU alias from which the TP is to accept incoming Attaches. This name must match the name of a local APPC LU on the SNAplus2 node. If you do not specify an LU alias, the TP accepts incoming Attaches from any local LU.

This field applies only if you specify that the parameters for this TP definition are for invocation on any LU.

You can define multiple TPs that have the same TP name, provided each TP definition specifies a different LU alias.

Multiple instances supported

If you do not select this option, the TP is a queued TP. Any incoming Allocate requests arriving while the TP is running are queued until the TP issues another Receive_Allocate, or until it finishes running and can be restarted. An incoming Allocate request is routed to this TP only if it is received by an LU that is configured to route incoming Allocate requests to this computer, or if it is received by an LU on this computer that has no routing information configured.

If you select this option, the TP is a nonqueued TP. SNAplus2 starts a new copy of the TP each time an incoming Allocate request arrives for it. A nonqueued TP cannot be started by an operator; it is always started automatically by SNAplus2. For a nonqueued TP, SNAplus2 permits more than one copy of the TP to be running at a time. All copies run with the same user and group IDs and the same working directory, as defined by the User ID and Group ID parameters. If the TP writes to files on the local system, you need to ensure that different copies of the TP do not overwrite each other's files.

Route incoming Allocates to running TP

This option applies only if multiple instances are not supported.

Select this option if the TP is a broadcast queued TP. Any incoming Allocate requests arriving while the TP is running are queued until the TP issues another Receive_Allocate, or until it finishes running and can be restarted. When the TP is started, information

190

Chapter 7