 |
» |
|
|
|
Conversations between transaction programs can be locally
initiated (initiated by the TP on the HP 3000), or remotely
initiated (initiated by the TP on the remote system). This section
describes the tasks that the node manager, the local application
programmer, and the remote application programmer must perform in
order to establish a locally or remotely initiated conversation. Locally Initiated Conversations | |
The following things must occur for a local TP to initiate
a conversation: An APPC session of the appropriate
session type must be established. A local end user must run the local TP. The local TP must send an allocate request over
the session assigned to it, to request a conversation with the remote
TP. The remote TP must be coded to receive the allocate
request from the local TP.
Note that the session must be established before the local
TP can use it to send the allocate request. This section describes
the tasks that the node manager and the local application programmer
must perform in order to establish a locally initiated conversation. To prepare for a locally initiated conversation, you must
do the following: Configure an appropriate session type.
The session type must direct data to the remote LU that serves the
remote TP. For information on configuring session types, see Chapter 4 “APPC Subsystem Configuration” Tell the application programmer the name of the
session type. The programmer must code the name of the session type
into the local TP. Activate a session of the appropriate session type
by issuing the APPCCONTROL SESSIONS command, or configure a session for automatic activation
at subsystem startup.
To prepare for a locally initiated conversation, the local
TP programmer must do the following: Work with the programmer on the remote
system to design and code the TP. 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. 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: An APPC session of the appropriate
session type must be established. The remote TP must issue an allocate request over
that session, specifying the name of the local TP with which it
wants a conversation. 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. 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. 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.
The local TP must be coded to receive the allocate
request from the remote TP.
To prepare for a remotely initiated conversation, you must
do the following: 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. Tell the application programmer the name of the
session type. The programmer must code the name of the session type
into the local TP. Activate a session of the appropriate session type
by issuing the APPCCONTROL SESSIONS command, or configure a session for automatic activation
at subsystem startup. 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. 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> |
Configure the name of the job file in the "APPC:
Transaction Program Data" screen in NMMGR. 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. 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. 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.
To prepare for remotely initiated conversations, the local
TP programmer must do the following: 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. 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. Code the name of the session type into the local
TP. 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. Code the TP name into the local TP. Tell the node manager the executable file name of
the TP. The node manager will create a job to run the TP. 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. 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. Tell the node manager whether to configure the TP
for manual or automatic startup.
To prepare a remote program to initiate a conversation with
a TP on the HP 3000, the remote programmer must do the
following: Design and code the program to initiate
a conversation with the corresponding TP on the HP 3000. Make sure that the remote TP passes the proper TP
name in the allocate request. The HP application programmer must
tell the remote TP programmer which TP name to use.
|
