Software Release Bulletin: VOS Release 14.5.0 Stratus Technologies R914-05 Notice The information contained in this document is subject to change without notice. UNLESS EXPRESSLY SET FORTH IN A WRITTEN AGREEMENT SIGNED BY AN AUTHORIZED REPRESENTATIVE OF STRATUS TECHNOLOGIES, STRATUS MAKES NO WARRANTY OR REPRESENTATION OF ANY KIND WITH RESPECT TO THE INFORMATION CONTAINED HEREIN, INCLUDING WARRANTY OF MERCHANTABILITY AND FITNESS FOR A PURPOSE. Stratus Technologies assumes no responsibility or obligation of any kind for any errors contained herein or in connection with the furnishing, performance, or use of this document. Software described in Stratus documents (a) is the property of Stratus Technologies International, S.a r.l. or the third party, (b) is furnished only under license, and (c) may be copied or used only as expressly permitted under the terms of the license. Stratus documentation describes all supported features of the user interfaces and the application programming interfaces (API) developed by Stratus. Any undocumented features of these interfaces are intended solely for use by Stratus personnel and are subject to change without warning. This document is protected by copyright. All rights are reserved. No part of this document may be copied, reproduced, or translated, either mechanically or electronically, without the prior written consent of Stratus Technologies. Stratus, the Stratus logo, Continuum, Continuous Processing, StrataLINK, and StrataNET are registered trademarks of Stratus Technologies International, S.a r.l. The Stratus Technologies logo, ftServer, ftServer with design, Stratus 24 x 7 with design, The World's Most Reliable Servers, The World's Most Reliable Server Technologies, ftMemory, ftMessaging, ftStorage, Selectable Availability, XA/R, SQL/2000, and The Availability Company are trademarks of Stratus Technologies International, S.a r.l. RSN is a trademark of Lucent Technologies, Inc. All other trademarks are the property of their respective owners. TCP Wrappers copyright information: Copyright (c) 1987 Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED "AS IS"' AND WITHOUT ANY EXPRESS OR IMPLIED SRB: VOS Release 14.5.0 (R914) FRONT-1 WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. Copyright 1995 by Wietse Venema. All rights reserved. Some individual files may be covered by other copyrights. This material was originally written and compiled by Wietse Venema at Eindhoven University of Technology, The Netherlands, in 1990, 1991, 1992, 1993, 1994 and 1995. Redistribution and use in source and binary forms are permitted provided that this entire copyright notice is duplicated in all such copies. This software is provided "as is" and without any expressed or implied warranties, including, without limitation, the implied warranties of merchantability and fitness for any particular purpose. Manual Name: Software Release Bulletin: VOS Release 14.5.0 Part Number: R914 Revision Number: 05 VOS Release Number: 14.5.0 Printing Date: April 2002 Stratus Technologies, Inc. 111 Powdermill Road Maynard, Massachusetts 01754-3409 (c) 2002 Stratus Technologies International, S.a r.l. All rights reserved. SRB: VOS Release 14.5.0 (R914) FRONT-2 SRB: VOS Release 14.5.0 (R914) FRONT-3 Contents -------- Preface xv Introduction to VOS Release 14.5.0 1-1 Overview 1-2 Highlights of VOS Release 14.5.0 1-2 Changes Beginning in VOS Release 14.5.0 1-3 New Hardware 1-4 Software Enhancements 1-9 Layered Product Support 1-15 Products Not Supported in This VOS Release 1-16 XA2000-Series Modules 1-16 XA/R-Series Modules 1-16 C-Series Hardware 1-17 Software Products 1-17 Year-2000 (Y2K) Certification 1-18 Notice of a Change in an Upcoming Release 1-19 Removal of harvest_meters.pm 1-19 Product End-of-Life Notices 1-19 VOS Release Notation 1-23 New and Changed Documentation 1-24 New and Revised Manuals 1-24 The VOS StrataDOC Online Documentation System 1-26 The >system>doc Directory 1-26 VOS Updates and Errata Files 1-28 Customer Survey 1-28 Operation and Administration 2-1 Changes to the module_start_up.cm Command Macro 2-2 SRB: VOS Release 14.5.0 (R914) TOC-1 Contents Continuum-Series Modules 2-4 CPU/Memory Boards 2-5 PA-8000 Processors 2-5 PA-8500 Processors 2-6 PA-8600 Processors 2-6 Larger Memory Sizes 2-7 Configurations 2-7 Summary of Processors for Continuum-Series Modules 2-9 New System Console Command 2-10 Change to the reset_configuration Command 2-10 Auto Recovery for Hung Modules 2-10 New Tape Drives 2-11 Disk-Related Changes 2-11 Changes to the D700 Subsystem 2-11 New Disk Commands 2-14 Changed Disk Commands 2-17 Changes to display_disk_label 2-18 Changes to display_disk_info 2-19 Changes to initialize_boot_disk 2-19 Changes to initialize_disk and initialize_duplex_disk 2-19 Changes to set_partition_size 2-20 Changes to salvage_disk 2-20 System Error Log Changes 2-21 SRB: VOS Release 14.5.0 (R914) TOC-2 Contents Changes to start_disk_recovery 2-22 Changes to update_disk_label 2-22 Changes to Disk-Related analyze_system Requests 2-25 Changes to the dump_disk_info Request 2-25 Changes to the disk_meters Request 2-25 New Disk-Related analyze_system Requests 2-25 The list_disk_params Request 2-26 The set_disk_param Request 2-26 Open Disk Support 2-26 Streamlining Disk Renames 2-26 New Disk Salvaging Behavior 2-27 Tape-Related Changes 2-28 Default Expiration Date Change 2-28 Tape Subsystem Changes 2-28 The T705 and T706 Tape Drives 2-29 Booting from Tape 2-30 New Tape Commands 2-30 Changed Tape Commands 2-30 The V105 Terminal and Other Terminal Support Issues 2-30 Miscellaneous Changes to the analyze_system Command 2-31 The analyze_system Command Argument -c_expressions 2-31 Expanded dump_vm_pool_info Display 2-32 New dump_sdlmux Request 2-32 New dump_dlmux_info Request 2-33 SRB: VOS Release 14.5.0 (R914) TOC-3 Contents The VOS Dead-CPU Time-Out Value 2-33 Freezing and Thawing Processes 2-33 Terminating Dumps Prematurely 2-34 Tuning the File System Cache Manager 2-36 Device and Firmware Configuration Summary 2-37 Changes to General User Commands 2-37 Changes to the compare_files Command 2-38 Changes to the network_watchdog Command 2-38 Changes to the save Command 2-38 Changes to the start_logging Command 2-39 Changes to the start_process and batch Commands 2-39 Change to the who_locked Command 2-39 Changes to Security-Related Commands 2-40 Changes to the set_registration_info Command 2-40 Changes to the registration_admin Command 2-40 Changes to System Administration Commands 2-42 Changes to the set_scheduler_info Command 2-42 Changes to the test_index Command 2-42 Changes to the dump_memory Command 2-43 Changes to the Manual Boot Procedure 2-43 Change to Home Directory During Automatic Startup 2-44 Change to the devices.tin File 2-44 Change to the languages.tin File 2-45 The VOS Operating System 3-1 Changes to the Cache Manager 3-1 SRB: VOS Release 14.5.0 (R914) TOC-4 Contents Changes to the VOS STREAMS Memory Allocator 3-2 Creating Meter Files Using the analyze_system Command 3-4 Resetting Meters 3-4 Logical Volumes and the Paging Partition of Nonboot Disks 3-5 Pre-login Processes 3-5 Process Management 3-5 Increase in Ports per Process and Events per Module 3-6 Setting and Displaying VOS STREAMS Parameters 3-6 Time-Zone Changes 3-7 New Information in the Disk Label 3-7 Additional Time Zones 3-7 Time Zone Changes to the analyze_system Command 3-10 General User Interface 4-1 Office/2000 4-1 New Commands 4-2 Changed Commands 4-3 Obsolete Commands 4-16 New and Changed Command Functions 4-17 The (iso_date) Command Function 4-17 The (iso_date_time) Command Function 4-17 The (module_info) Command Function 4-18 The (process_info) Command Function 4-18 Emacs Changes 4-18 The STOPPROCESS Condition Handler 4-18 Change to the save_file Request 4-18 SRB: VOS Release 14.5.0 (R914) TOC-5 Contents New Control Arguments 4-19 Communications 5-1 Products Supported on Continuum-Series Modules 5-1 Continuum-Series Modules 5-2 Modules with PA-7100 Processors 5-3 Products Not Supported on Continuum-Series Modules 5-4 Improvements Affecting STREAMS Drivers 5-4 Loading and Unloading STREAMS Drivers 5-4 New and Changed STREAMS Requests in analyze_system 5-5 New Daemon Processes 5-6 Unloadable Host Remote STREAMS Driver (hrsd) 5-6 The K115-10 Token-Ring I/O Adapter 5-7 Configuring the K115-10 I/O Adapter for 16-Mbps Line Speed 5-7 New K115 I/O Adapter (Token Ring) Request in analyze_system 5-8 Configuring the K115-00 I/O Adapter 5-8 Determining the Maximum Number of Link Stations 5-8 Changes to X.25 and X.25 T1 5-8 Change to the Multiplexed Host Interface (MHI) 5-10 Changes to the UCOMM Binder Control File 5-11 TCP/IP Products 5-11 General Requirements for STCP and OS TCP/IP 5-12 Running Both STCP and OS TCP/IP on the Same SRB: VOS Release 14.5.0 (R914) TOC-6 Contents Module 5-12 Network Interfaces and Required Drivers 5-13 Overview of STCP 5-14 STCP Administration 5-15 OSPF Support 5-22 STCP Programming 5-22 Enhanced Support for Migrating OS TCP/IP Applications 5-24 Changes to the NFS Facility 5-24 Changes to OS TCP/IP 5-25 Basic Configuration Requirements 5-25 Change in the Location of Lower-Level Drivers 5-26 New Arguments for the ftpd Daemon in OS TCP/IP 5-26 Summary of Changes to OS TCP/IP Since VOS Release 13.0 5-27 STCP and TCP Wrappers Functionality 5-28 Overview of TCP Wrappers Functionality 5-29 New and Changed Daemons and Files for TCP Wrappers Functionality 5-30 Unsupported Features of TCP Wrappers 5-31 Configuring TCP Wrappers Functionality 5-31 Configuring the Daemons 5-31 The inetd.conf File and TCP Wrappers Functionality 5-32 The hosts.allow and hosts.deny Database Files 5-32 SRB: VOS Release 14.5.0 (R914) TOC-7 Contents Troubleshooting TCP Wrappers 5-32 STCP and POSIX.1 Compliance 5-33 Overview of STCP Changes for POSIX.1 Compliance 5-33 New Files for POSIX.1-Compliance 5-35 The start_inetd.cm and stop_inetd.cm Command Macros 5-35 The tftpd.pm and bootpd.pm Program Modules 5-35 The inetd.conf File 5-35 The inetd.conf File and the kill Command 5-36 The tftplog Log File 5-36 New Arguments for the inetd and tftpd Daemons 5-36 Changes to Existing Components of STCP 5-37 The Data-Link Multiplexer: SDLMUX and DLMUX 5-38 SDLMUX 5-38 DLMUX 5-39 VOS Open StrataLINK 5-40 Open StrataLINK Changes for VOS Release 13.2.0 and Later 5-42 Intermodule Compatibility 5-43 Open StrataLINK and STCP 5-44 Changes Affecting Window Terminal Devices 5-45 New sys_info$wtm_allow_multiple_user External Variable 5-45 New Argument for the set_terminal_parameters Command 5-46 SRB: VOS Release 14.5.0 (R914) TOC-8 Contents New Window Terminal Opcodes 5-47 New VOS Forms Management System (FMS) Subroutines 5-47 Enhanced Polling Support 5-48 The File System 6-1 Support for Byte and Record Count in File Entries 6-1 Overview of Byte and Record Count 6-1 VOS Commands Affected by Byte and Record Count Support 6-2 Changes to the display_file_status Command 6-2 Changes to the verify_end_of_file Command 6-3 VOS Subroutines Affected by Byte and Record Count Support 6-3 Creating Deleted Record Indexes for Fixed Files 6-3 Cache Manager Improvements 6-4 Disk and Cache Manager Improvements 6-5 Maximum Cache Size 6-6 New s$control Opcodes 6-6 New Cache-Related Tuning Arguments 6-7 Cache Buffer Pinning Replaced 6-11 Changes to the dump_cache Request in analyze_system 6-12 Changes to the dump_cache_info Request in analyze_system 6-16 Changes to the cache_meters Request in analyze_system 6-17 SRB: VOS Release 14.5.0 (R914) TOC-9 Contents New and Changed Arguments to the cache_meters Request 6-17 Cache Health and Status Displays 6-21 Change to the Hit/Miss Data Displayed 6-23 Per-Disk Metering Information 6-24 Changes to the dump_afte and dump_axte Requests in analyze_system 6-24 Changes to the dump_disk_info Command 6-25 Dynamically Allocated Extents (DAE) 6-26 File Layout 6-27 Command Changes 6-27 The create_file Command 6-28 The create_index Command 6-28 The display_file_status Command 6-29 The recreate_index Command 6-33 The restore command 6-35 The set_file_allocation Command 6-35 The verify_save Command 6-36 The where_block Command 6-36 Reclaiming DAE Reserved Space 6-36 Subroutine Changes 6-37 Minimizing Disk Fragmentation 6-38 Free-Space Emergencies 6-39 DAE-Related Changes to analyze_system Requests 6-40 The dump_adt Request 6-40 SRB: VOS Release 14.5.0 (R914) TOC-10 Contents The dump_adte Request 6-41 The dump_afte Request 6-41 The dump_axte Request 6-42 The dump_bmt Request 6-43 Languages 7-1 Changes to the C Runtime and C Cross Runtime Products 7-1 Changes to the VOS Binder 7-2 Changes to the bind Command 7-2 New Binder Control-File Directive 7-3 New Predefined Preprocessor Variable 7-3 Obsolete bind_kernel Command 7-4 Stacks, Heaps, and Fences 7-4 Changes to the VOS Compilers 7-4 General Changes to the VOS Compilers 7-4 Cross-Compiler Support 7-5 New Processor Value 7-5 New Predefined Preprocessor Variables 7-5 Source Line Limit Increased 7-6 Symbol Table Size Increased 7-6 VOS C and VOS Standard C Compilers 7-6 Saving Arguments on the Stack for C Programs 7-7 New Function and Macros 7-8 Changes to C I/O Functions 7-10 VOS COBOL Compiler 7-10 The current-date Function 7-10 SRB: VOS Release 14.5.0 (R914) TOC-11 Contents VOS PL/I Compiler 7-11 The datetime Function 7-12 Saving Arguments on the Stack for PL/I Programs 7-12 Changes to the VOS Symbolic Debugger 7-13 POSIX.1 Support 7-14 Preparing Your System for VOS POSIX.1 7-15 Building VOS POSIX.1 Applications 7-15 Product Limitations 7-16 Compatibility Issues 7-16 Administrative Changes 7-17 Changed Functions 7-17 New Functions 7-17 New Processes 7-18 New Commands 7-18 New Subroutines 7-19 Additional Documentation 7-19 Subroutines 8-1 New Subroutines 8-1 New Subroutines Documented in the Subroutines Manuals 8-1 New Subroutines Not Documented in the Subroutines Manuals 8-2 The s$connect_vm_region3 Subroutine 8-3 The s$disconnect_vm_region3 Subroutine 8-4 The s$get_object_status Subroutine 8-5 The s$get_registration_info Subroutine 8-11 SRB: VOS Release 14.5.0 (R914) TOC-12 Contents The s$perform_ext_authentication Subroutine 8-15 Changed Subroutines 8-21 Subroutine Changes Documented in the Subroutines Manuals 8-21 Subroutine Changes Not Documented in the Subroutines Manuals 8-23 Changes to the s$control Subroutine 8-23 Changes to the s$copy_file Subroutine 8-24 Changes to the s$create_extent_file Subroutine 8-24 Changes to the s$create_extent_index Subroutine 8-24 Changes to the s$expand_star_info Subroutine 8-24 Changes to the s$get_file_status Subroutine 8-24 Changes to the s$get_index_status Subroutine 8-26 Changes to the s$get_open_file_info Subroutine 8-26 Changes to the s$get_port_info Subroutine 8-26 Changes to the s$get_process_dir and s$get_temp_file Subroutines 8-28 Changes to the s$get_process_info Subroutine 8-28 Changes to the s$get_processes_info Subroutine 8-30 Changes to the s$list_devices Subroutine 8-31 SRB: VOS Release 14.5.0 (R914) TOC-13 Contents New FMS Subroutines 8-31 The s$fms_move_subwindow_to_frnt Subroutine 8-31 The s$fms_move_subwindow_to_back Subroutine 8-33 The Transaction Processing Facility 9-1 Changes to TPF Subroutines 9-1 Change to the s$msg_rewrite Subroutine 9-1 The s$msg_send Subroutine 9-2 TPF Performance Improvements 9-2 Criteria Used to Abort Transactions 9-3 Minimum Wait Period Change 9-4 Lock-Conflict Logging Changes 9-5 Transaction Metering Improvements 9-5 Deadlock Detection 9-5 Transaction Priority Enhancements 9-6 I/O Operations and Aborts 9-6 New TP Lock Manager 9-7 Processing Delays Eliminated during Transaction Log Switches 9-7 New TPOverseer Error Messages 9-7 New TPF-Related analyze_system Requests 9-8 New TPF Include File 9-8 Installation Procedures and Customer Assistance 10-1 Installing Software 10-1 Installing VOS 10-2 Layered Product License Agreement 10-3 SRB: VOS Release 14.5.0 (R914) TOC-14 Contents The display_software_purchased Command 10-3 Upgrading from PA-7100 to a PA-8X00 Processor 10-4 The Verification Phase 10-4 The Pre-boot Phase 10-5 The Post-boot Phase 10-6 Installation with Low Disk Space 10-7 Downgrading 10-9 Downgrading from VOS Release 14.5.0 10-9 The locate_dae_files Tool 10-9 Downgrading from a PA-8X00 Processor to a PA-7100 Processor 10-10 Setting the Calendar/Clock 10-10 Contacting the CAC 10-11 Manual List for VOS Products A-1 SRB: VOS Release 14.5.0 (R914) Figures ------- Figure 6-1.Percentage Components of the Cache Health Display 6-23 Figure 6-2.Time Components of the Cache Health Display 6-24 SRB: VOS Release 14.5.0 (R914) Tables ------ Table 1-1.New and Changed VOS Commands 1-11 Table 1-2.VOS Release Notation1-24 Table 1-3.Documentation Files in the >system>doc Directory 1-28 Table 2-1.CPU/Memory Board Configurations 2-7 Table 2-2.Processors for Continuum-Series Modules 2-9 Table 3-1.Time Zones Supported in VOS 3-7 Table 5-1.The Network Interfaces and Drivers Required to Support STCP or OS TCP/IP 5-14 Table 5-2.Network Interface and Drivers That Support OS TCP/IP 5-27 Table 5-3.Summary of OS TCP/IP Changes 5-29 Table 5-4.Documentation for Related SDLMUX Information 5-42 Table 5-5.Documentation for Related DLMUX Information 5-43 Table 5-6.Documentation Needed to Configure Open StrataLINK for STCP 5-48 Table 7-1.C and POSIX Include Files 7-1 Table 7-2.Predefined Preprocessor Variables 7-6 Table 7-3.Character Positions Returned by the current-date Function 7-11 Table 7-4.Components of the datetime Function 7-12 Table 10-1.Worldwide CAC Telephone Numbers 10-11 Table A-1.VOS StrataDOC CD A-3 Table A-2.General System and User Manuals A-3 Table A-3.Subroutines Manuals A-8 Table A-4.Language/Programming Manuals A-9 Table A-5.Communications Manuals A-11 Table A-6.Transaction Processing Facility (TPF) Manuals A-17 Table A-7.Forms Management System (FMS) Manuals A-17 Table A-8.JYACC Application Manager (JAM) Manuals A-19 SRB: VOS Release 14.5.0 (R914) LOT-1 Tables Table A-9.Systems Network Architecture (SNA) Manuals A-20 Table A-10.Technical Reports A-20 SRB: VOS Release 14.5.0 (R914) Preface ======= The Software Release Bulletin: VOS Release 14.5.0 (R914) documents VOS Release 14.5.0. This manual is intended for those who administer and/or use Stratus computers. Much of the information in this SRB is directed to experienced VOS users. Manual Version -------------- This manual is a revision. Change bars, which appear in the margin, note the specific changes to text since the previous publication of this manual. Note, however, that change bars are not used in new chapters or appendixes. Manual Organization ------------------- This manual contains 10 chapters and 1 appendix. Chapter 1 provides general information about VOS Release 14.5.0. Chapter 2 describes changes that affect the operation and administration of Stratus systems. Chapter 3 discusses changes to the VOS operating system. Chapter 4 discusses changes to the general user interface. Chapter 5 describes changes to VOS communications products. Chapter 6 describes changes to the file system. Chapter 7 discusses changes to the VOS language products. Chapter 8 describes changes to the VOS subroutines. Chapter 9 describes changes to the Transaction Processing Facility (TPF). Chapter 10 discusses changes pertaining to installation procedures and also describes how to contact the nearest Stratus Customer Assistance Center (CAC). Appendix A lists all of the manuals available for VOS products. SRB: VOS Release 14.5.0 (R914) PREF-1 Manual Organization Notation Conventions -------------------- This manual uses the following notation conventions. o Italics introduces or defines new terms. For example: The master disk is the name of the member disk from which the module was booted. o Boldface emphasizes words in text. For example: Every module must have a copy of the module_start_up.cm file. o Monospace represents text that would appear on your terminal's screen (such as commands, subroutines, code fragments, and names of files and directories). For example: change_current_dir (master_disk)>system>doc o Monospace italic represents terms that are to be replaced by literal values. In the following example, the user must replace the monospace-italic term with a literal value. list_users -module module_name o Monospace bold represents user input in examples and figures that contain both user input and system output (which appears in monospace). For example: display_access_list system_default %dev#m1>system>acl>system_default w *.* Key Mappings for VOS Functions ------------------------------ VOS provides several command-line and display-form functions. Each function is mapped to a particular key or combination of keys on the terminal keyboard. To perform a function, you press the appropriate key(s) from the command-line or display form. For an explanation of the command- line and display-form functions, see the manual Introduction to VOS (R001). SRB: VOS Release 14.5.0 (R914) PREF-2 Key Mappings for VOS Functions The keys that perform specific VOS functions vary depending on the terminal. For example, on a V103 ASCII terminal, you press the and keys simultaneously to perform the INTERRUPT function; on a V105 PC/+ 106 terminal, you press the <1> key on the numeric keypad to perform the INTERRUPT function. Note: Certain applications may define these keys differently. Refer to the documentation for the application for the specific key mappings. The following table lists several VOS functions and the keys to which they are mapped on commonly used Stratus terminals and on an IBM PC (r) or compatible PC that is running the Stratus PC/Connect-2 software. (If your PC is running another type of software to connect to a Stratus host computer, the key mappings may be different.) For information about the key mappings for a terminal that is not listed in this table, refer to the documentation for that terminal. --------------------------------------------------------------------------- | : : : IBM PC : : | | : : : or : : | | : V103 : V103 : Compatibl : V105 : V105 | | : : : e PC : : | | VOS Function : ASCII : EPC : : PC/+ 106 : ANSI | |-------------------------------------------------------------------------| | CANCEL : : * : * + : <5> + : | | : : FOOTNOTE: : : or * + : | | : : 1 : : : | |-------------------------------------------------------------------------| | CYCLE : : : - : <4> + : | |-------------------------------------------------------------------------| | CYCLE BACK : : - : - : <7> + : - | | : - : : : : | |-------------------------------------------------------------------------| | DISPLAY FORM : : - + : - + : <6> + : | | : : : : or - + : or | | : : : : : - | | : : : : : | |-------------------------------------------------------------------------| | HELP : : - : - : - : | | : - : : : : | |-------------------------------------------------------------------------| | INSERT DEFAULT: : - : - : - : | | : - : : : : | |-------------------------------------------------------------------------| | INSERT SAVED : : : : : | |-------------------------------------------------------------------------| | INTERRUPT : : - : - : <1> + : - | | : - : : : : | SRB: VOS Release 14.5.0 (R914) PREF-3 Key Mappings for VOS Functions |-------------------------------------------------------------------------| | NO PAUSE : : - : -

: <8> + : - | | : - : * + : : : | --------------------------------------------------------------------------- FOOTNOTE: 1 Numeric-keypad key Format for Commands and Requests -------------------------------- Stratus manuals use the following format conventions for documenting commands and requests. (A request is typically a command used within a subsystem, such as analyze_system). Note that the command and request descriptions do not necessarily include each of the following sections. name The name of the command or request is at the top of the first page of the description. Privileged This notation appears after the name of a command or request that can be issued only from a privileged process. (See the online glossary, which is located in the file >system>doc>glossary.doc, for the definition of privileged process.) Purpose Explains briefly what the command or request does. Display Form Shows the form that is displayed when you type the command or request name followed by -form or when you press the key that performs the DISPLAY FORM function. Each field in the form represents a command or request argument. If an argument has a default value, that value is displayed in the form. (See the online glossary for the definition of default value.) The following table explains the notation used in display forms. The Notation Used in Display Forms ------------------------------------------------------------------------ | Notation : Meaning | |----------------------------------------------------------------------| | : Required field with no default value. | |----------------------------------------------------------------------| | : The cursor, which indicates the current | | : position on the screen. For example, the | | : cursor may be positioned on the first | | : character of a value, as in ll. | |----------------------------------------------------------------------| SRB: VOS Release 14.5.0 (R914) PREF-4 Format for Commands and Requests | current_user : The default value is the current user, | | : module, system, or disk. The actual name is | | current_module : displayed in the display form of the command | | : or request. | | current_system : | | : | | current_disk : | ------------------------------------------------------------------------ Command-Line Form Shows the syntax of the command or request with its arguments. You can display an online version of the command-line form of a command or request by typing the command or request name followed by -usage. The following table explains the notation used in command-line forms. In the table, the term multiple values refers to explicitly stated separate values, such as two or more object names. Specifying multiple values is not the same as specifying a star name. (See the online glossary for the definition of star name.) When you specify multiple values, you must separate each value with a space. The Notation Used in Command-Line Forms ------------------------------------------------------------------------- | Notation : Meaning | |-----------------------------------------------------------------------| | argument_1 : Required argument. | |-----------------------------------------------------------------------| | argument_1... : Required argument for which you can specify | | : multiple values. | |-----------------------------------------------------------------------| | : Set of arguments that are mutually exclusive; | | : you must specify one of these arguments. | | {} : | | : | | : | |-----------------------------------------------------------------------| | [argument_1] : Optional argument. | |-----------------------------------------------------------------------| | [argument_1]... : Optional argument for which you can specify | | : multiple values. | |-----------------------------------------------------------------------| | : Set of optional arguments that are mutually | | : exclusive; you can specify only one of these | | {} : arguments. | | : | | : | |-----------------------------------------------------------------------| | Note: Dots, brackets, and braces are not literal characters; you | | should not type them. Any list or set of arguments can contain more | SRB: VOS Release 14.5.0 (R914) PREF-5 Format for Commands and Requests | than two elements. Brackets and braces are sometimes nested. | ------------------------------------------------------------------------- Arguments Describes the command or request arguments. The following table explains the notation used in argument descriptions. The Notation Used in Argument Descriptions ------------------------------------------------------------------------ | Notation : Meaning | |----------------------------------------------------------------------| | : There are predefined values for this argument. | | : In the display form, you display these values | | : in sequence by pressing the key that performs | | : the CYCLE function. | |----------------------------------------------------------------------| | Required : You cannot issue the command or request without | | : specifying a value for this argument. | | : | | : | | : | | : If an argument is required but has a default | | : value, it is not labeled Required since you do | | : not need to specify it in the command-line | | : form. However, in the display form, a required | | : field must have a value--either the displayed | | : default value or a value that you specify. | |----------------------------------------------------------------------| | (Privileged) : Only a privileged process can specify a value | | : for this argument. | ------------------------------------------------------------------------ The following additional headings may appear in the command or request description: Explanation, Error Messages, Examples, and Related Information. Explanation Explains how to use the command or request and provides supplementary information. Error Messages Lists common error messages with a short explanation. Examples Illustrates uses of the command or request. Related Information Refers you to related information (in this manual or other manuals), including descriptions of commands, subroutines, and requests that you can SRB: VOS Release 14.5.0 (R914) PREF-6 Format for Commands and Requests use with or in place of this command or request. Format for Subroutines ---------------------- Stratus manuals use the following format conventions for documenting subroutines. Note that the subroutine descriptions do not necessarily include each of the following sections. subroutine_name The name of the subroutine is at the top of the first page of the subroutine description. Purpose Explains briefly what the subroutine does. Usage Shows how to declare the variables passed as arguments to the subroutine, declare the subroutine entry in a program, and call the subroutine. Arguments Describes the subroutine arguments. Explanation Provides information about how to use the subroutine. Error Codes Explains some error codes that the subroutine can return. Examples Illustrates uses of the subroutine or provides sample input to and output from the subroutine. Related Information Refers you to other subroutines and commands similar to or useful with this subroutine. Online Documentation -------------------- Stratus provides the following types of online documentation. o The directory >system>doc provides supplemental online documentation, including updates and corrections to Stratus manuals and a glossary of terms. SRB: VOS Release 14.5.0 (R914) PREF-7 Online Documentation o The VOS StrataDOC Web site is an online-documentation service provided by Stratus. It enables Stratus customers to view, search, download, print, and comment on VOS technical manuals via a common Web browser. It also provides the latest updates and corrections available on the VOS document set. If you are a Stratus customer with a current support contract, you can access the VOS StrataDOC Web site, at no charge, at http://stratadoc.stratus.com. You can also order the VOS StrataDOC CD- ROM from Stratus. This manual is available on the VOS StrataDOC Web site. For information about accessing the VOS StrataDOC Web site, contact the Stratus Customer Assistance Center (CAC). For information about ordering the VOS StrataDOC CD-ROM, see the next section, "Ordering Manuals." Ordering Manuals ---------------- You can order manuals in the following ways. o If your system is connected to the Remote Service Network (RSN(tm)), issue the maint_request command at the system prompt. Complete the on-screen form with all of the information necessary to process your manual order. o Customers in North America can call the Stratus Customer Assistance Center (CAC) at (800) 221-6588 or (800) 828-8513, 24 hours a day, 7 days a week. All other customers can contact their nearest Stratus sales office, CAC office, or distributor; see the file cac_phones.doc in the directory >system>doc for CAC phone numbers outside the U.S. Manual orders will be forwarded to Order Administration. Commenting on This Manual ------------------------- You can comment on this manual by using the command comment_on_manual or by completing the customer survey that appears at the end of this manual. To use the comment_on_manual command, your system must be connected to the RSN. If your system is not connected to the RSN, you must use the customer survey to comment on this manual. SRB: VOS Release 14.5.0 (R914) PREF-8 Commenting on This Manual The comment_on_manual command is documented in the manual VOS System Administration: Administering and Customizing a System (R281) and the VOS Commands Reference Manual (R098). There are two ways you can use this command to send your comments. o If your comments are brief, type comment_on_manual, press or , and complete the data-entry form that appears on your screen. When you have completed the form, press . o If your comments are lengthy, save them in a file before you issue the command. Type comment_on_manual followed by -form, then press or . Enter this manual's part number, R914, then enter the name of your comments file in the -comments_path field. Press the key that performs the CYCLE function to change the value of -use_form to no and then press . Note: If comment_on_manual does not accept the part number of this manual (which may occur if the manual is not yet registered in the manual_info.table file), you can use the mail request of the maint_request command to send your comments. Your comments (along with your name) are sent to Stratus over the RSN. Stratus welcomes any corrections and suggestions for improving this manual. SRB: VOS Release 14.5.0 (R914) Chapter 1: Introduction to VOS Release 14.5.0 =================================== This chapter provides an overview of VOS Release 14.5.0. It contains the following sections. o ``Overview" o ``Highlights of VOS Release 14.5.0" Note: This section contains a new section, ``Changes Beginning in VOS Release 14.5.0," that describes hardware and software changes that are new for VOS Release 14.5.0. It does not describe changes that occurred in previous releases. o ``Year-2000 (Y2K) Certification" o ``Notice of a Change in an Upcoming Release" o ``Product End-of-Life Notices" o ``VOS Release Notation" o ``New and Changed Documentation" o ``Customer Survey" Overview -------- This software release bulletin (SRB) describes the contents of VOS Release 14.5.0, including release-specific installation changes and procedures. VOS Release 14.5.0 is distributed on Continuum-series modules. Installation takes from one to four hours, depending on whether you run the verification phase and on the hardware configurations and software that you have purchased. See the following documentation for installation information. o The section ``Installing Software'' in Chapter 10 describes how to install software (including VOS Release 14.5.0). o The section ``Upgrading from PA-7100 to a PA-8X00 Processor'' in Chapter 10 describes how to install VOS Release 14.5.0 on a module with PA-8600 processors. o The VOS Installation Guide (R386) describes how to install a VOS release. SRB: VOS Release 14.5.0 (R914) 1-1 Overview Highlights of VOS Release 14.5.0 -------------------------------- This section discusses the following topics. o ``Changes Beginning in VOS Release 14.5.0" o ``New Hardware" o ``Software Enhancements" o ``Layered Product Support" o ``Products Not Supported in This VOS Release" The shipment of VOS Release 14.5.0 includes a printed copy of this manual and other Stratus manuals relevant to VOS Release 14.0.0 and later. Many Stratus manuals are also available on CD-ROM and on the Web; for more information, see ``The VOS StrataDOC Online Documentation System" later in this chapter. Note: This document summarizes new products and software enhancements beginning in VOS Release 14.0.0, as well as any changes to the user interface, and directs you to more complete documentation. Occasionally, changes may influence system behavior in a way that affects your applications. For example, an incorrectly written program that compiled and ran in a prior release might not compile successfully on VOS Release 14.5.0. For information about bug fixes, check the Quality Tracking System (QTS) report in the files 14.5.0_problems_srb.memo and io*problems_srb.memo in the directory >system>doc. Note: VOS 14.5.0 supports Continuum-series modules with PA-7100, PA- 8000, PA-8500, and PA-8600 processor modules. This SRB and other manuals from VOS Release 14.0.0 (and later releases) include information about VOS Release 14 functionality for all Continuum-series modules. Changes Beginning in VOS Release 14.5.0 ---------------------------------------- This section lists the VOS hardware and software changes that begin in VOS Release 14.5.0. More information about these changes is available later in this chapter in the ``New Hardware" and ``Software Enhancements" sections. SRB: VOS Release 14.5.0 (R914) 1-2 Highlights of VOS Release 14.5.0 o The install_new_files command should appear in the module_start_up.cm command macro before the local area network (LAN) drivers are loaded. o VOS supports the following disk drives. (Note that these disk drives are also supported in VOS Release 14.3.0 and later.) - D71120 (18 GB, 10,000 RPM) SCSI Disk Drive - D71150 (18 GB, 15,000 RPM) SCSI Disk Drive - D71220 (34 GB, 10,000 RPM) SCSI Disk Drive o The analyze_system command includes the following changes. - changes to the following additional requests: disk_meters, dump_lap_meters, and dump_dlmux_info (note that dump_dlmux_info was supported in earlier VOS releases but is newly documented for VOS Release 14.5.0) - the addition of the mpx_gcomm_stop_wait_time$ flow-control request for the K115 Token-Ring I/O Adapter o STCP includes the following changes. - The default inetd daemon is POSIX.1-compliant, and the inetd_posix daemon no longer exists. - The start_stcp.cm and stop_stcp.cm command macros have changed. - The KEEPALIVE socket option has changed. - STCP supports an increased number of IP multicast addresses. o In OS TCP/IP, the ftpd daemon has a new argument. o The s$poll subroutine allows you to poll files, pipes, and window terminals, as well as STREAMS devices, on remote modules. o A set of new macros and a new function have been added to the C runtime library. o Certain C formatted I/O functions now support 64-bit integer input and output. o The file entries of relative and sequential files that are not transaction files will support byte count and record count. (Note that this functionality was supported in VOS Release 14.4.1 but is newly documented for VOS Release 14.5.0.) SRB: VOS Release 14.5.0 (R914) 1-3 Highlights of VOS Release 14.5.0 o The arguments for the s$connect_vm_region3 and s$disconnect_vm_region3 VOS subroutines have changed. o The s$msg_rewrite TPF subroutine has a new restriction and newly documented error codes. o The (process_info) command function now supports the language key, which returns the name of the language of the current process. o A process performing operations on memory-resident and transient files no longer needs to be privileged. o The following commands have changed: network_watchdog, compare_files, start_process, batch, who_locked, and x25. In addition, the link_boot_server and set_bootload_time commands are no longer available on Continuum systems. New Hardware ------------- VOS supports the following new hardware on Continuum-series modules. o PA-8000 processors--Beginning in Release 14.0.0, VOS supports Hewlett-Packard (r) Company's PA-8000 processors running in 32-bit mode. The PA-8000 processor, which is located on a combined CPU/memory board in 6-slot or 12-slot modules, is upward-compatible with the PA-7100 processor. (VOS Releases 13 and 14 support PA-7100 processors.) For more information about PA-8000 processors, see ``PA- 8000 Processors'' in Chapter 2. o PA-8500 processors--Beginning in Release 14.2.0, VOS supports Hewlett-Packard Company's PA-8500 processors running in 32-bit mode. The PA-8500 processor, which is located on a combined CPU/memory board in 8-slot (6 usable) or 12-slot modules, is upward-compatible with the PA-8000 and PA-7100 processors. (VOS Releases 13 and 14 support PA-7100 processors.) For more information about PA-8500 processors, see ``PA-8500 Processors'' in Chapter 2. o PA-8600 processors--Beginning in Releases 14.2.3 and 14.3.1, VOS supports Hewlett-Packard Company's PA-8600 processors running in 32- bit mode. The PA-8600 processor, which is located on a combined CPU/memory board in 8-slot (6 usable) or 12-slot modules, is upward- compatible with the PA-8500, PA-8000, and PA-7100 processors. (VOS Releases 13 and 14 support PA-7100 processors.) For more information about PA-8600 processors, see ``PA-8600 Processors'' in Chapter 2. o Continuum Model 616--Beginning in VOS Release 14.2.1, Stratus introduces a PA-8500 RISC compact 6-slot module. The system supports SRB: VOS Release 14.5.0 (R914) 1-4 Highlights of VOS Release 14.5.0 up to 2 gigabytes (GB) of logical memory, in configurations of 0.5 GB or 2 GB logical memory per system. The disk subsystem supports 10 duplexed disk drives (5 logical). With the expansion cabinets, the system supports up to 96 duplexed disk drives (48 logical). The basic cabinet can accept an optional I/O adapter chassis with 11 slots (2 terminated) for 9 supported I/O adapters. Alternatively, the system can support up to 2 expansion cabinets, each with 16 slots (2 terminated), for a total of 28 I/O adapters. o Continuum Model 651-2--Beginning in VOS Releases 14.2.3 and 14.3.1, Stratus introduces a PA-8600 RISC uni-processor 8-slot module. The system supports up to 4 gigabytes of logical memory in configurations of 0.5, 1 GB, 2 GB, or 4 GB logical memory per system. The disk subsystem supports 10 duplexed disk drives (5 logical). With the expansion cabinets, the system supports up to 96 duplexed disk drives (48 logical). The basic cabinet can accept an optional I/O adapter chassis with 11 slots (2 terminated) for 9 supported I/O adapters. Alternatively, the system can support up to 2 expansion cabinets, each with 16 slots (2 terminated), for a total of 28 I/O adapters. o Continuum Model 1251-2--Beginning in VOS Releases 14.2.3 and 14.3.1, Stratus introduces a PA-8600 RISC uni-processor 12-slot module. The system supports up to 4 GB of logical memory in configurations of 0.5 GB, 1 GB, 2 GB, or 4 GB logical memory per system. The disk subsystem supports 84 duplexed disk drives (42 logical). With the expansion cabinets, the system supports up to 192 duplexed disk drives (96 logical). The basic cabinet can accept an optional I/O adapter chassis with 16 slots (2 terminated) for 14 supported I/O adapters. Alternatively, the system can support up to 6 expansion cabinets, each with 16 slots (2 terminated), for a total of 84 I/O adapters. o Continuum Model 652-2--Beginning in VOS Releases 14.2.3 and 14.3.1, Stratus introduces a PA-8600 RISC twin-processor 8-slot module. The system supports up to 4 GB of logical memory in configurations of 0.5, 1 GB, 2 GB, or 4 GB logical memory per system. The disk subsystem supports 10 duplexed disk drives (5 logical). With the expansion cabinets, the system supports up to 96 duplexed disk drives (48 logical). The basic cabinet can accept an optional I/O adapter chassis with 11 slots (2 terminated) for 9 supported I/O adapters. Alternatively, the system can support up to 2 expansion cabinets, each with 16 slots (2 terminated), for a total of 28 I/O adapters. o Continuum Model 1252-2--Beginning in VOS Releases 14.2.3 and 14.3.1, Stratus introduces a PA-8600 RISC twin-processor 12-slot module. The system supports up to 4 GB of logical memory in configurations of 0.5 GB, 1 GB, 2 GB, or 4 GB logical memory per system. The disk subsystem supports 84 duplexed disk drives (42 logical). With the SRB: VOS Release 14.5.0 (R914) 1-5 Highlights of VOS Release 14.5.0 expansion cabinets, the system supports up to 192 duplexed disk drives (96 logical). The basic cabinet can accept an optional I/O adapter chassis with 16 slots (2 terminated) for 14 supported I/O adapters. Alternatively, the system can support up to 6 expansion cabinets, each with 16 slots (2 terminated), for a total of 84 I/O adapters. o larger memory sizes--For more information about the larger memory sizes, see ``CPU/Memory Boards'' in Chapter 2. o V105 terminal--Beginning in Release 14.0.0, VOS supports the V105 terminal. This terminal supports two types of keyboards: the American National Standards Institute (ANSI) keyboard and the 106- key personal computer (PC/+ 106) keyboard. The V105 terminal allows you to choose 24 or 42 display lines with 80 or 132 characters per line. VOS supports one terminal emulation for the V105 terminal: Digital Equipment Corporation's VT(tm) 300. For additional information, see ``The V105 Terminal and Other Terminal Support Issues'' in Chapter 2. o Central Office systems--In VOS Release 14.2.0, the following Central Office systems are available: Continuum 600 and 1200 Series Model 615-CO, Model 625-CO, Model 1215-CO, and Model 1225-CO. o C619 Modem support--Beginning in Release 14.2.1, VOS supports the C619 modem, which replaces the C419 modem. For more information about the C619 modem, see the Continuum Series 600 and 1200: Site Planning Guide (R391) and the vendor documentation that accompanies the modem. o K124-20 I/O Adapter--Beginning in Release 14.2.1, VOS supports the K124-20 I/O adapter. This is an updated version of the K124-10 I/O adapter and provides support for a T1 line. o disk drives--Beginning in Release 14.0.0, VOS supports the following new disk drives. - D70410 2.2 GB, 7200 RPM SCSI Disk Drive--This disk drive replaces the D70400 7200 RPM SCSI Disk Drive and can be fully duplexed with the older disk drives of the same family. - D70520 4.5 GB, 7200 RPM SCSI Disk Drive--This disk drive replaces the D70510 7200 RPM SCSI Disk Drive and can be fully duplexed with the older disk drives of the same family. Beginning in Release 14.0.1, VOS supports the following new disk drives. - D70530 4.5 GB, 7200 RPM SCSI Disk Drive--This disk drive replaces the D70520 4.5 GB, 7200 RPM SCSI Disk Drive and can be SRB: VOS Release 14.5.0 (R914) 1-6 Highlights of VOS Release 14.5.0 fully duplexed with the older disk drives of the same family. - D70700 18.2 GB, 7200 RPM SCSI Disk Drive. - D70620 9 GB, 10,000 RPM SCSI Disk Drive. Beginning in Release 14.1.0, VOS supports the following new disk drives. - D71100 18 GB, 10,000 RPM SCSI Disk Drive. - D70620 9 GB, 10,000 RPM SCSI Disk Drive--This disk drive replaces the D70610 9.7 GB 7200 RPM SCSI Disk Drive and can be fully duplexed with the older disk drives of the same family. Beginning in Release 14.2.0, VOS supports the following new disk drive. - D71200 34 GB, 10,000 RPM SCSI Disk Drive. Beginning in Release 14.5.0, VOS supports the following new disk drive. - D71150 (18 GB, 15,000 RPM) SCSI Disk Drive. Beginning in Release 14.5.0, VOS supports the following replacement disk drives. - D71120 (18 GB, 10,000 RPM) SCSI Disk Drive. - D71220 (34 GB, 10,000 RPM) SCSI Disk Drive. For additional information about these disk drives, see ``Changes to the D700 Subsystem'' in Chapter 2. o tape drives--Beginning in Release 14.0.0, VOS supports the following new tape drives. - T705 24 GB, DDS-3 DAT Tape Drive--This single-cartridge tape drive, which is fully read-compatible with older products, replaces the T701 DAT tape drive. - T706 144 GB, DDS-3 DAT Tape Drive with Autoloader--This tape drive, which is fully read-compatible with older products, replaces the T702 DAT tape drive. For additional information about these tape drives, see ``The T705 and T706 Tape Drives'' in Chapter 2. o K470 PMC I/O Controller--Beginning in Release 14.1.0, VOS supports the K470 PMC I/O Controller on Continuum Series 600 and 1200 systems in order to provide peripheral component interconnect (PCI) I/O SRB: VOS Release 14.5.0 (R914) 1-7 Highlights of VOS Release 14.5.0 connectivity. Each K470 I/O controller provides up to three high- speed PCI connections on a Continuum system. Each Continuum Series 600 system can support two K470 I/O controllers. Each Continuum Series 1200 system can support up to six K470 I/O controllers. For complete information about the K470 I/O controller, see the Continuum Series 600 and 1200: PMC-Card Installation Guide (R443). o U713 10/100-Mbps Ethernet PMC Card--Beginning in Release 14.1.0, VOS supports the U713 Ethernet Peripheral Component Interconnect (PCI) Mezzanine Card (PMC card). The U713 10/100-Mbps Ethernet PMC card is a high-performance Network Interface Card (NIC) that enables you to connect a 6- or 12-slot Continuum module to an Ethernet local area network (LAN). The U713 10/100-Mbps Ethernet PMC card is inserted into the K470 Communications I/O Controller. The U713 10/100-Mbps Ethernet PMC card is based on a 32-bit bus architecture that optimizes data flow between the system and the network, resulting in higher throughput with low CPU utilization. The U713 10/100-Mbps Ethernet PMC card provides both 10 megabits-per- second (Mbps) Ethernet and 100-Mbps Fast Ethernet communications. The card automatically senses the speed of the port to which it is attached, and configures itself properly. For additional information, see the Continuum Series 600 and 1200: PMC-Card Installation Guide (R443). o U714 Gigabit Ethernet PMC Card--Beginning in Release 14.4.0, VOS supports the U714 Gigabit Ethernet Peripheral Component Interconnect (PCI) Mezzanine Card (PMC card). The U714 PMC card is a high- performance, 1 gigabit-per-second (Gbps) Network Interface Card (NIC) that enables you to connect a 6- or 12-slot Continuum module to an Ethernet local area network (LAN) through a 1000Base-SX fiber- optic link. The U714 PMC card is inserted into the K470-10 Communications I/O Controller. The U714 PMC card provides 1000 Mbps full-duplex Ethernet communication through one fiber connection that supports either a 50 or 62.5 micron multimode. Note: Although you can physically insert a total of 18 U714 PMC cards on a 12-slot module with 6 K470 I/O controllers, VOS supports a maximum of 6 U714 PMC cards on one module. For additional information, see the Continuum Series 600 and 1200: PMC-Card Installation Guide (R443). o U720 Token-Ring PMC Card--Beginning in Release 14.2.2, VOS supports the U720 Token-Ring PCI Mezzanine Card (PMC). The U720 PMC card is a SRB: VOS Release 14.5.0 (R914) 1-8 Highlights of VOS Release 14.5.0 high-performance NIC that enables you to connect a 6- or 12-slot Continuum module to a Token-Ring LAN. The U720 PMC card is inserted into the K470 I/O controller. (If your module is running a point release of VOS Release 14 that is earlier than 14.2.2, contact the Stratus Customer Assistance Center (CAC) about using the U720 PMC card.) The U720 PMC card is based on a 32-bit bus architecture that optimizes data flow between the system and the network, resulting in the highest possible throughput with low CPU utilization. The U720 PMC card has a default line speed of 16 Mbps Token-Ring communication, but you can configure a line speed of 4 Mbps. For information about configuring a Token-Ring LAN with the U720 PMC card on Continuum-series modules, see the following documentation. - Product Configuration Bulletin: Token-Ring Devices (R303) - Software Release Bulletin: Token-Ring DLC Interface (R237) - Updates and errata file to the VOS Communications Software: Token-Ring DLC Interface Programmer's Guide (R213). Updates and errata files are located in the directory >system>doc>vos_pubs_corrections. Stratus customers with a current support contract can access them on the VOS StrataDOC Web site at http://stratadoc.stratus.com. - Continuum Series 600 and 1200: PMC-Card Installation Guide (R443) For detailed information about Continuum-series modules, see the following manuals. - For VOS systems with the PA-7100 processor, see the Continuum Series 600 and 1200: Site Planning Guide (R391) and Continuum Operation and Maintenance: 600 and 1200 Series (R396). - For VOS systems with the PA-8000 processor, see the VOS Continuum 600 and 1200 Series with PA-8000: Operation and Maintenance Guide (R445). - For VOS systems with the PA-8500 processor, see the VOS Continuum Series 600 and 1200: Operation and Maintenance Guide (R463). Software Enhancements --------------------- VOS supports the following software enhancements. o RADIUS--Beginning in VOS Release 14.4.0, VOS RADIUS Support permits SRB: VOS Release 14.5.0 (R914) 1-9 Highlights of VOS Release 14.5.0 a VOS system administrator to designate that selected VOS users must be authenticated by an external RADIUS service instead of by VOS itself. VOS RADIUS Support, when used with a RADIUS service, permits an organization to designate a single authentication service for multiple computer systems from a wide variety of vendors, and permits these users to be authenticated using a variety of methods. For more information about RADIUS, see the manual VOS System Administration: Registration and Security (R283). o STREAMS TCP/IP (STCP)--The following changes are related to STCP. - Beginning in VOS Release 14.2.0, STCP supports IP multicast level 2 (receive). See ``Overview of STCP'' in Chapter 5 for more information. - Beginning in VOS Release 14.3.0, the maximum number of STCP TCP sockets has increased from 5000 to 8000 on the PA-RISC 8X00 processor systems. For more information about STCP TCP sockets, see the VOS STREAMS TCP/IP Programmer's Guide (R420), which discusses creating sockets, setting and checking their options, and other topics concerning communicating through STCP sockets. - The NFS facility has been modified to interoperate with STCP. If you are using STCP, you must install NFS Release 1.3. For more information about these changes, see the Software Release Bulletin: NFS and RPC Release 1.3 (R252). - Beginning in VOS Release 14.3.0, an STCP compatibility library is provided to ease the porting of OS TCP/IP applications to STCP. The library contains many of the objects of OS TCP/IP networking library functions not supported in STCP. Depending upon the design of your application, you may not have to recompile an OS TCP/IP application with the STCP include library. When rebinding the application, you can bind in the STCP compatibility object library along with the existing STCP object library. See ``STCP Administration" in Chapter 5. - The ftpd daemon process has two new arguments, - security_check_file and -allow_any_port. See ``New Arguments for the ftpd Daemon in STCP'' in Chapter 5. - Beginning in VOS Release 14.3.0, STCP is capable of using POSIX.1. See ``Programming Support for POSIX.1 Compliance" in Chapter 5. - Beginning in VOS Release 14.3.0, VOS supports the Open Shortest Path First (OSPF) routing protocol on VOS modules that are running STCP. See ``OSPF Support" in Chapter 5. - Beginning in VOS Release 14.4.0, STCP includes TCP wrappers SRB: VOS Release 14.5.0 (R914) 1-10 Highlights of VOS Release 14.5.0 functionality, which provides authentication and logging capabilities that enable STCP to control client access to FTP and TELNET, and to any services that the inetd daemon starts (for example, BOOTP and TFTP). See ``STCP and TCP Wrappers Functionality'' in Chapter 5. - Beginning in VOS Release 14.5.0, the default inetd daemon is POSIX.1-compliant, and the inetd_posix daemon no longer exists. See ``STCP and POSIX.1 Compliance'' in Chapter 5. - Beginning in VOS Release 14.5.0, the KEEPALIVE socket option has changed. See ``Other STCP Programming Changes'' in Chapter 5. - Beginning in VOS Release 14.5.0, STCP supports an increased number of IP multicast addresses. See ``Increased Number of IP Multicast Addresses'' in Chapter 5. - The start_stcp.cm and stop_stcp.cm command macros have changed. See ``Changes to the start_stcp.cm Command Macro'' in Chapter 5 and ``Changes to the stop_stcp.cm Command Macro'' in Chapter 5. o Enhancements to polling--Beginning in VOS Release 14.5.0, the s$poll subroutine allows you to poll files, pipes, and window terminals, as well as streams devices (previously, it only polled streams devices) on remote modules. See ``Enhanced Polling Support'' in Chapter 5. o Changes to OS TCP/IP--In VOS Release 14.3.0 and in VOS Release 14.5.0, the ftpd daemon process has new arguments. See ``New Arguments for the ftpd Daemon in OS TCP/IP'' in Chapter 5. o Changes to the VOS Data-Link Multiplexer driver software--See ``The Data-Link Multiplexer: SDLMUX and DLMUX'' in Chapter 5. o New and changed commands, as described in Table 1-1. Table 1-1. New and Changed VOS Commands (Page 1 of 2) ------------------------------------------------------------------------- | : Release : | | : Where : | | : Change : | | : Was : | | : Introduced : | | : : | | : : | | : : | | Command : : Where Described | |-----------------------------------------------------------------------| | add_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| SRB: VOS Release 14.5.0 (R914) 1-11 Highlights of VOS Release 14.5.0 | add_paging_file : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | cancel_disk_retry : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | cancel_fast_disk_recovery: 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | delete_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | dismount_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | display_disk_fragmentati : 14.4.0 : ``New Disk Commands'' in | | on : : Chapter 2 | |-----------------------------------------------------------------------| | display_disk_info : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | display_disk_label : 14.1.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | dump_memory : 14.2.0 : ``Changes to the | | : : dump_memory Command'' in | | : : Chapter 2 | |-----------------------------------------------------------------------| | format_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | initialize_boot_disk : 14.2.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | initialize_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | initialize_duplex_disk : 14.0.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | mount_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | network_watchdog : 14.5.0 : ``Changes to the | | : : network_watchdog Command'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | registration_admin : 14.1.0, : ``Changes to the | | : 14.3.0 : registration_admin | | : : Command'' in Chapter 2 | SRB: VOS Release 14.5.0 (R914) 1-12 Highlights of VOS Release 14.5.0 |-----------------------------------------------------------------------| | remove_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | remove_tape : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | salvage_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | save : 14.4.0 : ``Changes to the save | | : : Command'' in Chapter 2 | |-----------------------------------------------------------------------| | select_duplex_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | set_bootload_time : 14.5.0 : ``Changes to the | | : : dump_memory Command'' in | | : : Chapter 2 | |-----------------------------------------------------------------------| | set_partition_size : 14.3.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | set_registration_info : 14.1.0 : ``Changes to the | | : : set_registration_info | | : : Command'' in Chapter 2 | |-----------------------------------------------------------------------| | set_scheduler_info : 14.4.0 : ``Changes to the | | : : set_scheduler_info | | : : Command'' in Chapter 2 | |-----------------------------------------------------------------------| | setup_disk : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | setup_tape : 14.4.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | start_disk_recovery : 14.0.0 : ``Changed Disk Commands'' | | : : in Chapter 2 | |-----------------------------------------------------------------------| | start_logging : 14.4.0 : ``Changes to the | | : : start_logging Command'' in | | : : Chapter 2 | |-----------------------------------------------------------------------| | test_index : 14.3.0 : ``Changes to the test_index | | : : Command'' in Chapter 2 | |-----------------------------------------------------------------------| | update_disk_label : 14.1.0, : ``Changed Disk Commands'' | | : 14.4.0 : in Chapter 2 | ------------------------------------------------------------------------- SRB: VOS Release 14.5.0 (R914) 1-13 Highlights of VOS Release 14.5.0 o Window terminal devices. The following changes are related to window terminal devices. See ``Changes Affecting Window Terminal Devices'' in Chapter 5. - Beginning in VOS Release 14.2.0, the external variable sys_info$wtm_allow_multiple_user has been added to prevent a nonprivileged user from being able to share the window terminal device of another user. In addition, the set_terminal_parameters command has a new argument that allows you to share window terminal devices on an individual basis. - Beginning in VOS Release 14.3.0, new window terminal opcodes and Forms Management System (FMS) subroutines have been added to allow multiple processes to update portions of the terminal screen simultaneously and to provide compatible terminal support for POSIX. o Changes to the module_start_up.cm command macro. See ``Changes to the module_start_up.cm Command Macro'' in Chapter 2. o Changes in Emacs--See ``Emacs Changes'' in Chapter 4. o Support for memory-resident files--Beginning in VOS Release 14.2.2, you can designate files as memory-resident. Also, beginning in VOS Release 14.5.0, a process performing operations on memory-resident and transient files no longer needs to be privileged. See ``Cache Manager Improvements" in Chapter 6. o Support for byte and record count--Beginning in VOS Release 14.4.1, newly-created relative and sequential files that are not transaction files will support byte count and record count. See ``Support for Byte and Record Count in File Entries'' in Chapter 6. o Change to the (process_info) command function--This command function now supports the language key. See ``The (process_info) Command Function'' in Chapter 4. o Streamlining disk renames--Beginning in VOS Release 14.2.2, the disk salvager allows for quick renaming of duplexed disks. See ``Streamlining Disk Renames" in Chapter 2. o Booting from tape--You can use a DAT tape in a T705 or T706 tape drive to boot a Continuum-series module from tape (either autoloaded or manually loaded). o Changes to the manual boot procedure--Beginning in VOS Release 14.3.0, you can configure a tape during a manual boot. See ``Changes to the Manual Boot Procedure'' in Chapter 2. SRB: VOS Release 14.5.0 (R914) 1-14 Highlights of VOS Release 14.5.0 o Increase in ports per process and events per module--Beginning in VOS Release 14.2.2, the maximum number of ports per process and events per module have increased. See ``Increase in Ports per Process and Events per Module" in Chapter 3. o Change to the home directory during automatic startup--Beginning in VOS Release 14.3.0, the home directory of the initialization process is set to (master_disk)>Overseer during both manual and automatic startup. See ``Change to Home Directory During Automatic Startup'' in Chapter 2. o Change to the languages.tin file--The languages.tin file has a new field, input_date_format. See ``Change to the languages.tin File'' in Chapter 2. o Cache manager changes--The cache manager has a number of significant changes. See ``Tuning the File System Cache Manager'' in Chapter 2, ``Changes to the Cache Manager'' in Chapter 3, and ``Cache Manager Improvements'' in Chapter 6. o Support for dynamically allocated extent (DAE) files--Beginning in VOS Release 14.3.0, the usability of extent files is greatly improved with the use of DAE files. See ``Dynamically Allocated Extents (DAE)" in Chapter 6. o Open disk support--Beginning in VOS Release 14.3.0, any user on a PA- RISC system can add disk drives with new capacities or with like capacity drives automatically without requiring a kernel update or the execution of an external command. o New analyze_system requests--Beginning in VOS Release 14.5.0, the analyze_system command supports changes to the following requests: disk_meters, dump_lap_meters, list_disk_params, set_disk_param, and dump_dlmux_info (note that list_disk_params, set_disk_param, and dump_dlmux_info were supported in earlier VOS releases but are newly documented for VOS Release 14.5.0). In addition, the mpx_gcomm_stop_wait_time$ flow-control request has been added for the K115 Token-Ring I/O Adapter. o New C runtime function and macros--Beginning in VOS Release 14.5.0, a set of new macros and a new function have been added to the C runtime library. See ``New Function and Macros'' in Chapter 7. o New VOS subroutines--VOS supports the new s$connect_vm_region3, s$disconnect_vm_region3, s$get_object_status, and s$perform_ext_authentication subroutines. For more information, see ``New Subroutines Not Documented in the Subroutines Manuals'' in Chapter 8. The subroutine s$get_registration_info is newly documented. See ``New SRB: VOS Release 14.5.0 (R914) 1-15 Highlights of VOS Release 14.5.0 Subroutines Not Documented in the Subroutines Manuals'' in Chapter 8. o Changes to VOS subroutines--A number of VOS subroutines have been modified. See ``Subroutine Changes Not Documented in the Subroutines Manuals'' in Chapter 8. o New locate_dae_files tool--The locate_dae_files tool allows you to locate and identify DAE files and indexes when you downgrade a module from VOS Release 14.5.0 to a previous VOS release. See ``Downgrading from VOS Release 14.5.0'' in Chapter 10. Layered Product Support ----------------------- Beginning in VOS Release 14.4.0, some of the layered products supported on VOS will require you to accept an online license agreement before you complete the installation. See ``Layered Product License Agreement" in Chapter 10 for more information. VOS supports the following layered products. o Apache Web Server--Beginning in VOS Release 14.3.0, the Apache Web Server is available on VOS. Apache is the most popular WWW server on the internet and has been ported to a number of operating systems. For information on the implementation of the Apache Web Server on VOS, see the Software Release Bulletin: VOS Apache Web Server Release 1.3.12 (R466). o GNU C++ and GNU Tools Release 2.0.0--Beginning in Release 14.4.0, VOS supports the separately released product GNU C++ and GNU Tools Release 2.0.0. The VOS GNU C++ product is a port of the Free Software Foundation's popular GNU C++ compiler, debugger, libraries, and utilities to the VOS platform. VOS GNU Tools is a port of several common GNU UNIX tools to the VOS platform. The GNU Tools include a shell (bash), gmake, binary utilities, and many UNIX commands that are used in UNIX (r) scripts and makefiles to allow POSIX-compliant C or C++ source code to be built on VOS for the VOS POSIX environment. For more information, see the Software Release Bulletin: VOS GNU C++ and GNU Tools Release 2.0.1 (R468). Beginning in Release 14.5.0, VOS supports the separately released product GNU C++ and GNU Tools Release 2.0.1. This release is a revision of Release 2.0.0 that includes support for the Perl programming language. For more information, see the Software Release Bulletin: VOS GNU C++ and GNU Tools Release 2.0.1 (R468). o POSIX.1--Beginning in Release 14.3.0, VOS supports POSIX.1. POSIX.1 refers to Part 1 of the IEEE POSIX (r) standard, which is a system application programming interface. POSIX.1 support enables VOS SRB: VOS Release 14.5.0 (R914) 1-16 Highlights of VOS Release 14.5.0 programmers to port to VOS, with minimal source-code modification, applications written in the C programming language that conform to the POSIX.1 standard. See ``POSIX.1 Support" in Chapter 7 for programming-related changes, and see ``STCP and POSIX.1 Compliance'' in Chapter 5 for STCP-related changes. o Samba--Samba Release 2.0.7 is supported beginning with VOS Release 14.4.0. VOS Samba provides file services to SMB/CIFS clients. Storage Message Block (SMB) was one of the early file-sharing protocols for PC-based operating systems. Common Internet File System (CIFS) is the new name for this class of protocols. Clients that implement the SMB/CIFS protocol include Microsoft(r) Windows(r) 95, 98, ME, NT 4.0, 2000, IBM, OS/2, and Linux. Add-on packages to provide SMB/CIFS support are available for other operating systems. For information on Samba, see the Software Release Bulletin: VOS Samba Release 2.0.7 (R470). Products Not Supported in This VOS Release ------------------------------------------- The following sections describe hardware and software products that VOS no longer supports. (Subsequent chapters in this document describe supported hardware and software products.) o ``XA2000-Series Modules" o ``XA/R-Series Modules" o ``C-Series Hardware" o ``Software Products" XA2000-Series Modules ********************* Beginning in Release 14.0.0, VOS does not support XA2000-series modules. VOS Release 13 (including all point releases of Release 13) is the last release of VOS that supports XA2000-series modules. Note the following about this end of support. o Stratus has not accepted orders for XA2000 Models 210, 220, 230, 240, 250, 260, 270, 280, 2260, 2460, 2660, and 2860, and all hardware and software products that are unique to those modules since October 30, 1996. However, Stratus will support these products for at least five years from October 30, 1996. o XA2000 Models 75, 80, 110-160, and 200, and all hardware and SRB: VOS Release 14.5.0 (R914) 1-17 Highlights of VOS Release 14.5.0 software products that are unique to those modules, were no longer sold as of September 30, 1995. However, Stratus will support these products for at least five years from September 30, 1995. Although support for XA2000-series modules ended in VOS Release 14.0.0, you can still generate code and cross-bind object modules for an XA2000- series module from an XA/R- or Continuum-series module. This support enables Stratus modules to maintain cross-development for networked XA2000- series modules. XA/R-Series Modules ******************* Beginning in Release 14.2.0, VOS does not support XA/R-series modules. VOS Release 14.1.0 is the last release of VOS that supports the XA/R product set. Note the following about this end of support. Stratus stopped accepting orders for XA/R models R/5, R/5S, R/10, R/10S, R/15, R/15S, R/20, R/25, R/25S, R/35, R/35S, R/45, R/45S, R/55, R/55S, R/300, R/305, R/310, R/320, R/330, and R/340 and all hardware and software products that are unique to those modules effective December 11, 1999. However, Stratus will support these products for at least five years from December 11, 1999. Although support for XA/R modules ended in VOS Release 14.2.0, you can still generate code and cross-bind object modules for an XA/R module from an XA/R- or Continuum-series module. This support enables Stratus modules to maintain cross-development for networked XA/R modules and to support firmware running on UCOMM I/O adapters. C-Series Hardware ***************** Beginning in Release 14.0.0, VOS does not support C-series hardware, including the C100 and C200 communications controllers and the line adapters (C102, C103, and so on). Because the C-series hardware runs only with XA2000-series modules, VOS Release 13 (including all point releases of Release 13) is the last release of VOS that supports C-series hardware. Software Products ****************** Beginning in Release 14.0.0, VOS does not support the following software on Continuum-series modules. Chapter 5 provides a complete list of the communication products supported by VOS Release 14.0.0. o DNS/200 International SRB: VOS Release 14.5.0 (R914) 1-18 Highlights of VOS Release 14.5.0 o Dow Jones News RetrievalFOOTNOTE: 1 o Local 4993 o TCP/IP 2.x product set--Beginning in VOS Release 13.0, Stratus no longer sells or supports this product on any module type. o I104 FDDI Interface--VOS Release 13.3.0 is the last VOS release to support the I104 FDDI interface. For more information, see ``Product End-of-Life Notices" later in this chapter. (On Continuum-series modules, however, VOS Release 14.0.0 and later provides an interface to FDDI networks through the U250 Remote I/O Switch and the K460 I/O controller.) o VOS Local Area Transport (LAT(r))--Beginning in VOS Release 14.0.0, Stratus no longer sells or supports this product on any module type. (Stratus still supports this product on VOS Release 13.3.0 and earlier releases for existing LAT customers.) o StrataLINK (also known as traditional or proprietary StrataLINK)-- Open StrataLINK provides the VOS communication within a system of modules that traditional StrataLINK formerly provided. Year-2000 (Y2K) Certification ----------------------------- VOS Releases 14.x are certified to operate properly after December 31, 1999. Customers who intend to operate their systems beyond December 31, 1999 must upgrade their VOS modules to a certified release before January 1, 2000. (The certified VOS releases also include 12.1.2, 12.4.0, 13.3.3, 13.4.0, 13.5.0.) To help address the Y2K problem, VOS Release 14.0.0 includes the following features. o The upper limit of the VOS epoch is January 19, 2048, 3:14:06 Greenwich Mean Time (GMT), or 2048-01-19_03:14:06_gmt. (An epoch is the duration of time for which the operating system time will function correctly.) The beginning of the VOS epoch is January 1, 1980, or 1980-01-01, as previously documented. Dates and times that VOS returns are within the VOS epoch (for example, the date that the (date) command function returns). In addition, when you use a command such as set_date_time or a subroutine such as s$cv_to_int_date_time, you must specify dates and times that are within the VOS epoch. Note that because local time zones can be up to 13 hours different from GMT, the last full day that VOS can process in any time zone is SRB: VOS Release 14.5.0 (R914) 1-19 Year-2000 (Y2K) Certification January 17, 2048, or 2048-01-17, and the first full day that VOS can process is January 2, 1980, or 1980-01-02. For complete information about the set_date_time command, see the manual VOS System Administration: Administering and Customizing a System (R281). For complete information about the s$cv_to_int_date_time subroutine, see the VOS Subroutines manuals. For more information about the command functions, see the VOS Commands Reference Manual (R098). o VOS PL/I and VOS COBOL support new functions, datetime and current- date, respectively. See ``The datetime Function'' in Chapter 7 for more information about the datetime function, and see ``The current- date Function'' in Chapter 7 for more information about the current- date function. o VOS supports two new command functions, (iso_date_time) and (iso_date). See ``New and Changed Command Functions'' in Chapter 4 for more information. o ANSI and IBM (r) label tapes have the default expiration date value of none (" 00000"--note the leading space). For more information, see ``Default Expiration Date Change'' in Chapter 2. Applications that you have purchased from other sources or developed in- house may be subject to Y2K problems. Stratus recommends the following actions. o Contact the vendors of any non-Stratus software you are using to ascertain that it is certified to operate properly with dates after 1999. o Examine applications you have developed in-house for potential problems, and modify them as needed. See the Stratus web site listed at the end of this section for further information. o Search application source files and command macros for strings that may indicate date-time usage (for example, date, year, and yy). Make sure dates are used properly. Stratus's Y2K Internet Web site pages have been and will continue to be Stratus's primary mechanism for communicating Y2K information. The Web site is located at http://www.stratus.com. Stratus strongly recommends that you periodically check this Web site for the most up-to-date Y2K information. SRB: VOS Release 14.5.0 (R914) 1-20 Notice of a Change in an Upcoming Release of a Change in an Upcoming Release ----------------------------------------- The following change is planned for an upcoming VOS release. Since this change may be incompatible with your current system configuration or administrative procedures, you may need to perform some modifications before updating to this VOS release. Removal of harvest_meters.pm ----------------------------- Because PMRS was replaced in 2000 by ViewPoint, which has subsequently been replaced by SightLine, harvest_meters.pm will no longer be available on the VOS release tape, beginning in VOS Release 15.0.0. If you wish to upgrade to the replacement product, SightLine, please contact the CAC. Product End-of-Life s --------------------------- Stratus continually enhances its hardware and software products to provide customers with new functionality and improved performance, and to take advantage of new technology. To achieve the greatest advances in performance and technology, Stratus will phase out some of its older hardware and software products, as follows: o U250 Remote I/O Switches--As of March 7, 2002, no further U250 switch orders can be accepted for this factory-shipped product. Limited quantities of U250 switch products may be obtained from Stratus on an "as available" basis. Stratus will provide service for a minimum of five (5) years from March 7, 2002. Documentation for hardware and software products currently offered on these systems as of March 7, 2002 will be available at their current March 7, 2002 revision levels for the duration of the five years. Any Stratus software or hardware changes that occur during that time and that are essential to usability will be documented in an online file. Due to the significant industry decline of FDDI as a protocol, no direct replacement products are available. o 7200 RPM SCSI disk drives-- As of September 1, 1999, the D803, D705, D706, D707, D720, D721, D722, D604, and D605 are no longer available. However, Stratus will provide service for a minimum of five (5) years from September 1, 1999. o XA/R-series modules--VOS Release 14.1.0 is the last release of VOS to support the XA/R product set. The End-of-Life for the XA/R product set is effective December 11, 1999. Maintenance releases of VOS 14.1.0 will remain available until December 11, 2004 for this SRB: VOS Release 14.5.0 (R914) 1-21 Product End-of-Life Notices product set. Beginning in Release 14.2.0, VOS will not support the XA/R product set. VOS 13.5.0 is the last version of VOS 13 that will support the XA/R product set and will continue to be supported until June 11, 2003. The XA/R product set consists of the following XA/R models: R/5, R/5S, R/10, R/10S, R/15, R/15S, R/20, R/25, R/25S, R/35, R/35S, R/45, R/45S, R/55, R/55S, R/300, R/305, R/310, R/320, R/330, and R/340. o C-series hardware--Beginning in Release 14.0.0, VOS does not support C-series hardware, including the C100 and C200 communications controllers and the line adapters (C102, C103, and so on). Because the C-series hardware runs only with XA2000-series modules, VOS Release 13 (including all point releases of Release 13) is the last release of VOS to support C-series hardware. o the help system--VOS Release 13 (including all point releases of VOS Release 13) is the last release of VOS to support the VOS commands help system. VOS StrataDOC, which is discussed in ``The VOS StrataDOC Online Documentation System" later in this chapter, supersedes this system. o I104 FDDI interface--VOS Release 13.3.0 is the last VOS release to support the I104 FDDI interface (this interface is also known as VOS FDDI). As of July 1, 1997, Stratus will no longer sell the I104 FDDI interface for VOS XA/R-series modules. Stratus will provide maintenance versions of VOS Release 13.3.0 for five years, until June 30, 2002. The I104 FDDI interface includes the following hardware products. - the I104 FDDI controller board - the K130 FDDI I/O adapter - the C-connector cable pair Stratus will continue to honor existing service commitments and warranties on these products. However, Stratus reserves the right, when necessary, to provide the most recent available revision of the hardware products or a substitute of equal or greater value and function. The software products of the I104 FDDI interface will be available at their current revision level as of June 30, 1997, or, at Stratus's option, a later revision level for license until June 30, 1998. Documentation for the I104 FDDI interface as of June 30, 1997 will be available at the current July 1, 1997 revision levels for the duration of the five years, until July 1, 2002. Any software or hardware changes that occur during that time and that are essential SRB: VOS Release 14.5.0 (R914) 1-22 Product End-of-Life Notices to usability will be documented in an online file. o K450 Differential SCSI/Ethernet I/O Controller--As of December 31, 1996, Stratus no longer accepts orders for the K450 I/O controller. This announcement, though, does not affect existing service commitments; Stratus continues to honor warranties for the K450 I/O controller. Complete Customer Service offerings for the K450 I/O controller continue to be available until at least December 31, 2001. (Stratus reserves the right to provide the most recent available revision of the K450 I/O controller or a substitute of equivalent or greater value and function if necessary.) Software products currently offered on the K450 I/O controller as of December 31, 1996 will be available at the controller's December 31, 1996 revision level or, at Stratus's option, a later level for license only until December 31, 1998. New software products not currently offered for use on the K450 I/O controller as of December 31, 1996 will not be available for use on these systems. Documentation for hardware and software products currently offered on the K450 I/O controller as of December 31, 1996, will be available at their current December 1, 1996 revision levels for the duration of the five years, until December 1, 2001. Any software or hardware changes that occur during that time and that are essential to usability will be documented in an online file. o T701, T702, and T703 tape drives--As of July 1997, the T701, T702, and T703 tape drives are no longer available. o TCP/IP 2.x product set--As of March 1995, Stratus no longer sells or supports the TCP/IP 2.x product set on any module type. o V101 and V102 terminals--Support for the V101 and V102 terminals ended on May 31, 1996. o VOS LAT--Beginning in VOS Release 14.0.0, Stratus no longer sells or supports VOS LAT on any module type. Note, however, that Stratus still supports this product in VOS Release 13.3.0 and earlier releases for existing VOS LAT customers. o XA2000-series modules--VOS Release 13 (including all point releases of Release 13) is the last release of VOS to support XA2000-series modules. - Stratus has not accepted orders for XA2000 Models 210, 220, 230, 240, 250, 260, 270, 280, 2260, 2460, 2660, and 2860, and all hardware and software products that are unique to those modules, since October 30, 1996. However, Stratus will support these products for at least five years from October 30, 1996. SRB: VOS Release 14.5.0 (R914) 1-23 Product End-of-Life Notices - XA2000 Models 75, 80, 110-160, and 200, and all hardware and software products that are unique to those modules, were no longer sold as of September 30, 1995. However, Stratus will support these products for at least five years from September 30, 1995. Although VOS Release 14.0.0 and later do not operate on XA2000-series modules, you can still generate code and cross-bind object modules for an XA2000-series module from an XA/R- or Continuum-series module. This support enables Stratus modules to maintain cross-development for networked XA2000-series modules and to support firmware running on UCOMM I/O adapters. Documentation for VOS Release 14.0.0 and later no longer contains information for XA2000-series modules except for information that involves cross-module functionality (for example, information on cross-compiling). o PA-7100-based Continuum 400 systems--As of September 1, 2000, Continuum Models 412, 422, 415, and 424 will no longer be available. However, Stratus will provide service for a minimum of five (5) years from September 1, 2000. o PA-7100-based Continuum 1200 systems--As of September 1, 2000, Continuum Models 1215, 1225, and 1245 will no longer be available. However, Stratus will provide service for a minimum of five (5) years from September 1, 2000. o PA-7100-based Continuum 600 systems--As of October 1, 2000, Continuum Models 615, 615S, and 625 will no longer be available. However, Stratus will provide service for a minimum of five (5) years from October 1, 2000. Consult your account team for more information about the preceding products. VOS Release Notation -------------------- In VOS Release 13.1.0, Stratus introduced a new notation for VOS releases. Previously, VOS products used a two-digit notation, which specified a major release number followed by an update or maintenance release number (for example, 12.0 or 12.2). Now, each VOS product release uses a three- or four-character notation to indicate the release type and contents. Table 1-2 describes each release type, including its distribution type and notation. SRB: VOS Release 14.5.0 (R914) 1-24 VOS Release Notation Table 1-2. VOS Release Notation ------------------------------------------------------------------------- | : : Distribution : | | : : Type : | | Release Type : Description : : Example | |-----------------------------------------------------------------------| | Major : The release contains a : General : 14.0.0 | | : new operating system, a : distribution : | | : new hardware platform, : : | | : and new functionality. : : | |-----------------------------------------------------------------------| | Update : The release contains : General : 14.1.0 | | : hardware and software : distribution : | | : enhancements. : : | |-----------------------------------------------------------------------| | Maintenance : The release contains bug : General : 14.1.1 | | : fixes only. : distribution : | |-----------------------------------------------------------------------| | Bug fix : The release contains : Available : 14.1.1a | | : accumulated bug fixes : only upon : | | : from major, update, or : request : | | : maintenance releases. : : | ------------------------------------------------------------------------- FOOTNOTE: 1 Numeric-keypad key Maintenance and bug-fix releases typically do not require any documentation changes. Therefore, Stratus does not plan to publish SRBs for those releases, and the SRB for the most recent major or update release will remain in effect for subsequent maintenance and bug-fix releases. Stratus will continue to publish SRBs for all major releases and for all update releases that require significant documentation changes. If a maintenance or bug-fix release requires accompanying documentation, Stratus will publish a .doc file that will be referenced in the cover letter for that release. You can find .doc files in the >system>doc directory on your module after you have installed the release. New and Changed Documentation ----------------------------- This section discusses the following topics. o ``New and Revised Manuals" o ``The VOS StrataDOC Online Documentation System" o ``The >system>doc Directory" o ``VOS Updates and Errata Files" SRB: VOS Release 14.5.0 (R914) 1-25 New and Changed Documentation New and Revised Manuals ----------------------- The following manuals are new or have been revised since VOS Release 14.0.0. See Appendix A for current revision levels. o VOS PL/I Subroutines Manual (R005) o VOS PL/I Language Manual (R009) o VOS PL/I Transaction Processing Facility Reference Manual (R015) o VOS BASIC Subroutines Manual (R018) o VOS COBOL Subroutines Manual (R019) o VOS FORTRAN Subroutines Manual (R020) o VOS Pascal Subroutines Manual (R021) o VOS COBOL Transaction Processing Facility Reference Manual (R034) o VOS FORTRAN Transaction Processing Facility Reference Manual (R036) o VOS Pascal Transaction Processing Facility Reference Manual (R038) o VOS C Subroutines Manual (R068) o VOS C Transaction Processing Facility Reference Manual (R069) o VOS System Analysis Manual (R073) o VOS Commands User's Guide (R089) o VOS Emacs User's Guide (R093) o VOS Commands Reference Manual (R098) o VOS PL/I User's Guide (R145) o Window Terminal Programmer's Guide for Asynchronous Communications (R194) o VOS Transaction Processing Facility Guide (R215) o Software Release Bulletin: NFS and RPC Release 1.3 (R252) o VOS System Administration: Administering and Customizing a System (R281) SRB: VOS Release 14.5.0 (R914) 1-26 New and Changed Documentation o VOS System Administration: Starting Up and Shutting Down a Module or System (R282) o VOS System Administration: Registration and Security (R283) o VOS System Administration: Disk and Tape Administration (R284) o VOS System Administration: Backing Up and Restoring Data (R285) o VOS System Administration: Administering the Spooler Facility (R286) o VOS System Administration: Configuring a System (R287) o Product Configuration Bulletin: Token-Ring Devices (R303) o VOS Symbolic Debugger User's Guide (R308) o VOS Standard C Reference Manual (R363) o VOS Standard C User's Guide (R364) o VOS Installation Guide (R386) o VOS Administrator's Guide for Open StrataLINK (R388) o Continuum Series 600 and 1200: Site Planning Guide (R391) o VOS STREAMS TCP/IP Migration Guide (R418) o VOS STREAMS TCP/IP Administrator's Guide (R419) o VOS STREAMS TCP/IP Programmer's Guide (R420) o VOS STREAMS TCP/IP User's Guide (R421) o VOS Data-Link Multiplexer Administrator's Guide (R425) o Product Configuration Bulletin: K104 I/O Adapter Using the GDL Driver (R426) o Product Configuration Bulletin: K450 and K460 SCSI/Ethernet I/O Controllers (R428) o Product Configuration Bulletin: U713 and U714 Ethernet PMC Cards (R441) o Continuum Series 600 and 1200: PMC-Card Installation Guide (R443) o VOS Continuum 600 and 1200 Series with PA-8000: Operation and Maintenance Guide (R445) SRB: VOS Release 14.5.0 (R914) 1-27 New and Changed Documentation o MQSeries Client for Stratus VOS (R450) o VOS GNU C++ User's Guide (R453) o VOS Continuum Series 600 and 1200: Operation and Maintenance Guide (R463) o Software Release Bulletin: VOS Apache Web Server Release 1.3.12 (R466) o Software Release Bulletin: VOS GNU C++ and GNU Tools Release 2.0.1 (R468) o Software Release Bulletin: VOS Samba Release 2.0.7 (R470) o Software Release Bulletin: VOS Release 14.5.0 (R914) The VOS StrataDOC Online Documentation System --------------------------------------------- You can access the manuals listed in the previous section as well as a selection of other VOS manuals through the Stratus online documentation system, VOS StrataDOC. VOS StrataDOC offers easy access to online documentation and is a convenient alternative to printed documentation. Hypertext links between chapters and from each entry in the table of contents and index help you to quickly find the answer to a question about a command, argument, or file name. You can also use VOS StrataDOC to scan through one or more online manuals to obtain more detailed information on a topic of interest. The VOS StrataDOC Web site is an online-documentation service provided by Stratus. It enables Stratus customers to view, search, download, print, and comment on VOS technical manuals via a common Web browser. It also provides the latest updates and corrections available on the VOS document set. If you are a Stratus customer with a current support contract, you can access the VOS StrataDOC Web site, at no charge, at http://stratadoc.stratus.com. You can also order the VOS StrataDOC CD-ROM from Stratus. For information about accessing the VOS StrataDOC Web site, contact the CAC. For information about ordering the VOS StrataDOC CD-ROM, see the section "Ordering Manuals" in the Preface. SRB: VOS Release 14.5.0 (R914) 1-28 New and Changed Documentation The >system>doc Directory ------------------------- The >system>doc directory contains copies of previous SRBs, the current version of the SRB in the file named r14.5.0_srb.memo, and other online documentation, including descriptions of fixed and known problems (in the file named 14.5.0_problems_srb.memo). The files listed in Table 1-3 are also available in the >system>doc directory. Note that Table 1-3 lists only the files in >system>doc that are relevant to topics discussed in this manual. Table 1-3. Documentation Files in the >system>doc Directory (Page 1 of 3) ------------------------------------------------------------------------ | File : Description | |----------------------------------------------------------------------| | as.doc : Describes changes to analyze_system | | : requests since the VOS System Analysis | | : Manual (R073) was last revised. | |----------------------------------------------------------------------| | c.doc : Describes changes made to VOS C since the | | : VOS C Language Manual (R040) was last | | : revised. | |----------------------------------------------------------------------| | cac_phones.doc : Lists the Customer Assistance Center (CAC) | | : phone numbers as of VOS Release 14.5.0. | | : (This list also exists in Table 10-1.) | |----------------------------------------------------------------------| | cache_tuning.doc : Describes recent changes to the cache | | : manager and how you can improve | | : performance by tuning the cache. | |----------------------------------------------------------------------| | cc.doc : Describes changes made to VOS Standard C | | : since the VOS Standard C Reference Manual | | : (R363) was last revised. | |----------------------------------------------------------------------| | cobol.doc : Describes changes made to VOS COBOL since | | : the VOS COBOL Language Manual (R010) was | | : last revised. | |----------------------------------------------------------------------| | datakit_admin_addendu : Describes changes made to the VOS | | m_ : Multiplexed Host Interface product since | | : the VOS Communications Software: Datakit | | r11.5.doc : Programming and Administration Guide | | : (R307) was written. (Note that the manual | | : title will change when the manual is next | | : revised.) | |----------------------------------------------------------------------| | debugger.doc : Describes the new watchpoint-related | | : requests available as of VOS Release | SRB: VOS Release 14.5.0 (R914) 1-29 New and Changed Documentation | : 14.1.0 for the debugger. | |----------------------------------------------------------------------| | fms>fms.doc : Documents the new FMS subroutines added to | | : provide FMS support for multiple processes | | : to update the terminal screen | | : simultaneously and to provide compatible | | : FMS terminal support for POSIX. See ``New | | : VOS Forms Management System (FMS) | | : Subroutines'' in Chapter 5 for a list of | | : the subroutines. | |----------------------------------------------------------------------| | fortran.doc : Describes changes made to VOS FORTRAN | | : since the VOS FORTRAN Language Manual | | : (R013) was last revised. | |----------------------------------------------------------------------| | osl_admin.doc : Describes the new osl_admin command for | | : administering an OSL implementation. | |----------------------------------------------------------------------| | pascal.doc : Describes changes made to VOS Pascal since | | : the VOS Pascal Language Manual (R014) was | | : last revised. | |----------------------------------------------------------------------| | pl1.doc : Describes changes made to VOS PL/I since | | : the VOS PL/I Language Manual (R009) was | | : last revised. | |----------------------------------------------------------------------| | stcp_interfaces.doc : Describes STCP-related network interfaces | | : beginning with VOS Release 14.1.0. | |----------------------------------------------------------------------| | posix>posix.doc : Describes the VOS POSIX.1 support | | : beginning with VOS Release 14.3.0. | |----------------------------------------------------------------------| | terminal_support.doc : Describes the following terminal support | | : topics for VOS Release 14.0.0 and later. | | : | | : o new .ttp definition files and setups | | : | | : o Office/2000 and terminal support | | : | | : o changes to the commands display and | | : display_file | | : | | : o the TTP include file emacs.incl.ttp | | : | | : o predefined TTPs for v105 and v105_ansi | | : | | : o TTP file changes | |----------------------------------------------------------------------| | tpf.doc : Describes changes made to VOS TPF since | | : the VOS Transaction Processing Facility | SRB: VOS Release 14.5.0 (R914) 1-30 New and Changed Documentation | : reference manuals and the VOS Transaction | | : Processing Facility Guide (R215) were last | | : revised. | |----------------------------------------------------------------------| | x25_command_args.doc : Describes arguments added to the x25 | | : command for VOS Release 14.0.0 and later: - | | : cafis_reset_diag, -cafis_tp1, and - | | : cafis_tp2. | ------------------------------------------------------------------------ Note: The d089-02.doc file has been deleted from the >system>doc directory. The information that it contained is now discussed in the VOS Commands User's Guide (R089). VOS Updates and Errata Files ---------------------------- Beginning in VOS Release 14.2.0, the vos_pubs.corrections file has been replaced with individual updates and errata files for each manual. All of the updates and errata files have the naming convention manual_number.errata.txt and are located in the following directory. >system>doc>vos_pubs_corrections Each updates and errata file gives a detailed description of the corrections or updated information for a specific manual. The errata information includes a bug number, the date of the errata entry, and the location in VOS StrataDOC and in the printed manual where the new or corrected information is included. The file may also contain updated information that has not yet been added to the manual. After a correction or update has been incorporated into a revision of a manual, Stratus removes the information from the updates and errata file. You can also view updates and errata information from the VOS StrataDOC Web site. Customer Survey --------------- Some manuals contain a customer survey at the end of the manual. This survey is an effort to solicit your feedback on a manual's quality, usability, and appropriateness. Stratus would appreciate your taking a few minutes to complete this survey and mail it back to us. -------------------------------------- FOOTNOTE: 1 The Dow Jones News Retrieval is supported on PA-7100. SRB: VOS Release 14.5.0 (R914) Chapter 2: Operation and Administration ============================ This chapter describes changes that affect the operation and administration of Stratus systems. It contains the following sections. o ``Changes to the module_start_up.cm Command Macro" o ``Continuum-Series Modules" o ``Disk-Related Changes" o ``Tape-Related Changes" o ``The V105 Terminal and Other Terminal Support Issues" o ``Miscellaneous Changes to the analyze_system Command" o ``The VOS Dead-CPU Time-Out Value" o ``Freezing and Thawing Processes" o ``Terminating Dumps Prematurely" o ``Tuning the File System Cache Manager" o ``Device and Firmware Configuration Summary" o ``Changes to General User Commands" o ``Changes to Security-Related Commands" o ``Changes to System Administration Commands" o ``Changes to the Manual Boot Procedure" o ``Change to Home Directory During Automatic Startup" o ``Change to the devices.tin File" o ``Change to the languages.tin File" For special instructions about installing this VOS release, see ``Installing Software'' in Chapter 10. SRB: VOS Release 14.5.0 (R914) 2-1 Changes to the module_start_up.cm Command Macro Changes to the module_start_up.cm Command Macro ----------------------------------------------- Note the following changes related to the module_start_up.cm command macro. o The load_kernel_program commands for the lower-level VOS drivers required for OS TCP/IP (the Data-Link Multiplexer, the GDL driver, and the BDL driver) have changed. Since the location of these drivers has changed, the path names for these drivers have changed, as specified by the load_kernel_program commands in the module_start_up.cm command macro. For more information, see ``Change in the Location of Lower-Level Drivers'' in Chapter 5. o On Continuum-series modules, the module_start_up.cm command macro must contain the dump_memory command in the following command lines. &if (exists (master_disk)>system>command_library>dump_memory.pm) &then dump_memory &else log_syserr_message `Module_start_up error: &+ Dump_memory command not installed.' -direct If you are using a module_start_up.cm command macro from Stratus, these lines exist as comments and you must activate the commands by deleting the ampersand (&) and space that precede each line. If you are using a module_start_up.cm command macro that you have created or customized, you must add these lines after the configure_devices and configure_disks command lines, or after the add_link_board command lines if they exist in the file. (When a module_start_up.cm command macro contains add_link_board command lines, they typically exist immediately after the configure_devices and configure_disks command lines.) For complete information about the dump_memory command, see the manual VOS System Administration: Configuring a System (R287). o Beginning in VOS Release 14.1.0, there are new commands that load STCP. For more information, see the VOS STREAMS TCP/IP Administrator's Guide (R419). o Beginning in VOS Release 14.1.0, there are new commands that load the lower-level drivers for STCP and OS TCP. For more information, see ``Network Interfaces and Required Drivers'' in Chapter 5 for both STCP and OS TCP/IP. o Beginning in VOS Release 14.1.0, there are new commands required to run OS TCP/IP and STCP on the same module. See the VOS STREAMS TCP/IP Migration Guide (R418). o Beginning in VOS Release 14.1.0, the module_start_up.cm command macro includes the following command line, which you must customize SRB: VOS Release 14.5.0 (R914) 2-2 Changes to the module_start_up.cm Command Macro if your configuration includes SDLMUX. & dlmux_admin # init_sdlmux For more information about SDLMUX, see ``The Data-Link Multiplexer: SDLMUX and DLMUX'' in Chapter 5. For more information about how to configure SDLMUX, see the VOS Data-Link Multiplexer Administrator's Guide (R425). o Beginning in VOS Release 14.3.0, the relative ordering of the include library search paths and object library search paths in the module_start_up.cm command macro has been clarified. The correct ordering for the include library paths is as follows: >system>PRODUCT1>include_library >system>PRODUCT2>include_library . . . >system>PRODUCTN>include_library >system>include_library The correct ordering for the object library paths is as follows: >system>PRODUCT1>object_library >system>PRODUCT2>object_library . . . >system>PRODUCTN>object_library >system>posix_object_library (if desired) >system>c_object_library (if desired) >system>object_library Note: OS TCP/IP is not compatible with POSIX. Do not attempt to SRB: VOS Release 14.5.0 (R914) 2-3 Changes to the module_start_up.cm Command Macro compile or bind source programs that reference OS TCP/IP functions with the POSIX headers or POSIX runtime functions. o Beginning in VOS Release 14.5.0, the install_new_files command should appear in the module_start_up.cm command macro before the local area network (LAN) drivers are loaded. The following sample module_start_up.cm command macro illustrates this change. . . . & install_new_files -syserr . . . & & Load LAN drivers. & & ++++ Uncomment the next line if you are using the K104 Ethernet & ++++ adapter & & load_kernel_program >system>kernel_loadable_library>gdl driver & . . . Continuum-Series Modules ------------------------ SRB: VOS Release 14.5.0 (R914) 2-4 Continuum-Series Modules This section discusses the following topics related to the operation and administration of Continuum-series modules running VOS Release 14.0.0 and later. o ``CPU/Memory Boards" o ``Summary of Processors for Continuum-Series Modules" o ``Change to the reset_configuration Command" o ``Auto Recovery for Hung Modules" o ``New Tape Drives" For more information about Continuum-series hardware, see the following manuals. o Continuum Series 600 and 1200: Site Planning Guide (R391) provides information about planning a site for Continuum-series modules with PA-7100 processors and/or PA-8000 processors. o Continuum Operation and Maintenance: 600 and 1200 Series (R396) provides information about configuring modules with PA-7100 processors. o VOS Continuum 600 and 1200 Series with PA-8000: Operation and Maintenance Guide (R445) provides information about configuring modules with PA-8000 processors. o VOS Continuum Series 600 and 1200: Operation and Maintenance Guide (R463) provides information about configuring modules with PA-8500 processors. CPU/Memory Boards ----------------- Beginning in Release 14, VOS supports the PA-8X00 processor family in various configurations, as the following sections describe. o ``PA-8000 Processors" o ``PA-8500 Processors" o ``PA-8600 Processors" o ``Larger Memory Sizes" o ``Configurations" SRB: VOS Release 14.5.0 (R914) 2-5 Continuum-Series Modules o ``Summary of Processors for Continuum-Series Modules" Note: On modules with PA-8000 family processors, code compiled for PA-8000 family processors may run more quickly than code compiled for PA-7100 processors. The performance effect, however, differs according to the application and your needs. In some cases, you may want to recompile your PA-7100 code for the PA-8000 processor family. PA-8000 Processors ****************** Beginning in Release 14.0.0, VOS supports Hewlett-Packard PA-8000 180- megahertz (MHz) processors with a 2-megabyte (MB) cache running in 32-bit mode. The PA-8000 processor, which is located on a combined CPU/memory board, is upward-compatible with the PA-7100 processor (VOS Releases 13 and 14 support PA-7100 processors). The PA-8000 processor provides major enhancements in performance and functionality, while the continuity and compatibility of VOS provide a smooth upgrade path for the installed base of PA-7100-based Continuum- series modules. The CPU/memory board with the PA-8000 processor resembles a suitcase and requires two slots in a main chassis cabinet. It is available in 6- and 12- slot modules, and only in uni- and twin-processor configurations; the PA- 8000 processor is not available in quad-processor configurations. (For more information, see ``Configurations" later in this chapter.) The model number for the PA-8000 processor is G311 for a uniprocessor configuration and G321 for a twin-processor configuration. The model number appears, for example, in the Model column of the output of the list_boards request of the analyze_system command. PA-8500 Processors ****************** Beginning in Release 14.2.0, VOS supports Hewlett-Packard PA-8500 360 MHz processors with a 2 MB cache running in 32-bit mode. The PA-8500 processor, which is located on a combined CPU/memory board, is upward- compatible with the PA-7100 processor (VOS Releases 13 and 14 support PA- 7100 processors) and the PA-8000 processor. The PA-8500 processor provides major enhancements in performance and functionality, while the continuity and compatibility of VOS provides a smooth upgrade path for the installed base of PA-7100 and PA-8000-based Continuum-series modules. SRB: VOS Release 14.5.0 (R914) 2-6 Continuum-Series Modules The CPU/memory board with the PA-8500 processor resembles a suitcase and requires two slots in a main chassis cabinet. It is available in 8- and 12- slot modules, and only in uni- and twin-processor configurations; the PA- 8500 processor is not available in quad-processor configurations. (For more information, see ``Configurations" later in this chapter.) Beginning in Release 14.2.1, VOS supports a 6-slot module that runs only in uni-processor configurations. The model number for the PA-8500 processor is G314 for a uni-processor configuration and G324 for a twin-processor configuration. The model number appears, for example, in the Model column of the output of the list_boards request of the analyze_system command. PA-8600 Processors ****************** Beginning in Releases 14.2.3 and 14.3.1, VOS supports Hewlett-Packard PA- 8600 480 MHz processors with a 2 MB cache running in 32-bit mode. The PA- 8600 processor, which is located on a combined CPU/memory board, is upward- compatible with the PA-7100 processor (VOS Releases 13 and 14 support PA- 7100 processors), the PA-8000 processor, and the PA-8500 processor. The PA-8600 processor provides major enhancements in performance and functionality, while the continuity and compatibility of VOS provides a smooth upgrade path for the installed base of PA-7100, PA-8000, and PA- 8500-based Continuum-series modules. The CPU/memory board with the PA-8600 processor resembles a suitcase and requires two slots in a main chassis cabinet. It is available in 8- and 12- slot modules, and only in uni- and twin-processor configurations; the PA- 8600 processor is not available in quad-processor configurations. (For more information, see ``Configurations" later in this chapter.) The model number for the PA-8600 processor is G333 for a uni-processor configuration and G334 for a twin-processor configuration. The model number appears, for example, in the Model column of the output of the list_boards request of the analyze_system command. Larger Memory Sizes ******************* Beginning in VOS Release 14.0.0, larger memory sizes allow a maximum of 2 GB of total memory for uni- or twin-processor configurations of PA-8000 or PA-7100 processors and 3 GB of total memory for quad-processor configurations of PA-7100 processors. SRB: VOS Release 14.5.0 (R914) 2-7 Continuum-Series Modules Beginning in VOS Release 14.2.0, larger memory sizes allow a maximum of 4 GB of total memory for uni- or twin-processor configurations of PA-8X00 processors. Note, however, that PA-8X00 6-slot modules allow a maximum of 0.5 GB or 2 GB of total memory, depending on their configuration. Configurations ************** Table 2-1 describes the uni-, twin-, and quad-processor configurations of Continuum-series CPU/memory boards. Note: A simplexed board is not fault tolerant. Note: When the configuration contains more than one CPU/memory board and the boards are duplexed, each duplexed pair must have the same logical CPU and memory configuration. PA-8X00 processors are available only in uni- and twin-processor configurations. PA-7100 processors are available in uni-, twin-, or quad- processor configurations. Table 2-1. CPU/Memory Board Configurations -------------------------------------------------------------------------- | Config- : Number of : Number : | | : : : | | uration : Logical CPUs: of Boards: Description | |------------------------------------------------------------------------| | Uni : One : One : One CPU/memory board is | | : : : simplexed and functions as one | | : (From the : : logical CPU with memory. | | : system's :----------------------------------------------| | : perspective : Two : Two CPU/memory boards run in | | : , this : : lockstep as one duplexed pair. | | : module has : : The pair functions as one | | : one CPU.) : : logical CPU with memory. | |-----------: -----------------------------------------------------------| | Twin : Two : One : One CPU/memory board is | | : : : simplexed and functions as two | | : (From the : : logical CPUs with memory. | | : system's :----------------------------------------------| | : perspective : Two : Two CPU/memory boards run in | | : , this : : lockstep as one duplexed pair. | | : module has : : Each board of the pair | | : two CPUs.) : : functions as two logical CPUs | | : : : with memory. As one duplexed | | : : : pair, the boards provide two | | : : : logical CPUs. | |-----------: -----------------------------------------------------------| | Quad : Four : Two : Two CPU/memory boards (with PA- | SRB: VOS Release 14.5.0 (R914) 2-8 Continuum-Series Modules | : : : 7100 processors) are simplexed. | | : (From the : : Each board functions separately | | : system's : : as two logical CPUs with memory. | | This : perspective :----------------------------------------------| | config- : , this : Three : One CPU/memory board (with PA- | | : module has : : 7100 processors) is simplexed | | uration : four CPUs.) : : and functions as two logical | | is : : : CPUs with memory, and two | | available : : : CPU/memory boards run in | | only with: : : lockstep as one duplexed pair | | : : : providing two logical CPUs with | | PA-7100 : : : memory. | | : :----------------------------------------------| | processor : : Four : Four CPU/memory boards (with PA- | | s. : : : 7100 processors) run in | | : : : lockstep as two duplexed pairs. | | : : : Each board of each pair | | : : : functions as two logical CPUs | | : : : with memory. As two duplexed | | : : : pairs, the four boards provide | | : : : four logical CPUs. | -------------------------------------------------------------------------- FOOTNOTE: 1 Numeric-keypad key Summary of Processors for Continuum-Series Modules ************************************************** Table 2-2 summarizes processors for Continuum-series modules. Table 2-2. Processors for Continuum-Series Modules -------------------------------------------------------------------------- | : : Number of : : | | : : : : | | : Continuum : Main Chassis : Model : Processor | | : : : : | | Processor : Modules : Slots : Numbers : Configurations | |------------------------------------------------------------------------| | PA-7100 : 600-series : 6 : 610 and 610S : Uni | | : : :-------------------------------| | : : : 620 : Twin | | : : :-------------------------------| | : : : 615 : Uni | | : : :-------------------------------| | : : : 625 : Twin | |------------: ----------------------------------------------------------| | PA-7100 : 1200-series: 12 : 1210 : Uni | | : : :-------------------------------| SRB: VOS Release 14.5.0 (R914) 2-9 Continuum-Series Modules | : : : 1215 : Uni | | : : :-------------------------------| | : : : 1220 : Twin | | : : :-------------------------------| | : : : 1225 : Twin | | : : :-------------------------------| | : : : 1245 : Quad | |------------: ----------------------------------------------------------| | PA-8000 : 600-series : 8 (6 usable) : 618 : Uni | | : : :-------------------------------| | : : : 628 : Twin | |------------: ----------------------------------------------------------| | PA-8000 : 1200-series: 12 : 1218 : Uni | | : : :-------------------------------| | : : : 1228 : Twin | |------------: ----------------------------------------------------------| | PA-8500 : 600-series : 6 : 616 and 616S : Uni | |------------------------------------------------------------------------| | PA-8500 : 600-series : 8 (6 usable) : 619 : Uni | | : : :-------------------------------| | : : : 629 : Twin | | : : : : | | : : : : | |------------: ----------------------------------------------------------| | PA-8500 : 1200-series: 12 : 1219 : Uni | | : : :-------------------------------| | : : : 1229 : Twin | |------------: ----------------------------------------------------------| | PA-8600 : 600-series : 8 (6 usable) : 651-2 : Uni | | : : :-------------------------------| | : : : 652-2 : Twin | |------------: ----------------------------------------------------------| | PA-8600 : 1200-series: 12 : 1251-2 : Uni | | : : :-------------------------------| | : : : 1252-2 : Twin | -------------------------------------------------------------------------- New System Console Command -------------------------- Beginning in VOS Release 14.0.0, Continuum-series modules based on the PA- 8000 family processors have an additional system console command, hpmc_reset (this command is not available on modules based on the PA-7100 processor). The hpmc_reset command enables you to reset a hung or malfunctioning module. When the hpmc_reset command restarts the system, it preserves the context and dump information that the CAC needs to successfully diagnose system problems. Such information is lost when, for example, the reset_bus command is issued. For complete information about SRB: VOS Release 14.5.0 (R914) 2-10 Continuum-Series Modules the hpmc_reset command, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). Change to the reset_configuration Command ----------------------------------------- Beginning in VOS Release 13.2.0 on Continuum-series modules, the reset_configuration command includes the argument - reset_cabinet_configuration. This argument puts all cabinet data collectors (CDCs) in "address-thawed" mode, which means that the cabinets can renumber themselves before the command "freezes" the addresses. Thereafter, the cabinets will not be renumbered again until the command is reissued. The default value of this argument is no. You should specify the -reset_cabinet_configuration argument each time a CDC is added to the system or after a CDC has been removed and reinserted. A "thawed" CDC is indicated by two blinking lights at the bottom of the address LED. Upon detection of a "thawed" CDC, the cabinet-monitoring software will advise the host of the CDC's state by issuing the following messages. CDC: WARNING, cabinet n's cabinet number is volatile and indeterminate. CDC: use reset_configuration -reset_cabinet_configuration freeze cab numbers For more information about the reset_configuration command, see the manual VOS System Administration: Configuring a System (R287). Auto Recovery for Hung Modules ------------------------------ A Continuum-series module is hung if it sends no indication of activity to the console controller for five minutes. The setting of the attempt_auto_recovery variable determines if a hung module automatically attempts to recover or if it requires that you manually restart it. The setting of this variable may differ from module to module. Stratus recommends that you disable automatic recovery attempts (that is, Stratus recommends that you set the value of the attempt_auto_recovery variable to No) because the automatic recovery process can delete system information that the CAC needs to determine the cause of the system failure. For information about how to determine the setting of the SRB: VOS Release 14.5.0 (R914) 2-11 Continuum-Series Modules attempt_auto_recovery variable on your module, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). For information about changing the setting, contact the CAC. New Tape Drives --------------- Beginning in VOS Release 14.0.0, Stratus offers the following tape drives for Continuum-series modules. o T705 DDS-3 DAT Drive o T706 DDS-3 DAT Drive with Autoloader For additional information about these tape drives, see ``The T705 and T706 Tape Drives" later in this chapter. Disk-Related Changes -------------------- This section discusses the following disk-related changes. o ``Changes to the D700 Subsystem" o ``New Disk Commands" o ``Changed Disk Commands" o ``Changes to Disk-Related analyze_system Requests" o ``New Disk-Related analyze_system Requests" o ``Open Disk Support" o ``Streamlining Disk Renames" o ``New Disk Salvaging Behavior" Changes to the D700 Subsystem ----------------------------- The D700 Disk/Tape Subsystem supports SCSI disk devices. It is installed in a D700-00X disk/tape enclosure and is connected to the K450 or K460 I/O controller. The D700 subsystem supports the following disk devices on Continuum-series modules. SRB: VOS Release 14.5.0 (R914) 2-12 Disk-Related Changes (For additional information about the changes to the disk commands, see ``Changed Disk Commands" later in this chapter.) o D701 and D702 disk drives--The D701 (1 GB, 5400 RPM) and D702 (1.9 GB, 5400 RPM) disk drives were introduced with VOS Release 13.0 for use with the D700 subsystem. These disk drives are still supported in VOS Release 14.0.0 and will be fully supported in subsequent releases. However, these disk drives are no longer available from the manufacturer. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70300 disk drive--The D70300 (1 GB, 7200 RPM) disk drive was introduced in VOS Release 13.0.1 for use with the D700 subsystem. This disk drive is still supported in VOS Release 14.0.0 and will be fully supported in subsequent releases. However, this disk drive is no longer available from the manufacturer, and because of technology trends, there is no planned replacement disk at the 1 GB capacity. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70400 disk drive--The D70400 (2 GB, 7200 RPM) SCSI disk drive is still supported in VOS Release 14.0.0 and will be fully supported in subsequent releases. However, this disk drive is no longer available from the manufacturer. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70410 disk drive--The D70410 (2.2 GB, 7200 RPM) SCSI disk drive is introduced in VOS Release 14.0.0 for use with the D700 subsystem. The D70410 can be fully duplexed with the older disk drives of the same family. It is SCSI-II compatible and is capable of burst data transfer speeds of 20 Mbps, with sustained transfer rates of 1.5 to 9.5 Mbps, depending on the zone in which the transfer takes place. However, this disk drive is no longer available from the manufacturer, and because of technology trends, there is no planned replacement disk at the 2.2 GB capacity. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70510 disk drive--The D70510 (4 GB, 7200 RPM) SCSI disk drive is still supported in VOS Release 14.0.0 and will be fully supported in subsequent releases. However, this disk drive is no longer available from the manufacturer. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70520 disk drive--The D70520 (4.5 GB, 7200 RPM) SCSI disk drive was introduced in VOS Release 14.0.0 for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the same family. It is SCSI-II compatible and is capable of burst data transfer speeds of 20 Mbps, with sustained transfer rates of 1.5 to 9.5 Mbps, SRB: VOS Release 14.5.0 (R914) 2-13 Disk-Related Changes depending on the zone in which the transfer takes place. However, this disk drive is no longer available from the manufacturer. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70530 disk drive--The D70530 (4.5 GB, 7200 RPM) SCSI disk drive was introduced in VOS Releases 13.4.0 and 14.0.1 for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the same family. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps, with sustained transfer rates of 9.375 to 15 Mbps, depending on the zone in which the transfer takes place. However, this disk drive is no longer available from the manufacturer, and because of technology trends, there is no planned replacement disk at the 4.5 GB capacity. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70600 disk drive--The D70600 (9.1 GB, 7200 RPM) SCSI disk drive was introduced in VOS Release 14.0.0 for use with the D700 subsystem. It is SCSI-II compatible and is capable of burst data transfer speeds of 20 Mbps, with sustained transfer rates of 1.5 to 11 Mbps, depending on the zone in which the transfer takes place. However, this disk drive is no longer available from the manufacturer. Stratus suggests that you purchase the newer, higher capacity disk drives when you require additional capacity. o D70610 disk drive--The D70610 (9.1 GB, 7200 RPM) SCSI disk drive was introduced in VOS Releases 13.4.0 and 14.0.1 for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the D706 family. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps, with sustained transfer rates of 3.75 to 15 Mbps. However, this disk drive is no longer available from the manufacturer. Stratus suggests that you purchase the newer, higher-capacity disk drives when you require additional capacity. o D70620 disk drive--The D70620 (9 GB, 10,000 RPM) SCSI disk drive was introduced in VOS Release 14.1.0 for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the D706 family. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps. It features a reduced rotational latency of 2.99 msec. o D70700 disk drive--The D70700 (18.2 GB, 7200 RPM) SCSI disk drive was introduced in VOS Releases 13.4.0 and 14.0.1 for use with the D700 subsystem. It is the first drive of its family and therefore can only be duplexed with other 18 GB drives It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps, with sustained transfer rates of 3.75 to 15 Mbps. SRB: VOS Release 14.5.0 (R914) 2-14 Disk-Related Changes o D71100 disk drive--The D71100 (18 GB, 10,000 RPM) SCSI disk drive was introduced in VOS Release 14.1.0 for use with the D700 subsystem. It is the first drive of its family and therefore can only be duplexed with other 18 GB drives. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps. It features a reduced rotational latency of 2.99 msec. o D71200 disk drive--The D71200 (34 GB, 10,000 RPM) SCSI disk drive was introduced in VOS Release 14.2.0 (and supported in 14.1.0) for use with the D700 subsystem. It is the first drive of its family and therefore can only be duplexed with other 34 GB drives. It is SCSI- III compatible and is capable of burst data transfer speeds of 20 Mbps. It features a reduced rotational latency of 2.99 msec. o D71120 disk drive--The D71120 (18 GB, 10,000 RPM) SCSI disk drive was introduced in VOS Release 14.5.0 (and supported in 14.3.0 and later) for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the D711 family. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps. It features a reduced rotational latency of 2.99 msec. o D71150 disk drive--The D71150 (18 GB, 15,000 RPM) SCSI disk drive was introduced in VOS Release 14.5.0 (and supported in 14.3.0 and later) for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the D711 family. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps. It features a reduced rotational latency of 2.99 msec. o D71220 disk drive--The D71220 (34 GB, 10,000 RPM) SCSI disk drive was introduced in VOS Release 14.5.0 (and supported in 14.3.0 and later) for use with the D700 subsystem. It can be fully duplexed with the older disk drives of the D712 family. It is SCSI-III compatible and is capable of burst data transfer speeds of 20 Mbps. It features a reduced rotational latency of 2.99 msec. New Disk Commands ----------------- Beginning in VOS Release 14.4.0, the new display_disk_fragmentation command can detect fragmented files, directories, and free space on a disk. The command's description follows. display_disk_fragmentation Privileged --------------------------------------------------------------------------- SRB: VOS Release 14.5.0 (R914) 2-15 Purpose Purpose ------- This command displays the fragmented state of the files, directories, and free space on a mounted logical volume. This command will not work over a network. Display Form ------------------------------------------------------------------------ | ------------------- display_disk_fragmentation -------------------- | | -- | | | | disk_name: | | | | -check_files: no | | | | -members: no | | | | -brief: yes | ------------------------------------------------------------------------ Command Line Form ----------------- display_disk_fragmentation disk_name [-check_files] [-members] [-no_brief] Arguments --------- disk_name Specifies the name of the disk volume for which fragmentation information on files, directories, and free space is required. -check_files If you specify yes, the command displays fragmentation information for all files and directories on the volume. (Note that this can take SRB: VOS Release 14.5.0 (R914) 2-16 Arguments a significant amount of time.) If you specify no (the default), the command displays only free space. -members Displays data for each individual member disk or for the whole logical volume. If you specify yes, the command displays data for each individual member disk along with summary statistics for the whole logical volume. If you specify no (the default), the command displays only the summary statistics for the whole logical volume. -brief Determines the display format of the free-space distribution output. If you specify no, the command displays each individual fragment. If you specify yes (the default), the command displays a list of the free-space fragments in the following block groupings: - 1-7 blocks - 8-15 blocks - 16-31 blocks - 32-63 blocks - 64-127 blocks - 128-255 blocks - more than 255 blocks Examples -------- The following example displays the output for a single logical volume using the default behavior to the display_disk_fragmentation command. display_disk_fragmentation a12_abc disk %se#a12_abc Size: 340464 Used 301444 (86.01%) Free: 49020 (13.99%) SRB: VOS Release 14.5.0 (R914) 2-17 Examples Max free chunk: 2261 (0.65%) Free space distribution: 1- 7 blocks: 5003 fragments (13049 blocks, 3.72%) 8- 15 blocks: 1016 fragments (10977 blocks, 3.13%) 16- 31 blocks: 324 fragments (6197 blocks, 1.77%) 32- 63 blocks: 51 fragments (2258 blocks, 0.64%) 64- 127 blocks: 38 fragments (3328 blocks, 0.95%) 128-255 blocks: 21 fragments (3526 blocks, 1.00%) more than 255 blocks: 15 fragments (9685 blocks, 2.76%) In the preceding example, the fields display the following information. - Size is the total number of blocks in the file partition. - Used is the number of blocks used by the files. - Free is the number of unallocated blocks. - Max free chunk is the size, in blocks, of the largest contiguous chunk of free space on the disk. Also displayed is a percentage of the total number of blocks in the Used, Free, and Max free chunk fields. The Free space distribution section displays the number of contiguous free blocks of various sizes. For example, there are 5003 fragments with block sizes between 1 and 7. These 5003 fragments take up 13,049 blocks of the disk's total free space, or 3.72% of that space. This information becomes useful when you wish to create extent files of 64 blocks, as you can quickly verify if there are fragments with sizes greater than 64. In the following example, the -brief argument is set to no, which displays a list of the free-space fragments. (Note that the command does not display sizes with a zero count.) display_disk_fragmentation a12_abc -no_brief disk %se#a12_abc Size: 268288 Used 42283 (15.76%) SRB: VOS Release 14.5.0 (R914) 2-18 Examples Free: 226005 (84.24%) Max free chunk: 196313 (73.17%) Free space distribution: Free Size: Count: Free Size:Count: Free Size:Count: 2 1 15 2 24 1 27 1 100 1 32481 118731 14388 1 196313 1 The following example shows the output when the -check_files argument is specified. Note that the total items column indicates the total number of items of each type on the disk, and the fragmented column indicates the number of those items that are fragmented. display_disk_fragmentation a12_abc -check_files disk %se#a12_abc Size: 268288 Used 42283 (15.76%) Free: 226005 (84.24%) Max free chunk: 196313 (73.17%) Free space distribution: 1-7 blocks: 1 fragment (2blocks, 0.00%) 8-15 blocks: 2 fragments (30 blocks, 0.01%) 16-31 blocks: 2 fragments (51 blocks, 0.02%) 32-63 blocks: 0 fragments 64-127 blocks: 1 fragment (100 blocks, 0.04%) 128-255 blocks: 0 fragments more than 255 blocks: 4 fragments (225822 blocks, 88.17%) Files and Directories: SRB: VOS Release 14.5.0 (R914) 2-19 Examples total items: fragmented: directory: 131 24 (18%, 179 fragments) file: 746 6 (0%, 783 fragments) index: 15 0 (0%, 15 fragments) Changed Disk Commands --------------------- All disk commands allow you to specify the values 0 through 31 for the member argument in order to specify disks with logical disk volumes containing up to 32 members. (The member argument specifies the member disk's location within the logical volume; previously, its values were 0 through 9.) Note: If you are booting a VOS release earlier than VOS Release 14.0.0, the presence of a logical disk volume containing more than 10 members could result in a system interruption. In addition, this section discusses the following changes to disk commands. o ``Changes to display_disk_label" o ``Changes to display_disk_info" o ``Changes to initialize_boot_disk" o ``Changes to initialize_disk and initialize_duplex_disk" o ``Changes to set_partition_size" o ``Changes to salvage_disk" o ``System Error Log Changes" o ``Changes to start_disk_recovery" o ``Changes to update_disk_label" Changes to display_disk_label ****************************** The output of the display_disk_label command has been updated to show the value of each of the new arguments described in ``Changes to update_disk_label" later in this chapter. The following example SRB: VOS Release 14.5.0 (R914) 2-20 Examples illustrates the new output when the arguments are set to no. Disk ID: m1_mst.0-1.pri Disk Initialized: 98-06-29 12:52:52 est Disk Root Dir: m1_mst Drive Type: D705 Capacity: 1100777 disk blocks. Duplexed state: RUNNING ALONE Duplexed State Updated: 98-11-30 09:53:22 est Bad blocks are remapped. Boot disk System: sys (1) Module: m1 (1) Station number: 1 Flags: monitor_terminal,auto_boot,has_bad_blk_part, no_quick_dump,no_skip_unreferenced_disk_cache, no_skip_paged_kernel,no_skip_paged_process, no_skip_kernel_maps Time zone: est Time zone delta: -300 (standard) Default boot partition: 1 Booted from partition: 1 Boot Partition Info P# Size Bound by Date Version * 1 3791 Installer 98-10-28 09:43:58 VOS Release 14.1.0.dev.cp For more information about the display_disk_label command, see the manual VOS System Administration: Disk and Tape Administration (R284). SRB: VOS Release 14.5.0 (R914) 2-21 Examples Changes to display_disk_info ***************************** Beginning in VOS Release 14.4.0, the display_disk_info command now displays the recovery state for any member disks that are recovering. Previously, it displayed the recovery state for the first member only. For more information about the display_disk_info command, see the manual VOS System Administration: Disk and Tape Administration (R284). Changes to initialize_boot_disk ******************************** The initialize_boot_disk command has a new argument, -quick_dump. After a failure, the system automatically writes a dump image to disk. When you specify the -quick_dump argument, the system performs only a partial dump while offline, and then performs a memory dump while booting. This reduces the time the system is offline. Beginning in VOS Release 14.2.0, the default dump partition size for the initialize_boot_disk command defaults to 10% of the boot disk's capacity. (Previously, the default was 1984 blocks.) In order to calculate the dump partition size, you must specify the disk name before displaying the form, and once the form is displayed, you must not modify the disk_name field. For more information about the initialize_boot_disk command, see the manual VOS System Administration: Disk and Tape Administration (R284). Changes to initialize_disk and initialize_duplex_disk ****************************************************** The initialize_disk and initialize_duplex_disk commands now allow you to specify the values 0 through 31 for the new_member argument in order to create logical disk volumes containing up to 32 members. (Prior to VOS Release 14.0.0, logical disk volumes could contain a maximum of 10 members.) The initialize_disk command also allows you to specify the values 1 through 32 for the -n_member argument. Note: Stratus recommends against creating large logical volumes due to the extensive time it could take to recover and salvage the disks. In addition, beginning in VOS Release 14.4.0, the behavior of the initialize_disk command's new_disk_name argument has changed as follows: o When you supply new_disk_name, the values of the -new_member and - n_members fields are automatically updated. SRB: VOS Release 14.5.0 (R914) 2-22 Examples o If new_disk_name does not exist, the value of -new_member is set to 0, and the value of -n_members is set to 1. o If new_disk_name does exist, VOS locates the value for -new_member by starting at member 0 and looking at each member in succession. As soon as a member is not found, the system selects that new number. Changes to set_partition_size ****************************** The set_partition_size command has the following changes. o For the size argument, the maximum value for a log partition using the default extent size of 128 is now 2,088,960 disk blocks (previously, it was 130,560 disk blocks). o This command has a new argument, -extent_size value, that specifies the extent size to be used by the log partition. Only the log partition can have a value greater than 1. When you create new partitions, the default value is 128 for log partitions and 1 for all other partitions. When you resize partitions, the default is the current partition extent size. Note that extent sizes must be a multiple of 8. For more information about the -extent_size argument, see the set_partition_size command description in the manual VOS System Administration: Disk and Tape Administration (R284). Changes to salvage_disk ************************ Beginning in VOS Release 14.4.0, when you issue the salvage_disk command and the system cannot determine the most recent partner of a duplexed disk, the terminal displays the following message: salvage_disk: Unable to determine the most recent partner of duplex disk, disk_name. Please contact the Stratus Customer Assistance Center if help is needed in determining the most recent partner. In addition, the system writes the following message to the system error log. This information is useful in determining which partner is the most recent. salvage_disk_in_parallel: Unable to determine the most recent disk of the SRB: VOS Release 14.5.0 (R914) 2-23 Examples pair of the pair disk_name disk_name.0-1.pri state: RUNNING_ALONE updated 00-00-00 00:00:00 est disk_name.0-1.pri last_mounted:NNN, last_shutdown: NNN,2 pcp_state: N disk_name.0-1.pri flags: shutdown, shutdown_by_esd disk_name.0-1.sec state: RUNNING_ALONE updated 00-00-00 00:00:00 est disk_name.0-1.sec last_mounted: NNN, last_shutdown: NNN, pcp_state: N disk_name.0-1.sec flags: (none) If the system cannot determine the most recent partner of the master disk during boot, the terminal displays the information shown in bold in the preceding example along with the following message: salvage_disk_in_parallel: Please contact the Stratus Customer Assistance Center if help is needed in determining the most recent partner. Select either the primary (pri) or secondary (sec) side of disk_name? If the disk is salvaged for the first time after being initialized, the following message is displayed regardless of whether the disk is simplexed or duplexed. salvage reason: disk_name - disk is newly initialized For more information about the salvage_disk command, see the manual VOS System Administration: Disk and Tape Administration (R284). System Error Log Changes ************************* Beginning in VOS Release 14.4.0, improvements to the disk commands include additional output to the system error log. You can use this output to identify which administration commands were executed on a system and who executed them. The add_disk, cancel_disk_retry, and delete_disk commands generate the corresponding new messages to the system error log if the command is successful. Note that the messages appear after the existing output. user_name: add_disk: added disk disk_name. SRB: VOS Release 14.5.0 (R914) 2-24 Examples user_name: cancel_disk_retry: retry cancelled for all disks. user_name: cancel_disk_retry: retry_cancelled for disk disk_name. user_name: delete_disk: deleted disk disk_name. The dismount_disk, format_disk, and mount_disk commands generate the corresponding messages to the system error log. Note that the new messages appear before the original command output. user_name: dismount_disk: called for disk disk_name. user_name: format_disk: called for disk disk_name. user_name: mount_disk: called for all disks. user_name: mount_disk: called for disk disk_name. The following commands append the user's name to the beginning of each message in the system error log. o add_paging_file o cancel_fast_disk_recovery o remove_disk o remove_tape o select_duplex_disk o setup_disk o setup_tape For example, the add_paging_file command generates the following message to the system error log. user_name: Adding paging file file_name, N blocks. The update_disk_label command generates the following new message to the system error log. user_name: update_disk_label: updated label on disk disk_name. SRB: VOS Release 14.5.0 (R914) 2-25 Changes to start_disk_recovery ******************************* Examples The start_disk_recovery command supports the -memory_pool argument, which tells the disk recovery processes which CPU memory pool to use (that is, it associates the disk recovery processes with a specific CPU memory pool). For more information about this argument, see the manual VOS System Administration: Disk and Tape Administration (R284). Changes to update_disk_label ***************************** Beginning in VOS Release 14.1.0, the update_disk_label command has four new arguments: -skip_unreferenced_disk_cache, -skip_paged_kernel, - skip_paged_process, and -skip_kernel_maps. Using these new arguments can result in a smaller system dump and faster creation of the dump. The display_disk_label command has been updated to show the value of each of the new arguments. The increasing size of physical memory configurations has a direct effect on the system dump process. In previous releases, the dump process included the entire state of the system. With limited disk resources to hold this state and with application downtime a growing concern, it is important to streamline the dump process. Certain regions of a typical system dump can be excluded without compromising its integrity. The new arguments provide ways to trim these regions so the dumped information can fit into existing dump partitions, and downtime is decreased. Although the dump partition maximum size has been expanded from 16,320 blocks to 262,140 blocks, some master disks may not have enough free space to assign to a larger dump partition. In these cases, the new arguments provide an opportunity to trim dumps to fit into the available space. In most cases, no loss of dump integrity occurs; in other cases, vital information may be lost. These arguments are therefore intended for use on systems where time or space considerations are crucial. The update_disk_label command can be used to set these flags. Stratus recommends that the flags be set as follows: -skip_unreferenced_cache_pages: YES -skip_paged_kernel: NO -skip_paged_process: NO -skip_kernel_maps: NO The four new arguments to the update_disk_label command are explained as follows. Each argument takes the value no as the default. Note: The benefits and risks for using these arguments are described in these explanations. SRB: VOS Release 14.5.0 (R914) 2-26 Examples -skip_unreferenced_disk_cache If the argument is set to the value yes, both the Primitive Control Program (PCP) and memory dump processes will skip unreferenced cache manager pages. If the -quick_dump argument is set to the value yes, these pages are skipped by the PCP dump process regardless of the value of this argument. Benefit: The VOS cache manager is probably the single largest system memory client. The number of client buffer pages that are in use at any given time is only about 5% to 10% of the total that was allocated by the cache manager. On small physical memory configurations, the number of pages affected by this argument will typically be more than the number of paged kernel or kernel map blocks; on large configurations, this is even more the case. Risk: The unreferenced cache manager pages are mostly uninteresting in the context of a dump because at the moment the dump was taken, these pages would have been inactive. The possibility that useful or even crucial information could be contained in a page that had just been marked inactive prior to taking the dump cannot be ruled out, however. Overall, this argument carries the least risk of the four arguments. -skip_paged_kernel If the argument is set to the value yes, the PCP dump process will skip kernel data pages not resident in memory. Benefit: Currently, the paged area of the VOS kernel accounts for roughly the same as the kernel maps but, on most systems, much less than the number of either the paged process or unreferenced disk cache blocks. Risk: The paged kernel area, in large part, consists of various utility functions and the paged heap. Like the unreferenced disk cache blocks, the pages affected by this argument would be inactive at the moment a dump was taken. Again, the possibility that useful or even crucial information could be contained in a block that had been paged cannot be ruled out. In addition, examination of the dump's paged heap data will likely be affected. For these reasons, the omission of these pages carries slightly more risk than the unreferenced disk cache blocks. -skip_paged_process If the argument is set to the value yes, the PCP dump process will SRB: VOS Release 14.5.0 (R914) 2-27 Examples skip process data pages not resident in memory. This argument is ignored for running processes. Benefit: On most systems, the number of processes is large enough so that the amount of paged process blocks is greater than the number of blocks associated with any of the other arguments. Risk: Although this argument would not affect the paged data of any running process, the likelihood that information that is useful or even crucial to determining the root cause of a system interruption is greater than that associated with the other three arguments. This is the case based simply on statistics: more actors and more absent pages mean more risk. -skip_kernel_maps If the argument is set to the value yes, both the PCP and memory dump processes will skip data pages in the map_page_list$ structure. If the -quick_dump argument is set to the value yes, these pages are skipped by the PCP dump process regardless of the value of this argument. Benefit: This argument concerns the physical pages in which the memory map entries (MMEs) are stored. The number of pages that are affected is directly proportional to the physical memory in the system. The theoretical maximum is 2 MME pages per 1 MB of physical pages (on Continuum modules, multipage mappings are used for much of the VOS kernel pages, so fewer MMEs and therefore fewer MME pages are required). Risk: The main drawback to using this request is that the MME information is crucial to resolving a set of possible mapping problems. For example, if one or more map entries contained an incorrect state (or had been corrupted), it would be nearly impossible to confirm the problem without these pages in the dump. The likelihood of such problems is small, but when you consider the worst-case scenario, the associated risk is more than that for either the unreferenced disk cache or paged kernel blocks. For more information about the update_disk_label command, see the manual VOS System Administration: Disk and Tape Administration (R284). Changes to Disk-Related analyze_system Requests ----------------------------------------------- This section describes the following topics. SRB: VOS Release 14.5.0 (R914) 2-28 Examples o ``Changes to the dump_disk_info Request' o ``Changes to the disk_meters Request" Changes to the dump_disk_info Request ************************************* Beginning in VOS Release 14.4.0, the dump_disk_info request of the analyze_system command has four new output fields. The new fields are as follows: o The cscan limit field displays the number of sequential requests after which the to_do queue is reordered, if there are any nonsequential requests that might experience excessive latency. o The msgs since transition field displays the current number of sequential requests that have been dequeued since the transition point on the to_do queue was last reached. This number must exceed cscan_limit before the to_do queue can be reordered. o The to_do reorders field displays the number of times the to_do queue was reordered to prevent excessive latency. o The max msgs since transition field displays the maximum value of the msgs since transition field. Changes to the disk_meters Request ********************************** Beginning in VOS Release 14.5.0, the disk_meters request of the analyze_system command has a new argument, -wrap, and the format of the output has changed. If you specify this argument, output lines that exceed 80 characters wrap to the next line instead of being truncated to fit on a single line. This argument affects brief metering output only, however. By default, the disk_meters request does not wrap lines. For more information about the disk_meters request, see the updates and errata file to the VOS System Analysis Manual (R073). Updates and errata files are located in the directory >system>doc>vos_pubs_corrections. Stratus customers with a current support contract can access them on the VOS StrataDOC Web site at http://stratadoc.stratus.com. New Disk-Related analyze_system Requests ---------------------------------------- This section describes the following topics. SRB: VOS Release 14.5.0 (R914) 2-29 Examples o ``The list_disk_params Request" o ``The set_disk_param Request" The list_disk_params Request ***************************** The list_disk_params request has been added to the analyze_system command. This request displays the value of a specified debugging or tuning parameter or the values of all debugging and tuning parameters related to the disk I/O subsystem. For more information about the list_disk_params request, see the updates and errata file to the VOS System Analysis Manual (R073). Updates and errata files are located in the directory >system>doc>vos_pubs_corrections. Stratus customers with a current support contract can access them on the VOS StrataDOC Web site at http://stratadoc.stratus.com. The set_disk_param Request *************************** The set_disk_param request has been added to the analyze_system command. This request modifies the values of a debugging or tuning parameter related to the disk I/O subsystem. For more information about the set_disk_param request, see the updates and errata file to the VOS System Analysis Manual (R073). Updates and errata files are located in the directory >system>doc>vos_pubs_corrections. Stratus customers with a current support contract can access them on the VOS StrataDOC Web site at http://stratadoc.stratus.com. Open Disk Support ----------------- Beginning in VOS Release 14.3.0, any user on a PA-RISC system can add disk drives with new capacities or with like capacity drives automatically without requiring a kernel update or the execution of an external command. Streamlining Disk Renames ------------------------- Beginning in VOS Release 14.2.2, the disk salvager allows for quick SRB: VOS Release 14.5.0 (R914) 2-30 Examples renaming of duplexed disks. When a duplexed disk volume is renamed, the salvager determines if the disk volume qualifies for a quick rename, and if so, you can mount the disk without performing a full salvage and recovery. For example, to rename a multi-member volume called m1_d01 to m1_d05, you would perform the following steps. 1. Update the disk label using the following command. update_disk_label m1_d01 -new_disk_name m1_d05 2. Dismount m1_d01. 3. Set up the physical disks that make up the volume, and invoke the salvager with the following command. salvage_disk m1_d01 At this point, you could expect to see the following types of messages in the system error log. 13:03:08 check_for_rename: attempting to rename m1_d01 to m1_d05. 13:03:08 Renaming disk pack m1_d01.0-3.pri to m1_d05.0-3.pri. 13:03:08 Renaming disk pack m1_d01.0-3.sec to m1_d05.0-3.sec. 13:03:08 Renaming disk pack m1_d01.1-3.pri to m1_d05.1-3.pri. 13:03:09 Renaming disk pack m1_d01.1-3.sec to m1_d05.1-3.sec. 13:03:09 Renaming disk pack m1_d01.2-3.pri to m1_d05.2-3.pri. 13:03:09 Renaming disk pack m1_d01.2-3.sec to m1_d05.2-3.sec. 4. Back up the physical disks that make up the volume, and invoke the salvager with the following command. salvage_disk m1_d01 At this point, you could expect to see the following types of messages in the system error log. 13:03:08 check_for_rename: attempting to rename m1_d01 to m1_d05. 13:03:08 Renaming disk pack m1_d01.0-3.pri to m1_d05.0-3.pri. SRB: VOS Release 14.5.0 (R914) 2-31 Examples 13:03:08 Renaming disk pack m1_d01.0-3.sec to m1_d05.0-3.sec. 13:03:08 Renaming disk pack m1_d01.1-3.pri to m1_d05.1-3.pri. 13:03:09 Renaming disk pack m1_d01.1-3.sec to m1_d05.1-3.sec. 13:03:09 Renaming disk pack m1_d01.2-3.pri to m1_d05.2-3.pri. 13:03:09 Renaming disk pack m1_d01.2-3.sec to m1_d05.2-3.sec. 13:03:10 Jane.SysAdmin: Starting quick rename operation for %m1_d05. 13:03:10 Jane.SysAdmin: Quick rename complete. Disk %#m1_d05 can + now be mounted. After a quick rename, you can mount the disk, at which time the volume is fully duplexed (for example, no disk recovery occurs). Without the quick rename functionality, the volume would be fully salvaged and recovered. If the quick rename is successful, no disk recovery occurs, and you can mount the disk. If the quick rename fails, the disk salvager sends a message to the console, notifying you to resalvage the disk. New Disk Salvaging Behavior --------------------------- Beginning in VOS Release 14.1.0, you can use the new control variable, sys_info$max_salvage_proc_act, to the salvage_disk request in the analyze_system command to restrict the number of simultaneous salvaging processes. This feature is useful in situations where you cannot increase the page partition on the boot disk and you cannot boot without increasing the paging partition. This control variable disables the parallel disk-salvaging process, thus allowing you to salvage in serial, which prevents the boot disk from running out of paging partitions. The default setting for sys_info$max_salvage_proc_act is a multiple of sys_info$salvage_proc_per_cpu (default is 5) times sys_info$num_cpus_configured. Tape-Related Changes -------------------- This section discusses the following topics related to changes in tape devices. SRB: VOS Release 14.5.0 (R914) 2-32 Tape-Related Changes o ``Default Expiration Date Change" o ``Tape Subsystem Changes" o ``New Tape Commands" o ``Changed Tape Commands" Default Expiration Date Change ------------------------------ Beginning in VOS Release 14.0.0, ANSI and IBM label tapes have the default expiration date value of none (" 00000"--note the leading space). Prior to VOS Releases 12.3.0 and 14.0.0, ANSI and IBM label tapes may have had the default expiration date value of December 31, 1999 (" 99365"--again, note the leading space) unless you explicitly specified an expiration date using the command set_tape_file_parameters or the s$control subroutine's opcode TAPE_SET_FILE_PARAMS_OPCODE (147). For more information about the set_tape_file_parameters command, see the VOS Commands Reference Manual (R098). For more information about the s$control subroutine, see the VOS Subroutines manuals. Tape Subsystem Changes ---------------------- Continuum-series modules implement a tape subsystem that supports the following SCSI tape devices. o T204 tape drive (1600/6250 bits per inch (bpi))--This tape drive is available in table-top and rack-mounted versions. o T403 3490 tape drive (200-400 MB/cartridge)--This tape drive is available in table-top and rack-mounted versions. o T701 DDS-2 Digital Audio Tape (DAT) Drive (4-8 GB) o T702 DDS-2 DAT Drive and Autoloader (24-48 GB) o T703 Quarter-Inch Cartridge (QIC) Tape Drive (525 MB) o T705 DDS-3 DAT Drive (24 GB) o T706 DDS-3 DAT Drive (144 GB) The tape subsystem supports tape drives that are contained in a D700-00X SRB: VOS Release 14.5.0 (R914) 2-33 Tape-Related Changes disk/tape enclosure or stand-alone tape drives that are connected to a D700 subsystem. The following sections provide additional information about tape subsystem changes in VOS Release 14.0.0. o ``The T705 and T706 Tape Drives" o ``Booting from Tape" The T705 and T706 Tape Drives ***************************** Beginning in VOS Release 14.0.0, Stratus offers the following new tape drives on Continuum-series modules. o ``The T705 DDS-3 DAT Tape Drive" o ``The T706 DDS-3 DAT Tape Drive with Autoloader" The preceding tape drives connect to the D700 subsystem on Continuum- series modules through the K450 I/O controller or the K460 Differential SCSI/Ethernet High-Speed I/O Controller. The T705 DDS-3 DAT Tape Drive ****************************** The T705 DDS-3 DAT tape drive is a single-cartridge tape drive that replaces the T701 DAT tape drive and is fully read-compatible with older products. Its capacity is 24 GB, and it supports hardware data compression using the Data Compression Lempel-Ziv (DCLZ) compression algorithm to increase both capacity and transfer rate. Like all DDS-3 tape drives, it accepts DDS-1 (60 meter and 90 meter), DDS-2, and DDS-3 cartridges. It supports a data density of 122,000 bpi. The T706 DDS-3 DAT Tape Drive with Autoloader ********************************************** The T706 DDS-3 DAT tape drive with autoloader replaces the T702 DAT tape drive and is fully read-compatible with older products. It has a 144-GB capacity and (like the T705 tape drive) supports hardware data compression using the DCLZ compression algorithm to increase both capacity and transfer rate. Like all DDS-3 tape drives, it accepts DDS-1 (60 meter and 90 meter), DDS-2, and DDS-3 cartridges. The tape drive supports a data density of 122,000 bpi. The autoloader has a SCSI-2 interface and combines a six-cartridge changer SRB: VOS Release 14.5.0 (R914) 2-34 Tape-Related Changes mechanism with a DDS-3 tape drive. The autoloader houses up to six DDS cartridges in a removable magazine, enabling you to back up 144 GB of data in a single magazine of six DDS-3 (125 meter) cartridges, assuming a compression ratio of 2:1. The autoloader supports both sequential and random access modes. Booting from Tape ***************** You can use a DAT tape in a T705 or T706 tape drive to boot a Continuum- series module from tape (either autoloaded or manually loaded). New Tape Commands ----------------- The following tape-related commands are new or newly documented for VOS Release 14.0.0 and later. o read_tape_encrypted--This command reads encrypted tape files and decrypts them using routines that you supply. The command then places the resulting files into your current directory. For complete information about this command, see the manual VOS System Administration: Disk and Tape Administration (R284). o view_release_tape_log--This command displays the log of installations on a module. For complete information about this command, see the VOS Installation Guide (R386). o write_tape_encrypted--This command optionally encrypts one or more files and writes them to the tape volume on the specified tape drive or on the tape drive connected to the specified port. For complete information about this command, see the manual VOS System Administration: Disk and Tape Administration (R284). Changed Tape Commands --------------------- Beginning in VOS Release 14.2.0, the read_tape command has a new argument, -multi_reel, which specifies that read_tape reads files that span tape volumes, and that the volume_id differs between succeeding reels. The read_tape command provides the additional support needed to handle this special situation. If all reels have the same value for the volume_id field, this argument is not needed for read_tape to process the tapes correctly. SRB: VOS Release 14.5.0 (R914) 2-35 Tape-Related Changes The V105 Terminal and Other Terminal Support Issues ---------------------------------------------------- Beginning in VOS Release 14.0.0, Stratus offers the V105 terminal for Continuum-series modules. The V105 terminal is a new asynchronous video- display terminal that replaces the V103 terminal. The V105 terminal supports two types of keyboards: the ANSI keyboard and the 106-key personal computer (PC/+ 106) keyboard. o The ANSI keyboard is similar to Digital Equipment Corporation's VT220 terminal keyboard v105_ansi. o The PC/+106 keyboard is similar to an IBM-compatible personal computer keyboard v105. The V105 terminal allows you to choose 24 or 42 display lines with 80 or 132 characters per line. VOS supports one terminal emulation for the V105 terminal: Digital Equipment Corporation's VT300. To use the V105 terminal, you must create an entry for it in the devices.tin file. This entry must contain all of the appropriate fields, including the terminal_type field with the value v105 or v105_ansi. For information about creating the devices.tin file entry for the V105 terminal, see the Product Release Bulletin: VOS Configuration for the V105 Terminal (R439). For more information about the V105 terminal, see the Stratus V105 Terminal User's Guide (R598-0011583). Beginning in Release 14.0.0, VOS provides enhanced support for some other terminals. See the file terminal_support.doc in the directory >system>doc for information on the following topics. o new .ttp definition files and setups o Office/2000 and terminal support o changes to the commands display and display_file o the TTP include file emacs.incl.ttp o predefined TTPs for v105 and v105_ansi o TTP file changes Miscellaneous Changes to the analyze_system Command --------------------------------------------------- This section describes the following topics. SRB: VOS Release 14.5.0 (R914) 2-36 Miscellaneous Changes to the analyze_system Command o ``The analyze_system Command Argument -c_expressions" o ``Expanded dump_vm_pool_info Display" o ``New dump_sdlmux Request" o ``New dump_dlmux_info Request" The analyze_system Command Argument -c_expressions --------------------------------------------------- The analyze_system command argument -c_expressions specifies that internal expressions are evaluated using a C language line parser instead of the traditional analyze_system line parser. The C language line parser implements a subset of the keywords and commands supported by the traditional analyze_system line parser. For information about expression evaluation, see the VOS System Analysis Manual (R073). Expanded dump_vm_pool_info Display ---------------------------------- The analyze_system request dump_vm_pool_info has new arguments that provide an expanded display. The dump_vm_pool_info request displays information about the virtual memory pool on the analyzed module. Beginning in VOS Release 14.0.0, the request has the following new arguments. o -by_tree--The value yes specifies that the output displays blocks (free or used) that are found on the binary tree structures supporting the virtual memory pool. Note that not all used blocks in the system can be seen on the used tree; in other words, when you specify the arguments -no_dump_free and -by_tree, not all used blocks are displayed. The value no (the default) displays only the block list. o -descending--The value yes specifies that the blocks in the pool are displayed in descending order. The value no (the default) specifies that the blocks in the pool are displayed in ascending order. o -header--The value yes formats the vm_pool header structure for the user. The value no (the default) specifies that the header is not displayed. o -show_links--The value yes specifies that the output shows the locations in the individual structures that point to neighboring structures, which makes the output similar to that of a true dump SRB: VOS Release 14.5.0 (R914) 2-37 Miscellaneous Changes to the analyze_system Command command. The value no (the default) does not show the link values. For complete information about the dump_vm_pool_info request, see the file as.doc in the >system>doc directory. New dump_sdlmux Request ----------------------- Beginning in VOS Release 14.1.0, the dump_sdlmux request has been added to the analyze_system command. The dump_sdlmux request displays information about the structures associated with an SDLMUX group that has been initialized. It displays the names of the two network interface cards in one (initialized) SDLMUX group. For more information about the dump_sdlmux request, see the updates and errata file to the VOS System Analysis Manual (R073). Updates and errata files are located in the directory >system>doc>vos_pubs_corrections. Stratus customers with a current support contract can access them on the VOS StrataDOC Web site at http://stratadoc.stratus.com. New dump_dlmux_info Request --------------------------- Beginning in VOS Release 14.0.0 (but newly documented for VOS Release 14.5.0), the dump_dlmux_info request has been added to the analyze_system command. This request displays information from the DLMUX control structures, including the state of each adapter in a DLMUX partnership. For more information about the dump_dlmux_info request, see the updates and errata file to the VOS System Analysis Manual (R073). Updates and errata files are located in the directory >system>doc>vos_pubs_corrections. Stratus customers with a current support contract can access them on the VOS StrataDOC Web site at http://stratadoc.stratus.com. The VOS Dead-CPU Time-Out Value ------------------------------- Beginning in VOS Release 14.0.0, when VOS checks for a dead CPU, the time- out value (that is, the dead-CPU time-out value) is one minute; previously, the value was three minutes. The dead-CPU time-out value determines the maximum amount of real time for which a CPU may process instructions without rescheduling. VOS uses the dead-CPU time-out value to detect a dead (or nonresponsive) CPU, as the name indicates. The value was lowered in order to improve system availability following a system failure SRB: VOS Release 14.5.0 (R914) 2-38 The VOS Dead-CPU Time-Out Value that results in a dead-CPU trap. If you have any questions about this change, contact the CAC. Freezing and Thawing Processes ------------------------------ Beginning in VOS Release 14.0.0, you can freeze a process and later thaw it. When you freeze a process, you suspend it. The process remains on the system, but it will never be scheduled to run on a CPU. When you thaw the process, it can be run. To freeze a process, you issue the command freeze_process. To thaw a process, you issue the command thaw_process. Freezing a process may eliminate the need for a dump. You can, for example, freeze a runaway process, and analyze it while the process is suspended in the system rather than dumping information for an analysis. You can determine that a process is frozen by issuing the list_users command. Beginning in VOS Release 14.0.0, the output of the list_users command includes the process state FZ, which indicates that the user process is frozen. The summary request of analyze_system also identifies frozen processes. For more information about the commands freeze_process and thaw_process, see the manual VOS System Administration: Administering and Customizing a System (R281). Terminating Dumps Prematurely ----------------------------- Beginning in VOS Release 14.0.0, you can terminate a system dump while it is in progress. (A system dump occurs when the module crashes and creates a dump in the dump partition.) You might want to prematurely terminate a system dump that requires a large amount of time to complete due to either a large number of processes running or a large memory configuration. When you terminate a dump, it can shorten the amount of time required to obtain meaningful information and to subsequently start rebooting the module. A prematurely terminated dump contains information critical for dump analysis. The use_dump request of the analyze_system command reports that a dump was prematurely terminated or aborted. Note: Terminating a dump prematurely may affect the CAC root-cause analysis of the dump. On a Continuum-series module, you can terminate a dump by issuing the restart_cpu command from the system console front panel at any time after SRB: VOS Release 14.5.0 (R914) 2-39 Terminating Dumps Prematurely the dump has started. For information about the system console front panel, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). After dumping critical information (completing steps 1 through 6 in the following procedure), the dump code determines if the restart_cpu command or RESTART message was issued. If the dump code detects that either the command or message was issued, it terminates the dumping process, marks the dump as aborted, and reboots the module (if you have specified the - auto_boot argument of the update_disk_label command) or returns to command level (if you have specified the -no_auto_boot argument of the update_disk_label command). (For information about this command, see the manual VOS System Administration: Disk and Tape Administration (R284).) A system dump occurs in the following sequence. This sequence enables VOS to dump the most important data first. VOS can terminate the dump during this sequence, as noted below. 1. A dump of the I/O controller that controls the boot device (if it exists) to memory and resets the board. (The I/O controller is also known as the BIO or HSC board.) 2. A dump of software critical pages (for example, syserr buffers and toehold data). 3. A dump of hardware pages. 4. A dump of virtual memory map pages. 5. A dump of kernel data space (not including pages in the disk cache). 6. A dump of stacks and kernel pages of the running processes. The dump can be aborted at this point. 7. A dump of stacks and kernel pages of the remaining processes. The dump can be aborted after dumping each process. 8. A dump of referenced cache manager pages. The dump can be aborted while dumping these pages. 9. A dump of the I/O processors and controllers. The dump can be aborted after dumping each I/O processor or controller. 10. A dump of the I/O adapters. The dump can be aborted after dumping each I/O adapter. 11. A dump of the nonboot I/O controllers. The dump can be aborted after dumping each I/O controller. SRB: VOS Release 14.5.0 (R914) 2-40 Terminating Dumps Prematurely 12. A dump of all pages of running processes. The dump can be aborted after dumping the running process. 13. A dump of the Overseer. The dump can be aborted at this point. 14. A dump of unreferenced cache manager pages. The dump can be aborted while dumping these pages. 15. At this point, the dump is complete. When you terminate the dump prematurely, the following message appears in the list of dump messages. Dump creation was deliberately aborted. The following example illustrates the messages that you may receive during a dump that you prematurely terminate. (Note that in this example, three consecutive vertical dots represent omitted output.) Dumping BIO board in slot 10 to memory Dumping BIO in slot 10 to memory. pbc 0A010101 thaw complete pbc 0A010101 tur complete pbc 0A010101 wide mode pbc 0A010101 sync mode pbc 0A020101 thaw complete pbc 0A020101 tur complete pbc 0A020101 wide mode pbc 0A020101 sync mode Dumping kernel. . . . Dumping.... [ 6000 pages dumped ] SRB: VOS Release 14.5.0 (R914) 2-41 Terminating Dumps Prematurely Dumping process, ptep C188B600, Overseer.System Dumping process, ptep C1195400, Cache_Manager_Post.System Dumping process, ptep C1193040, Cache_Manager_Timer.System Dumping process, ptep C10B58C0, Cache_Manager_Locker.System Dumping process, ptep C17F06C0, Paging_Daemon.System Dumping process, ptep C17F1380, Kernel_Utility.System Dumping process, ptep C17F2000, Maintenance_Utility.System Dumping process, ptep C17F5340, Diagnostic_Utility.System Dumping process, ptep C17F66C0, Diagnostic_Utility.System Dumping process, ptep C1842700, Overseer.System [sending break] restart_cpu Repeat command to confirm: restart_cpu Processor HALT&RESTART signal sent. Panel goes to sleep... Dumping process, ptep C1844740, Overseer.System Dumping process, ptep C182D540, Install.SysAdmin Dumping process, ptep C1881040, Overseer.System Dump creation was deliberately aborted. Dump incomplete, 6434 pages(2730 compressed pages). Proceed with caution - BIO memory dump may have overwritten non-PCP code pages. Re-entering PROM for reboot. Tuning the File System Cache Manager ------------------------------------ SRB: VOS Release 14.5.0 (R914) 2-42 Tuning the File System Cache Manager Beginning in VOS Release 14.2.2, the cache manager system has a number of new tuning arguments for the set_tuning_parameters command. For information about these new arguments, see ``New Cache-Related Tuning Arguments" in Chapter 6. Also, the file cache_tuning.doc in the directory >system>doc describes recent changes to the cache manager and how you can improve performance by tuning the cache. The information in the file supplements the description of the set_tuning_parameters command in the manual VOS System Administration: Administering and Customizing a System (R281). Device and Firmware Configuration Summary ----------------------------------------- This section summarizes the device and firmware configuration change that this chapter describes. For more information about how to configure devices and firmware, see the manual VOS System Administration: Configuring a System (R287). To enable VOS to recognize a V105 terminal that is connected to an asynchronous port, you must create an entry for it in the devices.tin file. This entry must contain all of the appropriate fields, including the terminal_type field with the value v105 or v105_ansi. For information about creating the devices.tin file entry for the V105 terminal, see the Product Release Bulletin: VOS Configuration for the V105 Terminal (R439). For more information about the V105 terminal, see the Stratus V105 Terminal User's Guide (R598-0011583). If your system includes the Data-Link Multiplexer (DLMUX) and/or the STREAMS Data-Link Multiplexer (SDLMUX), you need to configure DLMUX and/or SDLMUX devices. For information about DLMUX and SDLMUX, see ``The Data- Link Multiplexer: SDLMUX and DLMUX'' in Chapter 5. For detailed information about configuring DLMUX and SDLMUX devices, see the manuals listed in Table 5-4 and Table 5-5. If your system includes STREAMS TCP/IP (STCP), you need to configure STCP devices. For information about STCP, see ``Overview of STCP'' in Chapter 5. For detailed information about configuring STCP devices, see the VOS STREAMS TCP/IP Administrator's Guide (R419). Changes to General User Commands -------------------------------- This section describes changes to the following general user commands. o ``Changes to the compare_files Command" o ``Changes to the network_watchdog Command" SRB: VOS Release 14.5.0 (R914) 2-43 Changes to General User Commands o ``Changes to the save Command" o ``Changes to the start_logging Command" o ``Changes to the start_process and batch Commands" o ``Change to the who_locked Command" Changes to the compare_files Command ------------------------------------ Beginning in VOS Release 14.5.0, the -difference_count argument of the compare_files command now allows the value zero. This value lets the user print the number of differences when comparing files if that is the only information that is needed. For more information about the compare_files command, see the VOS Commands User's Guide (R089). Changes to the network_watchdog Command --------------------------------------- Beginning in VOS Release 14.5.0, the network_watchdog command has the following changes. o The num_minutes argument, which specifies the time interval, in minutes, between successive network-watchdog cleanup operations, has a new default value of 1. o A new argument, num_seconds, allows you to fine-tune your network. The default value is 0 seconds. If you specify a value of 0 for num_minutes, the command accepts the value specified in num_seconds. If you specify a nonzero value for num_minutes, the command ignores the num_seconds argument. The new command-line form for network_watchdog follows. network_watchdog [num_minutes [num_seconds]] [-syserr] For more information about the network_watchdog command, see the manual VOS System Administration: Administering and Customizing a System (R281). SRB: VOS Release 14.5.0 (R914) 2-44 Changes to General User Commands Changes to the save Command --------------------------- Beginning in VOS Release 14.4.0, the save command has two arguments that determine how blocks in files or indexes are read into cache. The arguments are: o -preread_lead N Where N is the number of blocks to read into cache when first opening a file or index. The minimum is 0. The default is 32. o -preread_size N Where N is the number of blocks read into cache in a group when reading an index or file. The minimum is 1. The default is 8. The optimal values for -preread_lead and -preread_size are system, configuration, and load dependent. You may need to experiment to find the best values for your system. Specify save -preread_lead 0 -preread_size 1 to do as little prereading as possible. This may be beneficial if you are saving to or from a busy disk. For more information about the save command, see the VOS Commands Reference Manual (R098). Changes to the start_logging Command ------------------------------------ Beginning in VOS Release 14.4.0, the start_logging command has two new arguments: -timestamp_beginning and -timestamp_ending. To log the time that an operation begins, specify -timestamp_beginning. To log the time that an operation ends, specify -timestamp_ending. Previously, the log files displayed the order in which specific actions took place. Now, you can use the timestamps in the log files to look at corresponding parts of the system error log file or application logs to correlate specific actions and return codes in the logging file with the time they occurred. By default, the command does not use timestamps. For more information about the start_logging command, see the VOS Commands Reference Manual (R098). Changes to the start_process and batch Commands ----------------------------------------------- Beginning in VOS Release 14.5.0, if you do not specify the -output_path SRB: VOS Release 14.5.0 (R914) 2-45 Changes to General User Commands argument, the start_process and batch commands use the command name to derive the name of the output file. Previously, the command derived the name of the output file from the first name of command_line. For example, the following command generates an output file named sleep.out. Previously, the output file was named system.out. batch `%system#module>system>command_libray>sleep -seconds 10' For more information about the start_process and batch commands, see the VOS Commands Reference Manual (R098). Change to the who_locked Command -------------------------------- Beginning in VOS Release 14.5.0, the who_locked command has the following new argument. -brief If the argument is set to the value yes, the command does not display unlocked files. The default value is no. For more information about the who_locked command, see the VOS Commands Reference Manual (R098). Changes to Security-Related Commands ------------------------------------ This section describes changes to the following security-related commands. o ``Changes to the set_registration_info Command" o ``Changes to the registration_admin Command" Changes to the set_registration_info Command --------------------------------------------- Beginning in VOS Release 14.1.0, the set_registration_info command has a new argument, -force_change which requires users to change their passwords the next time they log in. The default value for the -force_change argument is no. Setting this argument to yes allows the system administrator to force any user to change their password. The system forces this change regardless of when the user's password was changed or whether it was changed by the user SRB: VOS Release 14.5.0 (R914) 2-46 Changes to Security-Related Commands or the system administrator. The system administrator can issue a new password at the same time, forcing the user to change passwords, or can force the user to change the password the next time the user logs in. Note that forcing a user to change the password the next time the user logs in is applicable only when security checking is turned on for the module via the set_password_security command's -req_change_first_login argument being set to yes. For additional information about the set_registration_info and set_password_security commands, see the manual VOS System Administration: Registration and Security (R283). Changes to the registration_admin Command ------------------------------------------ Beginning in VOS Release 14.1.0, the registration_admin command now allows the system administrator to change a user's password when the - forbid_frequent_changes argument is set to yes in the set_password_security command. The system administrator is now able to issue a new password whenever necessary. Note that bypassing -forbid_frequent_changes behavior in this way is applicable only when security checking is turned on for the module via the -forbid_frequent_changes argument being set to yes by the set_password_security command. For additional information about the registration_admin and set_password_security commands, see the manual VOS System Administration: Registration and Security (R283). Beginning in VOS Release 14.3.0, the action argument of the registration_admin command has two new values in support of VOS POSIX.1. A description of the new values follows. o add_posix_ids--This value adds user IDs and group IDs for all existing users in the VOS registration database. Various functions in POSIX.1 require that POSIX ID's names be present in the user registration database. Note: You should invoke the registration_admin command with the add_posix_ids value as soon as the post-boot phase of the installation has finished, even if you are not planning to run any POSIX applications. This is necessary because certain applications shipped with VOS are POSIX applications. o list_posix_ids--This value displays a list of all registered user names and group names along with the corresponding numeric user IDs and group IDs. Beginning in VOS Release 14.3.0, Stratus recommends that you add both root SRB: VOS Release 14.5.0 (R914) 2-47 Changes to Security-Related Commands and nobody as users, and add root and nobody as groups to the registration database. The user name root should be registered in the group root, and the user name nobody should be registered in the group nobody. This is necessary because some of the system processes may run as root, and some applications may require the presence of the user name nobody. Note, however, that the kernel disables login for both root and nobody. For more information, see the file >system>doc>posix>posix.doc. After numeric IDs have been added to the registration database, you should not use the pre-Release 14.3.0 version of the registration_admin command. If you do, some users and groups may not have user and group IDs assigned. If a system contains modules running on different releases but one of the modules is brought up with VOS Release 14.3.0, Stratus recommends that the system administrator broadcast the VOS Release 14.3.0 version of the registration_admin command to all modules to ensure that the VOS Release 14.3.0 version of registration_admin is used. Beginning in VOS Release 14.3.0, when you enter your password in the registration_admin command, you must enter your password a second time. Note that your password is not echoed back to you. For more information about the registration_admin command, see the manual VOS System Administration: Registration and Security (R283). Changes to System Administration Commands ----------------------------------------- This section describes changes to the following system administration commands. o ``Changes to the set_scheduler_info Command" o ``Changes to the test_index Command" o ``Changes to the dump_memory Command" Changes to the set_scheduler_info Command ----------------------------------------- Beginning in VOS Release 14.4.0, the value range of the -time argument of the set_scheduler_info command has changed. The value must be set between 2 and 4000 milliseconds. This change reflects the greater processor speed available with the current hardware. For more information about the set_scheduler_info command, see the manual VOS System Administration: Administering and Customizing a System (R281). SRB: VOS Release 14.5.0 (R914) 2-48 Changes to System Administration Commands Changes to the test_index Command --------------------------------- The use and look_at requests of the test_index command have a new argument: -update. If you specify this argument, test_index can repair many problems with a damaged index when you also specify the check -repair request. Index corruption occurs very rarely, usually as the result of a module outage or duplexed disk failure. Stratus recommends that you consult with the CAC before using the check -repair request. The updated display forms for the use and look_at requests follow. Display Form ------------------------------------------------------------------------ | ----------------------------------- look_at ---------------------- | | ------------ | | | | file: | | | | index: | | | | -update: no | ------------------------------------------------------------------------ Display Form ------------------------------------------------------------------------ | ------------------------------------- use ------------------------ | | ------------ | | | | file: | | | | index_name: | | | | -update: no | ------------------------------------------------------------------------ For more information about the test_index command, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). Changes to the dump_memory Command ---------------------------------- Beginning in VOS Release 14.2.0, the dump_memory command has a new SRB: VOS Release 14.5.0 (R914) 2-49 Changes to System Administration Commands argument, -process_type, which specifies the context in which the memory dump procedure is executed. -process_type process_type Specifies the context in which the memory dump procedure is executed. The permitted values are as follows: o background (default)--The memory dump procedure runs in the background as the Overseer.System(Memory_Dump). This is a useful feature during module_start_up, the dump_memory command's primary use. The main benefit of operating in background mode is that the system and application startup can begin without waiting for the memory dump procedure to complete. Therefore, the amount of application downtime is reduced. o delayed--The memory dump takes place in a separate process called Overseer.System(Memory_Dump), but does not start until the initialization process on module_start_up exits. The delayed value replaces the argument called -delay_test. If you previously used the -delay_test argument to the dump_memory command, you need to modify any calls to this command in which the argument was specified; this may include module_start_up.cm. o foreground--The memory dump takes place when the command is issued and control returns to the user when the memory dump procedure completes. For more information about the dump_memory command, see the manual VOS System Administration: Configuring a System (R287). Changes to the Manual Boot Procedure ------------------------------------ Beginning in VOS Release 14.3.0, you can configure a tape during a manual boot, as follows: 1. During the manual boot procedure, after the message Enter PCP for manual repair? appears, the following new message appears. Configure BOOT TAPE for restore from tape? If you do not wish to restore from a boot tape, type n, and proceed as usual. Otherwise, type y. 2. The screen displays the following messages. Enter Device ID in the form 00/00/00/00 SRB: VOS Release 14.5.0 (R914) 2-50 Changes to the Manual Boot Procedure Enter full device ID for tape: Type the ID for your tape device (for example, 4/1/1/6). 3. Verify the device ID by typing y to continue with the manual boot procedure. (If you type n, the question displayed in step 1 is repeated.) Use 4/1/1/6 for ID? y The device you configured is called %ss#tape.mm.0, where ss is the system name, and mm is the module number. Once you are at the ready prompt, issue the list_devices -type tape command to display the tape device name. For more information about the manual boot procedure, see the manual VOS System Administration: Disk and Tape Administration (R284). Change to Home Directory During Automatic Startup ------------------------------------------------- In releases prior to VOS Release 14.3.0, the home directory of the initialization process was set to (master_disk)>Overseer during manual startup and to (master_disk) during automatic startup. Beginning in VOS Release 14.3.0, the home directory of the initialization process is set to (master_disk)>Overseer during both manual and automatic startup. If your module_start_up.cm command macro depends on the old behavior, you must modify your file. Note that the current directory of the initialization process is set to (master_disk)>Overseer during both manual and automatic startup. This is not a change in behavior but rather a clarification. For more information about manual and automatic startup, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). Change to the devices.tin File ------------------------------ Beginning in VOS Release 14.4.0, the devices.tin file has a new argument, local_dialup. A description of the argument follows. local_dialup Specifies that a dialup device be treated as a direct connect device, as far as inactivity time-outs are concerned. (Therefore, prelogin processes never time out.) The default value is 0. SRB: VOS Release 14.5.0 (R914) 2-51 Change to the devices.tin File For more information about the devices.tin file, see the manual VOS System Administration: Configuring a System (R287). Change to the languages.tin File -------------------------------- The languages.tin file has a new field, input_date_format. A description of the field follows. input_date_format Specifies the format of the input date. The string describes both the year/month/day sequence and the field delimiters. The following table describes the valid symbols that you can specify in the format. ------------------------------------------------------------------------ | Symbols : Description | |----------------------------------------------------------------------| | Year symbols : YYYY or yyyy represents four-digit years; | | : YY or yy represents two-digit years | |----------------------------------------------------------------------| | Month symbols : MM or mm | |----------------------------------------------------------------------| | Day symbols : DD or dd | |----------------------------------------------------------------------| | Delimiters : hyphen (-), slant (/), or period (.) | ------------------------------------------------------------------------ The input_date_format field specifies the format in which dates are input into the system. In contrast, the date_format field specifies the format of the date that is displayed. If you do not specify a value for the input_date_format field, the input and display formats both use the format specified in the date_format field. If the date_format field in your languages.tin file uses the dd-mm-yy format, you can use the input_date_format field to accept dates in the mm-dd-yy format. For example, assume that in your languages.tin file, the date_format field appears as follows: =date_format `dd-mm-yy' If you enter 2/1/1 (that is, January 2, 2001), your output will be: 02-01-01 00:00:00 edt If you want to accept the date January 2, 2001 in the format mm-dd- yy, the input_date_format field should appear as follows: =input_date_format `mm-dd-yy' SRB: VOS Release 14.5.0 (R914) 2-52 Change to the languages.tin File In this case, if you enter 1/2/1, the system will recognize your input as January 2, 2001. It will display as follows, however. 02-01-01 00:00:00 edt Before this field can take effect, you must regenerate the languages.table file with the create_file command, move the file to the directory (master_disk)>system, and run the configure_languages command. For more information about the languages.tin file, the create_table command, and the configure_languages command, see the manual VOS System Administration: Configuring a System (R287). For more information about how VOS interprets date-time strings, see the description of the s$cv_to_int_date_time subroutine in the VOS Subroutines manuals. SRB: VOS Release 14.5.0 (R914) Chapter 3: The VOS Operating System ======================== This chapter discusses changes to the VOS operating system. It contains the following sections. o ``Changes to the Cache Manager" o ``Changes to the VOS STREAMS Memory Allocator" o ``Creating Meter Files Using the analyze_system Command" o ``Logical Volumes and the Paging Partition of Nonboot Disks" o ``Pre-login Processes" o ``Process Management" o ``Increase in Ports per Process and Events per Module" o ``Setting and Displaying VOS STREAMS Parameters" o ``Time-Zone Changes" Changes to the Cache Manager ---------------------------- Beginning in VOS Release 14.2.2, the maximum number of cache-manager pages has increased to 2,441,406 (subject to available memory). For information about additional changes to the memory-resident and transient files, as well as instructions about how you can improve performance by tuning the cache, see ``Cache Manager Improvements'' in Chapter 6. Also, see the file cache_tuning.doc in the directory >system>doc. This file supplements the description of the set_tuning_parameters command in the manual VOS System Administration: Administering and Customizing a System (R281). Changes to the VOS STREAMS Memory Allocator ------------------------------------------- Beginning in VOS Release 14.1.0, STREAMS memory has been modified. The number of buckets has been reduced from 10 to 8. This helps reduce memory fragmentation and eliminates two bucket sizes (768 and 1344) that were not frequently used. SRB: VOS Release 14.5.0 (R914) 3-1 Changes to the VOS STREAMS Memory Allocator STREAMS can now preallocate memory from the kernel at bootload time. Memory preallocated at bootload time cannot be freed back to the system, but is held for the duration of the bootload by STREAMS. Normally, STREAMS is configured to not preallocate any memory from the system and to get the memory it needs upon demand. You can change this behavior through the analyze_system command by patching the variable sys_info$streams_prealloc. Patch the sys_info$streams_prealloc variable in the VOS partition by using the analyze_system use_partition request before the system is booted, or the patch will not take effect. This variable contains eight 2-byte (16-bit) integers that tell STREAMS the number of "chunks" of memory to preallocate for each of the buckets. The buckets are numbered 0 through 7. Bucket 0 is for STREAMS message headers; bucket 1 is for 64-byte messages; bucket 2 is for 128-byte messages; etc. You can use the analyze_system dump_stream -stm_msg request to determine what the chunk size is for each bucket and to determine what to set the sys_info$streams_prealloc variable to. The following output illustrates this. as: dump_stream -stm_msg stm_msg_mgmt= C0869600 stm_timeout_mgmt= C08697C0 stream_spin_infop$ = C0806B40 time_free.nextp = C150A740 time_pend.nextp = 00000001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information for Bucket 0 hq_size = 0 hq_alloc_incr = 511 hq_chunk_incr = 511 hq_multiplier = 4 hq_cache_incr = 32 SRB: VOS Release 14.5.0 (R914) 3-2 Changes to the VOS STREAMS Memory Allocator hq_pool[0]->total = 24575 hq_pool[0]->freemem[0]: stl_avail stl_first last_time 24575 C0EFFF80 never Information for Bucket 1 hq_size = 64 hq_alloc_incr = 383 hq_chunk_incr = 1344, 1% unusable hq_multiplier = 1 hq_cache_incr = 32 hq_cpu[0]->hq_stl.stl_first = C22A7080 hq_cpu[0]->hq_stl.stl_available = 32 hq_pool[0]->total = 5376 hq_pool[0]->freemem[1]: stl_avail stl_first last_time 5344 C22A7000 never . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information for Bucket 7 hq_size = 4096 hq_alloc_incr = 31 hq_chunk_incr = 62, 0% unusable hq_multiplier = 1 hq_cache_incr = 31 hq_pool[0]->total = 3472 hq_pool[0]->freemem[7]: stl_avail stl_first last_time SRB: VOS Release 14.5.0 (R914) 3-3 Changes to the VOS STREAMS Memory Allocator 3472 C5C6C800 never sys_info$streams_prealloc[0] = 48 (24528 msgs or 3139584 bytes) Currently pool 0 is at 48 (= 24575 msgs or 3145600 bytes) sys_info$streams_prealloc[1] = 4 (5376 msgs or 1032192 bytes) Currently pool 0 is at 4 (= 5376 msgs or 1032192 bytes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sys_info$streams_prealloc[7] = 56 (3472 msgs or 14665728 bytes) Currently pool 0 is at 56 (= 3472 msgs or 14665728 bytes) The hq_chunk_incr field is multiplied by the value you patch into the sys_info$streams_prealloc variable, and STREAMS will preallocate that number of messages. After printing out all of the STREAMS allocator information, the dump_stream -stm_msg request analyzes the current setting of the sys_info$streams_prealloc variable for you. STREAMS prints out the current value for each bucket and performs the multiplication, so you know how many messages each bucket holds. On the next line, STREAMS computes the value with which to patch sys_info$streams_prealloc to preallocate the amount of memory that is currently allocated. You can run dump_stream -stm_msg on your running system (under typical load), and STREAMS tells you how to set up the sys_info$streams_prealloc variable to preallocate that number of messages. You can adjust those numbers up or down to achieve whatever tuning goals you desire. On modules with PA-8000 family processors, the "best" values to put into sys_info$streams_prealloc are powers of 4 multiplied by a small constant. On the other architectures, it is irrelevant. Creating Meter Files Using the analyze_system Command ------------------------------------------------------ Beginning in VOS Release 14.0.0, the analyze_system command includes the following two requests. For more information about these requests, see the VOS System Analysis Manual (R073). o display_meter_file_info--This request displays information about the current meter file, including its path name. SRB: VOS Release 14.5.0 (R914) 3-4 Creating Meter Files Using the analyze_system Command o set_meter_file--This request allows you to specify the name of the meter file used to display and reset meters. Specifying the name of a meter file allows you to run multiple processes that gather meters. Resetting Meters ---------------- Beginning in VOS Release 14.5.0, the dump_lap_meters request of the analyze_system command has a new argument, -reset. When you specify the - reset argument, the request creates the file as_meter_file in your home directory. In addition, the request resets the meters but does not display them. You must issue the dump_lap_meters channel_name request to display the meters with their new values. You can use the set_meter_file request of the analyze_system command to change the default name of the as_meter_file file. For more information about the dump_lap_meters request of the analyze_system command, see the VOS System Analysis Manual (R073). Logical Volumes and the Paging Partition of Nonboot Disks --------------------------------------------------------- Beginning in VOS Release 13.3.0, the paging partition of nonboot disks is used only after the logical volume has been salvaged. This change may cause a bootload to fail on modules that do not have enough paging space on the boot disk to allow salvager processes to simultaneously salvage all of the nonboot disks. The paging partition on the boot disk is the only one that is available when the salvager is run during the reboot process. In the event that many simultaneous salvages are started for nonboot disks, there may be an exhaustion of paging partition and a potential failure to reboot cleanly. Pre-login Processes ------------------- Beginning in VOS Release 14.1.0, you can change the default priority of the pre-login processes on a per-module basis. If you would like to change this setting on your module for any reason, contact the CAC. Process Management ------------------ You can maximize the performance of processes running on a Continuum- SRB: VOS Release 14.5.0 (R914) 3-5 Process Management series module with a quad-processor configuration by adhering to the following scaling rules. o User processes issuing communications system calls should run in memory pool 0 (that is, the pool on which communications protocols are started). For example, if the module_start_up.cm command macro starts OS TCP/IP on memory pool 0, you can obtain optimal performance by ensuring that any processes calling OS TCP/IP also run on memory pool 0. o Processes communicating with each other (for example, a server queue) should run in the same memory pool. Note: On PA-7100 modules, VOS Release 14.0.0 allows a maximum of 2 GB of total memory for uni- or twin-processor configurations and a maximum of 3 GB of total memory for quad-processor configurations. You can check an application's memory-pool value by observing the memory- pool column (column M) that is displayed by the list_users command. In the following sample output of the list_users command, test.pm is associated with memory pool 1, while list_users.pm is associated with memory pool 0. USERS at 15:30:40 CPU DCPU PF DPF M PS F P PROGRAM Mary_Jones 26.4 9523 1 WS + 7 test.pm Mary_Jones 0.8 284 0 RD + 7 list_users.pm The who -cpu request of the analyze_system command displays the number of processes on each CPU (and therefore on each memory pool). Similarly, the sched_meters request of the analyze_system command displays the CPU usage on each processor (in the CPU time distribution section). Processes associated with a particular memory pool (that is, assigned to a CPU/memory board) receive memory only from that memory pool. If processes assigned to a memory pool use too much memory, excessive paging or memory- pool resource contention may occur. If you are dissatisfied with the distribution of CPU usage across processors on your module, stop a process on the more heavily used memory pool and restart it on the other memory pool. Increase in Ports per Process and Events per Module --------------------------------------------------- Beginning in VOS Release 14.2.2, the maximum number of port attachments per process has increased to 4096. The total number of events on a module has increased to 262,143. The total number of events per process has SRB: VOS Release 14.5.0 (R914) 3-6 Increase in Ports per Process and Events per Module increased from 1550 to 6000. You can change the number of events by using the -max_events_per_process argument of the set_tuning_parameters command. For more information about the set_tuning_parameters command, see the manual VOS System Administration: Administering and Customizing a System (R281). Setting and Displaying VOS STREAMS Parameters --------------------------------------------- Beginning in VOS Release 14.0.0, you can display and set STREAMS parameters using two new analyze_system requests: list_streams_params and set_streams_param. For information about these requests, see theVOS System Analysis Manual (R073). Time-Zone Changes ----------------- This section discusses the following topics related to time-zone changes. o ``New Information in the Disk Label" o ``Additional Time Zones" o ``Time Zone Changes to the analyze_system Command" New Information in the Disk Label --------------------------------- VOS stores information about the system time zone and minutes offset from Greenwich Mean Time (GMT), also known as Universal Time, in the disk label. VOS uses this information from the boot disk label when a system is brought up. Beginning in VOS Release 14.0.0, the time-zone information stored on the disk label now includes a flag that indicates daylight savings time. Additional Time Zones --------------------- Beginning in VOS Release 14.0.0, VOS supports the time zones listed in Table 3-1. Table 3-1. Time Zones Supported in VOS (Page 1 of 3) -------------------------------------------------------------------------- SRB: VOS Release 14.5.0 (R914) 3-7 Time-Zone Changes | : : Difference : Implements : New for | | : : from GMT : : | | : : : Daylight : VOS Release | | : : (in : : 14.0.0 | | Code : Description : Minutes) : Savings : | |------------------------------------------------------------------------| | adt : Atlantic Daylight : -180 : yes : no | |------------------------------------------------------------------------| | ast : Atlantic Standard : -240 : no : no | |------------------------------------------------------------------------| | at : Azores : -120 : no : yes | |------------------------------------------------------------------------| | bst : British Summer : 60 : yes : yes | |------------------------------------------------------------------------| | bt : Baghdad : 180 : no : yes | |------------------------------------------------------------------------| | cad : Central Australia : 630 : yes : yes | | : Daylight : : : | |------------------------------------------------------------------------| | cas : Central Australia : 570 : no : yes | | : Standard : : : | |------------------------------------------------------------------------| | cdt : Central Daylight : -300 : yes : no | |------------------------------------------------------------------------| | cet : Central European : 60 : no : yes | |------------------------------------------------------------------------| | chd : China Daylight : 540 : yes : yes | |------------------------------------------------------------------------| | cht : China Time : 480 : no : yes | |------------------------------------------------------------------------| | cst : Central Standard : -360 : no : no | |------------------------------------------------------------------------| | ead : East Australia : 660 : yes : yes | | : Daylight : : : | |------------------------------------------------------------------------| | eas : East Australia : 600 : no : yes | | : Standard : : : | |------------------------------------------------------------------------| | edt : Eastern Daylight : -240 : yes : no | |------------------------------------------------------------------------| | eet : Eastern Europe : 120 : no : yes | |------------------------------------------------------------------------| | est : Eastern Standard : -300 : no : no | |------------------------------------------------------------------------| | fst : French Summer : 120 : yes : yes | |------------------------------------------------------------------------| | fwt : French Winter : 60 : no : yes | |------------------------------------------------------------------------| | gmt : Greenwich Mean : 0 : no : no | |------------------------------------------------------------------------| SRB: VOS Release 14.5.0 (R914) 3-8 Time-Zone Changes | gst : Greenland Standard : -180 : no : yes | |------------------------------------------------------------------------| | hdt : Hawaii-Aleutian : -540 : yes : no | | : Daylight : : : | |------------------------------------------------------------------------| | hfe : Heure Francaise : 120 : yes : yes | | : d'Ete : : : | |------------------------------------------------------------------------| | hfh : Heure Francaise : 60 : no : yes | | : d'Hiver : : : | |------------------------------------------------------------------------| | hkt : Hong Kong : 480 : no : yes | |------------------------------------------------------------------------| | hst : Hawaii-Aleutian : -600 : no : no | | : Standard : : : | |------------------------------------------------------------------------| | ist : Indian Standard : 330 : no : yes | |------------------------------------------------------------------------| | jst : Japan Standard : 540 : no : yes | |------------------------------------------------------------------------| | jt : Java : 450 : no : yes | |------------------------------------------------------------------------| | kdt : Alaska Daylight : -540 : yes : yes | |------------------------------------------------------------------------| | kst : Alaska Standard : -600 : no : yes | |------------------------------------------------------------------------| | mas : Malaysia Standard : 480 : no : yes | |------------------------------------------------------------------------| | mdt : Mountain Daylight : -360 : yes : no | |------------------------------------------------------------------------| | mes : Middle Europe Summer: 120 : yes : yes | |------------------------------------------------------------------------| | met : Middle Europe : 60 : no : yes | |------------------------------------------------------------------------| | mew : Middle Europe Winter: 60 : no : yes | |------------------------------------------------------------------------| | mst : Mountain Standard : -420 : no : no | |------------------------------------------------------------------------| | ndt : Newfoundland : -150 : yes : no | | : Daylight : : : | |------------------------------------------------------------------------| | nst : Newfoundland : -210 : no : no | | : Standard : : : | |------------------------------------------------------------------------| | nt : Nome : -660 : no : yes | |------------------------------------------------------------------------| | nzd : New Zealand Daylight: 780 : yes : yes | |------------------------------------------------------------------------| | nzs : New Zealand Standard: 720 : no : yes | |------------------------------------------------------------------------| SRB: VOS Release 14.5.0 (R914) 3-9 Time-Zone Changes | pdt : Pacific Daylight : -420 : yes : no | |------------------------------------------------------------------------| | phs : Philippine Standard : 480 : no : yes | |------------------------------------------------------------------------| | pst : Pacific Standard : -480 : no : no | |------------------------------------------------------------------------| | sdt : Samoa Daylight : -660 : yes : yes | |------------------------------------------------------------------------| | sis : Singapore Standard : 480 : no : yes | |------------------------------------------------------------------------| | sst : Samoa Standard : -600 : no : yes | |------------------------------------------------------------------------| | tpe : Taiwan Standard : 480 : no : yes | |------------------------------------------------------------------------| | tst : Thailand Standard : 420 : no : yes | |------------------------------------------------------------------------| | ut : Universal : 0 : no : yes | |------------------------------------------------------------------------| | wad : West Australia : 540 : yes : yes | | : Daylight : : : | |------------------------------------------------------------------------| | was : West Australia : 480 : no : yes | | : Standard : : : | |------------------------------------------------------------------------| | wat : West Africa : -60 : no : yes | |------------------------------------------------------------------------| | wib : Indonesia Standard : 420 : no : yes | |------------------------------------------------------------------------| | ydt : Yukon Daylight : -480 : yes : no | |------------------------------------------------------------------------| | yst : Yukon Standard : -540 : no : no | |------------------------------------------------------------------------| | z : Zulu (Universal) : 0 : no : yes | -------------------------------------------------------------------------- FOOTNOTE: 1 Numeric-keypad key Note: Beginning in VOS Release 14.0.0, the bdt (Bering Daylight Time) time-zone code is no longer supported. Note: Beginning in VOS Release 14.0.0, the bst (Bering Standard Time) time-zone code is now used for British Summer time. The replacement time-zone code for Bering Standard Time is nt (Nome). Beginning in VOS Release 14.0.0, the hdt and hst time-zone codes are now used for Hawaii-Aleutian Daylight time and Hawaii-Aleutian Standard time, respectively. They were previously used for Alaska Daylight time and Alaska Standard time, but these now have the kdt and kst time-zone codes, respectively. SRB: VOS Release 14.5.0 (R914) 3-10 Time-Zone Changes Time Zone Changes to the analyze_system Command ------------------------------------------------ Beginning in VOS Release 14.0.0, the analyze_system command has the following changes related to time zones. o The display_process_info request now displays the daylight_time_zone flag in the list of pdr flags if the daylight_time_zone flag was set in the pdr for this process. o The dump_label request now displays either (standard) or (daylight) after the Time zone delta field. See the VOS System Analysis Manual (R073) for more information about the analyze_system command. SRB: VOS Release 14.5.0 (R914) Chapter 4: General User Interface ====================== This chapter discusses changes to the VOS general user interface. It contains the following sections. o ``Office/2000" o ``New Commands" o ``Changed Commands" o ``Obsolete Commands" o ``New and Changed Command Functions" o ``Emacs Changes" Office/2000 ----------- Beginning in VOS Release 14.0.0, Office/2000 has additional terminal support. For information about the following issues related to Office/2000 and terminal support, see the file terminal_support.doc in the directory >system>doc. o additional terminal-type (TTP) files that are supported for Office/2000 o "Emacs-style" input sequences o documentation for new input key sequences o additional input sequences The Office/2000 Simple Mail Transfer Protocol (SMTP) gateway does not work with STCP. For information about STCP, see ``Overview of STCP'' in Chapter 5. New Commands ------------ The following commands are new or newly documented beginning in VOS Release 14.0.0 or later. o display_disk_fragmentation--Beginning in VOS Release 14.4.0, this command detects fragmented files, directories, and free space on a disk. For complete information about the display_disk_fragmentation SRB: VOS Release 14.5.0 (R914) 4-1 New Commands command, see ``New Disk Commands" in Chapter 2. o freeze_process--This privileged command forces a running or waiting process to enter into the frozen state. Once a process is frozen, VOS will not schedule it to run on a CPU until the process is thawed using the command thaw_process. For more information about freezing and thawing processes, see ``Freezing and Thawing Processes'' in Chapter 2. For complete information about the freeze_process and thaw_process commands, see the manual VOS System Administration: Administering and Customizing a System (R281). o kill--Beginning in VOS Release 14.4.0, this command sends a signal to the process(es) specified by each PID operand. For information about the kill command, see ``New Commands'' in Chapter 7, and >system>doc>posix>posix.doc. o thaw_process--This privileged command thaws (that is, unfreezes) a process frozen by the freeze_process command. When a process thaws, it returns to the state it was in before it was frozen. So, for example, a process that was running before it was frozen will be returned to the ready queue. As another example, a process that was suspended (that is, waiting) will be returned to the wait state. For more information about freezing and thawing processes, see ``Freezing and Thawing Processes'' in Chapter 2. For complete information about the freeze_process and thaw_process commands, see the manual VOS System Administration: Administering and Customizing a System (R281). o list_kernel_programs--This command lists the program modules that are currently loaded into the VOS kernel. For complete information about the list_kernel_programs command, see the manual VOS System Administration: Administering and Customizing a System (R281). o patch_file--Beginning in VOS Release 14.0.0, this command changes a file without regard to its organization or content. For more information about this command, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). o patch_index--Beginning in VOS Release 14.0.0, this command changes the data in an index block without regard to its organization or content. For more information about this command, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). o read_tape_encrypted--This command reads encrypted tape files and decrypts them using routines that you supply. The command then places the resulting files into your current directory. For complete information about this command, see the manual VOS System Administration: Disk and Tape Administration (R284). SRB: VOS Release 14.5.0 (R914) 4-2 New Commands o unload_kernel_program--This command unloads a program module that is currently loaded into the VOS kernel. For complete information about the unload_kernel_program command, see the manual VOS System Administration: Administering and Customizing a System (R281). o view_release_tape_log--This command displays the log of installations on a module. For complete information about this command, see the VOS Installation Guide (R386). o write_tape_encrypted--This command optionally encrypts one or more files and writes them to the tape volume on the specified tape drive or on the tape drive connected to the specified port. For complete information about the write_tape_encrypted command, see the manual VOS System Administration: Disk and Tape Administration (R284). Changed Commands ---------------- This section lists the changes that have been made to VOS commands beginning in VOS Release 14.0.0. o add_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o add_paging_file--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o analyze_system--This command has numerous changes, which this manual describes in the following sections. - ``The analyze_system Command Argument -c_expressions'' in Chapter 2 - ``Expanded dump_vm_pool_info Display'' in Chapter 2 - ``New dump_sdlmux Request'' in Chapter 2 - ``New dump_dlmux_info Request'' in Chapter 2 - ``New Disk Salvaging Behavior'' in Chapter 2 - ``Changes to the disk_meters Request'' in Chapter 2 - ``Resetting Meters'' in Chapter 3 - ``Creating Meter Files Using the analyze_system Command'' in SRB: VOS Release 14.5.0 (R914) 4-3 Changed Commands Chapter 3 - ``Setting and Displaying VOS STREAMS Parameters'' in Chapter 3 - ``Time Zone Changes to the analyze_system Command'' in Chapter 3 - ``New and Changed STREAMS Requests in analyze_system'' in Chapter 5 - ``New K115 I/O Adapter (Token Ring) Request in analyze_system'' in Chapter 5 - ``Changes to the dump_cache Request in analyze_system'' in Chapter 6 - ``Changes to the dump_cache_info Request in analyze_system'' in Chapter 6 - ``Changes to the cache_meters Request in analyze_system'' in Chapter 6 - ``Changes to the dump_afte and dump_axte Requests in analyze_system'' in Chapter 6 - ``Changes to the dump_disk_info Command'' in Chapter 6 - ``DAE-Related Changes to analyze_system Requests'' in Chapter 6 - ``New TPF-Related analyze_system Requests'' in Chapter 9 o batch--Beginning in VOS Release 14.5.0, this command's behavior has changed if you do not specify the -output_path argument. See ``Changes to the start_process and batch Commands'' in Chapter 2. o bind--Beginning in VOS Release 14.0.0, the bind command has changed. See ``Changes to the VOS Binder'' in Chapter 7 for information. o break_process--Beginning in VOS Release 14.4.0, this command has a new value, info, for the -ask argument. When you specify the info value, the output display will include the PID information. For more information about the break_process command, see the VOS Commands Reference Manual (R098). o cancel_disk_retry and cancel_fast_disk_recovery--See ``Changed Disk Commands'' in Chapter 2. o compare_files--Beginning in VOS Release 14.5.0, the - difference_count argument of this command now allows the value zero. See ``Changes to the compare_files Command'' in Chapter 2 for more information about this argument. SRB: VOS Release 14.5.0 (R914) 4-4 Changed Commands o configure_gateways--Beginning in VOS Release 14.0.0, this command requires that gateway names be valid names as determined by the s$valid_name subroutine. See the manual VOS Communications Software: X.25 and StrataNET Administration (R091) for more information about the configure_gateways command. See the VOS Subroutines manuals for more information about the s$valid_name subroutine. o copy_file--This command has a new argument, -keep_audit. This argument indicates that the new file retains the audit options of the source file. For more information about copy_file, see the VOS Commands Reference Manual (R098). o create_file--Beginning in VOS Release 14.3.0, this command has a new argument, -dynamic_extents, used to specify a DAE file. See ``Command Changes" in Chapter 6 for more information about this argument. o create_index--Beginning in VOS Release 14.3.0, this command has a new argument, -dynamic_extents, used to specify a DAE index. See ``Command Changes" in Chapter 6 for more information about this argument. The -extent_size argument has a new limit of 524,280 blocks (previously, the limit was 32,768 blocks); this limit applies only to statically allocated extent (SAE) indexes and is the same as the limit for the create_file command. The -num_blocks argument has a new limit of 2**31-1 (previously, the limit was 32,768). Beginning in VOS Release 14.0.0, the create_index command supports a new argument, -duplicate_path. This argument logs invalid duplicate keys in the specified file but does not insert them into the index. This argument requires the path name of a file that will contain the log of records with invalid duplicate keys. This file will contain information enabling you to locate the records containing the invalid duplicate keys, as well as information about the record that the key locates and about the specific file and index being created. If no invalid duplicate keys exist or if the index allows duplicate keys, the file is deleted when the command terminates. If the file already exists, the command overwrites it. If you do not specify this argument and the index contains duplicate keys, create_index will terminate (this behavior is the same as in previous releases). The following is a sample file created by specifying the - duplicate_path argument. file: %foo#m5>dir_1>dir_2>dir_3>huge_seq SRB: VOS Release 14.5.0 (R914) 4-5 Changed Commands index: index_1 duplicate key: 00000000 494E4445 585F315F 4B45595F 37 |INDEX_1_KEY_7 | ignored in record number 4417 [1141x] at position 4417 [1141x] (block 2 [2x] offset 320 [140x]): 00000000 494E4445 585F315F 4B45595F 37202020 |INDEX_1_KEY_7 | 00000010 20202049 4E444558 5F325F4B 45595F37 | INDEX_2_KEY_7| 00000020 30202020 20202049 4E444558 5F335F4B |0 INDEX_3_K| 00000030 45595F37 30202020 20202020 |EY_70 | existing key locates record 385 [181x] at position 385 [181x] (block 1 [1x] offset 384 [180x]): 00000000 494E4445 585F315F 4B45595F 37202020 |INDEX_1_KEY_7 | 00000010 20202049 4E444558 5F325F4B 45595F37 | INDEX_2_KEY_7| 00000020 20202020 20202049 4E444558 5F335F4B | INDEX_3_K| 00000030 45595F37 20202020 20202020 |EY_7 | In the preceding example, the command first identifies the file and then identifies the index. Next, the command identifies each invalid duplicate key with the following information. - a dump of the duplicate key - the position of the record where the duplicate key was found - a dump of the record containing the invalid duplicate key - the position of the record currently identified by the key - a dump of the record currently identified by the key For more information about the create_index command, see the VOS Commands Reference Manual (R098). o create_registration_sysdb--Beginning in VOS Release 14.4.0, this command accepts POSIX ID information in the registration_file.table.tin. If the user or group does not have a POSIX ID in the .table file, the create_registration_sysdb command SRB: VOS Release 14.5.0 (R914) 4-6 Changed Commands assigns a POSIX ID. o delete_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o dismount_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o display and display_file commands--These commands have the following changes. For complete information about these commands, see the VOS Commands Reference Manual (R098). - Beginning in Release 14.0.0, VOS supports the -slave_printer argument for both TeleVideo-style (V101, V102, and V103) and ANSI-style (for example, VT100, VT220, VT320, and CIT482) terminals. In addition, VOS supports this argument on any terminal whose terminal-type definition (.ttp) file defines the sequences aux-printer-on and aux-printer-off. The following standard ANSI .ttp files now define the aux-printer-x output sequences: cit482, vt100, vt220, vt320, v105, and v105_ansi. Previously, VOS supported the -slave_printer argument for TeleVideo-style terminals only, and the slave-printer control sequences were hard coded in these commands. - These commands have new arguments: -file_separator and - line_length. The -file_separator argument controls the appearance of the command output when you specify a value for the -output_path argument. When you specify the value ff (form-feed) for the - file_separator argument, the command uses a form-feed character to separate the output of multiple files. The default value is 0 (null), which causes the command to use a blank line to separate the output of multiple files. The -line_length argument specifies the number of columns displayed before the line wraps. For terminal devices, the default line length is the width of the output device; for nonterminal output devices (for example, output to a file), the default line length is 132 columns. This change affects slave printers; previously, the default line length for slave printers was 132 columns; now, the default line length for slave printers and for terminals is the same (generally, 80 columns). - The display command now opens an input file for dirty input if the input file is exclusively locked by another process and you SRB: VOS Release 14.5.0 (R914) 4-7 Changed Commands do not specify the -index argument. Therefore, the display command can read any data that has already been written to disk. However, since some data that has been written to the file may not be on disk (when, for example, the data is held by fast file I/O in the locking process), the display command also displays the following message, where object_name is the object name of the file. display: File is in use; using dirty input mode. Some data may not be visible yet. object_name o display_bad_blocks--See ``Changed Disk Commands'' in Chapter 2. o display_device_info--The command output now includes K450, K460, and K470 I/O controller device and port information. In addition, the display_device_info command includes the following fields in its output. Clone limit: Clone count: Cloned from: device type name: streams device: streams minor number: streams remote minor number: streams remote clone limit: streams driver: remote streams driver: Some of the new fields are displayed only when the device type (type) is streams. The field streams minor number is displayed only when the field streams driver is non-null; the field remote streams driver is displayed only when both its value and the value of the field streams driver are non-null. The following sample output from the display_device_info command contains the new fields. display_device_info %se#tpipe_telnetd.m2 SRB: VOS Release 14.5.0 (R914) 4-8 Changed Commands Device Information for %se#tpipe_telnetd.m2 type: streams module name: %se#m2 slot number: -1 channel number: -1 event id: 6 adapter slot number: -1 adapter subchannel number: -1 BIO device: -1 BIO port: -1 Clone limit: 0 Clone count: 0 Cloned from: 0 device type name: streams streams device: 1 streams minor number: 0 streams remote minor number: 0 streams remote clone limit: 0 streams driver: tpipe Device Flags: local: 1 reserved: 0 shareable: 1 configured: 1 dial out: 0 SRB: VOS Release 14.5.0 (R914) 4-9 Changed Commands login slave: 0 force listen: 0 privileged terminal: 0 ebcdic: 0 dial up: 0 half duplex: 0 multiplexed: 0 sub device: 0 spooler: 0 alternate speed: 0 reference count: 0 baud: ext stop bits: 0? parity: even terminal type name: parent device name: mpx number: 0 sub device number: 0 firmware type: Unknown? parameters: For more information about the display_device_info command, see the VOS Commands Reference Manual (R098). o display_disk_info--Beginning in VOS Release 14.4.0, the display_disk_info command displays the recovery state for any member disks that are recovering. See ``Changed Disk Commands'' in Chapter 2. o display_file--For information about changes to this command, see the description of changes to the display command earlier in this list. SRB: VOS Release 14.5.0 (R914) 4-10 Changed Commands o display_file_status--Beginning in VOS Release 14.3.0, this command displays new information about extent files. For information about these changes, see ``Command Changes" in Chapter 6. o display_scheduler_info--In the output of the display_scheduler_info command, the column TIME now displays CPU time (in seconds) to a precision of milliseconds. An example of the command output follows. --INTERACTIVE-- -----BATCH----- PRI SKT TYPE CNT TIME SKT TYPE CNT TIME 0 1 4 3 0.500 1 14 1 1.000 6 5 1.000 6 5 0.500 10 1 0.500 1 1 4 5 1.000 1 12 1 0.500 4 5 0.500 6 5 0.500 10 1 0.500 2 1 2 1 0.250 1 12 1 1.000 6 5 1.000 6 5 0.500 10 1 0.500 3 1 2 1 0.500 1 10 1 0.750 4 3 2.000 6 5 2.000 10 1 1.500 For more information about the display_scheduler_info command, see the manual VOS System Administration: Administering and Customizing a System (R281). o display_software_purchased--The output of the display_software_purchased command includes information about the SRB: VOS Release 14.5.0 (R914) 4-11 Changed Commands purchase status of new software products in the VOS release to which you are upgrading. See ``The display_software_purchased Command'' in Chapter 10. o dump_memory--Beginning in VOS Release 14.2.0, the dump_memory command has a new argument, -process_type. See ``Changes to the dump_memory Command" in Chapter 2. o format_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o initialize_boot_disk--This command has a new argument, -quick_dump. See ``Changed Disk Commands'' in Chapter 2. o initialize_disk and initialize_duplex_disk--These commands now allow you to specify the values 0 through 31 for the new_member argument. See ``Changed Disk Commands'' in Chapter 2. o list_devices--The output generated by the -long argument now includes K450, K460, and K470 I/O controller device and port information. For more information about the list_devices command, see the VOS Commands Reference Manual (R098). o list_users--Beginning in VOS Release 14.0.0, the output of this command can include the process state FZ, which indicates that the user process is frozen. The frozen process state is similar to the wait state except that VOS will not schedule a frozen process to run on a CPU until the process is thawed using the command thaw_process. You freeze a process by issuing the command freeze_process. For complete information about the commands list_users, freeze_process, and thaw_process, see the VOS Commands Reference Manual (R098). Beginning in VOS Release 14.4.0, list_users supports a new argument, - process_id. The behavior of the -process_id argument depends on whether list_users is invoked with a value for the -interval argument. The default value for -process_id is no. When you specify the -process_id argument without specifying - interval time, a PID column is added to the output to the left of the USER field. (The PID is the process ID, an 8-digit hexadecimal number, followed by an x.) When you specify the -process_id argument with -interval time, the display line output becomes longer than a single line per process. To avoid this problem, you can change the view of the fields of the interval display with the use of a PID display toggle. If you press the P or p key, the display will change between the PID display and the normal display. The following example shows the normal output. SRB: VOS Release 14.5.0 (R914) 4-12 Changed Commands list_users -interval 5 -full USERS at 17:45:00CPUDCPUPFMPROGRAM Joe_Vos4.757770emacs.pm Jan_Stratus27.7270320list_users.pm When you press the P or p key, the output will change to the PID display: list_users -interval 5 -full -process_id USERS at 17:46:00PIDDCPUPFMPROGRAM Joe_Vos011E4BCFx57770emacs.pm Jan_Stratus011E85D4x270320list_users.pm If the -admin argument was specified, the PID column toggles between the M, PS, F, and P columns. The following example shows the normal output. list_users -interval 5 -admin USERS at 17:48:30CPUDCPUPFDPFM PS F P PROGRAM Joe_Vos4.757770 ws + 5 emacs.pm Jan_Stratus27.7270320 ws + 5 list_users.pm When you press the P or p key, the output will change to the PID display: list_users -interval 5 -admin -process_id USERS at 14:48:47CPUDCPUPF DPFPIDPROGRAM Joe_Vos4.75777 011e4bcfxemacs.pm Jan_Stratus27.727032 011e85d4xlist_users.pm For more information about the list_users command, see the VOS Commands Reference Manual (R098). o log_registered_user--Beginning in VOS Release 14.4.0, this command writes POSIX ID information to the registration_file.tin. For more information, see the POSIX information file in >system>doc>posix>posix.doc. SRB: VOS Release 14.5.0 (R914) 4-13 Changed Commands o mount_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o network_watchdog--Beginning in VOS Release 14.5.0, this command has a new argument, num_seconds, and the num_minutes argument has a new default. See ``Changes to the network_watchdog Command'' in Chapter 2. o read_tape--Beginning in VOS Release 14.2.0, the read_tape command supports a new argument, multi_reel. When you specify the multi_reel argument, the read_tape command reads files that span tape volumes; also, the volume_id differs between succeeding reels. If all reels have the same value for the volume_id field, this argument is not needed for read_tape to process the tapes correctly. For more information about the read_tape command, see the VOS Commands Reference Manual (R098). o recreate_index--Beginning in VOS Release 14.0.0, the recreate_index command supports a new argument, -duplicate_path. This argument logs invalid duplicate keys in the specified file but does not insert them into the index. For additional information about this argument, see the description of the create_index command earlier in this chapter. For complete information about the recreate_index command (including information about the -duplicate_path argument), see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). Beginning in VOS Release 14.3.0, the output for recreate_index has been modified for DAE files and now includes the fields dynamic_extents and extent_size. For more information, see ``Dynamically Allocated Extents (DAE)" in Chapter 6. o registration_admin--Beginning in VOS Release 14.3.0, the action argument has changed in support of POSIX.1. For more information about this change, see ``Changes to the registration_admin Command'' in Chapter 2. For more information about this command, see the manual VOS System Administration: Registration and Security (R283). o remove_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o remove_tape--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o reset_configuration--Beginning in VOS Release 13.2.0, this command has a new argument, -reset_cabinet_configuration. For more information, see ``Change to the reset_configuration Command'' in SRB: VOS Release 14.5.0 (R914) 4-14 Changed Commands Chapter 2. o restore--This command now updates the date-time-saved information of the file it restores. For complete information about the restore command, see the manual VOS System Administration: Backing Up and Restoring Data (R285). Beginning in VOS Release 14.3.0, the restore command supports a new argument for DAE files, -dynamic_extents. For more information, see ``Command Changes" in Chapter 6. o salvage_disk--Beginning in VOS Release 14.4.0, the output to this command has changed. For more information, see ``Changes to the save Command'' in Chapter 2. o save--Beginning in VOS Release 14.4.0, this command has two new arguments that determine how blocks in files or indexes are read into cache. For more information, see ``Changes to the save Command'' in Chapter 2. o select_duplex_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o set_date_time--The maximum value you can specify for dates when you issue the set_date_time command is January 19, 2048, 3:14:06 GMT (that is, 2048-01-19_03:14:06_gmt). For complete information about this command, see the manual VOS System Administration: Administering and Customizing a System (R281). o set_partition_size--This command has a new argument, -extent_size value. For more informations, see ``Changed Disk Commands'' in Chapter 2. Beginning in VOS Release 14.3.0, this command has a new value for partition_name: excess. For more information, see ``Command Changes" in Chapter 6. o set_registration_info--Beginning in VOS Release 14.1.0, this command has a new argument, -force_change. See ``Changes to the set_registration_info Command'' in Chapter 2. o set_scheduler_info--Beginning in VOS Release 14.4.0, the value range of the -time argument to the set_scheduler_info command has changed. See ``Changes to the set_scheduler_info Command'' in Chapter 2. o set_tuning_parameters--This command has the following changes beginning in VOS Release 14.0.0. - The default value for the -max_events_per_process argument is 64. SRB: VOS Release 14.5.0 (R914) 4-15 Changed Commands - The maximum number of physical disk cache buffers you can specify for the -bm_max_buffers argument depends on the module's memory configuration. - You can specify up to 524,288 virtual pages for the - bm_max_virtual_pages argument. If you specify a value that is inconsistent with the CPU type, even if it is within the boundaries of allowed values, the command uses the internally set value instead. If you specify a value larger than 32,767 for the -bm_max_buffers or - bm_max_virtual_pages argument and if the current module and the target module (that is, the module for which you are setting tuning parameters) are running different VOS releases, you could encounter errors, as follows: - If the current module is running VOS Release 14.0.0 or later and the target module is running VOS Release 13.3.0 or earlier, and if you attempt to set -bm_max_buffers or -bm_max_virtual_pages to a value larger than 32,767, the system returns the error e$out_of_range (1038) and the message module_name does not support buffer manager parameters greater than 32767. No errors occur if you set either or both of the arguments to a value less than or equal to 32,767. - If the current module is running VOS Release 13.3.0 or earlier and the target module is running VOS Release 14.0.0 or later, and if you attempt to set -bm_max_buffers or - bm_max_virtual_pages to a value larger than 32,767, a significant performance decrease could occur and the system returns the error e$out_of_range (1038). If you encounter either of the preceding errors, log in to the target module and issue the set_tuning_parameters command from that module. Beginning in VOS Release 14.2.2, the set_tuning_parameters command has the following new arguments to support memory-resident files. -cm_cache_mem_pct N -cm_max_resident_pct N -cm_min_cache_priority N -cm_disk_write_limit N -cm_cate_write_limit N Beginning in VOS Release 14.3.0, the set_tuning_parameters command SRB: VOS Release 14.5.0 (R914) 4-16 Changed Commands has the following new arguments to support memory-resident files. For more information, see ``New Cache-Related Tuning Arguments" in Chapter 6. -cm_disk_mod_limit N -cm_transient_mod_grace_time N For more information about the set_tuning_parameters command, see the manual VOS System Administration: Administering and Customizing a System (R281). For information about using the set_tuning_parameters command to tune the cache, see the file cache_tuning.doc in the directory >system>doc. o setup_disk--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o setup_tape--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o start_disk_recovery--This command supports the -memory_pool argument. See ``Changed Disk Commands'' in Chapter 2. o start_logging--Beginning in VOS Release 14.4.0, this command has two new arguments: -timestamp_beginning and -timestamp_ending. See ``Changes to the start_logging Command'' in Chapter 2. o start_process--Beginning in VOS Release 14.5.0, this command's behavior has changed if you do not specify the -output_path argument. See ``Changes to the start_process and batch Commands'' in Chapter 2. o stop_process--Beginning in VOS Release 14.4.0, this command has a new value, info, for the -ask argument. When you select the info value, the output display will include the PID information. For more information about the stop_process command, see the VOS Commands Reference Manual (R098). o test_index--The use and look_at requests of the test_index command have a new argument: -update. See ``Changes to the test_index Command'' in Chapter 2. o update_disk_label--Beginning in VOS Release 14.4.0, this command generates additional output to the system error log. See ``Changed Disk Commands'' in Chapter 2. o verify_save--Beginning in VOS Release 14.3.0, this command has been updated to work with DAE files. See the VOS Commands Reference SRB: VOS Release 14.5.0 (R914) 4-17 Changed Commands Manual (R098) for more information about the verify_save command. o where_block--Beginning in VOS Release 14.3.0, this command has been updated to work with DAE files. See the manual VOS System Administration: Disk and Tape Administration (R284) for more information about the where_block command. o who_locked--Beginning in VOS Release 14.5.0, this command has a new argument, -brief. See ``Changes to the Manual Boot Procedure'' in Chapter 2 for more information. o x25--Beginning in VOS Release 14.5.0, this command has new warning and error messages. See ``Changes to X.25 and X.25 T1'' in Chapter 5 for more information. Beginning in VOS Release 14.0.0, the x25 command has three new arguments: -cafis_reset_diag, -cafis_tp1, and -cafis_tp2. These arguments are intended for use only in the Credit and Financial Information System (CAFIS) network. These arguments do not appear in the display form of the x25 command. For information about these arguments, see the file x25_command_args.doc in the directory >system>doc. For information about the x25 command, see the manual VOS Communications Software: X.25 and StrataNET Administration (R091). Beginning in VOS Release 13.3.0, the x25 command has an additional argument, -send_window_1_override. If you specify the value yes, the command overrides the agreed send window size with a send window size of 1. This override affects all virtual circuits using the gateway. The default value is no. Also beginning in VOS Release 13.3.0, the x25 command supports packet sizes of up to 2048 bytes. o x25_exchange--The -syserr argument of the x25_exchange command has the following new values. - If you specify the log_only value, the command sends error messages to the system-error log file (syserr_log.date) only. - If you specify the log_file value, the command sends error messages to a log file in the >system directory. The log file has the format x25_exchange_log.yymmdd, where yy represents the year, mm represents the month, and dd represents the day on which x25_exchange was started. See the manual VOS Communications Software: X.25 and StrataNET Administration (R091) for more information about the x25_exchange command. o x25_t1--Beginning in VOS Release 13.3.0, the x25_t1 command supports SRB: VOS Release 14.5.0 (R914) 4-18 Changed Commands packet sizes of up to 4096 bytes. Obsolete Commands ----------------- The following commands are obsolete and no longer supported. o bind_kernel--Beginning in VOS Release 14.0.0, the bind_kernel command is no longer available. To bind a kernel-loadable program in VOS Release 14.0.0 and later releases, use the bind command with the kernel value of the options directive, which you specify by including the following statement at the beginning of your binder control file. options: kernel; o link_boot_server--Beginning in VOS Release 14.5.0, this command is no longer available on Continuum systems. The removal of this command has no impact on Continuum system users. o set_bootload_time--Beginning in VOS Release 14.5.0, this command is no longer available on Continuum systems. The removal of this command has no impact on Continuum system users. o set_cpu_config--Beginning in VOS Release 14.4.0, this command is no longer available on Continuum systems. The removal of this command has no impact on Continuum system users. o specify_cpu_configuration--Beginning in VOS Release 14.4.0, this command is no longer available on Continuum systems. The removal of this command has no impact on Continuum system users. New and Changed Command Functions --------------------------------- The following sections describe two new command functions, (iso_date) and (iso_date_time), as well as changes to the (module_info) and (process_info) command functions. See the VOS Commands Reference Manual (R098) for more information about these command functions. o ``The (iso_date) Command Function" o ``The (iso_date_time) Command Function" o ``The (module_info) Command Function" o ``The (process_info) Command Function" SRB: VOS Release 14.5.0 (R914) 4-19 New and Changed Command Functions The (iso_date) Command Function ------------------------------- The (iso_date) command function is identical to the existing (date) command function, except that it returns a four-digit year by default. For example, if the (date) command function returns the value 97-08-16, the (iso_date) command function would return the value 1997-08-16. Note that if you specify the -standard argument, the (iso_date) command function uses the formats in the languages.tin file to determine the format of the returned value, and the output may or may not include a four- digit year. The (iso_date_time) Command Function ------------------------------------ The (iso_date_time) command function is identical to the (date_time) command function, except that it returns a four-digit year by default. For example, if the (date_time) command function returns the value 97-08-16 19:19:19, the (iso_date_time) command function would return the value 1997- 08-16 19:19:19. Note that if you specify the -standard argument, the (iso_date_time) command function uses the formats in the languages.tin file to determine the format of the returned value, and the output may or may not include a four-digit year. The (module_info) Command Function ---------------------------------- The (module_info) command function has the following changes. o To return the current VOS version identifier, you can specify either the value os_release or system_release for the key argument. Previously, you could specify only the value system_release to return this information. o You can determine the current module's processor family by specifying the value cpu_family for the key argument. Possible return values are mc68k, i860, or hppa. The (process_info) Command Function SRB: VOS Release 14.5.0 (R914) 4-20 New and Changed Command Functions ----------------------------------- The (process_info) command function now supports the language key, which returns the name of the language of the current process. Emacs Changes -------------- This section discusses the following topics. o ``The STOPPROCESS Condition Handler" o ``Change to the save_file Request" o ``New Control Arguments" The STOPPROCESS Condition Handler --------------------------------- Beginning in VOS Release 14.1.0, Emacs sets up a condition handler for the STOPPROCESS condition. If Emacs catches the STOPPROCESS condition, it will print the following message on the status line. A STOPPROCESS has been received. Save any modified buffers and quit! After the STOPPROCESS condition is called, the operating system allows 60 seconds to execute the code defined in the application program's condition handler, if any, and then stops the process. Change to the save_file Request ------------------------------- Beginning in VOS Release 14.1.0, Emacs warns you when you try to save to a file that has been modified since Emacs read in the file. When you issue a save_file request to a file that has been modified since Emacs read in the file, you are warned of this condition and asked whether you wish to proceed. If the answer is yes, the other changes to the file are lost. If the answer is no, the save is aborted and the other changes are preserved. Prior to this change to Emacs, the other changes were overwritten without warning. The file timestamp is updated when the file is successfully saved. New Control Arguments --------------------- SRB: VOS Release 14.5.0 (R914) 4-21 Emacs Changes Beginning in VOS Release 14.4.0, Emacs supports four new arguments. These arguments specify file attributes to use when Emacs creates a new file. The new arguments are as follows: -organization organization Specifies one of the following types of file organization for the new file. - sequential - stream - relative - fixed By default, the command creates a sequential file. -record_size record_size Specifies the maximum record size, in bytes, when creating a file. The record_size is a value from 1 to 32,767. The command ignores this value for sequential and stream files. -character_set character_set Specifies one of the following default character sets to be assigned to the file. - none - ascii - latin_1 - kanji - katakana - hangul - simplified_chinese - chinese1 - chinese2 - user_dbcs SRB: VOS Release 14.5.0 (R914) 4-22 Emacs Changes By default, a value of none is assigned to the file, indicating no default character set. -shift_mode shift_mode Specifies the shift combinations allowed in the new file. Possible values for shift_mode are: - none - locking - single - all By default, the command assigns the value none. This argument is ignored when -character_set is none. Explanation *********** When Emacs creates a new file (for example, with the write_file or write_region request), it uses the values specified by the new arguments to create the file with the specified attributes. If the file already exists, Emacs retains the existing attributes of the file. If Emacs cannot create a file of the specified type, it displays an error and prompts you for a response with the following: Invalid shift mode. Can't make file. Make sequential file? (yes, no) If you type Yes, a sequential file with a character set of none and a shift mode of none is created (the defaults). If you type no, the request is aborted. When Emacs writes out a buffer that contains National Language Support (NLS) characters, it overrides a request to create a stream file; instead, it creates a sequential file with a character set of ascii and shift mode of all. Only fixed, relative, and sequential files can have a default character set. Stream files cannot have a default character set. A fixed file that has a default character set must specify a shift mode of none, indicating that no shift characters are allowed. SRB: VOS Release 14.5.0 (R914) 4-23 Emacs Changes For more information on using VOS Emacs, see the VOS Emacs User's Guide (R093). SRB: VOS Release 14.5.0 (R914) Chapter 5: Communications ============== This chapter discusses changes to Stratus communications products. It contains the following sections. o ``Products Supported on Continuum-Series Modules" o ``Products Not Supported on Continuum-Series Modules" o ``Improvements Affecting STREAMS Drivers" o ``The K115-10 Token-Ring I/O Adapter" o ``Changes to X.25 and X.25 T1" o ``Change to the Multiplexed Host Interface (MHI)" o ``Changes to the UCOMM Binder Control File" o ``TCP/IP Products" o ``The Data-Link Multiplexer: SDLMUX and DLMUX" o ``VOS Open StrataLINK" o ``Changes Affecting Window Terminal Devices" o ``Enhanced Polling Support" Products Supported on Continuum-Series Modules ---------------------------------------------- This section lists products supported on Continuum-series modules running VOS Release 14. o ``Continuum-Series Modules" o ``Modules with PA-7100 Processors" Continuum-Series Modules ------------------------- Continuum-series modules running VOS Release 14 support the following communications products. SRB: VOS Release 14.5.0 (R914) 5-1 Products Supported on Continuum-Series Modules o 3270 Terminal Support and 3270 Terminal Emulation o 48K Baud Tokyo Stock Exchange (TSE_48K) protocol o 48K Tokyo Stock Exchange (TSE) Support o Binary Synchronous Communications (BSC) protocol o City Protocol Support (CPS) o Data-Link Multiplexor (SDLMUX/DLMUX) o Electronic Funds Transfer (EFT) Protocol o FDDI (using the U250 Remote I/O Switch--See ``Summary of Changes to OS TCP/IP Since VOS Release 13.0" later in this chapter) o Financial Ticker Protocol Support o Link Access Procedure, Balanced (LAPB) protocol o Local 4993 o Local TPF o Multiplexed Host Interface (MHI) Software (this software enables communications with a Datakit (r) Virtual Circuit Switch (VCS) node) o Network Express (tm) o Network File Server (NFS(tm)) o Open StrataLINK o Osaka Stock Exchange (OSE) protocol o OSI Server o OS Transmission Control Protocol/Internet Protocol (OS TCP/IP) Application Support o OS TCP/IP Support o PC/Connect o Poll/Select o Remote Job Entry (RJE) 2780/3780/HASP SRB: VOS Release 14.5.0 (R914) 5-2 Products Supported on Continuum-Series Modules o standard asynchronous driver (V103 or other terminals) o StrataNET o STREAMS Transmission Control Protocol (STCP) o Synchronous Data Link Control (SDLC) o Systems Network Architecture (SNA) products - Advanced Program-to-Program Communications (APPC) - Communications and System Management (CASM) - Distributed System Services (DSS) - Primary SNA - Secondary SNA - SNA Network Interface Support - SNA Qualified Logical Link Control (QLLC) - SNA Routing Facility - SNA Token Ring Link Manager o TELNET and File Transfer Protocol (FTP) o Tokyo Stock Exchange (TSE) protocol o Universal Communications (UCOMM) o V105 terminal o Window terminal driver o VISA protocol o X.25 Network Facility o X.25 over T1 o X.29 Network Facility Modules with PA-7100 Processors ------------------------------- SRB: VOS Release 14.5.0 (R914) 5-3 Products Supported on Continuum-Series Modules Continuum-series modules with PA-7100 processors running VOS Release 14 support the following additional communications products. Note that Continuum-series modules with PA-8000 family processors running VOS Release 14 do not support these products. o Airline Link Control (ALC) o ALC Programmable Support o Dow Jones News Retrieval o Local 3272 Emulation o OSE Support o Programmable Ethernet o Synchronous Link Control (SLC) o SLC Programmable Support o Token-Ring NetBIOS o TSE Support o VISA protocol Products Not Supported on Continuum-Series Modules -------------------------------------------------- Continuum-series modules running VOS Release 14.0.0 and later do not support the following communications products regardless of the module's processor. o DNS/2000 International o TCP/IP 2.x product set (see ``Product End-of-Life Notices'' in Chapter 1) o VOS LAT (see ``Product End-of-Life Notices'' in Chapter 1) o traditional StrataLINK--Continuum-series modules do not support traditional StrataLINK hardware; Open StrataLINK provides the VOS communication within a system of modules that traditional StrataLINK formerly provided. Improvements Affecting STREAMS Drivers SRB: VOS Release 14.5.0 (R914) 5-4 Improvements Affecting STREAMS Drivers --------------------------------------- Beginning in Release 14.0.0, VOS provides several improvements to STREAMS drivers, including significant performance improvements. The following sections describe additional changes. o ``Loading and Unloading STREAMS Drivers" o ``New and Changed STREAMS Requests in analyze_system" o ``New Daemon Processes" o ``Unloadable Host Remote STREAMS Driver (hrsd)" You can restrict access to STREAMS drivers and modules by specifying an access list for each driver or module. For information about setting access to STREAMS drivers and modules, see the manual VOS System Administration: Registration and Security (R283). Loading and Unloading STREAMS Drivers ------------------------------------- Beginning in VOS Release 14.0.0, you are no longer required to issue either the configure_comm_protocol command or the load_kernel_program command to configure (or load) STREAMS drivers. (You are still required to load non-STREAMS drivers such as bdl, gdl, and dlmux by issuing either command.) If you issue either command, the driver remains loaded until you explicitly unload it with the unload_kernel_program command. If you do not issue either the configure_comm_protocol or load_kernel_program command to configure (or load) STREAMS drivers, the driver will be loaded the first time an application opens a device that uses the driver, and the driver will be unloaded when the last user closes such a device (if the driver is unloadable). To avoid consuming the CPU time required to constantly load and unload STREAMS drivers automatically, you may want to explicitly configure STREAMS drivers that are frequently loaded and unloaded. For more information about the configure_comm_protocol command, see the manual VOS System Administration: Configuring a System (R287). For more information about the unload_kernel_program command, see the manual VOS System Administration: Administering and Customizing a System (R281). New and Changed STREAMS Requests in analyze_system --------------------------------------------------- SRB: VOS Release 14.5.0 (R914) 5-5 Improvements Affecting STREAMS Drivers Beginning in VOS Release 14.0.0, the analyze_system command includes the following STREAMS requests. o list_streams_params, which displays the STREAMS parameters that you can change o scan_streams_msgs, which summarizes STREAMS message usage o set_streams_param, which allows you to change the value of an individual STREAMS parameter For complete information about these requests, see the VOS System Analysis Manual (R073). In addition to the new STREAMS requests, the dump_stream request of the analyze_system command has changed: its output is easier to understand. You no longer need detailed knowledge of STREAMS internals. The request now validates many of the STREAMS structures, and it displays detected errors, indicated by the string ***. Therefore, you can issue a request similar to the following to check STREAMS structures. as: match ***;dump_stream -all_streams -long A dump of a Synchronization Queue Header (SQH) now indicates who locked it and prints out queued operations in easy-to-understand output. Note: If you dump the SQH on a running system, you may receive inconsistent results because data is constantly changing. The dump_stream request contains the following arguments, which are new beginning in VOS Release 14.0.0. o -driver_table o -msg_dump_size o -stm_sched For more information about the analyze_system command, see the VOS System Analysis Manual (R073). New Daemon Processes -------------------- Beginning in VOS Release 14.0.0, STREAMS drivers create the following new daemon processes. o Streams_Daemon SRB: VOS Release 14.5.0 (R914) 5-6 Improvements Affecting STREAMS Drivers o Streams_Memory_Daemon You can view these processes by issuing the command list_users -kernel, as shown in the following example. list_users -kernel -process streams* Overseer.System (Streams_Daemon) Overseer.System (Streams_Daemon) Overseer.System (Streams_Memory_Daemon) Unloadable Host Remote STREAMS Driver (hrsd) --------------------------------------------- You can now unload the host remote STREAMS driver (hrsd) manually by issuing the command unload_kernel_program. The driver is also unloaded automatically when it is no longer being referenced. The hrsd driver is loaded automatically when it is first referenced; you can also load the driver manually by issuing the configure_comm_protocol command. For complete information about the unload_kernel_program command, see the manual VOS System Administration: Administering and Customizing a System (R281). The K115-10 Token-Ring I/O Adapter ---------------------------------- The K115-10 Token-Ring I/O adapter supports a line speed of 16 Mbps and 2 MB of memory on the controller. This section provides additional information on the following topics. o ``Configuring the K115-10 I/O Adapter for 16-Mbps Line Speed" o ``New K115 I/O Adapter (Token Ring) Request in analyze_system" o ``Configuring the K115-00 I/O Adapter" o ``Determining the Maximum Number of Link Stations" Configuring the K115-10 I/O Adapter for 16-Mbps Line Speed ---------------------------------------------------------- To enable the 16-Mbps line speed and 2-MB memory support, specify the SRB: VOS Release 14.5.0 (R914) 5-7 The K115-10 Token-Ring I/O Adapter value user2 for the firmware_type field in the devices.tin file entry for the K115-10 I/O adapter. (Entries for the subdevices remain unchanged.) The following example presents a devices.tin file entry for a K115-10 I/O adapter (t_ring_1) configured for a line speed of 16 Mbps. / =name t_ring_1 =module_name m1 =device_type mpx_gcomm =slot 2 =adapter_slot_no 5 =adapter_subchannel_no 0 =mpx_device 1 =firmware_type user2 =parameters `-rcv_len 2048 -mx_sap 8 -mx_sta 64 -t1_one 10 -t2_one 2 -ti_one 50 -t1_two 50 -t2_two 20 -ti_two 250' You can still configure a K115-10 I/O adapter for a line speed of 4 Mbps; to enable the 4-Mbps line speed, specify the value user1 in the firmware field of the devices.tin file entry. For more information about configuring devices.tin file entries for Token- Ring devices, see the following manuals. o Software Release Bulletin: Token-Ring DLC Interface (R237) o Product Configuration Bulletin: Token-Ring Devices (R303) New K115 I/O Adapter (Token Ring) Request in analyze_system ----------------------------------------------------------- Beginning in VOS Release 14.5.0, the analyze_system command includes the mpx_gcomm_stop_wait_time$ flow-control request for the K115 adapter. This request allows you to change the value to delay stopping a device after opening it. This is useful when your application is performing quick opens SRB: VOS Release 14.5.0 (R914) 5-8 The K115-10 Token-Ring I/O Adapter and closes. The default delay time is 20 seconds. For more information about the analyze_system command, see the VOS System Analysis Manual (R073). Configuring the K115-00 I/O Adapter ----------------------------------- When you create a devices.tin file entry for a K115-00 I/O adapter, you must specify the value user1 for the firmware_type field; if you specify the value user2, the firmware will fail to load. The K115-00 I/O adapter only supports 4 Mbps. Determining the Maximum Number of Link Stations ----------------------------------------------- The maximum number of link stations available to all applications using one K115 Token-Ring I/O Adapter is based on the type of Token-Ring I/O adapter, K115-10 or K115-00. For specific information about determining the number of link stations that applications can open, see the file token_ring_dca.doc in the directory >system>doc. Changes to X.25 and X.25 T1 ---------------------------- The following list describes changes to X.25 and X.25 T1. o Continuing in VOS Release 13.3.0, you can specify up to 4094 simultaneous LCNs per gateway. Note: If you specify more than 510 simultaneous LCNs per gateway, Stratus does not guarantee the module's or network's performance. Stratus recommends that you benchmark any use above 510 LCNs per gateway before increasing the number. You can use the new -max_connections argument of the x25 and x25_t1 commands to specify the LCN limit for each gateway. For example, this argument allows you to specify up to 2048 simultaneous LCNs on one gateway while you specify only 510 simultaneous LCNs on another gateway (these numbers are based on your benchmarks or other factors). The default value for -max_connections is 510, the maximum recommended value. o Several x25 and x25_t1 messages, including the messages listed in the following table, have been added or modified since VOS Release SRB: VOS Release 14.5.0 (R914) 5-9 Changes to X.25 and X.25 T1 12.2. ------------------------------------------------------------------------- | Error or Warning Message : Description | |-----------------------------------------------------------------------| | WARNING: configured : The argument to - | | max_connections max_connections : max_connections exceeds 510. | | exceeds supported 510 LCN limit. : This warning message is new. | |-----------------------------------------------------------------------| | Supported 510 LCN limit has been : The number of connections | | exceeded on channel channel_name. : actually in use has exceeded | | : the limit of 510. This warning | | : message is new. | |-----------------------------------------------------------------------| | Maximum connection limit : The maximum connection limit | | exceeded - virtual circuit : has been reached. This error | | allocation refused. : message is modified. | |-----------------------------------------------------------------------| | WARNING: configured number of : The number of LCNs exceeds the - | | LCNs number_of_lcn exceeds : max_connections specified. This | | configured max_connections : warning message is new. | | max_connections. : | |-----------------------------------------------------------------------| | Event or lock cannot be attached : The event table is full. This | | because the event table is full. : error message is modified. | | Internal event limit exceeded. : | ------------------------------------------------------------------------- FOOTNOTE: 1 Numeric-keypad key o Beginning in VOS Release 14.5.0, the x25 command has the following new warning and error messages: WARNING: configured number of LCNs number_of_lcn exceeds configured max_connections max_connections. The x25 process logs this warning message upon initialization when the number of LCNs is greater than the value specified in the - max_connections argument, where number_of_lcn is determined by the value of the parameters given in the following calculation: num_pvc+(max_lcn-min_lcn+1) and number_of_connections equals the value of -max_connections. Event or lock cannot be attached because the event table is full. Internal event limit exceeded. The x25 process logs this message when a connection attempt is made after the value specified in the -max_connections argument has been reached. The LCN is cleared with a diagnostic code of 197. The LCN number and internal LCN state are provided as a prefix to this message as LCN number [lcn_state]. SRB: VOS Release 14.5.0 (R914) 5-10 Changes to X.25 and X.25 T1 o Beginning in VOS Release 14.0.0, the x25 command has three new arguments: -cafis_reset_diag, -cafis_tp1, and -cafis_tp2. These arguments are intended for use only in the Credit and Financial Information System (CAFIS) network. These arguments do not appear in the display form of the x25 command. For complete information about these arguments, see the file x25_command_args.doc in the directory >system>doc. Beginning in VOS Release 13.3.0, the x25 command has an additional argument, -send_window_1_override. If you specify the value yes, the command overrides the agreed send window size with a send window size of 1. This override affects all virtual circuits using the gateway. The default value is no. Also beginning in VOS Release 13.3.0, the x25 command supports packet sizes of up to 2048 bytes. o Beginning in VOS Release 13.3.0, the x25_t1 command supports packet sizes of up to 4096 bytes. o The -syserr argument of the x25_exchange command has two new values. - If you specify the log_only value, the command sends error messages to the system-error log file syserr_log.(date) only. - If you specify the log_file value, the command sends error messages to a log file in the >system directory. The log file has the format x25_exchange_log.yymmdd, where yy represents the year, mm represents the month, and dd represents the day on which x25_exchange was started. o The configure_gateways command now requires that gateway names be valid names as determined by the s$valid_name subroutine. See the manual VOS Communications Software: X.25 and StrataNET Administration (R091) for more information about the configure_gateways command. See the VOS Subroutines manuals for more information about the s$valid_name subroutine. For more information about the x25 command, see the manual VOS Communications Software: X.25 and X.29 Programming (R028). For more information about the x25_t1 command, see the Product Configuration Bulletin: X.25 T1 (R124). For more information about the x25_exchange command, see the manual VOS Communications Software: X.25 and StrataNET Administration (R091). Change to the Multiplexed Host Interface (MHI) ----------------------------------------------- SRB: VOS Release 14.5.0 (R914) 5-11 Change to the Multiplexed Host Interface (MHI) Note: This product was previously known as Datakit. The following list describes the changes to the Multiplexed Host Interface (MHI) beginning in VOS Release 14.0.0. o The dkhs and dkux drivers have been combined into a single driver, dkux. o You can now unload the dkbk, dkty_al, dkux, and dkxqt drivers from the kernel by issuing the unload_kernel_program VOS internal command. For information about this command, see the VOS System Administration: Administering and Customizing a System (R281). o Beginning in VOS Release 14.0.0, any attempt to push or link an MHI (that is, Datakit STREAMS) module on the same stream as a non-MHI driver results in failure, returning the error code e$incompatible_driver_layers (8951). The reverse also occurs: any attempt to push or link a non-MHI module on the same stream as an MHI driver results in failure, returning the same error code. The MHI modules are the following loadable program modules: dkbk, dkhs, dkty_al, dkux, dkxqt. The preceding MHI modules are not designed to work with other loadable drivers. Therefore, this restriction is only an enforcement of existing conventions and is not a functionality restriction. Changes to the UCOMM Binder Control File ---------------------------------------- The binder control file for the UCOMM Programming Kit (ucomm_fw.bind) has changed since it was described in the manual Universal Communications I/O Adapter Programming (R109). This file determines the order in which UCOMM object modules are bound, their offsets, and their special attributes. Changes have been introduced as recently as VOS Release 12.4.0. If you are referencing data in the binder control file, you must merge your existing binder control file with the most recent one or note its changes. For information about the UCOMM Programming Kit, see the manual Universal Communications I/O Adapter Programming (R109). Note, however, that because this manual does not include recent changes to the file, you must examine the ucomm_fw.bind file in the >system>ucomm>user_src directory for the most recent changes. TCP/IP Products --------------- Beginning in VOS Release 14.1.0, VOS supports two TCP/IP products: STCP and OS TCP/IP. The introduction of STCP enables VOS to provide a STREAMS- SRB: VOS Release 14.5.0 (R914) 5-12 TCP/IP Products based TCP/IP product while it continues to support the non-STREAMS OS TCP/IP product. This section discusses the following topics. o ``General Requirements for STCP and OS TCP/IP" o ``Overview of STCP" o ``Changes to OS TCP/IP" For information about additional changes in STCP functionality beginning in VOS Release 14.4.0, see ``STCP and TCP Wrappers Functionality" and ``STCP and POSIX.1 Compliance" later in this chapter. General Requirements for STCP and OS TCP/IP -------------------------------------------- This section describes requirements that apply to both STCP and OS TCP/IP. This section discusses the following: o ``Running Both STCP and OS TCP/IP on the Same Module" o ``Network Interfaces and Required Drivers" Running Both STCP and OS TCP/IP on the Same Module ************************************************** If necessary, you can configure the module to run STCP and OS TCP/IP simultaneously, but certain restrictions apply. (Simultaneously running both products is considered an interim solution.) For example: o The module_start_up.cm command macro can define only one TCP/IP command library path for the module. Be careful when you specify commands, device names for network interfaces, and other information that could apply to (or potentially be used by) either protocol stack. Make sure that you specify the appropriate path names for commands issued from files, such as module_start_up.cm and/or the STCP start_stcp.cm. Some commands have the same name for STCP and OS TCP/IP, but they function differently. o STCP and OS TCP/IP do not share components. Both may have similarly named components that perform the same functions, such as TELNET, FTP, and certain administration tools, but each .pm will work only with either the STCP or OS TCP/IP stack. For example, the TELNET client in (master_disk)>system>stcp>command_library can make outbound connections only through interfaces configured for the STCP stack, configured by means of the ifconfig command in start_stcp.cm. Similarly, the STCP version of netstat will report only information SRB: VOS Release 14.5.0 (R914) 5-13 TCP/IP Products about STCP routes and sockets. To handle inbound TELNET connections received on an STCP interface, you must run the STCP TELNET server (telnetd), not the OS TCP/IP TELNET server (OS TELNET or the MST server). In addition, STCP requires the tli_term access layer loaded by STREAMS; it will not handle the telnet_al access layer that must be explicitly loaded for OS TCP/IP's OS TELNET. A list of the program module names used by both STCP and OS TCP/IP follows. telnet.pm, ftp.pm, inetd.pm, netstat.pm, route.pm, ifconfig.pm, ping.pm, packet_monitor.pm, arp.pm, tftp.pm o STCP and OS TCP/IP must run over different network interfaces. Each network interface must have a VOS device entry based on the chosen protocol stack and must be configured for the chosen protocol stack using the procedures required by that protocol stack. (For example, each STCP network interface must be defined with an STCP ifconfig command in the start_stcp.cm command macro.) o The two TCP stacks will appear to be different hosts on the network. STCP and OS TCP/IP have different configuration requirements and procedures. For additional information about the requirements for running both products on the module, see the VOS STREAMS TCP/IP Migration Guide (R418). Network Interfaces and Required Drivers **************************************** To support either STCP or OS TCP/IP in VOS Release 14.1.0 and later, you must use one or more of the network interfaces and the required drivers that Table 5-1 describes. Table 5-1. The Network Interfaces and Drivers Required to Support STCP or OS TCP/IP -------------------------------------------------------------------------- | Network Interface : Required Drivers : Description | |------------------------------------------------------------------------| | K470-00 or K470- : SDLMUX and the : Provides a 10- or 100-Mbps | | 10 I/O Controller : RENET driver : Ethernet network interface | | with the U713 : : supporting only STCP on 6- | | 10/100-Mbps : : and 12-slot Continuum- | | Ethernet PMC cards : : series modules | |------------------------------------------------------------------------| | K470-10 I/O : SDLMUX and the : Provides a 1 gigabit-per- | | Controller with : GENET driver : second (Gbps) Ethernet | SRB: VOS Release 14.5.0 (R914) 5-14 TCP/IP Products | the U714 gigabit : : interface supporting only | | Ethernet PMC cards : : STCP on 6- and 12-slot | | : : Continuum-series modules | |------------------------------------------------------------------------| | K460 : DLMUX : Provides a 10- or 100-Mbps | | SCSI/Ethernet I/O : : Ethernet network interface | | Controller : and : supporting STCP or OS | | : : TCP/IP on 6- and 12-slot | | : BDL driver : Continuum-series modules | |------------------------------------------------------------------------| | K450 : DLMUX : A 10-Mbps Ethernet network | | SCSI/Ethernet I/O : : interface supporting STCP | | Controller : and : or OS TCP/IP on 6- and 12- | | : : slot Continuum-series | | : BDL driver : modules | |------------------------------------------------------------------------| | K104 I/O Adapter : DLMUX : A 10-Mbps Ethernet card | | : : supporting STCP or OS | | : and : TCP/IP on XA/R-series | | : : modules or 6- and 12-slot | | : GDL driver : Continuum-series modules | -------------------------------------------------------------------------- Note: When you add or delete IP multicast addresses for a K104 I/O adapter, you will receive GDL error messages in the syserr_log. Similarly, when you add or delete IP multicast addresses for a duplexed K460 I/O controller, you will receive failover error messages. In both situations, the interface is still working correctly, but it has been open and closed to register/deregister IP multicast addresses to the specific interfaces. For the K470 I/O controller with the Ethernet PMC cards, SDLMUX enables you to configure two network interfaces of the same type as partners. To enable the functionality of level-2 IP multicasting, you must configure partnered or simplexed Ethernet PMC cards as members of SDLMUX groups. For the K460, K450, and the K104 interfaces, the required DLMUX enables you to configure two network interfaces of the same type as partners. The partners must be running the same protocol stack. For complete information about configuring SDLMUX and DLMUX as well as the supported network interfaces and their device drivers, see the following manuals. o VOS Data-Link Multiplexer Administrator's Guide (R425) o Product Configuration Bulletin: K104 I/O Adapter Using the GDL Driver (R426) o Product Configuration Bulletin: K450 and K460 SCSI/Ethernet I/O SRB: VOS Release 14.5.0 (R914) 5-15 TCP/IP Products Controllers (R428) o Product Configuration Bulletin: U713 and U714 Ethernet PMC Cards (R441) o Continuum Series 600 and 1200: PMC-Card Installation Guide (R443) Overview of STCP ---------------- STCP is a STREAMS-based implementation of the standard TCP/IP family of protocols for Stratus modules running VOS. Unlike OS TCP/IP, STCP functions within a standard STREAMS environment. You can configure STCP to run on an XA/R-series module or a 6- or 12-slot Continuum module. STCP does not run on XA2000-series modules. STCP supports a number of standard TCP/IP applications and relies on VOS device drivers and Stratus communications hardware to support a standard LAN architecture, such as Ethernet. It also provides a standard socket programming interface. STCP has the following features. o It offers a complete STREAMS-based protocol stack with kernel- loadable and unloadable drivers. For more information, see the VOS STREAMS TCP/IP Administrator's Guide (R419). o It simplifies configuration by relying on STREAMS to load the components in the protocol stack and any related STREAMS driver used by STCP. o It provides a wide range of applications, such as the Simple Network Management Protocol (SNMP) agent. (Stratus does not currently provide an SNMP manager.) You can easily modify STCP to support additional standard applications. o It supports variable-length subnets (VLSN), which provide flexibility in configuring subnet masks. o It supports level-1 and level-2 IP multicasting (send and receive). Note, however, that XA/R-series modules support IP multicast level 1 but do not support IP multicast level 2. o It supports Open StrataLINK. o It consists of one product that includes the protocol stack, the utilities, and the programming interface, unlike OS TCP/IP, which consists of three separately purchased products: OS TCP/IP Protocol SRB: VOS Release 14.5.0 (R914) 5-16 TCP/IP Products Support (the base product), OS TCP/IP Utilities, and OS TCP/IP Application Support. o Beginning in VOS Release 14.4.0, STCP incorporates TCP wrappers functionality. For complete information about this functionality and how to configure it, see ``STCP and TCP Wrappers Functionality" later in this chapter. o Beginning in VOS Release 14.5.0, the default inetd daemon complies with the IEEE POSIX.1 standard. (In VOS Release 14.4.0, the default inetd daemon is not POSIX.1-compliant; instead, STCP in VOS Release 14.4.0 includes the inetd_posix daemon.) For complete information about this functionality, see ``STCP and POSIX.1 Compliance" later in this chapter. For more information about STCP, see the following manuals. o VOS STREAMS TCP/IP Migration Guide (R418) o VOS STREAMS TCP/IP Administrator's Guide (R419) o VOS STREAMS TCP/IP Programmer's Guide (R420) o VOS STREAMS TCP/IP User's Guide (R421) For additional information about STCP requirements, see ``General Requirements for STCP and OS TCP/IP" earlier in this chapter. STCP Administration ******************* This section discusses the following changes in the administration of STCP. o ``Changes to the start_stcp.cm Command Macro" o ``Changes to the stop_stcp.cm Command Macro" o ``New Arguments for the ftpd Daemon in STCP" o ``New Arguments for the telnetd Daemon" o ``The inetd Daemon" o ``Changes to the inetd.conf File" o ``Giving Access to the User nobody.nobody" Beginning in VOS Release 14.4.0, STCP includes changes for TCP wrappers functionality and POSIX.1 compliance. For complete information on changes SRB: VOS Release 14.5.0 (R914) 5-17 TCP/IP Products to STCP administration for this new functionality, see ``STCP and TCP Wrappers Functionality" and ``STCP and POSIX.1 Compliance" later in this chapter. Changes to the start_stcp.cm Command Macro ****************************************** The following changes in the start_stcp.cm command macro support POSIX.1 compliance: the STCP compatibility library, OSPF, and SDLMUX. o In VOS Release 14.5.0, the start_stcp.cm command macro no longer includes the start_process command to start the inetd daemon process; rather, the start_inetd.cm command macro includes the start_process command to start the inetd daemon process. o Beginning in VOS Release 14.3.0, the following entries in the start_stcp.cm command macro ensure that a hostid file exists to support the hostid function in the STCP compatibility library. & check for the hostid file &if ^ (exists (master_disk)>system>stcp>hostid -file) &then !create_file (master_disk)>system>stcp>hostid -file !give_access write hostid o The following example shows commented entries that appear in the start_stcp.cm command macro beginning in VOS Release 14.4.0. To start the OSPF daemon on a module, remove the ampersand (&) and spaces before the start_process and !display_line commands in the start_stcp.cm command macro on the module. & *********************OSPFD****************************** start_process -privileged -process_name ospfd &+ -output_path (master_disk)>system>stcp>logs>ospfd.out &+ `(master_disk)>system>stcp>command_library>ospfd>system> stcp>ospfdconf' !display_line OSPFD . . SRB: VOS Release 14.5.0 (R914) 5-18 TCP/IP Products . o Beginning in VOS Release 14.3.0, the start_stcp.cm command macro must contain the dlmux_admin command (previously, the module_start_up.cm command macro included the dlmux_admin command). In the start_stcp.cm command macro, the dlmux_admin command with the init_sdlmux argument must appear before the ifconfig command. The following excerpt from the start_stcp.cm command macro (in the (master_disk)>system>stcp>templates>src directory) illustrates these changes. & ******************PMC Enet Cards******************* & If you are running PCI-based Mezzanine cards (PMC cards) & on K470 I/O controllers, and you have configured the PMC & cards as duplexed in SDLMUX groups, you need to issue the & dlmux_admin command below for each group, where & is the name of one of two devices from the & group (as specified & in the devices.tin file). The & device that you specify here will be the active device; & the other device in the group will automatically become & the partner (or backup) device. & Use ifconfig command to add sdlmux group as shown below: & & Example: #sdlmux.m1.8.1 <- sdlmux group name & #renet.m1.8.1 <- PMC card in slot 8/1 (active) & #renet.m1.9.1 <- PMC card in slot 9/1 (partner) & 89.10.10.1 <- Sample ip address & & (master_disk)>system>command_library>dlmux_admin &+ & #renet.m1.8.1 init_sdlmux & (master_disk)>system>stcp>command_library>ifconfig &+ & #sdlmux.m1.8.1 89.10.10.1 -netmask 0xffffff00 -add SRB: VOS Release 14.5.0 (R914) 5-19 TCP/IP Products & & Note: See stop_stcp.cm for uninitializing a SDLMUX group Changes to the stop_stcp.cm Command Macro ***************************************** Beginning in VOS Release 14.3.0, the stop_stcp.cm command macro contains a command line to support OSPF. In the STCP section of the command macro, the following line stops the OSPF daemon process: stop_process ospfd -user *.* -no_ask In VOS Release 14.5.0, the stop_stcp.cm command macro no longer includes the stop_process command to stop the inetd daemon process; rather, the stop_inetd.cm command macro includes the stop_process command to stop the inetd daemon process. New Arguments for the ftpd Daemon in STCP ***************************************** The ftpd daemon has the following new arguments. o -security_check_file o -allow_any_port o -tcpwrapper_check o -numeric -security_check_file security_file Beginning in VOS Release 14.3.0, this argument prevents unauthorized users from logging in to a remote host with FTP. If you also specify the -log argument, the log file records the following information. - if a user with null access attempts to log in via FTP - if the ftpd daemon cannot find security_file The value of security_file should be a path name to an empty file, which will become the security file. The access control lists on the security file control access to the system via FTP. For example, if a user logging in via FTP has non-null access to the file, the user is granted access to the system and can successfully log in. If the user has null access to the file, the user receives an error message and the FTP connection is terminated. SRB: VOS Release 14.5.0 (R914) 5-20 TCP/IP Products You can create a list of allowed users by setting null access for *.* and giving read access for the specific users who are allowed access. You can create a list of denied users by giving read access to *.* and setting null access to the list of specific users who are denied access. You can specify users as user_name.group_name, user_name.*, or *.group_name. The ftpd daemon determines access based on standard access-control-list processing as described in the VOS Commands User's Guide (R089). If the ftpd daemon cannot find the security file, the user is denied access to the system. If you want to start the ftpd daemon process with security enabled, issue the following command. start_process -output_path (master_disk)>system>stcp>logs>ftpd.out +'(master_disk)>system>stcp>command_library>ftpd -security_check_file +%se_j14#m14_d02>SW>Noah_Smith>ftp_security' -privileged -process_name ftpd7 Note: Do not enter the plus (+) sign that appears in this example; it is a line-continuation character. -allow_any_port Beginning in VOS Release 14.3.0, this argument checks that the IP address in the FTP protocol command PORT matches the client's IP address. By default, ftpd does not perform this check. The -allow_any_port argument provides protection against security breaches by detecting: - Whether the TCP/IP address in the PORT command is not from the originator - Whether the PORT number is less than 1024 You can use the -allow_any_port argument with the following external variables of the ftpd daemon. - allow_any_port$--This variable is set to 1 if you specify the - allow_any_port argument. By default, it is set to 0. If you use proxy servers, you must set this variable or the proxy servers will not function properly. - warn_on_port_misuse$--If this variable is set to 1 (the default) and an incorrect PORT command is received when you are running ftpd, the following message is returned. SRB: VOS Release 14.5.0 (R914) 5-21 TCP/IP Products `refused PORT (TCP/IP_address) from (client_name)' - warn_when_allow_port$--If this variable is set to 1 (the default) and you specify the -allow_any_port argument, the following message is returned. `Warning: ftpd invoked with -allow_any_port' You can use the set_external_variable command to set the preceding external variables, as shown in the following example. set_external_variable warn_on_port_misuse$ -in >system>stcp>command_library>ftpd.pm -to 1 -type integer For more information about the set_external_variable command, see the VOS Commands Reference Manual (R098). -tcpwrapper_check Beginning in VOS Release 14.4.0, this argument enables the ftpd daemon to authenticate each client that requests an FTP connection by checking the client's access as configured in the hosts.allow and hosts.deny files. As part of authenticating client requests, the daemon logs messages to the log files tcpdallow and tcpddeny. To enable authentication, specify the value yes. By default (the value no), the ftpd daemon does not authenticate clients and does not log messages in the log files. Authenticating client access is part of TCP wrappers functionality. For more information about this functionality, see ``STCP and TCP Wrappers Functionality" later in this chapter. -numeric Beginning in VOS Release 14.4.0, this argument enables the ftpd daemon to check only the client's IP address and to ignore the host name when the daemon authenticates client access. By checking only the numeric IP address and ignoring the host name, the daemon can authenticate the client more quickly. By default (the value yes), the ftpd daemon checks only the client's IP address. The value that you specify for the -numeric argument takes effect only when the value of the -tcpwrapper_check argument is yes. To enable the daemon to check the host name, specify the value no for the -numeric argument when you specify the value yes for the - tcpwrapper_check argument. If you specify the value no for the - tcpwrapper_check argument, the -numeric argument has no effect. Authenticating client access is part of TCP wrappers functionality. SRB: VOS Release 14.5.0 (R914) 5-22 TCP/IP Products For more information about this functionality, see ``STCP and TCP Wrappers Functionality" later in this chapter. New Arguments for the telnetd Daemon ************************************ The telnetd daemon has the following new arguments: o -tcpwrapper_check o -numeric -tcpwrapper_check Beginning in VOS Release 14.4.0, this argument enables the telnetd daemon to authenticate each client that requests a TELNET connection by checking the client's access as configured in the hosts.allow and hosts.deny files. As part of authenticating client requests, the daemon logs messages to the log files tcpdallow and tcpddeny. To enable authentication, specify the value yes. By default (the value no), the telnetd daemon does not authenticate clients and does not log messages in the log files. Authenticating client access is part of TCP wrappers functionality. For more information about this functionality, see ``STCP and TCP Wrappers Functionality" later in this chapter. -numeric Beginning in VOS Release 14.4.0, this argument enables the telnetd daemon to check only the client's IP address and to ignore the host name when the daemon authenticates client access. By checking only the numeric IP address and ignoring the host name, the daemon can authenticate the client more quickly. By default (the value yes), the telnetd daemon checks only the client's IP address. The value that you specify for the -numeric argument takes effect only when the value of the -tcpwrapper_check argument is yes. To enable the daemon to check the host name, specify the value no for the -numeric argument when you specify the value yes for the - tcpwrapper_check argument. If you specify the value no for the - tcpwrapper_check argument, the -numeric argument has no effect. Authenticating client access is part of TCP wrappers functionality. For more information about this functionality, see ``STCP and TCP Wrappers Functionality" later in this chapter. The inetd Daemon SRB: VOS Release 14.5.0 (R914) 5-23 TCP/IP Products **************** Beginning in VOS Release 14.5.0, the default inetd daemon is POSIX.1- compliant, and the inetd_posix daemon, which was introduced in VOS Release 14.4.0, no longer exists. For information about STCP and POSIX.1 compliance, see ``STCP and POSIX.1 Compliance" later in this chapter. Changes to the inetd.conf File ****************************** The STCP changes introduced in VOS Release 14.4.0 for TCP wrappers functionality and POSIX.1 compliance include changes in the inetd.conf file. For complete information about inetd.conf file changes, see ``The inetd.conf File and TCP Wrappers Functionality" and ``The inetd.conf File" later in this chapter. Giving Access to the User nobody.nobody *************************************** The STCP system administrator must give the user nobody.nobody appropriate access to the directories (master_disk)>system>stcp>tftp_default and (master_disk)>system>stcp>logs. o (master_disk)>system>stcp>tftp_default--The STCP system administrator must give the user nobody.nobody modify access to this directory if clients need to write files to this directory on the server. The tftpd daemon enables clients to read files in, and write files to, directories on the server only when the user nobody.nobody has proper access. Clients can read only the files to which the user nobody.nobody has read access. Clients can write files only to the directories to which the user nobody.nobody has modify access. When a client writes a file to the server but does not specify a directory for the file, the tftp daemon places that file in the directory (master_disk)>system>stcp>tftp_default if the user nobody.nobody has modify access to it. o (master_disk)>system>stcp>logs--This directory includes the tftplog and bootplog log files. The tftpd daemon makes log-file entries to the tftplog log file, and the bootpd daemon makes log-file entries to the bootplog log file. In order for these daemons to write messages in these log files, the STCP system administrator must give the user nobody.nobody modify access to the (master_disk)>system>stcp>logs directory. The STCP system administrator must also give the user nobody.nobody write access to the log files (tftplog and bootplog). SRB: VOS Release 14.5.0 (R914) 5-24 TCP/IP Products OSPF Support ************ Beginning in VOS Release 14.3.0, VOS supports the Open Shortest Path First (OSPF) routing protocol on VOS modules that are running STCP. The OSPF daemon provides this support, and the ospfd command starts the process. The omon command allows you to monitor OSPF routers. The VOS STREAMS TCP/IP Administrator's Guide (R419) provides the information you need to implement OSPF on your VOS module. STCP Programming **************** This section discusses the following topics related to STCP programming changes. o ``Programming Support for POSIX.1 Compliance" o ``New stcp_calls Requests" o ``Increased Number of IP Multicast Addresses" Programming Support for POSIX.1 Compliance ****************************************** Beginning in VOS Release 14.3.0, the support added to provide POSIX.1 compliance impacts the STCP programming environment in the following ways. o Some header files have been removed from subdirectories of (master_disk)>system>stcp>include_library, including the time.h and types.h files in the sys subdirectory. o The VOS Standard C library now provides support for some header files and for the select and select_with_events functions that the STCP library previously supported. o VOS STCP now supports the fork function in addition to the stcp_spawn_child_process function. For more information about the fork function, see the file posix.doc (in the directory (master_disk)>system>doc>posix). For more information about the stcp_spawn_child_process function, see the VOS STREAMS TCP/IP Programmer's Guide (R420). o Stratus recommends that you run the check_posix command if your system is running a VOS STCP application. This command checks that SRB: VOS Release 14.5.0 (R914) 5-25 TCP/IP Products the current module's configuration meets constraints imposed by the VOS POSIX.1 implementation. For more information about the check_posix command, see the file posix.doc (in the (master_disk)>system>doc>posix directory). The VOS STREAMS TCP/IP Programmer's Guide (R420) describes the current directory structure and the header files in the directories. Also, for more information about how changes to VOS C and POSIX affect STCP applications, see the file stcp_and_posix.doc (in the directory (master_disk)>system>doc>posix). New stcp_calls Requests *********************** Beginning in VOS Release 14.3.0, the stcp_calls command now supports the following new requests. -------------------------------------------------------------------------- | fcntl : gethostbyaddr : gethostbyname : gethostent | |------------------------------------------------------------------------| | getnetbyaddr : getnetbyname : getnetent : getprotobyname | |------------------------------------------------------------------------| | getprotobynumber : getprotoent : getservbyname : getservbyport | |------------------------------------------------------------------------| | getservent : inet_addr : inet_lnaof : inet_makeaddr | |------------------------------------------------------------------------| | inet_netof : inet_network : inet_ntoa : sethostent | |------------------------------------------------------------------------| | setnetent : setprotoent : setservent : | -------------------------------------------------------------------------- For more information about the stcp_calls command, see the VOS STREAMS TCP/IP Programmer's Guide (R420). Increased Number of IP Multicast Addresses ******************************************* Beginning in VOS Release 14.5.0, STCP supports a maximum of 256 IP multicast addresses per socket. (Prior to VOS Release 14.5.0, the maximum was 8.) Note: You can use IP multicast only with UDP sockets of the type SOCK_DGRAM. You cannot use IP multicast with TCP sockets or with raw sockets. Only the K470 I/O controller (with the U713 or U714 PMC card) supports a maximum of 256 IP multicast addresses per socket. SRB: VOS Release 14.5.0 (R914) 5-26 TCP/IP Products Other STCP Programming Changes ****************************** Beginning in VOS Release 14.3.0, a list of additional STCP programming changes follows. o Two header file directories have been removed: - >system>stcp>include_library>protocols - >system>stcp>include_library>snet o The following header files have been removed. - >system>stcp>include_library>resolv.h - >system>stcp>include_library>arpa>bootp.h - >system>stcp>include_library>arpa>nameser.h - >system>stcp>include_library>net>route.h - >system>stcp>include_library>netinet>if_ether.h - >system>stcp>include_library>netinet>igmp.h - >system>stcp>include_library>netinet>igmp_var.h - >system>stcp>include_library>netinet>ip_mroute.h - >system>stcp>include_library>sys>bsd_file.h o Beginning in VOS Release 14.5.0, the KEEPALIVE socket option has changed to comply with RFC1122. You can use the linger structure to set the KEEPALIVE socket option on or off, or to specify a time interval for the initial KEEPALIVE probe. For more information, see the errata file update for the VOS STREAMS TCP/IP Programmer's Guide (R420). Enhanced Support for Migrating OS TCP/IP Applications ***************************************************** Beginning in VOS Release 14.3.0, VOS provides an STCP compatibility library that eases the task of migrating OS TCP/IP applications to run over an STCP protocol stack. In many cases, you can migrate your application by binding it with the STCP compatibility and standard libraries. The compatibility library provides objects for many functions in OS TCP/IP that do not have identically-named counterparts in the STCP SRB: VOS Release 14.5.0 (R914) 5-27 TCP/IP Products standard library. These functions return the VOS-style error codes used by the OS TCP/IP library. For more information, see the VOS STREAMS TCP/IP Migration Guide (R418). In addition, the get_socket_event function has been added to the STCP standard libraries to ease the migration of STCP to OS TCP/IP applications that use that function. For more information about the get_socket_event function, see the VOS STREAMS TCP/IP Programmer's Guide (R420). Changes to the NFS Facility *************************** The NFS facility has been modified to interact with STCP. If you wish to use NFS with STCP, you must purchase NFS Version 1.3. For more information about these changes, see the Software Release Bulletin: NFS and RPC Release 1.3 (R252). Changes to OS TCP/IP --------------------- This section summarizes the following basic configuration requirements and changes to OS TCP/IP. o ``Basic Configuration Requirements" o ``Change in the Location of Lower-Level Drivers" o ``Summary of Changes to OS TCP/IP Since VOS Release 13.0" Basic Configuration Requirements ********************************* To support OS TCP/IP in VOS Release 14.0.0 or later, you must use one or more of the network interfaces and required drivers described in Table 5- 2. You can configure any of these types of network interfaces as partners to ensure hardware failover if the partner that handles communications I/O fails. Table 5-2. Network Interface and Drivers That Support OS TCP/IP -------------------------------------------------------------------------- | Network Interface : Required Drivers : Description | |------------------------------------------------------------------------| | K460 I/O : Data-Link : A 10- or 100-Mbps | | controller : Multiplexer : SCSI/Ethernet controller | | : : that runs OS TCP/IP on | | : and : Continuum-series modules | SRB: VOS Release 14.5.0 (R914) 5-28 TCP/IP Products | : : (for more information, see | | : BIO Data-Link : the manual Product | | : (BDL) driver : Configuration Bulletin: | | : : K450 and K460 | | : : SCSI/Ethernet I/O | | : : Controllers (R428)) | |------------------------------------------------------------------------| | K450 I/O controller: Data-Link : A 10-Mbps SCSI/Ethernet | | (for existing : Multiplexer : controller that runs OS | | configurations : : TCP/IP on Continuum-series | | only) : and : modules (for more | | : : information, see the | | : BDL driver : manual Product | | : : Configuration Bulletin: | | : : K450 and K460 | | : : SCSI/Ethernet I/O | | : : Controllers (R428)) | |------------------------------------------------------------------------| | K104 I/O adapter : Data-Link : A 10-Mbps Ethernet card | | : Multiplexer : that runs OS TCP/IP on | | with the : : XA/R- or Continuum-series | | : and : modules (for more | | K600 Type-B : : information, see the | | : Generic Data-Link : manual Product | | I/O processor : (GDL) driver : Configuration Bulletin: | | : : K104 I/O Adapter Using the | | : : GDL Driver (R426)) | -------------------------------------------------------------------------- Note: The required Data-Link Multiplexer enables you to configure two network interfaces of the same type as partners. Table 5-2 lists the different types of network interfaces that you can configure as partners (the partners must be running OS TCP/IP). The dlmux_admin command, located in the directory (master_disk)>system>command_library as of VOS Release 14.0.0, enables you to manage the partnered network interfaces. Change in the Location of Lower-Level Drivers ********************************************** Beginning in VOS Release 14.0.0, the lower-level VOS drivers required for OS TCP/IP (the Data-Link Multiplexer, the GDL driver, and the BDL driver) reside in the (master_disk)>system>kernel_loadable_library directory. Prior to VOS Release 14.0.0, these drivers were located in the (master_disk)>system>tcp_os directory. To load these drivers automatically at each bootload, you must issue the following commands from the module_start_up.cm command macro. load_kernel_program >system>kernel_loadable_library>gdl driver SRB: VOS Release 14.5.0 (R914) 5-29 TCP/IP Products load_kernel_program >system>kernel_loadable_library>bdl driver load_kernel_program >system>kernel_loadable_library>dlmux driver These drivers should be loaded before you load the OS TCP/IP components. The module_start_up.cm command macro shipped with VOS Release 14.0.0 and later reflects the order in which the drivers and the OS TCP/IP components must be loaded. For more information about the configuration procedures for OS TCP/IP, see the VOS OS TCP/IP Administrator's Guide (R223). New Arguments for the ftpd Daemon in OS TCP/IP ********************************************** The ftpd daemon has the following new arguments. o -security_check_file--This argument is new for VOS Release 14.3.0. For more information about this argument, see ``New Arguments for the ftpd Daemon in STCP" earlier in this chapter. Although this argument is described for STCP, it also applies to OS TCP/IP. o -allow_any_port--This argument is new for VOS Release 14.3.0. For more information about this argument, see ``New Arguments for the ftpd Daemon in STCP" earlier in this chapter. Although this argument is described for STCP, it also applies to OS TCP/IP. o -numeric--This argument is new for VOS Release 14.5.0. If you specify the value yes for this argument, the ftpd daemon logs the client's IP address, instead of the host name, in the system error log. By logging only the numeric IP address and ignoring the host name, the daemon can authenticate the client more quickly. By default, the ftpd daemon logs the client's host name in the system error log. For more information about the ftpd daemon, see the VOS OS TCP/IP Administrator's Guide (R223). Summary of Changes to OS TCP/IP Since VOS Release 13.0 ****************************************************** Table 5-3 summarizes the changes made to OS TCP/IP and its related software since VOS Release 13.0. For more information about managing OS TCP/IP, see the VOS OS TCP/IP Administrator's Guide (R223). Table 5-3. Summary of OS TCP/IP Changes (Page 1 of 2) ------------------------------------------------------------------------- SRB: VOS Release 14.5.0 (R914) 5-30 TCP/IP Products | : Release : | | : Introduci : | | : ng the : | | : Change : | | Change : : Description | |-----------------------------------------------------------------------| | Introduction : 13.2.0 : Required driver and administrative | | of Data-Link : on : command for managing network | | Multiplexer : Continuum : interfaces. This driver permits | | and : ; 13.3.0 : hardware failover for network | | dlmux_admin : on : interfaces of the same type configured | | command : XA2000 : as partners. The device entries for | | : and XA/R : partners require the -partner argument | | : : in the parameters field of the | | : : devices.tin file. Beginning in VOS | | : : Release 14.0.0, the Data-Link | | : : Multiplexer and related GDL and BDL | | : : drivers are loaded from the | | : : (master_disk)>system>kernel_loadable_li | | : : brary directory. For VOS Releases | | : : 13.2.0 and 13.3.0, these drivers are | | : : loaded from the | | : : (master_disk)>system>tcp_os directory. | |-----------------------------------------------------------------------| | Support for : 13.2.0 : Continuum main chassis boards | | K450 and K460 : : supporting SCSI and Ethernet I/O. The | | I/O : : K450 I/O controller supports one 10- | | controllers : : Mbps connection to a 10Base-5, 10Base- | | : : 2, or 10Base-T Ethernet LAN; the K460 | | : : I/O controller supports connections to | | : : 10- or 100-Mbps Ethernet LANs. Stratus | | : : recommends that you partner either of | | : : these board types to ensure load | | : : sharing of SCSI and Ethernet I/O. The | | : : devices.tin file entry for a K450 or | | : : K460 I/O controller must specify | | : : bio_enet in the device_type field and | | : : include the bio_port and bio_device | | : : fields. To specify line-speed and/or | | : : duplex settings in the device entry | | : : for the K460 I/O controller, use the - | | : : speed and -duplex arguments in the | | : : parameters field of the devices.tin | | : : file. | |-----------------------------------------------------------------------| | Support for : 13.2.0 : Required driver for the K450 and K460 | | the BDL driver : : I/O controllers. | |-----------------------------------------------------------------------| | Ethernet-to- : 13.2.0 : Enables a pair of K460 I/O controllers | | FDDI : : and U250 switches working with OS | SRB: VOS Release 14.5.0 (R914) 5-31 TCP/IP Products | switching : : TCP/IP to support remote I/O to an | | using the : : FDDI network. For more information | | U250 switch : : about the U250 switch, see the Product | | : : Configuration Bulletin: U250 Remote | | : : I/O Switch (R417). | |-----------------------------------------------------------------------| | Updated : 13.3.0 : Improved version of the command. | | packet_monitor : : | | command : : | |-----------------------------------------------------------------------| | Support for : 13.3.0 : Standard boot server that handles boot | | bootpd : : requests from diskless devices on the | | : : LAN. | |-----------------------------------------------------------------------| | Support for : 13.3.0 : Support for the Trivial File Transfer | | tftp and tftpd : : Protocol (TFTP) client and server. | | : : Works with bootpd to handle boot files. | |-----------------------------------------------------------------------| | Performance : 13.1.0 : VOS Release 13.1.0 introduced | | enhancements : and : performance enhancements related to | | : 13.2.0 : the replacement of the older OS TCP/IP | | : : adapter driver with the GDL driver on | | : : Continuum-series modules. VOS Release | | : : 13.2.0 provided performance | | : : enhancements over all previous | | : : releases and included support for | | : : directed interrupts. | |-----------------------------------------------------------------------| | New arguments : 14.3.0 : For a description of the new | | for ftpd : and : arguments, see ``New Arguments for the | | : 14.5.0 : ftpd Daemon in OS TCP/IP" earlier in | | : : this chapter. | ------------------------------------------------------------------------- STCP and TCP Wrappers Functionality ------------------------------------ Beginning in VOS Release 14.4.0, STCP includes TCP wrappers functionality, which provides authentication and logging capabilities that enable STCP to control client access to FTP and TELNET, and to any services that the inetd daemon starts (for example, BOOTP and TFTP). The following sections describe this functionality and how to configure it. o ``Overview of TCP Wrappers Functionality" o ``New and Changed Daemons and Files for TCP Wrappers Functionality" o ``Unsupported Features of TCP Wrappers" SRB: VOS Release 14.5.0 (R914) 5-32 STCP and TCP Wrappers Functionality o ``Configuring TCP Wrappers Functionality" o ``Troubleshooting TCP Wrappers" Note: If you configure TCP wrappers functionality on your STCP server, a client may experience a small delay in the FTP, TELNET, BOOTP, and TFTP services, which use this functionality. Note: For services that the inetd daemon starts (for example, BOOTP and TFTP), TCP wrappers functionality requires an inetd daemon that is POSIX.1-compliant. Beginning in VOS Release 14.5.0, the default inetd daemon is POSIX.1-compliant. No special procedures are necessary to implement the POSIX.1-compliant inetd daemon. (VOS Release 14.4.0 included the inetd_posix daemon as well as the default inetd daemon, which was not POSIX.1-compliant.) Overview of TCP Wrappers Functionality -------------------------------------- TCP wrappers functionality enables certain services (FTP, TELNET, and services that the inetd daemon starts) to authenticate and log client requests. This authentication and logging functionality is built into the ftpd daemon (for FTP requests) and the telnetd daemon (for TELNET requests). Services that the inetd daemon starts (for example, BOOTP and TFTP) require the tcpd daemon, which is new beginning in VOS Release 14.4.0. (The inetd daemon starts the services specified in the inetd.conf file.) When STCP receives an incoming client request, the appropriate daemon authenticates the client and logs the client request if you configure the daemon to do so. If, for example, a client requests FTP, the ftpd daemon authenticates the client and logs the request. If a client requests a service specified in the inetd.conf file, the tcpd daemon authenticates the client and logs the client request. The authenticating daemon checks two database files, hosts.allow and hosts.deny. The hosts.allow file lists clients with service daemons that can provide access to those clients; the hosts.deny file lists clients with service daemons that can deny access to those clients. If the authenticating daemon finds the client listed in the hosts.allow file with the appropriate service daemon, the authenticating daemon accepts the request. If the authenticating daemon does not find the client listed in the hosts.allow file with the appropriate service daemon, the authenticating daemon searches the hosts.deny file. If the authenticating daemon finds the client listed in the hosts.deny file with the appropriate service daemon, the authenticating daemon denies the client access--if the SRB: VOS Release 14.5.0 (R914) 5-33 STCP and TCP Wrappers Functionality client sent a TCP request, the authenticating daemon closes the connection; or if the client sent a User Datagram Protocol (UDP) request, the packet is dropped. If the authenticating daemon does not find the client listed in the hosts.deny file with the appropriate service daemon, the authenticating daemon accepts the request. The authenticating daemon also logs the connection request in the appropriate log file, tcpdallow or tcpddeny (in the directory (master_disk)>system>stcp>logs). TCP wrappers functionality also allows additional access checking with paranoid checks. When an authenticating daemon conducts a paranoid check, it conducts a reverse lookup of a client's IP address and host name. The authenticating daemon conducts a reverse lookup of the client's IP address and host name by using the resolv.conf file to contact a name server. The authenticating daemon separates the client's IP address and host name, and then uses the name server to check that the client's IP address matches the host name, and that the host name matches the IP address. If the IP address that the authenticating daemon received in the client request does not match the IP address listed with the name server, the daemon refuses the connection request; if the two IP addresses are identical, the daemon accepts the connection request. New and Changed Daemons and Files for TCP Wrappers Functionality ---------------------------------------------------------------- Stratus implements the TCP wrappers functionality with the following new and changed daemon and files. o a new networking daemon, tcpd, and its program module tcpd.pm in the directory (master_disk)>system>stcp>command_library o the new configuration files hosts.allow and hosts.deny in the directory (master_disk)>system>stcp o a new format for entries in the inetd.conf file--In this new format, the inetd daemon invokes the authenticating daemon tcpd, and then the tcpd daemon invokes the service daemon. (In the previous format, the inetd daemon directly invokes the service daemon.) See the VOS STREAMS TCP/IP Administrator's Guide (R419) for information about the new format. o new log files in the directory (master_disk)>system>stcp>logs: - tcpdallow--In this file, the tcpd daemon logs messages about client connection requests that it has accepted. - tcpddeny--In this file, the tcpd daemon logs messages about SRB: VOS Release 14.5.0 (R914) 5-34 STCP and TCP Wrappers Functionality client connection requests that it has denied. See the VOS STREAMS TCP/IP Administrator's Guide (R419) for examples of entries in these log files. If the log files tcpdallow and tcpddeny become larger than 256 blocks, VOS renames the files to tcpdallow.yy-mm-dd.hh-mm and tcpddeny.yy-mm-dd.hh-mm and starts new log files. (If you want to change the size at which log files become too large, you must contact the CAC.) Unsupported Features of TCP Wrappers ------------------------------------- The VOS implementation of TCP wrappers does not support the following features. o shell--Since VOS does not provide or support a shell command-line interface, the VOS implementation of TCP wrappers also does not support a shell command-line interface. o language extensions--The VOS implementation of TCP wrappers does not support language extensions in the hosts.allow and hosts.deny files. o tcpdchk program--The VOS implementation of TCP wrappers does not support the tcpdchk program (this program identifies common problems with the hosts.allow, hosts.deny, and inetd.conf files). Configuring TCP Wrappers Functionality -------------------------------------- You must configure STCP for the TCP wrapper functionality, as the following sections describe. o ``Configuring the Daemons" o ``The inetd.conf File and TCP Wrappers Functionality" o ``The hosts.allow and hosts.deny Database Files" Configuring the Daemons ************************ You must configure STCP daemons to authenticate client requests and to log information about these requests. SRB: VOS Release 14.5.0 (R914) 5-35 STCP and TCP Wrappers Functionality o ftpd--When you issue the ftpd command to start this daemon, specify the value yes for the -tcpwrapper_check argument. You can also specify a value for the -numeric argument when you specify a value for the -tcpwrapper_check argument. For information about these arguments, see ``New Arguments for the ftpd Daemon in STCP" earlier in this chapter. o telnetd--When you issue the telnetd command to start this daemon, specify the value yes for the -tcpwrapper_check argument. You can also specify a value for the -numeric argument when you specify a value for the -tcpwrapper_check argument. For information about these arguments, see ``New Arguments for the telnetd Daemon" earlier in this chapter. o inetd and tcpd--The inetd daemon starts the services specified in the inetd.conf file. Typically, these services include TFTP and BOOTP. When the inetd daemon receives a client request for one of its services, it invokes that service based on its entry in the inetd.conf file. In the inetd.conf file, you can configure the services BOOTP and TFTP so that the inetd daemon invokes the tcpd daemon first, rather than invoking the requested service directly. The tcpd daemon can then check the client's access to the requested service. Later in this chapter, ``The inetd.conf File and TCP Wrappers Functionality" provides detailed information about creating entries in the inetd.conf file to enable TCP wrappers functionality. The inetd.conf File and TCP Wrappers Functionality *************************************************** To enable TCP wrappers functionality in a service that the inetd daemon starts, the inetd daemon must first invoke the tcpd daemon to start the service rather than the inetd daemon invoking the service directly. When the tcpd daemon invokes a service, it checks the hosts.allow and hosts.deny files to determine if the client has access to the requested service. To enable the inetd daemon to first invoke the tcpd daemon to start the service, you must modify the service's entry in the inetd.conf file. See the VOS STREAMS TCP/IP Administrator's Guide (R419) for information about these entries in the inetd.conf file. Configuring the tcpd Daemon to Invoke the tftpd and bootpd Daemons ****************************************************************** The tftpd and bootpd daemons also provide examples of using the inetd.conf file to first invoke the tcpd daemon for access checking. See the VOS STREAMS TCP/IP Administrator's Guide (R419) for information about these SRB: VOS Release 14.5.0 (R914) 5-36 STCP and TCP Wrappers Functionality inetd.conf entries. The hosts.allow and hosts.deny Database Files ********************************************* The hosts.allow and hosts.deny files provide access information to daemons that authenticate client access. These daemons are telnetd, ftpd, and tcpd (for inetd). In the hosts.allow file, you list the path names of the daemons for services to which you want to provide client access; you also list the names of the clients to which you want to give access. In the hosts.deny file, you list the names of clients and the path names of the daemons for services to which you want to deny client access. For more information about the hosts.allow and hosts.deny files, see the VOS STREAMS TCP/IP Administrator's Guide (R419). Troubleshooting TCP Wrappers ----------------------------- If a client cannot establish a TELNET or FTP connection or a connection for one of the services configured with the tcpd daemon in the inetd.conf file, check the log file tcpddeny for a message stating that the client has been denied a connection because it is not listed in the hosts.allow file. You should also check the syserr_log.date file for messages indicating syntax errors in the hosts.allow or hosts.deny files. STCP and POSIX.1 Compliance ---------------------------- Beginning in VOS Release 14.5.0, the default inetd daemon is POSIX.1 compliant. (POSIX.1 is Part 1 of the IEEE POSIX standard. In VOS Release 14.4.0, the inetd_posix daemon is POSIX.1 compliant and the default inetd daemon is not.) Beginning in VOS Release 14.4.0, the tftpd and bootpd services changed as well, and these changes remain in subsequent VOS releases. The following sections describe these changes. o ``Overview of STCP Changes for POSIX.1 Compliance" o ``New Files for POSIX.1-Compliance" o ``New Arguments for the inetd and tftpd Daemons" o ``Changes to Existing Components of STCP" Overview of STCP Changes for POSIX.1 Compliance SRB: VOS Release 14.5.0 (R914) 5-37 STCP and POSIX.1 Compliance ------------------------------------------------ STCP incorporates changes for POSIX.1 compliance primarily in the inetd daemon; the tftpd and bootpd services have also changed. o inetd--The inetd daemon examines the user field in the inetd.conf file when it receives requests for services. In addition, the TCP services ECHO, DISCARD, and CHARGEN are internal services of the inetd daemon, while the TFTP and BOOTP services are external. The user root issues the start_inetd.cm command macro to start the inetd daemon. The inetd daemon then reads the inetd.conf configuration file, opens sockets for the services listed in that file, and then waits for incoming client connection requests. When the inetd daemon receives a client request for a TFTP or BOOTP connection, it invokes the appropriate program module (tftpd.pm or bootpd.pm) and starts a separate daemon for that service. o tftpd--The tftpd daemon handles multiple clients simultaneously and is external to the inetd daemon. Specifically, the tftpd daemon functions as a concurrent User Datagram Protocol (UDP) server, which means that it can simultaneously accept TFTP requests from multiple clients. The inetd daemon handles the initial client request for a TFTP connection. The inetd daemon then forks off a new process for this request, and this new process executes the tftpd.pm program module to run the tftpd daemon under the user nobody.nobody. Note: The tftpd daemon enables clients to read files in and write files to directories on the server only when the user nobody.nobody has the appropriate access. Clients can read only the files to which the user nobody.nobody has read access. Clients can write files to only the directories to which the user nobody.nobody has modify access. When a client writes a file to the server without specifying a directory, the tftpd daemon places the file in the (master_disk)>system>stcp>tftp_default directory, if the user nobody.nobody has modify permission to it. The tftpd daemon makes log-file entries to the file tftplog in the directory (master_disk)>system>stcp>logs. Note: The tftpd daemon can write messages to the log file tftplog only when the user nobody.nobody has modify access to the directory (master_disk)>system>stcp>logs and write access to the log file. o bootpd--The bootpd daemon is external to the inetd daemon. The inetd daemon handles the initial client connection for the BOOTP service, but then the inetd daemon executes the bootpd.pm program module and runs bootpd as a separate daemon, under the user nobody.nobody, SRB: VOS Release 14.5.0 (R914) 5-38 STCP and POSIX.1 Compliance external to the inetd daemon. The bootpd daemon makes log-file entries to the file bootplog in the directory (master_disk)>system>stcp>logs. Note: The bootpd daemon can write messages to the log file bootplog only when the user nobody.nobody has modify access to the directory (master_disk)>system>stcp>logs and write access to the log file. New Files for POSIX.1-Compliance --------------------------------- The changes in STCP for POSIX.1-compliance require the following new files. o ``The start_inetd.cm and stop_inetd.cm Command Macros" o ``The tftpd.pm and bootpd.pm Program Modules" o ``The inetd.conf File" o ``The inetd.conf File and the kill Command" o ``The tftplog Log File" The start_inetd.cm and stop_inetd.cm Command Macros *************************************************** The start_inetd.cm and stop_inetd.cm command macros (in the directory (master_disk)>system>stcp) start and stop the inetd daemon. You must be logged in as the user root to issue these command macros. The start_inetd.cm command macro follows: & **************************INETD********************* start_process -output_path (master_disk)>system>stcp>logs>inetd.out `(master_di +sk)>system>stcp>command_library>inetd' -privileged -root -process_name stcp_in +etd !display_line STCP_INETD ....... The stop_inetd.cm command macro follows: SRB: VOS Release 14.5.0 (R914) 5-39 STCP and POSIX.1 Compliance # This macro has to be run as root stop_process stcp_inetd -user root.root -no_ask The tftpd.pm and bootpd.pm Program Modules ****************************************** The tftpd.pm and bootpd.pm program modules in the STCP command library start the tftpd and bootpd daemons under the user nobody.nobody. The inetd daemon must start these daemons; they cannot run in stand-alone mode. The inetd.conf File ******************* The inetd.conf file contains entries that enable the user root to invoke the trivial services ECHO, DISCARD, DAYTIME, CHARGEN, and TIME. The file also contains, as comments, lines to invoke the bootpd and tftpd daemons and the swat administrative tool with or without TCP wrappers functionality. See the VOS STREAMS TCP/IP Administrator's Guide (R419) for information about the inetd.conf file and these entries. The inetd.conf File and the kill Command **************************************** When you configure changes in the inetd.conf file, you can activate those changes immediately by issuing the following kill command. kill -s HUP pid For the pid argument, specify the process ID of the inetd daemon process. To determine the process ID of the inetd daemon process, issue the following command. list_users -process_id The command output lists the process ID of all processes. For more information about the kill command, see the file posix.doc (in the directory (master_disk)>system>doc>posix). The tftplog Log File ******************** The tftplog log file, which resides in the directory (master_disk)>system>stcp>logs, replaces the tftpd.out log file. SRB: VOS Release 14.5.0 (R914) 5-40 STCP and POSIX.1 Compliance New Arguments for the inetd and tftpd Daemons --------------------------------------------- The inetd and tftpd daemons include new arguments. o The inetd daemon includes a new argument, -debug_level. The default inetd daemon creates the log file inetd.out (in the directory (master_disk)>system>stcp>logs) and logs messages to it. The argument -debug_level enables you to control the amount of information in the messages. The argument values are 0 and 1 (or any nonzero value). The value 0 specifies that the daemon logs messages about the following events. - services initially started - services started when the kill command is issued with the process ID of the inetd daemon process The value 1 (or any nonzero value) specifies that the daemon logs messages about all of the events that are included with the value 0, and also the following events. - connection requests - process ID of a child process that it forks - process ID of a child process that has completed its task - additional events For example, the following message, which indicates a request for the swat service though the swat service has not yet started, appears only when you specify the value 1. Someone wants swat o The tftpd daemon includes the -logging argument, which specifies that the tftpd daemon logs messages about TFTP transactions to the new log file tftplog (in the directory (master_disk)>system>stcp>logs). Changes to Existing Components of STCP -------------------------------------- SRB: VOS Release 14.5.0 (R914) 5-41 STCP and POSIX.1 Compliance POSIX.1 compliance requires changes to various components of STCP, as the following list describes. o In VOS releases prior to Release 14.5.0, the default inetd daemon manages bootptab and invokes program modules for the services ECHO, DISCARD, and CHARGEN. Beginning in VOS Release 14.5.0, the default inetd daemon does not perform these tasks: the services ECHO, DISCARD, and CHARGEN are internal services of the inetd daemon, while the services TFTP (which the tftpd.pm program module starts) and BOOTP (which the bootpd.pm program module starts) are external services that the inetd daemon starts. Thus, the following files are not part of the STCP command library for POSIX.1-compliant STCP: - chargen_stream.pm - discard_stream.pm - echo_stream.pm o The tftpd.out log file no longer exists; the log file tftpdlog replaces it. o The start_stcp.cm command macro does not start the inetd daemon; rather, the start_inetd.cm command macro starts it. o The stop_stcp.cm command macro does not stop the inetd daemon; rather, the stop_inetd.cm command macro stops it. The Data-Link Multiplexer: SDLMUX and DLMUX -------------------------------------------- Beginning in VOS Release 14.1.0, the Data-Link Multiplexer, a VOS communications driver, now provides the data-link interface between STCP and a device driver for Ethernet hardware. VOS now provides the following two versions of the VOS Data-Link Multiplexer. SDLMUX ****** The STREAMS Data-Link Multiplexer (SDLMUX) is a STREAMS driver that supports STREAMS device drivers for the peripheral component interconnect (PCI)-based Mezzanine cards (PMC cards). SDLMUX manages partnered and simplexed PMC cards and their device drivers. STREAMS loads SDLMUX automatically when it is needed. (SDLMUX is the program module sdlmux.cp.pm located in the directory (master_disk)>system>kernel_loadable_library.) SRB: VOS Release 14.5.0 (R914) 5-42 The Data-Link Multiplexer: SDLMUX and DLMUX Beginning in VOS Release 14.1.0, SDLMUX supports the RENET driver and the U713 PMC Card. RENET (renet.cp.pm) is a STREAMS driver that supports partnered U713 10/100-Mbps Ethernet PMC cards on Continuum-series modules. The U713 PMC card supports one Ethernet connection at either 10 Mbps or 100 Mbps (10Base-T or 100Base-TX). Beginning in VOS Release 14.5.0, U713 and U714 PMC cards support up to 1000 multicast group registrations per IP network. The previous limit was 14. Beginning in VOS Release 14.4.0, SDLMUX supports the GENET device driver and the U714 Gigabit Ethernet PMC Card. GENET (genet.cp.pm) is a STREAMS driver that supports U714 PMC cards on Continuum-series modules. The U714 PMC card is a high-performance, 1 gigabit-per-second (Gbps) Ethernet adapter that connects a Continuum series 600 or 1200 system to an Ethernet local area network (LAN) through a 1000Base-SX fiber-optic link. U713 and U714 PMC cards are located in slots on the K470 Communications I/O Controller, a main-chassis board that contains up to three PMC cards. Note, however, that the U714 PMC card requires the K470-10 I/O controller. K470 I/O controllers are not duplexed and do not themselves support failover; they are independent main-chassis boards. To ensure failover if a PMC card fails, you configure two PMC cards of the same type as partners (for example, two U714 PMC cards), where each card is on a different K470 I/O controller on the same module. Like SDLMUX, the RENET and GENET device drivers are loaded automatically by STREAMS; you do not need to explicitly load them on the module. Both the RENET and GENET device drivers are located in the directory (master_disk)>system>kernel_loadable_library. Table 5-4 lists the documentation that describes the STCP protocol stack, network interfaces, and LAN architectures that SDLMUX supports, as well as the documentation that describes how to configure and administer SDLMUX. Table 5-4. Documentation for Related SDLMUX Information ------------------------------------------------------------------------ | Topic : Documentation | |----------------------------------------------------------------------| | Configuring and : VOS Data-Link Multiplexer | | administering SDLMUX : Administrator's Guide (R425) | |----------------------------------------------------------------------| | Configuring STCP : VOS STREAMS TCP/IP Administrator's Guide | | : (R419) | |----------------------------------------------------------------------| | Creating device : VOS Data-Link Multiplexer | | entries for the : Administrator's Guide (R425) and Product | | Ethernet PMC cards and : Configuration Bulletin: U713 and U714 | SRB: VOS Release 14.5.0 (R914) 5-43 The Data-Link Multiplexer: SDLMUX and DLMUX | their drivers: the : Ethernet PMC Cards (R441) | | U714 PMC card with the : | | GENET driver or the : | | U713 PMC card with the : | | RENET driver : | |----------------------------------------------------------------------| | Release-specific : Online file stcp_interfaces.doc | | information about the : | | network interfaces and : in the directory (master_disk)>system>doc | | device drivers that : | | work with STCP : | |----------------------------------------------------------------------| | Installing the K470 : Continuum Series 600 and 1200: PMC-Card | | I/O controller, PMC : Installation Guide (R443) | | cards, and related : | | information : | ------------------------------------------------------------------------ DLMUX ***** The non-STREAMS Data-Link Multiplexer (DLMUX) supports non-STREAMS device drivers for the medium-specific communications hardware introduced in earlier VOS releases. It manages both partnered and simplexed network interfaces as well as their device drivers. (DLMUX is the program module dlmux.pm located in the directory (master_disk)>system>kernel_loadable_library as of VOS Release 14.1.0.) Since it is not a STREAMS driver and is not auto-loaded, DLMUX must be explicitly loaded on the module. (DLMUX also provides an interface for OS TCP/IP.) DLMUX communicates with the following lower-level device drivers. o Generic Data-Link (GDL) driver--This non-STREAMS device driver (gdl.pm) supports the K104 Ethernet Communications I/O Adapter, an Ethernet network interface. The K104 I/O adapter can be installed on XA/R-series modules and 6- and 12-slot Continuum modules configured with I/O processors. o BIO Data-Link (BDL) driver--This non-STREAMS device driver (bdl.pm) supports two SCSI/Ethernet I/O controllers as network interfaces on Continuum-series modules: the K450 Differential SCSI/Ethernet I/O Controller and the K460 Differential SCSI/Ethernet High-Speed I/O Controller. Both of these controllers can be installed on 6- and 12- slot Continuum modules. Like DLMUX, the GDL and BDL device drivers must be explicitly loaded on the module and are located in the (master_disk)>system>kernel_loadable_library directory as of VOS Release SRB: VOS Release 14.5.0 (R914) 5-44 The Data-Link Multiplexer: SDLMUX and DLMUX 14.1.0. Table 5-5 lists documentation that describes the protocol stacks (STCP and OS TCP/IP), network interfaces, and LAN architectures that DLMUX supports, as well as the documentation that describes how to configure and administer DLMUX. Table 5-5. Documentation for Related DLMUX Information ------------------------------------------------------------------------ | Topic : Documentation | |----------------------------------------------------------------------| | Configuring and : VOS Data-Link Multiplexer | | administering DLMUX : Administrator's Guide (R425) | |----------------------------------------------------------------------| | Configuring STCP : VOS STREAMS TCP/IP Administrator's | | : Guide (R419) | |----------------------------------------------------------------------| | Configuring OS TCP/IP : VOS OS TCP/IP Administrator's Guide | | : (R223) | |----------------------------------------------------------------------| | Creating device entries : Product Configuration Bulletin: K104 | | for the K104 I/O : I/O Adapter Using the GDL Driver (R426) | | adapter using the GDL : | | driver : | |----------------------------------------------------------------------| | Configuring device : Product Configuration Bulletin: K450 | | entries for the K450 : and K460 SCSI/Ethernet I/O Controllers | | and K460 I/O : (R428) | | controllers using the : | | BDL driver : | |----------------------------------------------------------------------| | Release-specific : Online file stcp_interfaces.doc in the | | information about the : directory (master_disk)>system>doc | | network interfaces and : | | device drivers that : | | work with STCP : | ------------------------------------------------------------------------ VOS Open StrataLINK -------------------- Beginning in VOS Release 13.3.0, VOS supports an improved implementation of Open StrataLINK. Open StrataLINK is the open-network implementation of StrataLINK and StrataNET, the two Stratus proprietary networks that establish VOS communications among Stratus modules and systems. Open StrataLINK works with one of the TCP/IP products that Stratus offers, OS TCP/IP or STREAMS TCP/IP (STCP). The combination of Open StrataLINK and SRB: VOS Release 14.5.0 (R914) 5-45 VOS Open StrataLINK TCP/IP enables Stratus modules and systems that were previously connected over proprietary StrataLINK local area networks (LANs) using proprietary software and hardware to communicate in a standard network environment using a standard LAN architecture, such as Ethernet. Note: Open StrataLINK requires either OS TCP/IP or STCP. (For information about these TCP/IP products, see ``TCP/IP Products" earlier in this chapter.) Before you configure modules for Open StrataLINK, you must correctly configure TCP/IP. For information about configuring OS TCP/IP, see the VOS OS TCP/IP Administrator's Guide (R223). For information about configuring STCP for Open StrataLINK, see the VOS STREAMS TCP/IP Administrator's Guide (R419) and the VOS Administrator's Guide for Open StrataLINK (R388); for a summary of the configuration procedures for using Open StrataLINK with STCP, see ``Open StrataLINK and STCP" later in this chapter. Note: Because Open StrataLINK works with a TCP/IP product and uses a standard network environment such as Ethernet, you typically need to work with your network administrator, whether you are using OS TCP/IP or STCP, during the TCP/IP portion of an Open StrataLINK configuration. Note: If you want to migrate from OS TCP/IP to STCP, see the VOS STREAMS TCP/IP Migration Guide (R418). Note: Customers with StrataNET licenses can receive a free upgrade to Open StrataLINK. If you are using OS TCP/IP, Open StrataLINK requires at least the base product of OS TCP/IP. OS TCP/IP consists of three separately purchased products: OS TCP/IP Protocol Support (the base product), OS TCP/IP Utilities, and OS TCP/IP Application Support. STCP is available as a separately purchased product set. It is included on the VOS release tape, not on its own tape. This section refers to the implementation of Open StrataLINK that is available beginning in VOS Release 13.3.0 as the current Open StrataLINK implementation. It refers to the implementation of Open StrataLINK that was available in previous VOS releases as the previous Open StrataLINK implementation. The current Open StrataLINK implementation has a new architecture, which is an improvement over the architecture of the previous Open StrataLINK implementation and from the architecture of proprietary StrataLINK. The new architecture contains the Open StrataLINK Net driver and OSL server processes, and requires the following: o new commands, including the osl_server command to start the OSL SRB: VOS Release 14.5.0 (R914) 5-46 VOS Open StrataLINK server and the osl_net_driver command to load the OSL Net driver o the Open StrataLINK configuration-table files (for example, the new_modules.table, new_systems.table, and new_backbone_systems.table files)--Some of the fields in these configuration-table files (for example, the socket_number field in the new_backbone_systems.table file) have changed in the current Open StrataLINK implementation. The current Open StrataLINK implementation is compatible with the previous Open StrataLINK implementation. However, note that all modules and systems connected via Open StrataLINK must have the current implementation in order to achieve better performance. For more information about the current Open StrataLINK implementation, see the VOS Administrator's Guide for Open StrataLINK (R388). The next section, ``Open StrataLINK Changes for VOS Release 13.2.0 and Later," discusses Open StrataLINK changes for VOS Release 13.2.0 and later. Open StrataLINK Changes for VOS Release 13.2.0 and Later -------------------------------------------------------- A system that includes Continuum-series modules can perform cross-system communications in one of three ways. o via Open StrataLINK--Bridge modules on the systems with which the Continuum-series modules directly communicate must also be running multisystem Open StrataLINK. o via cluster StrataLINK--The local bridge module must be an XA2000- series or XA/R-series module supporting StrataLINK backbone connections. o via traditional StrataNET--Traditional StrataNET is also available for cross-system communications. Support for Open StrataLINK necessitated the following operating-system changes. You can still use the older versions of many of these commands and files with traditional StrataLINK on XA2000-series and XA/R-series modules; however, Stratus recommends that you upgrade your modules to use Open StrataLINK. o In a single-system configuration using Open StrataLINK, the file new_modules.table replaces modules.table. The file modules.table is available for configurations using only traditional StrataLINK (on XA2000-series and XA/R-series modules). o In a multisystem configuration that includes Open StrataLINK, each SRB: VOS Release 14.5.0 (R914) 5-47 VOS Open StrataLINK system's nonbridge modules must use the file new_systems.table instead of systems.table. The file systems.table is available for configurations using only cluster StrataLINK (on XA2000-series and XA/R-series modules) or traditional StrataNET. o In a multisystem configuration that includes Open StrataLINK, the file new_backbone_systems.table replaces backbone_systems.table on each bridge module that communicates with a module in either the same system or with another system using Open StrataLINK. The file backbone_systems.table is available for systems that communicate using only cluster StrataLINK (on XA2000-series or XA/R-series modules) or traditional StrataNET. o Every hostname specification in entries contained in new_modules.tin and new_backbone_systems.tin must be IP addresses in dot notation only. No domain name specification is allowed. o The configure_modules command no longer searches for the file modules.table first. Instead, you can explicitly specify either new_modules.table or modules.table. If you do not specify a value, the command looks for the file new_modules.table first, and then for modules.table if it cannot find new_modules.table. o The configure_systems command no longer searches for the file backbone_systems.table first. Instead, you can explicitly specify the appropriate table file: new_backbone_systems.table, backbone_systems.table, new_systems.table, or systems.table. If you do not specify a value, the command looks for the first existing file in the following sequence: new_backbone_systems.table, backbone_systems.table, new_systems.table, or systems.table. o The add_module and add_system commands now support Open StrataLINK. See the VOS Administrator's Guide for Open StrataLINK (R388) for more information about Open StrataLINK. Intermodule Compatibility ************************* The following list identifies the ways in which you can configure systems of Continuum-series modules or add Continuum-series modules to existing network configurations. 1. You can create a stand-alone system of Continuum-series modules, using Open StrataLINK for intermodule communications within the system. In this scenario, you do not connect to an existing network configuration. 2. You can create a system of Continuum-series modules, using Open SRB: VOS Release 14.5.0 (R914) 5-48 VOS Open StrataLINK StrataLINK for intermodule communications within the system and traditional StrataNET for cross-system communications. 3. You can create a system of Continuum-series modules, using Open StrataLINK for both intermodule communications within the system and cross-system communications. In this scenario, the bridge modules of all other systems in the network must also be running Open StrataLINK. 4. You can modify a system to contain a mixture of Continuum-series, XA/R-series, and XA2000-series modules, using Open StrataLINK and traditional StrataLINK for single-system communications. In this scenario, communications within the system between pairs of XA2000- series or XA/R-series modules use traditional StrataLINK, and communications within the system involving at least one Continuum- series module use Open StrataLINK. Your cross-system options are then Open StrataLINK, cluster StrataLINK (for XA2000-series or XA/R-series modules only), or StrataNET. The VOS Administrator's Guide for Open StrataLINK (R388) describes the preceding configuration procedures in more detail. Open StrataLINK and STCP ------------------------ This section summarizes information required to configure Open StrataLINK for STCP. (For information about configuring OS TCP/IP, see the VOS OS TCP/IP Administrator's Guide (R223).) Note: You cannot run Open StrataLINK with STCP and OS TCP/IP on the same module simultaneously. You must choose to run Open StrataLINK on either STCP or OS TCP/IP. A module that is running Open StrataLINK with STCP can communicate with any other modules that are running Open StrataLINK with OS TCP/IP. Table 5-6 lists the documentation you may need to configure Open StrataLINK for STCP. Table 5-6. Documentation Needed to Configure Open StrataLINK for STCP ------------------------------------------------------------------------ | Document : Description | |----------------------------------------------------------------------| | VOS Administrator's Guide for Open : Describes Open | | StrataLINK (R388) : StrataLINK | | : configuration | | : procedures unique to STCP | |----------------------------------------------------------------------| | VOS STREAMS TCP/IP Administrator's : Describes standard STCP | SRB: VOS Release 14.5.0 (R914) 5-49 VOS Open StrataLINK | Guide (R419) : configuration procedures | |----------------------------------------------------------------------| | VOS STREAMS TCP/IP Migration Guide (R418): Compares OS TCP/IP and | | : STCP configuration | | : procedures | ------------------------------------------------------------------------ In addition to the standard STCP configuration procedures described in the VOS STREAMS TCP/IP Administrator's Guide (R419), you must also perform the following configuration steps. o Add an entry to the devices.tin file for the OSL Multiplexer. o Load the STCP OSL Net driver (sosl_net_driver.cp). o Start the OSL Daemon process for the OSL Multiplexer and the STCP protocol driver. The VOS Administrator's Guide for Open StrataLINK (R388) describes these configuration steps in detail. Changes Affecting Window Terminal Devices ----------------------------------------- This section discusses the following topics. o ``New sys_info$wtm_allow_multiple_user External Variable" o ``New Argument for the set_terminal_parameters Command" o ``New Window Terminal Opcodes" o ``New VOS Forms Management System (FMS) Subroutines" New sys_info$wtm_allow_multiple_user External Variable ------------------------------------------------------ Beginning in VOS Release 14.2.0, the external variable sys_info$wtm_allow_multiple_user has been added to prevent a nonprivileged user from being able to share another user's window terminal device. By default, sys_info$wtm_allow_multiple_user is set to 0. To allow the sharing of window terminal devices on a system-wide basis, set sys_info$wtm_allow_multiple_user to a nonzero value. This variable does not affect devices that have already been established; you must log off the system and reestablish a connection (that is, you cannot specify the logout -hold command). SRB: VOS Release 14.5.0 (R914) 5-50 Changes Affecting Window Terminal Devices New Argument for the set_terminal_parameters Command ---------------------------------------------------- The set_terminal_parameters command has a new argument: - allow_multiple_users. If you specify this argument, window terminal devices can be shared on an individual basis. This argument takes effect immediately for the specified device. The new set_terminal_parameters display form follows. Display Form ------------------------------------------------------------------------ | --------------------------- set_terminal_parameters -------------- | | ------------ | | | | -line_length: 80 | | | | -terminal_type: v103_ascii_a | | | | -setup: 80x24 | | | | -system_message: | | | | -prompt_message: | | | | -continue_message: + | | | | -pause_message: --PAUSE-- | | | | -pause_lines: 24 | | | | -max_typeahead_lines: 10 | | | | -tabs1: | | 6,11,16,21,26,31,36,41,46,51,56,61,66,71,76,81 | | | | -tabs2: 86,91,96,101,106,111,116,121,126 | | | | -break_action: signal_and_discard | | | | -cursor_format: steady_block | | | | -wait_cursor_format: off | | | | -forms_style: overlay | | | | -escape: \Q -break_to_wmgr: | SRB: VOS Release 14.5.0 (R914) 5-51 Changes Affecting Window Terminal Devices | yes | | | | -black_on_white: no -initial_overlay_on: | | no | | | | -key_click_on: no -cancel_doesnt_abort: | | no | | | | -smooth_scroll: no -return_doesnt_unpause: | | no | | | | -interrupt_key_enabled: yes -return_doesnt_tab: | | no | | | | -clear_reused_screen_pages: no -allow_multiple_users: | | no | ------------------------------------------------------------------------ For more information about the set_terminal_parameters command, see the VOS Commands Reference Manual (R098). New Window Terminal Opcodes --------------------------- The following new window terminal opcodes have been added to allow multiple processes to update the terminal screen simultaneously and provide compatible terminal support for POSIX. o TERM_OPEN_EXISTING_WINDOW_OPCODE (2107) o TERM_ENABLE_CACHED_IO_OPCODE (2108) o TERM_DISABLE_CACHED_IO_OPCODE (2109) o TERM_POSIX_OPEN_OPCODE (2110) o TERM_POSIX_CLOSE_OPCODE (2111) o TERM_GET_SUBWIN_BORDER_OPCODE (2112) o TERM_SET_SUBWIN_BORDER_OPCODE (2113) o TERM_GET_SESSION_ID_OPCODE (2114) o TERM_GET_POSIX_GETATTR_OPCODE (2115) o TERM_SET_POSIX_GETATTR_OPCODE (2116) SRB: VOS Release 14.5.0 (R914) 5-52 Changes Affecting Window Terminal Devices See the Window Terminal Programmer's Guide for Asynchronous Communications (R194) for explanations of these new opcodes. New VOS Forms Management System (FMS) Subroutines ------------------------------------------------- The following new FMS subroutines have been added to provide FMS support for multiple processes to update the terminal screen simultaneously and to provide compatible FMS terminal support for POSIX. o s$fms_get_master_bounds o s$fms_set_master_bounds o s$fms_get_subwindow_borders o s$fms_set_subwindow_borders o s$fms_get_form_origin o s$fms_set_form_origin See the file fms.doc in the directory >system>doc>fms for explanations of these new subroutines. Enhanced Polling Support ------------------------ Beginning in VOS Release 14.5.0, the s$poll subroutine allows you to poll files, pipes, and window terminals, as well as streams devices (previously, it only polled streams devices), on remote modules. For more information about the s$poll subroutine, see the VOS Communications Software: STREAMS Programmer's Guide (R306). SRB: VOS Release 14.5.0 (R914) Chapter 6: The File System =============== This chapter discusses changes to the VOS file system in VOS Release 14.0.0 and later. It contains the following sections. o ``Support for Byte and Record Count in File Entries" o ``Creating Deleted Record Indexes for Fixed Files" o ``Cache Manager Improvements" o ``Dynamically Allocated Extents (DAE)" Support for Byte and Record Count in File Entries ------------------------------------------------- This section discusses the following topics. o ``Overview of Byte and Record Count" o ``VOS Commands Affected by Byte and Record Count Support" o ``VOS Subroutines Affected by Byte and Record Count Support" Overview of Byte and Record Count ---------------------------------- Beginning in VOS Release 14.4.1, newly-created relative and sequential files that are not transaction files will support byte count and record count. This new feature will contribute to faster speeds during POSIX processing. To provide your existing relative and sequential files with byte and record count information, you can use either of the following methods. Each method calculates and stores byte and record counts. o Method 1: For each file to be updated, specify the following command. copy_file file_name -pack o Method 2: Open the file in Emacs, and save the file to the same file name. SRB: VOS Release 14.5.0 (R914) 6-1 Support for Byte and Record Count in File Entries Note: If you copy files from one system to another system across the network, all modules on all involved systems, as well as any bridge modules, must be running VOS Release 14.4.1 or later. Otherwise, byte and record counts for the files will be lost. VOS Commands Affected by Byte and Record Count Support ------------------------------------------------------- The following VOS commands have changes related to byte and record count support. o ``Changes to the display_file_status Command" o ``Changes to the verify_end_of_file Command" Changes to the display_file_status Command ****************************************** You can display byte and record count information with the display_file_status command. In the following example, note the byte and record count fields, which are shown in bold. display_file_status example1 name: %mis_user17>Cynthia_Smith>example1 file organization: sequential file last used at: 01-06-14 13:19:04 edt last modified at: 01-06-14 13:18:33 edt last saved at: never time created: 01-06-04 09:05:49 edt transaction file: no log protected: no implicit locking: no pipe file: no safety switch: no SRB: VOS Release 14.5.0 (R914) 6-2 Support for Byte and Record Count in File Entries audit: no dynamic extents: no extent size: 1 next byte: 51840 blocks used: 13 num indexes: 0 allocation size: 1 mode: w author: Cynthia_Smith.SysAdmin tag type: 0 tag version: 0 record count: 1396 data byte count: 45304 For more information about the display_file_status command, see the VOS Commands Reference Manual (R098). Changes to the verify_end_of_file Command ***************************************** Although the verify_end_of_file command does not itself change because of byte and record count support, the command is indirectly affected. Assume that you specify verify_end_of_file -update_directory and a file is updated. If the end of file is incorrect, the verify_end_of_file command will set the byte and record counts for the file to zero. For more information about the verify_end_of_file command, see the manual VOS System Administration: Starting Up and Shutting Down a Module or System (R282). VOS Subroutines Affected by Byte and Record Count Support --------------------------------------------------------- The s$get_file_status and s$get_object_status subroutines are affected by byte and record count support. For more information about SRB: VOS Release 14.5.0 (R914) 6-3 Support for Byte and Record Count in File Entries s$get_file_status, see ``Subroutine Changes Not Documented in the Subroutines Manuals'' in Chapter 8. For more information about s$get_object_status, see ``New Subroutines Not Documented in the Subroutines Manuals'' in Chapter 8. Creating Deleted Record Indexes for Fixed Files ----------------------------------------------- You should not create deleted record indexes for fixed files. If you attempt to do so by issuing the create_deleted_record_index command or the s$create_deleted_record_index subroutine for a fixed file, the command or subroutine returns the error e$bad_index_defined (1099). Instead of creating deleted record indexes for fixed files, issue the create_record_index command or use the s$create_record_index subroutine for fixed files. For complete information about the commands create_record_index and create_deleted_record_index, see the VOS Commands Reference Manual (R098). For complete information about the subroutines s$create_record_index and s$create_deleted_record_index, see the VOS Subroutines manuals. Cache Manager Improvements --------------------------- Beginning in VOS Release 14.3.0, the disk cache and the cache manager have been improved so that you can designate files as either memory-resident or transient files. Designating files as memory-resident or transient affects how the cache manager handles data and/or index blocks. Memory-resident files have their data blocks, index blocks, or both data and index blocks permanently kept in the disk cache, thereby reducing the amount of disk reads. Blocks of memory-resident files remain in the cache for as long as such files are active. You can reserve part of the cache for holding memory-resident files; if there are no such files in use, that part of the cache is available for general use. If more blocks from memory- resident files are active than will fit into the specified portion of the cache, the most recently used blocks will remain in the cache, while the other file blocks will compete for the remainder of the cache, as any normal block would do. Memory-resident files have an infinite unreferenced grace time. If there is enough space for memory-resident blocks, memory-resident files leave the cache only when the file is closed by the last opener. Transient files have their data blocks, index blocks, or both data and index blocks remain in cache for a very short, user-settable time. Identifying a file as transient has the effect of communicating to the SRB: VOS Release 14.5.0 (R914) 6-4 Cache Manager Improvements cache manager that its blocks probably will not be needed again. By default, transient files have a zero modified grace time and a zero unreferenced grace time. For information about using transient files, see ``New s$control Opcodes" and ``New Cache-Related Tuning Arguments" later in this chapter. The remainder of this section discusses the following topics. o ``Disk and Cache Manager Improvements" o ``Maximum Cache Size" o ``New s$control Opcodes" o ``New Cache-Related Tuning Arguments" o ``Cache Buffer Pinning Replaced" o ``Changes to the dump_cache Request in analyze_system" o ``Changes to the dump_cache_info Request in analyze_system" o ``Changes to the cache_meters Request in analyze_system" o ``Changes to the dump_afte and dump_axte Requests in analyze_system" o ``Changes to the dump_disk_info Command" Disk and Cache Manager Improvements ----------------------------------- Modifications to the disk cache and cache manager include the following: o The maximum cache size has increased from 2 GB to 10 GB but is limited by available memory. o Two new opcodes of the s$control subroutine allow you to set and observe the memory-resident and transient cache modes of files. o You can now limit, on a per-disk basis, the number of concurrent disk writes generated by the cache manager. Therefore, processes are less likely to undergo long waits for disk read access, and disk writes are more efficient and evenly distributed, particularly when files are spread over multi-member volumes. o Seven new tuning arguments to the set_tuning_parameters command allow you to more effectively control cache manager behavior. When SRB: VOS Release 14.5.0 (R914) 6-5 Cache Manager Improvements you specify one of these arguments, they immediately affect the cache manager's behavior. For more information, see ``New Cache- Related Tuning Arguments" later in this chapter. o You can now limit, on a per-disk basis, the number of blocks that can remain modified in the cache without being written to disk. o The cache-buffer pinning facility has been replaced by a more straightforward and predictable method of allowing low-priority processes to minimally degrade cache performance. o The output of several analyze_system requests contains cache-related changes. The analyze_system command also provides a number of additional metrics for analyzing cache performance, and per-disk write information is also displayed. o The cache manager recognizes solid-state disks and adjusts its algorithms, which limit disk-write queueing and maximum modified blocks based on disk type. o Excessive process delays related to cache manager activity have been eliminated. Note, however, that this does not mean that a user process will never have to wait for the cache manager to provide a buffer or for disk I/O to complete, but rather that delays appear more evenly distributed among processes, avoiding excessive delays in any one specific process. o Beginning in VOS Release 14.5.0, a process performing operations on memory-resident and transient files no longer needs to be privileged. Maximum Cache Size ------------------ The maximum size of the cache has increased from 2 GB to 10 GB, but the cache manager limits the total amount of memory as follows: o Virtual memory--The cache manager can consume up to 128K pages of kernel virtual address space available during the bootload. You cannot change the virtual memory to be greater than this limit. o Physical memory--VOS manages the memory to provide sufficient resources to respond to changing system demands. You can change the percentage of physical memory available for the cache with the new argument -cm_cache_mem_pct of the set_tuning_parameters command. See ``New Cache-Related Tuning Arguments" later in this chapter for information about changing the percentage of physical memory. When you increase the cache size, you may need to increase the size of the SRB: VOS Release 14.5.0 (R914) 6-6 Cache Manager Improvements dump partition. For information about changing the dump-partition size, see the manual VOS System Administration: Disk and Tape Administration (R284). For information about setting the cache-tuning parameters, see the cache_tuning.doc file in >system>doc. New s$control Opcodes --------------------- Two new control opcodes of the s$control subroutine allow you to modify and observe the disk cache mode to indicate that all data blocks and/or index blocks for the specific file should be memory-resident or transient. The new control opcodes of the s$control subroutine are as follows: 2204 SET_FILE_CACHE_MODES The control_info argument is the third argument passed with SET_FILE_CACHE_MODES. It is a 32-bit value in which the low-order bit (the one-bit) indicates whether all data blocks for the file in question should be memory-resident. The next low-order bit (the two-bit) indicates whether all index blocks associated with all indexes of the file should be memory- resident. If both bits are set to zero, memory-residency is turned off for the file. The four-bit indicates that the data blocks of the file in question should be transient, and the next low-order bit (the eight-bit) indicates whether all index blocks associated with all indexes of the file should be transient. If both the four- and eight-bits are zero, transience is turned off for the file. Note: The memory-resident and transient bits are mutually exclusive. The following error codes are returned for SET_FILE_CACHE_MODES: o The error code e$invalid_control_operation (1366) is returned if any bit in the 32-bit argument other than the four low-order bits is set to true. This error also results from trying to set either data or indexes to both transient and memory-resident. o The error code e$index_not_found (1102) is returned if the bit corresponding to index mode is set to true and the file has no indexes. The modification of the cache mode, Off to On, affects only the disk blocks that are not currently in the cache. Any blocks currently in the cache are affected by the change when accessed by a program or once they reenter the cache after being removed. Modification from On to Off affects disk blocks when they are scanned by the cache manager timer process, which runs every few seconds. SRB: VOS Release 14.5.0 (R914) 6-7 Cache Manager Improvements 2205 GET_FILE_CACHE_MODES The control_info argument is the third argument passed with GET_FILE_CACHE_MODES. It is a 32-bit value assignment for the control_info argument that returns the current settings for memory-residency. The index mode is set to the cache-mode value of the first index. (All indexes of a file will have the same setting.) If the file has no indexes, the bits corresponding to the index mode are set to zero. New Cache-Related Tuning Arguments ---------------------------------- The set_tuning_parameters command supports seven new cache-related tuning arguments: -cm_cache_mem_pct, -cm_transient_mod_grace_time, - cm_max_resident_pct, -cm_min_cache_priority, -cm_disk_mod_limit, - cm_disk_write_limit, and -cm_cate_write_limit. A sample display form for the set_tuning_parameters command follows. Display Form ------------------------------------------------------------------------ | --------------------- set_tuning_parameters ----------------------- | | -- | | | | -module: %s1#m1 | | | | -max_events_per_process: 64 | | | | -bm_max_buffers: 104856 | | | | -bm_min_buffers: 275 | | | | -bm_max_virtual_pages: 129024 | | | | -bm_modified_grace_time: 60 | | | | -cm_transient_mod_grace_time: 5 | | | | -bm_unreferenced_grace_time: 300 | | | | -bm_referenced_grace_time: 60 | | | | -bm_free_grace_time: 300 | | | | -cm_cache_mem_pct: 60 | | | SRB: VOS Release 14.5.0 (R914) 6-8 Cache Manager Improvements | -cm_max_resident_pct: 50 | | | | -cm_min_cache_priority: 0 | | | | -cm_disk_mod_limit: 4096 | | | | -cm_disk_write_limit: 128 | | | | -cm_cate_write_limit: 4096 | | | | -recover_disk_priority: 1 | | | | -unused_dir_timeout: 120 | | | | -max_events_per_task: 64 | | | | -max_events_per_module: 0 | ------------------------------------------------------------------------ FOOTNOTE: 1 Numeric-keypad key Arguments --------- -cm_cache_mem_pct N This argument allows you to change the maximum percentage of memory that can be used for the cache. The value N is the percentage of memory beyond the first 128 MB that is used for the cache. The cache manager can consume an amount of physical memory that is determined by the following formula: 20% of the first 64 MB of physical memory in the machine, plus 40% of the next 64 MB, plus N% of the remaining physical memory The default value of N is 60. The value of N is limited to the values 0 through 95. (Previously, this value could be changed by patching cm$cache_mem_pct, as documented in the >system>doc>cache_tuning.doc file.) This argument, along with the -bm_max_buffers argument, provides another limit on the cache. If -cm_cache_mem_pct is too small, the cache might not grow to the desired size. If -cm_cache_mem_pct and -bm_max_buffers are too large, and there is a demand that causes the cache to grow very large, the cache could possibly deprive other users of memory. This may result in excessive paging activity or the appearance of allocation-failure error messages in the syserr_log.date. SRB: VOS Release 14.5.0 (R914) 6-9 Arguments When you tune the cache, you must balance performance improvement (achieved when you increase the cache size, thus reducing the disk I/O) with the potential degradation that occurs if the system runs low on available memory. For more information about tuning the cache, see the cache_tuning.doc file located in >system>doc. You can view the current cache-tuning parameters by issuing the dump_cache_info request of the analyze_system command. For more information about using the dump_cache and dump_cache_info requests, see the VOS System Analysis Manual (R073). -cm_transient_mod_grace_time N This argument allows you to set the default grace time for expiring modified blocks from transient files. The value N is in terms of seconds and is limited to the values 0 through 3600. The default is 0. The value N represents the elapsed time that modified blocks from transient files will remain in the cache before they expire. For transient files, a modified block is not written until it has expired, even if force writing is requested by the cache manager interface (as may be the case with the target file of the copy_file command.) The value of N is limited by the value of -bm_modified_grace_time. It may be specified as higher, but transient blocks will expire when modified grace time has elapsed. -cm_max_resident_pct N This argument is the percentage of maximum cache size available for memory- resident files. The default maximum resident percentage value is 50. The value of N is limited to the values 0 through 95. -cm_min_cache_priority N This argument allows you to specify a minimum priority for processes that are entitled to retain data in the cache. The value N is the priority that is compared to the process's priority and must be a value of 0 through 9. Blocks used by processes running below priority N are the first to expire if the cache usage is above the minimum. Note: This new argument replaces buffer pinning, which was used in the following analyze_system requests: set_cache_pin_parameters and display_cache_pin_parameters. You can use the following throttling threshold to prevent the cache manager from holding an excess backlog of unwritten modified blocks in cache, thereby preventing latency problems that could otherwise occur when deactivating files or when shutting down the system. SRB: VOS Release 14.5.0 (R914) 6-10 Arguments -cm_disk_mod_limit N The value N is the maximum number of modified blocks per disk that the cache manager is allowed to hold in cache before initiating disk writes. When this limit is reached, blocks are queued for writing even if their mod expiration time has not been reached. Processes making the modifications may be slightly delayed in order to accomplish this. This value does not provide a hard limit, and the actual number of modifications may exceed it by 5% to 10%. The value of N is limited to the values 1 through 32,767. The default is 512. Note: The value used for limiting modified blocks on solid-state disks is derived by applying a factor of 2 to this value. You can use the following two cache manager throttling thresholds to prevent the cache manager from generating a backlog of writes to disk, thereby reducing disk-access wait time for other processes. -cm_disk_write_limit N For this argument, N is the maximum number of write requests that the cache manager is allowed to queue to each disk. When this limit is reached, future queue writes are delayed until the disk queues are reduced to 50% of this value. The value of N is limited to the values between 1 and 32,767. The default is 128. Note: The value used for limiting writes to solid-state disks is derived by applying a factor of 8 to this value. -cm_cate_write_limit N This argument replaces the external variable cm$max_diskw_per_cate, which was patchable through the analyze_system command. The value N is the maximum number of writes that are allowed to be concurrently queued for blocks associated with a cate before delays will occur for processes attempting to subsequently access other blocks in that cate. A cate is an operating system data structure. There is a separate cate for each index and for the data area of each file. When a request for a cache block is made for a file or index that has more than N writes queued, the process is stalled until a few of the writes are completed. This limit is also used when a file is deactivated and all blocks are flushed to disk. The value of N is limited to the values 1 through 32,767. The default value is 4096. Stratus recommends that you do not change this to a lower value; the ability to do so is provided only for compatibility purposes. Examples SRB: VOS Release 14.5.0 (R914) 6-11 Examples --------- The following sample output displays the seven new cache-related settings for the display_tuning_parameters command. display_tuning_parameters The tuning parameters on %s1#m1 are: max events per process 64 cache_manager, max buffers 104856 cache_manager, min buffers 275 cache_manager, max virtual pages 129204 cache_manager, modified grace time 60 seconds cache_manager, transient mod grace time 0 seconds cache_manager, unreferenced grace time 300 seconds cache_manager, referenced grace time 60 seconds cache_manager, free grace time 300 seconds cache_manager, cache memory percent 60 cache_manager, max resident percent 50 cache_manager, min cache priority 0 cache_manager, disk mod limit 512 cache_manager, disk write limit 128 cache_manager, cate write limit 4096 max processes per module 4096 recover_disk priority 1 scheduler short wait timeout 0.000 seconds unused directory timeout 120 seconds max events per task 64 max events per module 0 SRB: VOS Release 14.5.0 (R914) 6-12 Examples For more information about the set_tuning_parameters and display_tuning_parameters commands, see the manual VOS System Administration: Administering and Customizing a System (R281). Cache Buffer Pinning Replaced ----------------------------- The new argument, -cm_min_cache_priority, of the set_tuning_parameters command, replaces the buffer pinning used in the following analyze_system requests: set_cache_pin_parameters and display_cache_pin_parameters. If you execute these requests, the following error messages are displayed. get_cache_pin_parameters: The requested operation is not supported. Use display_tuning_parameters. set_cache_pin_parameters: The requested operation is not supported. Use set_tuning_parameters -cm_min_cache_priority argument. Changes to the dump_cache Request in analyze_system ---------------------------------------------------- The following arguments have been added to the dump_cache request: -brief, -list, -number, -address, -times, -check, -reverse, -interval, and -long. The dump_cache request display form follows. (Note that the -pin_info argument is no longer supported.) Display Form ------------------------------------------------------------------------ | --------------------------- dump_cache ----------------------- | | | | name: | | | | -all: no | | | | -full_path: no | | | | -brief: no | | | | -list: none | | | | -number: | | | | -address: | SRB: VOS Release 14.5.0 (R914) 6-13 Examples | | | -times: no | | | | -check: yes | | | | -reverse: yes | | | | -interval: 60 | | | | -log: no | | | | -long: yes | ------------------------------------------------------------------------ Command-Line Form ----------------- The command-line form for the dump_cache request follows. dump_cache name [-all] [-full_path] [-brief] [-list] {} [-times] [-no_check] [-no_reverse] [-interval interval] [-log] [-no_long] Arguments --------- SRB: VOS Release 14.5.0 (R914) 6-14 Arguments name phy_number A file name or file star name for which to list cache activity. If you specify the -all argument, the request ignores this argument. The default value is star (*), or all files. -all This argument displays all entries. The default value is no. -full_path This argument displays the full path name for all objects (files, directories, or indexes) using cache buffers. If you specify no, the request displays only the object's name. The default value is no. -brief This argument avoids displaying phys associated with bitmaps. The phy is a cache manager data structure that keeps track of buffers. There is one phy for each buffer. The default is no. -list This argument displays one or more phy lists or the mod list; choose from none, mod, unref, inmem, outmem, ref, transient, free, unref_vir, unref_novir, inmem_vir, inmem_novir, outmem_vir, outmem_novir, free_vir, free_novir, mod_only, eternal, or *. The selection argument * displays all lists. (On an active system, the list traversal can become disconnected; by default, start at the tail of the list to minimize this effect; specify the -no_reverse argument to start at the head.) The default value is none. Sample output of the -list argument follows. In the example, the first phy at each 60-second interval is shown, traversing the list in reverse order. LIST OF UNREF WITH VIR PHYS (7417) ***** <1:00 (60 seconds) 7414 20591 000004 UNMOD V FILE 5 N 12 U 0:39 HUB.config ***** <2:00 (120 seconds) 7234 22310 000000 UNMOD V FILE 8 N 12 U 1:43 reboot_info ***** <3:00 (180 seconds) . SRB: VOS Release 14.5.0 (R914) 6-15 Arguments . . -number phy_number This argument displays the indicated phy. The -number and -address arguments are mutually exclusive. -address phy_address This argument displays the phy at the specified address. The -address and -number arguments are mutually exclusive. -times This argument causes the output to display the various times (no, used, refed, first_mod, last_mod) in a second line. The default value is no. -no_check This argument checks for entries that are out of order (last_time_used is used for all lists except for the modified list, in which first_time_modified is used). Any out-of-order entries are shown, in addition to those at the breakpoints of the particular interval in force. The default value is yes. -no_reverse This argument specifies the direction in which the list is traversed. By default (if you specify yes), the -reverse argument traverses the list in reverse order (tail to head) with the assumption that it is more stable in that direction, since entries are usually removed from the head. The -no_reverse argument displays the list from head to tail. -interval interval This argument specifies the time interval between the phys that are displayed. By default, interval is 60, which means that the request displays the first phy at each 60-second interval. Each phy list can contain many minutes' worth of phys. This argument controls the amount of phys that are displayed. -log This argument displays log-protection information for the dumped phys. The default value is no. SRB: VOS Release 14.5.0 (R914) 6-16 Arguments -no_long By default, the dump_cache request displays the following information: ------------------------------------------------------------------------- | : phy : The disk cache buffer number | |-----------------------------------------------------------------------| | : Block : The file/directory block number | |-----------------------------------------------------------------------| | : State : The state of the buffer in the disk cache. Values | | : : include UNMOD (unmodified), MOD (modified), WRITE | | : : (writing to disk), and READ (reading from disk). | | : : If -all is used, NO MEM (no memory assigned), FREE | | : : (memory assigned but not tied to a file or | | : : directory), and INVAL (a transitory state between | | : : FREE and READ) are also possible. | |-----------------------------------------------------------------------| | : P, V, R : This grouping, which does not have a column | | : : heading, indicates the following: | | : : | | : : P: The block was pre-read | | : : | | : : V: The virtual address is assigned. | | : : | | : : R: The block is currently referenced | |-----------------------------------------------------------------------| | : Type : FILE, INDEX, DIR (the block belongs to a file, | | : : index, or directory, respectively) | |-----------------------------------------------------------------------| | : P : Priority of process using this phy (or if more | | : : than one is the highest priority) | |-----------------------------------------------------------------------| | : M : Cache mode (F represents freed, O represents | | : : outbound, N represents normal, M represents memory- | | : : resident, T represents transient, and t represents | | : : transient outbound) | |-----------------------------------------------------------------------| | : DN : Disk number (ddte table index) of the disk | | : : containing this block (or -1 if the address is not | | : : yet determined) | |-----------------------------------------------------------------------| | : Q : phy_links queue (U represents unref, F represents | | : : free, I represents inmem, O represents outmem, x | | : : represents a phy that is not queued, R represents | | : : referenced, and E represents eternal. Lowercase u, | | : : f, i, and o represent the corresponding uppercase | | : : queues but for phys without a virtual address). | |-----------------------------------------------------------------------| | : Time : Elapsed time since phy has been last used | SRB: VOS Release 14.5.0 (R914) 6-17 Arguments |-----------------------------------------------------------------------| | : Name : The name of the file | ------------------------------------------------------------------------- If you specify the -no_long argument, the P (indicating the priority), M, DN, and Q fields are omitted from the display. The following is an example of the output when the -long argument is set to yes. phy Block State Type P M DN Q Time Name 202 7319 UNMOD V FILE 0 N 12 U 41:40 file2 Changes to the dump_cache_info Request in analyze_system --------------------------------------------------------- Beginning in VOS Release 14.3.0, a new argument, -long, has been added to the dump_cache_info request of the analyze_system command. Some of the information previously displayed by default is now displayed only if you specify the -long argument. The default is -no_long. Changes in tuning the cache manager have made the cache sizing more immediately responsive to tuning changes. The following information may be useful in monitoring the effects of modifying the tuning parameters. The data first displayed, showing the maximum and minimum cache characteristics, shows the differences between the user-specified minimum phys and the real phys. Note that the latter may be larger due to bitmap requirements. ---------------------------------------------------------------------------- | : : : : real : log : mem | |--------------------------------------------------------------------------| | : max : cur : min : min/max : max : min/max | |--------------------------------------------------------------------------| | phyps: : 262144 : 1196 : 7641 : : : 7641/147454 | |--------------------------------------------------------------------------| | phys: : 104856 : 1196 : 301 : 7641/104856 : 2441406 : | |--------------------------------------------------------------------------| | virs: : 129024 : 1196 : 7641 : /129024 : : | ---------------------------------------------------------------------------- Data representing the state of the cache manager's utilization of disks is displayed. The following list shows disks that have had at least one cache write directed to them. --------------------------------------------------------------------------- | Per-disk writes: (3) : Count : Max : Total : Mod : Max | SRB: VOS Release 14.5.0 (R914) 6-18 Arguments |-------------------------------------------------------------------------| | fio.0 : 1 : 0 : 17 : 11196 : 0 : 9 | |-------------------------------------------------------------------------| | m17_mas.0 : 2 : 0 : 139 : 5530 : 2 : 177 | |-------------------------------------------------------------------------| | m17_user.0 : 3 : 0 : 1 : 18 : 0 : 2 | --------------------------------------------------------------------------- The output from the preceding example has the following meaning. o The first number (in the second column) represents the ddte number of a disk pair (used with the dump_ddte command). o The Count, first Max, and Total columns represent disk writes, with Count being the current number of writes queued that have not yet been posted. o The Mod and second Max columns represent the current and maximum number of modified blocks in the cache that have not been written. All of these values are reset to zero when a disk is remounted. Changes to the cache_meters Request in analyze_system ------------------------------------------------------ The cache_meters request has a number of changes that are described in the following sections. o ``New and Changed Arguments to the cache_meters Request" o ``Cache Health and Status Displays" o ``Change to the Hit/Miss Data Displayed" o ``Per-Disk Metering Information" New and Changed Arguments to the cache_meters Request ***************************************************** The cache_meters request has a number of new arguments, and the presentation and grouping of the arguments has been reorganized. The cache_meters display form follows. Display Form ------------------------------------------------------------------------ SRB: VOS Release 14.5.0 (R914) 6-19 Arguments | --------------------------------- cache_meters -------------------- | | ----------- | | | | -all: no | | | | -reset: no | | | | -long: no | | | | -interval: | | | | -hits: no | | | | -status: no | | | | -health: no | | | | -health_factor: 16 | | | | -brief: no | | | | -disk_no: | | | | -scroll: no | | | | -timestamps: yes | | | | -reset_cm_maxes: no | | | | -output_path: | | | | -times: | | | | -no_header: no | ------------------------------------------------------------------------ Command-Line Form ----------------- cache_meters [-all] [-reset] [-long] [-interval interval] SRB: VOS Release 14.5.0 (R914) 6-20 Command-Line Form {} [-status] [-health_factor sensitivity_value] [-brief] [-disk_no number] [-scroll] [-no_timestamps] [-reset_cm_maxes] [-output_path path_name] [-times number] [-no_header] Arguments --------- -all This argument causes additional information to be displayed, rather than a summary only. The specific information displayed depends on the type of display requested. By default, the cache_meters request displays a summary. -reset This argument resets meters. If you specify the -interval argument with this argument, -interval begins the display. If you do not specify the -interval argument, the -reset argument results in no display (since all meters displayed will be zero immediately after the reset is done). -long This argument eliminates the suppression of meters that have zero values. You can use this argument to obtain a fixed number of lines if the output is being saved for processing by edit or spreadsheet macros. SRB: VOS Release 14.5.0 (R914) 6-21 Arguments If you specify the -long argument with the -health argument, the eight components of the cache health and status displays are labeled. -interval interval This argument allows you to specify a time interval that indicates how often metrics should be collected and accumulated. In general, you use the -interval argument to provide a continuous display of cache meters repeated at every interval seconds. The most useful cache meters for providing feedback for tuning the cache will be gathered according to the specified interval and repeatedly updated and displayed. This is particularly useful in monitoring how tuning parameter modifications or changes in application workload actually affect cache behavior. This information can be optionally specialized for a particular disk pair by specifying the -disk_no argument, as opposed to being given for all disks, which is the default. If used alone (without the -health, -status, or -hits argument), the - interval argument displays a subset of the meters shown with the cache_meters command when not using this argument. -hits This argument displays the details of cache hit/misses, broken down by cate type and block type, as well as average time to gain access to (for example, get_block) each of these types. If you specify the - hits argument without specifying the -interval argument, an interval value of 2 (seconds) is assumed. -status This argument displays a representation of the cache manager's status. If you specify the -status argument without specifying the - interval argument, an interval value of 2 (seconds) is assumed. You can specify the -status argument with either the -health or -hits argument. The -status argument produces the following output: max cur min real min/max mem min/max Phys: 13106 532 32 541/9829 541/9829 States: Free OutBnd Unref Ref Mod InMem Trans Etern 429 0 45 1 4 0 0 50 Get Rel Read Write Mdelay Wdelay Max ms: 146.1 1.617 149.8 276.2 0 0 SRB: VOS Release 14.5.0 (R914) 6-22 Arguments Last ms: 2.853 0.061 21.91 74.89 0 0 Last n: 679 675 170 166 0 0 Expired: Mod Unref Ref Free CMT count: 1 0 0 0 0 msecs: 0.137 Per-disk status: ddte WQ'd Empty AveQ MaxQ Total Mods Max m2.0 1 7 938 4 13 8129 4 17 An explanation of the preceding output follows. o The Get...Rel...Read ... section displays information about get_block, release_block, disk reads, disk writes, delays for throttling excess modified blocks, and delays for throttling excess disk writes. Specifically, this section displays information about the number of these occurring over the last interval in the Last n row, and it also displays the average time in milliseconds per operation over that interval in the Last ms row. o The CMT count section displays the number of times that the cache manager timer process ran in the interval; the msecs value is the average time that the CMT ran per iteration. o The Expired section is displayed only if you specify the -all argument. If you have a large number of disks, the status data may not fit on one screen, resulting in a garbled display; in this case, specify the -disk_no argument to display data related to a particular disk. If you specify -disk_no 0, a single Total line is displayed, with the data combined for all disks on the system. -health This argument displays a representation of the cache manager's well- being. You can specify the -status and -health arguments together to show a representation of the health and status of the cache manager. If you specify the -interval argument with the -health argument, - interval may be a negative value, as low as -16, representing the inverse of screen update time (for example, specifying -interval -4 causes the screen to be updated 4 times per second). Negative values used in combination with other arguments are assumed to be 1 second. If you specify the -health argument without specifying the -interval argument, an interval value of 2 (seconds) is assumed. You can specify the -health argument with the -status argument, which displays output, provided that the screen has sufficient space. You SRB: VOS Release 14.5.0 (R914) 6-23 Arguments can specify the -brief argument to minimize the space required by specifying the -health argument. -health_factor sensitivity_value This argument tunes the X component of the health display with lower values causing increased sensitivity (time values have more prominence). -brief number This argument limits displays to fit on a 24-line terminal and causes display of only the most basic information. If you do not specify this argument, the display can take up to 55 lines. -disk_no number This argument allows you to specify a disk number (ddte number). (The mapping of numbers to disk names can be seen using the dump_cache_info or the cache_meters request.) If specified with the - health or -status argument, the disk-related information displayed will be for the specified disk instead of all disks. Otherwise, the - interval display will contain only disk-related data that applies to the specified disk; in this case, specifying a -disk_no value of 0 causes this type of display to be produced using the combined data from all disks. -scroll This argument controls the screen display. By default (the value no), when you specify the -status or -health argument, the cursor repositions to the top-left corner and the screen is redrawn. If you specify the value yes, the existing information scrolls off the screen. If you do not specify either the -status or -health argument, the request ignores the -scroll argument. -no_timestamps This argument specifies whether the request displays time-stamp information in the output. By default (the value yes), the output contains time-stamp information, including which module is in use and the current time. If you specify the value no, the output does not contain this information. -reset_cm_maxes This argument resets the per-disk maximum read/write meters tracked by the cache manager, thus allowing you to determine the correct maximum values for the upcoming sample interval. By default (the value no), these meters are not reset. SRB: VOS Release 14.5.0 (R914) 6-24 Arguments -output_path path_name This argument directs output of the command to a specified path name. -times number This argument indicates how many times the display is repeated. By default, the display continues indefinitely, assuming an interactive user who will break to stop it. Thus, the -times argument can be useful in batch mode. -no_header This argument suppresses the display of column-heading labels. By default, this display is not suppressed. Cache Health and Status Displays ******************************** Beginning in VOS Release 14.3.0, you can display an ongoing visual summary of the "health" of the cache (as opposed to numerical representation) by specifying the cache_meters request's -health argument with the -interval argument. This provides for a simple set of measurements of cache performance that are graphed and continually displayed at the specified interval, allowing nondetailed visual feedback patterns during times that tuning parameters are being modified, for workload changes, or for transitions in an application's state. You can perform this display on an ASCII terminal. In addition, you can monitor cache "status" concurrently with the cache health display. This is an ongoing display of the status of the contents of the cache, the various disk queues, and the time being used for get_block, release_block, disk reads, and disk writes. You can specialize the cache health and status displays on a per-disk basis, thereby displaying disk-related data applicable to a single selected disk-pair, as opposed to all disks. The cache health display involves four percentage values (which, ideally, are very high) and four average time values (which, ideally, are very low). In some cases, the data provided in the cache health display can be overly simplistic, but it usually will point to problems that you can then pursue using the more detailed meters. In general, the picture will provide some aspects of good health and some aspects of bad health, with a + symbol representing high percentages and low times, and an X representing high times and low percentages. If you specify the -long argument with the -health argument, the eight components are labeled. Note that if you also specify the -status argument, you may want to avoid the SRB: VOS Release 14.5.0 (R914) 6-25 Arguments extra lines required by the -long argument (that is, in order for both displays to fit on the screen, as the output displayed by the -status argument has a variable number of lines based on the number of disks involved). Figure 6-1 shows the percentage components of the cache health display. Figure 6-1. Percentage Components of the Cache Health Display Figure 6-2 shows the time components of the cache health display. Figure 6-2. Time Components of the Cache Health Display Change to the Hit/Miss Data Displayed ************************************* Beginning in VOS Release 14.3.0, the hit/miss data is calculated differently. In previous releases, any get_block access that did not result in a disk read was considered a hit. The Total column was simply the sum of the Hits and Misses columns. This method of reporting the hit/miss ratio counted get_block requests that were being done for new blocks as hits, which distorted actual caching effectiveness. Now, a hit is counted only if a block was being requested and was found in the cache. Sample hit/miss data follows. Hits Misses Total File Data 5043/ 35.74% 9067/ 64.26% 24757/ 39.03% Indirect 22513/ 99.44% 126/ 0.56% 22651/ 35.71% Index Data 1127/ 74.93% 377/ 25.07% 1504/ 2.37% Indirect 201/ 94.81% 11/ 5.19% 212/ 0.33% Directory Data 13076/ 93.47% 914/ 6.53% 13993/ 22.06% Indirect 287/ 90.54% 30/ 9.46% 317/ 0.50% Totals 42247/ 80.06% 10525/ 19.94% 63434 In the preceding example, although the display looks the same as it did in previous releases, the Total column represents all get_block requests and is no longer the sum of the Hits and Misses columns. SRB: VOS Release 14.5.0 (R914) 6-26 Arguments In the following example, note that in the output displayed by the -hits argument, two percentages are shown: the hit/miss ratio (that is, the number of hits per attempts) and the percent missed (that is, the number of get_block requests requiring a disk read). 2sec 10sec 30sec 1min 5min 10min Total File Data 292 1398 1942 27k ms/get 6.713 7.034 7.385 6.042 pct hit/miss 15.7% 16.5% 17.1% 25.6% hits 23 116 167 5216 misses 123 583 805 9873 pct missed 42.1% 41.7% 41.4% 26.9% File Indirect 292 1400 1922 25k ms/get 0 0.030 0.091 0.091 pct hit/miss 100% 99.9% 99.5% 49.8% hits 292 1398 1911 24k misses 0 1 9 135 pct missed 0% 0% 0.4% 0.5% Index Data 0 0 6 1512 ms/get 0 0 8.148 3.494 pct hit/miss 0% 0% 50.0% 42.7% hits 0 0 3 1131 misses 0 0 3 381 pct missed 0% 0% 50.0% 20.1% Index Indirect 0 0 0 212 ms/get 0 0 0 0.579 . SRB: VOS Release 14.5.0 (R914) 6-27 Arguments . . \n\n\n\n\n\n Per-Disk Metering Information ***************************** Beginning in VOS Release 14.3.0, per-disk information is displayed for each disk pair for which cache activity has occurred. The output of the cache_meters request in analyze_system contains per-disk metering information as follows: ------------------------------------------------------------------------- | Per-disk info : ( 3 ) : Count : Empty : Ave Q | |-----------------------------------------------------------------------| | fio.0 : 1 : 11196 : 10513 : 0 | |-----------------------------------------------------------------------| | m17_mas.0 : 2 : 5813 : 4894 : 2 | |-----------------------------------------------------------------------| | m17_user.0 : 3 : 21 : 21 : 0 | ------------------------------------------------------------------------- An explanation of the preceding output follows. o The Count column indicates the total number of disk writes that have been queued (although not necessarily completed). This will be approximately the same value as the dump_cache_info Total unless the -reset argument of this request has been used, in which case it will represent the number of disk writes since the reset. o The Empty column indicates the number of times that a write has been queued when the queue is empty. o The Ave Q field indicates the average queue depth. You can use this information to help determine how busy the cache manager is keeping the disks. Note: It is advantageous to have some queue backlog as opposed to continually allowing the queue to vary between empty and full. Beginning in VOS Release 14.3.0, the cache manager attempts to accomplish this. SRB: VOS Release 14.5.0 (R914) 6-28 Arguments Changes to the dump_afte and dump_axte Requests in analyze_system ------------------------------------------------------------------ The dump_afte and dump_axte requests of the analyze_system command have several cache-related changes. For more information, see ``DAE-Related Changes to analyze_system Requests" later in this chapter. Changes to the dump_disk_info Command ------------------------------------- The dump_disk_info command now provides additional information about average and maximum queue time when you specify the -meters argument. In the following example, the new output is shown in boldface. Device Instance Structure @ C119D340 BIO/HSC Disk Driver Device Instance: 9,0 Connections: 2 PDI Info for DS Driver 04/01/01/01, Type D705 at C11D07C0 Disk Meters: connects: 72831 number waiting: 0 busy time: 65384142 seek distance: 0 waiting time: 0 io ops: 202244 dma errors: 0 interrupts: 202244 started io: 68090 reads: 910833 data errors: 0 writes: 19604 device errors: 0 fatal errors: 0 cur consol: 0 max consol: 0 (0) todo q ave: 0.060 active q ave: 1.639 todo busy ave: 2.259 active busy ave: 2.000 todo q usage: 2.684% perf throttle: 00000000 / 0 todo r/w ave: 1.99 / 10.08 ms active r/w ave: 5.29 / 27.54 ms todo r/w max: 2050.99 / 196.04 ms active r/w max: 52.26 / 86.10 ms SRB: VOS Release 14.5.0 (R914) 6-29 Arguments total r/w max: 2059.72 / 234.46 ms total r/w min: 1.15 / 6.46 ms throttled: 0.000% io/interrupt: 4.600 for 930437 max todo count: 14 00-08-22 17:54:10 edt An explanation of the preceding output follows. o The todo data indicates the time that a disk read or write request waited on the disk driver's queue. o The active queue data indicates the time required to access the data on the disk. o The total data indicates the combined waiting and servicing time. Note that the average active queue time measures latency rather than disk- access efficiency. An approximation of average throughput needs to consider block consolidation as well as active queue count, since multiple reads and writes are occurring simultaneously. Dynamically Allocated Extents (DAE) ----------------------------------- Beginning in Release 14.3.0, VOS supports Dynamically Allocated Extents (DAE) files. DAE files offer the following features. o No pre-initialization of the entire file, which is costly with very large files o Maximum extent size of 64 o Dynamic file growth by extent size o A transparent network model: DAE files can be created across networks o Improved performance when sequentially accessing a file (if disk cache space allows) DAE files grow by extent size units. Extent sizes are a power of 2 between 8 and 64. DAE files can support fixed and relative files larger than 2 GB, up to 137 GB in some cases. With DAE, you can specify zero-length files at file creation, thus allowing for the file/index to grow dynamically over time. The extent size is given at file creation, but an extent is not initialized until a block within the extent is first accessed. When you ask for a given block in a DAE file, the corresponding extent is examined. SRB: VOS Release 14.5.0 (R914) 6-30 Dynamically Allocated Extents (DAE) If the disk address has not been assigned, it is calculated on the extent- size boundary and allocated. When the block within the extent is first accessed, all blocks within this extent are initialized. After allocation and initialization are complete, the desired block is returned to the user. Note: By default, VOS creates extent files as Statically Allocated Extent (SAE) files. If you wish to create DAE files, you must use the -dynamic_extents argument of the create_file command. For more information, see ``Command Changes" later in this chapter. If you have upgraded to VOS Release 14.3.0 from another VOS release and wish to downgrade your VOS software after using DAE files, see ``Downgrading from VOS Release 14.5.0" in Chapter 10. The remainder of this section discusses the following topics. o ``File Layout" o ``Command Changes" o ``Reclaiming DAE Reserved Space" o ``Subroutine Changes" o ``Minimizing Disk Fragmentation" o ``Free-Space Emergencies" o ``DAE-Related Changes to analyze_system Requests" File Layout ----------- With the introduction of DAE files, there are now three types of file extents that are set at file creation with the create_file command: simple files, SAE files, and DAE files. o Simple files--The default -extent_size value is 1. The number of records at creation time can be zero or more. If you enter a zero at creation time, a zero-length file is created. If you specify a nonzero number in the -num_records argument, a single block at a time is allocated for the desired number of records. File growth occurs in single blocks. o SAE files--At file creation, you must specify an -extent_size value that is a multiple of 8 and a -num_records value that is greater than zero. For fixed and relative files, the value specified in - SRB: VOS Release 14.5.0 (R914) 6-31 Dynamically Allocated Extents (DAE) num_records should be the maximum number of records in your file; for sequential and stream files, the value specified in -num_records should be the maximum number of blocks in your file. The - extent_size value multiplied by the number of extents determines the size of the file. At this point, all of the disk blocks are allocated and initialized for this file. After the initially allocated area has been used, the file grows in single blocks. o DAE files--At file creation, you must specify an -extent_size value that is a power of 2 between 8 and 64, and specify the - dynamic_extents argument. You may also specify a -num_records value of zero or greater. If zero is entered, a zero-length file is created. The file grows in extent-size units as long as enough contiguous space is available. If sufficient contiguous space for an extent is not available, the error e$insufficient_extent_space (4720) is returned. Command Changes --------------- The following commands have new or changed functionality. o create_file--See ``The create_file Command." o create_index--See ``The create_index Command." o display_file_status--See ``The display_file_status Command." o recreate_index--See ``The recreate_index Command." o restore--See ``The restore command." o set_file_allocation--See ``The set_file_allocation Command." o verify_save--See ``The verify_save Command." o where_block--See ``The where_block Command." For additional information about a specific command, see the VOS Commands Reference Manual (R098). The create_file Command *********************** The create_file command has a new argument: -dynamic_extents. The new display form for the create_file command follows. SRB: VOS Release 14.5.0 (R914) 6-32 Dynamically Allocated Extents (DAE) Display Form ------------------------------------------------------------------------ | --------------------------------- create_file -------------------- | | ------------ | | | | file_name: | | | | -organization: sequential | | | | -record_size: | | | | -num_records: | | | | -extent_size: 1 | | | | -dynamic_extents: no | | | | -character_set: none | | | | -shift_mode: all | ------------------------------------------------------------------------ The create_file command uses the arguments -extent_size and - num_records to control the creation of extent-based files. The - extent_size value multiplied by the number of extents determines the size of the file. You do not need to specify the number of records to implement DAE files. The -dynamic_extents and -extent_size arguments control the type of file that is created, as follows: - If you specify the -dynamic_extents argument with a value of no and specify the -extent_size argument with a value of 1, the operating system creates a simple file. - If you specify the -dynamic_extents argument with a value of no and specify the -extent_size argument with a value that is a multiple of 8, the operating system creates an SAE file. - If you specify the -dynamic_extents argument with a value of yes and specify the -extent_size argument with a value that is a power of 2 between 8 and 64, the operating system creates a DAE file. If you do not specify a value for the -extent_size argument, the error e$invalid_dae_extent_size (7629) is returned. The create_index Command ************************* SRB: VOS Release 14.5.0 (R914) 6-33 Dynamically Allocated Extents (DAE) The create_index command has a new argument: -dynamic_extents. The new display form for create_index follows. Display Form ------------------------------------------------------------------------ | --------------------------------- create_index ------------------- | | ------------ | | | | path_name: | | | | index_name: | | | | key_components: | | | | -type: embedded_key | | | | -collation: ascii | | | | -order: ascending | | | | -extent_size: 1 | | | | -dynamic_extents: no | | | | -num_blocks: 0 | | | | -duplicates: yes | | | | -null_keys: no | | | | -automatic_update: yes | | | | -work_dir: | | | | -duplicate_path: | ------------------------------------------------------------------------ The -dynamic_extents and -extent_size arguments control the type of index that is created, as follows: - If you specify the -dynamic_extents argument with a value of no and specify the -extent_size argument with a value of 1, the operating system creates a simple index. - If you specify the -dynamic_extents argument with a value of no and specify the -extent_size argument with a value that is 8 or a multiple of 8, the operating system creates an SAE index. - If you specify the -dynamic_extents argument with a value of yes SRB: VOS Release 14.5.0 (R914) 6-34 Dynamically Allocated Extents (DAE) and specify the -extent_size argument with a value that is a power of 2 between 8 and 64, the operating system creates a DAE index. If you do not specify a value for the -extent_size argument, the error e$invalid_dae_extent_size (7629) is returned. The display_file_status Command ******************************* The display_file_status command now includes information about the extent type for the file as a whole and for each index associated with the file. The following examples show the output of display_file_status for three different files. Simple File with Nonextent Indexes *********************************** In the following example, the file is a zero-length file. name: %abcd_user>Stratus>JLS>test_file1 file organization: sequential file last used at: 00-05-03 16:23:42 EDT last modified at: 00-05-03 16:22:46 EDT last saved at: never time created: 00-05-03 16:22:46 EDT transaction file: no log protected: no implicit locking: no pipe file: no safety switch: no audit: no dynamic extents: no extent size: 1 next byte : 0 SRB: VOS Release 14.5.0 (R914) 6-35 Dynamically Allocated Extents (DAE) blocks used: 0 num indexes: 2 allocation size: 1 mode: w author: JLS.Stratus tag type: 0 tag version: 0 index name: test_index_11 key components: 1,2 10,15 type: embedded_key collation: ascii data type: nonvarying string ascending: yes duplicates: yes null keys: no extent index: no dynamic extents: no automatic update: yes extent_size: 1 blocks: 0 index name: test_index_12 key components: 4,10 30,5 type: embedded_key collation: ascii data type: nonvarying string SRB: VOS Release 14.5.0 (R914) 6-36 Dynamically Allocated Extents (DAE) ascending: yes duplicates: yes null keys: no extent index: no dynamic extents: no automatic update: yes extent_size: 1 blocks: 0 Statically Allocated Extent File with SAE Indexes ************************************************** name: %abcd_user>Stratus>JLS>test_file2 file organization: sequential file last used at: 99-10-29 16:23:42 EDT last modified at: 99-10-29 16:22:46 EDT last saved at: never time created: 99-10-29 16:22:46 EDT transaction file: no log protected: no implicit locking: no pipe file: no safety switch: no audit: no dynamic extents: no extent size: 8 initial allocated size: 32 SRB: VOS Release 14.5.0 (R914) 6-37 Dynamically Allocated Extents (DAE) next byte: 0 blocks used: 32 num indexes: 1 allocation size: 1 mode: w author: JLS.Stratus tag type: 0 tag version: 0 index name: test_index_21 key components: 1,2 10,15 type: embedded_key collation: ascii data type: nonvarying string ascending: yes duplicates: yes null keys: no extent index: no automatic update: yes dynamic extents: no extent_size: 16 blocks: 0 Dynamically Allocated Extent File with DAE Indexes *************************************************** In the following example, the file was created with the -num_records argument set to 3. SRB: VOS Release 14.5.0 (R914) 6-38 Dynamically Allocated Extents (DAE) name: %abcd_user>Stratus>JLS>test_file3 file organization: sequential file last used at: 00-06-03 16:23:42 EDT last modified at: 00-06-03 16:22:46 EDT last saved at: never time created: 00-06-03 16:22:46 EDT transaction file: no log protected: no implicit locking: no pipe file: no safety switch: no audit: no dynamic extents: yes extent size: 64 next byte : 0 blocks used: 64 num indexes: 2 allocation size: 1 mode: w author: JLS.Stratus tag type: 0 tag version: 0 index name: test_index_31 key components: 1,2 type: embedded_key SRB: VOS Release 14.5.0 (R914) 6-39 Dynamically Allocated Extents (DAE) collation: ascii data type: nonvarying string ascending: yes duplicates: yes null keys: no extent index: yes automatic update: yes dynamic extents: yes extent_size: 32 blocks: 32 index name: test_index_32 key components: 4,10 30,5 type: embedded_key collation: ascii data type: nonvarying string ascending: yes duplicates: yes null keys: no extent index: yes automatic update: yes dynamic extents: yes extent_size: 32 blocks: 32 The recreate_index Command *************************** SRB: VOS Release 14.5.0 (R914) 6-40 Dynamically Allocated Extents (DAE) The output for recreate_index has been modified for DAE files and now includes the fields dynamic extents and extent size. The following output shows an example of the recreate_index command. The command was run on file dae1_8.2, a DAE file with two indexes, index1 and index2. The index1 index is a DAE index. recreate_index dae1_8.2 %abcd_user>Stratus>dae.00-06-06>dae1_8.2 file organization: sequential file last used: 00-06-06 15:32:45 edt last modified: 00-06-06 15:32:45 edt last saved: never time created: 00-06-06 13:51:12 edt transaction file: no implicit locking: no safety switch: no next byte: 0 blocks used: 8 num indexes: 2 allocation size: 1 mode: w author: Susan_Smith.SysAdmin index name: index1 key components: 1,2 type: embedded_key collation: ascii data type: nonvarying string ascending: yes SRB: VOS Release 14.5.0 (R914) 6-41 Dynamically Allocated Extents (DAE) duplicates: yes null keys: no automatic update: yes dynamic extents: yes extent size: 8 blocks: 8 Do you want to continue with index "index1"? (yes, no, info) y index name: index2 key components: 5,10 type: embedded_key collation: ascii data type: nonvarying string ascending: yes duplicates: yes null keys: no automatic update: yes dynamic extents: no extent size: 8 blocks: 8 Do you want to continue with index "index2"? (yes, no, info) y Creating index(es)... Deleting index "index1"... Deleting index "index2"... Creating index "index1" on file %swsle#bozon>dae.00-06-06>dae1_8.2 SRB: VOS Release 14.5.0 (R914) 6-42 Dynamically Allocated Extents (DAE) Create index complete for index "index1" on file %swsle#bozon>dae.00-06-06>dae1_8.2 Creating index "index2" on file %swsle#bozon>dae.00-06-06>dae1_8.2 Create index complete for index "index2" on file %swsle#bozon>dae.00-06-06>dae1_8.2 2 index(es) processed. 1 file(s) processed. The restore command ******************* To convert a simple file to a DAE file, specify the restore command's new argument -dynamic_extents. Note: This command modifies the file's extent type but not the extent type of its indexes. If the -dynamic_extents argument is set to yes, you must also set a value for the -extent_new_size argument. The value can be any power of 2 between 8 and 64. If you do not specify a value for the -extent_new_size argument, the error e$invalid_dae_extent_size (7629) is returned. To restore a DAE file to an SAE file, you must set the -dynamic_extents argument to no, specify the -extent_num_records argument, and enter the desired values for -extent_new_size, using a value that is a multiple of 8. If the -dynamic_extents argument is not set, the file retains its extent type. The display form for the restore command follows. Display Form ------------------------------------------------------------------------ | ----------------------------------- restore ---------------------- | | ------------ | | | | tape_device_or_port_name: | | | | object_names: | |