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

124 Chapter5
Managing the APPC Subsystem
Establishing Conversations
Node Manager Tasks
To prepare for a remotely initiated conversation, you must do the
following:
1. Configure an appropriate session type. The session type must direct
data to the remote LU that serves the remote TP. See Chapter 4 ,
“APPC Subsystem Configuration,” for information on configuring
session types.
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 by issuing the
APPCCONTROL SESSIONS command, or configure a session for
automatic activation at subsystem startup.
4. Ask the local TP programmer for the TP name, and configure it in
the “APPC: Select Transaction Program” screen. Make sure the
configuration file, the local TP programmer, and the remote TP
programmer all agree on the TP name. The same TP name must be
configured through NMMGR, coded into the local TP, and sent by the
remote TP in the allocate request.
5. Create a job that runs the executable TP file. Job files and
executable TP files may reside in any group and account. A job file
name must be eight characters long and begin with an alphabetic
character. Job files must not contain any passwords or lockwords.
The APPC subsystem configuration file associates each configured
TP name with a job file name. When the APPC subsystem receives
the local TP name from the remote TP, it gets the job file name from
the configuration file and streams the job, which runs the local TP.
Each remotely initiated local TP requires a separate job file.
Here is an example job file that would run the local TP
HPTP.BOB.MAPPED at the request of a remote TP. The name of the job
file is JOBFILE1.APPC.SYS.
!JOB JOBFILE1.APPC.SYS
!RUN HPTP.BOB.MAPPED
!EOJ<F255P255>
6. Configure the name of the job file in the “APPC: Transaction
Program Data” screen in NMMGR.
7. Configure the time-out value for the MCGetAllocate intrinsic in
the “APPC: Transaction Program Data” screen in NMMGR. After
the local TP calls the MCGetAllocate intrinsic to receive an
allocate request, it will be suspended until an allocate request
arrives from the remote TP or until the configured time-out value
expires. Ask the local TP programmer how long the TP should wait
for an allocate request from the remote TP.