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

Chapter 5 125
Managing the APPC Subsystem
Establishing Conversations
8. Configure the local TP to receive queued or non-queued allocate
requests. Ask the local TP programmer whether the local TP will call
the MCGetAllocate intrinsic multiple times or only once. If the
local TP will call MCGetAllocate multiple times, configure it to
accept queued allocate requests; if it will call MCGetAllocate only
once, configure it to accept non-queued allocate requests. Queued or
non-queued allocate requests are configured in the “APPC:
Transaction Program Data” screen in NMMGR.
9. Configure the local TP for manual or automatic startup. Ask the
local TP programmer whether the APPC subsystem should
automatically stream a job to run the local TP when it receives an
allocate request from the remote TP or whether the TP programmer
wants to start up the local TP manually by issuing the MPE RUN
command. Automatic or manual TP startup is configured in the
“APPC: Transaction Program Data” screen in NMMGR.
Local Programmer Tasks
To prepare for remotely initiated conversations, the local TP
programmer must do the following:
1. Work with the programmer on the remote system to design and code
the TP. The local TP can be designed to receive multiple allocate
requests from the remote TP, or it can be designed to receive only
one allocate request.
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.
4. Together with the programmer on the remote system, decide on a
name for the TP. It must be coded into the local TP, and it must be
sent by the remote system in the allocate request. Tell the node
manager the TP name. The node manager must configure the TP
name in the “APPC: Transaction Program Data” screen in NMMGR.
5. Code the TP name into the local TP.
6. Tell the node manager the executable file name of the TP. The node
manager will create a job to run the TP.
7. Tell the node manager how long the local TP should wait for an
allocate request from the remote TP before the MCGetAllocate
intrinsic times out. The node manager will configure the time-out
value.
8. Tell the node manager whether the TP calls the MCGetAllocate
intrinsic multiple times or only once. The node manager must
configure the TP to accept either single or queued allocate requests.