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
429311-001
NA
Published
February 2002
Virtual Hometerm Subsystem
(VHS) Manual
Glossary
Index
Examples
Figures
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 xv
Related Products and Manuals xv
Manual Organization xvi
Your Comments Invited xvii
Notation Conventions xvii
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
Tables
2. Installing VHS (continued)
Contents
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
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
3-7
Virtual Hometerm Subsystem (VHS) Manual—429311-001
ii
3. Using VHS (continued)
Contents
3. Using VHS (continued)
Reply Message Processing 3-11
Configuring VHS Inspect Processing 3-12
VHS AUTOMATIC-INSPECT-PROCESSING Parameter
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
3-12
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
iii
4. Using the VHS Browser (continued)
Contents
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
Getting Information About the VHS Parameters 5-17
Modifying a VHS Parameter 5-18
Getting Information About and Modifying Log Destinations
5-17
5-19
Virtual Hometerm Subsystem (VHS) Manual—429311-001
iv
5. Using VHSCI (continued)
Contents
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
v
7. Command Descriptions (continued)
Contents
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
vi
A. VHS Files
Contents
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
vii
C. VHS Event Messages (continued)
Contents
C. VHS Event Messages (continued)
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:
126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
143:
144:
145:
146:
ZVHS-EVT-TAKEOVER C-43
ZVHS-EVT-CHECKPOINT-FAILED C-45
ZVHS-EVT-CHECKOPEN-FAILED C-47
ZVHS-EVT-PRIMARY-LOG-IO-ERROR C-49
ZVHS-EVT-PROCESS-DELETED C-51
ZVHS-EVT-ALTERNATE-CREATED C-53
ZVHS-EVT-PROMPT-IO-ERROR C-54
ZVHS-EVT-PROMPT-FILE-CREATED C-56
ZVHS-EVT-PROMPT-ALT-CREATED C-57
ZVHS-EVT-CLEAN-PROMPT-FILE C-59
ZVHS-EVT-REMOVE-PROMPT C-61
ZVHS-EVT-BAD-REPLY C-63
ZVHS-EVT-CONFIG-IO-ERROR C-65
ZVHS-EVT-INVALID-LINE-FORMAT C-66
ZVHS-EVT-COLLECTOR ERROR C-68
ZVHS-EVT-INSP-UNKNOWN-LANGUAGE C-69
ZVHS-EVT-INSP-INVALID-FILENAME C-71
ZVHS-EVT-INSP-INVALID-PROCESS C-73
ZVHS-EVT-INSP-DUPLICATE-SEC C-75
ZVHS-EVT-INSP-TABLE-FULL-DATA C-77
ZVHS-EVT-INSP-TABLE-FULL-SEC C-78
ZVHS-EVT-INSP-PROCESSING-STOP C-80
ZVHS-EVT-INSP-TOO-MUCH-PROMPT C-81
ZVHS-EVT-OPEN-TABLE-THRESHOLD C-83
ZVHS-EVT-INSP-INVALID-PARAM C-84
ZVHS-EVT-INSP-LOAD-FILE-ERR C-86
ZVHS-EVT-OPENEDIT-ERROR C-87
ZVHS-EVT-READEDIT-ERROR C-89
ZVHS-EVT-SET-DEFINE C-90
ZVHS-EVT-INSP-RELOAD-FILE C-92
ZVHS-EVT-PROMPT-CANCEL C-93
ZVHS-EVT-PROMPT-NOT-UNIQUE C-96
ZVHS-EVT-INSP-INVALID-KEYWORD C-98
ZVHS-EVT-INSP-LINE-TOO-LONG C-100
ZVHS-EVT-INSP-LOAD-FILE C-101
ZVHS-EVT-INSP-RELOAD-FILE-ERR C-103
ZVHS-EVT-INSP-INVALID-REMOTE C-104
ZVHS-EVT-INSP-FILE-NOT-EXIST C-106
Virtual Hometerm Subsystem (VHS) Manual—429311-001
viii
C. VHS Event Messages (continued)
Contents
C. VHS Event Messages (continued)
147:
148:
150:
151:
152:
153:
154:
200:
ZVHS-EVT-INSP-INVALID-TEXT C-108
ZVHS-EVT-CLEAN-TABLE C-110
ZVHS-EVT-INSPECT-EXTENDED C-112
ZVHS-EVT-INSPECT-APPL-EXT C-114
ZVHS-EVT-INSPECT-SCOBOL-EXT C-117
ZVHS-EVT-DEBUG-EXTENDED C-120
ZVHS-EVT-PROMPT-RESEND C-123
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.
Example 2-2.
Example 2-3.
Example H-1.
VHS Custom Startup File 2-31
VHS Browser Environment Configuration File 2-34
VHS Browser Customized Environment Configuration File
Log Messages H-3
Virtual Hometerm Subsystem (VHS) Manual—429311-001
ix
2-35
Figures
Contents
Figures
Figure 1-1.
Figure 1-2.
Figure 1-3.
Figure 1-4.
Figure 1-5.
Figure 1-6.
Figure 1-7.
Figure 2-1.
Figure 2-2.
Figure 2-3.
Figure 2-4.
Figure 2-5.
Figure 3-1.
Figure 4-1.
Figure 4-2.
Figure 4-3.
Figure 4-4.
Figure 4-5.
Figure 4-6.
Figure 4-7.
Figure 4-8.
Figure 4-9.
Figure 4-10.
Figure 4-11.
Figure 4-12.
Figure 4-13.
Figure 8-1.
VHS Architecture 1-2
VHS Browser Screens 1-6
Multiple VHS Processes 1-7
VHS On One Node With A Single Environment 1-8
Multiple VHS Environments on One Node 1-9
VHS on a Network 1-11
Centralized VHS EMS Events 1-12
VHS Installation Flow Chart 2-3
Using the Installation Program 2-7
Installing the VHS Browser in ViewPoint 2-14
Installing the VHS Browser in Pathway 2-23
Modifying the VHS Configuration Files 2-30
VHS Log Files 3-17
Screen Navigation Map 4-5
VHS Screen Format 4-6
Log Browser Help Screen 4-7
Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to
0 4-9
Log Browser Screen: SHOW-DATE Set to 1 and SHOW-OBJECTNAME Set to 0 4-9
Log Browser Screen: SHOW-DATE Set to 0 and SHOW-OBJECTNAME Set to 1 4-10
Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to
1 4-10
Prompt Browser Screen 4-15
Prompt Detail Screen: SHOW-DATE Set to 0 4-17
Prompt Detail Screen: SHOW-DATE Set to1 4-17
VHS Profile Screen 4-19
VHS Profile Screen 4-20
Environment Detailed Screen 4-24
VHS GUI Architecture 8-2
Virtual Hometerm Subsystem (VHS) Manual—429311-001
x
Tables
Contents
Tables
Table 2-1.
Table 2-2.
Table 2-3.
Table 2-4.
Table 2-5.
Table 2-6.
Table 2-7.
Table 2-8.
Table 2-9.
Table 4-1.
Table 4-2.
Table 4-3.
Table 4-4.
Table 4-5.
Table 4-6.
Table 4-7.
Table 4-8.
Table 4-9.
Table 4-10.
Table 4-11.
Table 7-1.
Table C-1.
Table C-2.
Table C-3.
Table C-4.
Table H-1.
Table H-2.
NonStop VHS Installation Subvolume (ISV) File Listing 2-4
INSTVHS Definition File Name Used by Each INSTVHS Option 2-6
VHS and VHSCI Installation Parameter Values 2-8
VHS Browser ViewPoint Installation Parameter Values 2-15
VHS Browser Installation Parameter Values for a Stand-Alone Pathway
System 2-23
NonStop VHS Browser Pathway Configuration and Management
Files 2-25
VHS ASSIGNs 2-36
VHS Parameters 2-37
VHS DEFINE 2-38
VHS Field Descriptions 4-6
Log Browser Screen Field Descriptions 4-11
Log Browser Screen Function Keys 4-12
Prompt Browser Screen Field Descriptions 4-15
Prompt Browser Screen Function Keys 4-16
Prompt Detail Screen Field Descriptions 4-18
Prompt Detail Screen Function Keys 4-18
VHS Profile Screen Field Descriptions 4-22
VHS Profile Screen Function Keys 4-23
Environment Detailed Screen Field Descriptions 4-25
Environment Detailed Screen Function Keys 4-26
VHSCI Commands Overview 7-1
SPI Standard Definitions Used by VHS C-3
EMS Standard Definitions Used by VHS C-5
VHS Token Definitions (Simple Tokens) C-6
VHS Value Definitions C-7
VHS Primary Log File Record Definition (Primary File) H-1
VHS Primary Log File Record Definition (Alternate Key File) H-1
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xi
Contents
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xii
What’s New in This Manual
Manual Information
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
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xiii
What’s New in This Manual
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xiv
What’s New and Changed
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
Product Manuals
Distributed Systems Management
Introduction to Distributed Systems Management
(DSM)
SPI Programming Manual
Event Management Service (EMS)
EMS Manual
Pathway
NonStop TS/MP System Management Manual
Pathway/TS SCREEN COBOL Reference Manual
COBOL85
COBOL85 Manual
Debug
Debug Manual
Inspect
Inspect Manual
Related Products and Manuals
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xv
Manual Organization
About This Manual
For more information about these products, see the appropriate product manuals:
Related Products
Product Manuals
ViewPoint
ViewPoint Manual
Event Management Service (EMS)
Analyzer
Event Management Service (EMS) Analyzer User’s
Guide and Reference Manual
NonStop NET/MASTER
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
Summary
Gives a VHSCI command 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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xvi
Your Comments Invited
About This Manual
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]
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xvii
General Syntax Notation
About This Manual
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 ) ;
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xviii
Notation for Messages
About This Manual
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.
}
Virtual Hometerm Subsystem (VHS) Manual—429311-001
xix
Notation for Management Programming Interfaces
About This Manual
| 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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -1
VHS Architecture
Introduction to VHS
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
VHS
Inspect
File
VHS
Prompt
File
Console
Facilities
Application
VHS
Primary Log
File
Inspect or
Debug
EMS Log
Saveabend
File
EMS
Collector
Automation
Software
Consumer
Distributor
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -2
VHS and the Application Environment
Introduction to VHS
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
Emulates a 6530 terminal.
VHS conversational
interface
(VHSCI)
Enables you to interact with and configure the VHS
process in a standard conversational interface.
VHS Browser
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
VHS Action
Open message
Determines the object file of the process and acts accordingly
Display messages
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
Inspect prompts
Depending on the VHSINSP file and the AUTOMATIC-INSPECTPROCESSING 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)
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -3
VHS Components
Introduction to VHS
Type of message
VHS Action
Debug prompts
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)
Application prompts
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-PROMPTEVENT), and logs the message
Reply messages
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -4
VHS Browser
Introduction to VHS
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
Function
Log Browser screen
Displays messages in the VHS primary log file
Prompt Browser screen
Allows you to view and reply to application prompts in the
prompt file
Prompt Detail screen
Allows you to get detailed information and reply to an
application prompt
VHS Profile screen
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
Environment Detailed
screen
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -5
VHS Browser
Introduction to VHS
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -6
Using Multiple VHS Processes
Introduction to VHS
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -7
VHS on a Node
Introduction to VHS
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
Operator
Console
VHSB Conf
File
Management
Application
EMS Log
File
EMS
Collector
VHS Browser
Server
VHS Log
File
VHS Prompt
File
$VHS
VHS Inspect
File
Application
1-4
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -8
Setting Up VHS Environments
Introduction to VHS
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
Operator
Console
EMS Log
File
Management
Application
VHS Browser
Server
VHSB Conf
File
EMS
Collector
Env: ATM
Env: POS
VHS Prompt
File
VHS Log
File
VHS Prompt
File
$POS
VHS Inspect
File
VHS Log
File
$ATM
VHS Inspect
File
Application
Application
1-5
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1 -9
VHS on a Network
Introduction to VHS
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1- 10
VHS on a Network
Introduction to VHS
Figure 1-6. VHS on a Network
Node \A
Node \B
VHS
Screens
VHSB Conf
File
Pathway
TCP
Pathway
TCP
VHSB Conf
File
EMS Log
File
VHS Browser
Server
EMS
Collector
EMS Log
File
VHS Browser
Server
VHS Log
File
EMS
Collector
VHS Log
File
VHS Prompt
File
VHS Prompt
File
$VHS
$VHS
VHS Inspect
File
VHS Inspect
File
Application
Application
1-6
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1- 11
Centralizing VHS EMS Events
Introduction to VHS
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
$POS1
Application
$POS2
VHS
Prompt
File
$POS3
VHS
Log
File
$ATM1
$ATM2
VHS
Prompt
File
$ATM3
VHS
Log
File
VST017.vsd
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1- 12
Introduction to VHS
Centralizing VHS EMS Events
Virtual Hometerm Subsystem (VHS) Manual—429311-001
1- 13
Introduction to VHS
Centralizing VHS EMS Events
Virtual Hometerm Subsystem (VHS) Manual—429311-001
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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -1
VHS System Requirements
Installing VHS
•
•
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -2
Creating the VHS Installation Subvolume (ISV)
Installing VHS
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
Browser
stand-alone?
Use option 1 of
the INSTVHS
routine
No
Install Browser in Use option 2 of
ViewPoint/IOC the INSTVHS
environment
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -3
Installing the VHS Subsystem Components
Installing VHS
Table 2-1. NonStop VHS Installation Subvolume (ISV) File Listing
File Name
File Description
GLNK
ViewPoint SCREEN COBOL definitions used to compile REXTRA
INSTSEGF
VHS TACL installation segment file
INSTVHS
VHS TACL macro used to install the product
POBJCOD
VHS Browser requester programs library (code)
POBJDIR
VHS Browser requester programs library (directory)
REXTRA
ZVPT-EXTRAS SCREEN COBOL program example to call VHS Browser
screens
VHS
VHS program
VHSBCONF
VHS Browser environment configuration file example
VHSBHELP
VHS Browser HELP server program
VHSBSVR
VHS Browser server program
VHSBTEXT
VHS Browser HELP text
VHSCI
VHS conversational interface
VHSCSTM
VHS default custom file
VHSDDL
VHS source DDL definition for the primary log file database
VHSGAGT
VHS Agent program for the VHS GUI
VHSGCONF
VHS Agent configuration file
VHSGTEXT
VHS Agent HELP file
VHSGTPL
VHS Agent’s Filter template file
VHSGUI
VHS GUI zip file to be downloaded to a PC
VHSINSP
VHS Inspect file
VHSSTART
VHS startup file example
VHSTEXT
VHSCI HELP and error text
SOFTDOC
Programmer notes supplied on the release tape
ZVHSC
VHS SPI/EMS definitions for C
ZVHSCOB
VHS SPI/EMS definitions for COBOL85
ZVHSDDL
VHS SPI/EMS definitions for DDL
ZVHSSEGF
VHS SPI/EMS segment file
ZVHSTACL
VHS SPI/EMS definitions for TACL
ZVHSTAL
VHS SPI/EMS definitions for TAL
ZVHSTMPL
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:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -4
Installing VHS for the First Time
Installing VHS
•
•
•
•
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -5
Updating VHS
Installing 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
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
File Description
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -6
Installing the VHS and VHSCI Programs and the
VHS GUI Agent Facility
Installing VHS
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
Use the
INSTALL
program
Partial
SYSGEN
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -7
Installing the VHS and VHSCI Programs and the
VHS GUI Agent Facility
Installing VHS
Table 2-3. VHS and VHSCI Installation Parameter Values (page 1 of 5)
No.
Name
Value
Default
Description
1
ISV
isv-subvolume
current
subvolume
Specifies the name of the
installation subvolume
containing the software
update. The ISV parameter
has the label
$volume.ZVHS.
2
VHS-PROGRAMSUBVOL
VHS-programsubvolume
$SYSTEM.VHS
Specifies the subvolume on
which INSTVHS places the
VHS and VHSCI programs
and help text.
3
VHSCSTM-USERSUBVOL
default-usersubvolume
default user
subvolume
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.
4
VHS-STARTUPFILE
startup-file
$SYSTEM.VHS
.
VHSSTART
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.
5
VHS-PROCESSNAME
process-name
$VHS
Specifies the name of the
VHS process.
6
VHS-PRIMARYBACKUP-CPU
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -8
Installing the VHS and VHSCI Programs and the
VHS GUI Agent Facility
Installing VHS
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
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.
9
VHS-EMSCOLLECTOR
ems-collector
$0
Specifies the name of the
EMS collector used by
VHS to report events.
10
VHS-SUPPRESSDISPLAY
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.
11
VHSENVIRONMENTNAME
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.
12
PRIMARY-LOGFILE-NAME
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.
13
PRIMARY-LOGFILE-CODE
primary-file-code
0
Specifies the file code used
when creating the log files.
14
PRIMARY-LOGSECURITY
file-security
NUUU
Specifies the default
security used by VHS
when it creates primary log
files.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2 -9
Installing the VHS and VHSCI Programs and the
VHS GUI Agent Facility
Installing VHS
Table 2-3. VHS and VHSCI Installation Parameter Values (page 3 of 5)
No.
Name
Value
Default
Description
15
PRIMARY-LOGMAX-EXTENTS
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.
16
VHS-INSPECTSAVEFILE
inspect-savefile
$SYSTEM.
VHSDUMP.
SAVE0000
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.
17
VHS-PURGESAVEFILE
purge-savefileflag
FALSE
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.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 10
Installing the VHS and VHSCI Programs and the
VHS GUI Agent Facility
Installing VHS
Table 2-3. VHS and VHSCI Installation Parameter Values (page 4 of 5)
No.
Name
Value
Default
Description
19
PROMPT-EVENTRESEND-DELAY
wait-delay
15
Specifies the time (in
minutes) VHS will wait
before generating a repeat
(ZVHS-EVT-RESENDPROMPT) event for an
unanswered prompt. This
parameter will be ignored if
VHS-GUI-MODE is set to
OFF. The possible values
are from 1 to 60. See
Section 8, The VHS GUI
for a more complete
description of this
parameter.
20
PRIMARYLOGFILEBUFFERED
log-file-buffer
OFF
Allows the creation of the
Primary Log files using the
write-through caching
option.
21
PRIMARYLOGFILE-PURGE
log-file-purgeflag
ON
Allows the Primary Log
files to be kept instead of
using the maximum of 5
files.
22
VHS-LOGGER
logger-flag
ON
Used to turn on or turn off
the VHS logging function.
Valid values are ON and
OFF. ON means VHS will
log all messages into its
Primary Log file.
23
ADD-TEXT-TOEVENT
Text-in-eventflag
ON
Specifies if the token text
will be part or not of the
EMS event. Valid values
are ON and OFF.
24
GENERATEINSPECT-EVENT
generate-inspectevent-flag
ON
Used to turn off the EMS
event generation for
Inspect messages. Valid
values are ON and OFF.
25
GENERATEPROMPT-EVENT
generate-promptevent-flag
ON
Used to turn off the EMS
event generation for
Prompt messages. Valid
values are ON and OFF.
26
GENERATEDISPLAY-EVENT
generate-displayevent-flag
ON
Used to turn off the EMS
event generation for
display messages. Valid
values are ON and OFF.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 11
VHS, VHSCI and VHS GUI Agent Installation
Procedure
Installing VHS
Table 2-3. VHS and VHSCI Installation Parameter Values (page 5 of 5)
No.
Name
Value
Default
Description
27
REMOVE-EXTRASPACES
remove-space-flag
ON
When set to ON, VHS
replaces an occurrence of
multiple spaces by only
one space in the display
message. Valid values are
ON and OFF.
28
ACCEPT-EXTASCIICHARACTER
accept-ext-asciiflag
OFF
Specifies if VHS will accept
or not characters with eight
bit ON like KANA and
KANJI characters. Valid
values are ON and OFF.
29
AUTOMATICINSPECTPROCESSING
Automaticinspectprocessing-flag
ON
Specifies VHS will
automatically handle
Inspect prompts. Valid
values are ON and OFF.
ON means VHS will
automatically handle
Inspect prompts.
30
BACKUPCREATIONMESSAGE-DELAY
Delay-in-backupcreation- message
5
Specifies, in minutes, the
delay between each
occurrence of the backup
creation failure message.
Valid values are 0 through
999.
31
OPEN-TABLETHRESHOLD
Open-tablethreshold
90
Specifies how full, in
percent, the opener table
must be before VHS will
generate the ZVHS-EVTTABLE-THRESHOLD EMS
event. Valid values are
from 0 to 100.
Note. The default VHS process name is $VHS. If this name is already being used, make sure
to change the VHS process name in the installation procedure (by changing parameter 5 in
Table 2-3 or by editing the VHSSTART file).
VHS, VHSCI and VHS GUI Agent Installation Procedure
This subsection summarizes the VHS, VHSCI, and VHS GUI Agent facility installation.
To run the INSTVHS routine, enter this at the TACL prompt:
3> instvhs
or
3> run instvhs
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 12
VHS, VHSCI and VHS GUI Agent Installation
Procedure
Installing VHS
This command attaches the INSTSEGF segment file and displays an installation menu:
1-Install or update VHS and VHSCI programs and 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
Enter 1 to install the VHS and VHSCI programs and the VHS GUI Agent facility. The
INSTVHS program prompts you through the installation process that includes the
following steps:
1. Defining a File
Checks to see if a definition files exists and creates one if it does not. INSTVHS
uses default values to create a definition file, which you can change later.
2. Selecting and Defining the Parameters
Enables you to specify custom parameters.
Note. The default VHS process name is $VHS and the default value for the VHS-GUIMODE parameter is OFF. These values cannot be modified while VHS is running. Be sure
to change these values in the installation procedure or by editing the VHSSTART file.
3. Validating File Parameters
Validates your choices for VHS parameters.
4. Validating the VHS Installation Subvolume
Verifies that all the required files for VHS and VHSCI program and the VHS GUI
Agent facility installation are in the VHS installation subvolume. If the required files
are not in the installation subvolume, a message is issued and you should restart
the installation procedure.
5. Installing VHS Programs
The INSTVHS routine moves all the program and help text files to the subvolume
specified by the VHS-PROGRAM-SUBVOL parameter. The following files are
moved: VHS, VHSCI, VHSDDL, VHSINSP, and VHSTEXT. Then the VHS GUI
Agent files are copied to $SYSTEM.SYSTEM; these files are: VHSGAGT,
VHSGTPL, VHSTEXT, and VHSGCONF.
6. Creating the Default VHSCSTM Custom Configuration File
The INSTVHS routine creates a default VHSCSTM file in the subvolume specified
by the VHSCSTM-USER-SUBVOL parameter.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 13
Installing the VHS Browser in ViewPoint
Installing VHS
7. Creating the VHS Startup File
The INSTVHS routine creates the VHS startup file with the name specified by the
VHS-STARTUP-FILE parameter.
When all of the above steps are completed successfully, the installation of the VHS
and VHSCI programs and the VHS GUI Agent facility is complete and you can
continue with the installation of the VHS Browser facility.
Installing the VHS Browser in ViewPoint
To install the VHS Browser facility into ViewPoint, you run the INSTVHS routine and
follow the directions (see Figure 2-3).
Figure 2-3. Installing the VHS Browser in ViewPoint
Browser
stand-alone?
No
Install Browser in
ViewPoint
environment
Use option 2 of
the INSTVHS
routine
VST023.vsd
Note. If you plan to install the VHS Browser facility in ViewPoint later, then you must be the
owner of ViewPoint and ViewPoint must be running on your terminal. For example, if you want
to install the VHS Browser facility within ViewPoint, invoke ViewPoint by typing this at the TACL
prompt:
2> viewpt
Before you run INSTVHS, review Table 2-4 for the parameters you must provide during
the installation.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 14
Installing the VHS Browser in ViewPoint
Installing VHS
Table 2-4. VHS Browser ViewPoint Installation Parameter Values (page 1 of 2)
No.
Name
Value
Default
Description
1
ISV
isv-subvol
current
subvolume
Specifies the name of the
installation subvolume
containing the software
update. The ISV parameter is
labeled $volume.ZVHS.
2
VHS-BROWSERSUBVOL
VHS-Browsersubvol
n/a
Specifies the subvolume in
which INSTVHS places the
VHS Browser servers and
VHS Pathway configuration
files.
3
PATHWAYSYSTEM-TYPE
VIEWPOINT
VIEWPOINT
Specifies the target Pathway
system for VHS. The valid
parameter value is
"VIEWPOINT" for the
ViewPoint Operations
Console facility.
4
PATHWAYPATHCONFFILENAME
pathconffilename
n/a
Specifies the file name of the
current ViewPoint Pathway
PATHCONF configuration file.
5
PATHWAY-POBJFILE-PREFIX
pathway-pobj
n/a
Specifies the name of the
Pathway pseudo-object
TCLPROG library in which the
ViewPoint SCREEN COBOL
requesters have been
installed. The VHS Browser
requesters will be installed in
this library. The library name
contains from one to five
characters: for example,
POBJ.
6
PATHWAYPATHMON-NAME
pathmon-name
$ZVPT
Specifies the name of the
PATHMON that runs the
ViewPoint Pathway system.
This name is used to add the
new VHS Browser servers to
the Pathway system.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 15
Installing the VHS Browser in ViewPoint
Installing VHS
Table 2-4. VHS Browser ViewPoint Installation Parameter Values (page 2 of 2)
No.
Name
Value
Default
Description
7
INSTALL-ZVPTEXTRAS
{ YES | NO }
NO
8
VHS-BROWSERNAME
VHS-Browsername
$VHSB
Specifies whether a new
ZVPT-EXTRAS requester
program will be installed in
the Pathway pseudo-object
TCLPROG library. If you have
already developed a ZVPTEXTRAS requester, set this
parameter to NO. (See
“Merging VHS Browser With
Your ZVPT-EXTRAS
Requester” below.) This
version of the ZVPT-EXTRAS
requester program can invoke
the VHS Browser facility and
the Object Monitoring Facility
(OMF) product. If you have
OMF, you will need to install
this version of the requester
Specifies the name of the
VHS Browser process. The
default is $VHSB.
9
VHS-CONFIGFILE-NAME
configurationfile-name
n/a
Specifies the name of the file
that will contain the VHS
Browser configuration for all
environments known by the
VHS Browser.
10
VHS-BROWSERCPUS
VHS-server-cpus
0:1
Specifies a pair of CPUs on
which the VHS Browser
server processes will run.
11
VHS-BROWSERPRIORITY
VHS-serverpriority
150
Specifies the NonStop Kernel
priority at which the VHS
Browser server processes will
run.
12
VHS-DEFAULTENVIRONMENT
environmentname
VHS
Specifies the default VHS
environment name used by
the VHS Browser. This name
must be from one to eight
consecutive letters.
13
VHS-DEFAULTPROMPT-FILE
prompt-logfile
$SYSTEM.VH
S
LOG.PROMPT
Specifies the name of the
prompt log file used by VHSDEFAULT-ENVIRONMENT.
The form of this parameter is
$volume.subvolume.PRO
MPT where
$volume.subvolume
specify the location of the
volume and subvolume where
the default VHS environment
was installed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 16
VHS Browser Restrictions
Installing VHS
Note. If you do not have a ZVPT-EXTRAS ViewPoint Extras screen, you will not be able to
access the VHS Browser. To get an Extras screen, change the INSTALL-ZVPT-EXTRAS (7)
value to YES.
VHS Browser Restrictions
Certain restrictions apply when you use VHS Browser within the ViewPoint
environment:
•
•
Printing is performed using the PATHMON user ID rather than the current user ID.
Screens can be written to a terminal, process, or printer, but not to a disk file. (This
is a Pathway restriction.)
•
Spooler output generated by the VHS Browser is owned by the owner of the
Pathway environment.
•
Events generated by the VHS Browser set the EMS token ZEMS-TKN-USERID to
the PATHMON user ID.
VHS Browser Installation in ViewPoint Procedure
This subsection summarizes the VHS Browser installation in ViewPoint. This sample
assumes that ViewPoint is already running and active on your terminal. To run the
INSTVHS routine, enter this at the TACL prompt:
3> instvhs
or
3> run instvhs
This command attaches the INSTSEGF segment file and displays an installation menu:
1-Install or update VHS and VHSCI programs and 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
Enter 2 to install the VHS Browser in ViewPoint. The INSTVHS program prompts you
through the following steps:
1. Defining a File
Checks to see if a definition file exists and creates one if it does not. At its creation,
this file is filled with default values from your ViewPoint Pathway system.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 17
VHS Browser Installation in ViewPoint Procedure
Installing VHS
2. Selecting and Defining the Parameters
Provides the VHS Browser parameters. You can accept the default parameter
values or modify the appropriate parameters.
3. Validating File Parameters and Definitions
Verifies your settings for the VHS Browser parameters.
4. Validating the Installation Subvolume
Verifies that all the files required to install the VHS Browser are present in the
VHS ISV.
5. Deleting Old Copies of VHS Browser Servers and Requesters
Checks to see if the VHS Browser was previously installed in your Pathway
system. If so, the previous version of the VHS Browser servers and requesters are
deleted.
6. Installing the VHS Browser Server Programs and Data Files
Copies all the program and data files to the subvolume specified by the
VHS-BROWSER-SUBVOL parameter.
7. Installing the VHS Browser Requesters
Copies all the VHS Browser requester programs to the location specified by the
PATHWAY-POBJ-FILE-PREFIX parameter.
If the INSTALL-ZVPT-EXTRAS parameter is set to YES, a version of the
ZVPT-EXTRAS requester program is also installed in the Pathway POBJ program
library.
8. Creating the VHS Browser Pathway Configuration Files
Creates two Pathway configuration files. The first one, called VHSDEFS, contains
the server configuration. This file adds the new server into the Pathway
environment.
The second file, called VHSSTRT, contains the Pathway commands to start the
VHS Browser servers.
9. Updating the Pathway Configuration File PATHCONF
Updates the current Pathway PATHCONF file by adding two OBEY commands.
These commands execute the two VHS Pathway command files created in Step 8,
VHSDEFS and VHSSTRT, to add VHS in the Pathway environment.
The Pathway system uses PATHCONF whenever you issue a VIEWPT:
STARTCOLD macro to start the Pathway environment from a cold state.
10. Creating the VHS Default Browser Configuration File
Creates the default Browser configuration file used to list all the known VHS
environments on this system. The result is put in an EDIT file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 18
ViewPoint Installation Considerations
Installing VHS
11. Installing VHS Browser into the Pathway system
Adds and starts the VHS servers in the Pathway environment.
12. Modifying the VHS Browser Environment Configuration File
This step is described in Modifying the VHS Configuration Files on page 2-29.
ViewPoint Installation Considerations
The following subsections describe additional considerations for installing the VHS
Browser into your ViewPoint environment.
Merging VHS Browser With Your ZVPT-EXTRAS Requester
If a ViewPoint Extras screen already exists within your Pathway environment, you can
do either of the following:
•
•
Add your ViewPoint Extras screen code into the one supplied with VHS. The
SCREEN COBOL source file, REXTRA, that is supplied with VHS, is located on
the ISV. This program uses the ViewPoint SCREEN COBOL definitions from the
GLNK file, which is also located on the ISV.
Add the necessary code in your own ViewPoint Extras screen program. To do so,
associate a function key with each of the two major VHS Browser screens—the
VHS Log Browser and the VHS Prompt Browser—and add the following piece of
code into your SCREEN COBOL source file.
In the working section of the data division of your SCREEN COBOL program, add
this code:
01 ws-initial-program
PIC X(30).
Add the following lines to the procedure division of your SCREEN COBOL
program:
Do-VHSL SECTION.
MOVE "ZVHS-LOG-BROWSER-V3" TO ws-initial-program.
CALL "ZVHS-MAIN-PROFILE-V1" USING zvpt-link-data-l,
ws-option-line,
ws-initial-program
ON ERROR PERFORM VHSL-call-error.
MOVE ws-option-line TO z-option-line.
PERFORM Check-post-selection.
PERFORM Display-Extra.
Do-VHSP SECTION.
MOVE "ZVHS-PROMPT-BROWSER-V3" TO ws-initial-program.
CALL "ZVHS-MAIN-PROFILE-V1" USING zvpt-link-data-l,
ws-option-line,
ws-initial-program
ON ERROR PERFORM VHSL-call-error.
MOVE ws-option-line TO z-option-line.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 19
ViewPoint Installation Considerations
Installing VHS
PERFORM Check-post-selection.
PERFORM Display-Extra.
ViewPoint Pathway Configuration Files
ViewPoint uses these three files to configure and start its Pathway system:
PATHDEFS
Adds the ViewPoint servers to the Pathway configuration.
PATHSTRT
Starts the ViewPoint servers.
PATHCONF
Adds the ViewPoint TCP and program to the Pathway configuration
and starts your Pathway system cold. PATHCONF invokes
PATHDEFS and PATHSTRT to perform the cold start.
INSTVHS generates two Pathway configuration files in the VHS-BROWSER-SUBVOL:
VHSDEFS
Adds VHS servers to the Pathway configuration.
VHSSTRT
Starts the VHS servers.
The ViewPoint PATHCONF file is updated by INSTVHS to invoke VHSDEFS and
VHSSTRT. You can specify the name of the ViewPoint PATHCONF file during
installation by modifying Parameter 4, PATHWAY-PATHCONF-FILENAME.
INSTVHS updates the ViewPoint PATHCONF file by adding the following two
command lines:
OBEY $SYS1.VPTTOOLS.VHSDEFS
OBEY $SYS1.VPTTOOLS.VHSSTRT
The VHS Browser facility is added and started automatically whenever you start your
ViewPoint Pathway system cold.
Too Many Servers
When adding VHS servers into your ViewPoint Pathway environment, if you reach the
maximum number of server processes and/or server classes allowed, one of the
following events is generated:
ZPWY-ERR-PM-TOOMANYSC (1102)
ZPWY-ERR-PM-TOOMANYSCPROCESS (1103)
To resolve this problem, increase the Pathway MAXSERVERCLASSES and
MAXSERVERPROCESSES parameters in the PATHCONF file. For example, supply
the following commands:
SET PATHWAY MAXSERVERCLASSES 20
SET PATHWAY MAXSERVERPROCESSES 100
You would then load the ViewPoint application.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 20
ViewPoint Installation Considerations
Installing VHS
Call Errors
When paging from screen to screen within the VHS Browser, you might encounter the
following event message:
ZPWY-ERR-TCP-STACKOVERFLOW (3016)
When this happens, one of the following call error messages displays:
A Call error was returned when invoking { program-name }
program.
{ VHS-error-number-1 } 0016.
A Call error was returned from { program-name } program.
{ VHS-error-number-2 } 0016.
program-name
specifies the name of the invoked SCREEN COBOL program if you were trying to
enter a screen, or the name of the current SCREEN COBOL program you were in.
VHS-error-number-1
specifies a VHS message error number. For an explanation of VHS errors, see
Appendix F.
VHS-error-number-2
specifies a VHS message error number. For an explanation of VHS errors, see
Appendix F.
The number following the VHS-error-number-1 or VHS-error-number-2 fields
(0016) is an error code returned by SCREEN COBOL, designating a terminal stack
space overflow. This means that the ViewPoint TCP requires more data space than is
configured. To resolve this problem, modify the PATHCONF file and set the TCP
MAXTERMDATA parameter to at least 64000 bytes. You must first stop the TCP:
SET TCP MAXTERMDATA 64000
Once this is done, restart the TCP.
No EXTRAS Screen Available
If you do not have a ZVPT-EXTRAS ViewPoint Extras screen, you will not be able to
access the VHS Browser. When trying to enter the ViewPoint Extras screen, you get
the following error message:
No EXTRAS screen is available.
0025
To remedy this situation, reinstall the ZVPT-EXTRAS program or modify your code. For
more information, see Merging VHS Browser With Your ZVPT-EXTRAS Requester on
page 2-19.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 21
ViewPoint Installation Considerations
Installing VHS
Security Considerations
VHS Browser does not provide its own security checking. If you are using the
ViewPoint environment, VHS Browser relies on the security system provided by
ViewPoint to check for two authorization levels:
•
•
Who can install and start VHS Browser
Who can run VHS Browser
When INSTALL is run, the VHS ISV files are restored with the operator’s ownership
and security values. Verify these values to ensure that they are acceptable. VHS
installation procedures require read access to the ISV files and result in files being
copied and created on the subvolume defined by the VHS-BROWSER-SUBVOL
parameter.
Once installed, VHS Browser follows ViewPoint security measures. For more
information on ViewPoint security, refer to the ViewPoint Manual.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 22
Installing the VHS Browser as a Stand-Alone
Pathway System
Installing VHS
Installing the VHS Browser as a Stand-Alone
Pathway System
To install the VHS Browser facility as a stand-alone Pathway system, you run the
INSTVHS routine and follow the directions (see Figure 2-4).
If this is the first time you are installing the VHS Browser facility as a stand-alone
Pathway system, you do not need to have this Pathway system running. If you are
updating an installation, you must have the VHS Browser stand-alone Pathway system
running.
Figure 2-4. Installing the VHS Browser in Pathway
Browser
stand-alone?
Yes
Install Browser in
Pathway system
Use option 3 or 4
of the INSTVHS
routine
VST024.vsd
Before you run the INSTVHS routine, review Table 2-5 for the parameters required.
Table 2-5. VHS Browser Installation Parameter Values for a Stand-Alone Pathway
System (page 1 of 3)
No.
Name
Value
Default
Description
1
ISV
isv-subvol
current
subvolume
Specifies the name of the
installation subvolume
containing the software
update. The ISV
parameter is labeled
$volume.ZVHS.
2
VHS-BROWSERSUBVOL
VHS-Browsersubvol
$SYSTEM.VHS
B
Specifies the subvolume
in which INSTVHS places
the VHS Browser servers
and VHS Pathway
configuration files.
3
PATHWAY-SYSTEMTYPE
STAND-ALONE
STAND-ALONE
Specifies the target
Pathway system for the
VHS Browser facility.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 23
Installing the VHS Browser as a Stand-Alone
Pathway System
Installing VHS
Table 2-5. VHS Browser Installation Parameter Values for a Stand-Alone Pathway
System (page 2 of 3)
No.
Name
Value
Default
Description
4
PATHWAY-POBJ-FILEPREFIX
pathway-pobj
$SYSTEM.VHS
B.POBJ
Specifies the name of the
Pathway pseudo-object
TCLPROG library where
the VHS Browser
SCREEN COBOL
requesters will be
installed. The library
name contains from one
to five characters: for
example, POBJ.
5
PATHWAY-PATHMONNAME
pathmon-name
$ZVHS
Specifies the name of the
PATHMON that runs the
Pathway system. This
name will be used for the
creation of the VHS
Browser Pathway system.
6
VHS-BROWSER-NAME
VHS-Browsername
$VHSB
Specifies the name of the
VHS Browser process.
7
VHS-CONFIG-FILENAME
configuration
-file-name
$SYSTEM.VHS
B.VHSBCONF
Specifies the name of the
file that will contain the
VHS Browser
configuration for all
environments known by
the VHS Browser.
8
VHS-BROWSER-CPUS
VHS-Browsercpus
0:1
Specifies a pair of CPUs
on which the VHS
Browser server
processes will run.
9
VHS-BROWSERPRIORITY
VHS-Browserpriority
150
Specifies the NonStop
Kernel priority at which
the VHS Browser server
processes will run.
Pathway default is
PATHMON priority minus
10.
10
VHS-TCP-PRIORITY
VHS-tcppriority
DEFAULT
Specifies the NonStop
Kernel priority that the
VHS Browser TCP will
run. Pathway default is
PATHMON priority minus
20.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 24
Installing the VHS Browser as a Stand-Alone
Pathway System
Installing VHS
Table 2-5. VHS Browser Installation Parameter Values for a Stand-Alone Pathway
System (page 3 of 3)
No.
Name
Value
Default
Description
11
PATHWAY-OWNER
pathway-owner
N.A.
Specifies the user ID that
will be the owner of the
VHS Browser Pathway
system for management
purposes. The user ID
will also be used as the
owner of the VHS
Browser programs.
12
PATHWAY-SECURITY
pathwaysecurity
CCCC
Specifies the security
attributes for the Pathway
program, for
management purposes.
13
PROGRAM-SECURITY
programsecurity
NNNN
Specifies the security
attributes for the Pathway
program, indicating who
can use the VHS Browser
programs.
14
VHS-DEFAULTENVIRONMENT
environmentname
VHS
Specifies the default VHS
environment name used
by the VHS Browser. The
name must be from one
to eight letters.
15
VHS-DEFAULTPROMPT-FILE
promptlogfile
$SYSTEM.
VHSLOG.
PROMPT
Specifies the name of the
prompt log file used by
VHS-DEFAULTENVIRONMENT. The
form of this parameter is
$volume.subvol.PRO
MPT where
$volume.subvol
specifies the location of
the volume and
subvolume where the
default VHS environment
was installed.
Table 2-6 lists all the Pathway management files created by the installation of the VHS
Browser into a stand-alone Pathway system.
Table 2-6. NonStop VHS Browser Pathway Configuration and Management Files
File Name
File Description
ZVHSCONF
Pathway configuration file for the stand-alone Pathway system
ZVHSDEFS
Pathway configuration file defining the VHS Browser servers
ZVHSSTRT
Pathway configuration file starting the VHS Browser servers
VHSL
TACL macro used to start the VHS Log Browser program
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 25
VHS Browser Restrictions
Installing VHS
Table 2-6. NonStop VHS Browser Pathway Configuration and Management Files
File Name
File Description
VHSP
TACL macro used to start the VHS Prompt Browser program
VHSCOLD
TACL macro used to cold start the stand-alone Pathway system
VHSCOOL
TACL macro used to cool start the stand-alone Pathway system
VHSDOWN
TACL macro used to shut down the stand-alone Pathway system
VHS Browser Restrictions
Certain restrictions apply when you use the VHS Browser within the stand-alone
Pathway environment:
•
•
Printing is performed using the PATHMON user ID instead of the current user ID.
Screens can be written to a terminal, process, or printer, but not to a disk file. (This
is a Pathway restriction.)
•
Spooler output generated by the VHS Browser is owned by the owner of the
Pathway environment.
•
Events generated by the VHS Browser set the EMS token ZEMS-TKN-USERID to
the PATHMON user ID.
VHS Browser Installation as a Stand-Alone Pathway
System Procedure
This subsection summarizes the VHS Browser installation as a stand-alone Pathway
system. To run the INSTVHS routine, enter this at the TACL prompt:
3> instvhs
or
3> run instvhs
This command attaches the INSTSEGF segment file and displays an installation menu:
1-Install or update VHS and VHSCI programs and 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
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 26
VHS Browser Installation as a Stand-Alone Pathway
System Procedure
Installing VHS
Enter 3 to install the VHS Browser as a stand-alone Pathway system. The INSTVHS
program prompts you through the following steps:
1. Defining a File
Checks to see if a definition file exists and creates one if it does not. At its creation,
this file is filled with default values from your Pathway system.
2. Selecting and Defining the Parameters
Provides the VHS parameters. You can accept the default parameter values or
modify the appropriate parameters.
3. Validating File Parameters and Definitions
Verifies your settings for the VHS Browser parameters.
4. Validating the VHS Installation Subvolume
Verifies that all the files required to install VHS Browser are present in the VHS
ISV.
5. Deleting Old Copies of VHS Browser Servers and Requesters
Checks to see if VHS was previously installed in your Pathway system. It is
executed only if this is an update of the VHS Browser stand-alone Pathway
system. If so, the previous version of the VHS servers and requesters are deleted.
6. Installing the VHS Browser Server Programs and Data Files
Copies all the program and data files to the subvolume specified by the
VHS-BROWSER-SUBVOL parameter. If a previous VHS configuration file exists, it
is not updated.
7. Installing the VHS Browser Requesters
Copies all VHS requester programs to the location specified by the PATHWAYPOBJ-FILE-PREFIX parameter.
8. Creating the VHS Browser Pathway Configuration Files
Creates three Pathway configuration files:
ZVHSCONF
Contains the basic definitions to start the stand-alone Pathway
system.
ZVHSDEFS
Contains the VHS Browser server configuration. This file adds
the new server into the Pathway environment.
ZVHSSTRT
Contains the Pathway commands to start the VHS servers.
9. Creating the VHS Browser Pathway Management Files
Creates a set of Pathway management files used to start and stop the stand-alone
Pathway system and to invoke the VHS Program from a TACL prompt.
10. Creating the VHS Default Browser Configuration File
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 27
Pathway Installation Considerations
Installing VHS
Creates the default Browser configuration file used to list all the known VHS
environments on this system. The result is put in an EDIT file.
11. Installing VHS Browser Into the Pathway System
This is executed only if this is an update of the VHS Browser stand-alone Pathway
system. This step adds and starts the VHS servers in the Pathway environment.
12. Modifying the VHS Browser Environment Configuration File
This step is described in, Modifying the VHS Configuration Files on page 2-29
13. Starting and Stopping the VHS Browser Stand-Alone Pathway
The VHS Installation routine provides routines to start and stop the stand-alone
Pathway system. You always cold start a Pathway system the first time you run it
and again if you change the ZVHSCONF configuration file. The routines are:
•
To cold start the VHS Browser Pathway system, enter:
3> VOLUME program-subvol
4> VHSCOLD [/CPU PATHMON-cpu, PRI PATHMON-priority/]
[PATHMON-name]
•
To cool start the VHS Browser Pathway system, enter:
3> VOLUME program-subvol
4> VHSCOOL [/CPU PATHMON-cpu, PRI PATHMON-priority/]
[PATHMON-name]
•
To shut down the VHS Browser Pathway system, enter:
3> VOLUME program-subvol
4> VHSDOWN [PATHMON-name]
The CPU option specifies the PATHMON primary CPU. The default CPU is 0. PRI
specifies the PATHMON execution priority. PATHMON-name specifies the name of
the VHS Browser stand-alone PATHMON name. The default name of the VHS
Browser PATHMON is $ZVHS.
These routines are examples of how to start and stop the VHS Browser and might
not be appropriate for all installations. It is recommended that you customize these
routine macros for your specific system needs.
Pathway Installation Considerations
The following subsections describe additional considerations for installing VHS
Browser into your Pathway environment.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 28
Modifying the VHS Configuration Files
Installing VHS
VHS Browser Stand-Alone Pathway Configuration Files
When you install the VHS Browser as a stand-alone Pathway system, several files are
created. Table 2-6 lists all the files created. Three Pathway configuration files are
important to note:
ZVHSCONF
Starts the Pathway system.
ZPATHWAY
Adds VHS servers to the Pathway configuration.
ZVHSSTRT
Starts the VHS servers.
The VHS Browser facility is added and started automatically whenever you start your
Pathway system cold.
Security Considerations
The VHS Browser facility does not provide its own security checking. VHS relies on the
security system provided by Pathway to check for two authorization levels:
•
•
Who can install and start the VHS Browser facility
Who can run the VHS Browser facility
When INSTVHS is run, the VHS ISV files are restored with the operator’s ownership
and security values. Verify these values to ensure that they are acceptable. VHS
installation procedures require read access to the ISV files and result in files being
copied and created on the VHS-BROWSER-SUBVOL parameter subvolume.
Modifying the VHS Configuration Files
After you have installed the VHS process, VHSCI, VHS GUI Agent facility, and the
VHS Browser facility, you can modify the VHS configuration files (see Figure 2-5):
•
•
•
•
•
VHSSTART (VHS custom startup file)
VHSINSP (VHS Inspect file)
VHSCSTM (VHSCI custom configuration file)
VHSBCONF (VHS Browser environment configuration file)
VHSGCONF (VHS GUI Agent configuration file)
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 29
VHSSTART File
Installing VHS
Figure 2-5. Modifying the VHS Configuration Files
Customize VHS
configuration files
End
VST025vsd
VHSSTART File
VHSSTART is the startup file used to run VHS. The default VHSSTART file is shown in
Appendix B, VHS Limits. Example 2-1 shows an example of the VHSSTART file
modified to start three VHS environments: ATM, POS, and DEV.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 30
VHSSTART File
Installing VHS
Example 2-1. VHS Custom Startup File (page 1 of 2)
======================================================================
== NonStop Virtual Hometerm Subsystem - T9517D43 - (30SEP96)
== Copyright Tandem Computers Incorporated 1992, 1993, 1994, 1995, 1996
==
== File Type:
VHS Startup Configuration File.
==
== Source File Name:
$SYSTEM.STARTUP.VHSSTART
== Source File Version:
1
==
== File Description: This file is used to specify all the VHS environments
==
existing on this node.
==
== Modifications Summary:
==
== Added definition for the ATM, POS and DEV Environments, Oct. 10th, 1996
==
VOLUME $CTTMD.VDEV
== Start an EMS Alternate Collector for all the VHS processes
EMSACOLL/NOWAIT,PRI 100,NAME $CVHS, CPU 3/BACKUP 2
== Set up =_EMS_COLLECTOR define to specify an EMS
== alternate collector to be used by all VHS processes
DELETE DEFINE =_EMS_COLLECTOR
SET DEFINE CLASS MAP
SET DEFINE FILE $CVHS
ADD DEFINE =_EMS_COLLECTOR
==================================================================
==
== Define first VHS environment = DEV
==
PARAM ENVIRONMENT
"DEV"
ASSIGN
PARAM
PARAM
PARAM
PRIMARY-LOGFILE,
MAXEXTENTS
PRIMARY-SECURITY
SUPPRESS-DISPLAY
ASSIGN INSPECT-SAVEFILE,
PARAM PURGE-SAVEFILE
ASSIGN INSPECT-FILE,
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
$CTTMD.VDEV.DEV, EXT (100, 100), CODE 0
16
"NUUU"
FALSE
$CTTMD.VDEV.SAVE0000
FALSE
$CTTMD.VDEV.VHSINSP
VHS-LOGGER
ADD-TEXT-TO-EVENT
GENERATE-INSPECT-EVENT
GENERATE-PROMPT-EVENT
GENERATE-DISPLAY-EVENT
REMOVE-EXTRA-SPACES
ACCEPT-EXT-ASCII-CHARACTER
VHS-GUI-MODE
PROMPT-EVENT-RESEND-DELAY
ON
ON
ON
ON
ON
ON
OFF
OFF
15
PARAM AUTOMATIC-INSPECT-PROCESSING ON
PARAM BACKUP-CREATION-MESSAGE-DELAY 5
PARAM OPEN-TABLE-THRESHOLD
90
RUN $CTTM.ZVHSQA.VHS / NAME $VDEV, CPU 3, PRI 150, NOWAIT/ 0
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 31
VHSSTART File
Installing VHS
Example 2-1. VHS Custom Startup File (page 2 of 2)
====================================================================
== Define second VHS environment = POS
==
PARAM ENVIRONMENT
"POS"
ASSIGN
PARAM
PARAM
PARAM
$DATA.VPOS.POS, EXT (100, 100), CODE 0
16
"NUUU"
FALSE
PRIMARY-LOGFILE,
MAXEXTENTS
PRIMARY-SECURITY
SUPPRESS-DISPLAY
ASSIGN INSPECT-SAVEFILE,
PARAM PURGE-SAVEFILE
ASSIGN INSPECT-FILE,
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
$DATA.VPOS.POS10000
FALSE
$DATA.VPOS.VHSINSP
VHS-LOGGER
ADD-TEXT-TO-EVENT
GENERATE-INSPECT-EVENT
GENERATE-PROMPT-EVENT
GENERATE-DISPLAY-EVENT
REMOVE-EXTRA-SPACES
ACCEPT-EXT-ASCII-CHARACTER
VHS-GUI-MODE
PROMPT-EVENT-RESEND-DELAY
ON
ON
ON
ON
ON
ON
OFF
ON
10
PARAM AUTOMATIC-INSPECT-PROCESSING ON
PARAM BACKUP-CREATION-MESSAGE-DELAY 5
PARAM OPEN-TABLE-THRESHOLD
90
RUN $CTTM.ZVHSQA.VHS / NAME $VPO1, CPU 3, PRI 150, NOWAIT/ 0
ASSIGN INSPECT-SAVEFILE,
$DATA.VPOS.POS20000
ASSIGN INSPECT-FILE,
$DATA.VPOS.VHSINSP2
RUN $CTTM.ZVHSQA.VHS / NAME $VPO2, CPU 2, PRI 150, NOWAIT/ 1
==================================================================
== Define third VHS environment = ATM
==
PARAM ENVIRONMENT
"ATM"
ASSIGN
PARAM
PARAM
PARAM
$PROD2.VATM.ATM, EXT (100, 100), CODE 0
16
"NUUU"
FALSE
PRIMARY-LOGFILE,
MAXEXTENTS
PRIMARY-SECURITY
SUPPRESS-DISPLAY
ASSIGN INSPECT-SAVEFILE,
PARAM PURGE-SAVEFILE
ASSIGN INSPECT-FILE,
RUN $CTTM.ZVHSQA.VHS / NAME
$PROD2.VATMD.SAVE0000
FALSE
$DATA.VATMD.VHSINSP
$VAT1, CPU 0, PRI 150, NOWAIT/ 1
ASSIGN INSPECT-SAVEFILE,
$PROD2.VATMD.SAV20000
ASSIGN INSPECT-FILE,
$DATA.VATMD.VHSINSP2
RUN $CTTM.ZVHSQA.VHS / NAME $VAT2, CPU 1, PRI 150, NOWAIT/ 2
ASSIGN INSPECT-FILE,
$DATA.VATMD.VHSINSP3
ASSIGN INSPECT-SAVEFILE,
$PROD2.VATMD.SAV30000
RUN $CTTM.ZVHSQA.VHS / NAME $VAT3, CPU 2, PRI 150, NOWAIT/ 3
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 32
VHSINSP File
Installing VHS
VHSINSP File
To automatically process Inspect prompts, VHS uses a VHS Inspect file (VHSINSP)
that will contain commands to send to Inspect depending on the process name, the
program file name, or the application language. This file is empty at installation time.
When VHS receive an Inspect prompt, it first gets information on the application
currently prompting and tries to find in the VHS Inspect file a section corresponding to
the application. It then sends the commands of the section matching the application to
Inspect and, if Inspect prompts VHS back, VHS tries to create a SAVEABEND file. See
Section 3 for more details.
VHSCSTM File
From the installation of the VHS and VHSCI programs, a custom configuration file
(VHSCSTM) is created. If this file is located in your default subvolume, it will be read
each time you run VHSCI. All VHSCI users should have their own VHSCSTM file in
their own default subvolumes. You can use an ASSIGN command to tell VHSCI to read
the VHSCSTM file from another subvolume if desired.
1> ASSIGN VHSCSTM, $DATA.ZVHS.VHSCSTM
2>
3> == You may now run VHS and it will get VHSCSTM file
4> == from $DATA.ZVHS.VHSCSTM
The VHSCI custom configuration file can be used to configure your session
parameters. You can use the ALIAS command to create shortcut commands for
frequently invoked commands. By using the ALIAS command, you can substitute the
typing of an abbreviated command or pressing of a function key for the original
command or combination of commands. For example, if F1 is defined as the INFO
command, each time you press F1, VHSCI interprets this key as the INFO command
and executes this command.
For information about VHSCI commands, see Section 7, Command Descriptions.
For a sample of a VHSCSTM file, see Appendix A, VHS Files.
VHSBCONF File
VHSBCONF is the VHS Browser environment configuration file. You need to modify
the default file if you want to do the following:
•
•
Change the location of the VHS primary log file
Set up multiple VHS environments
After you modify the VHS Browser environment configuration file and you want to have
the VHS Browser read the latest copy, go to the VHS Profile screen and press F14 to
refresh the profile. The VHS Browser checks the timestamp of the file and reloads it if
the file was changed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 33
VHSBCONF File
Installing VHS
Example 2-2 shows a sample VHS Browser environment configuration file. In this
example, two VHS environments are installed:
•
•
A default environment called VHS with the primary log file volume and subvolume
$SYSTEM.VHS
An environment called ATM with the primary log file volume and subvolume
$PROD.VHSLOG
Example 2-2. VHS Browser Environment Configuration File
============================================================================
==
== NonStop Virtual Hometerm Subsystem - T9517D43 - (30SEP96)
== Copyright Tandem Computers Incorporated 1992, 1993, 1994, 1995, 1996
==
== File Type:
VHS Browser Environment Configuration File.
==
== Source File Name:
$VHS.VHSD43.VHSBCONF
== Source File Version:
1
==
== File Description: This file is used to define the relationship
==
between the environment Name used by the VHS Browser
==
screens and the different VHS server environments.
==
== File Structure:
Two record types are valid.
==
The first one is a comment line and should begin
==
with two equal signs "==".
==
The second record type is the mapping of the
==
environment name to the prompt file name of each
==
VHS environment. Each line should contain the
==
following items:
==
<environment-name> <1 or more space> <VHS prompt file name>
==
== Modifications Summary:
== Sept. 30, 1996 10:55:58
File Creation.
==
============================================================================
== Default configuration for the VHS Browser Environment file
============================================================================
== <environment-name> <1 space or more> <VHS prompt file name>
==
VHS
$SYSTEM.VHS.PROMPT
ATM
$PROD.VHSLOG.PROMPT
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 34
VHSGCONF File
Installing VHS
Example 2-3 shows a sample VHS Browser environment configuration file with three
VHS environments installed: ATM, POS, and DEV.
Example 2-3. VHS Browser Customized Environment Configuration File
============================================================================
==
== NonStop Virtual Hometerm Subsystem - T9517D43 - (30SEP96)
== Copyright Tandem Computers Incorporated 1992, 1993, 1994, 1995, 1996
==
== File Type:
VHS Browser Environment Configuration File.
==
== Source File Name:
$VHS.VHSD43.VHSBCONF
== Source File Version:
1
==
== File Description: This file is used to define the relationship
==
between the environment Name used by the VHS Browser
==
screens and the different VHS server environments.
==
== File Structure:
Two record types are valid.
==
The first one is a comment line and should begin
==
with two equal signs "==".
==
The second record type is the mapping of the
==
environment name to the prompt file name of each
==
VHS environment. Each line should contain the
==
following items:
==
<environment-name> <1 or more space> <VHS prompt file name>
==
==
== Modifications Summary:
== Sept. 30, 1996 10:55:58
File Creation.
==
== Added the DEV,ATM and POS Environment, Oct. 17, 1996
==
======================================================================
== Default configuration for the VHS Browser Environment file
======================================================================
== <environment-name> <space> <VHS Prompt file name>
==
DEV
$CTTMD.VDEV.PROMPT
ATM
$PROD2.VATM.PROMPT
POS
$DATA.VPOS.PROMPT
VHSGCONF File
VHSGCONF is the VHS GUI Agent configuration file. You need to modify the default
file if you want to do the following:
•
•
Use the VHS GUI facility
Restrict VHS GUI user capabilities
The VHSGCONF file must reside in the $SYSTEM.SYSTEM subvolume. See
Appendix 8, The VHS GUI for a detailed description of this file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 35
VHS Run-Time Options
Installing VHS
VHS Run-Time Options
The following subsections present some file-specific considerations that you should be
aware of before using VHS.
VHS ASSIGNs
You can customize the VHS server to your specific requirements with a set of run-time
options. These run-time options can be modified by editing the VHS startup file created
during the installation process.
Table 2-7 lists each ASSIGN used by VHS.
Table 2-7. VHS ASSIGNs
ASSIGN
Name
Default Value if Omitted
Description
PRIMARYLOGFILE
$SYSTEM. VHSLOG.LOG
Specifies the name of the primary log
file for VHS. The form of this
parameter is
$volume.subvolume.aaa where
aaa must be alphabetical: for
example, $SYSTEM.VHSLOG.LOG.
The primary and secondary extents
of the primary-logfile are also
specified using this ASSIGN.
INSPECTFILE
$currentvolume.subvolume.VHSINSP
Specifies the name of the VHS
Inspect file used for automatic
processing of Inspect prompts.
INSPECTSAVEFILE
$SYSTEM.VHSDUMP.SAVE0000
Specifies the name of the Inspect
SAVEABEND files for VHS. The form
of this parameter is
$SYSTEM.VHSDUMP.SAVE0000.
VHS Conversational Interface Help and Error Text File
The VHSTEXT file contains help text and error messages for VHSCI. This file should
be located in the same subvolume as VHSCI. If you want VHSTEXT to be located on a
different subvolume from the VHSCI program, you can use an ASSIGN command to
tell VHSCI to read the VHSTEXT file from another subvolume.
1> ASSIGN VHSTEXT, $DEV.ZVHS.VHSTEXT
2>
3> == You may now run VHS and it will get VHSTEXT file
4> == from $DEV.ZVHS.VHSTEXT
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 36
VHS Parameters
Installing VHS
VHS Parameters
Table 2-8 lists each parameter used by VHS and its default value if omitted.
Table 2-8. VHS Parameters (page 1 of 2)
Parameter Name
Default
Description
ACCEPT-EXTASCIICHARACTER
OFF
Specifies if VHS will accept non-ascii characters (e.g.
Kanji). The value can be ON or OFF.
AUTOMATICINSPECTPROCESSING
ON
Specifies if VHS will automatically process Inspect
prompts. The value can be ON or OFF.
BACKUPCREATION-DELAY
5
Delay in minutes between each occurrence of the backup
creation failure message. The value must be between 0
and 999.
ENVIRONMENT
VHS
Specifies the name of the environment that this VHS
process will run. This name has two purposes: a prefix for
all EMS messages generated, and for the VHS Browser
facility to specify which VHS environment the user wants
to look at.
GENERATEDISPLAY-EVENT
ON
Specifies if EMS events must be generated for display
type messages. The value can be ON or OFF. If the VHSGUI-MODE parameter is ON, GENERATE-DISPLAYEVENT will always be considered to be ON.
GENERATEINSPECT-EVENT
ON
Specifies if EMS events must be generated for
Inspect/Debug type messages. The value can be ON or
OFF. If the VHS-GUI-MODE parameter is ON,
GENERATE-INSPECT-EVENT will always be considered
to be ON.
GENERATEPROMPT-EVENT
ON
Specifies if EMS events must be generated for
prompt/reply type messages. The value can be ON or
OFF. If the VHS-GUI-MODE parameter is ON,
GENERATE-PROMPT-EVENT will always be considered
to be ON.
MAXEXTENTS
16
Specifies the maximum number of extents to be created
for the primary log file. The value is an integer in the
range of 0 through 978.
OPEN-TABLETHRESHOLD
90
Specifies the percentage of full value of the opener table
at which VHS will generate an EMS event message. The
value must be between 0 and 100.
PRIMARYSECURITY
NUUU
Specifies the default security used by VHS when it
creates primary log files.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 37
VHS DEFINE Parameter
Installing VHS
Table 2-8. VHS Parameters (page 2 of 2)
Parameter Name
Default
Description
PROMPT-EVENTRESEND-DELAY
15
Specifies the time (in minutes) VHS will wait before
generating a repeat (ZVHS-EVT-RESEND-PROMPT)
event for an unanswered prompt. This parameter will be
ignored if VHS-GUI-MODE is set to OFF. The possible
values are from 1 to 60. See Section 8, The VHS GUI for
a more complete description of this parameter.
PURGE-SAVEFILE
FALSE
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 will purge any savefile that
existed before with the same file name. The valid
parameter values are TRUE or FALSE.
REMOVE-EXTRASPACES
TRUE
Specifies whether VHS deletes extra spaces (two or more
consecutive spaces) in displaying messages. By deleting
extra spaces, VHS makes the messages more readable
and prevents line truncations if messages exceed
displayable line length.
SUPPRESSDISPLAY
FALSE
Specifies whether the display messages sent to VHS will
be shown on the ViewPoint or NonStop NET/MASTER
screen. The valid parameter values are TRUE or FALSE.
When the VHS-GUI-MODE parameter is ON, VHS
generates additional display events that are not affected
by this parameter. See Section 8, The VHS GUI for a
more complete description of these events.
VHS-LOGGER
ON
Specifies if VHS must log in its primary log files. The
value can be ON or OFF.
VHS-GUI-MODE
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 or OFF. See Section 8, The
VHS GUI for a more complete description of this
parameter.
VHS DEFINE Parameter
Table 2-9 lists the DEFINE parameter used by VHS and its default value.
Table 2-9. VHS DEFINE
DEFINE Name
Default Value
Description
=_EMS_COLLECTOR
LOCAL COLLECTOR ($0)
Specifies the name of the collector
used by VHS to report its events.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2- 38
3
Using VHS
This section describes how to use VHS. It has the following subsections:
•
•
•
•
•
•
•
•
Before using VHS
Starting VHS
Specifying VHS as the home terminal of applications
How VHS manages messages
Configuring VHS Inspect processing
Understanding the VHS log files
Stopping VHS
Using VHS with a ViewPoint filter
Before Using VHS
Before you can use VHS, you need to determine which applications should use VHS
as a home terminal.
To use VHS with an application, follow these steps:
1. Start VHS.
2. Stop the application.
3. Configure the application so that the VHS process is its home terminal. (See the
subsection Specifying VHS as the Home Terminal of Applications later in this
section.)
4. Start the application.
Because the application is not available between the time you stop it and restart it, you
need to plan how to integrate VHS in your application environment to minimize
application downtime.
Caution. The hometerm of VHS should be a physical (static) device. A dynamic device, such
as a Telnet window, might cause problems when it is terminated.
Starting VHS
To run VHS, locate and invoke the startup file created during the installation process.
For example, if the VHS startup file VHSSTART was created on $SYSTEM.STARTUP,
then you would type the following command:
1> OBEY $SYSTEM.STARTUP.VHSSTART
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -1
Starting VHS
Using VHS
When VHS starts, it reads and validates all ASSIGNs, parameters, and DEFINEs to
initialize its environment. If a parameter is not specified, VHS uses its default values
(listed in Section 2).
If the parameters are valid, VHS does the following:
•
•
•
•
Creates a backup process
Opens the prompt file (if it does not exist, it is created)
Opens the log file (if it does not exist, it is created)
Waits for application messages to arrive
While the VHS process is executing, you can modify some of its configuration
parameters by using the VHSCI conversational interface. See the ALTER Command,
ENV Command, PARAM Command, and TIMEOUT Command in Section 7, Command
Descriptions.
Note. To run VHS with High PIN support, ensure that the #HIGHPIN built-in variable is set to
On at the TACL prompt.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -2
Sample VHSSTART File
Using VHS
Sample VHSSTART File
The following is an example of a VHSSTART startup file that has been modified to start
three VHS processes ($VHS1, $VHS2, $VHS3) using the same primary log file:
==========================================================================
==
== NonStop Virtual Hometerm Subsystem - T9517D43 - AAQ - (26FEB98)
== Copyright Tandem Computers Incorporated 1992, 1993, 1994, 1995, 1996,
1997
==
== File Type:
VHS Startup Configuration File.
==
== Source File Name:
$SYSTEM.VHS.VHSSTART
== Source File Version:
1
==
== File Description: This file is used to specify all the VHS environments
==
existing on this node.
==
== Modifications Summary:
== February 12, 1998 14:16:37
File Creation.
==
==========================================================================
==
== Define first VHS Environment "VHS"
==========================================================================
==
DELETE DEFINE =_EMS_COLLECTOR
SET DEFINE CLASS MAP
SET DEFINE FILE $0
ADD DEFINE =_EMS_COLLECTOR
PARAM
ENVIRONMENT-NAME
ASSIGN
PARAM
PARAM
PARAM
PARAM
PARAM
PRIMARY-LOGFILE,
$SYSTEM.VHSLOG.LOG, EXT (100, 100), CODE 0
PRIMARY-LOGFILE-BUFFERED OFF
PRIMARY-LOGFILE-PURGE
ON
MAXEXTENTS
16
PRIMARY-SECURITY
"NUUU"
SUPPRESS-DISPLAY
FALSE
ASSIGN INSPECT-SAVEFILE,
PARAM PURGE-SAVEFILE
ASSIGN INSPECT-FILE,
"VHS"
$SYSTEM.VHSDMP1.SAVE0000
FALSE
$SYSTEM.VHSDMP1.VHSINSP
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -3
Guidelines for Running VHS
Using VHS
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
VHS-LOGGER
ADD-TEXT-TO-EVENT
GENERATE-INSPECT-EVENT
GENERATE-PROMPT-EVENT
GENERATE-DISPLAY-EVENT
REMOVE-EXTRA-SPACES
ACCEPT-EXT-ASCII-CHARACTER
VHS-GUI-MODE
PROMPT-EVENT-RESEND-DELAY
ON
ON
ON
ON
ON
ON
OFF
OFF
15
PARAM AUTOMATIC-INSPECT-PROCESSING ON
PARAM BACKUP-CREATION-MESSAGE-DELAY 5
PARAM OPEN-TABLE-THRESHOLD
90
RUN $SYSTEM.VHS.VHS / NAME $VHS1, CPU 0, PRI 180, TERM $TRM0.#A, NOWAIT/ 1
==
== Second VHS process $VHS2
==
ASSIGN INSPECT-SAVEFILE,
$SYSTEM.VHSDMP2.SAVE0000
ASSIGN INSPECT-FILE,
$SYSTEM.VHSDMP2.VHSINSP
RUN $SYSTEM.VHS.VHS / NAME $VHS2, CPU 0, PRI 180, TERM $TRM0.#A, NOWAIT/ 1
== Third VHS process $VHS3
==
ASSIGN INSPECT-SAVEFILE,
$SYSTEM.VHSDMP3.SAVE0000
ASSIGN INSPECT-FILE,
$SYSTEM.VHSDMP3.VHSINSP
RUN $SYSTEM.VHS.VHS / NAME $VHS3, CPU 0, PRI 180, TERM $TRM0.#A, NOWAIT/ 1
Guidelines for Running VHS
If you use the VHSSTART file to start VHS, you do not need to be concerned with the
following run-time guidelines. However, if you run VHS from TACL, make sure you
follow these guidelines:
•
•
•
VHS must be run as a named process because it is opened by other processes
and has device subtype 30 (device emulation).
VHS should be run as a process pair because it must be always available to
receive messages.
To run VHS with High PIN support, ensure that the #HIGHPIN built-in variable is
set to On at the TACL prompt.
Caution. The hometerm of VHS can be a dynamic device, such as a Telnet window, but this
might cause problems when the window is terminated. It is safer to start VHS with a physical
(static) device.
VHS Run Syntax
The syntax for the VHS RUN command follows.
[ RUN ] VHS / name $process-name, nowait [, run-option ] /
backup-cpu-number
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -4
VHS Run Syntax
Using VHS
RUN
specifies the TACL RUN command.
VHS
specifies the program file name of the VHS program.
NAME $process-name
specifies the name you are assigning to VHS. Specify $process-name as an
alphanumeric string of one to five characters, the first of which must be a letter.
Examples of VHS process names are $VHS1, $VHS2, or $HOME.
Note. VHS is a subtype 30 process and must be named to execute properly. VHS does
not start if it is an unnamed process.
NOWAIT
specifies that TACL does not wait while the program runs. TACL returns a
command input prompt after sending the startup message to the new process. You
should always specify NOWAIT when you run VHS.
run-option
specifies any of the NonStop Kernel run options, separated by commas, valid for
the RUN command in TACL, as described in the TACL Reference Manual. The
following options are of particular importance for this command:
CPU cpu-number
specifies the number of the processor where the primary process of VHS is to
execute. cpu-number is an integer in the range 0 through 15. If you omit this
option, VHS runs in the same processor as TACL. (If the CPU option is omitted
and a $CMON process exists, $CMON might specify a CPU other than the one
in which the current TACL process is running. For more information about
$CMON, see the NonStop Kernel Operating System Programmer’s Guide.)
PRI priority
specifies the run priority of the VHS process. The priority must be an integer in
the range 1 to 199. If you omit this option, VHS runs at a priority of 1 less than
that of the TACL process. If your applications have a high message rate, you
should specify a high priority. (If a $CMON process exists, $CMON might
specify a priority other than 1 less than your TACL process. For more
information about $CMON, see the NonStop Kernel Operating System
Programmer’s Guide.)
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -5
VHS Run Syntax
Using VHS
backup-cpu-number
specifies the number of the processor in which the backup process of VHS is to
execute. cpu-number is an integer in the range 0 through 15. If you omit this
parameter, VHS does not run as a process pair.
Caution. Make sure you specify the backup CPU number when running VHS. Specifying the
backup CPU number ensures that VHS runs as a NonStop process and is always available to
your applications.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -6
Specifying VHS as the Home
Terminal of Applications
Using VHS
Specifying VHS as the Home
Terminal of Applications
How you specify VHS as the home terminal of your application depends on what type
of application you have. For most non-Pathway applications, specifying VHS as the
home terminal is simple. For Pathway applications, specifying VHS as the home
terminal can be done by using several methods. Two of these methods are described
in the subsections below.
Before you specify VHS as the home terminal for your applications, make sure VHS is
running. If VHS is not running, your application will not work correctly and might not
start.
Non-Pathway Applications
When you start a non-Pathway application from TACL, modify the TERM attribute and
specify the name of the VHS process. The following command starts a non-Pathway
application MYAPP and specifies the VHS process $VHS as the home terminal for this
application:
1> RUN MYAPP / NAME $APP, NOWAIT, CPU 3, TERM $VHS /
Pathway Application Example 1
If you have not hardcoded the HOMETERM attribute for every server in the Pathway
configuration file, you can use this first method to specify VHS as the home terminal.
1. Stop Pathway to reconfigure it.
2. Modify the Pathway startup file to start the VHS process before the Pathway
system is started and to cold load the Pathway system. The TERM option of the
command to start PATHMON should be set to the VHS process, for example,
$VHS. Setting the TERM option will ensure that all the servers have the same
home terminal as the PATHMON process.
In the following example, the Pathway startup file includes two commands to run
with VHS. These commands are in boldface:
OBEY $SYSTEM.STARTUP.STARTVHS
PURGE PATHLOG
CREATE PATHLOG, 4
PURGE PATHCTL
ASSIGN PATHCTL, PATHCTL
PATHMON /NAME $DJCT, OUT PATHLOG, NOWAIT, TERM $VHS, CPU 0/
PATHCOM /IN PATHCNFG/ $DJCT
3. When you start the PATHMON process of your Pathway system, be sure to use the
TERM option to specify the home terminal of PATHMON. In this example, the VHS
process is named $VHS:
1> PATHMON / NAME $PM, NOWAIT, CPU 3, TERM $VHS /
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -7
Pathway Application Example 2
Using VHS
By default, each server class uses the home terminal of the PATHMON process.
Note. If you create your new Pathway configuration file by using the OBEYFORM facility,
then all TCPs and servers will have the SET HOMETERM parameter set. Check to make
sure all home terminals are set to the VHS process.
Pathway Application Example 2
If you have already hardcoded the HOMETERM attribute for every server in the
Pathway configuration file, you will have to modify the HOMETERM attribute as
specified for the EMPLOYEE-SERVER in the following example. The command that
specifies VHS as the home terminal is in boldface.
SET PATHMON BACKUPCPU 1
SET PATHWAY MAXASSIGNS 10
SET PATHWAY MAXDEFINES 5
SET PATHWAY MAXPARAMS 5
SET PATHWAY MAXPATHCOMS 5
SET PATHWAY MAXPROGRAMS 5
SET PATHWAY MAXSERVERCLASSES 5
SET PATHWAY MAXSERVERPROCESSES 20
SET PATHWAY MAXSTARTUPS 5
SET PATHWAY MAXTCPS 5
SET PATHWAY MAXTERMS 10
SET PATHWAY MAXLINKMONS 16
START PATHWAY COLD !
RESET TCP
SET TCP AUTORESTART 2
SET TCP MAXREPLY 2000
SET TCP MAXTERMDATA 32000
SET TCP SERVERPOOL 20000
SET TCP TERMPOOL 8000
SET TCP MAXTERMS 25
SET TCP MAXPATHWAYS 5
SET TCP PROGRAM $SYSTEM.SYSTEM.PATHTCP2
SET TCP TCLPROG POBJ
ADD TCP TCP-6530, CPUS 0:1
RESET PROGRAM
ADD PROGRAM EMPREQ, TYPE T16-6530 (INITIAL EMPREQ), TCP TCP-6530
RESET SERVER
SET SERVER PROGRAM EMPSRV
SET SERVER CPUS (0:1)
SET SERVER HOMETERM $VHS
SET SERVER MAXSERVERS 5, NUMSTATIC 0
SET SERVER LINKDEPTH 1, MAXLINKS 5
SET SERVER TMF ON, AUTORESTART 2
SET SERVER ASSIGN ERROR-LOG-FILE, ERRORLOG
SET SERVER ASSIGN EMPLOYEE-FILE, EMPLOYEE
ADD SERVER EMPLOYEE-SERVER
RESET SERVER
SET SERVER PROGRAM TSTSRV
SET SERVER CPUS (0:1)
SET SERVER MAXSERVERS 5, NUMSTATIC 0
SET SERVER LINKDEPTH 1, MAXLINKS 5
SET SERVER TMF ON, AUTORESTART 2
SET SERVER ASSIGN ERROR-LOG-FILE, ERRORLOG
SET SERVER ASSIGN EMPLOYEE-FILE, TESTCONV
ADD SERVER TESTCONV-SERVER
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -8
How VHS Manages Messages
Using VHS
After you have reconfigured your Pathway system, you can restart it and your Pathway
application.
How VHS Manages Messages
The VHS process receives messages of many types from many sources. VHS
manages these types of messages:
•
•
•
•
•
•
OPEN messages
Display messages
Inspect prompts
Debug prompts
Application prompts
Reply messages (to application prompts)
The following table summarizes how VHS responds to application messages and
prompts.
Type of message
VHS Action
Open message
Determines the object file of the process and acts accordingly.
Display message
Saves the message in the text part of an EMS event, sends the event
to the collector if configured to do so (see parameter GENERATEDISPLAY-EVENT), and logs the message in the primary log file.
Inspect prompt
Depending on the VHSINSP file and the AUTOMATIC-INSPECTPROCESSING parameter, VHS handles the Inspect prompt by
sending commands found in the VHSINSP file, and creates a
saveabend file to save the application’s context and stops the
application; or, VHS lets you handle the prompt by writing to its prompt
file. VHS logs 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).
Debug prompt
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).
Application prompt
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-PROMPTEVENT), and logs the message.
Reply messages
Sends reply messages to the application, keeps a copy of the reply in
its primary log file, removes the prompt from its prompt file, and, if
configured to do so (see the GENERATE-PROMPT-EVENT),
generates an EMS event.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3 -9
OPEN Message Processing
Using VHS
OPEN Message Processing
When VHS receives an OPEN message, it goes through the following steps:
1. VHS adds an entry into the opener table and executes the NonStop Kernel
procedure PROCESSINFO to determine the name of the object file of the process.
2. If the object file name is equal to Inspect, then VHS sets the opener type as
Inspect.
3. If the state of the program is Debug, then VHS sets the opener type as Debug.
4. For all the other openers, VHS sets the opener type as Unknown.
Note. VHS cannot be opened by remote processes. VHS can only be opened by local
processes.
Display Message Processing
When VHS receives a DISPLAY message (a WRITE), it updates its opener table to
reflect that the last message received was a DISPLAY and validates the text message
to ensure that no unprintable characters are present.
If the parameter ACCEPT-EXT-ASCII-CHARACTER (default is OFF) is set to ON, VHS
accepts these characters (for example, Kanji characters); if not, VHS converts these
characters into question marks (?).
If the parameter REMOVE-EXTRA-SPACES is set to ON, VHS replaces an occurrence
of multiple spaces by only one space in the DISPLAY message. It then adds a
timestamp to the message and writes the message to its current primary log file.
If the parameter GENERATE-DISPLAY-EVENT is set to ON, VHS generates an EMS
message with the ZEMS-TKN-TEXT token containing the text message received from
the application.
Note that DISPLAY type messages include all messages written using the WRITE
NonStop Kernel procedure. This includes DISPLAY messages in COBOL as well as all
messages from the COBOL 74 and COBOL85 run-time libraries.
Inspect Prompt Processing
When VHS receives an Inspect message, it logs all display messages received from
Inspect in its Primary log file and, at the first Inspect prompt received, VHS sends the
SET PROMPT PID LANGUAGE (SET P P,L) command. When the Inspect prompt
comes back and if the AUTOMATIC-INSPECT-PROCESSING parameter is set to OFF:
•
VHS writes the prompt to its prompt file and the user is able to reply to this Inspect
prompt via the Prompt Browser screen.
Or, if the AUTOMATIC-INSPECT-PROCESSING parameter is set to ON:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 10
Debug Prompt Processing
Using VHS
•
•
•
•
•
•
VHS extracts the name and the PID of the application from the result of the
SET P P,L command.
VHS extracts the language of the application trapped into Inspect from the ENV
Inspect command.
When Inspect prompts VHS back, VHS tries to find a match between the
application information and one of the sections from the VHS Inspect file. The VHS
Inspect file format is described later in this section.
If a section matched the application information, VHS sends the commands of this
particular section to Inspect. If, after executing the Inspect commands, Inspect
prompts VHS again, VHS creates a saveabend file and stops the application.
If none of the VHS Inspect file sections matched the application information
trapped into Inspect, VHS creates a saveabend file and stops the application.
Every Inspect command executed is logged in the primary log file and an EMS
event is generated only if the parameter GENERATE-INSPECT-EVENT is set
to ON.
Debug Prompt Processing
When VHS receives a Debug message, VHS logs the message as a DEBUG
message, sends the D;T;S (Display; Trace; Stop) commands to Debug, logs the result
of the commands to its primary log file, stops the application, and generates an EMS
message to the collector if the parameter GENERATE-INSPECT-EVENT is set to ON.
Application Prompt Processing
When VHS receives an application prompt (a WRITEREAD), it updates its opener
table to reflect that the last message received was a prompt and validates the text
message to ensure that no unprintable characters are present. If the parameter
ACCEPT-EXT-ASCII-CHARACTER (default is OFF) is set to ON, VHS accepts these
characters (for example, Kanji characters); if not, VHS converts these characters into
question marks (?). Next, it adds a timestamp to the message and writes it to its
current primary log file and to the prompt file. It then, if the parameter GENERATEPROMPT-EVENT is set to ON, generates an EMS message with the ZEMS-TKNTEXT token containing the prompt message received from the user application.
Reply Message Processing
When VHS receives a reply message, it sends the reply message to the application,
logs the reply text in its log file, and then deletes the application prompt from its prompt
file. VHS generates an EMS message to the collector if the parameter GENERATEPROMPT-EVENT is set to ON.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 11
Configuring VHS Inspect Processing
Using VHS
Configuring VHS Inspect Processing
To handle Inspect prompts, VHS uses the AUTOMATIC-INSPECT-PROCESSING
parameter and a file (VHSINSP) that contains various sections specifying Inspect
commands to execute depending on the process name, the program file name, or the
language of the application trapped into Inspect.
VHS AUTOMATIC-INSPECT-PROCESSING Parameter
The AUTOMATIC-INSPECT-PROCESSING parameter can be set to ON (true) or OFF
(false). Setting the parameter to ON causes VHS to automatically reply to the Inspect
prompt by sending the commands from the VHS Inspect file. If the parameter is set to
OFF, VHS writes the Inspect prompt to its prompt file and the user will be able to reply
to it via the Prompt Browser screen. The AUTOMATIC-INSPECT-PROCESSING
parameter can be set when starting VHS, as part of the VHS startup file (VHSSTART).
If the parameter value is not set, the default is ON.
The parameter value can also be set and changed online via the VHSCI by using the
ALTER command. The ALTER command will not have any effect on already existing
Inspect openers and subsequently for all applications that are handled by those
Inspect openers. The ALTER command will take effect only with new Inspect openers.
This means that, if a new application is trapping into Inspect and an already existing
Inspect (one already opening VHS) is handling this application, the new value of the
AUTOMATIC-INSPECT-PROCESSING parameter won’t be in effect.
Inspect Processing Considerations
Changing the value of the AUTOMATIC-INSPECT-PROCESSING parameter online
can create unexpected situations as in the following scenario:
AUTOMATIC-INSPECT-PROCESSING Parameter value is ON.
VHS has two Inspect openers:
•
•
Inspect #1 has 1 application to handle .
Inspect #2 has 2 applications to handle:
The value of the parameter is changed to OFF via the VHSCI.
A new application traps into Inspect. The application is dispatched to Inspect #2, which
already opens VHS. Because the Inspect opener is not a new one, the value of the
parameter won’t be in effect for the new application. This means that the new
application will be handled automatically by VHS instead of going into the Prompt file to
be handled by the user.
VHS Inspect File
You configure the VHS Inspect processing via the VHS Inspect file (VHSINSP). When
receiving an Inspect message, VHS tries to match the application information with the
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 12
VHS Inspect File
Using VHS
information contained in the VHSINSP file. The VHSINSP file is composed of section
keywords such as PROCESS, PROGRAMFILE, and LANGUAGE; of section names
such as process name, program file name, and language name; and of Inspect
commands. Each section is delimited by a section keyword. A name is expected on
the same line as the keyword.
For the keyword PROCESS, a process name is expected, for the keyword
PROGRAMFILE, a program file name (object file name) is expected, and for the
keyword LANGUAGE, a language name is expected. Each section contains all the
Inspect commands to be executed for the specific process name, program file name,
or for the language of the application trapped into Inspect. The first section matching
the application information will be the one to be used by VHS, and only one section is
used per application. A section can be used for many applications.
Following is the syntax of the sections for the VHS Inspect file used to put comments in
the file:
{COMMENT | == comment }
{PROCESS $process-name }
{PROGRAMFILE diskfile-name }
{LANGUAGE language }
$process-name
specifies the name of a process. The process name consists of a dollar sign ($)
followed by a letter and by zero to four alphanumeric characters with no embedded
blanks, for example $APPL.
{PROGRAMFILE diskfile-name }
diskfile-name specifies a NonStop Kernel operating system file name. A disk
file in the NonStop Kernel operating system is identified by a unique, symbolic file
name. A complete NonStop Kernel disk file name describes the location of a file
and has four parts:
\system-name
$volume-name
subvolume-name
file-name
For convenience, default values are provided for all parts of a complete file name:
[\system-name.] [$volume-name.] [subvolume-name.] file-name
\system-name
identifies a specific system within a network.
$volume-name
identifies a volume.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 13
VHS Inspect File
Using VHS
subvolume-name
identifies a set of files defined by the user.
file-name
identifies a particular file within the subvolume.
The syntax of system-name, volume-name, subvolume-name, and filename in VHS is identical to the syntax defined for these components for the
NonStop Kernel operating system.
{LANGUAGE language }
language specifies one of the following:
C
COBOL
FORTRAN
PASCAL
SCOBOL
TAL
Example of a VHS Inspect File
COMMENT This file contains all Inspect process info for ATM VHS
environment
PROCESS $ATM1
COMMENT Display general information when this Process is trapped into
INSPECT
FILES
TRACE
PROGRAMFILE $DISK.PROD.ATMPRG
COMMENT we must check the max^count variable when we have a problem
COMMENT with this program
TRACE;DISPLAY max^count
PROGRAMFILE $DISK.PROD.POSPRG
TRACE; FILES
LANGUAGE TAL
COMMENT For applications written in TAL
COMMENT the application.
TRACE
LANGUAGE COBOL
COMMENT For applications written in COBOL
SOURCE
SAVE Command in VHS Inspect File
The Save command in the VHS Inspect file is treated as a special case.
When the SAVE command is specified without any file name, Inspect saves the
savefile of the application (trapped into Inspect) under the default save file name
specified in the VHS startup file (VHS-INSPECT-SAVEFILE parameter).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 14
VHS Inspect File
Using VHS
Example for SAVE Command Without a File Name
PROCESS
COMMENT
COMMENT
ENV
COMMENT
SAVE
EXIT
$INS1
displays the current settings of the Inspect environment
and selectable parameters.
Invoke default save command
When the Save command is given with a file name, VHS appends an index to the save
file name specified. Inspect saves the savefile of the application trapped under this file
name. When the same application enters into trap again, the index appended to the
save file will be incremented by 1.
Command
File saved as
SAVE A
Annnn (A0000 to A9999)
SAVE ABCD
ABCDnnnn (ABCD0000 TO ABCD9999)
SAVE ABCDEFG
ABCDEFGn (ABCDEFG0 TO ABCDEFG9)
SAVE
ABCDEFGH
ABCDEFGH (No index is added)
SAVE ABC012
ABC012nn (Note that numbers in the file name
are treated just like other characters.)
The number of digits in the index will be <= 4.
VHS Inspect File Validation
Each time VHS loads the VHS Inspect file, a validation is performed. VHS validates the
keywords PROCESS, PROGRAMFILE, and LANGUAGE and what follows those
keywords on the same line. VHS does not validate the information between two
sections; in particular, Inspect commands are not validated. Also, if VHS rejects a
section keyword or name, all the following lines are also rejected until VHS finds
another valid keyword and section name. If a line has more than 132 characters, VHS
keeps only the first 132 characters and discards the rest of the line. For each error
found in the VHS Inspect file, an EMS event is generated.
VHS Inspect File Limitations
In the VHS Inspect file, you can have up to 100 sections and a maximum of 5000 bytes
loaded in memory. If the Inspect file contains more than 100 sections and/or more than
5000 bytes, VHS stops loading when one of these two limits is reached, and an EMS
event is generated specifying that the loading was stopped.
Modification of the VHS Inspect File
VHS loads the VHS Inspect file when it starts. The VHS Inspect file can also be
modified any time while VHS is running. When that happens, VHS reloads the file only
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 15
Understanding the VHS Log Files
Using VHS
when a new application traps into Inspect. At this point, VHS stops sending commands
to Inspect from the previous VHS Inspect file sections, doing this for all currently
existing Inspect openers and subsequently for all applications that are handled by
those Inspect openers at the time of the reload. For each application that was
previously in Inspect, VHS generates an EMS event (ZVHS-EVT-INSP-PROCESSINGSTOP) saying that the Inspect processing has been stopped, creates a saveabend file,
and stops the application. VHS then uses the new VHS Inspect file for all new
applications trapping into Inspect.
Understanding the VHS Log Files
VHS has both a primary log file set and a secondary log destination. The VHS primary
log file set provides an audit trail of the messages received by VHS. The maximum
number of the files in the primary log file set is controlled by the PRIMARY-LOGFILEPURGE parameter. You can specify the primary, secondary, and maximum extents of
the log files when you start VHS or alter these values via the VHSCI.
You can use a report generator, such as Enform, or a COBOL program to extract the
information from the primary log files.
PRIMARY-LOGFILE-PURGE Parameter
The PRIMARY-LOGFILE-PURGE parameter can be set ON (true) or OFF( false). This
parameter can be set when starting VHS, as part of the VHS startup file (VHSSTART).
If the parameter value is not set, the default is ON.
Setting the parameter to ON results in the primary log file set containing up to a
maximum of five files. VHS stores its messages in these five consecutively numbered
log files. For example, when the first file LOG0000 is full, VHS creates up to four more
log files named LOG0001 through LOG0004. When all five log files are full, VHS
purges the oldest file and creates the next file (Figure 3-1).
Purging of the log files can be avoided by setting this parameter to OFF. There will be
no restriction on the number of files in the primary log file set. When one log file is full,
the next consecutive log file is created. For example, when LOG0004 is full, LOG0005
is created. The older log files are not purged.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 16
Secondary Log Destination
Using VHS
Figure 3-1. VHS Log Files
Before LOG0004 is
full:
LOG0000
LOG0001
LOG0002
LOG0003
LOG0004
With PRIMARY-LOGFILE-PURGE parameter ON,
When LOG0004 is full, LOG0000 is purged and LOG0005 is created.
LOG0000
LOG0001
LOG0002
LOG0003
LOG0004
LOG0005
LOG0004
LOG0005
With PRIMARY-LOGFILE-PURGE parameter OFF,
When LOG0004 is full, LOG0005 is created.
LOG0000
LOG0001
LOG0002
LOG0003
VST031.vsd
Secondary Log Destination
You can also set up a secondary log destination. The secondary log destination can be
a disk file, collector, or terminal. Using the VHS conversational interface, you can
specify a secondary log destination for each major message type (display messages,
Inspect and Debug prompts, application prompts, or all message types).
Stopping VHS
Before stopping VHS, you should stop all applications that use VHS as their home
terminal. If you do not stop these applications first, they could abend.
1. Find out which applications use VHS as a home terminal by using the TACL
STATUS command:
4> STATUS *, TERM $vhs-process
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 17
Using VHS With a ViewPoint Filter
Using VHS
The system displays all the applications that use the specified VHS process as
home terminal. For example:
Process
$ZATM 0,82
$Z798 0,127
$Z801 0,145
$OMFN 0,151
Pri PFR %WT Userid
170
005 215,4
150
001 215,4
160
001 215,4
160
001 215,4
Program file
Hometerm
$SYSTEM.SYSTEM.ATM
VHS
$SYSTEM.SYSTEM.ATM
$VHS
$SYSTEM.SYSTEM.INVC
$VHS
$SYSTEM.SYSTEM.INVC
$VHS
2. Stop any applications that use VHS as a home terminal.
3. To ensure that no applications open a VHS process, use the LISTOPENS
command in VHSCI:
-> LISTOPENS
VHS W00201 No process currently open VHS server
Probable Cause
There is no process that actually opens the VHS server.
Recommended Action
This is a warning. No action is necessary.
4. If the LISTOPENS command shows that no processes are opening VHS, then you
can stop VHS by typing the following TACL command:
3> STOP $VHS
Caution. If any application has used the NonStop Kernel procedure MYTERM to get the home
terminal name, but has not yet opened the home terminal, the application might later fail. This
situation cannot be detected by VHS. One way to detect this condition is to do a STATUS *,
TERM $vhs-process at the TACL prompt.
Using VHS With a ViewPoint Filter
VHS sends all messages it receives to the EMS collector $0. You can highlight the
VHS messages so that critical or action-event messages can be easily identified on the
ViewPoint console.
If your application is not instrumented with EMS, you will need to analyze the
messages to determine keywords that ViewPoint should highlight. For example, many
applications use these keywords to indicate when operator intervention is needed:
•
•
•
•
Error
Abend
Abnormal
Unsuccessful
For a sample ViewPoint filter used to highlight application messages, see Appendix I,
ViewPoint Event Filter.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
3- 18
4
Using the VHS Browser
This section describes how to use the VHS Browser and contains the following
subsections:
•
•
•
•
•
•
•
•
•
•
•
Accessing the VHS Browser
Exiting the VHS Browser
VHS screen navigation
VHS screen format
Help screens
Log Browser screen
Prompt Browser screen
Prompt Detail screen
VHS Profile screen
Environment Detailed screen
Printing a screen
The following table summarizes the VHS screens:
VHS Screen
Purpose
Log Browser
View, select, and get detailed information about home terminal
messages sent to the VHS primary log file
Prompt Browser
View and reply to application prompts sent to the VHS process and
stored in the prompt file
Prompt Detail
Get detailed information and reply to an application prompt
VHS Profile
Get VHS configuration information
Environment Detailed
View detailed information on all existing environments
Accessing the VHS Browser
How you access the VHS Browser depends on whether the VHS Browser is installed
on your system in ViewPoint or as a stand-alone Pathway system.
VHS Installed in ViewPoint
If the VHS Browser is installed in ViewPoint, first start ViewPoint on your terminal. You
must have the ViewPoint Extras screen, included with VHS, installed. See Section 2,
Installing VHS for installation details.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -1
Using the VHS Browser
VHS Installed as a Stand-Alone Pathway System
Accessing VHS From the ViewPoint TACL Prompt
To access the VHS Log Browser screen, type VHSL or vhsl at the ViewPoint TACL
prompt and press the SF15 function key.
1> VHSL
or
1> vhsl
To access the VHS Prompt Browser screen, type VHSP or vhsp at the ViewPoint TACL
prompt and press the SF15 function key.
1> VHSP
or
1> vhsp
Accessing VHS Browser From any ViewPoint Screen
•
•
To access the VHS Log Browser screen, enter VHSL or vhsl in the ViewPoint
option line (line 24) and press the SF15 function key.
To access the VHS Prompt Browser screen, enter VHSP or vhsp in the ViewPoint
option line (line 24) and press the SF15 function key.
Accessing VHS Browser From the ViewPoint Extras Screen
To access VHS Browser from the ViewPoint Extras screen:
•
•
Press the SF15 function key to display the ViewPoint Extras screen.
Press the SF6 function key to access the VHS Log Browser screen or the SF7
function key to access the VHS Prompt Browser screen.
To access VHS Browser from a custom ViewPoint Extras screen:
•
•
•
Press the SF15 function key to display the custom ViewPoint Extras screen.
Check the menu to determine which function keys have been assigned to VHS
Browser.
Press the function key assigned to VHS Log Browser to display the Log Browser
screen or press the function key assigned to VHS Prompt Browser to display the
Prompt Browser screen.
VHS Installed as a Stand-Alone Pathway System
If the VHS Browser is installed as a stand-alone Pathway system, make sure the VHSL
and VHSP macros exist in your current subvolume or you are positioned in the
subvolume where VHS is installed.
You can access the VHS Browser from the TACL prompt:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -2
High PIN Support
Using the VHS Browser
•
To access the VHS Log Browser screen, enter this at the TACL prompt:
1> run vhsl
or
1> vhsl
•
To access the VHS Prompt Browser screen, enter this at the TACL prompt:
1> run vhsp
or
1> vhsp
High PIN Support
To run the VHS Browser with High PIN support:
1. Ensure that the #HIGHPIN built-in variable is set to ON at the TACL prompt.
2. Set the HIGHPIN attribute to ON in the file ZVHSDEFS in the browser subvolume.
3. Restart Pathway.
Exiting the VHS Browser
How you exit the VHS Browser depends on whether the VHS Browser is installed on
your system in ViewPoint or as a stand-alone Pathway system.
VHS Installed in ViewPoint
To exit the VHS Browser, use the Log Browser screen, the Prompt Browser screen, or
the Environment Detailed screen. You must have installed the ViewPoint Extras screen
included with VHS. See Section 2, Installing VHS for installation details.
How you exit the VHS Browser depends on the type of ViewPoint Extras screen.
Exiting VHS Browser and Returning to the ViewPoint
Extras Screen
To exit the VHS Browser and return to the ViewPoint Extras screen, do the following:
•
•
Press the F16 function key until you return to the Log Browser screen, the Prompt
Browser screen, or the Environment Detailed screen.
Press the SF16 function key to return to the ViewPoint Extras screen.
Exiting VHS Browser From a Custom ViewPoint Extras
Screen
To exit VHS from a custom ViewPoint Extras screen, do the following:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -3
VHS Installed as a Stand-Alone Pathway System
Using the VHS Browser
•
•
•
Press the F16 function key until you return to the Log Browser screen, the Prompt
Browser screen, or the Environment Detailed screen.
Press the SF16 function key to display the custom ViewPoint Extras screen.
Check the menu to determine your exit options.
Exiting VHS Browser and Returning to Other
ViewPoint Functions
To exit the VHS Browser and return to other ViewPoint functions, do the following:
•
•
Press the F16 function key until you return to the Log Browser screen or the
Prompt Browser screen, or the Environment Detailed screen.
Type the name of the desired ViewPoint screen or the screen function key in the
screen option line (line 24) and press the SF16 function key to display the desired
screen. For example, type one of the following:
ViewPoint Screen
Action
STATUS | status | F2 | f2
Displays the Network Status Summary screen
PRI-EVENT | pri-event | F3 | f3
Displays the Primary Events screen
LAST-EVENT | last-event | F4 | f4
Displays the Last Event screen
ALT-EVENT | alt-event | SF3 | sf3
Displays the Alternate Events screen
PROFILE | profile | F14 | f14
Displays the Profile screen
OMF | omf |SF4 | sf4
Displays the General Status screen of OMF if OMF
is installed and SF4 is its associated function key
on the extras screen
OMF | omf |SF5 | sf5
Displays the Network Status screen of OMF if OMF
is installed using the Network option and SF5 is its
associated function key on the Extras screen
Note. For these exit options to work properly, you must have installed the ViewPoint
Extras screen that is included with VHS. You must type the ViewPoint screen name or
function key name in all upper or all lower case, as displayed above. Do not press the
function key.
VHS Installed as a Stand-Alone Pathway System
To return to the TACL prompt from the VHS Browser, do the following:
•
•
Press the F16 function key until you return to the Log Browser screen, the Prompt
Browser screen, or the Environment Detailed screen.
Press the SF16 function key to display the TACL prompt.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -4
VHS Screen Navigation
Using the VHS Browser
VHS Screen Navigation
From the VHS Log Browser screen or the VHS Prompt Browser screen, you can
navigate to the other VHS Browser screens. Figure 4-1 shows the simplified guidelines
for moving from one screen to another. You can access the Help screen from any of
the other four screens by pressing F15.
Figure 4-1. Screen Navigation Map
F3
SF6
Log Browser
F10
Env Detail
F10
F4
F10
F3
Console Facility
F14
Return to
last screen ( F16)
F14
SF7
Prompt Browser
F11
F14
VHS Profile
Exit VHS ( SF16)
F4
Prompt
Detail
VST041.vsd
VHS Screen Format
The VHS screens follow the screen format used in many other Pathway block-mode
applications. In block mode, information is transmitted as complete messages or
blocks of data. Block-mode operation is identified by the word BLOCK in the last
screen information field located on line 25.
Figure 4-2 provides an example of the general format of the screens; Table 4-1
explains each major section of the screen.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -5
Help Screens
Using the VHS Browser
Figure 4-2. VHS Screen Format
Screen Header
Search Criteria
Current Page of Screen Data
Advice Line
Function-Key Assignment
Option Line
Line 25
BLOCK
VST042.vsd
Table 4-1. VHS Field Descriptions
Field
Description
Screen Header
Indicates the current screen, the last screen update time,
and the current position in the file
Search Criteria
Indicates search criteria for the current screen, such as
Environment, Date, Time, Process Name, and Search Text
Current Page of Screen
Data
Displays the current page of screen data
Advice Line
Provides error notices or advice messages
Function Key Assignments
Indicates the function keys available for the current screen
Option Line
Provides an input field for passing a destination name
Line 25
In block mode, it displays a field at the end of the line
indicating block mode (BLOCK) or keyboard locked (KBD
LOCKED). If you are running ViewPoint, line 25 displays the
count of outstanding events and a portion of the text of the
most recently reported outstanding event
Help Screens
Online help is available for each VHS screen. The help text provides general
information about the current screen, including its purpose, fields, and function keys.
To obtain help for the current screen, do the following:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -6
Paging Through Help
Using the VHS Browser
•
•
Press F15.
Press any function key to exit the Help screen.
Paging Through Help
You can page through Help for a specific screen by using the Prev Page and Next
Page keys. To return to the beginning of the help, press Shift-Prev Page. To go to the
end of the help, press Shift-Next Page.
Figure 4-3 shows the first of five pages of the help text for the Log Browser screen.
Figure 4-3. Log Browser Help Screen
1998-02-13 12:28
LOG BROWSER HELP SCREEN
Page
1
MORE
Function key descriptions
PAGING
Use NEXT PAGE and PREV PAGE; SHIFT/PREV PAGE = first
page and SHIFT/NEXT PAGE = last page.
Change Search F2 Accepts the search criteria specified by Environment,
Criteria
After (date, time), Process and Search Text, and
refreshes the screen with the messages that match these
criteria.
Prompt Browser F4 Move to the Prompt Browser screen.
Refresh Count
F5 Refreshes the number of pending prompts.
Print
F9 Prints the information displayed on the screen. You
can use the default printer specified in the Pathway
configuration for your terminal or enter a
destination name on the option line.
Env Detail
F10 Move to the Environment Detailed screen.
VHS Profile
F14 Move to the VHS Browser Profile screen.
Help
F15 Move to the Help text for the current screen.
Exit
SF16 Exits VHS Browser.
*** Press Next Page for more information about the screen. ***
*** Press any function key to return. ***
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -7
Log Browser Screen
Using the VHS Browser
Log Browser Screen
You use the Log Browser screen to search and display messages in the VHS log file. If
you do not enter any search criteria, the Log Browser screen shows the last page of
messages in the log file.
Changing Search Criteria
If you enter search criteria (environment, date and time in the After field, for example),
the Log Browser screen shows the first page of messages that meet the search
criteria.
If you enter search text only as search criteria, the Log Browser screen shows the last
page of messages that meet the search criteria.
Getting Environment Detailed Information
To get more information about the current environment or other existing environments,
press F10 to go to the Environment Detailed screen. From that screen, you can browse
various environment information and also change the current environment.
Paging Through the Log File
You can page through the messages by using Prev Page and Next Page. To return to
the beginning of the messages, press Shift-Prev Page. To go to the end of the
messages, press Shift-Next Page. Figure 4-4, Figure 4-5, Figure 4-6 and Figure 4-7
show samples of Log Browser screens with different SHOW-DATE and SHOWOBJECT-NAME parameters. For more information regarding the SHOW-DATE and
SHOW-OBJECT-NAME parameters, see Date and Object-Name Display on
page 4-13.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -8
Paging Through the Log File
Using the VHS Browser
Figure 4-4. Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to
0
1998-02-12 13:30
VHS LOG BROWSER FOR SYSTEM \IDC5
Position: END
Environment: BVHS
After:
:
:
Process:
Search Text: *
Prompts: 0001
First message date: 1998-02-12
Last message date: 1998-02-12
12:11:12 1,143
File Utility Program - T6553D40 - (01APR97) System \IDC5
12:11:13 1,143
Copyright Tandem Computers Incorporated 1981, 1983, 1985-1997
12:11:14 1,143
Prompt: "-"
12:11:32 1,143
Prompt: "-" Reply: "help"
12:11:32 1,143
ALLOCATE ALLOW ALTER BUILDKEYRECORDS CHECKSUM
12:11:32 1,143
COPY CONFIGURE CREATE DEALLOCATE DISPLAYBITS
12:11:32 1,143
DUP EXIT FC FILENAMES FILES
12:11:32 1,143
GIVE HELP HISTORY INFO LICENSE
12:11:32 1,143
LISTLOCKS LISTOPENS LOAD LOADALTFILE OBEY
12:11:32 1,143
PURGE PURGEDATA RELOAD RELOCATE REMAP
12:11:32 1,143
RENAME REPORTWIDTH RESET RESTART REVOKE
12:11:33 1,143
SECURE SET SHOW STATUS SUBVOLS
12:11:33 1,143
SUSPEND SYSTEM VOLS VOLUME !
12:11:33 1,143
? FILELIST FILENAME FILESET NEWS
12:11:33 1,143
QUALEXPR SUBVOLSET VOLSET
12:11:33 1,143
Prompt: "-"
Screen updated.
F2=Change Search Criteria
F4=Prompt Browser
F5=Refresh Count
F9=Print
F10=Env Detail
F14=VHS Profile
F15=Help
SF16=Exit
Figure 4-5. Log Browser Screen: SHOW-DATE Set to 1 and SHOW-OBJECTNAME Set to 0
1998-02-12 15:56
VHS LOG BROWSER FOR SYSTEM \IDC5
Position: MORE
Environment: BVHS
After:
:
:
Process:
Search Text: *
Prompts: 0001
First message date: 1998-02-12
Last message date: 1998-02-12
02-12 12:11:12 1,143
File Utility Program - T6553D40 - (01APR97) System
\IDC5
02-12 12:11:13 1,143 Copyright Tandem Computers Incorporated 1981, 1983,
1985-1997
02-12 12:11:14 1,143
Prompt: "-"
02-12 12:11:32 1,143
Prompt: "-" Reply: "help"
02-12 12:11:32 1,143
ALLOCATE ALLOW ALTER BUILDKEYRECORDS CHECKSUM
02-12 12:11:32 1,143
COPY CONFIGURE CREATE DEALLOCATE DISPLAYBITS
02-12 12:11:32 1,143
DUP EXIT FC FILENAMES FILES
02-12 12:11:32 1,143
GIVE HELP HISTORY INFO LICENSE
02-12 12:11:32 1,143
LISTLOCKS LISTOPENS LOAD LOADALTFILE OBEY
02-12 12:11:32 1,143
PURGE PURGEDATA RELOAD RELOCATE REMAP
02-12 12:11:32 1,143
RENAME REPORTWIDTH RESET RESTART REVOKE
02-12 12:11:33 1,143
SECURE SET SHOW STATUS SUBVOLS
02-12 12:11:33 1,143
SUSPEND SYSTEM VOLS VOLUME !
02-12 12:11:33 1,143
? FILELIST FILENAME FILESET NEWS
F2=Change Search Criteria F4=Prompt Browser
F10=Env Detail
F14=VHS Profile
F5=Refresh Count
F15=Help
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4 -9
F9=Print
SF16=Exit
Paging Through the Log File
Using the VHS Browser
Figure 4-6. Log Browser Screen: SHOW-DATE Set to 0 and SHOW-OBJECTNAME Set to 1
1998-02-12 16:02
VHS LOG BROWSER FOR SYSTEM \IDC5
Position: MORE
Environment: BVHS
After:
:
:
Process:
Search Text: *
Prompts: 0001
First message date: 1998-02-12
Last message date: 1998-02-12
12:11:12 1,143
\IDC5.$SYSTEM.SYS00.FUP
File Utility Program - T6553D40 - (01APR97) System \IDC5
12:11:13 1,143
\IDC5.$SYSTEM.SYS00.FUP
Copyright Tandem Computers Incorporated 1981, 1983, 1985-1997
12:11:14 1,143
\IDC5.$SYSTEM.SYS00.FUP
Prompt: "-"
12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
Prompt: "-" Reply: "help"
12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
ALLOCATE ALLOW ALTER BUILDKEYRECORDS CHECKSUM
12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
COPY CONFIGURE CREATE DEALLOCATE DISPLAYBITS
12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
DUP EXIT FC FILENAMES FILES
12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
GIVE HELP HISTORY INFO LICENSE
F2=Change Search Criteria F4=Prompt Browser
F10=Env Detail
F14=VHS Profile
F5=Refresh Count
F15=Help
F9=Print
SF16=Exit
Figure 4-7. Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to
1
1998-02-12 16:00
VHS LOG BROWSER FOR SYSTEM \IDC5
Position: MORE
Environment: BVHS
After:
:
:
Process:
Search Text: *
Prompts: 0001
First message date: 1998-02-12
Last message date: 1998-02-12
02-12 12:11:12 1,143
\IDC5.$SYSTEM.SYS00.FUP
File Utility Program - T6553D40 - (01APR97) System \IDC5
02-12 12:11:13 1,143
\IDC5.$SYSTEM.SYS00.FUP
Copyright Tandem Computers Incorporated 1981, 1983, 1985-1997
02-12 12:11:14 1,143
\IDC5.$SYSTEM.SYS00.FUP
Prompt: "-"
02-12 12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
Prompt: "-" Reply: "help"
02-12 12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
ALLOCATE ALLOW ALTER BUILDKEYRECORDS CHECKSUM
02-12 12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
COPY CONFIGURE CREATE DEALLOCATE DISPLAYBITS
02-12 12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
DUP EXIT FC FILENAMES FILES
02-12 12:11:32 1,143
\IDC5.$SYSTEM.SYS00.FUP
GIVE HELP HISTORY INFO LICENSE
F2=Change Search Criteria F4=Prompt Browser
F10=Env Detail
F14=VHS Profile
F5=Refresh Count
F15=Help
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 10
F9=Print
SF16=Exit
Log Browser Screen Field Descriptions
Using the VHS Browser
Log Browser Screen Field Descriptions
Table 4-2 lists the field descriptions for the Log Browser screen.
Table 4-2. Log Browser Screen Field Descriptions
Field/Line
Name
Header
Search Criteria
Description
Specifies current date and time, the name of the
screen, the system name, and the position of the
log file (MORE or END)
Environment
Specifies the current VHS environment
After
Specifies that VHS display the messages after the
date and time entered
Process
Specifies that VHS display the messages from the
process entered
Search Text
Specifies that VHS display only messages that
match the search text. All characters are
accepted. An asterisk (*) can specify many or no
characters. A question mark (?) can specify one
character and all other characters must be a
perfect match. For example: C??pa? C* would find
“Compaq Computers”
Prompts
Shows the number of outstanding prompts in
current environment. Updated when F5 key is
pressed.
Last Message Date
Shows the date of the last message listed on the
screen
Line 4
First Message Date
Shows the date of the first message listed on the
screen
Data
Date
[Optional] Shows the time of the message
Time
Shows the time of the message
Process name or PID
Shows the process name if the process is a
named process or the process identification (CPU,
PIN) of the process that produced the message
Object name
[Optional] Shows the object name of the process
that generated the message
Text
Shows the display message from the process
Line 3
Note. The fields Search Text and Last Message Data are available with only the D21 version
and newer.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 11
Log Browser Screen Function Keys
Using the VHS Browser
Log Browser Screen Function Keys
Table 4-3 describes the specific function keys used within the Log Browser screen.
Table 4-3. Log Browser Screen Function Keys
Key
Function
Description
F2
Change Search
Criteria
Accepts the search criteria specified by Environment,
After (date, time), Process, and Search Text and
refreshes the screen with the messages that match these
criteria
F4
Prompt Browser
Goes to the Prompt Browser screen
F5
Refresh Count
Refresh the pending prompt count for current
environment
F9
Print
Prints the current screen. You can use the default printer
specified in the Pathway configuration for your terminal or
enter a destination name on the option line
F10
Env Detail
Goes to the Environment Detailed screen
F14
VHS Profile
Goes to the VHS Profile screen
F15
Help
Goes to the help text for the current screen
SF16
Exit
Exits VHS
Note. The F10 - Env Detail function key is available with only the D21 version and newer.
Search Text Field
The search text field specifies that VHS display only messages that match the search
text. All characters are accepted. An asterisk (*) can specify many or no characters. A
question mark (?) can specify one character and all other characters must be a perfect
match. For each template entered, VHS adds an asterisk (*) at the beginning of the
template if the template does not begin with one and adds an asterisk (*) at the end of
the template if the template does not end with one.
For example:
Search Text: C??pa? C*
This search text is replaced by *C??pa? C*
VHS will find “Compaq Computers”.
The following list shows a few of the possible search text templates:
?????? Computers
replaced by *?????? Computers*
*
stays the same
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 12
Date and Object-Name Display
Using the VHS Browser
Prompt: * Reply: *
replaced by *Prompt: * Reply*
?acl *?ki?*je
replaced by *?acl *?ki?*je*
?23* Montreal 19?
replaced by *?23* Montreal 19?*
Date and Object-Name Display
The display of the date and object-name fields for each message can be controlled
using the following parameters:
Parameter
Value
SHOW-DATE
Description
This parameter determines whether to display
the date in the log screen.
0
The date is not displayed. This is the default
value.
1
The date is displayed.
SHOW-OBJECTNAME
This parameter determines whether to display
the object name of the process that generated
a log message is to be displayed.
0
The object name is not displayed. This is the
default value.
1
The object name is not displayed.
Note. The above parameters are in the file ZVHSDEFS in the browser subvolume. To change
the parameters, edit the file and restart Pathway.
Prompt Browser Screen
The Prompt Browser screen displays the outstanding prompts for a specific VHS
environment.
Changing Search Criteria
You can change the environment by typing over the current environment and pressing
F2 (Update Screen).
Getting Environment Detailed Information
To get more information about the current environment or other existing environments,
press F10 to go to the Environment Detailed screen. From that screen, you can browse
various environment information and also change the current environment.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 13
Going to a Specific Page
Using the VHS Browser
Going to a Specific Page
To go directly to a specific page, you can enter the page number (up to 750) in the
option line and press F2.
If there are more than five prompts on the Prompt Browser screen, multiple pages are
available. When multiple pages of information exist, MORE appears in the upper right
corner of that screen. The following table summarizes the VHS Browser key functions
and their corresponding actions for paging through a multiple-page screen display.
Desired Action
Required Keys
Function
Next Page
NEXT PAGE, pg dn, or page down
Displays the next page
Previous Page
PREV PAGE, pg up, or page up
Displays the previous page
Last Page
Shift and NEXT PAGE, pg dn, or page
down
Displays the last page of
information
First Page
Shift and PREV PAGE, pg up, or page up
Displays the first page of
information
Getting Detailed Prompt Information
To get context information about the prompt, first mark the prompt that you want to get
information about. You mark the prompt by placing a character in the first column by
the date of the prompt. Next press F11 to go to the Prompt Detail screen.
Replying to a Prompt
You can send a reply to the prompt from this screen or from the Prompt Detail screen.
To reply to a prompt, do the following:
1. Press F8 to suspend the automatic refresh of the screen.
2. Mark the prompt you want to answer. To mark a prompt, enter a character in the
first column next to the date of the prompt. If the screen has one prompt only, you
do not have to mark the prompt.
3. Go to the Reply field by pressing Return or Tab or using the cursor arrow keys.
4. Enter the reply text in the Reply field.
5. Press F6 to send the reply.
6. Press SF8 to resume the automatic refresh of the screen.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 14
Prompt Browser Screen Field Descriptions
Using the VHS Browser
Figure 4-8 shows a sample Prompt Browser screen.
Figure 4-8. Prompt Browser Screen
1998-02-13 10:23
VHS PROMPT BROWSER FOR SYSTEM \IDC5
Environment: BVHS
1998-02-13 10:23:07
Prompt: "-"
1998-02-13 10:23:11
Prompt: "#"
Number of outstanding prompts:
1,116
\IDC5.$SYSTEM.SYS00.FUP
1,98
Page
1
END
2
\IDC5.$SYSTEM.SYS00.PUP
Reply:
F2=Update Screen
F10=Env Detail
F3=Log Browser
F6=Send reply F8=Freeze SF8=Thaw F9=Print
F11= Prompt Detail F14=VHS Profile
F15=Help
SF16=Exit
Prompt Browser Screen Field Descriptions
Table 4-4 describes the fields on the Prompt Browser screen.
Table 4-4. Prompt Browser Screen Field Descriptions
Field/Line
Name
Header
Description
Specifies current date and time, the name of the
screen, the system name and the position of the
prompt file (page number and MORE or END)
Search Criteria
Environment
Number of
Outstanding Prompts
Data
Specifies the VHS environment
Specifies the number of prompts that need to be
answered
Date and Time
Shows the date and time of the prompt
Process
Name or PID
Shows the name (if the process has one) or the
PID (CPU,PIN) of the process that produced the
message
Object File
Name
Shows the object file name of the process that
prompted VHS
Text
Shows the prompt message from the process
Reply
Provides an input field for you to enter the
information needed by the prompt
Line 24 (option line)
Allows you to go directly to a specific page. Enter
the number of the page (up to 750) in the option
line and press F2
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 15
Prompt Browser Screen Function Keys
Using the VHS Browser
Prompt Browser Screen Function Keys
Table 4-5 describes the specific function keys used with the Prompt Browser screen.
Table 4-5. Prompt Browser Screen Function Keys
Key
Function
Description
F2
Update
Screen
Accepts the environment name and the page number entered in
the option line (if one is entered) and refreshes the screen by
rereading the prompt file
F3
Log Browser
Goes to the Log Browser screen
F6
Send Reply
Accepts the prompt text specified in the Reply field and sends it
back to the application
F8
Freeze
Suspends the automatic refresh of the screen
SF8
Thaw
Resumes the automatic refresh of the screen
F9
Print
Prints the information displayed on the current screen. You can
use the default printer specified in the Pathway configuration for
your terminal or enter a destination name on the option line
F10
Env Detail
Goes to the Environment Detailed screen
F11
Prompt Detail
Goes to the VHS Prompt Detail screen
F14
VHS Profile
Goes to the VHS Profile screen
F15
Help
Goes to the Help screen for the current screen
SF16
Exit
Exits VHS
Note. The F10 - Env Detail function key is available with only the D21 version and newer.
Prompt Detail Screen
The Prompt Detail screen provides information about application messages written to
the log before the current prompt was written to VHS. The screen displays the context
of a prompt so you have the information you need before you reply to the prompt.
Replying to a Prompt
To reply to a prompt, do the following:
1. Go to the Reply field.
2. Enter the reply in the Reply field.
3. Press F6 to send the reply.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 16
Prompt Detail Screen Field Descriptions
Using the VHS Browser
Figure 4-9 and Figure 4-10 show a sample of a Prompt Detail Screen with different
SHOW-DATE params.
Figure 4-9. Prompt Detail Screen: SHOW-DATE Set to 0
1998-02-13 11:35
VHS PROMPT DETAIL FOR SYSTEM \IDC5
Env: BVHS
Process: 1,116
Program: \IDC5.$SYSTEM.SYS00.FUP
First message date: 1998-02-13
Last message date: 1998-02-13
10:23:06 1,116
File Utility Program - T6553D40 - (01APR97) System \IDC5
10:23:06 1,116
Copyright Tandem Computers Incorporated 1981, 1983, 1985-1997
10:23:07 1,116
Prompt: "-"
11:35:24 1,116
Prompt: "-" Reply: "help"
11:35:25 1,116
ALLOCATE ALLOW ALTER BUILDKEYRECORDS CHECKSUM
11:35:25 1,116
COPY CONFIGURE CREATE DEALLOCATE DISPLAYBITS
11:35:25 1,116
DUP EXIT FC FILENAMES FILES
11:35:25 1,116
GIVE HELP HISTORY INFO LICENSE
11:35:25 1,116
LISTLOCKS LISTOPENS LOAD LOADALTFILE OBEY
11:35:25 1,116
PURGE PURGEDATA RELOAD RELOCATE REMAP
11:35:25 1,116
RENAME REPORTWIDTH RESET RESTART REVOKE
11:35:26 1,116
SECURE SET SHOW STATUS SUBVOLS
11:35:26 1,116
SUSPEND SYSTEM VOLS VOLUME !
11:35:26 1,116
? FILELIST FILENAME FILESET NEWS
11:35:26 1,116
QUALEXPR SUBVOLSET VOLSET
11:35:26 1,116
Prompt: "-"
Reply:
F6=Send reply
F9=Print
F11=Next prompt
F15=Help
F16=Return
Figure 4-10. Prompt Detail Screen: SHOW-DATE Set to1
1998-02-13 11:39
VHS PROMPT DETAIL FOR SYSTEM \IDC5
Env: BVHS
Process: 1,116
Program: \IDC5.$SYSTEM.SYS00.FUP
First message date: 1998-02-13
Last message date: 1998-02-13
02-13 10:23:06 1,116
Copyright Tandem Computers Incorporated 1981, 1983,
1985-1997
02-13 10:23:07 1,116
Prompt: "-"
02-13 11:35:24 1,116
Prompt: "-" Reply: "help"
02-13 11:35:25 1,116
ALLOCATE ALLOW ALTER BUILDKEYRECORDS CHECKSUM
02-13 11:35:25 1,116
COPY CONFIGURE CREATE DEALLOCATE DISPLAYBITS
02-13 11:35:25 1,116
DUP EXIT FC FILENAMES FILES
02-13 11:35:25 1,116
GIVE HELP HISTORY INFO LICENSE
02-13 11:35:25 1,116
LISTLOCKS LISTOPENS LOAD LOADALTFILE OBEY
02-13 11:35:25 1,116
PURGE PURGEDATA RELOAD RELOCATE REMAP
02-13 11:35:25 1,116
RENAME REPORTWIDTH RESET RESTART REVOKE
02-13 11:35:26 1,116
SECURE SET SHOW STATUS SUBVOLS
02-13 11:35:26 1,116
SUSPEND SYSTEM VOLS VOLUME !
02-13 11:35:26 1,116
? FILELIST FILENAME FILESET NEWS
02-13 11:35:26 1,116
QUALEXPR SUBVOLSET VOLSET
02-13 11:35:26 1,116
Prompt: "-"
Reply:
F6=Send reply
F9=Print
F11=Next prompt
F15=Help
Prompt Detail Screen Field Descriptions
Table 4-6 describes the fields on the Prompt Detail screen.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 17
F16=Return
Prompt Detail Function Key Descriptions
Using the VHS Browser
Table 4-6. Prompt Detail Screen Field Descriptions
Field/Line
Name
Description
Header
Specifies current date and time, the name of the screen,
and the system name
Information
Line 4
Data
Env
Specifies the VHS environment
Process
Specifies that VHS display the messages from the
process entered
Program
Shows the object file name of the process that
prompted VHS
First Message Date
Shows the date of the first message listed on the screen
Last Message Date
Shows the date of the last message listed on the screen
Date
[Optional] Shows the date of the message
Time
Shows the time of the message
Text
Shows the prompt message from the process
Reply
Provides an input field so that you can enter the
information needed by the prompt
Note. The field Last Message Data is available with only the D21 version and newer.
Prompt Detail Function Key Descriptions
Table 4-7 describes the specific function keys used within the Prompt Detail screen.
Table 4-7. Prompt Detail Screen Function Keys
Key
Function
Description
F6
Send Reply
Accepts the text specified in the reply field and sends it to the
application
F9
Print
Prints the information displayed on the current screen. You can use
the default printer specified in the Pathway configuration for your
terminal (the default is $s.#zvhs) or enter a destination name on the
option line (line 24)
F11
Next
Prompt
If you marked more than one prompt on the Prompt Browser screen,
VHS displays the next prompt marked
F15
Help
Goes to the Help screen for the current screen
F16
Return
Returns to the Prompt screen
VHS Profile Screen
The VHS Profile screen provides profile information about VHS. Use the screen
information to modify VHS profile data. From the VHS Profile screen you can view the
following information:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 18
VHS Profile Screen
Using the VHS Browser
•
•
•
•
Server Config Filename.
Existing environment (if you are running a previous D21 version) and current
environment. In the D21 version and newer, a new screen, the Environment
Detailed screen, provides detailed information on all existing environments.
Information about the first and last log.
Screens Automatic Update (screen automatic update delay).
Figure 4-11 shows the format of the VHS Profile screen for all previous D21 versions.
Figure 4-11. VHS Profile Screen
1995-07-11 13:59
VHS PROFILE SCREEN
System Name: \MTL
Server Class Name: ZVHS-SERVER-V1
Under Pathmon: $ZVHD
Server Version: T9517D20^01JUN93^VHSBSVR
Server Config Filename: $CTTM.ZVHSVPT.VHSBCONF
Existing Environments: GL1
DEV2
Current Environment:
First Log Filename:
First Message Timestamp:
Last Log Filename:
Last Message Timestamp:
POS
PREPROD
ATM
PROD
DEV1
DEV1
$CTTMD.VDEV.DEV0148
1995-06-05 12:44:10
$CTTMD.VDEV.DEV0152
1992-07-10 13:57:48
Screens Automatic Update:
1 minutes
( Must be between 1 and 480 -> 8 hours )
F9=Print
F15=Help
F14=Change Profile
F16=Return
SF14=Recover
Figure 4-12 shows the format of the VHS Profile screen for D21 and newer versions.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 19
VHS Profile Screen
Using the VHS Browser
Figure 4-12. VHS Profile Screen
1995-07-11 14:00
VHS PROFILE SCREEN
System Name:
Server Class Name:
Under Pathmon:
Server Version:
Server Config Filename:
Current Environment:
First Log Filename:
First Message Timestamp:
Last Log Filename:
Last Message Timestamp:
\POLLUX
ZVHS-SERVER-V1
$ZVHS
T9517D21_21JUL95_VHSBSVR
$VHS.VHSD21.VHSBCONF
PROD
$VHS.VHSD21.LOG0012
1995-07-09 12:31:19
$VHS.VHSD21.LOG0016
1995-07-11 13:59:45
Screens Automatic Update:
1 minutes
( Must be between 1 and 480 -> 8 hours )
F9=Print
SF14=Recover
F10=Environment Detail
F15=Help
F14=Change Profile
F16=Return
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 20
Switching Systems
Using the VHS Browser
From the VHS Profile screen, you can do the following:
•
•
•
•
•
Switch systems.
Switch VHS servers.
Switch PATHMONs.
Switch environments.
Change the screens automatic update delay.
Switching Systems
The System Name field shows which system is currently in use. To switch to a new
system, do the following:
•
•
Enter the desired system name in the System Name field.
Press F14 to update the VHS Profile screen.
Switching VHS Browser Servers
The Server Class Name field displays the current VHS Browser server. To switch to
another server, do the following:
•
•
Enter the desired VHS Browser server class name in the Server Class Name field.
Press F14 to update the VHS Profile screen.
Switching PATHMONs
The Under Pathmon field displays the current PATHMON. To switch to another
PATHMON, do the following:
•
•
Enter the desired PATHMON in the Under Pathmon field.
Press F14 to update the VHS Profile screen.
Switching Environments
The Current Environment field shows which environment is currently in use.
D21 and Newer Versions
To switch to another environment, do the following:
•
•
Enter the name of another existing environment in the Current Environment field.
Press F14 to update the VHS Profile screen.
or
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 21
Changing the Screens Automatic Update
Using the VHS Browser
•
•
•
Go to the Environment Detailed screen by pressing F10. This screen displays all
existing environments.
Select one environment by positioning the cursor in the field preceding the
environment name or typing any non-blank character in that field. Press F11 to see
the environment-related information and/or F12 to make the selected environment
the current one.
Press F14 to go back to the VHS Profile screen.
Previous D21 Versions
The Existing Environments field shows which environments are available. To switch to
another environment, do the following:
•
•
Enter the name of another existing environment in the Current Environment field.
Press F14 to update the VHS Profile screen.
Changing the Screens Automatic Update
The Screens Automatic Update field displays the current delay, in minutes, used for the
screens (Prompt Browser, Log Browser, and Environment Detailed) automatic update.
To change the update delay value, do the following:
•
•
Enter the desired delay value in the Screens Automatic Update field.
Press F14 to update the VHS Profile screen.
VHS Profile Screen Field Descriptions
Table 4-8 lists the field descriptions for the VHS Profile screen.
Table 4-8. VHS Profile Screen Field Descriptions (page 1 of 2)
Field
Name
Description
1
System Name
Current system name on which VHS is running
2
Server Class Name
VHS Browser server class name defined in the
Pathway configuration
3
Under Pathmon
PATHMON process name of the environment
4
Server Version
VHS product number and date
5
Server Config Filename
Name of the file that contains object configurations
6
Existing Environments
Existing environments on this system (up to eight).
This field is displayed only for previous D21 versions
7
Current Environment
Current VHS environment
8
First Log Filename
File name of the first VHS primary log file
9
First Message Timestamp
Timestamp of the first VHS primary log file
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 22
VHS Profile Screen Function Keys
Using the VHS Browser
Table 4-8. VHS Profile Screen Field Descriptions (page 2 of 2)
Field
Name
Description
10
Last Log Filename
File name of the last VHS primary log file
11
Last Message Timestamp
Timestamp of the last VHS primary log file
12
Prompt Screen Automatic
Update
Time interval in minutes after which the Prompt
Browser, Log Browser, and Environment Detailed
screens are automatically updated. This timer restarts
after each function key operation
Note. The timestamps are in local civil time.
VHS Profile Screen Function Keys
Table 4-9 describes the specific function keys used within the VHS Profile screen.
Table 4-9. VHS Profile Screen Function Keys
Key
Function
Description
F9
Print
Prints the information displayed on the current screen. You can
use the default printer specified in the Pathway configuration for
your terminal or enter a destination name on the option line
F10
Env Detail
Goes to the Environment Detailed screen (only for D21 and more
recent versions)
F14
Change Profile
Updates profile with newly entered data
SF14
Recover
Recovers the screen to its last known state
F15
Help
Gets the Help screen for this screen
F16
Return
Returns to the last screen
Environment Detailed Screen
The Environment Detailed screen provides detailed information on selected
environments and lists all existing environments. This screen is available from only
D21 and newer versions. The detailed information on selected environments is:
•
•
•
•
•
•
•
The first log file name.
The first message timestamp in the first log file.
The last log file name.
The last message timestamp in the last log file.
The current number of log files.
The prompt file name.
The current number of outstanding prompts in the prompt file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 23
Getting Environment Detailed Information
Using the VHS Browser
•
The lists of processes currently opening the prompt file. This list should only
contain the name of VHS processes.
Figure 4-13 shows the format of the Environment Detailed screen.
Figure 4-13. Environment Detailed Screen
1995-07-11 14:07
VHS ENVIRONMENT DETAILED FOR SYSTEM \POLLUX
Page
1 MORE
Existing Environments:
DEV
DEVATM
DEVPOS
DEV1
DEVVHS
DEVPROD
PROD
PRODATM
PRODPOS
PROJECT1
NEWPROD
NEWDEV
VHSLOG
VHSG
VHSSNAX
VHSBASE
BASE
VHSOMF
VHSEMS
VHSINSP
VHSDEB
VHSEXPAND CTTM
MPPG
OPS
TRMO
COBOL
PREPROD
----------------------- Detailed Environment Information ---------------------Selected Environment: PROD
First Log File: $VHS.VHSD21.LOG0012
First Message Timestamp: 1995-07-09 12:31:19
Last Log File: $VHS.VHSD21.LOG0016
Last Message Timestamp: 1995-07-11 14:06:45
Number of Log Files: 5
Prompt File: $VHS.VHSD21.PROMPT
Number of Outstanding Prompts:
1
------------------------------ Opener Processes ------------------------------\POLLUX.$VHSBB \POLLUX.$VHS21 \POLLUX.$VHS
F2=Update Screen F3=Log Browser
F11=Detail Env
F12=Set Current Env
F4=Prompt Browser F5=Switch
F9=Print
F14=VHS Profile
F15=Help
SF16=Exit
Getting Environment Detailed Information
To get more information about an environment, select one environment by positioning
the cursor in the field preceding the environment name or typing any non-blank
character in that field and press F11 to see the environment-related information.
Setting the Current Environment
To make an environment the current one:
•
If the Selected Environment is the one you want as the current environment, press
F12.
or
•
Select one environment by positioning the cursor in the field preceding the
environment name or typing any non-blank character in that field and press F12 to
make the current environment the selected one.
Paging Through the Existing Environments
You can page through the existing environments by using Prev Page and Next Page.
To return to the beginning of the list, press Shift-Prev Page. To go to the end of the list,
press Shift-Next Page.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 24
Environment Detailed Screen Field Descriptions
Using the VHS Browser
Environment Detailed Screen Field Descriptions
Table 4-10 lists the field descriptions for the Environment Detailed screen.
Table 4-10. Environment Detailed Screen Field Descriptions
Field
Name
Description
1
Header
Specifies the current date and time, the name of the
screen, the system name, the page number of existing
environments, and if there are other pages available
(MORE or END)
2
Existing Environments
Lists the name of VHS environments from the
VHSBConf file. More than one page of environments
may be available. The page number, on the right top
corner, indicates if more pages are available (MORE)
or if the current page is the last one (END). Up to 28
environments can be displayed on one page. Up to
100 total environments can be displayed
3
Selected Environment
Specifies the environment for which the following
information is displayed
4
First Log File
Displays the file name of the first VHS primary log file.
When switching to another set of log files, use this field
to enter the name of the first primary log file you want
to start viewing.
5
First Message Timestamp
Displays the timestamp of the first VHS primary log file
6
Last Log Filename
Displays the file name of the last VHS primary log file
7
Last Message Timestamp
Displays the timestamp of the last VHS primary log file
8
Number of Log Files
Shows the current number of existing primary log files.
If log files are switched using the Switch function (F5),
the value in this field determines the number of
primary log files that are viewed.
9
Prompt File
Displays the file name of the VHS prompt file
10
Number of outstanding
prompts
Specifies the number of prompts that need to be
answered for the prompt file displayed above
11
Opener processes
Lists the name of processes opening the prompt file of
the selected environment. Up to 20 openers can be
displayed
Notes. The timestamps are in local civil time.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 25
Environment Detailed Screen Function Keys
Using the VHS Browser
Environment Detailed Screen Function Keys
Table 4-11 describes the specific function keys used with the Environment Detailed
screen
.
Table 4-11. Environment Detailed Screen Function Keys
Field
Name
Description
F2
Update Screen
Refresh the screen by using the environment name in the
Selected Environment field
F3
Log Browser
Go to the Log Browser screen
F4
Prompt Browser
Go to the Prompt Browser screen
F5
Switch
Switches the log files according to the values entered in the
fields:
•
•
First log file (the first log file to start viewing)
Number of log files (maximum of five log files that are
viewed in sequential order).
Use F3 to view the information logged into the switched log
files and F2 to update the screen with the current five log files.
F9
Print
Print the information displayed on the current screen. You can
use the default printer specified in the Pathway configuration
for your terminal or enter a destination name on the option line
F11
Detail Env
Select one environment by positioning the cursor in the field
preceding the environment name or typing any non-blank
character in that field and press F11 to see the environmentrelated information
F12
Set Current Env
Use the environment from the Selected Environment field and
press F12 to make it the current environment; or select one
environment by positioning the cursor in the field preceding the
environment name, type any non-blank character in that field,
and press F12 to make the selected environment the current
one
F14
VHS Profile
Go to the VHS Profile screen
F15
Help
Go to the Help screen for the current screen
SF16
Exit
Exit VHS
Notes. To view the messages that are logged in the log files (except for the last five log files
logged using the Switch function (F5)), set the PARAM PRIMARY-LOGFILE-PURGE to OFF in
the VHSSTART file before starting VHS.
Printing a Screen
To print any VHS screen, access the desired screen. You can print to the default printer
specified in the Pathway configuration for your terminal or to another printer.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 26
Printing a Screen
Using the VHS Browser
To print the current screen to the default printer, do the following:
•
Press F9.
To print the current screen to another printer:
•
•
Enter the printer name in the option line.
Press F9.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 27
Printing a Screen
Using the VHS Browser
Virtual Hometerm Subsystem (VHS) Manual—429311-001
4- 28
5
Using VHSCI
This section describes how to use the VHS conversational interface (VHSCI). VHSCI
enables you to interact with and configure a VHS process in a standard conversational
interface. This section has the following subsections:
•
•
•
•
•
•
•
•
Getting started
Getting statistics
Getting status information
Listing all current openers
Getting information about and modifying VHS parameters
Getting information about and modifying log destinations
Switching the backup CPU to the primary CPU
Getting information about a VHS environment
Getting Started
VHSCI follows the conventions of Compaq conversational interfaces, such as the
Subsystem Control Facility (SCF). If you have used other Compaq products with a
conversational interface, you will find VHSCI easy to use and understand.
Running VHSCI
You can run VHSCI from the TACL prompt. The RUN command to start VHSCI is
described in this subsection. All the VHSCI commands are described in Section 7,
Command Descriptions.
Note. To run VHSCI with High PIN support, ensure that the #HIGHPIN built-in variable is set to
On at the TACL prompt.
If VHSCI is installed in the $SYSTEM.SYSTEM or $SYSTEM.SYSnn subvolume, you
can type the following from any volume or subvolume to run VHSCI:
1> vhsci
However, if VHSCI is not installed in $SYSTEM.SYSTEM or $SYSTEM.SYSnn
subvolume, you can use the TACL VOLUME command to move to the subvolume
where VHSCI is installed:
1> volume $vol.subvol
2> run vhsci
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -1
Running VHSCI
Using VHSCI
Alternatively, you can specify the volume and subvolume where VHSCI is located in
the run command:
3> run $vhs.vhs.vhsci
Note. You do not have to be a super ID user to run VHSCI.
At the beginning of a VHSCI session, VHSCI displays its product banner, which
includes the Tandem part number, version number, release date, and copyright
statement of the VHSCI program. The VHSCSTM file is automatically invoked. This file
is an OBEY file including commands executed each time you run VHSCI (See
Appendix A, VHS Files).
VHSCI - T9517D21 - (21JUL95) - (VHSCI) - 07/10/95 12:21:22 System \POLLUX
Copyright Tandem Computers Incorporated 1992,1993
(Invoking $VHS.JUNON.VHSCSTM)
Confirm....... ON
PROCESS $VHSD 1->
VHS Info PROCESS running under Environment PROD
The VHSCI prompt is the arrow (->), but you can modify the prompt by using the
SETPROMPT command.
The syntax for the RUN command follows:
[ RUN ] VHSCI [ / run-option / ]
]
[ command [ ; command ] ...
RUN
is the TACL RUN command.
VHSCI
is the program file name of the VHSCI program.
run-option
is one of the following. This list describes commonly used RUN options. For a
complete list of RUN options, see the TACL Reference Manual.
CPU cpu-number
specifies the number of the CPU in which VHSCI is to run. cpu-number is an
integer in the range of 0 through 15. If you omit this option, VHSCI runs in the
same processor as TACL. (If the CPU option is omitted and a $CMON process
exists, $CMON might specify a CPU other than the one in which the current
TACL process is running. For more information about $CMON, see the
Guardian Programmer’s Guide.)
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -2
Exiting VHSCI
Using VHSCI
IN [ file-name ]
specifies the input file for the VHSCI process. If you do not include the IN
file-name, VHSCI uses the IN file in effect for the current TACL (usually your
home terminal).
NAME [ $process-name ]
specifies the name you are assigning to VHSCI. Specify the $process-name
as an alphanumeric string of 1 to 5 characters, the first of which must be a
letter. (For network access, the name must be no more than four characters.) If
you omit this parameter, the VHSCI process is not named and has only a CPU
number and process ID.
NOWAIT
specifies that TACL does not wait while the program runs. TACL returns a
command input prompt after sending the startup message to the new process.
If you omit this option, TACL pauses while VHSCI runs.
OUT [ listfile ]
specifies the output file for the VHSCI process. If you omit OUT listfile, the
VHSCI process uses the OUT file in effect for the current TACL (usually your
home terminal).
PRI priority
specifies the run priority of the VHSCI process. Specify priority as an integer in
the range of 1 to 199. Processes with higher numbers are executed first. If you
omit this option, VHSCI runs at a priority of 1 less than that of the TACL
process. (If a $CMON process exists and you omit the PRI option, $CMON
might specify a priority other than 1 less than your TACL process. For more
information about $CMON, see the Guardian Programmer’s Guide.)
command
is any valid VHSCI command. For information on VHSCI commands, see
Section 7.
Exiting VHSCI
To exit from VHSCI, type the following at the prompt:
-> exit
You can also exit VHSCI by entering E (the abbreviation for EXIT), pressing SF16, or
pressing CTRL/Y.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -3
Entering VHSCI Commands
Using VHSCI
Entering VHSCI Commands
When VHSCI successfully completes all initialization, it is ready to process commands.
It indicates this by displaying its prompt, the greater than sign (->). This prompt can be
changed with the SETPROMPT command. This manual assumes either the selection
of the NONE parameter, which issues only the prompt without a command-line
number, or the OBJECT parameter, which issues the assumed object type and object
name.
Entering Multiple Commands on a Line
You can enter multiple VHSCI commands at a single prompt (->) by separating the
commands with semicolons. For example, the command line:
-> info, detail; alter, VHS-LOGGER OFF; info, detail
is equivalent to the following series of commands:
-> info, detail
-> alter, VHS-LOGGER OFF
-> info, detail
When processing a command line that contains more than one command, VHSCI
executes the commands one at a time from left to right. If a syntax error occurs, VHSCI
displays the appropriate error message and ignores the rest of the command line.
The following VHSCI commands cannot be embedded in a string of commands
because VHSCI does not process any command following these commands: ALIAS,
PARAM, EXIT, OBEY, RUN, FC, exclamation point (!), and question mark (?).
Entering a Command on More Than One Line
You can continue a command that starts on one line onto a second line by terminating
the first line with an ampersand (&). VHSCI will prompt for additional input before
executing the command. You must not enter more than 2048 characters for any input
command.
VHSCI begins to execute the command when it receives a command line not
terminated with an ampersand. If you place multiple commands (separated by
semicolons) on a continued line, VHSCI waits until it has received the entire command
string before processing any of the commands.
For example, the command line
-> info, detail; alter, VHS-LOGGER OFF; info, detail &
-> status; alter, primary 1; &
-> status
is equivalent to the following series of commands:
-> info detail
-> alter, VHS-LOGGER OFF
-> info detail
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -4
Configuring Function Keys
Using VHSCI
-> status
-> alter, primary 1
-> status
Entering a Comment Line
You can enter a comment following the comment characters (==) at the beginning of a
line or within a line. Any text on the line following the == is not processed:
-> == This is a comment.
Also, a comment can be entered using the COMMENT command. The command
COMMENT must appear as the first characters of the line:
-> COMMENT This is a comment.
Using Keyword Abbreviations
VHSCI recognizes keyword abbreviations as long as they are unique. Keywords
include commands, object types, and attribute names. Alias names cannot be
abbreviated, and OBEY (command) files cannot contain abbreviated keywords.
The following are examples of keyword abbreviations:
•
•
•
SE is a valid abbreviation for SETPROMPT.
VE is a valid abbreviation for VERSION.
I is a valid abbreviation for INFO.
Using the BREAK Key
If a command is in progress, you can press the BREAK key to cancel further execution
of that command. If no command is in progress, pressing the BREAK key returns
control to TACL. At the TACL prompt, you can type PAUSE to give the control back to
VHSCI.
Using the HELP Key
You can use the HELP key, F16, to display information about VHSCI commands. The
principle is the same as when you use the TACL HELP key. Pressing F16 while
entering a VHSCI command returns a message indicating the expected input.
Configuring Function Keys
You can use the ALIAS command to set up function keys. The VHSCI default custom
file already contains a set of function key configuration commands. To view the VHSCI
default custom file, see Appendix A.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -5
Configuring Function Keys
Using VHSCI
Setting Up Function Keys
You can use function keys as predefined keywords or commands by using the ALIAS
command.
This example associates F3 with the STATS command. Pressing the F3 function key
has the same result as typing the command STATS:
-> alias F3 stats
This example associates F4 with the STATUS DETAIL command:
-> alias F4 status, detail
This example associates the keyword L with the LISTOPENS command:
-> alias l listopens
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -6
Setting Detail Error Display
Using VHSCI
Example
PROCESS $VHSD -> alias f3 stats
F3................... STATS
PROCESS $VHSD -> alias f4 status, detail
F4................... STATUS, DETAIL
PROCESS $VHSD -> alias l listopens
L.................... LISTOPENS
PROCESS $VHS ->
!pressing the F3 function key
VHS Stats PROCESS $VHSD running under Environment PROD
Started.... 10Jul95,11:54:47
Last reset. 10Jul95,14:32:35
Number of messages/log:
Total opens since last reset.... 0
Total messages since last reset. 5
#Inspect
#Debug
#Display
0
0
5
$VHS.VHSD21.LOG0003
(P)
PROCESS $VHSD 30->
!pressing the F4 function key
#Prompt #Outstd.
prompt
1
1
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD21.LOG0003
$VHS.VHSD21.PROMPT
$VHS.VHSD21.SAVE0000
10Jul95,11:54:47
0
6
$VHS.VHSD21.LOG0003
04Jul95,11:33:46
10Jul95,14:21:58
0
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(6,6,16)
215,4
NNNN
63%
$VHS.VHSD21.PROMPT
Extents.........
04Jul95,11:02:17
10Jul95,11:55:37
0
Owner........... 215,4
Security (RWEP). NNNN
PROCESS $VHSD -> l
VHS ListOpens PROCESS $VHSD running under Environment PROD
Process Objname
$JUNE
$SYSTEM.SYS00.FUP
$DISP $VHS.T9517QA.DISP512
Open
Time of
Time of
Mode
open
last message
PROMPT
10Jul95,11:55:34 10Jul95,11:55:36
DISPLAY 10Jul95,11:55:42 10Jul95,14:40:10
Setting Detail Error Display
You can set the detail error flag to remove or obtain detailed error messages. If you
have detailed error message set to ON, VHSCI shows the probable cause and the
recommended action for each error:
VHS W00201 No process currently open VHS server
Probable Cause
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -7
Setting the Output Destination
Using VHSCI
No process currently has VHS open.
Recommended Action
This is a warning. No action is necessary.
To set the detail error flag to provide the error message only, type the following at the
prompt:
-> detail error off
Setting the Output Destination
To specify the output destination for a VHSCI session, use the OUT command. For
example, if you use the following command, VHSCI would begin sending its output
displays to the specified spooler destination:
-> out $s.#vhsci
VHSCI also allows you to specify an output destination for a single command, leaving
the output destination for the session unchanged. To change the output destination for
a single command, use /OUT file-spec/ following the command keyword. For
example, VHSCI will send the display output for the following STATS command to a
disk file named VHSSTATS on the default system, volume, and subvolume:
-> status /out vhsstats/
To echo both the input commands and the corresponding output displays in a single
file, use the LOG command. Specifying a log file does not change either the input
source or the output destination; instead, a copy of the commands and displays is sent
to the specified file. For example, the following LOG command creates a file named
$DATA.VHSCI.SESSION that will contain each subsequent input command followed by
the output that VHSCI will display in response to that command:
-> log $data.vhsci.session
Editing the VHSCI Custom Configuration File
The installation procedure creates a custom configuration file called VHSCSTM. If this
file is located in your default subvolume, it will be read each time you execute the
VHSCI program command, VHSCI. This file can be used to pre-configure your session
parameters. Use the ALIAS facility of VHSCI to create shortcut commands for often
invoked commands as desired. You can also set up function keys to invoke some of
the VHSCI commands. For example, the F1 function key is defined as the INFO with
DETAIL command. Each time you press the F1 function key, VHSCI interprets this key
as the INFO with DETAIL command and executes this command.
For a sample of a VHSCSTM file, refer to Appendix A, VHS Files.
Once you have used VHSCI a few times, you will have some preferences that you can
put in the VHSCI custom file. Take a copy of the VHSCI custom file (VHSCSTM) from
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -8
Using Online Help
Using VHSCI
the subvolume where NonStop VHS was installed and put it into your user ID default
subvolume:
1> fup dup VHS-subvol.vhscstm, your-subvol.vhscstm
Edit the file VHSCSTM by using EDIT or TEDIT, and then run VHSCI.
Consideration
The VHSCSTM file must be on the default subvolume of the current user ID or you can
use a TACL ASSIGN command to point to this file if it is located on a different
subvolume (see Section 2, Installing VHS).
Example
6> fup dup VHS-subvol.vhscstm, your-subvol.vhscstm
7> edit your-subvol.vhscstm
TEXT EDITOR - T9601B30 - (08MAR87)
CURRENT FILE IS $MYDISK.DEFAULT.VHSCSTM
* enter commands
* exit
8> vhsci
Using Online Help
VHSCI has extensive help text online so that you can look up command information
easily and conveniently. You can use Help in either command mode or menu mode.
Command mode help is recommended because it is easier and faster to use than
menu mode.
Command Mode
To access online help in command mode, enter the HELP command followed by the
name of the command you want help for. The following example shows how to get help
on the LISTOPENS command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5 -9
Using Online Help
Using VHSCI
Example
->
help listopens
The LISTOPENS command lists all processes which currently open
the specified object or objects.
LISTOPENS
[ /OUT <file-spec>/ ]
[ <object-spec> ]
[, <open-mode> ]
/OUT <file-spec>/
causes any VHSCI output generated for this command to be directed
to the specified file.
<object-spec>
designates the objects whose openers are to be displayed. If
<object-spec> is omitted, the openers of the assumed object are
listed (see the VHSCI ASSUME command).
<open-mode>
indicates an open mode to select specific opener processes.
<open-mode> can be one of the following:
INSPECT
all opener processes that prompt the specified
object with an Inspect prompt are listed
DEBUG
all opener processes that prompt the specified
object with a Debug prompt are listed
DISPLAY
all opener processes that display to the specified
object are listed
PROMPT
all opener processes that prompt the specified
object are listed
UNKNOWN
all opener processes that open the specified
object with no other information are listed
PSERVER
all VHS screen servers that open the specified
object are listed
Usage Considerations
o
If there are no current openers, a warning is returned.
Examples
LISTOPENS PROCESS $vhs1
LISTOPENS /OUT OutListo/ PROCESS $vhs2, PROMPT
LISTOPENS PROCESS $vhs1, DISPLAY
To get a list of all the VHSCI commands, type either of the following:
-> help all
-> help vhs
To get help about commands syntax, type the following:
-> help syntax
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 10
Using Online Help
Using VHSCI
To get help about command usage examples, type the following:
-> help examples
Menu Mode
To access online help in menu mode, simply enter the HELP command:
-> help
The HELP menu appears and prompts you for a basic component, subsystem, device
name or option.
Welcome to VHSCI menu mode.
+------------------------------Main Menu---------------------------------+
|
|
| Basic Components:
|
| ALL
ATTRIBUTE-SPEC
CHARACTER-STRING COMMAND
|
| EXAMPLES
FILE-NAME
HELP-KEY
INTEGER
|
| OBJECT-LIST
OBJECT-NAME
OBJECT-SPEC
OBJECT-TYPE
|
| SYNTAX
TIME
|
|
|
|
|
| Subsystems:
|
| VHS
|
|
|
| Device name:
|
| $<name>
|
|
|
+-------------------------Next Menu Selection----------------------------+
|
|
| Options:
|
| QUIT
|
|
|
+------------------------------------------------------------------------+
Enter a basic component, a subsystem, a device name or an option:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 11
Using Online Help
Using VHSCI
To get a list of VHSCI commands and to get help on using HELP, enter ALL at the
HELP prompt:
HELP : all
VHSCI is a conversational interface for the VHS subsystem.
-------------------------- COMMANDS-----------------------------------The following are VHSCI commands:
ALIAS
ASSUME
CPUS
EXIT
INFO
OUT
REPEAT
STATUS
VOLUME
ALLOW
CLEAR
DELAY
FC
LISTOPENS
PAGESIZE
RUN
SYSTEM
!
ALTER
COMMENT
DETAIL
HELP
LOG
PARAM
SETPROMPT
TIMEOUT
?
ASSIGN
CONFIRM
ENV
HISTORY
OBEY
PAUSE
STATS
VERSION
--------------------- HOW TO USE HELP --------------------------------The HELP command displays a detailed description of
commands, object types, and basic components. There are two modes
of help operation--line mode and menu mode. Help text is accessed
in line mode (when the prompt is "->") by entering the full help
command (e.g. "HELP STATUS"). Help text is accessed in
menu mode (when the prompt is "HELP :") by entering each part of the
command in answer to the prompting text. VHSCI is in line mode by
default. To enter menu mode type "HELP" followed by the return key.
Menu mode help can only be used in interactive mode. If HELP<CR>
is entered during a non-interactive VHSCI session, HELP ALL (this text)
will be displayed.
To obtain a description of the help command while in line mode
type "HELP HELP <return>" or while in menu mode type "VHSCI <return>
HELP <return>".
The help key (F16) is used to show all of the valid options at any
point in a command. For a complete description of the help key
while in line mode type "HELP HELP-KEY <return>" or while in menu
mode type "HELP-KEY <return>".
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 12
Using Online Help
Using VHSCI
If you want command information, enter VHS at the HELP prompt.
HELP : VHS
+-------------------------------VHS Menu---------------------------------+
|
|
| Commands:
|
| ALIAS
ALLOW
ALTER
ASSIGN
ASSUME
CLEAR
COMMENT
|
| CONFIRM
CPUS
DELAY
DETAIL
ENV
EXIT
FC
|
| HELP
HISTORY
INFO
LISTOPENS LOG
OBEY
OUT
|
| PAGESIZE
PARAM
PAUSE
REPEAT
RUN
SETPROMPT STATS
|
| STATUS
SYSTEM
TIMEOUT
VERSION
VOLUME
?
!
|
| EXAMPLES
SYNTAX
|
|
|
| Objects:
|
| PROCESS
|
|
|
| Error Numbers:
|
| [ E | W ] [ - ] <integer>
|
|
|
+-------------------------Next Menu Selection----------------------------+
|
|
| Options:
|
| QUIT MAIN RETURN
|
|
|
+------------------------------------------------------------------------+
Enter a command, an object, an error, or an option:
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 13
Using Online Help
Using VHSCI
If you want specific command information, enter the name of the command at the
HELP VHS prompt; for example, LISTOPENS.
HELP VHS : LISTOPENS
The LISTOPENS command lists all processes which currently open
the specified object or objects.
LISTOPENS
[ /OUT <file-spec>/ ]
[ <object-spec> ]
[ , <open-mode> ]
/OUT <file-spec>/
causes any VHSCI output generated for this command to be directed
to the specified file.
<object-spec>
designates the objects whose openers are to be displayed. If
<object-spec> is omitted, the openers of the assumed object are
listed (see the VHSCI ASSUME command).
<open-mode>
indicates an open mode to select specific opener processes.
<open-mode> can be one of the following:
INSPECT
all opener processes that prompt the specified
object with an Inspect prompt are listed
DEBUG
all opener processes that prompt the specified
object with a Debug prompt are listed
DISPLAY
all opener processes that display to the specified
object are listed
PROMPT
all opener processes that prompt the specified
object are listed
UNKNOWN
all opener processes that open the specified
object with no other information are listed
PSERVER
all VHS screen servers who open the specified
object are listed
Usage Considerations
o
If there are no current openers, a warning is returned.
Examples
LISTOPENS PROCESS $vhs1
LISTOPENS /OUT OutListo/ PROCESS $vhs2, PROMPT
LISTOPENS PROCESS $vhs1, DISPLAY
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 14
Getting Statistics
Using VHSCI
Getting Statistics
You can get a variety of statistics about a specific VHS process. You can get the
number of messages received by the VHS process grouped by message type: Inspect,
Debug, Display, Prompt. The number of outstanding prompts is also displayed.
The following command gives you statistics about the VHS process $VHSD:
-> stats process $vhsd
Consideration
You can use the RESET option of the STATS command to reset all counts to zero.
When this option is used, the actual count values display and the VHS process writes
those current values into the primary log destination before resetting them to zero.
Example
-> stats process $vhsd
VHS Stats PROCESS $VHSD running under Environment PROD
Started.... 10Jul95,11:54:47
Last reset. 10Jul95,14:32:35
Number of messages/log:
$VHS.VHSD21.LOG0003
(P)
Total opens since last reset.... 0
Total messages since last reset. 33
#Inspect
#Debug
#Display
0
0
33
#Prompt #Outstd.
prompt
1
1
Getting Status Information
The STATUS command gives you dynamic information about a specific VHS process,
such as the name of the primary log, the name of the prompt file, the name of the next
saveabend file to be created, the number of applications which currently open the VHS
process, etc. It also gives you detailed information about the primary log, the
secondary log destination (if one is configured) and the prompt file.
The following command gives you detailed status information about the VHS process
$VHSD:
-> status process $vhsd, detail
Consideration
If a secondary log destination is configured, VHS provides status information according
to the type of the secondary log destination. For example, if the secondary log
destination is a disk file VHS provides the same information as the primary log and
prompt file. If the secondary log destination is a terminal or spooler, VHS provides less
status information.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 15
Listing All Current Openers
Using VHSCI
Example
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD21.LOG0003
04Jul95,11:33:46
10Jul95,16:00:16
0
$VHS.VHSD21.LOG0003
$VHS.VHSD21.PROMPT
$VHS.VHSD21.SAVE0000
10Jul95,11:54:47
0
65
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(6,6,16)
215,4
NNNN
75%
Secondary log:
Name.......... $S.#VHSLOG
Last Access... 10Jul95,16:00:16
Last Error
0
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
$VHS.VHSD21.PROMPT
Extents.........
04Jul95,11:02:17
10Jul95,11:55:37
0
Owner........... 215,4
Security (RWEP). NNNN
Listing All Current Openers
You can get a list of all application processes which currently open the VHS process by
using the LISTOPENS command. The LISTOPENS command shows the process, its
program file name, and the mode used to open the VHS process. The mode can be
one of the following: Inspect, Debug, Display, Prompt, Unknown, or Pserver (prompt
server).
The following command gives you a list of all applications which currently open the
VHS process $VHSD:
-> listopens process $vhsd
Considerations
If no applications currently open the VHS process, a warning displays.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 16
Getting Information About and Modifying VHS
Parameters
Using VHSCI
Example
VHS ListOpens PROCESS $VHSD running under Environment PROD
Process
$JUNE
$DISP
Objname
$SYSTEM.SYS00.FUP
$VHS.T9517QA.DISP512
Open
Time of
Time of
Mode
open
last message
PROMPT 10Jul95,11:55:34 10Jul95,11:55:36
DISPLAY 10Jul95,11:55:42 10Jul95,15:22:50
Getting Information About and Modifying VHS
Parameters
This subsection describes how to get information about the VHS parameters and how
to modify them.
Getting Information About the VHS Parameters
Use the INFO command with the DETAIL option to get information about the VHS
Parameters. This lists all the VHS Parameters with the values of each of them.
The following command gives you information about the VHS process $VHSD:
-> info process $vhsd, detail
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 17
Modifying a VHS Parameter
Using VHSCI
Example
VHS Info Process $VHSD, detail
VHS Detailed Info PROCESS $VHSD running under Environment PROD
Max opens.....................
Primary log...................
Max primary log files.........
Prompt file...................
EMS collector.................
Inspect file..................
Next save file................
512
\POLLUX.$VHS.VHSD21.LOG0003
5
\POLLUX.$VHS.VHSD21.PROMPT
\POLLUX.$0
\POLLUX.$VHS.VHSD21.VHSINSP
\POLLUX.$VHS.VHSD21.SAVE0000
Accept-ext-ascii-character....
Add-text-to-event.............
Automatic-inspect-processing..
Backup-creation-message-delay.
Environment-name..............
File-code.....................
OFF
ON
ON
5
PROD
0
Generate-display-event........
Generate-inspect-event........
Generate-prompt-event.........
Maxextents....................
Open-table-threshold..........
Primary-security..............
Prompt-event-resend-delay.....
Purge-savefile................
Remove-extra-spaces...........
Saveabend-file................
Suppress-display..............
Vhs-GUI-mode..................
Vhs-logger....................
ON
ON
ON
16
90
NNNN
15
OFF
ON
ON
OFF
ON
ON
Logs:
*LogName
\POLLUX.$VHS.VHSD21.LOG0003
(P)
*LogType
ALL
Considerations
•
•
You can modify all the parameters appearing in the list above.
You do not need to enter all the letters of the parameter name when you want to
modify it. Only the first characters that differentiate the parameter from the other
one is accepted. For example, if you want to modify the GENERATE-DISPLAYEVENT, you can enter the following command:
-> alter process $vhsd, GENERATE-D OFF
Since GENERATE-D differentiates the GENERATE-DISPLAY-EVENT parameter
from the other, it will be understood by the VHSCI as the GENERATE-DISPLAYEVENT parameter.
Modifying a VHS Parameter
You can modify a parameter with the ALTER command. When you modify a parameter,
the new value of this parameter is immediately used by the VHS process.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 18
Getting Information About and Modifying
Log Destinations
Using VHSCI
The following command modifies the GENERATE-DISPLAY-EVENT:
-> alter process $vhsd, GENERATE-DISPLAY-EVENT OFF
The GENERATE-DISPLAY-EVENT parameter is now set to OFF for VHS.
Considerations
•
You do not need to enter all the letters of the parameter name when you want to
modify it. Only the first characters that differentiate the parameter from the other
one is accepted. For example, if you want to modify the GENERATE-DISPLAYEVENT, you can enter the following command:
-> alter process $vhsd, GENERATE-D OFF
Since GENERATE-D differentiates the GENERATE-DISPLAY-EVENT parameter
from the other, it will be understood by the VHSCI as the GENERATE-DISPLAYEVENT parameter.
•
Note that all the modifications are applicable on a specific VHS process and not on
a VHS environment. If you want to modify a parameter for a VHS environment, you
must modify this parameter for each VHS process of the corresponding VHS
environment.
Getting Information About and Modifying
Log Destinations
This subsection describes how to get information about the log configuration and how
to add, modify or delete a secondary log destination.
Getting Information About the Log Configuration
Use the INFO command with the DETAIL option to get information about the log
configuration. This lists the configured primary log destination and the secondary log
destination if one is configured.
The following command gives you information about the VHS process $VHSD:
-> info process $vhsd, detail
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 19
Adding a Secondary Log
Using VHSCI
Example
-> info process $vhsd, detail
VHS Detailed Info PROCESS $VHSD running under Environment PROD
Max opens.....................
Primary log...................
Max primary log files.........
Prompt file...................
EMS collector.................
Inspect file..................
Next save file................
512
\POLLUX.$VHS.VHSD21.LOG0003
5
\POLLUX.$VHS.VHSD21.PROMPT
\POLLUX.$0
\POLLUX.$VHS.VHSD21.VHSINSP
\POLLUX.$VHS.VHSD21.SAVE0000
Accept-ext-ascii-character....
Add-text-to-event.............
Automatic-inspect-processing..
Backup-creation-message-delay.
Environment-name..............
File-code.....................
Generate-display-event........
Generate-inspect-event........
Generate-prompt-event.........
Maxextents....................
Open-table-threshold..........
Primary, secondary-extent.....
Primary-security..............
Prompt-event-resend-delay.....
Purge-savefile................
Remove-extra-spaces...........
Saveabend-file................
Suppress-display..............
Vhs-GUI-mode..................
Vhs-logger....................
OFF
ON
ON
5
PROD
0
OFF
ON
ON
16
90
(5,5)
NNNN
15
OFF
ON
ON
OFF
OFF
ON
logs:
*LogName
\POLLUX.$VHS.VHSD21.LOG0003
(P)
*LogType
ALL
Adding a Secondary Log
You can add a secondary log destination. A secondary log destination can be either a
disk file, a spooler, or a terminal. This secondary log contains all messages the VHS
process receives according to the type specified when configuring it. For example, you
can choose to log only Display messages to a particular spooler destination.
The following command adds a secondary log destination which receives all Display
messages:
-> alter process $vhsd, log $s.#vhslog, add, type display
Considerations
•
•
You can have only one secondary log destination.
The disk file names of the primary log destination, the prompt file, and the save file
are not accepted as valid file names for a secondary log destination. For the
primary log destination and the save file, the names are considered the same even
if the numeric part of the file name is different. This is to avoid future confusion
when a primary log file gets full and rolls over into another log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 20
Modifying a Secondary Log
Using VHSCI
Example
-> alter process $vhsd, log $s.#vhslog, add, type display
Alter accepted by VHS: PROCESS \OMSNCC.$VHSD
-> info process $vhsd, detail
VHS Detailed Info PROCESS $VHSD running under Environment PROD
Max opens.....................
Primary log...................
Max primary log files.........
Prompt file...................
EMS collector.................
Inspect file..................
Next save file................
512
\POLLUX.$VHS.VHSD21.LOG0003
5
\POLLUX.$VHS.VHSD21.PROMPT
\POLLUX.$0
\POLLUX.$VHS.VHSD21.VHSINSP
\POLLUX.$VHS.VHSD21.SAVE0000
Accept-ext-ascii-character.....OFF
Add-text-to-event............. ON
Automatic-inspect-processing.. ON
Backup-creation-message-delay. 5
Environment-name.............. PROD
File-code..................... 0
Generate-display-event........ OFF
Generate-inspect-event........ ON
Generate-prompt-event......... ON
Maxextents.................... 16
Open-table-threshold.......... 90
Primary, secondary-extent..... (5,5)
Primary-security.............. NNNN
Prompt-event-resend-delay..... 15
Purge-savefile................ OFF
Remove-extra-spaces........... ON
Saveabend-file................ ON
Suppress-display.............. OFF
Vhs-GUI-mode.................. OFF
Vhs-logger.................... ON
logs:
*LogName
\POLLUX.$VHS.VHSD21.LOG0003
\POLLUX.$S.#VHSLOG
(P)
*LogType
ALL
DISPLAY
Modifying a Secondary Log
You can modify the type of a secondary log destination to another type of message.
For example, you can choose to change the type of the secondary log destination
added in the previous subsection from Display messages to Prompt messages.
The following command modifies the secondary log destination to make it log all
Prompt messages:
-> alter process $vhsd, log $s.#vhslog, type prompt
Consideration
The primary log destination cannot be altered. It must exist and must have ALL as its
log type.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 21
Deleting a Secondary Log
Using VHSCI
Example
-> alter process $vhsd, log $s.#vhslog, type prompt
Alter accepted by VHS: PROCESS \OMSNCC.$VHSD
-> info process $vhsd, detail
VHS Detailed Info PROCESS $VHSD running under Environment PROD
Max opens.....................
Primary log...................
Max primary log files.........
Prompt file...................
EMS collector.................
Inspect file..................
Next save file................
512
\POLLUX.$VHS.VHSD21.LOG0003
5
\POLLUX.$VHS.VHSD21.PROMPT
\POLLUX.$0
\POLLUX.$VHS.VHSD21.VHSINSP
\POLLUX.$VHS.VHSD21.SAVE0000
Accept-ext-ascii-character....
Add-text-to-event.............
Automatic-inspect-processing..
Backup-creation-message-delay.
Environment-name..............
File-code.....................
Generate-display-event........
Generate-inspect-event........
Generate-prompt-event.........
Maxextents....................
Open-table-threshold..........
Primary, secondary-extent.....
Primary-security..............
Prompt-event-resend-delay.....
Purge-savefile................
Remove-extra-spaces...........
Saveabend-file................
Suppress-display..............
Vhs-GUI-mode..................
Vhs-logger....................
OFF
ON
ON
5
PROD
0
OFF
ON
ON
16
90
(5,5)
NNNN
15
OFF
ON
ON
OFF
ON
ON
Logs:
*LogName
\POLLUX.$VHS.VHSD21.LOG0003
\POLLUX.$S.#VHSLOG
(P)
*LogType
ALL
PROMPT
Deleting a Secondary Log
You can delete the secondary log destination. No more messages will be logged in that
destination after the destination is removed from the VHS process configuration.
The following command deletes the secondary log destination:
-> alter process $vhsd, log $s.#vhslog, delete
Consideration
The primary log destination cannot be deleted. It must exist and must have ALL as its
log type.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 22
Switching the Backup CPU to the Primary CPU
Using VHSCI
Example
-> alter process $vhsd, log $s.#vhslog, delete
VHS Detailed Info PROCESS $VHSD running under Environment PROD
-> info process vhsd, detail
VHS Detailed Info PROCESS $VHSD running under Environment PROD
Max opens.....................
Primary log...................
Max primary log files.........
Prompt file...................
EMS collector.................
Inspect file..................
Next save file................
512
\POLLUX.$VHS.VHSD21.LOG0003
5
\POLLUX.$VHS.VHSD21.PROMPT
\POLLUX.$0
\POLLUX.$VHS.VHSD21.VHSINSP
\POLLUX.$VHS.VHSD21.SAVE0000
Accept-ext-ascii-character....
Add-text-to-event.............
Automatic-inspect-processing..
Backup-creation-message-delay.
Environment-name..............
File-code.....................
Generate-display-event........
Generate-inspect-event........
Generate-prompt-event.........
Maxextents....................
Open-table-threshold..........
Primary, secondary-extent.....
Primary-security..............
Prompt-event-resend-delay.....
Purge-savefile................
Remove-extra-spaces...........
Saveabend-file................
Suppress-display..............
Vhs-GUI-mode..................
Vhs-logger....................
OFF
ON
ON
5
PROD
0
OFF
ON
ON
16
90
(5,5)
NNNN
15
OFF
ON
ON
OFF
OFF
ON
logs:
*LogName
\POLLUX.$VHS.VHSD21.LOG0003
(P)
*LogType
ALL
Switching the Backup CPU to the Primary CPU
The VHS process should be started as a NonStop process pair. If you want to make
the backup CPU be the primary CPU, use the ALTER command. The following
command makes the backup CPU (CPU 1) become the primary CPU of the VHS
process $VHSD:
-> alter process $vhsd, primary 1
Consideration
The CPU number specified in the ALTER command must be the current backup CPU
number; otherwise, an error displays.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 23
Switching the Backup CPU to the Primary CPU
Using VHSCI
Example
-> status process $vhsd, detail
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
00,36
01,52
03,17
0
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD21.LOG0007
$VHS.VHSD21.PROMPT
$VHS.VHSD21.SAVE0000
10Jul95,11:54:47
0
0
$VHS.VHSD21.LOG0007
11Jul95,9:36:40
11Jul95,10:46:54
0
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(6,6,16)
215,4
NNNN
27%
$VHS.VHSD21.PROMPT
Extents.........
04Jul95,11:02:17
11Jul95,9:36:41
0
Owner........... 215,4
Security (RWEP). NNNN
-> alter process $vhsd, primary 1
Alter accepted by VHS: PROCESS \POLLUX.$VHSD
-> status process $vhsd, detail
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD21.LOG0007
$VHS.VHSD21.PROMPT
$VHS.VHSD21.SAVE0000
10Jul95,11:54:47
0
0
$VHS.VHSD21.LOG0007
11Jul95,9:36:40
11Jul95,10:48:29
0
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
$VHS.VHSD21.PROMPT
Extents.........
04Jul95,11:02:17
11Jul95,9:36:41
0
Owner........... 215,4
Security (RWEP). NNNN
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 24
(6,6,16)
215,4
NNNN
27%
Getting Information About a VHS Environment
Using VHSCI
Getting Information About a VHS Environment
You can have multiple VHS processes running under one VHS environment. You can
get useful information about this environment with a single command if you set up an
appropriate alias. The following example shows how to get statistics about the
environment PROD.
-> alias STATSPROD stats process ($PROD1, $PROD2, $PROD3)
-> statsprod
Consideration
You can set up all your aliases in your VHSCSTM file. They are automatically defined
for you each time you run VHSCI.
Example
-> alias STATSPROD stats process ($PROD1, $PROD2, $PROD3)
STATSPROD............ STATS PROCESS ($PROD1, $PROD2, $PROD3)
-> statsprod
VHS Stats Process $PROD1 running under Environment PROD
Started.... 10Jul95,11:54:47
Last reset. 11Jul95,10:48:28
Number of messages/log:
$VHS.VHSD21.LOG0007
Total opens since last reset.... 0
Total messages since last reset. 7
#Inspect
#Debug
#Display
0
0
7
(P)
#Prompt #Outstd.
prompt
0
1
VHS Stats Process $PROD2 running under Environment PROD
Started.... .7Jun95,12:49:47
Last reset. 10Jul95,10:32:19
Number of messages/log:
$VHS.VHSD21.LOG0007
Total opens since last reset.... 14
Total messages since last reset. 22
#Inspect
#Debug
#Display
3
0
4
(P)
#Prompt #Outstd.
prompt
0
0
VHS Stats Process $PROD3 running under Environment PROD
Started.... 10Jul95,13:44:37
Last reset. 10Jul95,13:44:37
Number of messages/log:
$VHS.VHSD21.LOG0007
(P)
Total opens since last reset.... 89
Total messages since last reset. 310
#Inspect
#Debug
#Display
17
3
270
#Prompt #Outstd.
prompt
20
4
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 25
Using VHSCI
Getting Information About a VHS Environment
Virtual Hometerm Subsystem (VHS) Manual—429311-001
5- 26
6
Command Components
This section contains a description of the basic syntactic components used with VHS.
This section describes the following components:
•
•
•
•
Objects and object lists
Attributes and attribute values
Strings, integers, and time values
Disk file names
Objects and Object Lists
Objects are the entities that you use the VHSCI to configure, control, and inquire
about. Many VHSCI commands accept a list of object names in place of a single object
name. Listing multiple object names requires a pair of parentheses and commas to
separate each object. Commands are applied to all the objects in an object list. For
example, the commands ASSUME PROCESS, INFO ($VHS, $VHSD), and STATUS
($VHS, $VHSD) apply to both VHS processes: $VHS and $VHSD.
Object-Spec Variable
The variable object-spec is used throughout the command descriptions to represent
all variations of object references.
The general format of object-spec is as follows:
[ object-type ] [ object-name
[ (object-name [, object-name ]...
]
) ]
object-type
designates a specific keyword that identifies the type of object referenced or to be
acted upon by the command. In VHSCI, the only valid object type is PROCESS. If
you do not want to retype object-type for each command that requires an
object type, use the ASSUME command to always set object-type to
PROCESS.
object-name
specifies the name of a single object. The general form of object-name is as
follows:
$process-name
specifies the name of a process. The process name consists of a dollar sign
($) followed by a letter and by zero to four (zero to three if the node name is
included for network access) alphanumeric characters with no embedded
blanks, for example, $VHSD.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
6 -1
Attributes and Attribute Values
Command Components
The object name specifies a single object. The format of an object name is the
same as the format of a NonStop Kernel process name. In VHSCI, the object name
represents a VHS process. The object name can be omitted if the ASSUME
command is used to establish an appropriate object name.
If an ASSUME command is used to establish a default object type and fully
qualified object name, and if the object type and object name refer to a valid object,
the object specification can be omitted from commands. Each command is applied
to the object known as the assumed object, the object designated using the
ASSUME command. For example, if the command ASSUME PROCESS $VHSD is
entered, entering INFO displays information about the VHS process called $VHSD.
Attributes and Attribute Values
A VHSCI object has an associated set of attributes, each of which identifies some
characteristic for that object. Each attribute has an associated set of values.
Attribute-Spec Variable
The syntax for the VHSCI ALTER command includes the variable attribute-spec,
which indicates the name and value for the required attribute.
The general form of attribute-spec is as follows:
attribute-name [ attribute-value ]
attribute-name
is a string of one or more characters. The first character is alphabetic. Subsequent
characters can be any printable alphanumeric or special characters except
embedded blanks.
attribute-value
is the value to be associated with attribute-name.
This syntax is used to assign a new value to an attribute. For example, ALTER
PROCESS $VHSD, PRIMARY 1 assigns the value 1 to the PRIMARY attribute.
Strings, Integers, and Time Values
VHSCI requires a standard format for entering character strings, integers, and time
values. The variables for these items are:
char
integer
time
Virtual Hometerm Subsystem (VHS) Manual—429311-001
6 -2
Char Variable
Command Components
Char Variable
The variable char is used for attributes that accept one or more 8-bit characters. The
syntax of char is as follows:
{ "character-string" }
{ 'character-string' }
character-string
is any string of one or more printable ASCII characters.
To include a single or double quotation mark in a string delimited by the same type of
quotation mark, enter the quotation mark character twice. For example:
""apple"" produces "apple"
''pie'' produces 'pie'
To include a single or double quotation mark in a string delimited by a different type of
quotation mark enter the string-enclosing quotation mark twice, for example:
''"apple"'' produces "apple"
""'pie'""produces 'pie'
Integer Variable
The variable integer is used for attributes that accept an 8-bit, 16-bit, 32-bit, or 64-bit
negative or positive integer value. The syntax of integer is as follows:
[ - ]
{
{ %
{{ %B
{{ %H
{
{
{
{
0|1|2|3|4|5|6|7|8|9 } ...
0|1|2|3|4|5|6|7 } ...
0|1} ...
0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F } ...
}
}
}
}
Values that include a minus sign (-) are interpreted as negative numbers.
Values that do not include a percent sign (%) are interpreted as decimal numbers.
Values prefixed by the percent sign (%) are interpreted as octal numbers. Values
prefixed by %B are interpreted as binary numbers, and values prefixed by %H are
interpreted as hexadecimal numbers.
•
•
•
•
The range of an 8-bit integer is -128 through 127. If it is unsigned, the range is
0 through 255.
The range of a 16-bit integer is -32768 through 32767. If it is unsigned, the range is
0 through 65535.
The range of a 32-bit integer is -2147483648 through 2147483647.
The range of a 64-bit integer is -2**63 through 2**64-1.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
6 -3
Time Variable
Command Components
Time Variable
The variable time is used for attributes that require a specified time interval. The
syntax of time is as follows:
[ [ hours : ] minutes : ] seconds [ . fraction ]
hours
specifies an integer, as defined in Integer Variable on page 6-3.
minutes
specifies an integer, as defined in Integer Variable on page 6-3.
seconds
specifies an integer, as defined in Integer Variable on page 6-3.
fraction
specifies an integer in the range 000 to 999, representing a decimal fraction of a
second.
The only required part of the time specification is seconds. The actual range for the
time value for a particular attribute is context dependent.
Disk File Names
Disk files in the NonStop Kernel operating system are identified by a unique, symbolic
file name. VHSCI uses the same conventions. A complete NonStop Kernel disk file
name describes the location of a file and has four parts:
•
•
•
•
\system-name
$volume-name
subvolume-name
file-name
For convenience, default values are provided for all parts of a complete file name
except file-name. Default values for a VHSCI session can be established through
the use of the SYSTEM and VOLUME commands. For additional information, refer to
the SYSTEM command and VOLUME command descriptions in Section 7, Command
Descriptions. The initial default values are the values provided by the command
interpreter through which VHSCI was invoked.
File Specification
In the syntax descriptions for VHSCI commands, the variable file-spec is used to
denote a fully or partially qualified NonStop Kernel disk file name. A fully qualified file
Virtual Hometerm Subsystem (VHS) Manual—429311-001
6 -4
File Specification
Command Components
name has all four parts explicitly specified. A partially qualified file name has one or
more optional parts missing. VHSCI uses the appropriate default values to expand the
file name to four parts. The syntax of file-spec is as follows:
[ \system-name.] [ $volume-name.] [ subvolume-name.] filename
\system-name
identifies a specific system within a network.
$volume-name
identifies a volume.
subvolume-name
identifies a set of files defined by the user.
file-name
identifies a particular file within the subvolume.
The syntax of system-name, volume-name, subvolume-name, and file-name in
VHSCI is identical to the syntax defined for these components for the NonStop Kernel
operating system.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
6 -5
File Specification
Command Components
Virtual Hometerm Subsystem (VHS) Manual—429311-001
6 -6
7
Command Descriptions
This section describes the syntax of all commands available with the conversational
interface of VHS, VHSCI. The information in this section is critical to understanding
what commands are available, what they do, and how they are entered. VHSCI makes
certain assumptions when various options are omitted.
Table 7-1 gives an overview of the VHSCI commands. A full description of each
command follows.
Table 7-1. VHSCI Commands Overview (page 1 of 2)
Commands
Description
!
Reexecutes a command line
?
Displays a specific command line
ALIAS
Defines a command or text abbreviation
ALLOW
Specifies the number of errors or warnings permitted during the
execution of an OBEY (command) file
ALTER
Changes the values of the attributes of an existing VHS object
ASSIGN
Changes, adds, and displays ASSIGN messages that are passed to new
processes initiated by the VHSCI RUN command
ASSUME
Sets the default object type, object name, or both
CLEAR
Clears the logical file assignments made with the ASSIGN command.
Parameters are set with the PARAM command, and aliases are defined
with the ALIAS command
COMMENT
Allows you to enter comments or descriptions in OBEY (command) files
CONFIRM
Enables or disables the display of positive responses from subsystems
CPUS
Displays the names of all known systems on the network and the states
of their associated CPUs
DELAY
Suspends VHSCI processing for a specified time interval
DETAIL ERROR
Enables or disables detailed error descriptions
ENV
Displays the settings of various VHSCI session parameters, referred to
as environmental parameters
EXIT
Terminates a VHSCI session
FC
Allows you to correct a VHSCI command line (fix command)
HELP
Displays information about VHSCI commands
HISTORY
Displays previously entered commands
INFO
Displays the attribute values for the specified object
LISTOPENS
Lists all processes which currently open the specified object
LOG
Directs a copy of entered VHSCI commands and displays to a file
OBEY
Causes commands to be read from a disk file
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -1
Exclamation Point (!) Command
Command Descriptions
Table 7-1. VHSCI Commands Overview (page 2 of 2)
Commands
Description
OUT
Redirects VHSCI displays to a designated location, such as terminal,
spooler, or out file
PAGESIZE
Sets the terminal screen size and printer page size
PARAM
Changes, adds, and displays PARAM values that are passed to a
process initiated by VHSCI RUN command
PAUSE
Suspends VHSCI and releases the terminal for use by another process.
Usually, this command is used in conjunction with the RUN command
REPEAT
Causes the remainder of the command line to be repeated for a specific
number of iterations, or until the BREAK key is activated
RUN
Runs another program from within VHSCI
SETPROMPT
Changes the command line prompt
STATS
Displays the accumulated statistics for an object and optionally resets
them
STATUS
Displays information about the specified object
SYSTEM
Sets the default system name for all file name and object name
expansions
TIMEOUT
Enables the user to vary the amount of time VHSCI waits for a response
before canceling the request
VERSION
Displays the version level of the specified object
VOLUME
Sets the default volume and subvolume names for all file name
expansions
Exclamation Point (!) Command
The exclamation point (!) command causes a previous command line to be reexecuted.
! [ [ - ] number
]
[ character-string ]
number
if positive, is the line number of the command line to be re-executed. If negative,
the current command-line number minus number is the line number of the
command line to be re-executed.
character-string
is the first few characters of the command line to be re-executed. The most recent
command line whose first characters match the string are re-executed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -2
Question Mark (?) Command
Command Descriptions
Considerations
•
•
•
•
•
If you use an exclamation point (!) alone, the previous command is re-executed.
The exclamation point (!) alone is the same as ! -1.
If you specify a negative number and the associated command line is no longer in
the history buffer, you get an error message. (The history buffer of command lines
is 1024 bytes in length.)
The exclamation point (!) command does not increment the command-line number
in VHSCI prompt. The display of command line numbers in the prompt is controlled
by the SETPROMPT command.
The exclamation point (!) command can be issued only by an interactive user.
The exclamation point (!) command cannot be followed by another command on
the same line.
Examples
-> INFO PROCESS $VHS
-> STATUS PROCESS $VHS
.
.
.
-> !-2
INFO PROCESS $VHS
-> !STAT
-> STATUS PROCESS $VHS
.
.
.
-> !
STATUS PROCESS $VHS
.
.
.
{Re-execute two commands ago
}
{Re-execute the most recent command}
{beginning with "STAT"
}
{Re-execute the most recent command}
Question Mark (?) Command
The question mark (?) command causes a previous command line to be displayed.
? [ [ - ] number
]
[ character-string ]
number
if positive, is the line number of the command line to be displayed. If negative, the
current command-line number minus number is the line number of the command
line to be displayed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -3
ALIAS Command
Command Descriptions
character-string
is the first few characters of the command line to be displayed. The most recent
command line whose first characters match the string is displayed.
Considerations
•
•
•
•
•
If you use a question mark (?) alone, the previous command is displayed. The
question mark (?) alone is the same as ? -1.
If you specify a negative number and the associated command line is no longer in
the history buffer, you get an error message. The history buffer of command lines is
1024 bytes in length.
The question mark (?) command does not increment the command-line number in
VHSCI prompt. The display of command line numbers in the prompt is controlled
by the SETPROMPT command.
The question mark (?) command can be issued only by an interactive user.
The question mark (?) command cannot be followed by another command on the
same line.
Examples
-> INFO PROCESS $VHS
-> STATUS PROCESS $VHS
.
.
.
-> ?INF
INFO PROCESS $VHS
->
ALIAS Command
The ALIAS command enables you to abbreviate commands. If the name of the alias is
encountered at the beginning of a line, VHSCI expands the alias to its associated text.
If the name of the alias is encountered at the end of the line, VHSCI expands the alias
to its associated text if the name of the alias is preceded by a hyphen (-) and
terminated with a special character (comma, period, backslash, semicolon or end of
line).
ALIAS [ / OUT file-spec / ] [ identifier [ text ] ]
[ wildcard ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -4
ALLOW Command
Command Descriptions
identifier
is the name of the alias, consisting of an alphabetic character followed by 0 to 20
alphanumeric characters. If omitted, all previously defined aliases are displayed.
text
consists of any printable characters. This is the text that the alias name is
expanded into. If omitted, the selected alias is displayed.
wildcard
displays a subset of the existing aliases that matches the wild-card template. A
wild-card alias name can contain one or more asterisks (*) or question marks(?).
The asterisk (*) specifies any number of characters. The question mark (?)
specifies one character.
Considerations
•
•
If you have multiple commands on a command line, do not use other commands
after the ALIAS command.
Alias names can appear within the text associated with other aliases.
Examples
The following is an example of an alias name used at the beginning of a line.
-> == Add an alias
-> ALIAS sp setprompt
-> == Display the defined alias
-> ALIAS s*
-> SP.................. SETPROMPT
-> == Use the alias sp
-> sp ALL
\SIRIUS $SYSTEM SYSTEM 32-> == Delete the alias sp
\SIRIUS $SYSTEM SYSTEM 32-> CLEAR ALIAS sp
\SIRIUS $SYSTEM SYSTEM 33->
The following is an example of an alias name used at the end of a line.
-> == Add an alias object type and name
->ALIAS PR PROCESS $VHS
-> == Use the ALIAS PR within line by specifying the alias with a hyphen
as
-> == prefix and an end of line as suffix
->INFO -PR
-> == the alias name expands to INFO PROCESS $VHS
ALLOW Command
The ALLOW command specifies the maximum number of warnings or errors allowed
during execution of a command that refers to multiple objects or that issues multiple
commands. If any value is exceeded, VHSCI halts execution of the command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -5
ALLOW Command
Command Descriptions
Commands that refer to multiple objects or that issue multiple commands are most
commonly used in OBEY (command) files or IN files.
Use the ALLOW command to continue executing a startup command file despite the
occurrence of errors from inoperable lines or devices. Errors can cause the execution
of the OBEY (command) file to terminate. ALLOW permits the network to be started.
The ALLOW command can be entered interactively or from within an OBEY
(command) file.
ALLOW [ / OUT file-spec / ] [ ALL
] [ ERRORS
]
[ NO
] [ WARNINGS ]
[ count ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
ALL
indicates that there is no limit on the number of errors or warnings.
NO
indicates that no errors or warnings are allowed.
count
indicates an integer specifying the number of errors or warnings permitted during
the execution of a command.
ERRORS
declares that the entered command applies to errors only.
WARNINGS
declares that the entered command applies to warnings only.
Considerations
•
•
•
If the ALLOW command is not used or if it is entered with no parameters, the
default setting is NO ERRORS and ALL WARNINGS.
If ERRORS or WARNINGS is specified but ALL, NO, and count are omitted, ALL
is assumed.
If ALL, NO, or count is specified, but ERRORS and WARNINGS are omitted,
ERRORS is assumed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -6
ALTER Command
Command Descriptions
Examples
-> ALLOW
Execution of an OBEY (command) file aborts with the detection of the first error.
Warnings are ignored.
-> ALLOW 5 ERRORS
Execution of an OBEY (command) file aborts if more than five errors are detected.
Warnings are ignored.
ALTER Command
The ALTER command changes the attribute values of an existing object. Only the
specified attributes of the target object or objects are changed. This command modifies
the configuration of the VHS server.
ALTER [ / OUT file-spec / ] [ object-spec ]
[, attribute-spec
]...
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
object-spec
designates the object or objects whose attributes are altered. If object-spec is
omitted, the assumed object is used. See the VHSCI ASSUME command.
attribute-spec is one of:
PRIMARY number
LOG
file-name { , TYPE log-type }
{ , ADD [ , TYPE log-type ] }
{ , DELETE }
EMS-COLLECTOR
collector-name
INSPECT-FILE
file-name
ACCEPT-EXT-ASCII-CHARACTER
on-off-value
ADD-TEXT-TO-EVENT
on-off-value
AUTOMATIC-INSPECT-PROCESSING
on-off-value
BACKUP-CREATION-MESSAGE-DELAY
time-value
ENVIRONMENT-NAME
string-value
EXTENT
numeric-values
FILE-CODE
numeric-value
GENERATE-DISPLAY-EVENT
on-off-value
GENERATE-INSPECT-EVENT
on-off-value
GENERATE-PROMPT-EVENT
on-off-value
MAXEXTENTS
numeric-value
OPEN-TABLE-THRESHOLD
numeric-value
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -7
ALTER Command
Command Descriptions
PRIMARY-SECURITY
PROMPT-EVENT-RESEND-DELAY
PURGE-SAVEFILE
REMOVE-EXTRA-SPACES
SUPPRESS-DISPLAY
VHS-LOGGER
string-value
numeric-value
on-off-value
on-off-value
on-off-value
on-off-value
PRIMARY number
specifies a CPU number. number must be a 0 to 15 integer and is expected to
be the backup CPU number of the specified VHS process.
LOG file-name
designates the log destination to be altered:
file-name:[ terminal-name | spooler-location | file-name ]
terminal-name
represents a terminal identification.
Example: $term26.
spooler-location
identifies the desired spooler location.
Example: $s.#vhslog.
file-name
represents a disk file name.
Example: $VHS.VHSLOG.LOGSEC1
TYPE log-type
designates the log type to be associated with the specified secondary log
destination.
log-type: [ ALL | DEBUG | DISPLAY | PROMPT ]
ALL
receives all messages processed by VHS.
DEBUG
receives only Debug and Inspect messages processed by VHS.
DISPLAY
receives only the applications processed by VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -8
ALTER Command
Command Descriptions
PROMPT
receives only the prompt messages processed by VHS.
ADD [ , TYPE log-type ]
adds the specified log destination to the list of current log destinations. The log
type of the new log destination is the one specified by log-type, or ALL by
default. A VHS process supports a primary log and a secondary log file.
DELETE
deletes the specified log destination from the list of current log destinations.
EMS-COLLECTOR collector-name
specifies the name of the EMS collector.
INSPECT-FILE file-name
specifies the name of the Inspect file.
ACCEPT-EXT-ASCII-CHARACTER on-off-value
specifies whether VHS will accept non-ASCII characters. The default value is OFF.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
allows VHS to accept non-ASCII characters.
OFF | FALSE
forbids VHS to accept non-ASCII characters.
ADD-TEXT-TO-EVENT on-off-value
specifies if the text token must be added to all EMS event messages. The default
value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
adds the text token to EMS event messages.
OFF | FALSE
does not add the text token to EMS event messages.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7 -9
ALTER Command
Command Descriptions
AUTOMATIC-INSPECT-PROCESSING on-off-value
specifies if VHS is to process inspect prompts or let the user manage them via the
VHS Prompt Browser screen. The default value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS is to automatically process inspect prompts.
OFF | FALSE
indicates that VHS is not to process inspect prompts. They are to be managed
via the VHS Prompt Browser screen.
BACKUP-CREATION-MESSAGE-DELAY time-value
specifies the delay in minutes between each occurrence of the backup creation
failure message. time-value must be between 0 and 999. The default value is
5 minutes.
ENVIRONMENT-NAME string-value
specifies the name of the VHS process environment. string-value specifies
the environment name length. The value must be between quotes and its first
character must be alphabetic. All other characters can be alphabetic, numeric, or a
“-”. The environment name length can be from 1 to 8 characters long.
EXTENT numeric-values
specifies primary and secondary extents to be used for the creation of the primary
log file. The primary and secondary extent values must be between 2 and 65535,
between parenthesis, and comma-separated. The default value is (100,100).
FILE-CODE numeric-value
specifies the file code to be used for the creation of the primary log file. Must be
between 0 and 65535. The default value is 0.
GENERATE-DISPLAY-EVENT on-off-value
specifies if an EMS event message is to be generated for a display type message.
The default value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS will generate an EMS event message for a display type
message.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 10
ALTER Command
Command Descriptions
OFF | FALSE
indicates that VHS will not generate an EMS event message for a display type
message.
This attribute can only be modified when the VHS-GUI-MODE is set to OFF.
GENERATE-INSPECT-EVENT on-off-value
specifies if an EMS event message is to be generated for an inspect type
message. The default value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS will generate an EMS event message for an inspect type
message.
OFF | FALSE
indicates that VHS will not generate an EMS event message for an inspect
type message.
This attribute can only be modified when the VHS-GUI-MODE is set to OFF.
GENERATE-PROMPT-EVENT on-off-value
specifies if an EMS event message is to be generated for a prompt type message.
The default value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS will generate an EMS event message for a prompt type
message.
OFF | FALSE
indicates that VHS will not generate an EMS event message for a prompt type
message.
This attribute can only be modified when the VHS-GUI-MODE is set to OFF.
MAXEXTENTS numeric-value
specifies the maximum number of extents to be used for the creation of the primary
log file. The value must be between 16 and 978.
OPEN-TABLE-THRESHOLD numeric-value
indicates the percentage of full value of the opener table at which VHS will
generate an EMS event message. The value must be between 0 and 100. The
default value is 90.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 11
ALTER Command
Command Descriptions
PRIMARY-SECURITY string-value
specifies the security string to be used for the creation of the primary log file. The
value must be between quotes. The default value is “NUUU”.
PROMPT-EVENT-RESEND-DELAY numeric-value
indicates the time delay in minutes used by VHS before resending EMS events for
unanswered prompts.
This attribute can only be modified when the VHS-GUI-MODE is set to ON.
PURGE-SAVEFILE on-off-value
specifies that VHS is to add the “force it” (!) option when sending a SAVE
command to inspect. The default value is OFF.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS will add the “force it” (!) option when sending a SAVE
command to Inspect. If the save file already exists, it will be purged before
creating the new one.
OFF | FALSE
indicates that VHS will not add the “force it” (!) option when sending a SAVE
command to Inspect.
REMOVE-EXTRA-SPACES on-off-value
specifies if an occurrence of multiple spaces is to be replaced by only one space in
the display type message. The default value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS will replace an occurrence of multiple spaces by only one
space in the display type message.
OFF | FALSE
indicates that VHS will log the display type message as received.
SUPPRESS-DISPLAY on-off-value
specifies if the EMS event messages are to appear in the Viewpoint and NonStop
NetMaster (NNM) screens. The default value is OFF.
on-off-value: [ ON | TRUE | OFF | FALSE ]
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 12
ASSIGN Command
Command Descriptions
ON | TRUE
indicates that EMS event messages will not appear in the Viewpoint and NNM
screens.
OFF | FALSE
indicates that EMS event messages will appear in the Viewpoint and NNM
screens.
VHS-LOGGER on-off-value
specifies if VHS is to log in its primary log files. The default value is ON.
on-off-value: [ ON | TRUE | OFF | FALSE ]
ON | TRUE
indicates that VHS will log in its primary log files.
OFF | FALSE
indicates that VHS will not log in its primary log files.
Considerations
•
•
If the specified CPU number is the CPU of the primary process, a warning
message is returned.
If the specified CPU number is not the CPU of the backup process or the primary
process, an error message is returned.
Examples
ALTER
ALTER
ALTER
ALTER
ALTER
ALTER
ALTER
/OUT OutAlter/
PROCESS $z123,
PROCESS $z123,
PROCESS $wawa,
PROCESS $vhs,
PROCESS $vhs,
PROCESS $vhs,
PROCESS $abc, LOG $s.#vhslog, TYPE ALL
LOG $term28, ADD
LOG $term30, ADD, TYPE DISPLAY
PRIMARY 2
LOG $term28, DELETE
REMOVE-EXTRA-SPACES ON
OPEN-TABLE-THRESHOLD 95
ASSIGN Command
The ASSIGN command changes, adds, and displays ASSIGN messages passed to a
process initiated by the VHSCI RUN command. It has the same syntax as the TACL
ASSIGN command.
ASSIGN [ logical-unit [, actual-file-name ]
[, create-open-spec ] ]
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 13
ASSIGN Command
Command Descriptions
logical-unit
specifies the name to which a file name or file attributes are assigned. logicalunit requires one of the following:
*.logical-file
program-unit.logical-file
logical-file
Both program-unit and logical-file consist of 1 to 31 alphanumeric
characters, including hyphen (-) and circumflex (^).
The exact meanings of the asterisk (*), program-unit, and logical-file
depend on the application. In general, the following is true:
•
•
•
The asterisk (*) applies the assignment to all program units in the object
program file running.
program-unit is the name, as designated in the source program, that the
file name assignment applies to.
logical-file is the name of the file as designated in the source program.
actual-file-name
specifies the name of a physical file. A partial file name is not expanded.
create-open-spec
specifies the file creation or file open specification that assigns values to certain file
attributes. The attribute specifications are separated by commas (,). The applicable
attribute specifications for create-open-spec are the following:
extent-spec
exclusion-spec
access-spec
CODE file-code
REC record-size
BLOCK block-size
extent-spec
specifies the size of the file extents allocated to the file.
EXT [(] pri-extent-size [)]
EXT ( [ pri-extent-size ] , sec-extent-size )
pri-extent-size
specifies the size of the first file extent to be allocated to the file (primary
extent). The value is an integer in the range of 1 through 65535.
sec-extent-size
specifies the size of the extents allocated to the file after the primary extent
is allocated. The value is an integer in the range from 1 through 65535.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 14
ASSIGN Command
Command Descriptions
exclusion-spec
specifies the exclusion mode for logical-unit. It determines the
circumstances in which other processes can access the file. The possible
values for exclusion-spec are the following:
EXCLUSIVE
means other processes cannot access actual-file-name while the
program containing logical-unit has the file open.
SHARED
means that other processes can both read from and write to actualfile-name while the program containing logical-unit has the file
open.
PROTECTED
means that another process can read, but not write to, actual-filename while the program containing logical-unit has the file open. See
the Enscribe Programmer’s Guide for more information about exclusion
modes.
access-spec
specifies the access mode for logical-unit. It specifies the type of file
operations that can be performed. The possible values for access-spec are
the following:
I-O
means that processes can both read the file and write to it.
INPUT
means that processes can only write to the file.
OUTPUT
means that processes can only read the file.
CODE file-code
assigns a file code to logical-unit. Specify file-code as an integer in
the range 0 through 65535. If file-code is omitted, the file code is set to 0.
REC record-size
sets the length of records in logical-unit. Specify record-size as an
integer in the range 1 through 65535.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 15
ASSUME Command
Command Descriptions
BLOCK block-size
sets the size of the data blocks used by logical-unit. Specify blocksize as an integer in the range 1 through 65535.
Considerations
•
•
•
•
•
•
•
•
•
If logical-unit is omitted, ASSIGN displays all the current assigned values.
If the actual-file-name is omitted, the current assignment value for the
logical-unit displays.
If actual-file-name is omitted but create-open-spec is included, blanks are
passed in the actual-file-name field of the ASSIGN message.
Use the CLEAR command to delete existing ASSIGN messages. See the CLEAR
command description.
There is a limit of 50 ASSIGN messages supported by VHSCI.
VHSCI creates an ASSIGN message for each ASSIGN command. A new process
must request its ASSIGN message following receipt of the startup message. All
ASSIGN messages read from TACL and the ones set in VHSCI are passed to the
new process.
The ASSIGN message resulting from entry of an ASSIGN command supersedes
any ASSIGN message read at VHSCI startup time.
The ASSIGN messages set in VHSCI are lost when exiting from VHSCI.
If the BREAK key is pressed during a VHSCI session and a new ASSIGN message
is set outside of VHSCI, VHSCI cannot receive this ASSIGN message. VHSCI
cannot pass the new ASSIGN message when it creates a process.
Examples
-> ASSIGN
-> ASSIGN
SSV0, $NEW2.T9263C20
EXTDECS, $GUESS.TOOLSC30.EXTDECS1
ASSUME Command
The ASSUME command sets the default object type, object name, or both for
subsequent commands. The default object type is used when the object type is omitted
from a command. The default object name is used when the object name is omitted
from a command. If no default object name has been established and the object name
is omitted from a command, a syntax error message occurs. A remote object name
cannot be assumed.
ASSUME [ / OUT file-spec / ] [ object-type ] [ object-name ]
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 16
ASSUME Command
Command Descriptions
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
object-type
specifies a keyword that represents the default object type.
object-name
specifies the name of the object that is to be the default object.
Considerations
•
•
•
When a VHSCI session begins, the assumed object-type and object-name
are null.
If object-type is omitted and object-name is specified, the default object-type
remains unchanged. If an object type is specified and the object name is omitted,
the default object name remains unchanged. If both object type and object name
are omitted, the assumed object type and object name become null.
When accessing remote systems, it is recommended that you change the name of
the default system using the SYSTEM command and then assume the object
name.
Examples
The following ASSUME command assigns a VHS process ($VHS) as the assumed
object. The subsequent INFO command gives information about the assumed object.
-> ASSUME PROCESS $VHS
-> INFO
Object:
.
.
.
$VHS (Appropriate Information)
If entered after the ASSUME command above, the following ASSUME command
replaces the object-name part of the assumed object. The INFO command that
follows displays information about the new assumed process.
-> ASSUME $VHS2
-> INFO
Object: $VHS2 (Appropriate Information)
.
.
.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 17
CLEAR Command
Command Descriptions
CLEAR Command
The CLEAR command clears the logical-file assignments made with the
ASSIGN command, parameters set with the PARAM command, and alias names
assigned with the ALIAS command.
CLEAR {
{
{
{
PARAM param-name
ASSIGN logical-file
ALIAS alias-name
ALL [ PARAM | ASSIGN | ALIAS ]
}
}
}
}
PARAM param-name
deletes param-name. See the description of the PARAM Command on page 7-37.
ASSIGN logical-file
deletes logical-file. See the description of the ASSIGN Command on
page 7-13.
ALIAS alias-name
deletes alias-name. See the description of the ALIAS Command on page 7-4.
ALL
deletes all logical-file assignments and parameters. Note that aliases cannot
be cleared by default; use the ALL ALIAS form to clear all aliases.
ALL PARAM
deletes all parameters set with the PARAM command.
ALL ASSIGN
deletes all ASSIGN messages defined with the ASSIGN command.
ALL ALIAS
deletes all aliases assigned by the ALIAS command.
Considerations
•
•
The TACL parameter values and ASSIGN messages read at startup can be
cleared using the CLEAR command.
This command does not affect TACL parameter values and ASSIGN messages
after you have exited from VHSCI.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 18
COMMENT Command
Command Descriptions
Examples
-> CLEAR ASSIGN SSV0
-> CLEAR ALL
COMMENT Command
The COMMENT command enables you to add descriptive text to OBEY (command)
files. Any text following this command is not evaluated.
COMMENT [ text ]
text
consists of one or more printable characters.
Consideration
This command has the same function as the double equal characters (==) appearing at
the beginning of a command line.
Examples
-> COMMENT This file contain commands for starting \COS
-> == This is also a comment.
CONFIRM Command
The CONFIRM (confirmation) command enables or disables the display of a positive
confirmation message when the last command is successfully completed. Error and
warning responses always display, regardless of whether or not confirmation
messages display.
CONFIRM [ / OUT file-spec / ] { ON } { OFF }
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
ON
enables the display of confirmation messages.
OFF
disables the display of confirmation messages.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 19
CPUS Command
Command Descriptions
Consideration
Initially, confirmation messages are not displayed.
Example
The following example shows confirmation messages that are returned as a result of
the CONFIRM ON command.
-> CONFIRM ON
CONFIRM ..... ON
-> ALTER PROCESS $VHS1, LOG $S.#VHS, ADD
ALTER accepted by VHS: PROCESS \MTL.$VHS1
-> PAGESIZE
PAGESIZE ..... -1
CPUS Command
The CPUS command displays CPU configuration, CPU status, and the operating
system version of one or all systems on the network.
CPUS [ / OUT file-spec / ] [ system-name ] [ DETAIL ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
system-name
specifies the name of the system whose CPU status displays. If system-name is
omitted, the command displays the CPU status of all systems on the network.
DETAIL
displays detailed information in addition to the summary information. See the
following description of the display format. The format of the CPUS display is in
two parts: Detailed Information and Summary Information.
Detailed Information
System
sss system
sss system
sss system
.
.
.
0--CPU States--15
nnnn,nnnn,nnnn,nnnn
nnnn,nnnn,nnnn,nnnn
nnnn,nnnn,nnnn,nnnn
OS Version
xxx
xxx
xxx
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 20
CPUS Command
Command Descriptions
Summary Information
Total
Systems
aaaaa
Connected
Systems
bbbbb
Total
CPUs
ccccc
Up
CPUs
ddddd
Explanation of Symbols
sss system
specifies the number and name of one of the systems that are now or were
once connected to the network.
nnnn,nnnn,nnnn,nnnn
specifies the status of each processor in a system.
1
indicates that the processor is active.
0
indicates it is inactive.
Period (.)
represents a nonexistent processor.
NOT CONNECTED
identifies a known system not currently connected to the network.
xxx
specifies the version of the operating system running on that system.
aaaaa
specifies the total number of systems.
bbbbb
specifies the number of connected systems.
ccccc
specifies the total number of CPUs.
ddddd
specifies the number of running CPUs.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 21
DELAY Command
Command Descriptions
Examples
-> CPUS
displays summary information about all systems on the network.
-> CPUS \C2
displays summary information about the system \C2.
-> CPUS DETAIL
displays both detailed and summary information about all systems on the network.
DELAY Command
The DELAY command suspends the VHSCI process for a specified time interval. The
DELAY command can be useful in OBEY (command) files. For example, you might
want to execute a LISTOPENS command, wait three seconds by using the DELAY
command, and then execute another LISTOPENS command.
DELAY [ / OUT file-spec / ] time
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
time
specifies the time interval during which VHSCI is to suspend processing. The
maximum quantity of time that can be specified is 5965:13:56.47. The smallest
quantity of time that can be specified is 1 second. See the Time format description
in Section 6.
Examples
-> DELAY 5
suspends VHSCI process for 5 seconds.
-> DELAY 11:22:31
suspends VHSCI process for 11 hours, 22 minutes, and 31 seconds.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 22
DETAIL ERROR Command
Command Descriptions
DETAIL ERROR Command
The DETAIL ERROR command enables or disables the display of a full error
description and suggested recovery action when an error is detected.
DETAIL ERROR [ ON | OFF ]
ON
causes the display of detailed error information.
OFF
disables the display of detailed error information.
Examples
-> DETAIL ERROR ON
-> ALTER PROCESS $VHSD, PRIMARY 15
VHS E00117 The specified CPU is not the current backup CPU or is invalid
Probable Cause
The specified CPU is not the current backup CPU of the VHS server,
or it is not a valid CPU number.
Recommended Action
Specify the current backup CPU of the VHS server.
ENV Command
The ENV (environment) command displays the VHSCI startup banner and the current
settings of the program environment parameters. You set these parameters by using
other VHSCI commands.
ENV [ / OUT file-spec / ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 23
EXIT Command
Command Descriptions
Example
-> ENV
VHSCI - T9517D21 - (21JUL96) - (VHSCI) - 07/12/96 14:44:19 System \POLLUX
Copyright Tandem Computers Incorporated 1992,1993
Allow......... ALL ERRORS
Allow......... ALL WARNINGS
Assume........ PROCESS $VHSD
Confirm....... ON
Detail Error.. ON
Log...........
In............ $ZTN0.#PTY12
Out........... $ZTN0.#PTY12
Pagesize...... 60 PRINTER
Pagesize...... 23 TERMINAL
System........ \POLLUX
Timeout ...... 0:01:30.00
Volume........ $CTTMB.JUNON
EXIT Command
The EXIT command stops VHSCI.
E[XIT]
Consideration
The end-of-file character (CTRL/Y) and the SF16 function key have the same effect as
the EXIT command.
FC Command
The FC (fix) command enables you to edit and repeat a command line. FC displays the
specified command line, up to 240 characters, and prompts for editing input with two
periods. Continued command lines (commands entered with the ampersand (&)
continuation character) display fully assembled without the ampersand.
FC [ [ - ] number ] [ character-string ]
number
if positive, is the line number of the command line to be fixed. If negative, the
current command line number minus number is the line number of the command
line to be fixed.
character-string
is the first few characters of the command line to be fixed. The most recent
command line whose first characters match the string are fixed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 24
HELP Command
Command Descriptions
Considerations
•
•
•
•
•
•
If you use FC alone, the previous command is fixed (FC alone is the same as FC
1).
If you specify a negative number and the associated command line is no longer in
the history buffer, you will get an error message. The history buffer of command
lines is 1024 bytes in length.
The FC command does not increment the command line number in VHSCI prompt.
The display of command line numbers in the prompt is controlled by the
SETPROMPT command.
FC cannot be issued by a noninteractive user and is ignored if encountered.
Another command cannot follow the FC command on the same line.
For more information on the FC command, see the NonStop Kernel Operating
System User’s Guide.
Examples
-> FC
..STARFUS PROCESS $A
DDIT
inserting
== deleting the letters RF and
== the letter T
..STATUS PROCESS $A
RVHS1
..STATUS PROCESS $VHS1
== replacing the A and spaces with VHS1
== finally, just a carriage return is
== entered, and the command is executed
HELP Command
The HELP command displays the syntax and meaning of VHSCI commands.
HELP [
[
[
[
[
[
[
/OUT file-spec/
ALL
basic-component
VHS error-number
command
object-type
object-name
]
]
]
]
]
]
]
/OUT file-spec/
directs any VHSCI output generated for this command to the specified file.
ALL
displays general information about VHSCI. This includes all available commands
and how to use the HELP command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 25
HELP Command
Command Descriptions
basic-component
describes a VHSCI syntax basic component. The basic components are as follows:
attribute-spec, character-string, command, examples, file-name,
help-key, integer, object-list, object-name, object-spec, objecttype, syntax, and time.
VHS error-number
specifies the name of the subsystem VHS and number of the error for which help is
requested.
command
specifies the name of a VHSCI command.
object-type
specifies a valid object type.
object-name
specifies an existing VHSCI supported object name.
Considerations
•
•
•
•
•
If you enter HELP, VHSCI enters a menu driven help mode that displays the
available help options. Press CTRL/Y to exit the menu driven mode.
If you enter HELP ALL, VHSCI displays information about all commands and
objects supported. HELP VHS gives the same results.
If you enter HELP command, VHSCI displays specific information about the
specified command.
If you enter HELP object-type, VHSCI displays generic information about the
specified object-type.
The menu driven mode of the HELP command cannot be invoked from an OBEY
(command) file. The HELP command entered by itself from an OBEY (command)
file produces the HELP ALL help text.
Examples
-> HELP ALL
displays general information.
-> HELP PROCESS
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 26
HISTORY Command
Command Descriptions
displays general information about the PROCESS object type.
-> HELP INFO
displays specific information about the INFO command.
HISTORY Command
The HISTORY command displays the most recently entered commands.
HISTORY [ / OUT file-spec / ] [ number ]
file-spec
directs any VHSCI output generated for this command to the specified file.
number
specifies the number of command lines to be displayed. If omitted, the 10 most
recently entered commands display.
Considerations
•
•
•
The VHSCI history buffer is 1024 bytes in memory. The exact number of
retrievable command lines depends on the length of the commands.
The command lines are saved in the history buffer exactly as they were entered,
with the exception of the FC and ! commands. The command lines generated by
these commands display instead of the commands themselves.
The HISTORY command cannot be issued by a noninteractive user.
Examples
-> HISTORY
displays the last 10 commands.
-> HISTORY 22
displays the last 22 commands.
INFO Command
The INFO command displays the current attribute values for the specified object or
objects.
INFO [ / OUT file-spec / ] [ object-spec ] [ , DETAIL ]
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 27
INFO Command
Command Descriptions
file-spec
directs any VHSCI output generated for this command to the specified file.
object-spec
designates the object or objects whose attribute values are to be displayed. If
object-spec is omitted, attribute values for the assumed object display. See the
VHSCI ASSUME command.
DETAIL
causes detailed information to be displayed. If omitted, only one line of information
is displayed for each object.
Consideration
Use the STATUS command to display dynamic information about objects.
Examples
-> INFO PROCESS $vhsd
-> INFO /OUT OutInfo/ PROCESS $vhs1, DETAIL
Output Format Without DETAIL
The display of the INFO command without the DETAIL option has the following format:
6-> INFO PROCESS $VHSD
VHS Info PROCESS running under Environment PROD
Max. prim.
Max.
Name
opens
$VHSD
512
•
•
•
•
Primary log
Prompt file
$VHS.VHSD43.LOG0012
$VHS.VHSD43.PROMPT
log files
5
Name is the name of the process object.
Primary log is the name of the primary log destination currently in use. All
messages received by the VHS process are logged in that file. The primary log
destination is always present, and has ALL as log type. If there is no primary log
destination specified when the VHS process is started, a default primary log
destination is assigned by the VHS process.
Prompt file is the name of the file that contains all prompts received by the VHS
process. The prompt file must always be present. If there is no prompt file specified
when the VHS process is started, a default prompt file is assigned by the VHS
process.
Max. prim. log files is the maximum number of primary log files that can be
created before there is a rollover and the first primary log file created purged.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 28
INFO Command
Command Descriptions
•
Max. opens is the maximum number of processes that can open the VHS process
simultaneously. If the maximum is reached, an error is returned to the process that
exceeded the limit and could not open the VHS process.
Output Format With DETAIL
The display of the INFO command with the DETAIL option has the following format:
7-> INFO PROCESS $vhsd, DETAIL
VHS Detailed Info PROCESS $VHSD running under Environment PROD
Max opens.....................
Primary log...................
Max primary log files.........
Prompt file...................
EMS collector.................
Inspect file..................
Next save file................
512
\POLLUX.$VHS.VHSD43.LOG0012
5
\POLLUX.$VHS.VHSD43.PROMPT
\POLLUX.$
\POLLUX.$VHS.VHSD43.VHSINSP
\POLLUX.$VHS.VHSD43.SAVE0000
Accept-ext-ascii-character....
Add-text-to-event.............
Automatic-inspect-processing..
Backup-creation-message-delay.
Environment-name..............
File-code.....................
Generate-display-event........
Generate-inspect-event........
Generate-prompt-event.........
Maxextents....................
Open-table-threshold..........
Primary, secondary-extent.....
Primary-security..............
Prompt-event-resend-delay.....
Purge-savefile................
Remove-extra-spaces...........
Saveabend-file................
Suppress-display..............
Vhs-GUI-mode..................
Vhs-logger....................
OFF
ON
ON
5
PROD
0
ON
ON
ON
16
90
(5,5)
NNNN
15
OFF
ON
ON
OFF
ON
ON
Logs:
*LogName
\POLLUX.$VHS.VHSD43.LOG0012
(P)
*LogType
ALL
Note. The asterisk (*) beside LogName and LogType indicates attributes that you can alter by
using the ALTER command. You can change the attributes of the secondary log destination
only. You cannot change the attributes of the primary log.
•
•
Max opens is the maximum number of processes that can open the VHS process
simultaneously. If the maximum is reached, an error is returned to the process that
exceeded the limit and could not open the VHS process.
Primary log is the name of the primary log destination currently in use. All
messages received by the VHS process are logged in that file. The primary log
destination is always present, and has ALL as log type. If there is no primary log
destination specified when the VHS process is started, a default primary log
destination is assigned by the VHS process.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 29
INFO Command
Command Descriptions
•
•
•
•
•
•
•
•
•
•
•
Max. primary log files is the maximum number of primary log files that can be
created before there is a rollover and the first primary log file created is purged.
Prompt file is the name of the file which contains all prompts received by the VHS
process. The prompt file must always be present. If there is no prompt file specified
when the VHS process is started, a default prompt file is assigned by the VHS
process.
Next save file is the name of the next saveabend file to be created (when a
process traps into Inspect, VHS creates this saveabend file).
Accept-ext-ascii-character allows the VHS process to accept or not accept nonASCII characters. If the Accept-ext-ascii-character is set to ON, VHS accepts nonASCII characters. If Accept-ext-ascii-character is set to OFF, VHS does not accept
non-ASCII characters. By default VHS sets Accept-ext-ascii-character to OFF.
Add-text-to-event is the parameter that specifies if the token text is to be added to
all EMS events. If the Add-text-to-event is set to ON, VHS will add the token text to
all EMS event messages. If Add-text-to-event is set to OFF, VHS will not add the
token text to all EMS messages. By default VHS sets Add-text-to-event to ON.
Automatic-inspect-processing specifies if VHS is to process Inspect prompts or
let the user manage them via the VHS Prompt Browser screen. When Automaticinspect-processing is ON, VHS automatically handles Inspect prompts. When
Automatic-inspect-processing is OFF, VHS does not process Inspect prompts; they
will be managed via the VHS Prompt Browser screen. By default VHS sets
Automatic-inspect-processing to ON.
Backup-creation-message-delay is the delay in minutes between each
occurrence of the backup creation failure message. The delay must be between 0
and 999. If there is no delay specified, the default delay is 5 minutes.
Environment-name is the name of the VHS process environment. The string
value assigned to Environment-name must be between quotes ( " ). The first
character must be alphabetic. All other characters can be alphabetic or numeric or
a “-”. The environment name length can be from 1 to 8 characters long.
File-code is used for the primary log file creation. The numeric value assigned to
File-code must be between 0 and 65535. If there is no numeric value assigned
then the default value is 0.
Generate-display-event specifies if an EMS event message is to be generated for
a display type message. When Generate-display-event is set to ON, VHS
generates EMS events for display type messages. When Generate-display-event
is set to OFF, VHS does not generate EMS events for display type messages. By
default VHS sets Generate-display-event to ON.
Generate-inspect-event specifies if an EMS event message must be generated
for Inspect type messages. When Generate-inspect-event is set to ON VHS
generates EMS events for Inspect type messages. When Generate-inspect-event
is set to OFF VHS does not generate EMS events for Inspect type messages. By
default VHS sets Generate-inspect-event to ON.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 30
INFO Command
Command Descriptions
•
•
•
•
•
•
•
•
•
•
Generate-prompt-event specifies if an EMS event message must be generated
for a prompt type message. When Generate-prompt-event is set to ON, VHS
generates EMS events for prompt type messages. When Generate-prompt-event
is set to OFF, VHS does not generate EMS events for prompt type messages. By
default VHS sets Generate-prompt-event to ON.
Maxextens is the maximum number of extents to be used for the primary log file
creation. The numeric value assigned to Maxextents must be between 16 and 978.
If there is no value specified, the default maximum number of extents is 16.
Open-table-threshold is the percentage that represents the full value of the
opener table where VHS will generate an EMS event message. The numeric value
assigned to Open-table-threshold must be between 0 and 100. If there is no value
specified, the default value is 90.
Primary-security is used for the primary log file creation. The string value
assigned to Primary-security must be between quotes ( " ). If there is no value
specified the default value is “NUUU”.
Prompt-event-resend-delay specifies the time (in minutes) VHS will wait before
generating a repeat event for an unanswered prompt. This parameter is ignored if
VHS-GUI-MODE is set to OFF. The possible values are from 1 to 60.
Purge-savefile specifies if VHS should add the “force it” (!) option when sending a
SAVE command to Inspect. When Purge-savefile is set to ON, VHS adds the
“force it” (!) option when sending a SAVE command to Inspect. If the save file
already exists, it will be purged before creating the new one. When Purge-savefile
is set to OFF, VHS will not add the “force it” (!) option when sending a SAVE
command to Inspect. By default VHS sets Purge-savefile to OFF.
Remove-extra-spaces specifies if an occurrence of multiple spaces must be
replaced by only one space in the display type message. When Remove-extraspaces is set to ON, VHS replaces an occurrence of multiple spaces by only one
space in the display type message. When Remove-extra-spaces is set to OFF,
VHS logs the display type message as received. By default VHS sets Removeextra-spaces to ON.
Suppress-display specifies if EMS event messages are to appear in the
Viewpoint and NonStop NetMaster (NNM) screens. When Suppress-display is set
to ON, EMS events will not appear in the ViewPoint and NNM screens. When
Suppress-display is set to OFF, EMS events will appear in the ViewPoint and NNM
screens. By default VHS sets Suppress-display to OFF.
Vhs-GUI-mode specifies whether the VHS program will provide the VHS GUI
application with the proper events. Valid parameter values are ON or OFF. Refer to
Section 8, The VHS GUI, for more detail.
Vhs-logger specifies if VHS is to log in its primary log file. When Vhs-logger is set
to ON, VHS logs in its primary log files. When Vhs-logger is set to OFF, VHS does
not log in its primary log files. By default VHS sets Vhs-logger to ON.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 31
LISTOPENS Command
Command Descriptions
•
•
LogName is the list of the current log destination names (the primary log
destination is marked with a (P) ).
LogType is the list of the current log destination types associated with the names.
LISTOPENS Command
The LISTOPENS command lists all processes which currently open the specified
object or objects.
LISTOPENS [ / OUT file-spec / ] [ object-spec ] [, open-mode
]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
object-spec
designates the object whose openers are to be displayed. If object-spec is
omitted, the openers of the assumed object are listed (see the VHSCI ASSUME
command).
open-mode
designates an open mode to select specific opener processes. Mode is one of the
following values:
[ INSPECT | DEBUG | DISPLAY | PROMPT | UNKNOWN | PSERVER ]
INSPECT
lists all opener processes that prompted the specified object with an Inspect
prompt.
DEBUG
lists all opener processes that prompted the specified object with a Debug
prompt.
DISPLAY
lists all opener processes that displayed to the specified object.
PROMPT
lists all opener processes that prompted the specified object.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 32
LISTOPENS Command
Command Descriptions
UNKNOWN
lists all opener processes that opened the specified object with no other
information.
PSERVER
lists all VHS prompt servers that opened the specified object.
Consideration
•
•
If there are no current openers, a warning is returned.
VHS cannot be opened by remote processes. VHS can only be opened by local
processes.
Examples
LISTOPENS PROCESS $vhs1
LISTOPENS /OUT OutListo/ PROCESS $vhs2, PROMPT
LISTOPENS PROCESS $vhs1, DISPLAY
Output Format
The display of the LISTOPENS command has the following format:
10-> LISTOPENS PROCESS $vhsd
VHS ListOpens PROCESS $VHSD running under Environment PROD
Process
$JUNE
$DISP
•
•
•
•
•
Open
Objname
Mode
$SYSTEM.SYS00.FUP
PROMPT
$VHS.T9517QA.DISP512 DISPLAY
Time of
Time of
open
last message
10Jul96,11:55:34 13Jul96,11:45:26
10Jul96,11:55:42 13Jul96,12:55:28
Process is the name of a process which currently opens the VHS process as a
home terminal.
Objname is the program file name of the process which currently has the VHS
process open.
Mode is the type of message the opening process sends to the VHS process; it is
the reason why the VHS process was opened.
Time of open is the timestamp indicating when this process opened the VHS
process.
Time of last message is the timestamp indicating when the VHS process received
the last message from this process.
Note. All timestamps in VHS are in local civil time (LCT).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 33
LOG Command
Command Descriptions
LOG Command
The LOG command directs a copy of the input commands and the output generated by
VHSCI to a file.
LOG [ logfile-spec [ ! ] ]
logfile-spec
if present, specifies the file to which the commands and output are written. If the
logfile-spec has the form of a disk file name and the file does not exist, an
EDIT file is created. If the named file is an existing disk file, the information is
appended to the file. If logfile-spec is omitted, all logging stops and the log file
is closed.
!
purges the specified file and creates a new file of the same name. If this option is
not specified, VHSCI appends the log information to the end of the existing file.
Considerations
•
•
•
If logfile-spec is specified when logging is already in progress, the current log
file is closed and logging begins to the new file.
The log file cannot have the same name as the OUT file. See the description of the
OUT command.
Logging does not interfere with the writing of output or the collection of input.
Examples
-> LOG $DATA.AUDIT.OCT14
-> LOG
OBEY Command
The OBEY command causes commands to be read from a specified file (an OBEY
(command) file). OBEY commands can appear within an OBEY (command) file. OBEY
(command) files can be nested to a depth of ten.
Commands are read from the named file and processed until the end of the file, an
EXIT command, or an error is encountered. If the end of file is encountered, command
processing continues from the previous input source. If the maximum number of errors
or warnings set by the ALLOW command is exceeded, the current OBEY (command)
file and all previously opened OBEY (command) files close. Command input reverts to
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 34
OBEY Command
Command Descriptions
interactive mode. If VHSCI was started with a disk file specified as the IN file (that is, if
VHSCI was not run in interactive mode), VHSCI terminates.
O[BEY] [ / OUT file-spec / ] file-spec [, NOECHO ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
file-spec
specifies the file from which the commands are to be read. If file-spec is not
fully qualified, the name is expanded using the default values supplied by the
SYSTEM and VOLUME commands.
NOECHO
suppresses the echo of each line executed in the OBEY (command) file. Use this
option when speed is important.
Considerations
•
•
•
•
•
FC, HISTORY, PAUSE, exclamation point (!), and question mark (?) commands
cause an error if they are encountered in an OBEY (command) file.
OBEY (command) file processing stops when the number of allowed errors or
warnings is exceeded. The number of allowed errors and warnings is set by the
ALLOW command.
OBEY commands can appear within OBEY (command) files. OBEY (command)
files can be nested to a depth of ten. If a depth of ten is exceeded, the file is not
executed and an error message displays.
Commands are read considerably faster when NOECHO is specified. However, in
this case, only error messages are returned, not the command lines that caused
the errors.
The menu driven mode of the HELP command cannot be invoked from an OBEY
(command) file. The HELP command entered by itself from an OBEY (command)
file produces the HELP ALL help text.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 35
OUT Command
Command Descriptions
Examples
-> OBEY STARTUP.NET
-> OBEY NET
OUT Command
The OUT command directs the display output to a specified file (the OUT file).
OUT [ file-spec [ ! ] ]
file-spec
specifies the file to which the output listing is written to. If file-spec has the form
of a disk file name and the file does not exist, an EDIT file is created. If the named
file is an existing disk file, the output is appended to the file. If file-spec is
omitted, the output destination is restored to the setting it had at startup time.
!
purges the specified file and creates a new file of the same name. If this option is
not specified, VHSCI appends the output to the end of the existing file.
Consideration
The OUT file cannot have the same name as the log file. See the description of the
LOG command.
Examples
->
->
->
->
->
->
->
== Send the output of the INFO command to a disk file.
OUT $OPS.TEMP.INFO
INFO PROCESS $VHS1
OUT
== The same result is achieved with the following
== command.
INFO /OUT $OPS.TEMP.INFO/ PROCESS $VHS1
PAGESIZE Command
The PAGESIZE command designates the size of a printed page or of a display page
on the terminal screen. When a page of data displays on a terminal, VHSCI stops at
the end of the page and requests that the display continues or stops. Pressing the
Return key continues the display. This enables you to read each screen.
PAGESIZE [ integer ] [ TERMINAL ]
[ PRINTER ]
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 36
PARAM Command
Command Descriptions
integer
specifies the size of the printer or terminal page. If integer is in the range 2
through 255, VHSCI displays integer-1 lines before providing a page break. If
integer is omitted or has the value -1, VHSCI cannot provide a page break. The
default page size is 60 lines for a printer and 23 lines for a terminal.
TERMINAL
specifies that the terminal page size is being designated.
PRINTER
specifies that the printer page size is being designated.
Considerations
•
•
If both TERMINAL and PRINTER are omitted, TERMINAL is assumed.
When the current output file is a spooler destination, the VHSCI banner is
displayed at the beginning of each page; these banner lines are not included in the
number of lines you specify as PRINTER option.
Examples
-> PAGESIZE 20
-> PAGESIZE
PARAM Command
The PARAM command enables you to change, add, and display PARAM values that
are passed to a process initiated by the VHSCI RUN command.
PARAM [ param-name [ param-value ] ]
param-name
specifies a user-defined name to be assigned a value. The name contains from
1 to 31 alphanumeric characters, including hyphen (-) and circumflex (^).
param-value
specifies the value assigned to param-name.
Considerations
•
•
Leading and trailing blanks are deleted in the param-value.
VHSCI reserves 1024 bytes of internal storage for parameters and their values.
This limits the number and length of parameters.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 37
PAUSE Command
Command Descriptions
•
•
•
•
•
•
•
•
If both param-name and param-value are omitted, all current PARAM values
display.
If param-value is omitted, the current PARAM value associated with paramname displays.
The PARAM command supersedes any PARAM specification for the same paramname that was read at VHSCI startup time.
Use the CLEAR command to delete existing PARAM values. Refer to the CLEAR
command description.
A new process must request its PARAM message following receipt of the startup
message. The PARAM values read from TACL and the ones set in VHSCI are
passed to the new process.
The PARAM values set in VHSCI are lost when you exit from VHSCI.
If the Break key is pressed during a VHSCI session and a new PARAM value is set
outside of VHSCI, VHSCI does not receive this PARAM value. VHSCI cannot pass
on the new PARAM value when it creates a process.
Another command cannot follow the PARAM command on the same line.
Examples
-> PARAM VHSCI^DEBUG^ENABLE ON
-> PARAM
PARAM VHSCI^DEBUG^ENABLE
.ON.
PAUSE Command
The PAUSE command suspends VHSCI and allows the terminal to be used by another
process. When you invoke a process during a VHSCI session through the RUN
command, you can use the Break key to reactivate VHSCI. Once in VHSCI, you can
use the PAUSE command to allow access to the terminal by the other process.
PAUSE
Consideration
The PAUSE command can be issued only by an interactive user.
REPEAT Command
The REPEAT command causes the remainder of the command line to be repeated for
the number of iterations specified or until the Break key is pressed if none is specified.
REPEAT [ / OUT file-spec / ] [ count ] command-line
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 38
RUN Command
Command Descriptions
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
count
specifies the number of times the command-line is executed. If omitted, the
command-line is executed until the Break key is pressed, or the process is sent
a WAKE message, or the process is terminated.
command-line
specifies one or more VHSCI commands separated by semicolons (;).
Considerations
•
•
Only one REPEAT command can appear on a command line. To obtain multiple
levels of iteration, use REPEAT commands within OBEY (command) files.
Alias names following a REPEAT command must be prefaced with a hyphen (-).
Only aliases at the beginning of the line are expanded by default. For more
information, see the ALIAS command.
Examples
-> REPEAT 5 STATUS PROCESS $VHS1; DELAY 2:00
-> ALIAS LISTO LISTOPENS PROCESS $VHS1
-> REPEAT DELAY 5:00 -LISTO
RUN Command
The RUN command initiates the execution of other programs from VHSCI. Many
programs can be run from VHSCI, including EDIT, PUP, CUP, FUP, ERROR,
NETMON, and DIAG6100. VHSCI is suspended while the other program runs, and
reactivates when the other program terminates. To enter Debug on the first executable
instruction of the program, use RUND.
RUN[D] [ / OUT file-spec / ] file-spec [ /run-options/ ]
[ parameter-string ]
OUT file-spec
directs any VHSCI output generated for this command to the specified file.
file-spec
specifies the file name of the program to be executed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 39
SETPROMPT Command
Command Descriptions
/run-options/
specifies a list of one or more RUN options.
parameter-string
specifies a list of run parameters to be passed to the initiated program. All text
following the program file name is assumed to be part of the parameter string.
Continuation lines can be used.
Considerations
•
The keyword RUN can be left off the RUN command if the file name is not the
same as a valid VHSCI command and if the program file is located in either the
$SYSTEM.SYSnn or the $SYSTEM.SYSTEM subvolume. VHSCI runs the
program on $SYSTEM.SYSTEM if the program exists on both subvolumes.
•
If the keyword RUN is included, VHSCI looks for the program file on the default
volume and subvolume only.
•
•
•
The RUN command must be the last command on the command line.
TACL ASSIGN messages and PARAM values are passed to the created process.
Process creation precedes abbreviation expansion. For example, if a program file
named VER exists on the subvolume $SYSTEM.SYSTEM, the abbreviation VER
(for VERSION) runs the program file VER rather than executing the VERSION
command.
Examples
->
->
->
->
RUN MYPROG /NOWAIT/
CUP /IN INFILE, OUT $S.#LP1/
EDIT FILE1;XVS F
ERROR 48
SETPROMPT Command
The SETPROMPT command enables you to choose the prompt setting.
SETPROMPT [ / OUT file-spec / ]
{ [ NO ] prompt-option [, [ NO ] prompt-option ] ... }
{ ALL [, [ NO ] prompt-option ] ...
}
{ NONE [, prompt-option ] ...
}
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 40
SETPROMPT Command
Command Descriptions
NO
disables the following prompt-option.
prompt-option
specifies one of the following keywords:
{
{
{
{
{
{
DIM
NUMBER
OBJECT
REVERSE
SYSTEM
VOLUME
}
}
}
}
}
}
DIM
displays the prompt in dim video.
NUMBER
displays the command line number.
OBJECT
displays the assumed object-type and object-name. See the ASSUME
command.
REVERSE
displays the prompt in reverse video.
SYSTEM
displays the current system name.
VOLUME
displays the default volume and subvolume names.
ALL
enables all prompt-options.
NONE
disables all prompt-options.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 41
STATS Command
Command Descriptions
Considerations
•
The REVERSE and DIM options can be used only on a Tandem 6530 or 6520
terminal or a device operating as a 6530 emulator. If these options are enabled on
any other terminal, the following error message displays:
VHS 20210 Invalid terminal type for REVERSE and/or DIM
option.
•
•
If the NONE option is specified, all the prompt-options are returned to their
default settings.
By default, the prompt-option NUMBER is enabled and all others are disabled.
Examples
-> assume process $vhs
-> setprompt all, no volume
\SYS1 PROCESS $VHS1 3-> setprompt no object, no number
\SYS1 -> setprompt volume
\SYS1 $DATA.MYSUBVOL ->
STATS Command
The STATS command displays statistical information for the specified object or objects.
STATS [ / OUT file-spec / ]
[ object-spec ]
[ , RESET ]
file-spec
causes any VHSCI output generated for this command to be directed to the
specified file.
object-spec
designates the object or objects whose statistical information is displayed. If
object-spec is omitted, the statistics for the assumed object display (see the
VHSCI ASSUME command).
RESET
if present, resets all the statistics counters to zero after the statistics are displayed.
Consideration
VHS has a safeguard to ensure the counter values do not become too large; this is
implemented as an automatic reset of all counters. If a counter is reset, a message
describing the action is logged in the primary log destination.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 42
STATS Command
Command Descriptions
Examples
STATS PROCESS $vhsd
STATS /OUT OutStats/ PROCESS $vhs1, RESET
Output Format
The display of the STATS command has the following format:
8-> STATS PROCESS $VHSD
VHS Stats PROCESS $VHSD running under Environment PROD
Started.... 10Jul96,11:54:47
Last reset. 11Jul96,10:48:28
Number of messages/log:
#Outstd.
prompt
$VHS.VHSD43.LOG0016
1
•
•
•
•
•
•
•
•
•
Total opens since last reset.... 1
Total messages since last reset. 3025
#Inspect
(P)
0
#Debug
0
#Display
3024
#Prompt
1
Started is the timestamp indicating when the VHS process was started.
Tot. opens since last reset is the total number of processes that have opened the
VHS process since the last reset occurred.
Last reset is the timestamp indicating when the statistics of the VHS process were
last reset.
Total messages since last reset is the total number of messages received by the
VHS process since the last reset of statistics.
#Inspect is the number of processes that have opened the VHS process which
were trapped into Inspect. If a dash appears, this secondary log destination does
not log these type of messages.
#Debug is the number of processes that have opened the VHS process which
were trapped into Debug. If a dash appears, this secondary log destination does
not log this type of message.
#Display is the number of displays or writes that have been issued to the VHS
process by applications. If a dash appears, this secondary log destination does not
log this type of message.
#Prompt is the number of writeread issued to the VHS process by applications. If
a dash appears, this secondary log destination does not log this type of message.
#Outstanding prompt is a subset of the number of prompts. It includes all
unanswered prompts; that is, the ones that have not been replied to.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 43
STATUS Command
Command Descriptions
STATUS Command
The STATUS command displays status information about the specified object or
objects.
STATUS [ / OUT file-spec / ] [ object-spec ] [ , DETAIL ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
object-spec
designates the object(s) whose dynamic information displays. If object-spec is
omitted, dynamic information for the assumed object displays. See the ASSUME
command.
DETAIL
if present, returns detailed status information. If DETAIL is omitted, a single line of
data returns for each object name.
Consideration
To display only the configuration information for each object, use the INFO command.
INFO does not display dynamic information.
Examples
STATUS PROCESS $vhsd
STATUS /OUT OutStus/ PROCESS $vhs1, DETAIL
Output Format Without DETAIL
The display of the STATUS command without the DETAIL option has the following
format:
9-> STATUS PROCESS $vhsd
VHS Status PROCESS running under Environment PROD
Name
$VHSD
•
•
PPID
01,52
BPID
00,36
Primary log
$VHS.VHSD43.LOG0016
Prompt file
$VHS.VHSD43.PROMPT
Name is the name of the process object.
PPID is the primary process ID (CPU number and process number) of the VHS
process.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 44
STATUS Command
Command Descriptions
•
•
•
BPID is the backup process ID (CPU number and process number) of the VHS
process.
Primary log is the name of the primary log destination currently in use. All
messages received by the VHS process are logged in that file. The primary log
destination is always present, and has ALL as log type. If there is no primary log
destination specified when the VHS process is started, a default primary log
destination is assigned by the VHS process.
Prompt file is the name of the file which contains all prompts received by the VHS
process. The prompt file must always be present. If there is no prompt file specified
when the VHS process is started, a default prompt file is assigned by the VHS
process.
Output Format With DETAIL (No Secondary Log)
When no secondary log is configured, the display of the STATUS command with the
DETAIL option has the following format:
10-> STATUS PROCESS $vhsd, DETAIL
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD43.LOG0016
$VHS.VHSD43.PROMPT
$VHS.VHSD43.SAVE0000
10Jul96,11:54:47
1
29
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.LOG0016
13Jul96,10:04:40
13Jul96,13:27:36
0
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
Prompt file:
Name..........
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.PROMPT
04Jul96,11:02:17
13Jul96,11:45:27
0
Extents....... (100,100,100)
Owner........... 215,4
Security (RWEP). NNNN
•
•
•
•
(6,6,16)
215,4
NNNN
67%
PPID is the primary process ID (CPU number and process number) of the VHS
process.
Primary log is the name of the primary log destination currently in use. All
messages received by the VHS process are logged in that file. The primary log
destination is always present, and has ALL as its log type. If there is no primary log
destination specified when the VHS process is started, a default primary log
destination is assigned by the VHS process.
BPID is the backup process ID (CPU number and process number) of the VHS
process.
Prompt file is the name of the file which contains all prompts received by the VHS
process. The prompt file must always be present. If there is no prompt file specified
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 45
STATUS Command
Command Descriptions
when the VHS process is started, a default prompt file is assigned by the VHS
process.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
APID is the ancestor process ID (CPU number and process number) of the VHS
process.
Next save file is the name of the next saveabend file to be created (when a
process traps into Inspect, VHS creates this saveabend file).
Primary CPU is the CPU number where the primary VHS process is currently
running.
Started is the timestamp indicating when the VHS process was started.
Save files created is the number of saveabend files created since the last reset of
statistics.
Tot. opens since reset is the total number of processes that have opened the
VHS process since the last reset of statistics.
Current opens is the number of processes which currently open the VHS process.
Tot. events generated is the total number of events the VHS process has
generated since the last reset of statistics.
Name is the name of the file for which status information is displayed.
Extents is the value of the primary extents, secondary extents, and maximum
extents for the file.
Creation Date is a timestamp indicating when the file was created.
Owner is the user group and number associated with the file.
Last Modif is a timestamp indicating when the file was last modified.
Security is the security attributes (RWEP) associated with the file.
Last error is the number of the last file system error that has occurred on that log
destination. A file system error “0” indicates that no error occurred.
EOF (% full) is a percentage value indicating how full the file is. This value applies
to the primary log destination and to the secondary log destination if it is a disk file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 46
STATUS Command
Command Descriptions
Output Format With DETAIL (Secondary Log Is a Disk File)
When the configured secondary log is a disk file, the display of the STATUS command
with the DETAIL option has the following format:
10-> STATUS PROCESS $vhsd, DETAIL
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD43.LOG0016
$VHS.VHSD43.PROMPT
$VHS.VHSD43.SAVE0000
10Jul96,11:54:47
1
29
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.LOG0016
13Jul96,10:04:40
13Jul96,14:20:51
0
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(6,6,16)
215,4
NNNN
81%
Secondary log:
Name..........
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.LOGSEC1
13Jul96,14:21:14
13Jul96,14:21:14
0
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(20,100,16)
215,4
NNNN
0%
$VHS.VHSD43.PROMPT
Extents.........
04Jul96,11:02:17
13Jul96,11:45:27
0
Owner........... 215,4
Security (RWEP). NNNN
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
See Output Format With DETAIL (No Secondary Log) on page 7-45 for an explanation
for each field.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 47
STATUS Command
Command Descriptions
Output Format With DETAIL (Secondary Log Is a Terminal)
When the configured secondary log is a terminal, the display of the STATUS command
with the DETAIL option has the following format:
10-> STATUS PROCESS $vhsd, DETAIL
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.LOG0016
13Jul96,10:04:40
13Jul96,14:36:04
0
Secondary log:
Name..........
Last Access...
Last error....
Creation Date.
Last Modif....
Last error....
$ZTN0.#PTY10
13Jul96,14:36:09
40
04Jul96,11:02:17
13Jul96,11:45:27
0
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.LOG0016
$VHS.VHSD43.PROMPT
$VHS.VHSD43.SAVE0000
10Jul96,11:54:47
1
29
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(6,6,16)
215,4
NNNN
85%
Owner........... 215,4
Security (RWEP). NNNN
$VHS.VHSD43.PROMPT
Extents.........
04Jul96,11:02:17
13Jul96,11:45:27
0
Owner........... 215,4
Security (RWEP). NNNN
See Output Format With DETAIL (No Secondary Log) on page 7-45 for an explanation
for each field except Last Access:
•
Last Access is a timestamp indicating when the file was last accessed. This value
applies only to terminal and spooler secondary log destinations.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 48
SYSTEM Command
Command Descriptions
Output Format With DETAIL (Secondary Log Is a Spooler)
When the configured secondary log is a spooler destination, the display of the STATUS
command with the DETAIL option has the following format:
10-> STATUS PROCESS $vhsd, DETAIL
VHS Detailed Status PROCESS $VHSD running under Environment PROD
PPID...............
BPID...............
APID...............
*Primary CPU.......
Save files created.
Current opens......
Primary log:
Name..........
Creation Date.
Last Modif....
Last error....
01,52
00,36
03,17
1
0
2
Primary log...........
Prompt file...........
Next save file........
Started...............
Tot.opens since reset.
Tot.events generated..
$VHS.VHSD43.LOG0016
13Jul96,10:04:40
13Jul96,14:43:40
0
$VHS.VHSD43.LOG0016
$VHS.VHSD43.PROMPT
$VHS.VHSD43.SAVE0000
10Jul96,11:54:47
1
29
Extents.........
Owner...........
Security (RWEP).
EOF (% Full)....
(6,6,16)
215,4
NNNN
88%
Secondary log:
Name.......... $S.#VHSLOG
Last Access... 13Jul96,14:44:30
Last error.... 0
Prompt file:
Name..........
(100,100,100)
Creation Date.
Last Modif....
Last error....
$VHS.VHSD43.PROMPT
Extents.........
04Jul96,11:02:17
13Jul96,11:45:27
0
Owner........... 215,4
Security (RWEP). NNNN
See Output Format With DETAIL (No Secondary Log) on page 7-45 and Output
Format With DETAIL (Secondary Log Is a Terminal) on page 7-48 for an explanation of
all fields.
SYSTEM Command
The SYSTEM command designates the default system name for all file name and
object name expansion.
SYSTEM [ / OUT file-spec / ] [ \system-name ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
\system-name
specifies the system name that is to become the default system name. If \systemname is omitted, the system name from the beginning of the VHSCI session is
used.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 49
TIMEOUT Command
Command Descriptions
Consideration
When a VHSCI session begins, the default system name is the system name obtained
from the startup message.
Examples
-> SYSTEM \B7
-> SYSTEM \SD
-> SYSTEM
TIMEOUT Command
The TIMEOUT command enables you to change the amount of time VHSCI waits for a
response from a VHS process before canceling the request. There might be a delay in
VHS server response, a normal situation in requester-server communication. The
TIMEOUT value ensures that if VHS receives hundreds of requests at the same time,
including a request from VHSCI, the request will not time out before getting an answer.
TIMEOUT [ / OUT file-spec / ] [ time ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
time
designates the amount of time VHSCI waits for a response from a VHS process. If
time is omitted, VHSCI waits 90 seconds. The maximum amount of time that can
be specified is 5965:13:56.47. The smallest amount of time that can be specified is
1.00 second.
Consideration
TIMEOUT functions in the same manner as pressing the Break key: it cancels any
outstanding operation. Use this command with caution.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 50
VERSION Command
Command Descriptions
Examples
-> TIMEOUT 5
-> TIMEOUT 11:22:31
-> TIMEOUT
! 5 seconds
! 11 hours, 22 minutes and 31 seconds
! -1 (no timeout)
VERSION Command
The VERSION command displays the version level of the specified object or objects.
VERSION [ / OUT file-spec /] [ object-spec ] [, DETAIL ]
/ OUT file-spec /
causes any VHSCI output generated for this command to be directed to the
specified file.
object-spec
designates the object or objects whose version level is to be displayed. If objectspec is omitted, version level for the assumed object displays. See the ASSUME
command.
DETAIL
designates that complete version information is to be returned for the specified
object or objects. If DETAIL is omitted, a single line of version information is
returned for the specified object or objects.
Consideration
The version level of VHSCI displays in the startup banner and when the ENV
command is executed.
Examples
VERSION PROCESS $vhs1
VERSION /OUT OutVers/ PROCESS $vhs2, DETAIL
Output Format Without DETAIL
The display of the VERSION command without the DETAIL option has the following
format:
11-> VERSION PROCESS $vhsd
VERSION PROCESS \POLLUX.$VHSD: VHS - T9517D21 - (21JUL96) - (VHS)
•
VHS is the product name.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 51
VOLUME Command
Command Descriptions
•
•
T9517D21 is the product number.
21JUL96 is the product release date.
Output Format With DETAIL
The display of the VERSION command with the DETAIL option has the following
format:
12-> VERSION PROCESS $vhsd, DETAIL
Detailed VERSION PROCESS \POLLUX.$VHSD running under Environment PROD
SYSTEM \POLLUX
NonStop Kernel - T9050 - (N20)
VHSCI - T9517D21 - (21JUL96) - (VHSCI)
VHS
- T9517D21 - (21JUL96) - (VHS)
VOLUME Command
The VOLUME command designates the default volume and subvolume names for
expansion of all file names.
VOLUME [ / OUT file-spec /
[ $volume-name [ . subvolume-name ]
[ subvolume-name
]
]
]
/ OUT file-spec /
directs any VHSCI output generated for this command to the specified file.
$volume-name
specifies the name of the volume that is to become the default volume.
subvolume-name
specifies the name of the subvolume that is to become the default subvolume.
Considerations
•
•
•
When a VHSCI session begins, the current volume and subvolume are the default
values used by the NonStop Kernel command interpreter through which VHSCI
was invoked.
If volume-name is omitted and subvolume name is specified, the current default
volume remains unchanged. Similarly, if volume-name is specified and
subvolume-name is omitted, the current default subvolume remains unchanged.
If both are omitted, the default volume and subvolume are restored to their initial
settings from the beginning of the VHSCI session.
A system name cannot be specified in the VOLUME command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 52
VOLUME Command
Command Descriptions
Examples
-> VOLUME $MKT
-> VOLUME $MKT.ABC
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 53
VOLUME Command
Command Descriptions
Virtual Hometerm Subsystem (VHS) Manual—429311-001
7- 54
8
The VHS GUI
Introduction to the VHS GUI
This section describes the architecture and the features available with the VHS GUI. It
contains steps on how to install and start the VHS GUI. It also contains the information
that you need to know when you configure the host part of the VHS GUI. For more
information regarding the client part of the VHS GUI, read the readme file and online
help available on the workstation.
VHS GUI Overview
The VHS graphical user interface (GUI) provides an interface to NonStop VHS. It acts
as a virtual home terminal for applications to receive and log messages, thereby
providing easy access to system operators. The VHS GUI provides centralized
preprompt message and prompt management; real-time management views; and
automatic host communication using CSG/SSG over TCP/IP or asynchronous
communication links.
The VHS GUI can be customized in a variety of ways. It permits you to navigate
preprompt and prompt messages, and to reply to prompts. It allows you to customize
displays, including detailed field and attribute specifications for messages and prompts.
It also has the ability to isolate the preprompt messages and prompts of a specific
application process from those of other processes in the view.
The VHS GUI runs on workstations running Window NT connected via an
asynchronous or TCP/IP communications link to one NonStop Kernel system at a time.
The VHS GUI also uses the services of the SeeView Server Gateway. In order to
communicate with your Compaq node, it is necessary to install the SeeView Server
Gateway on your central Compaq node.
Host Installation Requirements
NonStop VHS product T9517D43 and the EMS Distributor product T9632AAW should
both be installed on each NonStop Kernel system that will use the VHS GUI. Refer to
Section 2, Installing VHS, for a detailed description of how to install the NonStop VHS
product.
The SSG product T8488D42 should be installed on the central node of the NonStop
Kernel system. It does not need to be installed on each node.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -1
VHS GUI Architecture
The VHS GUI
VHS GUI Architecture
The following figure depicts the architecture of the VHS GUI services.
Figure 8-1. VHS GUI Architecture
Workstation
Compaq Server - Central Node
Applications
VHS GUI
VHS GUI
Agent
CSG
SSG
VHS
Process
EMS
Bdist
EMS
Collector
EMS
Logs
EMS
Collector
Applications
VHS
Process
EMS
Forward
EMS
Logs
Compaq Server - Remote Node
VST081.vsd
Windows NT Workstation
Following are descriptions of the workstation applications running Windows NT
depicted in Figure 8-1.
VHS GUI
The VHS GUI provides the facility to browse and to reply to VHS prompts based on
VHS EMS events.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -2
Compaq Server - Central Node
The VHS GUI
CSG
The Client Server Gateway (CSG) provides a bridge between programs running on
Windows NT workstations and programs running on the Nonstop Kernel systems.
Compaq Server - Central Node
Following are descriptions of the processes depicted for the Compaq Server - Central
Node depicted in Figure 8-1.
VHS GUI Agent
The VHS GUI Agent collects and sends the VHS EMS events and then sends the
user’s reply to the appropriate VHS process on the network. The VHS GUI Agent also
manages the VHS GUI user capability. The VHS GUI automatically starts the VHS GUI
Agent.
SSG
SeeView Server Gateway (SSG) provides the communication link between the VHS
GUI Agent and the CSG.
EMS Bdist
The VHS GUI Agent starts a browsing distributor. This browsing distributor sends the
VHS EMS events to the VHS GUI Agent.
VHS Process
This is the VHS process that is used as a hometerm for the applications.
Applications
These are applications that use the VHS process as their hometerm.
EMS Collector.
This is the EMS collector assigned to the VHS process.
EMS LOGS
This represents the current EMS log files used by the VHS EMS collector.
Compaq Server - Remote Node
Following is a description of the forwarding distributor for the processes depicted in
Figure 8-1.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -3
VHS GUI Installation
The VHS GUI
EMS Forward
This is the EMS forwarding distributor that forwards the VHS EMS events to the central
node (see the filter example at the end of this section).
VHS GUI Installation
VHS GUI installation consists of the following steps:
STEP 1: Install VHS on the Compaq System.
To install VHS, see Section 2, Installing VHS.
STEP 2: Install the SeeView Server Gateway on Your Central
Compaq System.
To install the SeeView Server Gateway on your central host computer, refer to the
SeeView Server Gateway Manual. The manual provides an in-depth description of
how to install the SSG on NonStop servers. In brief, the steps are:
> LOGON network-group.userid
> VOLUME $SSG-ISV-Volume.ZNOWSSG
> SEEVIEW /in SSGSETUP/
Follow the directions contained in the SSG Online Help for 'Local Node Install'.
Note. If DSM/NOW is installed on your VHS Central Node, SSG will have been installed as
well and does not need to be reinstalled.
Once the SSG Installation is completed, start SSG by using the SSGCOM command
interpreter START command. For example:
> SSGCOM
+ START
STEP 3: Install the VHS GUI on Your Workstation Running
Windows NT.
A self-extracting VHS GUI is included in the VHS GUI Host Installation Subvolume
(ISV) with the file name VHSGUI.
To install the VHS GUI from the Compaq Host, you should perform the following steps:
1. Download VHSGUI from your Compaq Host system, and place it in a directory
such as C:\VHSISV.
2. Rename VHSGUI to VHSGUI.EXE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -4
Starting the VHS GUI
The VHS GUI
3. Run VHSGUI.EXE.
Note. VHS GUI Setup will not replace pre-existing files such as DLL, EXE, and OCX files if the
preexisting files on your workstation are newer or of a later version than those in the VHS GUI
distribution zip file. You might get access violation warnings if any of these files are already
opened.
Starting the VHS GUI
Unless your site has modified the default configuration, the VHS GUI application is in
the workstation file C:\Program Files\Tandem\VHSGUI\VHSGUI.EXE pointed to by an
icon named VHS GUI in the Windows Start Menu.
To start the VHS GUI, use one of the following Windows methods:
1. Navigate to Programs in the Start Menu. In the Tandem Folder, click on the VHS
GUI icon.
2. Double-click the VHSGUI.EXE icon in the File Manager.
3. Select the Run command and specify C:\Program Files\Tandem\VHSGUI.EXE in
the Command Line field. (C:\Program Files\Tandem\VHSGUI is the default
directory; the VHS GUI files may be installed in a different directory in your
workstation.)
The VHS GUI Splash Screen appears, giving status messages on the initialization
process.
The New VHS Parameters
When you install the D43 version of NonStop VHS, you need to set the value of the
new parameters. These parameters are set during the VHS server installation on the
Compaq Nonstop Himalaya system and, during this process, they are written in the
VHSSTART file.
VHS-GUI-MODE
The VHS-GUI-MODE must be set to ON if you want to see and reply to the prompts via
the VHS GUI. The default value of this parameter is OFF; this is for compatibility with
previous releases of VHS. This parameter should be set to ON for each VHS process
that you want to be able to access with the VHS GUI. When the VHS-GUI-MODE is set
to ON, VHS will generate new EMS events as described in the following section.
Note. The VHS-GUI-MODE can only be specified as a startup parameter, and cannot be
changed with the VHSCI after VHS is started. To change this parameter you must stop and
restart the VHS process.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -5
EMS Event Messages Generated by VHS
The VHS GUI
VHS-PROMPT-RESEND-DELAY
The VHS-PROMPT-RESEND-DELAY is the time interval (in minutes) at which VHS will
resend the VHS prompt event message when a prompt is unanswered. By default, this
parameter has a value of 15 minutes. The possible value is from 1 to 60 minutes. This
parameter will be ignored if the VHS-GUI-MODE parameter is set to OFF.
VHS handles these two attributes in the following manner:
As soon as a prompt is received by VHS, it is available to the VHS GUI.
If you do not answer the prompt, VHS generates the ZVHS-PROMPT-RESENDEVENT at each interval specified by the PROMPT-RESEND-DELAY parameter.
The ZVHS-PROMPT-RESEND-EVENT parameter is generated by VHS with the
SUPPRESS-DISPLAY attribute set to ON.
This purpose of this new event message is to prevent the loss of a prompt in case of a
partial network, software, or system failure.
EMS Event Messages Generated by VHS
The behavior of VHS changes when you set the VHS-GUI-MODE parameter to ON.
This parameter overrides the setting of the GENERATE-INSPECT-EVENT,
GENERATE-DISPLAY-EVENT, and GENERATE-PROMPT-EVENT parameters. All
these parameters are set to ON and they cannot be changed via the VHSCI.
As a consequence, every application message received by VHS will be written to the
VHS EMS Collector (by default $0). This new setting generates more EMS traffic to
your operator console, and additional filtering may be necessary.
The following five EMS events are generated by VHS when the VHS-GUI-MODE
parameter is set to ON:
•
•
•
•
•
ZVHS-EVT-INSPECT-EXTENDED
ZVHS-EVT-INSPECT-APPL-EXT
ZVHS-EVT-INSPECT-SCOBOL-EXT
ZVHS-EVT-DEBUG-EXTEND
ZVHS-EVT-PROMPT-RESEND
For more information on event messages, see Appendix C, VHS Event Messages of
this manual.
Use of Alternate EMS Collectors
To reduce the number of event messages written to the primary collector $0, and
accordingly the load on this collector, you can use an alternate collector for VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -6
Restricting VHS GUI User Capability
The VHS GUI
To specify an alternate collector as the EMS collector for VHS, modify the define
=_EMS_COLLECTOR in the VHSSTART file. Refer to the EMS Manual for a
description on how to set up EMS alternate collectors. You can change the EMS
collector for VHS at any time by using the VHSCI.
Restricting VHS GUI User Capability
When you install the VHS GUI, any user that can log on to the Tandem system can
browse and reply to any prompts generated on a node or a network of systems. You
can restrict the capabilities of a group or individual user by modifying the file
VHSGCONF installed on $SYSTEM.SYSTEM. By default, this file has no user
restrictions entry.
The following syntax describes how to restrict a VHS GUI user to browse and reply
actions for only specific VHS Host Environments:
ADDUSER {group-name.user-name | group-name.* |
group-id, group-userid | group-id, *} ,
ENVIRONMENT {* environment-name | (environment-name, …) }
group-name
specifies a standard Tandem group name.
user-name
specifies a standard Tandem user name.
* (asterisk)
represents all user names or user IDs associated with the group name or the group
ID specified. The asterisk can also represent all environment names that are
logged in the VHS EMS collector.
group-id
specifies a number from 1 to 255 that represents a standard Tandem group ID.
user-id
specifies a number from 0 to 255 that represents a standard Tandem user ID.
environment-name
specifies a valid VHS environment name applicable for any system. There is
currently a maximum of 8 environments to which a specific group or user can have
access.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -7
Restricting VHS GUI User Capability
The VHS GUI
Example 1:
ADDUSER
ADDUSER
ADDUSER
ADDUSER
PROD.*,
PROD.MGR,
PROD.NEW,
215,3,
ENVIRONMENT
ENVIRONMENT
ENVIRONMENT
ENVIRONMENT
(ATM, POS, BATCH)
*
BATCH
DEV
The first entry specifies that all users of the PROD group can browse and reply to
prompts generated by the ATM, POS, and BATCH VHS environments on any system.
The second entry specifies that the PROD.MGR user can browse and reply to prompts
generated by any VHS environment on any system.
The third entry specifies that the PROD.NEW user can only browse and reply to
prompts generated by the VHS environment named BATCH on any system.
The fourth entry specifies that the user 215,3 can only browse and reply to prompts
generated by the VHS environment named DEV on any system.
Example 2:
ADDUSER
ADDUSER
ADDUSER
ADDUSER
ADDUSER
PROD.*,
DEV.*,
PROD.MGR,
DEV.MGR,
215,*,
ENVIRONMENT
ENVIRONMENT
ENVIRONMENT
ENVIRONMENT
ENVIRONMENT
*
DEV
*
(DEV, PRODA, PRODB)
(QA, DEV)
The first entry specifies that all users of the PROD group can browse and reply to
prompts generated by all VHS environments on any system.
The second entry specifies that all users of the DEV group can only browse and reply
to prompts generated by the DEV VHS environment on any system.
The third entry specifies that the PROD.MGR user can browse and reply to prompts
generated by all VHS environments on any system.
The fourth entry specifies that the DEV.MGR user can only browse and reply to
prompts generated by the DEV, PRODA, and PRODB VHS environments.
The fifth entry specifies that all the users of the group-id 215 can browse and reply to
the prompts generated by the QA and DEV environments on any system.
Restriction rules summary:
1. If the VHSGCONF is empty, any user can browse and reply to any prompt in all
environments.
2. If one of the VHSGCONF entries is for a specific user (for example,
PROD.BATCH). then only this entry will be used when the corresponding user logs
on.
3. If a user does not have a specific entry, the corresponding group entry (for
example, PROD.*) is used for the user.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -8
Broadcasting
The VHS GUI
4. If the VHSGCONF file is not empty and there is no entry for the user, the user is
not able to browse and reply to the VHS prompts.
Note. The user of the VHS GUI is set via the logon of the CSG.
Broadcasting
Many Windows NT workstations can see the same set of VHS prompts. So if one user
replies to a prompt, all the other workstations that have access to the same prompt are
updated. In that case, the VHS GUI will just remove the prompt on the view, based on
the EMS event generated by VHS.
Single Node Recommended Setup
If you plan to use VHS on a single node and you have a high volume of application
messages, we recommend that you use an alternate collector instead of the default
($0). By using an alternate collector, you are spreading the load across multiple CPUs
and disks, improving the VHS GUI performance.
Multiple Node Recommended Setup
If you plan to use the VHS GUI to browse application messages and prompts
distributed on multiple nodes, you need to configure and use EMS Forwarding
Distributors. These distributors require a special filter to pass only a subset of the VHS
events to a central node.
The following is an example of a filter that passes only the events required by the VHS
GUI.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8 -9
Multiple Node Recommended Setup
The VHS GUI
-- VhsGui Filter used by an EMS Forwarding Distributor
[SINK [#LOAD $SYSTEM.ZSPIDEF.ZSPITACL]]
[SINK [#LOAD $SYSTEM.ZSPIDEF.ZEMSTACL]]
[SINK [#LOAD $SYSTEM.ZSPIDEF.ZVHSTACL]]
[#DEF zems^val^ss text |body|[zspi^val^TANDEM].[zspi^ssn^zems].0]
[#DEF zvhs^val^ss text |body|[zspi^val^TANDEM].[zspi^ssn^zvhs].0]
FILTER VhsGui^Forwarding^Filter;
BEGIN SSID(ZEMS^VAL^SS)
IF ZSPI^TKN^SSID = SSID (ZVHS^VAL^SS) THEN
BEGIN
IF ( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^PROMPT]
( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^REPLY]
( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^REMOVE^PROMPT]
( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^PROMPT^RESEND]
( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^CLEAN^PROMPT^FILE]
( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^PROMPT^CANCEL]
( ZEMS^TKN^EVENTNUMBER = [ZVHS^EVT^BAD^REPLY]
THEN PASS
ELSE FAIL;
ELSE
FAIL;
END;
Virtual Hometerm Subsystem (VHS) Manual—429311-001
8- 10
)
)
)
)
)
)
)
OR
OR
OR
OR
OR
OR
A
VHS Files
VHSCSTM File
The following is the VHS custom configuration file supplied with VHS:
COMMENT NonStop Virtual Hometerm Subsystem - T9517D43 - (30SEP96)
COMMENT Copyright Tandem Computers Incorporated 1992, 1993, 1994, 1995,
1996
COMMENT VHS Custom file
COMMENT File Creation: September 30, 1996 13:33:22
SETPROMPT none, object, number
allow all errors
detail error on
alias F1 Info, detail
alias F2 listopens
alias F3 stats
alias F4 status, detail
alias F5 version, detail
alias primary alter, primary
alias log alter, log
alias i info, detail
alias l listopens
alias li listopens, inspect
alias lde listopens, debug
alias ld listopens, display
alias lp listopens, prompt
alias lu listopens, unknown
alias lps listopens, pserver
alias s stats
alias st status, detail
alias v version, detail
assume process $VHS
confirm on
Virtual Hometerm Subsystem (VHS) Manual—429311-001
A- 1
VHSSTART File
VHS Files
VHSSTART File
The following is the VHS startup file supplied with VHS:
COMMENT
COMMENT
COMMENT
PARAM ENVIRONMENT-NAME
ASSIGN
PARAM
PARAM
PARAM
PRIMARY-LOGFILE,
MAXEXTENTS
PRIMARY-SECURITY
SUPPRESS-DISPLAY
VHS Startup file
"PROD"
$VHS.VHSD43.LOG, EXT (5, 5), CODE 0
16
"NNNN"
FALSE
ASSIGN INSPECT-SAVEFILE,
PARAM PURGE-SAVEFILE
ASSIGN INSPECT-FILE,
$VHS.VHSD43.SAVE0000
FALSE
$VHS.VHSD43.VHSINSP
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
PARAM
ON
ON
ON
ON
ON
ON
OFF
ON
10
VHS-LOGGER
ADD-TEXT-TO-EVENT
GENERATE-INSPECT-EVENT
GENERATE-PROMPT-EVENT
GENERATE-DISPLAY-EVENT
REMOVE-EXTRA-SPACES
ACCEPT-EXT-ASCII-CHARACTER
VHS-GUI-MODE
PROMPT-EVENT-RESEND-DELAY
PARAM AUTOMATIC-INSPECT-PROCESSING ON
PARAM BACKUP-CREATION-MESSAGE-DELAY 5
PARAM OPEN-TABLE-THRESHOLD
90
RUN $SYSTEM.UTILITY.VHS / NAME $VHS, CPU 0, PRI 180, NOWAIT/ 1
Virtual Hometerm Subsystem (VHS) Manual—429311-001
A- 2
VHSBCONF File
VHS Files
VHSBCONF File
The following is the VHS Browser configuration file supplied with VHS:
==========================================================================
==
==
== NonStop Virtual Hometerm Subsystem - T9517D43 - (30SEP96)
== Copyright Tandem Computers Incorporated 1992, 1993, 1994, 1995, 1996
==
== File Type:
VHS Browser Environment Configuration File.
==
== Source File Name:
$VHS.VHSD43.VHSBCONF
== Source File Version:
1
==
== File Description: This file is used to define the relationship
==
between the environment Name used by the VHS Browser
==
screens and the different VHS server environments.
==
== File Structure:
Two record types are valid.
==
The first one is a comment line and should begin
==
with two equal signs "==".
==
The second record type is the mapping of the
==
environment name to the prompt file name of each
==
VHS environment. Each line should contain the
==
following items:
==
<environment-name> <1 or more space> <VHS prompt file name>
==
==
== Modifications Summary:
==
== This is the first release of this file,
Sept 30, 1996 10:55:58
==
======================================================================
== Default configuration for the VHS Browser Environment file
======================================================================
== <environment-name> <space> <VHS Prompt file name>
==
VHS
$SYSTEM.VHS.PROMPT
ATM
$PROD.VHSLOG.PROMPT
Virtual Hometerm Subsystem (VHS) Manual—429311-001
A- 3
VHSBCONF File
VHS Files
Virtual Hometerm Subsystem (VHS) Manual—429311-001
A- 4
B
VHS Limits
Description
Limit
Comments
Maximum primary log files
5
None
Maximum opens of VHS process
512
For all opener types
Maximum prompts
512
Per VHS process
Maximum number of VHS processes
No limit
Multiple VHS processes can be used for
load balancing or for separating
application environments.
Maximum number of remote
openers
0
VHS cannot be opened by remote
processes. VHS can only be opened by
local processes.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
B- 1
VHS Limits
Virtual Hometerm Subsystem (VHS) Manual—429311-001
B- 2
C
VHS Event Messages
This section lists the Event Management Service (EMS) event messages that are
generated by VHS and the VHS Browser server.
Note. In this section, event names, values, and tokens are represented in DDL (or COBOL85)
format using hyphens (-) as separators.
VHS Event Messages
Event messages are reported through EMS. They are formatted as a special
Subsystem Programmatic Interface (SPI) buffer specific for EMS and are sent to the
local collector ($0 or an alternate collector) on the node where VHS is operating.
VHS Application-Related Events
The following lists VHS application-related event messages:
ZVHS-EVT-INSPECT-SAVE
(1)
ZVHS-EVT-INSPECT-NO-SAVE
(2)
ZVHS-EVT-INSPECT-OBEY
(3)
ZVHS-EVT-INSPECT-SCOBOL
(4)
ZVHS-EVT-DEBUG-ERROR
(5)
ZVHS-EVT-DISPLAY
(6)
ZVHS-EVT-PROMPT
(7)
ZVHS-EVT-REPLY
(8)
ZVHS-EVT-INSPECT-EXTENDED
(150)
ZVHS-EVT-INSPECT-APPL-EXT
(151)
ZVHS-EVT-INSPECT-SCOBOL-EXT
(152)
ZVHS-EVT-DEBUG-EXTENDED
(153)
ZVHS-EVT-PROMPT-RESEND
(154)
VHS Internal Events
The following lists VHS internal event messages:
ZVHS-EVT-VHS-STARTED
(100)
ZVHS-EVT-BACKUP-CREATED
(101)
ZVHS-EVT-PRIMARY-LOG-CREATED
(102)
ZVHS-EVT-PRIMARY-LOG-ROLLOVER
(103)
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 1
VHS Internal Events
VHS Event Messages
ZVHS-EVT-CREATE-BACKUP-FAILED
(104)
ZVHS-EVT-BACKUP-STOPPED
(105)
ZVHS-EVT-BACKUP-DELETED
(106)
ZVHS-EVT-BACKUP-ABENDED
(107)
ZVHS-EVT-TAKEOVER
(108)
ZVHS-EVT-CHECKPOINT-FAILED
(109)
ZVHS-EVT-CHECKOPEN-FAILED
(110)
ZVHS-EVT-PRIMARY-LOG-IO-ERROR
(111)
ZVHS-EVT-PROCESS-DELETED
(112)
ZVHS-EVT-ALTERNATE-CREATED
(113)
ZVHS-EVT-PROMPT-IO-ERROR
(114)
ZVHS-EVT-PROMPT-FILE-CREATED
(115)
ZVHS-EVT-PROMPT-ALT-CREATED
(116)
ZVHS-EVT-CLEAN-PROMPT-FILE
(117)
ZVHS-EVT-REMOVE-PROMPT
(118)
ZVHS-EVT-BAD-REPLY
(119)
ZVHS-EVT-COLLECTOR-ERROR
(122)
ZVHS-EVT-INSP-UNKNOWN-LANGUAGE
(123)
ZVHS-EVT-INSP-INVALID-FILENAME
(124)
ZVHS-EVT-INSP-INVALID-PROCESS
(125)
ZVHS-EVT-INSP-DUPLICATE-SEC
(126)
ZVHS-EVT-INSP-TABLE-FULL-DATA
(127)
ZVHS-EVT-INSP-TABLE-FULL-SEC
(128)
ZVHS-EVT-INSP-PROCESSING-STOP
(129)
ZVHS-EVT-INSP-TOO-MUCH-PROMPT
(130)
ZVHS-EVT-OPEN-TABLE-THRESHOLD
(131)
ZVHS-EVT-INSP-INVALID-PARAM
(132)
ZVHS-EVT-INSP-LOAD-FILE-ERR
(133)
ZVHS-EVT-OPENEDIT-ERROR
(134)
ZVHS-EVT-READEDIT-ERROR
(135)
ZVHS-EVT-SET-DEFINE
(136)
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 2
VHS Browser Events
VHS Event Messages
ZVHS-EVT-INSP-RELOAD-FILE
(137)
ZVHS-EVT-PROMPT-CANCEL
(138)
ZVHS-EVT-PROMPT-NOT-UNIQUE
(139)
ZVHS-EVT-INSP-INVALID-KEYWORD
(140)
ZVHS-EVT-INSP-LINE-TOO-LONG
(141)
ZVHS-EVT-INSP-LOAD-FILE
(143)
ZVHS-EVT-INSP-RELOAD-FILE-ERR
(144)
ZVHS-EVT-INSP-INVALID-REMOTE
(145)
ZVHS-EVT-INSP-FILE-NOT-EXIST
(146)
ZVHS-EVT-INSP-INVALID-TEXT
(147)
ZVHS-EVT-CLEAN-TABLE
(148)
ZVHS-EVT-INTERNAL-ERROR
(200)
VHS Browser Events
The following lists VHS Browser internal event messages:
ZVHS-EVT-CONFIG-IO-ERROR
(120)
ZVHS-EVT-INVALID-LINE-FORMAT
(121)
VHS Token List
VHS event messages use SPI standard definitions, EMS standard definitions, and
VHS definitions. A general description of these definitions is provided in the following
paragraphs. This appendix also describes the event messages for VHS.
SPI Standard Definitions
SPI standard definitions begin with ZSPI- and are listed in Table C-1. They are
described under each event message.
Table C-1. SPI Standard Definitions Used by VHS (page 1 of 2)
Header Tokens
Value Names
Token Types
ZSPI-TKN-SSID
ZSPI-SSN-ZVHS
ZSPI-TYP-CHAR4
ZSPI-TKN-MANAGER
ZSPI-VAL-FALSE
ZSPI-TYP-CHAR6
ZSPI-VAL-TANDEM
ZSPI-TYP-CHAR8
ZSPI-VAL-TRUE
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR50
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 3
SPI Standard Definitions
VHS Event Messages
Table C-1. SPI Standard Definitions Used by VHS (page 2 of 2)
Header Tokens
Value Names
Token Types
ZSPI-TYP-CHAR128
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR254
ZSPI-TYP-BOOLEAN
ZSPI-TKN-CRTPID
ZSPI-TKN-FNAME
ZSPI-TYP-FNAME32
ZSPI-TYP-INT
ZSPI-TYP-INT2
ZSPI-TYP-INT4
ZSPI-TYP-SSID
ZSPI-TYP-TIMESTAMP
SPI standard definitions are described in detail in the SPI Programming Manual.
VHS-specific information on SPI definitions is described in the following paragraphs.
ZSPI-TKN-SSID contains ZVHS-VAL-SSID, the subsystem ID of the VHS subsystem.
ZVHS-VAL-SSID has the following structure:
def ZVHS-VAL-SSID tacl ssid.
02 Z-FILLER
02 Z-OWNER
02 Z-NUMBER
02 Z-VERSION
type character 8
value is ZSPI-VAL-TANDEM
redefines Z-FILLER
type ZSPI-DDL-CHAR8
type ZSPI-DDL-INT
value is ZSPI-SSN-ZVHS
type ZSPI-DDL-UINT
value is ZVHS-VAL-VERSION.
end.
ZSPI-SSN-ZVHS contains the subsystem number (138) assigned to VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 4
EMS Standard Definitions
VHS Event Messages
EMS Standard Definitions
EMS standard definitions begin with ZEMS- and are listed in Table C-2. They are
described under each event message.
Table C-2. EMS Standard Definitions Used by VHS
Header Tokens
Data Portion Tokens
ZEMS-TKN-CPU
ZEMS-TKN-ACTION-ID
ZEMS-TKN-PROC-DESC
ZEMS-TKN-ACTION-NEEDED
ZEMS-TKN-CRTPID
ZEMS-TKN-SUBJECT-MARK
ZEMS-TKN-EMPHASIS
ZEMS-TKN-TEXT
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
EMS standard definitions are described in detail in the following paragraphs. For
additional information on EMS standard definitions, see the EMS Manual.
ZEMS-TKN-ACTION-ID contains the number identifying a particular action-event
message.
ZEMS-TKN-ACTION-NEEDED is set to ZSPI-VAL-FALSE or ZSPI-VAL-TRUE. The
value TRUE means that the message is a request for action.
ZEMS-TKN-CPU contains the CPU number of the reporting VHS process.
ZEMS-TKN-PROC-DESC contains the process descriptor of the reporting VHS
process.
ZEMS-TKN-CRTPID contains the CRTPID of the reporting VHS process.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE or ZSPI-VAL-TRUE, depending on
the event message generated by the VHS process. The value TRUE means that the
event message is critical.
ZEMS-TKN-EVENTNUMBER contains the event message number for each VHS
event message.
ZEMS-TKN-GENTIME contains the time (Greenwich mean time) that the reporting
VHS process created the event message.
ZEMS-TKN-LOGTIME contains the time (Greenwich mean time) that the collector
wrote the event message to its log files.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 5
VHS Definitions
VHS Event Messages
ZEMS-TKN-PIN contains the PIN of the reporting VHS process.
ZEMS-TKN-SUBJECT-MARK marks the token that follows it in the event-message
buffer as a subject of the event message.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE or ZSPI-VAL-TRUE,
depending on the event message generated by the VHS process. TRUE tells the
ViewPoint application or NonStop NET/MASTER not to display the token text. FALSE
means that ViewPoint will display the token text.
ZEMS-TKN-SYSTEM contains the Expand system number of the system (node) in
which the event message was reported.
ZEMS-TKN-TEXT contains the displayable text describing the event message (that is,
the message).
ZEMS-TKN-USERID contains the user ID of the reporting VHS process.
VHS Definitions
VHS definitions contain two different categories: tokens and values.
VHS Token Definitions
VHS token definitions begin with ZVHS- and are listed in Table C-3. They are
described under each event message.
Table C-3. VHS Token Definitions (Simple Tokens) (page 1 of 2)
ZVHS-TKN-APPLICATION-NAME
ZVHS-TKN-PREVIOUS-MESSAGE-3
ZVHS-TKN-CHECKPOINT-STATUS
ZVHS-TKN-PREVIOUS-MESSAGE-4
ZVHS-TKN-CONFIG-LINE
ZVHS-TKN-PREVIOUS-MESSAGE-5
ZVHS-TKN-CPU
ZVHS-TKN-PREV-TIMESTAMP-1
ZVHS-TKN-CRTPID
ZVHS-TKN-PREV-TIMESTAMP-2
ZVHS-TKN-DATAFILE
ZVHS-TKN-PREV-TIMESTAMP-3
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-PREV-TIMESTAMP-4
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-PREV-TIMESTAMP-5
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PRI
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-FILENAME1
ZVHS-TKN-PROC-NAME
ZVHS-TKN-FILENAME2
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-INSPECT-COMMAND
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-PROMPT-TIMESTAMP
ZVHS-TKN-INSPECT-OBJECT2
ZVHS-TKN-PROMPT-TS-INTERNAL
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 6
VHS Value Definitions
VHS Event Messages
Table C-3. VHS Token Definitions (Simple Tokens) (page 2 of 2)
ZVHS-TKN-INTERNAL-ERROR-CODE
ZVHS-TKN-REPLY-STRING
ZVHS-TKN-JOBID
ZVHS-TKN-SAVEFILE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-SECURITY-STRING
ZVHS-TKN-MESSAGE-STRING2
ZVHS-TKN-SEND-RECEIVE-MSG
ZVHS-TKN-MESSAGE-STRING3
ZVHS-TKN-SUBDEVICE
ZVHS-TKN-MESSAGE-TYPE
ZVHS-TKN-TABLE-THRESHOLD
ZVHS-TKN-NEWPROCESS-ERROR
ZVHS-TKN-TAKEOVER-CODE
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-TAKEOVER-CPU
ZVHS-TKN-OPERATION-CODE
ZVHS-TKN-TERMNAME
ZVHS-TKN-PIN
ZVHS-TKN-USER-ID
ZVHS-TKN-PNAME
ZVHS-TKN-VERSION
ZVHS-TKN-PREVIOUS-MESSAGE-1
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-PREVIOUS-MESSAGE-2
ZVHS-TKN-VHS-PNAME
VHS Value Definitions
VHS value definitions begin with ZVHS- and are listed in Table C-4. They are
described under each event message.
Table C-4. VHS Value Definitions
ZVHS-VAL-BACKUP
ZVHS-VAL-INSPECT-RECEIVE
ZVHS-VAL-INSPECT-SEND
ZVHS-VAL-SSID
ZVHS-VAL-VERSION
Private Token and Field Types
VHS does not define any private token or field types.
Predefined Token and Field Values
ZVHS-VAL-INSPECT-RECEIVE contains 0, which indicates that a message was
received from Inspect.
ZVHS-VAL-INSPECT-SEND contains 1, which indicates that a message was sent to
Inspect.
ZVHS-VAL-SSID contains the VHS subsystem ID. The structure is shown under the
description for ZSPI-TKN-SSID.
ZVHS-VAL-VERSION contains the version number of the VHS subsystem.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 7
Simple Tokens
VHS Event Messages
Simple Tokens
These tokens are described in the following paragraphs.
Description of VHS Event Messages
The following descriptions of the VHS event messages are in ascending order by event
number, which is ZVHS-EVT-object-state, where object is an abbreviation of the
object type or the object type itself and state is the current state of the object.
Each description contains the following information:
•
•
•
•
•
•
A header shows the numeric and symbolic values for the event message number.
The first paragraph identifies the condition that generated the event message.
A box contains a list of tokens that can appear in the event message. Header
tokens are included in the list because an event message can be filtered on these
tokens, as well as other tokens. Tokens in an actual event message do not
necessarily appear in the same order that they are listed in the box.
The box also contains the event-message text.
A description for each token follows the box.
The recommended action describes what action should be taken.
Unconditional and Conditional Tokens
Tokens are grouped into two categories, unconditional and conditional:
•
•
An unconditional token is always present in an event message with a specific
subsystem ID and event message number. An example of an unconditional token
is ZEMS-TKN-EVENTNUMBER.
A conditional token is present only in the event message for certain cases. For
example, the token ZEMS-TKN-ACTION-NEEDED appears in an event message
only if the event message type is action-attention.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 8
1: ZVHS-EVT-INSPECT-SAVE
VHS Event Messages
1: ZVHS-EVT-INSPECT-SAVE
VHS generates this critical message when it is prompted by Inspect, a savefile has
been created, and the program is stopped.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-SAVEFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string
entered Inspect. Savefile savefile-name was created. Process
has been stopped. Program file program-name. Primary log file
primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-SAVE (1).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C- 9
1: ZVHS-EVT-INSPECT-SAVE
VHS Event Messages
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has gone into Inspect.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into
Inspect.
ZVHS-TKN-SAVEFILE is the saveabend file name created by VHS.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -10
2: ZVHS-EVT-INSPECT-NOSAVE
VHS Event Messages
Probable Cause
An application entered Inspect. Inspect prompted the VHS process. The VHS process
supplied commands to create a saveabend file, Inspect created the saveabend file and
stopped the application.
Recommended Action
Advise software personnel of this event message. Use the created saveabend file to fix
the application’s problem. See the primary log file for more information about the
problem.
2: ZVHS-EVT-INSPECT-NOSAVE
VHS generates this critical event message when Inspect is unable to create a
saveabend file as requested by VHS.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-SAVEFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -11
2: ZVHS-EVT-INSPECT-NOSAVE
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Process process-id-string
entered Inspect. Savefile savefile-name could not be created
due to file-system error file-error. Process has been
stopped. Program file program-name. Primary log file primarylog-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-NO-SAVE (2).
EMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the
subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under the EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has gone into Inspect.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into
Inspect.
ZVHS-TKN-SAVEFILE is the saveabend file name created by VHS.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-FILE-ERROR is the file-system error number.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -12
2: ZVHS-EVT-INSPECT-NOSAVE
VHS Event Messages
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
An application entered Inspect. Inspect prompts the VHS process. The VHS process
supplied commands to create a saveabend file, but an error occurred on the creation of
the saveabend file.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -13
3: ZVHS-EVT-INSPECT-OBEY
VHS Event Messages
3: ZVHS-EVT-INSPECT-OBEY
VHS generates this critical message when it is prompted by Inspect and it sends a
command line to Inspect.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-INSPECT-COMMAND
ZVHS-TKN-JOBID
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-CHAR132
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string
entered Inspect. The command "command-string" has been sent
to Inspect. Program file program-name. Primary log file
primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-OBEY (3).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -14
3: ZVHS-EVT-INSPECT-OBEY
VHS Event Messages
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5n.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has gone into Inspect.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into
Inspect.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-INSPECT-COMMAND is the line command send to Inspect, if not empty.
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -15
4: ZVHS-EVT-INSPECT-SCOBOL
VHS Event Messages
Probable Cause
An application entered Inspect. Inspect prompts the VHS process. The VHS process
supplies a command line to Inspect from the VHS Inspect file.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
4: ZVHS-EVT-INSPECT-SCOBOL
VHS generates this critical event message when a Pathway terminal enters Inspect.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-TERMNANE
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZSPI-TKN-SUBSYSTEM-MANAGER
ZVHS-TKN-APPLICATION-NAME
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-INSPECT-COMMAND
ZVHS-TKN-JOBID
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR16
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TKN-FNAME32
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-CHAR132
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -16
4: ZVHS-EVT-INSPECT-SCOBOL
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Pathway terminal terminalname entered Inspect. The command "command-string" has been
sent to Inspect. PATHMON process name pathmon-name. Inspect
process process-id-string. Primary log file primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-SCOBOL (4).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-TERMNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZSPI-TKN-SUBSYSTEM-MANAGER contains the name of the PATHMON process
that controls this Pathway terminal.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the Inspect process.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-TERMNAME is the terminal name of the SCREEN COBOL program that
has gone into Inspect.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -17
4: ZVHS-EVT-INSPECT-SCOBOL
VHS Event Messages
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-INSPECT-COMMAND is the line command send to Inspect, if not empty.
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
VHS generates this critical message when a Pathway terminal enters Inspect. VHS
supplies a command line to Inspect from the VHS Inspect file.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -18
5: ZVHS-EVT-DEBUG-ERROR
VHS Event Messages
5: ZVHS-EVT-DEBUG-ERROR
VHS generates this critical event message when it is prompted by Debug.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string
entered Debug. Process has been stopped. Program file
program-name. Primary log file primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-DEBUG-ERROR (5).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -19
5: ZVHS-EVT-DEBUG-ERROR
VHS Event Messages
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Debug.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has gone into Debug.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into Debug.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Debug.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
An application entered Debug. Debug prompts the VHS process. The VHS process
supplies commands to display register values and stop the application. You can look at
the results of these commands in the primary log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -20
6: ZVHS-EVT-DISPLAY
VHS Event Messages
Recommended Action
Correct the application problem. More information about the problem is available in the
primary log file.
6: ZVHS-EVT-DISPLAY
VHS generates this informative event message when it receives a user display.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-MESSAGE-STRING2
ZVHS-TKN-MESSAGE-STRING3
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR128
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: message-string. Display text
received from process process-id-string. Program file
program-name. Primary log file primary-log-name.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -21
6: ZVHS-EVT-DISPLAY
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-DISPLAY (6).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is ZSPI-VAL-FALSE because the message is informative.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE or ZSPI-VAL-TRUE
depending on the VHS SUPPRESS-DISPLAY parameter value. The TRUE value tells
the ViewPoint application not to display the event message. A FALSE value means
that ViewPoint will display the event message.
ZVHS-TKN-APPLICATION-NAME is the application that sent a user display to VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID that is displayed as text to VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application that sent a user
display.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application that sent a user display to VHS.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -22
6: ZVHS-EVT-DISPLAY
VHS Event Messages
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-MESSAGE-STRING is the first 254 characters of the user display received
by VHS, if not empty.
ZVHS-TKN-MESSAGE-STRING2 is the following 254 characters of the user display
received by VHS, if there are more than 254 characters.
ZVHS-TKN-MESSAGE-STRING3 is the last 128 characters of the user display
received by VHS, if necessary.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
A user display from an application has been sent to the VHS process.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -23
7: ZVHS-EVT-PROMPT
VHS Event Messages
7: ZVHS-EVT-PROMPT
VHS generates this action-attention event message when it is prompted by an
application.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-ATTENTION
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-PROMPT-TIMESTAMP
ZVHS-TKN-PROMPT-TS-INTERNAL
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-GUI-MODE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT4
ZSPI-TYP-INT2
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -24
7: ZVHS-EVT-PROMPT
VHS Event Messages
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-PREVIOUS-MESSAGE-1
ZVHS-TKN-PREVIOUS-MESSAGE-2
ZVHS-TKN-PREVIOUS-MESSAGE-3
ZVHS-TKN-PREVIOUS-MESSAGE-4
ZVHS-TKN-PREVIOUS-MESSAGE-5
ZVHS-TKN-PREV-TIMESTAMP-1
ZVHS-TKN-PREV-TIMESTAMP-2
ZVHS-TKN-PREV-TIMESTAMP-3
ZVHS-TKN-PREV-TIMESTAMP-4
ZVHS-TKN-PREV-TIMESTAMP-5
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string.
Prompt "prompt-string". Program file program-name. Primary
log file primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT (7).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is an
action-attention event message.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to TRUE to specify that this is an action-attention
event message.
ZVHS-TKN-APPLICATION-NAME is the application that has prompted VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -25
7: ZVHS-EVT-PROMPT
VHS Event Messages
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has prompted VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file of the application that prompted VHS.
ZVHS-TKN-MESSAGE-STRING is the prompt string received by VHS.
ZVHS-TKN-PROMPT-FILE is the name of the prompt file of VHS.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current prompt file. This number includes prompts from other VHS processes using the
same prompt file.
ZVHS-TKN-PROMPT-TIMESTAMP is the timestamp of this prompt.
ZVHS-TKN-PROMPT-TS-INTERNAL is the timestamp of this prompt in fixed format. It
is represented in LCT. This token is only used by the VHS GUI.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application that has sent a prompt to VHS.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-GUI-MODE indicates if the VHS process is running in GUI mode or
not. ZVHS-VAL-VHS-GUI-OFF (0) indicates that the VHS-GUI-MODE parameter is set
to OFF. ZVHS-VAL-VHS-GUI-ON (1) indicates that the VHS-GUI-MODE parameter is
set to ON.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-PREVIOUS-MESSAGE-1 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the oldest one.
ZVHS-TKN-PREVIOUS-MESSAGE-2 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-1.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -26
7: ZVHS-EVT-PROMPT
VHS Event Messages
ZVHS-TKN-PREVIOUS-MESSAGE-3 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-2.
ZVHS-TKN-PREVIOUS-MESSAGE-4 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-3.
ZVHS-TKN-PREVIOUS-MESSAGE-5 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-4, which means the
one received just before the prompt.
ZVHS-TKN-PREV-TIMESTAMP-1 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-1. Token ZVHS-TKN-PREV-TIMESTAMP-1
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-1 is present.
ZVHS-TKN-PREV-TIMESTAMP-2 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-2. Token ZVHS-TKN-PREV-TIMESTAMP-2
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-2 is present.
ZVHS-TKN-PREV-TIMESTAMP-3 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-3. Token ZVHS-TKN-PREV-TIMESTAMP-3
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-3 is present.
ZVHS-TKN-PREV-TIMESTAMP-4 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-4. Token ZVHS-TKN-PREV-TIMESTAMP-4
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-4 is present.
ZVHS-TKN-PREV-TIMESTAMP-5 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-5. Token ZVHS-TKN-PREV-TIMESTAMP-5
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-5 is present.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
prompting VHS.
Probable Cause
An application has prompted the VHS process.
Recommended Action
Use the VHS Prompt Browser facility to select and answer the application prompt.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -27
8: ZVHS-EVT-PROMPT-REPLY
VHS Event Messages
8: ZVHS-EVT-PROMPT-REPLY
VHS generates this action-completion message when a user answer an application
prompt.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-ATTENTION
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-REPLY-STRING
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-CHAR128
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string.
Prompt "prompt-string". Reply "reply-string". Program file
program-name. Primary log file primary-log-name.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -28
8: ZVHS-EVT-PROMPT-REPLY
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-REPLY (8).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is an
action completion event message.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has prompted
VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has prompted VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application that has prompted
VHS.
ZVHS-TKN-MESSAGE-STRING is the prompt string received by VHS.
ZVHS-TKN-PROMPT-FILE is the name of the prompt file of VHS.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current prompt file. This number includes prompts from other VHS processes using the
same prompt file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -29
8: ZVHS-EVT-PROMPT-REPLY
VHS Event Messages
ZVHS-TKN-REPLY-STRING is the string replied to the application prompt by VHS.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application that has sent a prompt to VHS.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
A user answered the application prompt.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -30
100: ZVHS-EVT-VHS-STARTED
VHS Event Messages
100: ZVHS-EVT-VHS-STARTED
VHS generates this informative event message when VHS has successfully started.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-VHS-GUI-MODE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-STRING
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
successfully started.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-VHS-STARTED (100).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -31
101: ZVHS-EVT-BACKUP-CREATED
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-VHS-GUI-MODE indicates if the VHS process is running in GUI mode or
not. ZVHS-VAL-VHS-GUI-OFF (0) indicates that the VHS-GUI-MODE parameter is set
to OFF. ZVHS-VAL-VHS-GUI-ON (1) indicates that the VHS-GUI-MODE parameter is
set to ON.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS started successfully.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
101: ZVHS-EVT-BACKUP-CREATED
VHS generates this informative event message when a new VHS process in the
backup CPU has been successfully created.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-PRI
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -32
101: ZVHS-EVT-BACKUP-CREATED
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
created backup in CPU cpu-number. Priority priority. Program
file program-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-BACKUP-CREATED (101).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number of the VHS backup process.
ZVHS-TKN-PIN is the process number of the VHS backup process.
ZVHS-TKN-PRI is the priority of the VHS backup process.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS primary process has started a new backup process.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -33
102: ZVHS-EVT-PRIMARY-LOG-CREATED
VHS Event Messages
102: ZVHS-EVT-PRIMARY-LOG-CREATED
VHS generates this informative event message when it has created a new primary
log file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
created primary log file primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PRIMARY-LOG-CREATED (102).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -34
103: ZVHS-EVT-PRIMARY-LOG-ROLLOVER
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS process created a new primary log file.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
103: ZVHS-EVT-PRIMARY-LOG-ROLLOVER
VHS generates this informative event message when it has created a new primary
log file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-FILENAME1
ZVHS-TKN-FILENAME2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
switched log files from file old-primary-log to new-primarylog because old file is full.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -35
103: ZVHS-EVT-PRIMARY-LOG-ROLLOVER
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PRIMARY-LOG-ROLLOVER (103).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-FILENAME1 is the old primary log file name of VHS.
ZVHS-TKN-FILENAME2 is the new primary log file name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A VHS primary log file rollover occurred.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -36
104: ZVHS-EVT-CREATE-BACKUP-FAILED
VHS Event Messages
104: ZVHS-EVT-CREATE-BACKUP-FAILED
VHS generates this critical event message when it cannot create its backup process
because of a NEWPROCESS error. This condition causes VHS to generate this
message and to continue processing.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PRI
ZVHS-TKN-NEWPROCESS-ERROR
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
failed to create backup in CPU cpu-number due to NEWPROCESS
error newprocess-error : error-text. Priority priority.
Program file program-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-CREATE-BACKUP-FAILED (104).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -37
104: ZVHS-EVT-CREATE-BACKUP-FAILED
VHS Event Messages
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number of the VHS backup process.
ZVHS-TKN-PRI is the priority of the VHS backup process.
ZVHS-TKN-FILE-ERROR is the file error returned by NEWPROCESS.
ZVHS-TKN-MESSAGE-STRING is the error text corresponding to NEWPROCESS
error.
ZVHS-TKN-NEWPROCESS-ERROR is the error returned by NEWPROCESS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS tried to start its backup process but the NEWPROCESS failed with an error. The
primary VHS process tries to restart its backup process unless the NEWPROCESS
error indicates that the backup CPU is down. In this case, VHS tries to create a new
backup 10 seconds after it receives the CPU UP system message for the backup CPU.
For errors other than CPU down, the VHS primary process waits for 10 seconds and
retries; if this first attempt fails, the next attempt occurs after a 20-second delay.
Thereafter, the primary process attempts to create a new backup process every 20
seconds.
Recommended Action
The recommended action depends on the most significant bytes of the
NEWPROCESS error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -38
105: ZVHS-EVT-BACKUP-STOPPED
VHS Event Messages
105: ZVHS-EVT-BACKUP-STOPPED
VHS generates this critical event message when the VHS backup process stopped.
This condition causes VHS to generate this message and to continue processing.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name,
backup process cpu,pin stopped.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-BACKUP-STOPPED (105).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -39
106: ZVHS-EVT-BACKUP-DELETED
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number of the VHS backup process.
ZVHS-TKN-PIN is the process number of the VHS backup process.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS backup process was stopped. The VHS primary process attempts to create a
new backup process after a 1-minute delay.
Recommended Action
No action is needed.
106: ZVHS-EVT-BACKUP-DELETED
VHS generates this critical event message when the backup VHS process fails. This
condition causes VHS to generate this event message and to continue processing.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name,
backup process cpu,pin deleted (CPU DOWN).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -40
106: ZVHS-EVT-BACKUP-DELETED
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-BACKUP-DELETED (106).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number of the VHS backup process.
ZVHS-TKN-PIN is the process number of the VHS backup process.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The CPU in which the backup process was running has failed. The primary VHS
process does not attempt to create a backup until it receives the CPU UP system
message for its backup CPU.
Recommended Action
Follow the recommended procedure for a CPU failure.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -41
107: ZVHS-EVT-BACKUP-ABENDED
VHS Event Messages
107: ZVHS-EVT-BACKUP-ABENDED
VHS generates this critical event message when the backup process has abended.
This condition causes VHS to generate this event message and to continue
processing.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name,
backup process cpu,pin abended.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-BACKUP-ABENDED (107).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -42
108: ZVHS-EVT-TAKEOVER
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number of the VHS backup process.
ZVHS-TKN-PIN is the process number of the VHS backup process.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS backup process abended. The VHS primary process attempts to create a
new backup process after a 10-second delay. If the VHS primary process cannot
create the backup process after 10 seconds, it retries every 20 seconds.
Recommended Action
No action is needed.
108: ZVHS-EVT-TAKEOVER
VHS generates this critical message after a takeover by the VHS backup process. This
condition causes VHS to generate this message and to continue processing.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-TAKEOVER-CPU
ZVHS-TKN-TAKEOVER-CODE
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -43
108: ZVHS-EVT-TAKEOVER
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Process VHS-process-name,
takeover by backup in CPU cpu because primary process cpu,pin
takeover-text.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-TAKEOVER (108).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-TAKEOVER-CPU is the CPU number of the VHS backup process that
takes over the primary process.
ZVHS-TKN-TAKEOVER-CODE is the status value<8:15> returned by
CHECKMONITOR.
ZVHS-TKN-CPU is the CPU number of the VHS primary process.
ZVHS-TKN-PIN is the process number of the VHS primary process.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Note that takeover-text depends on the value of ZVHS-TKN-TAKEOVER-CODE
and is one of the following:
•
•
•
•
Stopped
Abended
Deleted (CPU DOWN)
Switched
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -44
109: ZVHS-EVT-CHECKPOINT-FAILED
VHS Event Messages
Probable Cause
The primary VHS process or the CPU in which it runs has failed. If the primary VHS
process has failed, an attempt is made to create a new backup. In the case of a CPU
failure, a new backup will be created after the receipt of a CPU UP system message by
the new primary process.
Recommended Action
If the primary VHS process abended, investigate the event message log to determine
why.
109: ZVHS-EVT-CHECKPOINT-FAILED
VHS generates this critical event message when an error occurs during a checkpoint
operation.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name,
CHECKPOINT failed due to file-system error error-number.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-CHECKPOINT-FAILED (109).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -45
109: ZVHS-EVT-CHECKPOINT-FAILED
VHS Event Messages
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-FILE-ERROR is the status value<8:15> returned by CHECKPOINT.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS backup process has received an I/O error during a checkpoint operation. The
VHS backup process is stopped and an attempt is made to create a new backup after
a 10 second delay. Resource allocation failures (error 30 through 37) might indicate
that the primary and/or backup CPU is overloaded.
Recommended Action
For errors 30 through 37, free up system resources. If this does not correct the
problem or results in a different error, contact your service provider and provide all
relevant information as follows:
•
•
•
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a processor dump, if applicable
If your local operating procedures require contacting the Compaq Global Customer
Support Center (GCSC), supply your system number and the numbers and versions of
all related products as well.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -46
110: ZVHS-EVT-CHECKOPEN-FAILED
VHS Event Messages
110: ZVHS-EVT-CHECKOPEN-FAILED
VHS generates this critical event message when the backup VHS process is unable to
open a file previously opened by the primary process.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-FILENAME1
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name,
CHECKOPEN failed on file filename due to file-system error
file-error.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-CHECKOPEN-FAILED (110).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -47
110: ZVHS-EVT-CHECKOPEN-FAILED
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-FILE-ERROR is the error returned by the CHECKOPEN. See the
Guardian Procedure Calls Reference Manual for details.
ZVHS-TKN-FILENAME1 is the file name associated with the file error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The primary VHS process determines that its backup process is malfunctioning. The
VHS process stops its backup and attempts to create a new backup after a 10 second
delay.
Recommended Action
For errors 30 through 37, free up system resources. If this does not correct the
problem or results in a different error, contact your service provider and provide all
relevant information as follows:
•
•
•
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a processor dump, if applicable
If your local operating procedures require contacting the Compaq Global Customer
Support Center (GCSC), supply your system number and the numbers and versions of
all related products as well.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -48
111: ZVHS-EVT-PRIMARY-LOG-IO-ERROR
VHS Event Messages
111: ZVHS-EVT-PRIMARY-LOG-IO-ERROR
VHS generates this critical event message when it is unable to access the primary log
file. This condition causes VHS to generate this event message and to continue
processing.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-OPERATION-CODE
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
failed operation on primary log file primary-log-name due to
file-system error file-error.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PRIMARY-LOG-IO-ERROR (111).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -49
111: ZVHS-EVT-PRIMARY-LOG-IO-ERROR
VHS Event Messages
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-OPERATION-CODE is the code corresponding to an I/O operation. The
value can be one of the following:
1. CREATE operation
2. OPEN operation
3. WRITE operation
4. CLOSE operation
5. ACCESS operation (file error on primary log name)
ZVHS-TKN-FILE-ERROR is the file-system error.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS generates this event message when it is unable to access its primary log file.
Recommended Action
The recommended action depends on the file error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -50
112: ZVHS-EVT-PROCESS-DELETED
VHS Event Messages
112: ZVHS-EVT-PROCESS-DELETED
VHS generates this event when the CPU of an application is down.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-PNAME
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-TYPE
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZEMS-TKN-ACTION-ID
ZEMS-TKN-ACTION-NEEDED
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR6
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
Event-Message Text
timestamp pid environment-name: Process process-name deleted
(CPU DOWN).
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROCESS-DELETED (112).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -51
112: ZVHS-EVT-PROCESS-DELETED
VHS Event Messages
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has stopped
communicating with VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process ID number of the application.
ZVHS-TKN-CRTPID is the process ID of the application.
ZVHS-TKN-MESSAGE-TYPE is the type of this message for VHS. Note that
type-of-msg can be one of: INSPECT, DEBUG, DISPLAY, PROMPT, UNKNOWN.
ZVHS-TKN-MESSAGE-STRING is the deleted prompt.
ZVHS-TKN-OBJECTFILE is the object file name of the application.
ZVHS-TKN-USER-ID is the user ID of the application that has stopped communicating
with VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message if the last message received by VHS for this program was a
prompt message.
Probable Cause
The application CPU is down. The VHS process deletes this application entry in its
internal opener table.
Recommended Action
No recommended action needed.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -52
113: ZVHS-EVT-ALTERNATE-CREATED
VHS Event Messages
113: ZVHS-EVT-ALTERNATE-CREATED
VHS generates this informative event message when it has created a new primary log
alternate key file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
created primary log alternate key file primary-log-alternatekey-file-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-ALTERNATE-CREATED (113).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -53
114: ZVHS-EVT-PROMPT-IO-ERROR
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PRIMARY-LOG is the primary log alternate key file name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS process created a new primary log alternate key file.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
114: ZVHS-EVT-PROMPT-IO-ERROR
VHS generates this critical event message when it is unable to access the prompt file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-OPERATION-CODE
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
failed operation on prompt file prompt-file-name due to
file-system error file-error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -54
114: ZVHS-EVT-PROMPT-IO-ERROR
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT-IO-ERROR (114).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-OPERATION-CODE is the code corresponding to an I/O operation. The
value can be one of the following:
1. CREATE operation
2. OPEN operation
3. WRITE operation
4. CLOSE operation
5. ACCESS operation (file error on prompt file)
ZVHS-TKN-FILE-ERROR is the file-system error.
ZVHS-TKN-PROMPT-FILE is the prompt file name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS generates this event message when it is unable to access its primary log file.
Recommended Action
The recommended action depends on the file error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -55
115: ZVHS-EVT-PROMPT-FILE-CREATED
VHS Event Messages
115: ZVHS-EVT-PROMPT-FILE-CREATED
VHS generates this informative event message when it has created a new prompt file.
The prompt file contains the name of the current primary log file for this VHS
environment in its first record. Other records will contain all outstanding prompts for this
VHS environment.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
created prompt file prompt-file-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT-FILE-CREATED (115).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -56
116: ZVHS-EVT-PROMPT-ALT-CREATED
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PROMPT-FILE is the prompt file name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS process created a new prompt file.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
116: ZVHS-EVT-PROMPT-ALT-CREATED
VHS generates this informative event message when it has created a new prompt
alternate key file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
created prompt alternate key file prompt-alternate-key-filename.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -57
116: ZVHS-EVT-PROMPT-ALT-CREATED
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT-ALT-CREATED (116).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PROMPT-FILE is the prompt alternate key file name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS process created a new prompt alternate key file.
Recommended Action
This event message is an informative message only; no corrective action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -58
117: ZVHS-EVT-CLEAN-PROMPT-FILE
VHS Event Messages
117: ZVHS-EVT-CLEAN-PROMPT-FILE
VHS generates this action-completion event message when it restarts and finds
outstanding prompts not processed by the previous VHS process that had the same
VHS process name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-ID
ZEMS-TKN-ACTION-NEEDED
ZVHS-TKN-PNAME
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-CHAR6
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
INITIALIZATION procedure WARNING, unanswered prompt "prompttext" found from program program-name. Prompt was deleted.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-CLEAN-PROMPT-FILE (117).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -59
117: ZVHS-EVT-CLEAN-PROMPT-FILE
VHS Event Messages
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is
informative.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-EMS-ACTION-ID is set to an internal VHS reference number.
ZVHS-EMS-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has prompted
VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CRTPID is the process ID of the application that has prompted VHS.
ZVHS-TKN-MESSAGE-STRING is the prompt text read from the prompt file.
ZVHS-TKN-PRIMARY-LOG is the name of the primary log file for this VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-PROMPT-FILE is the prompt file name of VHS.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current prompt file. This number includes prompts from other VHS processes using the
same prompt file.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS generates this action-completion event message when it restarts and finds
outstanding prompts not processed by the previous VHS process that had the same
VHS process name.
Recommended Action
No corrective action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -60
118: ZVHS-EVT-REMOVE-PROMPT
VHS Event Messages
118: ZVHS-EVT-REMOVE-PROMPT
VHS generates this action-completion event message when it detects that a prompting
application has closed the VHS process without receiving a reply from VHS for its
prompt. VHS deletes the outstanding prompt from its prompt file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-ATTENTION
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Prompt "prompt-text" deleted
in prompt file prompt-file-name because process process-name
is not available for reply.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-REMOVE-PROMPT (118).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -61
118: ZVHS-EVT-REMOVE-PROMPT
VHS Event Messages
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has prompted
VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has prompted VHS.
ZVHS-TKN-MESSAGE-STRING is the prompt text string received by VHS.
ZVHS-TKN-PROMPT-FILE is the prompt file name of VHS.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current prompt file. This number includes prompts from other VHS processes using the
same prompt file.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application.
ZVHS-TKN-USER-ID is the user ID of the application that has sent a prompt to VHS.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -62
119: ZVHS-EVT-BAD-REPLY
VHS Event Messages
Probable Cause
VHS generates this action-completion event message when it detects that a prompting
application has closed the VHS process; VHS deletes the outstanding prompt from its
prompt file.
Recommended Action
No corrective action is necessary.
119: ZVHS-EVT-BAD-REPLY
VHS generates this action-completion event message when it cannot reply to the
application because the application is unavailable.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-CRTPID
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-NEEDED
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PNAME
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CRTPID
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name
unable to reply to prompting process process-name because it
is not available. Reply text "reply-text".
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-BAD-REPLY (119).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -63
119: ZVHS-EVT-BAD-REPLY
VHS Event Messages
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-CRTPID.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CRTPID is the process ID of the application that has prompted VHS.
ZVHS-TKN-MESSAGE-STRING is the prompt text string received by VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application that has prompted
VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS generates this action-completion event message when it cannot reply to the
application because the application is unavailable.
Recommended Action
Correct the problem that has made the application unavailable.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -64
120: ZVHS-EVT-CONFIG-IO-ERROR
VHS Event Messages
120: ZVHS-EVT-CONFIG-IO-ERROR
The VHS Browser generates this event message when an I/O error occurs on the
configuration file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-FILENAME1
ZVHS-TKN-OPERATION-CODE
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-PNAME
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid VHSB: Process VHSB-process-name failed
operation-name on configuration file file-name due to
file-system error file-error.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-CONFIG-IO-ERROR (120).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-CRTPID.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-FILENAME1 is the name of the configuration file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -65
121: ZVHS-EVT-INVALID-LINE-FORMAT
VHS Event Messages
ZVHS-TKN-OPERATION-CODE is the code corresponding to an I/O operation. The
value can be one of the following:
1. CREATE operation
2. OPEN operation
3. WRITE operation
4. CLOSE operation
5. ACCESS operation (file error on prompt file)
ZVHS-TKN-FILE-ERROR is the file-system error.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of the VHS Browser server
ZVHS-TKN-VERSION is the version of the VHS Browser.
Probable Cause
The VHS Browser generates this event message when it is unable to access its
configuration file.
Recommended Action
The recommended action depends on the file error.
121: ZVHS-EVT-INVALID-LINE-FORMAT
The VHS Browser generates this event message when an invalid line format is read in
the configuration file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -66
121: ZVHS-EVT-INVALID-LINE-FORMAT
VHS Event Messages
Event-Message Text
timestamp pid VHSB: Configuration file error. Invalid line
"line" detected in configuration file file-name. Continuing
processing.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INVALID-LINE-FORMAT (121).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZVHS-TKN-PNAME is the process name of the VHS Browser.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of the VHS Browser server.
ZVHS-TKN-VERSION is the version of the VHS Browser.
Probable Cause
The VHS Browser read a line in the configuration file with an invalid format.
Recommended Action
Correct the line in the configuration file with a valid line format.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -67
122: ZVHS-EVT-COLLECTOR ERROR
VHS Event Messages
122: ZVHS-EVT-COLLECTOR ERROR
VHS generates this critical event message when it is unable to write an EMS event to
its alternate collector.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Process VHS-process-name has
an error file-system-error on the Alternate collector
alt-collector-name. Program file vhs-object-file. Primary log
file primary-log-file-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-COLLECTOR-ERROR (122).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -68
123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PRIMARY-LOG is the primary log alternate key file name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS process was unable to log an EMS event to its alternate collector.
Recommended Action
Take action according to the file-system error contained in the EMS event.
123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE
VHS generates this critical message when, in the VHS Inspect file, a section is found
using the LANGUAGE keyword with an undefined language as the section name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Unknown language
inspect-object, the corresponding section is not loaded.
Inspect file inspect-file. Line number number1.number2.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -69
123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-UNKNOWN-LANGUAGE (123).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
An unknown language was found as a section name in the VHS Inspect file. The
corresponding section is skipped. VHS continues loading the VHS Inspect file.
Recommended Action
Edit the file and correct the line specified in the event message. VHS will automatically
reload the Inspect file when another application traps into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -70
124: ZVHS-EVT-INSP-INVALID-FILENAME
VHS Event Messages
124: ZVHS-EVT-INSP-INVALID-FILENAME
VHS generates this critical message when, in the VHS Inspect file, a section is found
using the PROGRAMFILE keyword with an invalid file name as the section name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Invalid program file name
file-name, the corresponding section is not loaded. Inspect
file inspect-file. Line number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-INVALID-FILENAME (124).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -71
124: ZVHS-EVT-INSP-INVALID-FILENAME
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
An invalid file name was found as a section name in the VHS Inspect file. The
corresponding section is skipped. VHS continues loading the VHS Inspect file.
Recommended Action
Edit the file and correct the line specified in the EMS event. VHS will automatically
reload the Inspect file when another application traps into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -72
125: ZVHS-EVT-INSP-INVALID-PROCESS
VHS Event Messages
125: ZVHS-EVT-INSP-INVALID-PROCESS
VHS generates this critical message when, in the VHS Inspect file, a section is found
using the PROCESS keyword with an invalid process name as the section name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Invalid process name processname, the corresponding section is not loaded. Inspect file
inspect-file. Line number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-INVALID-PROCESS (125).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -73
125: ZVHS-EVT-INSP-INVALID-PROCESS
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
An invalid process name was found as a section name in the VHS Inspect file. The
corresponding section is skipped. VHS continues loading the VHS Inspect file.
Recommended Action
Edit the file and correct the line specified in the EMS event. VHS will automatically
reload the Inspect file when another application traps into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -74
126: ZVHS-EVT-INSP-DUPLICATE-SEC
VHS Event Messages
126: ZVHS-EVT-INSP-DUPLICATE-SEC
VHS generates this critical message when, in the VHS Inspect file, more than one
section has the same section name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Inspect section section-name
duplicate, only the first section is loaded. Inspect file
inspect-file. Line number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-DUPLICATE-SEC (126).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -75
126: ZVHS-EVT-INSP-DUPLICATE-SEC
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the name of the rejected section found in the
Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
Two sections with the same name were found in the VHS Inspect file.
Recommended Action
Edit the file and correct the line specified in the EMS event or remove the entire
duplicate section. VHS will automatically reload the Inspect file when another
application traps into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -76
127: ZVHS-EVT-INSP-TABLE-FULL-DATA
VHS Event Messages
127: ZVHS-EVT-INSP-TABLE-FULL-DATA
While loading the VHS Inspect file, VHS generates this critical message when the
amount of data exceeds 5000 bytes.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Not enough space in VHS
inspect table. Limit of 5000 bytes reached. Section
section-name skipped. Inspect file inspect-file. Stopped at
line number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-TABLE-FULL-DATA (127).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -77
128: ZVHS-EVT-INSP-TABLE-FULL-SEC
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the name of the skipped section.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The total of bytes in the VHS Inspect file exceeds 5000.
Recommended Action
Edit the file and remove unnecessary commands or sections. VHS will automatically
reload the Inspect file when another application traps into Inspect.
128: ZVHS-EVT-INSP-TABLE-FULL-SEC
While loading the VHS Inspect file, VHS generates this critical message when the
number of sections exceeds 100.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -78
128: ZVHS-EVT-INSP-TABLE-FULL-SEC
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Too many sections in VHS
inspect table. Limit of 100 sections reached. Inspect file
inspect-file. Stopped at line number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-TABLE-FULL-SEC (128).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the name of the last loaded section.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS Inspect file contains too many sections. The limit is 100 sections.
Recommended Action
Edit the file and remove unnecessary sections. The number of sections must not
exceed 100. VHS will automatically reload the Inspect file when another application
traps into Inspect. See Section 3, Using VHS for more detail on the format of the
Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -79
129: ZVHS-EVT-INSP-PROCESSING-STOP
VHS Event Messages
129: ZVHS-EVT-INSP-PROCESSING-STOP
VHS generates this critical message when it stops processing Inspect prompts for an
application.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PNAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR6
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
Event-Message Text
timestamp pid environment-name: Inspect processing stopped
for process-id-string. The Inspect file was reloaded.
Program file program-file.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-PROCESSING-STOP (129).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -80
130: ZVHS-EVT-INSP-TOO-MUCH-PROMPT
VHS Event Messages
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into
Inspect.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
If the VHS Inspect file is changed while VHS processes Inspect prompts, VHS stops
processing those Inspect prompts for all applications and generates this event.
Recommended Action
None.
130: ZVHS-EVT-INSP-TOO-MUCH-PROMPT
VHS generates this critical message when there are more than 10 prompts from the
same Inspect process.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-INSPECT-OBJECT
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-PNAME
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR50
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -81
130: ZVHS-EVT-INSP-TOO-MUCH-PROMPT
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Integrity problem with the
Inspect process inspect-object. VHS was prompted more than
10 times.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-TOO-MUCH-PROMPT (130).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-INSPECT-OBJECT.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-INSPECT-OBJECT is the name of the Inspect process.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
One Inspect process can handle up to 10 different applications. If Inspect prompts VHS
with more than 10 different applications for one process, VHS does not accept the
application prompts over 10.
Recommended Action
None.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -82
131: ZVHS-EVT-OPEN-TABLE-THRESHOLD
VHS Event Messages
131: ZVHS-EVT-OPEN-TABLE-THRESHOLD
VHS generates this critical message when the VHS opener table reaches or goes over
the configured threshold (parameter OPEN-TABLE-THRESHOLD).
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-TABLE-THRESHOLD
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Opener table for process
vhs-process-name is full at percentage-full%.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-OPEN-TABLE-THRESHOLD (131).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -83
132: ZVHS-EVT-INSP-INVALID-PARAM
VHS Event Messages
ZVHS-TKN-TABLE-THRESHOLD is the value of the OPEN-TABLE-THRESHOLD
parameter.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS opener table has reached the value of the OPEN-TABLE-THRESHOLD
parameter. The default value of this parameter is 90%.
Recommended Action
You might consider using another VHS environment. See Section 3, Using VHS for
more detail.
132: ZVHS-EVT-INSP-INVALID-PARAM
VHS generates this critical message when an invalid parameter in found in the VHS
Inspect file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-OBJECT2
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Invalid parameter parametertext in section section-name, the corresponding section is
not loaded. Inspect file inspect-file. Line number
number1.number2.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -84
132: ZVHS-EVT-INSP-INVALID-PARAM
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-INVALID-PARAM (132).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-INSPECT-OBJECT is the rejected parameter found in the Inspect file.
ZVHS-TKN-INSPECT-OBJECT2 is the name of the section in which the error was
found
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
An invalid parameter was found in a section of the VHS Inspect file.
Recommended Action
Edit the file and correct the line number displayed in the event. VHS will automatically
reload the Inspect file when another application traps into Inspect. See Section 3,
Using VHS for more detail on the format of the Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -85
133: ZVHS-EVT-INSP-LOAD-FILE-ERR
VHS Event Messages
133: ZVHS-EVT-INSP-LOAD-FILE-ERR
VHS generates this informative message when it is unable to reload the VHS Inspect
file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Unable to reload Inspect file
inspect-file.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-LOAD-FILE-ERR (133).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -86
134: ZVHS-EVT-OPENEDIT-ERROR
VHS Event Messages
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A problem occurred when trying to reload the VHS Inspect file.
Recommended Action
Verify the VHS Inspect file condition and security.
134: ZVHS-EVT-OPENEDIT-ERROR
VHS generates this informative message when an error occurs on the EDITOPEN of
the VHS Inspect file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: EDITOPEN error file-error on
inspect-file.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -87
134: ZVHS-EVT-OPENEDIT-ERROR
VHS Event Messages
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-OPENEDIT-ERROR (134).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-FILE-ERROR is the file-system error that occurred on the EDITOPEN of
the VHS Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A problem occurred on the EDITOPEN of the VHS Inspect file.
Recommended Action
Take action according to the file-system error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -88
135: ZVHS-EVT-READEDIT-ERROR
VHS Event Messages
135: ZVHS-EVT-READEDIT-ERROR
VHS generates this informative message when an error occurs on the READEDIT of
the VHS Inspect file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: READEDIT error file-error on
inspect-file.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-READEDIT-ERROR (135).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -89
136: ZVHS-EVT-SET-DEFINE
VHS Event Messages
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-FILE-ERROR is the file-system error that occurred on the READEDIT of
the VHS Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A problem occurred on the READEDIT of the VHS Inspect file.
Recommended Action
Take action according to the file-system error.
136: ZVHS-EVT-SET-DEFINE
VHS generates this critical message when it is unable to alter the value of the Define
=_EMS-COLLECTOR.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-FILE-ERROR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Unable to alter Define
=_EMS_COLLECTOR. Error file-error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -90
136: ZVHS-EVT-SET-DEFINE
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-SET-DEFINE (136).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-FILE-ERROR is the file-system error that occurred on the alter of the
Define =_EMS_COLLECTOR.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A problem occurred while trying to alter the value of the Define =_EMS_COLLECTOR.
Recommended Action
Take action according to the file-system error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -91
137: ZVHS-EVT-INSP-RELOAD-FILE
VHS Event Messages
137: ZVHS-EVT-INSP-RELOAD-FILE
VHS generates this informative message when the VHS Inspect file is reloaded.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Inspect file inspect-file
reloaded.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-RELOAD-FILE (137).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -92
138: ZVHS-EVT-PROMPT-CANCEL
VHS Event Messages
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS Inspect file is reloaded.
Recommended Action
This is an informative message; no action is necessary.
138: ZVHS-EVT-PROMPT-CANCEL
VHS generates this action-completion message when a prompt is canceled by its
application.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-NEEDED
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -93
138: ZVHS-EVT-PROMPT-CANCEL
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Prompt "prompt-string"
deleted in prompt file prompt-file because the prompt has
been canceled by process process-id-string.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT-CANCEL (138).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the Inspect process.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application that canceled the
prompt.
ZVHS-TKN-MESSAGE-STRING is the deleted prompt.
ZVHS-TKN-PROMPT-FILE is the name of the VHS prompt file.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current prompt file. This number includes prompts from other VHS processes using the
same prompt file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -94
138: ZVHS-EVT-PROMPT-CANCEL
VHS Event Messages
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has canceled the
prompt.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
An application has canceled a previous prompt by sending a Cancel message.
Recommended Action
None.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -95
139: ZVHS-EVT-PROMPT-NOT-UNIQUE
VHS Event Messages
139: ZVHS-EVT-PROMPT-NOT-UNIQUE
VHS generates this action-completion message when a prompt must be deleted from
the prompt file because the application has prompted VHS again; VHS only accepts
one prompt at a time by an application.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-NEEDED
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CRTPID
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Prompt "prompt-string"
deleted in prompt file prompt-file because another prompt has
been received from process process-id-string.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT-NOT-UNIQUE(139).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -96
139: ZVHS-EVT-PROMPT-NOT-UNIQUE
VHS Event Messages
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to FALSE to specify that this is an actioncompletion event message.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the Inspect process.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application that canceled the
prompt.
ZVHS-TKN-MESSAGE-STRING is the deleted prompt.
ZVHS-TKN-PROMPT-FILE is the name of the VHS prompt file.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current prompt file. This number includes prompts from other VHS processes using the
same prompt file.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-APPLICATION-NAME is the name of the application sending a new
prompt.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS has received a second prompt from an application without sending a reply to the
first one. VHS deleted the first prompt from its prompt file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -97
140: ZVHS-EVT-INSP-INVALID-KEYWORD
VHS Event Messages
Recommended Action
None.
140: ZVHS-EVT-INSP-INVALID-KEYWORD
VHS generates this critical message when an invalid keyword is found in the VHS
Inspect file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Invalid keyword inspectobject. Inspect file inspect-file. Line number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-INVALID-KEYWORD(140).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -98
140: ZVHS-EVT-INSP-INVALID-KEYWORD
VHS Event Messages
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
An Invalid keyword was found in the VHS Inspect file. Only PROGRAM, PROCESS
and LANGUAGE are valid keywords.
Recommended Action
Edit the file and correct the line number displayed in the event. VHS will automatically
reload the Inspect file when another application traps into Inspect. See Section 3,
Using VHS for more detail on the format of the Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C -99
141: ZVHS-EVT-INSP-LINE-TOO-LONG
VHS Event Messages
141: ZVHS-EVT-INSP-LINE-TOO-LONG
VHS generates this critical message when a line in the VHS Inspect file exceeds
132 characters.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Line number number1.number2
is too long, only the first 132 characters are kept. Inspect
file inspect-file.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-LINE-TOO-LONG(141).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-100
143: ZVHS-EVT-INSP-LOAD-FILE
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A line from the VHS Inspect file has more than 132 characters. Only the first
132 characters are kept.
Recommended Action
Edit the file and correct the line number displayed in the event. VHS will automatically
reload the Inspect file when another application traps into Inspect. See Section 3,
Using VHS for more detail on the format of the Inspect file.
143: ZVHS-EVT-INSP-LOAD-FILE
VHS generates this informative message when the VHS Inspect file is loaded at
startup time.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-101
143: ZVHS-EVT-INSP-LOAD-FILE
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Inspect file inspect-file
loaded.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-LOAD-FILE (143).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS Inspect file is loaded.
Recommended Action
This is an informative event; no action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-102
144: ZVHS-EVT-INSP-RELOAD-FILE-ERR
VHS Event Messages
144: ZVHS-EVT-INSP-RELOAD-FILE-ERR
VHS generates this informative message when it is unable to reload the VHS Inspect
file.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Unable to reload Inspect file
inspect-file.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-RELOAD-FILE-ERR (144).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-103
145: ZVHS-EVT-INSP-INVALID-REMOTE
VHS Event Messages
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
A problem occurred while reloading the VHS Inspect file.
Recommended Action
Verify the file condition and security. You might need to edit the file. If the file is
modified, VHS will automatically reload the Inspect file when another application traps
into Inspect. See Section 3, Using VHS for more detail on the format of the Inspect file.
145: ZVHS-EVT-INSP-INVALID-REMOTE
VHS generates this critical message when, in the VHS Inspect file, a section name,
process, or program file name is a remote process or program file name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Section name section-name
remote, the corresponding section is not loaded. Inspect file
inspect-file. Line number number1.number2.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-104
145: ZVHS-EVT-INSP-INVALID-REMOTE
VHS Event Messages
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-INVALID-REMOTE (145).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
In the VHS Inspect file, a section name, process, or program file name is a remote
process or program file name. VHS only accepts a local process name and local
program file name.
Recommended Action
Edit the file and correct the line number displayed in the event. VHS will automatically
reload the Inspect file when another application traps into Inspect. See Section 3,
“Using VHS,” for more detail on the format of the Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-105
146: ZVHS-EVT-INSP-FILE-NOT-EXIST
VHS Event Messages
146: ZVHS-EVT-INSP-FILE-NOT-EXIST
VHS generates this critical message when, in the VHS Inspect file, a section name for
the PROGRAMFILE keyword is a file that does not exist.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Program file file-name does
not exist, the corresponding section is not loaded. Inspect
file inspect-file. Line number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-FILE-NOT-EXIST (146).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-106
146: ZVHS-EVT-INSP-FILE-NOT-EXIST
VHS Event Messages
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
In the VHS Inspect file, a section name for the PROGRAMFILE keyword specified a file
name that does not exist. The file must exist.
Recommended Action
Edit the file and correct the line number displayed in the event. VHS will automatically
reload the Inspect file when another application traps into Inspect. See Section 3,
Using VHS for more detail on the format of the Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-107
147: ZVHS-EVT-INSP-INVALID-TEXT
VHS Event Messages
147: ZVHS-EVT-INSP-INVALID-TEXT
VHS generates this critical message when, in the VHS Inspect file, one or more
characters are found following a section name.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INSPECT-OBJECT
ZVHS-TKN-INSPECT-OBJECT2
ZVHS-TKN-INSPECT-FILE
ZVHS-TKN-EDIT-LINE1
ZVHS-TKN-EDIT-LINE2
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-CHAR50
ZSPI-TYP-INT2
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Invalid text inv-text
following section name section-name, the corresponding
section is not loaded. Inspect file inspect-file. Line
number number1.number2.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSP-INVALID-TEXT (147).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-108
147: ZVHS-EVT-INSP-INVALID-TEXT
VHS Event Messages
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INSPECT-OBJECT is the rejected line found in the Inspect file.
ZVHS-TKN-INSPECT-OBJECT is the name of the rejected section from the
Inspect file.
ZVHS-TKN-INSPECT-FILE is the name of the VHS Inspect file.
ZVHS-TKN-EDIT-LINE1 is the first part of the EDIT line number of the line in error.
ZVHS-TKN-EDIT-LINE2 is the second part of the EDIT line number of the line in error.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
VHS generates this message when, in the VHS Inspect file, one or more characters
are found following a section name.
Recommended Action
Edit the file and correct the line number displayed in the event. VHS will automatically
reload the Inspect file when another application traps into Inspect. See Section 3,
Using VHS for more detail on the format of the Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-109
148: ZVHS-EVT-CLEAN-TABLE
VHS Event Messages
148: ZVHS-EVT-CLEAN-TABLE
VHS generates this event when an application stops communicating with VHS.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-PNAME
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-TYPE
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZEMS-TKN-ACTION-ID
ZEMS-TKN-ACTION-NEEDED
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR6
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
Event-Message Text
timestamp pid environment-name: Process process-name deleted
from internal table because this process stopped
communicating with VHS. Message type type-of-msg. Program
file program-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-CLEAN-TABLE (148).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-110
148: ZVHS-EVT-CLEAN-TABLE
VHS Event Messages
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has stopped
communicating with VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application.
ZVHS-TKN-MESSAGE-TYPE is the type of this message for VHS. type-of-msg
can be one of the following: INSPECT, DEBUG, DISPLAY, PROMPT, or UNKNOWN.
ZVHS-TKN-OBJECTFILE is the object file name of the application.
ZVHS-TKN-USER-ID is the user ID of the application that has stopped communicating
with VHS.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is FALSE to specify this is an action-completion
message if the last message received for this program was a prompt message.
Probable Cause
An application stopped communicating with VHS. The VHS process deletes this
application entry in its internal opener table.
Recommended Action
You might verify the status of the application.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-111
150: ZVHS-EVT-INSPECT-EXTENDED
VHS Event Messages
150: ZVHS-EVT-INSPECT-EXTENDED
VHS generates this informative message when receiving a message from Inspect or
sending a message to Inspect before knowing which application is trapped into
Inspect. This event is generated only when the VHS-GUI-MODE parameter is set to
ON.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-SEND-RECEIVE-MSG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZEMS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Inspect process process-idstring. Message "message-string" [received from|sent to]
Inspect. Program file program-name. Primary log file primarylog-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-EXTENDED (150).
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-112
150: ZVHS-EVT-INSPECT-EXTENDED
VHS Event Messages
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-TRUE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has gone into Inspect.
ZVHS-TKN-MESSAGE-STRING is the message text received from or sent to Inspect.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into
Inspect.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-SEND-RECEIVE-MSG indicates if the message contained in token ZVHSTKN-MESSAGE-STRING was received from Inspect or sent to Inspect. If it is ZVHSVAL-INSPECT-RECEIVE (0) the message was received from Inspect. If it is ZVHSINSPECT-SEND (1) the message was sent by VHS to Inspect.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
An application entered Inspect. VHS received a message from Inspect or sent a
message to Inspect and still does not know which application is trapped into Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-113
151: ZVHS-EVT-INSPECT-APPL-EXT
VHS Event Messages
The text received from or sent to Inspect is the text of this message. This event
message is generated only when the VHS-GUI-MODE parameter is set to ON.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
151: ZVHS-EVT-INSPECT-APPL-EXT
VHS generates this informative message when receiving a message from Inspect or
sending a message to Inspect after knowing which application is trapped into Inspect.
The application is not a SCobol program. This event is generated only when the VHSGUI-MODE parameter is set to ON.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-SEND-RECEIVE-MSG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZEMS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-114
151: ZVHS-EVT-INSPECT-APPL-EXT
VHS Event Messages
Event-Message Text
timestamp pid environment-name: Process process-id-string
entered Inspect. Message "message-string" [received from|sent
to] Inspect. Program file program-name. Primary log file
primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-APPL-EXT (151).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-TRUE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the application that has gone into Inspect.
ZVHS-TKN-MESSAGE-STRING is the message text received from or sent to Inspect.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into
Inspect.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-SEND-RECEIVE-MSG indicates if the message contained in token ZVHSTKN-MESSAGE-STRING was received from Inspect or sent to Inspect. If it is ZVHSVAL-INSPECT-RECEIVE (0) the message was received from Inspect. If it is ZVHSINSPECT-SEND (1) the message was sent by VHS to Inspect.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-115
151: ZVHS-EVT-INSPECT-APPL-EXT
VHS Event Messages
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
An application entered Inspect. VHS received a message from Inspect or sent a
message to Inspect and knows which application is trapped into Inspect. The text
received from or sent to Inspect is the text of this message. This event message is
generated only when the VHS-GUI-MODE parameter is set to ON.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-116
152: ZVHS-EVT-INSPECT-SCOBOL-EXT
VHS Event Messages
152: ZVHS-EVT-INSPECT-SCOBOL-EXT
VHS generates this informative message when receiving a message from Inspect or
sending a message to Inspect after knowing which application is trapped into Inspect.
The application is a SCobol program. This event is generated only when the VHS-GUIMODE parameter is set to ON.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-TERMNAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-SUBSYSTEM-MANAGER
ZVHS-TKN-APPLICATION-NAME
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PNAME
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-SEND-RECEIVE-MSG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZEMS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR16
ZSPI-TYP-STRING
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-FNAME32
ZSPI-TYP-CHAR8
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Pathway terminal terminalname entered Inspect. Message "message-string" [received
from|sent to] Inspect. PATHMON process name pathmon-name.
Inspect process process-id-string. Primary log file primarylog-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-117
152: ZVHS-EVT-INSPECT-SCOBOL-EXT
VHS Event Messages
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INSPECT-SCOBOL-EXT (152).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-TERMNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-TRUE.
ZSPI-TKN-SUBSYSTEM-MANAGER contains the name of the PATHMON process
that controls this Pathway terminal.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Inspect.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID of the Inspect process.
ZVHS-TKN-MESSAGE-STRING is the message text received from or sent to Inspect.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-TERMNAME is the terminal name of the SCREEN COBOL program that
has gone into Inspect.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-SEND-RECEIVE-MSG indicates if the message contained in token ZVHSTKN-MESSAGE-STRING was received from Inspect or sent to Inspect. If it is ZVHSVAL-INSPECT-RECEIVE (0) the message was received from Inspect. If it is ZVHSINSPECT-SEND (1) the message was sent by VHS to Inspect.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-118
152: ZVHS-EVT-INSPECT-SCOBOL-EXT
VHS Event Messages
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
An application entered Inspect. VHS received a message from Inspect or sent a
message to Inspect and knows which application is trapped into Inspect. The
application is a SCobol program. The text received from or sent to Inspect is the text of
this message. This event message is generated only when the VHS-GUI-MODE
parameter is set to ON.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-119
153: ZVHS-EVT-DEBUG-EXTENDED
VHS Event Messages
153: ZVHS-EVT-DEBUG-EXTENDED
VHS generates this informative message when receiving a message from Debug or
sending a message to Debug. This event is generated only when the VHS-GUI-MODE
parameter is set to ON.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PNAME
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-SEND-RECEIVE-MSG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Conditional Tokens
ZVHS-TKN-JOBID
ZEMS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string
entered Debug. Message "message-string" [received from|sent
to] Debug. Program file program-name. Primary log file
primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-120
153: ZVHS-EVT-DEBUG-EXTENDED
VHS Event Messages
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-DEBUG-EXTENDED (153).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-TRUE.
ZVHS-TKN-APPLICATION-NAME is the name of the application that has gone into
Debug.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
ZVHS-TKN-CRTPID is the process ID in of the application that has gone into Debug.
ZVHS-TKN-MESSAGE-STRING is the message text received from or sent to Debug.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into Debug.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-SEND-RECEIVE-MSG indicates if the message contained in token ZVHSTKN-MESSAGE-STRING was received from Inspect or sent to Inspect. If it is ZVHSVAL-INSPECT-RECEIVE (0) the message was received from Inspect. If it is ZVHSINSPECT-SEND (1) the message was sent by VHS to Inspect.
ZVHS-TKN-USER-ID is the user ID of the application trapped into Debug.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-121
153: ZVHS-EVT-DEBUG-EXTENDED
VHS Event Messages
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
An application entered Debug. VHS received a message from Debug or sent a
message to Debug. The text received from or sent to Debug is the text of this
message. This event message is generated only when the VHS-GUI-MODE parameter
is set to ON.
Recommended Action
Advise software personnel of this event message. More information about the problem
is available in the primary log file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-122
154: ZVHS-EVT-PROMPT-RESEND
VHS Event Messages
154: ZVHS-EVT-PROMPT-RESEND
VHS generates this action-attention event message when an outstanding prompt has
been pending for at least the value of the PROMPT-EVENT-RESEND-DELAY
parameter (in minutes). This event is generated for the number of minutes specified by
each PROMPT-EVENT-RESEND-DELAY for as long as the prompt stays outstanding.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-APPLICATION-NAME
ZEMS-TKN-PROC-DESC
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZEMS-TKN-ACTION-ATTENTION
ZEMS-TKN-ACTION-ID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-CPU
ZVHS-TKN-PIN
ZVHS-TKN-CRTPID
ZVHS-TKN-PNAME
ZVHS-TKN-OBJECTFILE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-PROMPT-FILE
ZVHS-TKN-PROMPT-NUMBER
ZVHS-TKN-PROMPT-TIMESTAMP
ZVHS-TKN-PROMPT-TS-TIMESTAMP
ZVHS-TKN-PROMPT-INDEX
ZVHS-TKN-PRIMARY-LOG
ZVHS-TKN-USER-ID
ZVHS-TKN-VHS-EMS-COLLECTOR
ZVHS-TKN-VHS-GUI-MODE
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR8
ZSPI-TYP-STRING
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-INT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-CHAR6
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT4
ZSPI-TYP-INT2
ZSPI-TYP-FNAME
ZSPI-TYP-CHAR16
ZSPI-TYP-CHAR16
ZSPI-TYP-INT
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-123
154: ZVHS-EVT-PROMPT-RESEND
VHS Event Messages
Conditional Tokens
ZVHS-TKN-JOBID
ZVHS-TKN-PREVIOUS-MESSAGE-1
ZVHS-TKN-PREVIOUS-MESSAGE-2
ZVHS-TKN-PREVIOUS-MESSAGE-3
ZVHS-TKN-PREVIOUS-MESSAGE-4
ZVHS-TKN-PREVIOUS-MESSAGE-5
ZVHS-TKN-PREV-TIMESTAMP-1
ZVHS-TKN-PREV-TIMESTAMP-2
ZVHS-TKN-PREV-TIMESTAMP-3
ZVHS-TKN-PREV-TIMESTAMP-4
ZVHS-TKN-PREV-TIMESTAMP-5
ZEMS-TKN-SUBDEVICE
Token Type
ZSPI-TYP-INT
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-CHAR132
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-CHAR16
Event-Message Text
timestamp pid environment-name: Process process-id-string.
Prompt "prompt-string". Program file program-name. Primary
log file primary-log-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-PROMPT-RESEND (154).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-APPLICATION-NAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-FALSE because this event message is an
action-attention event message.
(ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-TRUE.
ZEMS-TKN-ACTION-ID is set to an internal VHS reference number.
ZEMS-TKN-ACTION-NEEDED is set to TRUE to specify that this is an action-attention
event message.
ZVHS-TKN-APPLICATION-NAME is the application that has prompted VHS.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
ZVHS-TKN-CPU is the CPU number the application is running in.
ZVHS-TKN-PIN is the process number of the application.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-124
154: ZVHS-EVT-PROMPT-RESEND
VHS Event Messages
ZVHS-TKN-CRTPID is the process ID of the application that has prompted VHS.
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-OBJECTFILE is the object file of the application that prompted VHS.
ZVHS-TKN-MESSAGE-STRING is the prompt string received by VHS.
ZVHS-TKN-PROMPT-FILE is the name of the prompt file of VHS.
ZVHS-TKN-PROMPT-NUMBER is the current number of outstanding prompts in the
current Prompt file. This number includes prompts from other VHS processes using the
same prompt file.
ZVHS-TKN-PROMPT-TIMESTAMP is the timestamp of this prompt in LCT format.
ZVHS-TKN-PROMPT-TS-INTERNAL is the timestamp of this prompt in fixed format. It
is represented in LCT. This token is only used by the VHS GUI.
ZVHS-TKN-PROMPT-INDEX is the entry index in the internal opener table of VHS
where the prompt information is stored.
ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
ZVHS-TKN-USER-ID is the user ID of the application that has sent a prompt to VHS.
ZVHS-TKN-VHS-EMS-COLLECTOR is the EMS Collector name used by VHS to
generate its EMS events.
ZVHS-TKN-VHS-GUI-MODE indicates if the VHS process is running in GUI mode or
not. ZVHS-VAL-VHS-GUI-OFF (0) indicates that the VHS-GUI-MODE parameter is set
to OFF. ZVHS-VAL-VHS-GUI-ON (1) indicates that the VHS-GUI-MODE parameter is
set to ON.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Conditional Tokens
ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into
Inspect.
ZVHS-TKN-PREVIOUS-MESSAGE-1 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the oldest one.
ZVHS-TKN-PREVIOUS-MESSAGE-2 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-1.
ZVHS-TKN-PREVIOUS-MESSAGE-3 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-125
154: ZVHS-EVT-PROMPT-RESEND
VHS Event Messages
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-2.
ZVHS-TKN-PREVIOUS-MESSAGE-4 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-3.
ZVHS-TKN-PREVIOUS-MESSAGE-5 is the text of a previous message received from
the same application. VHS keeps the last five messages preceding the prompt and
received by the same application. This token contains the message text received after
the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-4, which means the
one received just before the prompt.
ZVHS-TKN-PREV-TIMESTAMP-1 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-1. Token ZVHS-TKN-PREV-TIMESTAMP-1
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-1 is present.
ZVHS-TKN-PREV-TIMESTAMP-2 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-2. Token ZVHS-TKN-PREV-TIMESTAMP-2
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-2 is present.
ZVHS-TKN-PREV-TIMESTAMP-3 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-3. Token ZVHS-TKN-PREV-TIMESTAMP-3
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-3 is present.
ZVHS-TKN-PREV-TIMESTAMP-4 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-4. Token ZVHS-TKN-PREV-TIMESTAMP-4
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-4 is present.
ZVHS-TKN-PREV-TIMESTAMP-5 is the timestamp of the message text contained in
token ZVHS-TKN-PREVIOUS-MESSAGE-5. Token ZVHS-TKN-PREV-TIMESTAMP-5
is present only if token ZVHS-TKN-PREVIOUS-MESSAGE-5 is present.
ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application
trapped into Inspect.
Probable Cause
A prompt has been pending for at least the value of the PROMPT-EVENT-RESENDDELAY parameter (in minutes).
Recommended Action
Use the VHS GUI to select and answer the application prompt.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-126
200: ZVHS-EVT-INTERNAL-ERROR
VHS Event Messages
200: ZVHS-EVT-INTERNAL-ERROR
VHS generates this critical event message when it encounters an internal error.
Unconditional Tokens
ZSPI-TKN-SSID
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-CPU
ZEMS-TKN-SUBJECT-MARK
ZVHS-TKN-PNAME
ZEMS-TKN-CRTPID
ZEMS-TKN-EMPHASIS
ZEMS-TKN-GENTIME
ZEMS-TKN-LOGTIME
ZEMS-TKN-PIN
ZEMS-TKN-SUPPRESS-DISPLAY
ZEMS-TKN-SYSTEM
ZEMS-TKN-USERID
ZVHS-TKN-ENVIRONMENT-NAME
ZVHS-TKN-INTERNAL-ERROR-CODE
ZVHS-TKN-MESSAGE-STRING
ZVHS-TKN-VHS-OBJECTFILE
ZVHS-TKN-VERSION
ZEMS-TKN-TEXT
Token Type
ZSPI-TYP-SSID
ZSPI-TYP-INT
ZSPI-TYP-INT
ZSPI-TYP-SSCTL
ZSPI-TYP-CHAR6
ZSPI-TYP-CRTPID
ZSPI-TYP-BOOLEAN
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-TIMESTAMP
ZSPI-TYP-INT
ZSPI-TYP-BOOLEAN
ZSPI-TYP-UINT
ZSPI-TYP-UINT
ZSPI-TYP-CHAR8
ZSPI-TYP-INT
ZSPI-TYP-CHAR254
ZSPI-TYP-FNAME
ZSPI-TYP-INT
ZSPI-TYP-CHAR800
Event-Message Text
timestamp pid environment-name: Internal error internalerror-code occurred in VHS due to error text. Program
filename program-name.
Unconditional Tokens
ZSPI-TKN-SSID is the subsystem ID for VHS and is described in the SPI Programming
Manual. The value of this token is always ZVHS-VAL-SSID.
ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event
message is ZVHS-EVT-INTERNAL-ERROR (200).
ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes
the subject token ZVHS-TKN-PNAME.
ZEMS-TKN-EMPHASIS is set to ZSPI-VAL-TRUE because this event message is
critical.
(ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and
TEXT are described under EMS Standard Definitions on page C-5.
ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS. If no
environment name is defined using the VHS startup parameter ENVIRONMENTPARAM, then the default value is VHS.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-127
200: ZVHS-EVT-INTERNAL-ERROR
VHS Event Messages
ZVHS-TKN-PNAME is the process name of VHS.
ZVHS-TKN-INTERNAL-ERROR-CODE is the code associated with the internal error.
The value of this code is in the range 2001 through 2027.
Note that internal-error-code and internal-error-text can be one of the
following:
2001
CHECKMONITOR error error-number.
2002
CHECKPOINT illegal parameter parameter-number.
2003
$RECEIVE read error error-number.
2004
$RECEIVE reply error error-number.
2005
Invalid savefile name file-name. Error error-number.
2006
Savefile name file-name not NNNN form
2007
Invalid log file name file-name. Error error-number.
2008
Primary log file name file-name not NNNN form.
2009
SPI error error-number with procedure SSPUTTKN.
2010
SPI error error-number with procedure SSGETTKN.
2011
SPI error error-number with procedure SSPUT.
2012
SPI error error-number with procedure SSGET.
2013
SPI error error-number with procedure SSMOVE.
2014
SPI error error-number with procedure SSNULL.
2015
SPI error error-number with procedure SSINIT.
2016
SIGNALTIMEOUT. Unable to allocate TLE or illegal timeout value
timeout-value .
2017
CANCELTIMEOUT. Invalid tag value timeout-number.
2018
Invalid event number event-number.
2019
CREATION of file file-name FAILED due to file-system error errornumber.
2020
OPEN FAILED on file file-name due to file-system error error-number.
2021
CHECK SETMODE FAILED on file file-name due to file-system error
error-number.
2022
Invalid prompt file name file-name. Error error-number.
2023
Demo copy expiration date passed.
2024
Prompt file name file-name does not have the VHS prompt file format.
2025
Primary log file name file-name mismatch. Current primary file name
file-name.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-128
200: ZVHS-EVT-INTERNAL-ERROR
VHS Event Messages
2026
Invalid Primary log file name file-name. Must have 3 characters.
2027
The Primary log file name file-name is not a local file name.
or
The Savefile name file-name is not a local file name.
2028
VHSB: Prompt file file-name is not a local file name.
or
VHSB: Configuration file file-name is not local file name.
2029
VHSB: Invalid file name file-name.
2030
VHSB: Invalid configuration file name file-name. Error error-number.
2031
Internal Error.
ZVHS-TKN-MESSAGE-STRING is the error message string corresponding to the
internal error code.
ZVHS-TKN-VHS-OBJECTFILE is the object file name of VHS.
ZVHS-TKN-VERSION is the version of VHS.
Probable Cause
The VHS process or the VHSBSVR has encountered an internal error.
Recommended Action
Recovery. Contact your service provider and provide all relevant information as
follows:
•
•
•
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a processor dump, if applicable
If your local operating procedures require contacting the Compaq Global Customer
Support Center (GCSC), supply your system number and the numbers and versions of
all related products as well.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-129
VHS Event Messages
200: ZVHS-EVT-INTERNAL-ERROR
Virtual Hometerm Subsystem (VHS) Manual—429311-001
C-130
D
VHSCI Command Summary
This appendix gives a summary of all the commands available in the conversational
interface of VHS, the VHSCI. For detailed information on each of these commands,
refer to Section 7, Command Descriptions.
(page 1 of 2)
Commands
Description
!
Reexecutes a command line
?
Displays a specific command line
ALIAS
Defines a command or text abbreviation
ALLOW
Specifies the number of errors or warnings permitted during the
execution of an OBEY (command) file
ALTER
Changes the values of the attributes of an existing VHS object
ASSIGN
Changes, adds, and displays ASSIGN messages that are
passed to new processes initiated by VHSCI RUN command
ASSUME
Sets the default object type, object name, or both
CLEAR
Clears the logical file assignments made with the ASSIGN
command. Parameters are set with the PARAM command, and
aliases are defined with the ALIAS command
COMMENT
Allows you to enter comments or descriptions in OBEY
(command) files
CONFIRM
Enables or disables the display of positive responses from
subsystems
CPUS
Displays the names of all known systems on the network and the
states of their associated CPUs
DELAY
Suspends VHSCI processing for a specified time interval
DETAIL ERROR
Enables or disables detailed error descriptions
ENV
Displays the settings of various VHSCI session parameters,
referred to as environmental parameters
EXIT
Terminates a VHSCI session
FC
Allows you to correct a VHSCI command line (fix command)
HELP
Displays information about VHSCI commands
HISTORY
Displays previously entered commands
INFO
Displays the attribute values for the specified object
LISTOPENS
Lists all processes which currently open the specified object
LOG
Directs a copy of entered VHSCI commands and displays to a file
OBEY
Causes commands to be read from a disk file
OUT
Redirects VHSCI displays to a designated location, such as terminal,
spooler, or out file
Virtual Hometerm Subsystem (VHS) Manual—429311-001
D- 1
VHSCI Command Summary
(page 2 of 2)
Commands
Description
PAGESIZE
Sets the terminal screen size and printer page size
PARAM
Changes, adds, and displays PARAM values that are passed to a
process initiated by VHSCI RUN command
PAUSE
Suspends VHSCI and releases the terminal for use by another
process. Usually, this command is used in conjunction with the RUN
command
REPEAT
Causes the remainder of the command line to be repeated for a
specific number of iterations, or until the BREAK key is activated
RUN
Runs another program from within VHSCI
SETPROMPT
Changes the command line prompt
STATS
Displays the accumulated statistics for an object and optionally resets
them
STATUS
Displays information about the specified object
SYSTEM
Sets the default system name for all file name and object name
expansion
TIMEOUT
Enables the user to vary the amount of time VHSCI waits for a
response before canceling the request
VERSION
Displays the version level of the specified object
VOLUME
Sets the default volume and subvolume names for all file name
expansion
Virtual Hometerm Subsystem (VHS) Manual—429311-001
D- 2
E
VHS Process Messages
VHS Process not named.
Cause. In the run command you did not specify the NAME option for the VHS
process. VHS must run as a named process.
Recovery. In the run command use the NAME option.
VHS Invalid backup cpu: backup-cpu
Cause. The backup CPU option in the run command is an invalid CPU number.
Recovery. Specify a valid backup CPU in the run command.
VHS $RECEIVE open error: error-number
Cause. An error occurred when VHS opened the file $RECEIVE.
Recovery. The recommended action depends on the file error.
VHS Error invoking SETMODE on filename : error-number
Cause. An error occurred when VHS was invoking the SETMODE on a file.
Recovery. The recommended action depends on the file error.
VHS EMS collector open error: error-number
Cause. An error occurred when VHS opened the EMS collector.
Recovery. The recommended action depends on the file error.
VHS EMS collector write error error-number while generating
event event-number.
Cause. An error occurred when VHS wrote an EMS message to the collector.
Recovery. The recommended action depends on the file error.
VHS Initialize Egen Record error: error-number
Cause. An error occurred when VHS initialized the Egen record.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
E- 1
VHS Process Messages
Recovery. Contact your service provider.
VHS Egen error: error-number
Cause. There is an error with Egen.
Recovery. Contact your service provider.
VHS Invalid event number event-number
Cause. VHS tried to generate an invalid event message.
Recovery. Contact your service provider.
VHS The primary filename filename is not a local filename
Cause. A remote filename was given with the PRIMARY-LOGFILE ASSIGN.
Recovery. Specify a local filename with the PRIMARY-LOGFILE ASSIGN.
VHS The Savefile name filename is not a local filename
Cause. A remote filename was given with the SAVEABEND-FILE ASSIGN.
Recovery. Specify a local filename with the SAVEABEND-FILE ASSIGN.
VHS Error error-number on Primary log file filename
Cause. An error occurred when VHS did an I/O operation on the primary log file.
Recovery. The recommended action depends on the file error.
VHS Invalid Primary log name filename Must be 3 characters.
Cause. The file name specified with the PRIMARY-LOGFILE ASSIGN has more than
three alphabetic characters.
Recovery. Specify a file name with three alphabetic characters for the PRIMARYLOGFILE ASSIGN.
VHS Primary filename mismatch. Current current-primary-fname
Cause. The primary file name does not match the one associated with prompt file on
this subvolume.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
E- 2
VHS Process Messages
Recovery. Specify the primary log file name corresponding with the prompt file on this
subvolume or specify the subvolume of the desired location of the prompt file.
VHS Error error-number on Prompt file filename
Cause. An error occurred when VHS did an I/O operation on the prompt file.
Recovery. The recommended action depends on the file error.
VHS Invalid Prompt file name filename. Error error-number
Cause. The prompt file name is invalid. VHS takes the volume and the subvolume of
the primary log file name and adds PROMPT as suffix to the prompt file name.
Recovery. Give a valid volume and subvolume for the PRIMARY-LOGFILE ASSIGN.
VHS will create a valid prompt file name with the volume and subvolume of this
ASSIGN.
VHS Prompt file filename does not have VHS prompt file
format.
Cause. VHS takes the volume and the subvolume of the primary log file name and
adds PROMPT as suffix to the prompt file name. On this subvolume the prompt file
does not have the VHS prompt file format.
Recovery. With the PRIMARY-LOGFILE ASSIGN, specify a subvolume where the
prompt file is a VHS prompt file or specify another subvolume for the primary file name
where the prompt file does not exist.
VHS invalid file security: "security".
Cause. The PRIMARY-SECURITY parameter does not have the valid file security
syntax.
Recovery. Correct the syntax of the PRIMARY-SECURITY parameter.
VHS Environment env-name is not valid. Only one word is
accepted.
Cause. Environment name is composed of more than one word.
Recovery. Modify the environment name in the VHS startup file (VHSSTART).
VHS Environment env-name contains invalid character.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
E- 3
VHS Process Messages
Cause. Environment name has invalid characters.
Recovery. Modify the environment-name parameter in the VHS startup file
(VHSSTART). The first character must be alphabetic. All other characters can be
alphabetic or numeric or a “-”. The environment-name length can be from 1 to 8
characters long.
VHS Environment env-name contains more than 8 characters
Cause. Environment-name is too long.
Recovery. Modify the environment-name parameter in the VHS startup file
(VHSSTART). The first character must be alphabetic. All other characters can be
alphabetic or numeric or a “-”. The environment-name length can be from 1 to 8
characters long.
VHS Remote Inspect file file-name rejected.
Cause. Inspect file is remote. Only a local file is accepted.
Recovery. Put the Inspect file on the same system as VHS.
VHS Unable to load Inspect file file-name.
Cause. Unable to access the VHS Inspect file.
Recovery. Verify the status of the VHS Inspect file.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
E- 4
F
VHS Browser Messages
This section lists the error and advisory messages displayed by the VHS Browser.
Advisory messages provide VHS Browser warnings or action steps. Error messages
inform you of erroneous operations or when actions cannot be completed.
Error messages have associated message numbers. Advisory messages do not
display a number. Advisory messages are identified by an (A) within this listing.
The messages are displayed on line 23 of the Prompt Detail screen and on line 21 of
all other screens. In the case of error messages, the message number follows the text
of the error message. Certain error messages display a second number that provides
additional error information, such as a NonStop Kernel file-system error number or the
SCREEN COBOL TERMINATION-STATUS special register.
0001
Illegal server class name.
Probable Cause. The server class name you entered is illegal.
Recommended Action. Verify the syntax.
0002
Illegal PATHMON name.
Probable Cause. The PATHMON name you entered is illegal.
Recommended Action. Verify the syntax.
0003
Illegal system name.
Probable Cause. The system name you entered is illegal.
Recommended Action. Verify the syntax.
0004
An I/O error occurred on request to the server or PATHMON.
Probable Cause. The SEND request resulted in an I/O error. The error is indicated by
the second number in the message. The second number in the error message
indicates the content of the SCREEN COBOL TERMINATION-STATUS special
register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of SEND errors.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-1
VHS Browser Messages
0005
PATHMON is unavailable.
Probable Cause. The PATHMON name does not exist.
Recommended Action. Provide another PATHMON name.
0006
A problem occurred while communicating with the VHS Server.
Probable Cause. The SEND request resulted in an I/O error. The error is indicated by
the second number in the message. The second number in the error message
indicates the content of the SCREEN COBOL TERMINATION-STATUS special
register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of SEND errors.
0007
Server class is undefined.
Probable Cause. The server class does not exist.
Recommended Action. Provide another server class.
0008
Undefined system.
Probable Cause. The system does not exist.
Recommended Action. Provide another system.
0010
A CALL error was returned while invoking the DETAIL program.
Probable Cause. The Pathway on-error clause was triggered by the call to the DETAIL
program unit. The second number in the error message indicates the content of the
SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-2
VHS Browser Messages
0011
A CALL error was returned while invoking the HELP program.
Probable Cause. The Pathway on-error clause was triggered by the call to the HELP
program unit. The second number in the error message indicates the content of the
SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0012
A CALL error was returned while invoking the LOG program.
Probable Cause. The Pathway on-error clause was triggered by the call to the LOG
program unit. The second number in the error message indicates the content of the
SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0013
A CALL error was returned while invoking the PROMPT program.
Probable Cause. The Pathway on-error clause was triggered by the call to the
PROMPT program unit. The second number in the error message indicates the content
of the SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0014
A CALL error was returned while invoking the ENVIRONMENT
program.
Probable Cause. The Pathway on-error clause was triggered by the call to the
ENVIRONMENT program unit. The second number in the error message indicates the
content of the SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-3
VHS Browser Messages
0020
A CALL error was returned from the DETAIL program.
Probable Cause. The DETAIL program unit terminated abnormally. The Pathway onerror clause was triggered. The second number in the error message indicates the
content of the SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0021
A CALL error was returned from the HELP program.
Probable Cause. The HELP program unit terminated abnormally. The Pathway
on-error clause was triggered. The second number in the error message indicates the
content of the SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0022
A CALL error was returned from the LOG program.
Probable Cause. The LOG program unit terminated abnormally. The Pathway on-error
clause was triggered. The second number in the error message indicates the content
of the SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0023
A CALL error was returned from the PROMPT program.
Probable Cause. The PROMPT program unit terminated abnormally. The Pathway
on-error clause was triggered. The second number in the error message indicates the
content of the SCREEN COBOL TERMINATION-STATUS special register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0024
A CALL error was returned from the ENVIRONMENT program.
Probable Cause. The ENVIRONMENT program unit terminated abnormally. The
Pathway on-error clause was triggered. The second number in the error message
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-4
VHS Browser Messages
indicates the content of the SCREEN COBOL TERMINATION-STATUS special
register.
Recommended Action. See the Pathway/TS SCREEN COBOL Reference Manual for
an explanation of CALL errors.
0030(A)
Printing
Probable Cause. A print screen is currently being performed.
Recommended Action. None.
0031(A)
Screen printed.
Probable Cause. The print screen is done.
Recommended Action. None.
0032
You pressed an inactive function key. Choose another.
Probable Cause. The key pressed is not active on the current screen.
Recommended Action. Press F15 to help you choose another key.
0033
This is the last page.
Probable Cause. The page you are currently in is the last available page.
Recommended Action. None.
0034
There is no previous page.
Probable Cause. You are already at the first page.
Recommended Action. None.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-5
VHS Browser Messages
0035
Type correct destination name. Then press F9 to print.
Probable Cause. You typed an invalid spooler destination name before pressing the
F9 function key. A valid spooler destination name is an existing spooler collector name.
Recommended Action. Type the correct destination name and press F9 to print.
0050
You can't change criteria while you're doing this.
Probable Cause. You tried to change the criteria name while paging through a Log
Browser screen or while calling the PROMPT program within the log screen. The old
criteria will be restored and displayed.
Recommended Action. Try your action again if you want to.
0057
The log screen is empty. You can not page.
Probable Cause. You cannot page when the log screen is empty.
Recommended Action. None.
0060 (A)
Automatic screen update ...
Probable Cause. Indicates that the automatic screen update operation is currently
being performed.
Recommended Action. None.
0061
You can not change the environment name while you are doing
this.
Probable Cause. You cannot change the environment name while replying to a prompt
or calling the LOG program or the DETAIL program, or while you are paging through
the prompt file within the prompt screen. The old environment will be restored and
displayed.
Recommended Action. Try your action again if you want to.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-6
VHS Browser Messages
0062
There is no prompt on this screen. You can not do this.
Probable Cause. When the Prompt screen is empty you cannot reply to a prompt,
access the Prompt Detail screen, or page through the prompt file.
Recommended Action. None.
0063
Type correct page number. Then press F2 to update.
Probable Cause. You typed an invalid page number on the option line within prompt
screen before pressing the Update Screen function key (F2). A valid page number is
numeric and does not contain a decimal point and has to be between 1 and 750.
Recommended Action. Type the correct page number and press F2 to update.
0064
The screen is already thawed.
Probable Cause. You pressed the Thaw function key (SF8) while the screen was
already thawed. The SF8 function key is used when the screen is in a frozen state.
Recommended Action. None.
0065
Select prompts and press F11.
Probable Cause. The Detail function key (F11) was pressed, but no prompts were
selected.
Recommended Action. Select prompts by positioning the cursor or by entering a
character in column 1 prior to pressing F11.
0066
Select only one prompt to send your reply.
Probable Cause. The Send Reply function key (F6) was pressed, but you have
selected more than one prompt to reply to.
Recommended Action. Select only one prompt by entering a character in column 1
prior to pressing F6.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-7
VHS Browser Messages
0067
Select a prompt before sending your reply.
Probable Cause. The Send Reply function key (F6) was pressed, but you did not
select any prompt to reply to.
Recommended Action. Select only one prompt by entering a character in column 1
prior to pressing F6.
0080
The detail screen is empty. You can not reply to a prompt.
Probable Cause. The Send Reply function key (F6) was pressed, but the detail screen
is empty.
Recommended Action. None.
0085
Select an environment and press F11.
Probable Cause. The Detail Env function key (F11) was pressed, but you did not
select any environment.
Recommended Action. Select only one environment by typing any non-blank character
in the field preceding the environment name or position the cursor in that field and
press F11.
0086(A)
Screen Updated.
Probable Cause. The Environment Detailed screen indicates that the screen has been
updated with the latest values according to the current selected environment (F2).
Recommended Action. None.
0087(A)
Detailed environment information updated.
Probable Cause. The Environment Detailed screen indicates that the selected
environment detailed information has been correctly updated on the screen (F11).
Recommended Action. None.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-8
VHS Browser Messages
0088(A)
Current environment set.
Probable Cause. The Environment Detailed screen indicates that the selected
environment is now the current one and its detailed information has been correctly
updated on the screen (F12).
Recommended Action. None.
0100
An error occurred while closing a primary file.
Probable Cause. An error occurred while closing a primary file. The second number in
the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0101
An error occurred while inquiring about the primary file.
Probable Cause. An error occurred while inquiring about the primary file. The second
number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0102
An error occurred while positioning a primary file.
Probable Cause. An error occurred while positioning a primary file. The second
number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0103
The primary file does not exist.
Probable Cause. The primary file does not exist. The second number in the error
message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F-9
VHS Browser Messages
0104
An error occurred while opening a primary file.
Probable Cause. An error occurred while opening a primary file. The second number
in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0105
An error occurred when reading a primary file.
Probable Cause. An error occurred when reading a primary file. The second number in
the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0107
This prompt does not exist any more and the prompt file is
empty.
Probable Cause. The attempt to reply to the only prompt on the screen failed because
this prompt has already been moved from the prompt file which had only this one
prompt.
Recommended Action. None.
0108
An error occurred while closing the prompt file.
Probable Cause. An error occurred while closing the prompt file. The second number
in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0109
The prompt file is empty.
Probable Cause. The prompt file is empty. The second number in the error message
indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 10
VHS Browser Messages
0110
An error occurred at a key position in the prompt file.
Probable Cause. An error occurred at a key position in the prompt file. The second
number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0111
The previous prompt does not exist any more. The screen is
refreshed.
Probable Cause. The attempt to reply to a prompt on the screen failed because this
prompt has already been moved from the prompt file.
Recommended Action. None.
0112
An error occurred while opening the prompt file.
Probable Cause. An error occurred while opening the prompt file. The second number
in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0113
An error occurred while reading the prompt file.
Probable Cause. An error occurred while reading the prompt file. The second number
in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0114
Can not get the information requested.
Probable Cause. Cannot get the information requested. The second number in the
error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 11
VHS Browser Messages
0115
An error occurred while closing the VHS process.
Probable Cause. An error occurred while closing the VHS process. The second
number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0116
An error occurred while opening the VHS process.
Probable Cause. An error occurred while opening the VHS process. The second
number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0117
An error occurred while writereading the VHS process.
Probable Cause. An error occurred while doing a write-read on the VHS process. The
second number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0118
You entered an invalid environment name. Choose another.
Probable Cause. The attempt to modify the environment name failed because the
environment name chosen does not exist in this node.
Recommended Action. Go to the profile screen, if you are not already there, by
pressing the Profile function key (F14) and choose one from the existing environments.
0119
An invalid file date occurred.
Probable Cause. An invalid file date occurred. The second number in the error
message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 12
VHS Browser Messages
0120
A primary name error occurred.
Probable Cause. The primary name does not exist in this environment. The second
number in the error message indicates a file-system error.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
0121
Unable to get the Primary file information (Fileinquire).
Probable Cause. In some particular cases, the Procedure Call Fileinquire does not
return a valid error and VHS cannot display the Primary Log file information.
Recommended Action. None.
0130 (A)
VHS Profile updated.
Probable Cause. The changes on the VHS Browser Profile performed successfully.
Recommended Action. None.
0131
The value for the update must be between 1 and 480 (8 hours).
Probable Cause. The prompt screen automatic-update value you entered was not
between 1 and 480 (8 hours).
Recommended Action. Enter a value between 1 and 480.
0140
These are the last messages in this primary file.
Probable Cause. You pressed NEXT-PAGE within the log browser screen but you are
already on the last available messages.
Recommended Action. None.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 13
VHS Browser Messages
0141
There is no previous message in this primary file.
Probable Cause. You pressed PREV-PAGE within the log browser screen but you are
already on the first available messages.
Recommended Action. None.
0142
There is no record in this primary file matching these
criteria.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed criteria. But there are no records in this primary file matching these criteria.
Recommended Action. Change criteria and press the F2 function key again.
0143
You entered an invalid day. Choose another.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed day. But the entered day is invalid.
Recommended Action. Change the day and press the F2 function key again.
0144
You entered an invalid hour. Choose another.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed hour. But the entered hour is invalid.
Recommended Action. Change the hour and press the F2 function key again.
0145
The minutes you entered are invalid. Choose others.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed minutes. But the entered minutes are invalid.
Recommended Action. Change minutes and press the F2 function key again.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 14
VHS Browser Messages
0146
You entered an invalid month. Choose another.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed month. But the entered month is invalid.
Recommended Action. Change the month and press the F2 function key again.
0147
You entered an invalid process name. Choose another.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed process name. But the entered process name does not exist in this
environment.
Recommended Action. Change the process name and press the F2 function key
again.
0148
The seconds you entered are invalid. Choose others.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed seconds. But the entered seconds are invalid.
Recommended Action. Change seconds and press the F2 function key again.
0149
You entered an invalid timestamp. Choose another.
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed timestamp. But the entered timestamp is invalid.
Recommended Action. Change the timestamp and press the F2 function key again.
0150
You entered an invalid year. Choose another
Probable Cause. You pressed the Change Search Criteria function key (F2) after you
changed year. But the entered year is invalid.
Recommended Action. Change the year and press the F2 function key again.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 15
VHS Browser Messages
0160 (A)
Automatic screen update is performed.
Probable Cause. The update of the VHS Prompt screen performed successfully.
Recommended Action. None.
0161 (A)
Screen thawed and refreshed.
Probable Cause. The VHS Prompt screen was thawed and the values have been
refreshed.
Recommended Action. None.
0162 (A)
Screen updated.
Probable Cause. The current screen values have been updated.
Recommended Action. None.
0170 (A)
Reply was successful. Screen is refreshed.
Probable Cause. You pressed the Send Reply function key (F6) to send a reply to a
prompt. The reply was successful, and the screen values have been refreshed.
Recommended Action. None.
0171
Reply has been done successfully. The prompt file is empty.
Probable Cause. You pressed the Send Reply function key (F6) to send a reply to a
prompt. The reply was successful, but the prompt file is empty.
Recommended Action. None.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 16
VHS Browser Messages
0180
Unable to get the Prompt file opener process name.
Probable Cause. The VHS Browser server was unable to convert a VHS process
handle that is part of the current environment into a process name. The second
number in the error message indicates the NonStop Kernel file-system error.
Recommended Action. Verify the file-system error and correct the problem.
0181
Unable to get the Prompt file opener process handle.
Probable Cause. The VHS Browser server was unable to get a VHS process handle
that is part of the current environment. The second number in the error message
indicates the NonStop Kernel file-system error.
Recommended Action. Verify the file-system error and correct the problem.
0182
An error occurred while getting the number of outstanding
prompts.
Probable Cause. An error occurred while reading the Prompt file to get the number of
outstanding prompts. The second number in the error message indicates the NonStop
Kernel file system error.
Recommended Action. Verify the file-system error and correct the problem.
0183
The selected Environment was not found.
another.
Please select
Probable Cause. The selected environment does not exist anymore.
Recommended Action. Verify the VHSBCONF file to see if the selected environment is
included in the file.
1000
The request code is not known by the server.
Probable Cause. The VHS Browser server has received an unknown request.
Recommended Action. Repeat your request.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 17
VHS Browser Messages
1001
Request sent to the wrong server.
Probable Cause. The server identification is invalid.
Recommended Action. Repeat your request.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
F- 18
G
VHSCI Messages
This section lists VHSCI warnings and error messages. File-system messages are
described in the Guardian Procedure Errors and Messages Manual.
Message Descriptions
VHS 00100
Command not supported by VHS
Probable Cause. This command is not supported by the VHS subsystem.
Recommended Action. Use HELP VHS for a list of all supported commands.
VHS 00101
Too many opened VHS servers
Probable Cause. VHSCI cannot open any more VHS servers.
Recommended Action. Exit and re-enter VHSCI, or start another VHSCI session.
VHS 00102
Internal Error: Case value out of range
Probable Cause. There is a problem with internal data.
Recommended Action. Contact your service provider.
VHS 00103
Log destination cannot be added: the maximum is reached
Probable Cause. No more log destinations can be added.
Recommended Action. None.
VHS 00104
Not a current log destination
Probable Cause. The specified log destination is not a current log destination.
Recommended Action. Use the INFO with DETAIL command for a list of current log
destinations.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 1
Message Descriptions
VHSCI Messages
VHS 00105
Logtype of the primary log destination cannot be altered
Probable Cause. The logtype of the primary log destination is not alterable. It must
always be ALL.
Recommended Action. Alter the logtype of another log destination, or add a new log
destination with the logtype you need.
VHS 00106
Primary log destination cannot be deleted
Probable Cause. You cannot delete the primary log destination. It must always exist.
Recommended Action. None.
VHS 00107
Log destination does not exist
Probable Cause. The given log destination does not exist and cannot be accepted.
Recommended Action. Specify an existing log destination.
VHS 00108
File system error number
Probable Cause. A file-system error occurred.
Recommended Action. Use the ERROR program to get an explanation of the
file-system error.
VHS 00109
File-name already used by VHS as a log destination
Probable Cause. The specified file name is already used as a current log destination.
There is a special case for the primary log destination: if the alphabetic part of the file
name is the same, it is considered the same file name even if the numeric part is
different.
Recommended Action. Use the INFO command with DETAIL for a list of current log
destinations. Specify a file name different from the ones already used.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 2
Message Descriptions
VHSCI Messages
VHS 00110
File-name already used by VHS as a critical file name
Probable Cause. The specified file name is the same as a critical file name used by
VHS: the savefile name, the prompt file name, the alternate prompt file name or the
alternate primary log file name. There is a special case for the savefile name and the
alternate primary log file name: only the alphabetic part is compared, so the new file
may be considered the same as a VHS critical file name even if the numeric part is
different.
Recommended Action. Specify a file name different from the critical file names.
VHS 00111
Problem with the server: cannot obtain information
Probable Cause. The VHS server cannot provide the requested information at the
moment.
Recommended Action. If the problem persists, contact your service provider.
VHS 00112
Remote files for VHS are not allowed
Probable Cause. The specified file name or log name is remote for the VHS server, or
the node has not been specified.
Recommended Action. Specify a local file name or log name (in the same system as
the VHS server), or specify the complete format of the file name or log name including
the node, or use the command: “-> SYSTEM \node-where-VHS-server-runs” and
then use the local form of file names.
VHS 00113
Cannot continue to process response: index value out of range
Probable Cause. There was a problem with the context token value while processing
the response. The data (index value) was corrupted.
Recommended Action. Contact your service provider.
VHS 00114
SPI command buffer invalid or incomplete
Probable Cause. Information is missing from the command buffer or the buffer format
is not valid.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 3
Message Descriptions
VHSCI Messages
Recommended Action. Issue the command again and, if the problem persists, contact
your service provider.
VHS 00115
Version incompatibility between VHSCI and VHS server
Probable Cause. The VHSCI version is more recent than the VHS server version.
Recommended Action. Make sure that VHSCI has the same version as the VHS
server.
VHS 00116
Invalid SSID into SPI buffer
Probable Cause. The SSID token present in the SPI buffer is invalid.
Recommended Action. Issue the command again and if the problem persists, contact
your service provider.
VHS 00117
The specified CPU is not the current backup CPU or is invalid
Probable Cause. The specified CPU is not the current backup CPU of the VHS server,
or it is not a valid CPU number.
Recommended Action. Specify the current backup CPU of the VHS server.
VHS 00118
The specified VHS server is not a NonStop process: cannot
switch CPU
Probable Cause. The specified VHS server was not initiated as a process pair. You
cannot switch CPUs because there is no backup process.
Recommended Action. Do not use this command unless the VHS server is a process
pair.
VHS 00119
Parameter not supported
Probable Cause. The specified parameter is not supported by the VHS server.
Recommended Action. Use HELP for a list of all supported parameters.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 4
Message Descriptions
VHSCI Messages
VHS 00120
Unable to switch the primary log
Probable Cause. An error occurred during the execution of the switchlog command.
See the EMS event for more detail.
Recommended Action. Correct the error and redo the command.
VHS 00121
Unable to alter the EMS collector
Probable Cause. VHS was unable to alter the define =_EMS_collector. See the EMS
event for more detail.
Recommended Action. Correct the error and redo the command.
VHS 00122
The alternate collector name is invalid
Probable Cause. The specified alternate collector name is invalid.
Recommended Action. Enter the name of an existing alternate collector.
VHS 00123
The collector name is invalid
Probable Cause. The specified collector name is invalid.
Recommended Action. Correct the format of the collector name you entered.
VHS 00124
The inspect file name is invalid
Probable Cause. The specified inspect file name is invalid.
Recommended Action. Correct the Inspect file name you entered.
VHS 00125
Invalid primary security
Probable Cause. The specified primary security string is invalid.
Recommended Action. Correct the security string.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 5
Message Descriptions
VHSCI Messages
VHS 00126
Invalid evironment name.
Probable Cause. The specified environment name string is invalid.
Recommended Action. Correct the environment name string.
VHS 00127
parameter-name not modifiable when VHS-GUI-MODE is set to ON.
Probable Cause. This parameter is not modifiable when VHS-GUI-MODE is set to ON.
Recommended Action. None.
VHS 00200
Command not implemented
Probable Cause. The specified command is supported by the VHS server, but it is not
implemented yet.
Recommended Action. This is a warning. No action is necessary.
VHS 00201
No process currently open VHS server
Probable Cause. No process currently has VHS open.
Recommended Action. This is a warning. No action is necessary.
VHS 00202
The command is accepted but a FS error nnnn occurred on a
CLOSE
Probable Cause. The command is valid and was processed correctly, but a problem
occurred while trying to close the old file.
Recommended Action. Verify the current state of the old file, that is the file which is not
part of the VHS server configuration anymore.
VHS 00203
The given CPU number is already the primary CPU
Probable Cause. The specified CPU is already the primary CPU of the VHS server.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 6
Message Descriptions
VHSCI Messages
Recommended Action. Specify the backup CPU of the VHS server.
VHS 00204
Values identified by question marks (??) could not be
obtained
Probable Cause. Some values could not be obtained from the VHS server. Available
values are displayed; missing values are identified with question marks (for
example:??,?????).
Recommended Action. This is a warning. No action is necessary.
VHS 20001
Maximum number of nested OBEY files (n) exceeded
Probable Cause. Nesting is when an OBEY file invokes another OBEY file. This error
indicates that the maximum number of times this can be done has been exceeded.
This is usually caused by an OBEY file that invokes itself directly or through a chain of
OBEY commands.
Recommended Action. Find the OBEY command that caused the recursive loop.
VHS 20002
Can not obtain default volume and subvolume
Probable Cause. The call to the procedure VERIFYUSER has failed.
Recommended Action. Consult your system manager.
VHS 20003
This command is only valid in interactive mode
Probable Cause. The specified command can be used only while the input and output
of VHSCI is directed to your terminal.
Recommended Action. Remove the command from your OBEY file.
VHS 20004
No more than n numbers are allowed in this list
Probable Cause. Too many comma-separated values have been specified in a list of
numbers.
Recommended Action. Remove the extra values from the list.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 7
Message Descriptions
VHSCI Messages
VHS 20006
This command is only valid with a terminal for an infile
Probable Cause. The specified command will not function properly unless the VHSCI
input file is a terminal.
Recommended Action. Remove the command from the OBEY file or do not use the
command while communicating with VHSCI through a process.
VHS 20007
name value must be from lower-bound to upper-bound
Probable Cause. The specified value is out of range.
Recommended Action. Specify a value within range.
VHS 20025
Open of $RECEIVE failed
Probable Cause. An attempt to open the file name $RECEIVE was unsuccessful.
Recommended Action. Consult your system manager.
VHS 20029
INTERNAL ERROR:
reins^parser^ptrs out of bounds
Probable Cause. The global variable reins^parser^ptrs has been corrupted.
Recommended Action. Contact your service provider.
VHS 20032
INTERNAL ERROR:
Case value out of range
Probable Cause. An invalid case value was generated with no associated case label.
Recommended Action. Contact your service provider.
VHS 20034
Input string is too long
Probable Cause. Too much text on one command line.
Recommended Action. Put separate commands on separate command lines or issue
one command for each object name.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 8
Message Descriptions
VHSCI Messages
VHS 20035
Command line does not exist
Probable Cause. The command issued attempted to refer to a command that either no
longer exists or never existed in the history buffer.
Recommended Action. Correct the command to refer to a command in the history
buffer. The HISTORY command can be used to find existing commands.
VHS 20039
The specified help text is unavailable
Probable Cause. There is no help text available for the selected keyword combination.
Usually this occurs when the subsystem does not support the specified command,
object type, or command/object type combination.
Recommended Action. Type “HELP subsystem” to find out which commands and
object types a subsystem supports.
VHS 20040
READUPDATE of $RECEIVE failed
Probable Cause. A call to the procedure READUPDATE on the file $RECEIVE failed.
Recommended Action. Consult your system manager.
VHS 20047
NEWPROCESS error n on file-name
Probable Cause. An undocumented error was returned from the procedure
NEWPROCESS.
Recommended Action. Contact your service provider.
VHS 20049
CPU is unavailable
Probable Cause. The specified CPU is currently unavailable.
Recommended Action. Use the CPUS system-name command to determine which
CPUs are currently available for a given system.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G- 9
Message Descriptions
VHSCI Messages
VHS 20050
System is unavailable
Probable Cause. The specified system is currently unavailable.
Recommended Action. Use the CPUS DETAIL command to determine which systems
are currently available.
VHS 20051
Subsystem is not supported
Probable Cause. The subsystem of the specified object is not currently supported by
VHSCI.
Recommended Action. Consult your system manager or use another command
interpreter such as PUP or CMI.
VHS 20052
Creating file file-name
Probable Cause. A disk file has been created by VHSCI for you.
Recommended Action. No action is necessary.
VHS 20053
NEWPROCESS error 1: Process has undefined externals
Probable Cause. The program file refers to procedures that are not in the system
library and have not been bound in.
Recommended Action. If the program resides on $SYSTEM.SYSTEM or
$SYSTEM.SYSnn, then consult your system manager; otherwise, consult the author of
the program that has undefined externals.
VHS 20054
NEWPROCESS error 2: No process control block available
Probable Cause. Too many processes are running on the system right now.
Recommended Action. Consult your system manager.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-10
Message Descriptions
VHSCI Messages
VHS 20055
NEWPROCESS error 4: Unable to allocate map
Probable Cause. System resources are currently unavailable.
Recommended Action. Consult your system manager.
VHS 20056
NEWPROCESS error 6: File format error on file-name
Probable Cause. The program file is invalid.
Recommended Action. If the program resides on $SYSTEM.SYSTEM or
$SYSTEM.SYSnn, then consult your system manager; otherwise, consult the author of
the invalid program.
VHS 20057
NEWPROCESS error 7: Unlicensed privileged program
Probable Cause. The program must be licensed before it can be run.
Recommended Action. Consult your system manager.
VHS 20058
NEWPROCESS error 8: Process name error (file system error n)
Probable Cause. A file-system error occurred.
Recommended Action. Use the ERROR program for an explanation of the file-system
error.
VHS 20059
NEWPROCESS error 9: Library conflict
Probable Cause. The wrong library file was specified.
Recommended Action. Find the correct library file.
VHS 20060
NEWPROCESS error 10:
monitor process
Unable to communicate with system
Probable Cause. The system monitor process is currently unavailable.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-11
Message Descriptions
VHSCI Messages
Recommended Action. Usually no recovery is necessary. If further problems exist,
consult your system manager.
VHS 20061
NEWPROCESS error 12:
the same
Program file and library file cannot be
Probable Cause. The program and library files are identical.
Recommended Action. Reissue the command with the correct library name.
VHS 20062
NEWPROCESS error 13: Extended data segment initialization
error (file system error n)
Probable Cause. A file-system error occurred while attempting to allocate an extended
segment.
Recommended Action. Use the ERROR program for an explanation of the file-system
error.
VHS 20063
NEWPROCESS error 14:
system error n)
Extended segment swap file error (file
Probable Cause. A file-system error occurred while attempting to allocate an extended
segment.
Recommended Action. See the ERROR program for an explanation of the file-system
error.
VHS 20064
NEWPROCESS error 15:
error n)
Illegal home terminal (file system
Probable Cause. The home terminal specified in the RUN command was not a legal
terminal.
Recommended Action. Specify a valid terminal name.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-12
Message Descriptions
VHSCI Messages
VHS 20069
Invalid help command combination specified
Probable Cause. The combination of parameters to the HELP command are invalid.
Either the subsystem does not support the command or the object type is not
applicable to the command.
Recommended Action. Type the command HELP subsystem to determine valid
subsystem/command combinations or HELP subsystem command to determine the
valid subsystem/command/object-type combinations.
VHS 20080
VHSCI subsystem has no object type
Probable Cause. In help menu mode, the VHSCI subsystem was previously selected
and an object type entered.
Recommended Action. Select a subsystem other than VHSCI.
VHS 20081
INTERNAL ERROR:
key)
Cannot get word list from VHSTEXT file (key:
Probable Cause. An attempt to retrieve a word list from the VHSTEXT file failed.
Recommended Action. Contact your service provider.
VHS 20082
The device/process name may only be number characters long
Probable Cause. The device/process name entered was too long.
Recommended Action. Use the FC command to enter a device/process name shorter
than number characters in length.
VHS 20083
Wildcard characters ("*" and "?") are not allowed in this
object name
Probable Cause. You entered an object name where wildcard characters are not
allowed.
Recommended Action. Retype the command without wildcard characters in the object
name. The FC command can be used to accomplish this.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-13
Message Descriptions
VHSCI Messages
VHS 20084
Quoted string can be no more than number characters long
Probable Cause. This instance of a quoted string can contain only number characters.
Recommended Action. Retype the command with a shorter quoted string length. The
FC command can be used to accomplish this.
VHS 20085
item can be no more than number characters long
Probable Cause. The expected item is too long.
Recommended Action. Shorten the item to meet the required length limit.
VHS 20086
The maximum size of a param value is number characters
Probable Cause. The value portion of the PARAM command is too long.
Recommended Action. Reissue the PARAM command with a shorter param value
length.
VHS 20087
Internal Error:
Memory location zero overwritten
Probable Cause. The first G-relative memory location has been altered. This should
never happen under normal conditions. Usually, this is caused by an uninitialized
pointer.
Recommended Action. Contact your service provider.
VHS 20088
Either the STOP or TO option must be specified in each TRACE
command
Probable Cause. When starting a trace, the trace file must be specified using the TO
option. When stopping a trace, the STOP option must be specified.
Recommended Action. Contact your service provider.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-14
Message Descriptions
VHSCI Messages
VHS 20089
The REPEAT command may only appear once per command line
Probable Cause. The REPEAT command acts upon the entire remainder of the
command line, and therefore can only appear once in any command line.
Recommended Action. To obtain multiple levels of iteration, use REPEAT commands
within OBEY files.
VHS 20090
name value must be from lower-bound to upper-bound
Probable Cause. The specified value is out of range.
Recommended Action. Specify a value within range.
VHS 20091
This command is not allowed when a repeat command has been
issued
Probable Cause. A REPEAT command was specified prior to the execution of this
command.
Recommended Action. Do not specify the REPEAT command in conjunction with this
command.
VHS 20092
Repeat command stack overflow, command not available
Probable Cause. Too many repeat commands were specified on long command lines.
Recommended Action. Put commands to be repeated in an OBEY file and repeat the
execution of the OBEY file.
VHS 20093
Menu Mode HELP cannot be used in a REPEATed command
Probable Cause. The HELP command was entered without any help subject.
Recommended Action. Either leave the HELP command out of the repeated command
or issue the HELP command without first issuing the REPEAT command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-15
Message Descriptions
VHSCI Messages
VHS 20095
No aliases match the wildcard
Probable Cause. There are no aliases defined which match the wildcard entered.
Recommended Action. Use another wildcard or print all the aliases by not specifying
the alias name portion of the command.
VHS 20096
NEWPROCESS error 5: File error number on swap file file-name
Probable Cause. The swap file location is invalid. The file error number details the
cause of the error.
Recommended Action. Select a valid swap file location. Determine the appropriate
action from the file-system error number.
VHS 20097
Duplicate command modifier
Probable Cause. The modifier is a duplicate of one already specified on the command
line.
Recommended Action. Contact your service provider.
VHS 20100
Duplicate item in list
Probable Cause. Duplicates cannot be specified in this list.
Recommended Action. Remove the duplicate from the list.
VHS 20101
Timeout value must not be less than 1 second.
may fail.
Terminal I/O
Probable Cause. The timeout for all VHSCI output must not be less than one second
or all output from VHSCI could fail including error messages.
Recommended Action. Specify a larger timeout interval.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-16
Message Descriptions
VHSCI Messages
VHS 20103
Alias buffer is full.
No more aliases can be defined.
Probable Cause. Either the maximum number of aliases or the size of the alias text
buffer has been exceeded.
Recommended Action. Delete an alias before adding the next or do not add any more
aliases.
VHS 20104
A recursive alias has been detected
Probable Cause. An alias that refers to itself directly or by other aliases has been
invoked.
Recommended Action. Use the CLEAR ALIAS command to delete the alias that is
causing the recursive loop.
VHS 20105
Alias expansion has overflowed the input buffer
Probable Cause. Expanding the aliases contained on this line will produce more text
than will fit into the input buffer. This can be caused by a recursive alias.
Recommended Action. Delete the alias that caused the recursive loop or reduce the
amount of text generated by the aliases.
VHS 20106
DEFINEPOOL error n while defining alias pool
Probable Cause. A call to the procedure DEFINEPOOL failed.
Recommended Action. Contact your service provider.
VHS 20110
System name may not be specified in the ASSUME command
Probable Cause. Due to complications in object name expansion, a system name
cannot be specified in the ASSUME command.
Recommended Action. Use the SYSTEM command to change the default system.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-17
Message Descriptions
VHSCI Messages
VHS 20111
The size of the specified object names exceed the allocated
space
Probable Cause. Too many object names were specified in a single command.
Recommended Action. Split the object names into two commands.
VHS 20112
Maximum number of allowable errors exceeded
Probable Cause. This message informs the user that processing has been terminated
because the maximum number of errors set by the ALLOW command has been
exceeded.
Recommended Action. Either correct the conditions that are causing the errors or
increase the number of allowable errors with the ALLOW command.
VHS 20113
Maximum number of allowable warnings exceeded
Probable Cause. This message informs the user that processing has been terminated
because the maximum number of warnings set by the ALLOW command has been
exceeded.
Recommended Action. Either correct the conditions that are causing the warnings or
increase the number of allowable warnings with the ALLOW command.
VHS 20114
ASSIGN/PARAM message exceeds allocated space
Probable Cause. The ASSIGN/PARAM command or ASSIGN/PARAM message
cannot be processed because the allocated space was exceeded.
Recommended Action. Clear unneeded ASSIGNs/PARAMs by using the CLEAR
command.
VHS 20116
NEWPROCESS error 16:
I/O error on home terminal
Probable Cause. The home terminal was unavailable.
Recommended Action. If the home terminal was specified in the RUN command, then
specify a different home terminal; otherwise, consult your system manager.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-18
Message Descriptions
VHSCI Messages
VHS 20117
NEWPROCESS error 17:
DEFINE context error
Probable Cause. The specified DEFINEs could not be processed.
Recommended Action. Consult your system manager.
VHS 20118
NEWPROCESS error 18:
Process/device subtype is illegal
Probable Cause. A specified device was of the wrong type.
Recommended Action. See the documentation for the program you are trying to run to
determine which devices are valid.
VHS 20119
NEWPROCESS error 19: Process/device subtype is not the same
as its existing sibling
Probable Cause. There is a subtype mismatch.
Recommended Action. Consult your system manager.
VHS 20200
wildcard-name did not expand to any VHSCI supported object
names
Probable Cause. The specified wildcard name did not expand to any supported object
name(s).
Recommended Action. No recovery is necessary.
VHS 20201
Duplicate object name in list
Probable Cause. There are two object names in the object name list that are exactly
the same.
Recommended Action. Delete the duplicate object name from the list.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-19
Message Descriptions
VHSCI Messages
VHS 20202
INTERNAL ERROR:
Required Parameter missing on call to proc
Probable Cause. A required parameter was not included in a procedure call.
Recommended Action. Contact your service provider.
VHS 20203
INTERNAL ERROR:
Illegal value: n Call: proc Param: param
Probable Cause. An illegal value was supplied as a parameter to a procedure.
Recommended Action. Contact your service provider.
VHS 20204
Object name is too long
Probable Cause. The specified object name is too long.
Recommended Action. Reenter the object name.
VHS 20205
INTERNAL ERROR:
A call to PUTPOOL failed
Probable Cause. A call to the procedure PUTPOOL failed.
Recommended Action. Contact your service provider.
VHS 20207
Unknown file system error n on proc-call of file-name
Probable Cause. A file-system error out of the normal range for file-system errors
occurred.
Recommended Action. Report the circumstance in which the error occurred to your
service provider.
VHS 20208
All paths are down to system system-name
Probable Cause. The system is known to exist locally but at the present time it cannot
be communicated with. The system is either down or all Expand lines to that system
are down.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-20
Message Descriptions
VHSCI Messages
Recommended Action. Consult your system administrator.
VHS 20209
The unit n must be positive
Probable Cause. The specified unit must be a positive number.
Recommended Action. Use the FC command to change the number to a positive
value.
VHS 20210
Invalid terminal type for REVERSE and/or DIM option
Probable Cause. The SETPROMPT command with the REVERSE and/or DIM option
was specified for a terminal other than a 6530 or a 6520.
Recommended Action. Use the FC command to remove the REVERSE and/or DIM
option and re-issue the command.
VHS 20211
Invalid object type
Probable Cause. The specified object type is not supported.
Recommended Action. Reenter the command with a valid object type.
VHS 20212
The abbreviation is not unique; it expands to: text
Probable Cause. The specified abbreviation could be interpreted as more than one
key word. The matching key words follow the error message.
Recommended Action. Re-enter the command with a unique abbreviation.
VHS 20213
The subsystem product module has not been bound into VHSCI
Probable Cause. The code necessary to perform this subsystem’s tasks has not been
bound into the VHSCI object code.
Recommended Action. Consult your system manager.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-21
Interprocess Communication Messages
VHSCI Messages
VHS 20214
Exceeded max number of chars allowed on the RUN command line
Probable Cause. The number of characters following the name of a program file
exceeds the maximum number allowable.
Recommended Action. Do not type more than two lines of text on the RUN command
line.
VHS 20215
Expecting a blank
Probable Cause. A blank character was expected at this point in the command.
Recommended Action. Use the FC command to fix the command to include a blank.
VHS 20216
No fewer than n values are allowed in this list
Probable Cause. The list of values contained too few entries.
Recommended Action. Use the FC command to fix the command to have no fewer
than n entries.
VHS 20217
Expansion of abbreviation abbr has overflowed the input
buffer
Probable Cause. There was so much text on the command line that the expansion of
the abbreviation abbr caused the input buffer to overflow. This is usually caused by a
recursively defined alias or by too much text. The abbreviation expansion is not the
direct cause.
Recommended Action. Find and correct the recursive alias or shorten the command
line.
Interprocess Communication Messages
The following subsection lists interprocess communication warnings and errors you
might encounter when using VHSCI.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-22
Interprocess Communication Messages
VHSCI Messages
-00001
Already using resource
Probable Cause. The object of the command is already using the requested resource.
Recommended Action. This is a warning. No action is necessary.
-00002
Command was accepted and is being processed by obj-name
Probable Cause. A command was issued and received by the target subsystem. The
execution of the command is pending, or is in progress. This warning is issued by a
subsystem if the execution of a command is taking a long time to complete.
Recommended Action. This is a warning. No action is necessary.
-00003
Command not allowed while object in state state for obj-name
Probable Cause. The command is invalid in its current summary state. A command
was issued and the current summary state of the target object prevents processing of
the command. This error is returned whenever the state-transition specification is not
met.
Recommended Action. Make sure the target object is in a summary state compatible
with the command being issued.
-00004
Command/object type combination is not valid for this
subsystem
Probable Cause. A command was issued, but the object contained in the command
buffer is not a valid type for the command.
Recommended Action. For more information about the command and its associated
object types, refer to the subsystem-specific reference manual.
-00005
Command is not supported by this subsystem
Probable Cause. A command was issued that is unknown to the subsystem that owns
the object name.
Recommended Action. For more information about the commands supported by the
subsystem, refer to the subsystem-specific reference manual.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-23
Interprocess Communication Messages
VHSCI Messages
-00006
Command sequence invalid for obj-name
Probable Cause. The command sequence is invalid. A command was issued and
cannot be executed because of the current activity or state of the target object.
Recommended Action. This can be a warning or an error. For more information about
how that subsystem handles this warning or error condition, refer to the subsystemspecific reference manual.
-00008
Internal error:
SPI buffer larger than expected for obj-name
Probable Cause. A command was issued and the byte-count read by the file-system
procedure (for example, READUPDATE) is smaller than the used-length value in the
command buffer.
Recommended Action. Contact your service provider.
-00009
Invalid file name: file-name
Probable Cause. The command contained a syntactically invalid file-name.
Recommended Action. Correct the file name in error and reissue the request. See the
subsystem-specific reference manual for the file name format.
-00010
File system error: num, call: call, file: name
Probable Cause. A procedure call to the file-system failed during execution of a
request. For example, an OPEN was rejected by a process.
Recommended Action. Refer to the Guardian Procedure Errors and Messages Manual
for recovery procedures.
-00011
Invalid type of file: file-name for obj-name
Probable Cause. The file specified in the request has an invalid format.
Recommended Action. Determine the valid file type code for the target file and reissue
the command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-24
Interprocess Communication Messages
VHSCI Messages
-00012
Maximum Limit Exceeded: limit-number for obj-name
Probable Cause. A fixed limit or configuration limit was exceeded. This error is usually
used to report any overrun of a limit, including internal control blocks or tables.
Recommended Action. The recovery action depends on the limit exceeded. For
information about recovery from this error, see the subsystem-specific reference
manual.
-00013
number Modem Error: number signal loss
Probable Cause. A hardware problem occurred and the signal was lost.
Recommended Action. Recovery is hardware-specific; check the modem, port, and
other hardware.
-00014
Unable To Obtain Memory: text for obj-name
Probable Cause. Unable to obtain memory space.
Recommended Action. This error usually indicates a resource-availability problem
caused by a large amount of activity (assuming that the configuration is proper for the
operating environment and that the associated hardware is functioning normally).
Attempt to determine and correct the problem, or wait awhile before reissuing the
request.
-00015
Object name Already Defined
Probable Cause. An ADD request was attempted against a defined object.
Recommended Action. This is a warning. No action is necessary.
-00016
Object name is already in state state
Probable Cause. A request to change the summary state of an object was issued but
the object is already in that state.
Recommended Action. This is a warning. No action is necessary.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-25
Interprocess Communication Messages
VHSCI Messages
-00017
Object name Not Found
Probable Cause. The specified object name could not be found within the subsystem.
This usually means the object has not yet been added. This error situation includes the
case where a command refers explicitly to an object and no object of that type is
supported by the target subsystem.
Recommended Action. Add the device first, and then correct the object name or object
type.
-00018
Object type is not supported by this subsystem
Probable Cause. This object type is not supported. An invalid, unknown, or
unsupported object type was encountered.
Recommended Action. For information about the object types supported by that
subsystem, see the subsystem-specific reference manual.
-00019
Invalid object name: name
Probable Cause. An invalid object name template was found in the command buffer.
Recommended Action. Correct the object name syntax and reissue the request.
-00020
Path path is inaccessible for obj-name
Probable Cause. Unexpected loss of the link between objects.
Recommended Action. Recovery is subsystem-specific. For information about
recovery from this error condition, refer to the subsystem-specific reference manual.
-00022
Security violation for obj-name
Probable Cause. A sensitive command request was attempted by an unauthorized
user.
Recommended Action. If possible, acquire the proper security and reissue the request.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-26
Interprocess Communication Messages
VHSCI Messages
-00023
Internal Error:
SPI error num text on call (Tnm: num)
Probable Cause. A call to an SPI procedure resulted in an error.
Recommended Action. Contact your service provider.
-00024
Internal Error: Invalid subsystem ID:
Number: number Version: number
Owner: subsystem
Probable Cause. The subsystem ID specified (using a call to SSINIT) in the request is
invalid.
Recommended Action. Contact your service provider.
-00025
Object name has no subordinates
Probable Cause. A command using the SUB modifier was issued but no subordinate
objects were found. This error applies only when the SUB modifier contains the
SUB-ONLY value, or the value of a specific object type.
Recommended Action. This is a warning. No action is necessary.
-00026
Internal Error:
(tnm:num)
Invalid Token:
Token Code: HEX-num
Probable Cause. An invalid, unknown, or unsupported token code was encountered.
Recommended Action. Contact your service provider.
-00027
Internal Error:
(tnm:num)
Duplicate Token:
Token Code:
HEX-num
Probable Cause. A token that can be specified only once appears more than once in
the command request buffer.
Recommended Action. Contact your service provider.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-27
Interprocess Communication Messages
VHSCI Messages
-00028
Internal Error: Invalid Token Length:
(tnm:num, Len: num)
Token Code: HEX-num
Probable Cause. Token length is either too long or too short.
Recommended Action. Contact your service provider.
-00029
Internal Error:
(tnm:num)
Required token Missing:
Token Code: HEX-num
Probable Cause. A command was issued with a missing required token.
Recommended Action. Contact your service provider.
-00030
Internal Error:
for obj-name
Invalid Value: text (tnm:num, Offset: num)
Probable Cause. An illegal value was encountered in a supported token.
Recommended Action. Recovery action depends on the token in error and on the
value specified in that token. For information about recovery from this error, see the
subsystem-specific reference manual.
-00031
Required Value Missing for Attribute: text (tnm:num, Offset:
num)
Probable Cause. A required attribute value was omitted.
Recommended Action. Supply the required value and reissue the request.
-00032
Incompatible Version: num, Command required subsystem to be
num for obj-name
Probable Cause. A command request was issued in which the command version was
a higher level than the version of the target subsystem, and the command contained
tokens unknown to the subsystem. This error can also occur if the version of a field in a
structured token is at a higher level than the version of the target subsystem.
Recommended Action. Communication with the subsystem is not possible. Refer to
the SPI Programming Manual for information about recovery from version
incompatibility. The experienced user could do a VERSION command and determine
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-28
Interprocess Communication Messages
VHSCI Messages
what part of the original command can be modified so that the command can be issued
successfully.
-00033
Internal Error: Empty SPI response
Probable Cause. There was no more data to display in a response to a continuation
request from VHSCI to the subsystem.
Recommended Action. Contact your service provider.
-00034
Attribute attribute-name is required in conjunction with
attribute-name for object-name
Probable Cause. The attribute specified is required in conjunction with one of the
attributes for the named object.
Recommended Action. Add the specified attribute with an appropriate value and
reissue the command.
-00035
Attribute attribute-name may not be used with attribute-name
for object-name
Probable Cause. The attribute named conflicts with one or more of the other attributes
for the specified object.
Recommended Action. Reissue the command, deleting the named attribute.
-00036
Value of attribute attribute-name may not be used in
conjunction with attribute-name for object-name
Probable Cause. The particular value specified with the named attribute conflicts with
one of the other attribute values for the object.
Recommended Action. Specify a different value or delete the attribute, and reissue the
command.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-29
Interprocess Communication Messages
VHSCI Messages
-00037
Command power level too weak for the state of object
object-name
Probable Cause. The command power specified on the command was insufficient to
change the state of the object.
Recommended Action. Reissue the command with a higher command power level.
-00038
Command power level too weak for the condition of object
object-name
Probable Cause. The command power specified on the command was insufficient to
change the state of the object.
Recommended Action. Reissue the command with a higher command power level.
-00039
Command not supported by object-name
Probable Cause. The object mentioned does not support the command.
Recommended Action. See the subsystem documentation for a more complete
description of when this object can and cannot support this command.
-00040
Command in progress for object-name
Probable Cause. This command has already been issued against this object and the
object is processing the command.
Recommended Action. None.
-00986
Attribute is not alterable: attr
Probable Cause. An attempt was made to alter an attribute that is not alterable.
Recommended Action. Correct the problem and retry the request.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-30
Interprocess Communication Messages
VHSCI Messages
-00987
REQID found in SPI buffer sent by non-qualified requester
Probable Cause. A security error occurred. A requester must have a user ID of -1 to
send a REQID token to the message buffer.
Recommended Action. Obtain the proper authority, if possible, and retry the request.
-00993
No TLE was available for command timeout
Probable Cause. No TLE available for command timeout.
Recommended Action. Contact your system manager.
-00994
SIGNALTIMEOUT error; could not set command timeout
Probable Cause. The command timeout could not be set.
Recommended Action. Contact your service provider.
-00995
Internal Error:
token
invalid name specified in MANAGER or OBJNAME
Probable Cause. The subsystem manager process could not be accessed; invalid
server name specified in MANAGER or OBJNAME token.
Recommended Action. Contact your service provider.
-00998
Internal Error:
subsystem
Server version could not be obtained from
Probable Cause. The server version is not valid.
Recommended Action. Contact your service provider.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-31
VHSCI Messages
Interprocess Communication Messages
Virtual Hometerm Subsystem (VHS) Manual—429311-001
G-32
H
VHS DDL Files
VHS Primary Log File
Table H-1 shows the DDL record definition of the VHS primary log file.
Table H-1. VHS Primary Log File Record Definition (Primary File)
Field Name
Data Type
Description
timestamp
BINARY 64
Corresponds to the timestamp at which the
message was received.
pid
CHARACTER 8
PID of the process which wrote this message
to the VHS process.
process-name
CHARACTER 8
Name of the process that wrote this message
to the VHS process. If the process is not
named, this field contains CPU,PIN in text
format.
text-line
CHARACTER 652
Text message written to the VHS process. The
first part of the text contains the timestamp in
text format and the object name.
The primary key of the primary log file is composed of the following fields: timestamp,
PID. The alternate key is process-name.
Table H-2 shows the DDL record definition of the alternate key file of the VHS primary
log.
Table H-2. VHS Primary Log File Record Definition (Alternate Key File)
Field Name
Data Type
Description
key-identifier
CHARACTER 2
The key identifier is K1.
processname
CHARACTER 8
Name of the process which wrote this message to the
VHS process. If the process is not named, this field
contains CPU,PIN in text format.
timestamp
BINARY 64
Corresponds to the timestamp at which the message was
received.
pid
CHARACTER 8
PID of the process which wrote this message to the VHS
process.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
H- 1
Log File Format
VHS DDL Files
Log File Format
This subsection describes the formats of log messages. Log MessagesExample H-1
shows an example of a log file.
File and Spooler
All the messages logged into a file or into a spooler location have the following format:
YY-MM-DD HH:MM:SS Pr_Nm (CPU-num, PIN-num) Object_Name text
message
YY-MM-DD
is the year-month-day indicating when the message is logged.
HH-MM-SS
is the hour-minute-second indicating at what time the message is logged.
Pr_Nm
is the process name that opens the VHS process as a home terminal. This process
is omitted if there is no process name.
CPU-num, PIN-num
is the CPU number (from 0 to 16) and the process ID number.
Object_Name
is the file name of the process that opens the VHS process as a home terminal.
text message
is the descriptive part of the message. Lines of more than 132 characters are
truncated; such lines are indicated by ellipses in the following examples.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
H- 2
File and Spooler
VHS DDL Files
Example H-1. Log Messages
98-02-12 12:11:12 1,143 \IDC5.$SYSTEM.SYS00.FUP File Utility Program - T6553D40 (01APR97) System \IDC5
98-02-12 12:11:13 1,143 \IDC5.$SYSTEM.SYS00.FUP Copyright Tandem Computers
Incorporated 1981, 1983, 198598-02-12 12:11:14 1,143 \IDC5.$SYSTEM.SYS00.FUP Prompt: "-"
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP Prompt: "-" Reply: "help"
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP ALLOCATE ALLOW ALTER BUILDKEYRECORDS
9898-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP COPY CONFIGURE CREATE DEALLOCATE
DISPLAYB
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP DUP EXIT FC FILENAMES FILES
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP GIVE HELP HISTORY INFO LICENSE
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP LISTLOCKS LISTOPENS LOAD LOADALTFILE
OBEY
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP PURGE PURGEDATA RELOAD RELOCATE
REMAP
98-02-12 12:11:32 1,143 \IDC5.$SYSTEM.SYS00.FUP RENAME REPORTWIDTH RESET RESTART
REVOKE
98-02-12 12:11:33 1,143 \IDC5.$SYSTEM.SYS00.FUP SECURE SET SHOW STATUS SUBVOLS
98-02-12 12:11:33 1,143 \IDC5.$SYSTEM.SYS00.FUP SUSPEND SYSTEM VOLS VOLUME !
98-02-12 12:11:33 1,143 \IDC5.$SYSTEM.SYS00.FUP ? FILELIST FILENAME FILESET NEWS
Virtual Hometerm Subsystem (VHS) Manual—429311-001
H- 3
File and Spooler
VHS DDL Files
Virtual Hometerm Subsystem (VHS) Manual—429311-001
H- 4
I
ViewPoint Event Filter
--- NonStop VHS - T8975D43 - (07JUL96)
--- File Type:
EMF Source file
--- Source File Name:
VHSFILTS
--- Object File Produced:
VHSFILTO
--- Generation Time:
May 28, 1996 16:47:32
--- Language Compiler Required: Event Management Filter (EMF)
--- Compiler Version Required: C20
--- Compiler Command:
EMF/ IN vhsfilts / vhsfilto
--- Compiler Note:
You may have to change the two first lines
-to specify the location of the ZSPITACL and
-ZEMSTACL TACL definition files.
--- File Description: This file contains a filter which passes only
-- event messages generated by a specific subsystem. This filter is
-- compatible with ViewPoint and can be used to change the meaning of
-- events to be displayed.
----------------------------------------------------------------------[SINK [#LOAD $SYSTEM.ZSPIDEF.ZSPITACL]]
[SINK [#LOAD $SYSTEM.ZSPIDEF.ZEMSTACL]]
[#SET ZEMS^VAL^SSID [ZSPI^VAL^TANDEM].[ZSPI^SSN^ZEMS].0]
[#DEF zvhs^val^ssid STRUCT
BEGIN
SSID x VALUE TANDEM.138.C30;
END;
] == End DEF
FILTER VHS^DEFAULT^FILTER;
BEGIN SSID ( ZEMS^VAL^SSID )
IF ZSPI^TKN^SSID = SSID ( ZVHS^VAL^SSID ) THEN
BEGIN
--- Fails on suppress^display events which are not
-- action-completion.
-IF ZEMS^TKN^SUPPRESS^DISPLAY = [ZSPI^VAL^TRUE] THEN
BEGIN
IF TOKENPRESENT ( ZEMS^TKN^ACTION^NEEDED ) AND
ZEMS^TKN^ACTION^NEEDED = [ZSPI^VAL^FALSE] THEN PASS 3
ELSE
FAIL;
END;
Virtual Hometerm Subsystem (VHS) Manual—429311-001
I-1
ViewPoint Event Filter
---IF
---IF
-------IF
Passes action-attention and action-completion events
TOKENPRESENT ( ZEMS^TKN^ACTION^NEEDED ) THEN PASS 1;
Testing for <> false for critical events
ZEMS^TKN^EMPHASIS <> [ZSPI^VAL^FALSE] THEN PASS 2;
All text events from VHS processes
that match the list of key words in (MATCH ...)
will be passed as critical events, otherwise they
will be passed as informative events.
(zems^tkn^eventnumber = 6 ) AND
( (MATCH (zems^tkn^text, "*ABNORMAL*"))
(MATCH (zems^tkn^text, "*A B N O R M A L*"))
(MATCH (zems^tkn^text, "*CALL USER*"))
(MATCH (zems^tkn^text, "*LOCKED*"))
(MATCH (zems^tkn^text, "*ACTION*"))
(MATCH (zems^tkn^text, "*WARNING*"))
(MATCH (zems^tkn^text, "*PROBLEM*"))
(MATCH (zems^tkn^text, "*INFORM*"))
(MATCH (zems^tkn^text, "*NOT TERMINATED*"))
(MATCH (zems^tkn^text, "*NOT COMPLETE*"))
(MATCH (zems^tkn^text, "*NOT UPDATED*"))
(MATCH (zems^tkn^text, "*UNKNOWN*"))
(MATCH (zems^tkn^text, "*UNSUCCESS*"))
(MATCH (zems^tkn^text, "*OVERFLOW*"))
)
THEN
PASS 2
ELSE
IF (zems^tkn^eventnumber = 6 )
THEN
PASS;
OR
OR
OR
OR
OR
OR
OR
OR
OR
OR
OR
OR
OR
END
ELSE FAIL;
END;
Virtual Hometerm Subsystem (VHS) Manual—429311-001
I-2
Glossary
action event. An event that requires operator action to resolve. Each subsystem
determines which events are action events by including a unique EMS token in the
event message. See Event Management Service.
advice line. Line 23 (or 21 in some cases) of the VHS block-mode screens. It provides
information pertinent to your operation of VHS, such as error notices and advisory
messages (such as operation-complete messages).
alias. An alternative name for a command or a series of commands.
automated teller machine (ATM). A type of terminal used by banks for automated deposits
and withdrawals.
collector. An EMS process that accepts event messages from subsystems and logs them in
an event log. See Event Management Service. Compare distributor.
command. A demand for action by or for information from a subsystem, or the operation
demanded by an operator or application. A command is typically conveyed as an
interprocess message from an application to a subsystem.
configuration file. A file that contains only configuration data. The ViewPoint application
has configuration files for status and for events, and there may be several of each. An
operator selects the desired configuration file by entering its name in the appropriate
field in the Profile screen. When the operator exits from the Profile screen, the data in
the named file is the new configuration for all status and event screens that are
subsequently displayed.
consumer distributor. An EMS distributor process that returns selected event messages to
management applications upon request. See Event Management Service. Compare
forwarding distributor and printing distributor.
critical event. An event designated as critical to the operation of the system or network.
Each subsystem determines which set of events generated by that subsystem should
be designated as critical. The subsystem identifies whether an event is critical or
noncritical by setting the value of the emphasis token in the event message.
Data Definition Language (DDL). A language and compiler used to define SPI token
codes, token maps, and token types and to generate a DDL definition file and
language-specific definition files; the language-specific definition files can be included
in the source code for management applications or management interfaces that use
SPI. See Subsystem Programmatic Interface.
data-portion token. A token within the body of an SPI message, as opposed to within the
header. Data-portion tokens are placed in the buffer using SSPUT or SSPUTTKN.
Some data-portion tokens can occur multiple times in the buffer, and most can be
enclosed in lists. See Subsystem Programmatic Interface. Compare header token.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -1
DDL
Glossary
DDL. See Data Definition Language.
Debug. Compaq debugger. Allows you to use code and data breakpoints and to view
variables by data space locations and offsets. Replaced by Inspect. See Inspect.
Distributed Systems Management (DSM). A set of software applications, tools, and
services that facilitates management of systems and networks. DSM products include
the Subsystem Programmatic Interface (SPI), the Event Management Service (EMS),
the Distributed Name Service (DNS), the DSM Template Services, the Subsystem
Control Facility (SCF) for data communications subsystems, and a set of management
applications including ViewPoint, Distributed System Management Solutions (DSMS),
and the DSM/Problem Manager (DSM/PM). DSM also includes SPI interfaces to the
management processes for various Compaq subsystems in addition to various other
tools that assist in the development of management applications.
Distributed Systems Management Application (DSMA). A term used to describe a
management application. See management application.
Distributed Systems Management Solutions (DSMS). A Compaq application package
with two interfaces, NetStatus and NetCommand, and an underlying management
service layer, Distributed Systems Network Management (DSNM), that you use to
monitor and control systems and networks from a single terminal. DSMS is particularly
useful for managing subsystems and their objects.
distributor. An EMS process that distributes event messages from event logs to requesting
management applications, to a collector on another node, or to printers, devices, or
files. See Event Management Service. See also consumer distributor, forwarding
distributor, and printing distributor.
DSM. See Distributed Systems Management.
EMS. See Event Management Service.
EMS standard definitions. The set of declarations provided by the Event Management
Service (EMS) for use in event management regardless of the subsystem. Any
application that retrieves tokens from event messages needs the EMS standard
definitions. Names of EMS standard definitions start with ZEMS.
enumerated type. A 16-bit signed data type that has one of a specified list of values with
designated meanings. The enumerated type is one of the standard token data types
defined by SPI; but the list of acceptable values and what they mean varies depending
on the token number and is defined by the subsystem.
event. A significant change in some condition in the system or network. Events can be
operational errors, notifications of limits exceeded, requests for action needed, and
so on.
event collector. An EMS process that collects all operator event messages generated in a
given system and files them in a file called an event log.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -2
event configuration file
Glossary
event configuration file. A file that contains configuration information to control what
ViewPoint displays on an events screen. There can be any number of event
configuration files; operators specify on the Profile screen which file ViewPoint is to use
to display events at their terminals.
Event Detail screen. The ViewPoint screen on which selected event messages are
described in detail.
event log. A file or set of files maintained by the Event Management Service (EMS) to store
event messages generated by subsystems.
event management. The reporting and logging of important events that occur in a system
or network, the distribution and retrieval of information concerning those events, and
the actions taken by operations personnel or management applications in response to
the events.
Event Management Service (EMS). A software facility that provides event-message
collection, logging, and distribution facilities for the NonStop Kernel operating system.
It lets an operator or management application select conveniently from event-message
data and allows for flexible distribution of event messages within a system or network.
It has programmatic interfaces based on SPI for both event reporting and event
retrieval. See event message.
event message. The text intended for a system operator that describes a change in some
condition in the system or network, whether minor or serious. The change of condition
is termed an event. Events may be operational errors, notifications of limits exceeded,
requests for action needed, and so on. Each event message, when displayed on an
event screen, is displayed as one line of text.
Extras. A SCREEN COBOL program unit that a programmer can add to the ViewPoint
application, possibly as a means of invoking a larger set of program units that you
supply. The ViewPoint application calls the Extras program unit (which must have the
name EXTRAS) when the user presses the Extras function key.
File Utility Program (FUP). The Compaq interactive utility that lets you perform a variety of
operations on files.
filter. A file that contains a list of criteria against which incoming event messages can be
compared so as to pass a given message (if it meets all criteria) or not pass it (if it fails
one or more criteria).
filter object file. A file containing the compiled filter code that determines which events are
displayed on an events screen.
forwarding distributor. An Event Management Service (EMS) distributor process that
sends selected event messages to an EMS collector on another network node or, if the
node has multiple collectors, to an EMS collector on the same node. Compare
consumer distributor and printing distributor.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -3
FUP
Glossary
FUP. See File Utility Program.
header token. A special kind of token that provides information pertaining to the SPI or
EMS message as a whole. Header tokens differ from other tokens in several ways:
they exist in the buffer at initialization and their values are usually set by SSINIT or
EMSINIT; they can occur only once in a buffer; they are never enclosed in a list; they
cannot be moved to another buffer with SSMOVE. Programs retrieve the values of
header tokens by passing appropriate token codes to SSGET or EMSGET, and can
change the values of some header tokens by passing their token codes to SSPUT or to
EMSADDSUBJECT or EMSADDTOKENS.
information event. This is an event that is neither critical nor requires action, such as an
event that reports a change in the status of a process or device. Compare action event
and critical event.
Inspect. An interactive symbolic debugger for TAL, FORTRAN, COBOL, and Pathway
program development.
INSTALL. A software installation utility. It can install a new version of the software or interim
patches.
last event. A recent event that concerns a particular object. When requested, ViewPoint
displays on the Last Events screen a page of last-event messages whose subject is a
selected object.
Last Events screen. The screen on which ViewPoint displays all events with a particular
subject.
macro. A sequence of TACL commands and built-in functions that can contain dummy
arguments, thus providing a means for simple argument substitution. These arguments
are not checked for validity. When the macro name is given to TACL, TACL substitutes
the expansion of the command sequence for the name, replacing any dummy
arguments with parameter values supplied in the invocation. See Compaq Tandem
Advanced Command Language. Compare routine.
management application. A program or set of programs that issues commands to
subsystems, retrieves event messages, or does both things to assist in managing a
computer system or a network of systems. A management application is a requester
with respect to the subsystems to which it sends commands; the subsystems are
servers with respect to the management application. DSM provides a set of
management applications (including ViewPoint, DSM/PM, and DSMS); customers can
also write their own custom management applications.
management interface. A programmatic interface through which applications can manage
a subsystem and its objects. In some subsystems, one or more processes are
dedicated to the management interface; in other subsystems, the process that provides
the management interface also performs other functions.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -4
management process
Glossary
management process. The process through which an application issues commands to a
subsystem. A management process can be associated with more than one subsystem;
in this case, the management process is logically part of each of the subsystems. The
Subsystem Control Point (SCP) and PATHMON are examples of management
processes.
management service. A set of services that supports the programmatic interface between
the management applications in the operations environment and the subsystems and
objects in the subsystem environment. The services include the Event Management
Service (EMS), the Distributed Name Service (DNS), and the DSM Template Services.
Management services are always servers with respect to management applications
and subsystems. See management application.
message. A block of information, usually in the form of a structure, that is sent from one
process to another.
network control node (NCN). A node (one NonStop Himalaya system) which is used to
control other nodes. Since it is possible to have more than one such process in a
network, there can likewise be more than one NCN in a network of NonStop Himalaya
systems.
NonStop NET/MASTER. A menu-driven Compaq management service product that allows
you to monitor and manage a single NonStop Himalaya system or a heterogeneous
network from a single terminal.
operations activities. Activities, as defined by the Compaq operations management model,
that support managing a production system, solving production problems, and
monitoring and controlling performance. See production management and problem
management.
operations environment. An interface that enables both DSM management applications
and custom management applications to manage Compaq subsystems and customer
applications programmatically. See subsystem environment.
operations management model. A model for managing NonStop Himalaya systems that
divides operations management into two main functions: managing production and
managing change. DSM applications and tools provide support primarily for the two
main production activities: operations and support. See operations activities.
option line. Line 24 of the block-mode screens in the ViewPoint application. This line is
used by operators to enter information (an option) that is used by the next function key
that is pressed.
outstanding event. An action or critical event that has not yet been deleted by operator
action or by system action. The outstanding attribute is created by the ViewPoint
application for management of important events; it is not an inherent part of the event
message.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -5
outstanding prompt
Glossary
outstanding prompt. A prompt sent by an application to VHS that is waiting for a response.
The VHS prompt file contains all outstanding prompts.
owner. In the case of a disk file, the user or program that created the file, or a user or
program to whom the creator has given the file. In the case of a process, the user or
program that created the process or the user or program that owns the code file. In the
case of a token or other definition, the subsystem that provided the definition. In the
case of a subsystem, the company or organization that provides the subsystem, or the
eight-character string identifying that company.
Pathway. A Compaq subsystem for managing online transaction processing; it uses the
requester-server model with requesters consisting of a Compaq supplied terminal
control process (TCP) and user-written SCREEN COBOL program units, and servers
grouped into server classes to perform the requested processing. ViewPoint is a
Pathway application. See SCREEN COBOL.
point-of-sale (POS) terminal. A type of terminal used by retail stores for automated sales
transactions.
primary event. An event that is reported to a collector for display at all ViewPoint terminals
at a network control node. Primary events are displayed on the ViewPoint Primary
Events screen.
Primary Event Configuration screen. The one-page ViewPoint event configuration screen
requested from the Primary Events screen on which the operator can specify criteria to
control the display of events on the Primary Events screen for all operators.
primary-events distributor. An EMS consumer distributor that distributes event messages
to a ViewPoint event collection server for display on all terminals at a network control
node. See distributor.
Primary Events screen. The screen on which ViewPoint displays events configured for all
operators; these are events that pass the filter for primary events and the configuration
criteria specified on the Primary Events Configuration screen.
primary log file. A set of up to five files used to log all messages sent to VHS.
printing distributor. An Event Management Service (EMS) distributor process that sends
selected event messages to printers, devices, processes, or files. Compare consumer
distributor and forwarding distributor.
problem. Any occurrence that has a negative impact on system operations.
problem management. Activities that provide support for resolving problems in a
production environment. One of the operations activities in the operationsmanagement model. See operations management model.
production management. The set of regularly scheduled activities that keeps the
applications on a system or network of systems running smoothly. These activities
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -6
Profile screen
Glossary
include administering storage media such as disks and tapes, managing space in
CPUs and disks, and starting or stopping system components. One of the operations
activities in the operations-management model. See operations management model.
Profile screen. The ViewPoint screen on which the operator can specify the status
configuration and event configuration files to be used to control the display of status on
the Network Status Summary screen and of events on the Primary Events screen.
programmatic command. A command issued by a program, rather than by a human
operator.
programmatic interface. A means for a program to communicate with another program.
On a Compaq system, a programmatic interface typically includes the following: a
message format, a set of message formats, or a set of procedures (such as the SPI
procedures) to build and decode messages; definitions of message elements
(commands, data types, objects, parameters, response data, errors, and so on); rules
for communication between the requester and the server; and software to receive and
respond to messages defined for the interface.
programmed operator. A management application that performs functions that might
otherwise be performed by a human operator.
reply, reply message. One message from a server to a requester, in response to a request.
request, request message. One message from a requester to a server.
response. The information or confirmation supplied by a subsystem in response to a
command.
routine. A sequence of TACL commands and built-in functions that can perform complex
argument interpretation. Compare macro.
SCF. See Subsystem Control Facility.
SCP. See Subsystem Control Point.
SCREEN COBOL. A Compaq supplied language used to write program units that specify
the terminal interface for Pathway requesters. See Pathway.
session. The period during which two entities can exchange data. In the context of a
management application, the period during which an application can issue commands
to a subsystem. In the context of a command interpreter, the period during which a
user can issue commands to the command interpreter. In the context of the ViewPoint
application, the period between the user’s invoking ViewPoint and exiting.
status configuration file. A file that contains the configuration information controlling what
ViewPoint displays on the Network Status Summary screen. There can be any number
of status configuration files; operators specify on the Profile screen which file
ViewPoint uses to display status at their terminals.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -7
status item
Glossary
status item. A measurable condition in a system or network that is displayed on one line of
a Network Status Summary display screen. Each such item is separately chosen and
configured for display through the Status Item Configuration screen.
status server. A server that gathers data for the ViewPoint Network Status Summary
screen. Compaq provides a default status server; you can write and configure
additional status servers to augment or replace the functions of the default status
server. Typically, a status server issues programmatic commands to subsystems to find
out how many or how much of some resource is available—for example, how many
network nodes are available or how many terminals are running.
subject. In event management, a device, process, or other named entity about which a
given event message is concerned.
subsystem. A process or collection of processes that manages a cohesive set of objects.
Each subsystem has a process (in some cases, this process is the entire subsystem)
through which applications can request services by issuing commands defined by that
subsystem. See management process.
Subsystem Control Facility (SCF). An interactive interface for configuring, controlling, and
collecting information from Compaq data communications subsystems.
Subsystem Control Point (SCP). The management process through which management
applications, including SCF, manage Compaq data communications subsystems. See
management process.
subsystem definitions. The set of token definitions available for use with a particular
subsystem that supports an SPI programmatic interface.
subsystem environment. The Compaq subsystems and customer applications that use an
SPI management interface to communicate with management applications and with
the DSM management services. See operations environment.
subsystem ID (SSID). A data structure that uniquely identifies a subsystem (including
whether it is a Compaq subsystem or a subsystem you write). It consists of the
subsystem owner, the subsystem number, and the subsystem version number.
subsystem number. An integer that identifies a subsystem. Each subsystem has an owner,
generally the company that supplies the subsystem.
subsystem object name. A name by which an object is known to a subsystem; subsystemobject names are defined in a DNS database.
subsystem owner. A value identifying the company that supplies a particular subsystem. It
consists of a name of up to eight characters, blank-filled on the right. The owner for all
subsystems supplied by Compaq is COMPAQ.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -8
Glossary
Subsystem Programmatic Interface (SPI)
Subsystem Programmatic Interface (SPI). A set of procedures, associated definition files,
and conventions used to define message-based interfaces between management
applications and the subsystems they manage.
subsystem version number. A 16-bit integer representing the software release version of
a subsystem. The subsystem version number is a field of the subsystem ID.
SYSGEN. A program that is run against a CONFTEXT file (NonStop Kernel system
configuration) to generate a runable version of the NonStop Kernel operating system
that can be loaded into a processor. SYSGEN is usually invoked by INSTALL. See
INSTALL.
TACL. See Compaq Tandem Advanced Command Language.
Compaq Tandem Advanced Command Language (TACL). The Compaq product that is
both the standard NonStop Kernel command interpreter and a language consisting of
functions, macros, and routines that allows you to build your own commands.
token. A distinguishable unit in an SPI message. A token has two parts: an identifying code
(or token code) and a token value. For command and response messages, a token
normally represents a parameter to a command, an item of information in a response,
or control information for the subsystem. For event messages, a token normally
represents an item of information about an event or about the event message itself.
Transaction Monitoring Facility (TMF). The Compaq software product that provides
transaction protection, database consistency, and database recovery.
ViewPoint. An extensible interactive Compaq application for managing operations. It allows
a system or a network to be controlled from a single terminal. It includes several blockmode display screens for events, a block-mode display for system or network status, a
conversational TACL screen, and a facility called Define Process to maintain sessions
with multiple subsystems at the same time.
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -9
ViewPoint
Glossary
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Glossary -10
Index
A
Accessing VHS
as a stand-alone Pathway system 4-2
from a custom ViewPoint Extras
screen 4-2
from ViewPoint TACL prompt 4-2
ALIAS 7-4
ALLOW command 7-5
ALTER command 7-7
Application prompts 3-11
Applications, specifying VHS as home
terminal 3-7
Architecture 1-2
ASSIGN command 7-13
ASSIGNs 2-36
ASSUME command 7-16
Attributes 6-2
Automatic update delay 4-22
B
Backup CPU, switching to primary 5-23
Before using VHS 3-1
Benefits of VHS 1-1
Break key 5-5
Browser
accessing 4-1
exiting 4-3
C
Call errors 2-21
Changing the automatic update delay 4-22
CLEAR command 7-18
Commands
abbreviating 7-4
abbreviations 5-5
ALIAS 7-4
ALLOW 7-5
ALTER 7-7
ASSIGN 7-13
ASSUME 7-16
CLEAR 7-18
COMMENT 7-19
components 6-1
CONFIRM 7-19
CPUS 7-20
DELAY 7-22
DETAIL ERROR 7-23
displaying again 7-3
entering 5-4
ENV 7-23
exclamation point (!) 7-2
EXIT 7-24
FC 7-24
fixing 7-24
HELP 7-25
HISTORY 7-27
INFO 7-27
list and descriptions 7-1
LISTOPENS 7-32
LOG 7-34
multiple on a line 5-4
OBEY 7-34
on more than one line 5-4
OUT 7-36
PAGESIZE 7-36
PARAM 7-37
PAUSE 7-38
question mark (?) 7-3
REPEAT 7-38
repeating 7-2, 7-38
RUN 7-39
SETPROMPT 7-40
STATS 7-42
STATUS 7-44
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Index -1
D
Index
Commands (continued)
summary D-1
SYSTEM 7-49
VERSION 7-51
VOLUME 7-52
COMMENT command 7-19
Comments 5-5
Configuration
file, modifying 2-29
function keys 5-5
inspect processing 3-12
Configuration file A-1
CONFIRM command 7-19
CPUS command 7-20
CPU, switching 5-23
Custom configuration file 2-33, A-1
editing 5-8
D
Debug messages 3-11
DEFINEs 2-38
DELAY command 7-22
DETAIL ERROR command 7-23
Disk file names 6-4
Display messages 3-10
E
EMS events, centralizing 1-12
EMS standard definitions C-5
ENV command 7-23
Environment
getting information on 5-25
setting up 1-9
settings 7-23
switching 4-21
Environment Detailed screen 4-23
Equal signs (==) 7-19
Error messages
browser F-1
DETAIL ERROR command 7-23
process E-1
setting detail on 5-7
setting number to allow 7-5
Event filter I-1
Event messages C-1
Exclamation point (!) 7-2
EXIT command 7-24
Exit options
ALT-EVENT 4-4
LAST-EVENT 4-4
PRI-EVENT 4-4
PROFILE 4-4
STATUS 4-4
Exiting VHS
as a stand-alone Pathway system 4-4
from the ViewPoint Extras screen 4-3
Exiting VHSCI 5-3
Extras screen 2-21
F
FC command 7-24
Files
clearing ASSIGNs 7-18
custom configuration 2-33, A-1
help and error text location 2-36
inspect 3-12
installation 2-4, 2-25
log 7-34
names 6-4
primary log H-1
specification 6-5
using ASSIGNs 7-13
VHSBCONF A-3
VHSCSTM A-1
VHSSTART 3-3, A-2
Filter, ViewPoint 3-18, I-1
Function keys
configuring 5-5
setting 7-4
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Index -2
H
Index
H
HELP
online, command mode 5-9
online, menu mode 5-11
HELP command 7-25
Help key 5-5
Help screens 4-6
HISTORY command 7-27
Home terminal, specifying 3-7
I
INFO command 7-27
Inspect
file 3-12
messages 3-10
Installation
files 2-4, 2-25
parameters 2-8, 2-15, 2-23
restrictions 2-17
security considerations 2-29
Installing
VHS 2-2
VHS Browser as stand-alone Pathway
system 2-23
VHS Browser in ViewPoint/IOC 2-14
INSTVHS routine 2-4
Integers 6-2, 6-3
IOC, installing VHS Browser 2-14
K
modifying 5-17, 5-19
paging through 4-8
record definition H-1
M
Management applications 1-2
Merging VHS Browser with Extras
screen 2-19
Messages
debug 3-9
display 3-9
EMS event 1-12
inspect 3-9
open 3-9
reply 3-9
VHS management 3-9
VHSCI G-1
Modifying
log destinations 5-17, 5-19
VHS configuration files 2-29
Multiple commands on a line 5-4
O
OBEY command 7-34
Objects 6-1
Online help 4-6
OPEN messages 3-10
Openers, listing 5-16, 7-32
OUT command 7-36
Output, setting 5-8, 7-36
Keyword abbreviations 5-5
P
L
PAGESIZE command 7-36
Page, setting size 7-36
PARAM command 7-37
Parameters
inspect processing 3-12
list of 2-37
PATHCONF file 2-20
Limits B-1
Listing current openers 5-16
LISTOPENS command 7-32
Log Browser screen 4-8
LOG command 7-34
Log files
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Index -3
Q
Index
PATHDEFS file 2-20
PATHMONs, switching 4-21
PATHSTRT file 2-20
Pathway
configuration files 2-20, 2-29
examples 3-7
PAUSE command 7-38
Primary log file record definition H-1
Printing a screen 4-27
process H-1
Processes, multiple 1-7
Profile screen 4-18
Prompt Browser screen 4-13
Prompt Detail screen 4-16
Prompt, setting 7-40
Q
Question mark (?) 7-3
Quitting VHSCI 5-3
R
Record definition H-1
REPEAT command 7-38
Reply messages 3-11
Requirements,system 2-2
RUN command 7-39
Running VHS 3-4
Servers
switching 4-21
too many 2-20
SETPROMPT command 7-40
SPI standard definitions C-3
Starting VHS 3-1
Statistics 5-15, 7-42
STATS command 7-42
STATUS command 7-44
Status information 5-15
Stopping VHS 3-17
Strings 6-2, 6-3
Suspending a VHS process 7-22
Switching
backup CPU to primary CPU 5-23
environments 4-21
systems 4-21
VHS PATHMONs 4-21
VHS servers 4-21
Syntax, running VHS 3-4
SYSTEM command 7-49
Systems, switching 4-21
T
Time values 6-2, 6-4
TIMEOUT command 7-50
Tokens C-6
S
U
Screen
format 4-5
navigation 4-5
printing 4-27
Secondary log destination
adding 5-20
deleting 5-22
modifying 5-21
setting up 3-17
Security considerations 2-22
Updating VHS 2-5
V
VERSION command 7-51
VHS
accessing 4-2
architecture 1-2
ASSIGNs 2-36
assuming a process 7-16
before using 3-1
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Index -4
W
Index
VHS (continued)
benefits 1-1
Browser 1-5
components 1-3
conversational interface 1-3
DEFINEs 2-38
environments 1-9, 5-25
event messages C-1
help screens 4-6
installing 2-2
limits B-1
management applications 1-2
managing messages 3-9
modifying configuration files 2-29
multiple processes 1-7
network 1-10
node 1-8
parameters 2-37
process 1-3
Profile screen 4-18
run syntax 3-4
run-time options 2-36
screens 4-5
starting 3-1
startup file 2-30
stopping 3-17
suspending a process 7-22
system requirements 2-2
token definitions C-6
updating 2-5
with ViewPoint filter 3-18
VHS Browser
configuration file 2-33
Environment Detailed screen 4-23
error messages F-1
help screens 4-6
installing as stand-alone Pathway
system 2-23
installing in ViewPoint/IOC 2-14
Log Browser screen 4-8
Prompt Browser screen 4-13
Prompt Detail screens 4-16
screen navigation 4-5
VHS Profile screen 4-18
ZVHSDEFS 2-29
ZVHSSTRT 2-29
VHS BrowserZVHSCONF 2-29
VHSBCONF file 2-33, A-3
VHSCI
components 1-3
configuration file 5-8
entering commands 5-4
exiting 5-3
getting statistics 5-15
getting status information 5-15
listing current openers 5-16
run syntax 5-2
running 5-1
setting the output destination 5-8
VHSCSTM file 2-33, A-1
VHSDEFS file 2-20
VHSSTART file 2-30, A-2
VHSSTRT file 2-20
ViewPoint
event filter I-1
Extras screen 2-19
filter 3-18
installing VHS Browser 2-14
PATHCONF 2-20
PATHDEFS 2-20
PATHSTRT 2-20
VOLUME command 7-52
W
Warning messages, setting number to
allow 7-5
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Index -5
Z
Index
Z
ZPATHWAY file 2-29
ZVHSCONF file 2-29
ZVHSSTRT file 2-29
Virtual Hometerm Subsystem (VHS) Manual—429311-001
Index -6