Operator Messages Manual
Chapter 128 VHS (Virtual Hometerm Subsystem) Messages
The messages in this chapter are sent by the NonStop Virtual
Hometerm Subsystem (VHS). The subsystem ID displayed by these messages
includes VHS as the subsystem name.  |  |  |  |  | NOTE: Negative-numbered messages are common to most subsystems. If
you receive a negative-numbered message that is not described in this
chapter, see Chapter 15. |  |  |  |  |
1 Process process-id-string has entered Inspect. Savefile savefile-name was created. Process has been stopped. Program file program-name. Primary log file primary-log-name | Cause The VHS generates this critical message when an application
goes into Inspect and Inspect prompts the VHS process. Effect A save file is created, and the program is stopped. Recovery Advise software personnel of this error message. Use the saveabend
file created to fix the application’s problem. See the primary
log file for more information about the problem. |
2 Process process-id-string entered Inspect. Savefile savefile-name could not be created due to file-system error file-error. Process has been stopped. Program file program-name. Primary log file primary-log-name. | file-error | identifies a file-system error. |
Cause The VHS generates this critical message when an application
goes into Inspect. Inspect prompts the VHS process, and the VHS tries
to create a saveabend file but encounters an error. Effect No saveabend file is created. Recovery Advise software personnel of this error message. More information
about the problem is available in the primary log file. See Appendix B, for a definition
of the specified error. For more detailed information including recovery
actions, see the Guardian Procedure Errors and Messages
Manual. |
3 Process process-id-string entered Inspect. The command "command-string" has been sent to Inspect. Program file program-name. Primary log file primary-log-name. | Cause The VHS generates this critical message when it is prompted
by Inspect and sends a command (OBEY) file to Inspect. Effect The VHS process supplies a command file to Inspect. Recovery Advise software personnel of this error message. See the primary
log file for more information about the problem. |
4 Pathway terminal terminal-name 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. | Cause The VHS generates this critical message when a user enters the
INSPECT TERM command in PATHCOM to invoke the Inspect process to debug
a SCREEN COBOL program running on a Pathway/TS terminal. Effect The VHS process supplies a command or insert in the previous
message file to Inspect. Recovery Advise software personnel of this message. See the primary log
file for more information about the problem. |
5 Process process-id-string entered Debug. Process has been stopped. Program file program-name. Primary log file primary-log-name. | Cause The VHS generates this critical message when it is prompted
by Debug. Effect The VHS process supplies commands to display register values
and stop the application. Recovery Look at the results of these commands in the primary log file
and correct the application problem. |
6 message-string. Display
text received from process process-id-string. Program file program-name. Primary
log file primary-log-name. | Cause The VHS generates this message when it receives a user display. Effect The primary log file shows the user display. Recovery Informational message only; no corrective action is needed. |
7 PIN process-id-string. Prompt "prompt-string". Program file program-name. Primary log file primary-log-name | Cause The VHS generates this action-attention message when it is prompted
by an application. Effect The prompt file contains the application prompt text. Recovery Use the VHS Prompt Browser facility to select and answer the
application prompt. |
8 PIN process-id-string. Prompt "prompt-string". Reply "reply-string". Program file program-name. Primary log file primary-log-name. | Cause The VHS generates this action-completion message when a user
answers the application prompt. Effect The VHS sends the reply to the application and deletes the prompt
from the prompt file. Recovery Informational message only; no corrective action is needed. |
100 Process VHS-process-name successfully started. | Cause The VHS generates this message when the VHS has successfully
started. Effect The VHS is started. Recovery Informational message only; no corrective action is needed. |
101 Process VHS-process-name created backup in CPU cpu-number. Priority priority. Program file program-name. | Cause The VHS generates this message when a new VHS process in the
backup processor has been successfully created. Effect A VHS process in the backup processor has been created. Recovery Informational message only; no corrective action is needed. |
102 Process VHS-process-name created primary log file primary-log-name. | Cause The VHS generates this message when it has created a new primary
log file. Effect The VHS process created a new primary log file. Recovery Informational message only; no corrective action is needed. |
103 Process VHS-process-name switched log files from file old-primary-log to new-primary-log because old file is
full. | Cause A VHS primary log file rollover occurred. Effect The VHS created a new primary log file. Recovery Informational message only; no corrective action is needed. |
104 Process VHS-process-name failed to create backup in CPU cpu-number due to NEWPROCESS error newprocess-error : error-text. Priority priority. Program file program-name. | Cause The VHS generates this critical message when it cannot create
a backup process because of a NEWPROCESS error. Effect The primary VHS process retries this error unless the NEWPROCESS
error indicates that the backup processor is down. In this case, the
VHS tries to create a new backup 10 seconds after it receives the
CPU UP system message for the backup processor. For errors other than
processor down, the VHS primary process waits for 10 seconds and retries;
if this first attempt fails, the next attempt occurs after a 20-second
delay. Thereafter, the primary process attempts to create a new backup
process every 20 seconds. Recovery See Appendix C,
for information about the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. |
105 Process VHS-process-name, backup process cpu,pin stopped. | Cause The VHS backup process has stopped. Effect The VHS primary process attempts to create a new backup process
after a one-minute delay. Recovery Informational message only; no corrective action is needed. |
106 Process VHS-process-name, backup process cpu,pin deleted (CPU DOWN). | Cause The processor in which the backup process was running has failed. Effect The primary VHS process does not attempt to create a backup
until it receives the CPU UP system message for its backup processor. Recovery Follow the recommended procedure for a processor failure. |
107 Process VHS-process-name, backup process cpu,pin abended. | Cause The VHS backup process abended. Effect The VHS primary process attempts to create a new backup process
after a 10‑second delay. If the VHS primary process cannot create
the backup process after 10 seconds, it retries every 20 seconds. Recovery Informational message only; no corrective action is needed. |
108 Process VHS-process-name, takeover by backup in CPU cpu because
primary process cpu,pin takeover-text. | Cause The VHS generates this critical message after a takeover by
the VHS backup process. The primary VHS process or the processor in
which it ran has failed. Effect If the primary VHS process has failed, an attempt is made to
create a new backup. In the case of a processor failure, a new backup
is created after receipt of a CPU UP system message by the new primary
process. Recovery If the primary VHS process abended, investigate the error message
log to determine why. |
109 Process VHS-process-name, CHECKPOINT failed due to file-system error error-number. | error-number | identifies a file-system error. |
Cause The VHS generates this critical message when an error occurs
during a checkpoint operation. Effect The VHS backup process has received an input/output (I/O) error
during a checkpoint operation. The VHS backup process is stopped,
and an attempt is made to create a new backup process after a 10-second
delay. Resource allocation failures (errors 30 through 37) might indicate
that the primary processor or backup processor is overloaded. Recovery See Appendix B,
for a definition of the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. For errors 30 through 37, free up system resources. If this
does not correct the problem or results in a different error, contact
your support representative and provide all relevant information as
follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
110 Process VHS-process-name, CHECKOPEN failed on file filename due
to file-system error file-error. | file-error | identifies a file-system error. |
Cause The VHS generates this critical event message when the backup
VHS process is unable to open a file previously opened by the primary
process. Effect The primary VHS process determines that its backup process is
malfunctioning. The VHS process stops its backup process and attempts
to create a new backup after a 10‑second delay. Recovery See Appendix B,
for a definition of the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. For errors 30 through 37, free up system resources. If this
does not correct the problem or results in a different error, contact
your support representative and provide all relevant information as
follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
111 Process VHS-process-name failed operation on primary log file primary-log-name due to file-system error file-error. | file-error | identifies a file-system error. |
Cause The VHS generates this critical message when it is unable to
access the primary log file. Effect The VHS continues processing. Recovery See Appendix B,
for a definition of the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. |
112 Process process-name deleted { (CPU DOWN). } { from internal table because this process
stopped communicating with VHS. Message type type-of-msg. Program file program-name.} | Cause The VHS generates this action-completion message when the processor
of an application is down or when an application stops communicating
with the VHS. Effect The VHS process deletes this application entry in its internal
opener table. Recovery Follow the recommended procedure for a processor failure, or
correct the problem that has made the applications unavailable. |
113 Process VHS-process-name created primary log alternate key file primary-log-alternate-key-file-name. | Cause The VHS generates this message when it has created a new primary-log
alternate‑key file. Effect The VHS continues processing. Recovery Informational message only; no corrective action is needed. |
114 Process VHS-process-name failed operation on prompt file prompt-file-name due to file-system error file-error. | file-error | identifies a file-system error. |
Cause The VHS generates this critical message when it is unable to
access the prompt file. Effect The VHS continues processing. If the VHS was trying to add a
new prompt in the prompt file, the new prompt is rejected and the
VHS returns error 2 (operation not allowed) to the application. Recovery See Appendix B,
for a definition of the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. |
115 Process VHS-process-name created prompt file prompt-file-name. | Cause The VHS generates this 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, and other records
contain all outstanding prompts for this VHS environment. Effect The VHS creates a new prompt file. Recovery Informational message only; no corrective action is needed. |
116 Process VHS-process-name created prompt alternate key file prompt-alternate-key-file-name. | Cause The VHS generates this message when it has created a new prompt
alternate-key file. Effect The VHS creates a new prompt alternate-key file. Recovery Informational message only; no corrective action is needed. |
117 Process VHS-process-name initialization procedure WARNING, unanswered prompt "prompt-text" found from program program-name. Prompt was deleted. | Cause The VHS generates this action-completion message when it restarts
and finds outstanding prompts not processed by the previous VHS process
that had the same VHS process name. Effect The VHS continues processing. Recovery Informational message only; no corrective action is needed. |
118 Prompt "prompt-text" deleted in prompt file prompt-file-name because process process-name is not available
for reply. | Cause The VHS generates this action-completion message when it detects
that a prompting application has closed the VHS process without receiving
the reply from the VHS for its prompt. Effect The VHS deletes the outstanding prompt from its prompt file. Recovery Informational message only; no corrective action is needed. |
119 Process VHS-process-name unable to reply to prompting process process-name because it is not available. Reply text "reply-text". | Cause The VHS generates this action-completion message when it cannot
reply to the application because the application is unavailable. Effect The VHS continues processing. Recovery Correct the problem that has made the application unavailable. |
120 VHSB: Process VHSB-process-name failed operation-name on configuration
file file-name due to file-system error
file-error. | file-error | identifies a file-system error. |
Cause The VHS Browser generates this message when an input/output
(I/O) error occurs on the configuration file. Effect The VHS Browser server stops. Recovery See Appendix B,
for a definition of the specified error. For more detailed information
including recovery actions, see the Guardian Procedure
Errors and Messages Manual. |
121 VHSB: Configuration file error. Invalid line
"line" detected in configuration file file-name. Continuing processing. | Cause The VHS Browser generates this message when an invalid line
format is read in the configuration file. Effect The VHS Browser server stops. Recovery Correct the line in the configuration file with a valid line
format. |
122 VHS Process VHS-process-name has an error file-system-error on the
Alternate collector alt-collector-name.
Program file vhs-object-file. Primary log
file primary-log-file-name. | Cause The VHS process was unable to log an EMS event to its alternate
collector. Effect There is no effect on the running process. If a new process
is started, it logs its message to the default collector. Recovery Take action according to the file-system error contained in
the EMS event. |
123 Unknown langnuage inspect-object, the corresponding
section is not loaded. Inspect file inspect-file. Line number number1.number2. | Cause An unknown language was found as a section name in the VHS Inspect
file. The corresponding section is skipped. VHS continues loading
the VHS Inspect file. Effect The corresponding section is not loaded. Recovery 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. VHS performs the default actions SAVE and EXIT
for that section. The language should not be selected from the list
provided in the VHS User’s Guide. |
124 Invalid program file name file-name, the corresponding section is not loaded. Inspect file inspect-file. Line number number1.number2. | Cause An invalid file name was found as a section name in the VHS
Inspect file. Effect The corresponding section was not loaded. VHS continues loading
the VHS Inspect file. Recovery 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. |
125 Invalid process name, the corresponding section
is not loaded. Inspect file inspect-file. Line number number1.number2. | Cause An invalid process name was found as a section name in the VHS
Inspect file. Effect The corresponding section was not loaded. Recovery 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. |
126 Inspect section section-name duplicate, only the first section is loaded. Inspect file inspect-file. Line number number1.number2. | Cause Two messages with the same name were found in the VHS Inspect
file. Effect The duplicate section is not loaded. Recovery Edit the file and correct the line specified in the EMS event
or remove the entire duplicate section. VHS will automatically reload
the Inspect file when another application traps into Inspect. |
127 Not enough space in VHS inspect table. Limit
of 5000 bytes reached. Section section-name skipped. Inspect file inspect-file. Stopped
at line number number1.number2. | Cause The total of bytes in the VHS Inspect file exceeds 5000, which
is the maximum limit. Effect This section is skipped and it tries to load the next section. Recovery Edit the file and remove unnecessary commands or sections. VHS
will automatically reload the Inspect file when another application
traps into Inspect. |
128 Too many sections in VHS inspect table. Limit
of 100 sections reached. Inspect file inspect-file. Stopped at line number number1.number2. | Cause The VHS Inspect file contains too many sections. The limit is
100 sections. Effect All sections after the 100th section are skipped. The message
specifies the last section that has been loaded. Recovery 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. |
129 Inspect processing stopped for process-id-string. The Inspect file was reloaded. Program
file program-file. | Cause If the VHS Inspect file is changed while VHS processes Inspect
prompts, VHS stops processing those Inspect prompts for all applications
and generates this event. Effect VHS stops processing those Inspect prompts and performs the
default operations Save and Exit. Recovery Informational message only; no corrective action is needed.
Do not modify the Inspect file during Inspect processing. |
130 Integrity problem with the Inspect process inspect-object.
VHS was prompted more than 10 times. | Cause One Inspect process can handle up to 10 different applications;
the number of Inspect prompts exceeded 10. Effect VHS does not accept the application prompts over 10 for the
same process. Recovery Stop some of the Inspect processes that are running. |
131 Opener table for process vhs-process-name is full at percentage-full%. | Cause The VHS opener table has reached the value of the OPEN-TABLE-THRESHHOLD
parameter. The default value for this parameter is 99%. Effect It has no effect on the running process. Recovery Informational message only; no corrective action is required. |
132 Invalid parameter parameter-text in section section-name, the corresponding
section is not loaded. Inspect file inspect-file. Line number number1.number2. | Cause An invalid parameter was found in a section of the VHS Inspect
file. Effect The corresponding section is not loaded. Recovery Edit the file and correct the line number displayed in the event.
Assign only valid parameters to the section and try to restart Inspect.
VHS will automatically reload the Inspect file when another application
traps into Inspect. VHS performs the default actions Save and Exit
for the corresponding section. |
133 Unable to unload Inspect file inspect-file. | Cause A problem occurred when trying to reload the VHS Inspect file;
the Inspect file specified in the VHSSTART file is not available. Effect This causes VHS to abend. Recovery Stop the VHS process. Load the Inspect file and restart VHS.
Also verify the VHS Inspect file condition and security. |
134 EDITOPEN error file-error on inspect-file. | Cause The Inspect file specified in the VHSSTART file cannot be opened. Effect This causes VHS to abend. Recovery Stop the VHS process. Make sure the INSPECT file, as specified
in VHSSTART, can be opened and restart VHS. |
135 READEDIT error file-error on inspect-file. | Cause The Inspect file specified in the VHSSTART file is not readable. Effect The Inspect file is not loaded. Recovery The Inspect file might be corrupt. Create a new Inspect file. |
136 Unable to alter Define=_EMS-COLLECTOR. Error file-error. | Cause The attributes of _EMS_COLLECTOR cannot be altered. Effect There is no effect on the running process. Recovery Stop VHS and restart it. |
137 Inspect file inspect-file reloaded. | Cause The VHS Inspect file is reloaded. Effect It has no effect on the running process. Recovery Informational message only; no corrective action is needed. |
138 Prompt “prompt-string” deleted in prompt file prompt-file because the prompt has been cancelled by process process-id-string. | Cause An application has cancelled a previous prompt by sending a
Cancel message. Effect It has no effect on the running processes. Recovery Informational message only; no corrective action is needed. |
139 Prompt “prompt-string” deleted in prompt file prompt-file because another prompt has been received from process process-id-string. | Cause VHS has received a second prompt from an application without
sending a reply to the first one. VHS deleted the first prompt from
its prompt file. Effect It has no effect on the running process. Recovery Informational message only; no corrective action is needed. |
140 Invalid keyword inspect-object. Inspect file inspect-file. Line number1.number2. | Cause An invalid keyword was found in the VHS Inspect file. Effect The corresponding section is not loaded. Recovery VHS will automatically reload the Inspect file when another
application traps into Inspect. VHS performs the default actions Save
and Exit for the corresponding section. The keywords must be selected
from the list of keywords specified from the list of keywords in the VHS User’s Guide. |
141 Line number number1.number2 is too long, only the first 132 characters are kept. Inspect file inspect-file. | Cause A line from the VHS Inspect file has more than 132 characters. Effect Only the first 132 characters are recognized and the rest of
the command is ignored. Recovery The line should not contain more than 132 characters. VHS will
automatically reload the Inspect file when another application traps
into Inspect. |
142 timestamp pid environment-name: Invalid
value for AUTOMATIC-INSPECT-PROCESSING parameter in section inspect-object. Expecting ON or OFF. The corresponding
section is not loaded. Inspect file inspect-file. Line number number1.number2. | 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. | inspect-object | is the rejected line found in the Inspect file. | inspect-file | is the name of the VHS Inspect file. |
Cause An invalid value was given for the parameter AUTOMATIC-INSPECT-PROCESSING
in the VHS Inspect file. Expected value is ON or OFF. Effect The corresponding section is skipped. VHS continues loading
the VHS Inspect file. Recovery 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. |
143 Inspect file inspect-file loaded. | Cause The VHS Inspect file is loaded. Effect It has no effect on the running processes. Recovery Informational message only; no corrective action is needed. |
144 Unable to reload Inspect file inspect-file. | Cause A problem occurred while reloading the VHS Inspect file. The
Inspect file cannot be loaded. Effect It has no effect on the running processes. Recovery Informational message only, no corrective action needed. |
145 Section name section-name remote, the corresponding section is not loaded. Inspect file inspect-file. Line number number1.number2. | Cause In the VHS Inspect file, a section name, process, or program
file name is a remote process or program file name. VHS only accepts
a local process name and local program name. A remote section is present
in the Inspect file. Effect The corresponding section is not loaded. Recovery VHS performs the default actions Save and Exit for the corresponding
section. VHS will automatically reload the Inspect file when another
application traps into Inspect. For more detail on the format of the
Inspect file, see the NonStop Virtual Hometerm Subsystem
(VHS) Manual. |
146 Program file file-name does not exist, the corresponding section is not loaded. Inspect
file inspect-file. Line number number1.number2. | Cause In the VHS Inspect file, a section name for the PROGRAMFILE
keyword specified a file name that does not exist. The file must exist. Effect The corresponding section is not loaded. Recovery VHS performs the default actions Save and Exit for the corresponding
section. VHS will automatically reload the Inspect file when another
application traps into Inspect. For more detail on the format of the
Inspect file, see the NonStop Virtual Hometerm Subsystem
(VHS) Manual. |
147 Invalid text inv-text following section name section-name,
the corresponding section is not loaded. Inspect file inspect-file. Line number number1.number2. | Cause One or more characters are found following a section name in
the VHS Inspect file. Effect The corresponding section is not loaded. Recovery VHS performs the default actions Save and Exit for the corresponding
section. VHS will automatically reload the Inspect file when another
application traps into Inspect. For more detail on the format of the
Inspect file, see the NonStop Virtual Hometerm Subsystem
(VHS) Manual. |
148 Process process-name deleted from internal table because this process stopped communicating
with VHS. Message type type-of-msg. Program
file program-name. | Cause An application stopped communicating with VHS. The VHS process
deletes this application entry in its internal opener table. Effect The process is deleted from the opener table and it can no longer
be applied. Recovery No recovery action can be performed. |
150 Inspect process process-id-string. Message “message-string”
[received from|sent to] Inspect. Program file program-name. Promary log file primary-log-name. | Cause An application entered Inspect. VHS received a message from
Inspect or sent a message to Inspect and still does not know which
application is trapped into Inspect. The text received from or sent
to Inspect is the text of the message. This event message is generated
only when the VHS-GUI-MODE parameter is set to ON. Effect It has no effect on the running process. Recovery Informational message only; no corrective action is needed. |
151 Process process-id-string entered Inspect. Message “message-string” [received from|sent to] Inspect. Program file program-name. Primary log file primary-log-name. | Cause An application entered Inspect. VHS received a message from
Inspect or sent a message to Inspect and knows which application is
trapped into Inspect. The text received from or sent to Inspect is
the text of this message. This event message is generated only when
the VHS-GUI-MODE parameter is set to ON. Effect It has no effect on the running process. Recovery Informational message only; no corrective action is needed. |
152 Pathway terminal terminal-name entered Inspect.
Message “message-string” [received from|sent to] Inspect.
PATHMON process name pathmon-name. Inspect process process-id-string.
Primary log file primary-log-name. | Cause The applied file is in SCOBOL, but the state of the VHS is not
and the GUI mode is active. Effect There is no effect on the running process. Recovery Advise software personnel of this event message. More information
about the problem is available in the primary log file. |
153 Process process-id-string entered Debug. Message “message-string” [received from|sent to] Debug. Program file program-name. Primary log file primary-log-name. | Cause An application entered Debug. VHS received a message from Debug
or sent a message to Debug. The text received from or sent to Debug
is the text of this message. This event message is generated only
when the VHS-GUI-MODE parameter is set to ON. Effect It has no effect on the running process. Recovery Advise software personnel of this event message. More information
about the problem is available in the primary log file. |
154 Process process-id-string. Prompt “prompt-string”.
Program file program-name. Primary log
file primary-log-name. | Cause A prompt has been pending for at least the value of the PROMPT-EVENT-RESEND-DELAY
parameter (in minutes). Effect It has no effect on the running process. Recovery Informational message only; no corrective action is needed. |
200 Internal error internal-error-code occurred in VHS due to error text. Program
filename program-name. | Cause The VHS generates this critical message when it encounters an
internal error. Effect The VHS primary process stops. When the VHS is just starting,
some verifications are made. If an internal error occurs in those
verifications, the VHS primary process stops and the VHS is not available
because the backup process was not started. If an internal error occurs
when the backup process is running, then the primary process is stopped
and a takeover by the backup process occurs. Recovery Contact your support representative and provide all relevant
information as follows: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
|