APPC Subsystem on MPE XL Node Manager’s Guide HP 3000 MPE/iX Computer Systems Edition 2 Manufacturing Part Number: 30294-90007 E0692 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction APPC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LU 6.2 Verbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conversations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Reading the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4. APPC Subsystem Configuration Data Required From the Remote Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 NMMGR Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Configuration File Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Creating a Critical Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Local Programmer Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Remote Programmer Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Shutting Down the APPC Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 6. Troubleshooting the APPC Subsystem Troubleshooting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents APPC: Independent LU Session Type Data Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . APPC: Select Mode Type Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APPC: Mode Type Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Program Configuration Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMMGR Critical Summary . . . . . . . . . . . . . . . . .
Contents 8
Figures Figure 1-1. Conversation over an LU 6.2 Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Figure 1-2. The APPC Subsystem in the SNA Architecture . . . . . . . . . . . . . . . . . . . . . . . . 21 Figure 1-3. HP 3000 in an Example SNA Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Figure 4-1. Map of APPC Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Figure 4-2. Main Screen . . . . . . . . . . . . . . . . .
Figures Figure B-18. Example Network ID Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Figure B-19. NET ID Screen Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Figure B-20. Example Select Session Type Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Figure B-21. Session Types Screen Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Figure B-22.
Tables Table 2-1. Control Operator Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3-1. Control Operator Intrinsics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-1. NCP, VTAN, and CICS Corresponding Values . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-2. AS/400 Corresponding Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4-3. NMMGR Screen Index. . . . . . . . .
Tables 12
Preface This manual introduces the fundamental concepts and vocabulary of Advanced Program-To-Program Communication. It also provides the information necessary for configuration and day-to-day operation of the APPC subsystem on the MPE XL operating system. NOTE MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers.
Audience This manual is intended for the HP 3000 node manager or HP 3000 system manager who is responsible for data communications between the HP 3000 and the remote system. The node manager should have knowledge of the MPE XL operating system, should be familiar with the remote environment, and should have HP 3000 Node Manager (NM) capabilities.
Appendix D , “LU 6.2 API/XL Installation Guidelines,” describes the tasks involved in installing LU 6.2 API/XL on your system. It lists the hardware and software required on the IBM system and the HP 3000 in order to run LU 6.2 API/XL.
Related HP Publications The MPE XL node manager can find related information in these manuals: • SNA Link/XL Node Managers Guide • Using the Node Management Services Utilities • LU 6.
1 Introduction This chapter introduces the basic concepts of Advanced Program-to-Program Communication (APPC) and gives a general description of the APPC subsystem.
Introduction APPC Overview APPC Overview IBM’s Logical Unit 6.2 (LU 6.2) architecture specifies a common set of functions and protocols that application programs running on separate processors can use to communicate with each other. LU 6.2 allows for standardized program-to-program communication, which IBM calls Advanced Program-to-Program Communication, or APPC. The functions and protocols that LU 6.2 architecture specifies are called verbs. Application programs used for communicating in an LU 6.
Introduction APPC Overview Transaction Programs There are two kinds of TPs: application TPs and service TPs. • Application TPs are programs that perform services for end users. They typically use mapped conversation verbs. An application TP written with mapped conversation verbs must rely on a service TP or underlying system to perform the data formatting and error recovery functions. • Service TPs are programs that provide a service or system to other TPs.
Introduction APPC Overview Figure 1-1 Conversation over an LU 6.2 Session This section has introduced terms and concepts you need to be familiar with as you work in the APPC environment. The remainder of this chapter describes the APPC subsystem.
Introduction The APPC Subsystem The APPC Subsystem The APPC subsystem is a component of several of Hewlett-Packard's LU 6.2 products; multiple LU 6.2 products on the same node use one APPC subsystem. The APPC subsystem implements the base set of basic conversation verbs and certain option sets. These verbs are implemented as intrinsics that are accessed by the transaction programs associated with Hewlett-Packard’s LU 6.2 products.
Introduction The APPC Subsystem The SNA Link Product SNA/SDLC Link/XL is made up of a Programmable Serial Interface (PSI) card and a software module called SNA Transport. In order to connect the HP 3000 directly to multiple remote systems, or to connect multiple communication lines from the HP 3000 to a remote system, you need to install multiple copies of SNA/SDLC Link/XL. HP 3000 Node Types The APPC subsystem, together with SNA/SDLC Link/XL, allows the HP 3000 to function as either a Node Type 2.
Introduction The APPC Subsystem The LUs on an HP 3000 node can be configured as dependent LUs or independent LUs. • A dependent LU can communicate only with dependent LUs on a Type 5 (host) node. It functions as a secondary LU; that is, it cannot issue a BIND to initiate an APPC session. When a dependent LU wants an APPC session with the host, it must wait for the host to send the BIND.
Introduction The APPC Subsystem conduct sessions with LUs on two different nodes, because both nodes are connected to the HP 3000 through the same copy of SNA/SDLC Link/XL. AS/400 #2 is directly connected to the HP 3000. It is configured as a Network Node, so it can route sessions from the HP 3000 to AS/400 #3, which is not directly connected to the HP 3000. Dependent LU DEPLUA on the HP 3000 is conducting one session with dependent LU HOSTLU on the IBM host.
Introduction The APPC Subsystem Figure 1-3 HP 3000 in an Example SNA Network Chapter 1 25
Introduction The APPC Subsystem The Node Manager’s Interface to the APPC Subsystem Through the APPC subsystem, the node manager can control the network activities for LU 6.2 products. The APPC subsystem interface provides interactive control operator commands that allow the node manager to perform the following functions: • Activate and deactivate the APPC subsystem. • Control the number of active APPC sessions. • Determine the status of APPC sessions.
2 Interactive Control Operator Commands This chapter describes the APPCCONTROL commands used to control APPC subsystem functions. NOTE For all releases of the APPC subsystem that do not support Node Type 2.1, the APPCCONTROL commands are MPE commands interpreted by the MPE command interpreter. However, for the Node Type 2.1 version of the APPC subsystem, the APPC subsystem has its own command interpreter for APPCCONTROL commands. For the Node Type 2.
Interactive Control Operator Commands Table 2-1 lists the APPC subsystem control operator commands. Table 2-1 Control Operator Commands APPCCONTROL DUMP Dumps APPC subsystem internal data structures to dump file APPCDPxx.APPC.SYS. APPCCONTROL HELP Displays help text for APPCCONTROL commands. APPCCONTROL PERFORMANCE Displays session statistics and performance-related data, if statistics gathering is enabled.
Interactive Control Operator Commands APPCCONTROL DUMP APPCCONTROL DUMP Dumps APPC subsystem internal data structures to dump file APPCDPxx.APPC.SYS. Syntax APPCCONTROL DUMP Description APPCCONTROL DUMP creates a dump of the APPC subsystem internal data structures. The name of the dump file it creates is APPCDPxx.APPC.SYS, where xx is a number from 00 through 49. Only 25 dump files can exist on disk at one time.
Interactive Control Operator Commands APPCCONTROL HELP APPCCONTROL HELP Displays help text for APPCCONTROL commands. Syntax APPCCONTROL HELP Description Type APPCCONTROL HELP to get online help for APPCCONTROL commands. NOTE The MPE command HELP APPCCONTROL will not work, because the APPCCONTROL commands are not interpreted by the MPE command interpreter. If you want to print the output from the APPCCONTROL HELP command, you can redirect the output to a disk file and then print the file.
Interactive Control Operator Commands APPCCONTROL PERFORMANCE APPCCONTROL PERFORMANCE Displays session statistics and performance-related data, if the gathering of performance statistics has been enabled. Syntax APPCCONTROL PERF[ORMANCE] [;STYPE=Session Type Name] [;SID=Session ID] Parameters Session Type Name An active session type name. Performance statistics are displayed for all active sessions of the session type specified.
Interactive Control Operator Commands APPCCONTROL PERFORMANCE The APPCCONTROL PERFORMANCE display pauses at the end of every screen of data. To see the next screen of data, press [RETURN]. NOTE You must enable the gathering of performance statistics before issuing the APPCCONTROL PERFORMANCE command, or no statistics will be available for display.
Interactive Control Operator Commands APPCCONTROL PERFORMANCE Examples In this example, the APPCCONTROL PERFORMANCE command was issued for the independent session type SESS1. Two sessions of session type SESS1 are active on the independent LU INDLU1.
Interactive Control Operator Commands APPCCONTROL PERFORMANCE SESS3 , LU = DEPLU8 , NODE = IBMNODE , SID = 2298 Session Started : FRI, JUN 20, 1990, 2:37 AM Duration : 30 minutes 2 seconds Bytes Sent = 1011 Bytes Received = 5 RUs Sent = 5 RUs Received = 1 Negative Responses Sent = 0 Negative Responses Received = 0 Avg. Remote Response Time (msec) = 0 Avg. CONFIRM Time (msec) = 0 Conversations Started = 0 Avg. bytes per Conversation = 0 Avg.
Interactive Control Operator Commands APPCCONTROL PERFORMANCE Bytes Received The total number of bytes received since session initiation. Bytes Sent The total number of bytes sent since session initiation. RUs Sent The total number of RUs sent since session initiation. RUs Received The total number RUs received since session initiation. Negative Responses Sent The total number of negative responses sent over this session since session initiation.
Interactive Control Operator Commands APPCCONTROL PERFORMANCEOFF APPCCONTROL PERFORMANCEOFF Disables the gathering of session statistics and performance-related data. Syntax APPCCONTROL PERF[ORMANCE]OFF Description The APPCCONTROL PERFORMANCEOFF command disables the gathering of APPC subsystem performance statistics. When the APPC subsystem starts up, statistics gathering is disabled by default.
Interactive Control Operator Commands APPCCONTROL PERFORMANCEON APPCCONTROL PERFORMANCEON Enables the gathering of session statistics and performance-related data. Syntax APPCCONTROL PERF[ORMANCE]ON Description The APPCCONTROL PERFORMANCEON command enables the gathering of APPC subsystem performance statistics. NOTE The APPCCONTROL PERFORMANCEON command does not display performance statistics; it only enables the gathering of performance statistics.
Interactive Control Operator Commands APPCCONTROL SESSIONS APPCCONTROL SESSIONS Controls the number of active APPC sessions of a specified APPC session type. Syntax APPCCONTROL SESS[IONS] ;STYPE=Session Type Name ;LIMIT=New Session Limit Parameters Session Type Name Required. A session type that is configured in the APPC subsystem configuration file. New Session Limit Required. The new number of active sessions for the session type. The following restrictions apply to the new session limit: 1.
Interactive Control Operator Commands APPCCONTROL SESSIONS Using the APPCCONTROL SESSIONS command to reduce the session limit for a session type causes an orderly termination of the sessions affected; termination will not occur until conversations on the affected sessions have ended. All current conversations for the affected sessions are allowed to complete, but no new conversations are allocated for those sessions.
Interactive Control Operator Commands APPCCONTROL START APPCCONTROL START Activates the APPC subsystem. Any APPC sessions configured for automatic activation will be established when the subsystem is activated Syntax APPCCONTROL START [;TRACEON=tracing option] [;TFILENAME=trace file name] [;TFILESIZE=record count] [;PERFON=performance option] [;ERROPT=error option] Parameters tracing option Enables or disables APPC subsystem internal state tracing.
Interactive Control Operator Commands APPCCONTROL START command. To start a new trace file without bringing down the APPC subsystem, turn tracing off and back on again with the APPCCONTROL TRACEOFF and APPCCONTROL TRACEON commands. record count A decimal number, from 0 through 32767, specifying the trace file size, in 128-word records. Once the record count has been reached, trace records are overwritten starting at the beginning of the file. Default: 4096.
Interactive Control Operator Commands APPCCONTROL START Hewlett-Packard recommends that you specify ERROPT=SUB so that the rest of the system can remain active when there is a problem with the APPC subsystem. However, if an APPC subsystem problem cannot be found, your HP representative may ask you to specify ERROPT=SYS so that a system dump is taken when the internal error occurs.
Interactive Control Operator Commands APPCCONTROL STATUS APPCCONTROL STATUS Displays the status of the APPC subsystem. Syntax APPCCONTROL STAT[US] [;STYPE=Session Type Name] Parameters Session Type Name The name of a session type configured in the APPC subsystem configuration file. Status information will be displayed for all APPC sessions of the specified type.
Interactive Control Operator Commands APPCCONTROL STATUS If you want to print the output from the APPCCONTROL STATUS command, you can redirect the output to a disk file and then print the file. Redirecting the output creates a temporary file, so you must save the file to disk before you can print it.
Interactive Control Operator Commands APPCCONTROL STATUS --------------------------------------Independent LU Session Type : STYPE2 --------------------------------------Number of Active Sessions : Number of Queued Session Requests : Local LU -------INDLU1 SNA Node -------SNANODE Session ID LFSID -------------* No active sessions 0 0 Remote LU ----------------NET1.
Interactive Control Operator Commands APPCCONTROL STATUS In the following example, the APPCCONTROL STATUS command was issued for one independent session type: STYPE1. The display includes information about the active sessions of that session type and the transaction programs running on those sessions. :APPCCONTROL STATUS;STYPE=SESS1 Internal Trace File : NMTC0020.PUB.
Interactive Control Operator Commands APPCCONTROL STATUS Reading the Display Each of the columns in the example status display is described below: Number of Active Sessions The current number of active or pending sessions for the session type. This number should be equal to the configured Automatically Activated Sessions value at subsystem startup, or, if you have issued the APPCCONTROL SESSIONS command to raise the session limit, it should be equal to the number you specified in the command.
Interactive Control Operator Commands APPCCONTROL STATUS Session ID The unique identification number given to each session activated for the session type. LFSID Local Form Session Identifier. This number identifies the session to the SNA link product. The SNACONTROL STATUS command, which displays the status of the SNA link product, identifies each LU-LU session by LFSID. For more information on the SNACONTROL STATUS command, see the SNA Link/XL Node Manager’s Guide. State The state of a session.
Interactive Control Operator Commands APPCCONTROL STATUS TP ID The unique identification number of an active transaction program process. R When the TPID is followed by R, the transaction program was started up by the remote system. Program File Name The fully qualified file name for an active transaction program. TP Name The configured transaction program name. # Conv. The number of conversations being conducted by an active TP process.
Interactive Control Operator Commands APPCCONTROL STOP APPCCONTROL STOP Deactivates all APPC sessions, writes out performance data to the log file (if performance statistics gathering is enabled and APPC subsystem logging is configured), and brings down the APPC subsystem. Syntax APPCCONTROL STOP [;TYPE=StopType] Parameters StopType Indicates the manner in which you wish the APPC subsystem to be shut down. Valid choices are as follows: K[ILL] Immediate shutdown of the APPC subsystem.
Interactive Control Operator Commands APPCCONTROL STOP Description Try to use APPCCONTROL STOP with the TYPE=Q parameter; this will ensure orderly shutdown of the APPC subsystem. If it is not possible to wait for current conversations to complete, escalate the shutdown type to TYPE=P (protocol shutdown). A TYPE=P shutdown ensures that resources used by the APPC subsystem for conversations are successfully returned to the system before shutdown. If TYPE=P does not work, use TYPE=K.
Interactive Control Operator Commands APPCCONTROL STOPSESSION APPCCONTROL STOPSESSION Terminates the session with the specified Session ID. Syntax APPCCONTROL STOPSESS[ION] ;SID=Session ID Parameters Session ID Required. The unique session identification number of the session you want to terminate. You can obtain the Session ID by issuing the APPCCONTROL STATUS command. Description The APPCCONTROL STOPSESSION command is used to terminate a single APPC session.
Interactive Control Operator Commands APPCCONTROL TRACEOFF APPCCONTROL TRACEOFF Disables internal state tracing for the APPC subsystem. Syntax APPCCONTROL TRACEOFF Description The APPCCONTROL TRACEOFF command disables internal state tracing. Internal state tracing records significant state changes, events and data to a disk file. The disk file is closed when tracing is disabled. When the APPC subsystem is activated, internal tracing is disabled by default.
Interactive Control Operator Commands APPCCONTROL TRACEON APPCCONTROL TRACEON Enables internal state tracing for the APPC subsystem. Syntax APPCCONTROL TRACEON [;TFILENAME=trace file name] [;TFILESIZE=record count] Parameters trace file name An 8-character name consisting of alphanumeric characters and beginning with a letter. A trace file with this name will be created in the group and account from which the APPCCONTROL TRACEON command was issued. The default trace file name is NMTCxxxx.PUB.
Interactive Control Operator Commands APPCCONTROL TRACEON When the APPC subsystem is activated, internal tracing is disabled by default. It can be enabled at startup by specifying TRACEON = YES in the APPCCONTROL START command. See the description of APPCCONTROL START, earlier in this chapter. If you start up the APPC subsystem programmatically, you can enable internal tracing by setting the TraceOn parameter of the APPCStart intrinsic to 1.
Interactive Control Operator Commands APPCCONTROL VERSION APPCCONTROL VERSION Displays software module version information for the APPC subsystem and LU 6.2 products. Syntax APPCCONTROL VERSION Description The APPCCONTROL VERSION command is used to obtain the versions of LU 6.2 product modules that are currently installed on the system. The user will be informed if module versions do not match or if modules are missing, which indicates that the subsystem has been installed incorrectly.
Interactive Control Operator Commands APPCCONTROL VERSION :APPCCONTROL VERSION LU 6.2 API XL procedure: Catalog file: HP30294 module versions: LU 6.2 API APIVERS CATAPI.PUB.SYS Version: Version: B0000200 B0000200 HP30294 overall version = B.00.
Interactive Control Operator Commands APPCCONTROL VERSION 58 Chapter 2
3 Control Operator Intrinsics Control operator intrinsics are subroutines that you can call from inside programs written in COBOL II, Pascal, C, or Transact. They have the same functions as the interactive control operator commands described in Chapter 2 , “Interactive Control Operator Commands.” You must have Node Manager (NM) capability to call control operator intrinsics. You must declare intrinsics with the keyword INTRINSIC.
Control Operator Intrinsics >0 Execution was successful, but a warning condition was encountered. The positive value corresponds to a warning message in set 11 of the APPC message catalog, CATAPPC.APPC.SYS. APPC subsystem warning messages are followed by (APPCWARN xxxx), where xxxx is the message number. The subsystem field (bits 16–31) may contain the following values: 0 The intrinsic executed successfully and there are no messages.
Control Operator Intrinsics APPCSessions APPCSessions Controls the number of active sessions of a specified APPC session type. Syntax CA I16V I32 APPCSessions (SessionType, NewLimit, ReturnCode) Parameters SessionType Required. Character array; input. The name of the session type whose session limit you want to change. This must be a session type name configured in the APPC subsystem configuration file. SessionType is an 8-character ASCII array, left justified and padded with blanks. NewLimit Required.
Control Operator Intrinsics APPCSessions and the actions you should take to resolve any problems. Description The APPCSessions intrinsic changes the number of active sessions for a specified session type. The new session limit for the session type is in effect only while the APPC subsystem is currently active; the APPCSessions intrinsic does not update the APPC configuration file.
Control Operator Intrinsics APPCStart APPCStart Activates the APPC subsystem and all APPC sessions configured for automatic activation. Syntax I32 I16V CA I16V APPCStart (ReturnCode [,TraceOn] [,TFileName] [,TFileSize] I16V I16V [,PerformanceOn] [,Erropt]) Parameters ReturnCode Required. 32-bit signed integer; output. Indicates the result of the intrinsic execution.
Control Operator Intrinsics APPCStart Default: 0 (tracing disabled) TFileName Optional. 8-character ASCII array, left justified and padded with blanks. This parameter specifies the name of the trace file, which will be created in the logon group and account of the user who ran the calling program. A valid name is up to 8 alphanumeric characters long and begins with a letter. The default trace file name is NMTCxxxx.PUB.SYS, where xxxx is a number from 0000 through 9999.
Control Operator Intrinsics APPCStart Erropt Optional. 16-bit signed integer; input. This parameter specifies the action taken when an irrecoverable internal error occurs. Possible values are as follows: 1 System shutdown. The system is brought down when an irrecoverable error occurs. 2 Subsystem shutdown. Only the APPC subsystem is brought down when an irrecoverable error occurs.
Control Operator Intrinsics APPCStart Return Codes 0 = Successful completion -1002 = Parameter error -1004 = Too many parameters specified -1005 = Syntax error -1006 = Redundant parameter -1007 = Missing parameter after equal sign -1008 = Missing or invalid delimiter -1009 = Parameter out of bounds -1010 = User missing NM capability -1011 = Invalid value for Erropt parameter -1012 = Invalid value for TraceOn parameter -1013 = Invalid value for TFileSize parameter -1014 = Invalid value for PerformanceOn pa
Control Operator Intrinsics APPCStatus APPCStatus Indicates whether the APPC subsystem is active. Syntax I16 I32 (SubsystemState, ReturnCode) APPCStatus Parameters SubsystemState Required. 16-bit integer; output. Indicates the current state of the APPC subsystem. Possible values are as follows: ReturnCode 1 The APPC subsystem is inactive. 2 APPC subsystem startup is pending. 3 The APPC subsystem is active. 4 The APPC subsystem is shutting down. Required. 32-bit signed integer; output.
Control Operator Intrinsics APPCStatus Return Codes 0 -1002 -1004 -1005 -1006 -1007 -1008 -1009 -1010 -1065 -1072 68 = = = = = = = = = = = Successful completion Parameter error Too many parameters specified Syntax error Redundant parameter Missing parameter after equal sign Missing or invalid delimiter Parameter out of bounds User missing NM capability Control Operator internal error APPC subsystem not active Chapter 3
Control Operator Intrinsics APPCStop APPCStop Deactivates the APPC subsystem and all active APPC sessions. Syntax I32 I16V APPCStop (ReturnCode [,StopType]) Parameters ReturnCode Required. 32-bit signed integer; output. Indicates the result of the intrinsic execution. The ReturnCode consists of two 16-bit fields: an information field, containing the number of an APPC warning or error message, and a subsystem field, containing the number of the subsystem that generated the message.
Control Operator Intrinsics APPCStop be brought down until the conversation using it has been deallocated. When the conversation has completed, the session will be terminated. TPs will not be terminated. Default: 3 (Quiesce) Description The APPCStop intrinsic is used to shut down the APPC subsystem by deactivating all active APPC sessions. If possible, you should specify a StopType of 3 (Quiesce).
4 APPC Subsystem Configuration This chapter describes how to use the NM configuration manager (NMMGR) to create or modify a configuration for the APPC subsystem. Appendix C , “Configuration Worksheets,” provides configuration worksheets to help you plan APPC subsystem configuration. Step-by-step instructions for completing the worksheets are included in Appendix C , “Configuration Worksheets.
APPC Subsystem Configuration Data Required From the Remote Configuration Data Required From the Remote Configuration Data in the APPC subsystem configuration must correspond to information from the remote configuration. Before using NMMGR, you should consult with the remote system programmer to ensure that the information in the following tables is consistent between the HP 3000 configuration and the remote system configuration. If you are configuring the HP 3000 as a Node Type 2.
APPC Subsystem Configuration Data Required From the Remote Configuration Though these two items have no corollaries in the HP 3000 configuration, you will need them when communicating with people at the remote site. If you are configuring the HP 3000 as a Node Type 2.1 that communicates with an AS/400 (Type 2.1 node), Table 4-2 lists the local and remote configuration items that must agree.
APPC Subsystem Configuration NMMGR Configuration Overview NMMGR Configuration Overview Use NMMGR to create or modify an APPC subsystem configuration. The NMMGR utility is described in Using the Node Management Services Utilities; if you are not familiar with NMMGR, you should read that manual before continuing. You configure the APPC subsystem by defining the network in which it will operate, the nodes and LUs that will communicate over APPC sessions and the properties of the APPC sessions.
APPC Subsystem Configuration NMMGR Configuration Overview Figure 4-1 Map of APPC Configuration Screens Configuration File Validation NMMGR has a utility for validating the configuration file to ensure that the APPC subsystem configuration data is logically and syntactically correct. It also checks the APPC subsystem configuration against the SNA node (SNA/SDLC Link/XL) configuration for correctness and consistency.
APPC Subsystem Configuration NMMGR Configuration Overview Creating a Critical Summary NMMGR allows you to create a summary of critical APPC subsystem configuration data. The critical summary is a printout of the APPC subsystem data in the configuration file. It can be used to check current contents of the configuration file to determine whether the configuration is correct. The critical summary is generated through NMMGR; see Using the Node Management Services Utilities.
APPC Subsystem Configuration Configuring the APPC Subsystem Configuring the APPC Subsystem This section describes the NMMGR screens used for APPC subsystem configuration. NOTE NMMGR will operate on a file of any legal name. However, the SNA node will not activate unless the configuration file is named NMCONFIG.PUB.SYS. Main Screen The NMMGR “Main” screen lets you select the category of network subsystems you want to configure. The “Main” screen is shown in Figure 4-2.
APPC Subsystem Configuration Configuring the APPC Subsystem HP-IBM Configuration Screen From the “HP-IBM Configuration” screen, shown in Figure 4-3, you can select the SNA Service or subsystem you want to configure. Figure 4-3 HP-IBM Configuration Screen To get to the APPC subsystem configuration screens, first press [f6] (Next Key Labels), and then press [f2] (Go To APPC).
APPC Subsystem Configuration Configuring the APPC Subsystem APPC Configuration Screen The “APPC Configuration” screen, shown in Figure 4-4, allows you to choose among the four branches of the APPC subsystem configuration: Network ID, Session Types, Mode Types, and TPs. Figure 4-4 APPC Configuration Screen The network ID must be configured only if the HP 3000 will operate as a Node Type 2.1 in a peer-to-peer environment. Press [f1] (Go To NET ID) to get to the “APPC: Network ID Data” screen.
APPC Subsystem Configuration Configuring the APPC Subsystem APPC: Network ID Data Screen The “APPC: Network ID Data” screen, shown in Figure 4-5, is where you configure the name of the local SNA network. Configure the network ID only if your HP 3000 will operate as a Node Type 2.1 in a peer-to-peer environment. When you have finished entering the network ID, press [f6] (Save Data), and then press [f8] (Prior Screen) to return to the “APPC Configuration” screen.
APPC Subsystem Configuration Configuring the APPC Subsystem APPC: Select Session Type Screen In the “APPC: Select Session Type” screen, shown in Figure 4-6, you enter the name of a new session type you want to configure or a previously configured session type you want to modify. A session type is a grouping of a remote LU, one or more local LUs, and a mode name.
APPC Subsystem Configuration Configuring the APPC Subsystem Fields Session Type Name 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.
APPC Subsystem Configuration Configuring the APPC Subsystem An independent LU can communicate with another independent LU on a Type 2.1 node, like an IBM AS/400. The APPC subsystem allows the HP 3000 to act as a Type 2.1 node in a peer-to-peer environment, where two independent LUs can establish an APPC session between themselves without the supervision of the SSCP on a host node.
APPC Subsystem Configuration Configuring the APPC Subsystem Fields SNA Node Name 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.
APPC Subsystem Configuration Configuring the APPC Subsystem Fully Qualified Remote LU Name 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.
APPC Subsystem Configuration Configuring the APPC Subsystem 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: 1. The maximum number of simultaneously active sessions for an independent session type is 256. 2. The maximum number of simultaneously active sessions for the whole APPC subsystem is 256. 3.
APPC Subsystem Configuration Configuring the APPC Subsystem Figure 4-8 Possible and Impossible Configurations APPC: Dependent LU Session Type Data Screen The “APPC: Dependent LU Session Type Data” screen, shown in Figure 4-9, is used to configure session types for dependent LUs. Dependent LUs can communicate only with other dependent LUs on a host (Type 5) node. They always function as secondary LUs; that is, they cannot initiate a session by sending a BIND.
APPC Subsystem Configuration Configuring the APPC Subsystem Figure 4-9 Dependent LU Session Type Data Screen Fields SNA Node Name 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.
APPC Subsystem Configuration Configuring the APPC Subsystem “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.
APPC Subsystem Configuration Configuring the APPC Subsystem Automatically Activated Sessions 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.
APPC Subsystem Configuration Configuring the APPC Subsystem After you enter the LU names into the “APPC: Dependent LU List Data” screen, press [f6] (Save Data), and then press [f8] (Prior Screen) twice to get back to the “APPC: Select Session Type” screen. From there, you can configure another session type, or you can press [f8] (Prior Screen) again to get back to the “APPC Configuration” screen.
APPC Subsystem Configuration Configuring the APPC Subsystem APPC: Select Mode Type Screen You configure mode types through the “APPC: Select Mode Type” screen, shown in Figure 4-11, and the “APPC: Mode Type Data” screen, shown in Figure 4-12. A mode type determines the following four characteristics of a session type: 1. The maximum size of RUs sent by the local LU. 2. The maximum size of RUs received by the local LU. 3.
APPC Subsystem Configuration Configuring the APPC Subsystem 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.
APPC Subsystem Configuration Configuring the APPC Subsystem Figure 4-12 Mode Type Data Screen Fields Maximum RU Size (Send) 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.
APPC Subsystem Configuration Configuring the APPC Subsystem 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 Maximum Pacing Window (Receive) 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.
APPC Subsystem Configuration Configuring the APPC Subsystem Fields TP Name 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.
APPC Subsystem Configuration Configuring the APPC Subsystem Figure 4-14 Startup of Remotely Initiated TP APPC: Transaction Program Data Screen The “APPC: Transaction Program Data” screen, shown in Figure 4-15, indicates the following things: 1. The location of the job file used to run the TP. 2. How long the local TP’s MCGetAllocate intrinsic call will wait for an allocate request from the remote TP before timing out. 3.
APPC Subsystem Configuration Configuring the APPC Subsystem Figure 4-15 Transaction Program Data Screen Fields Job Name 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.
APPC Subsystem Configuration Configuring the APPC Subsystem 0–480 minutes If Queued Allocate Requests = N Default: 5 minutes, if Queued Allocate Requests = Y 0 minutes, if Queued Allocate Requests = N Queued Allocate Requests? 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.
APPC Subsystem Configuration Configuring the APPC Subsystem Automatic TP Startup? 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. Y The APPC subsystem will start the local TP automatically by streaming a job when it receives an allocate request from the remote TP. If the local TP is configured to accept queued allocate requests, the APPC subsystem will stream the job only once.
APPC Subsystem Configuration Configuring the APPC Subsystem Figure 4-16 Receiving Queued Allocate Requests Chapter 4 101
APPC Subsystem Configuration Planning APPC Configuration Planning APPC Configuration 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.
APPC Subsystem Configuration Planning APPC Configuration 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.
APPC Subsystem Configuration Planning APPC Configuration 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.
APPC Subsystem Configuration Configuration Illustrations Configuration Illustrations This section contains network diagrams for three example configurations. The first illustration, Figure 4-17, shows one dependent LU session type. The three screens pictured at the bottom of the illustration are the APPC configuration screens used to configure a dependent LU session type. The dashed lines show the correspondence between configuration items and software entities in the SNA network.
APPC Subsystem Configuration Configuration Illustrations The second illustration, Figure 4-18, shows three dependent LU session types using the same SNA node. Session types DEPSESS1 and DEPSESS2 share the same five LUs, each of which can communicate with either copy of CICS on the remote system. At subsystem startup, sessions are activated on all five LUs: two of type DEPSESS1 and three of type DEPSESS2.
APPC Subsystem Configuration Configuration Illustrations The third illustration, Figure 4-19, shows four session types using three SNA nodes. The dotted lines represent APPC sessions that are activated at subsystem startup. Figure 4-19 Example Configuration, Four Session Types Figure 4-19 shows two SNA networks. AS/400 #2 has intermediate routing capabilities that allow it to connect the HP 3000 in network 1 with AS/400 #3 in network 2.
APPC Subsystem Configuration Configuration Illustrations The APPC subsystem is using three SNA nodes on the HP 3000: HOSTPU, AS4001, and AS4002. Each connection to a remote system requires a separate configured SNA node and a separate copy of SNA/SDLC Link/XL. Independent LU HPINDLU1 on the HP 3000 is configured to communicate with two independent LUs on AS/400 #1: GREENLU and BLUELU. One session type is configured for each remote independent LU.
APPC Subsystem Configuration Coordinating with the TP Programmer Coordinating with the TP Programmer To use sessions, each local TP must pass the name of a configured session type to the APPC subsystem. After you have completed APPC configuration, you must tell the TP programmers the session type names to use for development and run time. For information on TP development, see the LU 6.2 API Application Programmer’s Reference Manual.
APPC Subsystem Configuration Migrating an APPC Configuration Migrating an APPC Configuration If you are migrating your APPC subsystem configuration from MPE V to MPE XL, or from an earlier version of MPE XL to a version that supports Node Type 2.1, run the NMS utility NMMGRVER.PUB.SYS, described in Using the Node Management Services Utilities. NMMGRVER will convert your old configuration to a configuration that is compatible with your new software.
5 Managing the APPC Subsystem This chapter contains the following sections: • Activating the APPC Subsystem tells you how to start up the APPC subsystem and all APPC sessions configured for automatic activation. • Managing APPC Sessions tells you how to check the status of the APPC subsystem and how to activate and deactivate APPC sessions during run time. • Establishing Conversations tells you how to establish remotely and locally initiated conversations between transaction programs.
Managing the APPC Subsystem Activating the APPC Subsystem Activating the APPC Subsystem The subsystem is activated by issuing the APPCCONTROL START command. The APPCCONTROL START command can be issued from any user terminal by anyone with NM capability. Once the command is issued, the APPC subsystem and all APPC sessions configured for automatic activation will come up. (Automatic activation is discussed in Chapter 4 , “APPC Subsystem Configuration,” “APPC Subsystem Configuration.
Managing the APPC Subsystem Activating the APPC Subsystem If, for any reason, the APPC subsystem is unable to execute the APPCCONTROL START command, an error message will be displayed on the terminal from which the command was issued. Appendix A , “Messages,” lists APPC subsystem error messages, their meanings, and the actions you should take to resolve errors.
Managing the APPC Subsystem Managing APPC Sessions Managing APPC Sessions This section discusses the APPCCONTROL STATUS and APPCCONTROL SESSIONS commands. You issue the APPCCONTROL STATUS command to check the status of the APPC subsystem during run time. You use the APPCCONTROL SESSIONS command to control the number of active APPC sessions. Checking APPC Subsystem Status At subsystem startup, the number and characteristics of active sessions are determined by the parameters in the APPC configuration file.
Managing the APPC Subsystem Managing APPC Sessions :APPCCONTROL STATUS Internal Trace File : NMTC0020.PUB.
Managing the APPC Subsystem Managing APPC Sessions In the following example, the APPCCONTROL STATUS command is issued with the parameter STYPE=INDSESS2, so information is displayed for only one session type. Session type INDSESS2 is an independent session type with two active sessions. The identical TPIDs show that both sessions are being used by one instance of the same TP; that is, one instance of the TP is conducting two conversations simultaneously, over two APPC sessions.
Managing the APPC Subsystem Managing APPC Sessions Controlling the Number of Sessions The APPC subsystem supports up to 256 active APPC sessions. By issuing the APPCCONTROL SESSIONS command, you can vary the number of active sessions and reapportion active sessions among different session types. The following APPCCONTROL STATUS display shows the status of an example APPC session type at subsystem startup.
Managing the APPC Subsystem Managing APPC Sessions value. The Current value is the new session limit after you issue the APPCCONTROL SESSIONS command. If you issue the APPCCONTROL SESSIONS command to raise the session limit for an independent LU session type with parallel sessions, the limit you specify in the command might be negotiated with the remote LU. Therefore, after the command has executed, the new session limit might not be the same limit you specified in the command.
Managing the APPC Subsystem Managing APPC Sessions One session is active but idle; it is not being used for a conversation, so its TP ID field is blank. If two more TP processes request sessions, the first TP process will be given the idle session (the one with no TP ID listed), and the second session request will be queued to wait for an available session.
Managing the APPC Subsystem Managing APPC Sessions -------------------------------------Independent LU Session Type : INDSESS1 -------------------------------------Number of Active Sessions : Number of Queued Session Requests : Local LU -------INDLU1 Session ID ---------26 27 28 29 30 SNA Node -------AS400PU LFSID ----0101 1 0102 1 0103 1 0104 1 0105 1 5 <$&shade 11-1> 0 Session Limits Remote LU Mode Maximum Current ---------------------------- ------NET1.
Managing the APPC Subsystem Managing APPC Sessions -------------------------------------Independent LU Session Type : INDSESS1 -------------------------------------Number of Active Sessions : Number of Queued Session Requests : Local LU -------INDLU1 Session ID ---------26 28 29 SNA Node -------AS400PU LFSID ----0101 1 0103 1 0104 1 3 0 Remote LU ----------------NET1.
Managing the APPC Subsystem Establishing Conversations Establishing Conversations 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.
Managing the APPC Subsystem Establishing Conversations Local Programmer Tasks To prepare for a locally initiated conversation, the local TP programmer 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. 3. Code the name of the session type into the local TP.
Managing the APPC Subsystem Establishing Conversations Node Manager Tasks To prepare for a remotely initiated conversation, you must do the following: 1. 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. 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.
Managing the APPC Subsystem Establishing Conversations 8. 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.
Managing the APPC Subsystem Establishing Conversations 9. Tell the node manager whether to configure the TP for manual or automatic startup. Remote Programmer Tasks To prepare a remote program to initiate a conversation with a TP on the HP 3000, 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.
Managing the APPC Subsystem Shutting Down the APPC Subsystem Shutting Down the APPC Subsystem You shut down the APPC subsystem by issuing the APPCCONTROL STOP command. Whenever the APPC subsystem shuts down, performance statistics are logged for all sessions that were active at the time of the shutdown (if logging is configured and statistics gathering is enabled). The APPCCONTROL STOP command shuts down the APPC subsystem by deactivating all APPC sessions.
Managing the APPC Subsystem Shutting Down the APPC Subsystem 128 Chapter 5
6 Troubleshooting the APPC Subsystem This chapter gives you troubleshooting procedures to follow when you suspect a problem with the APPC subsystem. It should be used with the SNA Link/XL Node Manager’s Guide. This chapter contains the following sections: • Troubleshooting tools. This section describes the tools available to the APPC subsystem node manager. • Startup problems. These problems commonly occur during installation and configuration. • Run-time problems.
Troubleshooting the APPC Subsystem Troubleshooting Tools Troubleshooting Tools This section describes the available troubleshooting tools and tells you how to use them to troubleshoot the APPC subsystem.
Troubleshooting the APPC Subsystem Troubleshooting Tools A new trace file is created every time APPC subsystem internal tracing is turned on, at subsystem startup or during run time. To start a new trace file during run time, turn tracing off with the APPCCONTROL TRACEOFF command, and then turn it back on again with the APPCCONTROL TRACEON command. NOTE When storing trace files to tape for analysis, be sure to include all the files on disk at the time the problem occurred.
Troubleshooting the APPC Subsystem Troubleshooting Tools APPC Subsystem Messages and Return Codes Appendix A , “Messages,” contains a complete list of all APPC subsystem messages and return codes. It describes the cause of each message and any actions you should take to resolve a problem. The APPC subsystem generates the following kinds of messages: • Subsystem startup messages are returned to the terminal from which the APPCCONTROL START command is issued.
Troubleshooting the APPC Subsystem Troubleshooting Tools The SNACONTROL STATUS Command To get the status of the local SNA node and LU, issue the SNACONTROL STATUS command. This command will tell you whether SNA Transport is active and will display the status of the PU-SSCP sessions and LU-SSCP sessions. NOTE For Type 2.1 nodes, the SNACONTROL STATUS command always lists the SESSION STATE as RESET (unless Node 2.1 Dependent LU Support = Y in the “SNA Node Configuration: PU Data” screen).
Troubleshooting the APPC Subsystem Startup Problems Startup Problems This section gives some suggestions for troubleshooting startup problems. It is divided into two sections: • Link and Node Level Problems • APPC Subsystem Problems Check that the recommended logging classes have been enabled at the system console through NMMGR. See the SNA Link/XL Node Manager’s Guide for Hewlett-Packard’s recommended logging configuration.
Troubleshooting the APPC Subsystem Startup Problems SNA node in the APPC subsystem configuration and the SNA node configuration. • Node Type 2.1. If the HP 3000 is configured to communicate with a peer node, like an IBM AS/400, make sure the Node Type in the “SNA Node Configuration: PU Data” screen is configured as 2.1. • ID BLK and ID NUM.
Troubleshooting the APPC Subsystem Startup Problems 6. Check for hardware problems. Check that all hardware is installed properly and working correctly. Make sure that the proper cabling has been installed and connected and that the modems are turned on and working properly. Many problems are related to such things as incompatible modems, bad phone lines and cables and so forth. 7. Check for activity on the line.
Troubleshooting the APPC Subsystem Startup Problems 2. Verify that the HP 3000 has been configured properly. Check the following items: • LU session types. Make sure the independent LU session types are configured to use independent LUs on Type 2.1 nodes. Make sure the dependent LU session types are configured to use dependent LUs on Type 2.0 nodes or on Type 2.1 nodes with dependent LU support. • Local LU Name of independent LU.
Troubleshooting the APPC Subsystem Startup Problems • Maximum RU size. The Maximum RU Size (Send and Receive) configured in the “APPC: Mode Type Data” screen, must match the maximum RU size configured for the remote LU. The maximum RU size for LUs on an IBM mainframe is configured in the RUSIZES parameter of the MODEENT in the Logmode Table. The maximum RU size for LUs on an AS/400 is configured in the MAXLENRU field of the Mode Description.
Troubleshooting the APPC Subsystem Run-Time Problems Run-Time Problems This section gives some suggestions for troubleshooting run-time problems. It is divided into the following sections: • Lost Data • APPC Subsystem Hang • APPC Subsystem Failure • Transaction Program Hang • Remotely Initiated TP Failure • System Hang or Failure Lost Data If data loss occurs at either the HP 3000 side or the remote side, follow these steps: 1. Get a description of what is missing.
Troubleshooting the APPC Subsystem Run-Time Problems If the APPC: Subsystem Stopped message does not appear, or if the APPCCONTROL STATUS display indicates that APPC sessions are still active, then the APPC subsystem is probably hung. Follow the procedure below to collect all needed diagnostic information and bring the subsystem down.
Troubleshooting the APPC Subsystem Run-Time Problems 2. Find the APPC dump if there is one. APPC dumps are created automatically in certain cases. The following message should appear on the console, containing the name of the dump file: APPC: Object dumped to file APPCDP03 (APPCLOG 29). The file will be called APPCDPxx.APPC.SYS where xx is a number from 00 through 49. To be sure you collect the most recent file, store off all files with the name APPCDPxx. 3.
Troubleshooting the APPC Subsystem Run-Time Problems Remotely Initiated TP Failure If a remotely initiated TP that worked on a previous version of APPC fails after you install a new version, get a user trace of the TP and check the status info value returned on the MCGetAllocate intrinsic. If the status info value is -1008, do the following things: 1. Modify the local TP so that it passes the LocalTPName as an input parameter to the MCGetAllocate intrinsic.
Troubleshooting the APPC Subsystem Submitting an SR Submitting an SR Listed below are some guidelines for submitting a service request (SR). Some of the guidelines refer to Node Management Services programs (NMDUMP, NMMAINT, NMMGR, etc.). For more information about these programs, see Using the Node Management Services Utilities. Common Information For any SR, include this common information, where applicable: • A characterization of the problem.
Troubleshooting the APPC Subsystem Submitting an SR • Document your interim, or “workaround,” solution. The cause of the problem can sometimes be found by comparing the circumstances in which it occurs with the circumstances in which it does not occur. • Save copies of any SNA link or SNA service trace files that were active when the problem occurred. • If the problem involves NMMGR, give a copy of NMMGRF.PUB.SYS to your HP representative. • If a system failure has occurred, take a full memory dump.
A Messages This appendix lists the following types of messages that can be returned by the APPC subsystem: • Subsystem startup messages, returned to the terminal from which an APPCCONTROL START command is issued. • Logging messages, which are returned to the system console, to a disk file, or to a user terminal, depending upon configuration. • Error messages, which are returned to the terminal from which an APPCCONTROL command is issued.
Messages Subsystem Startup Messages Subsystem Startup Messages Startup messages are returned by the APPC subsystem when the node manager issues an APPCCONTROL START command. These messages are returned to the terminal from which the APPCCONTROL START command is issued. Note that these messages are informational only, and no action is required. 1 MESSAGE: Successful completion. CAUSE: APPC subsystem activation has begun. ACTION: None.
Messages Logging Messages Logging Messages APPC logging messages are returned during subsystem startup and while the subsystem is active. There are five classes of events that can be logged for the APPC subsystem (SUB0016). They are as follows: • CLAS0010 records internal errors. • CLAS0011 records subsystem warnings. • CLAS0012 records subsystem information messages. • CLAS0013 records conversation information messages. • CLAS0014 records session performance statistics.
Messages Logging Messages 7 MESSAGE: APPC: Session Stopped, Session ID=!, Reason=! (APPCLOG 7). CAUSE: An APPC session with the specified Session ID number has been stopped (unbound) due to the Reason given. (Reasons can include APPC_Kill, APPC_Protocol, APPC_Quiesce, Host_Unbind, Link_Failure, SNA_Error, Convers_Abend, BIS_Error, CTLA_Shutdown, SNA_Kill, SNA_Protocol, SNA_Quiesce, HS_Error, SM_Error, and RM_Error.) ACTION: If you suspect a problem, note the Reason and contact your HP representative.
Messages Logging Messages 11 MESSAGE: APPC: SNA/LINK Error, Session ID=!, Result=! (APPCLOG 11). CAUSE: The APPC subsystem has encountered an error in SNA/SDLC Link/XL. ACTION: Give the APPC subsystem internal trace to your HP representative. 12 MESSAGE: APPC: Received Notify, Session ID=! (APPCLOG 12). CAUSE: The remote system has sent an SNA NOTIFY command over the session with the specified Session ID.
Messages Logging Messages 17 MESSAGE: APPC: TP started, TPName=!, TCB ID=! (APPCLOG 17). CAUSE: A transaction program with the specified transaction program name and Transaction Control Block ID (TCB ID) has been started. ACTION: No action required. 18 MESSAGE: APPC: TP stopped, TPName=!, TCB ID=! (APPCLOG 18). CAUSE: A transaction program with the specified transaction program name and Transaction Control Block ID (TCB ID) has been stopped. ACTION: No action required.
Messages Logging Messages 24 MESSAGE: APPC: Remote Attach Failed: TPName=! Creation Failed (APPCLOG 24). CAUSE: The APPC subsystem was unable to stream the job to start up the local TP. ACTION: Make sure the job name is configured correctly through NMMGR and that the configured job file exists. Make sure there are no lockwords on the job file. 25 MESSAGE: APPC: Conversation Started, TCB ID=!, RCB ID=! (APPCLOG 25).
Messages Logging Messages 30 MESSAGE: APPC: Half Session Creation Error, SUBSYS=!, INFO=! (APPCLOG 30). CAUSE: The APPC subsystem was unable to create the Half Session process ACTION: Contact your HP representative. 31 MESSAGE: Resource Manager Creation Error, NMError=! (APPCLOG 31). CAUSE: The APPC subsystem was unable to create the Resource Manager process. ACTION: Verify that the program file RM.APPC.SYS exists 32 MESSAGE: APPC: Session Manager Creation Error, NMError=! (APPCLOG 32).
Messages Logging Messages 37 MESSAGE: APPC: Session Manager Internal Error, Error=! (APPCLOG 37). CAUSE: The APPC module SM (Session Manager) has detected an internal error. ACTION: Give the APPC subsystem internal trace to your HP representative. 38 MESSAGE: APPC: Half Session Internal Error, Error=! (APPCLOG 38). CAUSE: The APPC module HS (Half Session) has detected an internal error. ACTION: Give the APPC subsystem internal trace to your HP representative.
Messages Logging Messages 43 MESSAGE: APPC: Session Manager Non-Fatal Error: INFO=!, SUBSYS=! (APPCLOG 43). CAUSE: The Session Manager encountered a non-fatal error. The INFO value in the message is the number of a warning or informational message. The SUBSYS value indicates which subsystem generated the message. If SUBSYS=732, the message was generated by the APPC subsystem. ACTION: Note the INFO and SUBSYS< values, and notify your HP representative.
Messages Logging Messages 48 MESSAGE: APPC: SECONDARY STATUS: INFO=!, SUBSYS=! (APPCLOG 48). CAUSE: This message follows another message and supplies the subsystem number and the return code from the MPE XL intrinsic that failed. ACTION: See the message that was logged just before this one for more information 49 MESSAGE: APPC: ! ! Limits Succeeded: OK AS SPECIFIED (APPCLOG 49). CAUSE: The requested session limits have been accepted as specified; they were not negotiated. ACTION: No action required.
Messages Logging Messages 54 MESSAGE: APPC: ! ! Limits Failed: TRANSACTION FAILURE (APPCLOG 54). CAUSE: Internal error in CNOSTP or COPRTP. ACTION: Give the internal trace to your HP representative. 55 MESSAGE: APPC: ! ! Limits Failed: SESSION OUTAGE OCCURRED (APPCLOG 55). CAUSE: The APPC session ended unexpectedly during a CNOSTP or COPRTP conversation. ACTION: Use the APPCCONTROL STATUS command, specifying STYPE=SNASVCMG, to verify that a CNOS session is active.
Messages Logging Messages 61 MESSAGE: APPC: Stype=!, Mode=! (APPCLOG 61). CAUSE: A CNOS (Change-Number-Of-Sessions) transaction failed. This message follows a message from APPCLOG 51 through APPCLOG 59 and supplies more information. ACTION: See the message that was logged just before this one for more information.
Messages Error Messages Error Messages Error messages may be returned by the APPC subsystem when the node manager issues an APPCCONTROL command. These messages are returned to the terminal from which the command is issued. Some error messages are generated by the NMDUMP utility, which is used to format the APPC subsystem internal trace and the LU 6.2 API/XL user trace.
Messages Error Messages ACTION: Check that $STDIN, if redirected when running NMDUMP, is equated properly to an existing MPE text file. See the MPE XL Intrinsics Reference Manual for the exact meaning of the FREAD error indicated by errornum. 905 MESSAGE: APPC failed to read message #messagenum in set #setnum of NMCAT.PUB.SYS. (APPCERR 905) Intrinsic Error Number: errornum. CAUSE: The APPC subsystem failed to read the specified message in the specified set of NMCAT.PUB.SYS.
Messages Error Messages 1003 MESSAGE: PARAMETER STRING LENGTH TOO LONG. (APPCERR 1003) CAUSE: Parameter string exceeded specified length. ACTION: Check the syntax of this command by typing APPCCONTROL HELP or by looking in Chapter 2 , “Interactive Control Operator Commands,” of this manual. 1004 MESSAGE: TOO MANY PARAMETERS SPECIFIED. (APPCERR 1004) CAUSE: An APPCCONTROL command was issued with too many parameters.
Messages Error Messages 1010 MESSAGE: NM CAPABILITY REQUIRED. (APPCERR 1010) CAUSE: A user without NM capability issued a command that requires NM capability. ACTION: Assign NM capability to the user, or log on to another user that has NM capability 1011 MESSAGE: INVALID ERROPT — [SYS OR SUB]. (APPCERR 1011) CAUSE: Incorrect value assigned to the ERROPT parameter of the APPCCONTROL START command. ACTION: Retype the command with the correct ERROPT value.
Messages Error Messages 1016 MESSAGE: INVALID SESSION LIMIT OR SUBSYSTEM'S LIMIT EXCEEDED (APPCERR 1016) CAUSE: Session limit specified in the LIMIT parameter of the APPCCONTROL SESSIONS command is greater than the number currently allowed. ACTION: You could receive this message because you tried to exceed the maximum number of sessions that the APPC subsystem can support, or because you exceeded the number of sessions configured for this session type.
Messages Error Messages ACTION: Run NMMGR and validate the APPC subsystem. Note and correct any errors. If the problem persists, contact your HP representative. 1035 MESSAGE: UNABLE TO OPEN NMCONFIG FILE. (APPCERR 1035) CAUSE: The APPC subsystem is unable to open the NMCONFIG.PUB.SYS file. ACTION: Restart the APPC subsystem. If the same message is returned, call your HP representative. 1036 MESSAGE: UNABLE TO CLOSE NMCONFIG FILE. (APPCERR 1036) CAUSE: The APPC subsystem is unable to close the NMCONFIG.
Messages Error Messages 1042 MESSAGE: TRACE FILE OPEN FAILED. (APPCERR 1042) CAUSE: The APPC subsystem is unable to create the APPC internal trace file. ACTION: Restart the APPC subsystem. If the problem still exists, call your HP representative. 1043 MESSAGE: TRACE FILE CLOSE FAILED. (APPCERR 1043) CAUSE: The APPC subsystem is unable to close the APPC internal trace file. ACTION: Restart the APPC subsystem. If the problem still exists, call your HP representative.
Messages Error Messages 1048 MESSAGE: UNABLE TO CREATE CNOS TP AT SUBSYSTEM STARTUP. (APPCERR 1048) CAUSE: The APPC subsystem detected an error trying to create the Change Number of Sessions (CNOS) TP process during subsystem startup. ACTION: Verify that the program file CNOSTP.APPC.SYS exists and that the capabilities and access privileges for the APPC.SYS group and account are correct. If the problem still exists, contact your HP representative.
Messages Error Messages 1063 MESSAGE: RESOURCE MANAGER ERROR — CHANGE SESSIONS FAILED. (APPCERR 1063) CAUSE: The APPC subsystem detected an internal error. ACTION: Call your HP representative. 1064 MESSAGE: RESOURCE MANAGER ERROR — SUBSYSTEM SHUTDOWN FAILED. (APPCERR 1064) CAUSE: The APPC subsystem detected an internal error while trying to shut down the APPC subsystem after the APPCCONTROL STOP command was issued. ACTION: Call your HP representative.
Messages Error Messages 1073 MESSAGE: APPC SUBSYSTEM PENDING ACTIVE. (APPCERR 1073) CAUSE: The command issued cannot be executed because the APPC subsystem is in the progress of starting up. ACTION: Check the status of the APPC subsystem and reenter your command when the subsystem is active. If problems still exist, call your HP representative. 1074 MESSAGE: APPC SUBSYSTEM ALREADY ACTIVE.
Messages Warning Messages Warning Messages Warning messages may be returned by the APPC subsystem when the node manager issues an APPCCONTROL command. These messages are returned to the terminal from which the command is issued. 1201 MESSAGE: SESSION LIMIT EXCEEDED, REMAINING SESSION IGNORED. (APPCWARN 1201) CAUSE: The total session limit of the subsystem has been reached before the end of the configuration file. Remaining session types are initialized in the APPC Object with SESSION_LIMIT = 0.
Messages Warning Messages 1206 MESSAGE: APPC PERFORMANCE TRACING ALREADY ENABLED. (APPCWARN 1206) CAUSE: An APPCCONTROL PERFORMANCEON command was issued when APPC subsystem performance tracing was already enabled. ACTION: No action required. 1207 MESSAGE: APPC PERFORMANCE TRACING ALREADY DISABLED. (APPCWARN 1207) CAUSE: An APPCCONTROL PERFORMANCEOFF command was issued when APPC subsystem performance tracing was already disabled. ACTION: No action required.
Messages Return Codes Return Codes This section lists the intrinsic return codes that may be returned to a TP by control operator intrinsics. The return codes are returned in the ReturnCode parameter of the intrinsics. 0 MESSAGE: Successful completion CAUSE: The intrinsic completed successfully, and there are no error or warning messages. ACTION: No action necessary. -1001 MESSAGE: Missing required parameter CAUSE: A required parameter was omitted from the intrinsic call.
Messages Return Codes -1006 MESSAGE: Redundant parameter CAUSE: A parameter was used more than once in a control operator intrinsic call. ACTION: Change the intrinsic call, leaving out the duplicated parameter. -1007 MESSAGE: Missing parameter after equal sign CAUSE: A parameter was specified with no value assigned to it, or there was a syntax error in the intrinsic call. ACTION: See Chapter 3 , “Control Operator Intrinsics,” of this manual for the syntax of control operator intrinsics.
Messages Return Codes -1013 MESSAGE: Invalid value for TFileSize parameter CAUSE: The TFileSize APPCStart intrinsic is not a valid value. ACTION: Check the APPCStart intrinsic call and make sure the TFileSize parameter is from 0 through 32767. See Chapter 3 , “Control Operator Intrinsics.” -1014 MESSAGE: Invalid value for PerformanceOn parameter CAUSE: The parameter of the APPCStart intrinsic is not a valid value.
Messages Return Codes ACTION: Issue the APPCCONTROL VERSION command to determine which software modules are installed on the system, and save the output to a file. Call your HP representative. -1032 MESSAGE: Invalid module ID in version check CAUSE: The APPC subsystem detected NM return code 105 during version checking. ACTION: Issue the APPCCONTROL VERSION command and save the output to a file. Contact your HP representative.
Messages Return Codes -1040 MESSAGE: Unable to open NM log file CAUSE: The APPC subsystem is unable to open the Node Management Log File. ACTION: Check the logging class configuration in NMMGR. -1041 MESSAGE: Unable to close NM log file CAUSE: The APPC subsystem is unable to close the Node Management Log File. ACTION: Check the logging class configuration in NMMGR. -1042 MESSAGE: Unable to open internal trace file CAUSE: The APPC subsystem is unable to create the internal trace file.
Messages Return Codes -1051 MESSAGE: CNOS TP detected error during subsystem start-up CAUSE: Internal error in APPC subsystem. ACTION: Contact your HP representative. -1063 MESSAGE: Resource Manager error — CHANGE_SESSIONS_FAILED CAUSE: The APPC subsystem detected an internal error. ACTION: Call your HP representative. -1064 MESSAGE: Resource Manager error — subsystem shutdown failed CAUSE: Internal error in APPC subsystem. ACTION: Call your HP representative.
Messages Return Codes ACTION: Check the status of the subsystem and wait until the subsystem has completed shutdown. Then, restart your program. -1201 MESSAGE: Session limit exceeded CAUSE: The session limit for the APPC subsystem was reached before the end of the configuration file. Remaining session types are initialized in the APPC object with a session limit of 0. ACTION: No action is necessary if you don’t use the session types that are not initialized.
Messages Configuration Messages Configuration Messages This section lists the messages that NMMGR may generate when validating the APPC portion of HP-IBM configuration. NOTE During HP-IBM validation, NMMGR attempts to validate all SNA subsystems. Whenever it finds no configuration data for a particular subsystem, it generates a warning message. Disregard any warning messages about subsystems you have not installed on your system.
Messages Configuration Messages ACTION: Notify your HP Representative. 7 MESSAGE: No configuration data exists for the APPC subsystem. (APPCVALWARN 7) CAUSE: You have attempted to validate the APPC subsystem portion of the configuration file, but no data has been configured for the APPC subsystem. ACTION: Configure the APPC subsystem before validating the configuration file. 8 MESSAGE: Path : APPC.NETID Required NETID is not configured.
Messages Configuration Messages 13 MESSAGE: Path : APPC.SESSION At least one Session Type must be configured. (APPCVALERR 13) CAUSE: You have attempted to validate the APPC subsystem configuration file without configuring any session types. ACTION: Configure at least one session type before validating the configuration file. 14 MESSAGE: Path : APPC.SESSION.! No data is configured for this Session Type.
Messages Configuration Messages ACTION: Configure the Mode Name in the APPC: Select Mode Type screen and the APPC: Mode Type Data screen. 19 MESSAGE: Path : APPC.SESSION.! SNA Node “!” does not support dependent LUs. (APPCVALERR 19) CAUSE: You have configured a dependent LU session type to use a Type 2.1 SNA node without dependent LU support. ACTION: Specify Node 2.
Messages Configuration Messages 24 MESSAGE: Path : APPC.SESSION.! LU “!” is not an independent LU under SNANODE.! screen. (APPCVALERR 24) CAUSE: You have configured an independent LU session type to use a local LU that is not configured as an independent LU on the SNA node you specified for the session type. ACTION: Specify an LU that is configured as an independent LU on the correct SNA Node. (Independent LUs must have no LU# configured in the “SNA Node Configuration: LU Data” screen.
Messages Configuration Messages 29 MESSAGE: Path : APPC.TP.! TP Job Name “!” does not exist on the system. (APPCVALWARN 29) CAUSE: You have specified a Job Name that cannot be found. ACTION: Create a job to stream the configured local TP. Make sure it has the same file name and is located in the same group and account you specified in the Job Name field of the APPC: Transaction Program Data screen. 30 MESSAGE: Path : APPC.TP “!” is a reserved name and can not be reconfigured.
Messages Configuration Messages ACTION: Go to the Logging Configuration: Logging Classes screen for SUB0016 and correct the logging class specifications. Valid SUB0016 logging class names are CLAS0010, CLAS0011, CLAS0012, CLAS0013, and CLAS0014. See the SNA Link/XL Node Manager’s Guide for information about logging configuration. 35 MESSAGE: Path : LOGGING.SUB0016 “!” is not a correctly formatted User Name. (APPCVALERR 35) CAUSE: The User Name specified was not in the proper format.
Messages Configuration Messages 184 Appendix A
B Sample Configuration The sample configuration in this appendix is based on Figure 4-19. The figure is reproduced in this section as Figure B-1. This appendix contains samples of the following: • SNA node configuration screens based on the LU 6.2 configuration shown in Figure B-1. • APPC subsystem configuration screens based on the LU 6.2 configuration shown in Figure B-1. • A sample of the NMMGR critical summary output for the APPC subsystem based on the LU 6.2 configuration in shown in this appendix.
Sample Configuration The example shown in Figure B-1 is reproduced from Chapter 4 , “APPC Subsystem Configuration.” Configuration screens, critical summary, and remote system gens in this appendix are based on the configuration in Figure B-1.
Sample Configuration HP 3000 Configuration HP 3000 Configuration Figure B-2 shows the NMMGR screen structure for the LU 6.2 configuration shown in Figure B-1. The configuration must be performed across two separate NMMGR subtrees: “SNANODE” and “APPC”. You select the subtree you want to configure from the list on the “HP-IBM Configuration” screen. The screens discussed in this appendix have been highlighted in Figure B-2.
Sample Configuration HP 3000 Configuration Configuration Screens The following NMMGR screens are used to illustrate this configuration example: • “SNA Node Configuration” screen • “SNA Node Configuration: PU Data” screens • “SNA Node Configuration: LU Data” screens • “APPC: Network ID Data” screen • “APPC: Select Session Type” screen • “APPC: Dependent LU Session Type Data” screen • “APPC: Dependent LU List Data” screen • “APPC: Independent LU Session Type Data” screens • “APPC: Select Mode Type” screen •
Sample Configuration HP 3000 Configuration SNA Node Configuration Screen Figure B-3 shows the “SNA Node Configuration” screen. Three nodes are configured in it: HOSTPU, AS4001 and AS4002. Each node requires a separate copy of SNA/SDLC Link/XL, which links the HP 3000 to a remote system. The SNA node name HOSTPU matches the PU name configured on the IBM host. The SNA node names AS4001 and AS4002 match the RMTCPNAME (remote control point name) values configured on the two AS/400s.
Sample Configuration HP 3000 Configuration The following diagram as shown in Figure B-4 shows how the “SNA Node Configuration” screen fits into the NMMGR screen structure. The SNA nodes configured here will be entered in the “APPC: Dependent LU Session Type Data” and “APPC: Independent LU Session Type Data” screens for the session types that will use these nodes.
Sample Configuration HP 3000 Configuration SNA Node Configuration: PU Data and LU Data Screens Figure B-5 shows the “SNA Node Configuration: PU Data” screen for node HOSTPU. The Node Type for HOSTPU is configured as 2.0, because all the LUs using this node are dependent LUs. Independent LUs must be configured on Type 2.1 nodes. If you wanted to configure both independent and dependent LUs on the same node, you would configure it as a Node Type 2.1, and you would specify Y in the Node 2.
Sample Configuration HP 3000 Configuration The following diagram as shown in Figure B-6 shows how the “SNA Node Configuration: PU Data” screen for HOSTPU fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration Figure B-7 shows the “SNA Node Configuration: LU Data” screen for node HOSTPU. The four LUs configured here are used by the session type DEPSESS1, the only session type configured to use this node. The LU names configured here match the LU names configured on the IBM host.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-8 shows how the “SNA Node Configuration: LU Data” screen for HOSTPU fits into the NMMGR screen structure. The LUs configured here will be entered in the “APPC: Dependent LU List Data” screen for session type DEPSESS1.
Sample Configuration HP 3000 Configuration Figure B-9 shows the “SNA Node Configuration: PU Data” screen for node AS4001. The Node Type for AS4001 is configured as 2.1, because the HP 3000 functions as a peer node when it communicates with an AS/400. Since no dependent LUs will use AS4001, the Node 2.1 Dependent LU Support field is set to N. The ID BLK and ID NUM fields, together, make up the EXCHID configured in the Controller Description on the AS/400.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-10 shows how the “SNA Node Configuration: PU Data” screen for AS4001 fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration Figure B-11 shows the “SNA Node Configuration: LU Data” screen for node AS4001. The independent LU configured here is used by two session types: INDSESS1 and INDSESS2. The LU# field must be left blank for an independent LU. The LU name HPINDLU1 must match the RMTLOCNAME (remote location name) configured in the Device Description on the AS/400.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-12 shows how the “SNA Node Configuration: LU Data” screen for AS4001 fits into the NMMGR screen structure. The LU configured here will be entered in the “APPC: Independent LU Session Type Data” screens for session types INDSESS1 and INDSESS2.
Sample Configuration HP 3000 Configuration Figure B-13 shows the “SNA Node Configuration: PU Data” screen for node AS4002. The ID BLK and ID NUM fields, together, make up the EXCHID configured in the Controller Description on the AS/400. (The EXCHID in the Controller Description, for this example configuration, is 05600002.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-14 shows how the “SNA Node Configuration: PU Data” screen for AS4002 fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration Figure B-15 shows the “SNA Node Configuration: LU Data” screen for node AS4002. The independent LU configured here is used by session type INDSESS3. The LU# field must be left blank for an independent LU. The LU name HPINDLU2 must match the RMTLOCNAME (remote location name) configured in the Device Description on the AS/400.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-16 shows how the “SNA Node Configuration: LU Data” screen for AS4002 fits into the NMMGR screen structure. The LU configured here will be entered in the “APPC: Independent LU Session Type Data” screen for session type INDSESS3.
Sample Configuration HP 3000 Configuration SNA Node Configuration: SDLC Link Data screen Every node configured in the “SNA Node Configuration” screen must have its communications link parameters and phone data configured in the “SNA Node Configuration: SDLC Link Data” screen. The “SNA Node Configuration: SDLC Link Data” screen is not shown here, but it is fully documented in the SNA Link/XL Node Manager’s Guide.
Sample Configuration HP 3000 Configuration APPC: Network ID Data Screen If your HP 3000 will operate as a Type 2.1 node, you must configure the identifier for your local network in the “APPC: Network ID Data” screen. Chapter Figure B-18, “Example Network ID Data Screen.” shows the “APPC: Network ID Data” screen for the example configuration illustrated in this appendix. The Local Network ID matches the RMTNETID configured in the Device Description on the AS/400.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-19 shows how the “APPC: Network ID Data” screen fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration APPC: Select Session Type Screen Figure B-20 shows the “APPC: Select Session Type” screen. Four session types are configured for the APPC subsystem: DEPSESS1, INDSESS1, INDSESS2, and INDSESS3. DEPSESS1 communicates with an IBM mainframe through node HOSTPU. INDSESS1 and INDSESS2 communicate with IBM AS/400 #1 through node AS4001. INDSESS3 communicates with IBM AS/400 #3 through node AS4002.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-21 shows how the “APPC: Select Session Type” screen fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration APPC: Dependent LU Session Type Data Screen Figure B-22 shows the “APPC: Dependent LU Session Type Data” screen for session type DEPSESS1. Two APPC sessions are configured to activate automatically at subsystem startup. Beyond the automatically activated sessions, two more sessions can be activated before the maximum session limit for DEPSESS1 is reached. See Chapter 5 , “Managing the APPC Subsystem,” for more information on session activation.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-23 shows how the “APPC: Dependent LU Session Type Data” screen fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration APPC: Dependent LU List Data Screen Figure B-24 shows the “APPC: Dependent LU List Data” screen for DEPSESS1. The LUs listed in this screen must first be configured in the “SNA Node Configuration: LU Data” screen for HOSTPU. Since the maximum session limit for DEPSESS1 is 4, there must be four LUs configured in the LU list.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-25 shows how the “APPC: Dependent LU List Data” screen fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration APPC: Independent LU Session Type Data Screens Figure B-26 shows the “APPC: Independent LU Session Type Data” screen for INDSESS1. In this screen, INDSESS1 is configured to use node AS4001. Only one independent LU is configured for that node: HPINDLU1. HPINDLU1 is capable of participating in multiple, simultaneous sessions with both of the independent LUs on IBM AS/400 #1. Sessions of type INDSESS1 are configured to communicate with remote LU BLUELU.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-27 shows how the “APPC: Independent LU Session Type Data” screen for INDSESS1 fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration Figure B-28 shows the “APPC: Independent LU Session Type Data” screen for INDSESS2. INDSESS1 and INDSESS2 both use node AS4001. They also use the same independent LU, HPINDLU1. Sessions of type INDSESS2 are configured to communicate with remote LU GREENLU on AS/400 #1. Session type INDSESS2 has parallel sessions disabled (Parallel Sessions = N), so only one session of this type can be active at a time.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-29 shows how the “APPC: Independent LU Session Type Data” screen for INDSESS2 fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration Figure B-30 shows the “APPC: Independent LU Session Type Data” screen for INDSESS3. Sessions of type INDSESS3 are configured to communicate with remote LU PURPLELU on AS/400 #3, which is indirectly connected to the HP 3000 through AS/400 #2. AS/400 #3 is located in NET2, a different network from the HP 3000 and AS/400 #2. AS/400 #2 identifies the location of the destination LU (NET2.PURPLELU) from the Fully Qualified Remote LU Name field of this screen.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-31 shows how the “APPC: Independent LU Session Type Data” screen for INDSESS3 fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration APPC: Select Mode Type Screen Figure B-32 shows the “APPC: Select Mode Type” screen. The mode type MODE1, used by all the independent LU session types in this example configuration, is the only mode type configured here. The data for mode type MODE1 is configured in the “APPC: Mode Type Data” screen, shown in figure B-17.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-33 shows how the “APPC: Select Mode Type” screen fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration APPC: Mode Type Data Screen Figure B-34 shows the “APPC: Mode Type Data” screen for mode type MODE1. All the independent LU session types in this example configuration use mode type MODE1. independent LUs on the HP 3000 can send and receive RUs no larger than 2048 bytes. This is the default maximum RU size for both sending and receiving. The local LU can send 7 RUs before it must wait for a response from the remote LU.
Sample Configuration HP 3000 Configuration The following diagram shown in Figure B-35 shows how the “APPC: Mode Type Data” screen for mode type MODE1 fits into the NMMGR screen structure.
Sample Configuration HP 3000 Configuration Transaction Program Configuration Screens The “APPC: Select Transaction Program” and “APPC: Transaction Program Data” screens are used to configure transaction programs that call the MCGetAllocate intrinsic to accept allocate requests from remote LUs. The TP screens are not pictured here, but they are fully documented in Chapter 4 , “APPC Subsystem Configuration,” of this manual.
Sample Configuration HP 3000 Configuration NMMGR Critical Summary This is a sample critical summary reflecting the APPC configuration shown in this appendix. CRITICAL SUMMARY - APPC CONFIGURATION THU, SEP 6, 1991, 2:32 PM CONFIGURATION FILE NAME: NMCONFIG.PUB.SYS Validated subsystem.
Sample Configuration Remote Configuration Remote Configuration Figure B-37 shows sample lines from an NCP gen that correspond to values configured on the HP 3000. Figure B-37 Sample Lines from an NCP Gen ************************************************* * LN044 LINE ADDRESS=044 * * This is the LINEID. It isn't configured on the HP 3000. * HOSTPU PU ADDR=C1 * * PU name on the host corresponds to SNA Node Name on the HP 3000.
Sample Configuration Remote Configuration Figure B-38 Sample Lines from an AS/400 Configuration Display Mode Description Mode description name. . . . Maximum number of sessions . Locally controlled sessions. Inbound pacing value . . . . Outbound pacing value. . . . @COMPUTERTEXTW = Display Line description . . . . Data link role . . . . . Exchange identifier. . . . . . . . . . . . . . . . . . . . . . . .: .: .: .: .: MODD MAXSSN LCLCTLSSN INPACING OUTPACING Line Description . . . . . . .: LIND . .
Sample Configuration Remote Configuration 226 Appendix B
C Configuration Worksheets The worksheets in this appendix are provided to help you plan your APPC subsystem configuration. Before you fill them out, you should read Chapter 4 , “APPC Subsystem Configuration.” At the beginning of Chapter 4 , “APPC Subsystem Configuration,” is a section called “Data Required from the Remote Configuration.” You will need the information listed in that section to complete the configuration worksheets.
Configuration Worksheets Completing the Worksheets Completing the Worksheets This section gives you step-by-step instructions for filling out the Independent LU Session Types worksheet, the Dependent LU Session Types worksheet, and the Mode Types worksheet. One copy of each worksheet is included at the end of this appendix. Make some photocopies of the worksheets before you start filling them out so that you will have enough room to plan your whole configuration.
Configuration Worksheets Completing the Worksheets 5. 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).
Configuration Worksheets Completing the Worksheets Completing the Dependent LU Session Types Worksheet A dependent LU session type is used to communicate with dependent LUs on a host (Type 5) node. Follow these steps to complete the Dependent LU Session Types worksheet: 1. 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.
Configuration Worksheets Completing the Worksheets 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. 7.
Configuration Worksheets Example Worksheets Example Worksheets The completed worksheets in this section are based on the configuration illustrated in Figure C-1. Appendix B , “Sample Configuration,” shows the NMMGR screens used for the configuration in this figure.
Configuration Worksheets Example Worksheets Figure C-2 is a Independent LU Session Types worksheet for the example configuration in Figure C-1.
Configuration Worksheets Example Worksheets Figure C-3 is a Dependent LU Session Types worksheet for the example configuration in Figure C-1.
Configuration Worksheets Example Worksheets Figure C-4 is a Mode Types worksheet for the example configuration in Figure C-1.
Configuration Worksheets Example Worksheets 236 Appendix C
D LU 6.2 API/XL Installation Guidelines To run LU 6.2 API/XL on your HP 3000, you must install the product and configure both your HP 3000 environment and the remote system to support LU 6.2 API/XL. HP 3000 configuration is described in Chapter 4 , “APPC Subsystem Configuration,” of this manual. Remote system configuration is described in the IBM Host System Programmer References, listed in the preface of this manual. This appendix describes the tasks you need to perform to install LU 6.2 API/XL.
LU 6.2 API/XL Installation Guidelines Pre-Installation Tasks Pre-Installation Tasks Before you install LU 6.2 API/XL on the HP 3000 you must do the following: 1. Ensure that the remote system has all the required hardware and software listed under “Remote System Requirements,” later in this appendix. 2. Ensure that the modem link operates between the HP 3000 and the remote system. If you use HP modems, Hewlett-Packard will help you verify that these modems work. 3.
LU 6.2 API/XL Installation Guidelines Installation Tasks Installation Tasks After you perform the pre-installation tasks, your HP 3000 will be prepared for LU 6.2 API/XL installation. 1. Log on as MANAGER.SYS. Ask all users to log off. 2. Check whether you have enough disk space to install LU 6.2 API/XL.
LU 6.2 API/XL Installation Guidelines Installation Tasks 9. Issue the following command to install the UDCs that invoke APPCCONTROL commands: SETCATALOG APPCUDC.APPC.SYS;SYSTEM;APPEND 10.
LU 6.2 API/XL Installation Guidelines Remote System Requirements Remote System Requirements This section describes the remote hardware and software required to communicate with Hewlett-Packard’s LU 6.2 API. Hardware The following hardware is required to communicate with an HP 3000 that is acting as a Type 2.0 node: • An IBM host, which can be any IBM plug-compatible computer. The IBM mainframes include the 433x, 434x, 438x, 303x, 308x or 309x.
LU 6.2 API/XL Installation Guidelines HP 3000 Requirements HP 3000 Requirements This section describes the HP 3000 operating environment that supports LU 6.2 API/XL. Hardware The following hardware is required to run LU 6.2 API/XL: • A 900 Series HP 3000. • An HP 30263A Programmable Serial Interface (PSI) card and the appropriate PSI cables. The PSI is bundled with SNA/SDLC Link/XL or SNA/X.25 Link/XL. One PSI is required for each link to a remote system.
Glossary A C Advanced Program-to-Program Communication (APPC): cluster controller: A machine that allows multiple devices to send and receive data over the same communications link. Programmatic communication based on IBM's LU 6.2 architecture. APPC provides partner programs with a common set of rules for communication. Application Program Interface (API): A set of subprograms, callable from inside applications, that carry out data communications tasks.
implement the same functions as control operator commands. (See control operator commands.) peripheral device (like a printer or a terminal), or an application program. conversation: The logical communication between two transaction programs. F Customer Information Control System (CICS): An IBM application subsystem that provides file handling and data communications services for application programs. D dependent LU: An LU capable of conducting only one APPC session at a time.
host: A central computer that provides services for other computers and terminals attached to it. I independent LU: An LU capable of conducting multiple, simultaneous (parallel) APPC sessions with another independent LU on a remote system. An independent LU can function as either a primary or secondary LU. See dependent LU. INIT-SELF: An SNA request to the SSCP to initiate an LU-LU session.
specifications for programmatic interfaces, document interchange, and data distribution. M mapped conversation: A programmatic conversation in which the application is freed from handling the GDS headers required by the LU 6.2 architecture. mapped conversation verbs: Node Type 2.1: The node type for a peripheral node or cluster controller capable of peer-to-peer communication. Node Type 2.1 is supported by the APPC subsystem on MPE XL.
remotely controlled session: An APPC session controlled by an LU on the remote system. Also called a bidder session. The APPC subsystem does not support remotely controlled sessions. See locally controlled session. RH: Request or response header. These are attached to SNA RUs to control data flow and support other network services. RU: Request or response unit. S SDLC: See Synchronous Data Link Control. SNA: See Systems Network Architecture.
Index Symbols (Programmable Serial Interface) PSI, 22 A activating sessions, 117 activating sessions at subsystem startup, 86, 90 activating sessions programmatically, 62 activating the APPC subsystem, 40, 112 activating the APPC subsystem programmatically, 63 activating the SNA node (SNA link product), 42, 65, 112 active sessions reapportioning, 117 Advanced Program-to-Program Communication APPC, 18 allocate requests queued, 99, 123, 125 APPC definition of, 18 Network ID Data Screen NMMGR, 80 Select Sess
Index example, 56 interpretation of display, 57 APPCDPxx.APPC.
Index G general data stream, 18 H help file printing, 30 help on line for APPCCONTROL commands, 30 HP-IBM Screen NMMGR, 78 hung subsystem, 139 I IBM AS/400, 23, 102, 107 IBM system configuration, 72, 73 idle sessions, 120 independent LU, 23, 103, 108 definition of, 83 INIT_SELF, 23, 87, 90 INPACING AS/400 configuration, 95 interactive session control, 22, 26 intermediate routing between nodes, 23, 102, 107 internal error full system shutdown, 41, 65 subsystem shutdown, 41, 65 internal tracing tracing, 40,
Index AS/400 configuration, 94 MCGetAlllocate intrinsic timer configuring, 125 MCGetAllocate intrinsic timer, 98 configuring, 97 message catalog, 59 migrating a configuration, 110 MODE AS/400 configuration, 93 Mode AS/400 configuration, 84 Mode Name configured on HP 3000, 84, 89, 92 default, 84, 89 renaming, 93 MODENAME operand of DFHTCT TYPE=SYSTEM macro, 89, 93 multiple allocate requests, 123, 125 multiple links to remote systems, 22, 83, 102, 107 multiple sessions, 23, 83 N negotiating session limits w
Index Q Queued Allocate Requests configuration, 99 queued allocate requests, 123, 125 queued session requests, 117 QUIESCE stoptype, 39, 50, 62, 70, 121 R receiving data, 18 Remote LU Name configured on the HP 3000, 89 Remote LUs configuring multiple, 103 remotely initiated, 125 remotely initiated conversation, 123, 124 remotely initiated conversations, 122 remotely initiated local TP configuring, 95, 97, 123, 125 manual or automatic startup, 126 reserved LUs, 103 return codes for control operator intrinsi
Index configured on HP 3000, 84, 88 SNA Services using multiple on one SNA node, 127 SNA Transport activation, 112 SNA/SDLC Link/XL, 21 multiple copies, 22, 23, 108 product structure, 22 SNA/X.25 Link/XL, 21 SNACONTRAL STATUS command for Type 2.1 nodes, 133 SNACONTROL START command, 42, 65, 112 SNACONTROL STATUS command, 133 for Type 2.
Index APPC configuration, 134 validation messages APPC configuration, 132 verbs base sets, 18 basic conversation, 18, 21 definition of, 18 mapped conversation, 18 option sets, 18 version checking of software modules, 56 VTAM APPLID, 89 W warning messages, 132 Index 255
