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

34 Chapter2
Conversations
Establishing Conversations
5. Ask the node manager for the name of the job file that runs the local
TP, and tell the programmer on the remote system what the job file
name is. The remote system must send the name of the job file in the
allocate request.
Node Manager Tasks
To prepare for a remotely initiated conversation on MPE V, the node
manager must do the following:
1. Configure an appropriate session type. See the LU 6.2 API/V Node
Manager’s Guide for information on session type configuration.
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.
4. Create a job that runs the executable TP file. The job file must be
located in the APPC.SYS group and account. See the LU 6.2 API/V
Node Manager’s Guide for more information.
Remote Programmer Tasks
To prepare a remote program to initiate a conversation with an HP TP
on MPE V, the remote programmer must do the following:
1. Design and code the program to initiate a conversation with the
corresponding TP on the HP 3000.
2. Make sure that the remote TP passes the proper job name in the
allocate request. The HP application programmer must tell the
remote TP programmer which job name to use.
Remotely Initiated Conversations on MPE XL
The following things must occur for a remote TP to initiate a
conversation with a local TP on MPE XL:
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.