Virtual Hometerm Subsystem (VHS) Manual

Virtual Hometerm Subsystem (VHS) Manual Abstract This manual describes the Compaq NonStop Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications by emulating a 6530 terminal. Product Version Not applicable. Supported Releases This manual supports G06.15 and D48.03 and all subsequent Gxx.xx and Dxx.xx releases until otherwise indicated in a new edition. Part Number Published 429311-001 February 2002

Document History Part Number Product Version Published 429311-001 NA February 2002

Virtual Hometerm Subsystem (VHS) Manual Glossary Index Examples Figures Tables What s New in This Manual xiii Manual Information xiii What s New and Changed xiii About This Manual xv Audience xv Prerequisite Products and Manuals Related Products and Manuals xv Manual Organization xvi Your Comments Invited xvii Notation Conventions xvii xv 1. Introduction to VHS Benefits of VHS 1-1 VHS Architecture 1-2 VHS and Management Applications 1-2 VHS Subsystem 1-2 VHS and the Application Environment 1-3 VHS Components 1-3 VHS Browser 1-5 Using Multiple VHS Processes 1-7 VHS on a Node 1-8 Setting Up VHS Environments 1-9 VHS on a Network 1-10 Centralizing VHS EMS Events 1-12 2. Installing VHS VHS System Requirements 2-2 VHS Disk Space Requirements 2-2 Installation Summary 2-2 Creating the VHS Installation Subvolume (ISV) 2-3 Installing the VHS Subsystem Components 2-4 Installing VHS for the First Time 2-5 Compaq Computer Corporation 429311-001 i

Contents 2. Installing VHS (continued) 2. Installing VHS (continued) Updating VHS 2-5 Installing the VHS and VHSCI Programs and the VHS GUI Agent Facility 2-7 VHS, VHSCI and VHS GUI Agent Installation Procedure 2-12 Installing the VHS Browser in ViewPoint 2-14 VHS Browser Restrictions 2-17 VHS Browser Installation in ViewPoint Procedure 2-17 ViewPoint Installation Considerations 2-19 Installing the VHS Browser as a Stand-Alone Pathway System 2-23 VHS Browser Restrictions 2-26 VHS Browser Installation as a Stand-Alone Pathway System Procedure 2-26 Pathway Installation Considerations 2-28 Modifying the VHS Configuration Files 2-29 VHSSTART File 2-30 VHSINSP File 2-33 VHSCSTM File 2-33 VHSBCONF File 2-33 VHSGCONF File 2-35 VHS Run-Time Options 2-36 VHS ASSIGNs 2-36 VHS Parameters 2-37 VHS DEFINE Parameter 2-38 3. Using VHS Before Using VHS 3-1 Starting VHS 3-1 Sample VHSSTART File 3-3 Guidelines for Running VHS 3-4 VHS Run Syntax 3-4 Specifying VHS as the Home Terminal of Applications 3-7 Non-Pathway Applications 3-7 Pathway Application Example 1 3-7 Pathway Application Example 2 3-8 How VHS Manages Messages 3-9 OPEN Message Processing 3-10 Display Message Processing 3-10 Inspect Prompt Processing 3-10 Debug Prompt Processing 3-11 Application Prompt Processing 3-11 ii

Contents 3. Using VHS (continued) 3. Using VHS (continued) Reply Message Processing 3-11 Configuring VHS Inspect Processing 3-12 VHS AUTOMATIC-INSPECT-PROCESSING Parameter 3-12 Inspect Processing Considerations 3-12 VHS Inspect File 3-12 Understanding the VHS Log Files 3-16 PRIMARY-LOGFILE-PURGE Parameter 3-16 Secondary Log Destination 3-17 Stopping VHS 3-17 Using VHS With a ViewPoint Filter 3-18 4. Using the VHS Browser Accessing the VHS Browser 4-1 VHS Installed in ViewPoint 4-1 VHS Installed as a Stand-Alone Pathway System 4-2 High PIN Support 4-3 Exiting the VHS Browser 4-3 VHS Installed in ViewPoint 4-3 VHS Installed as a Stand-Alone Pathway System 4-4 VHS Screen Navigation 4-5 VHS Screen Format 4-5 Help Screens 4-6 Paging Through Help 4-7 Log Browser Screen 4-8 Changing Search Criteria 4-8 Getting Environment Detailed Information 4-8 Paging Through the Log File 4-8 Log Browser Screen Field Descriptions 4-11 Log Browser Screen Function Keys 4-12 Search Text Field 4-12 Date and Object-Name Display 4-13 Prompt Browser Screen 4-13 Changing Search Criteria 4-13 Getting Environment Detailed Information 4-13 Going to a Specific Page 4-14 Getting Detailed Prompt Information 4-14 Replying to a Prompt 4-14 Prompt Browser Screen Field Descriptions 4-15 iii

Contents 4. Using the VHS Browser (continued) 4. Using the VHS Browser (continued) Prompt Browser Screen Function Keys 4-16 Prompt Detail Screen 4-16 Replying to a Prompt 4-16 Prompt Detail Screen Field Descriptions 4-17 Prompt Detail Function Key Descriptions 4-18 VHS Profile Screen 4-18 Switching Systems 4-21 Switching VHS Browser Servers 4-21 Switching PATHMONs 4-21 Switching Environments 4-21 Changing the Screens Automatic Update 4-22 VHS Profile Screen Field Descriptions 4-22 VHS Profile Screen Function Keys 4-23 Environment Detailed Screen 4-23 Getting Environment Detailed Information 4-24 Setting the Current Environment 4-24 Paging Through the Existing Environments 4-24 Environment Detailed Screen Field Descriptions 4-25 Environment Detailed Screen Function Keys 4-26 Printing a Screen 4-26 5. Using VHSCI Getting Started 5-1 Running VHSCI 5-1 Exiting VHSCI 5-3 Entering VHSCI Commands 5-4 Configuring Function Keys 5-5 Setting Detail Error Display 5-7 Setting the Output Destination 5-8 Editing the VHSCI Custom Configuration File 5-8 Using Online Help 5-9 Getting Statistics 5-15 Getting Status Information 5-15 Listing All Current Openers 5-16 Getting Information About and Modifying VHS Parameters 5-17 Getting Information About the VHS Parameters 5-17 Modifying a VHS Parameter 5-18 Getting Information About and Modifying Log Destinations 5-19 iv

Contents 5. Using VHSCI (continued) 5. Using VHSCI (continued) Getting Information About the Log Configuration 5-19 Adding a Secondary Log 5-20 Modifying a Secondary Log 5-21 Deleting a Secondary Log 5-22 Switching the Backup CPU to the Primary CPU 5-23 Getting Information About a VHS Environment 5-25 6. Command Components Objects and Object Lists 6-1 Object-Spec Variable 6-1 Attributes and Attribute Values 6-2 Attribute-Spec Variable 6-2 Strings, Integers, and Time Values 6-2 Char Variable 6-3 Integer Variable 6-3 Time Variable 6-4 Disk File Names 6-4 File Specification 6-4 7. Command Descriptions Exclamation Point (!) Command 7-2 Question Mark (?) Command 7-3 ALIAS Command 7-4 ALLOW Command 7-5 ALTER Command 7-7 ASSIGN Command 7-13 ASSUME Command 7-16 CLEAR Command 7-18 COMMENT Command 7-19 CONFIRM Command 7-19 CPUS Command 7-20 DELAY Command 7-22 DETAIL ERROR Command 7-23 ENV Command 7-23 EXIT Command 7-24 FC Command 7-24 HELP Command 7-25 HISTORY Command 7-27 v

Contents 7. Command Descriptions (continued) 7. Command Descriptions (continued) INFO Command 7-27 LISTOPENS Command 7-32 LOG Command 7-34 OBEY Command 7-34 OUT Command 7-36 PAGESIZE Command 7-36 PARAM Command 7-37 PAUSE Command 7-38 REPEAT Command 7-38 RUN Command 7-39 SETPROMPT Command 7-40 STATS Command 7-42 STATUS Command 7-44 SYSTEM Command 7-49 TIMEOUT Command 7-50 VERSION Command 7-51 VOLUME Command 7-52 8. The VHS GUI Introduction to the VHS GUI 8-1 VHS GUI Overview 8-1 Host Installation Requirements 8-1 VHS GUI Architecture 8-2 Windows NT Workstation 8-2 Compaq Server - Central Node 8-3 Compaq Server - Remote Node 8-3 VHS GUI Installation 8-4 Starting the VHS GUI 8-5 The New VHS Parameters 8-5 EMS Event Messages Generated by VHS 8-6 Use of Alternate EMS Collectors 8-6 Restricting VHS GUI User Capability 8-7 Broadcasting 8-9 Single Node Recommended Setup 8-9 Multiple Node Recommended Setup 8-9 vi

Contents A. VHS Files A. VHS Files VHSCSTM File A-1 VHSSTART File A-2 VHSBCONF File A-3 B. VHS Limits C. VHS Event Messages VHS Event Messages C-1 VHS Application-Related Events C-1 VHS Internal Events C-1 VHS Browser Events C-3 VHS Token List C-3 SPI Standard Definitions C-3 EMS Standard Definitions C-5 VHS Definitions C-6 VHS Token Definitions C-6 VHS Value Definitions C-7 Private Token and Field Types C-7 Predefined Token and Field Values C-7 Simple Tokens C-8 Description of VHS Event Messages C-8 Unconditional and Conditional Tokens C-8 1: ZVHS-EVT-INSPECT-SAVE C-9 2: ZVHS-EVT-INSPECT-NOSAVE C-11 3: ZVHS-EVT-INSPECT-OBEY C-14 4: ZVHS-EVT-INSPECT-SCOBOL C-16 5: ZVHS-EVT-DEBUG-ERROR C-19 6: ZVHS-EVT-DISPLAY C-21 7: ZVHS-EVT-PROMPT C-24 8: ZVHS-EVT-PROMPT-REPLY C-28 100: ZVHS-EVT-VHS-STARTED C-31 101: ZVHS-EVT-BACKUP-CREATED C-32 102: ZVHS-EVT-PRIMARY-LOG-CREATED C-34 103: ZVHS-EVT-PRIMARY-LOG-ROLLOVER C-35 104: ZVHS-EVT-CREATE-BACKUP-FAILED C-37 105: ZVHS-EVT-BACKUP-STOPPED C-39 106: ZVHS-EVT-BACKUP-DELETED C-40 107: ZVHS-EVT-BACKUP-ABENDED C-42 vii

Contents C. VHS Event Messages (continued) C. VHS Event Messages (continued) 108: ZVHS-EVT-TAKEOVER C-43 109: ZVHS-EVT-CHECKPOINT-FAILED C-45 110: ZVHS-EVT-CHECKOPEN-FAILED C-47 111: ZVHS-EVT-PRIMARY-LOG-IO-ERROR C-49 112: ZVHS-EVT-PROCESS-DELETED C-51 113: ZVHS-EVT-ALTERNATE-CREATED C-53 114: ZVHS-EVT-PROMPT-IO-ERROR C-54 115: ZVHS-EVT-PROMPT-FILE-CREATED C-56 116: ZVHS-EVT-PROMPT-ALT-CREATED C-57 117: ZVHS-EVT-CLEAN-PROMPT-FILE C-59 118: ZVHS-EVT-REMOVE-PROMPT C-61 119: ZVHS-EVT-BAD-REPLY C-63 120: ZVHS-EVT-CONFIG-IO-ERROR C-65 121: ZVHS-EVT-INVALID-LINE-FORMAT C-66 122: ZVHS-EVT-COLLECTOR ERROR C-68 123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE C-69 124: ZVHS-EVT-INSP-INVALID-FILENAME C-71 125: ZVHS-EVT-INSP-INVALID-PROCESS C-73 126: ZVHS-EVT-INSP-DUPLICATE-SEC C-75 127: ZVHS-EVT-INSP-TABLE-FULL-DATA C-77 128: ZVHS-EVT-INSP-TABLE-FULL-SEC C-78 129: ZVHS-EVT-INSP-PROCESSING-STOP C-80 130: ZVHS-EVT-INSP-TOO-MUCH-PROMPT C-81 131: ZVHS-EVT-OPEN-TABLE-THRESHOLD C-83 132: ZVHS-EVT-INSP-INVALID-PARAM C-84 133: ZVHS-EVT-INSP-LOAD-FILE-ERR C-86 134: ZVHS-EVT-OPENEDIT-ERROR C-87 135: ZVHS-EVT-READEDIT-ERROR C-89 136: ZVHS-EVT-SET-DEFINE C-90 137: ZVHS-EVT-INSP-RELOAD-FILE C-92 138: ZVHS-EVT-PROMPT-CANCEL C-93 139: ZVHS-EVT-PROMPT-NOT-UNIQUE C-96 140: ZVHS-EVT-INSP-INVALID-KEYWORD C-98 141: ZVHS-EVT-INSP-LINE-TOO-LONG C-100 143: ZVHS-EVT-INSP-LOAD-FILE C-101 144: ZVHS-EVT-INSP-RELOAD-FILE-ERR C-103 145: ZVHS-EVT-INSP-INVALID-REMOTE C-104 146: ZVHS-EVT-INSP-FILE-NOT-EXIST C-106 viii

Contents C. VHS Event Messages (continued) C. VHS Event Messages (continued) 147: ZVHS-EVT-INSP-INVALID-TEXT C-108 148: ZVHS-EVT-CLEAN-TABLE C-110 150: ZVHS-EVT-INSPECT-EXTENDED C-112 151: ZVHS-EVT-INSPECT-APPL-EXT C-114 152: ZVHS-EVT-INSPECT-SCOBOL-EXT C-117 153: ZVHS-EVT-DEBUG-EXTENDED C-120 154: ZVHS-EVT-PROMPT-RESEND C-123 200: ZVHS-EVT-INTERNAL-ERROR C-127 D. VHSCI Command Summary E. VHS Process Messages F. VHS Browser Messages G. VHSCI Messages Message Descriptions G-1 Interprocess Communication Messages G-22 H. VHS DDL Files VHS Primary Log File H-1 Log File Format H-2 File and Spooler H-2 I. ViewPoint Event Filter Glossary Index Examples Example 2-1. VHS Custom Startup File 2-31 Example 2-2. VHS Browser Environment Configuration File 2-34 Example 2-3. VHS Browser Customized Environment Configuration File 2-35 Example H-1. Log Messages H-3 ix

Contents Figures Figures Figure 1-1. VHS Architecture 1-2 Figure 1-2. VHS Browser Screens 1-6 Figure 1-3. Multiple VHS Processes 1-7 Figure 1-4. VHS On One Node With A Single Environment 1-8 Figure 1-5. Multiple VHS Environments on One Node 1-9 Figure 1-6. VHS on a Network 1-11 Figure 1-7. Centralized VHS EMS Events 1-12 Figure 2-1. VHS Installation Flow Chart 2-3 Figure 2-2. Using the Installation Program 2-7 Figure 2-3. Installing the VHS Browser in ViewPoint 2-14 Figure 2-4. Installing the VHS Browser in Pathway 2-23 Figure 2-5. Modifying the VHS Configuration Files 2-30 Figure 3-1. VHS Log Files 3-17 Figure 4-1. Screen Navigation Map 4-5 Figure 4-2. VHS Screen Format 4-6 Figure 4-3. Log Browser Help Screen 4-7 Figure 4-4. Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to 0 4-9 Figure 4-5. Log Browser Screen: SHOW-DATE Set to 1 and SHOW-OBJECT- NAME Set to 0 4-9 Figure 4-6. Log Browser Screen: SHOW-DATE Set to 0 and SHOW-OBJECT- NAME Set to 1 4-10 Figure 4-7. Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to 1 4-10 Figure 4-8. Prompt Browser Screen 4-15 Figure 4-9. Prompt Detail Screen: SHOW-DATE Set to 0 4-17 Figure 4-10. Prompt Detail Screen: SHOW-DATE Set to1 4-17 Figure 4-11. VHS Profile Screen 4-19 Figure 4-12. VHS Profile Screen 4-20 Figure 4-13. Environment Detailed Screen 4-24 Figure 8-1. VHS GUI Architecture 8-2 x

Contents Tables Tables Table 2-1. NonStop VHS Installation Subvolume (ISV) File Listing 2-4 Table 2-2. INSTVHS Definition File Name Used by Each INSTVHS Option 2-6 Table 2-3. VHS and VHSCI Installation Parameter Values 2-8 Table 2-4. VHS Browser ViewPoint Installation Parameter Values 2-15 Table 2-5. VHS Browser Installation Parameter Values for a Stand-Alone Pathway System 2-23 Table 2-6. NonStop VHS Browser Pathway Configuration and Management Files 2-25 Table 2-7. VHS ASSIGNs 2-36 Table 2-8. VHS Parameters 2-37 Table 2-9. VHS DEFINE 2-38 Table 4-1. VHS Field Descriptions 4-6 Table 4-2. Log Browser Screen Field Descriptions 4-11 Table 4-3. Log Browser Screen Function Keys 4-12 Table 4-4. Prompt Browser Screen Field Descriptions 4-15 Table 4-5. Prompt Browser Screen Function Keys 4-16 Table 4-6. Prompt Detail Screen Field Descriptions 4-18 Table 4-7. Prompt Detail Screen Function Keys 4-18 Table 4-8. VHS Profile Screen Field Descriptions 4-22 Table 4-9. VHS Profile Screen Function Keys 4-23 Table 4-10. Environment Detailed Screen Field Descriptions 4-25 Table 4-11. Environment Detailed Screen Function Keys 4-26 Table 7-1. VHSCI Commands Overview 7-1 Table C-1. SPI Standard Definitions Used by VHS C-3 Table C-2. EMS Standard Definitions Used by VHS C-5 Table C-3. VHS Token Definitions (Simple Tokens) C-6 Table C-4. VHS Value Definitions C-7 Table H-1. VHS Primary Log File Record Definition (Primary File) H-1 Table H-2. VHS Primary Log File Record Definition (Alternate Key File) H-1 xi

Contents xii

What s New in This Manual Manual Information Abstract Virtual Hometerm Subsystem (VHS) Manual This manual describes the Compaq NonStop Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications by emulating a 6530 terminal. Product Version Not applicable. Supported Releases This manual supports G06.15 and D48.03 and all subsequent Gxx.xx and Dxx.xx releases until otherwise indicated in a new edition. Part Number Published 429311-001 February 2002 Document History Part Number Product Version Published 429311-001 NA February 2002 What s New and Changed This manual has been updated as follows: The environment-detail screen has a new function: F5-Switch. This function enables you to switch to and view another set of available log files. You can now enable VHS, VHSCI, VHS Browser and VHS Browser-help to run at high PIN. VHS cannot be opened by remote processes. VHS can only be opened by local processes. Minor editorial corrections. xiii

What s New in This Manual What s New and Changed xiv

About This Manual This manual describes the NonStop Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications. It receives messages normally sent to a home terminal, such as displays, prompts, COBOL run-time library errors, and Inspect or Debug prompts. VHS can be used with an operator console program (such as ViewPoint, IOC, or NonStop NET/MASTER) to highlight critical or action event messages that affect system or application performance. Audience This manual is intended for personnel responsible for the configuration and management of systems and applications. Prerequisite Products and Manuals Before using this manual, you should be familiar with the Compaq NonStop Kernel operating system and the Event Management Service (EMS). VHS works with several other Compaq products. For more information about these products, see the appropriate product manuals: Related Products Distributed Systems Management Event Management Service (EMS) Pathway COBOL85 Debug Inspect Product Manuals Related Products and Manuals Introduction to Distributed Systems Management (DSM) SPI Programming Manual EMS Manual NonStop TS/MP System Management Manual Pathway/TS SCREEN COBOL Reference Manual COBOL85 Manual Debug Manual Inspect Manual You can use other Compaq products to manage system and user messages. VHS operates independently of these tools, but is designed to work with and enhance each of the following tools. xv

About This Manual Manual Organization For more information about these products, see the appropriate product manuals: Related Products ViewPoint Event Management Service (EMS) Analyzer NonStop NET/MASTER Product Manuals ViewPoint Manual Event Management Service (EMS) Analyzer User s Guide and Reference Manual NonStop NET/MASTER documentation Manual Organization This manual consists of the following sections and appendixes: Section Title Description 1 Introduction to VHS Provides an introduction to VHS, including a description of VHS architecture 2 Installing VHS Describes how to install VHS and its screens 3 Using VHS Describes how to run and how to use VHS 4 Using the VHS Browser Describes how to use the VHS Browser, the VHS screen facility to browse the VHS log file and the VHS prompt file 5 Using VHSCI Describes how to use the VHS conversational interface, VHSCI 6 Command Components Introduces the VHSCI command components 7 Command Descriptions Describes the VHSCI commands in detail 8 The VHS GUI Describes the VHS Graphical User Interface (GUI) architecture, features, and installation procedures. A VHS Files Lists the contents of some key VHS configuration and startup files: VHSCSTM file, a sample custom configuration file; the VHSSTART file, a sample startup file for VHS; and VHSBCONF, the VHS Browser configuration file B VHS Limits Lists VHS limits C VHS Event Messages Lists and describes the event messages generated by VHS D VHSCI Command Gives a VHSCI command summary Summary E VHS Process Messages Lists and describes the messages from the VHS Browser F VHS Browser Messages Lists and describes the messages from the VHS process G VHSCI Messages Lists and describes the messages from VHSCI xvi

About This Manual Your Comments Invited Section Title Description H VHS DDL Files Lists the data definition language for the VHS log file, the VHS prompt file, and VHS I ViewPoint Event Filter Displays a ViewPoint filter to highlight critical and action event messages Glossary Defines terms used in this manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card. Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual. Many of the improvements you see in manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals. Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] xvii

About This Manual General Syntax Notation A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [, new-value ]... [ - ] {0 1 2 3 4 5 6 7 8 9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; xviii

About This Manual Notation for Messages If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [, attribute-spec ]... Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LDEV ldev [ CU %ccu CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } xix

About This Manual Notation for Management Programming Interfaces Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: %005400 P=%p-register E=%e-register Notation for Management Programming Interfaces UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type xx

1 Introduction to VHS This manual describes the NonStop Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications by emulating a 6530 terminal. VHS requires no changes to your application. It runs as a named process with a subtype of 30 (device emulation). VHS receives messages normally sent to the home terminal, such as displays, application prompts, COBOL run-time library errors, and Inspect or Debug prompts. VHS uses these messages to generate event messages to the EMS collector to inform operations staff of problems. You can use VHS with operator console applications, such as ViewPoint or NonStop NET/MASTER, to highlight system or application problems. Benefits of VHS VHS improves operations productivity by helping you avoid three known problems related to using dedicated physical home terminals: Inability of operations staff to find and respond to critical messages because of the large volume of routine messages. Need for constant monitoring of physical home terminals by operations staff. Loss of productivity due to a stopped terminal that is waiting for a response. VHS emulates a terminal, but does not have the disadvantages of a single, dedicated physical terminal. VHS gives you the following benefits over a physical terminal: Easy access to critical application messages Centralized message handling Freeing up of physical terminals Automated handling of Inspect or Debug prompts Improved availability of applications to end users Information retrieval that highlights the cause of a problem, expediting its resolution 1-1

Introduction to VHS VHS Architecture VHS Architecture Figure 1-1 shows a simplified picture of the VHS architecture. It depicts the NonStop portion only, without the Pathway environment. Figure 1-1. VHS Architecture Management VHS Applications Subsystem Application Environment $VHS Application Console Facilities VHS Inspect File VHS Prompt File VHS Primary Log File Inspect or Debug EMS Collector Automation Software Consumer Distributor EMS Log Saveabend File VST011.vsd VHS and Management Applications VHS works with management applications, such as ViewPoint and NonStop NET/MASTER, or it can be run directly from the Compaq Tandem Advanced Command Language (TACL) prompt. You can have all the messages from VHS included in EMS events and sent to the EMS collector. VHS Subsystem The VHS subsystem has two key files: the prompt file and the primary log file. VHS stores application prompt messages in its prompt file and stores all messages it receives in its primary log file. VHS sends event messages to the EMS collector and optionally to a console facility for display messages only. 1-2

Introduction to VHS VHS and the Application Environment VHS and the Application Environment You configure your applications to send home terminal messages to VHS. If your applications go into Inspect or Debug, VHS will handle the Inspect prompt or let you do it, depending on your configuration. VHS Components VHS has three major components: VHS process VHS conversational interface (VHSCI) VHS Browser Emulates a 6530 terminal. Enables you to interact with and configure the VHS process in a standard conversational interface. Enables you to look at primary log file messages and application prompts and to reply to application prompts. The VHS process receives messages of many types from many sources. VHS manages six types of messages: open messages, display messages, Inspect prompts, Debug prompts, application prompts, and reply messages. The following table summarizes how VHS responds to messages and prompts. Type of message Open message Display messages Inspect prompts VHS Action Determines the object file of the process and acts accordingly Saves the message in the text part of an EMS event, sends the event to the collector if configured to do so (see parameter GENERATE-DISPLAY-EVENT), and logs the message in the primary log file Depending on the VHSINSP file and the AUTOMATIC-INSPECT- PROCESSING parameter, VHS will handle the Inspect prompt by sending commands found in the VHSINSP file, will also create a saveabend file to save the application s context and will stop the application, or VHS will let you handle the prompt by writing to its prompt file. VHS will log Inspect messages in its primary log file. VHS can also send EMS events to the collector if configured to do so (see the GENERATE-INSPECT-EVENT parameter) 1-3

Introduction to VHS VHS Components Type of message Debug prompts Application prompts Reply messages VHS Action VHS sends to Debug the D;T;S (Display;Trace;Stop) commands and stops the application. VHS logs Debug messages in its primary log file. VHS can also send EMS events to the collector if configured to do so (see the GENERATE-INSPECT-EVENT parameter) Saves the prompt to its prompt file. The prompt can be answered via the Prompt Browser screen. Also sends the event to the collector, if configured to do so (see the parameter GENERATE-PROMPT- EVENT), and logs the message Sends reply messages to the application, keeps a copy of the reply in its primary log file, and, if configured to do so (see the GENERATE-PROMPT-EVENT), generates an EMS event 1-4

Introduction to VHS VHS Browser VHS Browser VHS Browser, the VHS screen facility, enables you to access two important files created by VHS: VHS primary log file set contains all the messages received by VHS VHS prompt file contains all outstanding (unanswered) prompts received from applications The VHS primary log file set provides an audit trail of the messages received by VHS. This log or audit trail is actually a set of up to five files. You can specify the primary and secondary extent sizes and maximum number of extents of the primary log files when you start VHS. See Section 3, Using VHS, for more information about the VHS primary log file set. To view the primary log file set or the VHS prompt file, you access the appropriate VHS Browser screen. On the Log Browser screen, if you want to view messages from a specific process or after a specific time, you can specify criteria such as date, time, or process. The following table summarizes the functions of VHS Browser: Screen Log Browser screen Prompt Browser screen Prompt Detail screen VHS Profile screen Environment Detailed screen Function Displays messages in the VHS primary log file Allows you to view and reply to application prompts in the prompt file Allows you to get detailed information and reply to an application prompt Displays information about the VHS configuration. If your VHS configuration has multiple environments or is linked to other nodes, this screen enables you to change nodes Provides a list of all existing environments, gives detailed information on selected environments, and lists all VHS processes for a selected environment. This screen also enables you to change the current environment 1-5

Introduction to VHS VHS Browser Figure 1-2 shows how the VHS Browser screens are organized. Figure 1-2. VHS Browser Screens Log Browser Prompt Browser Prompt Detail VHS Profile Environment Detail VST012.vsd 1-6

Introduction to VHS Using Multiple VHS Processes Using Multiple VHS Processes You can use multiple VHS processes to balance the load on your system. For instance, you could have one VHS process for specific applications: $VHS1 could run in CPU0 and receive messages from telecommunication applications, $VHS2 could run in CPU2 and receive messages from production applications, and $VHS3 could run in another CPU and receive messages from development applications. Note that each VHS process can handle a maximum of 512 opens at the same time. Note. VHS cannot be opened by remote processes. VHS can only be opened by local processes. When you have multiple VHS processes running on your system, you can choose to have these processes use one set of log and prompt files. Figure 1-3 shows how three VHS processes ($VHS1, $VHS2, and $VHS3) share the same primary log and prompt files. However, you can create a separate VHS environment for one or more VHS processes, with its own set of prompt and log files, as described later. Figure 1-3. Multiple VHS Processes Environment: VHS $VHS1 VHS Log File VHS Inspect File $VHS2 $VHS3 VHS Prompt File VST013.vsd 1-7

Introduction to VHS VHS on a Node VHS on a Node VHS, on a single node, has multiple components: first, the VHS non-stop process itself, with its various files; then, the Pathway environment, which includes the VHS Browser server, the Help Server, and some other files. Figure 1-4 shows a complete VHS setup on one node with a single environment including an operator console program working with VHS. Figure 1-4. VHS On One Node With A Single Environment Node \A Management Application EMS Log File Operator Console EMS Collector VHS Browser Server VHSB Conf File VHS Prompt File VHS Log File $VHS VHS Inspect File Application 1-4 1-8

Introduction to VHS Setting Up VHS Environments Setting Up VHS Environments The grouping of multiple VHS processes that share one VHS prompt file and one VHS primary log file is called a VHS environment. You might have one VHS environment for ATM applications and another VHS environment for point-of-sale programs. You can have up to a hundred separate VHS environments. Each VHS environment has a name that you specify, such as ATM, POS, or DEV. Figure 1-5 shows a VHS configuration that includes an operator console program (such as ViewPoint or NonStop NET/MASTER). This configuration has two environments: ATM and POS. You use Pathway screens to move from environment to environment. For the clarity of the diagram, only one VHS process is depicted per environment. You could assume that each $ATM and $POS represents one or more VHS processes. Figure 1-5. Multiple VHS Environments on One Node Node \A Management Application Operator Console EMS Log File VHSB Conf File VHS Browser Server EMS Collector Env: POS Env: ATM VHS Prompt File VHS Log File VHS Prompt File VHS Log File $POS $ATM VHS Inspect File VHS Inspect File Application Application 1-5 1-9

Introduction to VHS VHS on a Network VHS on a Network You can have VHS installed and running on various nodes. The VHS Pathway environment must be installed on each node you want to get information from. From one node, using the VHS Profile screen, you can go to any other node that has the VHS Pathway environment installed and view the primary log file, reply to any prompt, and so on. You can perform all the same functions as if you were on the local node. Note. VHS cannot be opened by remote processes. VHS can only be opened by local processes. Figure 1-6 shows a complete VHS setup on a network. 1-10

Introduction to VHS VHS on a Network Figure 1-6. VHS on a Network Node \A Node \B VHS Screens VHSB Conf File Pathway TCP Pathway TCP VHSB Conf File VHS Browser Server EMS Collector EMS Log File VHS Browser Server EMS Collector EMS Log File VHS Log File VHS Log File VHS Prompt File VHS Prompt File $VHS $VHS VHS Inspect File Application VHS Inspect File Application 1-6 1-11

Introduction to VHS Centralizing VHS EMS Events Centralizing VHS EMS Events A VHS process can generate its EMS events to a local or a remote collector. To centralize VHS EMS events on one node, you can set the _EMS_COLLECTOR define for all the VHS processes on every node to a remote/centralized collector. From the central node you will be able to see all VHS EMS events, as depicted in Figure 1-7. Figure 1-7. Centralized VHS EMS Events Node \A EMS Collector Environment: VATM Application $VTAM1 $VTAM2 VHS Prompt File VHS Log File Node \B Environment: POS Environment: ATM Application Application $POS1 $POS2 $POS3 $ATM1 $ATM2 $ATM3 VHS Prompt File VHS Log File VHS Prompt File VHS Log File VST017.vsd 1-12

Introduction to VHS Centralizing VHS EMS Events 1-13

Introduction to VHS Centralizing VHS EMS Events 1-14

2 Installing VHS This section describes how to install and configure the NonStop Virtual Hometerm Subsystem (VHS) components: VHS Process VHSCI VHS Graphical User Interface (GUI) Agent VHS Browser It is recommended that you read this section before installing or running VHS for the first time. The VHS and VHSCI programs are stand-alone programs that must be installed and configured before you install the VHS Browser facility and/or the VHS GUI. The VHS GUI Agent facility is the set of host files needed to use the VHS Graphical User Interface on a Microsoft Windows NT platform. See Section 8, The VHS GUI, for a description of this interface. The VHS Browser facility is a Pathway application that can be integrated with the ViewPoint operation console facility and accessed through the ViewPoint EXTRAS screen. The VHS Browser facility can also be installed as a stand-alone Pathway system and be accessed through the TACL product or by other management applications such as NonStop NET/MASTER. A stand-alone Pathway system is a Pathway system dedicated to the VHS Browser facility. If you are running ViewPoint but do not have an EXTRAS screen configured, VHS provides a ViewPoint EXTRAS screen configuration with options to access the VHS Browser and another Tandem product, the Object Monitoring Facility (OMF). If you do not have OMF, the OMF functions are not functional. For VHS Browser to perform correctly, you must follow the proper procedures for installing and configuring the ViewPoint and NonStop NET/MASTER products. The installation procedures described in this section include references to the ViewPoint configuration used with the VHS Browser. For more information on ViewPoint or NonStop NET/MASTER, see the appropriate product manuals. Note. VHS is designed to be used with the Event Management Service (EMS) and requires proper EMS operation. For more information about event management, see the EMS Manual. This section has the following subsections: VHS system requirements Installation summary Installing the VHS and VHSCI programs and the VHS GUI Agent facility Installing the VHS Browser in ViewPoint Installing the VHS Browser as a stand-alone Pathway system 2-1

Installing VHS VHS System Requirements Modifying the VHS configuration files VHS run-time options VHS System Requirements VHS requires the NonStop Kernel operating system, release D20.06 or later. To install the VHS Browser facility as a stand-alone Pathway application, you must have Pathway release D20 or later. If you install the VHS Browser facility in ViewPoint, you must have the ViewPoint, release D20 or later. VHS Disk Space Requirements The VHS installation subvolume (ISV) uses approximately 2.5 megabytes of disk space. Installation Summary The VHS installation procedure is summarized here. You use: INSTALL to copy VHS from tape to an installation subvolume. INSTVHS to install the VHS and VHSCI programs and the VHS GUI Agent files first and then the VHS Browser. The VHS Browser can be installed as a standalone Pathway system or as part of ViewPoint. If you wish to install the VHS GUI, refer to Section 8, The VHS GUI, and to the Softdoc. 2-2

Installing VHS Creating the VHS Installation Subvolume (ISV) Figure 2-1 shows the sequence of steps required to install all the VHS components. Figure 2-1. VHS Installation Flow Chart Start Create VHS Installation subvolume Install VHS, VHSCI, and VHS GUI agent facility Use option 1 of the INSTVHS routine Browser stand-alone? No Install Browser in ViewPoint/IOC environment Use option 2 of the INSTVHS routine Yes Install Browser in Pathway system Use option 3 or 4 of the INSTVHS routine Customize VHS configuration files End VST021.vsd Creating the VHS Installation Subvolume (ISV) You should follow any instructions given in the associated software release document and any installation instructions that come with your site update tape (SUT). Install the software from the SUT by using the INSTALL program provided with the tape. The INSTALL program handles the installation of the NonStop VHS system software. Table 2-1 lists the files that you should find in your installation subvolume following this step. 2-3

Installing VHS Installing the VHS Subsystem Components Table 2-1. NonStop VHS Installation Subvolume (ISV) File Listing File Name GLNK INSTSEGF INSTVHS POBJCOD POBJDIR REXTRA VHS VHSBCONF VHSBHELP VHSBSVR VHSBTEXT VHSCI VHSCSTM VHSDDL VHSGAGT VHSGCONF VHSGTEXT VHSGTPL VHSGUI VHSINSP VHSSTART VHSTEXT SOFTDOC ZVHSC ZVHSCOB ZVHSDDL ZVHSSEGF ZVHSTACL ZVHSTAL ZVHSTMPL File Description ViewPoint SCREEN COBOL definitions used to compile REXTRA VHS TACL installation segment file VHS TACL macro used to install the product VHS Browser requester programs library (code) VHS Browser requester programs library (directory) ZVPT-EXTRAS SCREEN COBOL program example to call VHS Browser screens VHS program VHS Browser environment configuration file example VHS Browser HELP server program VHS Browser server program VHS Browser HELP text VHS conversational interface VHS default custom file VHS source DDL definition for the primary log file database VHS Agent program for the VHS GUI VHS Agent configuration file VHS Agent HELP file VHS Agent s Filter template file VHS GUI zip file to be downloaded to a PC VHS Inspect file VHS startup file example VHSCI HELP and error text Programmer notes supplied on the release tape VHS SPI/EMS definitions for C VHS SPI/EMS definitions for COBOL85 VHS SPI/EMS definitions for DDL VHS SPI/EMS segment file VHS SPI/EMS definitions for TACL VHS SPI/EMS definitions for TAL VHS EMS templates object file Installing the VHS Subsystem Components The INSTVHS routine automates the installation of the VHS components and subsequent updates. The INSTVHS routine affects the following files: 2-4

Installing VHS Installing VHS for the First Time Program and configuration files for the VHS and VHSCI programs and the VHS GUI Agent facility Program and configuration files for the VHS Browser facility HELP text files VHS Browser Pathway configuration files The INSTVHS routine presents four options to help you install and update the VHS components. The four options are: 1. Install or update VHS and VHSCI programs and the VHS GUI Agent facility 2. Install or update the VHS Browser facility in a running ViewPoint Pathway system 3. Install the VHS Browser facility as a stand-alone Pathway system 4. Update the VHS Browser facility in a stand-alone Pathway system After you install the VHS and VHSCI programs and the VHS GUI Agent facility by choosing option 1, determine how you want to install the VHS Browser facility and then select the appropriate option (2, 3, or 4). If you wish to install the VHS GUI, refer to Section 8, The VHS GUI, and to the Softdoc. Installing VHS for the First Time INSTVHS follows certain general guidelines when installing VHS for the first time: VHS files such as the VHS programs, help text, and configuration files are owned by the user running the installation routine; their security attributes are set to NUNU. VHS Pathway files are owned by the user running the installation routine; their security attributes are set to the current default security values. Updating VHS INSTVHS follows certain general guidelines when installing a VHS software update: Files released by Tandem replace older versions. Files containing user data (such as VHSCSTM, VHSBCONF, and VHSGCONF) are not replaced. If the installation replaces an old copy of a VHS file, such as the VHS program or HELP text file, the new file has the owner and security attributes of the old file. If the installation replaces an old copy of an VHS configuration file, the new file has the owner and the security attributes of the user running the installation routine. If the installation creates a new file, the new file is owned by the user running the installation routine; its security attributes are set to the current default security values. 2-5

Installing VHS Updating VHS Each option of the INSTVHS routine uses a different definition file to direct files to their intended subvolumes and to set common configuration parameters. You should use the default definition file name when you install the VHS components. Table 2-2 describes the default definition file name used by each INSTVHS option. Table 2-2. INSTVHS Definition File Name Used by Each INSTVHS Option INSTVHS Option Default Definition File Name File Description 1 INSTPROG Definition file used to keep the installation parameters for the VHS and VHSCI programs 2 INSTBVPT Definition file used to keep the installation parameters for the VHS Browser in ViewPoint 3 or 4 INSTBSAP Definition file used to keep the installation parameters for the VHS Browser in a stand-alone Pathway system Based on the INSTVHS option selected, INSTVHS generates a default definition file and provides a menu-like interface with which you can modify the default parameters. 2-6

Installing VHS Installing the VHS and VHSCI Programs and the VHS GUI Agent Facility Installing the VHS and VHSCI Programs and the VHS GUI Agent Facility To install the VHS and VHSCI programs and the VHS GUI Agent facility, you run the INSTVHS routine and follow the directions (see Figure 2-2). Figure 2-2. Using the Installation Program Start Partial SYSGEN Use the INSTALL program Complete INSTALL Run INSTALL^ TEMPLATES Macro Install VHS, VHSCI, & VHS GUI programs & agent files Use option 1 of the INSTVHS routine VST022.vsd You can terminate the installation activity by pressing the BREAK key at any time during the installation process. If the installation produces undesirable results, you can purge the undesirable files and reexecute the installation procedure. After a successful installation of the VHS and VHSCI programs and of the VHS GUI Agent facility, INSTVHS will redisplay its menu, and you will be able to continue with the installation of the VHS Browser facility. Before you install VHS and VHSCI and the VHS GUI Agent facility, review Table 2-3 for the parameters required. Also, if you wish to install the VHS GUI, refer to Section 8, The VHS GUI, for a more complete description of the GUI installation parameters. Note. VHS must be stopped before you update the VHS and VHSCI programs. Also, all users of the VHS GUI must exit this application. If VHS is not stopped, or if the VHS GUI applications are still running, the installation fails. 2-7

Installing VHS Installing the VHS and VHSCI Programs and the VHS GUI Agent Facility Table 2-3. VHS and VHSCI Installation Parameter Values (page 1 of 5) No. Name Value Default Description 1 ISV isv-subvolume current subvolume 2 VHS-PROGRAM- SUBVOL 3 VHSCSTM-USER- SUBVOL 4 VHS-STARTUP- FILE 5 VHS-PROCESS- NAME 6 VHS-PRIMARY- BACKUP-CPU VHS-programsubvolume default-usersubvolume startup-file $SYSTEM.VHS default user subvolume $SYSTEM.VHS. VHSSTART Specifies the name of the installation subvolume containing the software update. The ISV parameter has the label $volume.zvhs. Specifies the subvolume on which INSTVHS places the VHS and VHSCI programs and help text. Specifies the subvolume on which INSTVHS will create a default VHS custom file (VHSCSTM) for the current user. This file has to be located in the default user subvolume and will be executed each time you run the VHSCI program. Each VHSCI user should have a VHSCSTM file in his/her own default subvolume. Specifies the name of the startup file that will be created during the installation. This start-up file, a command (OBEY) file, can then be executed to start the VHS process. process-name $VHS Specifies the name of the VHS process. primary-backupcpu 0:1 Specifies a pair of CPUs in which VHS will run. 7 VHS-PRIORITY priority 180 Specifies the priority at which the VHS process will be executing. It is recommended that a high priority (relative to your online applications) be given to the VHS process. 2-8

Installing VHS Installing the VHS and VHSCI Programs and the VHS GUI Agent Facility Table 2-3. VHS and VHSCI Installation Parameter Values (page 2 of 5) No. Name Value Default Description 8 VHS-HOMETERM home-terminal default system home terminal 9 VHS-EMS- COLLECTOR 10 VHS-SUPPRESS- DISPLAY 11 VHS- ENVIRONMENT- NAME 12 PRIMARY-LOG- FILE-NAME 13 PRIMARY-LOG- FILE-CODE 14 PRIMARY-LOG- SECURITY Specifies the home terminal for VHS. Possible values are any existing physical (static) terminal name or the MYTERM keyword. If MYTERM is specified, the hometerm of VHS will be the one from which it is started. ems-collector $0 Specifies the name of the EMS collector used by VHS to report events. display-onconsole FALSE Specifies whether the display messages sent by VHS will be shown on the ViewPoint or NonStop Net/Master OCS screen. Valid parameter values are TRUE or FALSE. environment-name VHS Specifies the name of the environment that this VHS will run. The name must be from one to eight letters with no embedded blanks. This name will be used for two purposes: as a prefix for all EMS messages generated and by the VHS Browser facility to specify which VHS environment the user wants to look at. primary-logfile $SYSTEM. VHSLOG. LOG Specifies the name of the primary log file for VHS. The form of this parameter is $volume.subvolume.fi leprefix, where fileprefix must be exactly 3 alphabetic characters. primary-file-code 0 Specifies the file code used when creating the log files. file-security NUUU Specifies the default security used by VHS when it creates primary log files. 2-9

Installing VHS Installing the VHS and VHSCI Programs and the VHS GUI Agent Facility Table 2-3. VHS and VHSCI Installation Parameter Values (page 3 of 5) No. Name Value Default Description 15 PRIMARY-LOG- MAX-EXTENTS 16 VHS-INSPECT- SAVEFILE 17 VHS-PURGE- SAVEFILE maximum-extents 16 Specifies the maximum number of extents to be created for the primary log file. The value is an integer in the range of 1 through 978. inspect-savefile purge-savefileflag $SYSTEM. VHSDUMP. SAVE0000 FALSE Specifies the name of the Inspect saveabend files for VHS. The form of this parameter is $volume.subvolume.fi leprefixnnnn, where fileprefix must be 4 consecutive alphabetic characters and nnnn is replaced with numbers. Specifies whether VHS should add the force it (!) option when VHS sends a SAVE command to Inspect. When this option is set to TRUE, Inspect purges any savefile that existed before with the same file name. Valid parameter values are TRUE or FALSE. 18 VHS-GUI-MODE gui-mode-flag OFF Specifies whether the VHS GUI will be used to reply to prompts. If the parameter is set to OFF, the VHS GUI will not be able to reply to application prompts. Valid parameter values are ON and OFF. See Section 8, The VHS GUI for a more complete description of this parameter. 2-10