LU 6.2 API Application Programmer's Reference Guide (30294-90008)

Chapter 2 33
Conversations
Establishing Conversations
1. Configure an appropriate session type. For information on
configuring session types, see the APPC Subsystem on MPE XL Node
Manager’s Guide or the LU 6.2 API/V Node Manager’s Guide.
2. Tell the application programmer the name of the session type. The
programmer must code the name of the session type into the local
TP.
3. Activate a session of the appropriate session type, or configure one
for automatic activation at subsystem startup. For more information
on session activation, see the APPC Subsystem on MPE XL Node
Manager’s Guide or the APPC Subsystem on MPE V Node Manager’s
Guide.
Remotely Initiated Conversations on MPE V
The following things must occur for a remote TP to initiate a
conversation on MPE V:
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 job that runs the local TP with which it
wants a conversation.
3. The APPC subsystem must receive the allocate request and stream
the job that runs the local TP.
4. The local TP must be coded to receive the allocate request from the
remote TP.
Local Programmer Tasks
To prepare for remotely initiated conversations, you must do the
following:
1. Work with the programmer on the remote system to design and code
the TP. The local TP must call the MCGetAllocate intrinsic to
receive an allocate request from the remote 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. The session type must direct data to the remote
LU that serves the remote TP.
3. Code the name of the session type into the
SessionType parameter
of the MCGetAllocate intrinsic.
4. Tell the node manager the executable file name of the TP. The
executable file may reside in any group and account. The node
manager will create a job to run the TP.