Virtual Hometerm Subsystem (VHS) Manual Abstract This manual describes the HP NonStop™ Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications by emulating a 6530 terminal. Product Version H01 Supported Releases This publication supports D48.03 and all subsequent D-series RVUs, G06.15 and all subsequent G-series RVUs, and H06.
Document History Part Number Product Version Published 429311-001 NA February 2002 429311-002 H01 January 2006
Virtual Hometerm Subsystem (VHS) Manual Glossary Index What’s New in This Manual xiii Manual Information xiii New and Changed Information Examples Figures xiii About This Manual xv Audience xv Prerequisite Products and Manuals xv Related Products and Manuals xvi Organization of This Manual xvi Notation Conventions xvii Change Bar Notation xx 1.
2. Installing VHS (continued) Contents 2.
3. Using VHS (continued) Contents 3. Using VHS (continued) Application Prompt Processing 3-11 Reply Message Processing 3-11 Configuring VHS Inspect Processing 3-11 VHS AUTOMATIC-INSPECT-PROCESSING Parameter Inspect/eInspect Processing Considerations 3-12 VHS Inspect File 3-12 Understanding the VHS Log Files 3-17 PRIMARY-LOGFILE-PURGE Parameter 3-17 Secondary Log Destination 3-18 Stopping VHS 3-18 Using VHS With a ViewPoint Filter 3-19 3-11 4.
4. Using the VHS Browser (continued) Contents 4.
5. Using VHSCI (continued) Contents 5. Using VHSCI (continued) Getting Information About and Modifying Log Destinations 5-19 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.
7. Command Descriptions (continued) Contents 7. Command Descriptions (continued) HISTORY Command 7-27 INFO Command 7-28 LISTOPENS Command 7-33 LOG Command 7-34 OBEY Command 7-35 OUT Command 7-36 PAGESIZE Command 7-37 PARAM Command 7-38 PAUSE Command 7-39 REPEAT Command 7-39 RUN Command 7-40 SETPROMPT Command 7-41 STATS Command 7-43 STATUS Command 7-45 SYSTEM Command 7-50 TIMEOUT Command 7-51 VERSION Command 7-52 VOLUME Command 7-53 8.
A. VHS Files Contents A. VHS Files VHSCSTM File A-1 VHSSTART File A-2 VHSBCONF File A-3 B. VHS Limits C. VHSCI Command Summary D.
D. VHS Event Messages (continued) Contents D.
D. VHS Event Messages (continued) Contents D. VHS Event Messages (continued) 146: 147: 148: 150: 151: 152: 153: 154: 200: ZVHS-EVT-INSP-FILE-NOT-EXIST D-135 ZVHS-EVT-INSP-INVALID-TEXT D-137 ZVHS-EVT-CLEAN-TABLE D-140 ZVHS-EVT-INSPECT-EXTENDED D-142 ZVHS-EVT-INSPECT-APPL-EXT D-145 ZVHS-EVT-INSPECT-SCOBOL-EXT D-149 ZVHS-EVT-DEBUG-EXTENDED D-152 ZVHS-EVT-PROMPT-RESEND D-156 ZVHS-EVT-INTERNAL-ERROR D-162 E. VHS Process Messages F. VHS Browser Messages G.
Figures (continued) Contents Figures (continued) 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 8-1.
Tables (continued) Contents Tables (continued) 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 D-1. Table D-2. Table D-3. Table D-4. Table H-1. Table H-2.
Contents Virtual Hometerm Subsystem (VHS) Manual—429311-002 xii
What’s New in This Manual Manual Information Virtual Hometerm Subsystem (VHS) Manual Abstract This manual describes the HP NonStop™ Virtual Hometerm Subsystem (VHS). VHS acts as a virtual home terminal for applications by emulating a 6530 terminal. Product Version H01 Supported Releases This publication supports D48.03 and all subsequent D-series RVUs, G06.15 and all subsequent G-series RVUs, and H06.
What’s New in This Manual • • • • • • Changes to the G06.15 Manual Added information about the EPROCESS keyword under VHS Inspect File on page 3-12. Updated the syntax of the VHS Inspect file on page 3-13 with the new keywords, EPROCESS, EPROGRAMFILE, and ELANGUAGE. Added C++ as one of the options for language under {language } on page 3-14. Updated the example with new keywords under Example of a VHS Inspect File on page 3-15. Added a new subsection, {elanguage } on page 3-14.
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/eInspect 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. Note.
Related Products and Manuals About This Manual Related Products and Manuals You can use other HP products to manage system and user messages. VHS operates independently of these tools, but is designed to work with and enhance each of these tools.
Notation Conventions About This Manual Table i.
General Syntax Notation About This Manual { } 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.
Notation for Messages About This Manual 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 This 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.
Notation for Management Programming Interfaces About This Manual % 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.
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 doesnot require any change 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/eInspect or Debug prompts.
VHS Architecture Introduction to VHS • Information retrieval that highlights the cause of a problem, expediting its resolution. 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 and the Application Environment Introduction to VHS receives in its primary log file. VHS sends event messages to the EMS collector and optionally to a console facility for display messages only. VHS and the Application Environment Configure your applications to send home terminal messages to VHS.
VHS Browser 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.
Using Multiple VHS Processes 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 Using Multiple VHS Processes You can use multiple VHS processes to balance the load on your system.
VHS on a Node Introduction to VHS Figure 1-3. Multiple VHS Processes Environment: VHS $VHS1 VHS Log File $VHS2 VHS Inspect File $VHS3 VHS Prompt File VST013.vsd 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.
Setting Up VHS Environments Introduction to 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 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.
VHS on a Network Introduction to VHS 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. Use Pathway screens to move from one environment to an another. 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.
VHS on a Network Introduction to 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 be opened only by local processes. Figure 1-6 shows a complete VHS setup on a network. Figure 1-6.
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 can see all VHS EMS events, as shown in Figure 1-7. Figure 1-7.
2 Installing VHS This section includes: • • • • 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.
VHS System Requirements Installing VHS • • Modifying the VHS Configuration Files on page 2-28 VHS Run-Time Options on page 2-34 VHS System Requirements VHS requires the NonStop operating system, H06.04 or later RVU. To install the VHS Browser facility as a stand-alone Pathway application, you must have Pathway, H01 or later RVU. If you install the VHS Browser facility in ViewPoint, you must have the ViewPoint, H01 or later RVU.
Creating the VHS Installation Subvolume (ISV) Installing VHS Figure 2-1 shows the sequence of steps required to install the VHS components. Figure 2-1.
Creating the VHS Installation Subvolume (ISV) Installing VHS Table 2-1 lists the files that you should find in your installation subvolume: Table 2-1.
Installing the VHS Subsystem Components Installing VHS Installing the VHS Subsystem Components The INSTVHS routine automates the installation of the VHS components and subsequent updates.
Updating VHS Installing VHS • • 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.
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, run the INSTVHS routine and follow the directions as shown in Figure 2-2. Figure 2-2.
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.
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.
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/eInspectsavefile $SYSTEM. VHSDUMP.
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.
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.
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 facil
Installing the VHS Browser in ViewPoint Installing VHS The INSTVHS routine creates the VHS startup file with the name specified by the VHS-STARTUP-FILE parameter. When the above steps are completed successfully, the installation of the VHS and VHSCI programs and the VHS GUI Agent facility is complete. You can continue with the installation of the VHS Browser facility.
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.
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.
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.
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.
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-28. ViewPoint Installation Considerations The following subsections describe the additional considerations for installing the VHS Browser into your ViewPoint environment.
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.
ViewPoint Installation Considerations Installing VHS Call Errors When paging from screen to screen within the VHS Browser, you might encounter this event message: ZPWY-ERR-TCP-STACKOVERFLOW (3016) When this happens, one of the these 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.
Installing the VHS Browser as a Stand-Alone Pathway System 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.
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 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 $SYSTEM.
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 2) No. Name Value Default Description 9 VHS-BROWSERPRIORITY VHS-Browserpriority 150 Specifies the NonStop priority at which the VHS Browser server processes will run. Pathway default is PATHMON priority minus 10.
VHS Browser Restrictions Installing VHS 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.
VHS Browser Installation as a Stand-Alone Pathway System Procedure Installing VHS 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 3 to install the VHS Browser as a stand-alone Pathway system. The INSTVHS program prompts you through these steps: 1.
VHS Browser Installation as a Stand-Alone Pathway System Procedure Installing VHS 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.
Pathway Installation Considerations Installing VHS 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.
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. Example 2-1.
VHSSTART File Installing VHS Example 2-1. VHS Custom Startup File (page 2 of 3) ================================================================== == == 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.
VHSINSP File Installing VHS Example 2-1. VHS Custom Startup File (page 3 of 3) == 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.
VHSBCONF File Installing VHS 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 more information about VHSCI commands, see Section 7, Command Descriptions.
VHSBCONF File Installing VHS Example 2-2. VHS Browser Environment Configuration File (page 2 of 2) = == Modifications Summary: == Sept. 30, 1996 10:55:58 File Creation. == ============================================================================ == Default configuration for the VHS Browser Environment file ============================================================================ == <1 space or more> == VHS $SYSTEM.VHS.PROMPT ATM $PROD.VHSLOG.
VHSGCONF File Installing VHS VHSGCONF File VHSGCONF is the VHS GUI Agent configuration file. You need to modify the default file to: • • Use the VHS GUI facility Restrict VHS GUI user capabilities The VHSGCONF file must reside in the $SYSTEM.SYSTEM subvolume. For more information, see Appendix 8, The VHS GUI. VHS Run-Time Options The following subsections present some file-specific considerations that you should be aware of before using VHS.
VHS Parameters Installing VHS 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. The 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.
VHS Parameters Installing VHS Table 2-8. VHS Parameters (page 2 of 2) Parameter Name Default Description 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.
VHS DEFINE Parameter Installing VHS 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.
VHS DEFINE Parameter Installing VHS Virtual Hometerm Subsystem (VHS) Manual—429311-002 2- 38
3 Using VHS This section describes how to use VHS. It includes: • • • • • • • Before Using VHS Starting VHS Specifying VHS as the Home Terminal of Applications on page 3-5 How VHS Manages Messages on page 3-7 Configuring VHS Inspect Processing on page 3-11 Understanding the VHS Log Files on page 3-17 Using VHS With a ViewPoint Filter on page 3-19 Before Using VHS Before using the VHS, determine the applications that should use VHS as a home terminal. To use VHS with an application: 1. Start VHS. 2.
Sample VHSSTART File Using VHS • • • • 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. For more information, see ALTER Command, ENV Command, PARAM Command, and TIMEOUT Command in Section 7, Command Descriptions. Note.
Guidelines for Running VHS Using VHS 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, PARAM PARAM PARAM PARAM PARAM PARAM PARAM PARAM PARAM "VHS" $SYSTEM.VHSDMP1.SAVE0000 FALSE $SYSTEM.VHSDMP1.
VHS Run Syntax Using VHS 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 is: [ RUN ] VHS / name $process-name, nowait [, run-option ] / backup-cpu-number 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.
Specifying VHS as the Home Terminal of Applications Using VHS 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.
Pathway Application Example 2 Using VHS 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 this example, the Pathway startup file includes two commands to run with VHS. These commands are in boldface: OBEY $SYSTEM.
How VHS Manages Messages Using VHS 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.
OPEN Message Processing Using VHS This 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.
Display Message Processing Using VHS 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 (?).
eInspect Prompt Processing (H-series RVUs only) Using VHS • 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. eInspect Prompt Processing (H-series RVUs only) When VHS receives an eInspect message, it logs all display messages received from eInspect in its Primary log file.
Application Prompt Processing Using VHS 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 (?).
Inspect/eInspect Processing Considerations Using VHS Inspect/eInspect Processing Considerations Changing the value of the AUTOMATIC-INSPECT-PROCESSING parameter online can create unexpected situations as in this scenario: AUTOMATIC-INSPECT-PROCESSING Parameter value is ON. VHS has two Inspect/eInspect openers: • • Inspect/eInspect #1 has 1 application to handle. Inspect/eInspect #2 has 2 applications to handle: The value of the parameter is changed to OFF via the VHSCI.
VHS Inspect File Using VHS 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 } {EPROCESS $ process-name } {EPROGRAMFILE diskfile-name } {ELANGUAGE elanguage } $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.
VHS Inspect File Using VHS {language } language specifies one of these: C C++ COBOL FORTRAN PASCAL SCOBOL TAL {elanguage } elanguage specifies one of these H-series RVUs only: C C++ ASM CHILL FORTRAN JAVA MODULA-2 pTAL SCHEME Virtual Hometerm Subsystem (VHS) Manual—429311-002 3- 14
VHS Inspect File Using VHS 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.
VHS Inspect File Using VHS 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.
Understanding the VHS Log Files Using VHS has been stopped, creates a saveabend file, and stops the application. VHS then uses the new VHS Inspect file for all the new applications trapping into Inspect/eInspect. 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.
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.
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.
Using VHS Using VHS With a ViewPoint Filter Virtual Hometerm Subsystem (VHS) Manual—429311-002 3- 20
4 Using the VHS Browser This section describes how to use the VHS Browser and includes: • • • • • • • • • • • Accessing the VHS Browser Exiting the VHS Browser on page 4-3 VHS Screen Navigation on page 4-5 VHS Screen Format on page 4-5 Help Screens on page 4-7 Log Browser Screen on page 4-8 Prompt Browser Screen on page 4-12 Prompt Detail Screen on page 4-15 VHS Profile Screen on page 4-18 Environment Detailed Screen on page 4-22 Printing a Screen on page 4-25 This table summarizes the VHS screens: VHS
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.
High PIN Support Using the VHS Browser You can access the VHS Browser from the TACL prompt: • To access the VHS Log Browser screen, enter: 1> run vhsl or 1> vhsl • To access the VHS Prompt Browser screen, enter: 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.
VHS Installed in ViewPoint Using the VHS Browser Exiting VHS Browser From a Custom ViewPoint Extras Screen To exit VHS from a custom ViewPoint Extras screen: • • • 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.
VHS Installed as a Stand-Alone Pathway System Using the VHS Browser VHS Installed as a Stand-Alone Pathway System To return to the TACL prompt from 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 TACL prompt. VHS Screen Navigation From the VHS Log Browser screen or the VHS Prompt Browser screen, you can navigate to the other VHS Browser screens.
VHS Screen Format 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.
Help Screens Using the VHS Browser 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: • • 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.
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.
Paging Through the Log File Using the VHS Browser Figure 4-4. Log Browser Screen: SHOW-DATE and SHOW-OBJECT-NAME Set to 0 (page 2 of 2) 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 F10=Env Detail F14=VHS Profile F15=Help F9=Print SF16=Exit Figure 4-5.
Log Browser Screen Field Descriptions Using the VHS Browser Figure 4-6. Log Browser Screen: SHOW-DATE Set to 0 and SHOW-OBJECTNAME Set to 1 (page 2 of 2) DUP EXIT FC FILENAMES FILES 02-12 12:11:32 1,143 GIVE HELP HISTORY INFO LICENSE \IDC5.$SYSTEM.SYS00.FUP F2=Change Search Criteria F4=Prompt Browser F10=Env Detail F14=VHS Profile F15=Help F5=Refresh Count SF16=Exit F9=Print Log Browser Screen Field Descriptions Table 4-2 lists the field descriptions for the Log Browser screen. Table 4-2.
Log Browser Screen Function Keys Using the VHS Browser Table 4-2. Log Browser Screen Field Descriptions (page 2 of 2) Field/Line Name Description 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 Note.
Date and Object-Name Display Using the VHS Browser For example: Search Text: C??pa? C* This search text is replaced by *C??pa? C* VHS will find “HP Computers”.
Changing Search Criteria Using the VHS Browser 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.
Prompt Browser Screen Field Descriptions Using the VHS Browser 5. Press F6 to send the reply. 6. Press SF8 to resume the automatic refresh of the screen. Figure 4-7 shows a sample Prompt Browser screen. Figure 4-7. 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.
Prompt Browser Screen Function Keys Using the VHS Browser Table 4-4. Prompt Browser Screen Field Descriptions Field/Line Name Description 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.
Replying to a Prompt Using the VHS Browser Replying to a Prompt To reply to a prompt: 1. Go to the Reply field. 2. Enter the reply in the Reply field. 3. Press F6 to send the reply. Figure 4-8 and Figure 4-9 shows a sample of a Prompt Detail Screen with different SHOW-DATE params. Figure 4-8. 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.
Prompt Detail Screen Field Descriptions Using the VHS Browser Figure 4-9. Prompt Detail Screen: SHOW-DATE Set to1 (page 2 of 2) 02-13 11:35:26 1,116 Reply: F6=Send reply F9=Print Prompt: "-" F11=Next prompt F15=Help F16=Return Prompt Detail Screen Field Descriptions Table 4-6 describes the fields on the Prompt Detail screen. Table 4-6.
VHS Profile Screen Using the VHS Browser Table 4-7. Prompt Detail Screen Function Keys Key Function Description 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.
Switching Systems Using the VHS Browser Figure 4-11 shows the format of the VHS Profile screen for D21 and newer versions. Figure 4-11. 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.
Switching PATHMONs Using the VHS Browser • Press F14 to update the VHS Profile screen. Switching PATHMONs The Under Pathmon field displays the current PATHMON. To switch to another PATHMON: • • 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.
VHS Profile Screen Field Descriptions Using the VHS Browser VHS Profile Screen Field Descriptions Table 4-8 lists the field descriptions for the VHS Profile screen. Table 4-8.
Environment Detailed Screen Using the VHS Browser 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.
Setting the Current Environment Using the VHS Browser 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.
Environment Detailed Screen Function Keys Using the VHS Browser Table 4-10. Environment Detailed Screen Field Descriptions (page 2 of 2) Field Name Description 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.
Printing a Screen Using the VHS Browser Table 4-11.
Printing a Screen Using the VHS Browser Virtual Hometerm Subsystem (VHS) Manual—429311-002 4- 26
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.
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.
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.
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 VHSCI Commands Using VHSCI semicolons) on a continued line, VHSCI waits until it has received the entire command string before processing any of the commands.
Configuring Function Keys Using 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.
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.
Setting the Output Destination Using VHSCI VHS W00201 No process currently open VHS server Probable Cause 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 this at the prompt: -> detail error off Setting the Output Destination To specify the output destination for a VHSCI session, use the OUT command.
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. For more information, see Section 2, Installing VHS.
Using Online Help Using VHSCI Example -> help listopens The LISTOPENS command lists all processes which currently open the specified object or objects. LISTOPENS [ /OUT / ] [ ] [, ] /OUT / causes any VHSCI output generated for this command to be directed to the specified file. designates the objects whose openers are to be displayed. If is omitted, the openers of the assumed object are listed (see the VHSCI ASSUME command).
Using Online Help Using VHSCI To get help about command usage examples, type this: -> 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.
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.
Using Online Help Using VHSCI For command information, enter VHS at the HELP prompt.
Using Online Help Using VHSCI For 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 / ] [ ] [ , ] /OUT / causes any VHSCI output generated for this command to be directed to the specified file. designates the objects whose openers are to be displayed.
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. Here the #Inspect applies to both Inspect and eInspect openers.
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.
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.
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.
Getting Information About and Modifying Log Destinations Using VHSCI This 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.
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.
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.
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.
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.
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.........
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. This 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.
Using VHSCI Getting Information About a VHS Environment Virtual Hometerm Subsystem (VHS) Manual—429311-002 5- 26
6 Command Components This section contains a description of the basic syntactic components used with VHS. This section describes these components: • • • • Objects and Object Lists Attributes and Attribute Values on page 6-2 Strings, Integers, and Time Values on page 6-2 Disk File Names on page 6-4 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.
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 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.
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: { "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.
Time Variable Command Components Time Variable The variable time is used for attributes that require a specified time interval. The syntax of time is: [ [ 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.
File Specification Command Components qualified file 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: [ \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 Specification Command Components Virtual Hometerm Subsystem (VHS) Manual—429311-002 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 provides an overview of the VHSCI commands. A full description of each command follows. Table 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.
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.
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.
ALIAS 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.
ALLOW Command Command Descriptions 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. Commands that refer to multiple objects or that issue multiple commands are most commonly used in OBEY (command) files or IN files.
ALTER Command Command Descriptions • If ALL, NO, or count is specified, but ERRORS and WARNINGS are omitted, ERRORS is assumed. Examples -> ALLOW Execution of an OBEY (command) file terminates with the detection of the first error. Warnings are ignored. -> ALLOW 5 ERRORS Execution of an OBEY (command) file terminates if more than five errors are detected. Warnings are ignored. ALTER Command The ALTER command changes the attribute values of an existing object.
ALTER Command Command Descriptions GENERATE-DISPLAY-EVENT GENERATE-INSPECT-EVENT GENERATE-PROMPT-EVENT MAXEXTENTS OPEN-TABLE-THRESHOLD PRIMARY-SECURITY PROMPT-EVENT-RESEND-DELAY PURGE-SAVEFILE REMOVE-EXTRA-SPACES SUPPRESS-DISPLAY VHS-LOGGER on-off-value on-off-value on-off-value numeric-value numeric-value string-value numeric-value on-off-value on-off-value on-off-value on-off-value PRIMARY number specifies a CPU number.
ALTER Command Command Descriptions DEBUG receives only Debug and Inspect/eInspect messages processed by VHS. Note. The eInspect debugger is supported only on systems running H-series RVUs. DISPLAY receives only the applications processed by VHS. 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.
ALTER Command Command Descriptions ON | TRUE adds the text token to EMS event messages. OFF | FALSE does not add the text token to EMS event messages. AUTOMATIC-INSPECT-PROCESSING on-off-value specifies if VHS must process Inspect/eInspect 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 automatically processes Inspect/eInspect prompts.
ALTER Command Command Descriptions ON | TRUE indicates that VHS will generate an EMS event message for a display type message. 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.
ALTER Command Command Descriptions 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. 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”.
ALTER Command Command Descriptions 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 ] 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.
ASSIGN Command Command Descriptions 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.
ASSIGN Command Command Descriptions 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: 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.
ASSIGN Command Command Descriptions 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: 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.
ASSUME Command Command Descriptions • • 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.
CLEAR Command Command Descriptions Examples This 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, ASSUME command replaces the object-name part of the assumed object. The INFO command that follows displays information about the new assumed process.
COMMENT Command Command Descriptions 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.
CONFIRM Command Command Descriptions 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.
CPUS Command Command Descriptions / 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.
DELAY Command Command Descriptions 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. Examples -> CPUS displays summary information about all systems on the network.
DETAIL ERROR Command Command Descriptions 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. For more information, see Time Variable on page 6-4. Examples -> DELAY 5 suspends VHSCI process for 5 seconds. -> DELAY 11:22:31 suspends VHSCI process for 11 hours, 22 minutes, and 31 seconds.
ENV Command Command Descriptions 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.
FC Command Command Descriptions 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.
HELP Command Command Descriptions 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.
HISTORY Command Command Descriptions 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.
INFO Command Command Descriptions 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.
INFO Command Command Descriptions 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 this 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.
INFO Command Command Descriptions Output Format With DETAIL The display of the INFO command with the DETAIL option has this 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.
INFO Command Command Descriptions 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/eInspect, 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.
INFO Command Command Descriptions 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.
LISTOPENS Command Command Descriptions 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.
LOG Command Command Descriptions 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.
OBEY Command Command Descriptions 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.
OUT Command Command Descriptions 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.
PAGESIZE Command Command Descriptions ! 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. For more information, see LOG Command on page 7-34. Examples -> -> -> -> -> -> -> == Send the output of the INFO command to a disk file. OUT $OPS.TEMP.
PARAM Command Command Descriptions • 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.
PAUSE Command Command Descriptions • • 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.
RUN Command Command Descriptions 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, For more information, see ALIAS Command on page 7-4.
SETPROMPT Command Command Descriptions • 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.
SETPROMPT Command Command Descriptions NUMBER displays the command line number. OBJECT displays the assumed object-type and object-name. For more information, see ASSUME Command on page 7-17. 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.
STATS Command Command Descriptions 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.
STATS Command Command Descriptions Examples STATS PROCESS $vhsd STATS /OUT OutStats/ PROCESS $vhs1, RESET Output Format The display of the STATS command has this 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.
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. For more information, see ASSUME Command on page 7-17.
STATUS Command Command Descriptions • • 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.
STATUS Command Command Descriptions • • • • • • • • • • • • • • • • • 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. APID is the ancestor process ID (CPU number and process number) of the VHS process.
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 this 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...........
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 this 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...........
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 this 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....
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.
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.
VOLUME Command Command Descriptions • 21JUL96 is the product release date. Output Format With DETAIL The display of the VERSION command with the DETAIL option has this format: 12-> VERSION PROCESS $vhsd, DETAIL Detailed VERSION PROCESS \POLLUX.
VOLUME Command Command Descriptions Examples -> VOLUME $MKT -> VOLUME $MKT.
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 Architecture The VHS GUI VHS GUI Architecture This 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.
HP 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 systems. HP Server - Central Node Following are descriptions of the processes depicted for the HP Server - Central Node depicted in Figure 8-1 on page 8-2. 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.
VHS GUI Installation The VHS GUI EMS Forward This is the EMS forwarding distributor that forwards the VHS EMS events to the central node (For more information, see the filter example at the end of this section). VHS GUI Installation VHS GUI installation consists of these steps: STEP 1: Install VHS on the HP System To install VHS, see Section 2, Installing VHS.
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.
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.
Use of Alternate EMS Collectors The VHS GUI 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. 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.
Restricting VHS GUI User Capability The VHS GUI 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. Example 1: ADDUSER ADDUSER ADDUSER ADDUSER PROD.*, PROD.MGR, PROD.
Broadcasting The VHS GUI 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. 4.
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].
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
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.
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 File VHS Files Virtual Hometerm Subsystem (VHS) Manual—429311-002 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.
VHS Limits Virtual Hometerm Subsystem (VHS) Manual—429311-002 B- 2
C 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.
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.
D 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.
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 (1
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 This table lists VHS Browser internal e
SPI Standard Definitions VHS Event Messages Table D-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.
EMS Standard Definitions VHS Event Messages EMS Standard Definitions EMS standard definitions begin with ZEMS- and are listed in Table D-2. They are described under each event message. Table D-2.
VHS Definitions VHS Event Messages 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.
VHS Token Definitions VHS Event Messages VHS Token Definitions VHS token definitions begin with ZVHS- and are listed in Table D-3. They are described under each event message. Table D-3.
VHS Value Definitions VHS Event Messages VHS Value Definitions VHS value definitions begin with ZVHS- and are listed in Table D-4. They are described under each event message. Table D-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.
Unconditional and Conditional Tokens VHS Event Messages • • • • 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 and 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.
1: ZVHS-EVT-INSPECT-SAVE VHS Event Messages 1: ZVHS-EVT-INSPECT-SAVE VHS generates this critical message when it is prompted by Inspect/eInspect, a savefile has been created, and the program is stopped.
1: ZVHS-EVT-INSPECT-SAVE VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTINSPECT-SAVE (1). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
1: ZVHS-EVT-INSPECT-SAVE VHS Event Messages ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into Inspect/eInspect. 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/eInspect. 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.
2: ZVHS-EVT-INSPECT-NOSAVE VHS Event Messages 2: ZVHS-EVT-INSPECT-NOSAVE VHS generates this critical event message when Inspect/eInspect is unable to create a saveabend file as requested by VHS.
2: ZVHS-EVT-INSPECT-NOSAVE 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-EVTINSPECT-NO-SAVE (2). EMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-APPLICATION-NAME.
2: ZVHS-EVT-INSPECT-NOSAVE VHS Event Messages ZVHS-TKN-CRTPID is the process ID of the application trapped into Inspect/eInspect. ZVHS-TKN-PNAME is the process name of VHS. ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into Inspect/eInspect. 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.
3: ZVHS-EVT-INSPECT-OBEY VHS Event Messages Probable Cause An application entered Inspect/eInspect. Inspect/eInspect 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.
3: ZVHS-EVT-INSPECT-OBEY VHS Event Messages Event-Message Text timestamp pid environment-name: Process process-id-string entered Inspect/eInspect. The command "command-string" has been sent to Inspect/eInspect. 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.
3: ZVHS-EVT-INSPECT-OBEY 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 gone into Inspect/eInspect. ZVHS-TKN-PNAME is the process name of VHS. ZVHS-TKN-OBJECTFILE is the object file name of the application trapped into Inspect/eInspect. ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS.
4: ZVHS-EVT-INSPECT-SCOBOL VHS Event Messages Probable Cause An application entered Inspect/eInspect. Inspect/eInspect prompts the VHS process. The VHS process supplies a command line to Inspect/eInspect 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.
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.
4: ZVHS-EVT-INSPECT-SCOBOL 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 ENVIRONMENT-PARAM, 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.
5: ZVHS-EVT-DEBUG-ERROR VHS Event Messages 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.
5: ZVHS-EVT-DEBUG-ERROR VHS Event Messages Conditional Tokens ZVHS-TKN-JOBID ZVHS-TKN-SUBDEVICE 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.
5: ZVHS-EVT-DEBUG-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 ENVIRONMENT-PARAM, 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.
6: ZVHS-EVT-DISPLAY 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. 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. Recommended Action Correct the application problem. More information about the problem is available in the primary log file.
6: ZVHS-EVT-DISPLAY VHS Event Messages Conditional Tokens ZVHS-TKN-JOBID ZVHS-TKN-MESSAGE-STRING ZVHS-TKN-MESSAGE-STRING2 ZVHS-TKN-MESSAGE-STRING3 ZVHS-TKN-SUBDEVICE 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.
6: ZVHS-EVT-DISPLAY VHS Event Messages 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 ENVIRONMENT-PARAM, 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.
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/eInspect. 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.
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.
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 Z
7: ZVHS-EVT-PROMPT VHS Event Messages 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 ENVIRONMENT-PARAM, then the default value is VHS.
7: ZVHS-EVT-PROMPT VHS Event Messages 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.
7: ZVHS-EVT-PROMPT VHS Event Messages 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.
7: ZVHS-EVT-PROMPT VHS Event Messages ZVHS-TKN-PREV-TIMESTAMP-5 is the timestamp of the message text contained in token ZVHS-TKN-PREVIOUSMESSAGE-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.
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.
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-EVTREPLY (8). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-APPLICATION-NAME.
8: ZVHS-EVT-PROMPT-REPLY 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 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.
100: ZVHS-EVT-VHS-STARTED 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/eInspect. ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application trapped into Inspect. Probable Cause A user answered the application prompt.
100: ZVHS-EVT-VHS-STARTED VHS Event Messages 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-EVTVHS-STARTED (100).
101: ZVHS-EVT-BACKUP-CREATED VHS Event Messages 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.
101: ZVHS-EVT-BACKUP-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-EVTBACKUP-CREATED (101). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-PNAME.
102: ZVHS-EVT-PRIMARY-LOG-CREATED VHS Event Messages 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. 102: ZVHS-EVT-PRIMARY-LOG-CREATED VHS generates this informative event message when it has created a new primary log file.
102: ZVHS-EVT-PRIMARY-LOG-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-EVTPRIMARY-LOG-CREATED (102). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-PNAME.
103: ZVHS-EVT-PRIMARY-LOG-ROLLOVER VHS Event Messages 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.
103: ZVHS-EVT-PRIMARY-LOG-ROLLOVER VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-PNAME is the process name of VHS.
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.
104: ZVHS-EVT-CREATE-BACKUP-FAILED VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-PNAME is the process name of VHS.
105: ZVHS-EVT-BACKUP-STOPPED VHS Event Messages 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.
105: ZVHS-EVT-BACKUP-STOPPED 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-EVTBACKUP-STOPPED (105). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-PNAME.
106: ZVHS-EVT-BACKUP-DELETED VHS Event Messages ZVHS-TKN-VERSION is the version of VHS. Probable Cause The VHS backup process was stopped. The VHS primary process tries 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.
106: ZVHS-EVT-BACKUP-DELETED VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTBACKUP-DELETED (106). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
107: ZVHS-EVT-BACKUP-ABENDED VHS Event Messages Recommended Action Follow the recommended procedure for a CPU failure. 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.
107: ZVHS-EVT-BACKUP-ABENDED VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-PNAME is the process name of VHS.
108: ZVHS-EVT-TAKEOVER VHS Event Messages 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.
108: ZVHS-EVT-TAKEOVER 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 D-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.
109: ZVHS-EVT-CHECKPOINT-FAILED VHS Event Messages • • Deleted (CPU DOWN) Switched 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 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-EVTCHECKPOINT-FAILED (109). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-PNAME.
110: ZVHS-EVT-CHECKOPEN-FAILED VHS Event Messages 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.
110: ZVHS-EVT-CHECKOPEN-FAILED VHS Event Messages 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-EVTCHECKOPEN-FAILED (110).
110: ZVHS-EVT-CHECKOPEN-FAILED VHS Event Messages 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 tries to create a new backup after a 10 second delay. Recommended Action For errors 30 through 37, free up system resources.
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.
111: ZVHS-EVT-PRIMARY-LOG-IO-ERROR 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 D-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.
112: ZVHS-EVT-PROCESS-DELETED VHS Event Messages 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. 112: ZVHS-EVT-PROCESS-DELETED VHS generates this event when the CPU of an application is down.
112: ZVHS-EVT-PROCESS-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-EVTPROCESS-DELETED (112). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-APPLICATION-NAME.
112: ZVHS-EVT-PROCESS-DELETED VHS Event Messages 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.
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.
113: ZVHS-EVT-ALTERNATE-CREATED VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS.
114: ZVHS-EVT-PROMPT-IO-ERROR VHS Event Messages 114: ZVHS-EVT-PROMPT-IO-ERROR VHS generates this critical event message when it is unable to access the prompt file.
114: ZVHS-EVT-PROMPT-IO-ERROR VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS.
115: ZVHS-EVT-PROMPT-FILE-CREATED VHS Event Messages Recommended Action The recommended action depends on the file error. 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.
115: ZVHS-EVT-PROMPT-FILE-CREATED VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-PNAME is the process name of VHS.
116: ZVHS-EVT-PROMPT-ALT-CREATED VHS Event Messages 116: ZVHS-EVT-PROMPT-ALT-CREATED VHS generates this informative event message when it has created a new prompt alternate key file.
116: ZVHS-EVT-PROMPT-ALT-CREATED VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS.
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.
117: ZVHS-EVT-CLEAN-PROMPT-FILE VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTCLEAN-PROMPT-FILE (117). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-APPLICATION-NAME. 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 D-5.
117: ZVHS-EVT-CLEAN-PROMPT-FILE VHS Event Messages 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.
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.
118: ZVHS-EVT-REMOVE-PROMPT VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTREMOVE-PROMPT (118). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
118: ZVHS-EVT-REMOVE-PROMPT VHS Event Messages 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.
119: ZVHS-EVT-BAD-REPLY VHS Event Messages 119: ZVHS-EVT-BAD-REPLY VHS generates this action-completion event message when it cannot reply to the application because the application is unavailable.
119: ZVHS-EVT-BAD-REPLY VHS Event Messages 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 D-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 action-completion event message. ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS.
120: ZVHS-EVT-CONFIG-IO-ERROR VHS Event Messages 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. 120: ZVHS-EVT-CONFIG-IO-ERROR The VHS Browser generates this event message when an I/O error occurs on the configuration file.
120: ZVHS-EVT-CONFIG-IO-ERROR VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTCONFIG-IO-ERROR (120). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
121: ZVHS-EVT-INVALID-LINE-FORMAT VHS Event Messages 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.
121: ZVHS-EVT-INVALID-LINE-FORMAT VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZVHS-TKN-PNAME is the process name of the VHS Browser. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
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.
122: ZVHS-EVT-COLLECTOR ERROR VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS.
123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE VHS Event Messages 123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE VHS generates this critical message when, in the VHS Inspect file, a section is found using the LANGUAGE/ELANGUAGE keyword with an undefined language as the section name.
123: ZVHS-EVT-INSP-UNKNOWN-LANGUAGE 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 D-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 ENVIRONMENT-PARAM, then the default value is VHS.
124: ZVHS-EVT-INSP-INVALID-FILENAME VHS Event Messages Recommended Action Note. The eInspect debugger is supported only on systems running H-series RVUs. 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/eInspect.
124: ZVHS-EVT-INSP-INVALID-FILENAME VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTINSP-INVALID-FILENAME (124). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
125: ZVHS-EVT-INSP-INVALID-PROCESS VHS Event Messages 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/eInspect.
125: ZVHS-EVT-INSP-INVALID-PROCESS 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-EVTINSP-INVALID-PROCESS (125). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-PNAME.
126: ZVHS-EVT-INSP-DUPLICATE-SEC VHS Event Messages 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.
126: ZVHS-EVT-INSP-DUPLICATE-SEC VHS Event Messages 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.
126: ZVHS-EVT-INSP-DUPLICATE-SEC VHS Event Messages 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.
127: ZVHS-EVT-INSP-TABLE-FULL-DATA VHS Event Messages 127: ZVHS-EVT-INSP-TABLE-FULL-DATA Note. The eInspect debugger is supported only on systems running H-series RVUs. While loading the VHS Inspect file, VHS generates this critical message when the amount of data exceeds 5000 bytes.
127: ZVHS-EVT-INSP-TABLE-FULL-DATA VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS.
128: ZVHS-EVT-INSP-TABLE-FULL-SEC VHS Event Messages 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/eInspect. 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.
128: ZVHS-EVT-INSP-TABLE-FULL-SEC VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTINSP-TABLE-FULL-SEC (128). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
129: ZVHS-EVT-INSP-PROCESSING-STOP VHS Event Messages 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/eInspect. For more information, see Section 3, Using VHS. 129: ZVHS-EVT-INSP-PROCESSING-STOP VHS generates this critical message when it stops processing Inspect/eInspect prompts for an application.
129: ZVHS-EVT-INSP-PROCESSING-STOP VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE.
130: ZVHS-EVT-INSP-TOO-MUCH-PROMPT VHS Event Messages 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/eInspect process.
130: ZVHS-EVT-INSP-TOO-MUCH-PROMPT 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 D-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 ENVIRONMENT-PARAM, then the default value is VHS.
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).
131: ZVHS-EVT-OPEN-TABLE-THRESHOLD VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
132: ZVHS-EVT-INSP-INVALID-PARAM VHS Event Messages 132: ZVHS-EVT-INSP-INVALID-PARAM VHS generates this critical message when an invalid parameter in found in the VHS Inspect file.
132: ZVHS-EVT-INSP-INVALID-PARAM 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 D-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 ENVIRONMENT-PARAM, then the default value is VHS.
133: ZVHS-EVT-INSP-LOAD-FILE-ERR VHS Event Messages 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/eInspect. For more information, see Section 3, Using VHS. 133: ZVHS-EVT-INSP-LOAD-FILE-ERR VHS generates this informative message when it is unable to reload the VHS Inspect file.
133: ZVHS-EVT-INSP-LOAD-FILE-ERR VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS.
134: ZVHS-EVT-OPENEDIT-ERROR VHS Event Messages 134: ZVHS-EVT-OPENEDIT-ERROR VHS generates this informative message when an error occurs on the EDITOPEN of the VHS Inspect file.
134: ZVHS-EVT-OPENEDIT-ERROR VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
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.
135: ZVHS-EVT-READEDIT-ERROR VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
136: ZVHS-EVT-SET-DEFINE VHS Event Messages 136: ZVHS-EVT-SET-DEFINE VHS generates this critical message when it is unable to alter the value of the Define =_EMS-COLLECTOR.
136: ZVHS-EVT-SET-DEFINE VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
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.
137: ZVHS-EVT-INSP-RELOAD-FILE VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
138: ZVHS-EVT-PROMPT-CANCEL VHS Event Messages 138: ZVHS-EVT-PROMPT-CANCEL VHS generates this action-completion message when a prompt is canceled by its application.
138: ZVHS-EVT-PROMPT-CANCEL VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTPROMPT-CANCEL (138). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
138: ZVHS-EVT-PROMPT-CANCEL VHS Event Messages 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.
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.
139: ZVHS-EVT-PROMPT-NOT-UNIQUE VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTPROMPT-NOT-UNIQUE(139). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5.
139: ZVHS-EVT-PROMPT-NOT-UNIQUE VHS Event Messages 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.
140: ZVHS-EVT-INSP-INVALID-KEYWORD VHS Event Messages 140: ZVHS-EVT-INSP-INVALID-KEYWORD VHS generates this critical message when an invalid keyword is found in the VHS Inspect file.
140: ZVHS-EVT-INSP-INVALID-KEYWORD 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 D-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 ENVIRONMENT-PARAM, then the default value is VHS.
141: ZVHS-EVT-INSP-LINE-TOO-LONG VHS Event Messages 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/eInspect. For more information, see Section 3, Using VHS. 141: ZVHS-EVT-INSP-LINE-TOO-LONG VHS generates this critical message when a line in the VHS Inspect file exceeds 132 characters.
141: ZVHS-EVT-INSP-LINE-TOO-LONG VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS.
143: ZVHS-EVT-INSP-LOAD-FILE VHS Event Messages 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/eInspect. For more information, see Section 3, Using VHS. 143: ZVHS-EVT-INSP-LOAD-FILE VHS generates this informative message when the VHS Inspect file is loaded at startup time.
143: ZVHS-EVT-INSP-LOAD-FILE VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS.
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.
144: ZVHS-EVT-INSP-RELOAD-FILE-ERR VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
145: ZVHS-EVT-INSP-INVALID-REMOTE VHS Event Messages 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.
145: ZVHS-EVT-INSP-INVALID-REMOTE 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 D-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 ENVIRONMENT-PARAM, then the default value is VHS.
146: ZVHS-EVT-INSP-FILE-NOT-EXIST VHS Event Messages 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/eInspect. For more information, see Section 3, Using VHS. 146: ZVHS-EVT-INSP-FILE-NOT-EXIST VHS generates this critical message when, in the VHS Inspect file, a section name for the PROGRAMFILE/EPROGRAMFILE keyword is a file that does not exist.
146: ZVHS-EVT-INSP-FILE-NOT-EXIST VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-ENVIRONMENT-NAME is the name of the environment of this VHS.
147: ZVHS-EVT-INSP-INVALID-TEXT VHS Event Messages Probable Cause In the VHS Inspect file, a section name for the PROGRAMFILE/EPROGRAMFILE 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/eInspect. For more information, see Section 3, Using VHS.
147: ZVHS-EVT-INSP-INVALID-TEXT 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-EVTINSP-INVALID-TEXT (147). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-PNAME.
147: ZVHS-EVT-INSP-INVALID-TEXT VHS Event Messages 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.
148: ZVHS-EVT-CLEAN-TABLE VHS Event Messages 148: ZVHS-EVT-CLEAN-TABLE VHS generates this event when an application stops communicating with VHS.
148: ZVHS-EVT-CLEAN-TABLE VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-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 D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-FALSE. ZVHS-TKN-PNAME is the process name of VHS.
150: ZVHS-EVT-INSPECT-EXTENDED VHS Event Messages 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.
150: ZVHS-EVT-INSPECT-EXTENDED VHS Event Messages 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 Z
150: ZVHS-EVT-INSPECT-EXTENDED VHS Event Messages ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-APPLICATION-NAME. (ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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/eInspect.
151: ZVHS-EVT-INSPECT-APPL-EXT VHS Event Messages ZVHS-TKN-SEND-RECEIVE-MSG indicates if the message contained in token ZVHS-TKN-MESSAGE-STRING was received from Inspect/eInspect or sent to Inspect/eInspect. If it is ZVHS-VALINSPECT-RECEIVE (0) the message was received from Inspect/eInspect. If it is ZVHS-INSPECT-SEND (1) the message was sent by VHS to Inspect/eInspect. ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect/eInspect.
151: ZVHS-EVT-INSPECT-APPL-EXT VHS Event Messages application is trapped into Inspect/eInspect. The application is not a SCobol program. This event is generated only when the VHS-GUI-MODE parameter is set to ON.
151: ZVHS-EVT-INSPECT-APPL-EXT VHS Event Messages ZEMS-TKN-EVENTNUMBER is the event message number. The value for this event message is ZVHS-EVTINSPECT-APPL-EXT (151). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-APPLICATION-NAME. (ZEMS-TKN-) CPU, PROC-DESC, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-5. ZEMS-TKN-SUPPRESS-DISPLAY is set to ZSPI-VAL-TRUE.
151: ZVHS-EVT-INSPECT-APPL-EXT VHS Event Messages ZVHS-TKN-PRIMARY-LOG is the primary log name of VHS. ZVHS-TKN-SEND-RECEIVE-MSG indicates if the message contained in token ZVHS-TKN-MESSAGE-STRING was received from Inspect/eInspect or sent to Inspect/eInspect. If it is ZVHS-VALINSPECT-RECEIVE (0) the message was received from Inspect/eInspect. If it is ZVHS-INSPECT-SEND (1) the message was sent by VHS to Inspect/eInspect. ZVHS-TKN-USER-ID is the user ID of the application trapped into Inspect/eInspect.
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.
152: ZVHS-EVT-INSPECT-SCOBOL-EXT 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-EVTINSPECT-SCOBOL-EXT (152). ZEMS-TKN-SUBJECT-MARK is the standard EMS token that immediately precedes the subject token ZVHSTKN-TERMNAME.
152: ZVHS-EVT-INSPECT-SCOBOL-EXT VHS Event Messages 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.
153: ZVHS-EVT-DEBUG-EXTENDED VHS Event Messages Probable Cause An application entered Inspect/eInspect. VHS received a message from Inspect/eInspect or sent a message to Inspect/eInspect and knows which application is trapped into Inspect/eInspect. The application is an SCobol program. The text received from or sent to Inspect/eInspect is the text of this message. This event message is generated only when the VHS-GUI-MODE parameter is set to ON.
153: ZVHS-EVT-DEBUG-EXTENDED VHS Event Messages Conditional Tokens ZVHS-TKN-JOBID ZEMS-TKN-SUBDEVICE 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.
153: ZVHS-EVT-DEBUG-EXTENDED 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 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.
153: ZVHS-EVT-DEBUG-EXTENDED VHS Event Messages Conditional Tokens ZVHS-TKN-JOBID is the job ID used at starting time for the application trapped into Inspect/eInspect. ZVHS-TKN-SUBDEVICE is the subdevice used at starting time for the application trapped into Inspect/eInspect. 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.
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.
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-TI
154: ZVHS-EVT-PROMPT-RESEND VHS Event Messages 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 ENVIRONMENT-PARAM, then the default value is VHS.
154: ZVHS-EVT-PROMPT-RESEND VHS Event Messages 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.
154: ZVHS-EVT-PROMPT-RESEND VHS Event Messages 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 received by the same application. This token contains the message text received after the one contained in token ZVHS-TKN-PREVIOUS-MESSAGE-2.
154: ZVHS-EVT-PROMPT-RESEND VHS Event Messages ZVHS-TKN-PREV-TIMESTAMP-5 is the timestamp of the message text contained in token ZVHS-TKN-PREVIOUSMESSAGE-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).
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.
200: ZVHS-EVT-INTERNAL-ERROR VHS Event Messages (ZEMS-TKN-) CPU, CRTPID, GENTIME, LOGTIME, PIN, SYSTEM, USERID and TEXT are described under EMS Standard Definitions on page D-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 ENVIRONMENT-PARAM, then the default value is VHS. ZVHS-TKN-PNAME is the process name of VHS.
200: ZVHS-EVT-INTERNAL-ERROR VHS Event Messages 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.
200: ZVHS-EVT-INTERNAL-ERROR VHS Event Messages Recommended Action Recovery.
VHS Event Messages 200: ZVHS-EVT-INTERNAL-ERROR Virtual Hometerm Subsystem (VHS) Manual—429311-002 D-166
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.
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 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 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).
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.
VHS Browser Messages Recovery. See the Pathway/TS SCREEN COBOL Reference Manual for an explanation of SEND errors. 0005 PATHMON is unavailable. Cause. The PATHMON name does not exist. Recovery. Provide another PATHMON name. 0006 A problem occurred while communicating with the VHS Server. Cause. The SEND request resulted in an I/O error. The error is indicated by the second number in the message.
VHS Browser Messages 0011 A CALL error was returned while invoking the HELP program. 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. Recovery. 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. Cause.
VHS Browser Messages 0020 A CALL error was returned from the DETAIL program. Cause. The DETAIL 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. Recovery. See the Pathway/TS SCREEN COBOL Reference Manual for an explanation of CALL errors. 0021 A CALL error was returned from the HELP program. Cause. The HELP program unit terminated abnormally.
VHS Browser Messages 0024 A CALL error was returned from the ENVIRONMENT program. Cause. The ENVIRONMENT 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. Recovery. See the Pathway/TS SCREEN COBOL Reference Manual for an explanation of CALL errors. 0030(A) Printing Cause. A print screen is currently being performed. Recovery. None. 0031(A) Screen printed.
VHS Browser Messages 0034 There is no previous page. Cause. You are already at the first page. Recovery. None. 0035 Type correct destination name. Then press F9 to print. 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. Recovery. Type the correct destination name and press F9 to print. 0050 You can't change criteria while you're doing this. Cause.
VHS Browser Messages 0061 You can not change the environment name while you are doing this. 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. Recovery. Try your action again. 0062 There is no prompt on this screen. You can not do this. Cause.
VHS Browser Messages 0066 Select only one prompt to send your reply. Cause. The Send Reply function key (F6) was pressed, but you have selected more than one prompt to reply to. Recovery. Select only one prompt by entering a character in column 1 before pressing F6. 0067 Select a prompt before sending your reply. Cause. The Send Reply function key (F6) was pressed, but you did not select any prompt to reply to. Recovery. Select only one prompt by entering a character in column 1 before pressing F6.
VHS Browser Messages 0087(A) Detailed environment information updated. Cause. The Environment Detailed screen indicates that the selected environment detailed information has been correctly updated on the screen (F11). Recovery. None. 0088(A) Current environment set. 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). Recovery. None.
VHS Browser Messages 0103 The primary file does not exist. Cause. The primary file does not exist. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error. 0104 An error occurred while opening a primary file. Cause. An error occurred while opening a primary file. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error.
VHS Browser Messages 0109 The prompt file is empty. Cause. The prompt file is empty. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error. 0110 An error occurred at a key position in the prompt file. Cause. An error occurred at a key position in the prompt file. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error.
VHS Browser Messages 0114 Can not get the information requested. Cause. Cannot get the information requested. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error. 0115 An error occurred while closing the VHS process. Cause. An error occurred while closing the VHS process. The second number in the error message indicates a file-system error. Recovery.
VHS Browser Messages 0119 An invalid file date occurred. Cause. An invalid file date occurred. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error. 0120 A primary name error occurred. Cause. The primary name does not exist in this environment. The second number in the error message indicates a file-system error. Recovery. Use the ERROR program to get an explanation of the file-system error.
VHS Browser Messages 0140 These are the last messages in this primary file. Cause. You pressed NEXT-PAGE within the log browser screen but you are already on the last available messages. Recovery. None. 0141 There is no previous message in this primary file. Cause. You pressed PREV-PAGE within the log browser screen but you are already on the first available messages. Recovery. None. 0142 There is no record in this primary file matching these criteria. Cause.
VHS Browser Messages 0145 The minutes you entered are invalid. Choose others. Cause. You pressed the Change Search Criteria function key (F2) after you changed minutes. But the entered minutes are invalid. Recovery. Change minutes and press the F2 function key again. 0146 You entered an invalid month. Choose another. Cause. You pressed the Change Search Criteria function key (F2) after you changed month. But the entered month is invalid. Recovery. Change the month and press the F2 function key again.
VHS Browser Messages 0150 You entered an invalid year. Choose another Cause. You pressed the Change Search Criteria function key (F2) after you changed year. But the entered year is invalid. Recovery. Change the year and press the F2 function key again. 0160 (A) Automatic screen update is performed. Cause. The update of the VHS Prompt screen performed successfully. Recovery. None. 0161 (A) Screen thawed and refreshed. Cause. The VHS Prompt screen was thawed and the values have been refreshed. Recovery.
VHS Browser Messages 0171 Reply has been done successfully. The prompt file is empty. 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. Recovery. None. 0180 Unable to get the Prompt file opener process name. 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 file-system error.
VHS Browser Messages Recovery. 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. Cause. The VHS Browser server has received an unknown request. Recovery. Repeat your request. 1001 Request sent to the wrong server. Cause. The server identification is invalid. Recovery. Repeat your request.
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 Cause. This command is not supported by the VHS subsystem. Recovery. Use HELP VHS for a list of all supported commands. VHS 00101 Too many opened VHS servers Cause. VHSCI cannot open any more VHS servers. Recovery. Exit and re-enter VHSCI, or start another VHSCI session.
Message Descriptions VHSCI Messages VHS 00105 Logtype of the primary log destination cannot be altered Cause. The logtype of the primary log destination is not alterable. It must always be ALL. Recovery. 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 Cause. You cannot delete the primary log destination. It must always exist. Recovery. None. VHS 00107 Log destination does not exist Cause.
Message Descriptions VHSCI Messages VHS 00110 File-name already used by VHS as a critical file name 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.
Message Descriptions VHSCI Messages Recovery. Issue the command again and, if the problem persists, contact your service provider. VHS 00115 Version incompatibility between VHSCI and VHS server Cause. The VHSCI version is more recent than the VHS server version. Recovery. Make sure that VHSCI has the same version as the VHS server. VHS 00116 Invalid SSID into SPI buffer Cause. The SSID token present in the SPI buffer is invalid. Recovery.
Message Descriptions VHSCI Messages VHS 00120 Unable to switch the primary log Cause. An error occurred during the execution of the switchlog command. For more information, see the Appendix D, VHS Event Messages. Recovery. Correct the error and redo the command. VHS 00121 Unable to alter the EMS collector Cause. VHS was unable to alter the define =_EMS_collector. For more information, see the Appendix D, VHS Event Messages. Recovery. Correct the error and redo the command.
Message Descriptions VHSCI Messages Recovery. Correct the security string. VHS 00126 Invalid evironment name. Cause. The specified environment name string is invalid. Recovery. Correct the environment name string. VHS 00127 parameter-name not modifiable when VHS-GUI-MODE is set to ON. Cause. This parameter is not modifiable when VHS-GUI-MODE is set to ON. Recovery. None. VHS 00200 Command not implemented Cause. The specified command is supported by the VHS server, but it is not implemented yet.
Message Descriptions VHSCI Messages VHS 00203 The given CPU number is already the primary CPU Cause. The specified CPU is already the primary CPU of the VHS server. Recovery. Specify the backup CPU of the VHS server. VHS 00204 Values identified by question marks (??) could not be obtained Cause. Some values could not be obtained from the VHS server. Available values are displayed; missing values are identified with question marks (for example:??,?????). Recovery. This is a warning.
Message Descriptions VHSCI Messages VHS 20004 No more than n numbers are allowed in this list Cause. Too many comma-separated values have been specified in a list of numbers. Recovery. Remove the extra values from the list. VHS 20006 This command is only valid with a terminal for an infile Cause. The specified command will not function properly unless the VHSCI input file is a terminal. Recovery.
Message Descriptions VHSCI Messages Recovery. Contact your service provider. VHS 20034 Input string is too long Cause. Too much text on one command line. Recovery. Put separate commands on separate command lines or issue one command for each object name. VHS 20035 Command line does not exist Cause. The command issued attempted to refer to a command that either no longer exists or never existed in the history buffer. Recovery. Correct the command to refer to a command in the history buffer.
Message Descriptions VHSCI Messages VHS 20049 CPU is unavailable Cause. The specified CPU is currently unavailable. Recovery. Use the CPUS system-name command to determine which CPUs are currently available for a given system. VHS 20050 System is unavailable Cause. The specified system is currently unavailable. Recovery. Use the CPUS DETAIL command to determine which systems are currently available. VHS 20051 Subsystem is not supported Cause.
Message Descriptions VHSCI Messages VHS 20054 NEWPROCESS error 2: No process control block available Cause. Too many processes are running on the system right now. Recovery. Consult your system manager. VHS 20055 NEWPROCESS error 4: Unable to allocate map Cause. System resources are currently unavailable. Recovery. Consult your system manager. VHS 20056 NEWPROCESS error 6: File format error on file-name Cause. The program file is invalid. Recovery. If the program resides on $SYSTEM.SYSTEM or $SYSTEM.
Message Descriptions VHSCI Messages VHS 20060 NEWPROCESS error 10: monitor process Unable to communicate with system Cause. The system monitor process is currently unavailable. Recovery. 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 Cause. The program and library files are identical. Cause. Reissue the command with the correct library name.
Message Descriptions VHSCI Messages VHS 20069 Invalid help command combination specified 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. Recovery. 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 Cause.
Message Descriptions VHSCI Messages VHS 20084 Quoted string can be no more than number characters long Cause. This instance of a quoted string can contain only number characters. Recovery. 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 Cause. The expected item is too long. Recovery. Shorten the item to meet the required length limit.
Message Descriptions VHSCI Messages VHS 20089 The REPEAT command may only appear once per command line Cause. The REPEAT command acts upon the entire remainder of the command line, and therefore can only appear once in any command line. Recovery. To obtain multiple levels of iteration, use REPEAT commands within OBEY files. VHS 20090 name value must be from lower-bound to upper-bound Cause. The specified value is out of range. Recovery. Specify a value within range.
Message Descriptions VHSCI Messages VHS 20095 No aliases match the wildcard Cause. There are no aliases defined which match the wildcard entered. Recovery. 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 Cause. The swap file location is invalid. The file error number details the cause of the error. Recovery. Select a valid swap file location.
Message Descriptions VHSCI Messages VHS 20103 Alias buffer is full. No more aliases can be defined. Cause. Either the maximum number of aliases or the size of the alias text buffer has been exceeded. Recovery. Delete an alias before adding the next or do not add any more aliases. VHS 20104 A recursive alias has been detected Cause. An alias that refers to itself directly or by other aliases has been invoked. Recovery. Use the CLEAR ALIAS command to delete the alias that is causing the recursive loop.
Message Descriptions VHSCI Messages VHS 20111 The size of the specified object names exceed the allocated space Cause. Too many object names were specified in a single command. Recovery. Split the object names into two commands. VHS 20112 Maximum number of allowable errors exceeded 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. Recovery.
Message Descriptions VHSCI Messages VHS 20117 NEWPROCESS error 17: DEFINE context error Cause. The specified DEFINEs could not be processed. Recovery. Consult your system manager. VHS 20118 NEWPROCESS error 18: Process/device subtype is illegal Cause. A specified device was of the wrong type. Recovery. 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 Cause.
Message Descriptions VHSCI Messages Recovery. Contact your service provider. VHS 20203 INTERNAL ERROR: Illegal value: n Call: proc Param: param Cause. An incorrect value was supplied as a parameter to a procedure. Recovery. Contact your service provider. VHS 20204 Object name is too long Cause. The specified object name is too long. Recovery. Reenter the object name. VHS 20205 INTERNAL ERROR: A call to PUTPOOL failed Cause. A call to the procedure PUTPOOL failed. Recovery.
Message Descriptions VHSCI Messages VHS 20209 The unit n must be positive Cause. The specified unit must be a positive number. Recovery. Use the FC command to change the number to a positive value. VHS 20210 Invalid terminal type for REVERSE and/or DIM option Cause. The SETPROMPT command with the REVERSE and/or DIM option was specified for a terminal other than a 6530 or a 6520. Recovery. Use the FC command to remove the REVERSE and/or DIM option and reissue the command.
Message Descriptions VHSCI Messages VHS 20214 Exceeded max number of chars allowed on the RUN command line Cause. The number of characters following the name of a program file exceeds the maximum number allowable. Recovery. Do not type more than two lines of text on the RUN command line. VHS 20215 Expecting a blank Cause. A blank character was expected at this point in the command. Recovery. Use the FC command to fix the command to include a blank.
Interprocess Communication Messages VHSCI Messages Interprocess Communication Messages The following subsection lists interprocess communication warnings and errors you might encounter when using VHSCI. -00001 Already using resource Cause. The object of the command is already using the requested resource. Recovery. This is a warning. No action is necessary. -00002 Command was accepted and is being processed by obj-name Cause. A command was issued and received by the target subsystem.
Interprocess Communication Messages VHSCI Messages -00005 Command is not supported by this subsystem Cause. A command was issued that is unknown to the subsystem that owns the object name. Recovery. For more information, about the commands supported by the subsystem, see the subsystem-specific reference manual. -00006 Command sequence invalid for obj-name 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.
Interprocess Communication Messages VHSCI Messages Recovery. Refer to the Guardian Procedure Errors and Messages Manual for recovery procedures. -00011 Invalid type of file: file-name for obj-name Cause. The file specified in the request has an invalid format. Recovery. Determine the valid file type code for the target file and reissue the command. -00012 Maximum Limit Exceeded: limit-number for obj-name Cause. A fixed limit or configuration limit was exceeded.
Interprocess Communication Messages VHSCI Messages Recovery. This is a warning. No action is necessary. -00016 Object name is already in state state Cause. A request to change the summary state of an object was issued but the object is already in that state. Recovery. This is a warning. No action is necessary. -00017 Object name Not Found Cause. The specified object name could not be found within the subsystem. This usually means the object has not yet been added.
Interprocess Communication Messages VHSCI Messages -00022 Security violation for obj-name Cause. A sensitive command request was attempted by an unauthorized user. Recovery. If possible, acquire the proper security and reissue the request. -00023 Internal Error: SPI error num text on call (Tnm: num) Cause. A call to an SPI procedure resulted in an error. Recovery. Contact your service provider. -00024 Internal Error: Invalid subsystem ID: Number: number Version: number Owner: subsystem Cause.
Interprocess Communication Messages VHSCI Messages -00027 Internal Error: (tnm:num) Duplicate Token: Token Code: HEX-num Cause. A token that can be specified only once appears more than once in the command request buffer. Recovery. Contact your service provider. -00028 Internal Error: Invalid Token Length: (tnm:num, Len: num) Token Code: HEX-num Cause. Token length is either too long or too short. Recovery. Contact your service provider.
Interprocess Communication Messages VHSCI Messages -00032 Incompatible Version: num, Command required subsystem to be num for obj-name 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. Recovery.
Interprocess Communication Messages VHSCI Messages -00036 Value of attribute attribute-name may not be used in conjunction with attribute-name for object-name Cause. The particular value specified with the named attribute conflicts with one of the other attribute values for the object. Recovery. Specify a different value or delete the attribute, and reissue the command. -00037 Command power level too weak for the state of object object-name Cause.
Interprocess Communication Messages VHSCI Messages -00986 Attribute is not alterable: attr Cause. An attempt was made to alter an attribute that is not alterable. Recovery. Correct the problem and retry the request. -00987 REQID found in SPI buffer sent by non-qualified requester Cause. A security error occurred. A requester must have a user ID of -1 to send a REQID token to the message buffer. Recovery. Obtain the proper authority, if possible, and retry the request.
Interprocess Communication Messages VHSCI Messages -00998 Internal Error: subsystem Server version could not be obtained from Cause. The server version is not valid. Recovery. Contact your service provider.
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.
Log File Format VHS DDL Files Log File Format This subsection describes the formats of log messages. Example H-1 on page H-3 shows an example of a log file. File and Spooler All the messages logged into a file or into a spooler location have this 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.
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.
File and Spooler VHS DDL Files Virtual Hometerm Subsystem (VHS) Manual—429311-002 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.
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.
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 (EMS). 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.
DDL Glossary enclosed in lists. See Subsystem Programmatic Interface (SPI). Compare header token. DDL. See Data Definition Language (DDL). Debug. An HP debugger. Allows you to use code and data breakpoints and to view variables by data space locations and offsets. Replaced by Inspect. For more information, see Inspect. Distributed Systems Management (DSM). A set of tools used to manage HP NonStop™ systems and Expand networks. Distributed Systems Management Application (DSMA).
event Glossary 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. event configuration file. A file that contains configuration information to control what ViewPoint displays on an events screen.
filter object file Glossary 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. FUP. See File Utility Program (FUP). header token.
management interface Glossary 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. management process. The process through which an application issues commands to a subsystem.
outstanding prompt Glossary application for management of important events; it is not an inherent part of the event message. 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.
production management Glossary production management. The set of regularly scheduled activities that keeps the applications on a system or network of systems running smoothly. These activities 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.
status item Glossary of status configuration files; operators specify on the Profile screen which file ViewPoint uses to display status at their terminals. 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.
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.
ViewPoint Glossary Virtual Hometerm Subsystem (VHS) Manual—429311-002 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-6 ALTER command 7-7 Application prompts 3-11 Applications, specifying VHS as home terminal 3-5 Architecture 1-2 ASSIGN command 7-14 ASSIGNs 2-34 ASSUME command 7-17 Attributes 6-2 Automatic update delay 4-20 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-
D Index Commands (continued) STATUS 7-45 summary C-1 SYSTEM 7-50 VERSION 7-52 VOLUME 7-53 COMMENT command 7-19 Comments 5-5 Configuration file, modifying 2-28 function keys 5-6 inspect processing 3-11 Configuration file A-1 CONFIRM command 7-20 CPUS command 7-20 CPU, switching 5-23 Custom configuration file A-1 description of 2-31 editing 5-8 D Debug messages 3-10 DEFINEs 2-37 DELAY command 7-22 DETAIL ERROR command 7-23 Disk file names 6-4 Display messages 3-9 E einspect Glossary-2 eInspect prompt proc
H Index Files (continued) VHSSTART 3-2, A-2 Filter, ViewPoint 3-19, I-1 Function keys configuring 5-6 setting 7-4 H HELP online, command mode 5-9 online, menu mode 5-11 HELP command 7-26 Help key 5-6 Help screens 4-7 HISTORY command 7-27 Home terminal, specifying 3-5 I INFO command 7-28 Inspect file 3-12 messages 3-9 Installation files 2-4, 2-25 parameters 2-8, 2-15, 2-23 restrictions 2-17 security considerations 2-28 Installing VHS 2-2 VHS Browser as stand-alone Pathway system 2-22 VHS Browser in ViewP
P Index P PAGESIZE command 7-37 Page, setting size 7-37 PARAM command 7-38 Parameters inspect processing 3-11 list of 2-35 PATHCONF file 2-20 PATHDEFS file 2-20 PATHMONs, switching 4-20 PATHSTRT file 2-20 Pathway configuration files 2-20, 2-28 examples 3-5 PAUSE command 7-39 Primary log file record definition H-1 Printing a screen 4-25 process H-1 Processes, multiple 1-5 Profile screen 4-18 Prompt Browser screen 4-13 Prompt Detail screen 4-15 Prompt, setting 7-41 Q Question mark (?) 7-3 Quitting VHSCI 5-
V Index V VERSION command 7-52 VHS accessing 4-2 architecture 1-2 ASSIGNs 2-34 assuming a process 7-17 before using 3-1 benefits 1-1 Browser 1-4 components 1-3 conversational interface 1-3 DEFINEs 2-37 environments 1-7, 5-25 event messages D-1 help screens 4-7 installing 2-2 limits B-1 management applications 1-2 managing messages 3-7 modifying configuration files 2-28 multiple processes 1-5 network 1-8 node 1-6 parameters 2-35 process 1-3 Profile screen 4-18 run syntax 3-4 run-time options 2-34 screens 4
W Index VOLUME command 7-53 W Warning messages, setting number to allow 7-6 Z ZPATHWAY file 2-28 ZVHSCONF file 2-28 ZVHSSTRT file 2-28 Special Characters { 3-14 Virtual Hometerm Subsystem (VHS) Manual—429311-002 Index -6
