MPE/iX System Utilities Reference Manual HP e3000 Computer Systems Manufacturing Part Number : 32650-90908 E0602 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 2. Utilities Quick Reference ASOCTBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Additional Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FCOPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation. . . . . . . . . . . . . . . .
Contents Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NLIOUTIL . . . . . . . . . . . . . . . . .
Contents SPIFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Discussion . . . . .
Contents VOLUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Discussion . . . . . . .
Contents Saving multiple file sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SHOWDEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TAPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNCONFIG. . . . . . . . . . . . . . . . . . . .
Contents Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 11. LANGINST Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Listing Supported Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding a Language . . . . . . . . .
Contents M .............................................................................. DG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MODIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Messages . . . . . . . . . . . . . . . .
Contents Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DIag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DUmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reset . . . . . . . . . . . . . . . . . .
Tables Table 4-1. BULDACCT Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Table 7-1. EDIT/3000 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Table 8-1. FCOPY Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Table 11-1. LANGINST Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 14
Figures Figure 25-1. LIF Standard Logical Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 Figure 25-2. Boot utility format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Figure 32-1. UPSUTIL Invocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 16
Preface MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX.
1 Introduction MPE/iX utilities are programs that provide a dimension of system management and control that ranges from the required or necessary to the helpful or convenient. As such, they help ensure your success as an HP e3000 computer owner by enabling you to fully utilize the potential of your machine. This manual approaches utilities in two ways: First, chapter 2 provides a quick reference to the basic operation of each utility. This treatment does not provide in-depth usage detail.
Introduction 20 Chapter 1
2 Utilities Quick Reference This chapter arranges utilities in alphabetical order and provides a quick summary of the basic operation of each one. It does not provide in-depth information. At the end of each summary, you are told where to find more detailed information. In many cases, you are referred to another chapter in this manual. Where a utility is described in a separate document, however, you are directed toward that source of information.
Utilities Quick Reference ASOCTBL ASOCTBL Syntax ASOCTBL or RUN ASOCTBL.PUB.SYS The system responds with > and you should enter: >devclass=username.acctname Operation Use ASOCTBL to distribute operator commands for specific devices to standard MPE/iX users. This utility creates a device class/user table in a file called ASOCIATE.PUB.SYS. Once a user is included in the association table, he or she gains access to the corresponding device class by the use of the ASSOCIATE command.
Utilities Quick Reference AUTOINST AUTOINST Syntax AUTOINST Operation Use AUTOINST to restore the information contained on the FOS and SUBSYS tapes, set up the necessary accounting structure and creates a customized system load tape (SLT). The fundamental operating system (FOS) and subsystem (SUBSYS) tapes contain programs and utilities for performing specific functions such as compiling programs, copying files, or editing text.
Utilities Quick Reference BULDACCT BULDACCT Syntax To use BULDACCT interactively, enter: BULDACCT Or, you may invoke BULDACCT and specify options as part of the ;INFO string by entering: BULDACCT;INFO=" ... " Operation Use BULDACCT to take a snapshot of the directory structure on the source system and recreate it on a destination system. It is especially useful for creating a directory structure on a system without a tape drive where the ;DIRECTORY option of the RESTORE command cannot be used.
Utilities Quick Reference BUILDINT BUILDINT Syntax RUN BUILDINT.PUB.SYS or BUILDINT Operation Use BUILDINT to build or change Compatibility Mode (CM) intrinsic disk files. BUILDINT accepts SPL procedure head declarations (OPTION EXTERNAL is required) and optional commands as input data. If no commands are issued, the procedure head declarations are added to the intrinsic file. Any input data that is not a procedure head terminates input.
Utilities Quick Reference CLKUTIL CLKUTIL Syntax From the system console: ISL> CLKUTIL Operation CLKUTIL is a standalone utility that runs only on the physical console at the ISL prompt. It reads and sets the battery-backed-up hardware clock, which should be set to Greenwich Mean Time (GMT). The hardware clock provides the basis for timestamps and time displays that are part of some ISL utilities.
Utilities Quick Reference DEBUG DEBUG Syntax DEBUG or RUN PROGNAME;DEBUG Operation System programmers use DEBUG to set breakpoints within programs and to display and modify data stacks and registers. To use the DEBUG utility, you must have privileged mode (PM) capability. However, the ;DEBUG option of the RUN command is available to anybody and allows users to debug their applications. CAUTION Normal MPE safeguards are bypassed in privileged mode.
Utilities Quick Reference DIRMIG DIRMIG Syntax DIRMIG or RUN DIRMIG.PUB.SYS Operation Use the directory migration tool (DIRMIG) to simplify the migration of your environment from MPE V/E-based systems to MPE/iX-based systems. DIRMIG uses an MPE V/E SYSDUMP tape to transport data to MPE/iX. The data includes the system directory (accounting structure), UDCs, user logging IDs, user files and information specifically related to user volumes.
Utilities Quick Reference DISCFREE DISCFREE Syntax DISCFREE or RUN DISCFREE.PUB.SYS;INFO="[format][,ldev]" or DISCFREE "[[format]][,ldev]" Operation Use DISCFREE to display information about the system’s free disk space in histogram or allocation formats. It determines disk volume fragmentation and transient and permanent disk space limits. DISCFREE also shows total volume space capacity, as well as disk allocation for single volumes or for the whole system.
Utilities Quick Reference DISCUTIL DISCUTIL Syntax ISL> DISCUTIL Operation DISCUTIL is a standalone utility that you can invoke only at the ISL> prompt from the physical console. It lets you request various disk operations when the operating system is not running. When used in conjunction with the RECOVER command of VOLUTIL, it can save, and subsequently recover, files from a system that is logically inoperable.
Utilities Quick Reference DUMP DUMP Syntax ISL> DUMP Operation DUMP is a standalone utility that you can invoke only at the ISL> prompt from the physical console. It takes a snapshot or dump of system memory at a given point in time, which can help HP support personnel to determine the cause of system problems. You must precede the DUMP command by a non-destructive boot.
Utilities Quick Reference EDIT/3000 EDIT/3000 Syntax EDITOR Operation Use EDIT/3000 to create and update ASCII files. The Editor commands allow you to insert, delete, replace, modify, search for, and manipulate characters, strings of characters, or entire lines of characters. You can run EDIT/3000 in batch mode or interactively. In an interactive session, you enter commands and text through an interactive terminal.
Utilities Quick Reference FCOPY FCOPY Syntax FCOPY FROM=filename;TO=filename[;options] Operation Use FCOPY to copy and translate files. The FCOPY command identifies a from file, a to file, and one or more functions that let you convert data, copy files from other systems, append files, extract subsets of files, display binary files in ASCII format, and other tasks. • A from file is the input file for an FCOPY command; it contains the data that you want to copy.
Utilities Quick Reference FSCHECK FSCHECK Syntax FSCHECK Operation Use the file system check utility (’’FCHECK’’) to detect and repair inconsistencies found in the file directories and file label tables of the MPE/iX operating systems. You also use it to query and display various attributes of these objects. It is a standalone utility and should be the only program running on the system when it is in use.
Utilities Quick Reference GENCAT GENCAT Syntax RUN GENCAT.PUB.SYS or GENCAT Operation Use GENCAT to modify a source catalog or to expand a formatted message catalog (for instance, with messages in the user’s native language). It is available to users without any special capabilities. Additional Discussion For more information, refer to the Message Catalogs Programmer’s Guide.
Utilities Quick Reference I7DB8CNV I7DB8CNV Syntax RUN I7DB8CNV.PUB.SYS Operation Use I7DB8CNV to convert the character data in an IMAGE database from any Hewlett-Packard 7-bit national substitution set to ROMAN8. The program is a special version of the program DBLOAD.PUB.SYS, and the conversion is done as part of a database load. Generally, you run DBUNLOAD.PUB.SYS and DBUTIL.PUB.SYS,ERASE before you run the I7DB8CNV utility. Additional Discussion For more information, refer to Chapter 10, “I7DB8CNV.
Utilities Quick Reference IOMAP IOMAP Syntax ISL> IOMAP Operation IOMAP is a standalone utility that you run at the ISL prompt from the physical console. It identifies the actual I/O configuration of the system and its paths and devices. You can also use IOMAP’s self test and loopback diagnostics to test I/O system components.
Utilities Quick Reference KSAMUTIL KSAMUTIL Syntax To invoke KSAMUTIL, enter: RUN KSAMUTIL.PUB.SYS or KSAMUTIL Operation Use KSAMUTIL to manage compatibility mode KSAM files. With KSAMUTIL commands, you can create a CM KSAM file, rename both the data and key files, save a temporary file as a permanent file, clear all data from a file, purge a file, and verify the contents and access history of an existing file. KSAMUTIL runs in either session or batch mode.
Utilities Quick Reference LANGINST LANGINST Syntax LANGINST Operation Use LANGINST to configure language-specific information onto your HP e3000. Specifically, LANGINST enables you to: • add a language to the configuration file • remove a language from the configuration file • display and modify local formats of a configured language • display the languages supported by Hewlett-Packard • display the language currently configured • modify the system default language You must log on as MANAGER.
Utilities Quick Reference LINK EDITOR/XL LINK EDITOR/XL Syntax LINKEDIT or RUN LINKEDIT.PUB.SYS;INFO=infostring Operation Use Link Editor/XL to prepare native mode (NM) compiled object files for execution on 900 Series HP e3000 computers. Link Editor/XL can also create and maintain relocatable and executable libraries. To invoke Link Editor/XL for interactive use, enter LINKEDIT at the MPE/iX prompt.
Utilities Quick Reference LOGTOOL LOGTOOL Syntax SYSDIAG DUI> RUN LOGTOOL Operation Use the system and memory log analysis tool (LOGTOOL) to perform a variety of functions on the system log files. You use LOGTOOL to manipulate two types of log files: system log files and the memory log file. LOGTOOL is available in multi user mode, but you are required to execute at a diagnostic security level for some functions.
Utilities Quick Reference MAKECAT MAKECAT Syntax RUN MAKECAT.PUB.SYS Operation Use MAKECAT to maintain the following message catalogs: • CATALOG.PUB.SYS, which contains system error messages • CICAT.PUB.SYS, which contains the Help catalog • User-defined catalogs for various applications Additional Discussion For more information, refer to the Message Catalogs Programmer’s Guide.
Utilities Quick Reference MKNODProgram MKNODProgram Usage mknod "name c|p major minor [link_name]" Operation Use MKNOD to create special files in a traditional UNIX format of major and minor numbers. When creating a device link or streams file (character-type file), you must enter both the major and minor numbers. If you enter a major number of 0, MKNOD creates a device link file that defaults to the LDEV number specified in the minor number argument.
Utilities Quick Reference N7MF8CNV N7MF8CNV Syntax N7MF8CNV or RUN N7MF8CNV.PUB.SYS Operation Use N7MF8CNV to convert data in EDIT/XL and other MPE text and data files from a Hewlett-Packard 7-bit national substitution character to ROMAN8. N7MF8CNV prompts you for language and a file type of text or data. For each data file, N7MF8CNV prompt you for the starting position and length of each field (portion of a record) to be converted. (For a text file, each record is converted as one field.
Utilities Quick Reference NLIOUTIL NLIOUTIL Syntax NLIOUTIL or RUN NLIOUTIL.PUB.SYS;INFO=infostring Operation Use NLIOUTIL to dynamically activate the Native Language I/O (NLIO) subsystem for Asian and Middle East/African (MEA) peripheral devices (terminals and printers). NLIO is the basic input and output system integrated into the operating system for Native Language Support (NLS). Once activated by NLIOUTIL, properly configured native devices may use the Native Language I/O facility.
Utilities Quick Reference NLUTIL NLUTIL Syntax NLUTIL or RUN NLUTIL.PUB.SYS Operation NLUTIL is a utility program used to verify a variety of Native Language Support (NLS) languages and corresponding character sets available on the operating system. A complete listing may be selected to print on the system printer. NLUTIL allows the user to display a table showing the currently configured languages and their character set types. Additional Discussion For more information, refer to Chapter 17, “NLUTIL.
Utilities Quick Reference NMMGR NMMGR Syntax NMMGR Operation Use the Node Management Services Configuration manager to configure your HP 3000’s data communications subsystems. Additional Discussion For more information refer to the following publications: NS3000/XL Network Manager’s Reference Manual and the NS3000/XL NMMGR Screens Reference Manual.
Utilities Quick Reference OCA OCA Syntax OCA Operation Use the object code analyzer to detect migration incompatibilities in compatibility mode applications. You use the output of this tool to formulate a migration plan. When run on MPE/iX systems, it identifies incompatibilities that would prevent the movement of applications from compatibility mode to native mode. OCA is also available on MPE V/E systems as a component of the migration tool set.
Utilities Quick Reference OCT OCT Syntax OCTOMP Operation Use the object code translator to convert compatibility mode (CM) object code to HP Precision Architecture (PA-RISC) instructions for increased performance. With OCT, you can create a new file with translated object code, translate only selected segments of the object code, or add translated segments to another file. OCT translates most CM instructions into HP precision architecture instructions and appends them to the end of the destination file.
Utilities Quick Reference PATCH PATCH Syntax PATCH or RUN PATCH.PUB.SYS Operation Use PATCH to access, display, and/or modify a program file’s object code without recompiling the program. You can make simple changes to program instructions or to global stack area variables on compatibility mode programs. PATCH requires the memory location of the target program symbols, the beginning locations of each program unit, and the offsets for each line of code from these locations.
Utilities Quick Reference PXUTIL PXUTIL Syntax RUN PXUTIL.PUB.SYS Operation Use PXUTIL to manage the UID/GID databases. The PXUTIL utility requires exclusive access to the databases. This means that any command that needs to modify these files (such as NEWACCT, ALTUSER, and so on) fails during PXUTIL operations.
Utilities Quick Reference SAINT SAINT SAINT is a standalone initialization utility that you use to analyze system libraries (that contain system object modules, or SOMs) to produce bootable images. A bootable image is a file that can be copied directly to memory and executed without modification. SAINT primarily depends on the system library file for input. The format of the library file is defined in the SOM Architecture Control Document. WARNING Do not use this utility without service center support.
Utilities Quick Reference SEGMENTER SEGMENTER Syntax SEGMENTER Operation Use SEGMENTER to manage and prepare compatibility mode code segments. Invoked directly with the SEGMENTER command, SEGMENTER lets you manage code segments in USLs (user subprogram libraries), RLs (relocatable libraries) and SLs (segmented libraries), including the ability to group RBMs (relocatable binary modules) into code segments.
Utilities Quick Reference SLPATCH SLPATCH Syntax SLPATCH or RUN SLPATCH.PUB.SYS Operation Use SLPATCH to display or modify the contents of a segmented library (SL) file. CAUTION SLPATCH bypasses normal MPE/iX safeguards and will modify the contents of privileged SLs. It is, therefore, possible to corrupt the SL or the entire operating system. Hewlett-Packard is not responsible for modifications that you make to the operating system or system files.
Utilities Quick Reference SOMPATCH SOMPATCH Use SOMPATCH for binary modification (or patching) of a native mode spectrum object module (SOM) program or library file. WARNING Chapter 2 Do not use this utility without service center support. Unauthorized use will void your warranty and may cause data loss.
Utilities Quick Reference SORT-MERGE/XL SORT-MERGE/XL Syntax SORT or MERGE or RUN SORT.PUB.SYS RUN MERGE.PUB.SYS Operation Use SORT to sort files based on single-key or multiple-key items. Use MERGE to merge data from two or more sorted files into a single, new file. SORT-MERGE/XL operates as a standalone utility (either interactively or in batch mode), or from within a program. You can use SORT-MERGE/XL to sort or merge data in various ways.
Utilities Quick Reference SPIFF SPIFF Syntax SPIFF Operation Use the Native Mode Spooler Interface Facility to list, manipulate, and transfer spooled device files (spoolfiles) that are created and maintained by MPE/iX. SPIFF is the MPE/iX replacement for the MPE compatability mode SPOOK5 program. Additional Discussion The Native Mode Spooler Reference Manual presents a detailed description of the SPIFF utility and its commands.
Utilities Quick Reference STANDARDS STANDARDS The system bootstrap, initial program load (IPL) and initial system load (ISL) standard provides a standard interface through which any Hewlett-Packard Precision Architecture (PA-RISC) computer can boot any operating system. The standard also provides a common user interface for booting PA-RISC systems. WARNING The use of this information without service center support will void your warranty and may cause data loss.
Utilities Quick Reference STORE/RESTORE STORE/RESTORE Syntax To invoke STORE enter: STORE fileset[;parameters] To invoke RESTORE enter: RESTORE storfile[;parameters] Operation Use STORE/RESTORE to store and restore one or more files and directories to and from tape. It has special options that allow you to store files for backup, transport, or archival purposes. For example, to store all files in all groups in the MFG account, enter: FILE T;DEV=TAPE STORE @.@.
Utilities Quick Reference SWITCH ASSIST TOOL SWITCH ASSIST TOOL Syntax SWAT or RUN SWAT.PUB.SYS Operation Use the switch assist tool (SWAT) to simplify the process of implementing an application that has modules written both in native and compatibility modes. SWAT takes input from the user and generates output in the form of PASCAL/XL source code. Additional Discussion For more information, refer to Switch Programming Guide.
Utilities Quick Reference SYSGEN SYSGEN Syntax SYSGEN Operation Use SYSGEN to modify your system configuration.
Utilities Quick Reference SYSMAP SYSMAP Syntax SYSDIAG DUI> RUN SYSMAP ENTER MAP> Operation Use SYSMAP to display the hardware configuration of a system. It displays the device type, product number, logical device number (LDEV) and device address of I/O devices, and the CPU and memory boards. SYSMAP is part of the online diagnostics subsystem. To use SYSMAP, you start the diagnostic subsystem by entering SYSDIAG and, at the DUI> prompt, enter the command RUN SYSMAP.
Utilities Quick Reference TERMDSM TERMDSM Syntax SYSDIAG DUI > RUN TERMDSM Operation Use TERMDSM to diagnose, dump, and reset logical devices, ports, and data communications and terminal controllers (DTCs). You also use it to check the status of ports and DTCs. Additional Discussion For more information, refer to Troubleshooting Terminal, Printer, and Serial Device Connections.
Utilities Quick Reference tic tic Syntax tic.hpbin.sys[-v[n]]-c file Operation Use the tic utility to compile source terminfo descriptions. tic installs the compiled entry under the /usr/lib/terminfo directory hierarchy, unless you set the TERMINFO environment variable, in which case it places results in the directory it points to instead. Entries are stored in directories that match the first character of their name. The entry for the VT-100 terminal, for example, is stored in /usr/lib/terminfo/v/vt100.
Utilities Quick Reference TTUTIL TTUTIL Syntax RUN TTUTIL.PUB.SYS or TTUTIL Operation Use TTUTIL to create, view and modify an existing terminal or printer type file. You can modify characteristics of serial port connections such as flow control, modem control, printer control and character handling. To do so, you enter the terminal or printer type file name and then specify a function.
Utilities Quick Reference untic untic Syntax untic.hpbin.sys[term] Operation Use untic to decompile a terminfo binary file into its source format. If a TERMINFO environment variable is set, the untic utility searches the specified directory; otherwise, untic assumes the file is in the directory /usr/lib/terminfo. The output of an untic decompile is sent to the standard output. Additional Discussion For more information, refer to Chapter 29, “untic.
Utilities Quick Reference V7FF8CNV V7FF8CNV Syntax V7FF8CNV or RUN V7FF8CNV.PUB.SYS Operation Use V7FF8CNV to convert text and literals in VPLUS/XL forms files from a Hewlett-Packard 7-bit national substitution character set to ROMAN8. Additional Discussion For more information, refer to Chapter 30, “V7FF8CNV.
Utilities Quick Reference VERSION VERSION Syntax VERSION or VERSION filename or VERSION "filename [,search string]" Where file(s) File(s) is the name of a program file or a wild carded file set. search string Search string is the name of a particular $version string in a system object module (SOM)(Not applicable for CM program files.) Quotes are required if a search string is specified. Operation Use VERSION to display information about compatibility mode and native mode files.
Utilities Quick Reference VOLUTIL VOLUTIL Syntax VOLUTIL volutil> command name or RUN VOLUTIL.PUB.SYS volutil> command name Operation Use VOLUTIL to manage and maintain individual volumes, volume sets, and volume classes and to make inquiries about their contents, availability, and status. VOLUTIL commands are organized into four groups, based on the object they manipulate.
Utilities Quick Reference VOLUTIL 70 Chapter 2
3 ASOCTBL The ASOCTBL utility lets users with SM or OP capability distribute operator commands for specific devices to other system users. It creates an association table in ASOCIATE.PUB.SYS, where the users are identified with the device classes that they may associate. Once a user is included in the association table, he or she can use the ASSOCIATE command to gain access to the corresponding device class.
ASOCTBL Operation Using ASOCTBL with an ASCII File To run ASOCTBL with an ASCII file you must first create the file using a text editor such as EDIT3000. For example, in the following ASCII file the users and accounts, MGR.MNFG, USER.UTILTY and JACK.MR KTG will be able to associate with LP, TAPE and LP2 respectively. EDITOR /ADD 1 LP = MGR.MNFG 2 TAPE = USER.UTILTY 3 LP2 = JACK.
ASOCTBL Operation Listing the Association Table To list the association table in ASOCIATE.PUB.SYS (users and the devices to which they may associate) enter: RUN ASOCTBL.PUB.SYS,LIST Fatal Errors The following error messages indicate a condition where no modifications are made to the association table. Although you may continue to make inputs to the system without damage, you should exit from ASOCTBL and begin again. UNABLE TO DELETE OLD ’ASOCIATE.PUB.SYS’ FILE EXPECTED AT LEAST 3 PARAMETERS, LDEV = USER.
ASOCTBL Operation 74 Chapter 3
4 BULDACCT The BULDACCT utility lets users with SM capability take a snapshot of the directory structure on a source system running MPE/iX and recreate it on a different destination system. It is especially useful for creating a directory structure on a system without a tape drive where the ;DIRECTORY option of the RESTORE command cannot be used. BULDACCT also lets you migrate a set of accounts from one volume set to another.
BULDACCT Operation Operation To invoke BULDACCT and use the utility interactively, enter: BULDACCT The utility responds with the BULDACCT: prompt, where you enter options from the list shown in Table 4-1 You may use a maximum of 80 characters in the command line. Or, you may invoke BULDACCT and enter options when you issue the command, like this: BULDACCT;INFO=" ... " In this format, you insert options from the list shown in Table 4-1 in the ;INFO string. You may use a maximum of 240 characters.
BULDACCT Operation CAUTION If the destination system already contains user, group or account names that existed on the source system, BULDJOB1 will change their attributes to match those of the source system. If the destination system already contains hierarchical directories that existed on the source system, BULDJOB1 will change the ACDs to match the source system.
BULDACCT Operation 1. Log on as manager.sys and store all the files in the selected account: STORE @.@.GYPSY;;SHOW 2. Run BULDACCT with the VSACCT option to create job files BULDJOB1 and BULDJOB2: RUN BULDACCT;INFO="GYPSY%VSACCT=target_vol_set" 3. Close system level UDC’s residing in the GYPSY account (if any): SETCATALOG udc_file;SYSTEM;DELETE 4.
BULDACCT Operation 6. Restore files to the GYPSY account; making sure that the files whose creators have been purged are also restored. RESTORE ;@.@.@;SHOW;VOLSET=target_vol_set;CREATE=CREATOR (You may wish to add ;OLDDATE to this command to preserve the modify, access and create dates.) 7. Reset all user/account level UDC’s: STREAM BULDJOB2 8.
BULDACCT Operation RUN BULDACCT;INFO="%HELP" 80 Chapter 4
5 DISCFREE Use the DISCFREE utility to display information about disk volume fragmentation and the allocation of transient and permanent space on the disk. DISCFREE also shows total volume space capacity, as well as disk allocation for single volumes or for the whole system. Transient space refers to temporary, fluctuating volume space. Permanent space is volume space set aside for job/session temporary files, permanent disk files, and operating system directories and other data.
DISCFREE Operation Operation To invoke DISCFREE enter: DISCFREE or RUN DISCFREE.PUB.SYS;INFO="[format][,ldev]" or DISCFREE "[format][,ldev]" where format is the specified display type. The format default is A. ldev specifies a particular system volume. The ldev default is no ldev, causing all volumes to be displayed. If you do not specify either of the parameters, DISCFREE prompts for them. If you enter format but not ldev, DISCFREE reports on all logical disk devices.
DISCFREE Operation DISCFREE "C" If you omit quotation marks, the default is the specified format for all devices. DISCFREE displays the following information: DEVICE SIZE The capacity, in sectors, of the device. TRANS SPACE The number of sectors currently allocated for transient space. Transient space is used for objects which are not permanent files, such as stacks, heaps and system tables. MAX TRANS SPACE An upper limit on the number of sectors that may be allocated for transient space.
DISCFREE Operation 84 Chapter 5
6 DISCUTIL DISCUTIL is a standalone utility that lets you perform various disk operations without the operating system. It is particularly important when you need to move files to tape from disks on a system that is logically inoperable, such as one with directory damage. (Once you have done so, you then use the RECOVER option of the VOLUTIL utility on this tape to move the files back onto disk.) You start the utility by entering DISCUTIL at the Initial System Load (ISL) prompt from the system console.
DISCUTIL Operation MOUNT Mounts a disk volume making it accessible to DISCUTIL. PDEV Lists the disks that are currently configured and mounted. REDO Modifies and reexecutes a command from the command history stack. SAVE Saves user-specified files from disks to tape. SHOWDEV Displays information about each configured device. TAPE Displays and selects the current tape ldev. UNCONFIG Unconfigures currently configured devices. The remainder of this chapter describes each of the commands.
DISCUTIL Operation discutil> DO [ [CMD=]cmdid] For example, to re-execute the fifth command, enter: discutil>DO 5 DSTAT Use this command to display information about each mounted volume (i.e., any volume that is currently listed in the mounted volume table).
DISCUTIL Operation MOUNT The MOUNT command is used to mount an unmounted volume. If the ldev represents a disk and if the device is responding, DISCUTIL will attempt to mount the volume. Only MASTER or MEMBER volumes can be mounted. Once mounted, a volume becomes available to DISCUTIL and is added to its mounted volume table. The ldev must be configured prior to mounting a volume on it.
DISCUTIL Operation This command would re-execute the fifth command entered after allowing you to modify it. To re-execute the last command entered enter: discutil>REDO SAVE Use SAVE to retrieve files from disk and copy them to magnetic tape. You might use SAVE after a system failure, when a directory has been corrupted, or when a disk becomes inaccessible to the operating system.
DISCUTIL Operation 2. When you see the ENTER FILE SET TO BE SAVED prompt for the second time, press RETURN to complete the first tape set and rewind the tape. 3. At the discutil> prompt, enter the SAVE command again. (This begins the save procedure for the next file set.
DISCUTIL Operation TAPE Use the TAPE command to display the ldev number of the current tape or to specify a new current tape. If the ldev parameter is omitted, the current tape ldev is displayed. If the ldev parameter is supplied, that ldev will become the new tape ldev. The ldev must have been configured as a tape.
DISCUTIL Operation For example, to see the current tape drive enter: discutil>TAPE To assign a logical device number as the current tape drive enter: discutil>TAPE 7 UNCONFIG Use the UNCONFIG command to remove a device from the system’s configuration. This frees or releases the corresponding ldev and physical path, making them available for reassignment with the CONFIGURE command.
7 EDIT/3000 The EDIT/3000 text editor lets you create and edit ASCII files. Specifically, you may insert, delete, replace, modify and search for characters and strings of characters. You may run EDIT/3000 in either of two modes, interactive or batch. In an interactive session, you enter commands and text from an interactive terminal. Messages and other output (such as prompt characters) from EDIT/3000 are listed on the terminal.
EDIT/3000 Operation Below is a summary of commands you may use with EDIT/3000. Table 7-1 COMMAND EDIT/3000 Commands DESCRIPTION ADD Enters text into the WORK file from the standard input device and/or from the HOLD file. BEGIN Used as the first expression in a BEGIN-END pair. CHANGE Changes existing contents of the WORK file. COPY Copies text from one location to another in the WORK file. DELETE Deletes characters and/or lines from the WORK file. END Terminates EDIT/3000 operation.
EDIT/3000 Operation Table 7-1 COMMAND EDIT/3000 Commands (Continued) DESCRIPTION TEXT Copies the contents of a TEXT file into the WORK file, deleting the current WORK file contents. USE Instructs EDIT/3000 to receive commands from the USE file and to send messages to the OUTPUT file and, generally, to expect input from the INPUT file. VERIFY Reports the current EDIT/3000 operating conditions declared in a SET command, or the default conditions not declared in a SET command.
EDIT/3000 Operation File Definitions EDIT/3000 uses seven files: INPUT, OUTPUT, WORK, TEXT, JOIN, HOLD, and USE. Each file is described below. INPUT Used to enter commands and text records to EDIT/3000. Generally, this file is a terminal in interactive mode and a batch input device in batch mode. EDITIN is the formal file designator. OUTPUT Receives messages (and prompt characters in interactive sessions). Generally this file is a terminal in interactive mode and a line printer in batch mode.
8 FCOPY You use the FCOPY utility to copy and translate files. The FCOPY command identifies a from file, a to file, and one or more FCOPY functions. Some of the functions you may perform include: • converting data • copying files from other systems • appending files • extracting subsets of files • displaying binary files in ASCII format • copying byte-stream files A from file is the input file for an FCOPY command; it contains the data you want to copy.
FCOPY Operation Operation To invoke FCOPY enter: FCOPY FROM=input file;TO=output file;functions For example, to create a new disk file (in exactly the same format as another file) use the NEW parameter: > FROM=OLDFILE;TO=NEWFILE;NEW To copy a subset of one file to another enter: > FCOPY FROM=FILEONE;TO=FILETWO;SUBSET=29:33 In this example FCOPY copies the 30th through 34th records. You specify ;SUBSET=29:33 because FCOPY sees the first record in a file as record number 0.
FCOPY Operation The example below describes an output file name outfile for an FCOPY command. ;TO=outfile FCOPY Functions In addition to specifying input and output files in an FCOPY command, you also describe the FCOPY functions that you want to perform. Each function has its own syntax and guidelines for its use. The NEW function, for example, lets you create a new disk file.
FCOPY Operation Table 8-1 FCOPY Functions (Continued) Function Description NOUSERLABELS Omits user labels when copying between disk and tape. OCTAL Displays the contents of a file in octal form. SKIPEOF Positions a serial storage device at a desired file. SUBSET Copies a subset of a file. UPSHIFT Converts lowercase characters to uppercase. VERIFY Compares files after copying.
FCOPY Operation General Guidelines for FCOPY Commands An FCOPY command must follow these general guidelines: • Semicolons always separate the different components of a command. You can leave spaces between components. However, there can be no more than 70 characters between two semicolons. For example, all three FCOPY commands below are valid.
FCOPY Operation Using FCOPY with KSAM Files To FCOPY from an old compatibility mode KSAM file to a new compatibilty mode KSAM file enter: FCOPY FROM=OLDFILE;TO=(DATAFILE,KEYFILE) OLDFILE is the old compatibility mode KSAM data file. DATAFILE is the new compatibility mode data file and KEYFILE is the new compatibilty mode key file. The new key and data files are constructed for you with exactly the same structure as the old key and data files. The ;NEW option need not be used.
9 FSCHECK The file system check utility (FSCHECK) is a native mode program used to detect and repair inconsistencies found in the file directories and file label tables of the MPE/iX operating system and to display the file extent map. It is a standalone utility and should be the only program running on the system when it is in use. FSCHECK also provides a consistent MPE/iX subsystem interface, including LISTREDO, REDO, DO, USE, DEBUG, and LOG functionality.
FSCHECK Operation CHECKDIRC [CD] The CHECKDIRC command checks the directory on the specified volume set for internal consistency and makes sure that for each directory entry there exists an associated file label entry. This command assumes that all volumes of the identified volume set are mounted and available and that the system is fully operational.
FSCHECK Operation CHECKEXTENTS [CE] The CHECKEXTENTS command checks the extent map for each file label in the label table for duplicate extent descriptors. Duplicate extent descriptors are those with overlapping file sector offset. Syntax CHECKEXTENTS ldev [DEV=] set_name ALL Parameters The DEV parameter is optional. If omitted, the default is to check the extent maps on each mounted volume of the system volume set.
FSCHECK Operation CHECKLABEL [CL] The CHECKLABEL command checks the label table(s) on the specified volume(s) for internal consistency and verifies that each file label entry has an associated entry in the volume set’s directory. It does not verify the integrity of HFS-syntax files whose file names are blanked out in the file label. If neither the CNAME or VNAME parameter is specified, the label table of each volume in the sytem volume set is checked by default (MPEXL_SYSTEM_VOLUME_SET).
FSCHECK Operation CHECKFILE [CF] The CHECKFILE command checks the label of the specified file for internal consistency. Syntax CHECKFILE [FILENAME=] filename Parameters Specifies the name of the file to be checked. The file name can be an MPE/iX file name of the form filename[.group][.account] or it can be a fully-qualified HFS pathname. You may use wildcard characters that conform to MPE/iX convention, to specify the file, group, and account names. filename Examples fscheck: CHECKFILE @.PUB.
FSCHECK Operation DEBUG The DEBUG command invokes the native mode system. Syntax DEBUG Parameters None Example fscheck: DEBUG Return DISPLAYLABEL [DL] The DISPLAYLABEL command displays the fully qualified file name and offset within the label table for each file label entry of the label table on the specified logical device. Syntax DISPLAYLABEL [DEV=] ldev set_name ALL Parameters DEV= DEV= is an optional keyword for the parameter.
FSCHECK Operation DISPLAYEXTENTS [DE] This command displays the extent map for the specified file. For each extent of the file, it displays the number of sectors in the extent, the single vector disk sector address (in hex), the file sector offset (in hex), and the volume set index of the volume on which the extent resides. Currently the file name must be fully qualified, that is, with the group and the account names specified.
FSCHECK Operation DO [CMD=] cmd_id Parameters Cmd_id identifies a particular command in the command line history stack. It can be a number relative to the last command (-n), an absolute number (n) identifying the particular command, or a string used to match a particular command in the stack. cmd_id Example fscheck: DO CMD=-2 Return EMPTYSLOUGH [ES] Removes all extents from the slough file without attempting to deallocate the secondary storage owned by its extents.
FSCHECK Operation EXIT [E] This command terminates the FSCHECK utility and returns to the process from which it was invoked. Syntax EXIT Parameters None Example fscheck: EXIT Return EXTENTDISTRIB [ED] Displays the distribution of extents by extent size or file size on the specified volume(s). If you choose the EXTENT option, FSCHECK displays the total number of extents that falls in the extent size range.
FSCHECK Operation Parameters None Example HELP Return LISTREDO This command displays the contents of the command line history stack, from the least recently entered command to the most recently entered command. It is identical in function to the LISTREDO command. Syntax LISTREDO Parameters None Example fscheck: LISTREDO Return LOG This command logs the user or program dialog to the specified file, as it appears to the user.
FSCHECK Operation PURGEFILE [PF] This command purges the specified file. Syntax PURGEFILE [FILENAME=]filename Parameters Specifies the file to be purged. The file name may be an MPE/iX file of the form filename[.group[.account]], or it may be a fully qualified HFS pathname. filename Examples fscheck: PURGEFILE TEMP.PUB.SYS Return fscheck: PURGEFILE /sys/dir1/myfile Return REDO This command edits and re-executes a command from the command line history stack.
FSCHECK Operation Parameters The DEV parameter is optional. If omitted, the default is to synchronize the account and group directories of the system volume set. set_name Set_name is the name of the volume set whose directories are to be synchronized. The volume set must be opened. (The set’s master volume must be mounted in the MASTER state as displayed by the DSTAT command). QUIET QUIET specifies that the list of accounts and groups processed should not be displayed on the $STDLIST device.
FSCHECK Operation UNLOCKFILE [UF] MPE/iX locks files whose extents contain bad sectors. This command unlocks a locked file so that it can be purged or analyzed. Syntax UNLOCKFILE [FILENAME=] filename Parameters Filename is the fully qualified name of the file to be unlocked. filename Example fscheck: UNLOCKFILE AFILE.BGROUP.CACCT Return USE This command reads and executes commands contained in the specified file.
FSCHECK Operation 116 Chapter 9
10 I7DB8CNV I7DB8CNV converts the character data in an IMAGE database from any Hewlett-Packard 7-bit national substitution set to ROMAN8. The program is a special version of the DBLOAD.PUB.SYS program, and the conversion is done as part of a database load. Operation To run I7DB8CNV, do the following: 1. Enter RUN DBUNLOAD.PUB.SYS to unload the database to tape: 2. Enter RUN DBUTIL.PUB.SYS,ERASE to erase the database data. 3. Enter RUN I7DB8CNV to convert the data and reload it into the database.
I7DB8CNV Operation 7. ESPANOL 8. ESPANOL M 9.
11 LANGINST The LANGINST utility builds and modifies the LANGDEF.PUB.SYS file, which contains all language-dependent information for every language that the system manager plans to configure. LANGINST gathers data from the NLSDEF.PUB.SYS and CHRDEFxx.PUB.SYS files and writes it to LANGDEF.PUB.SYS. The system manager uses the LANGINST utility to: • Add a language to the configuration file. • Remove a language from the configuration file. • Display and modify local formats of a configured language.
LANGINST Operation Operation The system manager initiates the LANGINST utility by entering: LANGINST When the LANGINST main menu appears, you choose one of the following functions: 0. 1. 2. 3. 4. 5. 6. 7.
LANGINST Operation • The addition continues if a language is requested that is supported but has not been previously configured. LANGINST configures the language and displays a message. 2. When the addition is completed, the LANGINST main menu is displayed. Deleting a Language LANGINST allows the system manager to delete any configured language except NATIVE-3000 (which is hard-coded and therefore always configured) and the system default language.
LANGINST Operation • • The modification is aborted if one of the following conditions is met: • Entering a language that is not configured on the system. • Entering NATIVE-3000. • Pressing Return. The modification continues if the language requested is configured. 2. If a configured language is entered, the user dialog is displayed: 1. Long calendar format 2. Date format (Calendar format) 3. Custom date format (Short) 4. Time format (Clock format) 5. Currency sign 6. Currency name 7.
LANGINST Operation After you have made changes to the file, a new copy of it is saved under the name LANGDEF and the old (unchanged) version of the file is saved under the name LANGDxxx. The number xxx increases by one each time a new copy of LANGDEF is saved. This allows the user to return to a configuration that existed before LANGDEF was changed. To return to the previous configuration, PURGE or RENAME the current LANGDEF then RENAME the LANGDxxx with the highest number LANGDEF.
LANGINST Operation * There are two ASCII characters mapping to the same EBCDIC character. ** Change the mapping of C8 to its new EBCDIC value. To display the translation tables, return to the main menu and enter option 7. Then enter the language ID number and the table you want to display.
LANGINST Operation Modifying 16-Bit Asian ASCII/EBCDIC Translation Tables To modify the 16-bit Asian ASCII/EBCDIC translation tables for any language other than NATIVE-3000, select option 3 from the LANGINST main menu. When the Modify Native Formats menu is displayed, enter: 1. The language name or language ID number. • • The modification is aborted if one of the following conditions is met: • Entering a language that is not configured on the system. • Entering NATIVE-3000. • Pressing Return.
LANGINST Operation The current default translation value is Enter the new value (HEX please) 0000 : 0000 Input Asian character (HEX please) : c1c4 Current translation value is (in HEX) : 0000 Input new translation value (HEX please): a1a1 (*) (*) Input Asian character (HEX please) : a1b2 Current translation value is (in HEX) : 4FE3 Input new translation value (HEX please): 4fe3 (*) (**) (***) Input Asian chracater (HEX please) (****) : 00a5 *** The character (00a5) is not defined.
LANGINST Operation Table 11-1 LANGINST Error Messages Message Cause Action A NONNUMERIC GRAPHIC CHARACTER IS EXPECTED... An alphabetic or special character (not numeric) is expected. Enter a valid character. ATTEMPTING TO ADD TOO MANY CHARACTER SETS. Adding this language would exceed the maximum configurable character sets. Do not configure languages from so many character sets. BUILDING AN EMPTY LANGDEF ... There was no existing LANGDEF file; a new, empty one is being built. None.
LANGINST Operation Table 11-1 LANGINST Error Messages (Continued) Message Cause Action langname IS NOT CONFIGURED. The language selected is not configured on the system. Add the language to the list of currently configured languages with this program. langname IS NOT IN THE CHRDEF FILE. One of the CHRDEFxx files is not consistent with the NLSDEF file. Restore all CHRDEFxx files and NLSDEF from your master backup. NATIVE-3000 IS ALWAYS CONFIGURED.
LANGINST Operation Table 11-1 LANGINST Error Messages (Continued) Message Cause Action THERE IS NO MORE ROOM FOR ADDITIONAL DATE PERIODS. PLEASE REPORT. There is no room for additional entries in the national date table. Contact your Hewlett-Packard representative. TOO MANY LANGUAGES HAVE BEEN CONFIGURED. Adding another language would exceed the maximum configurable languages. Don’t configure so many languages on one system. UNABLE TO RENAME LANGDEF TO LANGDnnn.
LANGINST Operation 130 Chapter 11
12 LINK EDITOR/XL Use LINK EDITOR/XL to prepare native mode (NM) compiled object modules. The LINK EDITOR process resolves all external references which cannot be resolved at run-time. A compiled object module (program file) which has not been link edited will not run. You may also use LINK EDITOR/XL to create and maintain relocatable and executable libraries. To prepare and manipulate edit compatibility mode (CM) program files and libraries use the SEGMENTER utility.
LINK EDITOR/XL Operation Commands The following tables list LINK EDITOR/XL commands in alphabetical order within function. Table 12-1 COMMAND Miscellaneous Link Editor/XL Commands DESCRIPTION EXIT Quits an interactive Link Editor session. LINK Creates an executable program file. LISTOBJ Lists the contents of an object file. The listing shows the symbols contained within the file. LISTPROG Lists the contents of an executable program file. The listing shows the symbols contained within the file.
LINK EDITOR/XL Operation Table 12-3 XL Link Editor Commands COMMAND DESCRIPTION ADDXL Adds all object modules from an object file or a relocatable library to an executable library. BUILDXL Builds and initializes a new executable library. This library becomes the current executable library for subsequent interactive commands. CLEANXL Rebuilds an executable library by removing any fragmentation and leaving room for 25% expansion within its internal tables.
LINK EDITOR/XL Operation 134 Chapter 12
13 LOGTOOL The System and Memory Log Analysis Tool (LOGTOOL) lets you display and manage system log files and the memory log file. System log files contain information generated by the operating system. The memory error log file contains memory error information gathered by the memory error logging process MEMLOGP. You can request that the operating system keep records of certain users as well as particular events. To keep a certain type of log, change its status to ON using SYSGEN.
LOGTOOL Operation 5. If necessary, display logfile record types. (You may skip this step if you already are famililar with types) : LOGTOOL> TYPES 6. Display the analysis for specified logfiles as a formatted list. SYSDIAG>LIST LOG=9/14,17,20,22;TYPE=111,146 You may enter the LOG parameter as a range of numbers such as 9/14, as a string of numbers such as 17,20,22, or as a combination range and string.
LOGTOOL Operation COMMAND SUMMARY There are three categories of LOGTOOL commands: System Log File Commands (SLF), Memory Log File Commands (MLF), and Miscellaneous Commands (MC). They are briefly described in the following table. Table 13-1 Name LOGTOOL Commands Category Description DISPLAYLOG (SLF) Displays I/O entries as information is logged. EXIT (MC) Exits LOGTOOL and returns user to DUI. HELP (MC) Gives help on running LOGTOOL. LAYOUT (SLF) Reads in a layout file.
LOGTOOL Operation Logging system events The following list shows the types of system log events that you can track. To do so, you enable a log event by turning it ON in SYSGEN.
LOGTOOL Operation Table 13-2 SYSGEN System Logging (Continued) System Log Events Event Type Maintenance request log 146 UPS Monitor event logging 148 Diagnostic information record 150 High-priority machine check 152 Low-priority machine check 152 Directory open/close logging 155 CM file close record 160 Chdir 161 Process Adoption 162 File Owner Change 163 All log information is kept in records.
LOGTOOL Operation 140 Chapter 13
14 MKNOD The MKNOD utility lets you create device link files, streams files, and fifo files. The security restrictions enforced with MKNOD are as follows: • To create a streams file, you must have either SM or NM capability. • To create a device link file, you must have SM capability. • To create a fifo device file, you must CD access to the directory in which you're creating the file.
MKNOD Operation Operation MKNOD determines how to create the files based on the arguments passed to the program. When creating a device link or streams (character-type) file, you must enter both the major and minor numbers. To create a device link file, enter a major number of 0 and the LDEV number of the device as the minor number. To create a streams file, enter a major number greater than 0.
MKNOD Operation 128W 128W 128W FBf FBs FBd 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 * MYFIFO * STRMFILE * tape7 :LISTFILE /dev/tape7,5 ********************** FILE: /dev/tape7 FILE CODE : 0 BLK FACTOR: 1 REC SIZE: 256 (BYTES) BLK SIZE: 256 (BYTES) EXT SIZE: 0 (SECT) NUM REC: 0 NUM SEC: 0 NUM EXT: 0 MAX REC: 1 NUM LABELS: MAX LABELS: DISC DEV #: SEC OFFSET: VOLNAME : DEV TYPE LDEV FOPTIONS: BINARY,FIXED,NOCCTL,DEVICE LINK OWNER : ** GROUP ID: ** SECURITY--READ : WRITE : APPEND : LOCK : EXECUTE: **SECURITY IS O
MKNOD Operation 144 Chapter 14
15 N7MF8CNV N7MF8CNV converts data in EDIT/XL and other MPE text and data files from a Hewlett-Packard 7-bit national substitution character set to ROMAN8. Operation N7MF8CNV prompts you for language and file type (text or data). For each data file, you enter the starting position and length of each field (portion of a record) to be converted. For a text file, each record is converted as one field. The user is prompted for the name of each file to be converted.
N7MF8CNV Operation A CTRL Y entered during conversion displays the number of records successfully converted, and conversion continues. On variable length data files, if a field or portion of a field is beyond the length of the record just read, a warning is displayed and that field is not converted on that record. Other fields on the same record are converted, and processing continues with subsequent records. After each file has been converted, the user is prompted for another file name.
16 NLIOUTIL The NLIOUTIL utility dynamically activates the Native Language I/O (NLIO) subsystem for Asian and Middle East/African terminals and printers. (NLIO is the basic input and output system integrated into MPE/iX for Native Language Support NLS.) Once activated by NLIOUTIL, properly configured native devices may use the Native Language I/O facility.
NLIOUTIL Operation HELP Command The HELP command shows the usage of each of the NLIOUTIL commands. HELP [HELP | OPEN | SHUT | SHOW | EXIT | END | E ] OPEN Command The OPEN command is used to start the NLIO service for a specified device with a specified language. OPEN [nliodevice] [,lang_id] [;RECCONV | ;NORECCONV] [;LATIN | ;NONLATIN] [;WIDTH=length] [;SHAPE=shape_mode] nliodevice is the ldev or device class name.
NLIOUTIL Operation SHOW Command The SHOW command displays the status of the NLIO service for a specified device. SHOW [nliodevice] nliodevice is the ldev or device class name. If the nliodevice is ommitted, the current stdin device is assumed when it is an interactive device. System Supervisor (OP) capability is required to specify devices other than your own stdin. The "at" sign (@) can be specified to designate all devices that are currently opened.
NLIOUTIL Operation 150 Chapter 16
17 NLUTIL The NLUTIL utility lets you verify the Native Language Support (NLS) Languages and character sets available on the system. Operation To display a table showing the currently configured languages and their character set types, enter: NLUTIL or RUN NLUTIL.PUB.SYS NLUTIL displays information in columnar format and then prompts you to request a full listing.
NLUTIL Operation 152 Chapter 17
18 PATCH The PATCH utility accesses, displays, and/or modifies a compiled, prepped executable modules. You may make simple changes to program instructions or to global stack area variables with this utility. You may use PATCH on compatibility mode programs only. Before using this utility you should be familiar with machine-executable instructions and the internal format of executable modules in the HP3000 system environment.
PATCH Operation When the file name is accepted, PATCH displays the ? prompt, where you enter one of the following four subcommands: D Displays code segment contents. M Modifies code segment contents. DG Displays global area of initial stack. MG Modifies global area of initial stack. After each command, PATCH prompts you for another. To terminate PATCH press Return without entering a command. (An incorrectly entered command also terminates PATCH.
PATCH Operation When you enter the M command, the contents of the current instruction are displayed followed by a comma. To leave the value unchanged, you must re-enter the contents! If you press RETURN without entering anything the instruction will be set to zeros (%000000, a NOP instruction). For a list of segment names and their addresses within a program file use the PMAP option of the PREP command.
PATCH Operation Parameters reloffset The DB-relative offset of the word to modify, found in your compiler listing. numwords The number of words, in octal, that you wish to modify. The default is one. The MG command displays the contents of the current stack word, followed by a comma. To leave the value unchanged, you must re-enter the contents! If you press RETURN without entering anything the word will be filled with zeros.
PATCH Operation The following changes the zeros displayed above to the values shown after each comma: ?MG,0,5 000000,112 000000,52 000000,64 000000,264 000000,464 The following displays the first changed value: ?DG,,1 000112 Additional Discussion For more information on PREP command refer to the MPE/iX Commands Reference Manual V. For more information on User Subprogram Library (USL) files refer to the MPE Segmenter Reference Manual.
PATCH Operation 158 Chapter 18
19 PXUTIL The system manager uses the PXUTIL utility to perform operations related to the UID and GID databases. These include: • creating the UID and GID databases • synchronizing existing UID and GID database files with the current directory PXUTIL requires exclusive access to the databases. This means that any command that needs to modify these files (such as NEWACCT, ALTUSER, and so on) fails during PXUTIL operations.
PXUTIL Operation Operation You can invoke the PXUTIL utility from a session or job. It requires SM capability. It is breakable except for the period during which either old database files are being purged or new ones are being saved. The PXUTIL utility supports the following four commands: • UPDATE • HELP (H) • QUIT (Q) • EXIT (E) Each of these commmands is explained on the following pages.
PXUTIL Operation RUN PXUTIL.PUB.SYS MPE/iX PXUTIL A.00.01 Copyright (C) Hewlett-Packard 1991. All Rights Reserved. PXUTIL> update User and group databases sucessfully created. PXUTIL> quit Below is a typical invocation and operation of PXUTIL when the databases previously exist. Note that users that were added to the database are displayed. (Refer the commands section for more information on the UPDATE command.) MPE/iX PXUTIL A.00.01 Copyright (C) Hewlett-Packard 1991. All Rights Reserved.
PXUTIL Operation 162 Chapter 19
20 SAINT The Standalone Initialization Utility (SAINT) is an interactive utility program that analyzes system libraries (which contain system object modules, or SOMs) to produce executable images known as boot images. A bootable image is a file that can be copied directly to memory and executed without modification. The SAINT utility’s primary function is to produce a boot image for the operating system. The input file upon which the SAINT utility is primarily dependent is the system library file.
SAINT file offset A byte offset relative to the beginning of the file. virtual offset A byte offset relative to the beginning of the space. space offset The same as virtual offset. Preparation for use To bring up the operating system, the START boot image contains the code that builds the required software structures and initializes the various components of MPE/iX, such as the virtual space manager, memory manager, IPC, compatibility mode emulator, and so forth.
SAINT Operation Operation WARNING Do not use this utility without service center support. Unauthorized use will void your warranty and may cause data loss. The boot sequence expected by the boot image is described below: 1. IPL locates the START file in the LIF directory and reads the first 128 words of that file, which is the operating system boot image. 2. When the file has been identified as a valid bootable image, the file is booted into physical memory. 3.
SAINT Operation BUILDPME This command creates the permanent boot image from the internal data structures (symbol tables, code arrays, and so on.) built by the SAINT utility in previous load commands. These data structures keep track of the information designated by the load commands previously invoked in this SAINT utility session. Syntax BUILDPME bootimagename [,SXRT] Parameters bootimagename The name of the boot image file. This parameter is required.
SAINT Operation Parameters symbolname The symbol to be found in the symbol table. This parameter is required. filename The name of the boot image file. The default is the currently built boot image. Example FINDSYM system_abort,start.abuild01.official HELP This command displays a list of the SAINT utility commands in alphabetical order, plus a short description of each command’s syntax and function.
SAINT Operation Syntax LOADMILLI filename Parameters The name of the SOM file containing the system macros. This parameter is required. filename Example LOADMILLI foobar LOADSXRT This command opens the system cross-reference table declaration file (DSXRT), to be used when the SXRT is built by the BUILDPME command. The file is used to build the first section of the SXRT, which continues entries for all system entry points used by switches for CM.
SAINT Operation Example LOADSYSLIB nl.abuild00.official MAP This command generates a map of the boot images symbol table. It describes the location of the major components of the boot image. In addition, a flag in the command’s parameter list turns on the display of symbolic information obtained from the library symbol tables contained within the boot image. Syntax MAP [filename[,radix[,sym]]] Parameters filename The name of the boot image file used to generate the map and symbol table.
SAINT Operation ACTION You may try and use the PME or change the linker commands used to build the NL that is the source of the PME. The linker commands that affect the location of the pages are the limit option on the buildxl command and the cleanxl command. Internal ERROR. Attempt to read or write with index < 0 CAUSE SAINT has attempted to read or write a file using an invalid index. This is an error in an input file or an internal error.
SAINT Operation Enter an SR describing the problem. Send supporting material: A store tape with a copy of all files used as input to SAINT, (NL, CME, DSXRT, EXTMILLI) a copy of the PME written, and the SAINT program. An SXRT file has not been defined CAUSE The buildpme command has been entered with the sxrt option and the loadsxrt file command has not been entered. ACTION Enter the "loadsxrt file" command specifying a valid DSXRT file.
SAINT Operation 172 Chapter 20
21 SLPATCH The SLPATCH utility accesses, displays, and/or modifies segmented library (SL) files. Before using this utility, you should be familiar with machine-executable instructions and the internal format of segmented library files in the HP3000 system environment. CAUTION Chapter 21 SLPATCH bypasses normal MPE/iX safeguards and will modify the contents of privileged SL’s. It is therefore possible to corrupt the SL or the entire operating system.
SLPATCH Operation Operation To invoke SLPATCH enter: SLPATCH or RUN SLPATCH.PUB.SYS SLPATCH responds with the following and displays ? to prompt you for the SL file name you wish to work on. Enter the file name in the form: filename[.groupname[.acctname]], and use all uppercase letters. For example: SLPATCH A.43.11 (C) HEWLETT-PACKARD CO., 1976 SL FILE? SL.PUB.HITECH When SLPATCH accepts the name of the segmented library file, it displays another ? to prompt you for a segment name and a command.
SLPATCH Operation NOTE To find the segment displacement, add the instruction offset (generally found in the compiler listing) to the starting address of the procedure (supplied by the PMAP option of the PREP command). For information regarding the offsets of instructions in program files, refer to compiler options for the programming language in which the code was written. SLPATCH Example Invoke SLPATCH and enter the SL name. For example, if the name of the segmented library file is SL.PUB.
SLPATCH Operation 176 Chapter 21
22 SOMPATCH Use the SOMPATCH utility for binary modification of a native mode spectrum object module (SOM) program or library file. Binary modification is referred to informally as patching. WARNING Do not use this utility without service center support. Unauthorized use will void your warranty and may cause data loss. This utility is capable of tracking all of the modifications that it makes to a SOM file.
SOMPATCH The SOMPATCH utility sets two JCWs: the system JCW and a private JCW, PATCHJCW. PATCHJCW is set as follows: No error -- value of 0 Nonfatal error -- value of 1 Fatal error -- value of 2 Really fatal -- value of 3 (Program will gracefully abort.) Under these error conditions, the SOMPATCH utility also sets the system JCW to the standard MPE values, OKAY, WARN, and FATAL. Preparation for Use Patching modifies object code when a problem cannot be easily or conveniently fixed in source code.
SOMPATCH Operation Operation The MPE/iX command interpreter includes the implied RUN concept, which allows the user to invoke a program merely by naming it. For the SOMPATCH utility, type sompatch[.group[.account and then specify a string of parameters (enclosed in quotes) before typing Return. The program file is searched according to the CI variable HPPATH. Currently, the SOMPATCH utility is stored in PUB.SYS.
SOMPATCH Operation When using a patch file, specify a list file, so that if the JCW is FATAL after the SOMPATCH utility executes, the list file can be examined to determine the problem. In the following examples, the patch file is pat0511 and the list file is lpat0511. sompatch "nl.abuild00.official lpat0511" OR sompatch "nl.abuild00.
SOMPATCH Operation Syntax ; text Parameters The ASCII text describing the problem and why the patch fixes it. text Example ;no_op call to check_for_overflow to prevent system error ;#2099 on bootup. ;source fix anticipated in SEL CORE release C.06 BACKOUT This command returns a file previously patched to an unmodified state. It is possible to undo a patch if the patch ID given in the LOG command used to apply the patch is known. This number can be seen in the output of the SHOW [BACKOUTS] command.
SOMPATCH Operation Example backout :12 This example shows 12 as the patch ID specified with the LOG command. backout file=patchfle.pub This example shows that all patches applied under patchfle.pub are to be removed. Error Messages No patchfile as given. CAUSE The FILE= option specified a script file that was not used on this file. The FILES option on the SHOW command indicates what files have been used. ACTION Specify the correct file. No patchid as given.
SOMPATCH Operation The display is sent to $STDLIST. The parameter symbolname may be entered in uppercase or lowercase or mixed case, unless it is defined in a C procedure, in which case it must be entered in the specific case in which it is listed out from the linker. If the symbol starts with an underbar, that should be entered as the first character.
SOMPATCH Operation Example The following example displays ‘trap_handler$248$set_up_user_trap :find @set_up_user_trap HELP This command displays a summary of commands, including syntax and options. Syntax HE[LP] Parameters None LIST This command causes the SOMPATCH utility to open an output list file. Syntax LI[ST] filename Parameters filename The output list file name. If you omit the group and account, SOMPATCHcreates the file in the logon group and account.
SOMPATCH Operation Syntax LO[G ] username ,patchid [,srnumber] Parameters username An ASCII string that gives the name of the person installing the patch and the name of the patch creator, if it is not the same person. The string is terminated by a comma, but can include other non-alpha characters. patchid The identification code from the patch management system. It is parsed as a string and is terminated by a comma. Blanks are ignored. srnumber The SR number that this patch is fixing.
SOMPATCH Operation Syntax MO[DIFY] [symbol][+/-off][,count] [?mode] [oval] nval ...‘lb‘ Parameters symbol Specifies the name of the associated level 1 symbol. This is normally a CODE type symbol, but SOMPATCH accepts a DATA symbol. If the symbol has duplicates (that is, the same name is used more than once in a multi-SOM library), the SOM command must be used to tell SOMPATCH which SOM to look in for the desired symbol. If the symbol is not specified, absolute addressing from 0 is assumed.
SOMPATCH Operation sp>modify iobuf+10 2154#### FFFFFFFF Return {only check upper 16 bits} Also refer to the "Operation" section for an example of this command. Error Messages Symbol symbolname not found. CAUSE PATCHJCW is set to the FATAL condition. ACTION Change the PATCHJCW setting. Old value is not as specified. CAUSE The old value is displayed, and PATCHJCW is set to the FATAL condition. ACTION Specify the old value. Illegal syntax--use help. CAUSE PATCHJCW is set to the FATAL condition.
SOMPATCH Operation PATCHFILE This command causes the SOMPATCH utility to generate a patch file from the patches in the main input file. It generates a patch file from the patch information in the ypatch areas in the SOM(s) in the main input file. If there are no patches, a file containing a few lines of header is generated. If there are no ypatch areas, an error message is generated. Syntax PA[TCHFILE] filename Parameters Filename is the file to be generated.
SOMPATCH Operation In pre-releases of MPE XL, the installation procedures may not clearly define the proper use of the CLKUTIL utility. In this case, the system clock may not be correctly set, and the time of patch shown may be the Greenwich Mean Time, rather than the local time.
SOMPATCH Operation Illegal date specified--syntax YYMMDD. CAUSE The date as specified, with defaults, is not a legal date. ACTION Supply a date with the correct syntax. Symbol not found. CAUSE The symbol given in symbolspec was not in the symbol table for the file being queried. ACTION Use a correct symbol. SOM This command causes the SOMPATCH utility to look only in the specified SOM for symbols. There are no SOM errors when parameters are entered as specified. Remember to start indexing from zero.
SOMPATCH Operation | | -----------------------ProcA + 00xx-->| Proc B’s Level 2 code| | | ProcB + 0000-->-----------------------| | | Proc B -- Level 1 | ------------------------ <-- code being patched The patch instruction may have the following syntax, but the second represents the preferred method: 1) Modify ProcA + 00xx Modify ProcB - 00yy OR 2) (Where ProcA + xx + yy = ProcB) When the multi-SOM NL is linked, the two relocatable object files are sometimes no longer congruent.
SOMPATCH Operation VERSION This command gives the current SOMPATCH utility version. It is used to show the version of the SOMPATCH utility that is being run. The version is also printed on the list file and as part of each patch written to the ypatch area.
SOMPATCH Operation Syntax VE[RSION] Parameters None Example sp> VERSION Return Sompatch Version A.00.
SOMPATCH Operation 194 Chapter 22
23 SORT-MERGE/XL SORT-MERGE/XL allows you to sort files by single or multiple key fields and to merge two or more sorted files into a single new sorted file. You may use SORT-MERGE/XL as a standalone utility (either interactively or in batch mode), or from within a program. For information on how to use SORT-MERGE/XL programmatically, refer to the SORT-MERGE/XL Programmer’s Guide. Operation Using SORT To invoke the sort portion of SORT-MERGE/XL enter: SORT or RUN SORT.PUB.
SORT-MERGE/XL Operation MERGE or RUN MERGE.PUB.SYS SORT-MERGE/XL responds with a display similar to: HP31900A.01.01 MERGE/V TUE, JAN (C) HEWLETT-PACKARD CO. 1987 2, 1990, 3:54 PM It then presents a > prompt. At this prompt you must supply INPUT file(s) an OUTPUT file and SORT key(s). For example: > > > > INPUT INFILE1, INFILE2,... INFILEN OUTPUT OUTFILE KEY 1,12 END You may enter the parameters in any order. However, you must specify the keywords INPUT, OUTPUT and KEY.
24 SPIFF Use the Native Mode Spool File Interface Facility to list, manipulate, and transfer spooled device files (spoolfiles) that are created and maintained by MPE/iX. SPIFF replaces the CM SPOOK program. SPIFF supports many of the commands of the SPOOK program, and has also been enhanced with the following features: • Access to the MPE/iX Command Interpreter. • Case insensitive FIND, which you may set as the default. • Native mode output display. • No LOCKED state for spool files.
SPIFF Operation Operation To run the Native Mode Spooler Utility, enter SPIFF. You will see an identifying banner and the > prompt, like this: SPIFF A.00.00 (C) COPYRIGHT HEWLETT-PACKARD CO. 1993 > Once you see the prompt, you may enter any of the commands described on the following page. Table 24-1 COMMAND SPIFF Commands DESCRIPTION ALTER Alters the priority, number of copies, target device, or any combination of these attributes, of one spoolfile or many spoolfiles.
SPIFF Operation SPIFF recognizes only the first letter of the full form of the command (F or FIND in the above example), except for APPEND and STORE. The abbreviations for these two commands require two letters (AP, ST) to distinguish them from the ALTER (A) and SHOW (S) abbreviations, respectively. File Definitions SPIFF opens the formal file designator SPUTIN as its $STDIN(X) and the formal file designator SPUTOUT as its $STDLIST. You may redirect these files as desired with a file equation.
SPIFF Operation 200 Chapter 24
25 STANDARDS The system bootstrap, initial program load (IPL) and initial system load (ISL) standard provides a standard interface through which any Hewlett-Packard Precision Architecture (PA-RISC) computer can boot any operating system. The standard also provides a common user interface for booting PA-RISC systems. WARNING Do not use this information without service center support. Unauthorized use will void your warranty and may cause data loss.
STANDARDS The initial system loader The initial system loader The Initial System Loader performs these functions: • provides user interface with boot path information and alters boot path. • loads an operating system-specific code set or a hardware-specific code set and launches it. If this implementation-specific code does not damage the ISL image, ISL remains in memory in case the code returns control to ISL for initialization of further utilities.
STANDARDS The initial system loader A detailed internal representation of a boot or console path (the format applies to the auto bootpath, the alternate boot path, the dump path, and the console path) is as follows: Table 25-2 Boot or console path 0000 flags BC(0) BC(1) BC(2) 0004 BC(3) BC(4) BC(5) MOD 0008 Logical_ID 000C Device_Depend 001F 0020 Note that in the above illustration, the flags field in the console path is ignored.
STANDARDS The initial system loader NVM is an optional implementation, not required by the architecture.
STANDARDS The initial system loader The following drawing represents the LIF standard logical layout of disk and tape media.
STANDARDS The initial system loader The LIF volume label allows easy identification of media type and gives the location of the directory.
STANDARDS The initial system loader Each directory is organized as follows: Table 25-7 LIF addressing BYTE CONTENTS 0-9 File name (1-10 ASCII characters, trailing blanks) 10-11 File type 12-15 Starting address (in blocks) 16-19 Length of file (in blocks) 20-25 Time of creation 26-27 1 /volume number 28-31 Set to 0 (implementation) The file type is a 16-bit signed integer.
STANDARDS The initial system loader All software implementation intends to support the system object module (SOM) format, using the linker; therefore, an auxilary SOM header for IPL, as described below, would meet IPL’s needs for loading and launching bootable utilities. For further description of the linker and the SOM format, refer to the System Linker External Specifications and the System Object File Format Architectural Control Document.
STANDARDS The initial system loader Figure 25-2 Chapter 25 Boot utility format 209
STANDARDS The initial system loader Main Memory Layout Although the exact memory locations of boot and IPL code during the boot process vary according to size of the IODC and IPL, a general description of memory layout is presented here for clarification. Also, the first page of main memory is reserved for communication between PDC and software.
STANDARDS The initial system loader The format of the console terminal and boot device configurations are as follows: Table 25-9 Console terminal and boot device configuration X’00 path 00 X’08 LAYERS 08 X’20 HPA 322 X’24 SPA 36 X’28 IODC_IO 40 X’2C Reserved 44 X’30 Class 48 The format of the boot and system console device paths is the same as that for the autoboot, alternate boot, and console paths in stable storage. In the console path, the flags are ignored.
STANDARDS The initial system loader 212 Chapter 25
26 SYSMAP SYSMAP maps the hardware configuration of I/O devices, CPU boards and memory boards. Operation To invoke SYSMAP enter: SYSDIAG DUI> RUN SYSMAP SYSMAP is part of the Online Diagnostics Subsystem. To use this utility, start the diagnostic subsystem by entering SYSDIAGand at the DUI> prompt, enter RUN SYSMAP.
SYSMAP Operation 214 Chapter 26
27 tic The tic utility compiles the terminfo source file. Operation The tic utility compiles source terminfo descriptions. The compiled entry is installed under the /usr/lib/terminfo directory hierarchy. If the TERMINFO environment variable is set, results are placed in the directory it points to instead. Entries are stored in directories that match the first character of their name. The entry for the VT-100 terminal, for example, is stored in /usr/lib/terminfo/v/vt100.
tic Operation 216 Chapter 27
28 TERMDSM TERMDSM is part of the Online Diagnostics Subsystem and is used to diagnose, dump, and reset logical devices, ports, and distributed terminal controllers. It also performs status checks of ports and DTC’s.
TERMDSM Operation Comment Comment allows comments to be entered for later reference. Security level is 2. DIag DIag is entered to run diagnostic functions.
TERMDSM Operation Reset Reset resets a DTC, SIC or port. When the Reset command is entered the system responds with the following: (reset) Ldev # POrt #,#,# SIc #,# (multiplexer card in DTC) DTc # (carriage return to exit) ? Parameters are DTC, SIC and port for POrt and DTC and SIC for SIc. Other parameters are as indicated. Security is 1 for Ldev’s and ports; 0 for DTC’s or SIC’s. CAUTION Active sessions are logged off reset devices. Status STatus displays information about the DTC or port.
TERMDSM Operation 220 Chapter 28
29 untic The untic utility decompiles the terminfo binary file. Operation The untic utility decompiles a terminfo binary file into its source format. If a TERMINFO environment variable is set, the untic utility searches the specified directory; otherwise, untic assumes the file is in the directory /usr/lib/terminfo. The output of an untic decompile is sent to the standard output. Syntax untic.hpbin.
untic Operation 222 Chapter 29
30 V7FF8CNV V7FF8CNV converts text and literals in VPLUS/XL forms files from a Hewlett-Packard 7-bit national substitution character set, to ROMAN8. V7FF8CNV is a special version of FORMSPEC.PUB.SYS and is run the same way. Operation 1. Use the STORE command or SYSGEN to back up the forms file. 2. Configure your terminal for 8-bit operation. Refer to the System Startup, Configuration, and Shutdown Reference Manual for information on peripheral configuration. 3. RUN V7FF8CNV.PUB.
V7FF8CNV Operation Alternate Character Sets Hewlett-Packard block mode terminals, which have the capability of handling all or part of ROMAN8, can be divided into two groups. The group differentiation is based on how they handle alternate character sets when configured for 8-bit operation. Files using alternate character sets on one group of terminals will not display correctly on the terminals of the other group, even when terminals from both groups are configured for 8-bit operation.
V7FF8CNV Operation Procedure Example V7FF8CNV must be run on a terminal supported by VPLUS/XL which supports display of all characters, enhancements, and alternate character sets used in the forms. If alternate character sets are used, the HP 2392, 2625, 2627, 2628, 2700, or 150 are recommended. The V7FF8CNV procedure is: 1. Configure your terminal type properly for 8-bit operation by using the settings recommended in the System Startup, Configuration, and Shutdown Reference Manual. 2. Run V7FF8CNV.PUB.
V7FF8CNV Operation 226 Chapter 30
31 VERSION VERSION displays information about compatibility mode (CM) program files and native mode (NM) executable files (program files or executable library files), object files, and nonexecutable library files. Operation To invoke VERSION enter: VERSION or VERSION file(s) or VERSION "file(s),search string" Parameters file(s) The name of a program file or a wildcarded fileset. search string The name of a particular $version string in a system object module SOM. (Not applicable for CM program files.
VERSION Operation If the input to VERSION is a file set, every file in the set will be processed even if an error occurs processing a previous file. If there is an error opening a file, the file system error will be displayed in addition to the VERSION error message. VERSION displays the following information. CM program file Number of segments, stack size, maximum data segment size, total data reference base (DB), data segment limit (DL), and capabilities.
VERSION Operation Chapter 31 229
VERSION Operation 230 Chapter 31
32 UPSUTIL for MPE/iX Introduction UPSUTIL is an easy-to-use support tool that helps to manage the UPS Monitor/iX UPS-management subsystem on MPE/iX HP e3000 systems. Working in conjunction with the system’s UPS Monitor/iX UPS management subsystem, UPSUTIL provides easily accessible functions that assist authorized users to: • Check the system to see if the UPS Monitor/iX subsystem is running. • Check the system to see what, if any, UPS LDEVS (logical devices) has been configured.
UPSUTIL for MPE/iX Introduction • HP3000 Series 991/995/997 • HP3000 Series 9X8 • HP3000 Series 9x9 • HP e3000 N-Class and A-Class • Future HP e3000 systems with UPS devices While it is possible to run the program harmlessly on other HP e3000 models (where there are no UPS devices), there is nothing useful that UPSUTIL can do on such systems. Software Environment UPSUTIL runs under the MPE/iX Operating System, and requires system release “5.0 Push” (Core System Release C.50.
UPSUTIL for MPE/iX UPSUTIL OVERVIEW UPSUTIL OVERVIEW Functional Overview Through a very simple “command keyword” user interface, the UPSUTIL program provides the following functions pertaining to the management of UPS devices and the UPS Monitor/iX subsystem on HP e3000 systems running MPE/iX Release 5.0 “Push” or later releases: 1. A configuration query function that obtains and displays the list of UPS Ldevs (logical devices) that are in the I/O configuration of the system that is running. 2.
UPSUTIL for MPE/iX UPSUTIL OVERVIEW There is no run-time parameter (parm=) and no information string (info=) for UPSUTIL. When activated, UPSUTIL presents the start-up display information see Figure 32-1 on the Output file (terminal screen). The start-up display shows the version and copyright banner of UPSUTIL, the “help menu” of UPSUTIL’s commands, and then the UPSUTIL prompt for the user’s first command input. Figure 32-1 UPSUTIL Invocation UPS Utility Program A.02.
UPSUTIL for MPE/iX UPSUTIL OVERVIEW Introduction of the “user-specified UPS powerfail command file”. This is an MPE/iX CI command file that can be specified by a configuration command within the UPS Monitor configuration file. When so specified, this command file will be executed by the MPE/iX CI at a user-specified time following the detection by the UPS Monitor of a UPS device’s powerfail signal.
UPSUTIL for MPE/iX UPSUTIL OVERVIEW The UPSUTIL command set is summarized in the following (Table 32-1) Subsequent sections of this document explain the commands in detail. Table 32-1 UPSUTIL Commands Summary Command Name Keyword Command Function Help help Displays the menu of UPSUTIL commands. Exit exit Terminates UPSUTIL execution, returns to CI.
UPSUTIL for MPE/iX UPSUTIL Commands UPSUTIL Commands UPSUTIL’s command set is defined and explained in this section.
UPSUTIL for MPE/iX UPSUTIL Commands most recent execution of the “powerfail command file”. status - Show System UPS Monitor process status. ------------------------------------------------------------------------------ UPSUTIL: Command > EXIT Command The EXIT command terminates a UPSUTIL session. When the EXIT command is entered, UPSUTIL finishes execution and returns to the MPE/iX Command Interpreter.
UPSUTIL for MPE/iX UPSUTIL Commands There are 3 UPS devices configured on this system. UPS # LDEV # ~~~~~ ~~~~~~ 1 22 2 23 3 24 End SHOW UPS CONFIGURATION Operation -------------------------------------------------------------------------- UPSUTIL: Command > The second example shows the result of performing a CONFIG command on a system on which there are no UPS devices configured.
UPSUTIL for MPE/iX UPSUTIL Commands to any user terminals. This configuration option is called the “powerfail message routing” option. In the future, more configuration options may be added to the UPS Monitor configuration file facility, as the need arises. Revision of December 2001: Version 9: Additional Configuration Commands The UPS Monitor has been enhanced to include more configuration options.
UPSUTIL for MPE/iX UPSUTIL Commands For example, the first implemented UPS Monitor configuration command establishes the setting of how to route ** RECOVERY FROM POWERFAIL ** messages, and it appears as follows in a UPS Monitor configuration file: powerfail_message_routing = all_terminals -orpowerfail_message_routing = console_only 6.
UPSUTIL for MPE/iX UPSUTIL Commands Powerfail Grace Period The powerfail grace period configuration option allows you to specify a “grace period” (a delay time) following the detection of a UPS power failure by the UPS Monitor during which the UPS Monitor will wait to see if AC power returns to that UPS.
UPSUTIL for MPE/iX UPSUTIL Commands The Default UPS Monitor Configuration File You can still control the UPS Monitor with a configuration file even if you never use UPSUTIL’s NEWCONFIG command. This is because the UPS Monitor (Version 8 of March 2000, or later version) automatically attempts to open and read a default UPS Monitor configuration file, named UPSCNFIG.PUB.SYS, at each system startup (each system boot).
UPSUTIL for MPE/iX UPSUTIL Commands (and no “powerfail grace period time” configured), so there will be no special action taken following a UPS device power fail signal. Finally, the default UPS Monitor action for “UPS low battery charge condition” will be system abort.
UPSUTIL for MPE/iX UPSUTIL Commands Powerfail Recovery Messages : All terminals. Configuration File Name 3 UPS Devices Allocated : UPSCNFIG.PUB.SYS Powerfail Command File Name : $null ( Config File Ok ) ( Pfail Cmd File Ok ) Powerfail Command File Parms: none Powerfail Grace Period (secs: 0 Powerfail Grace Timer : Not Running. Powerfail Command File : Not Running.
UPSUTIL for MPE/iX UPSUTIL Commands UPS Monitor Operating State : Running (PIN = UPS Monitor Version Number : 9 System Power State : Power is normal. 3 UPS Devices Configured Powerfail Recovery Messages : Console only. Configuration File Name 78) 3 UPS Devices Monitored 3 UPS Devices Allocated : UPSCNFGB.PUB.SYS Powerfail Command File Name : $null ( Config File Ok ) ( Pfail Cmd File Ok ) Powerfail Command File Parms: none Powerfail Grace Period (secs: 0 Powerfail Grace Timer : Not Running.
UPSUTIL for MPE/iX UPSUTIL Commands configuration file “UPSCNFGC.PUB.SYS” at record 2, column 29. (UPSERR 0640) SET NEW CONFIG FILE UPS Monitor operation successfully initiated. End SET NEW CONFIG FILE UPS Monitor operation ---------------------------------------------------------------------------- UPSUTIL: Command > status ---------------------------------------------------------------------------Begin display of UPS Monitor status.
UPSUTIL for MPE/iX UPSUTIL Commands STATUS Command The STATUS command causes UPSUTIL to query the UPS Monitor Process for its status and for the status of each configured UPS device, and to display the status information reported by the UPS Monitor process.
UPSUTIL for MPE/iX UPSUTIL Commands The Status Display The status display produced by the STATUS command’s execution is shown in the above example and in several additional examples that follow this explanation of the parts of the status display. The status display has two main sections, titled UPS MONITOR PROCESS STATUS and UPS DEVICES STATUS. The former section gives information about the UPS Monitor Subsystem Process, while the latter gives information about each UPS device configured on the system.
UPSUTIL for MPE/iX UPSUTIL Commands Powerfail Recovery Messages This field shows the current setting of the UPS Monitor’s configuration option for handling ** RECOVERY FROM POWERFAIL ** messages. This setting is established when the UPS Monitor processes its configuration file, either during system startup (using UPSCNFIG.PUB.SYS) or, when the system is up, via the NEWCONFIG command of the UPSUTIL program.
UPSUTIL for MPE/iX UPSUTIL Commands Powerfail Grace Timer This field shows the current state of the UPS Monitor’s “powerfail grace period timer”, which measures the amount of time (powerfail grace period) from the time of the onset of a UPS device power failure until the time when the power fail command file begins to be executed. Possible values of this field are: • Not Running — The grace period timer is dormant. There is no UPS power failure in progress, so no grace period time is being measured.
UPSUTIL for MPE/iX UPSUTIL Commands • System Abort — The UPS monitor will invoke a particular System Abort in case of low battery charge condition, to ensure that there is no “partial write” on any disk device when the UPS output power does turn off. • Keep Running — The UPS monitor will NOT invoke a System Abort in case of UPS low battery charge condition. Rather, it will allow the HP e3000 system to keep running in that condition.
UPSUTIL for MPE/iX UPSUTIL Commands A value of No in this column indicates that either initialization of the UPS device failed (in which case there will be log entries in the system log file showing what errors were encountered during initialization), or that Initialization is in progress but not yet completed (in which case, a later repetition of the STATUS command will show a Yes in this column, denoting completion of initialization).
UPSUTIL for MPE/iX UPSUTIL Commands The “normal state” of hardware status is simply: AC Power Normal. In this normal state, AC Power Normal will be the only status item shown in the Hardware Status display. The UPS devices, however, are capable of reporting a number of status conditions to the host system, and in cases of additional UPS hardware status, there will be multiple lines in the status display showing the additional status conditions.
UPSUTIL for MPE/iX UPSUTIL Commands • High Battery Voltage — The UPS device reported a High Battery Voltage status, which indicates that the UPS control module perceived an overvoltage at the battery terminals, indicative of a hardware problem. • Low Battery Voltage — The UPS device reported a Low Battery Voltage status, which indicates that the UPS control module perceived an undervoltage at the battery terminals, indicative of a hardware problem.
UPSUTIL for MPE/iX UPSUTIL Commands -------------------------------------------------------------------------- UPSUTIL: Command > status -------------------------------------------------------------------------Begin display of UPS Monitor status. UPS MONITOR PROCESS STATUS: UPS Monitor Operating State : Running (PIN = UPS Monitor Version Number : 9 System Power State : Power has failed. 3 UPS Devices Configured Powerfail Recovery Messages : All terminals.
UPSUTIL for MPE/iX UPSUTIL Commands -------------------------------------------------------------------------- UPSUTIL: Command > status -------------------------------------------------------------------------Begin display of UPS Monitor status. UPS MONITOR PROCESS STATUS: UPS Monitor Operating State : Running (PIN = UPS Monitor Version Number : 9 System Power State : Power has failed. 3 UPS Devices Configured Powerfail Recovery Messages : All terminals.
UPSUTIL for MPE/iX UPSUTIL Commands UPSUTIL: Command > status -------------------------------------------------------------------------Begin display of UPS Monitor status. UPS MONITOR PROCESS STATUS: UPS Monitor Operating State : Running (PIN = UPS Monitor Version Number : 9 System Power State : Power has failed. 3 UPS Devices Configured Powerfail Recovery Messages : All terminals. Configuration File Name 196) 3 UPS Devices Monitored 3 UPS Devices Allocated : UPSCNFIG.PUB.
UPSUTIL for MPE/iX UPSUTIL Commands = “Yes”) by the UPS Monitor Process, that the first UPS device (Ldev# = 22) has completed its initialization sequence and is now being monitored (Init = “Yes” and State = “Monitoring”), and that the other two UPS devices, Ldevs 23 and 24, are still in the process of being initialized (Init = “No” and State = “Initializing”).
UPSUTIL for MPE/iX UPSUTIL Commands 1 22 Yes Yes Monitoring Normal AC Power Normal 2 23 Yes No Initializing ??? ??? 3 24 Yes No Initializing ??? ??? End display of UPS Monitor status. -------------------------------------------------------------------------- UPSUTIL: Command > status -------------------------------------------------------------------------Begin display of UPS Monitor status.
UPSUTIL for MPE/iX UPSUTIL Commands In this case, as in Example #6 when initialization was not yet completed, the UPS Monitor Process does not know what the power status or hardware status of the UPS device is, so the STATUS display shows “???” for those fields.
UPSUTIL for MPE/iX UPSUTIL Commands RESETPFAIL Command The RESETPFAIL command is for the purpose of clearing-out from the UPS Monitor’s status display the information pertaining to past completions of the “Powerfail Grace Period Timer” and “Powerfail Command File”.
UPSUTIL for MPE/iX UPSUTIL Commands Powerfail Grace Timer : Completed. TUE, FEB 12, 2002, 2:53 PM Powerfail Command File : Completed.
UPSUTIL for MPE/iX UPSUTIL Commands Powerfail Grace Timer : Not Running. Powerfail Command File : Not Running. Action on UPS Low Battery : Keep Running UPS DEVICES STATUS: UPS# Ldev# Alloc Init State Power ~~~~ ~~~~~~ ~~~~~ ~~~~ ~~~~~~~~~~~~ ~~~~~~ Hardware Status ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 22 Yes Yes Monitoring Normal AC Power Normal 2 23 Yes Yes Monitoring Failed AC Power Fail 3 24 Yes Yes Monitoring Normal AC Power Normal End display of UPS Monitor status.
UPSUTIL for MPE/iX UPSUTIL Commands -------------------------------------------------------------------- UPSUTIL: Command > Example #2 — Rejected START -------------------------------------------------------------------- UPSUTIL: Command > start -------------------------------------------------------------------Begin START UPS Monitor operation ** WARNING: UPS Monitor process is already running at this time. ** WARNING: START UPS Monitor operation not performed.
UPSUTIL for MPE/iX UPSUTIL Commands End STOP UPS Monitor operation -------------------------------------------------------------------- UPSUTIL: Command > Example #2 — Rejected STOP -------------------------------------------------------------------- UPSUTIL: Command > stop -------------------------------------------------------------------Begin STOP UPS Monitor operation ** WARNING: UPS Monitor process is not running at this time. ** WARNING: STOP UPS Monitor operation not performed.
UPSUTIL for MPE/iX UPSUTIL Commands RESTART UPS Monitor operation successfully executed. End RESTART UPS Monitor operation -------------------------------------------------------------------- UPSUTIL: Command > Example #2 — Rejected RESTART -------------------------------------------------------------------- UPSUTIL: Command > restart -------------------------------------------------------------------Begin RESTART UPS Monitor operation ** WARNING: UPS Monitor process is not running at this time.
UPSUTIL for MPE/iX UPSUTIL Commands 268 Chapter 32
Index SHOWDEV command, 238 Symbols $STDIN, 234 $STDLIST, 71, 234 ), 180 A AC Power Fail, 256 account(s) migrating with BULDACCT, 75 African peripherals, 147 application code written in both native and compatibilty mode facilitating with SWAT, 60 Asian peripherals, 147 ASOCIATE.PUB.SYS, 22, 71 ASOCTBL, 22, 71 errors, 73 input to, 71 listing association table, 72 parameters, 71 removing entries from ASOCIATE.PUB.
Index DIRMIG, 28 DISASSOCIATE command, 22, 71 DISCFREE, 29, 81 allocation summary, 82 format options, 82 histogram, 82 parameters, 82 DISCUTIL, 30, 85 commands, 85 CONFIGURE command, 86 DISMOUNT command, 86 DO command, 86 DSTAT command, 87 EXIT command, 87 HELP command, 87 LISTREDO command, 87 messages and errors, 92 MOUNT command, 88 PDEV command, 88 REDO command, 88 SAVE command, 89 SHOWDEV command, 90 TAPE command, 91 UNCONFIG command, 92 DISCUTIL’’ file recovery, 85 disk fragmentation, 29, 81 disk manag
Index help menu, 234 hierarchical file system, 240 HPFOPEN intrinsic, 252 I I7DB8CNV, 36, 117 IBM tape copying with FCOPY, 98 IMAGE data base converting to ROMAN8, 36, 117 Initial stack, modifying, 156 intrinsic disk files building,changing, 25 IOMAP, 37 ISL> prompt, 85 K keep_running, 240 keyword config, 236 exit, 236 help, 236 new config, 236 resetfail, 236 restart, 236 start, 236 status, 236 stop, 236 KSAM, 145 copying files, 102 KSAM files managing with KSAMUTIL, 38 KSAMUTIL, 38 L label table check, 34,
Index activating for devices, 45 NEWCONFIG command, 234, 239, 240, 244 NLIODEF.PUB.
Index SYSDIAG, 135, 213 SYSGEN, 61, 71, 147 SYSMAP, 62, 213 CPUMAP, 213 IOMAP, 213 MEMMAP, 213 system abort, 242 system abort signal, 240 system backup and recovery, 59 system diagnosis TERMDSM, 63 system log file, 41 system logging, 138 System Manager (SM), 233 system volume(s), 75 system_abort, 240 information displayed, 228 volume label, 89 volume number in volume set, 88 volume set(s) managing with VOLUTIL, 69 volumes mounted, 29, 81 VOLUTIL, 69 RECOVER, 30 VOLUTIL'' RECOVER, 85 VPLUS converting to ROM
Index 274
