Completing the Worksheets

Write the name of each independent remote LU with which you will communicate in a separate Remote LU Name field on the worksheet. For AS/400 communication, the Remote LU Name must match the LCLLOCNAME in the Device Description on the AS/400.

The number of independent remote LUs you write down is the minimum number of independent LU session types you will need. (You might want to configure additional session types for reserved sessions.)

Write a name for each independent LU session type in the Session Type Name field next to each Remote LU Name. A Session Type Name must be 8 or fewer characters long and begin with a letter. It does not have to match anything in the remote configuration. Every Session Type Name must be unique.

In the Remote Network ID field under each Remote LU Name, write the network ID of the network where the remote LU is located. For AS/400 communication, the Remote Network ID must match the Local network ID in the Network Attributes Table on the AS/400.

The Remote Network ID and the Remote LU Name make up the Fully Qualified Remote LU Name in the "APPC: Independent LU Session Type Data" screen in NMMGR.

In the SNA Node Name field under each Session Type Name, write the name of the configured local SNA node that connects the HP 3000 with the system where the remote LU is located. The SNA Node Name, and the names of all the LUs associated with it, must be already configured in the SNANODE branch of NMMGR.

In the Local Independent LU Name field under each SNA Node Name field, write the name of the local independent LU that will communicate with the remote independent LU. The Local Independent LU Name you write must be configured on the node you wrote in the SNA Node Name field.

You can use the same independent LU for all the session types that use the same local SNA node (the same copy of SNA/SDLC Link/XL). Ordinarily, you need to configure only one independent LU per local SNA node; however, if you want to reserve sessions for a specific application or group of users, you can configure an independent LU for that purpose alone.

In the Mode Name field for each session type, write the mode name configured for the remote LU. The mode name configured on the HP 3000 must match the mode name configured for the remote LU. For AS/400 configuration, the Mode Name must match the MODE in the Device Description on the AS/400.

For each session type, determine the maximum number of active sessions you will need and write that number in the Maximum Number of Sessions field. You will need as many active sessions as you will have conversations using the session type at once. The number of sessions you will need for each session type is

[(instances of TP1 x (simultaneous conversations with TP1)]
 
+ [(instances of TP2 x (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.

For each session type, determine the number of sessions that will be activated when the APPC subsystem is started, and write the number in the Automatically Activated Sessions field. The Automatically Activated Sessions value must be less than or equal to the Maximum Number of Sessions value.

When you have completed the Independent LU Session Types worksheet, add up all the Automatically Activated Sessions for all the session types. If the sum is greater than 256, adjust the Automatically Activated Sessions values until the sum is less than or equal to 256. The sum of all the Automatically Activated Sessions, for all independent and dependent LU session types, must be less than or equal to 256.

Write the name of each remote LU with which you will communicate in a separate Remote LU Name field on the worksheet. The Remote LU Name must match the APPLID in the Label field of the VTAM APPL definition statement.

The number of remote LUs you write down is the minimum number of dependent LU session types you will need. (You might want to configure additional session types for reserved sessions.)

Write a name for each dependent LU session type in the Session Type Name field next to each Remote LU Name. A Session Type Name must be 8 or fewer characters long and begin with a letter. It does not have to match anything in the remote configuration. Every Session Type Name must be unique.

In the SNA Node Name field under each Session Type Name, write the name of the configured local SNA node that connects the HP 3000 with the system where the remote LU is located. The SNA Node Name, and the names of all the LUs associated with it, must be already configured in the SNANODE branch of NMMGR.

In the Mode Name field for each session type, write the mode name configured for the remote LU. The mode name configured on the HP 3000 must match the CICS MODENAME operand of the DFHTCT TYPE=SYSTEM macro.

For each session type, determine the maximum number of active sessions you will need and write that number in the Maximum Number of Sessions field. You will need as many active sessions as you will have conversations using the session type at once. The number of sessions you will need for each session type is

[(instances of TP1) x (simultaneous conversations with TP1)]
 
+ [(instances of TP2) x (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.

Under Local Dependent LU Names, list the local dependent LUs that will communicate with the remote LU. The Local Dependent LU Names you list must be configured on the node you wrote in the SNA Node Name field. The number of dependent LUs must match the number in the Maximum Number of Sessions field.

You can list the same LUs for more than one session type, but you must make sure you have enough LUs to accommodate all the sessions, of all types, that will be active at once. A dependent LU can carry on only one session at a time.

For each session type, determine the number of sessions that will be activated when the APPC subsystem is started, and write the number in the Automatically Activated Sessions field. The Automatically Activated Sessions value must be less than or equal to the Maximum Number of Sessions value.

When you have completed the Dependent LU Session Types worksheet, add up all the Automatically Activated Sessions for all the dependent and independent LU session types. If the sum is greater than 256, adjust the Automatically Activated Sessions values until the sum is less than or equal to 256. The sum of all the Automatically Activated Sessions, for all independent and dependent LU session types, must be less than or equal to 256.

Write each different Mode Name from your Independent LU Session Types worksheet and Dependent LU Session Types worksheet in a separate Mode Name field on the Mode Types worksheet.

Under each Mode Name, write the Maximum Size of RU to Send and the Maximum Size of RU to Receive. These values must match the values configured for the remote LU.

For IBM mainframe communication, these values must match the values configured in the RUSIZES parameter of the MODEENT Logmode Table macro. For AS/400 communication, these values must match the MAXLENRU value in the Mode Description on the AS/400.

For each mode type, write the Maximum Size of Send Pacing Window and the Maximum Size of Receive Pacing Window. These values must match the values configured for the remote LU.

For IBM mainframe communication, these values must match the SRCVPAC and SSNDPAC parameters of the MODEENT Logmode Table macro. For AS/400 configuration, these values must match the INPACING and OUTPACING values configured in the Mode Description on the AS/400.