Configuring the APPC Subsystem

Required. Enter the network ID of the local SNA network. For AS/400 communication, the Local Network ID should match the RMTNETID in the Controller Description of the AS/400 configuration. If the RMTNETID on the AS/400 is specified as *NETATTR, the Local Network ID in this screen must match the Local network ID in the AS/400 Network Attributes Table.

Required. The name of a new session type you want to add or a previously configured session type you want to modify. You can configure 60 session types for the APPC subsystem. A session type name can be up to 8 alphanumeric characters; the first character must be alphabetic. The session type name does not have to match anything in the local or remote configuration.

This field is required if you are adding a new session type. It is not required if you are updating the configuration for an existing session type. Enter IND for an independent LU session type or DEP for a dependent LU session type. An independent LU is used for peer-to-peer communication with a Type 2.1 node, like an AS/400, and dependent LUs are used for communication with a host node (Type 5).

For information on independent LUs, see the description of the "APPC: Independent LU Session Type Data" screen, later in this chapter. For information on dependent LUs, see the description of the "APPC: Dependent LU Session Type Data" screen, later in this chapter.

If you want to change a configured session type from independent to dependent (or from dependent to independent) you must delete the session type and reenter it.

The new name of a session type you want to rename. To rename a configured session type, enter its current name in the Session Type Name field, enter its new name in the New Name field, and press [f4] (Rename).

Required. The name of the SNA node on which the LU for this session type resides. The SNA node name must also be configured in the SNANODE branch of NMMGR. See the SNA Link/XL Node Manager's Guide for information on SNA node configuration. The SNA node name can be up to 8 alphanumeric characters; the first character must be alphabetic.

Every SNA node is a link to a remote system, so by configuring multiple session types with different SNA node names, you can connect the APPC subsystem to multiple remote systems.

Required. The name of a configured mode type. If the HP 3000 will communicate with an AS/400, the mode name must match the MODE in the Device Description for the partner LU on the AS/400. A mode name can be up to 8 alphanumeric characters; the first character must be alphabetic. The Mode Name must also be configured in the "APPC: Select Mode Type" screen. Data for each mode type is configured in the "APPC: Mode Type Data" screen, described later in this chapter. The default mode name is MODE0.

	NOTE: If you use the default mode name, MODE0, you still must configure a mode named MODE0 on the AS/400.

Required. The name of the local independent LU that will use the session type. If the HP 3000 will communicate with an AS/400, the Local LU Name must match the RMTLOCNAME in the Device Description for the partner LU on the AS/400.

The local LU must be configured on the SNA node you specified in the SNA Node Name field. SNA nodes and LUs are configured in the SNANODE branch of NMMGR. See the SNA Link/XL Node Manager's Guide for more information. A local LU name can be up to 8 alphanumeric characters; the first character must be alphabetic.

Only one local independent LU is needed for each independent LU session type, because an independent LU can conduct multiple, simultaneous sessions with the remote LU.

Required. The network ID and LU name of the remote LU with which the local LU will communicate. A fully qualified LU name is of the form NetworkID.LUName, where NetworkID and LUName are strings of up to 8 alphanumeric characters, each beginning with a letter.

If the HP 3000 will communicate with an AS/400, the NetworkID part must match the Local network ID configured in the Network Attributes Table on the AS/400, and the LUName part must match the LCLLOCNAME in the Device Description for the partner LU on the AS/400.

Required. Enables or disables parallel sessions between the specified local and remote LUs. Enter Y or N. The partner LU on the remote system must be similarly configured for parallel or single sessions.

Default: Y (parallel sessions enabled)

Required. The maximum number of APPC sessions that may be simultaneously active between the specified local and remote LUs.

If parallel sessions are disabled (Parallel Sessions = N), the Maximum Number of Sessions value must be 1.

If parallel sessions are enabled (Parallel Sessions = Y), the following restrictions apply to the Maximum Number of Sessions value:

If parallel sessions are enabled, the Maximum Number of Sessions value might be negotiated at session activation time.

Default: 8

Required. The number of sessions that will be activated automatically when the APPCCONTROL START command is issued or the APPCStart intrinsic is called. The Automatically Activated Sessions value must be less than or equal to the value in the Maximum Number of Sessions field. The sum of the Automatically Activated Sessions values for all the session types on the APPC subsystem must not exceed 256.

Default: 0

Required. The name of the SNA node on which the LUs for this session type reside. The SNA node name must also be configured in the SNANODE branch of NMMGR. See the SNA Link/XL Node Manager's Guide for information on SNA node configuration. The SNA node name can be up to 8 alphanumeric characters; the first character must be alphabetic. For troubleshooting purposes, Hewlett-Packard recommends that the SNA Node Name match the puname operand of the PU macro on the IBM host.

Every SNA node is a link to a remote system, so by configuring multiple session types with different SNA node names, you can connect the APPC subsystem to multiple remote systems.

Required. The name of a configured mode type. The mode name must match the CICS MODENAME operand of the DFHTCT TYPE=SYSTEM macro. A mode name can be up to 8 alphanumeric characters; the first character must be alphabetic. The Mode Name must also be configured in the "APPC: Select Mode Type" screen. Data for each mode type is configured in the "APPC: Mode Type Data" screen, described later in this chapter. The default mode name is MODE0.

If you use the default mode name, MODE0, dependent LU sessions of this type will use the default mode name configured for the partner LU on the IBM mainframe. The mode name configured on the IBM mainframe does not have to be MODE0. (For independent LU sessions, the mode name configured on the remote system must match the mode name configured on the HP 3000, even if MODE0 is used.)

Required. The name of the remote LU with which the dependent LUs of this session type will communicate. The Remote LU Name must match the APPLID in the Label field of the VTAM APPL definition statement. A remote LU name can be up to 8 alphanumeric characters; the first character must be alphabetic.

Only one remote LU name is configured for each session type. The local LUs for the session type are configured in the "APPC: Dependent LU List Data" screen.

Required. The maximum number of APPC sessions that may be simultaneously active between the dependent LUs of this session type and the specified remote LU. This value is not negotiated with the remote LU.

The following restrictions apply to the Maximum Number of Sessions value:

Default: 8

Required. The number of sessions that will be activated automatically when the APPCCONTROL START command is issued or the APPCStart intrinsic is called. The Automatically Activated Sessions value must be less than or equal to the value in the Maximum Number of Sessions field. The sum of the Automatically Activated Sessions for all the session types on the APPC subsystem must not exceed 256.

Default: 0

Required. Enables or disables unsolicited BINDs from the remote LU. Enter Y or N. Hewlett-Packard recommends that you disable unsolicited BINDs.

Default: N (unsolicited BINDs disabled)

The LUs you enter must be configured in the SNANODE branch of NMMGR. The SNA node with which they are associated in the SNANODE configuration must be the same one specified in the SNA Node Name field of the "APPC: Dependent LU Session Type Data" screen. See the SNA Link/XL Node Manager's Guide for information on SNA node and LU configuration. A local LU name can be up to 8 alphanumeric characters; the first character must be alphabetic. For troubleshooting purposes, Hewlett-Packard recommends that the Local LU Names match the values in the luname operand of the LU macro on the IBM host.

Required. The name of a new mode you want to configure or an existing mode whose configuration you want to modify. A mode name can be up to 8 alphanumeric characters; the first character must be alphabetic. Up to 36 mode types may be configured.

If the HP 3000 will communicate with CICS on an IBM host, the Mode Name must match the CICS MODENAME operand of the DFHTCT TYPE=SYSTEM macro. If the HP 3000 will communicate with an IBM AS/400, the Mode Name must match the MODE in the Device Description for the partner LU on the AS/400.

The default mode name MODE0 is defined internally in the APPC subsystem. Its defined RU size, for sending and receiving, is 256. The size of its pacing window, for sending and receiving, is 7. See "APPC: Mode Type Data Screen," later in this chapter, for more information.

	NOTE: If you use MODE0 for an independent LU session type that communicates with an IBM AS/400, you must configure a mode called MODE0 on the AS/400. If you use MODE0 for a dependent LU session type that communicates with an IBM mainframe, the sessions of that type actually use the default mode name configured for the partner LU on the IBM mainframe. Therefore, the mode name on the IBM mainframe does not have to be MODE0. The names MODE0 and SNASVCMG are reserved names. You cannot configure a mode with either of these names. (SNASVCMG is a mode used internally by APPC to control parallel sessions.)

The new name you want to assign to an existing mode type. To rename a mode type, enter its old name in the Mode Name field, enter its new name in the New Name field, and press [f4] (Rename).

Required. The size, in bytes, of the largest RU that can be sent by the local LU over a session with this mode type. For IBM mainframe communication, this must match the receive part of the RUSIZES parameter of the MODEENT macro in the Logmode Table. For AS/400 communication, this must match the MAXLENRU value in the Mode Description on the AS/400.

Default: 2048

Required. The size, in bytes, of the largest RU that can be received by the local LU over a session with this mode type. For IBM mainframe communication, this must match the send part of the RUSIZES parameter of the MODEENT macro in the Logmode Table. For AS/400 communication, this must match the MAXLENRU value in the Mode Description on the AS/400.

Default: 2048

Required. The maximum number of RUs the local LU can send before it must receive a response from the remote LU. For IBM mainframe communication, this must match the SRCVPAC parameter of the MODEENT macro in the Logmode Table. For AS/400 communication, this must match the INPACING value in the Mode Description on the AS/400.

Default: 7

Required. The maximum number of RUs the remote LU can send before it must receive a response from the local LU. For IBM mainframe communication, this must match the SSNDPAC parameter of the MODEENT macro in the Logmode Table. For AS/400 communication, this must match the OUTPACING value in the Mode Description on the AS/400.

Default: 7

Required. The name of a new remotely initiated TP you want to configure or an existing remotely initiated TP whose configuration you want to modify. A TP name can be up to 8 alphanumeric characters; the first character must be alphabetic. Up to 256 TP names may be configured.

The remote TP sends a TP name to indicate the local TP with which it wants a conversation. When the APPC subsystem receives the local TP name from the remote TP, it streams a job that runs the local TP. The job name for each remotely initiated local TP is configured in the "APPC: Transaction Program Data" screen.

The TP Name field must match the TP name sent by the remote TP. It must also match the LocalTPName parameter of the local TP's TPStarted intrinsic call, and it must match the LocalTPName parameter of the local TP's MCGetAllocate intrinsic call.

The new name you want to assign to a configured TP. To rename a TP, enter its old name in the TP Name field, enter its new name in the New Name field, and press [f4] (Rename).

Required. This is the 26-character location (filename.groupname.accountname) of the job file that runs the local TP. This file must not contain any lockwords. When the APPC subsystem receives an allocate request from the remote TP, it streams this job, which runs the local TP.

If you want to start the local TP manually, leave this field blank and configure N in the Automatic TP Startup field.

This parameter tells the APPC subsystem how long to wait for an allocate request from the remote TP after the local TP calls the MCGetAllocate intrinsic. If the timer expires before an allocate request arrives, the MCGetAllocate intrinsic returns with a status info value of +29. For more information on the MCGetAllocate intrinsic, see the LU 6.2 API Application Programmer's Reference Manual.

Allowable Time-out Values are as follows:

Required. This parameter tells the APPC subsystem whether to queue allocate requests from the remote TP until the current local TP process calls the MCGetAllocate intrinsic, or whether to initiate a new TP process for every allocate request that arrives from the remote TP.

Default: Y

This parameter tells the APPC subsystem whether or not to stream a job to run the local TP when an allocate request arrives from the remote TP.

	NOTE: While you are developing and debugging a remotely initiated TP, you might want to start it manually. However, after the TP has been debugged, Hewlett-Packard recommends that you allow the APPC subsystem to start it up.