HPlogo APPC Subsystem on MPE XL Node Manager's Guide: HP 3000 MPE/iX Computer Systems > Chapter 4 APPC Subsystem Configuration

Planning APPC Configuration
» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

Before using NMMGR, you should plan the following things:

  1. The number of session types you will configure.

  2. The number of sessions you will need for each session type.

  3. The number of sessions that will be activated automatically at subsystem startup.

Appendix C “Configuration Worksheets” provides forms you can fill out to help you plan APPC subsystem configuration. Step-by-step instructions for completing the forms are included in Appendix C “Configuration Worksheets”

Planning the Number of Session Types

You may configure up to 60 session types for the APPC subsystem. This total includes both independent and dependent LU session types. The number of session types you will need depends on three things:

  1. The number of SNA nodes (copies of SNA/SDLC Link/XL) the APPC subsystem will use. Each session type is configured to use only one link to a remote system.

  2. The number of remote LUs with which APPC LUs will interact. Each session type is configured to communicate with only one remote LU.

  3. The number of sessions you want to reserve for particular groups of users. A reserved session type should use LUs that are not configured for any other session type.

Session Types for Different SNA Nodes

Each SNA node (each copy of SNA/SDLC Link/XL) on the HP 3000 is a link with one remote system. If you plan to use several SNA nodes, you will need to configure at least one session type for each node. The SNA Node Name field of the "APPC: Independent LU Session Type Data" or "APPC: Dependent LU Session Type Data" screen specifies the SNA node you want to use.

Some remote systems, like the IBM AS/400, can perform intermediate routing between nodes in an SNA network. If your HP 3000 is connected to one of these systems, you can configure independent LU session types to communicate with nodes that are not directly connected to your local system. The Fully Qualified Remote LU Name field of the "APPC: Independent LU Session Type Data" screen specifies the network location of the LU with which you want to communicate.

Session Types for Different Remote LUs

You must configure at least one session type for each remote LU with which the APPC subsystem will communicate.

A session type that will communicate with an independent LU on the remote system must be an independent LU session type. An independent LU on the HP 3000 can conduct multiple, simultaneous APPC sessions with an independent remote LU. One local independent LU can be configured to communicate with several remote LUs simultaneously, as long as the remote LUs are all connected to the HP 3000 through the same copy of SNA/SDLC Link/XL.

Session types that will communicate with dependent LUs on the host must be dependent LU session types.

Session Types for Reserved Sessions

A group of users or an LU 6.2 product requiring guaranteed session access should have one or more session types reserved for its use. When you configure a reserved session type, you should specify LUs that no other session type will use.

Planning the Number of Active Sessions

Every conversation between transaction programs requires an APPC session. When planning the number of active sessions, you must take into account the following restrictions:

  1. The total number of simultaneously active sessions, for all session types combined, may not exceed 256. You can configure more than 256 sessions, as long as you never have more than 256 sessions active at once.

  2. An independent LU session type has only one independent LU associated with it. This independent LU can support a maximum of 256 active sessions.

  3. A dependent LU session type can support up to 32 active sessions. You must configure at least one dependent LU for every active dependent LU session.

The number of sessions you will need for each session type depends on 3 things:

  1. How many transaction programs will use the session type at once.

  2. How many instances of each transaction program will be running at once.

  3. How many conversations each instance of a transaction program will be conducting at once.

The number of sessions you will need for each session type is

[(instances of TP1) ö (simultaneous conversations with TP1)]+ [(instances of TP2) ö (simultaneous conversations with TP2)]
                           .
                           .
                           .
+ [(instances of TPn) x (simultaneous conversations with TPn)]

where TP1, TP2, . . . TPn are the transaction programs that will be using the session type at the same time.

Planning Automatic Session Activation

When you configure a session type, you specify how many sessions of that type will activate automatically at subsystem startup. No more than 256 sessions may be active at once, so the sum of all the automatically activated sessions, for all APPC session types, may not exceed 256.

Once the APPC subsystem has started up, you can use the APPCCONTROL SESSIONS command or the APPCSessions intrinsic to change the number of active sessions or reapportion sessions among different session types during run time. See Chapter 5 “Managing the APPC Subsystem” for more information.



Configuring the APPC Subsystem
  		 


Configuration Illustrations  
Feedback to webmaster