APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)

Chapter 5 123
Managing the APPC Subsystem
Establishing Conversations
Local Programmer Tasks
To prepare for a locally initiated conversation, the local TP programmer
must do the following:
1. Work with the programmer on the remote system to design and code
the TP.
2. Ask the node manager for the name of an appropriately configured
session type, or ask the node manager to configure a session type for
the conversation.
3. Code the name of the session type into the local TP.
Remotely Initiated Conversations
The following things must occur for a remote TP to initiate a
conversation with a local TP:
1. An APPC session of the appropriate session type must be
established.
2. The remote TP must issue an allocate request over that session,
specifying the name of the local TP with which it wants a
conversation.
3. The APPC subsystem must receive the allocate request, look up the
local TP name in the APPC subsystem configuration file, and
determine from the configuration file what to do with the allocate
request.
a. If the local TP is configured to conduct multiple remotely initiated
conversations, and if it is already active and in conversation, the
APPC subsystem must queue the allocate request until the local
TP finishes the current conversation and calls the
MCGetAllocate intrinsic again. If the local TP is not currently
running, the APPC subsystem must stream the job that runs the
local TP.
b. If the local TP is configured to conduct only one remotely initiated
conversation, the APPC subsystem must stream the job that runs
the local TP.
4. The local TP must be coded to receive the allocate request from the
remote TP.
NOTE Any local TPs that will conduct remotely initiated conversations must
be configured through NMMGR. See Chapter 4 , “APPC Subsystem
Configuration,” for information on TP configuration.