Kernel-Managed Swap Facility (KMSF) Manual Abstract This manual describes the installation, configuration, and management of the KernelManaged Swap Facility (KMSF), which manages virtual memory for HP NonStop™ systems. It describes the operation of and command syntax for NSKCOM, the HP NonStop operating system command interface to KMSF. This manual is primarily written for those who configure, manage, and monitor kernel-managed swap (KMS) space.
Document History Part Number Product Version Published 420260-001 NonStop operating system G06.
Kernel-Managed Swap Facility (KMSF) Manual Index Examples What’s New in This Manual vii Manual Information vii New and Changed Information About This Manual ix How This Manual Is Organized Related Manuals x Notation Conventions x Figures Tables vii ix 1.
3. Managing KMS Files Contents 3.
4. NSKCOM Command Reference (continued) Contents 4. NSKCOM Command Reference (continued) STOP Command 4-33 TIME Command 4-34 VER[SION] Command 4-35 VOL[UME] Command 4-35 5. Operator Messages for KMSF Messages are Generated Under the NSK Subsystem Name 200 5-1 201 5-2 202 5-3 203 5-3 204 5-4 206 5-5 207 5-5 208 5-6 209 5-6 210 5-7 211 5-7 212 5-7 213 5-8 214 5-9 215 5-10 5-1 Index Examples Example 1-1. Example 1-2. Example 2-1. Example 2-2. Example 3-1. Example 3-2. Example 3-3. Example 3-4.
Examples (continued) Contents Examples (continued) Example 3-7. Example 3-8. Example 3-9. Example 3-10. Example 3-11. Example 3-12. Example 3-13. Example 3-14. Example 3-15. Example 4-1. Example 4-2. Example 4-3. Example 4-4. Example 4-5. Example 4-6. Example 4-7. Example 4-8. Example 4-9. Example 4-10. Example 4-11. Example 4-12. Example 4-13. Example 4-14. Example 4-15. Example 4-16. Example 4-17. Example 4-18. Example 4-19. Example 4-20. Example 4-21.
Figures Contents Figures Figure 1-1. Figure 1-2. Figure 1-3. Figure 3-1. Figure 3-2. Figure 4-1. Relationships Between KMSF Components How Swap Space Is Allocated 1-6 How Data is Read from Swap Files 1-7 NSKCOM Opening Banner 3-3 ENV Command 3-10 ENV Command Display 4-16 1-4 Tables Table 1-1. Table 4-1.
Contents Kernel-Managed Swap Facility (KMSF) Manual—425824-005 vi
What’s New in This Manual Manual Information Kernel-Managed Swap Facility (KMSF) Manual Abstract This manual describes the installation, configuration, and management of the KernelManaged Swap Facility (KMSF), which manages virtual memory for HP NonStop™ systems. It describes the operation of and command syntax for NSKCOM, the HP NonStop operating system command interface to KMSF. This manual is primarily written for those who configure, manage, and monitor kernel-managed swap (KMS) space.
What’s New in This Manual • New and Changed Information In all sections, examples showing default swap files have been changed to show swap file sizes more commonly in use for both systems running H-series RVUs and systems running G-series RVUs. For H-series RVUs, the change made to increase the default swap file size (increasing the extent size) also affected configured swap files, but these changes were not documented in the previous edition of this manual.
About This Manual The Kernel-Managed Swap Facility (KMSF) Manual describes the installation, configuration, and management of kernel-managed swap (KMS) space. KMS space is HP’s method of managing virtual memory using swap files controlled by the HP NonStop operating system. Each processor has at least one KMS file that provides the swap space needed by its processes. Proper configuration and management of KMS space is critical to the operation of your system.
Related Manuals About This Manual Related Manuals The following manuals provide additional information concerning KMS space and your system. • Installation and Configuration Information • • • • The NonStop NS-Series Planning Guide and the NonStop S-Series Planning and Configuration Guide describe how to prepare your site and plan the installation and configuration of these servers. Planning for KMS space is part of this process.
General Syntax Notation About This Manual General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name computer type.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times.
Notation for Messages About This Manual !i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i:i. !i,o In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
Notation for Management Programming Interfaces About This Manual horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed.
Change Bar Notation About This Manual !o. The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information.
Change Bar Notation About This Manual Kernel-Managed Swap Facility (KMSF) Manual—425824-005 xvi
1 Introduction The Kernel-Managed Swap Facility (KMSF) and its related components manage virtual memory for processes.
Kernel-Managed Swap (KMS) Files Introduction • Can be used in addition to KMS files Kernel-Managed Swap (KMS) Files Kernel-managed swap (KMS) files: • • • • Are a required part of the NonStop operating system Are defined and managed by the KMSF Are dedicated to a single processor in the system and all processes running on the processor Are opened only once and are then remain available to all processes running on the processor, including processes started after the swap file is opened Benefits of Usi
KMSF and Users Introduction configured threshold and to changes in KMSF configuration. Managing KMS space is described in Section 3, Managing KMS Files. KMSF and Users When a user starts a process, KMSF provides the swap space that the process requires at process creation. User control over certain aspects of swap files is limited, because KMS files provide swap space for multiple processes: • • In most cases, users cannot decide where data is swapped.
Components of Managing Virtual Memory Using KMSF Introduction Figure 1-1. Relationships Between KMSF Components resized reservation operating system Memory Management Software KMSF reservation request NSKCOM resize request data $SYSTEM ZSYSCFG swap00 swap01 VST001.
Kernel-Managed Swap Space Process Flow Introduction Kernel-Managed Swap Space Process Flow When a processor is loaded, either because it is being loaded manually or because it is listed in the CIIN file when the system is started, KMSF manages the swap space for the processor: 1. KMSF checks the ZSYSCFG file to see if there are any configured swap files for the processor. 2.
Kernel-Managed Swap Space Process Flow Introduction given from a different swap file than that used for the initial reservation. When a process no longer needs swap space, the operating system returns it to the KMSF. Figure 1-2 illustrates how swap space is allocated. Figure 1-2.
Characteristics of KMS Files Introduction The operating system swaps data to the swap file as needed. If the process attempts to access a page that it has written to and that the operating system has swapped out, a page-fault interrupt is generated. The page-fault interrupt handler passes the access request to the operating system, which works with the disk process to read the absent page in from disk. The operating system makes the page available to the executing process, which can then resume execution.
Characteristics of KMS Files Introduction • • • Is an unstructured file identified by code 405 in the File Utility Program (FUP) Is set to CLEARONPURGE, so the disk process overwrites the file with blank data when the file is deleted (in NSKCOM, this process of overwriting data in a file is referred to as “cleaning” the file) Is one of two different formats: Format 1 and Format 2: ° Format 1 files are limited in size because of the limitations of 32-bit addressing.
Default Swap Files Introduction Table 1-1. Formats of KMS Files Format 1 Format 2 Attribute Min Max Default Min Max Default EXT 8 65504 512 (G-series RVUs) 8 65536 512 (G-series RVUs) 1024 (H-series RVUs) 1024 (H-series RVUs) MAXEXTENTS 16 800 64 16 800 64 SIZE* 256 KB 2047 MB** 64 MB 256 KB 100 GB 64 MB * SIZE=EXTENTS*MAXEXTENTS*2048 bytes ** The maximum size for Format 1 files is limited by 32-bit addressing.
KMS Files and New Systems Introduction • • • Default swap files are not displayed in the NSKCOM opening banner, which only displays configured swap files. Default swap files are always Format 1 swap files. The threshold for a default swap file can exceed the number of disk pages allocated. The threshold is relative to the default maximum size of the file instead of to the bytes currently allocated.
KMS Files and New Systems Introduction Example 1-2. Four-Processor System With Default Swap Files Only $SYSTEM SYS42 4> NSKCOM NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005 Copyright 1995 Compaq Computer Corporation NSK-INFO SWAPFILE * $SYSTEM.ZSYSSWAP.SWAP00 Extent Size 1024 pages MaxExtents 256 File Size 512.000 MB Format 1 CPU 0 Threshold Default $SYSTEM.ZSYSSWAP.SWAP01 Extent size 1024 disk pages MaxExtents 256 File Size 512.000 MB Format 1 CPU 1 Threshold Default $SYSTEM.ZSYSSWAP.
Introduction KMS Files and New Systems Kernel-Managed Swap Facility (KMSF) Manual—425824-005 1- 12
2 Configuring KMSF The KMSF configuration file, ZSYSCFG, is automatically created by NSKCOM. Use NSKCOM, the HP NonStop operating system command interface to KMSF, to create swap files and alter your configuration. There are two kinds of KMSF swap files: • • Default swap files Configured swap files This section describes configured swap files. For information about default swap files, see Default Swap Files on page 1-9.
Location of KMSF Swap Files Configuring KMSF Location of KMSF Swap Files Listed below are general guidelines for locations to place KMSF swap files: • • • • Default swap files are located on $SYSTEM, which has a high activity rate and is often near capacity. Putting configured swap files on a different mirrored volume can improve system performance. Place swap files on volumes that do not have high activity for data other than the swap files themselves.
Amount of Swap Space to Allocate Configuring KMSF Configuration Guidelines Follow these guidelines in planning your configuration: • • In general, systems used for application development require more swap space than systems running applications in a production environment because application development tools often require more swap space. The amount of swap space you need to configure for a processor is based on the peak load, where load is defined as the amount of swapable memory pages.
Using NSKCOM to Configure KMS Files Configuring KMSF • The following HP products consume a large amount of swap space. If you run these applications, you might need to configure additional swap space to handle the increased load: • • • • TELNET Server (Telserv) Native link editor (nld) Object file linker for TNS/E (eld) Open System Services (OSS) After the system has been running for a while, you can use historical data to guide you when you adjust your KMSF configuration.
Quick Start: Adding Configured Swap Files to a New System Configuring KMSF and starting swap files for a four-processor system running an H-series RVU. The memory size for each of the processors in the example system is 16 gigabytes. Therefore, the disk in the example, $SWAP, must have 256 gigabytes of available space. For a detailed description of the ADD and START commands, see Section 4, NSKCOM Command Reference. Example 2-1.
Making Adjustments to Your Configuration Configuring KMSF File size Format Threshold 16.000 GB 2 Default The ASSUME LIKE command sets the attribute values for all subsequent NSKCOM commands to be like those specified in the file $SWAP.KERSWAP.CPU00A. The RESET command resets the assumed defaults back to the original values (see the RESET command on page 4-22). The files you added are displayed in the opening banner the next time you run NSKCOM (Example 2-2). Example 2-2.
3 Managing KMS Files You manage KMS space using NSKCOM, a utility program for the operating system.
Key Indicators for KMSF Usage Managing KMS Files display the NSK subsystem name. By monitoring the EMS logs or ViewPoint for these messages, you can avoid actively checking your swap files. Key Indicators for KMSF Usage Monitor the following key indicators to determine whether your KMSF configuration is successfully meeting the needs of the system.
Using NSKCOM to Monitor KMS Space Managing KMS Files Figure 3-1. NSKCOM Opening Banner Usage threshold at which an EMS message is generated. If blank, the file has a default threshold of 85 percent. $SYSTEM SYS66 35> NSKCOM NSKCOM version NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005 Copyright 1995 Compaq Computer Corporation Configuration file List of configured swap files $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SWAP.KERSWAP.CPU00A THRESHOLD 70 KMS.SWAPFILE = 1 $SWAP.KERSWAP.CPU01A KMS.
Other Tools and KMSF Managing KMS Files Other Tools and KMSF Use NSKCOM, rather than other HP utilities, to monitor KMS files. Such utilities as the Object Monitoring Facility (OMF), PEEK, and the File Utility Program (FUP) are general-purpose utilities that do not return information specific to KMSF. Due to the architecture of KMS files, these utilities might give misleading information for KMS files. In particular, use NSKCOM instead of other tools to: • Determine the size and usage of your KMS files.
Other Tools and KMSF Managing KMS Files Example 3-2. Using NSKCOM to Determine a Process’s Swap File NSK-STATUS SWAPFILE *, CPU 0 Status of $SWAP.KERSWAP.CPU0 CPU 0 CPU Pages: Total 16384 Reserved 7855 Peak CPU Pages ever reserved 9157 Threshold 13926 CPU pages Available 8529 Status of $SYSTEM.ZSYSSWAP.SWAP00 CPU 0 CPU Pages: Total 16384* Reserved 10244 Available 6140 Peak CPU Pages ever reserved 11160 Threshold 13926 CPU pages * Default swapfile extents may not be fully allocated.
Other Tools and KMSF Managing KMS Files • Determine the processes that are using a swap file or files. The NSKCOM STATUS SWAPFILE command with the DETAIL attribute shows the processes that currently have space guarantees from a swap file. A swap file cannot be stopped when there are active space guarantees. Example 3-3 shows the swap file that is being used for CPU 0. Example 3-3. Using NSKCOM to Determine a Swap File’s Processes NSK-STATUS SWAPFILE $SWAP.KERSWAP.CPU0, DETAIL Status of $SWAP.KERSWAP.
Checking the Status of KMS Files Managing KMS Files Checking the Status of KMS Files Check your KMS files to ensure that they are working properly and that their usage is at an acceptable level. Use the NSKCOM STATUS command to display dynamic statistics on swap files. Example 3-4 shows the STATUS command display for all swap files for CPU 0. Example 3-4. Using the STATUS Command to Display Information on Swap Files NSK-STATUS SWAPFILE *, CPU 0 Status of $SWAP.KERSWAP.
Checking Swap Statistics Managing KMS Files Checking Swap Statistics You can use the STATUS SWAP-USAGE command to display the swap statistics of a processor, a process, or a process pair. The statistics will assist you in making decisions for allocating space based on actual need. Example 3-6 shows the STATUS SWAP-USAGE command being used to display the swap statistics of a processor. Example 3-6.
Checking Your Current Configuration Managing KMS Files Checking Your Current Configuration Using the INFO Command You can use the NSKCOM INFO command to display static configuration information and file attributes for swap files or processors. Example 3-7 shows the INFO command display for all swap files for CPU 1 on a system running an H-series RVU. Example 3-7. INFO Command NSK-INFO SWAPFILE *, CPU 1 $SWAP.KERSWAP.CPU01A Extent Size 10486 disk pages MaxExtents 800 File Size 16.
Checking Your Current Configuration Managing KMS Files • • All swap files known to NSKCOM, including both configured and default swap files Indicators of pending DELETE commands, pending STOP commands, and nondefault THRESHOLD values for all swap files that have them The ENV command does not display the status of swap files. To find out if a swap file is in use or not, use the INFO or STATUS command. Figure 3-2 shows the output of the ENV command. Note. For the H06.
Altering Your KMSF Configuration Managing KMS Files Altering Your KMSF Configuration Alter your configuration as necessary to ensure proper system operation. Using NSKCOM, you can resize swap files, add and delete swap files, and change the threshold at which EMS messages are generated. Writing Your Own Operator Guidelines Because KMSF is vital to system operations, consider writing your own operator instructions for altering the KMS configuration.
Altering Swap Files Managing KMS Files Altering Swap Files Use the ALTER command to alter the maximum extents or threshold of a file. You can increase the maximum extents of a file, or if the file is not fully reserved, decrease its maximum extents. In Example 3-9, the maximum number of extents of a swap file is increased to 512. Example 3-9. Altering a Swap File By Increasing MAXEXTENTS NSK-ALTER SWAPFILE $SWAP.KERSWAP.CPU00A MAXEXTENTS 512 ALTER was successful: $SWAP.KERSWAP.
Deleting Swap Files Managing KMS Files Example 3-11. STOP Pending Message NSK-STOP SWAPFILE $SWAP.KERSWAP.CPU00A File $SWAP.KERSWAP.CPU00A Stop Pending altered in ZSYSCFG STOP is pending NSKUsage of the file stops when all processes using the file have terminated. NSKCOM then gives the file’s status as “Not currently in-use.” Deleting Swap Files You use the STOP and DELETE commands to delete KMS files. The STOP command disables a swap file for use by additional processes.
Deleting Swap Files Managing KMS Files The file is not deleted until all the current processes using the file have terminated and NSKCOM is started by a super-group user (255, n). When NSKCOM is started by a super-group user (255, n), NSKCOM searches for files that are marked for deletion and that are not in use and deletes them. In Example 3-13 on page 3-14, the STOP and DELETE commands are not completed immediately because the swap file is in use.
Changing the Threshold for Messages Managing KMS Files Changing the Threshold for Messages The KMSF generates Event Management Service (EMS) messages when a swap file passes a preconfigured percent in-use threshold. The default threshold is 85 percent, that is, when 85 percent of the file is reserved, NSK message 200 is generated. For default swap files, the threshold is based on the maximum default file size instead of on the allocated file size.
Managing KMS Files Changing the Threshold for Messages Kernel-Managed Swap Facility (KMSF) Manual—425824-005 3- 16
4 NSKCOM Command Reference NSKCOM is the command interface to manage KMS space. Run NSKCOM by typing NSKCOM at the HP Tandem Advanced Command Language (TACL) prompt. NSKCOM includes the commands listed in Table 4-1. As indicated in the table, only super-group users (255, n) can issue commands that change the KMSF configuration by adding, stopping use of, or deleting swap space. Table 4-1.
NSKCOM Command Reference ADD Command ADD Command The ADD command creates a swap file to be used by a specific processor and adds an entry for the swap file to the configuration file, ZSYSCFG. You can specify attribute values for the swap file when you enter the ADD command. If you do not specify attributes, the swap file is created using the active default values. After entering the ADD command, enter the START command to enable use of the swap file.
NSKCOM Command Reference ADD Command MAX[EXTENT[S]] maximum-extents specifies the maximum number of extents for the file. For both Format 1 and Format 2 files: • • The minimum value is 16 The default value is 64 For Format 1 files, you can specify a maximum value up to 800. However, because of 32-bit addressing, Format 1 files are limited to a maximum size of 2047 megabytes, where: 2047= EXT * MAXEXTENTS * 2048 bytes. For Format 2 files, the maximum value is 800.
NSKCOM Command Reference ADD Command FORMAT {0 | 1 | 2} specifies the type of swap file format to be used. When format 0 is specified on the command line, the system chooses the file format to be used, based on the file’s size parameters. See Table 1-1 on page 1-9 to see how the values of extents, maxextents, and size change according to the format of the swap file used. In Example 4-1, a swap file with a file size of 128 megabytes is added for CPU 1. Example 4-1. ADD Command NSK-ADD SWAPFILE $SWAP.
NSKCOM Command Reference ALT[ER] Command ALT[ER] Command The ALTER command changes attributes of a swap file. Modifiable attributes are MAXEXTENTS, SIZE, and THRESHOLD. This command can be issued only by super-group users (255, n). ALT[ER] SWAPF[ILE] filename attribute value [, attribute value ] filename is the name of the swap file to be altered. The variable filename is specified as: $volume.subvolume.filename. attribute value optionally sets the value of an attribute of the swap file.
NSKCOM Command Reference ALT[ER] Command For Format 1 files, you can specify a maximum value up to 800. However, because of 32-bit addressing, Format 1 files are limited to a maximum size of 2047 megabytes, where: 2047= EXT * MAXEXTENTS * 2048 bytes. For Format 2 files, the maximum value is 800. If each extent is 1 megabyte (512 disk pages), then MAXEXTENTS is equivalent to SIZE. SIZE filesize {KB | MB | GB | PAGES} specifies the size of the file, where SIZE = EXT * MAXEXTENTS * 2048 bytes.
NSKCOM Command Reference ALT[ER] Command Example 4-2. Using the ALTER Command to Alter the Threshold NSK-ALTER SWAPFILE $SWAP.KERSWAP.CPU02A, THRESHOLD 75 File $SWAP.KERSWAP.CPU02A Threshold altered in ZSYSCFG ALTER was successful: $SWAP.KERSWAP.CPU02A NSKIn Example 4-3, the maximum extents of a swap file are increased. Example 4-3. Using the ALTER Command to Increase Maxextents NSK-ALTER SWAPFILE $SWAP.KERSWAP.CPU00A, MAXEXTENTS 560 ALTER was successful: $SWAP.KERSWAP.
NSKCOM Command Reference ASSUME Command ASSUME Command The ASSUME command establishes custom default values for subsequent commands for file attributes or command object. The default values are used when one or more attributes relevant to an NSKCOM command are not specified in the command. The default values specified in an ASSUME command are valid until you issue another ASSUME command for that attribute, issue the RESET command, or exit NSKCOM.
NSKCOM Command Reference ASSUME Command THRESHOLD percent-full specifies the default threshold for subsequent NSKCOM commands. FORMAT {0 | 1 | 2} specifies the type of swap file format to be used. When format 0 is specified on the command line, the system chooses the file format to be used, based on the file’s size parameters. See Table 1-1 on page 1-9 to see how the values of extents, maxextents, and size change according to the format of the swap files used.
NSKCOM Command Reference ASSUME Command In Example 4-5, the ASSUME command is used to set defaults for subsequent ADD commands. The VOLUME command sets the default volume and subvolume. The INFO command shows that the attributes of the configured file matches those specified in the ASSUME commands. Example 4-5. Using the ASSUME Command to Set Defaults When Adding Files NSK-ASSUME SWAPFILE NSK-ASSUME MAXEXTENTS 80 NSK-ASSUME THRESHOLD 75 NSK-ASSUME CPU 2 NSK-VOLUME $SWAP.KERSWAP NSK-ADD CPU02C File $SWAP.
NSKCOM Command Reference ASSUME Command In Example 4-6, files added following an ASSUME command with the LIKE option have the same attributes as the specified file, unless a different value is specified. Example 4-6. Specifying a Different Value When Using the ASSUME LIKE Command NSK-ASSUME LIKE $SWAP.KERSWAP.CPU01B NSK-ADD SWAPFILE $SWAP.KERSWAP.CPU00B, CPU 0 File $SWAP.KERSWAP.CPU00B was added to ZSYSCFG ADD was successful: $SWAP.KERSWAP.CPU00B NSK-ADD SWAPFILE $SWAP.KERSWAP.CPU02B File $SWAP.KERSWAP.
NSKCOM Command Reference COMMENT Command COMMENT Command The COMMENT, or “==” command causes the rest of the line to be treated as a comment and ignored by NSKCOM. If you use the NSKCOM LOG command to log your NSKCOM session, this command is a useful tool for commenting your changes. COMMENT [text] | == [text] text is the information that you enter at the keyboard.
NSKCOM Command Reference Notes and Considerations represented by a ‘.’. The user can press the Break key to abort the operation at any point. If the swap file is not currently in use, it is deleted immediately after cleaning. Example 4-7. Deleting a Stopped File NSK-STOP SWAPFILE $SWAP.KERSWAP.CPU01B File $SWAP.KERSWAP.CPU01B Stop Pending altered in ZSYSCFG STOP was successful: $SWAP.KERSWAP.CPU01B NSK-STATUS SWAPFILE $SWAP.KERSWAP.CPU01B Status of $SWAP.KERSWAP.CPU01B Not currently in-use.
NSKCOM Command Reference Notes and Considerations has a stop pending. The subsequent STATUS command shows both the stop and delete pending. Example 4-8. Deleting a File That Is in Use NSK-STOP SWAPFILE $SWAP.KERSWAP.CPU00A File $SWAP.KERSWAP.CPU00A Stop Pending altered in ZSYSCFG STOP is pending NSK-DELETE SWAPFILE $SWAP.KERSWAP.CPU00A *** Warning: File in-use: $SWAP.KERSWAP.CPU00A *** File Error 12: System Monitor: CPU 0 File marked 'delete pending' by Monitor File $SWAP.KERSWAP.
NSKCOM Command Reference ENV Command Example 4-9. Delayed Deletion of Files NSK-DELETE SWAPFILE $SWAP.KERSWAP.CPU0C *** Warning: File in-use: $SWAP.KERSWAP.CPU0C *** File Error 12: System Monitor: CPU 0 File marked 'delete pending' by Monitor File $SWAP.KERSWAP.CPU0C marked for delete in ZSYSCFG NSK-EXIT ... $SYSTEM SYSTEM 3> NSKCOM NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005 Copyright 1995 Compaq Computer Corporation $SYSTEM.SYSTEM.ZSYSCFG KMS.SWAPFILE = 0 $SWAP.KERSWAP.CPU00A THRESHOLD 70 KMS.
ENV Command NSKCOM Command Reference Figure 4-1 shows an ENV command display for a six-processor system. Note. For the H06.03 RVU, the ENV command incorrectly displays the default file size as 64 MB. The default file size is 128 MB. Figure 4-1.
E[XIT] Command NSKCOM Command Reference E[XIT] Command The EXIT command terminates your NSKCOM session. E[XIT] Following is an example of the EXIT command. Upon exiting NSKCOM, you are returned to the TACL prompt. NSK-EXIT > FC Command The FC command enables you to edit or repeat a previous command. When you enter FC, the last command entered is displayed, followed by the FC prompt, a period (.), on the next line.
H[ELP] Command NSKCOM Command Reference H[ELP] Command The HELP command provides help on NSKCOM command syntax. H[ELP] [ [ command ] | [ ALL ] If you enter just the command HELP with no command option, a list of commands is displayed: NSK-HELP ADD ENV LOG VERSION NSK- ALTER EXIT OBEY VOLUME ASSUME FC START COMMENT HELP STATUS DELETE INFO STOP If you enter the HELP command followed by a command name, information is given on that command, as shown in Example 4-11. Example 4-11.
NSKCOM Command Reference INFO Command INFO Command The INFO command displays static configuration information and file attributes for the specified object or objects. INFO now also gives information about the format of the swap files. For dynamic status information, use the STATUS command. INFO SWAPF[ILE] { filename | * } [ , CPU cpu-num ] filename is the name of the swap file for which you want to display information. The variable filename is specified as: $volume.subvolume.
LOG Command NSKCOM Command Reference Example 4-12. The INFO Command NSK-INFO SWAPFILE *, CPU 4 $SWAP.KERSWAP.CPU4A Extent Size 512 disk pages MaxExtents 64 File Size 64.000 MB Format 1 CPU 4 Threshold Default Stop Pending $SWAP.KERSWAP.CPU4B Extent Size 512 disk pages MaxExtents 64 File Size 64.000 MB Format 1 CPU 4 Threshold Default Stop Pending Delete Pending $SYSTEM.ZSYSSWAP.SWAP04 Extent Size 1024 disk pages MaxExtents 256 File Size 512.
NSKCOM Command Reference O[BEY] Command For example, to begin logging your NSKCOM session to the file NSKLOG, enter the following command: NSK-LOG NSKLOG NSKTo stop logging, enter: NSK-LOG NSKNote. If you use the FC command to fix or reenter a command, the fixed or reentered command does not appear in your log file. O[BEY] Command The OBEY command reads the contents of an EDIT file and performs the commands given there. Enter commands in an EDIT file as you would to NSKCOM.
NSKCOM Command Reference RESET Command RESET Command The RESET command changes all the attributes set by the ASSUME command to the following defaults: CPU: -1 MAXEXTENTS: 64 EXTENTS: 512 disk pages for G-series RVUs, 1024 disk pages for H-series RVUs SIZE: 64.000 MB for G-series RVUs, 128 MB for H-series RVUs Format: 0 Threshold: DEFAULT (85%) RESET For information about these attributes, see the ASSUME Command on page 4-8. START Command The START command enables use of a swap file.
NSKCOM Command Reference STATUS Command STATUS Command The STATUS command displays dynamic statistics for swap files. Use the STATUS SWAPFILE command to obtain information on swap files; use the STATUS SWAP-USAGE command to obtain information on processors, processes, and process pairs. This command excludes any information on read-only process object file or filebacked data segments. Use the STATUS KMSF command to obtain information on a system’s or processors’s swap files as a whole.
NSKCOM Command Reference STATUS SWAPF[ILE] STATUS SWAPF[ILE] Example 4-13 shows the STATUS command used with the SWAPFILE parameter. Example 4-13. The STATUS Command Used With the SWAPFILE Parameter NSK-STATUS SWAPFILE *, CPU 0, DETAIL Status of $SWAP.KERSWAP.
STATUS SWAPF[ILE] NSKCOM Command Reference Interpret this data as follows: : CPU The number of the processor that the swap file is dedicated to. CPU Pages: Total Total memory pages that are currently allocated for the file. CPU Pages: Reserved Total memory pages currently reserved in the swap file. CPU Pages: Available Total memory pages that are currently available in the file. Peak CPU Pages ever reserved The highest number of memory pages that have ever been reserved in the file at one time.
STATUS SWAP-USAGE NSKCOM Command Reference STATUS SWAP-USAGE Note. The abbreviation SU is also recognized. Example 4-14 shows the STATUS command used with the SWAP-USAGE parameter and specifying a processor. This command excludes any information on read-only object file or file-backed data segments. Example 4-14.
STATUS SWAP-USAGE NSKCOM Command Reference Interpret this data as follows: SYSTEM/LOGTIME System name and logon time. CPU Page Size Size in bytes of each processor memory page. Process Name Name of each process on the specified processor Program File Name Name of the file corresponding to each process. KMSF STATISTICS KMSF memory reservation for each process as a whole. It is the sum of the KMSF reservations for all the segments belonging to the process.
STATUS SWAP-USAGE NSKCOM Command Reference Example 4-15 shows the STATUS command used with the SWAP-USAGE parameter and specifying a process. Example 4-15.
NSKCOM Command Reference STATUS SWAP-USAGE Example 4-16. The STATUS Command Used With the SWAP-USAGE Parameter With a Process Pair Specified NSK-STATUS SWAP-USAGE $ZNET SYSTEM : \M5 LOGTIME : October 20, 1998 11:22:45 TYPE : (E=Extensible S=Shared O=Owner) (CPU Page size is 16384 Bytes) _______________________________________________________________ Process Pri User-ID Program File Name $ZNET b 1,20 175 255,255 $SYSTEM.SYS00.
STATUS KMSF NSKCOM Command Reference Interpret this data as follows: System/LOGTIME System name and logon time. TYPE Segment’s type. Process Space Guarantee Initial space guarantee specified during process creation, in kilobytes. SEG-ID TYPE Segment ID specified during segment allocation. Heap+Global+SRL+ Stack Swap statistics for system-allocated segments for Mainstack, SRL instance data, Globals, and Heap. SIZE Size of the KMSF-backed segment.
STATUS KMSF NSKCOM Command Reference Example 4-18 shows the STATUS command with the KMSF cpu-num parameter. This command displays all statistics for CPU cpu-num. Example 4-18. The STATUS command Used With the KMSF cpu-num Parameter NSK-STATUS KMSF CPU 1 KMSF statistics from CPU 1 Total swap space 128.
STATUS KMSF NSKCOM Command Reference Interpret this data as follows: Total swap space Total number of megabytes (MB) that are currently allocated in KMS files for the processor. Reserved CPU Pages Total memory pages that are currently allocated for the processor. Available pages Total number of memory pages currently available in swap files for the processor. Creates Total number of reservations made for process creations since the processor loaded.
NSKCOM Command Reference STATUS SWAPD[ISK] STATUS SWAPD[ISK] Example 4-19 shows the STATUS command used with the SWAPDISK attribute.The SWAPDISK attribute displays the processes that have dependencies on a swap disk. Example 4-19.
NSKCOM Command Reference TIME Command Activity in the file continues until all processes using the file have terminated. When you enter this command, a STOP mark is added to the file’s entry in the configuration file, ZSYSCFG. The STOP mark is persistent across processor reloads and system loads. Note. If the target swap file is the only swap file open, NSKCOM responds with the error “Cannot Stop a CPU’s last open swapfile!” and does not stop the file.
NSKCOM Command Reference VER[SION] Command VER[SION] Command The VERSION command displays KMSF version information. VER[SION] Here is an example of this command: NSK-VERSION NSKCOM - T5838H01 BASE (01OCT04) - Apr 15 2005 NSK- VOL[UME] Command The VOLUME command establishes the default volume or subvolume for qualifying file names in subsequent commands. Your current volume is the default. VOL[UME] [volume-name | volume-name.subvol-name | subvol-name ] volume-name specifies the new default volume.
NSKCOM Command Reference Kernel-Managed Swap Facility (KMSF) Manual—425824-005 4- 36 VOL[UME] Command
5 Operator Messages for KMSF Messages are Generated Under the NSK Subsystem Name This section describes all of the operator messages that are generated by the Kernel-Managed Swap Facility (KMSF). These messages appear under NSK, the subsystem name for the operating system. For a complete list of messages generated under the NSK subsystem name, refer to NSK (NonStop Kernel) Messages in the Operator Messages Manual. 200 For G06.
201 Operator Messages for KMSF num-extents identifies the maximum number of extents the identified swap file can use. file-size-reserved identifies the maximum size to which the identified swap file can grow. total-file-size identifies the currently allocated size of the identified swap file. Cause. Usage of the specified kernel-managed swap file exceeded its configured threshold. Effect. The effect depends on how high the value of swap space utilization is.
202 Operator Messages for KMSF 202 KMSF SWAPFILE PURGED: swapfile [ CPU cpu ] swapfile identifies the purged kernel-managed swap file. cpu is the processor associated with the swap file if the processor is known; otherwise, no value is shown. Cause. A kernel-managed swap file has been purged by the NSKCOM DELETE command. Effect. The swap file is no longer available for use. Recovery. Informational message only; no corrective action is needed.
204 Operator Messages for KMSF 204 KMSF SWAPFILE STOPPED: swapfile CPU cpu swapfile identifies the kernel-managed swap file. cpu is the processor associated with the swap file. Cause. A user stopped usage of the specified swap file by entering the NSKCOM STOP command, or the disk that the swap file was on went down. Effect. Swapping to the specified swap file is prevented. If the swap file’s disk went down, processes swapping to the file are abended.
206 Operator Messages for KMSF 206 KMSF SWAPFILE MAXEXTENTS ALTERED: maxextents CPU cpu swapfile NEW VALUE swapfile identifies the kernel-managed swap file. maxextents identifies the new maximum number of extents configured for the swap file. cpu is the processor associated with the swap file. Cause. A user entered the NSKCOM ALTER command and specified new MAXEXTENTS. Effect. The swap file’s size has been changed to the new MAXEXTENTS. Recovery.
Operator Messages for KMSF 208 208 KMSF SWAPFILE STOP PENDING: swapfile CPU cpu swapfile identifies the kernel-managed swap file. cpu is the processor associated with the swap file. Cause. The NSKCOM STOP command was issued against the specified swap file. Effect. The swap file does not accept any new processes, and its existing processes are not affected. The swap file remains in use until all processes using the file have terminated. The ZSYSCFG file is modified to mark the swap file with a STOP mark.
Operator Messages for KMSF 210 210 KMSF CONFIGURATION FILE NOT FOUND: config-file config-file identifies the Kernel-Managed Swap Facility (KMSF) configuration file. Cause. A processor being disk booted or bus booted did not find or could not open the KMSF configuration file, $SYSTEM.SYSTEM.ZSYSCFG. Effect. If space is available on $SYSTEM, KMSF creates and opens a default swap file, $SYSTEM.ZSYSSWAP.SWAPnn, where nn represents the processor number. Otherwise, the processor halts with halt code %3055.
Operator Messages for KMSF 213 If there are multiple lines with errors in the ZSYSCFG file, this message is generated for each line. Effect. The specified line of the configuration file is ignored. Any swap file specified on the line is not added or enabled for use. If there is no swap file configured for a processor, KMSF attempts to create a default swap file for the processor. If KMSF cannot create a default swap file, the processor does not come up.
Operator Messages for KMSF 214 processor loaded, use the NSKCOM START command to enable use of the swap file. If the processor did not load, ensure that the disk the swap file is on is up when the processor is loaded and reload the processor. 214 KMSF SWAPFILE START FAILED: swapfile CPU cpu swapfile identifies the kernel-managed swap file. cpu is the processor that the swap file is configured for. Cause.
Operator Messages for KMSF 215 215 KMSF DEFAULT SWAPFILE USED: swapfile swapfile identifies the kernel-managed swap file. Cause. During system startup, the operating system either was unable to enable the configured swap files for use or no swap files were configured. The operating system created and enabled a default swap file for use. This error might occur because a configured file was on a disk that was not yet up. Effect. Processes swap to the default swap file. Recovery.
Index A ADD command 4-2/4-4 Adding swap files Description of 3-11 quick start for new systems 2-4/2-6 See also ADD command ALTER command 4-5/4-7 Altering swap files 2-6, 3-12 See also ALTER command ASSUME command 4-8/4-11 Attributes of kernel-managed swap files See also ADD command See also ALTER command changing the value of 3-12 default values for 4-2, 4-5 C Checking swap files 3-7 See also STATUS command Checking the current configuration 3-9 See also INFO command Commands, NSKCOM 4-1, 4-35 See also ind
E Index Deleting swap files 3-13 See also DELETE command Description of 4-1/4-35 Disks down, and deleting swap files 4-15 mirrored, and swap files 2-2 space requirements for $SYSTEM 1-10 H E K ENV command 4-15 EOF of kernel-managed swap files 3-4 Errors See Messages, operator See Process creation errors Event Management Service (EMS) See Messages, operator EXIT command 4-17 EXT attribute ADD command 4-2 ALTER command 4-5 ASSUME command 4-8 Kernel-managed swapping components of 1-3 impact on users 1-3
N Index Messages, operator (continued) SWAPFILE MAXEXTENTS ALTERED... (message 206) 5-5 SWAPFILE NOT FOUND... (message 213) 5-8 SWAPFILE PURGE PENDING... (message 209) 5-6 SWAPFILE PURGED... (message 202) 5-3 SWAPFILE START FAILED... (message 214) 5-9 SWAPFILE STARTED... (message 203) 5-3 SWAPFILE STOP PENDING... (message 208) 5-6 SWAPFILE STOPPED... (message 204) 5-4 SWAPFILE THRESHOLD ALTERED...
T Index Swap files (continued) changing the attributes of 4-5 characteristics of 1-7/1-9 configuring to avoid processor halts 2-1 conventional 1-1 characteristics of 1-1 swap statistics 4-27 definition of 1-1 deleting 3-13 end-of-file (EOF) 3-4 file security 3-3 guidelines for configuring 2-3/2-4 kernel-managed 1-2 location of 2-2 monitoring 3-1 naming conventions 2-2 ownership of 3-3 peak usage of 3-2 reservation creation failures 3-2 starting the use of 3-11 stopping 3-12 when loading processors 1-5 SWA
