HPlogo LU 6.2 API Application Programmer's Reference Manual: HP 3000 MPE/iX Computer Systems > Chapter 2 Conversations

Establishing Conversations
» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

TP conversations 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 local application programmer, the node manager, 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:

  1. An APPC session of the appropriate session type must be established.

  2. A local end user must run the local TP.

  3. The local TP must send an allocate request over the session assigned to it, to request a conversation with the remote TP.

  4. 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 local application programmer and the node manager must perform in order to establish a locally initiated conversation.

Local Programmer Tasks

To prepare for a locally initiated conversation, you must do the following:

  1. Work with the programmer on the remote system to design and code the 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 MCAllocate intrinsic.

Node Manager Tasks

To prepare for a locally initiated conversation, the node manager must do the following:

  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.

  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.

    1. 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 .

    2. 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.

  4. The local TP must be coded to receive the allocate request from the remote TP.

NOTE: On MPE XL, any local TPs that will conduct remotely initiated conversations must be configured through NMMGR/XL. See the APPC Subsystem on MPE XL Node Manager's Guide for information on TP configuration.

Local Programmer Tasks

To prepare for remotely initiated conversations on MPE XL, you 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. A TP designed to receive multiple allocate requests must call the MCGetAllocate intrinsic multiple times. A TP designed to receive only one allocate request must call the MCGetAllocate intrinsic only once.

  2. Together with the programmer on the remote system, decide on a name for the TP. Make sure you and the other programmer agree on the TP name; 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 subsystem configuration file.

  3. Code the TP name into the LocalTPName parameter of the MCGetAllocate intrinsic and the LocalTPName parameter of the TPStarted intrinsic.

  4. 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.

  5. Code the name of the session type into the SessionType parameter of the MCGetAllocate intrinsic.

  6. 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.

  7. 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.

  8. Decide whether you want to start the TP yourself or have the APPC subsystem start the TP. While you are debugging the TP, you might want to start it yourself. However, once the TP is working, you should have the APPC subsystem start the TP when it receives an allocate request from the remote TP. Tell the node manager whether to configure the TP for manual or automatic startup.

  9. 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.

Node Manager Tasks

To prepare for a remotely initiated conversation on MPE XL, the node manager must do the following:

  1. Configure an appropriate session type.

  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. See the APPC Subsystem on MPE XL Node Manager's Guide for more information.

  5. Configure the TP name, the job name, the time-out value, whether the TP accepts queued allocate requests, and whether the programmer will start the TP manually. See the APPC Subsystem on MPE XL Node Manager's Guide for information on TP configuration.

Remote Programmer Tasks

To prepare a remote program to initiate a conversation with an HP TP on MPE XL, 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 TP name in the allocate request. The HP application programmer must tell the remote TP programmer which TP name to use.



Two-Way Conversation With Confirm
  		 


Chapter 3 Using Intrinsics  
Feedback to webmaster