Configuring Systems for Terminals, Printers, and Other Serial Devices HP 3000 MPE/iX Computer Systems Edition 11 32022-90051 E1098 Printed in: U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction Devices that Communicate Asynchronously . . . . . . . . . . . . . . . . . . . . How Devices Communicate Once They Are Connected. . . . . . . . . . . . Typical Network Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Host-Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PC-Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAD Access . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Step 1: Begin the Configuration Process . . . . . . . . . . . . . . . . . . . . . . Step 2: Open the Network Management Configuration File . . . . . . Step 3: Configure the Local Node Name . . . . . . . . . . . . . . . . . . . . . . Step 4: Configure the Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5: Select DTC Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 6: Specify DTC Configuration . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Terminal Profile Screen (Host-Based) . . . . . . . . . . . . . . . . . . . . . . . . Terminal Switching Configuration Screen . . . . . . . . . . . . . . . . . . . . . Terminal Profile Screen (PC-Based) . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Profile Screen (Host-Based) . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Switching Configuration Screen . . . . . . . . . . . . . . . . . . . . . . Printer Profile Screen (PC-Based) . . . . . . . . . . . . . . . . . . . . . .
Contents The XON/XOFF Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Read Trigger Character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Control Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modem Echo . . . . . . . . . . .
Contents Glossary Index 7
Contents 8
Figures Figure 1-1 . LAN with Host-Based Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Figure 1-2 . DTC/X.25 Network Access for a PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Figure 1-3 . DTC/X.25 iX Network Access Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Figure 1-4 . Telnet/iX Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 10
Tables Table 4-1. Dynamically Configurable Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Table 7-1. Host-Based Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 Table 7-2. PC-Based Terminal Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 Table 7-3. Host-Based Printer Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This manual documents functionality for the MPE/iX 6.0 release, as well as later releases, for HP 3000 Series 900 systems. This manual describes how terminals, printers, and other serial devices are connected to the HP 3000 Series 900 computer.
Guide to This Manual This manual is divided into the following chapters and appendices: • Chapter 1, “Introduction,” introduces Asynchronous Serial Communications (ASC) and the organization of the hardware and software used by the Datacommunications and Terminal Subsystem (DTS). • Chapter 2, “Before Configuring Terminal and Printer Connections,” explains how to prepare to configure communications between the HP 3000 computer and serial devices, such as terminals and printers.
• Appendix B, “Migrating From Previous Releases,” describes the steps to migrate network configuration files from previous MPE/iX and MPE V releases to the current release format. • Appendix C, “DTC User Interface,” describes how to use the interface and what commands are available. • Appendix D, “Error Messages,” lists error messages and causes and actions for each message. • Glossary, provides definition of commonly used terms and concepts.
• OpenView DTC Technical Reference Manual. This manual covers the technical detail of the DTC, including protocol implementations and limitations, explanation of how connections are established, and information on event logging. It is intended for experienced DTC users and programmers. Configuration At a Glance Before configuring your HP 3000 to use the DTC terminal servers, you must have completed the following tasks. These tasks are not covered in this manual: 1.
Chapter 5, “Configuring Serial Devices (for Host-Based Management),” and Chapter 6, “Configuring Serial Devices (for PC-Based Management).”. 1. Run NMMGR.PUB.SYS. 2. Modify your existing DTS configuration as necessary. 3. Validate your network configuration. (SYSGEN cross-validation is done automatically within NMMGR.) 4. At the prompt seen after cross-validation is complete, select to have DTS changes take effect dynamically. 5. Exit NMMGR. 6.
Introduction 1 Introduction This chapter provides an overview of communications between a HP 3000 Series 900 computer and its asynchronous devices, including the following: • The types of devices that communicate in an asynchronous serial fashion. • How devices communicate once they are connected to the Datacommunications and Terminal Controller (DTC). • Typical configurations for both host-based network management and PC-based network management.
Introduction Devices that Communicate Asynchronously Devices that Communicate Asynchronously Asynchronous Serial Communications (ASC) is the term used to describe the specific manner in which communications occur between a HP 3000 Series 900 computer and some of its associated devices. Asynchronous refers to the protocol used to inform the receiving end of a communications link that data is being sent and when the data transmission has completed.
Introduction How Devices Communicate Once They Are Connected How Devices Communicate Once They Are Connected With the exception of the system console (and, for certain HP 3000 Series 900 models), the remote support modem and the first UPS on the system), which has its own access port, asynchronous devices are connected to a HP 3000 Series 900 computer through the Datacommunications and Terminal Subsystem (DTS).
Introduction Typical Network Configurations Typical Network Configurations NOTE If you are configuring X.25 networking capabilities on a HP 3000 Series 900 computer using host-based network management, use Configuring and Managing Host-Based X.25 Links instead of this manual to configure DTCs and DTC connections. Use this manual for directions on how to perform Dynamic/Automatic Configuration or to execute a DTS shutdown or restart.
Introduction Typical Network Configurations Host-Based Management When an HP 3000 computer is used to configure and manage DTCs, the system is using Host-Based Management. Configuration and control information is maintained on the host, and downloaded from the host to each of the DTCs controlled by it. In the simplest configuration, devices connected through a DTC function as though a single cable were connecting the device and the computer that is managing the DTC.
Introduction Typical Network Configurations Host-based management also has the capability to provide the following types of network connections. These connections are described later in this section. • PAD access from terminals connected to PADs to the system that is managing the DTC. • X.25 Network Access from other systems connected to a PSN to the system that is managing the DTC. • Telnet access from terminals connected to the DTC ports to systems running ARPA standard Telnet services.
Introduction Typical Network Configurations PAD Access DTCs can optionally contain up to three DTC/X.25 Network Access cards. DTC/ X.25 Network Access cards connect devices to computers over a Packet Switching Network (PSN), by using a private or public PAD. A PAD, or Packet Assembler/Disassembler, is a device that converts asynchronous character streams into packets that can be transmitted over a PSN. Supported devices attached to the DTC can be remotely connected using a PAD.
Introduction Typical Network Configurations X.25 Network Access X.25 iX System Access, when used in conjunction with DTC/X.25 Network Access, allows you to establish a DTC/X.25 iX Network Access Link, thus connecting an HP 3000 computer to a public or private X.25 PSN. The X.25 network protocol processing is done by the DTC/X.25 Network Access card installed in the DTC. If PC-based management is used, then multiple HP 3000s can share the same X.25 network connection.
Introduction Typical Network Configurations Telnet/iX Access Telnet/iX provides connections to MPE systems from terminals connected to systems running ARPA standard Telnet services. Telnet/iX includes a Telnet Access Card (TAC) that resides in the DTC 48 or DTC 72MX and provides protocol conversion between Telnet and AFCP. Equivalent functionality is provided by the Telnet Express Server (HP2344A). NOTE A DTC 48 cannot contain both a TAC and an X.25 card.
Introduction Typical Network Configurations Multi-System Access Figure 1-5 shows a sample network configuration. The terminals connected to DTC 1 are configured so that they are able to establish connections to either System A or System B through the DTC Switching User Interface. Output devices connected to DTC 1, such as serial printers or plotters, are configured so that they can be opened using the software from either host.
Introduction Typical Network Configurations Back-to-Back Access By arranging DTCs and DTC terminal connections in a special way, terminal users can establish communications with an MPE V computer. This is referred to as back-to-back access. Figure 1-6 shows two DTCs in a simple back-to-back configuration. DTC 1 has terminals connected to it. DTC 2 is connected through one of its ports to the Advanced Terminal Processor (ATP) card in the MPE V computer.
Introduction Typical Network Configurations 30 Chapter 1
Before Configuring Terminal and Printer Connections 2 Before Configuring Terminal and Printer Connections This chapter contains information that is needed before configuration of systems for asynchronous device (terminal and printer) connections can begin. It also provides worksheets for you to collect your network configuration data before actual configuration.
Before Configuring Terminal and Printer Connections Plan the Network Plan the Network Before configuration can begin, the physical layout and configuration parameters for the systems, the DTCs, the OpenView Windows Workstation, and the connected devices on the LAN must be defined. This information must be translated into terms that the MPE/iX operating system can understand and use. For example, a node name for the system must be indicated and a link name must be specified.
Before Configuring Terminal and Printer Connections Defining the HP 3000 System Defining the HP 3000 System The following configuration parameters are required to define the HP 3000 host for asynchronous device connections. Local HP 3000 Node Name The name by which the HP 3000 Series 900 computer is known in your network. The format of a node name is nodename.domain.organization, where each field can contain 16 or fewer characters (alphanumeric, underscores, or hyphens).
Before Configuring Terminal and Printer Connections Defining the HP 3000 System HP 3000 Systems Slot Number 920, 922, 935, 932, 935, or 949 with HPIB 4.3 920, 925, 935, or 949 with ALINK 4.2 9X7 56 9X8 56/56 930 8.4 950, 955, 960, 980 2/4.
Before Configuring Terminal and Printer Connections Defining the DTC Defining the DTC The following parameters are required to define each DTC used for connection between the HP 3000 and its asynchronous devices (terminals and printers). DTC Name DTC LAN Station Address A name for the DTC, up to eight alphanumeric characters, beginning with a letter. Each DTC configured on the system must have a unique name. The local station address of the DTC.
Before Configuring Terminal and Printer Connections Defining the DTC DTC IP Address (optional) The internet protocol (IP) address of the DTC. The IP address is optional. It is used if your HP 3000 is configured as part of a network and you want the DTC to be able to respond to PING/iX requests. An IP address has four fields of decimal numbers: xxx.xxx.xxx.xxx where xxx is a number from 0 to 255. An IP address has two parts: a network portion and a node portion.
Before Configuring Terminal and Printer Connections Defining the DTC DTC 16iX/16MX/16RX has its two port connectors built directly onto its backplane for support of up to 16 asynchronous devices. It does not have removable cards; you do not specify the number or type of cards for a DTC 16iX/16MX/16RX. The valid card types are: For DTC 16 and DTC 48: D for direct connect cards (up to 8 ports per card), M for modem connect cards (up to 6 ports per card), X for DTC/X.
Before Configuring Terminal and Printer Connections Defining the DTC Connector Cards (or Boards) Defining the DTC Connector Cards (or Boards) Connector cards (also called boards) in the DTC allow terminals, printers, and other serial devices to be connected to the DTC for communication with an HP 3000 Series 900. For each connector card in a DTC, you must define the characteristics of its ports for connection to terminals, printers, and other serial devices.
Before Configuring Terminal and Printer Connections Defining the DTC Connector Cards (or Boards) called nailed devices. Printers and UPSs, as well as devices that will be programmatically accessed, must be nailed devices. Each nailed ldev number assigned in NMMGR must be unique. If the DTC management is PC-based (that is, managed by an OpenView Windows Workstation), you may have ports without ldev numbers assigned to them; hence they are non-nailed devices.
Before Configuring Terminal and Printer Connections Configuring With NMMGR Configuring With NMMGR NMMGR, the Node Management Configuration Manager, is the utility used by HP 3000 Series 900 to configure asynchronous device connections. The parameters described previously in this chapter are entered in NMMGR through a screen-by-screen user interface. These parameters are then stored by NMMGR into the HP 3000 network configuration file NMCONFIG.PUB.SYS.
Before Configuring Terminal and Printer Connections Configuring With NMMGR Figure 2-2 NMMGR DTS/DTC Screen Flow Chapter 2 41
Before Configuring Terminal and Printer Connections Configuration Worksheets Configuration Worksheets Before you proceed to NMMGR, it is recommended that you use the worksheets provided here to gather the necessary configuration information. Make copies of these worksheets and fill in the parameter information, then use these worksheets to guide you through configuration in NMMGR. Figure 2-3 shows which part of the configuration is covered by the worksheets.
Before Configuring Terminal and Printer Connections Configuration Worksheets HP 3000 DTC Configuration Worksheet Fill out worksheet as shown in Figure 2-4 with configuration information as needed. Figure 2-4 DTS Configuration Worksheet HP 3000 DTS Configuration Worksheet Local HP 3000 node name [node.domain.
Before Configuring Terminal and Printer Connections Configuration Worksheets DTC Configuration Worksheet Fill out worksheet as shown in Figure 2-5 for each DTC you are configuring.
Before Configuring Terminal and Printer Connections Configuration Worksheets DTC Card Configuration Worksheet Fill out worksheet as shown in Figure 2-6 for each direct connect card you are configuring Figure 2-6 DTC Card Configuration Worksheet Chapter 2 45
Before Configuring Terminal and Printer Connections Configuration Worksheets 46 Chapter 2
Automatic Configuration of DTCs 3 Automatic Configuration of DTCs This chapter describes how you can add and configure a new host-based managed DTC to the HP 3000 system without needing to specify detailed configuration information such as DTC cards/boards and ldevs (herein referred to as automatic configuration). You can perform an automatic configuration by using a command file that is activated either outside or inside the NMMGR utility.
Automatic Configuration of DTCs Performing an Automatic Configuration Outside NMMGR Performing an Automatic Configuration Outside NMMGR Automatic configuration is done via a command file called DTCCNTRL which allows you to manage DTS configurations. DTCCNTRL requires that you have a minimum of Network Manager (NM) capability. To perform an automatic configuration, you must still provide the DTC’s LAN address.
Automatic Configuration of DTCs Performing an Automatic Configuration Outside NMMGR For help on these topics, select 7 at the prompt below Select one of the numbers above corresponding to the desired operation: 3 • Automatic configuration operation specified: :DTCCNTRL func=autoconf 3. The following prompt will appear: ****Make sure your DTC is turned on NOW**** Enter the DTC LAN address in the format of xx-xx-xx-xx-xx-xx or press RETURN to exit: First, make sure that the DTC’s power has been turned on.
Automatic Configuration of DTCs Performing an Automatic Configuration Outside NMMGR All ports configured successfully.
Automatic Configuration of DTCs Performing an Automatic Configuration Inside NMMGR Performing an Automatic Configuration Inside NMMGR Automatic configuration can also be performed by invoking the DTCCNTRL command file inside the NMMGR utility. Refer to Chapter 5, “Configuring Serial Devices (for Host-Based Management),” for detailed steps on the NMMGR DTS host-based management configuration process. To automatically add and configure a DTC within NMMGR, you must still provide the DTC’s LAN address.
Automatic Configuration of DTCs Performing an Automatic Configuration Inside NMMGR Step 2: Activate Automatic Configuration Process The DTC Configuration Selection Screen (Figure 3-1) is displayed when you press the [Go to DTC] key at the Host Configuration Screen. Here you can access the DTC Automatic Configuration Screen and activate the automatic configuration process. Figure 3-1 DTC Configuration Selection Screen Follow the steps listed here to enter data for this screen. 1.
Automatic Configuration of DTCs Performing an Automatic Configuration Inside NMMGR Step 3: Complete Automatic configuration The DTC Automatic Configuration Screen appears (Figure 3-2). Figure 3-2 The DTC Automatic Configuration Screen Follow the steps listed here. 1. Make sure that the power for the DTC that you want to automatically add and configure is turned on. 2. Enter the LAN address of the DTC to be configured in the “DTC LAN station address” field.
Automatic Configuration of DTCs Performing an Automatic Configuration Inside NMMGR 5. Press the [Auto Config] function key to invoke DTCCNTRL and start the automatic configuration process. 6. The following will appear on the screen indicating successful DTC automatic configuration: DTCxxxx.domain.organization automatic configuration in progress..... (DTC download messages will appear here if you are at the system console.) DTCxxxx.domain.organization configured and downloaded successfully.
Dynamic Configuration and DTS Shutdown/Restart 4 Dynamic Configuration and DTS Shutdown/Restart This chapter describes how you can make most DTS configuration changes dynamically using NMMGR without rebooting the system (herein referred to as dynamic configuration. Such configuration changes include adding/deleting/ modifying terminals, printers, and DTCs. This chapter also discusses the DTS subsystem shutdown and restart capabilities provided through the DTCCNTRL command.
Dynamic Configuration and DTS Shutdown/Restart Dynamic Configuration Dynamic Configuration Dynamic configuration enables you to apply a select set of DTS configuration changes made in NMMGR without rebooting the system. Such configuration changes include adding or deleting terminals, printers and DTCs, changing most configuration parameters of terminals, printers and DTCs.
Dynamic Configuration and DTS Shutdown/Restart Dynamic Configuration Table 4-1 Dynamically Configurable Tasks Task Add/configure new terminal/printer Action Required for Change to Become Active No action; changes take effect dynamically Add/delete class name Change DTC event logging class Host-based X.25 configuration changes: – maximum number of PAD connections – X.25 link name – maximum number of switched virtual circuits – remote X.25 addresses and security – X.25 allow access – remote X.
Dynamic Configuration and DTS Shutdown/Restart Dynamic Configuration Task Action Required for Change to Become Active Host-based X.25 configuration changes: Use DTCCNTRL to: – change PAD access 1) Stop X.25/PADSUP – change level 1, 2, or 3 configuration 2) Start X.25/PADSUP (see Configuring and Managing Host-Based X.
Dynamic Configuration and DTS Shutdown/Restart Dynamic Configuration NMCONFIG and NMCONFIX Files Dynamic Configuration uses both files NMCONFIG.PUB.SYS and NMCONFIX.PUB.SYS to manage the devices created by the DTS subsystem. When users wish to make any dynamic change, NMMGR will be used to modify the configuration in NMCONFIG.PUB.SYS. When DTCCNTRL is invoked, either within or from outside of NMMGR, NMCONFIG will be compared to NMCONFIX and the desired changes will be made to the system configuration.
Dynamic Configuration and DTS Shutdown/Restart Dynamic Configuration Compressing the Configuration Files As your configuration grows and changes, you may find it necessary to compress or expand your configuration file. When you add items in a file, records are added sequentially from the beginning of the file. If you delete items from a configuration file, the records are not immediately recovered, so the middle of the file may contain unused records.
Dynamic Configuration and DTS Shutdown/Restart Performing a Dynamic Configuration Performing a Dynamic Configuration Follow the steps below to dynamically configure DTS changes. Refer to Chapter 5, “Configuring Serial Devices (for Host-Based Management),” and Chapter 6, “Configuring Serial Devices (for PC-Based Management),” for more detailed steps on the DTS configuration process using NMMGR for host-based and PC-based DTC management, respectively. NMMGR can keep up to 70 changes.
Dynamic Configuration and DTS Shutdown/Restart Performing a Dynamic Configuration If you type Y, dynamic configuration changes will take effect now. NMMGR calls DTCCNTRL which dynamically implements the DTS changes made in NMMGR. If you type N, dynamic configuration changes will not take effect now. Your changes will take effect the next time dynamic configuration is invoked, a DTS shutdown/ restart is performed, or the system is rebooted.
Dynamic Configuration and DTS Shutdown/Restart Performing a Dynamic Configuration DTCCNTRL After NMMGR Exit If you choose not to invoke DTCCNTRL implicitly within NMMGR, you can run the command from the CI prompt at any time after you exit NMMGR. DTCCNTRL requires that you have a minimum of Network Manager (NM) capability.
Dynamic Configuration and DTS Shutdown/Restart Performing a Dynamic Configuration NOTE To automatically add/configure a host-based managed DTC to DTS without needing to specify detailed configuration information such as DTC cards/boards and ldevs, refer to Chapter 3, “Automatic Configuration of DTCs.” To manage/dynamically configure host-based X.25 links, refer to the Configuring and Managing Host-Based X.25 Links manual.
Dynamic Configuration and DTS Shutdown/Restart Performing a Dynamic Configuration LOGDCC and LOGDCCBK Files When the system rebooted or a DTS shutdown/restart executed, an ASCII file call LOGDCC.PUB.SYS is purged and recreated to log DCC startup console messages, and the results of any dynamic configuration operations. This file acts as a log of all dynamic configuration changes since the last system reboot or DTS restart. An example of the contents in LOGDCC.PUB.
Dynamic Configuration and DTS Shutdown/Restart Performing a Dynamic Configuration Dynamic Configuration Status You can also use DTCCNTRL to check the status of the last dynamic configuration.
Dynamic Configuration and DTS Shutdown/Restart DTS Shutdown DTS Shutdown The DTS shutdown capability is provided by the DTCCNTRL command. It allows you to bring down the entire DTS subsystem and includes the release of all TIO-related system resources. DTCCNTRL requires that you have a minimum of System Manager (SM) capability. This operation can only be done from the system console.
Dynamic Configuration and DTS Shutdown/Restart DTS Shutdown Performing a DTS Shutdown To perform a DTS shutdown, type the DTCCNTRL command at the CI prompt either without specifying the desired shutdown operation or by specifying it using the syntax outlined below: • DTS shutdown operation not specified: :DTCCNTRL 0 exit 1 dynamically implement DTS changes made in NMMGR 2 view status of last DTS dynamic configuration 3 automatically add a new DTC 4 shutdown DTS subsystem 5 restart DTS subsystem
Dynamic Configuration and DTS Shutdown/Restart DTS Restart DTS Restart The DTS restart capability is provided by the DTCCNTRL command and allows you to restart the DTS subsystem. NOTE The DTS must first be shut down before it can be restarted.
Dynamic Configuration and DTS Shutdown/Restart DTS Restart 70 Chapter 4
Configuring Serial Devices (for Host-Based Management) 5 Configuring Serial Devices (for Host-Based Management) This chapter provides step-by-step instructions for configuring terminal, printer, and other serial device connections on the HP 3000 Series 900 using host-based management (that is, when the DTCs are managed by the HP 3000 host). For information on configuring for PC-based management, refer to Chapter 6, “Configuring Serial Devices (for PC-Based Management).
Configuring Serial Devices (for Host-Based Management) Network Configuration Overview Network Configuration Overview Information required for network configuration on the host is contained in one file. The name of this configuration file is NMCONFIG.PUB.SYS. When building a new configuration file, it is not necessary to define every field. This is because a sample configuration file is supplied with the MPE/iX operating system. The sample configuration file is called NMSAMP1.PUB.SYS.
Configuring Serial Devices (for Host-Based Management) Copy the Sample File Copy the Sample File Network information is stored in a configuration file called NMCONFIG.PUB.SYS. If you do not already have a NMCONFIG.PUB.SYS file, create a copy of NMCONFIG.PUB.SYS from the sample configuration file supplied on the HP 3000, NMSAMP1.PUB.SYS. To copy NMSAMP1.PUB.SYS into NMCONFIG.PUB.SYS, enter these commands at the MPE/iX prompt (:): HELLO MANAGER.SYS,PUB FILE CONFIG=NMCONFIG.PUB.SYS;DEV=1 FCOPY FROM=NMSAMP1.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Modify the Network Management Configuration File Use NMMGR to enter asynchronous device configuration information into the network management configuration file (NMCONFIG.PUB.SYS). A step-by-step procedure for updating the host’s network management configuration file follows. NOTE Before modifying the NMCONFIG.PUB.SYS file, make a backup copy of it.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Figure 5-1 Open Configuration/Directory Screen Follow the steps listed here to enter data for this screen. Refer to “Fields” subsection on the next page for detailed information about each field on the screen. 1. NMCONFIG.PUB.SYS is the name required by the software. Verify that this name is displayed in the Configuration file name field. 2.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File You can create or modify a configuration file using a different name and save it as an offline configuration file. You can use offline configuration files as a means of creating and storing configurations that you want to use in the future. When you are ready to use an offline configuration file, rename it as NMCONFIG.PUB.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Step 3: Configure the Local Node Name The Main screen is displayed after you press the [Open Config] key (Figure 5-2). This screen lets you specify the HP 3000 host’s name. It also asks whether you are using the HP 3000 host or an OpenView Windows Workstation (PC) for DTC management, and if you are using X.25 or PAD. Figure 5-2 Main Screen 1.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File 3. In the field after the question, “Do you have X.25 system-to-system or PAD connections?”, enter an N for no. If you have X.25, refer to the Configuring and Managing Host-Based X.25 Links manual. 4. After you enter the information on the screen, press the [Save Data] function key to save your entries. 5.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File 3. In the “Physical path of LANIC” field, type the slot number for the LANIC card in the host. See the list on the next page for commonly used slot numbers. 4. Press the [Save Data] function key. Press the [Go to DTC] function key to proceed to step 5: Select DTC Type. Go to UserPort The [Go To UserPort] key is used to configure the user port (default ldev 21) on the NIO console.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File HP 3000 Systems Slot Number 920, 922, 935, 932, 935, or 949 with HPIB 4.3 920, 925, 935, or 949 with ALINK 4.2 9X7 56 9X8 56/56 930 8.4 950, 955, 960, 980 2/4.2 990/992, 991/995 0/40 Step 5: Select DTC Type The DTC Configuration Selection screen (Figure 5-4) is displayed when you press the [Go To DTC] key at the Host Configuration screen. Here you specify the type of DTC to configure.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File 1. Select the DTC type by pressing one of the function keys: [DTC16iX], [DTC16MX/ RX], [DTC16], [DTC48], or [DTC72MX]. NMMGR will take you to the configuration screen for the specified DTC type. NOTE You may use the [List DTCs] key on the DTC Configuration Selection Screen to see a list of all DTC names configured on your system.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File The LAN address can be found on a label inside the front cover or on the back panel of the actual DTC box. For DTC 16RX access to an HP 3000 in an MPE/iX host-based management environment, use the value 00-00-00-00-00-00 as the DTC 16RX LAN address. Configuration of the DTC 16RX on the HP 9000 host using DTC 16RX Manager uses the DTC’s IP address and not its LAN address. 3.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Note that DTC 16iX/16MX/16RX does not have cards since its port connectors are built directly onto the DTC backplane. Refer to Chapter 2, “Before Configuring Terminal and Printer Connections,” for more information on card types for each DTC. 7. Press the [Save Data] function key. 8.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Config SNMP You may use the [Config SNMP] key on the DTC Screen to configure the DTC to act as an SNMP agent. This key goes to a screen to configure the DTC to act as an SNMP agent. Refer to Appendix C, “DTC User Interface,” for steps to do this. Refer to the DTC Technical Reference Guide manual for more information on SNMP.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File 3. Press the [Tab] key to move the cursor to the first port on the card. Enter an ldev number for this port in the “Ldev” field. Ldev numbers used for each port on the DTC must be unique. For example, you can use ldev number 100 for port 0 of the first card, and increment the ldev number by 1 for each consecutive port.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File CAUTION Before you exit this screen, make sure you press [Save Data] if you want to keep the data on the screen; otherwise your screen input will be lost. This occurs even if you temporarily exit the screen to read [Help] information. 7. To configure another card, enter the card number you want to configure in the field “To configure a different card, enter its number,...” .
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Step 8: Validate/Cross-Validate the Configuration File Validation ensures that no conflicts exist in the network configuration file (NMCONFIG.PUB.SYS) between the DTCs and other configuration parameters. After NMMGR validates the network configuration file, it will automatically cross-validate the file with the system I/O devices configured through the SYSGEN utility.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File NMMGR will now cross-validate the NMCONFIG file with SYSGEN. SYSGEN version E.02.00 : catalog version E.02.00 THU, DEC Copyright 1987 Hewlett-Packard Co. All Rights Reserved. 4, 1997, 2:58 AM **note** Retrieving NMMGR configuration data...
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File 3. After successful validation and cross-validation, and if the file in use is NMCONFIG.PUB.
Configuring Serial Devices (for Host-Based Management) Modify the Network Management Configuration File Step 9: Ensure DTS Changes Become Active If you answered Y to the question “Do you want DTS changes to become active now (Y/N)?” in step 8, refer to Table 4-1 in Chapter 4, “Dynamic Configuration and DTS Shutdown/Restart,” for a list of configuration tasks and associated actions for changes to become active.
Configuring Serial Devices (for PC-Based Management) 6 Configuring Serial Devices (for PC-Based Management) This chapter describes NMMGR configuration steps that you need to perform for PC-based management (that is, when the DTCs are managed by an OpenView Windows Workstation). For information on configuring for host-based management, refer to Chapter 5, “Configuring Serial Devices (for Host-Based Management).” NOTE If you are configuring X.
Configuring Serial Devices (for PC-Based Management) OpenView DTC Manager and NMMGR OpenView DTC Manager and NMMGR When the system is configured for PC-Based management, there are several parameters configured in NMMGR that must match corresponding parameters configured in the OpenView DTC Manager. For each DTC that is to have access to the system using nailed devices there must be a corresponding DTC configured on the OpenView DTC Manager.
Configuring Serial Devices (for PC-Based Management) Copy the Sample File Copy the Sample File Network information is stored in a configuration file called NMCONFIG.PUB.SYS. If you do not already have a NMCONFIG.PUB.SYS file, create a copy of NMCONFIG.PUB.SYS from the sample configuration file supplied on the HP 3000, NMSAMP1.PUB.SYS. To copy NMSAMP1.PUB.SYS into NMCONFIG.PUB.SYS, enter these commands at the MPE/iX prompt (:): HELLO MANAGER.SYS,PUB FILE CONFIG=NMCONFIG.PUB.SYS;DEV=1 FCOPY FROM=NMSAMP1.PUB.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Modify the Network Management Configuration File Use NMMGR to enter asynchronous device connection information into the Network Management Configuration File NMCONFIG.PUB.SYS. The procedure for updating the configuration file follows. Step 1. Begin the Configuration Process To run NMMGR, enter the following command at the MPE/iX prompt and then press the [Return] key. NMMGR.PUB.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Step 2: Open the Network Management Configuration File Invoke NMMGR, the Open Configuration/Directory File screen as shown in Figure 6-1, allows you to specify the configuration file name. Figure 6-1 Open configuration/Directory Screen 1. Use the default configuration file name, NMCONFIG.PUB.SYS. 2. Enter a backup configuration file name. The default is NMCBACK.PUB.SYS. 3.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Step 3: Configure the Local Node Name The Main screen is displayed (Figure 6-2). This screen lets you specify the HP 3000’s node name. It also asks whether you are using the HP 3000 or an OpenView Windows Workstation to manage the DTCs, and if you are using X.25 or PAD. Figure 6-2 Main Screen 1.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Step 4: Configure the Link The Host Configuration screen is displayed when you press the [DTS] key at the Main screen (Figure 6-3). Figure 6-3 Host Configuration Screen (PC-Based) 1. “Local HP 3000 node name” is a display-only field. Verify that it is correct. 2. Use the default link name, DTSLINK. 3. Enter the slot number of the LANIC in the “Physical path of LANIC” field.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File NOTE If you want the HP 3000 system to be able to accept connections from terminals on ARPA systems via a Telnet Express Server, you must use a modem profile for the non-nailed terminals, such as TR10U24. Note that you may use direct connect devices on a port with a modem profile. See the Host-Based Terminal Profiles table in Chapter 7, “Terminal and Printer Profiles,” for a list of available profiles.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Step 5: Select DTC Type The DTC Configuration Selection screen (Figure 6-4) is displayed when you press the [Go To DTC] key at the Host Configuration screen. Here you specify the type of DTC to configure. You only need to configure DTCs with nailed ports that will be accessed by this HP 3000 computer. Figure 6-4 DTC Configuration Selection Screen 1.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Step 6: Specify DTC Configuration The DTC Configuration screen is displayed after you select the DTC type. Figure 6-5 shows a DTC Configuration screen for a DTC 72MX. (DTC 16iX/16MX/16RX, DTC 16 and DTC 48 screens vary slightly.) Figure 6-5 DTC Configuration Screen 1. Enter the DTC name in the “DTC name” field. 2. Enter the DTC’s node name in the “DTC node name” field. 3.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File If you are configuring a direct or modem connect card the [Config Card] key will go to the screen described in the subsection Configure a Direct Connect Card. If you are configuring a X.25 card the [Config Card] key will go to the screen described in the subsection Configure a X.25 Card. To configure the ports on a DTC 16iX/16MX/16RX, simply press the [Config Ports] function key.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Figure 6-6 DTC Card Configuration Screen 1. Verify that the “DTC name” and “Card number” displayed are correct. 2. Use the [Tab] to move the cursor to the first nailed port on the card. Enter the ldev number and profile for each nailed device. Ldev numbers used for each port on the DTCs must be unique. Up to 4649 terminal I/O devices may be configured on an HP 3000 Series 900.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File 6. If all the cards with nailed ports have been configured, press the [Prior Screen] key to return to the DTC Configuration Selection screen to select another DTC with nailed ports to configure. Otherwise, if every DTC has been configured, press the [Validate DTS/LINK] key to validate the configuration file. Configure a X.25 Card When a X.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File The device name entered must match the PAD Device Name entered in the PAD Access screen on the OpenView DTC Manager. Refer to Using HP OpenView DTC Manager. Step 8: Validate/Cross-Validate the Configuration File Validation ensures that no conflicts exist in the network configuration file (NMCONFIG.PUB.SYS between the DTCs and other configuration parameters.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File 2. After validation of the network configuration file is complete, the following will appear on the screen as the file is cross-validated with the files created with SYSGEN (warning messages may vary): NMMGR will now cross-validate the NMCONFIG file with SYSGEN. SYSGEN version E.02.00 : catalog version E.02.00 THU, DEC Copyright 1987 Hewlett-Packard Co. All Rights Reserved.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File 3. After successful validation and cross-validation, and if the file in use is NMCONFIG.PUB.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File Step 9: Ensure DTS Changes Become Active If you answered Y to the question “Do you want DTS changes to become active now (Y/N/H)?” upon NMMGR exit in step 8, refer to Table 4-1 in Chapter 4, “Dynamic Configuration and DTS Shutdown/Restart,” for a list of configuration tasks and associated actions for changes to become active.
Configuring Serial Devices (for PC-Based Management) Modify the Network Management Configuration File 108 Chapter 6
Terminal and Printer Profiles 7 Terminal and Printer Profiles This chapter describes what are terminal and printer profiles and how to create and modify your own profiles. The process is similar for both host-based and PC-based management. Differences between host-based and PC-based management will be noted.
Terminal and Printer Profiles What is a Profile What is a Profile A profile is a grouping of device connection specifications and characteristics that can be associated to devices. Profiles can be associated to terminals, printers, PAD terminals and printers, and UPSs. The sample configuration file on the HP 3000 Series 900 supplies several terminal and printer profiles for use. You may also create your own profiles.
Terminal and Printer Profiles What is a Profile • Whether the user is allowed to enter the :HELLO command to logon to the HP 3000. • Whether the terminal will use hardware handshake. (Supported on DTC 16iX/ 16MX and DTC 72MX only.) • The type of parity that will be used if parity is enabled. • Specifies whether auto speed and parity sensing will occur at logon for terminals using this profile. (Does not apply to the DTC 16RX).
Terminal and Printer Profiles What is a Profile Printer Profiles Printer profiles define printer characteristics for printers. A printer profile defines these printer characteristics: • The profile name. • The printer type used (18, 21, 22, or 26) or the printer type file name if you are using a printer type file created through the workstation configurator utility (TTUTIL.PUB.SYS). For more information, see Printer type file name under “Printer Profile Screen,” later in this chapter.
Terminal and Printer Profiles What is a Profile • Specify whether “keep alive” mechanism is to be activated to detect if connection is still there. (Does not apply to the DTC 48 without memory extension.) • Specify whether port configuration parameters; data length and parity, have to be forced when binary mode is selected. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.) • Specify destination node if automatic connection is enabled.
Terminal and Printer Profiles What is a Profile These four parameters will also be ignored when the connection is made through a public PAD, because the connection will be established to a non-nailed device on the host. PAD Printer Profiles A PAD printer profile defines these characteristics of a PAD printer: • The profile name • The printer type used (26 for PAD printer) or the printer type file name if you are using a terminal type file created through the workstation configurator utility (TTUTIL.PUB.
Terminal and Printer Profiles What is a Profile • Specify whether ENQ/ACK flow control is enabled. • Number of stop bits to be used for asynchronous characters. (Supported on DTC 16iX/DTC 16MX and DTC 72MX only.) • Whether to enable flow control between the DTC port and the connected device. • Specify whether “keep alive” mechanism is to be activated to detect if connection is still there. (Does not apply to the DTC 48 without the memory extension.
Terminal and Printer Profiles What is a Profile Terminal Type 18 Use terminal type 18 for non-Hewlett-Packard devices. It differs from terminal type 10 in the following ways: • Block mode data transfers are not supported. • Data protection is supplied through the XON/XOFF protocol. By default, parity checking is not used. • The read trigger character is not recognized. Terminal Type 24 Use terminal type 24 for PAD terminals. Limitations apply to operations over PAD connections.
Terminal and Printer Profiles What is a Profile Printer type 18 responds to an XOFF character sent from a printer. The XOFF protocol stops the flow of data to the printer so data cannot be lost. However, the printer cannot send an XOFF character if it is unplugged, turned off, or loses power. In these instances, data is lost. Printer Type 21 Use printer type 21 for remote spooled printers. These are asynchronous printers that can use the MPE/iX spooler.
Terminal and Printer Profiles Creating and Modifying Profiles Creating and Modifying Profiles The DTS Profile Selection screen for PC-based management (Figure 7-1) lists the profiles available in your configuration file. (To reach this screen, press the [Go to Profiles] key at the Host Configuration screen or the Card Configuration screen.) From this Profile Selection screen, you may review, add, delete, or modify profiles. (Screen varies slightly for host-based management.
Terminal and Printer Profiles Creating and Modifying Profiles 5. If you are adding a profile, enter the profile type in the Type field. For host-based configuration files the valid profile types are: terminal, printer, padterm, padprint, host. Press the [Add Profile] key. Proceed to step 7 below. For pc-based configuration files the valid types are: terminal, printer. 6. If you are modifying or reviewing a profile, press the [Modify Profile] key. Proceed to the next step below. 7.
Terminal and Printer Profiles Terminal Profile Screen (Host-Based) Terminal Profile Screen (Host-Based) The Terminal Profile screen is used to define characteristics associated with a terminal profile. Figure 7-2 shows a Terminal Profile screen for host-based management. The PC-based Terminal Profile screen varies slightly, see Figure 7-4, Terminal Profile screen (PC-Based). Figure 7-2 Terminal Profile Screen (Host-Based) Review the profile settings on the screen.
Terminal and Printer Profiles Terminal Profile Screen (Host-Based) Terminal type file name Instead of using the default terminal types 10, 18, or 24, you may create your own terminal type and save it in a file. To create a customized terminal type, use the Workstation Configurator, TTUTIL.PUB.SYS. Refer to the Customizing Terminal and Printer Type Files with Workstation Configurator for more information. Line speed Record width Modem type The line speed, in bits per second.
Terminal and Printer Profiles Terminal Profile Screen (Host-Based) 1 specifies DCE modem behavior. Used for terminal connections. It uses a 2 minute timer to establish the link, and the DTC may disconnect if a carriage return is not received within a 2 minute interval. 2 specifies DTE modem behavior. Used for termtype 26 supported on MPE/iX for remote printer access. 3 specifies DCE modem behavior, except that it does not use a 2 minute timer to establish the link.
Terminal and Printer Profiles Terminal Profile Screen (Host-Based) Speed/Parity sensing? Specifies whether auto speed and parity sensing will occur at logon for terminals using this profile. This field does not apply for DTC 16RX access to an HP 3000 in an MPE/iX host-based management environment; any value entered in this field for a DTC 16RX will be ignored. Hardware handshaking? Specifies whether hardware handshake will be used.
Terminal and Printer Profiles Terminal Profile Screen (Host-Based) NOTE If you are changing profile characteristics, you can see which ldevs and DTCs will be affected by the change by pressing the [Assoc Ldevs] function key on the profile screen corresponding to the profile you are changing. After pressing this key, you will see a list of all ldevs using this profile in the DTCs configured in DTS.
Terminal and Printer Profiles Terminal Switching Configuration Screen Terminal Switching Configuration Screen Figure 7-3 displays the Terminal Switching Configuration screen. You can reach this screen by pressing [F5], the [Go To Switch] function key, at the Terminal Profile screen. The Terminal Switching Configuration screen allows you to configure host-based terminal switching parameters. Path name: DTS.PROFILE.profname.
Terminal and Printer Profiles Terminal Switching Configuration Screen Data transfer Specifies the mode of data transfer. For back-to-back connections, the field can be either ASCII or binary. If the profile will not be configured for back-to-back connections, enter 1 for ASCII. The default is ASCII. Escape from data transfer character Optional field which specifies the character which will return the terminal user to the DTC user interface. Field applies only if switching is enabled.
Terminal and Printer Profiles Terminal Switching Configuration Screen system. You will see a DTC prompt that is specified on the DTC User Interface screen Figure 8-3 in Chapter 8, “Additional DTC Configuration.” Connection to other systems on the LAN can be made by entering connect system name at the DTC prompt (refer to Chapter 8, “Additional DTC Configuration,” for more information on the DTC user interface).
Terminal and Printer Profiles Terminal Switching Configuration Screen address in the format xxx.xxx.xxx.xxx. Default is the entry in the field “Local HP 3000 node name” on the Main screen. Initialization string Optional field that specifies the string that will be sent to the attached device under one of the following circumstances: • After resetting a port. • After closing a session on the host and returning to the DTC user interface.
Terminal and Printer Profiles Terminal Profile Screen (PC-Based) Terminal Profile Screen (PC-Based) Figure 7-4 shows a Terminal Profile screen for PC-based management. Note that you only need to configure a terminal profile for nailed terminals if you are using PC-based management. Nailed terminals are ports with permanent ldevs assigned to them and can be accessed programmatically.
Terminal and Printer Profiles Printer Profile Screen (Host-Based) Printer Profile Screen (Host-Based) The Printer Profile screen is used to define the characteristics associated with a printer profile. Figure 7-5 shows a Printer Profile screen for host-based management. PC-based management Printer Profile screen varies slightly, see Figure 7-7. Figure 7-5 Printer Profile Screen (Host-Based) Review the profile settings on the screen. Use the [Tab] key to move from field to field.
Terminal and Printer Profiles Printer Profile Screen (Host-Based) Printer type file name Instead of using the default printer type files 18, 21, 22, or 26, you may create your own customized printer type and store it in a file. Use the Workstation Configurator, TTUTIL.PUB.SYS to create your own printer type files. Refer to the Customizing Terminal and Printer Type Files with Workstation Configurator for more information. Line speed Record width Modem type The line speed, in bits per second.
Terminal and Printer Profiles Printer Profile Screen (Host-Based) 1 specifies DCE modem behavior. Used for terminal connections. It uses a 2 minute timer to establish the link, and the DTC may disconnect if a carriage return is not received within a 2 minute interval. 2 specifies DTE modem behavior. Used for termtype 26 supported on MPE/iX for remote printer access. 3 specifies DCE modem behavior, except that it does not use a 2 minute timer to establish the link.
Terminal and Printer Profiles Printer Profile Screen (Host-Based) DTC 16RX access to an HP 3000 in an MPE/iX host-based management environment and any value entered in this field for a DTC 16RX will be ignored. Hardware handshaking? Specifies whether hardware handshake will be used. Hardware handshake uses modem signals CTS and RTS to pace the data transfer from the DTC to the attached device. (Supported on DTC 16iX/16MX and DTC 72MX only.
Terminal and Printer Profiles Printer Profile Screen (Host-Based) NOTE If you are changing profile characteristics, you can see which ldevs and DTCs will be affected by the change by pressing the [Assoc Ldevs] function key on the profile screen corresponding to the profile you are changing. After pressing this key, you will see a list of all ldevs using this profile in the DTCs configured in DTS.
Terminal and Printer Profiles Printer Switching Configuration Screen Printer Switching Configuration Screen Figure 7-6 displays the Printer Switching Configuration screen. You can reach this screen by pressing [F5], the [Go To Switch] function key, at the Printer Profile screen. Use the Printer Switching Configuration screen to configure host-based printer switching parameters. Path name: DTS.PROFILE.profname.
Terminal and Printer Profiles Printer Switching Configuration Screen Number of hosts sharing printer Specifies the number of hosts that can share the printer. If the port is being accessed by one system, and a second system attempts to access the port, the second system will be put in a queue and will be allowed to access the port when the first system is done. If more than the specified number of hosts attempt to access the port, the spooler will be stopped on error on the systems that exceeds the limit.
Terminal and Printer Profiles Printer Switching Configuration Screen port configuration remains unchanged when binary mode is selected. If set to N, then the data length is set to 8 and parity is set to none when binary mode is selected. The default is N. Supported on DTC 16iX/DTC 16MX and DTC 72MX only. Default destination This field specifies the system to which the printer is dedicated if “Dedicated printer” is enabled, or to which the printer will connect when automatic connection is enabled.
Terminal and Printer Profiles Printer Profile Screen (PC-Based) Printer Profile Screen (PC-Based) Figure 7-7 shows a Printer Profile screen used for PC-based management. Figure 7-7 Printer Profile Screen (PC-Based) NOTE The Printer Profile screen used for PC-based management contains a subset of the fields used by the Printer Profile screen used for host-based management (Figure 7-5). Refer to the previous subsection for an explanation of the fields.
Terminal and Printer Profiles PAD Terminal Profile (Host-Based) PAD Terminal Profile (Host-Based) The PAD Terminal Profile screen, as shown in Figure 7-8 is used to define the characteristics associated with a PAD terminal profile. Note that this screen is used for host-based management only. For PC-based management, you should use the regular PC-Based Terminal Profile screen shown in Figure 7-4 for PAD terminals.
Terminal and Printer Profiles PAD Terminal Profile (Host-Based) Fields Terminal type The terminal type being associated with the profile. The only valid terminal type for PAD terminal profiles is terminal type 24. Terminal type file name A terminal type file created with the Workstation Configurator utility (TTUTIL.PUB.SYS), to be associated with the profile instead of the system-supplied terminal type. Enter the fully qualified file name (filename.group.account).
Terminal and Printer Profiles PAD Terminal Profile (Host-Based) Record (AEOR) is set. If this field is Y then the data forwarding parms #3 and #4 setting established at connection time is always used. Data forwarding parm #3 and #4 This setting tells the PAD when a packet must be sent to the PDN. Parm #3 selects the set of characters that will signal the PAD to forward data to the PDN. Parm #4 sets the idle timer in 1/20 second increments.
Terminal and Printer Profiles PAD Terminal Profile (Host-Based) NOTE If you are changing profile characteristics, you can see which ldevs and DTCs will be affected by the change by pressing the [Assoc Ldevs] function key on the profile screen corresponding to the profile you are changing. After pressing this key, you will see a list of all ldevs using this profile in the DTCs configured in DTS.
Terminal and Printer Profiles PAD Printer Profile (Host-Based) PAD Printer Profile (Host-Based) The PAD Printer Profile screen, as shown in Figure 7-9 is used to define the characteristics associated with a PAD printer profile. This profile screen is used for host-based management only. For PC-based management, you should use the regular PC-based Printer Profile screen shown in Figure 7-7 for PAD printers. Figure 7-9 PAD Printer Profile Screen (Host-Based) Review the profile settings on the screen.
Terminal and Printer Profiles PAD Printer Profile (Host-Based) Customizing Terminal and Printer Type Files with Workstation Configurator for more information on TTUTIL.PUB.SYS. Record width The number of characters for each record. For HP terminals, the record width is usually 132 (the width of the line). Initially spooled? Specifies whether the printer will be initially spooled. NLIO device? Specifies whether native language devices will be used.
Terminal and Printer Profiles Host Profile Screen (Host-Based) Host Profile Screen (Host-Based) Figure 7-10 displays the new Host Profile screen. Use this screen to configure host ports for back-to-back. Path name: DTS.PROFILE.profname Figure 7-10 Host Profile Screen Review the profile settings on the screen. Use the [Tab] key to move from field to field. Make changes as needed by typing over the current values. When you have made the desired changes, press the [Save Data] key.
Terminal and Printer Profiles Host Profile Screen (Host-Based) If routers are used to connect two DTCs, this field must contain an IP address. Line speed The line speed, in bits per second. Supported speeds are 300, 1200, 2400, 4800, 9600, 19200, and 38400. Default is 9600. (Line speed 38400 is supported for direct connect devices on DTC 16iX/DTC 16MX and DTC 72MX only, and the attached device must also support this speed.) Modem type Specifies the type of modem used in the connection.
Terminal and Printer Profiles Host Profile Screen (Host-Based) Data Length/Parity Specifies the type of parity and data length will be used using this profile. The full list of supported data length with parity settings is as given: None means that the 8 bits data length with parity none will be used. Even means that the 7 bits data length with even parity will be used. Odd means that 7 bits data length with odd parity will be used. 0’s means that 7 bits data length with parity forced to 0 will be used.
Terminal and Printer Profiles Host Profile Screen (Host-Based) Hardware handshaking? Specifies whether hardware handshake will be used. Hardware handshake uses modem signals CTS and RTS to pace the data transfer from the DTC to the attached device. Default is N. (Supported on DTC 16iX/16MX and DTC 72MX only.) Automatic connection? Enables automatic connection capability of the port. When enabled, the port will automatically connect to the system specified in the “Destination node name” field.
Terminal and Printer Profiles Host Profile Screen (Host-Based) data length is forced to 8 and parity to none when binary mode is selected. Default value of this field is N Only applicable for new DTCs. Destination node name Optional field which specifies the system to which the port will connect if “Automatic connection?” field is enabled. A name must be entered if “Automatic connection?” is enabled.
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles System Supplied Terminal and Printer Profiles The following tables list the terminal and printer profiles supplied by the MPE/iX system for host-based and PC-based management. You may choose these profiles for your terminal and printer configuration. You may also create your own profiles. See Table 7-1 for Host-Based Terminal Profiles.
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Profile Name Characteristics Suggested Devices TR10U24 Terminal type 24 Record width of 80 bytes Parity: none Speed/Parity Sensing? N Reset HP Terminals? N Allow :HELLO logon? Y NLIO devices? N No device classes assigned Supported HP terminals Connected to modem port Set at 2400 bps TR24 Terminal type 24 Record width of 80 bytes Parity: none Speed/Parity Sensing? N Reset HP Terminals? N Allow :HELLO logon? Y NLIO devices? N
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Table 7-2 PC-Based Terminal Profiles Profile Name Characteristics Suggested Devices TR10D24 Terminal type 10 Record width of 80 bytes Allow :HELLO logon? Y NLIO devices? N No device classes assigned Supported HP terminals Connected directly TR10D96 Terminal type 10 Record width of 80 bytes Allow :HELLO logon? Y NLIO devices? N No device classes assigned Supported HP terminals Connected directly TR10E12 TR10U12 Terminal ty
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Table 7-3 Host-Based Printer Profiles Profile Name Characteristics Suggested Devices PR18D24 Printer type 18 Record width of 132 bytes Spooled No NLIO devices Parity: none Device class: SERLP1 Printers with no status checking Connected directly Set at 2400 bps PR18D96 Printer type 18 Record width of 132 bytes Spooled No NLIO devices Parity: none Device class: SERLP2 Printers with no status checking Connected directly Set at
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Profile Name Characteristics Suggested Devices PR26D96 Printer type 26 Record width of 132 bytes Spooled No NLIO devices Parity: none Device class: SERLP8 Supported HP printers Connected directly Set at 9600 bps PR26PAD Printer type 26 Record width of 132 bytes Spooled No NLIO devices PAD test requested? Y Send initial profile? Y X.
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles Table 7-4 PC-Based Printer Profiles Profile Name Characteristics Suggested Devices PR22D12 Printer type 22 Record width of 132 bytes Spooled No NLIO devices No device classes assigned Supported HP printers with status checking Connected to modem port PR22D24 Printer type 22 Record width of 132 bytes Spooled No NLIO devices No device classes assigned Supported HP printers with status checking Connected to modem port PR26 P
Terminal and Printer Profiles System Supplied Terminal and Printer Profiles 156 Chapter 7
Additional DTC Configuration 8 Additional DTC Configuration This chapter describes how to configure additional optional configuration parameters that are available from the DTC Configuration screen. These screens (except for Tune DTC) are only available from a host-based configuration. These additional screens allow you to configure the following: • Configure the DTC to use the address resolution facilities of Domain Name Services (DNS) and IP routing.
Additional DTC Configuration Configuring DNS/IP Configuring DNS/IP Figure 8-1 displays the DNS/IP Routing Configuration screen. You can reach this screen by pressing [F1], the [DNS/IP Routing] function key, at the DTC Configuration screen. See the beginning of this chapter to find out how to access the [DNS/IP Routing] function key.
Additional DTC Configuration Configuring DNS/IP 4. (Optional) Enter the ARPA default local domain name. If this field is configured then the Default Server Address must also be configured. 5. (Optional) Complete the “Default IP router address” field. 6. (Optional) Complete the “Backup IP router address” field. 7. Complete the “Subnet mask” field. The default is 255.000.000.000. 8. After you have entered the desired values, press the [Save Data] key. 9.
Additional DTC Configuration Configuring DNS/IP this field. Otherwise it concatenates the with the contents of this field. The DTC then sends a request to the Default Server to resolve the domain name into an IP address. Default IP router address Backup IP router address Optional field which specifies the IP address of the default router. The router routes outbound packets for destinations outside the local subnet.
Additional DTC Configuration Tuning Your DTC Tuning Your DTC This section describes the steps for tuning your DTC by selecting the AFCP, TCP and management timers that are appropriate for your DTC and network traffic. The timer selection is made by choosing a set from a predefined set of timer values. The TCP timers are only used for back-to-back connections from switched DTC ports. Figure 8-2 displays the Tune DTC — Timer Configuration screen.
Additional DTC Configuration Tuning Your DTC 4. Select one of two predefined sets of values for management timer. The default is selection 1. The management protocol timers determine different transmission algorithms. 5. After you have selected the desired timer values, press the [Save Data] key. 6. Press the [Prior Screen] key to return to the DTC Configuration screen, or press [Validate DTS/LINK] to validate your configuration if you have completed configuration for your DTCs.
Additional DTC Configuration Tuning Your DTC AFCP Timer Set 6 TCP Timer Set 1 TCP Timer Set 2 TCP Timer Set 3 TCP Timer Set 4 TCP Timer Set 5 MPE XL release 2.1 timer mode. This is appropriate for use with HP 3000 MPE XL FOS release 2.1. Normal timer mode. For local transaction processing applications and Telnet connections on local LAN. Bridge timer mode. Same mode as Set 1 but with bridges. Suitable for LANs with moderate delays. Router/X.25 timer mode. Same mode as Set 1 but with routers or X.25.
Additional DTC Configuration Configuring the DTC User Interface Configuring the DTC User Interface When a DTC port is assigned a profile that has the field “Enable Switching” set to Y then the user will enter the DTC user interface when [RETURN] is first pressed. While at the DTC user interface, the user can enter several commands. The DTC user interface screen is used to configure parameters that determine how this user interface behaves. See Appendix C, “DTC User Interface.
Additional DTC Configuration Configuring the DTC User Interface 4. (Optional) Complete the “Welcome message” field. 5. After you have completed the necessary fields, press the [Save Data] key. 6. Press the [Prior Screen] key to return to the Tune DTC – Timer Selection screen. Fields DTC name DTC user interface timeout A display-only field. The configuration applies to the DTC whose name is shown.
Additional DTC Configuration Configuring SNMP Configuring SNMP This section describes how to configure a host-managed DTC to act as an SNMP (Simple Network Management Protocol) agent. For PC-based DTC management, refer to the Using HP OpenView DTC Manager manual. Configuring SNMP Authorization Filters To configure SNMP authorization filters, access the SNMP Authorization Filter Configuration screen within NMMGR.
Additional DTC Configuration Configuring SNMP 1. Enter the IP address of the SNMP manager in the “IP Address” field. The IP address can be any valid individual IP address, or enter *.*.*.* or @.@.@.@ to indicate that any IP address is allowed access. 2. Enter the name of the SNMP community to which the DTC belongs in the “Community Name” field. The community name is a maximum of 80 alphanumeric characters and is case-sensitive. 3. The “Read Only” field defines the access mode to MIB objects.
Additional DTC Configuration Configuring SNMP Figure 8-5 SNMP MIB Configuration Screen The “DTC Name” field is a read-only field which indicates the SNMP configuration is for that specific DTC. 1. The “SysContact”, “SysName”, and “SysLocation” fields provide optional information about the DTC such as contact person, the DTC’s fully-qualified name and physical location. Each field allows text up to 256 alphanumeric characters and is case sensitive. 2.
Additional DTC Configuration Configuring SNMP Configuring Trap Destinations To specify the SNMP managers that will receive any SNMP error messages generated by the DTC, access the SNMP Trap. Destination Configuration screen. This screen can be accessed by pressing the [Go To Trap] key at the SNMP MIB Configuration screen or SNMP Authorization Filter Configuration screen. The SNMP Trap Destination Configuration screen for host-based management is shown in Figure 8-6.
Additional DTC Configuration Configuring SNMP 3. Press the [Go to Filter] key to configure authorization filters or the [Go To MIB] key to configure MIB parameters. Or, if you have completed configuration for your DTCs, press [Validate DTS/LINK] to validate your configuration.
Describing Asynchronous Devices 9 Describing Asynchronous Devices This chapter discusses the following concepts: • How the HP 3000 Series 900 initially recognizes devices and how it communicates with them from that time on. • How devices are owned, who can own them, and the restrictions that apply when a device is owned. • How the MPE/iX file system perceives devices and its response to some of their characteristics. • How different device operation modes set the functionality of devices.
Describing Asynchronous Devices How MPE/iX Identifies Devices How MPE/iX Identifies Devices Asynchronous devices (terminals, printers, plotters, etc.) are located and communicated with in two ways: • Through the device’s logical device (ldev) number. • Through the physical path from the HP 3000 to the asynchronous device. Logical Device Numbers The ldev number is a value that the MPE/iX operating system uses to recognize attached devices.
Describing Asynchronous Devices How MPE/iX Identifies Devices Nailed Devices A nailed device is permanently assigned an ldev number through the NMMGR configuration of the HP 3000 computer. Any time a connection exists between a computer and one of its nailed devices, the same ldev number will belong to that device. Only nailed devices can be accessed programmatically. All printers must be nailed, as must any device that will be accessed programmatically.
Describing Asynchronous Devices How MPE/iX Identifies Devices Terminal users should know the physical device address for their terminal. If a terminal is having problems, the physical device address is needed to troubleshoot the terminal. The physical device address consists of identifiers for the DTC, the interface card, and the port to which the device is connected. Refer to “Device Physical Path” later in this chapter for more information. Plotters Sometimes plotters are connected to a DTC.
Describing Asynchronous Devices How Devices Are Owned and Why How Devices Are Owned and Why Devices (terminals, printers, plotters, etc.) are subject to ownership. If a device is owned by a process, then use of the device by other processes is restricted. For instance, when a session owns a terminal, only the process which initiated the session or its child process, can access the terminal. To determine which process owns a device, use the MPE/iX SHOWDEV command.
Describing Asynchronous Devices How the File System Manages Information How the File System Manages Information The file system is the part of the MPE/iX operating system that manages information being stored or transferred. It handles various input/output operations, such as passing information to and from user processes. All input and output operations are done through files. Files can be kept in any storage medium and accessed by any input/output peripheral device.
Describing Asynchronous Devices How Operation Modes Set Functionality How Operation Modes Set Functionality Six device operation modes can be used. Each has different capabilities and is intended for a specific purpose. The six are as follows: • System console • Session-accepting devices • Programmatic devices • Spooled devices • Slaved devices • Uninterruptible Power Supply (UPS) devices on the DTC.
Describing Asynchronous Devices How Operation Modes Set Functionality Block mode applications do not prevent the system console from printing received messages. Such messages can cause data on block mode screens to be overwritten or lost. Because of this, block mode applications should not be run on the console. Some console functionality can be given to the logical console.
Describing Asynchronous Devices How Operation Modes Set Functionality The first serial port provides a connection to the local console. The port is always fixed as LDEV 20. For backwards compatibility with the CIO console, speed and parity on the console cannot be changed. The speed is set at 9600 baud and the parity is set at none. The second serial port is capable of connecting to the console port path and connecting directly to the system.
Describing Asynchronous Devices How Operation Modes Set Functionality • Place the terminal under partial control of a program running on the computer. • Communicate with other terminal users and with the system operator. • Transfer data and control information between the computer and a slaved device connected to the terminal. • Change the line speed of the terminal. • Terminate the session.
Describing Asynchronous Devices How Operation Modes Set Functionality Slaved Devices If two devices share the same port in the DTC (one device is connected to the port and the other device is connected by an additional cable to the first device), only one device is recognized by the DTS software. The device that is recognized is referred to as the master device, while the other device is called a slave device. The master might or might not be the device that is physically connected to the port.
Describing Asynchronous Devices How Connections Set Characteristics How Connections Set Characteristics Asynchronous devices can be connected to the DTC in the following ways: • Directly connected to the DTC. • Remotely connected through a modem, a mux, a switch, a PBX, a PAD, or Telnet/iX. Direct Connections A direct connection is one in which a device’s data communications cable is plugged into a port without being connected to any other communications equipment.
Describing Asynchronous Devices How Connections Set Characteristics Only full-duplex asynchronous modems are supported for use with HP 3000 Series 900 computers. Twenty-five pin RS-232-C cables must be used on each end of a modem connection because, in addition to send, receive, and ground signals, control signals are also required to control the modems. Both terminals and serial printers are supported over modems.
Describing Asynchronous Devices How to Access Multisessions How to Access Multisessions Multisession is the ability to have a device on a DTC simultaneously associated with multiple sessions, jobs, or processes on one or more hosts. Each port can support up to 5 connections and connections can only be active one at a time; the other connections are in a “hold” state.
Describing Asynchronous Devices How to Use Duplex Printing How to Use Duplex Printing Duplex printing is the ability to print on both the front and back sides of the printer paper. The Laserjet 3D and the Laserjet 3SI are the two PCL (Printer Control Language) laser printers that support duplex printing. These two printers also support simplex (one-sided) printing. To use duplex printing on these printers, duplex printing must be configured and enabled.
Describing Asynchronous Devices How to Use Duplex Printing Figure 9-1 Duplex Mode Page Binding In addition to the escape sequences mentioned above, the [RESET] escape sequence ([ESC]) will also disable duplex mode and return the printer to simplex mode. Therefore, the duplex mode escape sequences should be entered after the [RESET] escape sequence in an initialization string.
Describing Asynchronous Devices How to Control the Flow of Data How to Control the Flow of Data Flow control is how the transfer of data between the computer and the asynchronous device is regulated. Flow control protects the computer and the device from data overruns. A data overrun occurs when the sender of data transmits the data faster than the receiver can accept it. Because the receiver cannot accept all of the data being sent, it is said to be overrun with data. Therefore, some data may be lost.
Describing Asynchronous Devices How to Control the Flow of Data • The terminal user presses [CTRL]-S. (Pressing [Stop] on HP239x terminals also sends the XOFF character to the computer. Note that this key is a toggle switch; the second time it is pressed, it sends an XON character to the computer, the third time, an XOFF character, and so forth.) After a terminal sends an XOFF character, the DTC waits indefinitely for an XON character.
Describing Asynchronous Devices How to Control the Flow of Data The Read Trigger Character The read trigger character tells an asynchronous device when it can send data to the computer. It prevents a device from sending data before the computer is ready to receive it. Data sent before the read trigger character is received is not accepted unless typeahead is enabled. If typeahead is enabled, data can be entered at any time and the read trigger character is not necessarily sent to the terminal.
Describing Asynchronous Devices How to Control Terminals How to Control Terminals DTS helps control the operation of terminals. It automatically handles the input and output of data to the terminal as explained earlier in this chapter under “How to Control the Flow of Data.” Alternative methods for controlling terminals are as follows: • Echoing characters to the terminal screen as they are typed at the keyboard. • Allowing special characters to be processed as intended.
Describing Asynchronous Devices How to Control Terminals Local Echo When terminals are installed, local echo is turned off. If local echo is turned on, the terminal will echo each character to the screen as it is typed. Local echo is used with half-duplex communications lines and some statistical multiplexers. Note that block mode applications usually turn local echo on because input characters are sent to the DTC in a block of data, instead of one character at a time.
Describing Asynchronous Devices How to Control Terminals Backspace When a backspace character is entered, the DTC deletes the previous character from the input data and echoes the backspace character to the terminal (provided echo is enabled). When the echoed backspace character is received, the cursor on the screen moves back one character and is positioned at the character that was deleted. Use [Backspace] or [CTRL]-H to backspace.
Describing Asynchronous Devices How to Control Terminals Up to 16 AEOR’s are available but only through the use of FDEVICECONTROL 192, 66. System Console Attention Character When [CTRL]-A is entered on the system console, it signals a [CTRL]-A console command. The computer sends the system console a carriage return and line feed along with an equals sign prompt (=), signaling that it is ready for the command. [CTRL]-A commands are allowed only on the system console.
Describing Asynchronous Devices How to Control Terminals Subsystem Break Subsystem break stops a program-local or subsystem-local command and enables the user to enter a different command. The default subsystem break character in standard editing mode is [CTRL]-Y. Subsystem break is not enabled by default. It must be enabled programmatically through the FCONTROL 17 intrinsic. A subsystem break character can also be defined when entering transparent editing through the FCONTROL 41 intrinsic.
Describing Asynchronous Devices How to Control Terminals Hewlett-Packard asynchronous devices and the ASC software use two other parity settings as well. These are called ones and zeros. With ones parity, the parity bit of each character is set to one; with zeros parity, the parity bit is set to zero. If the eighth bit is involved in a transmission error, it is detected because the bit is not what was expected. It is possible to not use parity at all. This is called none parity or 8-bit pass-through.
Describing Asynchronous Devices How to Control Terminals Block Mode When a terminal operates in block mode, characters are held in the terminal's memory (buffer) as they are typed. Characters are not transmitted to the DTC until a specific action is taken. Pressing [Enter] at the end of a block of data will normally send it to the DTC. An application program can use an alternate method to end a block mode read.
Describing Asynchronous Devices How to Control Terminals Terminating Reads Reads can be programmatically terminated in one of several ways: • An EOR or AEOR character is sent from the terminal. • The input byte count is reached. • The read limit timer expires. • The block mode read timer expires. • The system break character (if it is enabled) is sent from the terminal. • The subsystem break character is sent from the terminal. • The [CTRL]-A character is sent from the system console.
Describing Asynchronous Devices How to Control Printers How to Control Printers Controlling printers is similar to controlling terminals, except for two differences: • Printers have no need for control mechanisms (such as echo, read trigger, special characters, or modes of input) related to user input. Note: printers which support status checking require a read trigger.
Describing Asynchronous Devices How to Control Printers Status Request Printers using printer type files 21, 22, or 26 have a data protection mechanism that prevents the DTC from sending data to a printer when it is unable to print it. This mechanism is called status request or status checking. Printers respond to the request and return information on their status. A status request is sent after each file has printed.
Describing Asynchronous Devices How to Control Printers 200 Chapter 9
Using NMMGR in Maintenance Mode A Using NMMGR in Maintenance Mode This appendix tells you how to use NMMGR’s maintenance mode interface to manage network directory and configuration files. It allows you to also generate job streams to update remote network directory and configuration files. It includes the following: • A description of how to enter NMMGR maintenance mode from the screen mode interface or from a batch job.
Using NMMGR in Maintenance Mode Using Maintenance Mode Using Maintenance Mode NMMGR’s maintenance mode is a character mode interface used to manage both network directory and configuration files. It can be used interactively, from within the screen mode interface, or as a set of commands entered via a batch job. Maintenance mode can generate a job stream to sequentially update directories on a list of NS nodes.
Using NMMGR in Maintenance Mode Using Maintenance Mode Running Maintenance Mode from a Batch Job You can also access maintenance mode directly from a batch job by running NMMGR within a job stream or by running NMMGR with a file equation for the formal designator NMMGRCMD set to a command file. An example of such an equation is: :FILE NMMGRCMD=CMDFILE Command input is echoed to $STDLIST if you are running NMMGR from within a job stream or when the input is read from a command file.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Maintenance Mode Commands Table A-1 lists the NMMGR maintenance mode commands, their syntax, and the actions they perform. NOTE Subsystem break ([CTRL]Y) may be used to interrupt the operation of the COPYCONF, DELETENODE, HELP, LISTDIR, MAKESTREAM and MERGEDIR commands. The EXPANDDIR command cannot be interrupted.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Command Syntax Action COMPRESSCONF CARDCONF cardno Compresses or expands the current configuration file. CONTINUE CONTINUE [ON or OFF] Prevents NMMGR from terminating in a job because of a maintenance mode error. COPYCONF COPYCONF srcpath[:srcfile][,[destpath][:destfle]][;KEEP][;NOVERS] Copies a configuration subtree Deletes a subtree from the current configuration file.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Command Syntax Action HELP HELP [keyword] Calls up the help function. LISTDIR LISTDIR [nodename] Lists the contents of a network directory. LISTLDEV LISTLDEV {dtcname} {dtc-nodename} {station-address} [filename] Lists LDEVS for a DTC card in a format compatible with ADDLDEV.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Command Syntax Action PASSWORD PASSWORD [password] Sets the password. Validates the NETXPORT subsystem configuration. Changes the password to allow write access on the OPEN screen. PATHCONF PATHCONF[=]path Sets the current path in the current configuration file. PURGECONF PURGECONF [pathname] Deletes the subtrees of records from the configuration file.
Using NMMGR in Maintenance Mode Maintenance Mode Commands Command Syntax Action VALIDATECONF VALIDATECONF subsystem Validates subsystem configuration. VERSIONCONF VERSIONCONF version Checks whether the specified version number matches NMMGR's current version number. WRITECONF WRITECONF fieldname, data Writes data to individual fields of the current path in the configuration file.
Using NMMGR in Maintenance Mode SUMMARYCONF SUMMARYCONF Prints a summary report for one or more communications subsystems. Syntax SUMMARYCONF subsystem[, subsystem[, ...]] Parameters subsystem Description SUMMARYCONF displays a summary report for a particular subsystem. This command is identical to the Print Summary function in the NMMGR Output Configuration screen. The name of the subsystem(s) for which the report will be generated.
Using NMMGR in Maintenance Mode SUMMARYCONF DTS Displays the DTS subsystem configuration parameters. E[XIT] Leaves DTS Summary and returns you to the maintenance mode prompt. HELP Displays the available DTS summary options. LDEV [ldev[/ldev]] LINK Displays the configuration for all ldevs (logical devices), a single ldev, or a range of ldevs. Displays the link configuration for the DTS.
Migrating From Previous Releases B Migrating From Previous Releases This appendix describes the steps for migrating network configuration files to the current MPE/iX release from previous MPE/iX or MPE V releases. A utility called NMMGRVER.PUB.SYS is provided to automatically convert your old network configuration file to the current release format. NOTE Customers who do not have an existing network configuration file, NMCONFIG.PUB.SYS, do not need to run NMMGRVER.
Migrating From Previous Releases Running NMMGRVER Running NMMGRVER To run NMMGRVER, logon as MANAGER.SYS in the PUB group and run the utility by entering NMMGRVER after the MPE/iX prompt. NMMGRVER will prompt you for the configuration file name. Enter NMCONFIG, and Y to the confirmation prompt. The steps to run NMMGRVER are shown here: : HELLO MANAGER.SYS,PUB : NMMGRVER NM Configuration File Conversion Utility 32098-20016 B.04.07 (C) Hewlett-Packard Co.
Migrating From Previous Releases Running NMMGRVER NOTE After converting your network configuration file with NMMGRVER, you must validate and cross-validate NMCONFIG.PUB.SYS inside NMMGR and reboot you HP 3000 system. Refer to Chapter 5, “Configuring Serial Devices (for Host-Based Management),” for details on these steps.
Migrating From Previous Releases Running NMMGRVER 214 Appendix B
DTC User Interface C DTC User Interface This appendix explains how to use the DTC user interface. Only terminals which are allowed terminal switching are connected to the DTC user interface.
DTC User Interface Command Line Syntax Command Line Syntax The following conventions are used for commands which must be entered at the DTC user interface. [optional] Text in square brackets is optional and need not be typed. For example, in the c[onnect] command, you can type connect or just c. Text in chevrons represents a variable which must be entered, for example, the name of a system. You do not type the chevrons.
DTC User Interface DTC User Interface Commands DTC User Interface Commands The following commands are available at the DTC user interface. Each command can be abbreviated. For example, to establish a connection, you can enter either C or CONNECT. The commands are not case-sensitive, so either c or C can be used. Connect Connect opens a connection to a system.
DTC User Interface DTC User Interface Commands 218 Appendix C
Error Messages D Error Messages This appendix contains validation and Datacommunication Configurator (DCC) error messages. Validation errors indicate problems with the network management configuration file. They are detected during network management configuration file validation. DCC errors indicate problems with the link or the DTS manager. They are detected when the host is rebooted.
Error Messages Validation Error Messages Validation Error Messages A numerical list of validation error messages and actions for each follows. Path: NMMGRpath — A read error encountered while reading the data record (bad file). (DTSERR=3) (DTSERR 3) Cause: Either a hardware problem occurred or the data record is too long. Action: Try to print the network management configuration file. Rebuild the file from a copy of the sample file NMSAMP1.PUB.SYS.
Error Messages Validation Error Messages Path: NMMGRpath — LINK.linkname is not defined. (DTSERR=8) (DTSERR 8) Cause: The linkname specified on the DTS Configuration screen is not defined; therefore, the link data record was not created. Action: Verify the linkname on the Host Configuration screen. If the link data record does not exist, update the DTS Configuration screen. Path: NMMGRpath — DTS.PROFPC.profilename is not defined.
Error Messages Validation Error Messages Path: NMMGRpath — Too many LDEVs are being used (must be <=4649). (DTSERR=15) (DTSERR 15) Cause: Too many logical device (ldev) numbers are being used. Action: Review the screens that use ldevs and delete some ldev numbers. The validation procedure allows a total of 4649 ldevs. Path: NMMGRpath — Defined LINK.linkname is not being used. (DTSWARN=17) (DTSWARN 17) Cause: The defined linkname is not used by DTS or the network interface.
Error Messages Validation Error Messages Path: NMMGRpath — Too many classes are being used (max. number allowed = 1000). (DTSERR=22) (DTSERR 22) Cause: The total number of classes exceeds the maximum allowed number. Action: Delete class names so that no more than 1000 different class names are associated with asynchronous devices. Path: NMMGRpath — Too many profiles are being used (max. number allowed = 1024).
Error Messages Validation Error Messages Path: NMMGRpath — Must supply a Physical Path. (DTSERR=32) (DTSERR 32) Cause: A physical path was not specified in the Physical Path of LANIC field. Action: Go to the DTS Configuration screen and enter the appropriate physical path. Path: NMMGRpath — Duplicate profile class name profilename used. (DTSWARN=34) (DTSWARN 34) Cause: The same class name is used in several terminal profiles or the same class name is used in several printer profiles.
Error Messages Validation Error Messages Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD012.PAD2. (DTSERR=40) (DTSERR 40) Cause: A PAD name is used more than once. Action: Remove all of the duplicate references to the PAD name. Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD3. (DTSERR=41) (DTSERR 41) Cause: A PAD name is used more than once. Action: Remove all of the duplicate references to the PAD name.
Error Messages Validation Error Messages Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD4. (DTSERR=48) (DTSERR 48) Cause: The same logical device (ldev) number is used more than once. Action: Remove the duplicate ldev number. Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTCPC.SELECT.DTCname.CARD345.PAD5. (DTSERR=49) (DTSERR 49) Cause: The same logical device (ldev) number is used more than once.
Error Messages Validation Error Messages Path: NMMGRpath — Profile profilename specified for non-nailed PAD terminals is of PRINTER or PADPRINT type. (DTSERR=57) (DTSERR 57) Cause: A printer or PAD printer profile is specified where only a terminal or pad terminal profile is allowed. Action: Change the printer profile to be a terminal profile. Path: NMMGRpath — The profile for LDEV #nnn, profilename, is of PADTERM or PADPRINT type.
Error Messages Validation Error Messages Path: NMMGRpath — PAD device name for LDEV #nnn is being used at DTS.DTC.SELECT.DTCname.CARD345.PAD5. (DTSERR=64) (DTSERR 64) Cause: The same PAD device name is used more than once in the configuration. Action: Remove any duplicate references to the PAD device name. Path: NMMGRpath — The same LDEV #nnn is being used at DTS.DTC.SELECT.DTCname.CARD012.PAD0. (DTSERR=65) (DTSERR 65) Cause: The logical device (ldev) number is used more than once in the configuration.
Error Messages Validation Error Messages Path: NMMGRpath — Modem behavior DCE high for LDEV #nnn, defined in Profile profilename, is not supported on DTC16 and DTC48. (DTSERR=71) (DTSERR 71) Cause: DCE high modem behavior is not supported for devices on a DTC 16 or DTC 48. DCE high is being specified for LDEV #nnn, which is on a DTC 16 or DTC 48.
Error Messages Validation Error Messages Internal error. Failed to get memory. (DTSERR=77) (DTSERR 77) Cause: The operating system was unable to allocate the memory needed to store data used during validation. Action: Build a new file from the sample file NMSAMP1.PUB.SYS. Try to validate the file. If the same error message appears when verifying the new file, contact your Hewlett-Packard support representative. Path: NMMGRpath — Back-to-Back, currently configured on LDEV #nnn, must use LDEV # -1.
Error Messages Validation Error Messages Path: NMMGRpath — Unknown cardtype specified for card c. (DTSERR=83) (DTSERR 83) Cause: The configuration for the DTC specified in NMMGRpath has been corrupted. Action: Delete the DTC specified in NMMGRpath and re-enter the data for this DTC. Path: NMMGRpath — Cardtype for card c does not match DTC card configuration. (DTSERR=84) (DTSERR 84) Cause: The configuration for the DTC specified in NMMGRpath has been corrupted.
Error Messages Validation Error Messages Path: NMMGRpath — Too few non-nailed ldevs available above TIO start ldev. (DTSERR=89) (DTSERR 89) Cause: There are not enough ldevs available above the TIO start ldev number to configure the number of ldev specified. Action: Lower the number of TIO non-nailed ldevs or delete all TIO non-nailed ldevs and specify a lower starting ldev number. Then add the desired number of ldevs. Path: NMMGRpath — Too few non-nailed ldevs available above PAD start ldev.
Error Messages DCC Error Messages DCC Error Messages As system start-up nears completion, the Datacomm Configurator (DCC) creates the LINK and DTS managers. If the procedure is successful, the following message will be displayed on the console: DCC STARTUP OK! If the procedure is not successful, the message above is replaced by one or more error messages.
Error Messages DCC Error Messages Action: Validate the NMCONFIG.PUB.SYS file and restart DTS. If the error persists, replace the file, validate it, and restart DTS. DCC ERROR P-L, configuration record data was invalid. NM Path: NMMGRpath (DCCERR=5) (DCCERR 5) Cause: Data in the NMCONFIG.PUB.SYS file was not validated or the data is corrupt. Action: Validate the NMCONFIG.PUB.SYS file and restart DTS. DCC ERROR P-L, (HLIO status SSSSSSSS, ldev LLL).
Error Messages DCC Error Messages DCC ERROR P-L, link name specified for the DTS does not exist. (DCCERR=13) (DCCERR 13) Cause: The link name configured in NMMGR on the DTS Configuration screen does not exist. Action: Go to the DTS Configuration screen and enter the link name, then restart DTS. DCC ERROR P-L, link name specified for the DTS is not available (link status SSSSSSSS).
Error Messages DCC Error Messages DCC WARNING P-L, Configuration file close error SSSSSSSS. (DCCWARN=21) (DCCERR 21) Cause: A problem occurred while closing the NMCONFIG.PUB.SYS file or the NMCONFIX.PUB.SYS file. Action: Check that the files exist, and that adequate disk space is available for them. If the files exist and the disk space is large enough, check for file system or hardware problems. NLIO status SSSSSSSS, ldev LLL) (DCCERR=22) (DCCERR 22) Cause: A problem exists in the NLIO services.
Error Messages DCC Error Messages Action: For DTC 72MX, the valid range for card number is 0 to 3. For DTC 48, the valid range for card number is 0 to 5. For DTC 16, you may use card 0 and 1 for connector cards and card 2 for X.25 card. DCC ERROR P-L, Invalid DTC type specified, (DCC status SSSSSSSS. (DCCERR=28) (DCCERR 28) Cause: The NMCONFIG.PUB.SYS file may be corrupt.
Error Messages DCC Error Messages DCC WARNING P-L, Ldev not added to class. (HLIO status SSSSSSSS, ldev LLL). (DCCWARN=33) (DCCWARN 33) Cause: A class contains more than 255 devices, a conflict in class names exists, or NMCONFIG.PUB.SYS was not cross-validated with files created with SYSGEN. Action: The ldev is still usable but will not be in the class. Validate the NMCONFIG.PUB.SYS file and run SYSGEN to verify conflict. DCC ERROR P-L, Delete Ldev from class failure. (HLIO status SSSSSSSS, ldev LLL).
Error Messages DCC Error Messages DCC ERROR P-L, nn dev(s) are owned, shutdown not done. (DCCERR=40) (DCCERR 40) Cause: While attempting a DTS shutdown, nn ldevs were found to be still logged on or spooled. The shutdown operation was aborted. Action: Logoff or stop the spooler on the devices that are still in use. Retry the DTS shutdown. DCC ERROR P-L, LLIO error (Status: SSSSSSSS, path: NMMGRpath) (DCCERR=41) (DCCERR 41) Cause: A problem exists with the low-level I/O services.
Error Messages DCC Error Messages Action: Make sure the DTC is powered on and the correct LAN address is specified. DCC WARNING P-L, (LLIO status SSSSSSSS) (DCCWARN=48) (DCCWARN 48) Cause: An internal problem has occurred with low-level I/O. Action: This is a warning. If it persists contact your Hewlett-Packard support representative. DCC WARNING P-L, Ldev LLL is unusable until next DTS restart.
Error Messages DCC Error Messages DCC WARNING P-L, (Startup) can not open NMCONFIX, status SSSSSSSS. (DCCWARN=103) (DCCWARN 103) Cause: The NMCONFIX.PUB.SYS file exists but it cannot be opened. Action: Check that the file is not locked. If the file is not locked, check for file system or hardware problems. DCC WARNING P-L, (Startup) can not create NMCONFIX, status SSSSSSSS. (DCCWARN=104) (DCCWARN 104) Cause: A disk space problem, a file system problem, or a hardware problem exists.
Error Messages DCC Error Messages 242 Appendix D
Glossary A access port A special interface card in the system cabinet through which the MPE/iX system console is connected. ADCP Avesta Device Control Protocol. An HP proprietary protocol which provides device control features. ADCP is optimized for communications between a DTC and MPE/iX systems address A numerical identifier defined and used by a particular protocol and associated software to distinguish one node from another. address key See X.25 address key.
Glossary AFCP, allowing connections from terminals on ARPA systems to HP 3000s. ASCII American National Standard Code for Information Interchange. A character set using 7-bit code used for information interchange among data processing and data communications systems. The American implementation of International Alphabet No. 5. asynchronous A device’s mode of operation in which a sequence of operations are executed irrespective of time coincidence with any event.
Glossary signal events per second. When one bit represents each signal change, baud is the same as “bits per second.” byte A sequence of eight consecutive bits operated on as a unit. C binary mode A data-transfer scheme in which no special character processing is performed. All characters are considered to be data and are passed through with no control actions being taken. bit Binary digit. A unit of information that designates one of two possible states, which are represented by either 1 or 0.
Glossary standards by making recommendations. The emphasis is on “recommendations”; no carrier is required to adhere to a CCITT recommendation, although most do so in their own interests. CIB The channel input/output bus in the backplane of an HP 3000. circuit-switching network A type of data communications network wherein a physical and exclusive link is maintained between two communicating devices for the call duration. An all-digital, circuit- switching network is often referred to as an X.21 network.
Glossary configuration file The configuration file contains the information that the network needs in order to operate. This file also contains information necessary for link- level and NetIPC logging. The only file name that the system recognizes is NMCONFIG.PUB.SYS control-X echo Three exclamation marks (!!!) output to the terminal screen when the cancel character (normally [CTRL]-X) is entered.
Glossary DCE Data circuit-terminating equipment. The interfacing equipment required in order to interface to data terminal equipment (DTE) and its transmission circuit. Synonyms: data communications equipment, dataset. A modem is an example of a DCE.
Glossary device name See PAD name. Dial ID protocol A proprietary Hewlett- Packard protocol that provides security checking and address exchange for dial links. dial link A connection made through public telephone lines. direct-connect device An asynchronous device that is connected directly to a DTC through an RS-232-C or RS-422 cable, with no intervening communications equipment. Also referred to as a “local connection.
Glossary asynchronous (direct and modem) LAN connections to HP 3000 systems. DTC 16MX HP J2063A product. A DTC terminal server for HP 3000 and Telnet systems. It allows up to 16 asynchronous (direct and modem) LAN connections for the HP 3000 environment and for computer systems running ARPA, such as HP 9000s and third party systems. When managed by the HP 3000, the DTC 16MX is configured and functions exactly like a DTC 16iX.
Glossary having up to 16 characters. The name begins with either a letter or a digit. DTC station address (802.3 address) A 12-digit hexadecimal number used to identify the DTC as a node belonging to the network configuration. Also called the LAN address or node address. DTC switching A facility enabling terminal users to select any host system that they want to connect to. DTC switching is available only when the OpenView DTC Manager is used for network management. DTC/X.
Glossary DTS shutdown The shutdown of the DTS subsystem, including the release of all TIO-related resources, using the DTCCNTRL command file. escape sequence A sequence of characters beginning with the escape character and followed by one or more other characters, used to convey control directives to printers, plotters, or terminals. duplex A transmission method that allows two-way communication. If both ends of the transmission link can transmit simultaneously, it is called full duplex.
Glossary fast select An optional packet-switching network facility by which user data can be transmitted as part of the control packets that establish and clear a virtual connection. FCS Frame Check Sequence. A sequence of bits generated by X.25 at Level 2 that forms part of the frame and guarantees the integrity of its frame’s contents. The FCS is also used by the IEEE 802.3 protocol to check the validity of frames.
Glossary gateway half A node that works in conjunction with another node on another network to form an internetwork. The only protocol used by gateway halves is the NS Point-to-Point 3000/iX Link. See also full gateway. gateway-half link A link between the two nodes of a gateway-half pair. Each of the two nodes of a gateway-half pair has a configured link (hardware interface card) that is used for the gateway half network interface.
Glossary HP block mode A block mode transmission method employed by HP computers where the system controls the block mode handshake. When HP block mode is used, the user program need not concern itself with data transfer protocol. HP PPN Hewlett-Packard Private Packet Network. Hewlett-Packard’s own packetswitching X.25 network, which gives users full control over the administration and security of their data communication.
Glossary Internet Protocol A protocol used to provide routing between different local networks in an internetwork, as well as among nodes in the same local network. The Internet Protocol corresponds to Layer 3, the Network Layer, of the OSI model. See also IP address. internet routing Internet routing involves all the processes required to route a packet from a node on one network to a destination node on another network. internetwork Two or more networks joined by gateways.
Glossary LANIC physical path The physical location (slot number) of the LANIC within the SPU. LANIC Self-Test A ROM-based program on a LANIC card that tests and reports the status of the LANIC hardware. LAP Link Access Protocol. The data link protocol specified by older versions (prior to 1980) of X.25 at Level 2 but still permitted and therefore usable. All new implementations of X.25 must use LAP-B, and all old implementations must migrate to LAP-B at a future date. LAP-B Link Access Protocol – Balanced.
Glossary events are to be logged. Class 1 (catastrophic event) is always logged. logical device number (ldev) A value by which MPE/iX recognizes a specific device. All DTC devices that are configured as nailed devices through the NMMGR configuration have ldev numbers permanently assigned. The DTC devices can then be accessed programmatically through use of their ldev number.
Glossary M bit More data bit. Setting this bit in a DATA packet indicates that at least one more DATA packet is required to complete a message of contiguous data. modulation The process in which certain characteristics of a carrier signal are altered in accordance with the changes of an information-bearing signal. MDP Modem Distribution Panel.
Glossary NetIPC Network Interprocess Communication. Software that enables programs to access network transport protocols. network A group of computers connected so that they can exchange information and share resources. network address This can be either 1) the network portion of an IP address as opposed to the node portion, or 2) when referring to X.25 networks, it is a node’s X.25 address. network boundary The logical division between networks in an internetwork.
Glossary NMCONFIG.PUB.SYS The file that contains all of the network configuration data for the HP 3000 Series 900 computer on which it resides. It includes information about the DTCs that can access the system as well as information about any Network Service (NS) products running on the system. This is the only file name allowed at run-time. NMDUMP A utility used to format log and trace files.
Glossary an ldev number at configuration time. When the user at such a device logs on to an MPE/iX system, an ldev is assigned from a pool of ldevs set aside for this purpose at configuration time. The association between a non-nailed device and this assigned ldev exists only for the duration of the session. One advantage of the use of non-nailed device connections is that configuration is simplified, since it is not required that each non-nailed device be individually configured.
Glossary by the DTC Manager, including monitoring and diagnostic functions. OpenView Windows he set of three programs: OV Admin, OV Draw and OV Run, running on the OpenView workstation under MS Windows, that acts as the platform for all OpenView applications, such as DTC Manager. OpenView Windows Workstation The personal computer that provides software downloads to enable operation of the Datacommunications and Terminal Controller (DTC).
Glossary partner gateway half When gateway halves are used, two gateway halves are required in order to provide communication between two networks. Each is the partner of the other. path name When configuring with NMMGR, you can type a string in the COMMAND: field on a screen to branch to another screen. Each screen has a unique path name that corresponds to its location in the hierarchy of configuration screens presented by NMMGR. PDN Public Data Network.
Glossary probe proxy server A node on an IEEE 802.3 network that possesses a network directory. A probe proxy server can provide a node with information about other nodes on the same or other networks of an internetwork. profile A method of grouping device connection specifications and characteristics so that the set of characteristics can be easily associated with groups of like devices. See also printer profile, terminal profile. program captive device See programmatic device.
Glossary reachable network A network that can be accessed (with additional internet hops possibly required) by a particular gateway. remote connect device An asynchronous device that is indirectly connected to a DTC through a modem and telephone hook-up or through a PAD. remote node Any network node that is physically separate from the node you are currently using or referring to.
Glossary are among the devices that communicate serially with MPE/iX computers. its master, by a cable. The actions of the slaved device are controlled by the master device. serial transmission A method of transferring data in which characters are transmitted one bit at a time and received one bit at a time in the order of transmission. This transmission scheme is employed by devices connected to the MPE/iX systems via the DTC. SNMP Simple Network Management Protocol.
Glossary stop bit A data bit used to signal the end of a character being transmitted in an asynchronous communication mode. SYSGEN The software program that allows you to configure the operating system on HP 3000 Series 900 computers. store-and-forward A technique in which messages are passed from one node to another in a network to reach their destination. Point-to-point networks use the store-and-forward technique to transmit messages.
Glossary a terminal by name. It can be shared by several terminals (pool port). terminal profile A set of configuration characteristics that can be associated with one or more terminals through the NMMGR configuration. Terminal profile specifications include the terminal type, line speed, device class assignment, and other values relevant to terminals connected through a DTC.
Glossary transport, network Software that corresponds to layers 3 and 4 of the OSI network architecture model. It sends data out over the communications link, receives incoming data, and routes incoming or outgoing data to the appropriate destination node. TS8 See HP TS8. TTUTIL Also known as the Workstation Configurator. A program, TTUTIL.PUB.SYS, on the HP 3000 that is used to create and modify terminal and printer type files. Tymnet A proprietary public data network in the USA.
Glossary V-Series (V.##) CCITT A set of CCITT recommendations related to data communication over a voice-grade telephone network. X.25 address The X.25 address provided by the network administration if you are connected to a public data network (PDN). VT See Virtual Terminal. W WAN Wide Area Network. A data communications network of unlimited size, used for connecting localities, cities, and countries. Workstation Configurator A utility available on MPE/iX systems, TTUTIL.PUB.
Glossary a remote Packet Assembly/ Disassembly (PAD) facility over a packet-switching network. XON/XOFF protocol The flow control used by MPE/iX systems to protect against data overruns. XON/XOFF protocol is controlled by the data recipient who sends an XOFF character (ASCII DC3) to the sender if it is unable to continue to receive data. The sender suspends transmission until it receives an XON character (ASCII DC1). X.Series (X.
Index Numerics 7-bit character sets, 194 8-bit pass-through none parity, 195 A ABORT command, 193 access port, 173, 177 additional EOR character AEOR, 192 Advanced Terminal Processor ATP, 29 AEOR, 192 AEOR character, 192, 197 AFCP timer, 161 alternate character set, 194 alternate EOR character AEOR character, 192 application printers, 116 ASC software, 20, 189, 192, 193, 195, 196, 198, 199 ASCII DC1 character, 188, 189 ASCII DC2 character, 189 ASCII DC3 character, 188 asynchronous character streams, 25 asy
Index DTE modem behavior, 122, 132 DTS, 21, 71, 91 DTS Host Configuration screen, 78, 97 DTS Profile Selection screen, 118 DTS restart, 55, 69, 90, 107 DTS shutdown, 55, 67, 90, 107 DTS software, 181 DTS validation, 87, 104 DTSDYNCONF command, 64 DTSLINK, 21, 97 duplex printing, 185 dynamic configuration, 55, 56, 79, 98 status, 66 E echo, 198 echoing characters, 190 enabling port, 147 end-of-record character EOR character, 192 enq/ack flow control, 148 entering maintenance mode from a batch job, 203 enteri
Index N nailed connections, 172, 173 nailed devices, 39, 91, 172 nailed ports, 101 native language character set, 112 native language device, 133 native language devices, 111 network directory file, 76, 95 network management, 22 network management configuration file NMCONFIG.PUB.SYS, 74 network planning, 32 NLIO device, 123, 133 NMCBACK.PUB.SYS, 76, 95 NMCONFIG.PUB.SYS, 61, 72, 73, 75, 87, 104 NMCONGIF.PUB.SYS, 87 NMGRXVAL.PUB.
Index Open Configuration/Directory File, 74, 95 PAD Printer Profile, 143 PAD Terminal Profile, 139 Printer Profile, 130, 138 Printer Switching Configuration, 135 SNMP Authorization Filter Configuration, 166 SNMP MIB Configuration, 167 SNMP Trap Destination Configuration, 169 Terminal Profile, 120, 129 Terminal Switching Configuration, 125 Tune DTC - Timer Selection, 161 serial devices, 173 serial port, 174 serial printers, 20, 117, 183 seriall printers, 183 session, 172, 175, 195 session-accepting, 177 ses
Index XON/XOFFprotocol, 187 Z zeros parity, 195 Index 277
