SNA IMF/XL Node Manager’s Guide HP 3000 MPE/iX Computer Systems Edition 3 Manufacturing Part Number: 30293-90010 E0692 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. SNA IMF Overview Network Configuration Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2. SNA IMF Installation Guidelines 3. SNA IMF Configuration Data Required From the Host Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMMGR Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of NMMGR Screens . . . . . . . . . . . .
Contents Glossary Index 4
Figures Figure 1-1 . HP 3000-to-IBM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Figure 3-1 . Main Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Figure 3-2 . HP-IBM Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 3-3 . SNA IMF Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 3-4 .
Figures 6
Tables Table 3-1 ACF/NCP and ACF/VTAM Corresponding Values . . . . . . . . . . . . . . . . . . . . . . . . . 16 Table 3-2 AS/400 Corresponding Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 8
Preface This manual describes Hewlett-Packard Company’s Systems Network Architecture Interactive Mainframe Facility (SNA IMF) for the MPE/XL operating system. Systems Network Architecture (SNA) is a comprehensive specification for distributed data processing networks, developed by IBM. SNA IMF allows interactive communications between an HP 3000 computer and an IBM host, by emulating the major features of an IBM 3270 control unit, using the protocols of a Node Type 2.
Organization This manual is divided into the following chapters and appendix: Chapter 1 , “SNA IMF Overview,” contains an overview of SNA IMF and the components of the network. Chapter 2 , “SNA IMF Installation Guidelines,” discusses installation procedures. Chapter 3 , “SNA IMF Configuration,” explains how to use the NM configuration manager (NMMGR) to create a hierarchical configuration file for SNA IMF.
1 SNA IMF Overview Systems Network Architecture Interactive Mainframe Facility (SNA IMF) emulates the major features of an IBM 3270 control unit, using the protocols of a Node Type 2.0 and Logical Unit Types 1, 2, and 3 (LU.T1, LU.T2, and LU.T3). SNA IMF supports interactive communication between an HP 3000 and an IBM host. The host can be an IBM System/370-compatible mainframe (for example, Model 370, 303x, or 43xx), an IBM System/36 or System/38, or an IBM AS/400.
SNA IMF Overview Network Configuration Order Note that SNA/SDLC Link is the only SNA link product shown in the figure. For a description of all SNA link products, see the SNA Link/XL Node Manager’s Guide. Network Configuration Order We recommend that the HP 3000 system and the software components of the IBM host be configured in this order: 1. The IBM host (VTAM, AS/400, etc.) 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.
2 SNA IMF Installation Guidelines To run SNA IMF on your HP 3000, you must install the product and configure both your HP 3000 environment and the host system to support SNA IMF. As part of the configuration process, you must ensure that the HP 3000 parameters match those on the host side. The necessary parameters are described in Chapter 3 , “SNA IMF Configuration,” in this manual. Before you install SNA IMF on the HP 3000, you must do the following things: 1.
SNA IMF Installation Guidelines 14 Chapter 2
3 SNA IMF Configuration This chapter describes how to use the NM configuration manager (NMMGR) to create or modify a hierarchical configuration file for SNA IMF. NOTE Before you can configure SNA IMF, you must have successfully configured the SNA link (including logging). Configuration of the SNA links is described in the SNA Link/XL Node Manager’s Guide. You also must coordinate the SNA IMF configuration with the IBM host configurations.
SNA IMF Configuration Data Required From the Host Configuration Data Required From the Host Configuration Data in an SNA IMF configuration file must correspond to information from the host configuration. Before using NMMGR, you should have certain information from the host configuration. You must coordinate the SNA IMF configuration with the ACF/NCP and ACF/VTAM host configurations.
SNA IMF Configuration Data Required From the Host Configuration NOTE When you configure a device on the AS/400, System/36, or System/38 to communicate with SNA IMF, the device type must be 3277. In addition to NMMGR configuration, SNA IMF also requires that you configure Pass Thru options in a file called PTCONFIG. In order to use Pass Thru to communicate with an IBM AS/400, you must specify UNBIND: NO in the PTCONFIG file. For more information, see Using SNA IMF Pass Thru.
SNA IMF Configuration NMMGR Configuration Overview NMMGR Configuration Overview The SNA IMF configuration is done by using NMMGR to create or modify a configuration file. The basic operation of NMMGR is described in Using the Node Management Services Utilities; if you are not familiar with NMMGR, you should read that manual before continuing. NOTE When configuring SNA IMF, the configuration file can be named anything you prefer.
SNA IMF Configuration NMMGR Configuration Overview example, correct LU names). See Appendix A , “Validation Messages,” of this manual for SNA IMF validation error messages. You should validate the configuration file after completing any of these tasks: • An initial configuration of one or more SNA nodes • An initial configuration of one or more SNA services • A modification of an existing configuration The configuration file is validated through NMMGR; see Using the Node Management Services Utilities.
SNA IMF Configuration NMMGR Configuration Overview LUNAME36, LUNAME43, LUNAME50, LUNAME57, LUNAME64 User List: LUNAME37, LUNAME44, LUNAME51, LUNAME58, USER1, USER4, LUNAME38, LUNAME45, LUNAME52, LUNAME59, LUNAME39, LUNAME46, LUNAME53, LUNAME60, USER2, USER5, Program List: PROGRAM1, PROGRAM3, PROGRAM5 LUNAME40, LUNAME47, LUNAME54, LUNAME61, LUNAME41, LUNAME48, LUNAME55, LUNAME62, USER3, USER6 PROGRAM2, PROGRAM4, - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SNANODE Nam
SNA IMF Configuration NMMGR Configuration Overview SNANODE Name: IBMNODE5 Security Class: CLASS5 LU List: (None configured) User List: (None configured) Program List: (None configured) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Some fields could not be found or printed.
SNA IMF Configuration Configuring SNA IMF Configuring SNA IMF Once you have opened the configuration file, you are placed at the NMMGR Main screen. Main Screen The Main Screen is shown in Figure 3-1, 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 SNA IMF, press [f4] (IBM). This places you at the HP-IBM Configuration screen.
SNA IMF Configuration Configuring SNA IMF HP-IBM Configuration Screen The HP-IBM Configuration Screen is shown in Figure 3-2, from this screen you can select the item you want to configure. Figure 3-2 HP-IBM Configuration Screen To select SNA IMF configuration, press [f5] (Go To IMF). SNA IMF Configuration Screen After you have selected SNA IMF configuration, NMMGR displays the SNA IMF Configuration Screen, shown in Figure 3-3.
SNA IMF Configuration Configuring SNA IMF Figure 3-3 SNA IMF Configuration Screen Fields Path For display only. The NMMGR branch you are in. SNA Node Name The name of the SNA node you want to configure for SNA IMF, or the configured node whose security class configuration you are modifying. The name can be up to eight alphanumeric characters long; the first character must be alphabetic.
SNA IMF Configuration Configuring SNA IMF Once you have entered the new name, press [f4] (Rename); the node is then renamed. Configured SNA Nodes for SNA IMF For display only. The names of the SNA nodes for which SNA IMF has been configured. You can configure a maximum 256 nodes for SNA IMF in a configuration file (use [f1] [Next Page] to display more fields). The nodes listed must also have been configured in the SNA node configuration; this is checked when the validation is done.
SNA IMF Configuration Configuring SNA IMF Figure 3-4 Security Classes Screen Fields Path For display only. The NMMGR path for this screen. It includes the name of the node you are configuring the security class for. Class Name The name of the new security class you are configuring, or the existing class whose configuration you are modifying. The name can be up to eight alphanumeric characters long; the first character must be alphabetic. New Name The new name of an existing security class.
SNA IMF Configuration Configuring SNA IMF Security Class Data Screen After you have selected a security class, NMMGR displays the SNA IMF Configuration: Security Class Data screen as shown in Figure 3-5. You can go directly to this screen from any screen by typing @IMF.nodename.classname in the command window and pressing [ENTER]. Here you specify the LUs that belong to the security class you selected earlier. Note that each LU is identified by its configured LU Name instead of its NAU number.
SNA IMF Configuration Configuring SNA IMF Host Configuration: For troubleshooting purposes, we strongly recommend that the LU names entered here match the luname operands of the LU macro that defines these LUs in VTAM on the host; see Table 3-1. If you use SNA IMF to communicate with an IBM AS/400, we strongly recommend that the LU names entered here match the names of the Device Descriptions on the AS/400; see Table 3-2. File For display only. The name of the configuration file.
SNA IMF Configuration Configuring SNA IMF Figure 3-6 User List Data Screen Fields Path For display only. The NMMGR path for this screen. It includes the names of the SNA node and the security class you are configuring. Users A list of up to 42 users to be authorized to use the LUs in this security class. Each name must be a valid MPE user name (UserName.AcctName), and cannot be more than 18 characters long; MPE wildcard characters can be used.
SNA IMF Configuration Configuring SNA IMF Program List Data Screen Once you have configured the LUs for the security class, you can configure the programs you want to be authorized to use the LUs. You configure authorized programs on the SNA IMF Configuration: Program List Data screen as shown in Figure 3-7. Note that if security is not going to be used, you do not need to access this screen: All programs will be authorized for this class (the @.@.
SNA IMF Configuration Configuring SNA IMF Default: @.@.@ (all programs) File For display only. The name of the configuration file. Once you have entered all of the program names, press [f6] (Save Data). After the information is processed, press [f8] (Prior Screen) until you redisplay the SNA IMF Configuration: Security Class Data screen. Then, if you need to configure authorized users for the security class, press [f1] (Go To USERLIST).
SNA IMF Configuration Migrating a Configuration from MPE V to MPE XL Migrating a Configuration from MPE V to MPE XL If you are migrating from SNA IMF/V to SNA IMF/XL, run the NMS utility NMMGRVER.PUB.SYS, described in Using the Node Management Services Utilities. NMMGRVER will convert your old configuration to a configuration that is compatible with your new software.
4 SNA IMF Session Startup and Shutdown This chapter describes how SNA IMF sessions are started up (establishing an LU-LU session) and how sessions are shutdown (terminating an LU-LU session). To start an SNA IMF session, you must establish an LU-LU session between an HP 3000 LU (the secondary LU) and a host LU (the primary LU). An SNA IMF LU-LU session can be initiated by an LU in the HP 3000 node or by a host LU. Both kinds of session initiation are described here.
SNA IMF Session Startup and Shutdown Starting a Session From the HP 3000 LU Starting a Session From the HP 3000 LU An SNA IMF LU-LU session initiated by an LU in the HP 3000 node is started by sending a character-coded logon message to the IBM host. The issued logon causes an INITiate-SELF (INIT-SELF) request to be sent to the SSCP. In processing the INIT-SELF request, the SSCP determines whether the host LU is accepting session-initiation requests.
SNA IMF Session Startup and Shutdown Starting a Session From the HP 3000 LU Figure 4-1 LU-LU Session Initiated by HP 3000 LU Chapter 4 35
SNA IMF Session Startup and Shutdown Starting a Session From the Host LU Starting a Session From the Host LU An SNA IMF LU-LU session can also be initiated by an LU on the IBM host. When the host LU initiates a session with SNA IMF, it begins by sending a session-initiation request to its SSCP. The SSCP returns a CINIT request, which contains the session parameters the host LU can support. The host LU sends these parameters in its BIND request to the LU on the HP 3000.
SNA IMF Session Startup and Shutdown Stopping a Session Stopping a Session AN LU-LU session exists to allow two users to communicate in an SNA network. Once that communication is completed, the LU-LU session should be terminated to allow the LUs to participate in other LU-LU sessions. An SNA IMF session is stopped by sending a logoff message to the IBM host. The logoff message is forwarded to the host by SNA Transport. The host LU sends an UNBIND request to the HP 3000 LU.
SNA IMF Session Startup and Shutdown Stopping a Session 38 Chapter 4
5 SNA IMF Troubleshooting You can troubleshoot SNA IMF by using the tracing and logging facilities for the SNA link: SNA IMF tracing and logging is done as part of SNA Transport tracing and logging (see the SNA Link/XL Node Manager’s Guide).
SNA IMF Troubleshooting Using NMMAINT for SNA IMF Using NMMAINT for SNA IMF The NMMAINT utility displays the version numbers of the HP data communications software installed on your system. The example below shows the SNA IMF information displayed when you run NMMAINT. Note that the version numbers shown below are not necessarily the current version numbers for SNA IMF; they are shown only as an example. NMMAINT is described in more detail in Using the Node Management Services Utilities.
SNA IMF Troubleshooting Problem Resolution Problem Resolution Problems that can occur while installing, configuring, and running SNA IMF, and how to deal with them, are described here. Guidelines for submitting a service request (SR) are also described. 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 IMF Troubleshooting Problem Resolution Corrupt Configuration File The configuration file is possibly 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 IMF 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. • Incorrect Logmode table definition. Ensure that the correct Logmode Table definitions are being used. The HP SNA Products: ACF/NCP and ACF/VTAM Guide contains more information about this.
SNA IMF Troubleshooting Problem Resolution • Pass Thru problems. Ensure that the HP terminal supports Pass Thru and that its MPE I/O configuration is correct. Using SNA IMF Pass Thru lists the terminals and printers you can use with Pass Thru. SNA IMF Run-Time Problems After both the hardware and software are installed, problems might occur. Many run-time problems are caused by inaccurate configuration.
SNA IMF Troubleshooting Problem Resolution set to ACTIVE or is not placed high enough in the node definition (see “Host Configuration Problems” earlier in this chapter). • Unable to log on. To log on, the display screen must be owned by the SSCP-LU session. Remember, display screen ownership is shared between the LU-LU session and the SSCP-LU session. When you first start Pass Thru, the screen is unowned. Press the System Request Key (SRK) to transfer display ownership to the SSCP-LU session.
SNA IMF Troubleshooting Problem Resolution data communications products installed, and any other products you were using when the problem arose. • Obtain the version, update, and fix information for all software by running NMMAINT (for SNA IMF, you also can call the VERS3270 intrinsic). This allows Hewlett-Packard to determine whether the problem is already known and if the correct software is installed at your site.
SNA IMF Troubleshooting Problem Resolution • Save copies of all active or in-use log files for analysis by your HP representative. • Record all intrinsic result codes and Pass Thru messages that appear at an emulated terminal or printer and the HP 3000 console. • Always obtain a copy of the host system generation you are using.
SNA IMF Troubleshooting Problem Resolution 48 Chapter 5
A Validation Messages This appendix contains messages that might occur when you validate the SNA IMF configuration data. Configuration file validation is discussed in Chapter 3 , “SNA IMF Configuration,” of this manual. IMFVAL ERR 3 MESSAGE: Corrupt configuration file. Missing IMF path. (IMFVALERR 3) CAUSE: The SNA IMF path is missing from the configuration file. ACTION: Restore the configuration file from a backup tape and retry the validation. Also, submit an SR.
Validation Messages ACTION: Configure the correct LUs for the security class on the SNA IMF Configuration: Security Class Data screen. IMFVAL ERR 9 MESSAGE: Path: NMMGRpath — LU LUName is not a valid LU for SNAnode NodeName. (IMFVALERR 9) CAUSE: The indicated LU is not configured under the indicated SNA node. ACTION: Ensure that the LU should be configured under the SNA node. If it should be configured, configure it on the SNANode Configuration: LU Data screen.
Validation Messages IMFVAL ERR 14 MESSAGE: Path: NMMGRpath — Unknown error occurred while getting this path. (IMFVALERR 14) CAUSE: An unexpected error occurred while attempting to obtain a path from the configuration file. This usually indicates a problem with the validation procedure. ACTION: Restore the configuration file from a backup tape and retry the validation. Also, submit an SR. IMFVAL ERR 15 MESSAGE: Path: NMMGRpath — Unknown error occurred while reading the path data.
Validation Messages 52 Appendix A
Glossary A B ACF: See Advanced Communication Function. bind: An SNA request sent by the host to activate a session between two logical units. The request specifies the detailed protocol to be accepted before initiating an LU-LU session. ACF/NCP: See Advanced Communication Function for the Network Control Program. ACF/VTAM: See Advanced Communication Function for the Virtual Telecommunications Access Method. active state: A state in which part of an SNA node is able to function as it was designed.
programmable and nonprogrammable communication controllers. Hewlett-Packard's INP and PSI are types of communications controllers. communications link: The hardware that directly connects two locations for the purpose of data transfer, including the interface boards, cables, and modems (if a telephone line is used). Control Unit (CU): A device that controls input and output for one or more devices such as printers or display stations. F FMD: See Function Management Data services.
opening files, opening communications lines, or transmitting data over a communications line. L ldev: See logical device. ldn: Logical device number. See logical device. link: The physical or logical connection between two devices in a network. logging: The recording of significant events that may be of use to the user at the time they occur. This is distinguished from tracing, which is the recording of events for future use.
LU.T1: See Logical Unit Type 1. LU.T2: See Logical Unit Type 2. LU.T3: See Logical Unit Type 3. M modem: An acronym for MODulator-DEModulator. A modem converts serial digital data from a transmitting terminal into a form suitable for transmission over the analog telephone channel. A second modem reconverts this signal to serial digital data for acceptance by the receiving terminal. Bell 201, 208, and 209 modems are used for synchronous data transfer. MPE: See MultiProgramming Executive.
• SSCP-LU • LU-LU Network Control Program (NCP): A program that controls the operation of a communications controller. Network File Transfer (NFT): A user-level protocol that enables the transfer or copying of files from one node to another or within a single node, interactively or programmatically. Network Services Procedure Error (NSPE): An SNA request from the SSCP to the LU indicating an error during session startup or shutdown. NFT: See Network File Transfer. NMS: See Node Management Services.
Request Unit (RU): A message unit containing control information such as a request code, or function management headers, end-user data, or both. Response Header (RH): Control information that indicates whether a response is positive or negative. A response unit optionally follows it. Response Unit (RU): A message unit that acknowledges a request unit. If the response unit is negative, it will contain sense data that defines the exception condition.
timeout: Time limit imposed for a given task to be completed. tracing: The recording of events for future use. See also logging. Transmission Header (TH): A transmission header is used by the Transmission Control and Path Control layers of SNA for routing and sequencing data sent through an SNA network. V Virtual Telecommunications Access Method (VTAM): An IBM communications access method within the host that handles the data communications and network control details for the host.
Index A ACF/NCP, 16 ACF/VTAM, 16 activating an LU, 44 activating an PU, 44 ACTIVE, 43 ACTIVE setting, 43 AS/400, 11 authorized programs of a security class, 18 authorized users of security class, 18 AUTOINST, 13 AUTOINST documentation, 13 B BIND request, 36 C CINIT request, 34, 36 Class Name field, 26 commands DISPLAY, 44 SNACONTROL START, 44 SNACONTROL STATUS, 47 SWITCHNMLOG, 46 VARY, 44 common information, 45 common problems, 41 corrupt configuration file, 42 file system errors, 42 insufficient MPE resou
Index Main screen, 22 memory dump, 46 migrating a configuration, 32 modem link, 13 N New Name field, 26 NMDUMP, 46 NMMAINT, 40 using for SNA IMF, 40 NMMGR configuration, 18 NMMGR configuration file create, 18 modify, 18 NMMGR screens Main, 22 NMMGRVER, 32 O overview of SNA IMF, 11 P parameter library VTAM, 43 Pass Thru problems, 44 Path field, 26, 27, 29, 30 Physical Path field, 42 problems, 41 common, 41 host configuration, 42 installation, 43 run-time, 44 Program List Data Screen, 30 Programmable Serial
