QIO Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the QIO subsystem on an HP NonStop™ S-series server and an HP Integrity NonStop™ NS-series server. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the QIO subsystem. Product Version QIO F40 QIO H01 Supported Release Version Updates (RVUs) This manual supports G06.17 and all subsequent G-series RVUs and H06.
Document History Part Number Product Version Published 424717-004 QIO F40 December 2004 424717-005 QIO F40 February 2005 QIO H01 424717-006 QIO F40 July 2005 QIO H01 424717-007 QIO F40 September 2006 QIO H01 424717-008 QIO F40 QIO H01 February 2011
Legal Notices Copyright 2011 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
QIO Configuration and Management Manual Glossary Index What’s New in This Manual v Manual Information v New and Changed Information Figures Tables v About This Manual vii Who Should Use This Manual vii How This Manual Is Organized vii Where to Get More Information vii NonStop S-Series Configuration and Management Manuals Notation Conventions xv Abbreviations xix 1.
Contents 2. Configuring the QIO Subsystem (continued) 2.
Contents 4. QIO Subsystem SCF Commands (continued) 4.
Contents Glossary Glossary Index Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 4-1.
What’s New in This Manual Manual Information QIO Configuration and Management Manual Abstract This manual describes how to configure, operate, and manage the QIO subsystem on an HP NonStop™ S-series server and an HP Integrity NonStop™ NS-series server. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the QIO subsystem. Product Version QIO F40 QIO H01 Supported Release Version Updates (RVUs) This manual supports G06.17 and all subsequent G-series RVUs and H06.
What’s New in This Manual Changes Made in Previous Versions Updated the figure with system space information on page 2-11. Added a note about system space information in the following sections: Setting the Size of QIO Memory section on page 2-14. How to Associate the Configuration File With QIO section on page 2-19. Changing an Existing Configuration File section on page 2-20. Reverting to an Original Configuration File section on page 2-21.
About This Manual This manual describes the architecture, configuration, management, and operation of the QIO subsystem on NonStop S-series servers and on Integrity NonStop NS-series servers. Who Should Use This Manual This manual is intended for experienced system managers and operators who need to configure and manage the QIO subsystem. How This Manual Is Organized Table i summarizes the contents of this manual. Table i.
About This Manual Where to Get More Information Table ii lists and describes all NonStop S-series server manuals. Table ii.
About This Manual Where to Get More Information NonStop S-Series Hardware Installation and FastPath Guide This guide is written for anyone qualified to install an NonStop S-series server. This guide describes how to install and start a NonStop S-series server for the first time.
About This Manual Where to Get More Information information for upgrading an enclosure from a 7000 server for use in a S7x000 server. The NonStop S-Series Service Provider Supplement is available only to service providers who have completed special training provided by HP. NonStop S-Series System Expansion and Reduction Guide This guide describes how to add enclosures to, and remove enclosures from, a NonStop S-series system online.
About This Manual Where to Get More Information Table iii lists and describes the NonStop S-series configuration and management manuals. . Table iii.
About This Manual Where to Get More Information DSM/SCM User’s Guide This guide introduces the Distributed Systems Management/Software Configuration Manager (DSM/SCM), and explains how to configure DSM/SCM and use it to manage and install software revisions on your NonStop S-series system. Kernel-Managed Swap Facility (KMSF) Manual This manual describes the installation, configuration, and management of the Kernel-Managed Swap Facility (KMSF).
About This Manual Where to Get More Information Table iv lists and describes Integrity NonStop NS-series server manuals. Table iv. Integrity NonStop NS-Series Server Manuals Category Purpose Title Reference Contains information about the manuals, the software releases, and the hardware that supports NS-series servers H0x.xx Release Version Update Compendium Describes how to prepare for changes to software or hardware configurations H0x.
About This Manual Where to Get More Information Introduction to Networking for HP Integrity NonStop NS-Series Servers This manual provides an overview of networking and data communications concepts, tasks, products, and manuals for Integrity NonStop NS-series servers.
About This Manual Notation Conventions Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
About This Manual General Syntax Notation { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
About This Manual Notation for Messages a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
About This Manual Notation for Management Programming Interfaces lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
About This Manual Change Bar Notation UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING.
About This Manual Abbreviations SCP. Subsystem Control Point SQL. Structured Query Language SWAN. ServerNet wide area network TACL. HP Tandem Advanced Command Language TAL. Transaction Application Language WAN.
1 Introduction to QIO This section describes the architecture and functions of the QIO subsystem.
Introduction to QIO Figure 1-1. High-Level View of the QIO Subsystem Client Process Client Process Client Process SCF/SCP QIO Subsystem QIO Library QIOMON Process Shared Memory Segment Driver/Interrupt Driver/Interrupt Handler Handler LAN 1 LAN 2 Driver/Interrupt Handler LAN 3 VST001.vsd The QIOMON process creates and manages the shared memory segment and presents a system-wide view of the shared memory subsystem.
Introduction to QIO Subsystem Architecture You can configure QIO to create its shared segment in a system data area known as Kseg2. This removes the QIO segment from the user data segment space allowing more space for the heap and flat segment memory to grow. You can configure QIO to create its memory segment space with a different starting base address. This can allow more room for the process heap to grow.
Introduction to QIO QIO Subsystem Requirements QIO Subsystem Requirements This subsection describes the NonStop S-series servers, Integrity NonStop NS-series servers, and LAN adapters supported by the QIO subsystem. Servers Supported The QIO subsystem is supported on all NonStop S-series servers and on Integrity NonStop NS-series servers, that are shipped with a generic preconfiguration of the QIO subsystem.
Introduction to QIO DSM/SCM DSM/SCM The Distributed Systems Management/Software Configuration Manager (DSM/SCM) is a system for the centralized planning, management, and installation of software on distributed NonStop S-series systems and Integrity NonStop NS-series systems. DSM/SCM performs the activities associated with installing and managing software revisions.
Introduction to QIO QIO SCF Subsystem QIO SCF Subsystem The QIO Subsystem Control Facility (SCF) subsystem provides the SCF commands used to configure and manage the various QIO subsystem objects. The MON and SEGMENT objects are at the highest point of the hierarchy, with all other objects subordinate to them. (The null object is not an actual object type but is used in commands that do not require specification of an object type.
Introduction to QIO SCF and the QIO Subsystem Each QUEUE object is associated with an APPL object. The QUEUE name is defined by the client process and must be unique within the segment. It is recommended that the name of the APPL that is creating the queue be used as the prefix for the QUEUE name. For example, $ZM02.#ZTC2.IN is the queue that belongs to the $ZTC2 client process under the $ZM02 QIOMON process.
Introduction to QIO Subsystem Functions Figure 1-2. SCF and the QIO Subsystem SCF SCP Client Process QIOMON QIO Subsystem QIO Library Driver/Interrupt Driver/Interrupt Handler Handler LAN1 LAN2 Driver/Interrupt Driver/Interrupt Driver/Interrupt Handler Handler Handler LAN3 LANn QIO Memory Segment VST002.vsd SCF is a software product designed to provide a common interactive management interface for a variety of data communications products, QIO being one of them.
Introduction to QIO Client Process Initialization For more information about configuring and starting the QIO subsystem, see Section 2, Configuring the QIO Subsystem. QIOMON is created as a generic process. On NonStop S-series servers and on Integrity NonStop NS-series servers, generic processes are created by the Kernel subsystem and are started automatically when a processor is reloaded.
Introduction to QIO Inbound Data Flow Figure 1-3. Queues Created by the Client Process Client Process Driver/Interrupt Handler Inbound Queue Outbound Queue VST007.vsd Inbound Data Flow Figure 1-4. Flow of Data From the LAN to a Client Process Client Process Driver/Interrupt Handler Message Message Inbound Queue Outbound Queue DIH Return Queue Inbound Data LAN VST004.
Introduction to QIO Outbound Data Flow Outbound Data Flow Figure 1-5. Flow of Data Sent to the LAN by a Client Process Client Process Message Driver/Interrupt Handler Inbound Queue Outbound Queue Outbound Data LAN VST005.vsd To send data, the client process retrieves a message descriptor from the shared memory segment. The data to be sent is placed in the message buffer and the message descriptor is put onto the outbound queue, invoking the driver to send the data to the LAN adapter.
Introduction to QIO Client Process Termination QIO Configuration and Management Manual—424717-008 1-12
2 Configuring the QIO Subsystem This section describes custom configuration of the QIO subsystem on a NonStop S-series server and on an Integrity NonStop NS-series server. Overview The default configuration of QIO is set to maximize QIO memory availability. However, the default configuration sacrifices memory space available to applications. Read this section to determine whether you should keep the default configuration or configure QIO differently.
Configuring the QIO Subsystem Understanding QIO Memory Configuration Understanding QIO Memory Configuration By default, QIO memory is stored in a flat memory space known as user-addressable data space. Note. On Integrity NonStop NS-series servers, HP recommends that you configure QIO to run in system data space unless your environment is using more than 256 MB of QIO shared memory space.
Configuring the QIO Subsystem Process Globals and Process Heap Space Figure 2-1. Default Configuration of User-Addressable Data Space Base Addresses 0800.0000 Process Heap and Process Globals 2000.0000 QIO Shared Memory Segment (default 512 MB) 4000.0000 4200.0000 QIO IOperm (32 MB) Flat Memory Space (User Addressable Data Space) Unassigned Flat Memory Space 4E00.0000 Main Stack and Flat Segment Memory Space Reserved for Programs 5000.0000 VST011.
Configuring the QIO Subsystem QIO Shared Flat Memory and QIO IOperm Segment The process globals space and the process heap space are cleared when the program exits. QIO Shared Flat Memory and QIO IOperm Segment The QIO memory segment within the user-addressable data space has a default size of 512 MB, which is also its maximum size. QIO memory is followed by 32 MB of IOperm memory, which is space in flat segment memory to provide an aliased memory space. The total QIO memory segment is 544 MB.
Configuring the QIO Subsystem Memory Management Memory Management QIO is configured to run in user-addressable data space, but if your environment is a NonStop S-series server and uses less than 128 MB of QIO shared memory or an Integrity NonStop NS-series server and uses less than 256 MB of QIO shared memory, HP recommends that you configure QIO to run in system data space (see Configuring QIO to Reside in System Data Space on page 2-9).
Configuring the QIO Subsystem Other Ways to Manage Memory Space Without Moving QIO Other Ways to Manage Memory Space Without Moving QIO QIO provides three methods of solving memory-conflict problems that do not involve running QIO in system data space: You can configure QIO to create its memory segment space with a different starting base address. This allows more room for the process heap to grow.
Configuring the QIO Subsystem Understanding the Configuration File This command results in a display similar to the following example: QIO Detailed Status SEGMENT \OSCAR.$ZM00 State.................. Segment State.......... Segment Type........... Segment Size........... MDs in Use............. Max MDs Used........... Last Fail Size......... Current Pool Size...... Max Pool Size.......... Current Pool Alloc..... Current Pool Frags.....
Configuring the QIO Subsystem Understanding the Configuration File Configuration File Attributes You can specify the following attributes in the configuration file: BaseAddress starting address where starting address is the base address where the segment is to start. The valid range of addresses is from 0x1000.00000 through 0x4e00000. CPU # where # (pound sign) specifies the number of the processor to be configured.
Configuring the QIO Subsystem Configuring QIO to Reside in System Data Space You can specify an attribute multiple times in the configuration file, but only the last attribute processed is applied. Blank lines are ignored. The configurations specified are not case-sensitive. Only one configuration parameter is allowed per line. If an invalid or undefined parameter is found in the configuration file, QIO will not start, and an EMS message is issued.
Configuring the QIO Subsystem Configuring QIO to Reside in System Data Space Figure 2-2. QIO Memory in Kseg2 Memory Space (NonStop S-Series Servers) Base Addresses 0800.0000 Process Heap and Process Globals Variable Address Flat Segment Memory Space Flat Memory (User Addressable Data Space) 5000.0000 8000.0000 Kseg0 Kseg1 Privileged space C000.0000 Kseg2 QIO Shared Memory Segment (default 128 MB, max 128 MB) VST016.
Configuring the QIO Subsystem Configuring QIO to Reside in System Data Space Figure 2-3. QIO Memory in Global Privileged Space (Integrity NonStop NS-Series Servers) Base Addresses 00000000.08000000 Process Heap and Process Globals Variable Address Flat Segment Memory Space Region 0 (User Addressable Data Space) 00000000.50000000 00000000.80000000 FFFFFFFF.80000000 QIO Shared Memory Segment (Default 256 MB Max 512 MB) Region 7 (Global Privileged Space) VST017.
Configuring the QIO Subsystem Setting an Alternate Base Address segment IDs to determine if QIO is running. They are selectable segments, and each is 8 bytes long. The QIO space segment (segment ID 2101/32 MB), which is created in flat memory to provide an aliased memory space, is not needed when QIO is configured to run in system data space. Requests for space from the IOperm segment are handled by the main QIO pool segment.
Configuring the QIO Subsystem Setting an Alternate Base Address Figure 2-4. QIO Shared Memory Segment Beginning at a Higher Base Address than the Default Base Addresses 0800.0000 Process Heap and Process Globals 2000.0000 (default) QIO segment starting address increased from default of 2000.0000 QIO Shared Memory Segment (Size reduced by specified starting address) 4000.0000 QIO IOperm 32 MB (No change in size) 4200.0000 Unassigned Flat Memory Space 4E00.0000 5000.
Configuring the QIO Subsystem Setting the Size of QIO Memory The last valid flat segment address is 0x4e000000-1. If the base address specified causes the end address of the QIO segment to exceed this boundary, the segment size is automatically reduced to fit. This does not take into account other flat segment requirements. To change the base address, specify the following attribute in the configuration file: BaseAddress starting address where the valid starting addresses are 0x10000000 to 0x4c000000.
Configuring the QIO Subsystem Setting the Size of QIO Memory Figure 2-5. QIO Shared Memory Segment Reduced From the Default of 512 MB Base Addresses 0800.0000 Process Heap and Process Globals 2000.0000 QIO Shared Memory Segment QIO IOperm 32 MB (No change in size) 4200.0000 (QIO default) QIO shared memory space reduced by a smaller specified segment size Unassigned Flat Memory Space Flat Segment Memory Space Reserved for Programs 8000.0000 VST012.vsd Some applications define their own flat segments.
Configuring the QIO Subsystem Configuring QIO in Individual Processors Configuring QIO in Individual Processors QIO allows you to configure each processor independently of the others. This lets you assign programs with different memory needs to individual processors that have been tailored to specific requirements. To configure QIO in individual processors, analyze your system for QIO clients and QIO usage and configure QIO in each processor based on those needs.
Configuring the QIO Subsystem Associating a New Configuration File When One Does not Already Exist Following is an example of an INFO process, detail display: NONSTOP KERNEL - Detailed Info PROCESS \OSCAR.$ZZKRN.#QIOMON *AutoRestart...............10 *BackupCPU.................Not Specified *CPU.......................ALL *DefaultVolume.............$SYSTEM.SYSTEM *ExtSwap...................Not Specified *Highpin...................ON *HomeTerminal..............$YMIOP.#CLCI *InFile....................$YMIOP.
Configuring the QIO Subsystem Associating a New Configuration File When One Does not Already Exist Task 5 Start an SCF session and enter the following command: -> ALTER process $zzkrn.#qiomon, infile $system.system.qioconf where infile filename specifies the name of the new configuration file you created. Task 6 Rename the QIOMON object file back to QIOMON such that the persistence manager can start it: -> RENAME qiomonx, qiomon Task 7 Reload all the processors.
Configuring the QIO Subsystem Changing an Existing Configuration File Note. For H06.22/J06.11 and all subsequent RVUs, the maximum QIO segment size in system space for Integrity NonStop NS-series is increased to 512 MB, while the default size remains 256 MB. Changing an Existing Configuration File To associate a new configuration file when one already exists, perform the following tasks: Task 1 Create a configuration file with the values you want QIO to have.
Configuring the QIO Subsystem Reverting to an Original Configuration File You can verify that the changes you made to the configuration file have taken effect in three ways: Check that the configuration file is open. Enter the command: -> INFO mon $zm00, detail and look at the display to verify the configuration file name. Config FileName........ \OSCAR.$SYSTEM.SYSTEM.QIOCONF Program FileName....... \OSCAR.$SYSTEM.SYSTEM.QIOMON Library FileName.......
Configuring the QIO Subsystem Falling Back to the Default Configuration Task 4 Reload the processor that you want to reconfigure and run the new QIO configuration file. Task 5 Verify your configuration changes. You can verify that the changes you made to the configuration file have taken effect in three ways: Check if the configuration file is open. Enter the command: -> INFO mon $zm00, detail and look at the display to verify the configuration file name. Config FileName........ \OSCAR.$SYSTEM.
Configuring the QIO Subsystem Falling Back to the Default Configuration Task 3 Rename the current configuration file: -> RENAME qioconf, qioconfx where qioconf is the name of the current configuration file. Task 4 Rename the empty configuration file: -> RENAME qioconfo, qioconf where qioconfo is the name of the empty configuration file. Task 5 Reload the processor that you want to reconfigure and run the new QIO configuration file. Task 6 Verify your configuration changes.
3 Managing the QIO Subsystem This section describes several tools provided to verify that your QIO environment is properly configured. These tools are also useful for troubleshooting your environment. Managing the QIO subsystem includes the following tasks: Configuring and starting the QIOMON process. Observing and controlling the shared memory segment while the subsystem is running.
Managing the QIO Subsystem Monitoring Subsystem Operations Monitoring Subsystem Operations The SCF STATUS command is useful for monitoring the operation of the QIO subsystem. The STATUS MON command with the DETAIL option displays the number of client processes and client process queues using the QIOMON process. SCF> status mon $zm02, detail QIO Detailed Status MON \NATIVE.$ZM02 State...................... CPU........................ Priority................... Num Queues................. Num Appls........
Managing the QIO Subsystem Traces Traces The QIO subsystem displays information on its operation. This information can be obtained through SCF STATUS commands. Subsystem Errors Most of the errors encountered at startup are configuration errors. If you have modified an HP-supplied configuration file, recheck your modifications to make sure they are correct. Inappropriate configuration of the QIO subsystem might result in a QIO event 2 message.
Managing the QIO Subsystem Managing the Display of Event Messages Managing the Display of Event Messages You can display event messages in three different ways: Use the ViewPoint application as described in the ViewPoint Manual. Run an EMS distributor, which writes event messages to a printer, terminal, or file. Read the event message display on the operator console. For more information on event messages, see the Event Management Service (EMS) Analyzer Manual.
4 QIO Subsystem SCF Commands This section contains the following information: An overview of the Subsystem Control Facility (SCF) features and operation, and the objects on which SCF operates A general description of the SCF interface to the QIO subsystem The SCF commands supported by the QIO subsystem and the object types supported for each command Sensitive and nonsensitive commands The following detailed information about each SCF command: A description of the command function Com
QIO Subsystem SCF Commands SCF Commands Figure 4-1. Control and Inquiry Management Interface to the QIO Subsystem Terminal Application Process Command (OBEY) File SCF Log File SCF QIO Subsystem QIO Manager Configuration Database vst006.vsd SCF automatically opens and closes the SCP. In most cases, the default SCP, known to the system as $ZNET, is the only one you will ever need.
QIO Subsystem SCF Commands Objects The SYSTEM and VOLUME commands control the default system, volume, and subvolume names used for expanding file names. The OBEY and OUT commands control the files used for command input and display output. The ASSUME command defines a default object to be used when the object is omitted from an SCF command. The ENV command displays the current settings of the SCF command parameters that establish the program environment.
QIO Subsystem SCF Commands Input Sources subsystem or its objects, SCF translates the command into a formatted message for SCP, which then communicates with the appropriate subsystem to perform the specified task. SCF accepts commands from a terminal, a disk file, or an application process. It sends display output to a terminal, a file, a process, or a printer. When SCF is started interactively, the input source and output destination are specified in the commandinterpreter RUN command used to start SCF.
QIO Subsystem SCF Commands Output Destinations system name and volume name are the default names currently in use by the TACL command interpreter through which the RUN command was entered): 19> SCF / IN $DATA.SCF.STARTUP / If you run SCF from TACL without specifying an input file, SCF assumes that the input is coming from your terminal. Output Destinations SCF can direct output to a disk file, an application process, a terminal, or a printer.
QIO Subsystem SCF Commands SCF Online Help SYSTEM \newsys, where newsys is the name of the system that is to become the default system. If the command pertains to an object, it is followed immediately by the object type and the object name. For example, the following command aborts a subnet named $ZTC0.#SN1: SCF> ABORT SUBNET $ZTC0.#SN1 The following command aborts a route named $ZTC0.#ROU1: SCF> ABORT ROUTE $ZTC0.
QIO Subsystem SCF Commands Object States Table 4-1. QIO SCF Commands Command Description ALTER Changes the values of the attributes of an existing object. INFO Obtains configuration information, such as the configured attribute values for an object. NAMES Displays a list of the subordinate object types and names for an object. STATUS Displays current status and configuration information about an object. STOP Terminates the activity of objects in a normal manner.
QIO Subsystem SCF Commands Sensitive and Nonsensitive Commands Sensitive and Nonsensitive Commands Because some SCF commands can have detrimental effects if improperly used, special qualification is required to use them. These commands are called sensitive commands. Sensitive commands can change the state or configuration of subsystem objects, start or stop tracing, or change the values of statistics counters.
QIO Subsystem SCF Commands ALTER Command ? Use the question mark to represent a single unknown character in a specific position; for example, $ZM01.#Z?1 selects all object names subordinate to $ZM01 that begin with #Z, end with 1, and contain exactly one character between the #Z and the 1. ALTER Command Use the ALTER command to change the values of the attributes of an existing object. The ALTER command changes only the specified attributes of the target object. This is a sensitive command.
QIO Subsystem SCF Commands Altering a SEGMENT Object SEGMENT segment-name indicates the SEGMENT you want to alter. Value: The SEGMENT name is the same as the MON name. The name of the MON object as defined by the Kernel subsystem on NonStop S-series servers or on Integrity NonStop NS-series servers. The possible values are: $ZMnn, where nn are numeric digits 00 through 15 that designate the processor in which the QIOMON process is running, or the asterisk ($ZM*) to specify all configured MON objects.
QIO Subsystem SCF Commands INFO Command Using the ALTER SEGMENT Command Use the following command to alter a SEGMENT object: SCF ALTER SEG $ZM03, POOLSIZE 4, UNIT M Considerations The specified SEGMENT object must be in the STARTED summary state. The ALTER command does not alter the summary state of the object. You cannot use the ALTER command to change the maximum percentage of available memory that the QIO subsystem will consume.
QIO Subsystem SCF Commands Obtaining Configuration Information About a MON Object Obtaining Configuration Information About a MON Object The INFO MON command returns the static configuration attribute values for a QIO monitor process object.
QIO Subsystem SCF Commands NAMES Command Config FileName is the name of the configuration file that the QIOMON process used at startup (if supplied). The format of the display for the INFO MON command with the DETAIL option is: 3-> info mon $zm00, detail QIO Detailed Info MON \MYSYS.$ZM00 Config FileName........ Program FileName....... \MYSYS.$SYSTEM.SYS01.QIOMON Library FileName....... Config FileName is the name of the configuration file that the QIOMON process used at startup.
QIO Subsystem SCF Commands Obtaining Names Information About an APPL Object Obtaining Names Information About an APPL Object The NAMES APPL command has the following syntax: NAMES [ / OUT file-spec / ] APPL appl-name OUT file-spec causes any SCF output generated for this command to be directed to the specified file as described earlier in this section under Output Destinations on page 4-5. APPL appl-name indicates the APPL name you want to obtain information about.
QIO Subsystem SCF Commands Obtaining Names Information About an APPL Object The format of the display for the NAMES APPL command is: 4-> names appl $zm00 QIO Names APPL \MYSYS. APPL $ZM00.#FOXKAU.30165E80 QUEUE $ZM00.#FOXKAU.30165E80.$FOXKAU.#COMP_Q $ZM00.#FOXKAU.30165E80.$FOXKAU.#WANR_Q APPL $ZM00.#IPCORE.301727C0 QUEUE $ZM00.#IPCORE.301727C0.$IPCORE.#COMP_Q $ZM00.#IPCORE.301727C0.$IPCORE.#WANR_Q APPL $ZM00.#IPCORE.30172FC0 QUEUE $ZM00.#IPCORE.30172FC0.EXPAND_UIP_COMPLQ_0031 $ZM00.#IPCORE.30172FC0.
QIO Subsystem SCF Commands Obtaining Names Information About a MON Object (continued) APPL $ZM00.#ZTC2.3010DC40 QUEUE $ZM00.#ZTC2.3010DC40.$ZTC2.#QIOSOCK.CMD APPL $ZM00.#ZTC3.300060C0 QUEUE $ZM00.#ZTC3.300060C0.$ZTC3.#QIOSOCK.CMD APPL $ZM00.#ZZLAN.30006140 APPL shows a list of the configured APPL objects. QUEUE shows a list of the configured QUEUE objects.
QIO Subsystem SCF Commands Obtaining Names Information About a MON Object The format of the display for the NAMES MON command is: 2-> names mon $zm00 QIO Names MON \MYSYS. MON $ZM00 APPL $ZM00.#FOXKAU.30165E80 QUEUE $ZM00.#FOXKAU.30165E80.$FOXKAU.#COMP_Q $ZM00.#FOXKAU.30165E80.$FOXKAU.#WANR_Q APPL $ZM00.#IPCORE.301727C0 QUEUE $ZM00.#IPCORE.301727C0.$IPCORE.#COMP_Q $ZM00.#IPCORE.301727C0.$IPCORE.#WANR_Q APPL $ZM00.#IPCORE.30172FC0 QUEUE $ZM00.#IPCORE.30172FC0.EXPAND_UIP_COMPLQ_0031 $ZM00.#IPCORE.30172FC0.
QIO Subsystem SCF Commands Obtaining Names Information About a QUEUE Object (continued): APPL $ZM00.#ZTC2.3010DC40 QUEUE $ZM00.#ZTC2.3010DC40.$ZTC2.#QIOSOCK.CMD APPL $ZM00.#ZTC3.300060C0 QUEUE $ZM00.#ZTC3.300060C0.$ZTC3.#QIOSOCK.CMD APPL $ZM00.#ZZLAN.30006140 SEGMENT $ZM00 MON shows a list of the configured MON objects. APPL shows a list of the configured APPL objects. QUEUE shows a list of the configured QUEUE objects. SEGMENT shows a list of the configured SEGMENT objects.
QIO Subsystem SCF Commands Obtaining Names Information About a SEGMENT Object QUEUE queue-name specifies the name of the QUEUE you want to obtain information about. Value: The QUEUE name is defined by the client process and must be unique within the segment. The name can as long as 23 characters. It is recommended that the name of the APPL that is creating the queue be used as the prefix for the QUEUE name. For example, $ZM02.#ZTC2.IN is the queue that belongs to the $ZM02.
QIO Subsystem SCF Commands Obtaining Names Information About a SEGMENT Object OUT file-spec causes any SCF output generated for this command to be directed to the specified file as described earlier in this section under “Output Destinations.” SEGMENT segment-name indicates the SEGMENT you want to obtain information about. Value: The SEGMENT name is the same as the MON name. The name of the MON object as defined by the Kernel subsystem on NonStop S-series servers.
QIO Subsystem SCF Commands STATUS Command STATUS Command Use the STATUS command to display current status and configuration information about an object. This is a nonsensitive command. The STATUS command is supported for the following QIO subsystem objects: APPL MON QUEUE SEGMENT Note. The display examples are preceded by the command syntax that generated the display.
QIO Subsystem SCF Commands Obtaining Status Information About an APPL Object The format of the display for the STATUS APPL command without the DETAIL option is: 8-> status appl $zm00 QIO Status APPL Name $ZM00.#FOXKAU.30165E80 $ZM00.#IPCORE.301727C0 $ZM00.#IPCORE.30172FC0 $ZM00.#ZLM00.30165C00 $ZM00.#ZTC0.300B5E80 $ZM00.#ZTC1.30006280 $ZM00.#ZTC2.3010DC40 $ZM00.#ZTC3.300060C0 $ZM00.#ZZLAN.
QIO Subsystem SCF Commands Obtaining Status Information About an APPL Object 9-> status appl $zm00, detail QIO Detailed Status APPL \MYSYS.$ZM00.#FOXKAU.30165E80 State.................. Appl Id................ Current Space.......... Space Limit............ DEFINED 806772352 0 0 QIO Detailed Status APPL \MYSYS.$ZM00.#IPCORE.301727C0 State.................. Appl Id................ Current Space.......... Space Limit............ DEFINED 806823872 0 0 QIO Detailed Status APPL \MYSYS.$ZM00.#IPCORE.
QIO Subsystem SCF Commands Obtaining Status Information About a MON Object Name is the name of the APPL object. State is the current summary state of the queue. The only valid value is DEFINED. APPL Id the module ID assigned to the application. The number is displayed in decimal numbers. Current Space is the size of the pool, in bytes, that the client obtained from the shared memory segment. Space Limit is the maximum memory, in bytes, that the client can obtain from the QIO segment.
QIO Subsystem SCF Commands Obtaining Status Information About a MON Object MON monitor-name indicates the QIO monitor process you want to obtain information about. Value: The name of the MON object as defined by the Kernel subsystem on NonStop S-series servers. The possible values are: $ZMnn, where nn are numeric digits 00 through 15 that designate the processor in which the QIOMON process is running, or the asterisk ($ZM*) to specify all configured MON objects.
QIO Subsystem SCF Commands Obtaining Status Information About a MON Object Priority is the priority of the QIOMON process. Trace Status indicates whether the trace facility is ON or OFF. The format of the display for the STATUS MON command with the DETAIL option is: 11-> status mon $zm00, detail QIO Detailed Status MON \MYSYS.$ZM00 State.................. CPU.................... Priority............... Num Queues............. Num Appls.............. Trace Status........... Trace FileName.........
QIO Subsystem SCF Commands Obtaining Status Information About a QUEUE Object Obtaining Status Information About a QUEUE Object Use the STATUS QUEUE command to display current status and configuration information about an QUEUE object.
QIO Subsystem SCF Commands Obtaining Status Information About a QUEUE Object The format of the display for the STATUS QUEUE command without the DETAIL option is: 12-> status queue $zm00 QIO Status QUEUE Name $ZM00.#FOXKAU.30165E80.$FOXKAU.#COMP_Q $ZM00.#FOXKAU.30165E80.$FOXKAU.#WANR_Q $ZM00.#IPCORE.301727C0.$IPCORE.#COMP_Q $ZM00.#IPCORE.301727C0.$IPCORE.#WANR_Q $ZM00.#IPCORE.30172FC0.EXPAND_UIP_COMPLQ_0031 $ZM00.#IPCORE.30172FC0.EXPAND_UIP_RCVQ_0031 $ZM00.#ZLM00.30165C00.E4SA0.0.MGMT.RXPENDQ $ZM00.#ZLM00.
QIO Subsystem SCF Commands Obtaining Status Information About a QUEUE Object Queue Id is the internal name assigned to the queue by the QIOMON process. Current MD Count is the number of message descriptors (MDs) currently in the queue. High MD Count is the maximum number of simultaneous MDs allowed on the queue. Obtaining Status Information About a SEGMENT Object Use the STATUS SEGMENT command to display current status and configuration information about an SEGMENT object.
QIO Subsystem SCF Commands Obtaining Status Information About a QUEUE Object Considerations The summary state of the object does not prevent the STATUS command from being successfully completed. The STATUS command does not alter the summary state of the objects. The format of the display for the STATUS SEGMENT command without the DETAIL option is: 14-> status segment $zm00 QIO Status SEGMENT Name $ZM00 State DEFINED Segment State STARTED Name is the name of the segment.
QIO Subsystem SCF Commands Obtaining Status Information About a QUEUE Object State indicates the current summary state of the MON object. DEFINED is the only valid value. Segment State is the current state of the QIO segment. Valid values are STARTING, STOPPING, and DEFINED. Segment Type is the type of the shared memory segment. Valid values are KSEG2 (for segments in Kseg2) and FLAT_UA (for segments in the flat memory space). Segment Size is the size, in bytes, of the QIO segment in the QIO subsystem.
QIO Subsystem SCF Commands STOP Command Max Pool Alloc is the high water mark, in bytes, allocated from the shared memory pool. Current Pool Frags is the current number of fragments in the shared memory pool. Max Pool Frags is the high water mark of fragments contained in the shared memory pool. STOP Command Use the STOP command to terminate the activity of objects in a normal manner. The STOP command prevents the object from accepting further service requests.
QIO Subsystem SCF Commands TRACE Command MON monitor-name indicates the QIO monitor process you want to stop. Value: The name of the MON object as defined by the Kernel subsystem on NonStop S-series servers. The possible values are: $ZMnn, where nn are numeric digits 00 through 15 that designate the processor in which the QIOMON process is running, or the asterisk ($ZM*) to specify all configured MON objects.
QIO Subsystem SCF Commands Obtaining Trace Information About a MON Object The STATUS MON command has the following syntax: TRACE [ / OUT file-spec / ] MON monitor-name { , STOP } { [ , COUNT count ] [ , NOCOLL ] [ , PAGES pages ] [ , RECSIZE size ] [ , SELECT select-spec ] [ , TO file-spec ] *** [ , WRAP ] } [ , NOBULKIO ] *** This attribute is required when a trace is started. OUT file-spec causes any SCF output generated for this command to be directed to the specified file.
QIO Subsystem SCF Commands Obtaining Trace Information About a MON Object NOCOLL indicates that the trace collector process should not be initiated. PAGES pages designates how much space, in units of pages, is allocated in the extended data segment used for tracing. PAGES can be specified only when a trace is being initiated, not when its parameters are being modified. pages is an integer in the range 4 through 1024, or it is equal to 0 (zero).
QIO Subsystem SCF Commands VERSION Command creates the file with an extent size of 100 pages for the primary extent and 20 pages for secondary extents. There are a maximum of 15 secondary extents for a maximum file size of 400 pages. If a file larger than 400 pages is needed, use a previously created file. WRAP specifies that when the trace disk file end-of-file (EOF) is reached, trace data will wrap around to the beginning of the file and overwrite any data that is there. The default is “NOWRAP.
QIO Subsystem SCF Commands VERSION Command MON monitor-name indicates the QIO monitor process you want to obtain information about. Value: The name of the MON object as defined by the Kernel subsystem on NonStop S-series servers. The possible values are: $ZMnn, where nn are numeric digits 00 through 15 that designate the processor in which the QIOMON process is running, or the asterisk ($ZM*) to specify all configured MON objects.
QIO Subsystem SCF Commands QIO Configuration and Management Manual—424717-008 4-38 VERSION Command
A QIO SCF Error Messages This appendix contains the following information: A description of the QIO subsystem operator messages and error messages generated by the QIO Monitor (QIOMON) process A description of the probable cause of each error and suggested recovery action Italics indicate actual values that are inserted into the message by the QIOMON process. QIO Error Messages The QIOMON process can generate error and operator messages.
QIO SCF Error Messages Operator Messages Operator Messages Operator messages are identified by number. You can use the SCF HELP command to display the text of a message. For example, if the system displays: 00001 Object you can enter the following command to display the text of the message: -> HELP QIO 1 The following QIO operator messages are presented in numerical order. 00001 Object yy-dd-mm hh:mm:ss monitor-name TANDEM.ZQIO.
QIO SCF Error Messages 00002 Object current-state indicates the state of the QIOMON process after the event occurred. Cause. The system has initialized the QIO segment, and the MON object is ready. The QIOMON process also generates this message when it receives a COUP STOP command, and the QIOMON process finds active client processes using the shared segment. Effect.
QIO SCF Error Messages 00002 Object previous-state indicates the state that the QIOMON process was in before this event occurred. current-state indicates the state of the QIOMON process after the event occurred. Cause. The cause for this event message can be one of the following: The amount of memory QIO needs for use is too large or the MemoryPercent parameter is too small.
QIO SCF Error Messages 00003 Buffer 00003 Buffer yy-dd-mm hh:mm:ss monitor TANDEM.ZQIO.D30 000003 Buffer shortage occurred nn times in last 3 minutes. yy-dd-mm hh:mm:ss is the date and time that the event occurred. monitor is the name of the QIOMON process that generated the event message. nn is the number of times the event occurred. Cause. The QIO Library was unable to obtain a buffer.
QIO SCF Error Messages 00005 Pool 00005 Pool yy-dd-mm hh:mm:ss monitor TANDEM.ZQIO.D30 000005 Pool shortage occurred nn times in last 3 minutes. yy-dd-mm hh:mm:ss is the date and time that the event occurred. monitor is the name of the QIOMON process that generated the event message. nn is the number of times the event occurred. Cause. The QIO Library has declined a pool request. This condition may occur often, so events after the initial event are accumulated and reported approximately every 3 minutes.
Glossary API. See application program interface (API). appearance side. The side of an HP NonStop™ S-series system enclosure that contains disk customer-replaceable units (CRUs) and the power monitor and control unit (PMCU) CRUs that do not require cables. The appearance side always has a short door and panel, or a tall door, that is required for cooling the enclosure. The appearance side is opposite the service side. The appearance-side door is lockable for security purposes. See also service side.
Glossary Class-3 CRU replacing HP NonStop™ S-series CRUs or equivalent training. Customers must be able to use the tools needed for the replacement procedure and must protect components from electrostatic discharge (ESD). Class-3 CRU. A customer-replaceable unit (CRU) that probably will cause a partial or total system outage if the documented replacement procedure is not followed correctly.
Glossary configured object configured object. A Subsystem Control Facility (SCF) object that exists at the time a subsystem completes its initialization process, or an SCF object that is brought into existence by a command issued through a subsystem management interface. connection. (1) The path between two protocol modules that provides reliable stream delivery service.
Glossary error error. A condition encountered when performing a command or other operation that causes the command or operation to fail. error number. For the Subsystem Programmatic Interface (SPI), a value that can be assigned to a return token or to the last field of an error token to identify an error that occurred. SPI defines a small set of error numbers, but most error numbers are defined by subsystems. Ethernet.
Glossary flat segment memory In the Guardian environment, disk file names include a node name, volume name, subvolume name, and file identifier; for example, \NODE.$DISK.SUBVOL.MYFILE. In the Open System Services (OSS) environment, a file is identified by a pathname; for example, /usr/john/workfile. See also filename flat segment memory. Nonprivileged memory space that appears a single large addressable space. FRU. See field-replaceable unit (FRU). generic process.
Glossary HP Tandem Advanced Command Language (TACL) HP Tandem Advanced Command Language (TACL). The user interface to the NonStop OS. The TACL product is both a command interpreter and a command language. Users can write TACL programs that perform complex tasks or provide a consistent user interface across independently programmed applications. inbound queue. The inbound queue is used to hold message descriptors for data received from the LAN. input source.
Glossary MB MB. See megabyte (MB). Mbps. See megabits per second (Mbps). media access control (MAC) address. A value in the Medium Access Control sublayer of the IEEE/ISO/ANSI LAN architecture that uniquely identifies an individual station that implements a single point of physical attachment to a LAN. megabits per second (Mbps). A data rate equal to 1,048,576 bits per second. megabyte (MB). A unit of measurement equal to 1,048,576 bytes (1024 kilobytes) for memory size.
Glossary NonStop™ Series TNS acceleration. Integrity NonStop NS-series systems include all HP NonStop™ systems that use NSE-x processors. NonStop™ Series TNS. See TNS. NonStop™ Series TNS/R. See TNS/R. NonStop Technical Library. See HP NonStop™ Technical Library (NTL). OBEY file. See command file. object. One or more of the devices, lines, processes, and files in an subsystem; any entity subject to independent reference or control by one or more subsystems.
Glossary Pathway pathname can be either relative or absolute. See also ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990 or POSIX.1), Clause 2.2.2.57. Pathway. An HP NonStop™ application that configures and manages online transaction applications. persistence. For the Subsystem Control Facility (SCF), the capability of a generic process to restart automatically if it was stopped abnormally. You configure this capability by specifying a nonzero AUTORESTART value in an ADD command.
Glossary PROFILE object type PROFILE object type. The Subsystem Control Facility (SCF) object type for the storage subsystem configuration profile. protocol. A set of rules used by processes or devices for exchanging data. QIO. An HP NonStop™ product that provides buffers and control blocks for client processes, (including TCP/IP, TLAM, NonStop IPX/SPX, and other processes) running on the same processor. QIO library.
Glossary ServerNet LAN Systems Access (SLSA) subsystem services in response to requests received from clients across a network. For example, the HP NonStop™ servers provides transaction processing, database access, and other services. (3) A process or program that provides services to a client or a requester.
Glossary shared memory segment shared memory segment. The shared memory segment is allocated when QIO is started. The shared memory segment contains the data structures used to send and receive data for each LAN controller in the processor. SLSA subsystem. See ServerNet LAN Systems Access (SLSA) subsystem. state. In Subsystem Control Facility (SCF), one of the generally defined possible conditions of an object with respect to the management of that object.
Glossary terabyte (TB) terabyte (TB). A unit of measurement equal to 1,099,511,627,776 bytes (1024 gigabytes). See also gigabyte (GB), kilobyte (KB), and megabyte (MB). TIM. See HP NonStop™ Technical Library (NTL). TNS. Refers to fault-tolerant HP computers that support the NonStop OS and are based on microcoded complex instruction-set computing (CISC) technology. TNS systems run the TNS instruction set. Contrast with TNS/R and TNS/E. TNS/R.
Glossary $ZPM QIO Configuration and Management Manual—424717-008 Glossary-14
Index Numbers D 2-14 2-14, 2-19, 2-20, 2-21, 2-22 2-22 2-22 DIH A Acquiring resources from shared memory segment 1-9 APPL name 1-6 object 1-6 object type 1-6 Architecture of QIO subsystem 1-3 B See Driver and interrupt handler Display examples INFO MON 4-12 NAMES APPL 4-15 NAMES MON 4-17, 4-19 NAMES SEGMENT 4-20 STATUS APPL 4-22 STATUS MON 4-25 STATUS QUEUE 4-28 STATUS SEGMENT 4-30 Driver and interrupt handler (DIH) 1-3 E Base address 2-12 C Client process acquiring resources 1-9 displaying number
Index I I INFO MON attribute 4-12 command 3-3, 4-12 Interrupt handler 1-3 IOperm 2-4 K Kseg2 2-8, 2-9, 2-10 L LAN driver and interrupt handler 1-3 Library file, displaying file name 3-3 Library of QIO procedures 1-3 M Management interfaces to QIO subsystem 1-5 Management tasks 3-1 Memory management 2-5 Memory pool description of 1-3 size 2-6, 3-2 Message buffer 1-3 descriptor 1-3 MON INFO MON command 4-12 object 1-6 object name 1-6 N NAMES command 3-3, 4-14, 4-16, 4-18, 4-19 Nonsensitive commands INFO
Index R functions 1-8 IOperm 2-4 library 1-3 management interfaces 1-5 management tasks 3-1 memory 2-14 monitoring 3-2 NonStop systems 1-4 object displaying operational state 3-3 program file displaying file name 3-3 QIO library displaying file name 3-3 QIO object displaying names 3-3 displaying summary state 3-3 requirements for 1-4 troubleshooting 3-2 QIOMON process 1-3 generic process 1-8 name 1-6 reconfiguring 3-2 starting and stopping 1-5 starting before client processes 1-8 verifying configuration 3
Index T displaying 3-3 T Templates for object names 4-8 TRACE MON command example 4-36 Tracing 3-3 Troubleshooting QIO subsystem 3-2 U User 2-2 User addressable data space 2-2 V ViewPoint application 3-4 W Wild-card characters in object names 4-8 Special Characters $ZMnn QIOMON process name 1-6 QIO Configuration and Management Manual—424717-008 Index-4
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.
Legal Notices Legal Notices 1 What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Who Should Use This Manual vii How This Manual Is Organized vii Where to Get More Information vii NonStop S-Series Configuration and Management Manuals Notation Conventions xv Abbreviations xix x 1.
3.
A.
Index QIO Configuration and Management Manual—424717-008 4
Examples Examples QIO Configuration and Management Manual—424717-008 1
Examples QIO Configuration and Management Manual—424717-008 2
Figures Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 1-4. Figure 1-5. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 4-1.
Figures QIO Configuration and Management Manual—424717-008 2
Tables Tables Table i. Table ii. Table iii. Table iv. Table 4-1. Table 4-2. Table 4-3. Table 4-4.
