SNA Link/iX Node Manager’s Guide HP 3000 MPE/iX Computer Systems Edition 7 Manufacturing Part Number: 30291-90009 E0394 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. SNA Links Overview SNA Layers Implemented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracing Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other SNA Transport Functions Provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNA/SDLC Link Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 PU Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 LU Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents The Logging Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNA Transport Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link-level Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDLC Link Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6. MPE Commands RESUMENMLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNACONTROL TRACEON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8
Figures Figure 1-1. SNA/SDLC Link HP-to-IBM Host Communication . . . . . . . . . . . . . . . . . . . . 19 Figure 1-2. SNA/SDLC Link HP-to-AS/400 Communication . . . . . . . . . . . . . . . . . . . . . . . 20 Figure 1-3. SNA/X.25 Link HP-to-IBM Host Communication . . . . . . . . . . . . . . . . . . . . . . 22 Figure 1-4. SNA/X.25 Link HP-to-AS/400 Communication . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 1-5. SNA/Token Ring Link Communications . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 10
Tables 11
Tables 12
Preface This manual describes Hewlett-Packard Company’s Systems Network Architecture link products for the MPE/iX operating system: • SNA/SDLC Link/iX (HP 30291A) • SNA/X.25 Link/iX (HP 30298A) • SNA/Token Ring Link/iX (HP J2249A) Systems Network Architecture (SNA) is a comprehensive specification for distributed data processing networks, developed by IBM. This manual describes the steps in configuring the HP 3000 computer system as a node in an IBM SNA network.
Chapter 4 , “SNA Node Startup and Shutdown,” explains how sessions and nodes are started and stopped. Chapter 5 , “SNA Link Troubleshooting,” gives you information about solving problems that might occur while configuring, installing, and running the SNA link products. Chapter 6 , “MPE Commands,” describes the SNA Transport MPE commands. Chapter 7 , “SNA Link Installation Information,” gives you the steps you must follow to install the SNA link products.
SNA Links Overview 1 SNA Links Overview HP 3000 users can communicate with an IBM SNA remote system by using one of the Hewlett-Packard SNA link products: • SNA/SDLC Link/iX (referred to as SNA/SDLC Link), which works with the SNA services to provide an HP 3000-to-IBM host or AS/400 connection over an SNA network. • SNA/X.25 Link/iX (referred to as SNA/X.25 Link), which works with the SNA services to provide an HP 3000-to-IBM host or AS/400 connection over an X.25 network.
SNA Links Overview SNA Layers Implemented SNA Layers Implemented The SNA services implement the upper layers of the SNA architecture. SNA Transport implements a type 2.0 (T2.0) node (formerly called a Physical Unit Type 2 [PU.T2]) and type 2.1 (T2.1) node (formerly called a Physical Unit Type 2.1 [PU 2.1]) for SNA/SDLC Link, a T2.0 node for SNA/X.25 Link, and a T2.0 and T2.1 for SNA/Token Ring Link. (Note that, at this time, LU 6.2 API/XL is the only SNA service that makes use of the T2.
SNA Links Overview Tracing Provided Tracing Provided Three levels of tracing for the SNA links are provided: node tracing, intrinsic tracing, and link-level tracing. Node tracing for SNA Transport is on a node basis and normally is turned off. When turned on, it traces SNA Transport internal events; so, it is a useful tool for troubleshooting SNA Transport. Intrinsic tracing is on a session basis and normally is turned off.
SNA Links Overview Other SNA Transport Functions Provided Other SNA Transport Functions Provided Besides tracing, SNA Transport also provides these basic services through the MPE command interpreter: • Starting and stopping an SNA node (see Chapter 5 , “SNA Link Troubleshooting,”and Chapter 6 , “MPE Commands.”) • Session and link status (see Chapter 6 , “MPE Commands.”) • Software version listing (see Chapter 6 , “MPE Commands.
SNA Links Overview SNA/SDLC Link Overview SNA/SDLC Link Overview SNA/SDLC Link is composed of hardware and software: • Programmable Serial Interface (PSI) card and cables (hardware) • SNA Transport (software) • SDLC link driver (software) The hardware of SNA/SDLC Link (the PSI and cables) and the downloaded SNA Transport software implement the Physical Control layer of SNA, and the SDLC link driver implements the Data Link Control layer.
SNA Links Overview SNA/SDLC Link Overview Figure 1-2 shows how SNA/SDLC Link and the SNA services implement HP 3000-to-IBM AS/400 communication. Figure 1-2 SNA/SDLC Link HP-to-AS/400 Communication Host Hardware and Software Requirements SNA/SDLC Link requires this IBM host hardware: • An IBM System/370-compatible mainframe (for example, Model 370, 303x, and 43xx). • An IBM 37xx-compatible communications controller that supports an SNA line.
SNA Links Overview SNA/SDLC Link Overview AS/400 Hardware and Software Requirements SNA/SDLC Link requires this IBM AS/400 hardware: • An IBM AS/400 computer system with the appropriate communications controller card installed. SNA/SDLC Link requires this IBM AS/400 software: • OS/400 operating system (all SNA-related software is included within the OS/400 operating system). For more-specific information, contact your Hewlett-Packard sales representative.
SNA Links Overview SNA/X.25 Link Overview SNA/X.25 Link Overview SNA/X.25 Link is composed of only software: • SNA Transport • Qualified Logical Link Control (QLLC) module SNA/X.25 Link communicates with the X.25 network through the X.25 System Access software on the HP 3000, which is supported by a Datacommunications and Terminal Controller (DTC). The QLLC module enforces the QLLC protocol, which is a special protocol developed by IBM to resolve differences between SDLC and X.25. It uses qualified X.
SNA Links Overview SNA/X.25 Link Overview Figure 1-4 SNA/X.25 Link HP-to-AS/400 Communication Host Hardware and Software Requirements SNA/X.25 Link requires this IBM host hardware: • An IBM System/370-compatible mainframe (for example, Model 370, 303x, and 43xx). • An IBM 37xx-compatible communications controller that supports an X.25 NCP Packet Switching Interface (NPSI) line. SNA/X.25 Link requires this IBM host software: • MVS/SP or MVS/XA operating system. • ACF/NCP network control program.
SNA Links Overview SNA/X.25 Link Overview • OS/400 operating system (all SNA-related software is included within the OS/400 operating system). For more-specific information, contact your Hewlett-Packard sales representative. HP 3000 Hardware and Software Requirements You can run SNA/X.25 Link on any HP 3000 Series 900 computer that has at least 32MB of real memory. Depending on your system configuration, more memory might be required. Contact your Hewlett-Packard sales representative for more information.
SNA Links Overview SNA/Token Ring Link Overview SNA/Token Ring Link Overview SNA/Token Ring Link is composed of hardware and software: • Token Ring HP-Precision Bus (HP-PB) adapter card (hardware) • SNA Transport (software) • Token ring link module (software) • Token ring link driver (software) The SNA/Token Ring Link uses the HP Token Ring HP-PB adapter card to connect to the token ring LAN. The SNA/Token Ring Link implements an IEEE 802.2 type II driver to handle connection-oriented traffic and IEEE 802.
SNA Links Overview SNA/Token Ring Link Overview Host Hardware and Software Requirements SNA/Token Ring Link requires this IBM host hardware: • An IBM System/370-compatible mainframe (for example, Model 370, 303x, and 43xx). • An IBM 37xx-compatible communications controller that supports an NCP Token Ring Interface (NTRI) connection or an IBM 3174 Establishment Controller that supports Token Ring. SNA/Token Ring Link requires this IBM host software: • MVS/SP or MVS/XA operating system.
SNA Links Overview SNA/Token Ring Link Overview • A block mode terminal that is supported by VPLUS, for use with the Node Management Services (NMS) NMMGR configuration manager. SNA/Token Ring Link requires this HP 3000 software: • HP 3000 Multiprogramming Executive with Integrated POSIX (MPE/iX) operating system.
SNA Links Overview SNA/Token Ring Link Overview 28 Chapter 1
SNA Node and Link Configuration 2 SNA Node and Link Configuration This chapter describes how to use the NMS configuration manager (NMMGR) to create or modify a hierarchical configuration file for the SNA node and link. To configure an SNA service, see the Node Manager’s Guide for that service.
SNA Node and Link Configuration Network Configuration Order Network Configuration Order We recommend that the HP 3000 system and the software components of the IBM host or AS/400 system be configured in this order: 1. The IBM host (JES2, JES3, VTAM, NCP, etc.) or AS/400 system 2. The SNA nodes on the HP 3000 3. Logging for SNA Transport on the HP 3000 4. The SNA services on the HP 3000 5. Logging for the SNA services on the HP 3000 NOTE For SNA/X.25 Link, the X.
SNA Node and Link Configuration Host Configuration Overview Host Configuration Overview Before communication between the HP 3000 and the IBM SNA host system is possible, both systems must be configured. The host configuration should be done first, and it consists of changes to the system generations of one or more of the following, as applicable for the SNA link being used: • ACF/NCP • ACF/VTAM • X.
SNA Node and Link Configuration AS/400 Configuration Overview AS/400 Configuration Overview Before communication between the HP 3000 and the IBM SNA AS/400 system is possible, both systems must be configured. The AS/400 configuration should be done first, and it consists of specifying values for certain parameters. The AS/400 configuration must be coordinated with the SNA node configuration on the HP 3000. Coordination between the AS/400 system and the SNA services also must be done.
SNA Node and Link Configuration HP 3000 Configuration Overview HP 3000 Configuration Overview Once the IBM remote system is configured, you can configure the HP 3000 system. Configuration of the HP 3000 system is accomplished through the Node Management Services configuration manager (NMMGR). The configuration consists of the creation of a configuration file, using NMMGR.
SNA Node and Link Configuration Data Required from the Host Configuration Data Required from the Host Configuration Data in an SNA node configuration file must correspond to information from the host configuration. So, before using NMMGR, you should have certain information from the host configuration. The host information that corresponds to SNA node configuration information for SNA/SDLC links, SNA/X.25 links, and SNA/Token Ring links is described below.
SNA Node and Link Configuration Data Required from the Host Configuration SNA/X.25 Information For the host and the HP 3000 to communicate, you must coordinate the SNA/X.25 node configuration with the host configuration. The HP SNA Products Remote System Configuration Guide explains this configuration. Table 2-2 shows the relationships between items from the host configuration and items in the SNA node configuration file for permanent virtual circuits (PVCs).
SNA Node and Link Configuration Data Required from the Host Configuration Table 2-3 Host Macro Values for X.25 Link SVC Host Configuration Macro nd Operand Field in NMMGR Screen SNA Node NMMGR Screen Virtual Circuit Type X.25 Link Data Call Direction X.25 Link Data PATH DIALNO Remote’s X.25 Network Address X.
SNA Node and Link Configuration Data Required from the Host Configuration Table 2-5 Host Macro Values for DTC Manager (X.25) Host Configuration Macro and Operand X25.VCCPT VWINDOW Field in OpenView Screen Window Size DTC Manager OpenView Screen X.25 Level 3 Although it is not an X.25 standard requirement, we recommend that the value specified in the Window Size field match the VWINDOW operand of the X25.VCCPT host macro.
SNA Node and Link Configuration Data Required from the Host Configuration SNA/Token Ring Information For the host and the HP 3000 to communicate, you must coordinate the SNA/Token Ring node configuration with the ACF/NCP and ACF/VTAM host configurations. The HP SNA Products Remote System Configuration Guide explains these configurations. Table 2-7 shows the relationships between items from the host configuration and items in the SNA node configuration file for an SNA/Token Ring link.
SNA Node and Link Configuration Data Required from the AS/400 Configuration Data Required from the AS/400 Configuration Data in an SNA node configuration file must correspond to information from the remote AS/400 type 2.1 parameters. So, before using NMMGR, you should have certain information from the AS/400 configuration. The AS/400 information that corresponds to SNA node configuration information for SNA/SDLC links, SNA/X.25 links, and SNA/Token Ring links is described below.
SNA Node and Link Configuration Data Required from the AS/400 Configuration Table 2-9 AS/400 Parameter Values for X.25 Link AS/400 Configuration Parameter NETADDR in the line description Field in NMMGR Screen NMMGR Screen Name X.25 Link Data Remote’s X.25 Network Address SNA/Token Ring Information For the AS/400 and the HP 3000 to communicate, you must coordinate the SNA/Token Ring node configuration with the AS/400 configuration.
SNA Node and Link Configuration NMMGR Configuration Overview NMMGR Configuration Overview The SNA node and link configuration is done by using NMMGR to create or modify a configuration file. The file contains this information: • SNA node information: used by SNA Transport to manage sessions with the host. • Link information: used for SDLC data link control and phone data (for switched lines), X.25 link information, and token ring link information.
SNA Node and Link Configuration NMMGR Configuration Overview For dependent LUs and independent LUs, you must provide information for the LU-LU sessions. For each LU defined in SNA Transport, an LU must be defined in the host’s NCP/VTAM configuration. You must configure each LU and establish a correspondence with an LU in the NCP/VTAM configuration. You configure these items for an SNA node: • Node identification. This information identifies the node to the host and specifies the type of node (T2.0 or T2.
SNA Node and Link Configuration NMMGR Configuration Overview Configuration File Validation Validating the configuration file ensures that the configuration data is logically and syntactically correct. Each SNA service’s data is also checked against the SNA node configuration data for correctness (for example, correct LU names). See each service’s Node Manager’s Guide for that service’s validation error messages.
SNA Node and Link Configuration NMMGR Configuration Overview Station ID: Connect Timeout: NRZI: FE 900 N Receive Timeout: 180 Error Retries: 7 Auto Dial: Y Local Timeout: Transmission Speed: 30 9600 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SNANODE NAME: IBMNODE2 ID Blk: 023 ID Num: 00001 LU Name LU# - - - - - LUNAME01 1 LU Name LU# - - - - - LUNAME02 2 Max Data: 265 LU Name LU# - - - - - LUNAME03 3 Type: SDLC LU Name LU# - - - - - LUNAME04 4 LINKDATA Physical Path:
SNA Node and Link Configuration NMMGR Configuration Overview SNANODE NAME: XSIMPVC ID Blk: 023 LU Name - - - LU1 LU# - 1 ID Num: FFFF0 LU Name - - - - LU# - - Max Data: 265 LU Name - - - - LU# - - Type: X.
SNA Node and Link Configuration NMMGR Configuration Overview - - - LU01 LU05 LU09 LU13 - 1 5 9 13 - - - LU02 LU06 LU10 LU14 - 2 6 10 14 - - - LU03 LU07 LU11 LU15 - 3 7 11 15 - - - LU04 LU08 LU12 LU16 - 4 8 12 16 X25LINK: NS NI Name: VC Type: Max Call Retries: PVC Number: X25NI PVC 3 1 Inactivity Timeout: Call Direction: Call Retry Delay: Remote Address: 0 OUT 600 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SNANODE NAME: SVCIN16 ID Blk: 023 LU Name - - - LU01 LU05 LU09
SNA Node and Link Configuration NMMGR Configuration Overview ID Blk: 023 LU Name - - - LU01 LU# - 1 ID Num: FFFF6 LU Name - - - - Max Data: 265 LU# - - LU Name - - - - LU# - - Type: X.
SNA Node and Link Configuration Configuring the SNA Node and Link Configuring the SNA Node and Link Once you have opened the configuration file, you are placed at the NMMGR “Main” screen. Main Screen From the screen shown in Figure 2-1, you can select the category of network subsystems you want to configure. Figure 2-1 Main Screen To access the NMMGR branch for configuring an SNA node and link, press [f4] (IBM). This places you at the “HP-IBM Configuration” screen.
SNA Node and Link Configuration Configuring the SNA Node and Link HP-IBM Configuration Screen From the screen shown in Figure 2-2, you can select the item you want to configure. Figure 2-2 HP-IBM Configuration Screen To select SNA node and link configuration, press [f2] (Go To SNANODE). SNA Node Configuration Screen After you have selected SNA node and link configuration, NMMGR displays the “SNA Node Configuration” screen, as shown in Figure 2-3.
SNA Node and Link Configuration Configuring the SNA Node and Link Figure 2-3 SNA Node Configuration Screen Example Fields Path For display only. The NMMGR branch you are in. SNA Node Name The name of the new SNA node you are configuring or the existing node whose configuration you are modifying. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.
SNA Node and Link Configuration Configuring the SNA Node and Link in the VTAM switched major node match this field; see Table 2-7. New Name The new name of an existing SNA node. The name can be up to eight alphanumeric characters long; the first character must be alphabetic. Host Configuration: • SNA/SDLC: For troubleshooting purposes, we recommend that the puname operand of the PU macro match this field; see Table 2-1. • SNA/X.
SNA Node and Link Configuration Configuring the SNA Node and Link PU Data Screen After you have selected a node, NMMGR displays the “SNA Node Configuration: PU Data” screen, as shown in Figure 2-4. (You can go directly to this screen from any screen by typing @SNANODE.nodename in the command window and pressing [ENTER].) Here you enter information that identifies the PU to the host. If you are configuring a new node, you must enter all of the information.
SNA Node and Link Configuration Configuring the SNA Node and Link If you are configuring a node for SNA/X.25 Link, you must enter 2.0 in this field. If you are configuring a node for SNA/Token Ring Link, enter 2.1 in this field. Values: 2.0 and 2.1 Default: 2.0 Host Configuration: • SNA/SDLC (dependent LU): The PUTYPE operand of the PU macro must be set to 2, and the XID operand of the same PU macro must be set to NO or not specified at all.
SNA Node and Link Configuration Configuring the SNA Node and Link Host Configuration: • SNA/SDLC: The MAXDATA operand of the PU macro must match this field; see Table 2-1. • SNA/X.25 (PVC): The MAXDATA operand of the X25.PU macro must match this field; see Table 2-2. • SNA/X.25 (SVC): The MAXDATA macro in the VTAM switched major node must match this field; see Table 2-3. • SNA/Token Ring: The MAXDATA operand of the PU macro in the VTAM switched major node must match this field; see Table 2-7.
SNA Node and Link Configuration Configuring the SNA Node and Link • SNA/Token Ring: The IDBLK macro must match this field; see Table 2-7. AS/400 Configuration: The EXCHID parameter in the controller description is required, and must match the entire exchange identifier (this field combined with ID NUM); see Table 2-8 and Table 2-10. ID NUM NOTE Five hexadecimal digits that are appended to ID BLK (see above) to form the exchange identifier used with exchange identification (XID) requests.
SNA Node and Link Configuration Configuring the SNA Node and Link Host Configuration: HP recommends that you use the PU name (the SNA Node Name field in the SNA Node Configuration screen) in this field. AS/400 Configuration: For APPN, the RMTCPNAME in the APPC display controller description must match this field; see Table 2-10. Otherwise, HP recommends that you use the PU name (the SNA Node Name field in the SNA Node Configuration screen) in this field. File For display only.
SNA Node and Link Configuration Configuring the SNA Node and Link Figure 2-5 LU Data Screen Example Fields Path For display only. The NMMGR path to this screen. It includes the name of the SNA node you are configuring. Logical Unit Data Information about the LUs to be configured for this node. You can configure a maximum 256 LUs for each node. LU Name The remote system name (not the Network Addressable Unit [NAU] number) of the LU.
SNA Node and Link Configuration Configuring the SNA Node and Link • SNA/SDLC (independent LU): The luname operand of the LU macro must match this field; see Table 2-1. • SNA/X.25 (PVC): For troubleshooting purposes, we recommend that the luname operand of the X25.LU macro match this field; see Table 2-2. • SNA/X.25 (SVC): For troubleshooting purposes, we recommend that the luname operand of the LU macro in the VTAM switched major node match this field; see Table 2-3.
SNA Node and Link Configuration Configuring the SNA Node and Link File For display only. The name of the configuration file. Note that you can enter LU information on up to eight pages of this screen. Each page contains 32 LU Name and LU # fields You do not have to fill all of the fields on a page before pressing [f1] (Next Page), [f2] (Prev Page), [f3] (First Page), or [f4] (Last Page) to display another page of the screen for entering information. That is, partially filled pages are allowed.
SNA Node and Link Configuration Configuring the SNA Node and Link SDLC Link Data Screen Once you have specified the PU and LU information, you are ready to configure the communications link parameters and the phone data for the SDLC link. You do this on the “SNA Node Configuration: SDLC Link Data” screen as shown in Figure 2-6. Select this screen by pressing [f1] (Go To LINKDATA) on the “SNA Node Configuration: PU Data” screen. (You can go directly to this screen from any screen by typing @SNANODE.
SNA Node and Link Configuration Configuring the SNA Node and Link 4 X SlotNumber where (a) X is the multiplication sign (not the character “X”), and (b) SlotNumber is the number of the slot the PSI is in. Example: If the PSI is in slot 6, the Physical Path is 24 (4 multiplied by 6).
SNA Node and Link Configuration Configuring the SNA Node and Link Local Timeout Required. The number of seconds the SDLC link driver waits for PSI card activity, before informing SNA Transport that the PSI is down and the link driver is going down. Note that the PSI card waits 20 seconds longer (than the value specified here) for SDLC link driver activity before bringing down the link and reporting a failure. This avoids unnecessary use of dial-up lines, which avoids excessive phone charges.
SNA Node and Link Configuration Configuring the SNA Node and Link Range: 1-999 (integer) Default: 7 Transmission Speed Required. The line transmission speed (bits per second). This value is overridden by the modem, if one is used. For direct-connect, the speed must be supported by the cable. Values: 1200 2400 4800 9600 19200 38400 56000 64000 (integer) Default: 9600 Host Configuration: The SPEED operand of the LINE macro must match this field; see Table 2-1.
SNA Node and Link Configuration Configuring the SNA Node and Link Default: N Phone Number The number you want the link to dial into. Note that you specify this field only if you are using an auto-dial modem. Allowable Characters: • Any of the 12 phone characters: 0 1 2 3 4 5 6 7 8 9 * # • - = A spacing character, used for readability purposes. • D = Pause for three seconds. • E = The end of the phone number. This character might be required by the modem; check your modem manual for details.
SNA Node and Link Configuration Configuring the SNA Node and Link After the information is saved, press [f8] (Prior Screen) until you get to the screen you need next. X.25 Link Data Screen Once you have specified the PU and LU information, you are ready to configure the communications link parameters and virtual circuit data for the X.25 link. You do this on the “SNA Node Configuration: X.25 Link Data” screen.
SNA Node and Link Configuration Configuring the SNA Node and Link Data Required from the NS Configurations Certain items from the X.25 System Access configuration and the DTC Manager configuration or the DTS configuration must match or be compatible with items in the SNA/X.25 configuration. Listed below are the X.25 System Access configuration screens and DTC Manager configuration or DTS configuration screens that contain those items. For an SNA/X.
SNA Node and Link Configuration Configuring the SNA Node and Link For an SNA/X.25 SVC: • “Network Interface Configuration” screen: The Configured Network Interfaces list must include the NI name specified for NS Network Interface Name on the “SNA Node Configuration: X.25 Link Data” screen. • “X.25 SVC Address Key Paths” screen: The name of the facility set configured for the SVC must be found on this screen, even though it is not actually used in the SNA/X.25 configuration.
SNA Node and Link Configuration Configuring the SNA Node and Link Figure 2-8 SVC Configuration Dependencies Figure 2-9 shows the X.25 Link Data Screen.
SNA Node and Link Configuration Configuring the SNA Node and Link Figure 2-9 X.25 Link Data Screen Example Fields Path For display only. The NMMGR pat to this screen. It includes the name of the SNA node you are configuring. NS Network Interface Name Required. The NS network interface that the X.25 link will use. The name can be up to eight alphanumeric characters long; the first character must be alphabetic. See the appropriate NS documentation for more information. X.
SNA Node and Link Configuration Configuring the SNA Node and Link result in an indefinite period of inactivity; however, note that it might be desirable to disable the timer for permanent virtual circuits (PVCs). Range: 0-32767 (integer) Default: 0 Virtual Circuit Type Required. The type of virtual circuit to be used to connect to the host: permanent virtual circuit (PVC) or switched virtual circuit (SVC). The X.
SNA Node and Link Configuration Configuring the SNA Node and Link of the “X.25 PVC Address Key Paths” screen), that address key must match the value specified in this field. See Figure 2-7 for an example. DTC Manager Configuration: The range specified for the LCI Range field (for PVCs) of the “DTC Manager DTCX25 Board # Level 3” screen must contain the value specified in this field. DTS Configuration: The range specified for the LCI Range field (for PVCs) of the “DTS X.
SNA Node and Link Configuration Configuring the SNA Node and Link SNA/X.25 SVC, the X.25 Address you specified in the “X.25 SVC Address Key Paths” screen must be the same as the address you specify in this field. See Figure 2-8 for an example. Call Direction Conditionally required. Enter IN if the HP 3000 will wait for the remote system to request a connection (incoming direction); OUT if the HP 3000 will initiate the connection (outgoing direction).
SNA Node and Link Configuration Configuring the SNA Node and Link Note that this field is valid only when OUT is specified for the Call Direction field. Range: 0-999 (integer) Default: 3 Call Retry Delay Conditionally required. The number of seconds the QLLC module waits between attempts to connect to the remote system. This field is required only if a value greater than 0 is specified for the Maximum Call Retries field.
SNA Node and Link Configuration Configuring the SNA Node and Link Token Ring Link Data Screen Once you have specified the PU and LU information, you are ready to configure the communications link parameters for the token ring link. You do this on the “SNA Node Configuration: Token Ring Link Data” screen as shown n Figure 2-10. Select this screen by pressing [f1] (Go To LINKDATA) on the “SNA Node Configuration: PU Data” screen. (You can go directly to this screen from any screen by typing @SNANODE.nodename.
SNA Node and Link Configuration Configuring the SNA Node and Link Fields Path For display only. The NMMGR path to this screen. It includes the name of the SNA node you are configuring. Link Name Required. The symbolic name of the token ring card. The name must start with an alphabetical character. NOTE If the same token ring card is being used for both NS and SNA communications, you must use the same name in this field as is configured for the NS link. Physical Path of Device Adapter Required.
SNA Node and Link Configuration Configuring the SNA Node and Link AS/400 Configuration: The DSAP in the controller description for the HP 3000 must match this field; see Table 2-10. NOTE A service access point (SAP) pair identifies a MAC type 2 connection. This pair consists of two SAPs: the destination SAP (DSAP) and the local SAP (LSAP). DSAP is the SAP of the remote computer and LSAP is the SAP of the local computer.
SNA Node and Link Configuration Configuring the SNA Node and Link Remote Station Address Required. Host Configuration: The LOCADD parameter in the LINE macro must match this field; see Table 2-7. AS/400 Configuration: The ADPTADR in the line description for the AS/400 must match this field; see Table 2-10. Use Factory-Configured Local Station Address Enter Y to use the factory-configured local station address. Enter N to use the address to be entered in the Local Station Address field.
SNA Node and Link Configuration Configuring the SNA Node and Link 78 Chapter 2
Logging Configuration 3 Logging Configuration This chapter describes how to use the NMS configuration manager (NMMGR) to create or modify a configuration file for logging. Basic information about NMMGR is contained in Using the Node Management Services Utilities; if you are not familiar with NMMGR, you should read that manual before continuing. Note that the logging configuration is completely HP 3000 dependent and has no corresponding remote system configuration.
Logging Configuration Table 3-1 Subsystem SNA Transport (SUB0001) SNA Logging Configuration Guidelines Class Events Console Logging Disk Logging CLAS0010 Node events* YES YES CLAS0011 Protocol errors YES YES CLAS0012 LU-LU activities NO YES CLAS0013 LU-SSCP activities NO** YES CLAS0010 Workstation events NO NO CLAS0012 Critical events and errors YES YES CLAS0013 Console commands and messages NO NO CLAS0010 Internal errors YES YES CLAS0011 Subsystem warnings YES YES
Logging Configuration Table 3-1 Subsystem Token Ring Link (SUB0061) SNA Logging Configuration Guidelines Class Events Console Logging Disk Logging CLAS0001 Errors NO YES CLAS0002 Warnings NO YES CLAS0003 Informational messages NO YES *If you are using an X.25 link and you want logging information recorded, logging (console, disk, or both) for SNA Transport class CLAS0010 must be enabled, because the X.25 link uses the logging facilities for that SNA Transport class.
Logging Configuration Configuration File Validation Configuration File Validation Validating the configuration file ensures that the configuration data is logically and syntactically correct. Each SNA service’s data is also checked against the SNA node configuration data for correctness (for example, correct LU names). See each service’s Node Manager’s Guide for that service’s validation error messages.
Logging Configuration Configuring Logging Configuring Logging Once you have opened the configuration file, you are placed at the NMMGR “Main” screen, as shown in Figure 3-1. Main Screen From this screen you can select the category of network subsystems you want to configure. Figure 3-1 Main Screen To access the NMMGR branch for configuring logging, press [f4] (IBM). This places you at the “HP-IBM Configuration” screen.
Logging Configuration Configuring Logging Figure 3-2 HP-IBM Configuration Screen To select logging, press [f1] (Go To LOGGING). IBM Logging Configuration (1) Screen After you have selected logging configuration, NMMGR displays the “IBM Logging Configuration (1)” screen, as shown in Figure 3-3. Here you specify logging information for these subsystems: SNA Transport, NRJE, and DHCF.
Logging Configuration Configuring Logging Figure 3-3 IBM Logging Configuration (1) Screen Example Fields Subsystem For display only. The names and numbers of the subsystems you can configure logging for on this screen. Class Name For display only. The names of the logging classes you can configure logging for on this screen. Console Logging Required. Enter Y if you want logging events for a class displayed at the HP 3000 console; N, otherwise. Refer to Table 3-1 for guidelines.
Logging Configuration Configuring Logging Disk Logging Required. Enter Y if you want logging events for a class recorded in the NM log file; N, otherwise. The file name that Node Management Services (NMS) uses is NMLGnnnn.PUB.SYS, where nnnn is a number from 0000 through 9999. This is a common file used for logging by all logging classes in all subsystems. At each MPE system startup, or when a file is full, NMS creates a new NMLGnnnn.PUB.SYS file, naming each successive file by incrementing nnnn.
Logging Configuration Configuring Logging • CLAS0012: LU-LU activities — OpenUser/CloseUser — Session activation/Session deactivation • CLAS0013: LU-SSCP activities — OpenUser/CloseUser — Session activation/Session deactivation Note that if you are using a manual-dial modem, console logging for this SNA Transport class (CLAS0013) must be enabled, so that pertinent logging messages can be displayed.
Logging Configuration Configuring Logging • CLAS0013: diagnostic messages — Internal data NOTE If you want the logging events for only a specific logging subsystem and class to be displayed at the list devices of users, see “Enabling Users for a Specific Subsystem and Class” later in this chapter. File For display only. The name of the configuration file. Once you have entered all of the logging information, press [f6] (Save Data).
Logging Configuration Configuring Logging Figure 3-4 IBM Logging Configuration (2) Screen Example Fields Subsystem For display only. The names and numbers of the subsystems you can configure logging for on this screen. Class Name For display only. The names of the logging classes you can configure logging for on this screen. Console Logging Required. Enter Y if you want logging events for a class displayed at the HP 3000 console; N, otherwise. Refer to Table 3-1 for guidelines.
Logging Configuration Configuring Logging Disk Logging Required. Enter Y if you want logging events for a class recorded in the NM log file; N, otherwise. The file name that Node Management Services (NMS) uses is NMLGnnnn.PUB.SYS, where nnnn is a number from 0000 through 9999. This is a common file used for logging by all logging classes in all subsystems. At each MPE system startup, or when a file is full, NMS creates a new NMLGnnnn.PUB.SYS file, naming each successive file by incrementing nnnn.
Logging Configuration Configuring Logging NOTE If you want the logging events for only a specific logging subsystem and class to be displayed at the list devices of users, see “Enabling Users for a Specific Subsystem and Class” later in this chapter. File For display only. The name of the configuration file. Once you have entered all of the logging information, press [f6] (Save Data).
Logging Configuration Configuring Logging Figure 3-5 IBM Logging Configuration (3) Screen Example Fields Subsystem For display only. The names and numbers of the subsystems you can configure logging for on this screen. Class Name For display only. The names of the logging classes you can configure logging for on this screen. Console Logging Required. Enter Y if you want logging events for a class displayed at the HP 3000 console; N, otherwise. Refer to Table 3-1 for guidelines.
Logging Configuration Configuring Logging file by incrementing nnnn. When NMLG9999.PUB.SYS is full, NMS names the next file NMLG0000.PUB.SYS. The MPE commands RESUMENMLOG, SHOWNMLOG, and SWITCHNMLOG are used to control logging and the log file. These commands are described in Chapter 6 , “MPE Commands,” of this manual. Refer to Table 3-1 for guidelines. Default: Each class’s default is the recommended setting for that class (see Table 3-1).
Logging Configuration Configuring Logging Then, if you do not want to configure logging information for other SNA subsystems, press [f5] (Validate HP-IBM) to validate the logging configuration you just did. Once the logging configuration is validated, press [f4] (Exit Logging) to return to the “HP-IBM Configuration” screen.
Logging Configuration Configuring Logging Fields Path For display only. The NMMGR path to this screen. It includes the names of the subsystem and the logging class you are enabling users for. Enable Console Logging? Required. Enter Y if you want logging events for only this subsystem and class displayed at the HP 3000 console; N, otherwise. Refer to Table 3-1 for guidelines.
Logging Configuration Configuring Logging Configuration (3)” screen, the value on the other screen is overridden by the value you enter here. Default: Y NOTE If you change the disk logging configuration for a subsystem, the changes will not take effect until that subsystem is shut down and restarted. Current number of users enabled for logging For display only. The number of users specified for Users enabled for logging.
SNA Node Startup and Shutdown 4 SNA Node Startup and Shutdown This chapter describes how SNA sessions are established with the IBM remote system, how SNA nodes are started up and shut down, and how SNA sessions are terminated. These topics are covered in this chapter: • Establishing sessions with the remote system — For a type 2.0 node — For a type 2.
SNA Node Startup and Shutdown Establishing Sessions with the Remote System Establishing Sessions with the Remote System Remote system session establishment is slightly different for a type 2.0 (T2.0) node than for a type 2.1 (T2.1) node. Session establishment for each node type is explained below, and examples of session establishment activities between the HP 3000 and the IBM remote system are shown later in this chapter.
SNA Node Startup and Shutdown Establishing Sessions with the Remote System manage the LU-LU sessions on the HP 3000. For a Type 2.1 Node Session establishment for a T2.1 node is different than establishment for a T2.0 node in one major way: An independent LU on a T2.1 node can establish an LU-LU session with a remote system LU without the need for a corresponding LU-SSCP session.
SNA Node Startup and Shutdown Establishing PU-SSCP Sessions on the HP 3000 Establishing PU-SSCP Sessions on the HP 3000 For each node you configure on the HP 3000, a corresponding T2.0 or T2.1 node should be in the remote system configuration. Figure 4-1 shows how a session is established between the SSCP on the remote system and the PU on the HP 3000 node (either a T2.0 node or a T2.1 node).
SNA Node Startup and Shutdown Establishing PU-SSCP Sessions on the HP 3000 Figure 4-1 PU-SSCP Session Establishment IBM Remote System HP 3000 (T2.0/T2.1 Node) Link started up from remote system SSCP polls for null XID null XID poll - - - - - -> If HP 3000 is a T2.0 node, it sends an XID0 If HP 3000 is a T2.
SNA Node Startup and Shutdown Establishing LU-SSCP Sessions on the HP 3000 Establishing LU-SSCP Sessions on the HP 3000 For a dependent LU on the HP 3000 to communicate with another dependent LU, it must first have a session with the SSCP on the host system. Each LU-SSCP session is managed by SNA Transport. Figure 4-2 shows LU-SSCP session establishment with SNA Transport acting as the LU service manager. The SSCP checks the configuration on the host for the LUs defined for the HP 3000 node.
SNA Node Startup and Shutdown Terminating SNA Sessions Terminating SNA Sessions PU-SSCP and LU-SSCP sessions can be terminated from the remote system by deactivating an LU, the PU, or the link. Also, the SNA link terminates all sessions on the HP 3000 node if the link is unexpectedly interrupted or deactivated. An HP 3000 SNA node can be intentionally shut down with the SNACONTROL STOP command (see Chapter 6 , “MPE Commands,” of this manual); any SNA services that are running are also terminated.
SNA Node Startup and Shutdown Terminating SNA Sessions 104 Chapter 4
SNA Link Troubleshooting 5 SNA Link Troubleshooting You can troubleshoot the SNA links by using the tracing and logging facilities. This chapter describes those facilities and other related topics: • The tracing facility — SNA Transport tracing — Link-level tracing • The logging facility — SNA Transport logging — Link-level logging • Using NMDUMP for the SNA links — SNA Transport output formats — SDLC link output formats — X.
SNA Link Troubleshooting The Tracing Facility The Tracing Facility Tracing provides data for analysis, and can be done on many levels. The highest level of tracing is at the services level (see the Node Manager’s Guide for each service for which tracing is available). SNA tracing is done at the SNA Transport level (an intermediate level) and at the link level (the lowest level). All of these functions are controlled through MPE commands (see Chapter 6 , “MPE Commands,” in this manual).
SNA Link Troubleshooting The Tracing Facility NOTE Although the format of the default trace file name is the same for all types of tracing, the same default file name will not be assigned for more than one trace. This is because the default trace file name is automatically assigned in numerical order. For example, suppose the last default trace file name assigned was NMTC0004.PUB.SYS. If you started SNA Transport intrinsic tracing, and did not specify a trace file name, the default name NMTC0005.PUB.
SNA Link Troubleshooting The Tracing Facility NOTE Although the format of the default trace file name is the same for all types of tracing, the same default file name will not be assigned for more than one trace. This is because the default trace file name is automatically assigned in numerical order. For example, suppose the last default trace file name assigned was NMTC0004.PUB.SYS. If you started SNA Transport intrinsic tracing, and did not specify a trace file name, the default name NMTC0005.PUB.
SNA Link Troubleshooting The Tracing Facility NOTE Regardless of whether you specify a trace file name or let the default name be assigned, the trace file that is opened when tracing is started is used until tracing is stopped. This means that if the file becomes full before tracing is stopped, the current contents of the file are overwritten with the new trace information, starting at the beginning of the file (no warning is issued).
SNA Link Troubleshooting The Logging Facility The Logging Facility Logging records subsystem events — significant normal events, as well as error events — for use in problem determination and monitoring network usage and resources. NMS performs SNA link logging| at two levels: for the SNA network (SNA Transport logging), and at link level (SDLC link logging, X.25 link logging, token ring link logging, and link trace logging).
SNA Link Troubleshooting The Logging Facility — Bad port messages • CLAS0012: LU-LU activities — OpenUser/CloseUser — Session activation/Session deactivation • CLAS0013: LU-SSCP activities — OpenUser/CloseUser — Session activation/Session deactivation Link-level Logging Four types of link-level logging are available: SDLC link logging, X.25 link logging, token ring link logging, and link trace logging.
SNA Link Troubleshooting The Logging Facility Token Ring Link Logging Token ring link logging records informational messages and error messages generated by the token ring link. It is controlled through the MPE commands SHOWNMLOG, SWITCHNMLOG, and RESUMENMLOG. These commands enable the node manager to determine the number of and available space in the current NM log file (NMLGnnnn.PUB.
SNA Link Troubleshooting Using NMDUMP for the SNA Links Using NMDUMP for the SNA Links The NMS utility NMDUMP can be used to format tracing and logging records for the SNA links. Described below are the tracing and logging formats produced for the SNA links by NMDUMP. Note that NMDUMP is described in more detail in Using the Node Management Services Utilities. If you are not familiar with NMDUMP, you should read that manual before running NMDUMP.
SNA Link Troubleshooting Using NMDUMP for the SNA Links Figure 5-1 SNA Transport Trace Format Example ************************************************************************* HP | EVENT : snasendexpedited call FEB 29, 1992, 8:27:43.022 HP | LU NAME : INDLU1 ROLE: Pri Session Type: LU-LU IND HP | Open ID : Not Used SIDH: nil SIDL: nil ODAI: nil HP | RESULT : Good Complete RU Length: 0020 HP | TH: SNF: 0001 Send ID: Not Used HP | RH: REQ SC FI.....BCI.ECI.DR1........................................
SNA Link Troubleshooting Using NMDUMP for the SNA Links Logging Records Figure 5-2 is a partial example of the format for SNA Transport logging information.
SNA Link Troubleshooting Using NMDUMP for the SNA Links SDLC Link Output Formats For the SDLC link, NMDUMP formats tracing records and logging records. When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for SDLC Link: 27. Then, proceed normally with NMDUMP. The format of the tracing records is shown below. Tracing Records Figure 5-3 is a partial example of the format of a tracing record for the SDLC link.
SNA Link Troubleshooting Using NMDUMP for the SNA Links Logging Records Figure 5-4 is a partial example of the format for SDLC link logging information. Figure 5-4 SDLC Link Logging Format Example SAT, Feb 29, 1992, 11:02:16.6 AM Link (27) Linkname = SDLC24 Module Log Class = Informational SAT, Feb 29, 1992, 11:03:05.2 AM Link (27) Linkname = SDLC24 Config Log Class = Informational MC Version = A004005D SAT, Feb 29, 1992, 11:03:07.
SNA Link Troubleshooting Using NMDUMP for the SNA Links X.25 Link Output Formats For the X.25 link, NMDUMP formats tracing records. (Logging information is contained within the SNA Transport logging information.) When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for X.25 Link: 38. Then, proceed normally with NMDUMP. The format of the tracing records is shown below.
SNA Link Troubleshooting Using NMDUMP for the SNA Links Token Ring Link Output Formats For the Token Ring link, NMDUMP formats tracing records and logging records. When NMDUMP displays the list of subsystems and IDs, and prompts you for the IDs you want to select, specify the ID for Token Ring Link: 61. Then, proceed normally with NMDUMP. The format of the tracing records is shown below. Tracing Records Figure 5-6 is a partial example of the format of a tracing record for the Token Ring link.
SNA Link Troubleshooting Using NMDUMP for the SNA Links Logging Records Figure 5-7 is a partial example of the format for token ring link logging information Figure 5-7 Token Ring Link Logging Format Example NOV 11, 1992, 3:51:34.6 PM 802.5 Token Ring LAN Linkname = T2REG2 call Log Class = Informational MC Version = A0045019 Subsystem opened link T2REG2 NOV 11, 1992 4:06:04.
SNA Link Troubleshooting Using NMMAINT for the SNA Links Using NMMAINT for the SNA Links The NMMAINT utility displays the version numbers of the HP data communications software installed on your system. NMMAINT is described in more detail in Using the Node Management Services Utilities. If you are not familiar with NMMAINT, you should read that manual before you run NMMAINT. SNA/Transport Information The example below shows the SNA/Transport-related information displayed when you run NMMAINT.
SNA Link Troubleshooting Using NMMAINT for the SNA Links SNA/SDLC Link Information The example below shows the SNA/SDLC Link-related information displayed when you run NMMAINT. Note that the modules and version numbers shown below are not necessarily current for SNA/SDLC Link; they are shown only as an example.
SNA Link Troubleshooting Using NMMAINT for the SNA Links SNA/Token Ring Link Information The example below shows the SNA/Token Ring Link-related information displayed when you run NMMAINT. Note that the modules and version numbers shown below are not necessarily current for SNA/Token Ring Link; they are shown only as an example.
SNA Link Troubleshooting Problem Resolution Problem Resolution Problems that can occur while installing, configuring, and running an SNA link — and how to deal with them — are described here. Guidelines for submitting a service request (SR) are also given. Common Problems Some problems are common to many situations — invalid software installation, version incompatibilities, insufficient MPE resources, corrupt configuration files, and file system errors.
SNA Link Troubleshooting Problem Resolution Corrupt Configuration File The configuration file might be corrupt. Validate the configuration file to check for possible corruption. If the error persists, use NMMGR to manually check the configuration file (if possible). If bad records seem to be localized to a particular item, delete that item and reconfigure it. If necessary, RESTORE a backup copy of the file.
SNA Link Troubleshooting Problem Resolution can be defined in a higher-level macro, this structure must be followed: GROUP, LINE, SERVICE, PU, and LU. A macro could be missing a required operand or an invalid operand might have been specified for a particular macro. Installation Problems Some common problems that might occur during installation, or as a result of improper or unsuccessful installation, are described below. 1. Inactive VTAM node.
SNA Link Troubleshooting Problem Resolution Common Information For any SR, include this common information, where applicable: • A characterization of the problem. Describe the events leading up to and including the problem. Try to describe the source of the problem. Describe the symptoms of the problem. Your characterization should include MPE commands, communication subsystem commands, job streams, result codes and messages, and data that can reproduce the problem.
SNA Link Troubleshooting Problem Resolution • Always obtain a copy of the generation of the host system you are using for ACF/VTAM and ACF/NCP. For the host system to be compatible with the SNA link, Hewlett-Packard sets certain operands and parameters to required values (see Chapter 2 , “SNA Node and Link Configuration,” of this manual). Note any differences between the actual system generation and your expectations. Keep this information for your Hewlett-Packard support contact. This is very important.
SNA Link Troubleshooting Problem Resolution and this trace file to your Hewlett-Packard support contact for analysis. NOTE It is important to give a copy of the PSI dump that took place while link-level tracing was enabled to your Hewlett-Packard support contact for analysis. • If a PSI failure has not taken place, turn on link-level tracing with the MPE command SNACONTROL START or SNACONTROL TRACEON (see Chapter 6 , “MPE Commands,” of this manual).
SNA Link Troubleshooting Problem Resolution 130 Chapter 5
MPE Commands 6 MPE Commands This chapter describes, in alphabetical order, the MPE commands related to SNA Transport. You must have MPE node manager (NM) capability to use these commands. Table 6-1 summarizes the functions of the commands. Table 6-1 MPE Command Summary Command Function RESUMENMLOG Resumes NM logging after a recoverable error. SHOWNMLOG Displays the identification number and available space of the NM log file. SNACONTROL AUTODIAL Causes an SNA node's auto-dial modem to dial.
MPE Commands RESUMENMLOG RESUMENMLOG Resumes NM logging after a recoverable error. Syntax RESUMENMLOG Use RESUMENMLOG can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Description RESUMENMLOG resumes logging to the NM log file (NMLGnnnn.PUB.SYS) after it was suspended because of a recoverable I/O error, once the error has been corrected. For example, assume that the system is on line, NM logging is enabled, and a recoverable error occurs.
MPE Commands SHOWNMLOG SHOWNMLOG Displays the identification number and available space of the NM log file. Syntax SHOWNMLOG Use SHOWNNMLOG can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Description SHOWNMLOG displays the number of the current NM log file (NMLGnnnn.PUB.SYS) and the percentage of available file space currently used.
MPE Commands SNACONTROL AUTODIAL SNACONTROL AUTODIAL Causes an SNA node’s auto-dial modem to dial. Syntax SNACONTROL AUTODIAL;NODE=NodeName Use SNACONTROL AUTODIAL can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameter NodeName Conditionally required. The name of the active SNA node you want to cause to automatically dial. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.
MPE Commands SNACONTROL AUTODIAL Example SNACONTROL AUTODIAL;NODE=IBMNODE The auto-dial modem configured for node IBMNODE is caused to dial.
MPE Commands SNACONTROL START SNACONTROL START Starts an SNA node, link-level tracing, and SNA Transport node tracing. Syntax SNACONTROL START;NODE=NodeName [;LINKTRACE[=[TraceType][,TraceFile]]] [;NODETRACE[=TraceFile]] [;ERROPT=ErrorOption] [;TFILESIZE=NumRecords] Use SNACONTROL START can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameters NodeName Conditionally required. The name of the configured SNA node you want to start.
MPE Commands SNACONTROL START error will occur. If you do not specify an account for a link-level trace file, the file will automatically be written to the SYS account. If you specify a file that does not exist, NMS builds a new one and opens it to record tracing. If you specify an existing file that NMS does not currently have open to record tracing, NMS will overwrite the file’s previous contents; no warning is issued.
MPE Commands SNACONTROL START If you are using a manual-dial modem, you can begin to dial after this logging message is displayed on the console: Node NodeName ready for activation by host Note that if you are using a manual-dial modem, console logging for SNA Transport logging class CLAS0013 must be enabled (see Chapter 3 , “Logging Configuration,”) so that the above message can be displayed. Also, note that once a node is active, reissuing this command for that node causes an error.
MPE Commands SNACONTROL STATUS SNACONTROL STATUS Displays the status of a specific SNA node.
MPE Commands SNACONTROL STATUS LUName The name of the LU whose session status you want displayed. The name can be up to eight alphanumeric characters long. The first character must be alphabetic. If this parameter is specified, neither the NAU nor LFSID parameters can be specified. Specifying this parameter without an LU name causes the sessions to be displayed in alphabetical order. NAU The NAU number of the dependent session whose status you want to display.
MPE Commands SNACONTROL STATUS ROUTE Specifies that the session’s Routing Table entry (packets received) is to be displayed. This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation. LURECORD Specifies that the session’s LU record is to be displayed. This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation. LINK This is the same as specifying the ALL link status parameter (described below).
MPE Commands SNACONTROL STATUS This information is explained in more detail after the examples later in this command description. CONFIGURATION Configuration data for the link is displayed: SDLC: • Link name • Link type • Link state • Physical path • Phone number • Auto dial status • Station ID • XID • Receive timeout • Error retries • Cable type • Buffer size • Connect timeout • Local timeout • Transmission speed X.
MPE Commands SNACONTROL STATUS — Call direction — Maximum call retries — Call retry delay — Call retry count Token Ring: • Link name • Link type • Link state • Physical path • Data rate • Current station address • Default station address • Functional address mask This information is explained in more detail after the examples later in this command description.
MPE Commands SNACONTROL STATUS • Overhead bytes received • Total frames received • Data frames received • Oversized frames received • Aborted frames received • Receive overruns • CRC errors • Statistics resets X.
MPE Commands SNACONTROL STATUS DIAGSTATS All of the status information for the link is displayed: • Link state status (see the LINKSTATE parameter description) • Link configuration data (see the CONFIGURATION parameter description) • Link statistics (see the STATISTICS parameter description) • Link diagnostics This parameter is for Hewlett-Packard debugging purposes, and should be used only under HP recommendation. RESET Link statistics are gathered from the time the link is started.
MPE Commands SNACONTROL STATUS where IBMNODE is already active could generate this display: Linkname: IBMNODE Linktype: SNA/SDLC Linkstate: CONNECTING LEVEL 1 Physical Path 40 Phone Number Auto Dial 0 Cable Type Station ID C1 Buffer Size XID XID6789012 Connect Timeout Receive Timeout 180 sec Local Timeout Error Retries 7 Transmission Speed Connect Duration Data Bytes Sent Overhead Bytes Sent Total Frames Sent Data Frames Sent Bytes Retransmitted Frames Retransmitted DSR Losses CTS Losses Unexpected DCD Car
MPE Commands SNACONTROL STATUS • CONNECTED LEVEL 2 = A level 2 connection has been established. • CONNECTING LEVEL 1 = A level 1 connection is in progress. • CONNECTING LEVEL 2 = A level 2 connection is in progress. • DISCONNECTING LVL 1 = A level 1 disconnection is in progress. • DISCONNECTING LVL 2 = A level 2 disconnection is in progress. • ERROR = The SDLC link driver has detected a link error. The physical path is the address of the PSI.
MPE Commands SNACONTROL STATUS The local timeout is the number of seconds the SDLC link driver will wait for PSI card activity before reporting a PSI failure. The transmission speed is the transmission speed (in bits per second) of the line being used by the link if a modem is not being used. If a modem is being used, the modem determines the speed. The connect duration is how long a level 2 connection has been maintained.
MPE Commands SNACONTROL STATUS Receive overruns is the total number of received frames that contained no control bytes. CRC errors is the total number of received frames that contained a Cyclical Redundancy Check (CRC) error. Statistics resets is the total number of times the statistics have been cleared. X.25 Link-Level Status Information Two examples of X.25 link-level status displays are given below, and the terminology used is described after the examples.
MPE Commands SNACONTROL STATUS where IBMNODE is already active, and a permanent virtual circuit (PVC) is being used, could generate this display: LINKNAME : IBMNODE SNA CONNECTED TRACING LINKTYPE : SNA X.25 : ON LINKSTATE: TRACEFILE: TRACE.PUB.
MPE Commands SNACONTROL STATUS where IBMNODE is already active, and a switched virtual circuit (SVC) is being used, could generate this display: LINKNAME : IBMNODE SNA CONNECTED TRACING LINKTYPE : SNA X.25 : ON LINKSTATE: TRACEFILE: TRACE.PUB.
MPE Commands SNACONTROL STATUS Terminology The linkname is the same as the node name. The linktype is “SNA X.25”. The linkstate is one of the following: • SNA CONNECT PENDING = The virtual circuit to the remote system has been established and an SNA connection (which must use the virtual circuit) is in the process of being established. • SNA CONNECTED = The SNA and X.25 connections to the remote system have been established. • SNA DISCONNECT PENDING = The SNA connection is in the process of terminating.
MPE Commands SNACONTROL STATUS without success. Note that this information is displayed for an outgoing SVC only. The call retry delay is the number of seconds the QLLC module will wait between attempts to connect to the remote system. Note that this information is displayed for an outgoing SVC only. The call retry count is the number of times call retries have been attempted. Note that this information is displayed for an outgoing SVC only.
MPE Commands SNACONTROL STATUS where IBMNODE is already active could generate this display: Linkname: IBMNODE CONNECTED Physical Path: Linktype: IEEE8025 48 Linkstate: Data Rate: 16 Mbps Current Station Address: Default Station Address: Functional Address Mask: 10-00-90-00-00-07 10-00-90-90-C8-46 00-00-00-00 Transmits no error: Transmit byte count: Transmit errors: 6614976 2368752825 0 Receives no error: Receives byte count: Receive errors: 6620830 2367702513 0 NAME ======== XPORTPU XPORTLU XPOR
MPE Commands SNACONTROL STATUS The current station address is the currently-active station address. The default station address is the factory-configured default station address. The function address mask is the address mask as described in the IBM Token-Ring Network Architecture Reference. Transmits no error is the number of frames transmitted without errors. Receives no error is the number of frames received without errors. Transmit byte count is the number of bytes transmitted without errors.
MPE Commands SNACONTROL STATUS Terminology The name is the PU or LU name. Note that XPORTPU and XPORTLU are the internal names that are used by SNA Transport. XPORTPU is a PU name used for maintaining the PU-SSCP session. XPORTLU is the LU name used for maintaining the LU-SSCP sessions (for dependent LUs). The type is the type of the session. This is either PU-SSCP for PU-SSCP sessions, LU-SSCP for LU-SSCP sessions, DEP_LU for dependent LU-LU sessions, or IND_LU for independent LU-LU sessions.
MPE Commands SNACONTROL STATUS • PEND_SON = Pending session outage notification. A Session Outage Notification (SON) deactivation request has been generated internally or received on the link. However, no response has been sent. • RESET = The initial state. No sessions exist. The user is the name of the user or program that owns the session. The trace file is the name of the trace file, if tracing has been turned on. If tracing is off, OFF is displayed.
MPE Commands SNACONTROL STOP SNACONTROL STOP Stops an SNA node and all activity on the node. Syntax SNACONTROL STOP;NODE=NodeName[;TYPE=StopType] Use SNACONTROL STOP can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameters NodeName Conditionally required. The name of the active SNA node you want to stop. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.
MPE Commands SNACONTROL STOP • Q = (Quiesce) The node is stopped in an orderly way. SNA Transport notifies the SNA services that it is stopping. Each service completes sending and receiving all active data sets. As the LUs become inactive, the services stop the LU-LU sessions, and SNA Transport stops the LU-SSCP sessions. Then, SNA Transport shuts down the PU-SSCP session.
MPE Commands SNACONTROL STOPSESS SNACONTROL STOPSESS Stops an LU-LU session without stopping the SNA node. Syntax SNACONTROL STOPSESS;NODE=NodeName;LUNAME=LUName [;TYPE=StopType] Use SNACONTROL STOPSESS can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameters NodeName Conditionally required. The name of the active SNA node the LU-LU session is on.
MPE Commands SNACONTROL STOPSESS • Q = (Quiesce) The session is stopped in an orderly way. SNA Transport notifies the SNA services that it is stopping the specified LU. Each service completes sending and receiving all active data sets in the LU-LU session. Once the session is stopped, a logging message specifying that the LU-LU session has terminated is generated. Default: Q Description SNACONTROL STOPSESS stops an LU-LU session without stopping the SNA node.
MPE Commands SNACONTROL TRACEOFF SNACONTROL TRACEOFF Turns off link-level tracing, and SNA Transport node tracing. Syntax SNACONTROL TRACEOFF;NODE=NodeName;LINKTRACE ;NODETRACE ;INTRINSIC=LUName Use SNACONTROL TRACEOFF can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameters NodeName Conditionally required. The name of the active SNA node for which you want to turn tracing off.
MPE Commands SNACONTROL TRACEOFF Description SNACONTROL TRACEOFF turns off link-level tracing (with the LINKTRACE parameter), SNA Transport intrinsic tracing (with the INTRINSIC parameter, and SNA Transport node tracing and NS over SNA tracing (with the NODETRACE parameter). Note that SNA Transport node tracing is also turned off with SNACONTROL STOP. Tracing is described in Chapter 5 , “SNA Link Troubleshooting,” of this manual. NOTE You must specify at least one type of tracing.
MPE Commands SNACONTROL TRACEON SNACONTROL TRACEON Turns on link-level tracing, SNA Transport intrinsic tracing, and SNA Transport node tracing. Syntax SNACONTROL TRACEON;NODE=NodeName [;LINKTRACE[=[TraceType][,TraceFile]]] [;INTRINSIC=LUName[,TraceFile]] [;NODETRACE[=TraceFile]] [;TFILESIZE=NumRecords] Use SNACONTROL TRACEON can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameters NodeName Conditionally required.
MPE Commands SNACONTROL TRACEON contents; no warning is issued. If you specify an existing file that NMS already has open to record tracing (even if it is recording events from a different subsystem), NMS will record trace events for this subsystem to the file in addition to the events that it is currently recording. This allows you to record tracing events from several subsystems to a single file. Default: NMTCnnnn.PUB.
MPE Commands SNACONTROL TRACEON displayed, and the command would have to be reissued with the proper NODE=NodeName parameter included. SNACONTROL TRACEON;LINKTRACE=,TF01 Partial (the default) link-level tracing is to be started for the only active SNA node, and the trace data is to be written to the file TF01.
MPE Commands SNACONTROL VERSION SNACONTROL VERSION Identifies the software version of SNA Transport, SNA/X.25 Link, and SNA/Token Ring Link. Syntax SNACONTROL VERSION Use SNACONTROL VERSION can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Description SNACONTROL VERSION identifies versions of SNA Transport program files, NL procedures, and SL procedures, as well as the overall version. It also identifies versions of the SNA/X.
MPE Commands SNACONTROL VERSION Example Typing SNACONTROL VERSION generates a display like this: SNA TRANSPORT 32098-20023 module versions: NL NL NL NL NL procedure: procedure: procedure: procedure: procedure: SNACMD_VERS SNAINTR_VERS SNATC_VERS SNAPC_VERS SNACBACCS_VERS NL SL NL NL SL NM NM NM NM NM procedure: SNAUTIL_VERS procedure: SNACMSTUB_VERS procedure: SNANMSTUB_VERS procedure: SNANMFMT_VERS procedure: SNACMFMT_VERS program file: SNASSV.PUB.SYS program file: SNACSC.PUB.
MPE Commands SWITCHNMLOG SWITCHNMLOG Closes the current NM log file and creates and opens a new one. Syntax SWITCHNMLOG [UPDATE ] [filenumber] Use SWITCHNMLOG can be issued from a session, a job, a program, or in break. Pressing [BREAK] has no effect on this command. Parameters UPDATE Updates logging configuration for all subsystems.
MPE Commands SWITCHNMLOG command’s normal display: NMLG FILE NUMBER nnnn IS mm% FULL NMLG FILE NUMBER nnnn ERROR #nn. NM LOGGING SUSPENDED. (NMCNERR 38) Once the error is corrected, you can issue the RESUMENMLOG command (described earlier in this chapter).
SNA Link Installation Information 7 SNA Link Installation Information This chapter contains information you need to know about installation of the SNA link products. To run an SNA link product on the HP 3000, you must install the product, and then your Hewlett-Packard support contact must configure your HP 3000 environment to support the product. Before the Hewlett-Packard support contact arrives to do the minimum configuration of the SNA link product on the HP 3000, you must do these things: 1.
SNA Link Installation Information 172 Chapter 7
Messages A Messages This appendix contains messages that are unique to SNA link activity. These messages are described: • SDLC link startup error messages: These are messages that can occur when you start the SDLC link. These messages occur when the SNACONTROL START command calls the WAN_Module_Config procedure and encounters an error.
Messages Link connect failure on node NodeName subsystem = SubsysID, procedure = ProcNum, error num = ErrorNum Link failure, recovery in progress on node NodeName subsystem = SubsysID, procedure = ProcNum, error num = ErrorNum Link failure, shutting down the node NodeName subsystem = SubsysID, procedure = ProcNum, error num = ErrorNum • X.25 link module configurator error codes: These are codes that are generated by the X.25 link module configurator.
Messages SDLC Link Startup Error Messages SDLC Link Startup Error Messages Listed below are the messages that might occur when you are starting the SDLC link. These messages occur when the SNACONTROL START command calls the WAN_Module_Config procedure and encounters an error. Depending on the logging configuration for the SDLC Link subsystem, these messages are logged to the console, to disk, or both.
Messages SDLC Link Startup Error Messages because this should not happen. The file system integrity might be questionable. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 5 MESSAGE: Could not open download file. CAUSE: The file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS was purged or renamed. ACTION: Restore the file from a backup tape and try to start the SDLC link again. CAUSE: The file PSISDLC0.PUB.SYS or PSISDLC1.PUB.
Messages SDLC Link Startup Error Messages 10 MESSAGE: Could not stop trace. CAUSE: Tracing might have been turned off with the SNACONTROL TRACEOFF command, but the link software status indicates that it was on. ACTION: Ignore this problem unless you are experiencing other problems. If you are, write down the error information displayed on the console and call your Hewlett-Packard support contact. 11 MESSAGE: Could not freeze the driver configuration data. CAUSE: Memory shortage problems are occurring.
Messages SDLC Link Startup Error Messages 17 MESSAGE: Could not unfreeze the configuration data. CAUSE: Memory problems are occurring. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 18 MESSAGE: Unable to obtain dump/diag ports. CAUSE: The Diagnostic User Interface (DUI) software or the Network Dump Process was not installed properly.
Messages SDLC Link Startup Error Messages error information displayed on the console and call your Hewlett-Packard support contact. 21 MESSAGE: Could not add the link name to the link table. CAUSE: Another link with the same name has already started. ACTION: Try shutting down the link and starting it up again. CAUSE: The link table does not exist. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. CAUSE: The link table has been corrupted.
Messages SDLC Link Driver Error Messages SDLC Link Driver Error Messages Listed below are the messages that are generated by the SDLC link driver. Depending on the logging configuration for the SDLC Link subsystem, these messages are logged to the console, to disk, or both.
Messages SDLC Link Driver Error Messages CAUSE: The host system is transmitting data before the HP 3000 sends a final bit in its frame to relinquish control of the line. ACTION: Run the SNACONTROL STATUS command, and check the Frames Retransmitted value in the link-level status information (see Chapter 6 , “MPE Commands,” of this manual).
Messages SDLC Link Driver Error Messages CAUSE: Bad PSI hardware. ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI. 1007 MESSAGE: Unknown PSI fatal error. CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt. ACTION: Replace the download file from your latest system update tape. CAUSE: Bad PSI hardware. ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.
Messages SDLC Link Driver Error Messages 1014 MESSAGE: PSI detected a bad checksum during download. CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt. ACTION: Replace the download file from your latest system update tape. CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed. ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.
Messages SDLC Link Driver Error Messages 1020 MESSAGE: PSI reported an unknown severe error type. CAUSE: Unknown. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 1023 MESSAGE: Unable to obtain IODC information from IO_GET_MODULE_REC during initialization. CAUSE: Unknown. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.
Messages SDLC Link Driver Error Messages ACTION: Your Hewlett-Packard support contact will have to ru2 diagnostics on the PSI. 1028 MESSAGE: A call to IO_CONFIG_INT failed during driver initialization. CAUSE: Unknown. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 1030 MESSAGE: PSI register test failed during PSI initialization. CAUSE: Bad PSI hardware.
Messages SDLC Link Driver Error Messages 1035 MESSAGE: No TAB data structures available. CAUSE: Top-plane Activity Block (TAB) internal data structures are used whenever the driver tries to start new hardware activity. A limited number of these data structures are available. Unexpected use of an incorrect port and subqueues might have created excessive pending hardware activity. This problem can also occur if a buffer manager buffer could not be obtained.
Messages SDLC Link Driver Error Messages 1039 MESSAGE: Unable to release a buffer manager buffer. CAUSE: The driver tried to free memory that the buffer manager did not recognize as a valid buffer because of a driver problem or memory data corruption. Also, a problem somewhere might have caused the driver to try to free a buffer that was not in use ACTION: A system dump will probably be required. Call your Hewlett-Packard support contact. 1040 MESSAGE: Unable to obtain an I/O Services timer.
Messages SDLC Link Driver Error Messages ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 1045 MESSAGE: Unable to release an I/O Services message frame. CAUSE: A call to the system message freeing routine returned in error. The port might belong to a process that no longer exists or is not operating with the required capabilities. Also, the message frame might not have been recognized by the system as a valid message frame.
Messages SDLC Link Driver Error Messages ACTION: If this problem occurs repeatedly, call your Hewlett-Packard support contact. 1051 MESSAGE: Request received when hardware in bad state. CAUSE: The hardware was not ready to process a request message that required hardware participation. ACTION: Retry the request at a later time. If the problem continues, call your Hewlett-Packard support contact. 1052 MESSAGE: Not enough TARs available to process request.
Messages SDLC Link Driver Error Messages driver did not find its own subsystem number in the expected buffer field. ACTION: Run NMMAINT to verify that the software versions between the driver (WANSDLCVERS) and module configurator (WANMCVERS) are correct. Also check your configuration screens, and if necessary, restore NMCONFIG.PUB.SYS from a system backup tape. If the problem continues, call your Hewlett-Packard support contact. 1057 MESSAGE: Input buffer passed in a message is too small.
Messages SDLC Link Driver Error Messages 1061 MESSAGE: Bad middle plane buffer pool in configuration data. CAUSE: The buffer pool ID of a pool that is to be used for read/write data communications line frames must be in a configuration buffer passed during startup. However, the driver found an ID of zero, which is an invalid ID. The transport should not have invoked the module configurator if the buffer pool could not be opened. Also, configuration buffer formats might be mismatched.
Messages SDLC Link Driver Error Messages error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 1065 MESSAGE: Local timer popped. CAUSE: This timeout should occur only if the PSI hardware hangs because of a hardware failure or a bug in the downloaded code. The driver solicited activity from the hardware “local timeout” seconds ago, and that activity has still not completed.
Messages SDLC Link Driver Error Messages 2004 MESSAGE: Disconnect timer popped before outstanding I-frames acknowledged. CAUSE: The remote system never acknowledged one or more Information (I) frames sent to it. You might have a very noisy line, or the remote system might not be running. ACTION: See whether the remote system is still running. 2005 MESSAGE: Disconnect timer popped attempting to sever level 2 connection.
Messages SDLC Link Driver Error Messages CAUSE: The I frame was never acknowledged, because the frame was delayed by the network longer than the configured REPLYTO parameter on the host system. ACTION: Check all possible network delays, and increase the REPLYTO operand of the GROUP macro in the host’s ACF/NCP generation accordingly. 2010 MESSAGE: PSI detects an internal error. CAUSE: The PSI is experiencing problems.
Messages SDLC Link Driver Error Messages 2015 MESSAGE: Autodial not completed. CAUSE: The automatic dial was not completed. This can happen when the remote system’s modem is not turned on or is not functional. ACTION: Check with the remote system to ensure that its modems are turned on and functional. 2016 MESSAGE: Local autodial modem not powered on. CAUSE: Your local automatic-dial modem has not been turned on. ACTION: Turn on your local automatic-dial modem.
Messages SNACONTROL Error Messages SNACONTROL Error Messages Listed below are the error messages that can be returned by SNACONTROL commands. They are listed in numerical order according to message number. These messages are written to $STDLIST; they are not logged. NMS messages might also be returned in response to SNACONTROL commands. For a list of those messages and their meanings, see the Using the Node Management Services Utilities manual.
Messages SNACONTROL Error Messages tracing, ensure that you are specifying the LINKTRACE parameter in the SNACONTROL TRACEOFF command. CAUSE: The SNACONTROL TRACEOFF command was issued after the SNA node has started to shut down. ACTION: None; tracing is automatically turned off when a node is shutting down. SNACIERR 5 MESSAGE: COULDN’T OPEN TRACE FILE. (SNACIERR 5) CAUSE: An illegal TraceFile parameter was specified in an SNACONTROL START or SNACONTROL TRACEON command.
Messages SNACONTROL Error Messages SNACIERR 9 MESSAGE: NODE SPECIFIED NOT ACTIVE. (SNACIERR 9) CAUSE: An SNACONTROL command was issued for an SNA node that is not active. The node either was never started or has been stopped. ACTION: Issue the SNACONTROL STATUS command to see whether the node is active. If the node is not active, issue the SNACONTROL START command for the node. Once the node is active, reissue the first SNACONTROL command.
Messages SNACONTROL Error Messages SNACIERR 14 MESSAGE: UNABLE TO OPEN BUFFER POOL. (SNACIERR 14) CAUSE: An internal system error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 16 MESSAGE: UNABLE TO CREATE PORTS FOR SNA SERVERS. (SNACIERR 16) CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 17 MESSAGE: COULDN'T START SNASSV PROCESS.
Messages SNACONTROL Error Messages number is not in the configured PVC range in the DTC X.25 configuration. ACTION: Issue the NETCONTROL command to verify the X.25 link status and start the link if necessary. When you check the link’s status, verify that the X.25 Level 1 status is “connected,” Level 2 is “on,” and Level 3 is “ready.” If the link status is correct, ensure that the SNA/X.25 Link configuration and the X.25/XL System Access configuration are compatible with each other and with the X.
Messages SNACONTROL Error Messages ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 27 MESSAGE: COULDN’T GET DIRECTORY INFO. (SNACIERR 27) CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 28 MESSAGE: THE LUNAME MUST BE SPECIFIED. (SNACIERR 28) CAUSE: The ROUTE, HSCB, or LURECORD parameter was specified in the SNACONTROL STATUS command, but no LUName parameter was specified.
Messages SNACONTROL Error Messages SNACIERR 36 MESSAGE: CAN’T SPECIFY STYPE HERE. (SNACIERR 36) CAUSE: The STYPE parameter was specified in an SNACONTROL command; none of the commands uses STYPE. ACTION: Reissue the command without an STYPE parameter. SNACIERR 37 MESSAGE: CAN’T SPECIFY STOP TYPE HERE. (SNACIERR 37) CAUSE: The StopType parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STATUS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command.
Messages SNACONTROL Error Messages SNACIERR 45 MESSAGE: CAN’T SPECIFY DEBUG HERE. (SNACIERR 45) CAUSE: The DEBUG parameter was specified in an SNACONTROL command; none of the commands uses DEBUG. ACTION: Reissue the command without a DEBUG parameter. SNACIERR 46 MESSAGE: SNA SWITCH FROM COMPAT. MODE TO NATIVE MODE ERROR. (SNACIERR 46) CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact.
Messages SNACONTROL Error Messages ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 51 MESSAGE: CAN’T SPECIFY LUNAME HERE. (SNACIERR 51) CAUSE: The LUName parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, or SNACONTROL VERSION command. None of these commands uses LUName. ACTION: Reissue the command without an LUName parameter. SNACIERR 52 MESSAGE: CAN’T SPECIFY LINKTRACE HERE.
Messages SNACONTROL Error Messages SNACIERR 60 MESSAGE: CAN’T SPECIFY “LINK=A” HERE. (SNACIERR 60) CAUSE: The LINK=A parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=A. ACTION: Reissue the command without a LINK=A parameter. SNACIERR 61 MESSAGE: CAN’T SPECIFY “LINK=C” HERE.
Messages SNACONTROL Error Messages STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=ALL. ACTION: Reissue the command without a LINK=ALL parameter. SNACIERR 67 MESSAGE: CAN’T SPECIFY “LINK=CONF” HERE. (SNACIERR 67) CAUSE: The LINK=CONF parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command.
Messages SNACONTROL Error Messages SNACIERR 72 MESSAGE: CAN’T SPECIFY “LINK=CONFIGURATION” HERE. (SNACIERR 72) CAUSE: The LINK=CONFIGURATION parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=CONFIGURATION. ACTION: Reissue the command without a LINK=CONFIGURATION parameter. SNACIERR 73 MESSAGE: CAN’T SPECIFY “LINK=LINKSTATE” HERE.
Messages SNACONTROL Error Messages SNACIERR 77 MESSAGE: COULDN’T CREATE SNA’S PORT FACILITY PROCESS. (SNACIERR 77) CAUSE: A call to Create_pfp to create SNA’s port facility process during SNACSC’s initialization failed. This is an internal error. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 78 MESSAGE: COULDN’T GET THE PIN OF SNA’S PORT FACILITY PROCESS.
Messages SNACONTROL Error Messages ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNACIERR 84 MESSAGE: CAN’T SPECIFY LURECORD HERE. (SNACIERR 84) CAUSE: The LURECORD parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LURECORD. ACTION: Reissue the command without an LURECORD parameter.
Messages SNACONTROL Error Messages SNACIERR 90 MESSAGE: LOCAL AUTODIAL MODEM IS NOT POWERED ON. (SNACIERR 90) CAUSE: The local automatic-dial modem is not turned on. ACTION: Turn the modem on. SNACIERR 91 MESSAGE: AUTODIAL NOT COMPLETED. (SNACIERR 91) CAUSE: The automatic dial was not completed, possibly because the remote system’s modem is not turned on or is not functional. ACTION: Ensure that the remote system’s modems are turned on and functional.
Messages SNACONTROL Error Messages SNACIERR 105 MESSAGE: CAN’T SPECIFY LFSID HERE. (SNACIERR 105) CAUSE: LFSID was specified as a parameter to an SNACONTROL command other than SNACONTROL STATUS. Only SNACONTROL STATUS permits this parameter. ACTION: Don’t specify LFSID as a parameter to any SNACONTROL command except SNACONTROL STATUS. SNACIERR 106 MESSAGE: CAN’T SPECIFY NAU HERE. (SNACIERR 106) CAUSE: NAU was specified as a parameter to an SNACONTROL command other than SNACONTROL STATUS.
Messages SNACONTROL Error Messages ACTION: The LFSID= parameter must specify an existing LFSID. SNACIERR 113 MESSAGE: BAD LUNAME SPECIFICATION. (SNACIERR 113) CAUSE: A bad LUNAME was specified in the LUNAME= parameter. ACTION: Verify that the LUNAME= parameter was valid. SNACIERR 114 MESSAGE: NO SUCH SESSIONS FOUND. (SNACIERR 114) CAUSE: No sessions were found that match the given STATE= and SESSTYPE= parameters. ACTION: None. This is a normal event. SNACIERR 115 MESSAGE: BAD TOKEN RING LINK NAME.
Messages SNA Transport Error Messages SNA Transport Error Messages Listed below are the error messages that can occur when SNA Transport intrinsics are being used. They are listed in numerical order according to message number. SNA Transport, itself, does not display these messages: It returns the error number to the SNA service using the intrinsics, and the service can optionally display the message. These messages are not logged; they are written to $STDLIST by the SNA service only.
Messages SNA Transport Error Messages SNAERR 9 MESSAGE: No available AFT entry. (SNAERR 9) No room left in current stack segment for another AFT. CAUSE: An SNAOpenUser was attempted, but no room for another Available File Table (AFT) entry is available in the current stack segment. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNAERR 10 MESSAGE: Bad PI in RH. (SNAERR 10) The Pacing indicator was set in the RH sent to SNA Transport.
Messages SNA Transport Error Messages SNAERR 15 MESSAGE: Internal Error. (SNAERR 15) An SNA Transport Internal Error occurred. CAUSE: A serious error occurred in SNA Transport. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNAERR 16 MESSAGE: Invalid RU size. (SNAERR 16) An attempt was made to send an RU longer than the Max RU size.
Messages SNA Transport Error Messages SNAERR 21 MESSAGE: Invalid LU name. (SNAERR 21) The LU name specified does not exist. CAUSE: A call to the SNAOpenUser intrinsic to open an LU-LU session was made, but the LU name specified in the call is not configured for this node. ACTION: Use NMMGR or the configuration file critical summary to check for the valid LUs configured for the requested node. SNAERR 22 MESSAGE: Invalid session type. (SNAERR 22) An attempt was made to open a non LU-LU session.
Messages SNA Transport Error Messages ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNAERR 28 MESSAGE: Invalid function code. (SNAERR 28) CAUSE: An SNA service passed a bad function code to the SNAControl or SNASessinfo intrinsic. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNAERR 29 MESSAGE: Inactive node or invalid node name. (SNAERR 29) CAUSE: An invalid node name was specified in a call to the SNAOpenUser intrinsic.
Messages SNA Transport Error Messages SNAERR 36 MESSAGE: Link shutdown occurred. (SNAERR 36) CAUSE: A link shutdown has been requested with the SNACONTROL STOP command, and all sessions are being notified. ACTION: Wait until the link has been restarted and then continue. SNAERR 37 MESSAGE: Protocol shutdown requested. (SNAERR 37) CAUSE: A protocol shutdown has been requested with the SNACONTROL STOP command, and all sessions are being notified.
Messages SNA Transport Error Messages SNAERR 51 MESSAGE: Link Failure occurred. (SNAERR 51) CAUSE: A link failure has occurred, and all sessions are being notified. ACTION: Wait until the node has been reactivated and then try again. SNAERR 52 MESSAGE: SNA Transport Internal Error Shutdown. (SNAERR 52) CAUSE: An SNA Transport internal error has occurred, and all sessions are being notified. ACTION: Write down the circumstances and call your Hewlett-Packard support contact.
Messages SNA Transport Error Messages SNAERR 103 MESSAGE: Invalid session control protocol. (SNAERR 103) CAUSE: An invalid sequence of session control events has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. SNAERR 104 MESSAGE: RQR request pending. (SNAERR 104) CAUSE: An attempt to send a ReQuest Recovery (RQR) request was made while in a state other than reset. ACTION: Write down the circumstances and call your Hewlett-Packard support contact.
Messages SNA Transport Error Messages SNAERR 111 MESSAGE: No such activation request (BIND,ACTLU,ACTPU) received. (SNAERR 111) CAUSE: An SNA service is trying to send a response to an activation request (BIND, ACTLU, or ACTPU), but no such activation request has been received. ACTION: The SNA service should examine the situations in which an activation response is sent, and verify that a response is sent only after an activation request has been received.
Messages SNA Transport Logging Messages SNA Transport Logging Messages Listed below are the messages that are logged for SNA Transport. Note that these messages can be logged singly or in groups. They are listed here singly, in alphabetical order according to the first word of the message. MESSAGE: PathInfoUnit CAUSE: This message is used to print a Path Information Unit (PIU) as part of a logging message. ACTION: None.
Messages SNA Transport Logging Messages MESSAGE: Host beginning activation of node NodeName CAUSE: SNA Transport received the ACTivate Physical Unit (ACTPU) request for the indicated node. ACTION: None; this is a normal event. MESSAGE: HP IS PRIMARY LU LUName CAUSE: This is part of the OpenUser/CloseUser logging messages. It indicates that the user is a primary LU, capable of issuing a BIND request. ACTION: None; this is a normal event.
Messages SNA Transport Logging Messages MESSAGE: Link failure, recovery in progress on node NodeName CAUSE: A recoverable link failure has occurred on the indicated node. ACTION: Call your Hewlett-Packard support contact. MESSAGE: Link failure, shutting down the node NodeName CAUSE: An irrecoverable link error has occurred on the indicated node. ACTION: Call your Hewlett-Packard support contact.
Messages SNA Transport Logging Messages CAUSE: SNA Transport received an error from the SDLC link driver because it received a busy signal or no answer at all from the remote system. ACTION: This should be a temporary problem. Wait a few minutes and then try re-dialing. MESSAGE: NETVIEW ALERT — Inoperative dialing device on node NodeName CAUSE: SNA Transport received an error from the SDLC link driver because it detected that the automatic calling unit (ACU) is not on or that the cable is missing.
Messages SNA Transport Logging Messages MESSAGE: Node NodeName shut down completed CAUSE: Node shutdown has completed successfully. The indicated node is no longer active. ACTION: None; this is a normal event. MESSAGE: Node shutdown in progress CAUSE: SNA Transport is discarding a Path Information Unit (PIU) received during the node shutdown. ACTION: None; this is a normal event. MESSAGE: Open user granted on node NodeName CAUSE: A request to open an LU user has been granted.
Messages SNA Transport Logging Messages ACTION: None; this is a normal event. The welcome screen is retransmitted by the remote system when the LU-LU session is established. MESSAGE: PU type 2.1 XID3 (negotiable) exchange protocol error on node NodeName CAUSE: SNA Transport detected an XID3 protocol violation. This may cause the MPE/iX SNA node to shut down. ACTION: Submit node trace, SNA/Transport version, NMCONFIG.PUB.SYS, and a console logging list to the Hewlett-Packard support contact.
Messages SNA Transport Logging Messages MESSAGE: Received PIU with invalid TH CAUSE: SNA Transport received a Path Information Unit (PIU) whose Transmission Header (TH) is not of the supported format. ACTION: Call your Hewlett-Packard support contact. MESSAGE: Received too long RU CAUSE: SNA Transport received a Path Information Unit (PIU) whose Request/Response Unit (RU) is longer than the maximum RU size specified in the BIND. ACTION: Call your Hewlett-Packard support contact.
Messages SNA Transport Logging Messages MESSAGE: Received XID3 with format error on node NodeName CAUSE: SNA Transport received an XID3 with illegal format. ACTION: The remote host does not conform to the XID3 exchange protocol. Submit an SR along with an SNA node trace, SNA/Transport version, NMCONFIG.PUB.SYS, a console logging list, and time and date of error to the Hewlett-Packard support contact. MESSAGE: Remote node did not support PU type 2.
Messages SNA Transport Logging Messages ACTION: Software internal error. Submit node trace, SNA/Transport version, NMCONFIG.PUB.SYS, and console logging list to the Hewlett-Packard support contact. MESSAGE: SDI rendezvous request failure on node NodeName CAUSE: The value specified in Local SSAP field in the SNA Node Token Ring Link screen is being used by another node.
Messages SNA Transport Logging Messages MESSAGE: Session terminated on node NodeName CAUSE: The indicated session received and processed a DeACTivate Physical Unit (DACTPU), DeACTivate Logical Unit (DACTLU), or UNBIND, as applicable. ACTION: None; this is a normal event. MESSAGE: Shutdown type = Internal error CAUSE: This is part of the logging messages “Node NodeName all sessions closed — beginning shutdown” and “Node NodeName shut down completed” (each message is described earlier in this listing).
Messages SNA Transport Logging Messages MESSAGE: Shutdown type = Quiesce CAUSE: This is part of the logging messages “Node NodeName all sessions closed — beginning shutdown” and “Node NodeName shut down completed” (each message is described earlier in this listing). This message indicates the type of shutdown (quiesce) that is in progress. ACTION: None. MESSAGE: SIDH = SessIDHi, SIDL = SessIDLo, ODAI OAFDAFAssgnInd CAUSE: This is part of the OpenUser/CloseUser logging messages.
Messages SNA Transport Logging Messages MESSAGE: Subsystem = SubsysID, Error Code = ErrorCode CAUSE: This is associated with the “INTERNAL ERROR ErrorNum IN NODE NodeName” logging message (the message is described earlier in this listing). ACTION: Write down the SubsysID and ErrorCode, and call your Hewlett-Packard support contact.
Messages SDLC Link Shutdown Error Messages SDLC Link Shutdown Error Messages Listed below are the messages that might occur when you are stopping the SDLC link. These messages occur when the SNACONTROL STOP command calls the WAN_Kill_Module procedure and encounters an error. Depending on the logging configuration for the SDLC Link subsystem, these messages are logged to the console, to disk, or both.
Messages SDLC Link Shutdown Error Messages ACTION: Ensure that the NodeName specified in the SNACONTROL STOP command is correct and try again. The link might have already been shut down. 56 MESSAGE: Could not delete the auxiliary buffer pool. CAUSE: Many causes exist; the Status field of the message provides more-detailed information about the specific cause of the problem. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.
Messages X.25 Link Failure Error Codes X.25 Link Failure Error Codes Listed below are the codes that are generated for X.25 link failures by the Qualified Logical Link Control (QLLC) module.
Messages X.25 Link Failure Error Codes -74 MESSAGE: DATACOM LINE LOST CAUSE: The virtual circuit has terminated. That is, it has been cleared, reset, or restarted. ACTION: Since this is a recoverable link error, restart the SNA node. If the error still occurs, call your Hewlett-Packard support contact. -76 MESSAGE: DISCONNECT TIMER POPPED CAUSE: The X.25 link has timed out while waiting for a solicited Q disconnect (QDC) from the remote system.
Messages X.25 Link Failure Error Codes -83 MESSAGE: UNEXPECTED QDC CAUSE: The remote system has sent an unsolicited Q disconnect (QDC). ACTION: Restart the SNA node. If the problem still occurs, call your Hewlett-Packard support contact. -84 MESSAGE: UNEXPECTED QSM CAUSE: The remote system has sent a QSM after the SNA connection has already been established. ACTION: Since this is a recoverable link error, the SNA node will be revived. So, no action is necessary.
Messages X.25 Link Module Configurator Error Codes X.25 Link Module Configurator Error Codes Listed below are the error codes that are generated by the X.25 link module configurator. These messages are displayed on the HP 3000 operator's console.
Messages X.25 Link Module Configurator Error Codes -204 MESSAGE: STATUS BUFFER INVALID CAUSE: The Qualified Logical Link Control (QLLC) module returned an invalid buffer containing the link status information. Note that the node can still function, but link status information cannot be retrieved. ACTION: Call your Hewlett-Packard support contact. -205 MESSAGE: STATUS REPLY INVALID CAUSE: The module configurator status routine received an invalid status reply.
Messages X.25 Link Module Configurator Error Codes ACTION: Call your Hewlett-Packard support contact. -506 MESSAGE: UNABLE TO SEND TRACE DISABLE REQUEST CAUSE: The module configurator encountered an error while trying to send the trace disable request message. ACTION: Call your Hewlett-Packard support contact. -507 MESSAGE: UNABLE TO GET MESSAGE FRAME FOR TRACE DISABLE REQUEST CAUSE: The module configurator encountered an error while trying to allocate the trace disable request message.
Messages X.25 Link QLLC Internal Error Codes X.25 Link QLLC Internal Error Codes Listed below are the codes that are generated by the X.25 link Qualified Logical Link Control (QLLC) module when a QLLC internal error occurs.
Messages X.25 Link QLLC Internal Error Codes -6 through -16 MESSAGE: (reserved for internal use only) CAUSE: An internal error has occurred. ACTION: Call your Hewlett-Packard support contact. -17 MESSAGE: CALL REJECTED DUE TO SECURITY VIOLATION CAUSE: An incoming SVC call was rejected by SNA/X.25 because the caller was unauthorized. That is, the caller's address was not included in the call packet, or it was not the remote address the SNA node is configured for. ACTION: Verify that the Remote’s X.
Messages X.25 Link QLLC Internal Error Codes -27 through -49 MESSAGE: (reserved for internal use only) CAUSE: An internal error has occurred. ACTION: Call your Hewlett-Packard support contact. -50 through -100 MESSAGE: INTERNAL ERROR CAUSE: An internal error has occurred. ACTION: Call your Hewlett-Packard support contact.
Messages NetView Alerts Error Messages NetView Alerts Error Messages Listed below are the error messages that can occur when an operator-generated NetView alert is sent. They are listed in alphabetical order according to the first word of the message. These messages are not logged; they are written to $STDLIST. MESSAGE: Can’t open CATSNA.PUB.SYS. CAUSE: The SNA message catalog (CATSNA.PUB.SYS) is missing, or is not in the correct format.
Messages Network Dump Manager Error Messages Network Dump Manager Error Messages Listed below are the messages that are generated by the Network Dump Manager when errors occur while the SDLC link is being dumped. If you must submit an SR or call your Hewlett-Packard support contact, please copy the error exactly as it appears on the operator’s console; it will make determining the cause of the problem easier. The messages are listed below in numerical order according to message number.
Messages Network Dump Manager Error Messages purging. Then, take a system memory dump and call your Hewlett-Packard support contact, who will need to analyze the “Llio Status” error that was logged. DUMP ERROR 4 MESSAGE: **** DUMP ERROR 4: CANNOT CREATE DUMP FILE CAUSE: The Network Dump Manager completed all hardware-dump setup, but was not able to open a new disk file to hold the dump.
Messages Network Dump Manager Error Messages message was generated, it might indicate that the dump took too long to produce. (This caused the driver to be shut down, deleting its memory.) A heavy system load can cause the dump to take too long. If no other messages were generated, issue the SWITCHNMLOG command (see Chapter 6 , “MPE Commands,” of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging.
Messages Network Dump Manager Error Messages ACTION: The partial dump file that was produced probably contains good link driver data but incomplete hardware data. So, your Hewlett-Packard support contact might be able to analyze the file. However, your hardware is probably faulty. If the system crashes, take a system memory dump. Otherwise, issue the SWITCHNMLOG command (see Chapter 6 , “MPE Commands,” of this manual) and note the name of the current NM log file.
Messages Network Dump Manager Error Messages hardware might be too faulty to produce a good dump, or a power failure might have occurred. (A power failure can produce a false fatal error, but it still aborts the dump.) Note that a partial dump file was produced. ACTION: The partial dump file that was produced probably contains good link driver data but incomplete hardware data. So, your Hewlett-Packard support contact might be able to analyze the file unless a power failure occurred.
Messages Network Dump Manager Error Messages DUMP ERROR 15 MESSAGE: **** DUMP ERROR 15: FATAL CARD ERROR PREVENTS DUMP CAUSE: After dumping SDLC link driver data, the Network Dump Manager checked the SDLC link hardware and found a “fatal error.” The link hardware cannot be dumped and might be faulty, or a power failure might have occurred. (A power failure can produce a false fatal error, but it still aborts the dump.) Note that a partial dump file was produced.
Messages Network Dump Manager Error Messages no other messages were generated, issue the SWITCHNMLOG command (see Chapter 6 , “MPE Commands,” of this manual) and note the name of the current NM log file. Save the current file and the previous file, to prevent accidental purging. Then, call your Hewlett-Packard support contact, who will need to analyze the “Llio Status” error that was logged.
Messages LAN Error Messages LAN Error Messages Listed below are the messages that are generated by the token ring driver or token ring card. Depending on the logging configuration for the Token Ring Link subsystem, these messages are logged to the console, to disk, or both. These messages have the following format: Internal driver error in SYSLINK (LANWARN ####) or (LANERR ####) where #### is an error number. The messages are listed in numerical order according to the error number. 2 MESSAGE: Bad LINK ID.
Messages LAN Error Messages 7 MESSAGE: A call to IO_CONFIG_INT failed during driver initialization. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 8 MESSAGE: A call to IO_DECONFIG_INT failed during driver shutdown. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.
Messages LAN Error Messages 14 MESSAGE: Unable to send I/O Services message frame to another process. CAUSE: A call to a system message SEND routine returned an error. The destination port may belong to a process that no longer exists or is not operating with required capabilities. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 16 MESSAGE: LAN console is not supported.
Messages LAN Error Messages 32 MESSAGE: Attempt to rendezvous with a link driver with SAP or SAP+XSAP or Ethernet Type already being used. CAUSE: The user is trying to rendezvous twice with a link driver or two different users are using the same SAP, SAP+XSAP or Ethernet Type. ACTION: Write down the error information displayed on the console submit an SR and call your Hewlett-Packard support contact. 33 MESSAGE: Attempt to separate from the driver failed.
Messages LAN Error Messages ACTION: Write down the error information displayed on the console submit an SR and call your Hewlett-Packard support contact. 40 MESSAGE: The Middle Plane is in wrong state. CAUSE: The Middle Plane state machine table is corrupted. ACTION: Write down the error information displayed on the console submit an SR, take a dump and call your Hewlett-Packard support contact. 41 MESSAGE: Missing inbound pool in the rendezvous request message.
Messages LAN Error Messages 50 MESSAGE: The NIO LAN/console card did not return to a ready state after a reset was issued. CAUSE: The problem is caused by bad NIO LAN/console hardware. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. 52 MESSAGE: The NIO LAN/console card register test failed during LAN/console card initialization. CAUSE: The problem is caused by bad NIO LAN/console hardware.
Messages LAN Error Messages 59 MESSAGE: The NIO LAN/console card detects a bad length of the configuration data buffer. CAUSE: The problem is caused by data corruption in the configuration quad. ACTION: Write down the error information displayed on the console, submit an SR, take a dump and call your Hewlett-Packard support contact. CAUSE: The problem is caused by a bad NIO LAN/console backplane. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.
Messages LAN Error Messages 63 MESSAGE: The NIO LAN/console card detects a bind request to already bound register. CAUSE: The problem is caused by a link driver internal error. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. CAUSE: The problem is caused by a bad NIO LAN/console backplane. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.
Messages LAN Error Messages ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 69 MESSAGE: The NIO LAN/console card reports that CCMD_IN was sent to an outbound only register set. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 70 MESSAGE: The NIO LAN/console card detects unknown CCMD. CAUSE: Unknown. Need more information.
Messages LAN Error Messages ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. 77 MESSAGE: The NIO LAN/console card detects a severe internal error. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 78 MESSAGE: The NIO LAN/console card detects a fatal error in the bus protocol. CAUSE: Unknown. Need more information.
Messages LAN Error Messages 84 MESSAGE: The BDMARS expected more DMA data to be transferred than the host CCMD_IN or CCMD_OUT count requested. CAUSE: The NIO LAN/console card was prepared to send more data bytes to the host, but the host did not provide enough buffers. Or the LAN/ console card expected more data than the host provided. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.
Messages LAN Error Messages 125 MESSAGE: The driver detects unknown option in the 802.2 control field of a test or xid packet. CAUSE: The problem is caused by a bad packet. ACTION: If this error appears repeatedly, write down the error information displayed on the console and call your Hewlett-Packard support contact. 144 MESSAGE: Dump request received when driver is dumping. CAUSE: Unknown. Need more information.
Messages LAN Error Messages 150 MESSAGE: Unable to send dump request message to dump manager. CAUSE: A call to a system message SEND routine returned in error. The dump manager port is not operating with required capabilities. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact. 151 MESSAGE: Unexpected timer event message. CAUSE: Unknown. Need more information.
Messages LAN Error Messages 178 MESSAGE: Type 2 connection disconnected. CAUSE: The remote system transmitted a DISC, causing the Type 2 connection to be dropped. ACTION: Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact. 179 MESSAGE: Type 2 error during reset or disconnect.
Messages LAN Error Messages 184 MESSAGE: Type 2 connection already exists. CAUSE: Two transports are configured to use the same MAC addresses and SAPs. ACTION: Correct the NMMGR configurations and restart the driver. 185 MESSAGE: Type 2 connection not available. CAUSE: The driver has reached the maximum number of supported connections. ACTION: Shut down some connections to free up resources. 186 MESSAGE: Type 2 Connection ID invalid.
Messages LAN Error Messages 199 MESSAGE: Type 2 non-fatal software error. CAUSE: A non-fatal Type 2 driver software error occurred. ACTION: Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact. 200 MESSAGE: Unable to send I/O Services message frame LINKNAME CAUSE: A call to a system message send routine returned in error.
Messages LAN Error Messages 208 MESSAGE: Type 2 non-fatal protocol error. CAUSE: An unexpected packet format was received. ACTION: Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact. 209–210 MESSAGE: Type 2 non-fatal software error. CAUSE: A non-fatal Type 2 driver software error occurred.
Messages LAN Error Messages 228 MESSAGE: Could not open NMCONFIG.PUB.SYS file. CAUSE: The configuration file NMCONFIG.PUB.SYS was purged or renamed or the NMCONFIG.PUB.SYS configuration file may be opened with exclusive access. ACTION: Type a LISTF NMCONFIG.PUB.SYS to determine if the file has been opened with exclusive access. If it has, wait for the program or process that has this file opened exclusively to close it.
Messages LAN Error Messages 235 MESSAGE: A call to IO_UNCONFIG failed during driver deconfiguration. CAUSE: Wrong physical path was specified in IO_UNCONFIG call due to configuration data corruption in the driver PDA. ACTION: Write down the error information displayed on the console, submit an SR, take a system dump, and call your Hewlett-Packard support contact. 236 MESSAGE: The LAN card is used by another link. CAUSE: The card was configured by another link.
Messages LAN Error Messages 242 MESSAGE: Could not get Write Initiator label. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 243 MESSAGE: Could not release Write Initiator label. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 244 MESSAGE: Could not open NMLGxxxx.PUB.SYS file.
Messages LAN Error Messages ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 250 MESSAGE: Timeout waiting for the config reply message. CAUSE: The link software or the card could not be configured. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. 251 MESSAGE: Driver’s PDA is corrupted. CAUSE: Unknown. Need more information.
Messages LAN Error Messages ACTION: If this error persists, check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network. 2103 MESSAGE: Token Ring adapter detected a soft error on LINKNAME CAUSE: This station has detected an error and notified the Ring Error Monitor. ACTION: If this error persists, query your Ring Error Monitor to determine the type of error. Check network components (adapters, cables, MSAUs, etc.).
Messages LAN Error Messages ACTION: Verify that any other stations are properly attached to the network. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network. 2109 MESSAGE: Token Ring adapter detected Claim Token Frame on LINKNAME CAUSE: The network is attempting to recover from a failure. ACTION: If this warning persists, check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.
Messages LAN Error Messages 276 Appendix A
Netview Alerts B Netview Alerts This appendix describes NetView alerts, and how they are sent from your HP 3000 to the IBM remote system.
Netview Alerts Overview Overview A NetView alert is information that is sent to the IBM remote system to tell the IBM operator that an error or problem has occurred on the HP 3000. (Note that NetView must be running on the IBM remote system.) So, be aware that the IBM operator might contact you to check on the status of the HP 3000 system if an alert is received at the remote system console.
Netview Alerts How Alerts Are Sent How Alerts Are Sent When an alert is generated (by either SNA Transport or an HP 3000 operator), it is stored in an MPE message file named nodename.PUB.SYS (where nodename is the name of the configured SNA node the alert is to be sent to). SNA Transport continually checks the message files for alerts. When it finds an alert in a message file, it sends the alert to the remote system and waits for an acknowledgment that the remote system received it.
Netview Alerts Creating the Message File Creating the Message File To enable SNA Transport to send alerts (generated by itself or an operator) to NetView, you must create the message file the alerts will be stored in. To create the file, type this command at the MPE system prompt: BUILD NodeName.PUB.SYS;MSG NodeName is the name of the configured SNA node the alerts are to be sent to. You must create a message file for each SNA node you will want alerts to be sent to.
Netview Alerts SNA Transport-Generated Alerts SNA Transport-Generated Alerts A set of alerts that SNA Transport generates have been predefined for these conditions: • Configuration or customization error — Bad phone number • Link error — Dial not completed, unknown automatic-dial error, or data line busy — No ACU power, or cable is missing — Datacomm line was lost — Internal error occurred Note that a logging message for each of these conditions is also generated.
Netview Alerts Operator-Generated Alerts Operator-Generated Alerts Anyone can generate an alert to be sent to the IBM remote system operator (no special user capabilities are needed). This function can be used for sending error-related information that might not be automatically reported by error detection programs and utilities. To be able to generate alerts, ensure that a message file exists for each SNA node you want to send alerts to (see “Creating the Message File” earlier in this appendix).
Netview Alerts Operator-Generated Alerts See Appendix A , “Messages,” for the error messages that can occur when you send an operator-generated NetView alert.
Netview Alerts Operator-Generated Alerts 284 Appendix B
Index A ACTLU request, 98, 102 ACTPU request, 98, 100 AS/400, 21, 23, 24, 26 AS/400 computer, 21, 23, 24, 26 AS/400 hardware, 21, 23, 26 AS/400 software, 21, 23, 26 B BIND request, 99 C classes, 110 commands, 100, 103 communications controller, 20, 23, 26 communications controller, host, 20, 23, 26 components, 19, 22, 25 components of, 19, 22, 25 configuration, 98 console logging, 98 controlling, 98, 102 D deactivating, 103 domain, controlling, 98 driver, link, 25 E establishing, 98, 99, 100, 102 F file na
Index protocol enforced by QLLC module, 22 PSI, 21 PU, 103 PU-SSCP session, 98, 100, 103 PU-SSCP, establishing, 98, 100 PU-SSCP, terminating, 103 token ring link driver, 25 token ring link module, 25 tracing, 17 Q QLLC module, 22 W with the host SSCP, establishing, 102 with the remote system PU, establishing, 100 with the remote system, establishing, 98, 99 R requirements, 20, 21, 23, 24, 26, 27 S SDLC link, 103 session, 97, 98, 99, 100, 102, 103 shutdown, 103 shutdown, overview of, 97 SNA Transport, 1
