VOS Administering and Customizing a System r281-03

8/20/2019 VOS Administering and Customizing a System r281-03

1/395

Stratus Computer, Inc.

R281-03

VOS System Administration:

Administering and Customizing a System


2/395

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 COMPUTER, INC., 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 Computer, Inc., 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 Computer, Inc., 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 manuals document all of the subroutines and commands of the user interface. Any other operating-systemcommands and subroutines 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 Computer, Inc.

Stratus, the Stratus logo, Continuum, StrataNET, FTX, and SINAP are registered trademarks of Stratus Computer, Inc.

XA, XA/R, StrataLINK, RSN, Continuous Processing, Isis, the Isis logo, Isis Distributed, Isis Distributed Systems, RADIO,

RADIO Cluster, and the SQL/2000 logo are trademarks of Stratus Computer, Inc.

Apple and Macintosh are registered trademarks of Apple Computer, Inc.

Hewlett-Packard is a trademark of Hewlett-Packard Company.IBM PC is a registered trademark of International Business Machines Corporation.

Intel is a registered trademark of Intel Corporation.

i860 is a trademark of Intel Corporation.

MC68000 and Motorola are registered trademarks of Motorola, Inc.

Sun is a registered trademark of Sun Microsystems, Inc.

Manual Name: VOS System Administration: Administering and Customizing a System

Part Number: R281

Revision Number: 03

VOS Release Number: 14.0.0Printing Date: January 1998

Stratus Computer, Inc.

55 Fairbanks Blvd.

Marlboro, Massachusetts 01752

© 1998 by Stratus Computer, Inc. All rights reserved.


3/395

Contents iii

Contents

Preface xi

1. The System Directory on the Master Disk 1-1The Master Disk 1-1The System Directory 1-2

Controlled System Libraries 1-5The Files in the System Directory 1-6Table Files 1-11Log Files 1-11

Creating a Principal Master Disk 1-11Keeping Printed Copies of Important Files 1-12

2. System Consoles 2-1Installing a System Console 2-1

Installing a System Console on XA/R-Series Modules 2-2The K200 I/O Processor 2-2The K103 I/O Adapter 2-3The K111 I/O Adapter 2-4The K118 I/O Adapter 2-6

Installing a System Console on Continuum-Series Modules 2-8Configuring a System Console 2-10

Modifying the devices.tin File 2-11The devices.tin Fields for System Consoles 2-12Sample System Consoles on XA/R-Series Modules 2-16Sample System Consoles on Continuum-Series

Modules 2-17Creating a devices.table File 2-17Updating the Disk Label 2-18Summary of System Console Characteristics 2-19


4/395

Contents

iv VOS System Administration: Administering and Customizing a System (R281)

3. Setting and Defining Priority Levels 3-1Setting Priority Levels 3-1

Changing the Priority of a Process 3-2Defining Priority Levels 3-2

Time Slices 3-2Sockets 3-5Installation Software Scheduling Parameters 3-5

Interactive-Process Scheduling Priorities 3-7Batch-Process Scheduling Priorities 3-7

Changing Scheduling Parameters 3-8

4. Setting a Module’s Default Command Limits 4-1Setting the Default Heap Limits 4-1Setting the Default Stack Limits 4-2Setting the Default Total Limits 4-3

5. The Batch Processor 5-1Batch Queues 5-2

Starting the normal Batch Queue 5-2Creating Batch Queues 5-3Restricting Access Rights to Batch Queues 5-3Deleting Batch Queues 5-3Starting a Batch Queue 5-4Stopping a Batch Queue 5-5

Managing Batch Traffic 5-6 Automatic Management (Load Control) 5-6Manual Intervention 5-6

6. The Load Control Facility 6-1Calculating the Load 6-2

Setting the Threshold Values 6-2The Load Control Tables 6-3The load_configuration.table File 6-4

The load_configuration.dd File 6-4The Fields in the load_configuration.table File 6-4Sample load_configuration.tin File Entries 6-5

The load_control.table File 6-6The load_control.dd File 6-6


5/395

Contents

Contents v

The Fields in the load_control.table File 6-7Sample load_control.tin File Entries 6-8

Load Control Tables in the Installation Software 6-9Changing a Load Control Table 6-10

Enabling the Load Control Facility 6-11Disabling the Load Control Facility 6-12Creating a Load Control Histogram 6-12

Sample Load Control Histogram 6-13

7. The Remote Service Network 7-1RSN Overview 7-2The RSN Bridge Module and the MaintBridgeServer Process 7-2The MaintServer Process 7-3The maint_request Command 7-3The Site Call System 7-4The comment_on_manual Command 7-5Remote Site Security 7-6RSN Files and the rsn_dir Directory 7-7Updating the RSN 7-8The Mail Facility 7-9

The mail Request of the maint_request Command 7-9The rsn_mail Command 7-9

8. Updating Program Modules 8-1The create_pm_var_file Command 8-1The update_program_module Command 8-2Updating Program Modules Online 8-3

9. The Accounting Facility 9-1The accounting_admin Command 9-1

Accounting Logs 9-1 Accounting Records 9-2

Types of Accounting Records 9-2Default Process Logging 9-3Command Logging 9-3Extended Process Logging 9-4File Logging 9-4Transaction Logging 9-5Port Logging 9-6

Administration Logging 9-6Monitoring Disk Usage 9-7


6/395

Contents

vi VOS System Administration: Administering and Customizing a System (R281)

The dump_accounting_file Command 9-7Processing the Accounting Logs 9-7

10. Customizing Status Codes and Messages 10-1

Status Code Definitions 10-1The Status Code Files 10-2The error_codes.dd File 10-3Defining Additional Status Codes 10-3

The Fields in the user_codes.tin File 10-3Sample user_codes.tin File Entry 10-4Defining or Modifying Your Own Status Codes 10-4

Modifying the Text of a Status Message 10-5The Fields in the error_codes.tin File 10-5Sample error_codes.tin File Entry 10-6

Setting System Defaults in the error_codes.tin File 10-6Setting Values for the -processor Argument 10-7Setting Values for the -mapping_rules Argument 10-10

11. Modifying Module and System Identifiers 11-1Restrictions 11-1Renaming a Module 11-2Renaming a System 11-7Modifying a Module and/or Station Number 11-13

Renumbering a System 11-16Modifying Your Site ID 11-18

12. Customizing Your Module’s Prelogin Screen 12-1

13. Managing the Help Subsystem 13-1The Status of the Help System 13-1The Kinds of Help Text Available 13-2

Where Help Files Are Stored in the File System 13-2How Help Files Are Named 13-2Files That Can Be Adapted for Local Information 13-3Storing Translated Help Files 13-4

14. Commands 14-1


7/395

Contents

Contents vii

accounting_admin 14-3add_default_library_path 14-6analyze_system 14-10batch 14-12batch_admin 14-17batch_overseer 14-19broadcast 14-20cancel_batch_requests 14-22check_jiffy_times 14-25comment_on_manual 14-27create_batch_queue 14-31create_os_symtab 14-32create_pm_var_file 14-33delete_default_library_path 14-37display_calendar_clock 14-40display_lock_wait_time 14-41

display_scheduler_info 14-43display_software_changes 14-46display_software_purchased 14-48display_tuning_parameters 14-50dump_accounting_file 14-53freeze_process 14-55link_boot_server 14-59list_default_cmd_limits 14-61list_default_library_paths 14-63list_kernel_programs 14-65load_control_admin 14-67load_control_histogram 14-69load_kernel_program 14-70log_syserr_message 14-77maint_request 14-79make_message_file 14-90network_watchdog 14-92notify_hardware_error 14-94overseer 14-96process_broadcast_queue 14-98rsn_mail 14-100

rsn_mail_janitor 14-105set_bootload_time 14-107set_date_time 14-109set_default_library_paths 14-114set_default_time_zone 14-119set_jiffy_times 14-123set_lock_wait_time 14-127set_priority 14-129


8/395

Contents

viii VOS System Administration: Administering and Customizing a System (R281)

set_scheduler_info 14-131set_system_log_mode 14-134set_tuning_parameters 14-135site_call_system 14-139

Site Call System Requests 14-151The add_call Request 14-152The add_court_value Request (Privileged) 14-155The change_call Request 14-156The comment_on_manual Request 14-157The display_call Request 14-158The help Request 14-160The list_calls Request 14-161The list_court_values Request 14-169The maint_request Request 14-170The new_call Request 14-171The purge_calls Request 14-172

The quit Request 14-176The remove_court_value Request (Privileged) 14-177The rsn_mail Request 14-178The set_mode Request 14-179The update_calls Request 14-180

start_mailhandler 14-184start_rsn 14-186start_site_call_xfer 14-190thaw_process 14-192tp_overseer 14-195unload_kernel_program 14-202update_codes 14-204update_default_cmd_limits 14-205update_program_module 14-212update_software_purchased 14-214validate_hub 14-216wait_for_overseer 14-217wait_for_tp_overseer 14-218

Appendix A. The VOS Internal Character Code Set A-1

Appendix B. Terminal Key Sequences B-1

Index Index-1


9/395


10/395

x VOS System Administration: Administering and Customizing a System (R281)

Tables

Table 1-1. The Subdirectories in the System Directory 1-2Table 1-2. The Files in the System Directory 1-6Table 2-1. Console Controller Values in the devices.tin File 2-13Table 2-2. Summary of System Console Characteristics 2-19Table 6-1. Load-Control Log File Abbreviations 6-11Table 9-1. Default Process Logging 9-3Table 9-2. Command Logging 9-3Table 9-3. Extended Process Logging 9-4Table 9-4. File Logging 9-5

Table 9-5. Transaction Logging 9-6Table 9-6. Port Logging 9-6Table 13-1. Help Files Relating to Important Operations 13-3Table 14-1. Time Zones Supported in VOS 14-120Table 14-2. Types of Recovery 14-200Table A-1. VOS Internal Character Sets A-1Table B-1. Operator Key Sequences (By Function Key) B-1Table B-2. Operator Key Sequences (By VOS Function) B-2


11/395

Preface xi

Preface

The manual VOS System Administration: Administering and Customizing aSystem (R281) documents the procedures for administering Stratus modules.

This manual is intended for system administrators.

Manual Version

This manual is a revision. Change bars, which appear in the margin, note the specificchanges to text since the previous publication of this manual. Note, however, that

change bars are not used in new chapters or appendixes.

This revision incorporates the following changes.

• Most of the information that is specific to XA2000-series modules has beenremoved, since VOS Release 14.0.0 does not support XA2000-series modules.Some examples have been updated to reflect output from XA/R- andContinuum-series modules.

• Chapter 1 includes new descriptions of important table files.

• Chapter 2 has been extensively rewritten to include new information about

installing a system console on XA/R- and Continuum-series modules.• Chapter 3 includes more detailed information about assigning socket numbers for

use in various networking configurations.

• Chapter 4 provides new heap, stack, and total program module memory limits forXA/R- and Continuum-series modules.

• Chapter 5 has been reorganized and provides additional information about batchqueues.

• Chapter 6 provides more information about load control histograms.

• Chapter 7 includes more information about changing the name of a Remote

Service Network (RSN) bridge module.

• Chapter 8 has been extensively rewritten to include new examples thatdemonstrate how to update a program module online.

• Chapter 9 includes more detailed information about the accounting facility.

• Chapter 10 has been updated to include new processor family status messages.


12/395

Preface

xii VOS System Administration: Administering and Customizing a System (R281)

• Chapter 11 describes several new restrictions that you should be aware of beforeyou change the module or system name, the module, station, or system number,or the site ID.

• Chapter 13 provides new information about the status of the help system.

• Chapter 14 provides updated information about the following commands:

analyze_system, display_scheduler_info,display_software_purchased, display_tuning_parameters,link_boot_server, load_kernel_program, maint_request, rsn_mail, set_date_time, set_default_time_zone, set_jiffy_times,set_scheduler_info, set_tuning_parameters, site_call_system,tp_overseer, and update_default_cmd_limits. Chapter 14 alsodocuments four new commands: freeze_process, list_kernel_programs,thaw_process, and unload_kernel_program.

• Appendix A provides the complete VOS internal character code set.

• Appendix B describes key mappings for the V105 terminal with the PC/+ 106keyboard and the V105 terminal with the ANSI keyboard.

Manual Organization

This manual contains 14 chapters and 2 appendixes.

Chapter 1 documents the (master_disk)>system directory.

Chapter 2 describes how to install and configure a system console.

Chapter 3 explains how to set and define priority levels for each process running on a

module.

Chapter 4 describes how to set a module’s default command limits.

Chapter 5 explains how to administer the batch processor.

Chapter 6 describes the load control facility.

Chapter 7 documents the Remote Service Network (RSN).

Chapter 8 describes how to use the wide area network to receive program module

updates.

Chapter 9 describes the accounting facility.

Chapter 10 describes how to customize your module’s status codes and statusmessages.

Chapter 11 describes how to modify important module and system identifiers.


13/395

Preface

Preface xiii

Chapter 12 describes how to customize your module’s prelogin screen.

Chapter 13 explains how to manage the help subsystem.

Chapter 14 documents system administration commands.

Appendix A lists the VOS internal character code set.

Appendix B lists operator key sequences for the Stratus-supported terminal types.

Related Manuals

Refer to the following Stratus manuals for related documentation.

• VOS PL/I Subroutines Manual (R005)

• SOS Administrator’s Guide (R042)

• VOS Communications Software: RJE Facility (R051)

• VOS C Subroutines Manual (R068)

• VOS System Analysis Manual (R073)

• VOS Commands User’s Guide (R089)

• VOS Communications Software: X.25 and StrataNET Administration (R091)

• Customer Support System Reference Manual (R094)

• VOS Commands Reference Manual (R098)

• VOS StrataLINK Administrator’s Guide (R192)

• VOS Transaction Processing Facility Guide (R215)

• Stratus V103 Terminal User’s Guide (R239)

• VOS System Administration: Starting Up and Shutting Down a Module orSystem (R282)

• VOS System Administration: Registration and Security (R283)

• VOS System Administration: Disk and Tape Administration (R284)

• VOS System Administration: Backing Up and Restoring Data (R285)

• VOS System Administration: Administering the Spooler Facility (R286)

• VOS System Administration: Configuring a System (R287)

• VOS Administrator’s Guide for Open StrataLINK (R388)

• Continuum 600 and 1200 Series: Site Planning Guide (R391)


14/395

Preface

xiv VOS System Administration: Administering and Customizing a System (R281)

• Continuum Operation and Maintenance: 600 and 1200 Series (R396)

• Product Release Bulletin: VOS Configuration for the V105 Terminal (R439)

• VOS Continuum 600 and 1200 Series with PA-8000: Operation and MaintenanceGuide (R445)

Notation Conventions

This manual uses the following notation conventions.

• Italics introduces or defines new terms. For example:

The master disk is the name of the member disk from which the module wasbooted.

• Boldface emphasizes words in text. For example:

Every module must have a copy of the module_start_up.cm file.

• Monospace represents text that would appear on your terminal’s screen (such ascommands, subroutines, code fragments, and names of files and directories).For example:

change_current_dir (master_disk)>system>doc

• Monospace italic represents terms that are to be replaced by literal values. In thefollowing example, the user must replace the monospace-italic term with a literalvalue.

list_users -module module_name

• Monospace bold represents user input in examples and figures that contain bothuser input and system output (which appears in monospace). For example:

display_access_list system_default

%dev#m1>system>acl>system_default

w *.*


15/395

Preface

Preface xv

Key Mappings for VOS Functions

VOS provides several command-line and display-form functions. Each function ismapped to a particular key or combination of keys on the terminal keyboard. Toperform a function, you press the appropriate key(s) from the command-line or displayform. For an explanation of the command-line and display-form functions, see the

manual Introduction to VOS (R001).

The keys that perform specific VOS functions vary depending on the terminal. Forexample, on a V103 ASCII terminal, you press the and keys simultaneouslyto perform the INTERRUPT function; on a V105 PC/+ 106 terminal, you press the keyon the numeric keypad to perform the INTERRUPT function.

Certain applications may define these keys differently.Refer to the documentation for the application for thespecific 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 ® or compatible PC that isrunning the Stratus PC/Connect-2 software. (If your PC is running another type ofsoftware 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, referto the documentation for that terminal.

VOS Function

V103

ASCII

V103

EPC

IBM PC or

Compatible

PC

V105

PC/+ 106

V105

ANSI

CANCEL *†

† Numeric-keypad key

*†

†

or *†

CYCLE - †

CYCLE BACK - - - † -

DISPLAY FORM - † - † † or - † or-

HELP - - - -

INSERT DEFAULT - - - -

INSERT SAVED

INTERRUPT - - - † -

NO PAUSE - - * † -

† -


16/395

Preface

xvi VOS System Administration: Administering and Customizing a System (R281)

Format for Commands and Requests

Stratus manuals use the following format conventions for documenting commands andrequests. (A request is typically a command used within a subsystem, such asanalyze_system). Note that the command and request descriptions do notnecessarily include all of the following sections.

name

The name of the command or request is at the top of the first page of thedescription.

Privileged

This notation appears after the name of a command or request that can be issuedonly from a privileged process. (See the online glossary, which is located in the file>system>doc>glossary.doc, for the definition of privileged process.)

add_disk Privileged

PurposeThe add_disk command tells the operating system on the currentmodule to recognize the specified logical volume for the duration ofthe current bootload.

Display Form

Command Line Formadd_disk disk_name

[ module_name ]

Argumentsdisk_name

The name of the logical volume to be recognized for the currentbootload.

. . .

H

AB

C

D

E

F

G

-------------------------- add_disk ------------------------- disk_name:

module_name: current_module

Required

A

B


17/395

Preface

Preface xvii

Purpose

Explains briefly what the command or request does.

Display Form

Shows the form that is displayed when you type the command or request namefollowed 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 anargument has a default value, that value is displayed in the form. (See the onlineglossary for the definition of default value.)

The following table explains the notation used in display forms.

The Notation Used in Display Forms

Command-Line FormShows the syntax of the command or request with its arguments. You can displayan online version of the command-line form of a command or request by typing thecommand 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 ormore object names. Specifying multiple values is not the same as specifying a starname. (See the online glossary for the definition of star name.) When you specifymultiple values, you must separate each value with a space.

The Notation Used in Command-Line Forms

Notation Meaning

Required field with no default value.

The cursor, which indicates the current position on thescreen. For example, the cursor may be positioned on thefirst character of a value, as in ll.

current_user

current_module

current_system

current_disk

The default value is the current user, module, system, ordisk. The actual name is displayed in the display form of thecommand or request.

Notation Meaning

argument_1 Required argument.

argument_1... Required argument for which you can specify multiple values.

C

D

a

E


18/395

Preface

xviii VOS System Administration: Administering and Customizing a System (R281)

Arguments

Describes the command or request arguments. The following table explains thenotation used in argument descriptions.

The Notation Used in Argument Descriptions

The following additional headings may appear in the command or requestdescription: Explanation, Error Messages, Examples, and Related Information.

Explanation

Explains how to use the command or request and provides supplementaryinformation.

Ç È Set of arguments that are mutually exclusive; you must specifyone 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 canspecify 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 than two elements. Brackets and bracesare sometimes nested.

Notation Meaning

There are predefined values for this argument. In the displayform, 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 avalue for this argument.

If an argument is required but has a default value, it is not labeledRequired since you do not need to specify it in the command-lineform. However, in the display form, a required field must have avalue—either the displayed default value or a value that youspecify.

(Privileged) Only a privileged process can specify a value for this argument.

Notation Meaning

argument_1

argument_2

argument_1

argument_2

F

G

H


19/395

Preface

Preface xix

Error Messages

Lists common error messages with a short explanation.

Examples

Illustrates uses of the command or request.

Related InformationRefers you to related information (in this manual or other manuals), includingdescriptions of commands, subroutines, and requests that you can use with or inplace of this command or request.

Online Documentation

Stratus provides the following types of online documentation.

• The directory >system>doc provides supplemental online documentation. Itcontains the latest information available, including updates and corrections to

Stratus manuals and a glossary of terms.• Stratus offers some of its manuals online, via StrataDOC, an online-documentation

product that consists of online manuals and StrataDOC Viewer, delivered on aCD-ROM (note that you must order StrataDOC separately). StrataDOC Viewerallows you to access online manuals from an IBM PC or compatible PC, a Sun ® orHewlett-Packard workstation, or an Apple ® Macintosh ® computer. StrataDOCprovides such features as hypertext links and, on the workstations and PCs, textsearch and retrieval across the manual collection. The online and printed versionsof a manual are identical.

If you have StrataDOC, you can view this manual online.

For a complete list of the manuals that are available online as well as moreinformation about StrataDOC, contact your Stratus account representative.

Ordering Manuals

You can order manuals in the following ways.

• If your system is connected to the Remote Service Network (RSN), issue themaint_request command at the system prompt. Complete the on-screen formwith all of the information necessary to process your manual order.

• 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. Allother customers can contact their nearest Stratus sales office, CAC office, ordistributor; see the file cac_phones.doc in the directory >system>doc for CACphone numbers outside the U.S.

Manual orders will be forwarded to Order Administration.


20/395

Preface

xx VOS System Administration: Administering and Customizing a System (R281)

Commenting on This Manual

You can comment on this manual by using the command comment_on_manual or bycompleting the customer survey that appears at the end of this manual. To use thecomment_on_manual command, your system must be connected to the RSN. If yoursystem is not connected to the RSN, you must use the customer survey to comment

on this manual.

The comment_on_manual command is documented in the manual VOS SystemAdministration: Administering and Customizing a System (R281) and the VOSCommands Reference Manual (R098). There are two ways you can use this commandto send your comments.

• If your comments are brief, type comment_on_manual, press or , andcomplete the data-entry form that appears on your screen. When you havecompleted the form, press .

• 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 . Enterthis manual’s part number, R281, then enter the name of your comments file in the-comments_path field. Press the key that performs theCYCLE function to changethe value of -use_form to no and then press .

If comment_on_manual does not accept the partnumber of this manual (which may occur if the manual isnot yet registered in the manual_info.table file), youcan 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.


21/395

The System Directory on the Master Disk 1-1

Chapter 1

The System Directory on theMaster Disk1-

The VOS installation software , the software that is included with every new module,includes important system configuration files. Many of these files are stored in the(master_disk)>system directory (hereafter referred to as the system directory).

This chapter describes the contents of the system directory and outlines twoprocedures to follow when setting up your system. It includes the following sections.

• ‘‘The Master Disk”

• ‘‘The System Directory”

• ‘‘Creating a Principal Master Disk”

• ‘‘Keeping Printed Copies of Important Files”

The Master Disk

The master disk is the name of the member disk from which the module was booted.

In the case of automatic bootload, it is the lowest-numbered disk on thelowest-numbered disk controller in the chassis. In the case of a manual boot, it is thedisk selected manually during the boot sequence.

In an automatic bootload, the master disk on each module is the disk that is attachedto the disk controller or input/output processor (IOP) that is in the lowest-numberedchassis slot.

When you specify commands, you can reference the master disk with the commandfunction (master_disk). This is equivalent to the name of the top directory in thatdisk’s directory hierarchy. Since some of the files in the system directory are used toboot the module, the master disk is also known as the boot disk .

In a manual bootload, the disk that you select during the boot sequence is the defaultmaster disk for the bootload.

For more information about master disks, refer to the manual VOS SystemAdministration: Disk and Tape Administration (R284).


22/395

The System Directory

1-2 VOS System Administration: Administering and Customizing a System (R281)


Each master disk contains a system directory, which contains many subdirectories andfiles. The contents of this directory vary dramatically depending on the products forwhich your site has licenses.

This section describes the subdirectories and files your system directory must contain.

Table 1-1 lists the subdirectories required for the system directory.

• accounting

Contains log files created by the accounting facility.

• cac

Contains tools used by the Stratus Customer Assistance Center (CAC).

• command_library

Contains all external commands shipped with the operating system.

• configuration

Contains input data files for table files. (See the manual VOS SystemAdministration: Configuring a System (R287) for a definition of table files.) Thisdirectory also contains copies of the module_start_up.cm file and the .table files.

Table 1-1. The Subdirectories in the System Directory

Subdirectories

accounting cac

command_library configuration†

css_command_library doc error

firmware†

help include_library

kernel_loadable_library

message_library object_library

pc/connect-term prom_code

queues† release_dir† rsn_dir†

sample_programs spooler transaction_logs†

† Indicates that the directory is not system controlled. See thesection ‘‘Controlled System Libraries” later in this chapter formore information.


23/395



• css_command_library

Contains the commands for the Customer Service System.

• doc

Contains copies of previous and current software release bulletins (SRBs) and

other online documentation. This directory also contains subdirectories fordocumentation on separately shipped products, as well as a series of files thathave names in the form product _loaded.info. Do not delete these productfiles.

• error

Contains the files used as input to the error codes table. See Chapter 10,‘‘Customizing Status Codes and Messages,” for more information.

• firmware

Contains files that hold user microcode for the PSI board and the operatingsystem-provided microcode for the High-Speed Async, High-Speed SyncI, andHigh-Speed SyncII line adapters.

• help

Contains a file of information that appears in response to the debug command’shelp request.

• include_library

Contains include files to which the compilers and the assembler must have access.

• kernel_loadable_library

Contains the program modules that are loaded using the load_kernel_program command. These include communications drivers, Forms Management System,and Stratus Office Solution.

• message_library

Contains per-command message files and help files. All Stratus-supplied files arein the subdirectory us_english.

• object_library

Contains object modules referenced by the binder.

• pc/connect-term

Contains the PC images for portions of the PC/Connect terminal emulationsoftware.


24/395



• prom_code

Contains microcode for use by Stratus personnel only.

• queues

Contains directories that hold queue files for the spooler, batch, and Remote Job

Entry facilities.

• release_dir

Contains files used during the installation of a new release of the operating system.

• rsn_dir

Contains files received from the hub of the Stratus Remote Service Network (RSN),which is described in Chapter 7, ‘‘The Remote Service Network.” This directory ison one module within each system that is part of the RSN. This directory is usefulonly if your system has a Stratus maintenance contract.

• sample_programs

Contains subdirectories of sample programs and any site-modifiable source forvarious parts of the operating system.

• spooler

Contains printer and spooler-related files. The spooler directory contains thespooler_configuration.v1.table file and may contain site-specific printerinformation. For more information on this table, see the manual VOS SystemAdministration: Administering the Spooler Facility (R286).

• transaction_logs

Contains a log of all transactions and a work area for use in completingtransactions.


25/395



Controlled System Libraries

The installation procedure imposes restrictions on the contents of most systemlibraries. (The libraries that are not system controlled are marked with a dagger (†) inTable 1-1.) The contents of these controlled system libraries are managed by theinstallation tools, and after the installation is complete, these libraries contain only

those files supported in the particular release. This results in the automatic deletion ofobsolete or renamed commands, documentation files, and so on.

If your site has added files or links to these libraries, theywill be deleted by the installation process.

If you have stored user-written application programs or macros in controlled systemlibraries, you must create separate user libraries for these files and move them. Youcan set up local libraries by performing the following procedure.

1. Create a directory to be used for your local library; for example,>system>applications_library.

2. Edit the module_start_up.cm file to add the add_default_library_path and add_library_path commands for the directory>system>applications_library.

3. Move user-written programs and macros into this library.

The file >system>error>user_codes.tin is notdeleted by the installation tools if the file exists at your site.


26/395



The Files in the System Directory

Table 1-2 lists the files required for the system directory.

Some of the .table and .log files are described in the ‘‘Table Files” and ‘‘Log Files”sections, respectively, later in this chapter. Here is a brief description of the other

necessary files in the system directory.

• abbreviations

Contains standard abbreviations for many operating system commands. Theoperating system reads this file when the use_abbreviations command isexecuted (usually at user startup).

Table 1-2. The Files in the System Directory

Files

abbreviations

backbone_systems.table

batch.one_way_server_queue

batch.server_queue

boards.table

broadcast_queue.message_queue

change_password.sysdb

current_release

devices.table

disks.table

echo_eventedit_help.table

error_codes.text

file_broadcaster.log

firmware.table

gateways.table

hardware_error_event

hardware_log.(date)

HUB.comm_MQ

HUB.comm_SQ

HUB.config

HUB.disk_dataHUB.msg_SQ

install_new_files.cm

load_configuration.table

load_control_event

load_control_log.(date)

load_control.server_queue

load_control.table

Module_Config

Module_Config.txt

module_start_up.cm

modules.table

network_access.table

network_routes

new_backbone_systems.table

new_modules.table

new_systems.table

nodes.table

noticesoverseer.message_queue

overseer.server_queue

remote_maint_log.(date)

rje_host_file

rsn_disk_threshold.table

security_log.(date)

software_purchase_table.table

spooler_configuration.table

spooler_configuration.v1.table

start_up.cm

syserr_log.(date)syserr_log_event

system_attributes.table

system_classes.table

system_libraries.table

system_red_light_event

systems.table

user_registration.sysdb


27/395



When the registration_admin command creates a home directory for a newuser, the command copies this file to the home directory. You can change thecontents of this file to suit your system, and individual users can tailor their copiesof the file to their own needs. See the VOS Commands User’s Guide (R089) forinformation about the abbreviations facility.

• batch.one_way_server_queue batch.server_queue

Communicate with the Batch Overseer process. The Overseer usesbatch.one_way_server_queue to communicate with the Batch Overseer;certain commands, such as batch_admin, use batch.server_queue forcommunications to and from the Batch Overseer. See Chapter 5, ‘‘The BatchProcessor.”

• broadcast_queue.message_queue

Holds broadcast requests issued with the broadcast_file command. You can

display the contents of this file with the list_broadcast_requests command,and you can delete a request from the file with thecancel_broadcast_requests command. See the manual VOS SystemAdministration: Configuring a System (R287) for more information about thesecommands.

• change_password.sysdb

user_registration.sysdb

Registration database files, created by the command create_user_sysdbs.

• current_release

A file used by the software that installs a new release of the operating system.

• echo_event

hardware_error_event

syserr_log_event

system_red_light_event

Create empty files that provide file names for events that are notified in cases suchas hardware errors.

• error_codes.text

Contains information about all of the operating system error codes. This file iscreated by the update_codes command. See Chapter 10, ‘‘Customizing StatusCodes and Messages.”

• file_broadcaster.log

An output file created by the most recent execution of the broadcast_file command.


28/395



• firmware.table

A table that associates communication protocols with firmware and adapters on asystem.

• hardware_log.(date)

syserr_log.(date)Contain the messages that the operating system writes to the hardware log andsystem error log files.

System error log files are created by the operating system with implicit locking:once opened for input, the current day’s system error log file cannot be deleted untilit is closed at the end of the day.

Keep these log files for at least two weeks. If the CAC is investigating problems onyour module, contact the CAC to verify that the information is no longer neededbefore deleting the files.

• HUB.comm_MQ

HUB.comm_SQ

HUB.config

HUB.disk_data

HUB.msg_SQ

remote_maint_log.(date)

Files used by the Remote Service Network (RSN), which is described in Chapter 7,‘‘The Remote Service Network.” Some of these files are on only one module withineach system that is part of the RSN. The RSN files are useful only if your system

has a Stratus maintenance contract.

Keep remote maintenance log files for two weeks, and then delete them.

• install_new_files.cm

A file that contains a command macro used in module startup to install programs,such as the Overseer, that cannot be installed when the system is running.

• load_control_event

load_control_log.(date)

load_control.server_queue

These files and the load control table files are used by the operating system tomeasure the load on a module. See Chapter 6, ‘‘The Load Control Facility,” for adescription of the load control facility.

Keep load control log files for two weeks, and then delete them.


29/395



The load control facility creates a file whenever it starts a process to increase theload on the module. Information about the process is written to a file namedstart_process.ilaN , which is placed in the system directory. In the file name,ila means “increase load action,” and N is the count of these files that have beencreated on the module.

• Module_Config

A machine-readable file that contains complete configuration information about thecurrent module, used by the CAC.

• Module_Config.txt

A text version of the Module_Config file, used by the CAC.

• module_start_up.cm

Contains commands that the operating system uses at module startup. This file

must be present in the system directory of every module.For protection against loss of the module_start_up.cm file, the installationsoftware stores a standard copy of this file in the >system>configuration directory. Always keep a printed copy of the current version of this file, since yoursite may have modified it.

See the manual VOS System Administration: Starting Up and Shutting Down aModule or System (R282) for a detailed description of module_start_up.cm.

• network_routes

Contains information about StrataNET routing for wide area network operation.This file is useful only if your system includes the StrataNET communicationsnetwork. See the manual VOS Communications Software: X.25 and StrataNETAdministration (R091) for information about wide area networks.

• notices

An ASCII text file containing messages for module users. The operating systemdisplays this file when the display_notices command is executed (usually atuser startup). You maintain this file.

• overseer.message_queueUsed by servers to communicate with each other.

• overseer.server_queue

Used by certain commands (for example, batch_admin) for communication toand from the Overseer process.


30/395



• rje_host_file

Holds host records for the Remote Job Entry (RJE) facility. See the manual VOSCommunications Software: RJE Facility (R051) for information about the RJEsubsystem.

• security_log.(date)Contains a record of each attempt by a user to access files and directories inviolation of the system’s access control. See the manual VOS SystemAdministration: Registration and Security (R283) for more information.

Security log files are created by the operating system with implicit locking: onceopened for input, the current day’s security log file cannot be deleted until it isclosed at the end of the day.

Keep these log files for two weeks, and then delete them.

• start_up.cm

A user command macro executed upon user login. The following example showsa simple start_up.cm file.

use_abbreviations

&if (process_type) = batch &then &return

display_notices

At login, the user process reads start_up.cm from the user’s home directory.The use_abbreviations command tells the operating system to recognize the

abbreviations in the abbreviations file in the user’s home directory. Thedisplay_notices command displays on the user’s terminal all files and alltargets of links to files matching the star name(master_disk)>system>notices*.

When the registration_admin command creates a home directory for a newuser, the command copies this macro to the home directory. You can change thecontents of the start_up.cm file to suit your system, and individual users cantailor their copies of the file to their own needs. For example, system administratorsmay want to include in their start_up.cm files the commandsnotify_hardware_error, notify_security_violation, and rsn_mail.

• system_attributes.table

Contains information necessary to collect the module’s hardware configurationinformation that is used by the CAC.

• system_classes.table

Contains information necessary to collect the system attributes information usedby the CAC.


31/395

Creating a Principal Master Disk


Table Files

The system directory contains several files whose names have the suffix .table.These are table files .

Most table files are created by the create_table command from input files containedin the configuration directory. The following table files are exceptions.

• the system_libraries.table file is created by the installation procedure

• the rsn_disk_threshold.table, system_attributes.table, andsystem_classes.table files are created by the CAC

See the manual VOS System Administration: Configuring a System (R287) forinformation about these files.

The new_modules.table, new_systems.table, andnew_backbone_systems.table files are used in conjunction with cross-moduleand cross-system communications products (for example, Open StrataLINK, traditional

or cluster StrataLINK, and X.25 StrataNET). For information about Open StrataLINK,see the VOS Administrator’s Guide for Open StrataLINK (R388). For information abouttraditional StrataLINK or cluster StrataLINK, see the VOS StrataLINK Administrator’sGuide (R192). For information about X.25 StrataNET, see the manual VOSCommunications Software: X.25 and StrataNET Administration (R091).

Log Files

The system directory contains several files whose names have the suffix .(date).These are log files .

For each type of log file, the operating system starts a new file each day when it writesthe first entry after 12:00 a.m. The .(date) suffix of each file name is the date the logwas written. For example:

hardware_log.97-11-01

If you specify a log file name with .(date) instead of the actual date, the operatingsystem uses the current date. Keep log files for two weeks, and, unless they are beingused to help debug a system problem, delete them.

Creating a Principal Master DiskIn a multimodule system, you can keep the configuration directory on the masterdisk of only one module. The master disk containing this directory is then known as theprincipal master disk . It should be on a fully duplex module. The module that containsthe principal master disk should also have the MaintBridgeServer process.


32/395

Keeping Printed Copies of Important Files


To access the configuration directory from other modules, create a link from eachof the other modules to the principal master disk. For information about creating links,see the description of the link command in the VOS Commands ReferenceManual (R098).

Perform the following steps to designate one master disk as the principal master disk.

1. Choose a master disk on a fully duplexed module to be the principal master disk.

2. Delete the configuration directory from every other module in the system.

3. In the directory (master_disk)>system on every other module, create links tothe configuration directory in the (master_disk)>system directory on themodule containing the principal master disk.

All references in this manual to the configuration directory assume that, if yoursystem has more than one module, you have followed these steps to create a link tothe principal master disk.

Keeping Printed Copies of Important Files

The file error_codes.tin is stored in the error directory and contains the text ofthe operating system error messages. Keep a printed copy of this file, in case youcannot access the online file. See Chapter 10, ‘‘Customizing Status Codes andMessages,” for more information about this file.

Also keep a printed copy of each module’s module_start_up.cm file, in case youlose both copies of that file.


33/395

System Consoles 2-1

Chapter 2

System Consoles2-

A system console , also called a monitor terminal , is a terminal that displays informationabout the module to which it is connected. In addition to displaying system messages,the system console also enables you to enter system commands and reboot themodule.

This chapter describes how to install and configure a system console. It contains thefollowing sections.

• ‘‘Installing a System Console”

• ‘‘Configuring a System Console”

Installing a System Console

A system console requires specialized hardware components. The following sectionsdescribe these hardware components and explain how to install a system console onXA/R- and Continuum-series modules.

• ‘‘Installing a System Console on XA/R-Series Modules”• ‘‘Installing a System Console on Continuum-Series Modules”


34/395



Installing a System Console on XA/R-Series Modules

Each Stratus system requires one calendar/clock and one RSN connection (the RSNconnection performs remote maintenance of the network). Each module in the systemalso requires one system console. On XA/R-series modules, the K200 I/O processor,in conjunction with one of the following K-series I/O adapters, provides the system

console connection.

• the K103 Remote Service Communications I/O Adapter

• the K111 Null-Modem MultiCommunications I/O Adapter

• the K118 Asynchronous I/O Adapter

The following sections describe these hardware components.

• ‘‘The K200 I/O Processor”

• ‘‘The K103 I/O Adapter”



The K200 I/O Processor

The K200 I/O processor manages a set of K-series I/O adapters that connect devicesto XA/R-series modules. The K200 I/O processor resides in the main chassis with theprocessor boards. Stratus recommends that the K200 I/O processor for the boot devicebe located in the lowest-numbered slot possible in the main chassis.

The K200 I/O processor is fully self-checking and operates in duplex. Duplex operationrefers to two partner boards performing the same function. If one partner fails, the otherpartner continues functioning, thereby saving the module from any down-time.(Simplex operation, by contrast, refers to one board operating by itself.) All Stratus I/Oprocessors except tape controllers are intended for duplex operation.

To operate in duplex, the partner K200 I/O processors must be in adjacent slots in aneven/odd sequence, where the first I/O processor in the pair is in an even slot and thesecond I/O processor is in the next higher-numbered odd slot. For example, I/Oprocessors residing in slots 2 and 3 are a duplex pair, but those residing in slots 7 and8 (adjacent odd/even slots) are not a duplex pair.


35/395


System Consoles 2-3

Figure 2-1 illustrates a K200 I/O processor pair in slots 2 and 3 of the main chassis ofa 12-slot XA/R module.

Figure 2-1. A K200 I/O Processor Pair Installed in an XA/R-Series Module

For more information about the K200 I/O processor, see the manual VOS SystemAdministration: Configuring a System (R287).

The K103 I/O Adapter

The K103 Remote Service Communications I/O Adapter provides the followingfeatures for XA/R-series modules.

• a battery-backed calendar/clock

• a full-modem RS-232-C line for the RSN

• a null-modem RS-232-C line for the system console

The K103 I/O adapter provides two RS-232-C connectors, which correspond to

subchannels 0 and 1. The top connector (subchannel 0) is reserved for the systemconsole; the bottom connector (subchannel 1) is reserved for the RSN.

12-Slot Main Chassis

K200 I/O Processor

Memory Board

Memory Board

Link Controller

Processor Board

Link Controller

K200 I/O Processor

Processor Board 01

3

4

5

6

7

8

9

2

1011

AD0693


36/395



Figure 2-2 illustrates the K103 I/O adapter’s two RS-232-C connectors.

Figure 2-2. The K103 I/O Adapter

The K103 I/O adapter must reside in slot 0 (the rightmost slot) of the I/O adapterchassis connected to the first K200 I/O processor pair. The K103 I/O adapter uses 18bulk watts of power.

For more information about the K103 I/O adapter, see the manual VOS SystemAdministration: Configuring a System (R287).


The K111 Null-Modem MultiCommunications I/O Adapter provides four RS-232-Cconnectors, which typically connect local terminals or printers to a module via adirect-connect cable. Its four DB-25 connectors correspond to four subchannelsnumbered 0-3, where 0 is the top connector. The maximum baud rate forasynchronous lines associated with terminal devices using paced input is 19,200 (9600for asynchronous lines associated with nonkeyboard devices using continuous input,such as printers).

K103I/O Adapter

subchannel 0 isfor the systemconsole

subchannel 1 isfor the RSN

subchannel 2 is forthe calendar/clock(no connector necessary)

Clock

1

2

0

RS-232-CInterface

AD0699


37/395


System Consoles 2-5

If the K103 I/O adapter or the K118 Asynchronous I/O Adapter does not provide thesystem console connection for an XA/R-series module, the K111 I/O adapter(subchannel 0) can provide the system console connection. To provide the connection,the K111 I/O adapter must reside in slot 0 of the I/O adapter chassis connected to thefirst K200 I/O processor pair.

Figure 2-3 illustrates the K111 I/O adapter’s four RS-232-C connectors.


The K111 I/O adapter uses the following amounts of power.

– The K111 AA-K10100 I/O adapter uses 19.8 bulk watts of power.

– The K111 AA-K10120 I/O adapter uses 20 bulk watts of power.

For more information about the K111 I/O adapter, see the manual VOS SystemAdministration: Configuring a System (R287).

K111I/O Adapter

RS-232-C

Interface

0

1

2

3

subchannel 0 isfor the systemconsole

AD0698


38/395




The K118 Asynchronous I/O Adapter supports 16 asynchronous lines in anycombination of full-modem or null-modem functionality. The K118 I/O adapter uses anRS-232-C interface and has a calendar/clock. The maximum baud rate forasynchronous lines associated with terminal devices using paced input is 19,200 (9600for asynchronous lines associated with nonkeyboard devices using continuous input,such as printers).

Like the K103 I/O adapter, the K118 I/O adapter can provide the system consoleconnection for XA/R-series modules, as well as the full-modem RSN connection andthe calendar/clock for the system. To provide the system console connection,subchannel 0 of the K118 I/O adapter must be configured for a direct connection, andthe I/O adapter must reside in slot 0 of the I/O adapter chassis connected to the firstK200 I/O processor pair.

The K118 I/O adapter has two 100-pin connectors that can connect it to a stand-alone

enclosure box containing two 100-pin connectors and 16 RS-232-C connectors. Thetop connector on the I/O adapter is labeled B and can use a 12-foot (for enclosureboxes) or 25-foot (for NP cabinets) cable to connect to the 100-pin connector labeledB on the back of the freestanding enclosure box. (Note that there is a package availablefor this adapter that allows an unenclosed version of the box to be rack-mounted in anI/O expansion cabinet.) The bottom 100-pin connector on the I/O adapter is labeled Aand uses a 12- or 25-foot cable to connect to the 100-pin connector labeled A on theback of the enclosure box. Each 100-pin connector governs a set of eight DB-25connectors, and each set of connectors governs eight device subchannels.

Figure 2-4 illustrates the K118 I/O adapter, the enclosure box, the 100-pin connectors,

and the distribution panel of the enclosure box.


39/395


System Consoles 2-7


The K118 I/O adapter uses 29.5 bulk watts of power.

For more information about the K118 I/O adapter, see the Installation Guide: K118Asynchronous I/O Adapter (R324) and the Site Planning Guide: K118 AsynchronousI/O Adapter (R325). For information about the packages available for this I/O adapter,contact your Stratus representative.

K118I/O Adapter

A

B100-Pin

Connectors

Up to16RS-232-C

Connections

K118Distribution Panel

in Stand-AloneEnclosure Box

Front of K118 Distribution Panel

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

AB

A

B

AD0695


40/395



Installing a System Console on Continuum-Series Modules

On Continuum-series modules, the console controller provides the system consoleconnection. The console controller serves as the system’s central collection point formaintenance and diagnostic information, the interface to the RSN, and the control pointfor the system’s power.

Figure 2-5 illustrates the console-controller interfaces.

Figure 2-5. Console-Controller Interfaces

The console controller has four serial ports configured for asynchronouscommunication. Three of the ports are configured for RS-232 communication: one portis used for the RSN connection, and two ports are used by the system console and asecond (remote) console for displaying system messages and entering systemcommands. The fourth console-controller port is configured for RS-485 communication

and is used to collect system maintenance and diagnostic information from the cabinetdata collectors (CDCs) located in each Continuum cabinet.

System Bus

CPU 0

SystemConsole

OnlineConsole Controller

Second (Remote)Console

RSNModem

Maintenanceand Diagnostics

CPU 1

StandbyConsole Controller

CAC

Bus

cm0004


41/395


System Consoles 2-9

Console controllers ensure continuous availability by providing hot standby for oneanother; that is, the second console controller is always ready to assumeconsole-controller functions if the first controller fails. The console controller is the onlyI/O board powered by its own housekeeping power supply, which initiates the systempower-on sequence.

The console controllers reside in slots CC0 and CC1, to the right of the main chassis.Figure 2-6 illustrates the console controllers in the main chassis of a 12-slot Continuummodule using PA-7100 processors.

Figure 2-6. Console Controllers in a 12-Slot Continuum Module

Console

Controllers

PS00 1 3 4 5 6 7 8 9 10 112 PS1

CC00 1 3 4 5 6 7 8 9 10 112 CC1

AD0679


42/395

Configuring a System Console


Figure 2-7 illustrates the console controllers in the main chassis of a 6-slot Continuummodule using PA-7100 processors.

Figure 2-7. Console Controllers in a 6-Slot Continuum Module

For more information about console controllers, see the manual VOS SystemAdministration: Configuring a System (R287).


XA/R- and Continuum-series modules support two types of system consoles:dedicated and acting.

• A dedicated system console is a terminal that serves exclusively as the systemconsole and is never used as a login terminal. When the Overseer Initializationprocess (used during a manual boot) logs out, the dedicated system consoleresumes the display of messages from the syserr.log.(date) file.

• An acting system console is a terminal that serves temporarily as a systemconsole. It receives system messages only during the initial stages of bootloading.When the Overseer Initialization process used during a manual boot logs out, the

1 3 50 2 4 PS0 PS1

Console

Controllers

1 3 50 2 4 CC0 CC1

AD0680


43/395


System Consoles 2-11

acting system console is available (for use as a login terminal) and systemmessages are written only to the syserr.log.(date) file.

Stratus recommends that you configure a terminal as a dedicated system console andthat you locate the terminal near the module to which it is connected. Do not configurea printer as a system console since a keyboard is required to perform a manual startup.

Also, though terminal responses are rarely required during automatic startup, you mayneed to respond to prompts from the operating system.

The following sections describe how to configure a system console.

• ‘‘Modifying the devices.tin File”

• ‘‘Creating a devices.table File”

• ‘‘Updating the Disk Label”

• ‘‘Summary of System Console Characteristics”

Modifying the devices.tin File

Whether you choose to configure a dedicated or acting system console, you mustdefine the system console in the device configuration-table file (devices.table).This file enables VOS to recognize all of the devices that reside within a system ofStratus modules. The devices.table file is compiled from a pair of files: a datadescription file (devices.dd) and its corresponding table input file (devices.tin).

The devices.table, devices.dd, and devices.tin files reside in the(master_disk)>system>configuration directory of each module. You typically

edit the devices.tin file that resides in the(master_disk)>system>configuration directory of the designated mastermodule. For detailed information about the devices.table, devices.dd, anddevices.tin files, see the manual VOS System Administration: Configuring aSystem (R287).

The following sections describe how to modify the devices.tin file for use withsystem consoles.

• ‘‘The devices.tin Fields for System Consoles”

• ‘‘Sample System Consoles on XA/R-Series Modules”

• ‘‘Sample System Consoles on Continuum-Series Modules”


44/395



The devices.tin Fields for System Consoles

This section describes the devices.tin fields that pertain to system consoles. Notethat some of the fields apply only to XA/R-series modules, while others apply only toContinuum-series modules.

*name

Specifies the name assigned to the system console. Make sure that no two entriesuse the same name.

* module_nameSpecifies the name of the module to which the system console is connected.

* terminal_typeSpecifies the terminal type of the system console (for example,v105, v105_ansi,v103, or v103_ascii). You can specify any type of terminal that is compiled andinstalled on the system.

See the Product Configuration Bulletin: Asynchronous Devices (R289) for moreinformation about specifying a terminal type.

* device_typeSpecifies the type of device providing the system console connection. OnXA/R-series modules using the K103, K111, or K118 I/O adapter, the value mustbe terminal. On Continuum-series modules using the console controller, thevalue must be window_term.

*slot

On Continuum-series modules, if the console controller provides the systemconsole connection, specify the value 36.

On XA/R-series modules, if the K103, K111, or K118 I/O adapter provides thesystem console connection, this field identifies the main-chassis slot that containsthe lowest-numbered K200 I/O processor in the module. The value you specifymust be an even number that represents the lower-numbered partner of theduplexed pair.

If this field identifies a K200 I/O processor, you must also specify values for theadapter_slot_no and adapter_subchannel_no fields.


45/395



* channelSpecifies the channel number of the system console connection provided by theconsole controller. The console controller provides connections for a primarysystem console, a secondary (or shadow) system console, and an RSNconnection. Specify one of the values listed in Table 2-1.

This field does not apply to XA/R-series modules.

* adapter_slot_noIdentifies the I/O adapter chassis slot number of the K103, K111, or K118 I/Oadapter providing the system console connection. The I/O adapter chassis slotmust always be 0 for system console connections. In addition, the I/O adapter inthe slot must be connected to the first K200 I/O processor pair in the module.

This field does not apply to Continuum-series modules.

* adapter_subchannel_noIdentifies the I/O adapter subchannel number providing the system console

connection. The I/O adapter subchannel number must use subchannel 0 of theappropriate I/O adapter in slot 0 of the I/O adapter chassis, and the subchannelmust be configured as a direct-connect subchannel.

This field is applicable only if the slot field identifies a K200 I/O processor and theadapter_slot_no field identifies a K103, K111, or K118 I/O adapter. This fielddoes not apply to Continuum-series modules.

* baud_rateSpecifies the baud rate of the system console. The system console must use abaud rate of 9600.

You must verify that the system console uses a baud rate of 9600. See the StratusV103 Terminal User’s Guide (R239) and the Product Release Bulletin: VOSConfiguration for the V105 Terminal (R439) for instructions on checking or settingthe baud rate.

Table 2-1. Console Controller Values in the devices.tin File

channel Field Value Definition

0 Primary monitor terminal

1 Secondary monitor terminal

2 RSN connection


46/395



* stop_bitsSpecifies the number of stop bits (either 1 or 2) associated with each character.The system console requires a stop bit value of 1.

You must verify that the system console uses a stop bit value of 1. See the StratusV103 Terminal User’s Guide (R239) and the Product Release Bulletin: VOS

Configuration for the V105 Terminal (R439) for instructions on checking or settingthe number of stop bits.

* paritySpecifies the parity assumed by the system console. The parity field can haveone of the following values: odd, even, mark, space, baudot, and none. Whenparity is set to none, eight bits of data are transmitted and received. When parityis mark or space, the parity bit is ignored on input and set to mark or space,respectively, on output. The system console requires odd parity.

You must verify that the system console uses odd parity. See the Stratus V103Terminal User’s Guide (R239) and the Product Release Bulletin: VOSConfiguration for the V105 Terminal (R439) for instructions on checking or settingthe parity.

* login_slaveSpecifies whether the system console is a dedicated (slave) or acting (login)system console. The value 0 specifies a dedicated system console; the value 1 specifies an acting system console. Stratus recommends that you specify thevalue 0 to configure a dedicated system console.

*priv_terminal

Specifies whether a privileged process can log in on the system console. Specifythe value 0 (no) for a dedicated system console. Specify the value 1 (yes) for anacting system console.

* prom_direct_connectSpecifies whether the K118 I/O adapter subchannel is configured for a directconnection. If you are configuring the subchannel for a direct connection of asystem console, specify the value 1 in this field and the value 0 in theprom_full_modem field. If you are configuring the subchannel for the RSNfull-modem connection, specify the value 0 in this field and the value 1 in the

prom_full_modem field.

You should specify both the prom_direct_connect field and the prom_full_modem field for eachsubchannel of a K118 I/O adapter. The configuration


47/395


48/395



Sample System Consoles on XA/R-Series Modules

The following sample devices.tin file entry defines a dedicated system console onthe XA/R-series module m2. The system console is a V103 terminal connected to eithera K103 or K111 I/O adapter.

/ =name mterm.1

=module_name m2

=terminal_type v103

=device_type terminal

=slot 2

=adapter_slot_no 0

=adapter_subchannel_no 0

=baud_rate 9600

=stop_bits 1

=parity odd

=login_slave 0

=priv_terminal 0=comment system console

The following sample devices.tin file entry defines an acting system console onthe XA/R-series module m12. The system console is a V103 ASCII terminal connectedto a K118 I/O adapter.

/ =name mterm.1

=module_name m12

=terminal_type v103_ascii

=device_type terminal

=slot 2

=adapter_slot_no 0

=adapter_subchannel_no 0

=baud_rate 9600

=stop_bits 1

=parity odd

=login_slave 0

=priv_terminal 0

=prom_direct_connect 1

=comment system console


49/395



Sample System Consoles on Continuum-Series Modules

The following sample devices.tin file entry defines a dedicated, primary systemconsole on the Continuum-series module m8. The system console is a V105 terminalconnected to channel 0 of the console controller.

/ =name mterm.1

=module_name m8

=terminal_type v105

=device_type window_term

=slot 36

=channel 0

=baud_rate 9600

=stop_bits 1

=parity odd

=login_slave 0

=priv_terminal 1

=comment system console (primary)=parameters '-access_layer recc_al'

The following sample devices.tin file entry defines a dedicated, secondary systemconsole on the Continuum-series module m8. The system console is a V105 terminalconnected to channel 1 of the console controller.

/ =name mterm.2

=module_name m8

=terminal_type v105

=device_type window_term

=slot 36=channel 1

=baud_rate 9600

=stop_bits 1

=parity odd

=priv_terminal 1

=comment system console (secondary)

=parameters '-access_layer recc_al'

Creating a devices.table File

After you define the system console in the devices.tin file, you must convert theconfiguration information to a machine-executable devices.table file. Issue thecreate_table command from the directory(master_disk)>system>configuration to generate a new devices.table file, as follows:

create_table devices


50/395



After you generate a devices.table file, you must copy it to the(master_disk)>system directory on all modules in the system (including thecurrent module), as follows:

broadcast_file devices.table >system

The devices.table file does not take effect until the next bootload, when themodule_start_up.cm file executes theconfigure_devices command. However,you can issue the configure_devices command on each module so that theoperating system on the current module immediately recognizes all of the newlydefined devices in the devices.table file.

For more information about the create_table, broadcast_file, andconfigure_devices commands, see the manual VOS System Administration:Configuring a System (R287).

Updating the Disk LabelIn addition to copying the devices.table file to the (master_disk)>system directory on all modules in the system, you must also update the disk label associatedwith the master disk on each module.

If you are configuring a dedicated system console, you must issue theupdate_disk_label command and specify yes as the value for the-monitor_terminal argument. This sets the value of the -monitor_terminal field in the module’s master disk label to on. The value of this field is significant only forthe master disk in each module. This change takes effect at the next bootload. If youwant to make a change that will be effective only during the current bootload, use theupdate_channel_info command to alter the login configuration of the systemconsole.

If you are configuring an acting system console, you must issue theupdate_disk_label command and specify no as the value for the-monitor_terminal argument. This sets the value of the -monitor_terminal field in the module’s master disk label to off. The value of this field is significant onlyfor the master disk in each module. This change takes effect at the next bootload.

You can set the disk label’s -monitor_terminal field

with the initialize_boot_disk command only wheninitializing a boot disk.

Summary of System Console Characteristics

Table 2-2 summarizes the differences between dedicated and acting system consoles.


51/395



Table 2-2. Summary of System Console Characteristics

Characteristic/Value Dedicated System Console Acting System Console

Unique entry in devices.tin =login_slave field 0 1

Setting of disk label’s

-monitor_terminal switch yes no

Login? No Yes

Keyboard active? For system prompts only At all times

Receive system messages? Anytime, except when manualboot process logs in. Messagesresume when process logs out.

During bootload only.Messages stop either whenmanual boot process logs inor when automatic boot ends.


52/395


53/395

Setting and Defining Priority Levels 3-1

Chapter 3

Setting and DefiningPriority Levels3-

Stratus modules support two types of processes: interactive and batch processes.Interactive processes are started with the login command. Batch processes arestarted with the batch command, the start_process command, or thes$start_process subroutine.

The operating system schedules CPU time for each interactive and batch processrunning on a module based on the following criteria: the priority level of each processand the parameters that define the meaning of the priority levels. There are 10 prioritylevels, 9 being the highest and 0 the lowest.

This chapter explains how to set and define priority levels. It contains the followingsections.

• ‘‘Setting Priority Levels”

• ‘‘Defining Priority Levels”

Setting Priority Levels

The priority of an interactive process, if you do not specify a different priority, is yourdefault priority . It is set in the Priority field of your entry in the registration database.If your entry does not contain a value for this field, the operating system assigns adefault priority of 0.

The registration database also can assign a maximum priority , which limits how high apriority can be on a process that you start. This value is assigned in the Max Priority field. If no value is assigned, the operating system assigns a maximum priority of 0.

Whenever you start a process, you can assign a priority to the process. There are threecommands (login, batch, and start_process) and one subroutine(s$start_process) with which you can start a process, and each of these has anargument for setting the priority of the process. (The priority cannot be higher than yourmaximum priority.) When you do not assign a priority for a new interactive process, theoperating system assigns your default priority, and for a new batch process, theoperating system assigns the priority of the calling process.


54/395

Defining Priority Levels


Changing the Priority of a Process

Once a process is started, you can change its priority by issuing the set_priority command. In the command, if you are privileged, you can specify one or moreprocesses by providing values for the arguments process_name and -useruser_name. Both arguments accept star names. If you do not specify any processes,

the operating system changes the priority of the process issuing the command.

You can make the following changes in the priority of a process by issuing theset_priority command.

• change the priority of another user’s process

• assign to a process a higher priority than the maximum priority of the user whoowns the process—This applies to all processes, including your own.

The following command assigns a priority of 7 to the user Smith’s process namedmake_report on the current module.

set_priority 7 make_report -user Smith

The following command assigns a priority of 6 to all of your processes on module m7.

set_priority 6 * -module m7


Priority levels are built into the installation software, but you can also define priority with

the set_scheduler_info command. Chapter 14 describes this command.

The following sections discuss defining priority levels.

• ‘‘Time Slices”

• ‘‘Sockets”

• ‘‘Installation Software Scheduling Parameters”

• ‘‘Changing Scheduling Parameters”

Time Slices

A time slice is an interval of CPU time that the operating system allocates to a process.The amount of CPU time that a process receives depends on the attributes of the timeslices assigned to that priority level and process type. These attributes are built into theinstallation software, as shown in Figure 3-1, and they can be changed, as describedin ‘‘Changing Scheduling Parameters” later in this chapter.


55/395


Setting and Defining Priority Levels 3-3

Time slices have the following attributes:

* typeSpecifies the priority, represented by a number between 1 and 255, with a type-1time slice having the highest priority and a type-255 time slice having the lowestpriority.

* countSpecifies the number of time slices of the type specified that a process can receive.The range is from 1 to 16.

* timeSpecifies the number of milliseconds that the operating system allocates for eachtime slice of the type specified. The range of allowed values is 100 to 32,000milliseconds (one-tenth of a second to 32 seconds).

When you assign a time slice type, you must assign count and time values for that type.

Assign values for these attributes in the set_scheduler_info command, asdescribed in ‘‘Changing Scheduling Parameters” later in this chapter. Thedisplay_scheduler_info command displays the attributes presently assigned.

For scheduling purposes, processes are ordered by their time slice types, beginningwith the lowest. The operating system does not include the time spent waiting for I/Oin a process’s time slice.

Each priority level/process type can have up to four time slice types, withcorresponding count and time values assigned to it. Each time a process uses all of the

time slices specified by a count value, it switches to the next time slice type. Thiscontinues until the process reaches the last of the given time slice types, where itcontinues to process regardless of the specified count. When a process finishesprocessing and enters wait mode , the operating system returns the process to the timeslice type specified first for that process priority.

Pre-emption is the default. Several times per second, thescheduler interrupts running processes to determine ifthere is a more eligible process to run.

The following example defines the time slices assigned to batch processes with a

priority of 0. The SKT (socket) field represents an address on a module used fornetwork communications and is explained in the ‘‘Sockets” section later in this chapter.

-----BATCH-----

PRI SKT TYPE CNT TIME

0 1 14 1 1.00

In this example, the operating system allocates the batch process a single type-14 timeslice that is 2 seconds in length.


56/395



The following example defines the time slices assigned to any interactive process witha priority of 2.

--INTERACTIVE--

PRI SKT TYPE CNT TIME

2 1 2 1 0.25

6 5 1.00 6 5 0.50

10 1 0.50

For example, assume that the process compile_reports has a priority of 2. Theoperating system allocates CPU time to the process using the time slice definitionsdisplayed in the previous example. The following sequence explains this allocation inmore detail.

Documents

VOS Administering and Customizing a System r281-03