HP 3000 MPE/iX MPE/iX software Error Messages Manual

MPE/iX Error Messages Manual
Volume III
HP 3000 MPE/iX Computer Systems
Edition 4
Manufacturing Part Number: 32650-90880
E0300
U.S.A. March 2000
Notice
The information contained in this document is subject to change
without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
material, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. Hewlett-Packard
shall not be liable for errors contained herein or for direct, indirect,
special, incidental or consequential damages in connection with the
furnishing or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of
its software on equipment that is not furnished by Hewlett-Packard.
This document contains proprietary information which is protected by
copyright. All rights reserved. Reproduction, adaptation, or translation
without prior written permission is prohibited, except as allowed under
the copyright laws.
Restricted Rights Legend
Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013.
Rights for non-DOD U.S. Government Departments and Agencies are
as set forth in FAR 52.227-19 (c) (1,2).
Acknowledgments
UNIX is a registered trademark of The Open Group.
Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.
© Copyright 1988, 1990, 1992, 2000 by Hewlett-Packard Company
2
Contents
1. Error Messages
(ACTIVATE ERROR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Break Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CIPER Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
CIPER Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Clock/Timers Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CM Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
(Subsystem 169) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CM Emulator & OCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
CM Support Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Debug Low Level Breakpoint Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Disk Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Distributed Terminal Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2. Error Messages Viii C 2
File System Label Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File System Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Floating Point Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High Level I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HPIB Adapter Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HPIO Channel Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Low Level I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Measurement Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
53
58
60
64
68
78
79
89
3. Error Messages Viii C 3
Memory Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
MPE/iX Data Communications Buffer Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
MPE/iX Error Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Native Mode Device File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
NLIOUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Parser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Port (IPC) Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Private Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Reply Information Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4. Error Messages Viii C 3
Secondary Storage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Socket Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Special Routine For Stack Unwind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
147
148
150
150
3
Contents
SUSPEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Symbolic Debugger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Sysmain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
System Disk Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
System Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
5. Error Messages V iii C 4
Table Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
TermDSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201
Terminal I/O Manager for Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
Transaction Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
6. TurboIMAGE/XL V iii C 5
Schema Processor Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237
Library Procedure Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
7. TurboIMAGE/XL V iii C 5
Utility Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276
User Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307
Workstation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
4
Tables
Table 6-1.. Status Area Changes for Native Applications. . . . . . . . . . . . . . . . . . . . . . . . . 248
5
Tables
6
Preface
MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of
forward-compatible operating systems for the HP 3000 line of computers.
In HP documentation and in talking with HP 3000 users, you will encounter references to
MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs
written for MPE XL will run without change under MPE/iX. You can continue to use MPE
XL system documentation, although it may not refer to features added to the operating
system to support POSIX (for example, hierarchical directories).
Finally, you may encounter references to MPE V, which is the operating system for HP
3000s, not based on PA-RISC architecture. MPE V software can be run on the PA-RISC
(Series 900) HP 3000s in what is known as compatibility mode.
7
8
1 Error Messages
(ACTIVATE ERROR)
20
MESSAGE
ACTIVATION OF SYSTEM PROCESS NOT ALLOWED
(ACTIVATE ERROR 20)
21
MESSAGE
ACTIVATION OF MAIN PROCESS NOT ALLOWED
(ACTIVATE ERROR 21)
Break Handling
(Subsystem 158)
1
5
6
7
MESSAGE
Jsinfo failed to return the job type to break
management.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Jsinfo failed to return the ldev number for
stdin to break management.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Break management requested the User Interrupt
Table entry pointer in order to process
BREAK, but found it to be a NIL pointer.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Break management tried to interrupt a process
to handle subsystem_break or system_break and
found that it could not.
CAUSE
Internal error.
9
Error Messages
Break Handling
9
10
11
12
13
14
10
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Table management was unable to create the
User Interrupt Table for break management.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Table Management was unable to delete the
User Interrupt Table for break management.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Break management attempted to lock the User
Interrupt Table and was unable to.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Break management attempted to release the
lock on the User Interrupt Table and found it
could not.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Break management attempted to allocate an
entry in the User Interrupt Table and found
it could not.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Break management attempted to deallocate an
entry in the User Interrupt Table and found
it could not.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
Chapter 1
Error Messages
CIPER Devices
CIPER Devices
(CIPER)
1
MESSAGE
Ldev #\ not ready; check cable connections.
(CIPER 1)
2
MESSAGE
Ldev #\ has been powered up or reset. (CIPER
2)
3
MESSAGE
Ldev #\ has been placed off-line. (CIPER 3)
4
MESSAGE
Ldev #\ has been placed on-line. (CIPER 4)
5
MESSAGE
Ldev #\ reports out of paper; please check
and correct if necessary. (CIPER 5)
6
MESSAGE
Ldev #\ reports paper jam; please check and
correct if necessary. (CIPER 6)
7
MESSAGE
Ldev #\ reports platen open; please check and
correct if necessary. (CIPER 7)
8
MESSAGE
Ldev #\ reports ribbon error; please check
and correct if necessary. (CIPER 8)
9
MESSAGE
Ldev #\ experienced self-test failure.
Failure code = !. (CIPER 9)
10
MESSAGE
Ldev #\ reports protocol error: illegal
header length received. (CIPER 10)
11
MESSAGE
Ldev #\ reports protocol error: record
sequence error in record received. (CIPER 11)
12
MESSAGE
Ldev #\ reports protocol error: incorrect
creator of record received. (CIPER 12)
13
MESSAGE
Ldev #\ reports protocol error: undefined
command received. (CIPER 13)
14
MESSAGE
Ldev #\ reports protocol error: undefined
data type received. (CIPER 14)
15
MESSAGE
Ldev #\ reports protocol error: illegal
format number in environmental status block.
(CIPER 15)
17
MESSAGE
Ldev #\ reports protocol error: illegal block
label length received. (CIPER 17)
18
MESSAGE
Ldev #\ reports protocol error: transport
service error. (CIPER 18)
19
MESSAGE
Ldev #\ reports protocol error: data overrun
from host. (CIPER 19)
Chapter 1
11
Error Messages
CIPER Devices
20
MESSAGE
Ldev #\ reports data loss. (CIPER 20)
30
MESSAGE
CIPER ldev #\ is being shut down due to an
internal data integrity error. Access to
device will be denied until a WARMSTART is
performed. (CIPER 30)
12
Chapter 1
Error Messages
CIPER Device Manager
CIPER Device Manager
(Subsystem 127)
252
253
254
255
MESSAGE
The CIPER I/O MANAGER detected an internal
software error.
CAUSE
Internal error.
ACTION
Call your support representative.
MESSAGE
The CIPER I/O MANAGER was not able to release
an I/O MESSAGE frame.
CAUSE
Internal error.
ACTION
Call your support representative.
MESSAGE
The CIPER I/O MANAGER was not able to SEND an
I/O MESSAGE to another I/O MANAGER.
CAUSE
Internal error.
ACTION
Call your support representative.
MESSAGE
The CIPER I/O MANAGER was not able to obtain
an I/O MESSAGE frame.
CAUSE
Internal error.
ACTION
Call your support representative.
Clock/Timers Manager
(Subsystem 110)
2
3
11
Chapter 1
MESSAGE
GET_TIMER/GET_TIMER_IN_TICKS failed to get a
new timer entry from TABLE MANAGEMENT.
CAUSE
All timer entries have been allocated.
ACTION
Take a system dump.
MESSAGE
A soft interrupt occurred during wait for a
timeout.
CAUSE
Pause received status from extend_receive.
ACTION
Pause will retry the timer.
MESSAGE
The status of the timer entry is NOTIFICATION
13
Error Messages
Clock/Timers Manager
IN PROGRESS (doing SEND_MSG).
12
13
1002
1003
1010
1102
1103
1110
1202
14
CAUSE
Timer interrupt handler has already sent notification
message.
ACTION
None needed.
MESSAGE
The status of the timer entry is non-active.
CAUSE
Release of a timer which is dormant.
ACTION
None needed.
MESSAGE
A soft interrupt occurred during pause.
CAUSE
Pause received status from extend_receive.
ACTION
Pause will retry.
MESSAGE
PDC read time of day call returned with an
error; the option is nonexistent.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC read time of day call returned with an
error; the time of day is invalid.
CAUSE
Clock hardware uninitialized.
ACTION
Initialize hardware clock.
MESSAGE
PDC read time of day call returned with an
error; the parameter is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC set time of day call returned with an
error; the option is nonexistent.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC set time of day call returned with an
error; the time of day is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC set time of day call returned with an
error; the parameter is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC timer call (read calib. and acc.)
returned with an error; the option is
Chapter 1
Error Messages
Clock/Timers Manager
nonexistent.
1203
1210
2002
2003
2004
2005
2010
2102
Chapter 1
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC timer call (read calib. and acc.)
returned with an error; the time of day is
invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC timer call (read calib. and acc.)
returned with an error; the parameter is
invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC READ stable storage call returned with an
error; the option is nonexistent.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC READ stable storage call returned with an
error; can not complete call without error.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC READ stable storage call returned with an
error; the stable storage address is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC READ stable storage call returned with an
error; the stable storage contents are
invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC READ stable storage call returned with an
error; the parameter is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC WRITE stable storage call returned with
an error; the option is nonexistent.
CAUSE
Same as message content.
15
Error Messages
CM Debugger
2103
2104
2105
2110
ACTION
Take a system dump.
MESSAGE
PDC WRITE stable storage call returned with
an error; cannot complete call without error.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC WRITE stable storage call returned with
an error; the stable storage address is
invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC WRITE stable storage call returned with
an error; the stable storage contents are
invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
MESSAGE
PDC WRITE stable storage call returned with
an error; the parameter is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump.
CM Debugger
16
Chapter 1
Error Messages
(Subsystem 169)
(Subsystem 169)
25000
25001
25002
25003
25004
25005
25006
Chapter 1
MESSAGE
An internal error occurred in DEBUG/STACKDUMP
intrinsics.
CAUSE
An unexpected error was encountered while processing the
command/intrinsic.
ACTION
Retry the command/intrinsic. If the error persists, record
any error information that is printed and call your
Hewlett-Packard Representative.
MESSAGE
The address for the STATUS parameter is
invalid or inaccessable.
CAUSE
The status parameter references an undefined address or
an address to which the callers do not have write access.
ACTION
Make sure the variable was defined as a 4-byte value, and
make sure the pointer dereferences reference valid data.
MESSAGE
The address for the CMDSTR parameter is
invalid or inaccessible.
CAUSE
The command string parameter references an undefined
address or an address to which the callers do not have
write access.
ACTION
Make sure pointer dereferences reference valid data.
MESSAGE
No closing delimter was found in the CMDSTR
parameter.
CAUSE
The first and last characters in the command string are
not the same.
ACTION
Make sure the first and last characters are the same.
Furthermore, that character should not appear within the
body of the command string. Make sure the string of
characters is > = the maximum size allowed.
MESSAGE
The address for the FILENAME parameter is
invalid or inaccessible.
CAUSE
The file name parameter references an undefined address
or an address to which the callers do not have write access.
ACTION
Make sure pointer dereferences reference valid data.
MESSAGE
An error was encountered when closing the
file.
CAUSE
FCLOSE reported an error while trying to close the file.
ACTION
Ensure the caller has file CREATE/SAVE capabilities.
MESSAGE
An error was encountered when opening the
17
Error Messages
(Subsystem 169)
file.
25007
25008
25009
25010
25011
25012
18
CAUSE
FOPEN reported an error while trying to open the passed
file name. The file is exclusively opened for writing as a
FIXED, 132-byte, ASCII file with CCTL.
ACTION
Ensure that the indicated file does not already exist;
ensure there is free disk space; ensure the caller has file
CREATE/SAVE capabilities.
MESSAGE
The file number passed is invalid or
inaccessible.
CAUSE
The file number does not correspond to an opened file. The
file number corresponds to STDIN or one of the file
numbers reserved for use by MPE/iX.
ACTION
Make sure the file number corresponds to an opened file.
MESSAGE
The file has the incorrect record size.
CAUSE
The record size is not in the required range (for example,
from 64 to 512 bytes).
ACTION
Specify a file that has a valid record size. Remember to
check for file equations that may alter the value specified
in source code.
MESSAGE
The file type is binary; it must be ASCII.
CAUSE
The file system reported that the file was opened as a
binary file.
ACTION
Open the file as an ASCII file. Be sure to check for file
equations with the same name as the file being opened.
MESSAGE
Insufficient access rights; write access to
the file is required.
CAUSE
The file system reported that the caller did not have write
access to the file. Either the file was not opened for write
access, or the particular caller was not granted write
access to the file.
ACTION
Make sure the file was opened for write access. Be sure to
check for file equations with the same name as the file
being opened. You may have to change file and/or
group/account security or "release" the file.
MESSAGE
Missing or unknown keyvalue for HPDEBUG
keyword option.
CAUSE
An odd number of itemnum/item were passed. Each
itemnum must have a corresponding item.
ACTION
Check the calling code to ensure that each itemnum is
paired with an item.
MESSAGE
Unknown HPDEBUG keyword option selector.
Chapter 1
Error Messages
(Subsystem 169)
25020
25021
25022
25023
25024
Chapter 1
CAUSE
One of the itemnum selectors was not recognized as a
supported itemnum.
ACTION
Verify the use of correct itemnums. Make sure that the
itemnum/items are correctly paired.
MESSAGE
You must have PM capability to debug program
files with PM capability.
CAUSE
An attempt was made to enter DEBUG for a program that
was linked/prepped with PM capability by a user who does
not have PM capability.
ACTION
Link/prep the program without PM capability or grant the
user PM capability.
MESSAGE
You must have READ/WRITE access to a program
file to debug it.
CAUSE
An attempt was made to enter DEBUG for a program file
to which the user does not have write access. Write access
validation is performed by the file system.
ACTION
Alter the file and/or group/account security so that the
user has write access to the program file.
MESSAGE
DEBUG could not be initialized. The debugger
request has been ignored.
CAUSE
The internal DEBUG data structures could not be
allocated and/or initialized. This could be due to a lack of
disk space or a lack of some other system resources
(including DEBUGGER table space).
ACTION
Verify there is sufficient free disk space for virtual
memory. Wait for the machine to become less loaded and
try again. If the error persists, record any error
information that is printed and call your Hewlett-Packard
Representative.
MESSAGE
Could not capture process state. The debugger
request has been ignored.
CAUSE
DEBUG was unable to obtain all of the required
information about a process which is necessary to debug it.
ACTION
Retry the command/intrinsic. If the error persists, record
any error information that is printed and call your
Hewlett-Packard Representative.
MESSAGE
Unknown ESCAPE while entering DEBUG. The
debugger request has been ignored.
CAUSE
An unexpected error was detected by DEBUG while trying
to enter the main command processing code.
ACTION
Retry the command/intrinsic. If the error persists, record
any error information that is printed and call your
19
Error Messages
CM Emulator & OCT
Hewlett-Packard Representative.
CM Emulator & OCT
(Subsystem 188)
1
2
3
201
202
203
204
205
20
MESSAGE
The input node is too low. (CMNODES ERROR 1)
CAUSE
Bad input parameter.
ACTION
No harm done. Function returns false.
MESSAGE
The input node is too high. (CMNODES ERROR 2)
CAUSE
Bad input parameter.
ACTION
No harm done. Function returns false.
MESSAGE
Invalid node return from debug. (CMNODES
ERROR 3)
CAUSE
Bad input parameter.
ACTION
No harm done. Function returns false.
MESSAGE
The code segment loaded emulated because
translation is bad.
CAUSE
Bad translation.
ACTION
Retranslate with a good OCT.
MESSAGE
The code segment loaded emulated because
translation is bad.
CAUSE
Bad translation.
ACTION
Retranslate with a good OCT.
MESSAGE
The code segment loaded emulated because OCT
is for another system.
CAUSE
The system and OCT versions are not compatible.
ACTION
Retranslate with the appropriate OCT version.
MESSAGE
The code segment loaded emulated because
translation is bad.
CAUSE
Bad translation.
ACTION
Retranslate with a good OCT.
MESSAGE
The code segment loaded emulated because
FFILEINFO failed.
CAUSE
Unknown.
Chapter 1
Error Messages
CM Support Routines
ACTION
Call your Hewlett-Packard Representative.
501
MESSAGE
OCT error occurred.
502
MESSAGE
! is an invalid code segment name.
503
MESSAGE
! is an invalid code segment number.
504
MESSAGE
Failed to open file !.
505
MESSAGE
! is an invalid input file.
506
MESSAGE
! is an unknown argument name.
507
MESSAGE
Argument ! is specified in an invalid manner.
508
MESSAGE
Attempt to read beyond PB.
510
MESSAGE
PLABEL ! is out of bounds.
550
MESSAGE
OCT internal error occurred.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
551
MESSAGE
An error occurred executing CI command.
552
MESSAGE
Invalid addressing mode.
553
MESSAGE
Invalid data type on stack.
554
MESSAGE
Double operand missing HOLE-REG.
555
MESSAGE
The maximum register usage has been exceeded.
556
MESSAGE
An invalid register is specified.
557
MESSAGE
Trap entry was not made.
558
MESSAGE
Unable to decode CM instruction.
559
MESSAGE
A TEMP REG has been clobbered.
560
MESSAGE
Trap entry was made but not PUT.
561
MESSAGE
An undefined block label is specified.
562
MESSAGE
An unknown INST type was encountered.
563
MESSAGE
An invalid BRANCH target is specified.
CM Support Routines
(Subsystem 154)
10
Chapter 1
MESSAGE
The code segment number is invalid.
CAUSE
The caller passed in a code segment which is invalid for
21
Error Messages
CM Support Routines
the process whose PIN was passed in, or the code segment
is unassigned.
30
60
65
160
301
302
304
305
22
ACTION
None.
MESSAGE
The data segment number is invalid.
CAUSE
The caller passed in an invalid or an unassigned data
segment number.
ACTION
None.
MESSAGE
FREEZE returned a bad status.
CAUSE
The memory manager failed to freeze a compatibility mode
code or data segment into memory.
ACTION
Examine the process error stack to determine what may
have caused the problem.
MESSAGE
UNFREEZE returned a bad status.
CAUSE
The memory manager failed to unfreeze a compatibility
mode code or data segment into memory.
ACTION
Examine the process error stack to determine what may
have caused the problem.
MESSAGE
SWITCH_TO_CM returned a bad status.
CAUSE
Corruption of an operating system data structure or
operating system code caused SWITCH_TO_CM to fail.
ACTION
Examine the process error stack to determine what may
have caused the problem.
MESSAGE
The logical device parameter is not a real
device.
CAUSE
An attempt was made to place a non-existent device or a
spooler virtual device into diagnostic mode.
ACTION
None.
MESSAGE
The device is currently not in diagnostic
mode.
CAUSE
An attempt was made to remove a device not owned by the
diagnostic system from the diagnostic mode.
ACTION
None.
MESSAGE
The device is already in diagnostic mode.
CAUSE
An attempt was made to place a device which was already
owned by the diagnostic system into the diagnostic mode.
ACTION
None.
MESSAGE
The device is currently in use.
CAUSE
An attempt was made to place a device currently being
Chapter 1
Error Messages
CM Support Routines
accessed by a user into the diagnostic mode.
309
311
312
320
321
2550
2551
Chapter 1
ACTION
Try again once the user is no longer accessing the device.
The SHOWDEV command can be used to determine the
current owner.
MESSAGE
The spooler for the device could not be
stopped.
CAUSE
While attempting to place a device into the diagnostic
mode, the system could not stop the spooler active on the
device.
ACTION
Use the STOPSPOOL command to stop the spooler. If
sucessful, attemp the diagnostic again.
MESSAGE
The spooler for the device could not be
restarted.
CAUSE
While removing the device from the diagnostic mode, the
system could not restart a spooler for the device.
ACTION
If desired, use the STARTSPOOL command on the console
to start a spooler for the device.
MESSAGE
The spooler for the device could not be
suspended.
CAUSE
While attempting to place a device into diagnostic mode,
the system could not suspend the currently active
spoolfile.
ACTION
Try using the SUSPENDSPOOL command on the console
to suspend the currently active spoolfile.
MESSAGE
The logical console cannot be placed in
diagnostic mode.
CAUSE
An attempt was made to place the logical console into
diagnostic mode.
ACTION
Move the logical console to another terminal using the
CONSOLE command.
MESSAGE
Disks cannot be placed in diagnostic mode.
CAUSE
An attempt was made to place a disk into diagnostic mode.
ACTION
None.
MESSAGE
GETSIR returned a bad status to the fast
switch stub.
CAUSE
Corruption of an operating system data structure or
operating system code caused GETSIR to fail.
ACTION
Perform a system dump. Reboot the system using START.
MESSAGE
RELSIR returned a bad status to the fast
switch stub.
23
Error Messages
Debug Low Level Breakpoint Management
CAUSE
Corruption of an operating system data structure or
operating system code caused RELSIR to fail.
ACTION
Perform a system dump. Reboot the system using START.
Debug Low Level Breakpoint Management
(Subsystem 165)
5
10
15
20
25
30
24
MESSAGE
This is an invalid address or caller has
insufficient capabilities to access it.
CAUSE
The address validation routines detected an error while
checking the indicated address.
ACTION
Check the address. If invalid, pass a valid address.
Remember to make sure the space ID for long pointers is
correct. If additional capabilities are required, increase
caller capabilities or reduce protection on target address.
MESSAGE
This is an invalid BREAKPOINT INDEX; it is
out of range for valid BREAKPOINTS.
CAUSE
The breakpoint index is out of range of valid breakpoints.
ACTION
Provide a valid breakpoint index.
MESSAGE
The SINGLE STEP COUNT is invalid.
CAUSE
A negative single step value was passed.
ACTION
Provide a positive value.
MESSAGE
An NM BREAKPOINT (not in the DEBUG TABLE) is
at that address.
CAUSE
An NM breakpoint was found at the indicated address.
Since the breakpoint was not found in the system debug
tables, it must be a breakpoint from some other subsystem
or placed in the code by the programmer.
ACTION
Pick another location to set a DEBUG breakpoint since
DEBUG will not set a breakpoint on another breakpoint.
MESSAGE
The BREAKPOINT INDEX could not be found in
the BREAKPOINT TABLE.
CAUSE
The breakpoint index specified is not in the breakpoint
tables.
ACTION
List the current breakpoints and use an index of an
existing breakpoint.
MESSAGE
A BREAKPOINT already exists at the indicated
Chapter 1
Error Messages
Debug Low Level Breakpoint Management
address; can't set another.
35
40
45
50
55
Chapter 1
CAUSE
The caller tried to set an NM breakpoint where they had
already set one. Complete information about the
breakpoint existing at the location is returned in the INFO
parameter.
ACTION
Pick a different place to set the NM breakpoint. Delete the
existing breakpoint and then set the new one.
MESSAGE
The BREAKPOINT is owned by another process;
can't clear it.
CAUSE
The caller tried to delete an NM breakpoint which he did
not own.
ACTION
Specify an NM breakpoint which the caller set. Grant the
user PM capabilities so they may delete other people's
breakpoints.
MESSAGE
The DATA BUFFER is too small to hold the
indicated number of bytes.
CAUSE
The user requested a data transfer that is larger than the
size of the passed buffer.
ACTION
Increase the size of the buffer or request less data.
MESSAGE
A CM BREAKPOINT already exists at that
address (it's not in DEBUG TABLES!)
CAUSE
A CM breakpoint was found at the indicated address.
Since the breakpoint was not found in the system debug
tables, it must be a breakpoint from some other subsystem
or placed in the code by the programmer.
ACTION
Pick another location to set a DEBUG breakpoint since
DEBUG will not set a breakpoint on another breakpoint.
MESSAGE
The procedure could not find the CM
BREAKPOINT in the BREAKPOINT TABLE; can't
clear it.
CAUSE
The CM breakpoint index specified is not in the breakpoint
tables.
ACTION
List the current CM breakpoints and use an index of an
existing breakpoint.
MESSAGE
There is a BREAKPOINT already set there.
CAUSE
The caller tried to set a CM breakpoint where they had
already set one. Complete information about the
breakpoint existing at the location is returned in the INFO
parameter.
ACTION
Pick a different place to set the CM breakpoint. Delete the
existing breakpoint and then set the new one.
25
Error Messages
Debug Low Level Breakpoint Management
60
65
70
75
85
90
95
26
MESSAGE
The END ADDRESS is bigger than START, or SIDs
don't match in DATA BREAK ADDRESS.
CAUSE
The caller specified a range of address that cross a space
boundary or is not an ascending range.
ACTION
Specify a correct address range.
MESSAGE
The DATA BREAKPOINT INDEX could not be found
in the BREAKPOINT TABLE.
CAUSE
The DATA breakpoint index specified is not in the
breakpoint tables.
ACTION
List the current DATA breakpoints and use an index of an
existing breakpoint.
MESSAGE
A DATA BREAKPOINT already exists somewhere in
the specified range; can't ARM.
CAUSE
The caller tried to set a DATA breakpoint where they had
already set one. Complete information about the
breakpoint existing at the location is returned in the INFO
parameter.
ACTION
Pick a different place to set the DATA breakpoint. Delete
the existing breakpoint and then set the new one.
MESSAGE
The DATA BREAKPOINT is owned by another
process; can't clear it.
CAUSE
The caller tried to delete a data breakpoint which he did
not own.
ACTION
Specify a DATA breakpoint which the caller set. Grant the
user PM capabilities so they may delete other peoples'
breakpoints.
MESSAGE
The TARGET PIN is invalid or cannot be found
in the DEBUG TABLES.
CAUSE
The system breakpoint PIN SYS_BP_PIN was specified
and is invalid for the desired function. Specified PIN is not
being monitored by the caller. Specified PIN does not exist
at all in the debug tables.
ACTION
Provide a correct PIN number.
MESSAGE
The procedure could not find the PIN in
BREAKPOINT TABLE; can't ARM LOWER PRIV trap.
CAUSE
A process attempted to stop at a place for which it had
insufficient capabilities. An attempt was made to arm the
LOWER PRIV trap, stopping the process at the proper
time. The trap could not be armed.
ACTION
None.
MESSAGE
No STATE found for the indicated PIN; can't
Chapter 1
Error Messages
Debug Low Level Breakpoint Management
ARM the LOWER PRIV trap.
100
105
110
115
120
125
Chapter 1
CAUSE
A process attempted to stop at a place for which it had
insufficient capabilities. An attempt was made to arm the
LOWER PRIV trap, stopping the process. The trap could
not be armed.
ACTION
None.
MESSAGE
The maximum number of BREAKPOINTS for your
process has been reached.
CAUSE
Each debug user is allowed a maximum fixed number of
breakpoints. That limit has been reached for the calling
process.
ACTION
Delete some existing breakpoints.
MESSAGE
You are not a DEBUG user (see the
documentation
on how to use DEBUG routines).
CAUSE
The caller has not identified himself as a debug user by
calling the debug_user_setup routine.
ACTION
Call the debug_setup_user procedure.
MESSAGE
You are not monitoring that PIN; can't
REMOVE/DISARM event.
CAUSE
Probable cause is corruption of the internal debug tables.
ACTION
Kill all processes using DEBUG and retry the desired
operation. Reboot the system. Call your Hewlett-Packard
Representative if the problem persists.
MESSAGE
Your user must have PRIV capabilities for
this function.
CAUSE
A request to perform an operation which required the user
to hav PM capabilities was issued. Possibilities include:
writing register data is not allowed without PM; resuming
execution at a new location requires PM.
ACTION
Grant the user PM capability.
MESSAGE
You may not resume that PIN; someone else has
control over it.
CAUSE
Same as for Message Content.
ACTION
Provide a correct PIN number.
MESSAGE
DEBUG cannot be run on this system; DEBUG
system start up code failed.
CAUSE
Debug was not successfully initiated at system boot time.
It is not available.
ACTION
Reboot the system. If the problem persists, call your
27
Error Messages
Debug Low Level Breakpoint Management
Hewlett-Packard Representative.
130
135
140
145
150
155
160
28
MESSAGE
The procedure could not locate the DEBUGGER
GLOBAL DATA area.
CAUSE
DEBUG could not allocate storage to maintain its own
local data storage. This could be due to lack of disk space
for virtual memory.
ACTION
Verify that there is free virtual memory disk space.
MESSAGE
The actual INSTRUCTION for that address is
not in the BREAKPOINT TABLE.
CAUSE
The indicated address does not exist in the debug tables as
an address where an NM breakpoint is set.
ACTION
None.
MESSAGE
The PIN is not accessible to you (not a CHILD
or you don't have PRIV mode).
CAUSE
A PIN number was specified that is not a child of the
caller.
ACTION
Grant the caller PM capabilities. Use a PIN that is a child
of the caller.
MESSAGE
The procedure could not find the STATE
INFORMATION (ISM) for the indicated process.
CAUSE
An interrupt marker (ISM) for the indicated PIN could not
be found in the debug tables. The ISM is needed to alter a
process's register state and to arm the branch taken trap.
ACTION
Make sure you are using the correct PIN number.
MESSAGE
The procedure could not allocate the object
needed to store DEBUG GLOBAL DATA.
CAUSE
VSM returned a bad status from a create_object call made
while initializing the debugger.
ACTION
Make sure there is sufficient free disk space for virtual
memory.
MESSAGE
This is an invalid PIN number; it is out of
range for the valid PINS.
CAUSE
Same as message content.
ACTION
Provide a valid PIN.
MESSAGE
This address is inaccessible to you;
insufficient privilege or access rights.
CAUSE
The VSM "probe" routine returned an error status. This is
caused by an undefined address or an address to which the
caller does not have access.
Chapter 1
Error Messages
Debug Low Level Breakpoint Management
165
170
175
180
185
190
195
Chapter 1
ACTION
Make sure the address is valid.
MESSAGE
The PIN was not found in the DEBUG TABLES;
can't RESUME the process.
CAUSE
While trying to resume a process at a newly specified
address, the interrupt marker for the process could not be
located in the debug tables.
ACTION
Call the resume routine without specifying a new resume
address.
MESSAGE
The PIN is invalid; you may not specify your
own PIN.
CAUSE
The caller's PIN was specified as the target of the request
function.
ACTION
Specify a PIN other than your own.
MESSAGE
SINGLE STEPPING is currently controlled by
another PIN; can set SS counter.
CAUSE
An attempt was made to single step a process whose single
step counter is controlled by another process.
ACTION
Do not single step the process or try later when the
current owner of the single step counter is finished with it.
MESSAGE
The PIN was not found in the DEBUG TABLES;
can't set SS counter.
CAUSE
While attempting to single step a process, the process's
interrupt marker could not be found in the system debug
tables.
ACTION
None.
MESSAGE
The DEBUG TABLES are full; try again later.
CAUSE
The global system debug table is full.
ACTION
Wait for the number of debug users to decrease. Delete
breakpoints, turn off traps (all these free table space).
MESSAGE
The indicated PIN does not exist.
CAUSE
The indicated PIN did not exist when the request was
made.
ACTION
Specify a valid PIN.
MESSAGE
A compiler generated TRACE BREAKPOINT is
already set at that location.
CAUSE
While attempting to set an NM breakpoint, one of several
compiler-generated breakpoints was found at the
indicated address.
ACTION
Choose a different address at which to set the breakpoint.
29
Error Messages
Debug Low Level Breakpoint Management
Recompile the program without the option that caused the
special breakpoints to be inserted. Relink the program,
specifying the ";NODEBUG" option.
200
205
210
215
220
225
230
235
30
MESSAGE
The TARGET PIN is invalid for the specified
TRACE event.
CAUSE
The system breakpoint PIN was specified as the target of
the trace event request.
ACTION
Use a PIN other than the system breakpoint PIN.
MESSAGE
The TRACE event is currently owned by another
process; can't ARM it.
CAUSE
The caller tried to set a trace event that has already been
set.
ACTION
None.
MESSAGE
The TRACE event is currently owned by another
process; can't DISARM it.
CAUSE
The caller tried to disarm a trace event which he did not
own.
ACTION
Specify a trace event which the caller set. Grant the user
PM capabilities so they may disarm other peoples' trace
events.
MESSAGE
Invalid TRAP ID.
CAUSE
An unknown or unsupported trap ID was specified.
ACTION
Use a valid trap ID.
MESSAGE
The trap is not currently ARMED.
CAUSE
A request was made to disarm a trap that was not armed.
ACTION
Specify a trap that is armed.
MESSAGE
The PIN was not found in the DEBUG TABLES;
can't ARM the trap.
CAUSE
While attempting to arm a trap, the interrupt marker for
the specified process could not be found in the debug
tables.
ACTION
None.
MESSAGE
WARNING** The PIN was not found in the DEBUG
TABLES; can't clear T bit in PSW for PIN.
CAUSE
While attempting to disarm a trap, the interrupt marker
for the specified process could not be found in the debug
tables.
ACTION
None.
MESSAGE
This trap is currently owned by another
Chapter 1
Error Messages
Debug Low Level Breakpoint Management
process; can't ARM it.
240
245
250
255
260
Chapter 1
CAUSE
The caller tried to set a trace event that has already been
set.
ACTION
None.
MESSAGE
This trap is currently owned by another
process; can't DISARM it.
CAUSE
The caller tried to disarm a trace event which he did not
own.
ACTION
Specify a trace event which the caller set. Grant user PM
capabilities so they may disarm other peoples' trace
events.
MESSAGE
You cannot set BREAKPOINTS on GATE
instructions; sorry.
CAUSE
The address specified for an NM breakpoint corresponds to
a precision architecture gateway page. Breakpoints may
not be set on gateway pages.
ACTION
None.
MESSAGE
Dual BPs within the same node must have
identical count values.
CAUSE
Another CM breakpoint was set that has a corresponding
translated NM breakpoint which maps to the same NM
node point. In such situations, the breakpoint "COUNT"
must be identical.
ACTION
Provide the same COUNT value as the existing breakpoint
at the node point. Delete the existing breakpoint before
trying to set this one.
MESSAGE
Dual BPs within the same node must have
identical comment strings.
CAUSE
Another CM breakpoint was set that has a corresponding
translated NM breakpoint which maps to the same NM
node point. In such situations, the breakpoint COMMAND
STRING values must be identical.
ACTION
Provide the same COMMAND STRING value as the
existing breakpoint at the node point. Delete the existing
breakpoint before trying to set this one.
MESSAGE
An escape occurred while reading REGS from
the ISM.
CAUSE
While trying to read/write register values to an interrupt
marker, an expected error was detected. The result of the
operation is undefined.
ACTION
None.
31
Error Messages
Disk Free Space
265
270
275
280
MESSAGE
Accessing NL.PUB.STS requires that you are in
PRIV mode.
CAUSE
An attempt was made to access the system NL by a user
without PM capability.
ACTION
Grant the user PM capability.
MESSAGE
Accessing SL.PUB.SYS requires that you are in
PRIV mode.
CAUSE
An attempt was made to access the system SL by a user
without PM capability.
ACTION
Grant the user PM capability.
MESSAGE
The actual CM INSTRUCTION for that address is
not in the breakpoint table.
CAUSE
The indicated address does not exist in the debug tables as
an address where an CM breakpoint is set.
ACTION
None.
MESSAGE
A DATA BREAK TRP occurred which DEBUG did not
arm.
CAUSE
Someone else has set a trap bit on a page in the page table.
ACTION
None.
Disk Free Space
(DFSWARN)
1
MESSAGE
Disc free space map read error on LDEV !,
page !, I/O status !. (DFSWARN 1)
2
MESSAGE
Disc free space map write error on LDEV !,
page !, I/O status !. (DFSWARN 2)
3
MESSAGE
Disc free space check sum error on LDEV !,
page !. (DFSWARN 3)
4
MESSAGE
Physical mount error on LDEV !, error reading
disc free space map descriptor table, I/O
status !. (DFSWARN 4)
5
MESSAGE
Physical mount error on LDEV !, error writing
disc free space map descriptor table, I/O
status !. (DFSWARN 5)
6
MESSAGE
Physical mount error on LDEV !, error reading
defective tracks table, I/O status !.
32
Chapter 1
Error Messages
Disk Free Space
(DFSWARN 6)
7
MESSAGE
Physical mount error on LDEV !, no DST
entries available. (DFSWARN 7)
8
MESSAGE
Physical mount error on LDEV !, no virtual
memory available. (DFSWARN 8)
9
MESSAGE
Physical mount error on LDEV !, pack has not
been converted to new disc free space format.
(DFSWARN 9)
10
MESSAGE
Physical mount error on LDEV !, disc free
space map has previously been damaged.
(DFSWARN 10)
11
MESSAGE
Logical mount error on LDEV !, error reading
disc label, I/O status !. (DFSWARN 11)
12
MESSAGE
Logical mount error on LDEV !, error writing
disc label, I/O status !. (DFSWARN 12)
13
MESSAGE
Logical dismount error on LDEV !, error
reading disc label, I/O status !. (DFSWARN
13)
14
MESSAGE
Logical dismount error on LDEV !, error
writing disc label, I/O status !. (DFSWARN
14)
15
MESSAGE
Logical dismount error on LDEV !, error
writing disc free space map descriptor table,
I/O status !. (DFSWARN 15)
16
MESSAGE
Free space allocation/deallocation disabled
for pack on LDEV !. Files can still be
accessed, but they can not be built. (DFSWARN
16)
17
MESSAGE
Disc free space map on LDEV ! is damaged, DFS
status !. (DFSWARN 17)
18
MESSAGE
VINIT error on LDEV !. The disc free space
map for this disc is damaged. (DFSWARN 18)
19
MESSAGE
Unexpected disc free space error on LDEV !,
DFS status !, I.D. = !. (DFSWARN 19)
20
MESSAGE
Physical mount error on LDEV !, error reading
volume limit of disc, I/O status !. (DFSWARN
20)
21
MESSAGE
Physical mount error on LDEV !, error reading
disc label, I/O status !. (DFSWARN 21)
22
MESSAGE
Physical mount error on LDEV !, error writing
disc label, I/O status !. (DFSWARN 22)
Chapter 1
33
Error Messages
Disk Free Space
50
MESSAGE
Disc free space allocation disabled on ldev
!, because of a disc label read error.
(DFSWARN 50)
51
MESSAGE
Disc free space allocation disabled on ldev
!, because of a disc label write error.
(DFSWARN 51)
52
MESSAGE
Disc free space allocation disabled on ldev
!, because of a defective tracks table read
error. (DFSWARN 52)
53
MESSAGE
Disc free space allocation disabled on ldev
!, because the pack has an old format disc
free space table. There is a program to
convert it to the new format. (DFSWARN 53)
54
MESSAGE
Disc free space allocation disabled on ldev
!, because no DST entries where available at
the time it was mounted. (DFSWARN 54)
55
MESSAGE
Disc free space allocation disabled on ldev
!, because of a free space descriptor table
read error. (DFSWARN 55)
56
MESSAGE
Disc free space allocation disabled on ldev
!, because of a free space descriptor table
write error. (DFSWARN 56)
57
MESSAGE
Disc free space allocation disabled on ldev
!, because not enough virtual memory was
available at the time it was mounted.
(DFSWARN 57)
58
MESSAGE
Disc free space allocation disabled on ldev
!, because the map has been flagged as
damaged. (DFSWARN 58)
59
MESSAGE
Disc free space allocation disabled on ldev
!, because of trying to return space that was
already marked as free. The free space map
will be flagged as damaged. (DFSWARN 59)
60
MESSAGE
Disc free space allocation disabled on ldev
!, because of trying to get space that is not
free. The free space map will be flagged as
damaged. (DFSWARN 60)
61
MESSAGE
Disc free space allocation disabled on ldev
!, because of an unexpected free space
management error. (DFSWARN 61)
62
MESSAGE
Disc free space allocation disabled on ldev
!, because of a VINIT COND/RECOVER error.
(DFSWARN 62)
34
Chapter 1
Error Messages
Distributed Terminal Subsystems
Distributed Terminal Subsystems
(DTSERR)
This chapter contains validation and Datacomm Configurator (DCC) error messages.
Validation errors indicate problems with the network management configuration file. They
are detected during network management configuration file validation. DCC errors
indicate problems with the link or the DTS manager. They are detected when the host is
rebooted.
Validation Error Messages
The network management configuration file must be validated before it can be processed
by SYSGEN. The validation procedure is invoked in NMMGR by requesting it on the
VALIDATE CONFIGURATION FILE screen. Error messages will be displayed on the
system console. Additionally, error messages can be directed to a printer. The DTS
validation procedure starts by displaying the following on the system console:
197 - Validation of DTS/LINK started. Errors are then listed to the console. When the validation procedure is complete, it will
print the following on the system console:
nnn Encountered Errors
NOTE
After successful validation, run SYSGEN to cross-validate the DTS
configuration with the System configuration.
197 - Validation of DTS/LINK finished. where nnn is the total number of errors found during validation. Following is
a numerical list of validation error messages and actions for each.
1
MESSAGE
Path: NMMGRpath.
A read error encountered while reading the data
record (bad file). (DTSERR=1)
2
CAUSE
Either a hardware problem occurred or the data record is
too long.
ACTION
Try to print the network management configuration file.
Rebuild the file from a copy of the sample file
NMSAMP1.PUB.SYS. If the problem persists, contact your
Hewlett-Packard support representative.
MESSAGE
Path: NMMGRpath.
A write error encountered while updating the
data record (bad file). (DTSERR=2)
CAUSE
Chapter 1
Either a hardware problem occurred or the data record file
35
Error Messages
Distributed Terminal Subsystems
is too small.
3
ACTION
If the data record file has been compressed, it is impossible
to validate the file. Go to the UTILITY screen and use the
compression utility to make the file larger. Try to validate
the file. If it still fails, build the file from a copy of the
sample file NMSAMP1.PUB.SYS. If the problem persists
when verifying the new file, contact your Hewlett-Packard
support representative.
MESSAGE
Path: NMMGRpath
The data record is empty (use Update Data
function key). (DTSERR=3)
4
CAUSE
The data record was not created for the NMMGRpath.
ACTION
Go back to the screen specified by the NMMGRpath,
update the screen, and press Update Data.
MESSAGE
Path: NMMGRpath
The same physical path is being used at
LINK.linkname. (DTSERR=4)
5
CAUSE
The physical path specified for this link is being used.
ACTION
Go to the link screen specified by the NMMGRpath or go to
the link screen specified by the linkname, and modify the
physical path.
MESSAGE
Path: NMMGRpath
The same station address is being used at
LINK.linkname. (DTSERR=5)
6
CAUSE
The IEEE 802.3 station address is already used. Each
station address must be unique.
ACTION
Go back to the screen specified by the NMMGRpath or go
to the screen specified by the linkname and modify the
station address.
MESSAGE
Path: NMMGRpath
LINK.linkname is not defined. (DTSERR=6)
36
CAUSE
The link name specified on the DTS DATACOMM &
TERMINAL CONTROLLER CONFIGURATION screen is
not defined; therefore, the link data record was not
created.
ACTION
Verify the link name on the DTS DATACOMM &
TERMINAL CONTROLLER CONFIGURATION screen.
Check that the link name exists on the LINK
SELECTION screen and if it does, check that the link data
record was created. If the link data record does not exist,
update the LINK SELECTION screen and press Update
Chapter 1
Error Messages
Distributed Terminal Subsystems
Data.
7
MESSAGE
Path: NMMGRpath
DTS.PROFILE.linkname is not defined. (DTSERR=7)
8
CAUSE
The linkname on the screen specified by the NMMGRpath
is not defined; therefore, the profile data record does not
exist.
ACTION
Check that the profile name exists on the DISTRIBUTED
TERMINAL SUBSYSTEM PROFILE SELECTION screen
and if it does, check that the data record for this profile
was created. If the profile data record was not created,
then update the linkname screen and press Update Data.
MESSAGE
Path: NMMGRpath
The same station address or node name is being
used at DTS.DTC. SELECT.linkname. (DTSERR=8)
9
CAUSE
The station address or node name used on the screen
specified by the NMMGRpath is also used on the screen
specified by the DTS.DTC.SELECT.linkname screen.
ACTION
Go to the screen specified by the NMMGRpath or to the
screen specified by the linkname and modify the station
address or node name.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTC.SELECT.linkname.CARD012. (DTSERR=9)
10
CAUSE
The logical device (ldev) number is being used on the
screen specified by the NMMGRpath and on the
DTS.DTC.SELECT.linkname.CARD012 screen.
ACTION
Go to one of the two screens and change the ldev number.
The ldev number must be unique for each port.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTC.SELECT.linkname.CARD345. (DTSERR=10)
12
CAUSE
The same logical device (ldev) number is being used on the
screen specified by the NMMGRpath and on the
DTS.DTC.SELECT.linkname.CARD345 screen.
ACTION
Go to one of the two screens and change the ldev number.
The ldev number must be unique for each port.
MESSAGE
Path: NMMGRpath
LDEV #nnn is too big (must be ≤999). (DTSERR=12)
CAUSE
Chapter 1
The logical device (ldev) number is bigger than the allowed
maximum ldev number.
37
Error Messages
Distributed Terminal Subsystems
13
ACTION
Go to the screen specified by the NMMGRpath and modify
the ldev number.
MESSAGE
Path: NMMGRpath
Too many LDEVs are being used (must be ≤600).
(DTSERR=13)
15
CAUSE
Too many logical device (ldev) numbers are being used.
ACTION
Visit the screens that use ldevs and delete some ldev
numbers. The validation procedure allows a total of 600
ldevs.
MESSAGE
Path: NMMGRpath
Defined LINK. linkname is not being used.
(DTSWARN15)
16
CAUSE
The defined linkname is not used by DTS or the network
interface.
ACTION
This is a warning only. No action is required.
MESSAGE
Path: NMMGRpath
Too many links are being used (max. number
allowed = 8). (DTSERR=16)
17
CAUSE
The link specified in the NMMGRpath cannot be
processed. Too many links are already defined.
ACTION
Go back to the LINK SELECTION screen and delete the
link specified in the NMMGRpath. Delete all unused links
so that eight or less links are being used.
MESSAGE
Path: NMMGRpath
Too many paths are being used (max. number
allowed = 8). (DTSERR=17)
18
CAUSE
The link specified in the NMMGRpath cannot be
processed. Too many physical paths are already defined.
ACTION
Go back to the LINK SELECTION screen and delete the
link specified in the NMMGRpath. Delete all unused links
so that eight or less links are being used.
MESSAGE
Path: NMMGRpath
Too many DTCs are being used (max. number allowed
= 24). (DTSERR=18)
19
38
CAUSE
The DTC specified in the NMMGRpath cannot be
processed. Too many DTCs are already configured.
ACTION
Go back to the DTC SELECTION screen and delete the
DTC specified in the NMMGRpath.
MESSAGE
Path: NMMGRpath
Chapter 1
Error Messages
Distributed Terminal Subsystems
Too many nodes are being used (max. number
allowed = 33). (DTSERR=19)
20
CAUSE
The DTC specified in the NMMGRpath cannot be
processed. Too many nodes are being used.
ACTION
Go to the DTC SELECTION screen and delete the DTC
specified in the NMMGRpath.
MESSAGE
Path: NMMGRpath
Too many classes are being used (max. number
allowed = 450). (DTSERR=20)
21
CAUSE
The total number of classes exceeds the maximum allowed
number.
ACTION
Delete class names so that no more than 450 different
class names are associated with asynchronous devices.
MESSAGE
Path: NMMGRpath
Too many profiles are being used (max. number
allowed = 100). (DTSERR=21)
22
23
24
CAUSE
The total number of defined profiles exceeds the maximum
allowed.
ACTION
Delete profiles so that no more than 100 are specified.
MESSAGE
No link is defined. (DTSWARN=22)
CAUSE
A link is not configured.
ACTION
Without a configured link, the network management
configuration file is useless. Return to the configuration
screens and add a link, making sure that all necessary
data records are created.
MESSAGE
No DTC is defined. (DTSWARN=23)
CAUSE
A DTC is not configured.
ACTION
An action is not required if neither terminals, printers, nor
both are needed. If terminals and printers are required,
return to the configuration screens and add a DTC,
making sure that all necessary data records are created.
MESSAGE
Path: NMMGRpath
LINK.linkname is shared with network interface.
(DTSWARN=24)
Chapter 1
CAUSE
The same link is shared between the DTS and the NS
subsystem. A separate link must exist for each of the two
subsystems.
ACTION
Decide which of the two subsystems should use the
existing link and configure an additional link for the
remaining subsystem.
39
Error Messages
Distributed Terminal Subsystems
25
MESSAGE
Path: NMMGRpath
Modem type not supported. (DTSERR=25)
27
CAUSE
The modem type specified on the DTS TERMINAL
PROFILE screen is not 0, 1, or 2.
ACTION
Modify the modem type specified on the DTS TERMINAL
PROFILE screen to specify the appropriate modem type.
Press Update Data.
MESSAGE
Path: NMMGRpath
Must supply a physical path. (DTSERR=27)
28
CAUSE
A physical path was not specified in the Physical Path
IEEE 802.3 Device Adapter field.
ACTION
Go the IEEE 802.3 LINK CONFIGURATION screen and
enter the appropriate physical path. Press Update Data.
MESSAGE
Path: NMMGRpath
Duplicate profile class name linkname used.
(DTSWARN=28)
29
CAUSE
The same class name is used in a terminal profile or a
printer profile.
ACTION
Remove the duplicate class name from the printer profile
or the terminal profile.
MESSAGE
Path: NMMGRpath
Class name duplicated between printer and
terminal profiles. (DTSERR=29)
30
CAUSE
The same class name is used for both a terminal profile
and a printer profile.
ACTION
Remove the duplicate class name from the terminal profile
or the printer profile.
MESSAGE
Path: NMMGRpath
Profile specified for non-nailed terminals is of
printer-type. (DTSERR=30)
31
CAUSE
A printer profile is specified where only a terminal profile
is allowed.
ACTION
Change the printer profile to be a terminal profile.
MESSAGE
Path: NMMGRpath
Profile linkname specified for non-nailed PAD
terminals is of Printer-type. (DTSERR=31)
CAUSE
40
A printer profile is specified where only a terminal profile
is allowed.
Chapter 1
Error Messages
Distributed Terminal Subsystems
32
ACTION
Change the printer profile to be a terminal profile.
MESSAGE
Path: NMMGRpath
PAD device name for LDev #nnn is being used at
DTS.DTCPC.SELECT.linkname.CARD012.PAD0.
(DTSERR=32)
33
CAUSE
A PAD name is used more than once.
ACTION
Remove all of the duplicate references to the PAD name.
MESSAGE
Path: NMMGRpath
PAD device name for LDev #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD012.PAD1.
(DTSERR=33)
34
CAUSE
A PAD name is used more than once.
ACTION
Remove all of the duplicate references to the PAD name.
MESSAGE
Path: NMMGRpath
PAD device name for LDev #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD012.PAD2.
(DTSERR=34)
35
CAUSE
A PAD name is used more than once.
ACTION
Remove all of the duplicate references to the PAD name.
MESSAGE
Path: NMMGRpath
PAD device name for LDev #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.PAD3.
(DTSERR=35)
36
CAUSE
A PAD name is used more than once.
ACTION
Remove all of the duplicate references to the PAD name.
MESSAGE
Path: NMMGRpath
PAD device name for LDev #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.PAD4.
(DTSERR=36)
37
CAUSE
A PAD name is used more than once.
ACTION
Remove all of the duplicate references to the PAD name.
MESSAGE
Path: NMMGRpath
PAD device name for LDev #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.PAD5.
(DTSERR=37)
Chapter 1
CAUSE
A PAD name is used more than once.
ACTION
Remove all of the duplicate references to the PAD name.
41
Error Messages
Distributed Terminal Subsystems
38
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname.CARD 012.PAD0.
(DTSERR=38)
39
CAUSE
The same logical device (ldev) number is used more than
once.
ACTION
Remove the duplicate ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD012.PAD1.
(DTSERR=39)
40
CAUSE
The same logical device (ldev) number is used more than
once.
ACTION
Remove the duplicate ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD012.PAD2.
(DTSERR=40)
41
CAUSE
The same logical device (ldev) number is used more than
once.
ACTION
Remove the duplicate ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.PAD3.
(DTSERR=41)
42
CAUSE
The same logical device number (ldev) is used more than
once.
ACTION
Remove the duplicate ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.PAD4.
(DTSERR=42)
43
CAUSE
The same logical device (ldev) number is used more than
once.
ACTION
Remove the duplicate ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.PAD5.
(DTSERR=43)
42
Chapter 1
Error Messages
Distributed Terminal Subsystems
44
CAUSE
The same logical device (ldev) number is used more than
once.
ACTION
Remove duplicate ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD012.(DTSERR=44)
45
CAUSE
The logical device (ldev) number is used more than once in
the CARD012 configuration.
ACTION
Remove any duplicate references to the ldev number.
MESSAGE
Path: NMMGRpath
The same LDEV #nnn is being used at
DTS.DTCPC.SELECT.linkname .CARD345.(DTSERR=45)
46
CAUSE
The logical device (ldev) number is used more than once in
the CARD345 configuration.
ACTION
Remove any duplicate references to the ldev number.
MESSAGE
Path: NMMGRpath
The same node name is being used at linkname.
(DTSERR=46)
47
CAUSE
The same node name is used more than once.
ACTION
Remove the duplicate reference to the node name.
MESSAGE
Path: NMMGRpath
Blank node name. (DTSERR=47)
CAUSE
A host node name is not specified on the screen specified in
the path.
ACTION
Enter a host node name on the screen specified in the
path.
DCC Error Messages
As system start-up nears completion, the Datacomm Configurator (DCC) creates the LINK
and DTS managers. If the procedure is successful, the following message will be displayed
on the console:
DCC STARTUP - OK!
If the procedure is not successful, the message above is replaced by one or more error
messages. When looking up an error message, note that the following strings of characters
are used to represent information that is inserted when the message is generated:
• P-L is replaced by a DCC procedure number and DCC location number; used for
detailed diagnostics by Hewlett-Packard support representative.
• SSSSSSSS is replaced by an eight-digit hexadecimal value; also used for detailed
Chapter 1
43
Error Messages
Distributed Terminal Subsystems
diagnostics.
• MMM and LLL are replaced by decimal values; used for detailed diagnostics.
• PATH is replaced by an NMCONF path or LLIO physical path.
MESSAGE
DCC ERROR P-L, (LLIO status SSSSSSSS).
CAUSE
A problem exists with the low-level I/O services.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, (reply status SSSSSSSS, msg descriptors
MMM).
CAUSE
A problem exists with interprocess communication.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, Configuration file open error SSSSSSSS.
CAUSE
The configuration file does not exist or it is locked.
ACTION
Check to see if NMCONFIG.PUB.SYS exists. If it exists, verify that it is the
proper file type and that it is not locked.
MESSAGE
DCC ERROR P-L, (NMCONF record error SSSSSSSS). NM Path:
NMMGRpath
CAUSE
The DCC surrogate cannot read a record in NMCONFIG.PUB.SYS, or data
in the file was not validated or the data is corrupt.
ACTION
Validate the NMCONFIG.PUB.SYS file and reboot. If necessary, replace the
file, validate the file, and reboot the system.
MESSAGE
DCC ERROR P-L, configuration record data was invalid. NM
Path: NMMGRpath
CAUSE
Data in the NMCONFIG.PUB.SYS file was not validated or the data is
corrupt.
ACTION
Validate the NMCONFIG.PUB.SYS file and reboot the system.
MESSAGE
DCC ERROR P-L, (HLIO status SSSSSSSS, ldev LLL).
CAUSE
A problem exists with the high-level I/O services.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, (Buffer manager status SSSSSSSS).
CAUSE
A problem exists with the datacomm buffers.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, (External procedure not found).
CAUSE
A problem exists with DCC execution.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, (Memory management status SSSSSSSS).
CAUSE
A problem with the system occurred; the DCC cannot obtain memory.
44
Chapter 1
Error Messages
Distributed Terminal Subsystems
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, (Ports status SSSSSSSS).
CAUSE
A problem with the DCC or the port's subsystem occurred.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, time out on reply msg, descriptors MMM.
CAUSE
The DCC did not receive a reply message within the allotted time.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, too many DTCs configured.
CAUSE
The NMCONFIG.PUB.SYS file contains more than the supported number of
DTCs.
ACTION
Remove excess DTCs from the NMCONFIG.PUB.SYS file and reboot.
MESSAGE
DCC ERROR P-L, link name specified for the DTS does not
exist.
CAUSE
The link name configured in NMMGR on the DTS DATACOMM &
TERMINAL CONTROLLER CONFIGURATION screen does not match
that on the LINK SELECTION screen.
ACTION
Go the DTS DATACOMM & TERMINAL CONTROLLER
CONFIGURATION screen and enter the correct link name.
MESSAGE
DCC ERROR P-L, link name specified for the DTS is not
available.
CAUSE
A problem occurred with the link hardware; the LANIC might be in the
wrong slot or it might not be connected to the LAN.
ACTION
Check the hardware configuration connections.
MESSAGE
DCC ERROR P-L, too many links configured.
CAUSE
More that eight links are configured.
ACTION
Delete all unused links so that eight or less links are used.
MESSAGE
DCC ERROR P-L, message received on wrong subqueue.
CAUSE
A problem exists with the interprocess communication.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, unrecognized message received.
CAUSE
A problem exists with the interprocess communication.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, internal DCC logic error.
CAUSE
A problem internal to the DCC exists.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC ERROR P-L, Link error status.
Chapter 1
45
Error Messages
Distributed Terminal Subsystems
CAUSE
A problem occurred while configuring the link manager.
ACTION
Contact your Hewlett-Packard support representative.
MESSAGE
DCC WARNING P-L, Add Ldev to class failure (HLIO status
SSSSSSSS, ldev LLL).
CAUSE
A class contains more than 255 devices, or a conflict in class names exists.
ACTION
Run SYSGEN to verify the conflict.
MESSAGE
DCC ERROR P-L, Configuration file close error SSSSSSSS.
CAUSE
A problem occurred while closing the NMCONFIG.PUB.SYS file or the
NMCONFIX.PUB.SYS file.
ACTION
Check that the files exist, and that adequate disk space is available for
them. If the files exist and the disk space is large enough, check for file
system or hardware problems.
MESSAGE
WARNING: I/O config from last START NORECOVERY will be
used. (DCCWARN 100)
CAUSE
A routine message; this indicates that a start recovery is being attempted.
ACTION
No action is required.
MESSAGE
DCC WARNING P-L, (Startup) cannot open NMCONFIG, status
SSSSSSSS.
CAUSE
Cannot open the NMCONFIG.PUB.SYS file.
ACTION
Check that the file exists and that it is not locked. If the file exists and is
not locked, check for file system or hardware problems.
MESSAGE
DCC WARNING P-L, (Startup) cannot purge NMCONFIX, status
SSSSSSSS.
CAUSE
The NMCONFIX.PUB.SYS file cannot be purged.
ACTION
Check that the file exists. If the file exists, check for file system or
hardware problems.
MESSAGE
DCC WARNING P-L, (Startup) cannot open NMCONFIX, status
SSSSSSSS.
CAUSE
The NMCONFIX.PUB.SYS file exists but it cannot be opened.
ACTION
Check that the file is not locked. If the file is not locked, check for file
system or hardware problems.
MESSAGE
DCC WARNING P-L, (Startup) cannot create NMCONFIX, status
SSSSSSSS.
CAUSE
A disk space problem, a file system problem, or a hardware problem exists.
ACTION
Verify that enough disk space is available. If enough disk space is
available, verify that no the file system problems exist. Then, verify that
no hardware problems exist.
MESSAGE
DCC WARNING P-L , (Startup) cannot copy record from
46
Chapter 1
Error Messages
Distributed Terminal Subsystems
NMCONFIX, status SSSSSSSS.
CAUSE
The NMCONFIX.PUB.SYS does not exist, or a file system or hardware
problem exists.
ACTION
Check that the NMCONFIX.PUB.SYS file exists. If it does not, restore it. If
the file exists, check for file system or hardware problems.
MESSAGE
DCC WARNING P-L, (Startup) cannot copy record to NMCONFIG,
status SSSSSSSS.
CAUSE
The NMCONFIG.PUB.SYS file does not exist, or a file system or hardware
problem exists.
ACTION
If the file does not exist, create it. If the file exists, check for file system or
hardware problems.
MESSAGE
DCC WARNING P-L, (Startup) cannot close NMCONFIG, status
SSSSSSSS.
CAUSE
The NMCONFIG.PUB.SYS file does not exist, or a disk space, a file system,
or hardware problem exists.
ACTION
Check that the NMCONFIG.PUB.SYS file exists. If it does not exist, restore
it. If the file exists, check for a disk space problem, a file system problem,
or a hardware problem.
MESSAGE
DCC WARNING P-L, (Startup) cannot close NMCONFIX, status
SSSSSSSS.
CAUSE
The NMCONFIX.PUB.SYS file does not exist, or a disk space, file system, or
hardware problem exists.
ACTION
Check that the NMCONFIX.PUB.SYS exists. If it does not exist, restore it. If
the file exists, check for a file system problem or a hardware problem.
MESSAGE
DCC ERROR P-L, Blank NODENAME.
CAUSE
A host node name was not configured.
ACTION
Configure a host node name.
MESSAGE
DCC ERROR P-L, Configuration file not validated.
CAUSE
Either modifications were made to the network management configuration
file and the file was not validated, or the file was validated but the errors
listed to the console were not corrected.
ACTION
Either validate the network management configuration file, or correct the
errors listed to the console when the file was first validated. Then
revalidate the file. The host will be rebooted.
Chapter 1
47
Error Messages
Distributed Terminal Subsystems
48
Chapter 1
2 Error Messages Viii C 2
File System Label Management
(Subsystem 153)
1
2
3
4
5
MESSAGE
An internal offset is not valid because it is
either less than the minimum or greater than
the maximum possible offset for the
designated label table.
CAUSE
A file corruption occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The offset component of the specified UFID is
invalid. It does not match the offset stored
in the file label assigned with the specified
UFID. The file label offset component is
probably corrupted.
CAUSE
A file corruption occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The time stamp components of the UFID do not
match the time stamp components stored in the
file label for the associated UFID.
CAUSE
A file corruption has occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The count of the number of descriptors in the
extent block exceeds the maximum possible
value.
CAUSE
A file corruption has occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The PARENT_LABEL_OFFSET field of the extent
or label extension block does not equal the
49
Error Messages Viii C 2
File System Label Management
offset of the parent file label to which this
block is linked.
6
7
8
9
10
50
CAUSE
A file corruption has occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The pointer to the first free extent block on
the extent free list is either greater than
the maximum or less than the minimum possible
offset for the designated label table.
CAUSE
A file corruption has occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The starting sector offset passed to the
Label Management mount routines does not
match that which is stored in the label
table's header.
CAUSE
A file corruption has occurred.
ACTION
Call Hewlett-Packard and notify your representative that
a possible file corruption has occurred.
MESSAGE
The file sector offset of the first extent of
the designated label table is not equal to
zero. This value is stored in the first
extent descriptor in the extent trap for the
label table itself.
CAUSE
The label table has been corrupted. START will fail, with
label management error displaying on the console.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The disk sector address field for the first
extent of the label table does not equal the
address passed to the label table mount
routines.
CAUSE
The label table has been corrupted. START will fail, with
label management error displaying on the console.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
There are no more magic extent block or label
extension blocks. The free pool has been
exhausted.
CAUSE
The system tried to allocate more magic extent blocks than
the label table has reserved. START will fail, with label
management error displaying on the console.
ACTION
Call your Hewlett-Packard Representative.
Chapter 2
Error Messages Viii C 2
File System Label Management
11
12
13
14
15
16
17
Chapter 2
MESSAGE
The internal timer field of the UFID does not
match the internal timer field stored in the
actual label for the associated UFID.
CAUSE
File corruption has occurred. LISTF will fail, with bad
UFID displaying on the console.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal change has been made and the size
of a label table entry no longer equals the
size of a table management entry.
CAUSE
An internal change has been made and the size of the label
table entry no longer equals the size of the table
management entry. The INSTALL of the system will fail.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The number of extent fields in the extent
block is out of range.
CAUSE
File corruption has occurred.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The requested magic file label has not yet
been allocated.
CAUSE
A requested magic file label has not yet been allocated.
START will fail, with a label management error displaying
on the console.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Label management was trying to allocate an
entry which is not marked as free.
CAUSE
label management was trying to allocate an entry which is
not marked as free.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The specified label extension category is
undefined. There are three defined extension
categories (sm;tm;ii), and a request has been
made to access an undefined category.
CAUSE
A request has been made to access an unidentified
category.
ACTION
The error status will be sent to the caller.
MESSAGE
An attempt has been made to access an
unallocated file label extension category.
The category is defined but the extension for
the specified file label has not yet been
allocated.
51
Error Messages Viii C 2
File System Label Management
18
19
20
21
22
23
24
52
CAUSE
A request has been made to access a file label extension
which is undefined.
ACTION
The error status will be sent to the caller.
MESSAGE
An attempt has been made to read beyond the
end of the file label extension for the
specified file label.
CAUSE
Read beyond the limit of the file label extension.
ACTION
The error status will be sent to the caller.
MESSAGE
The entry defined by the offset component of
the specified UFID is not marked as a file
label.
CAUSE
The entry defined by the offset in the UFID is not a file
label.
ACTION
The error status will be sent to the caller.
MESSAGE
The first extent block on the extent block
free list is not marked as a free extent
block.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The currently selected extent block for the
file identified by the UFID is not marked as
an allocated extent block but is being used
as such.
CAUSE
The extent block being accessed is not an allocated entry.
ACTION
The error status will be sent to the caller.
MESSAGE
The link field of the current extent block
does not point to an extent block that
belongs to the specified file label.
CAUSE
Same as message content.
ACTION
The error status will be sent to the caller.
MESSAGE
An extent with the same starting file sector
offset already exists.
CAUSE
File corruption.
ACTION
Abort the system and call your Hewlett-Packard
Representative.
MESSAGE
There exists an extent descriptor for this
file label that defines an extent that is not
page aligned.
CAUSE
Same as message content.
Chapter 2
Error Messages Viii C 2
File System Storage Management
25
26
27
28
29
ACTION
The error status will be sent to the caller. Call your
Hewlett-Packard Representative.
MESSAGE
There exists an extent descriptor for this
file label that defines an extent that is not
a multiple of a page size.
CAUSE
Same as message content.
ACTION
The error status will be sent to the caller.
MESSAGE
There exists an extent descriptor for this
file label that defines an extent that is not
within the defined limits of the file.
CAUSE
File corruption.
ACTION
The error status will be sent to the caller.
MESSAGE
There exists an extent descriptor for this
file label that defines an extent for which
no or partial secondary shortage is
allocated.
CAUSE
File corruption.
ACTION
The error status will be sent to the caller.
MESSAGE
The version of this label table is invalid or
incompatible with the current version of the
software.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
There exists an extent block linked to this
file label identified by the UFID that is
marked as a free entry but is not being used
as such.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
File System Storage Management
(Subsystem 185)
10
Chapter 2
MESSAGE
The procedure could not create a new file
label.
CAUSE
LM_ALLOC_LABEL returned bad status.
53
Error Messages Viii C 2
File System Storage Management
20
30
40
50
60
70
100
54
ACTION
Check the status returned from LM_ALLOC_LABEL and
call your Hewlett-Packard Representative.
MESSAGE
The new file size is greater than the
available disk space.
CAUSE
LM_ADD_EXTENT_DESCRIPTION returned bad status.
ACTION
Free some disk space and try again.
MESSAGE
The new file size is greater than the
available disk space.
CAUSE
ALLOCATE_SEC_STORAGE failed or accounting denied
disk request.
ACTION
Reduce requested file size or add on more disk space.
MESSAGE
The PAGE ALLOCATION request for a new file is
negative.
CAUSE
Bad parameter value (INIT_ALLOC_PAGE) passed to
SM_CREATE.
ACTION
Fix source and recompile if running user code..
MESSAGE
Initial page request exceeds file size.
CAUSE
Bad parameter passed to SM_CREATE.
ACTION
Fix source and recompile if running user code.
MESSAGE
Volume Management refused file open request.
CAUSE
VLM_INCR_OPEN_COUNT returned bad status. Possible
security violation.
ACTION
Examine the status returned from
VLM_INCR_OPEN_COUNT.
MESSAGE
Volume Management refused request to close a
file.
CAUSE
VLM_DECR_OPEN_COUNT returned bad status. Storage
management attempted to decrement the file open count
but it was already 0. Possible security violation. Possible
full KSAM file.
ACTION
Examine the status returned from
VLM_DECR_OPEN_COUNT. Check for possible security
violations. If you're using a KSAM file, verify that it is not
full. If it is, increase its size and try operation again.
MESSAGE
Missing FILE LABEL occurred during FILE OPEN.
CAUSE
LM_GET_FILE_LABEL_PTR returned bad status.
ACTION
Check the status returned from
LM_GET_FILE_LABEL_PTR. If corrupt, call your
Hewlett-Packard Representative.
Chapter 2
Error Messages Viii C 2
File System Storage Management
110
200
220
230
250
260
292
296
310
Chapter 2
MESSAGE
VSM failed to ALLOCATE a new file descriptor.
CAUSE
VSM_ALLOCATE_GU_FD failed. Table may be full.
ACTION
Examine the status returned from
VSM_ALLOCATE_GU_FD. Retry program; GU_FD table
entries will be made available dynamically.
MESSAGE
The GLOBAL FILE POINTER was not initialized.
CAUSE
Caller did not set parameter value correctly.
ACTION
Recode and recompile user program.
MESSAGE
Illegal protection request during FILE OPEN.
CAUSE
File is currently open and protected by an incompatible
protection scheme.
ACTION
Close the file or change access to match the one currently
being used or alter file security.
MESSAGE
New user requests incompatible access methods
during FILE_OPEN.
CAUSE
Another user has opened the file with a different PID
protection mechanism or with incompatible access rights.
ACTION
Alter the open method to include compatible access rights
or wait until all other users have closed the file.
MESSAGE
VSM was unable to MAP requested file to
memory.
CAUSE
VSM_MAP_IN_FILE failed. Possible memory contention.
ACTION
Examine the status returned from VSM_MAP_IN_FILE.
MESSAGE
VSM could not remove file from memory.
CAUSE
File is currently open with incompatible access methods or
SM_MAP_OUT_FILE returned bad status.
ACTION
Examine error stack to find original source of error.
MESSAGE
The file size exceeds the MAP-IN limit.
CAUSE
Size of the file is greater than maximum size of SR6/SR7
space.
ACTION
Reduce the file size.
MESSAGE
MAP-IN failed because of a bad volume ID.
CAUSE
VSM_MAP_IN_FILE failed.
ACTION
Examine the status returned from VSM_MAP_IN_FILE
and compare the value with the volume ID.
MESSAGE
STMGT received a READ/WRITE request for an
unopened file.
55
Error Messages Viii C 2
File System Storage Management
320
340
350
360
370
514
600
650
56
CAUSE
GUFD entry was not found in the hash table.
ACTION
Recode source to open file before reading/writing.
MESSAGE
On file close, a negative EOF value was
found.
CAUSE
Unknown at this time.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
MEMMGT failed to POST data from memory to
disk.
CAUSE
The call to POST returned bad status.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The root node (accounting) could not be
closed.
CAUSE
SM_CLOSE returned bad status. Another process may be
accessing the root node.
ACTION
Examine the status from SM_CLOSE.
MESSAGE
The procedure could not CLOSE account node.
CAUSE
SM_CLOSE failed. Another process may be accessing the
root node.
ACTION
Examine the status returned from SM_CLOSE.
MESSAGE
The procedure could not CLOSE group node.
CAUSE
SM_CLOSE failed.
ACTION
Examine the status returned from SM_CLOSE and call
your Hewlett-Packard Representative.
MESSAGE
A Pascal recover block was entered
unexpectedly.
CAUSE
Cause is usually associated with software or hardware
traps which have been tripped because of invalid
addresses, invalid access rights, or arithmetic
underflow/overflow.
ACTION
Take a system dump and call your Hewlett-Packard
Service Representative.
MESSAGE
An unknown option was passed to SM_CNTL.
CAUSE
Bad parameter.
ACTION
Review the source of the program.
MESSAGE
Label Management failed to update the EOF.
CAUSE
The request to start or restart a transaction failed.
ACTION
Examine the status returned from LM_START_WRITE
Chapter 2
Error Messages Viii C 2
File System Storage Management
and call your Hewlett-Packard Representative..
660
670
680
700
750
760
800
850
Chapter 2
MESSAGE
Label Management failed to update the EOF.
CAUSE
The request to finish a transaction failed.
ACTION
Examine the status returned from LM_FINISH_WRITE
and call your Hewlett-Packard Representative.
MESSAGE
The EOF could not be updated in the Label
Table.
CAUSE
XM_END_SYSTEM_TRANS failed.
ACTION
Examine the status from XM_END_SYSTEM_TRANS and
call your Hewlett-Packard Representative.
MESSAGE
After EOF expansion, the virgin area of the
file could not be filled on disk.
CAUSE
VSM_FILL_DISK_VIRGIN failed.
ACTION
Examine the status returned from
VSM_FILL_DISK_VIRGIN and call your Hewlett-Packard
Representative.
MESSAGE
The file's actual disk requirement could not
be determined.
CAUSE
GET_OBJECT_ATTRIBUTE failed.
ACTION
Examine return status from GET_OBJECT_ATTRIBUTE
and call your Hewlett-Packard Representative.
MESSAGE
The available disk space is less than the
amount requested.
CAUSE
The prefetch failed or an attempt to move data to disk
escaped because of insufficient disk space.
ACTION
Generate new disk space.
MESSAGE
A prefetch request failed.
CAUSE
A call to prefetch failed.
ACTION
Examine the status from prefetch to determine why it
failed.
MESSAGE
No file descriptors exist on the closed file
list.
CAUSE
Number of open files is exactly the same as available file
descriptors.
ACTION
Expand the VSOD table.
MESSAGE
An XM file could not be mapped from memory to
disk.
CAUSE
Call to XM_POST_FILE_FOR_MAP_OUT failed.
57
Error Messages Viii C 2
Floating Point Conversion
860
900
ACTION
Examine the status returned from
XM_POST_FILE_FOR_MAP_OUT and if necessary, add
more secondary storage.
MESSAGE
VSM failed to map file from memory to disk.
CAUSE
VSM_MAP_OUT_FILE failed.
ACTION
Examine the status returned from
VSM_MAP_OUT_FILE.
MESSAGE
The label table has a negative EOF.
CAUSE
Label management requested a negative EOF during
SM_MAP_LABEL.
ACTION
Fix the source to pass a positive EOF.
Floating Point Conversion
(Subsystem 193)
1
3
5
8
101
58
MESSAGE
Inexact exception in a floating point
conversion. (HPFPCONVERT WARNING 1)
CAUSE
Exact representation is not possible in the specified IEEE
destination format.
ACTION
None.
MESSAGE
Underflow exception in a floating point
conversion. (HPFPCONVERT WARNING 3)
CAUSE
Result magnitude is too small for the destination format.
ACTION
Consider other destination formats and/or rounding mode.
MESSAGE
Overflow result in a floating point
conversion. (HPFPCONVERT WARNING 5)
CAUSE
Result magnitude is too large for the destination format.
ACTION
Consider other destination formats and/or rounding mode.
MESSAGE
Invalid operation exception. (HPFPCONVERT
WARNING 8)
CAUSE
The input NaN cannot be represented in the destination
format.
ACTION
Program around the attempted conversion or correct the
bad data.
MESSAGE
Invalid source format. (HPFPCONVERT ERROR
101)
Chapter 2
Error Messages Viii C 2
Floating Point Conversion
102
104
105
106
Chapter 2
CAUSE
The source format value is not between 1 and 5.
ACTION
Use valid numbers (shortint 1 through 5): 1 = cm32, 2 =
cm64, 3 = nm32, 4 = nm64, 5 = nm128
MESSAGE
Invalid destination format. (HPFPCONVERT
ERROR 102)
CAUSE
The destination format value is not between 1 and 5.
ACTION
Use valid numbers (shortint 1 through 5): 1 = cm32, 2 =
cm64, 3 = nm32, 4 = nm64, 5 = nm128
MESSAGE
Invalid rounding mode. (HPFPCONVERT ERROR
104)
CAUSE
The rounding mode value is not between 0 and 3.
ACTION
Use valid numbers: 0 = round to nearest, 1 = round toward
zero, 2 = round toward + infinity, 3 = round toward infinity
MESSAGE
CM to NM switch error. (HPFPCONVERT ERROR
105)
CAUSE
Input parameters are incomplete or invalid.
ACTION
Use valid input parameters.
MESSAGE
CM parameter(s) missing. (HPFPCONVERT ERROR
106)
CAUSE
Parameters incomplete or invalid.
ACTION
Use all valid required parameters.
59
Error Messages Viii C 2
High Level I/O
High Level I/O
(Subsystem 111)
1
2
3
4
5
6
7
8
9
60
MESSAGE
The I/O request was aborted.
CAUSE
Many possible causes.
ACTION
This is a warning message and not a standard error
condition. Therefore, no additional action is required.
MESSAGE
The I/O request is currently active.
CAUSE
Same as message content.
ACTION
This is a warning message and not a standard error
condition. Therefore, no additional action is required.
MESSAGE
The request is currently queued in the
manager's input queue.
CAUSE
Same as message content.
ACTION
This is a warning message and not a standard error
condition. Therefore, no additional action is required.
MESSAGE
The LDEV specified was invalid.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The LDEV specified was not configured.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A bad virtual address or nil pointer was
specified.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The length specified was negative, or the
total length in the user data chain did not
add up to length.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The sector specified was zero.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The function specified was invalid for this
Chapter 2
Error Messages Viii C 2
High Level I/O
device.
10
11
13
14
15
17
18
19
20
Chapter 2
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The message was not found in the input queue.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The subqueue specified is used by the I/O
system.
CAUSE
Same as for message Content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The I/O completion port must be ICS-sendable.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The I/O completion port must be able to
handle the largest HLIO message.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The I/O completion port must have 32
subqueues.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The procedure can not be called from the ICS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The device is in a disabled state, and I/O
may not be performed to it.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The data chain passed to SENDIO had unaligned
data.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The I/O request has generated more than the
maximum of 32 data chains.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
61
Error Messages Viii C 2
High Level I/O
21
MESSAGE
The I/O request index supplied was outside
the range of the table. CAUSE
Internal error. ACTION
Call your Hewlett-Packard Representative.
22
MESSAGE
The RENDEZVOUS for the I/O request has
already been done. CAUSE
Internal error. ACTION
Call your Hewlett-Packard Representative.
24
25
26
27
28
29
30
31
62
MESSAGE
A message was received by the LDM that was
not understood.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A request to release the device was issued
while the device was still allocated.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A die request was sent to the LDM, but the LDM
is still bound to DM.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A request to release the device was issued
while I/O was still active.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The LDM is bound to a different DM than
specified in the LDM_DO_UNBIND_MSG.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The request failed because we were out of
resources.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The function requested is not implemented.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
There are currently no outstanding requests
Chapter 2
Error Messages Viii C 2
High Level I/O
for the device.
32
33
34
35
36
37
38
Chapter 2
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The device class is invalid.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The COMPATIBILITY MODE I/O queue index is
invalid.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
There is a flow control problem in the LDM.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
There is a flow control problem in the LDM.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The procedure failed to make the user's
buffer present.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The request to abort a MIB chain has found an
already aborted MIB.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An HLIO internal error was detected.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
63
Error Messages Viii C 2
HPIB Adapter Manager
HPIB Adapter Manager
(Subsystem 116)
1
MESSAGE
The READ transaction was terminated by END or
IDENTIFY (EOI) with an even number of bytes
transferred.
2
MESSAGE
The READ transaction was terminated by END or
IDENTIFY (EOI) with an odd number of bytes
transferred.
3
MESSAGE
The READ transaction was terminated by COUNT;
the COUNT was even.
4
MESSAGE
The READ transaction was terminated by COUNT;
the COUNT was odd.
5
MESSAGE
The READ transaction was terminated by
LINE-FEED; the COUNT was even.
6
MESSAGE
The READ transaction was terminated by
LINE-FEED; the COUNT was odd.
7
MESSAGE
The READ transaction was terminated by
SECONDARY ADDRESS; the COUNT was even.
8
MESSAGE
The READ transaction was terminated by the
SECONDARY ADDRESS; the COUNT was odd.
9
MESSAGE
The transaction was terminated by the host;
the data transfer to host was terminated by
Channel END (CEND) instead of Device END
(DEND).
10
MESSAGE
The HPIB DAM has detected a time-out when
identifying a device.
129
MESSAGE
The HPIB DAM has received an unknown TSTATUS.
137
MESSAGE
The HPIB DAM has detected an error in its
internal REQ_INFO_ENTRY; an entry is
currently in use.
138
MESSAGE
The HPIB DAM has detected an error in its
internal REQ_INFO entry; an incorrect user ID
is detected.
139
MESSAGE
The HPIB DAM has detected an error in its
internal RS_BLOCK; an incorrect use of
RS_BLOCK_PTR.
140
MESSAGE
The HPIB DAM has detected an error in its
internal RS_BLOCK; an entry of RS_BLOCK is
64
Chapter 2
Error Messages Viii C 2
HPIB Adapter Manager
currently in use.
141
MESSAGE
The HPIB DAM has detected an error in its
internal RS_BLOCK; an entry with incorrect
use of user ID.
142
MESSAGE
The HPIB DAM has detected no internal user ID
available.
143
MESSAGE
The HPIB DAM has detected its internal
REQ_INFO TABLE integrity error.
144
MESSAGE
The HPIB DAM has detected an error in its
internal DM_TABLE; table integrity error.
145
MESSAGE
The HPIB DAM has detected an error in its
internal DAM_TABLE; table integrity error.
146
MESSAGE
The HPIB DAM has detected internal fatal
software error.
154
MESSAGE
The HPIB device adapter has detected a
timeout during a detailed report phase; it
can be either in command, execution, or
report phase. The device adapter also
detected a second timeout while trying to
send UNTALK or UNLISTEN commands.
155
MESSAGE
The HPIB device adapter has detected a
timeout during a detailed report phase; it
can be either in command, execution, or
report phase. The device adapter is also no
longer a CONTROLLER-IN-CHARGE (CIC).
156
MESSAGE
The HPIB device adapter has detected a
timeout during a detailed report; it can
occur either in command, execution, or report
phase.
157
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 reporting phase, and it
also has detected a second timeout while
trying to send UNTALK or UNLISTEN commands.
158
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 reporting phase, and it
is no longer a CONTROLLER-IN-CHARGE (CIC).
159
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 reporting phase.
160
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 execution phase, and it
has also detected a second timeout while
trying to send UNTALK or UNLISTEN commands.
Chapter 2
65
Error Messages Viii C 2
HPIB Adapter Manager
161
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 execution phase, and
the device adapter is no longer a
CONTROLLER-IN-CHARGE (CIC).
162
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 execution phase.
163
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 command phase, and it
has also detected a second timeout while
trying to send UNTALK or UNLISTEN commands.
164
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 command phase, and it
is no longer a CONTROLLER-IN-CHARGE (CIC).
165
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 command phase.
166
MESSAGE
The HPIB device adapter has detected that the
data portion of the CS80 request block was
missing from the request phase.
192
MESSAGE
The HPIB device adapter has detected a
timeout during a CS80 execution phase.
205
MESSAGE
The HPIB device adapter has been set to a
different block size transferred. The block
size has to be reset first before setting to
a desired value. Other device(s) may be doing
the block size transferred.
206
MESSAGE
The HPIB DAM has currently exceeded the
maximum number of the concurrent I/O
transactions. It can only support 8
concurrent I/Os at any one time.
210
MESSAGE
The HPIB device adapter has detected that the
DEVICE ADAPTER PROGRAM (DAP) length exceeds
its maximum limit - DAP length greater than
512 bytes limit.
211
MESSAGE
The HPIB device adapter has detected an
illegal DEVICE ADAPTER LANGUAGE (DAL) opcode.
212
MESSAGE
The HPIB device adapter has detected a
DEAD-OR-DYING or PROTOCOL error.
213
MESSAGE
The HPIB device adapter did not return any
hardware TSTATUS.
214
MESSAGE
The HPIB device adapter has failed its
internal self test.
215
MESSAGE
The HPIB device adapter has failed to
66
Chapter 2
Error Messages Viii C 2
HPIB Adapter Manager
identify as an Advanced HPIB Device Adapter
Interface.
216
MESSAGE
The HPIB device adapter failed its internal
self test.
217
MESSAGE
The HPIB device adapter function can not be
done because PARALLEL POLL (PPOLL) interrupt
is enabled. It can be returned in response to
a setting of ATTENTION
(ATN) FALSE in the transaction.
218
MESSAGE
The HPIB device adapter has detected that the
LOOPBACK functional test failed.
219
MESSAGE
The HPIB device adapter outbound data is
frozen due to presence of inbound data on the
device adapter; it will not happen when the
device adapter is CONTROLLER-IN-CHARGE (CIC).
220
MESSAGE
The HPIB device adapter has detected an
INTERFACE CLEAR (IFC) abort of data transfer.
221
MESSAGE
The HPIB device adapter has detected an HPIB
DEVICE CLEAR (DCL).
222
MESSAGE
The HPIB transaction requires device adapter
to be either addressed or not
CONTROLLER-IN-CHARGE (CIC). Presently, it is
NOT in either case.
223
MESSAGE
The HPIB device adapter is
CONTROLLER-IN-CHARGE (CIC) and it should not
be.
224
MESSAGE
The HPIB device adapter is not
CONTROLLER-IN-CHARGE and it should be.
225
MESSAGE
The HPIB device adapter is not configured to
be a SYSTEM CONTROLLER (SC) and it should be.
226
MESSAGE
The HPIB device adapter transaction function
code is either NOT implemented or NOT
supported.
227
MESSAGE
The HPIB device adapter has detected that no
DEVICE ADAPTER PROGRAM (DAP) has been
downloaded. This error is given when an
execute downloaded DAP function is attempted
before the DAP has been previously
downloaded.
228
MESSAGE
The HPIB current DEVICE ADAPTER PROGRAM (DAP)
is still in use.
229
MESSAGE
The HPIB Device Adapter Program (DAP) has
Chapter 2
67
Error Messages Viii C 2
HPIO Channel Manager
detected a device locked during error
report/recovery.
230
MESSAGE
The HPIB device adapter has detected the
failure of the DEVICE ADAPTER PROGRAM (DAP)
being downloaded.
244
MESSAGE
The HPIB DAM has detected an ERROR when it
tries to get virtual quads for this I/O
request.
245
MESSAGE
The HPIB DAM has detected an error when it
tries to get a message frame; IO_GET_FRAME
error.
246
MESSAGE
The HPIB DAM has run out of its internal
software resources; FATAL internal error.
248
MESSAGE
The HPIB DAM has detected an error from the
CAM when checking the I/O pointers.
249
MESSAGE
The HPIB DAM has detected an error from the
CAM; CAM has no resources available.
250
MESSAGE
The HPIB DAM has detected that the I/O
request has been aborted.
251
MESSAGE
The CHANNEL ADAPTER MANAGER has returned an
error in the low level status.
252
MESSAGE
The HPIB DAM has detected that the I/O
request has
been aborted.
253
MESSAGE
The CHANNEL ADAPTER MANAGER has no resources
available.
254
MESSAGE
The CHANNEL ADAPTER MANAGER has detected an
error in the I/O request
pointers.
HPIO Channel Manager
(Subsystem 114)
38
68
MESSAGE
An I/O transaction completed with a non-zero
residue count. This is to be expected under
normal I/O conditions.
CAUSE
DMA transferred fewer bytes than specified.
ACTION
No action required.
Chapter 2
Error Messages Viii C 2
HPIO Channel Manager
44
46
51
129
150
151
Chapter 2
MESSAGE
An asynchronous interrupt from a device
adapter card was detected, but no associated
DMA was found. The interrupt is treated as
being spurious in nature.
CAUSE
Noisy signal from the CIO bus connector cable.
ACTION
Check the CIO bus connector cable and replace if
necessary.
MESSAGE
A spurious timer event message was received
without an associated request info block. The
timer event was discarded, assuming it to be
spurious in nature.
CAUSE
Software race condition with the timer subsystem.
ACTION
No action required.
MESSAGE
A request to enable parity checking for a
device adapter card must be denied, because
this version of the channel does not support
parity.
CAUSE
CIO channel adapter hardware version does not support
parity checking.
ACTION
No action required.
MESSAGE
The CIO-specific third-level interrupt
handler failed to send an interrupt event
notification message to the associated
CHANNEL ADAPTER MANAGER.
CAUSE
Interrupt Completion List has been corrupted.
ACTION
Take a system dump for analysis.
MESSAGE
The CHANNEL ADAPTER MANAGER has been set to a
"BROKEN" state by the diagnostic subsystem.
In this state, the channel adapter hardware
is assumed to be broken, such that no I/O
transaction can be successfully completed.
CAUSE
The CIO channel adapter hardware is broken.
ACTION
Refer to the diagnostic subsystem or replace the CIO
channel adapter hardware.
MESSAGE
The CHANNEL ADAPTER MANAGER has received an
event message for which an action procedure
is not known. This generally occurs during
anomalous manager state transitions, such as
powerfail recovery.
CAUSE
Software error reported.
ACTION
No action required.
69
Error Messages Viii C 2
HPIO Channel Manager
152
153
154
155
156
157
159
70
MESSAGE
The CHANNEL ADAPTER MANAGER has received a
message that contains a descriptor of unknown
value in the header. The message is thrown
away and no further action is taken.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The CHANNEL ADAPTER MANAGER is in an ILLEGAL
STATE condition. A possible cause for this
condition is the corruption of the port data
area.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The CHANNEL ADAPTER MANAGER has received a
request message that can not be legally
accepted and processed in its current state.
An error reply message is returned to the
originator of the request.
CAUSE
Software reported.
ACTION
No action required.
MESSAGE
The CHANNEL ADAPTER MANAGER has been invoked
with no associated message. This is a
catastrophic error and no action is taken by
the manager, except to notify the diagnostic
subsystem of the error.
CAUSE
A problem exists with IPC in SEND_MSG interface.
ACTION
Take a system dump for analysis.
MESSAGE
The CHANNEL ADAPTER MANAGER encountered a
system or I/O SERVICES error during the
processing of an I/O transaction. The general
nature of system service errors will tend to
be in the IPC or timer services.
CAUSE
A system service error occurred.
ACTION
Take a system dump for analysis.
MESSAGE
The channel hardware reported an undefined
subchannel state error condition. In
response, the associated device adapter card
is reset by the CHANNEL ADAPTER MANAGER to
clear the error condition.
CAUSE
Bad CIO connector cable or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware reported a subchannel
Chapter 2
Error Messages Viii C 2
HPIO Channel Manager
RTS buffer OVERRUN error condition. The
maximum RTS message allowed is 16 bytes. The
associated device adapter card is reset by
the CHANNEL ADAPTER MANAGER to clear the
error condition.
160
161
162
164
165
167
Chapter 2
CAUSE
Bad I/O connector cable or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware reported a SRQ assertion
on an inactive subchannel. This is generally
a noise problem on the CIO backplane.
CAUSE
Bad I/O connector cable or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware reported an unknown
subchannel DMA command. In response to this
error condition, the device adapter card is
reset by the CHANNEL ADAPTER MANAGER.
CAUSE
Bad CIO connector or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware reported an unknown
subchannel error. The CHANNEL ADAPTER
MANAGER, in response, will reset the
associated device adapter card.
CAUSE
Bad I/O connector cable or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware did not detect the
expected assertion of the MYAD line during a
subchannel primitive addressing operation.
The device adapter card is reset to clear the
subchannel error condition.
CAUSE
Bad CIO connector cable or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware reported a subchannel
data parity error condition. In response, the
device adapter card is reset by the CHANNEL
ADAPTER MANAGER to clear the error condition.
CAUSE
Bad CIO connector cable or defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware reported a catastrophic
module error with an undefined error code.
The entire channel is reset by the CHANNEL
ADAPTER MANAGER to clear the error condition.
71
Error Messages Viii C 2
HPIO Channel Manager
168
169
170
171
172
175
176
72
CAUSE
CIO channel adapter hardware or bus error.
ACTION
Run diagnostics on the channel adapter card.
MESSAGE
The channel hardware reported a catastrophic
module error where an ARQ line was asserted
on the CIO backplane, but no device adapter
card responded to the ARQ poll. The entire
channel is reset to clear the error
condition.
CAUSE
CIO channel adapter hardware or bus error occurred.
ACTION
Run diagnostics on the channel adapter.
MESSAGE
The channel hardware reported a catastrophic
module error where no response was found to a
midbus address transaction. In response, the
entire channel is reset to clear the error
condition.
CAUSE
CIO channel adapter hardware or bus error.
ACTION
Run diagnostics on the channel adapter.
MESSAGE
The channel hardware reported a catastrophic
module error where, as master on midbus, a
PROTOCOL error was detected. The entire
channel is reset in order to clear the error
condition.
CAUSE
CIO channel adapter hardware or bus error.
ACTION
Run diagnostics on the channel adapter.
MESSAGE
The channel hardware reported a catastrophic
module error where a data parity error was
detected during a midbus transaction. The
entire channel is reset in order to clear the
error condition.
CAUSE
CIO channel adapter hardware or bus error.
ACTION
Run diagnostics on the channel adapter.
MESSAGE
The channel hardware reported an error caused
by a diagnostic loopback test.
CAUSE
Bad CIO channel adapter hardware.
ACTION
Replace channel adapter hardware.
MESSAGE
The channel hardware received an invalid (not
decodable) command.
CAUSE
Bad CIO channel adapter hardware.
ACTION
Replace CIO channel adapter hardware.
MESSAGE
The channel hardware reported a catastrophic
Chapter 2
Error Messages Viii C 2
HPIO Channel Manager
internal module error condition. In response,
the entire channel is reset by the CHANNEL
ADAPTER MANAGER in order to clear the error
condition.
181
182
183
184
185
Chapter 2
CAUSE
Bad CIO channel adapter hardware.
ACTION
Replace CIO channel adapter hardware.
MESSAGE
The internal request information block list
is not consistent. This list is doubly linked
and is used to track all I/O transactions on
the channel hardware.
CAUSE
Channel Adapter Manager (CAM) data structure
corruption.
ACTION
Take a system dump for analysis.
MESSAGE
An internal table structure is not
consistent. These tables manage resource
allocation for I/O transactions on the
channel hardware.
CAUSE
Channel Adapter Manager (CAM) data structure
corruption.
ACTION
Take a system dump for analysis.
MESSAGE
The INTERNAL REQUEST INFO BLOCK TABLE has
been exhausted of free entries. The request
info blocks are used to track I/O
transactions on the channel hardware.
CAUSE
Too many concurrent I/O requests were activated on the
channel.
ACTION
Increase the load field in the SYSGEN I/O configuration
file for the channel to 256.
MESSAGE
The internal STATUS BLOCK TABLE has been
exhausted of free entries. The status blocks
are used in building physical quad chains to
return DMA residue count information.
CAUSE
Too many concurrent I/O requests were activated on the
channel.
ACTION
Increase the load field in the system I/O configuration file
for the channel to 256.
MESSAGE
The internal QUAD ENTRY TABLE has been
exhausted of free entries. The quad entries
are used in building physical quad chains to
perform DMA operations.
CAUSE
Too many concurrent I/O requests were activated on the
channel.
73
Error Messages Viii C 2
HPIO Channel Manager
186
191
192
195
196
200
206
74
ACTION
Increase the load field in the SYSGEN I/O configuration
file for the channel to 256.
MESSAGE
The internal LOGCHANNEL TABLE has been
exhausted of free entries. A unique
LOGCHANNEL number is assigned to each active
I/O transaction on the channel hardware.
CAUSE
Too many concurrent I/O requests were activated on the
channel.
ACTION
Increase the load field in the SYSGEN I/O configuration
file for the channel to 256.
MESSAGE
The interrupt completion list contained an
invalid list address. When a DMA operation is
completed, the channel hardware updates this
list before sending a completion interrupt.
CAUSE
Interrupt completion list has been corrupted.
ACTION
Take a system dump for analysis.
MESSAGE
The partial residue completion list contained
an invalid list address. This list is updated
by the channel hardware to return residue
count information on
a DMA order completion.
CAUSE
Residue completion list has been corrupted.
ACTION
Take a system dump for analysis.
MESSAGE
The CHANNEL ADAPTER MANAGER attempted a
diagnostic loopback test, but failed.
CAUSE
Defective CIO channel adapter hardware.
ACTION
Replace CIO channel adapter hardware.
MESSAGE
The CHANNEL ADAPTER MANAGER attempted a
diagnostic hardware selftest, but failed.
CAUSE
Defective CIO channel adapter hardware.
ACTION
Replace CIO channel adapter hardware.
MESSAGE
The event handling procedure detected an
invalid lock event option.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The reply to a request message could not be
sent, because the descriptor field in the
request message header was illegal.
CAUSE
Software error reported.
Chapter 2
Error Messages Viii C 2
HPIO Channel Manager
207
208
209
211
213
214
216
Chapter 2
ACTION
No action required.
MESSAGE
The WAIT sequence number in the request
information block for a DMA transaction is
illegal. This sequence number determines the
next step to start, resume, or abort a DMA
transaction.
CAUSE
Channel Adapter Manager (CAM) data structure
corruption.
ACTION
Take a system dump for analysis.
MESSAGE
The SELFTEST sequence number in the request
information block for a SELFTEST request is
illegal. This sequence number determines the
next step to complete the device adapter
SELFTEST sequence.
CAUSE
Channel Adapter Manager (CAM) data structure
corruption.
ACTION
Take a system dump for analysis.
MESSAGE
The CONTROL FUNCTION specified in a CIO
control request message is illegal. In
response, an error reply message is returned
to the requestor.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
A timer event message was received specifying
an illegal request number.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The device adapter detected a LOGCHANNEL
error trap condition while processing an I/O
transaction. The transaction is forced to
terminate prematurely with accompanying
reported status information.
CAUSE
Hardware error reported.
ACTION
No action required.
MESSAGE
An upper DMA requested a destructive
operation while it had other requests
pending.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The device adapter aborted an I/O transaction
75
Error Messages Viii C 2
HPIO Channel Manager
spontaneously, without a direct order to
destroy the transaction.
219
220
221
222
223
224
225
226
76
CAUSE
Hardware error reported.
ACTION
No action required.
MESSAGE
A request message contains an illegal buffer
address class field.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
A request message specifies an illegal device
adapter address.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The DEVICE ADAPTER is not ready to receive a
command.
CAUSE
Defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The DEVICE ADAPTER encountered a SUBCHANNEL
ERROR TRAP while processing an I/O
transaction.
CAUSE
Defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The DEVICE ADAPTER is not ready to accept an
RSC (resume subchannel) command. As a result,
the subchannel is assumed to be in a
permanently PAUSED condition.
CAUSE
Defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The channel hardware has set a SUBCHANNEL in
a not ready to start DMA state. This error
condition is indicative of a hung device
adapter card.
CAUSE
Defective device adapter card.
ACTION
Run diagnostics on the device adapter card.
MESSAGE
The virtual quad chain contains an illegal
CLC (connect LOGCHANNEL) order.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The virtual quad chain contains an ILLEGAL
Chapter 2
Error Messages Viii C 2
HPIO Channel Manager
DISCONNECT ORDER.
227
228
229
230
231
232
233
236
Chapter 2
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The virtual quad chain specified an ILLEGAL
TERMINATING ORDER.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The virtual quad chain specified an order
with the DMA continue bit set in an illegal
manner.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The virtual quad chain specified an illegal
CLC (connect LOGCHANNEL) buffer.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The virtual quad chain specified a buffer not
aligned to a 64-byte boundary.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The virtual quad chain specified a DMA buffer
not frozen in memory.
CAUSE
Software error reported.
ACTION
No action required.
MESSAGE
The channel hardware reported a loss of power
to the CIO backplane. As a result, all DMA
activity is terminated in an unknown state.
CAUSE
Remote CIO power loss reported.
ACTION
No action required.
MESSAGE
The channel hardware is not ready for a
command. This error condition can never occur
on a functioning channel.
CAUSE
Defective CIO channel adapter hardware.
ACTION
Replace CIO channel adapter hardware.
MESSAGE
Channel hardware configuration specifies an
invalid I/O module adapter type in the IODC
ROM.
77
Error Messages Viii C 2
I/O Services
CAUSE
Incorrect SYSGEN I/O configuration file.
ACTION
Check SYSGEN I/O configuration file.
I/O Services
(Subsystem 213)
1400
MESSAGE
Can not deliver interrupt message.
CAUSE
Ran out of LLIO message frames.
1401
MESSAGE
Can not obtain an I/O software semaphore.
1402
MESSAGE
Can not expand the I/O Completion Entry Pool.
CAUSE
Used up too many completion entries.
78
Chapter 2
Error Messages Viii C 2
Low Level I/O
Low Level I/O
(Subsystem 113)
NOTE
1
2
3
4
5
6
7
Chapter 2
Positive numbers are notes or warnings. Negative numbers are fatal errors.
MESSAGE
The operation was successful with retries.
CAUSE
An I/O was attempted and was successful, but retries were
required.
ACTION
None, unless an excessive number of retries occurred. If
there are an excessive number, then changing the device
or the media should be looked into. Call your
Hewlett-Packard Representative for assistance.
MESSAGE
Beginning of devices media encountered.
CAUSE
Beginning of media encountered when an I/O operation
was issued.
ACTION
None.
MESSAGE
An attempt was made to lock a device or
device manager which was already locked or
unlock one not currently locked by this
process.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
Disk contains marginal (possibly unreliable)
data.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A timeout occurred during a bind (software
connect) operation.
CAUSE
A device did not respond during configuration.
ACTION
Check to see if device is present.
MESSAGE
Hardware error detected during a BIND
operation.
CAUSE
A device did not respond during configuration.
ACTION
Check to see if device is connected.
MESSAGE
An end of file was detected.
CAUSE
Same as message content.
79
Error Messages Viii C 2
Low Level I/O
8
9
10
11
12
13
14
-75
-74
80
ACTION
None.
MESSAGE
The end of the media was detected.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
The I/O completed successfully with some
status available to be read.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
The read was terminated by an alternate end
of record (aeor).
CAUSE
Same as message content.
ACTION
None.
MESSAGE
Tape density requested is unknown or
unsupported.
CAUSE
Same as message content.
ACTION
Verify that the tape density is appropriate for the device.
MESSAGE
A save-set mark was detected.
CAUSE
During an I/O operation involving the
HPC1501A/HPC1511A cassette tape drive, a save-set
mark (a type of index mark) was detected.
ACTION
None.
MESSAGE
Device adapter does not support asynchronous
event notification (aen).
CAUSE
Device or device adaptor does not support asynchronous
event notification.
ACTION
None.
MESSAGE
Trying to remotely load a tape device that is
already loaded.
CAUSE
Same as message.
ACTION
None.
MESSAGE
Reservation conflict.
CAUSE
A device (or element in the device) cannot be accessed due
to a reservation conflict.
ACTION
Retry acquisition of the device later.
MESSAGE
Incorrect hardware type.
CAUSE
The device or card is not of the proper type for the
configured software.''
Chapter 2
Error Messages Viii C 2
Low Level I/O
-73
-72
-71
ACTION
Verify that the configuration and involved devices are
correct.
MESSAGE
Device is unavailable.
CAUSE
When trying to do a remotely-waited FOPEN of a device,
the device is not available.
ACTION
Retry the request later or determine why the remote
device is not responding.
MESSAGE
File does not have a correct file code.
CAUSE
Same as message.
ACTION
None.
MESSAGE
Cannot open file.
CAUSE
Same as message.
ACTION
None.
-70
MESSAGE A tape device has reported that a tape tension
loss condition has occurred.
-69
-68
-67
-66
-65
Chapter 2
CAUSE
Same as message.
ACTION
None.
MESSAGE
Special character passed in by previous
FDEVICE control call.
CAUSE
Same as message.
ACTION
None.
MESSAGE
A device data format error has occurred after
a device power failure.
CAUSE
Same as message.
ACTION
None.
MESSAGE
I/O read has been terminated by a subsystem
BREAK.
CAUSE
Same as message.
ACTION
None.
MESSAGE
The procedure cannot back space beyond the
beginning of the media.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
The procedure cannot READ past the end of the
volume.
CAUSE
Same as message content.
81
Error Messages Viii C 2
Low Level I/O
-64
-63
-62
-61
-60
-59
-58
-57
-56
82
ACTION
None.
MESSAGE
The device does not support the requested
density.
CAUSE
Same as message content.
ACTION
Check file equation for incorrect density.
MESSAGE
The device parity error count exceeded the
maximum retry count.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The I/O completed successfully, and the last
available device status should now be read.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
The download of the firmware failed.
CAUSE
This could be caused by a number of problems. Most likely
the device being downloaded to is not present, or a
hardware failure has occurred.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The device could not be cleared/reset.
CAUSE
This could be caused by a number of problems. Most likely
the device is not present, or a hardware failure occurred.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An incorrect hardware identification code was
returned from device.
CAUSE
Device configured does not match device type.
ACTION
Make sure device configured matches device type.
MESSAGE
A transmission error occurred; send the data
block again.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative to examine link
connection.
MESSAGE
An error has occurred.
CAUSE
An I/O error has occurred. Device status is now available
that should further explain the problem.
ACTION
None.
MESSAGE
An invalid internal software error occurred.
CAUSE
The operating system software module had an internal
Chapter 2
Error Messages Viii C 2
Low Level I/O
problem.
-55
-54
-53
-52
-51
-50
-49
-48
-47
-46
Chapter 2
ACTION
Call your Hewlett-Packard Representatiave.
MESSAGE
A BREAK error occurred.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
READ TIME was returned.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
No Control Y process ID (PIN) is present.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The device is off-line.
CAUSE
Same as message content.
ACTION
Place device online.
MESSAGE
A RECEIVER OVERRUN occurred.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A READ TIMEOUT error occurred.
CAUSE
Device timeout occurred.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A DATA TRANSMISSION error occurred.
CAUSE
Possible problem with media or link.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A data parity error was detected.
CAUSE
A media defect or link error occurred.
ACTION
Retry I/O operation. If problem persists, call your
Hewlett-Packard Representative.
MESSAGE
An invalid request code was detected by I/O
MANAGER.
CAUSE
Operating system software error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The request was not started or completed due
to an error condition.
CAUSE
Same as message content.
ACTION
Determine if device is present or online. If so, call your
83
Error Messages Viii C 2
Low Level I/O
Hewlett-Packard Representative.
-45
-44
-43
-42
-41
-40
-39
-38
-37
84
MESSAGE
Suspect data was encountered during I/O
operation.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A generic hardware problem occurred.
CAUSE
Error condition occurred in using a device with which
additional status is not available.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The length of requested transfer is invalid
for this device.
CAUSE
Same as message content.
ACTION
Length of I/O is not supported by device. Change file
equation to match device supported lengths.
MESSAGE
The format, or order of command to a device
is invalid.
CAUSE
Operating system software error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A CHANNEL TIMEOUT caused failure.
CAUSE
A device hardware or link failure was detected.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The request failed due to a device time out.
CAUSE
Same as message content.
ACTION
Verify that the device is connected properly and has power.
Call your Hewlett-Packard Representative.
MESSAGE
A LOWER LEVEL MANAGER error occurred; status
is unknown or not available.
CAUSE
Operating system software error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Data was lost due to a transfer error.
CAUSE
Some sort of data transmission error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An invalid device address was requested.
CAUSE
Operating system software error.
ACTION
Verify that the device configuration is correct. If it is, and
problem persists, call your Hewlett-Packard
Chapter 2
Error Messages Viii C 2
Low Level I/O
Representative.
-36
-35
-34
-33
-32
-31
-30
-29
-28
Chapter 2
MESSAGE
Unformatted media is being used.
CAUSE
Same as message content.
ACTION
Format media and try operation over.
MESSAGE
A parity, CRC, or other data type error was
detected.
CAUSE
Possible hardware, media, or link failure.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The device was physically reset or the I/O
request was aborted by a reset request.
CAUSE
Same as message content.
ACTION
None.
MESSAGE A device powering on condition was detected.
CAUSE
Same as message content.
ACTION
Determine reason for device power failure.
MESSAGE
A write operation to a read-only device was
attempted.
CAUSE
Same as message content.
ACTION
Determine process that attempted operation. Call your
Hewlett-Packard Representative for assistance.
MESSAGE
Operator attention is required, for example,
printer is out of paper; tape needs next
reel.
CAUSE
Same as message content.
ACTION
Take action to correct condition. For example, put paper in
the printer.
MESSAGE
An unexpected end-of-file or resource
occurred; for example, disk transfer hit the
end of the volume or tape hit the end-of-tape
mark.
CAUSE
Same as message content.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The device is not ready or is not responding.
CAUSE
Same as message content.
ACTION
Place device online.
MESSAGE
The I/O MANAGER must be locked for this
request and it is not.
85
Error Messages Viii C 2
Low Level I/O
-27
-26
-25
-24
-23
-22
-21
-20
86
CAUSE
Operating system or product software error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The I/O MANAGER has been locked by another
module.
CAUSE
Possibly an operating system or product software error.
ACTION
This may be a normal situation if a device diagnostic tool
has obtained exclusive access to the device (e.g., tape
device diagnostic tools such as REELDIAG and DIAG7978
do this). Check for this situation and if this is NOT the
case, call your Hewlett-Packard Representative.
MESSAGE
A memory request error occurred.
CAUSE
Operating system software error—Memory Manager
returned an error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The procedure was unable to obtain memory
necessary to continue operation.
CAUSE
Operating system software error—Memory Manager
services of the operating system returned an error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An attempt to release memory failed.
CAUSE
Operating system software error—Memory Manager
services of the operating system returned an error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Some resource was not released.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The request contained incorrect higher
manager port number.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The DO_UNBIND operation failed.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The port number of lower level I/O MANAGER is
incorrect.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
Chapter 2
Error Messages Viii C 2
Low Level I/O
-19
-18
-17
-16
-15
-14
-13
-12
-11
Chapter 2
MESSAGE
A DO_UNBIND request was made to a nonexistent
I/O MANAGER.
CAUSE
Operating system problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The procedure cannot UNBIND because I/O is
still pending.
CAUSE
Operating system or hardware failure.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The BIND operation did not work or an UNBIND
was requested of an I/O MANAGER that was not
bound.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The BIND request failed; manager is already
bound.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The BIND to lower manager failed.
CAUSE
Operating system software problem.
ACTION
Call you Hewlett-Packard Representative.
MESSAGE
Bad time on bus for this BIND or DO_BIND
request.
CAUSE
Hardware failure occurred during configuration sequence.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Bad critical response for this BIND or
DO_BIND request.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Bad bandwidth for this BIND or DO_BIND
request.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A bad hardware address was detected for a
BIND or DO_BIND request.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
87
Error Messages Viii C 2
Low Level I/O
-10
-9
-8
-7
-6
-5
-4
-3
-2
88
MESSAGE
A bad revision code was detected for a BIND
or DO_BIND request.
CAUSE
Operating system software problem—version mismatch
between modules and procedures.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A bad meta tag was detected for a BIND or a
DO_BIND request.
CAUSE
Operating system software problem occurred during
configuration of device manager components.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A bad subsystem identifier was detected for a
BIND or a DO_BIND request.
CAUSE
Operating system problem occurred during configuration
of device managers.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An unclassified software problem occurred.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The state of the I/O MANAGER is in
appropriate for this request.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The last available status was requested, but
none is available yet.
CAUSE
Possible hardware failure.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The requested operation cannot be understood
by the I/O MANAGER.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The requested function/operation is not
implemented by this I/O MANAGER.
CAUSE
Operating system software problem.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A system power failure occurred. An I/O
operation was aborted or not started.
CAUSE
Same as message content.
Chapter 2
Error Messages Viii C 2
Measurement Interface
-1
ACTION
Determine why system power failure occurred.
MESSAGE
An I/O operation was aborted by user.
CAUSE
Same as message content.
ACTION
Determine why I/O was aborted.
Measurement Interface
(Subsystem 133)
5
10
15
25
35
Chapter 2
MESSAGE
The PID has not been created.
CAUSE
The specific process no longer exists in the system. The
process has been specified by the Measurement Interface
(MI) user through the SUBCLASS_ARRAY parameter in
the procedure ENABLE_MEASUREMENTS.
ACTION
Retry with the correct process ID.
MESSAGE
The group PARM is greater than
MAX_GROUP_IN_CLASS for requested class.
CAUSE
The user of procedures which require a group value
entered an index value for the group which is outside the
range for groups within a performance class.
ACTION
Remove faulty value and try again.
MESSAGE
Too many user or program names given in an
ENABLE_MEASUREMENT call; ENABLE_MEASUREMENTS
does continue, however.
CAUSE
The user of the ENABLE_MEASUREMENT procedure
has requested more than 10 program names and/or 10
user names.
ACTION
Reduce the number of names to 10 (10 programs and/or 10
user names) and try again.
MESSAGE
The total subclasses were zero; condition not
acceptable.
CAUSE
A negative or zero value for the parameter for
TOT_SUBCLASSER for ENABLE_MEASUREMENT
and/or DISABLE_MEASUREMENT procedures.
ACTION
Correct the value and retry.
MESSAGE
The measurement interface PID list is full.
CAUSE
The user of ENABLE_MEASUREMENT has requested
more than 2700 processes to monitor.
89
Error Messages Viii C 2
Measurement Interface
50
65
70
90
100
110
90
ACTION
Reduce the number of processes requested and try again.
MESSAGE
The user buffer is not large enough to hold
all requested counters.
CAUSE
The user of GET_MEASUREMENTS has passed a buffer
to receive performance data which is too small.
ACTION
Increase buffer size and try again.
MESSAGE
The counter table has no more entries, so all
groups requested got enabled.
CAUSE
Major problem with the MEASUREMENT INTERFACE
data structure whereby there was a problem getting
enough memory to create the counter array.
ACTION
Scale back on the number of items being measured or
expand memory.
MESSAGE
The requested class has an index value less
than zero or greater than the current total
number of classes.
CAUSE
The requested class in ENABLE_MEASUREMENTS,
GET_MEASUREMENTS, and/or
DISABLE_MEASUREMENTS is not within the range of 1
to 3.
ACTION
Correct the class value and try again.
MESSAGE
A new subclass is requested, but the LOOKUP
TABLE is full.
CAUSE
A user has specified more LDEVs than the IO LOOKUP
TABLE can accommodate in the call to
ENABLE_MEASUREMENTS.
ACTION
Be more selective on the number of I/O devices. Adjust the
number of LDEVs and try again. See limits in the MPE XL
Measurement Interface User's Guide.
MESSAGE
ENABLE of measurement subclass failed.
CAUSE
A user has tried to enable performance measurements
through the procedure ENABLE_MEASUREMENTS, but
the number of MI users exceeds the limit of 25.
ACTION
Wait until an MI user quits and retry.
MESSAGE
No measurement ID entry in the MI_ID TABLE.
CAUSE
A user has called GET_MEASUREMENTS or
DISABLE_MEASUREMENTS without first enabling
measurements through the procedure
ENABLE_MEASUREMENTS.
ACTION
Check to be sure that you first call
ENABLE_MEASUREMENTS.
Chapter 2
Error Messages Viii C 2
Measurement Interface
130
140
150
160
170
180
Chapter 2
MESSAGE
The current class has been ENABLED too many
times without intervening DISABLES.
CAUSE
Either 1) a second enable for global class, 2) more ID class
enables than total number of device classes or more
LDEVs than exist in given device class, or 3) a change in
groups selected with new enables for new process in
process class.
ACTION
Correct misunderstanding in using ENABLE
MEASUREMENTS. See the MPE XL Measurement
Interface User's Guide for more information on using the
procedure ENABLE_MEASUREMENTS.
MESSAGE
The number of counters do not match the known
number of object classes.
CAUSE
User called CONVERT_TO_STD_OBJCL procedure with
group whose group header shows a number of counters to
be not 10, 33, or 501.
ACTION
Check to be sure group is an object class group. Modify
input and try again.
MESSAGE
The group index does not belong to an object
class group.
CAUSE
User called CONVERT_TO_STD_OBJCL procedure with
a group that is not recognized as an object class group for
the particular class.
ACTION
Check to be sure the group is an object class group. Modify
input and try again.
MESSAGE
LDEVS in the array are not all of the same
device type.
CAUSE
User called ENABLE_MEASUREMENT with an array of
LDEVs that are not of the same device class, or user called
DISABLE_MEASUREMENTS with an array of LDEVs
that are not of the same device class.
ACTION
Correct LDEVs in the array to be of the same device class
and retry.
MESSAGE
Failed to obtain lock for the MEAS_KSO_TABLE.
CAUSE
Major problem with MEASUREMENT INTERFACE data
structure or control block lock code of the operating
system.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Failed to obtain lock for the PROCESS LOOKUP
SUBCLS TABLE.
CAUSE
Major problem with MEASUREMENT INTERFACE data
structure, or control block lock code of the operating
91
Error Messages Viii C 2
Measurement Interface
system.
190
200
210
220
92
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Failed to obtain lock for the NAME POINTER
LIST TABLE.
CAUSE
Major problem with MEASUREMENT INTERFACE data
structure, or TABLE MANAGEMENT control block lock
code of the operating system.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Failed to obtain lock for the MI_ID TABLE.
CAUSE
Major problem with MEASUREMENT INTERFACE data
structure, or Table Management control block lock code of
the operating system.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Failed to obtain lock for the USER_LIST
TABLE.
CAUSE
Major problem with MEASUREMENT INTERFACE data
structure or TABLE MANAGEMENT control block lock
code of the operating system.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Failed to obtain lock for PROG_LIST TABLE.
CAUSE
Major problem with MEASUREMENT INTERFACE data
structure or TABLE MANAGEMENT control block lock
code of the operating system.
ACTION
Call your Hewlett-Packard Representative.
Chapter 2
3 Error Messages Viii C 3
Memory Manager
(Subsystem 101)
1
MESSAGE
The current process does not have access to
the given object.
2
MESSAGE
No contiguous virtual space is available.
3
MESSAGE
The MEMORY MANAGER is starting to THRASH and
will, therefore, not allow any further pages
to be kicked out until the danger subsides.
4
MESSAGE
The MEMORY MANAGER has delayed processing
requests for the current PIN, because there
is more urgent activity to be done elsewhere.
5
MESSAGE
The MEMORY MANAGER was unable to obtain an
I/O INFO entry from the I/O INFO TABLE.
6
MESSAGE
The MEMORY MANAGER was unable to obtain an
I/O notify entry from the I/O NOTIFY TABLE.
7
MESSAGE
The MEMORY MANAGER was unable to obtain an
I/O request entry from the I/O REQUEST TABLE.
8
MESSAGE
The virtual page does not exist.
9
MESSAGE
The MEMORY MANAGER cannot obtain I/O TABLE
entries (out of I/O resources).
10
MESSAGE
An I/O completion message has been received
from HIGH LEVEL I/O.
11
MESSAGE
A CLEAN page is not immediately available, so
a page must be kicked out and made CLEAN in
order to satisfy the request.
12
MESSAGE
A disk READ error from LOW LEVEL I/O was
encountered when trying to access a page on
the disk.
13
MESSAGE
Invalid options were used when attempting to
remap a physical page to a different virtual
page.
93
Error Messages Viii C 3
MPE/iX Data Communications Buffer Manager
14
MESSAGE
The virtual address of the source from which
data is to be copied is invalid.
15
MESSAGE
The virtual address of the target to which
data is to be copied is invalid.
16
MESSAGE
The length of the data to be copied from one
virtual address to another is invalid.
17
MESSAGE
Access to the alias operation (used to copy
data from one point to another) is not
allowed.
18
MESSAGE
The list of entries describing a PIN's
locality is full and can not be extended.
19
MESSAGE
The LOCALITY ENTRY TABLE is out of entries.
76
MESSAGE
An error occurred when changing from VPS to
KO.
73
MESSAGE
The disk allocation suspension counter in the
TCB has gone below zero.
MPE/iX Data Communications Buffer Manager
(Subsystem 201)
3090
MESSAGE
Illegal buffer ID passed to DCL Buffer
Manager procedure BMGR_FREE_BUFFER.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MPE/iX Error Management
(Subsystem 187)
1
2
94
MESSAGE
A system error STACK OVERFLOW occurred.
CAUSE
Number of error entries to PUSH into the Process Error
Stack is greater than the Process Error Stack size.
ACTION
Decrease the error entries or increase the Error Stack size.
MESSAGE
A system error STACK UNDERFLOW occurred.
Chapter 3
Error Messages Viii C 3
MPE/iX Error Management
3
4
5
6
7
8
9
Chapter 3
CAUSE
Number of error entries to POP off the Process Error
Stack is greater than the Error Stack size, or the Error
Stack is empty.
ACTION
Decrease the error entries or increase the Error Stack size.
MESSAGE
The specified STACK ENTRY does not exist on
the PROCESS ERROR STACK.
CAUSE
The value of INDEX does not correspond to an error in the
global error log, or in the Process Error Stack.
ACTION
Check the STACK ENTRY and use the valid one.
MESSAGE
CREATE_OBJECT failed in creating stack.
CAUSE
In creating stack, an attempt to call CREAT_OBJECT
failed; internal error.
ACTION
Check CREATE_OBJECT.
MESSAGE
RELEASE_OBJECT failed in releasing stack.
CAUSE
In releasing stack, an attempt to call RELEASE_OBJECT
failed; internal error.
ACTION
Check RELEASE_OBJECT.
MESSAGE
The specified error number is a zero, which
is invalid.
CAUSE
User specifies zero as an error number which is invalid in
the System Catalog file.
ACTION
Use the valid number( > 0, < 0).
MESSAGE
The specified subsystem number is not valid.
CAUSE
User specified an invalid SUBSYS number (<= 0) or the
SUBSYS number is not in the System Catalog.
ACTION
Use the correct SUBSYS number.
MESSAGE
The specified buffer is too small to hold the
text of the error message; the message has
been truncated.
CAUSE
The value of BUF_LEN is smaller than the actual message
in the System Catalog being returned. The message has
been truncated.
ACTION
Increase the buffer size to hold the entire text.
MESSAGE
The requested depth is outside of the valid
range for the PROCESS ERROR STACK.
CAUSE
User specified the depth outside of the Process Error Stack
range. It has to be in the range between 1 and 16.
ACTION
Use the valid stack depth, which is between 1 and 16.
95
Error Messages Viii C 3
MPE/iX Error Management
10
11
12
15
16
17
18
19
96
MESSAGE
An error occurred while attempting to create
a KSO for use by the ERROR MANAGEMENT
subsystem.
CAUSE
An error was encountered in attempting to create the
global system error log object or a KSO.
ACTION
Check the system.
MESSAGE
The ERROR MANAGEMENT subsystem was unable to
get a pointer to one of its KSOs.
CAUSE
An error occured in attempting to get a pointer to the
global system error log or the KSO which holds
parameters.
ACTION
Check the global system error log or KSO.
MESSAGE
The specified STACK ENTRY does not exist in
the SYSTEM ERROR STACK.
CAUSE
The value of DEPTH does not correspond to an error in the
System Error Stack.
ACTION
Check the value of DEPTH and System Error Stack.
MESSAGE
A RECOVER statement was unexpectedly invoked
in the ERROR MANAGEMENT subsystem.
CAUSE
An unexpected trap occurred which caused the RECOVER
block to be invoked.
ACTION
Check the error trap.
MESSAGE
An attempt was made to access process error
stack by a caller running on the ICS.
CAUSE
The caller is on ICS and, therefore, no operation was
performed when attempting to access process error stack.
ACTION
Do not access process error stack when the caller is on
ICS.
MESSAGE
An error occurred while attempting to close
the System Catalog.
CAUSE
When trying to close the System Catalog, an error occured.
ACTION
Check the System Catalog. You must open it before you
can close it.
MESSAGE
The process error stack is empty.
CAUSE
User is trying to access the process error stack and there
are no errors in the stack.
ACTION
Check the process error stack before accessing it.
MESSAGE
An error occurred while attempting to open
the System Catalog; error messages cannot be
Chapter 3
Error Messages Viii C 3
MPE/iX Error Management
obtained.
23
24
25
26
27
28
Chapter 3
CAUSE
User is trying to open the System Catalog to access the
error message and it failed.
ACTION
Check System Catalog.
MESSAGE
The BUFFER and BUF_LEN parameters must be
supplied in order to return the text of the
specified error to the caller.
CAUSE
User specified a message to go into buffer and BUFFER
and BUF_LEN parameters are not there.
ACTION
Check the parameters and provide BUFFER and
BUF_LEN parameters.
MESSAGE
The requested display option is invalid.
CAUSE
User is trying to use an invalid display option to display
errors.
ACTION
Check the requested display option and use the correct
one.
MESSAGE
There is no message set in the System Catalog
which corresponds to the subsystem number in
the specified status.
CAUSE
User is trying to use the invalid subsystem set number to
access the System Catalog.
ACTION
Check the System Catalog or use the valid subsystem set
number.
MESSAGE
There is no error number in the System
Catalog which corresponds to the specified
status.
CAUSE
User is tring to use the invalid error number to access the
error message from System Catalog.
ACTION
Check the System Catalog or use the valid error number.
MESSAGE
The specified number of message parameters to
push is invalid; valid range is from 1 to 5.
CAUSE
The value of message parameters is not in the range. The
valid range is from 1 to 5.
ACTION
Check the value of message parameters and use the valid
one.
MESSAGE
One of the message parameters to be pushed is
not a valid string parameter.
CAUSE
One of the string parameters specified is invalid, meaning
that the delimiter in the beginning of the string was not
found prior to the maximum number of characters allowed
97
Error Messages Viii C 3
MPE/iX Error Management
in the string.
200
201
202
203
204
205
98
ACTION
Check the string parameter and correct it.
MESSAGE
WARNING ** The error management subsystem was
unable to open the System Catalog; error
messages cannot be obtained.
CAUSE
When the user tried to access the System Catalog to
obtain error messages, an error occurred.
ACTION
Check the System Catalog or Error messages.
MESSAGE
WARNING ** Message set ! was not found in the
System Catalog.
CAUSE
If the user is trying to access System Catalog with an
invalid subsystem number, this warning message is
issued.
ACTION
Check the System Catalog and use the valid number.
MESSAGE
WARNING ** Message set !, Error number ! was
not found in the System Catalog.
CAUSE
When the user is trying to access the System Catalog with
invalid subsystem numbers and error number, this
warning message is issued.
ACTION
Check the subsystem and error number before accessing
the System Catalog.
MESSAGE
WARNING ** An unexpected error was
encountered while reading error messages from
the System Catalog.
CAUSE
When the user tried to query the System Catalog with
subsystem numbers and message numbers, an internal
error occurred.
ACTION
Check the subsystem numbers and message numbers.
MESSAGE
The ERROR MANAGEMENT subsystem was unable to
initialize its semaphore.
CAUSE
When the ERROR MANAGEMENT subsystem tried to
call the Control Block routine to initialize its semaphore,
an internal error occurred.
ACTION
Check the internal error and contact the Control Block
routines owner.
MESSAGE
WARNING ** One or more entries on the error
stack have been overwritten.
CAUSE
If the user tried to dump the entire error stack and some
entries were overwritten, this warning message is issued
to warn the user of that fact.
Chapter 3
Error Messages Viii C 3
MPE/iX Error Management
501
502
503
504
505
506
508
Chapter 3
ACTION
Check the error stack.
MESSAGE
The menu selection is not valid; select from
the menu choices only.
CAUSE
User has entered a character string which does not match
any of the options specified in the accompanying menu of
choices.
ACTION
Enter only the indicated selections.
MESSAGE
The specified INFO string is longer than
allowed.
CAUSE
User has entered an INFO string which is larger than the
program can handle.
ACTION
The program will handle an INFO string with the largest
possible subsystem INFO string. Entries must be limited
to 50 characters between the quotations.
MESSAGE
Only numeric digits (0...9) and an optional
sign indicator (+, -) are allowed.
CAUSE
Numeric entries may contain a leading "+" or "-", but all
other characters must be digits only. Blanks (other than
leading or trailing blanks) are not allowed.
ACTION
Enter a valid numeric quantity.
MESSAGE
The specified time code contains an invalid
date and/or time.
CAUSE
The time stamp code provided is not recognized by the
system conversion procedures.
ACTION
Check the time code and re-enter correctly.
MESSAGE
An internal failure of NATIVE LANGUAGE
SUPPORT intrinsic occurred.
CAUSE
Unexpected error of an unknown nature returned from
NLS.
ACTION
Notify your support engineer. An error stack dump may
indicate the precise nature of the error.
MESSAGE
NATIVE LANGUAGE SUPPORT is not available on
this system.
CAUSE
This is an unexpected error which should have been
detected at the start of the program and corrected by
bypassing Native Language support.
ACTION
Notify your support engineer.
MESSAGE
The subsystem was specified without a
corresponding message number.
CAUSE
The message number (second parameter) was left blank
99
Error Messages Viii C 3
MPE/iX Error Management
after specifying a subsystem number.
509
510
511
512
513
514
515
100
ACTION
Either provide a message number or delete the subsystem
number from the INFO string.
MESSAGE
A message number was specified without a
corresponding subsystem number.
CAUSE
A message number was specified but the subsystem
number (first parameter) was left blank.
ACTION
You must either specify both a subsystem number and
message number or neither.
MESSAGE
The specified number is outside the
permissible range of 1...32766.
CAUSE
The user has provided a number less than 0 or greater
than one less than maxshortint. (One less than
maxshortint is a message catalog limitation).
ACTION
Restrict entries to the indicated range.
MESSAGE
The specified number is outside the
permissible range of 1...2147483647.
CAUSE
The user has provided a number less than 0 or greater
than maxint.
ACTION
Restrict entries to the indicated range.
MESSAGE
The specified number is outside the
permissible range of 1...9223372036854775807.
CAUSE
The user has provided a number less than 0 or greater
than maxlongint.
ACTION
Restrict entries to the indicated range.
MESSAGE
The specified number is larger/smaller than
the largest/smallest integer which this
system can handle.
CAUSE
The user has provided a number that this system can not
handle.
ACTION
Check the number and use a correct one.
MESSAGE
An unexpected problem was encountered while
trying to convert a string to a number.
CAUSE
When trying to convert a string to a number, an internal
error was encountered.
ACTION
Check the string.
MESSAGE
Too few parameters were specified in the INFO
string.
CAUSE
Syntax error. Parameters may be nil, but their
Chapter 3
Error Messages Viii C 3
Native Mode Device File
corresponding delimiters must be present.
516
534
550
551
ACTION
Adhere to required syntax. The INFO string for this
program must contain a minimum of two parameters. If
you need help on syntax, type "HELP MSGUTIL".
MESSAGE
The name for the specified subsystem could
not be obtained.
CAUSE
The user has provided a subsystem number which is not in
the System Catalog.
ACTION
Check the System Catalog or use the right number.
MESSAGE
Unable to display Message #
ACTION
Information only.
MESSAGE
WARNING - Time/date display capabilities
could not be activated.
CAUSE
The program could not adequately initialize range
checking for time codes. Therefore, time code conversions
will not be accepted. This error is unexpected and may be
system dependent.
ACTION
Other functions of the program will continue to function.
Notify your support engineer.
MESSAGE
WARNING - Extra, unused parameters were
specified in the INFO string.
CAUSE
More than three parameters have been supplied.
MSGUTIL ignored all past those first three.
ACTION
Adhere to the required syntax.
Native Mode Device File
(Subsystem 231 NMDF WARN, NMDF ERR)
-1
MESSAGE
An invalid call to either Get or
Set_device_information has
occurred. No return parameter was provided
for a requested return
item.
-2
MESSAGE
An invalid call to either Get or
Set_device_information has occurred.
An item number was specified that is not a
valid item for Get or
Set_device_information.
Chapter 3
101
Error Messages Viii C 3
Native Mode Device File
-3
MESSAGE
A return parameter to NMDF specifies an
address out of the user data
area.
-4
MESSAGE
Information was requested on a native mode
device file that does not
exist.
-5
MESSAGE
Get or Set_device_information could not
sm_open a device file.
-6
MESSAGE
Get or Set_device_information was passed an
invalid device file
name.
-7
MESSAGE
Get/set_device_information could not open a
device file.
-8
MESSAGE
Get/set_device_information was asked for a
next device or class and no next device or
class exists.
-9
MESSAGE
A reference parameter to get or
set_device_information specifies an address
out of the user data area.
-10
MESSAGE
A non-existent device file name was passed to
get or set_device_information.
-11
MESSAGE
Both device and class were specified to
get/set_device_information.
-12
MESSAGE
No device or class was passsed to
get/set_device_information.
-13
MESSAGE
A parameter to Get/set_device_information was
out of its valid range.
-14
MESSAGE
Get or set_device_information was passed an
invalid device file name.
-15
MESSAGE
Device specifier not passed to
get/set_device_information.
-16
MESSAGE
No device or class was passsed to
get/set_device_information.
-17
MESSAGE
An invalid kind of device specifier was
passed to get/set_device_information.
-18
MESSAGE
In a call to Get/set_device_information,
caller requested to set an item that cannot
be set.
-19
MESSAGE
A parameter to Get/set_device_information
asks for information that is incompatible
with the type of device/class specified.
102
Chapter 3
Error Messages Viii C 3
Native Mode Device File
-20
MESSAGE
Get_device_information was asked for a next
device or class and no next device or class
exists.
-20
MESSAGE
Get_device_information was asked for a next
device or class and no next device or class
exists.
-21
MESSAGE
Get_device_information was asked for an nth
device and no nth device exists.
-22
MESSAGE
Get_device_information was asked for the nth
device/class but "n" was not first specified.
-23
MESSAGE
Information was requested on the nth device
or class and it is larger than the number of
devices or classes for the device file
specified.
-24
MESSAGE
A device specifier that was not properly
delimited was passed to
Get/Set_device_information.
-25
MESSAGE
A request was made to NMDF_reserve_device for
a device that was already reserved.
-26
MESSAGE
A request was made to
NMDF_exercise_device_reservation for a device
that was not reserved.
-27
MESSAGE
A request was made to
NMDF_exercise_device_reservation with a
ticket that was not valid.
-28
MESSAGE
A bad file name address was passed to
NMDF_convert_name_to_qualiafied_name.
-29
MESSAGE
Get or set_device_information was unabale to
access the file label extension for a device
file.
-30
MESSAGE
Nmdf_create_device_or_class could not HPFOPEN
a new device file.
-31
MESSAGE
NMDF_create_device_or_class could not create
the file label extensionfor the device file.
-32
MESSAGE
Add_device was called to add a locally
connected terminal to Network Server
processor.
1
MESSAGE
Nmdf_create_device_or_class was called to
create a device class that already exists.
2
MESSAGE
Nmdf_create_class was called to create a
class that already exists.
3
MESSAGE
Nmdf_create_device was called to create a
Chapter 3
103
Error Messages Viii C 3
NLIOUTIL
device that already exists.
NLIOUTIL
(NLIO WARN, NLIO ERR)
11
MESSAGE
TERMINAL n IS SHUT.
12
MESSAGE
PRINTER n IS SHUT.
21
MESSAGE
TERMINAL n IS OPENED IN LANGUAGE n.
22
MESSAGE
PRINTER n IS OPENED WITH LANGUAGE n.
31
MESSAGE
TERMINAL n IS OPENED WITH LANGUAGE n,
RECCONV.
32
MESSAGE
TERMINAL n IS OPENED WITH LANGUAGE n,
NORECCONV.
33
MESSAGE
PRINTER n IS OPENED WITH LANGUAGE n, RECCONV.
34
MESSAGE
PRINTER n IS OPENED WITH LANGUAGE n,
NORECCONV.
35
MESSAGE
LATIN MODE, WIDTH = n, SHAPE = n.
36
MESSAGE
NONLATIN MODE, WIDTH = n, SHAPE = n.
41
MESSAGE
TERMINAL n : LANGUAGE IS SET TO n.
42
MESSAGE
PRINTER n : LANGUAGE IS SET TO n.
51
MESSAGE
TERMINAL n : RECCONV IS SET.
52
MESSAGE
TERMINAL n : NORECCONV IS SET.
61
MESSAGE
PRINTER n : RECCONV IS SET.
62
MESSAGE
PRINTER n : NORECCONV IS SET.
71
MESSAGE
PRINTER n : LATIN MODE IS SET.
72
MESSAGE
PRINTER n : NONLATIN MODE IS SET.
81
MESSAGE
PRINTER n : WIDTH IS SET TO n.
91
MESSAGE
PRINTER n : SHAPE IS SET TO n.
1200
MESSAGE
TERMINAL n IS ALREADY OPENED. (NLIO WARN
1200)
1201
MESSAGE
PRINTER n IS ALREADY OPENED. (NLIO WARN 1201)
CAUSE
You tried to OPEN a device which was already OPENed.
ACTION
Use the SHOW command to check the status. Check the
104
Chapter 3
Error Messages Viii C 3
NLIOUTIL
ldev.
1202
MESSAGE
TERMINAL n IS CONTROLLED BY OTHER PROCESS.
(NLIO WARN 1202)
CAUSE
Same as message.
ACTION
Re-try the same command.
MESSAGE
TERMINAL n IS IN USE, SHUT PENDING. (NLIO
WARN 1204)
CAUSE
Same as message.
ACTION
No action required.
MESSAGE
PRINTER n IS IN USE, SHUT PENDING. (NLIO WARN
1205)
CAUSE
Same as message.
ACTION
No action required.
MESSAGE
TERMINAL n HAS NOT BEEN OPENED YET. (NLIO
WARN 1206)
CAUSE
You tried to SHUT a device which was not OPENed. Or, a
device which you SHOWed was not OPENed.
ACTION
Check the ldev if necessary
MESSAGE
PRINTER n HAS NOT BEEN OPENED YET. (NLIO WARN
1207)
CAUSE
You tried to SHUT a device which was not OPENed. Or, a
device which you SHOWed was not OPENed.
ACTION
Check the ldev if necessary
MESSAGE
NO TERMINAL/PRINTER HAS BEEN OPENED. (NLIO
WARN 1208)
CAUSE
You tried to SHUT devices, or SHOWed the status when
no device had been OPENed.
ACTION
No action is required.
MESSAGE
TERMINAL n IS SHUT PENDING. (NLIO WARN 1211)
CAUSE
Same as message.
ACTION
No action required.
MESSAGE
PRINTER n IS SHUT PENDING. (NLIO WARN 1212)
CAUSE
Same as message.
ACTION
No action required.
1300
MESSAGE
"NLIODEF.PUB.SYS" FILE BEING ACCESSED. (NLIO
WARN 1300)
2100
MESSAGE
UNKNOWN COMMAND WAS ENTERED. (NLIO ERR 2100)
1204
1205
1206
1207
1208
1211
1212
Chapter 3
105
Error Messages Viii C 3
NLIOUTIL
2101
2102
2110
2111
2113
2114
2115
106
CAUSE
Command name incorrect.
ACTION
Re-enter the command. Use HELP to check the syntax.
MESSAGE
TOO MANY PARAMETERS WERE ENTERED. (NLIO ERR
2101)
CAUSE
Same as message.
ACTION
Re-enter the command using the correct syntax. Use
HELP to check the syntax.
MESSAGE
INVALID DELIMITER WAS ENTERED. (NLIO ERR
2102)
CAUSE
The second OPEN delimeter is incorrect.
ACTION
Re-enter the command using the correct syntax. Use
HELP to check the syntax.
MESSAGE
LDEV CANNOT BE OMITTED FOR NON-INTERACTIVE
STDIN. (NLIO ERR 2110)
CAUSE
Same as message.
ACTION
Re-enter the command, specifying the ldev.
MESSAGE
NO DEVICE IS DESIGNATED FOR SPECIFICED
DEVICE. (NLIO ERR 2111)
CAUSE
The device or device class specified does not refer to a
configured device.
ACTION
Check the system configuration and re-enter the
command, specifying the correct ldev.
MESSAGE
SPECIFIED LDEV n IS NOT A TERMINAL OR
PRINTER. (NLIO ERR 2113)
CAUSE
The specified ldev was other than a terminal or a printer.
ACTION
Check the system configuration and re-enter the
command, specifying the correct ldev.
MESSAGE
SPECIFIED DEVICE CLASS IS NOT A TERMINAL OR
PRINTER. (NLIO ERR 2114)
CAUSE
The specified device class does not apply to terminals or
printers.`
ACTION
Check the system configuration and re-enter the
command, specifying the correct device class.
MESSAGE
INVALID PARAMETER WAS ENTERED. (NLIO ERR
2115)
CAUSE
The specified ldev was other than a terminal or a printer.
ACTION
Check the system configuration and re-enter the
command, specifying the correct ldev.
Chapter 3
Error Messages Viii C 3
NLIOUTIL
2116
MESSAGE
TMUX TERMINAL WAS SPECIFIED. (NLIO ERR 2116)
2120
MESSAGE
INVALID LANGUAGE WAS ENTERED. (NLIO ERR 2120)
CAUSE
The input language ID was not a valid one.
ACTION
Check the language ID and re-enter the command,
specifying a correct language ID.
MESSAGE
UNKNOWN LANGUAGE WAS ENTERED. (NLIO ERR 2121)
CAUSE
Unsupported language ID was entered. as the system
default language.
ACTION
Check the language ID and re-enter the command.
MESSAGE
INVALID LANGUAGE IS USED. (NLIO ERR 2122)
CAUSE
Unsupported language ID was set as the user interface
language set, or as the system default language.
ACTION
Re-enter the command, specifying the correct language ID.
MESSAGE
SPECIFIED LANGUAGE IS NOT CONFIGURED ON THE
SYSTEM. (NLIO ERR 2123)
CAUSE
The specified language is not supported on the system.
ACTION
Check and set the valid language, then re-enter the
command.
2130
MESSAGE
INVALID WIDTH PARAMETER WAS ENTERED. (NLIO
ERR 2130)
2131
MESSAGE
INVALID WIDTH VALUE WAS ENTERED. (NLIO ERR
2131)
2140
MESSAGE
INVALID SHAPE PARAMETER WAS ENTERED. (NLIO
ERR 2140)
2141
MESSAGE
INVALID SHAPE VALUE WAS ENTERD. (NLIO ERR
2141)
2150
MESSAGE
UNKNOWN COMMAND FOR HELP. (NLIO ERR 2150)
CAUSE
You entered a command that HELP does not recognize.
ACTION
Check the valid command names by entering the HELP
command without any parameters. Then re-enter the
HELP command using the correct parameter.
2160
MESSAGE
BOTH RECCONV AND NORECCONV PARAMETER WERE
ENTERED. (NLIO ERR 2160)
2161
MESSAGE
BOTH LATIN AND NONLATIN PARAMETER WERE
ENTERED. (NLIO ERR 2161)
2162
MESSAGE
REDUNDANT RECCONV PARAMETER. (NLIO ERR 2162)
2163
MESSAGE
REDUNDANT NORECCONV PARAMETER. (NLIO ERR
2163)
2121
2122
2123
Chapter 3
107
Error Messages Viii C 3
Parser
2164
MESSAGE
REDUNDANT LATIN PARAMETER. (NLIO ERR 2164)
2165
MESSAGE
REDUNDANT NONLATIN PARAMETER. (NLIO ERR 2165)
2166
MESSAGE
REDUNDANT WIDTH PARAMETER. (NLIO ERR 2166)
2167
MESSAGE
REDUNDANT SHAPE PARAMETER. (NLIO ERR 2167)
2170
MESSAGE
LANGUAGE WAS NOT ASIAN LANGUAGE. (NLIO ERR
2170)
2171
MESSAGE
LANGUAGE WAS NOT MEA LANGUAGE. (NLIO ERR
2171)
2180
MESSAGE
TERMINAL CANNOT BE OPENED WITH MEA LANGUAGE.
(NLIO ERR 2180)
2201
MESSAGE
OP CAPABILITY IS REQUIRED. (NLIO ERR 2201) OP
capability is required to specify an STDIN other than your
own. You currently do not have OP capability. Check the
ldev, or contact your System Manager to extend your
capabilities.
2300
MESSAGE
MISSING MESSAGE CATALOG FILE =
NLIOCAT.PUB.SYS. (NLIO ERR 2300) The message
catalog for the NLIOUTIL program is missing. Contact
your System Manager to locate the message catalog.
2301
MESSAGE
MISSING "NLIODEF.PUB.SYS FILE". (NLIO ERR
2301)
2
MESSAGE
Too many parameters were given for this
command. (parserr 02)
3
MESSAGE
Too many subparameters were given for this
parameter. (parserr 03)
4
MESSAGE
This parameter must have a value. (parserr
04)
6
MESSAGE
This is not a valid option for this command.
(parserr 06)
7
MESSAGE
This is not a valid keyword for this command.
(parserr 07)
8
MESSAGE
This duplicate specification overrides
previous specification. (parswarn 8)
Parser
(parserr)
108
Chapter 3
Error Messages Viii C 3
Parser
9
MESSAGE
The parser output buffer has overflowed.
(parserr 09)
10
MESSAGE
An integer value between -2147483648 and
2147483647 expected. (parserr 10)
11
MESSAGE
This value is not valid for this parameter.
(parserr 11)
12
MESSAGE
Invalid prompt string construct in column !.
(parserr 12)
13
MESSAGE
The ! and ! parameters may not be specified
together. (parserr 13)
14
MESSAGE
Subparameter # ! of the ! parameter is
required. (parserr 14)
15
MESSAGE
The ! parameter is required. (parserr 15)
16
MESSAGE
! and ! may not be specified together.
(parserr 16)
17
MESSAGE
This option has been specified more than
once. (parswarn 17)
20
MESSAGE
Semantic stack overflow. Parser internal
error. (parserr 20)
21
MESSAGE
Semantic stack underflow. Parser internal
error. (parserr 21)
22
MESSAGE
A command may not have more than 9
continuation lines. (parserr 22)
23
MESSAGE
A command name may not exceed 16 characters.
(parserr 23)
24
MESSAGE
A command line may not exceed 280 characters.
(parserr 24)
33
MESSAGE
A control character has been detected here.
(parserr 33)
34
MESSAGE
This string does not have a terminator.
(parserr 34)
35
MESSAGE
This character is not a valid delimiter.
(parserr 35)
36
MESSAGE
Expected a ! to terminate this string.
(parserr 36)
37
MESSAGE
Command contains too many parameters — parser
overflow. (parserr 37)
38
MESSAGE
The parser's output buffer has overflowed.
(parserr 38)
45
MESSAGE
This not a valid suboption for this option.
Chapter 3
109
Error Messages Viii C 3
Parser
(parserr 45)
46
MESSAGE
Too many UDC parameters have been specified.
(parserr 46)
48
MESSAGE
The forms message must be terminated by a
period. (parserr 48)
49
MESSAGE
Parser internal error (cntl-y). (parserr 49)
50
MESSAGE
Encountered an unexpected error. (parserr 50)
51
MESSAGE
Encountered an unexpected end-of-line.
(parserr 51)
52
MESSAGE
Encountered an unexpected left parenthesis.
(parserr 52)
53
MESSAGE
Encountered an unexpected right parenthesis.
(parserr 53)
54
MESSAGE
Encountered an unexpected comma. (parserr 54)
55
MESSAGE
Encountered an unexpected period. (parserr
55)
56
MESSAGE
Encountered an unexpected slash. (parserr 56)
57
MESSAGE
Encountered an unexpected semicolon. (parserr
57)
58
MESSAGE
Encountered an unexpected equals sign.
(parserr 58)
59
MESSAGE
Encountered an unexpected special token.
(parserr 59)
60
MESSAGE
Encountered an unexpected string. (parserr
60)
61
MESSAGE
Encountered an unexpected word. (parserr 61)
62
MESSAGE
Encountered an unexpected ci syntax token.
(parserr 62)
63
MESSAGE
Encountered an unexpected data syntax token.
(parserr 63)
64
MESSAGE
Encountered an unexpected group token.
(parserr 64)
65
MESSAGE
Encountered an unexpected udc header token.
(parserr 65)
66
MESSAGE
Encountered an unexpected js syntax token.
(parserr 66)
67
MESSAGE
Encountered an unexpected logon name token.
(parserr 67)
68
MESSAGE
Encountered an unexpected MPE/iX syntax
110
Chapter 3
Error Messages Viii C 3
Parser
token. (parserr 68)
69
MESSAGE
Encountered an unexpected special token.
(parserr 69)
70
MESSAGE
Encountered an unexpected udc syntax token.
(parserr 70)
71
MESSAGE
Encountered an unexpected vs name token.
(parserr 71)
72
MESSAGE
Encountered an unexpected less than token.
(parserr 72)
73
MESSAGE
Encountered an unexpected lt/eq token.
(parserr 73)
74
MESSAGE
Encountered an unexpected not equal token.
(parserr 74)
75
MESSAGE
Unknown token. (parserr 75)
76
MESSAGE
Encountered an unexpected greater than token.
(parserr 76)
77
MESSAGE
Encountered an unexpected gt/eq token.
(parserr 77)
78
MESSAGE
Encountered an unexpected AND token. (parserr
78)
79
MESSAGE
Encountered an unexpected NOT token. (parserr
79)
80
MESSAGE
Encountered an unexpected OR token. (parserr
80)
81
MESSAGE
Encountered an unexpected left bracket token.
(parserr 81)
82
MESSAGE
Encountered an unexpected right bracket
token. (parserr 82)
83
MESSAGE
Encountered an unexpected file reference
token. (parserr 83)
100
MESSAGE
Expected the next parameter or an option.
(parserr 100)
105
MESSAGE
Expected the next positional parameter.
(parserr 105)
110
MESSAGE
Expected a keyword parameter or an option.
(parserr 110)
115
MESSAGE
Expected a value for this keyword. (parserr
115)
120
MESSAGE
Expected an option. (parserr 120)
Chapter 3
111
Error Messages Viii C 3
Parser
125
MESSAGE
Expected a comma or a semicolon. (parserr
125)
130
MESSAGE
Expected account name. (parserr 130)
140
MESSAGE
Expected a file reference caret character.
(parserr 140)
201
MESSAGE
Value must be >= 0 and <= 65535. (parserr
201)
202
MESSAGE
Undefined variable name. (parserr 202)
203
MESSAGE
String expression is too complicated.
(parserr 203)
204
MESSAGE
String and integer operands may not be mixed
like this. (parserr 204)
205
MESSAGE
String values may not exceed 255 characters.
(parserr 205)
206
MESSAGE
Invalid operation for strings. (parserr 206)
207
MESSAGE
Division by zero. (parserr 207)
208
MESSAGE
Integer value greater than 65535. (parserr
208)
209
MESSAGE
Integer value less than 0. (parserr 209)
221
MESSAGE
Invalid access mode. (parserr 221)
222
MESSAGE
Invalid accessor. (parserr 222)
223
MESSAGE
The ! access mode is not valid for this
command. (parserr 223)
224
MESSAGE
The ! accessor is not valid for this command.
(parserr 224)
225
MESSAGE
The ! access mode must be on the right side of
the colon. (parserr 225)
226
MESSAGE
The ! accessor must be on the left side of the
colon. (parserr 226)
250
MESSAGE
Invalid prompt string. Application internal
error. (parserr 250)
251
MESSAGE
This comment must be terminated by a right
brace. (parserr 251)
252
MESSAGE
Parameter is too long. (parserr 252)
253
MESSAGE
The first character must be alphabetic.
(parserr 253)
254
MESSAGE
Numeric characters are not allowed. (parserr
254)
112
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
255
MESSAGE
Invalid use of wordchar. (parserr 255)
256
MESSAGE
Special characters are not allowed. (parserr
256)
257
MESSAGE
Parser internal error — delims array out of
sync (parserr 257)
258
MESSAGE
Missing left brace. (parserr 258)
259
MESSAGE
Duplicate specification of an access mode.
(parserr 259)
260
MESSAGE
Duplicate specification of an accessor.
(parserr 260)
261
MESSAGE
Can't have alpha characters. (parserr 261)
262
MESSAGE
This value is not valid for this parameter.
(parserr 262)
265
MESSAGE
Parameter not found in prompt string.
(parserr 265)
270
MESSAGE
No command name was found. (parserr 270)
275
MESSAGE
Integer parameters may not have values
greater than 2147483647 (parserr 275)
280
MESSAGE
Integer parameters may not have values less
than -2147483648 (parserr 280)
285
MESSAGE
Parameter number ! must be specified.
(parserr 285)
290
MESSAGE
"KEYWORD=" specification invalid, command has
no keywords. (parserr 290)
Port (IPC) Facility
(Subsystem 122)
10
15
Chapter 3
MESSAGE
The procedure attempted an OPEN_PORT to
become the process server for the port, but
another process has already made itself the
process server.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted an OPEN_PORT to
become the process server for the port, but
113
Error Messages Viii C 3
Port (IPC) Facility
the server type for the port is not a process
server.
20
21
30
40
50
105
114
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to queue a message
frame (via a SEND primitive) to a port that
is already queued to a port (either this port
or some other port), or on the free list of a
message port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt has been made to release a message
frame back to the message pool (via
REL_MSG_FRAME), but the frame is still queued
to a port (either this port or some other
port).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified address, which must be a
message frame, is not a valid message frame
for the specified port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
One or more of the specified parameters are
bad or inconsistent.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified index for the wait queue entry
is not a valid index.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified control item (for PORT_CONTROL)
is not available while executing on the ICS.
CAUSE
Same as message content.
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
110
115
120
121
122
123
Chapter 3
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to acquire a counting
semaphore port with a global port number
(must access this type of semaphore port with
a local port number).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified value for a port's message
threshold is not valid (must be a positive
number greater than zero).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified port number for the PFP port is
either that of a nonexistent port or a local
port number.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to create a resident
port and associate it with a non-resident PFP
port (PFP port must have same attributes as
the port).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified PFP port number is a valid port
number, but the port it is associated with is
not a PFP's port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure is trying to create a PFP or
associate a new port with a PFP, but is
unable to send/receive the initiation message
to/from the PFP.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
115
Error Messages Viii C 3
Port (IPC) Facility
124
125
126
127
128
129
130
131
116
MESSAGE
The PFP class to associate the new port with
is invalid.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified name for the PFP's port can not
be found in the port directory.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to purge a PFP's port via
(PURGE_PORT); must use KILL_PFP.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to associate a new port with a PFP
that is currently terminating.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error was encountered when attempting to
activate a new PFP process.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to kill one of the
standard (i.e., non-class 4) PFPs.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An innternal error occurred - the initial
message sent to a PFP so that it can perform
its initialization is not of the proper
message format.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error was encountered when performing a
name look-up for a PFP port's name.
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
132
160
165
170
171
172
Chapter 3
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to purge (via
PURGE_PORT) one of a process's standard
ports; these ports may only be purged via a
process termination.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to perform a SEND
request to a subqueue that is not enabled and
also dormant.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to create a semaphore
port with emergency messages.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error (from TABLE MGT) was encountered
when trying to obtain a message frame from
the port's message pool. Usually, the error
is due to the table (pool) being empty.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error (from TABLE MGT) was encountered
while trying to obtain an entry from the port
FREEZE DESCRIPTOR TABLE. Usually, the error
is due to the table being empty. (This table
is used for non-resident ports that are
accessed on the ICS).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error (from TABLE MGT) was encountered
when obtaining an entry from either the
resident or non-resident port descriptor
tables. Usually, the error is due to being
117
Error Messages Viii C 3
Port (IPC) Facility
out of table entries.
173
174
175
176
180
190
118
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error (from TABLE MGT) was encountered
when trying to obtain a table entry from a
process's local port DESCRIPTOR TABLE.
Usually, the error is due to the table being
empty.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error (from TABLE MGT) was encountered
when creating a process's local port
DESCRIPTOR TABLE. The table is created when
the first local port number is allocated.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Only expect a local port number in this
context.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error (from TABLE MGT) was encountered
when trying to obtain an entry from the STD
PROCESS PORTS TABLE. Usually, the error is
due to the table being empty. Entries from
this table are obtained during process
creation.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt
there were
subqueues,
wait for a
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to manipulate an EMPTY WAIT QUEUE
to receive a message from a port;
no messages on any enabled
and the process did not wish to
message to arrive.
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
LIST.
191
200
210
235
240
241
260
Chapter 3
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified WAIT ENTRY was not found in the
WAIT queue.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Internal status was never returned to a
caller.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to acquire exclusive access to the
specified semaphore port when the process
already owns the semaphore port in a shared
mode.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to CREATE or OPEN a
port with a fixed global port number, but the
global port descriptor for the specified port
has already been
allocated.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified access is not available yet.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified access is no longer supported.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Internal status was never returned to the
caller.
119
Error Messages Viii C 3
Port (IPC) Facility
261
262
270
280
285
300
120
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Internal status was never returned to the
caller.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Incompatible port access. Attempt to
FREEZE/UNFREEZE a port or change either of
the auxiliary data areas; the port descriptor
does not have a FREEZE descriptor. Attempt to
WAIT_ON_PORTS for port(s) that do not have
process servers.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to ACCESS a port's message POOL
while on the ICS when the POOL was LOCKED in a
process environment (before control was
transferred to the ICS).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to access a
non-resident port that was also illegal to
access from the ICS. Note, that SEND requests
will be delayed (and not produce this error);
any other port primitive will result in this
error.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
A process was awoken from the WAIT queue, but
the reply message sent does not match that
which was expected (i.e., does not match the
information in the WAIT queue entry).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
When creating a port and specifying an
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
initialization buffer for the server private
data area, the initialization length was
larger than the entire private data area.
342
343
344
365
373
374
Chapter 3
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The item value specified (via PORT_CONTROL)
for the item type is not valid.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The item number passed to PORT_CONTROL is not
valid.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to use PORT_CONTROL
to delete PROCESS_EXECUTABLE options from a
port, but the port does not have
ICS_EXECUTABLE options either.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The info item passed to PORT_INFO/POOL_INFO
is not valid.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The value used for the process interrupt
level (to CAUSE_PROCESS_INTERRUPT) is not
valid.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The interrupt level (passed to
CAUSE_PROCESS_INTERRUPT) is illegal for a CM
process interrupt handler.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
121
Error Messages Viii C 3
Port (IPC) Facility
375
380
390
400
410
420
450
122
MESSAGE
The value used for the process interrupt type
(to CAUSE_PROCESS_INTERRUPT) is not defined,
or illegal in this context (other process
interrupt manipulation
primitives).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure specified a subqueue location
that does not have a message frame queued, or
specified an invalid search location to
FIND_MSG.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure specified a message frame that
is not currently queued to the specified port
(from RETRIEVE_MSG).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure specified the MSG_FRAME option
to a port-receive primitive, and then
proceeded to not specify the MSG parameter to
get the message frame
address returned.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempte to create a semaphore
port with MSG_OPTIONS not as the empty set.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
When creating a message pool, the number of
initial messages exceeded the total (maximum)
number of frames requested.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
When creating a message pool, the number of
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
frames to reserve disc space for (for a
non-resident pool) exceeded the total
(maximum) number of frames requested.
460
480
490
500
535
537
Chapter 3
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to create a semaphore
port with port options that are invalid for a
semaphore port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The pattern length (passed to FIND_MSG) was
not valid; must be positive and non-zero.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified PIN was not a valid process
number.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified address does not point to a
message pool.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Either an illegal fixed port number was
specified when creating a port, or the port
number is not valid (i.e., never created or
already returned), but specified for one of
the other port access primitives.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error was encountered when performing a
port directory look-up. The port directory
entry for the specified name is not valid.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
123
Error Messages Viii C 3
Port (IPC) Facility
Representative.
540
560
580
590
600
605
610
124
MESSAGE
The specified port type is invalid, or the
access is inconsistent with the port's type.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified server type is invalid, or the
access is inconsistent with the port's type
of server.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Invalid or inconsistent specification in the
"SERVER_DESC" parameter to CREATE_PORT.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error was encountered from FINDLOCALITY.
This routine is called during port creation
for a port whose procedure server will
execute on the ICS, but whose server code is
not memory-resident.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Either the maximum number of possible
subqueues has been exceeded, or the subqueue
specified exceeds the maximum configured for
the specified port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified info. item is not available to
access while on the ICS.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
It is illegal to access a port via a local
port number while on the ICS.
CAUSE
Same as message content.
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
620
630
650
651
680
710
Chapter 3
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The process interrupt level being accessed in
not available to the caller since it exceeds
the caller's execution ring level.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
When creating a non-resident PORT/POOL that
is also ICS_SENDABLE, the message size for
the pool is greater than what the port
facility could handle if the message had to
be delayed.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified port server's PFP priority is
not within the valid range of - 0..30.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified ICS priority for an
ICS_EXECUTABLE server is not within the valid
range - 0..31.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The number of subqueues requested to
configure for the new port is not valid; must
be between 1 and 32.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure specified a message frame
access to a port that is illegal to use
frames with (i.e., the port is not a message
port).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
125
Error Messages Viii C 3
Port (IPC) Facility
720
730
750
760
770
775
776
126
MESSAGE
A message at the specified subqueue location
was not found on an enabled subqueue.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
No message was found on the specified port
that matched the specified pattern (and
search conditions).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The message length specified for a SEND
PRIMITIVE exceeds the maximum length for its
message pool, or the length specified for a
CAUSE_PROCESS_INTERRUPT message exceeds the
maximum.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The message length specified to either a
SEND/RECEIVE PRIMITIVE or to
CAUSE_PROCESS_INTERRUPT must be a positive
number of bytes.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to send a non-zero
length message, but the pointer to the
message is nil.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure requested to use a reserved
message frame, but none were ever reserved.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure requested to use a reserved
message frame, but there are no reserved
frames currently available (i.e., the
reserved list is currently empty).
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
778
779
780
785
790
791
Chapter 3
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The mode for the specified process interrupt
handler is not valid; must be either NM or
CM.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to delete pending
process interrupts for the calling process,
but no process interrupts of the requested
type were found to delete.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to enable a port
(with a process server) to notify the server
via a process interrupt, but the PLABEL for
the process interrupt handler has not been
defined yet.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error was detected when trying to block
the calling process onto the specified wait
queue.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to access a port with
an invalid port number (i.e., the port for
the port number was never defined, or already
purged, or not within the legal range of
possible port numbers).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to convert a local
port number for the specified PIN into its
equivalent global port number; either the PIN
127
Error Messages Viii C 3
Port (IPC) Facility
is invalid, or the procedure currently does
not have that local port number defined.
824
825
826
827
828
830
128
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to UNFREEZE (via
PORT_CONTROL) a port that was not previously
frozen.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to CREATE a port with
ICS_ACCESSIBLE option and associate it with a
message pool that does not have that option.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure returned an internal error when
deleting a delayed message for a port (via
DELETE_DELAYED_MSG).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure returned an internal error when
trying to delete a delayed message for a port
(via DELETE_DELAYED_MSG).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to delete delayed messages for a
port while on the ICS.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to create a port with ICS_SENDABLE
option and associate it with a message pool
that does not have that option.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
834
835
836
840
841
850
851
Chapter 3
MESSAGE
An attempt to create a port with
ICS_ACCESSIBLE option without MEMORY_RESIDENT
option.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to create a port with
MEMORY_RESIDENT option and associate it with
a message pool that does not have the option.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to change a port's auxiliary data
area(s) while the port is currently frozen.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to create a port with a name that
has already been used for another port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to open a named port, but the name
has not been defined in the port directory
(i.e., not created yet).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to perform a receive primitive on
a port when caller is not the port's server,
or an attempt to purge a port when the caller
is not the port owner, or an attempt to
give/release ownership when not the port
owner.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An error was encountered from the symbol
TABLE MANAGEMENT routines when accessing the
port directory.
129
Error Messages Viii C 3
Port (IPC) Facility
855
856
880
885
890
900
130
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to open a port; the port was
created with exclusive access, or the caller
requested exclusive access and another
process already opened it, or an attempt to
add exclusive access (via PORT_CONTROL) when
others have it opened.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to access a port, but there is a
purge pending (i.e., a PURGE_PORT been
requested for the specified port).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to release a semaphore port that
the caller does not own.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to use a SEND primitive specifying
RESERVRD_FRAME option, and the address of the
send buffer is already a message frame.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to perform a NON-SEND port
primitive to a port that is not legal to
access while on the ICS (i.e., is not
resident).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to acquire a ranked semaphore port
that is lower rank than the process currently
holds (i.e., acquiring ranked semaphore ports
out of order).
CAUSE
Same as message content.
Chapter 3
Error Messages Viii C 3
Port (IPC) Facility
905
910
915
920
950
960
Chapter 3
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to acquire a semaphore port that
has been marked as unavailable (via
PORT_CONTROL).
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to acquire a semaphore port that
is owned by another process, and the caller
did not wish to wait.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The previous owner(s) of a semaphore port
terminated while still the owner. The current
call to acquire the semaphore port was
successful; just a warning that previous
owner(s) were not tidy.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to access a semaphore port while
on the ICS.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to acquire a semaphore port with
shared access, but the semaphore port was not
configured to allow shared access.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An attempt to acquire a semaphore port with
shared access, but the caller used a global
port number; must use a local port number to
successfully acquired shared access to a
semaphore port.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
131
Error Messages Viii C 3
Port (IPC) Facility
990
1000
1010
1020
1030
1040
1050
132
MESSAGE
A process blocked on a port WAIT (via a
receive port primitive) and requested to be
notified if a process interrupt occurred
before the block was satisfied. Signifies
that the process interrupt occurred first;
receive not satisfied.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
An unexplained AWAKE of the calling process
from the WAIT queue has occurred.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The port primitive has not completed due to
the specified time out occurring first.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
A nil pointer was used as a pointer to a
message pool.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
Only local port numbers are expected to be
passed to this port primitive.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The port number passed into a port primitive
was the nil port number. The only primitive
that accepts this value is SEND_MSG.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The specified class for the semaphore to be
initialized is not within the valid range.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
Chapter 3
Error Messages Viii C 3
Private Volumes
1051
1060
1061
MESSAGE
The type of semaphore specified for this
semaphore record initialization is not within
the valid range.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to AWAKEN a process
from waiting on its standard signal port (via
IPC_WAIT_PROCESS), but the process was not
currently waiting on its standard signal
port; the AWAKE was sent anyway.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
MESSAGE
The procedure attempted to AWAKEN a process
from blocking on its standard signal port,
but the process was not waiting on the
event(s) specified; process was blocked for a
different event on the signal port; AWAKE was
sent anyway.
CAUSE
Same as message content.
ACTION
Take a system dump and call your Hewlett-Packard
Representative.
Private Volumes
(PVERR)
20
MESSAGE
PRIVATE VOLUMES FACILITY NOT INVOKED (PVERR
20)
21
MESSAGE
OPERATOR REJECTED MOUNT REQUEST (PVERR 21)
22
MESSAGE
INSUFFICIENT DRIVES AVAILABLE TO MOUNT VOLUME
SET (PVERR 22)
23
MESSAGE
VOLUME SET TEMPORARILY IN USE BY SYSTEM
(PVERR 23)
24
MESSAGE
GROUP IN VOLUME SET SPECIFICATION DOES NOT
EXIST (PVERR 24)
25
MESSAGE
ACCOUNT IN VOLUME SET SPECIFICATION DOES NOT
EXIST (PVERR 25)
Chapter 3
133
Error Messages Viii C 3
Private Volumes
26
MESSAGE
VOLUME SET IS NOT PHYSICALLY MOUNTED ON
SYSTEM (PVERR 26)
27
MESSAGE
VOLUME SET/CLASS DEFINITION DOES NOT EXIST
(PVERR 27)
28
MESSAGE
NO HOME VOLUME SET DESIGNATED FOR ! (PVERR
28)
29
MESSAGE
GROUP IN HOME VOLUME SET SPECIFICATION DOES
NOT EXIST (PVERR 29)
30
MESSAGE
ACCOUNT IN HOME VOLUME SET SPECIFICATION DOES
NOT EXIST (PVERR 30)
31
MESSAGE
GROUP DOES NOT EXIST ON VOLUME SET (PVERR 31)
32
MESSAGE
ACCOUNT DOES NOT EXIST ON VOLUME SET (PVERR
32)
33
MESSAGE
VOLUME SET ALREADY MOUNTED BY THIS USER
(PVERR 33)
34
MESSAGE
USER DOES NOT HAVE VOLUME SET MOUNTED (PVERR
34)
35
MESSAGE
OPERATOR DISMOUNT PENDING FOR VOLUME SET
(PVERR 35)
36
MESSAGE
DOWN PENDING FOR DISC CONTAINING MEMBER
VOLUME (PVERR 36)
37
MESSAGE
REQUEST FOR DIFFERENT MEMBERS THAN CURRENTLY
IN USE (PVERR 37)
38
MESSAGE
MUST USE HOME VOLUME SPECIFICATION IN THIS
CONTEXT (PVERR 38)
39
MESSAGE
CANNOT USE HOME VOLUME SET SPECIFICATION IN
THIS CONTEXT (PVERR 39)
41
MESSAGE
VOLUME SET CURRENTLY MOUNTED WITH DIFFERENT
GENERATION (PVERR 41)
42
MESSAGE
MOUNT ON BEHALF OF ! ALREADY PERFORMED BY
THIS USER (PVERR 42)
43
MESSAGE
MOUNT ON BEHALF OF ! NEVER PERFORMED BY THIS
USER (PVERR 43)
44
MESSAGE
UNABLE TO EXECUTE COMMAND DUE TO INSUFFICIENT
STACK SPACE (PVERR 44)
50
MESSAGE
MOUNTED VOLUME TABLE ERROR (SYSTEM PROBLEM)
(PVERR 50)
51
MESSAGE
VOLUME SET USER TABLE ERROR (SYSTEM PROBLEM)
(PVERR 51)
52
MESSAGE
DIRECTORY ERROR (SYSTEM PROBLEM) (PVERR 52)
134
Chapter 3
Error Messages Viii C 3
Private Volumes
53
MESSAGE
NAME SEGMENT (INTERNAL PROBLEM) FULL (PVERR
53)
54
MESSAGE
PV USER SEGMENT (INTERNAL PROB.) FULL (PVERR
54)
60
MESSAGE
LDEV# ! IS OUT OF RANGE (PVERR 60)
61
MESSAGE
LDEV# ! IS NOT CONFIGURED (PVERR 61)
62
MESSAGE
LDEV# ! IS NOT A DISC (PVERR 62)
63
MESSAGE
LDEV# ! IS NOT A REMOVABLE DISC (PVERR 63)
64
MESSAGE
LDEV# ! IS NOT AN ALLOWED REMOVABLE
DISC-INVALID SUBTYPE (PVERR 64)
65
MESSAGE
LDEV# ! IS NOT IN THE USER DISC DOMAIN (PVERR
65)
66
MESSAGE
LDEV# ! IS NOT ON-LINE (PVERR 66)
67
MESSAGE
LDEV# ! IS A SERIAL DISC (PVERR 67)
68
MESSAGE
LDEV# ! IS RESERVED FOR USE BY SYSTEM (PVERR
68)
69
MESSAGE
LDEV# ! IS DOWN-ED (PVERR 69)
70
MESSAGE
LDEV# ! HAS DOWN PENDING (PVERR 70)
71
MESSAGE
LDEV# ! IS IN USE BY PRIVATE VOLUMES (PVERR
71)
72
MESSAGE
INAPPROPRIATE OPERATION FOR A FOREIGN DISC
(PVERR 72)
73
MESSAGE
DEVICE IS WRITE PROTECTED *** (PVERR 73)
96
MESSAGE
UNREADABLE DISK LABEL ON LDEV #! (PVERR 96)
98
MESSAGE
NO ROOM IN VOLUME TABLE FOR LDEV #! (PVERR
98)
99
MESSAGE
NO ROOM IN VOLUME TABLE FOR LDEV #! (PVERR
99)
100
MESSAGE
** FUNCTION ABORTED ** (PVERR 100)
101
MESSAGE
UNRECOGNIZED FUNCTION (PVERR 101)
102
MESSAGE
INVALID TRACK DISPOSITION (PVERR 102)
103
MESSAGE
UNRECOGNIZED KEYWORD (PVERR 103)
104
MESSAGE
NO VOLUME SET CURRENTLY SPECIFIED (PVERR 104)
105
MESSAGE
LDEV# ! NOT DOWNED (PVERR 105)
106
MESSAGE
LDEV# ! NOT DOWNED OR SCRATCH (PVERR 106)
107
MESSAGE
VOLUME SPECIFIED IS NOT A MEMBER OF THE
VOLUME SET (PVERR 107)
Chapter 3
135
Error Messages Viii C 3
Private Volumes
108
MESSAGE
SUBTYPE INCONSISTENCY BETWEEN DEVICES
SPECIFIED (PVERR 108)
109
MESSAGE
PACK SIZE INCONSISTENCY BETWEEN DEVICES
SPECIFIED (PVERR 109)
110
MESSAGE
ATTEMPTED TO COPY TO A BAD TRACK (PVERR 110)
111
MESSAGE
NO SUSPECT TRACKS FOUND (PVERR 111)
112
MESSAGE
NO ALTERNATE TRACKS AVAILABLE (PVERR 112)
113
MESSAGE
TRACK NOT REASSIGNED (PVERR 113)
114
MESSAGE
TRACK IN RESERVED AREA - MUST REFORMAT PACK
(PVERR 114)
115
MESSAGE
INVALID NUMERIC VALUE FOR KEYWORD PARAMETER
(PVERR 115)
116
MESSAGE
VOLUME NAME MORE THAN EIGHT CHARACTERS IN
LENGTH (PVERR 116)
117
MESSAGE
VOLUME SET NAME MORE THAN EIGHT CHARACTERS IN
LENGTH (PVERR 117)
118
MESSAGE
KEYWORD IS MORE THAN EIGHT CHARACTERS IN
LENGTH (PVERR 118)
119
MESSAGE
VOLUME NAME HAS NON-ALPHA LEADING CHARACTER
(PVERR 119)
120
MESSAGE
VOLUME SET NAME HAS NON-ALPHA LEADING
CHARACTER (PVERR 120)
121
MESSAGE
KEYWORD HAS NON-ALPHA LEADING CHARACTER
(PVERR 121)
122
MESSAGE
VOLUME NAME CONTAINS A SPECIAL CHARACTER
(PVERR 122)
123
MESSAGE
VOLUME SET NAME CONTAINS A SPECIAL CHARACTER
(PVERR 123)
124
MESSAGE
KEYWORD CONTAINS A SPECIAL CHARACTER (PVERR
124)
125
MESSAGE
NO PARAMETERS ALLOWED FOR THIS FUNCTION
(PVERR 125)
126
MESSAGE
MISSING NON-OPTIONAL PARAMETER (PVERR 126)
127
MESSAGE
NON-NUMERIC CHARACTER IN LDEV SPECIFICATION
(PVERR 127)
128
MESSAGE
INVALID LDEV VALUE (PVERR 128)
129
MESSAGE
TOO MANY NAMES IN VOLUME SET SPECIFICATION
(PVERR 129)
130
MESSAGE
MISSING KEYWORD PARAMETER VALUE (PVERR 130)
136
Chapter 3
Error Messages Viii C 3
Private Volumes
131
MESSAGE
UNEXPECTED DELIMITER (PVERR 131)
132
MESSAGE
UNEXPECTED PARAMETER (PVERR 132)
133
MESSAGE
FORMAT SWITCH INSIDE DISC UNIT OFF (PVERR
133)
134
MESSAGE
Problem with DTT or DFSM (PVERR 134)
135
MESSAGE
ILLEGAL CYLINDER NUMBER — TRY AGAIN (PVERR
135)
136
MESSAGE
ILLEGAL HEAD NUMBER — TRY AGAIN (PVERR 136)
137
MESSAGE
DTT TABLE IS FULL — ENTRY NOT ADDED (PVERR
137)
138
MESSAGE
LDEV ! IS NOT IN VOLUME TABLE — TRY SWITCHING
DISC UNIT OFFLINE, THEN ONLINE (PVERR 138)
139
MESSAGE
DISC VOLUME SPECIFIED IS NOT MOUNTED — MAY BE
PART OF A VOLUME CLASS THAT'S NOT MOUNTED
(PVERR 139)
140
MESSAGE
WARNING: VOLUME ALREADY ! (PVWARN 140)
141
MESSAGE
WARNING: SUSPECT TRACK IN ALTERNATE AREA
(PVWARN 141)
142
MESSAGE
WARNING: SUSPECT TRACK IN RESERVED AREA
(PVWARN 142)
143
MESSAGE
WARNING: ! SUSPECT TRACKS DETECTED (PVWARN
143)
144
MESSAGE
WARNING: TRACK IS ALREADY IN DTT — NOT ADDED
(PVWARN 144)
145
MESSAGE
WARNING: THIS FUNCTION DOESN'T WORK UNLESS
ENTIRE VOLUME SET IS MOUNTED (PVWARN 145)
146
MESSAGE
WARNING: RECOVER CHANGED TO COND ONLY — MORE
THAN ONE USER/OPEN TEMPORARY FILES/OPEN
$OLDPASS (PVWARN 146)
147
MESSAGE
WARNING: RECOVER CHANGED TO COND ONLY —
SYSTEM VOLUME << YOU MUST UPD/COOL/COLD-START
FOR SYSTEM VOLUMES >> (PVWARN 147)
148
MESSAGE
FILE ! WAS PURGED (PVWARN 148)
149
MESSAGE
THIS FUNCTION REQUIRES: 1) ONLY ONE USER 2)
NO TEMP FILES 3) NO OPEN $OLDPASS (PVWARN
149)
150
MESSAGE
THE DISC LABEL (SECTOR 0) COULDN'T BE READ ON
LDEV ! — THE PACK IS PROBABLY UNFORMATTED
(PVWARN 150)
151
MESSAGE
PHYSICAL TRACK ! : HEAD ! DELETED (MADE
Chapter 3
137
Error Messages Viii C 3
Private Volumes
INVISIBLE) (PVWARN 151)
155
MESSAGE
Error* Could not get working space to begin
RECOVER. Allocation will be disabled on LDEV
!. Try again later (PVERR 155)
156
MESSAGE
Error* Fatal error while trying to RECOVER must re-INIT (PVERR 156)
157
MESSAGE
Beginning RECOVER (PVWARN 157)
158
MESSAGE
Finished RECOVERing files, beginning CONDense
(PVWARN 158)
159
MESSAGE
Error* File ! has disc space that has already
been allocated to another file. Will remove
the file from the Directory (PVERR 159)
160
MESSAGE
Warning* File not recovered and marked as bad
in the Directory *continuing* (PVWARN 160)
161
MESSAGE
Error* I/O error on DFSM while trying to
RECOVER - cannot RECOVER this disc must
re-INIT (PVERR 161)
162
MESSAGE
Error* I/O error on reading/writting the disc
label/DTT - could not begin to RECOVER (PVERR
162)
163
MESSAGE
Error* I/O error on reading disc label could not begin to COND (PVERR 163)
164
MESSAGE
Error* File ! is open. Quit RECOVERing - must
re-COND with RECOVER option after closing the
file (PVERR 164)
165
MESSAGE
FORMAT ABORTED — MORE THAN ! BAD TRACKS
(PVERR 165)
166
MESSAGE
FUNCTION ABORTED — ILLEGAL OR UNSUPPORTED
SUBTYPE (PVERR 166)
167
MESSAGE
FUNCTION ABORTED — SUSPECT TRACKS ON LDEV !
(AMONG OTHERS) (PVERR 167)
168
MESSAGE
Error* Deleted tracks in Disc Free Space
Map/Directory - could not begin to RECOVER
(PVERR 168)
169
MESSAGE
Error* I/O error encountered while trying to
RECOVER this disc - must re-INIT (PVERR 169)
171
MESSAGE
DIRPURGE FAILED WITH PARM=!,PARM=! ON FILE !
(PVERR 171)
172
MESSAGE
MUSTOPEN FAILED ON FILE ! (PVERR 172)
173
MESSAGE
FLCLOSE (DELETE) FAILED ON FILE ! (PVERR 173)
138
Chapter 3
Error Messages Viii C 3
Private Volumes
174
MESSAGE
Warning* Couldn't read file label ldev ! addr
! *continuing* (PVWARN 174)
175
MESSAGE
Warning* Checksum error on file !
*continuing* (PVWARN 175)
176
MESSAGE
Warning: Vinit is being run with a Factory
only entry point. This may compromise system
integrity. (PVWARN 188)
177
MESSAGE
Error* Problem with Disc Free Space Map
(PVERR 177)
178
MESSAGE
Warning* An extent of file ! already
released. Check file (PVWARN 178)
179
MESSAGE
Warning* System logging disabled while
CONDensing (PVWARN 179)
180
MESSAGE
Warning* System logging enabled by CONDense
(PVWARN 180)
181
MESSAGE
Try COND RECOVER(private vol) or Recover Lost
Disc Space (sys disc) (PVWARN 181)
182
MESSAGE
Error* I/O error on Disc Free Space Map
(PVERR 182)
183
MESSAGE
Warning* I/O error on writting file label of
file ! - will mark as bad in the Directory.
*continuing* (PVWARN 183)
184
MESSAGE
Could not begin COND (PVERR 184)
185
MESSAGE
Function aborted but disc and Directory are
not altered (PVERR 185)
186
MESSAGE
Warning* System logging disabled while
processing defective tracks - DTRACK (PVWARN
186)
187
MESSAGE
Warning* System logging enabled by DTRACK
(PVWARN 187)
190
MESSAGE
Error* Could not get working space to INIT
the disc. Try again later (PVERR 190)
191
MESSAGE
Cartridge has run out of spare sectors.
(PVERR 191)
192
MESSAGE
Media is uninitialized. (PVERR 192)
193
MESSAGE
Media has not been Formated. Use 'Format'
command and then use 'Serial' again. (PVERR
193)
194
MESSAGE
You have done a 'Scratch;Reset' operation on
a cartridge that was previously in
'Scratched' state or otherwise unrecognizable
Chapter 3
139
Error Messages Viii C 3
Private Volumes
to MPE/iX. This operation may not be
meaningful. (PVWARN 194)
195
MESSAGE
Cartridge Tapes do not have Defective Sector
Tables. (PVWARN 195)
196
MESSAGE
Unable to read the Disc Label. The following
defective sector information may not be
valid. (PVWARN 196)
197
MESSAGE
Unable to read the Defective Sector Table.
(PVERR 197)
198
MESSAGE
Defective Sector Table is empty. (PVERR 198)
199
MESSAGE
! Defective Sectors Found. (Sector values are
in Decimal.) (PVERR 199)
201
MESSAGE
Unable to read Cartridge Tape Spare Block
Table. (The Attachio call to Initiate Utility
failed. PVERR 201)
202
MESSAGE
The Spare Block Table has no entries. (PVERR
202)
205
MESSAGE
WARNING: OUT OF SPARE TRACKS
SECTOR ! NOT SPARED *CONTINUING* (PVWARN 205)
206
MESSAGE
IO ERROR* STATUS = ! *TERMINATED* (PVERR 206)
209
MESSAGE
Unable to read CS'80 Spare Track Table. (The
Attachio call to Initiate Utility failed.
(PVERR 209)
214
MESSAGE
WARNING: SUSPECT SECTOR IN DIRECTORY AREA
(PVWARN 214)
215
MESSAGE
WARNING: SUSPECT SECTOR IN BIT MAP AREA TRY
COND ldev;RECOVER (PVWARN 215)
216
MESSAGE
WARNING: SUSPECT SECTOR IN BIT MAP DESCRIPTOR
AREA TRY COND ldev;RECOVER (PVWARN 216)
217
MESSAGE
NON-CS80 DEVICE (PVERR 217)
218
MESSAGE
IT IS NOT A SERIAL DISC (PVERR 218)
219
MESSAGE
UNABLE TO READ A GAP TABLE; TRY OPTION "ALL"
(PVERR 219)
220
MESSAGE
NO DATA (PVWARN 220)
221
MESSAGE
UNABLE TO READ SECTOR ! (PVERR 221)
222
MESSAGE
SECTOR ! - END OF DATA
140
Chapter 3
Error Messages Viii C 3
Process Manager
Process Manager
(Subsystem 102)
1
2
3
4
5
6
7
8
9
Chapter 3
MESSAGE
The user lacks process handling capability.
CAUSE
User does not have Process Handling (PH) capability.
ACTION
Relink the program with PH capability.
MESSAGE
A required parameter is missing.
CAUSE
Same as message content.
ACTION
Supply the required parameter.
MESSAGE
The caller does not have access to a VAR
parameter.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
There are insufficient system resources to
create this process.
CAUSE
Same as message content.
ACTION
Take a system memory dump for analysis.
MESSAGE
An illegal item number was passed to
CREATEPROCESS.
CAUSE
Same as message content.
ACTION
Refer to the MPE/iX Intrinsics Reference Manual for legal
item number.
MESSAGE
The specified program file could not be
found.
CAUSE
Same as message content.
ACTION
Use valid program name.
MESSAGE
The program name is invalid.
CAUSE
Same as message content.
ACTION
Use valid program name.
MESSAGE
An illegal entry name was passed.
CAUSE
Same as message content.
ACTION
Use valid entry name.
MESSAGE
The default stack size was used.
CAUSE
Information only.
141
Error Messages Viii C 3
Process Manager
15
16
17
18
19
20
21
40
50
60
142
ACTION
None.
MESSAGE
The specified stack size is insufficient.
CAUSE
Same as message content.
ACTION
Respecify the stack size.
MESSAGE
The loader failed to LOAD the program.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
An illegal priority class was specified.
CAUSE
Same as message content.
ACTION
Refer to the MPE/iX Intrinsics Reference Manual for legal
priority class.
MESSAGE
The procedure failed to open STDIN.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
The procedure failed to open STDLIST.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
The missing ITEMNUM was passed to
CREATEPROCESS.
CAUSE
Same as message content.
ACTION
Refer to the MPE/iX Intrinsics Reference Manual.
MESSAGE
Privileged mode capability is required.
CAUSE
Same as message content.
ACTION
Relink the program with PM capability.
MESSAGE
An invalid action parameter was passed to
NOTIFICATION_LIST.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
There is no process which corresponds with
the specified PIN parameter.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
The specified process is not ALIVE.
CAUSE
Same as message content.
ACTION
None.
Chapter 3
Error Messages Viii C 3
Process Manager
71
80
100
200
210
220
300
1486
1487
Chapter 3
MESSAGE
The PROTECTID to be deleted does not exist.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
There is no process which corresponds with
the specified PROCESSID.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
A notification handler has not been supplied.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
ADOPT INTO failed to move process one to the
child list of process two.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
A process can not move another process to
anywhere except to PROGEN.
CAUSE
Same as message content.
ACTION
Debug the program.
MESSAGE
The ADOPTOR process is not ALIVE or does not
exist.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
A process must be a system process to request
for it to be made a detached process type.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
A trap occurred in the operating system
during system boot.
CAUSE
Same as message content.
ACTION
Take a system dump, and attempt to re-boot the system.
MESSAGE
A trap occurred during process termination.
CAUSE
Same as message content.
ACTION
Take a system dump.
143
Error Messages Viii C 3
Reply Information Table
Reply Information Table
(rit)
1
MESSAGE
INVALID LENGTH. ( rit 1)
2
MESSAGE
NON-NUMERIC CHARACTER. (rit 2)
3
MESSAGE
MUST BE YES, Y, NO, OR N. (rit 3)
4
MESSAGE
MUST BE YES, Y, NO, N, OR A NUMBER. (rit 4)
5
MESSAGE
EXPECTED A NUMERIC RESPONSE. (rit 5)
6
MESSAGE
EXPECTED A NUMERIC PARAMETER. (rit 6)
7
MESSAGE
EXPECTED A YES/Y/NO/N RESPONSE. (rit 7)
8
MESSAGE
EXPECTED A YES/Y/NO/N PARAMETER. (rit 8)
9
MESSAGE
EXPECTED A YES/NO/NUM RESPONSE. (rit 9)
10
MESSAGE
EXPECTED A YES/NO/NUM PARAMETER. (rit 10)
11
MESSAGE
EXPECTED ANOTHER PARAMETER. (rit 11)
12
MESSAGE
THERE ARE NO ALLOCATED ENTRIES. (rit 12)
13
MESSAGE
INVALID ENTRY NUMBER. (rit 13)
14
MESSAGE
ENTRY IS NOT ACTIVE. (rit 14)
15
MESSAGE
REQUEST DOES NOT EXIST. (rit 15)
16
MESSAGE
INVALID RESPONSE SPECIFIED. (rit 16)
17
MESSAGE
SUBQUEUE OF PORT DOES NOT EXIST. (rit 17)
18
MESSAGE
PORT SIZE IS TOO SMALL. (rit 18)
19
MESSAGE
REQUEST HAS BEEN ABORTED BY PROCESS
MANAGEMENT. (rit 19)
20
MESSAGE
INVALID RESPONSE SPECIFIED. (rit 20)
21
MESSAGE
CAN'T WAIT FOR REPLY. (rit 21)
22
MESSAGE
CAN'T LOCK THE RIT. (rit 22)
23
MESSAGE
EXTRA PARAMETER. (rit 23)
24
MESSAGE
COULDN'T FORMAT MESSAGE. (rit 24)
25
MESSAGE
TOO MANY DIGITS. (rit 25)
26
MESSAGE
REPLY IS TOO LONG. (rit 26)
27
MESSAGE
PARAMETER IS TOO LONG. (rit 27)
28
MESSAGE
ONLY NEED REPLY. (rit 28)
29
MESSAGE
CAN'T GET THE JOB/SESSION NUMBER. (rit 29)
144
Chapter 3
Error Messages Viii C 3
Reply Information Table
30
MESSAGE
REQUEST HAS BEEN ABORTED BY AUTOMATIC VOLUME
RECOGNITION. (rit 30)
31
MESSAGE
INVALID CHARACTER IN REPLY PARM. (rit 31)
32
MESSAGE
THIS REPLY HAS ONLY THREE PARAMETERS. (rit
32)
33
MESSAGE
THIS REPLY EXPECTS ONLY TWO PARAMETERS. (rit
33)
34
MESSAGE
REPLY HAS AT LEAST TWO PARAMETERS. (rit 34)
35
MESSAGE
EXPECTED A VALID PIN NUMBER. (rit 35)
36
MESSAGE
UNRECOGNIZED REPLY TYPE ENTERED IN RIT. (rit
36)
37
MESSAGE
SYNTAX OF RESPONSE INCORRECT. (rit 37)
38
MESSAGE
REQUESTING PROCESS UNRECOGNIZED BY RIT. (rit
38)
39
MESSAGE
INVALID PIN SPECIFIED. (rit 39)
40
MESSAGE
INVALID REPLY PARAMETER SPECIFIED. (rit 40)
41
MESSAGE
EXPECTED AN INTEGER BETWEEN ! AND !. (rit 41)
100
MESSAGE
REQUEST REQUIRING OPERATOR REPLY FOR SYS
! HAS BEEN ABORTED. (rit 100)
Chapter 3
145
Error Messages Viii C 3
Reply Information Table
146
Chapter 3
4 Error Messages Viii C 3
Secondary Storage Management
(Subsystem 145)
1
2
3
4
5
6
7
MESSAGE
Disk space is not available.
CAUSE
Same as message content.
ACTION
Purge old files or install a new disk.
MESSAGE
Allocation was disabled on this device.
CAUSE
Same as message content.
ACTION
Enable allocation on this device.
MESSAGE
SECONDARY STORAGE MAP (page allocation) is
out of sync.
CAUSE
Same as message content.
ACTION
Take a system memory dump for debugging purposes.
MESSAGE
Bad device identification was supplied by
caller.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
Invalid unit parameter was supplied by
caller.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
Invalid space limit was detected.
CAUSE
Same as message content.
ACTION
None.
MESSAGE
Invalid SECONDARY STORAGE MAP version was
detected.
CAUSE
Inconsistent version of the operating system.
ACTION
Reinstall the operating system.
147
Error Messages Viii C 3
Serial Disk
8
MESSAGE
SECONDARY STORAGE MAP is not on the page
boundary.
CAUSE
Same as message content.
ACTION
Take a system memory dump for debugging purposes.
Serial Disk
(SDERR)
1
MESSAGE
LDEV #\ Cannot access serial disc using
system buffers (SDERR 1)
2
MESSAGE
LDEV #\ ATTACHIO failure - reading/writing
disc label (SDERR 2)
3
MESSAGE
LDEV #\ Fatal error - serial disc interface
disabled (SDERR 3)
4
MESSAGE
LDEV #\ Invalid length in WRITE'BUFFER
(internal error) (SDERR 4)
5
MESSAGE
LDEV #\ End of tape detected (SDERR 5)
6
MESSAGE
LDEV #\ ATTACHIO failure - reading DTT/DSCT
(SDERR 6)
7
MESSAGE
LDEV #\ Pack overflow - probably ignored EOT
(SDERR 7)
8
MESSAGE
LDEV #\ ATTACHIO failure - writing DTT/DSCT
(SDERR 8)
9
MESSAGE
LDEV #\ Contig and non-contig data mixed in
RECBUFF (SDERR 9)
10
MESSAGE
LDEV #\ Can't call FINDSDISCGAP unless file
is open (SDERR 10)
11
MESSAGE
LDEV #\ FINDSDISCGAP - Block number must be >
0. (SDERR 11)
12
MESSAGE
LDEV #\ ATTACHIO failure - assigning
alternate tracks (SDERR 12)
13
MESSAGE
LDEV #\ ATTACHIO failure - reading Gap Table
(SDERR 13)
14
MESSAGE
LDEV #\ Invalid control code (SDERR 14)
15
MESSAGE
LDEV #\ ATTACHIO failure - writing Gap Table
(SDERR 15)
148
Chapter 4
Error Messages Viii C 3
Serial Disk
16
MESSAGE
LDEV #\ Attempted to write on protected drive
(SDERR 16)
17
MESSAGE
LDEV #\ Out of sync with Gap Table while
reading (SDERR 17)
18
MESSAGE
LDEV #\ Gap Table overflow - probably ignored
EOT (SDERR 18)
19
MESSAGE
LDEV #\ Too many EOFs for this disc (SDERR
19)
20
MESSAGE
LDEV #\ No spare blocks available. (SDERR 20)
21
MESSAGE
LDEV #\ Uninitialized media. (SDERR 21)
22
MESSAGE
LDEV #\ Attempted to read past end of data
(SDERR 22)
23
MESSAGE
LDEV #\ Buffer pointer exceeds buffer
(internal error) (SDERR 23)
24
MESSAGE
LDEV #\ Attempted a Backspace File while at
Load Point. (SDERR 24)
25
MESSAGE
LDEV #\ Attempted to space backward at Load
Point. (SDERR 25)
26
MESSAGE
LDEV #\ Not a serial disc (disc label or
internal error) (SDERR 26)
27
MESSAGE
LDEV #\ Runaway serial disc (access beyond
end of data) (SDERR 27)
28
MESSAGE
LDEV #\ Access beyond end of Gap Table
(internal error) (SDERR 28)
29
MESSAGE
LDEV #\ ATTACHIO failure - writing data.
(SDERR 29)
30
MESSAGE
LDEV #\ Leading/trailing lengths don't match
(corrupt disc) (SDERR 30)
31
MESSAGE
LDEV #\ Tried to overfill SDISC buffer
(internal error) (SDERR 31)
32
MESSAGE
LDEV #\ ATTACHIO failure - reading data
(SDERR 32)
33
MESSAGE
LDEV #\ Corrupt Defective Track/Sector Table
(SDERR 33)
34
MESSAGE
LDEV #\ Not enough memory for data buffers.
(SDERR 34)
35
MESSAGE
LDEV #\ Device not allocated or LDTX
corrupted (SDERR 35)
36
MESSAGE
LDEV #\ Extra data segment too small for this
device. (SDERR 36)
Chapter 4
149
Error Messages Viii C 3
Socket Initialization
37
MESSAGE
LDEV #\ Attempted to write past EOT without
capability (SDERR 37)
38
MESSAGE
LDEV #\ ATTACHIO failure - loading or
unloading (SDERR 38)
39
MESSAGE
LDEV #\ Request aborted externally. (SDERR
39)
40
MESSAGE
LDEV #\ "Write" capability denied by operator
(SDERR 40)
41
MESSAGE
LDEV #\ System or device powerfail. (SDERR
41)
42
MESSAGE
LDEV #\ ATTACHIO failure - setting IR on/off
(SDERR 42)
43
MESSAGE
LDEV #\ Required GPTMOD parameter missing.
(SDERR 43)
Socket Initialization
(sockets)
700
MESSAGE
UNABLE TO CREATE SOCKET NAME REGISTRY DST.
(SOCKETS 700)
701
MESSAGE
UNABLE TO CREATE GLOBAL SOCKET DST. (SOCKETS
701)
702
MESSAGE
UNABLE TO OPEN SOCKET LOGGING; NM ERROR = !.
(SOCKETS 702)
703
MESSAGE
SOCKET REGISTRY: IPCCREATE RETURNED SOCKET
ERROR !. (SOCKETS 703)
709
MESSAGE
UNABLE TO CREATE ADDRESS ALLOCATION DST.
(SOCKETS 709)
Special Routine For Stack Unwind
(Subsystem 103)
9
150
MESSAGE
**** Escape executed outside of TRY block;
CODE = ! (UNWIND 9).
Chapter 4
Error Messages Viii C 3
Special Routine For Stack Unwind
10
11
19
20
21
30
31
Chapter 4
CAUSE
A Pascal "ESCAPE" statement executed but no
TRY/RECOVER block was active anywhere in the runtime
stack.
ACTION
Put a TRY/RECOVER block around the statement which
causes the escape, or remove the "ESCAPE" statement
from your code (if possible).''
MESSAGE
**** Non-unwindable descriptor during Escape;
CODE = ! (UNWIND 10).
CAUSE
The procedure assembled with NO_UNWIND in .callinfo
statement, or there was an internal error.
ACTION
Reassemble the procedure without NO_UNWIND, or
remove the cause of stack UNWIND (Escape trap).
MESSAGE
**** Missing UNWIND descriptor during Escape;
CODE = ! (UNWIND 11).
CAUSE
The procedure assembled with "-U" option, or there was an
internal error.
ACTION
Reassemble the procedure without "-U" option or remove
cause of stack UNWIND (Escape trap).
MESSAGE
**** End-of-stack during non-local GOTO
(UNWIND 19).
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
**** Non-unwindable descriptor found during
non-local GOTO (UNWIND 20).
CAUSE
The procedure assembled with NO_UNWIND in .callinfo
statement, or there was an internal error.
ACTION
Reassemble the procedure with NO_UNWIND, or remove
cause of stack UNWIND (non-local GOTO trap).
MESSAGE
**** Missing UNWIND descriptor during
non-local GOTO (UNWIND 21).
CAUSE
The procedure assembled with '-U' option, or there was as
internal error.
ACTION
Reassemble the procedure without '-U' option, or remove
cause of stack UNWIND (non-local GOTO trap).
MESSAGE
**** No HEAP allocated to release (UNWIND
30).
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
**** HEAP allocation request FAILED. (UNWIND
31).
151
Error Messages Viii C 3
SUSPEND
CAUSE
This is a language construct problem. There is not enough
contiguous HEAP space available, or there was an invalid
HEAP request due to an unitialized variable, bad string
length, etc.
ACTION
Ensure correctness and/or efficiency of the code.
SUSPEND
(SUSPEND ERROR)
20
MESSAGE
INSUFFICIENT CAPABILITY (SUSPEND ERROR 20)
Switch
(Subsystem 100)
20
30
40
50
60
152
MESSAGE
Switch to CM was attempted with an illegal
method.
CAUSE
Bad value in method parameter.
ACTION
Use one of the legal methods.
MESSAGE
Not enough room in CM stack to complete
switch to CM.
CAUSE
Too much room required to move parameter to the CM
stack.
ACTION
Change the program so there is more room left on CM
stack before switching.
MESSAGE
Illegal number of parameters were
encountered.
CAUSE
The parameter specifying the number of parameters to
pass to CM was not within the legal values.
ACTION
Specify a legal value.
MESSAGE
Illegal parameter length was encountered.
CAUSE
Negative or zero length parameter specified.
ACTION
Change parameter length.
MESSAGE
Illegal privileged operation.
Chapter 4
Error Messages Viii C 3
Switch
80
90
110
120
130
150
152
154
156
Chapter 4
CAUSE
A switch was made to CM in METHOD_SPLIT by a user
mode program.
ACTION
Link the program with privilege mode.
MESSAGE
Procedure specification is illegal.
CAUSE
Switch to CM is not by ID, NAME or PLABEL.
ACTION
Fix the PROC parameter.
MESSAGE
Switch to CM was attempted with an illegal ID
number.
CAUSE
The ID number is out of range.
ACTION
Correct the ID number in the program.
MESSAGE
The SWITCH to CM PLABEL HASH TABLE is full.
CAUSE
Table to cache names of dynamically loaded CM
procedures is full.
ACTION
Do not dynamically load so many procedures.
MESSAGE
The CM procedure is not in the CM
procedure/PLABEL HASH TABLE.
CAUSE
The table does not exist or the CM procedure has not been
loaded.
ACTION
Check the table name or load the CM procedure.
MESSAGE
Invalid status parameter.
CAUSE
Either the LOAD_CM_PROCEDURE or the
UNLOAD_CM_PROCEDURE failed.
ACTION
Check procedure name or library search parameters.
MESSAGE
Illegal PROC address in SWITCH to CM.
CAUSE
User does not have the capability to access the area
containing the PROC record (in HPSWITCH TO CM).
ACTION
Put the PROC in an accessible area.
MESSAGE
Illegal parameter record address.
CAUSE
User does not have the capability to access the area
containing the PARMS record (in HPSWITCH TO CM).
ACTION
Put the parameter in an accessible area.
MESSAGE
Illegal parameter address.
CAUSE
User does not have the capability to access a parameter
specified in the PARMS record (in HPSWITCH TO CM).
ACTION
Put the parameter in an accessible area.
MESSAGE
Illegal PD_PARM_TYPE.
153
Error Messages Viii C 3
Switch
158
160
162
164
166
168
200
210
154
CAUSE
An illegal PD_PARM_TYPE was specified in a PARMS
record entry (in HPSWITCH TO CM).
ACTION
Use a legal type.
MESSAGE
Illegal I/O specification.
CAUSE
A reference parameter is not input or output in a reference
parameter in a PARMS record entry (in HPSWITCH TO
CM).
ACTION
Specify input, output or both.
MESSAGE
Illegal function return length.
CAUSE
The function length parameter was negative or greater
than the CM stack (64 Kbytes).
ACTION
Specify a legal length.
MESSAGE
Illegal function return address.
CAUSE
The user does not have the right to access the area
specified by the function address and function length.
ACTION
Specify an accessible area for the function.
MESSAGE
Illegal function return specification.
CAUSE
The function length was > 0 and nil return or address of
length = 0 and NON_NIL return address.
ACTION
Specify a legal function length and address.
MESSAGE
Illegal condition code address.
CAUSE
The user does not have the right to access the address
specified for the return of the condition code.
ACTION
Specify an accessible address for the condition code.
MESSAGE
Illegal status address.
CAUSE
The user does not have the right to access the area used
for the return of the status.
ACTION
Specify a legal address.
MESSAGE
The SWITCH to NM was attempted with an
illegal function type.
CAUSE
The parameter specifying the function type to be returned
was not one of the legal types.
ACTION
Use a legal function type.
MESSAGE
An illegal PARM type was encountered while
switching to NM.
CAUSE
An argument descriptor contained a type that was not
legal.
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
250
270
290
300
330
ACTION
Use a legal type.
MESSAGE
An illegal number of arguments was passed to
SWITCH to NM.
CAUSE
The parameter specifying the number of arguments was
not within the legal range.
ACTION
Use a legal number of arguments.
MESSAGE
The SWITCH to NM method is illegal.
CAUSE
Switch to NM is not by ID, NAME or PLABEL.
ACTION
Use a legal method.
MESSAGE
A FINDPROC error occurred while switching to
NM.
CAUSE
FINDPROC failed to load the procedure requested.
ACTION
Make sure the loader can find your procedure to load.
MESSAGE
The byte reference parameter is not 16-bit
aligned.
CAUSE
SWITCH to CM with METHOD_NOCOPY and a byte
reference parameter that is not 16-bit aligned.
ACTION
Recode program to align the parameter or use
METHOD_SPLIT to SWITCH to CM.
MESSAGE
Unable to swap parameters in NO_COPY method.
CAUSE
Parameters could not be enclosed within a DST because
the parameters are too far apart.
ACTION
Move parameters closer together.
Symbolic Debugger
(UE, DB)
This chapter lists messages that you may encounter while using HP Symbolic Debugger.
Self-explanatory messages and those which relate to syntax errors, such as missing or
extraneous characters in commands, are not listed in this chapter.
To assist you in finding the solution to a problem, several messages may be displayed. Look
up each message in this chapter to get complete information about the action to take.
Messages are preceded by unique reference numbers that indicate the error type.
Messages, with their message reference numbers, are listed in this order:
UE300-UE436 User Errors
Chapter 4
155
Error Messages Viii C 3
Symbolic Debugger
DB1-DB8
Debugger Errors
Internal error messages, which are in the range of 501 to 579, should not occur with
normal debugger use. If they do occur, report them to your HP support representative.
Child process (program) errors result in signals which are communicated to the debugger.
If a program error occurs while executing a procedure call from the command line, it is
handled like any other error (in other words, you can investigate the called procedure). To
recover from this, or to abort a procedure call from the command line, press CNTLY.
The following example message has a reference number of UE312 and is listed below as it
appears in this chapter:
UE312
MESSAGE
INVALID BREAKPOINT TYPE "TEXT"
A list of abbreviations that are used throughout this chapter and their meanings follow.
Note that in all explanations, commands are given in long form, but the short form may
also be used. Refer to HP Symbolic Debugger User's Reference Manual for further details.
ABBREVIATION
DEFINITION
CMD
A debugger command.
FILE
The name of a file.
NAME
The name of a data object.
NUM
A number.
PROC
A user program or procedure name.
TEXT
A text string; arbitrary user input.
UEnnn
User-created error.
DBnnn
A debugger error.
User Errors (UE300 - UE416)
User errors result from entering incorrect commands or from using the commands
incorrectly. User errors cause the command that you entered to fail. You must correct the
cause of the error and re-enter the command.
UE300
UE301
156
MESSAGE
ATTEMPT TO READ ON NON-WORD BOUNDARY
CAUSE
The debugger cannot read on a non-word aligned address.
ACTION
Do not try to read at a non-word boundary. An incorrect
reference to a data item has probably been made. Note:
Memory accesses are done word-at-a-time, regardless of
how data is formatted in memory.
MESSAGE
ATTEMPT TO WRITE TO ODD ADDRESS
CAUSE
An attempt to write a value on a non-word or half-word
boundary was made.
ACTION
Do not try to write to an odd address. Note: Memory
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
accesses are done word-at-a-time, regardless of how data
is formatted in memory.
UE302
UE303
UE304
UE306
UE307
UE308
UE309
Chapter 4
MESSAGE
ADDRESS NOT FOUND
CAUSE
The address is part of a command and is invalid. It is
probably out of range.
ACTION
Check the validity of the address and re-enter the
command.
MESSAGE
CANNOT READ THAT LOCATION
CAUSE
Access to the child process failed, possibly caused by an
invalid address.
ACTION
Check the validity of the address and re-enter the
command.
MESSAGE
NO CHILD PROCESS
CAUSE
The debugger attempted an operation that required a
child process that does not exist (was not running).
ACTION
To start a child process, use any of the run or step
commands.
MESSAGE
ATTEMPT TO WRITE TO NON-WORD BOUNDARY.
CAUSE
The debugger cannot write to a non-word aligned address.
ACTION
Do not try to write to a non-word boundary. An incorrect
reference to a data item has probably been made. Note:
Memory accesses are done word-at-a-time, regardless of
how data is formatted in memory.
MESSAGE
CANNOT WRITE THAT LOCATION
CAUSE
Access to a child process failed; this may have been caused
by an invalid address.
ACTION
Check the validity of the address and re-enter the
command.
MESSAGE
BAD ACCESS TO CHILD PROCESS
CAUSE
Failed to read data from or write data to a child process.
This may have been caused by an invalid address (for
example, dereferencing an invalid pointer), or by an
attempt to place a breakpoint in an unwritable child
process code space.
ACTION
Check the validity of the data and re-enter the command.
MESSAGE
CAN'T SET BREAKPOINT (INVALID ADDRESS)
CAUSE
The address of the specified breakpoint command was
invalid or unknown.
ACTION
Re-enter the breakpoint command with a correct address.
157
Error Messages Viii C 3
Symbolic Debugger
UE310
UE311
UE312
UE314
UE315
UE316
UE317
UE318
158
MESSAGE
STACK ISN'T THAT DEEP
CAUSE
The debugger tried to set a breakpoint or view a procedure
at an invalid depth. The child process stack was not that
deep.
ACTION
Use the trace command to list the child process stack.
MESSAGE
NO SYMBOLS FOR THAT PROCEDURE
CAUSE
The debugger tried to set a breakpoint using a stack
depth, when the procedure at that stack depth was
non-debuggable.
ACTION
Try setting a breakpoint-address using the name of the
procedure; for example, ba xxx.
MESSAGE
INVALID BREAKPOINT TYPE "TEXT"
CAUSE
TEXT was an invalid breakpoint type.
ACTION
Refer to the "Breakpoint Commands" section in the HP
Symbolic Debugger User's Reference Manual to see valid
breakpoint commands.
MESSAGE
INVALID LINE NUMBER ON "CMD" COMMAND
CAUSE
The quantity given for a line number on a breakpoint,
view, or continue command, was an invalid numeric
expression.
ACTION
Re-enter the command with a valid expression.
MESSAGE
NO SUCH PROCEDURE OR FILE NAME "TEXT"
CAUSE
An attempt was made to set a breakpoint, or continue to a
procedure or file TEXT that did not exist, or was
non-debuggable.
ACTION
Use the lp (list procedures) command to list all known
debuggable procedures and use the lf (list files) command
to list all known source files.
MESSAGE
PROCEDURE "PROC" NOT FOUND WHERE SPECIFIED
CAUSE
The nesting of procedure PROC was not properly specified.
ACTION
Use the trace command to list the stack.
MESSAGE
LABEL "TEXT" NOT FOUND WHERE SPECIFIED
CAUSE
The proc #label was entered incorrectly and that label is
not found in the named procedure.
ACTION
Re-enter the command, giving a valid proc #label
combination.
MESSAGE
NO COUNT GIVEN FOR "CMD" COMMAND
CAUSE
The user failed to specify a breakpoint count (after the \)
for a breakpoint command. Or, an attempt was made to
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
use the breakpoint count command on an existing
breakpoint.
UE319
UE320
UE321
UE322
UE323
UE324
UE326
Chapter 4
ACTION
Refer to the "Breakpoint Commands" section in the HP
Symbolic Debugger User's Reference Manual to see the
correct syntax for breakpoint commands.
MESSAGE
COUNT MUST BE POSITIVE OR NEGATIVE
CAUSE
A count of zero was given for a breakpoint or breakpoint
count command.
ACTION
Re-enter the command with a non-zero count.
MESSAGE
MUST SPECIFY A MACRO NAME
CAUSE
The def command was entered without arguments.
ACTION
Refer to the "Macro Facility Commands" section in the HP
Symbolic Debugger User's Reference Manual to see the
correct syntax for the def command.
MESSAGE
"NAME" IS NOT A VALID MACRO NAME
CAUSE
The debugger tried to define a macro via the def command
where the NAME specified was not a string of
alphanumeric characters beginning with a letter.
ACTION
Re-enter the def command using a string of characters
beginning with a letter for the macro name.
MESSAGE
MUST SPECIFY WHICH MACRO TO DELETE
CAUSE
The undef command was entered to delete or undefine a
macro without giving the name of the macro to delete.
ACTION
Use the lm (list macros) command to list all defined
macros.
MESSAGE
UNKNOWN NAME OR COMMAND "NAME"
CAUSE
An unrecognized string (NAME) was encountered as a
debugger command.
ACTION
Refer to the HP Symbolic Debugger/XL Quick Reference
Guide to see tables of valid debugger commands.
MESSAGE
UNKNOWN COMMAND "CMD" (NUM)
CAUSE
The command CMD (internal value NUM) is not
supported. The message "Unknown
name or command" is usually displayed.
ACTION
Refer to the HP Symbolic Debugger/XL Quick Reference
Guide to see tables of valid debugger commands.
MESSAGE
EMPTY ASSERTION NOT ADDED
CAUSE
The assertion command was given without an associated
command list.
159
Error Messages Viii C 3
Symbolic Debugger
UE328
UE329
UE330
UE331
UE332
UE333
UE334
ACTION
Re-enter the command and include a command-list within
braces ({ }).
MESSAGE
NO BREAKPOINT SET AT CURRENT LOCATION
CAUSE
An attempt was made to activate, delete, or suspend a
breakpoint where no breakpoint was defined.
ACTION
Use the lb (list breakpoints) command to see where
breakpoints are set.
MESSAGE
ADDRESS IS REQUIRED AFTER "CMD"
CAUSE
The ba (breakpoint address) command must be followed by
a code address.
ACTION
Use a valid code address (symbolic or numeric) with the
command.
MESSAGE
INVALID DEPTH GIVEN FOR "CMD" COMMAND
CAUSE
An attempt was made to specify a depth that is not a
number greater than or equal to 0.
ACTION
Re-enter the appropriate command with a valid depth.
MESSAGE
DEPTH MUST BE AN INTEGER
CAUSE
An attempt was made to specify a stack depth that is not a
number.
ACTION
Re-enter the command and specify an integer depth.
MESSAGE
"CMD" NOT ALLOWED WHILE RUNNING ASSERTIONS
CAUSE
These commands cannot be executed while assertions are
active: c (continue), C (Continue), r (run), R (Run), s (step),
S (Step), or k (kill). If one of these commands appears in an
assertion command list, it must follow an x (exit) command
with a non-zero modifier.
ACTION
Exit assertion mode to execute the command or delay
using the command.
MESSAGE
"da," "db," OR "dp" IS REQUIRED
CAUSE
The d (delete) command has only three valid variations.
This d (delete) command was followed by something other
than an assertion, breakpoint, or procedure command.
ACTION
Refer to the HP Symbolic Debugger User's Reference
Manual to see valid delete commands.
MESSAGE
MUST SPECIFY WHICH ASSERTION TO SUSPEND
MUST SPECIFY WHICH ASSERTION TO DELETE
160
CAUSE
The number of the assertion to suspend or delete was not
specified.
ACTION
Use the la (list assertions) command to find the number of
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
the assertion to suspend or delete.
UE335
UE336
UE337
UE338
UE339
UE341
UE343
Chapter 4
MESSAGE
"Directory" COMMAND NEEDS A DIRECTORY NAME
(IN QUOTES)
CAUSE
The D (Directory) command was invoked without
specifying a directory name surrounded by double
quotation marks ( " ).
ACTION
Re-enter the D (Directory) command and enclose a valid
directory name in quotation marks ( " ).
MESSAGE
INVALID EXPRESSION FOR DEPTH ON "CMD" COMMAND
CAUSE
The CMD command was given with an expression for a
depth that the debugger cannot evaluate.
ACTION
Use the t (trace) command to view the stack for the proper
procedure and depth.
MESSAGE
"format" COMMAND NEEDS A STRING ARGUMENT
CAUSE
The f (format) command was followed by something other
than null or a string in quotation marks.
ACTION
Refer to the "Miscellaneous Commands" section in the HP
Symbolic Debugger User's Reference Manual for more
information about the f (format) command.
MESSAGE
"goto" MUST BE FOLLOWED BY A LINE NUMBER
CAUSE
A g (goto) command was given without a numeric
argument or valid label.
ACTION
Refer to the "Miscellaneous Commands" section in the HP
Symbolic Debugger User's Reference Manual for more
information about the g (goto) command.
MESSAGE
MISSING "{"
CAUSE
The i (if) command did not have a brace ( { ) following the
conditional expression. Or, the expression might have been
entered incorrectly.
ACTION
Re-enter the expression, enclosing the command-lists in
braces.
MESSAGE
MAP IS NOT SUPPORTED
CAUSE
Your version of the debugger does not support the M (Map)
command, because core files are unsupported.
ACTION
Do not enter the M (Map) command.
MESSAGE
INVALID EXPRESSION GIVEN FOR "CMD" COMMAND
CAUSE
A non-numeric expression was entered as part of the s
(step), S (Step), t (trace), T (Trace), and sa (suspend
assertion) commands.
161
Error Messages Viii C 3
Symbolic Debugger
UE344
UE345
UE346
UE348
UE349
UE350
UE351
UE352
162
ACTION
Re-enter the command with a correct numeric expression.
MESSAGE
"t" MUST BE FOLLOWED BY "a", "b", "c", "m",
or "r", OR
EXPRESSION
CAUSE
As part of the t (toggle) command, the t (toggle) was not
followed by one of these commands: a (assertion), b
(breakpoint), c (case), m (macros), or r (recording).
ACTION
Refer to the individual command listings in the HP
Symbolic Debugger User's Reference Manual to see valid
toggle commands.
MESSAGE
INVALID WINDOW SIZE
CAUSE
The numeric expression given for the new window size on
the window command was not a valid numeric expression
or was outside the range of 1 to 21.
ACTION
Re-enter the command with a valid numeric expression
within the range of 1 to 21.
MESSAGE
"exit" IS ONLY ALLOWED WHILE RUNNING
ASSERTIONS
CAUSE
The debugger tried to exit the assertions mode while
assertions were not active.
ACTION
Refer to the x (exit) command listing in the HP Symbolic
Debugger User's Reference Manual.
MESSAGE
NO PLAYBACK NAME SPECIFIED
CAUSE
The < or << command was given without a file name
argument.
ACTION
Re-enter the command with the playback file name.
MESSAGE
CAN'T OPEN "FILE" AS PLAYBACK FILE
CAUSE
The system failed to open the specified playback file.
ACTION
Check the file path and permissions.
MESSAGE
CAN'T OPEN "FILE" AS RECORD FILE
CAUSE
The system failed to open the specified record file.
ACTION
Check the file path and permissions.
MESSAGE
OPERATOR STACK OVERFLOW
CAUSE
The expression was too complicated for the expression
handler to parse. A combination of more than 15 nested
parentheses and/or pending operators may be the cause.
ACTION
Re-enter the expression, using less than 15 nested
parentheses.
MESSAGE
OPERATOR STACK UNDERFLOW
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
UE353
UE354
UE355
UE356
UE357
UE358
UE359
CAUSE
The expression handler failed. This may have been caused
by a corrupt environment or a parsing problem.
ACTION
Re-enter the expression in an alternate form, if possible.
MESSAGE
DATA TOO BIG TO PUT IN THE CHILD PROCESS
CAUSE
A string constant or other data was larger than the total
size of the buffer in xdbend.lib.sys
ACTION
Re-enter a smaller string constant or data item, if
applicable.
MESSAGE
CAN'T STORE INTO A CONSTANT
CAUSE
The left side of an assignment statement was found to be a
constant; it cannot be modified.
ACTION
Use the \t display format for information on the assigned
variable.
MESSAGE
CAN'T SET ANY REGISTERS
CAUSE
Setting registers incorrectly is inherently dangerous and
can lead to complete lockup of the operating system.
ACTION
Only use the g (goto) command to make limited, safe
changes to the program counter ($pc). Avoid changing
register values directly.
MESSAGE
STRING TOO LONG FOR ASSIGNMENT
CAUSE
An attempt was made to assign a string over 1024 bytes to
an HP FORTRAN 77 CHAR*, HP Pascal string, or HP
Pascal packed array of char.
ACTION
Use the \t display format for type information of the
string assigning to, and re-enter the command with an
appropriately sized string.
MESSAGE
INCOMPATIBLE OPERANDS FOR STRING ASSIGNMENT
CAUSE
An attempt was made to assign to an HP FORTRAN 77
CHAR*, HP Pascal string, or HP Pascal packed array of
char, something other than an HP FORTRAN 77 CHAR*,
HP Pascal string, HP Pascal packed array of char, a string
constant, or a character constant.
ACTION
Re-enter the command with a proper assignment.
MESSAGE
CAN'T DEREFERENCE A CONSTANT
CAUSE
An attempt was made to dereference a constant.
ACTION
Use the \t format to find the type of the object to be
displayed.
MESSAGE
CAN'T TAKE THE ADDRESS OF A CONSTANT
CAN'T TAKE THE ADDRESS OF A REGISTER
Chapter 4
163
Error Messages Viii C 3
Symbolic Debugger
UE360
CAUSE
Operand of &, $addr, or addr operator is marked as a
constant or register type.
ACTION
Use the \t display format to find the type of the object
being displayed.
MESSAGE
POSTFIX "++" NOT SUPPORTED
POSTFIX "--" NOT SUPPORTED
PREFIX "++" NOT SUPPORTED
PREFIX "--" NOT SUPPORTED
UE361
UE362
UE363
UE364
UE365
164
CAUSE
An attempt was made to use an unsupported operator. For
example, ++n, --n, n++, n--.
ACTION
Make sure a space is used between a + or - operator and a
unary sign (for example 2- -5). +=1 or -=1 can be used to
increment or decrement, respectively.
MESSAGE
INVALID COMBINATION OF OPERATOR AND OPERANDS
CAUSE
The debugger tried to perform a numeric operation on one
or more non-numeric operands.
ACTION
Re-enter the command with a valid expression.
MESSAGE
UNKNOWN OPERATOR (NUM)
CAUSE
An unsupported operator, with internal value NUM, was
pushed on the operator stack.
ACTION
Re-enter the command using an operator known to the
current language or reset $lang to the language in which
the operator is valid.
MESSAGE
MISFORMED EXPRESSION
CAUSE
An expression was entered incorrectly. The debugger
attempts to show you where the error was detected in the
command line. The error token might be one token beyond
the actual error.
ACTION
Re-enter the expression using operators and operands
known to the current language or reset $lang to the
language in which the operator or operand is valid.
MESSAGE
TWO OPERATORS IN A ROW
CAUSE
The expression handler detected an improper construct in
an expression.
ACTION
Re-enter the command with a valid expression.
MESSAGE
FORTRAN VARIABLE NOT PURE ARRAY
CAUSE
An attempt was made to dereference an array that had
pointer or function qualifiers, while the current language
was set to FORTRAN, which does not support them.
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
UE366
UE367
UE368
UE369
UE370
UE371
UE372
UE373
Chapter 4
ACTION
Try again with $lang set to a different language.
MESSAGE
INVALID REAL NUMBER
CAUSE
The specified numeric expression was not a real number.
ACTION
See the appropriate language reference manual, or Table
4-3 in this manual, for the format of real numbers.
MESSAGE
MISFORMED GLOBAL NAME
CAUSE
Colon ( : ) must be followed by a variable name (string).
ACTION
Refer to the "Entering Variable Names" section in the HP
Symbolic Debugger User's Reference Manual to see how to
specify global variables.
MESSAGE
UNKNOWN GLOBAL
CAUSE
The variable specified with :var was not a recognized
global variable name.
ACTION
Use the lg (list globals) command to list all known global
variables.
MESSAGE
NEED A ":" AFTER THE NUMBER
CAUSE
Proc:depth:var was entered incompletely (:var was
missing).
ACTION
Refer to the l (list) command listing in the HP Symbolic
Debugger User's Reference Manual to see a list of
variables.
MESSAGE
INVALID LOCAL NAME
CAUSE
Proc[:depth]:var was entered incorrectly. Var must be a
valid variable name in the specified procedure, at the
specified depth.
MESSAGE
UNKNOWN LOCAL
CAUSE
The variable specified with proc[:depth]:var was not a
recognized local variable of proc.
ACTION
Use the l (list) command to list all known local variables of
the current proc, or use the T (Trace) command to list the
locals, variables, and procedures on the stack.
MESSAGE
PROCEDURE "PROC" NOT FOUND AT STACK DEPTH NUM
CAUSE
In proc:depth, the procedure PROC was not on the child
process stack at depth NUM. Either the stack was not that
deep, or the procedure at that depth was not PROC.
ACTION
Use the t (trace) command to list the stack.
MESSAGE
UNKNOWN LANGUAGE
CAUSE
An attempt was made to modify the current language by
assigning an invalid language designator to the special
165
Error Messages Viii C 3
Symbolic Debugger
variable $lang. The valid language designators are
COBOL, Pascal, FORTRAN, C, and default.
UE374
UE375
UE376
UE377
UE378
UE379
166
ACTION
Re-enter the command with COBOL, Pascal, FORTRAN,
C, or default as the designator.
MESSAGE
LOCAL IS NOT ACTIVE
CAUSE
A local variable name was recognized but the procedure it
belongs to was not currently active on the child process
stack.
ACTION
Re-enter the command after its procedure has been called.
MESSAGE
TWO OPERANDS IN A ROW
CAUSE
The expression handler detected an improper construct in
an expression.
ACTION
Refer to the "Entering Expressions" section in the HP
Symbolic Debugger User's Reference Manual
(31508-90003).
MESSAGE
NO SOURCE FILE FOR CURRENT ADDRESS
CAUSE
The given child process address did not map to a known,
debuggable source file.
ACTION
Use the lf (list files) command to view the files the
debugger recognizes, and re-enter the command with an
appropriate address expression.
MESSAGE
NO SEARCH PATTERN
CAUSE
The search command (/, ?, n (next), or N (Next)) was given
without a search pattern (in the case of n (next) and N
(Next), the previous search command / or ? was provided
without a pattern).
ACTION
Refer to the individual command listings in the HP
Symbolic Debugger User's Reference Manual for more
information about search commands.
MESSAGE
NO MATCH FOR "TEXT"
CAUSE
The search pattern (TEXT) for the /, ?, n, (next) or N
(Next) command was not found in the current viewing file.
Note that the pattern is a literal, not a regular expression.
ACTION
Try another pattern or view another file and search for the
pattern.
MESSAGE
INVALID DISPLAY FORMAT "TEXT"
CAUSE
Given the data display format, or a portion of it, the TEXT
contained invalid syntax.
ACTION
Refer to Table 4-3 in the HP Symbolic Debugger User's
Reference Manual to see valid data viewing formats.
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
UE381
UE382
MESSAGE
LENGTH NOT ALLOWED WITH "TEXT" FORMAT
CAUSE
Given the data display format, the TEXT did not allow the
data length specification because it is irrelevant or implicit
in the format.
ACTION
Refer to the HP Symbolic Debugger User's Reference
Manual to see valid data viewing formats.
MESSAGE
THIS DOES NOT APPEAR TO BE A STRUCT OR UNION
THIS DOES NOT APPEAR TO BE A RECORD OR UNION
UE385
UE386
UE387
UE388
UE390
UE391
Chapter 4
CAUSE
The debugger tried and failed to dump the contents of a
data object that was not a struct, union, or record.
ACTION
Use the \t display format for more information.
MESSAGE
NO CURRENT PROCEDURE
CAUSE
The debugger tried to list locals for the current viewing
procedure when the procedure was undefined.
ACTION
Use the lp (list procedures) command to list all the
debuggable procedures.
MESSAGE
NO SUCH PROCEDURE "PROC"
CAUSE
An attempt to list locals of a non-existent, or
non-debuggable procedure PROC was made.
ACTION
Use the lp (list procedures) command to list all known
debuggable procedures.
MESSAGE
UNRECOGNIZED "l" COMMAND
CAUSE
The l (list) command was given with a second part that
was neither a known procedure name, nor a valid option.
ACTION
Refer to the l (list) command listing in the HP Symbolic
Debugger User's Reference Manual for more information.
MESSAGE
":" MUST BE FOLLOWED BY A DEPTH
CAUSE
Proc:depth was entered incorrectly.
ACTION
Refer to the individual command listings in the HP
Symbolic Debugger User's Reference Manual for more
information.
MESSAGE
EXITING COMMAND LINE PROCEDURE CALL
CAUSE
The command line procedure call environment terminated
for an unusual reason, such as a break was encountered
during program execution, or an error was reached before
the procedure was called.
ACTION
Check the procedure call for errors and re-enter the
command line procedure call.
MESSAGE
CAN'T PASS MORE THAN NUM ARGUMENTS TO CALLED
167
Error Messages Viii C 3
Symbolic Debugger
PROCEDURE
UE392
UE393
UE396
UE398
UE399
UE400
UE401
168
CAUSE
A large limit (NUM) exists on how many parameters can
be passed to a procedure called from the command line.
ACTION
Check the number of parameters for the procedure you are
attemping to call. If the limit (NUM) is less than the
number of parameters in the procedure, that procedure
cannot be called from the command line.
MESSAGE
ARGUMENT LIST TOO LONG
CAUSE
Arguments to the run command exceeded 1024 bytes.
ACTION
Re-enter the run command with fewer arguments.
MESSAGE
CAN'T GOTO A LINE OUTSIDE OF THE CURRENT
PROCEDURE
CAUSE
The line number given to the g (goto) command was not an
executable source line in the top procedure or paragraph
on the child process stack. This is not always the same as
the current viewing procedure.
ACTION
Re-enter the g (goto) command with a line number within
the procedure or paragraph on the top of the child process
stack.
MESSAGE
UNKNOWN NAME
CAUSE
An unrecognized string (procedure or variable name) was
encountered in an expression.
ACTION
Use the lp (list procedures), lg (list globals), l (list), lc (list
commons), or ll (list labels) command to list all known
procedures, globals, locals, commons, or labels.
MESSAGE
MISFORMED HEX NUMBER
CAUSE
0x or 0X was given without digits following.
ACTION
Re-enter the command with a valid hexadecimal number.
MESSAGE
MISFORMED OCTAL NUMBER
CAUSE
An octal number starting with 0 contains an 8 or 9.
ACTION
Re-enter the command with the correct octal number.
MESSAGE
CHARACTER CONSTANT IS MISSING ENDING
CAUSE
Token parsed as a character constant is missing a trailing
single quotation mark ('). This applies to a single
quotation mark followed by a single character or
equivalent, backslash sequence.
ACTION
Re-enter the command enclosing the character constant in
single quotation marks (').
MESSAGE
STRING CONSTANT IS MISSING ENDING "
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
UE402
UE403
UE404
UE405
UE407
UE408
CAUSE
Token parsed as a string constant was missing a trailing
double quotation mark before the end of the command
line.
ACTION
Re-enter the string with a beginning and ending double
quotation marks.
MESSAGE
MACROS NESTED TOO DEEPLY
CAUSE
A user specified macro has caused the evaluation of over
20 macro definitions during its evaluation. The debugger
cannot evaluate macros nested this deep. This error can
also be caused by a recursive macro definition.
ACTION
Redefine the macro using fewer than 20 macro definitions,
or remove the recursive definition.
MESSAGE
MACROS PROCESSING OVERFLOW
CAUSE
While evaluating a userh specified macro, the buffer used
to hold the resulting definition for this macro was about to
overflow, and the processing for this macro terminated
unsuccessfully.
ACTION
Undefine the unnecessary macros and redefine the macro.
MESSAGE
SORRY, YOU CAN'T ACCESS A NAKED FIELD
CAUSE
An attempt was made to refer to a field by name without
specifying the qualifying structure (for example, union,
record, pointer, etc.).
ACTION
Use the \t display format for more information.
MESSAGE
TOO MANY SUBSCRIPTS
CAUSE
An attempt was made to dereference an array with more
dimensions than it was declared to have. However, HP C
does allow you to dereference pointers in this manner.
ACTION
Use the \t display format for more information.
MESSAGE
INVALID FIELD ACCESS: "NAME"
CAUSE
An attempt was made to do a field dereference of an object
(NAME) that was not a structure or union.
ACTION
Use the \t display format to determine the characteristics
of the object (NAME).
MESSAGE
NO SUCH FIELD NAME "NAME" FOR THAT RECORD
NO SUCH FIELD NAME "NAME" FOR THAT STRUCT
NO SUCH FIELD NAME "NAME" FOR THAT UNION
Chapter 4
CAUSE
Struct (union, record) did not contain a field of that
NAME.
ACTION
Use the \t display format for more information.
169
Error Messages Viii C 3
Symbolic Debugger
UE411
UE412
UE413
UE415
UE416
UE418
UE419
UE420
UE421
170
MESSAGE
OPERAND STACK OVERFLOW
CAUSE
An expression was too complicated for the expression
handler to parse. A combination of more than 15 nested
parentheses and/or pending operators may be the cause.
ACTION
Re-enter the expression, using less than 15 nested
parentheses.
MESSAGE
CAN'T EXECUTE CHILD PROGRAM
CAUSE
The debugger could not execute the object file given.
ACTION
Check to see that the file is executable.
MESSAGE
WINDOW MODE REQUIRED FOR THIS COMMAND
CAUSE
The debugger was probably invoked with the -L option.
ACTION
Verify that you are using an HP terminal and rerun the
debugger without the -L option.
MESSAGE
NO SUCH FIELD: "NAME"
CAUSE
The simple field NAME or field list specified does not exist.
ACTION
Check the declaration for the correct field name or field
list.
MESSAGE
NON-UNIQUE FIELD LIST
CAUSE
The field name or field list specified does not uniquely
identify a single field.
ACTION
Use a more complex field list to ensure it identifies a single
field.
MESSAGE
CAN'T MIX . AND OF OPERATORS
CAUSE
The field list includes both the . and of operators.
ACTION
Use only the . or of operator.
MESSAGE
ONE ARRAY SUBSCRIPT EXPECTED
CAUSE
The field specified is a table or one of the field's ancestors
is a table, but no array subscript was given.
ACTION
Determine which field is a table, and use the appropriate
subscript.
MESSAGE
LIST OF <NUMBER> ARRAY SUBSCRIPTS EXPECTED
CAUSE
The field specified is a table and/or one or more of the
field's ancestors is a table; <number> subscripts are
required, but no array subscripts were given.
ACTION
Determine which fields are tables, and use the appropriate
<number> of subscripts.
MESSAGE
NOT ENOUGH ARRAY SUBSCRIPTS, EXPECTED
<NUMBER>
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
UE422
UE423
UE424
UE425
UE426
UE427
UE428
Chapter 4
CAUSE
There are more tables among the field and its ancestors
than there were subscripts given.
ACTION
Determine which fields are tables, and supply <number>
subscripts.
MESSAGE
UNEXPECTED ARRAY SUBSCRIPT LIST
CAUSE
Neither the field specified nor any of its ancestors are
tables, but one or more subscripts was given.
ACTION
Do not give a list of subscripts.
MESSAGE
CAN'T MOVE TO A CONSTANT
CAUSE
The item which is the destination of the move is a
constant.
ACTION
Do not attempt to store into a constant, or look at the
declarations to determine the correct field name.
MESSAGE
CAN'T MOVE TO THAT DESTINATION
CAUSE
The item which is the destination of the move is of a type
into which the debugger can not store.
ACTION
Do not attempt to store into that item, or look at the
declarations to determine the correct field name.
MESSAGE
CAN'T HANDLE EDITED FIELDS AS DESTINATION
CAUSE
The item which is the destination of the move is an edited
field.
ACTION
None, the debugger can not currently handle edited fields
as the source or destination of a mov (move) command.
MESSAGE
CAN'T HANDLE EDITED FIELDS AS SOURCE
CAUSE
The item which is the source of the move is an edited field.
ACTION
None, the debugger can not currently handle edited fields
as the source or destination of a mov (move) command.
MESSAGE
CAN'T MOVE NUMERIC FIELD TO ALPHABETIC FIELD
CAUSE
The source of the move is a numeric field, while the
destination field is alphabetic.
ACTION
None, moving a numeric field to an alphabetic field is
illegal.
MESSAGE
CAN'T MOVE NUMERIC FIELD WITH A FRACTION TO
ALPHANUMERIC FIELD
CAUSE
The source of the move is a numeric field which has a
fraction, while the destination field is alphanumeric.
ACTION
None, moving a numeric field with a fraction to an
alphanumeric field is illegal.
171
Error Messages Viii C 3
Symbolic Debugger
UE429
UE430
UE431
UE432
UE433
UE434
UE435
172
MESSAGE
CAN'T MOVE ALPHABETIC FIELD TO NUMERIC FIELD
CAUSE
The source of the move is an alphabetic field, while the
destination field is numeric.
ACTION
None, moving an alphabetic field to a numeric field is
illegal.
MESSAGE
CAN'T MOVE ALPHANUMERIC FIELD CONTAINING
NON-DIGIT TO NUMERIC FIELD
CAUSE
The source of the move is an alphanumeric field
containing a non-digit, while the destination is numeric.
ACTION
None, moving an alphanumeric field containing a
non-digit to a numeric field is illegal.
MESSAGE
INVALID SIGN IN PACKED DECIMAL NUMBER
CAUSE
The packed decimal field that is either being displayed or
being used as the source of a move contains an invalid sign
field.
ACTION
Use either a data field that redefines the packed decimal
field, or use the group field that contains the packed
decimal data field.
MESSAGE
INVALID DIGIT IN PACKED DECIMAL NUMBER
CAUSE
The packed decimal field that is either being displayed or
being used as the source of a move contains an invalid
digit.
ACTION
Use either a data field that redefines the packed decimal
field, or use the group field that contains the packed
decimal data field.
MESSAGE
INVALID SIGN OVERPUNCH IN DISPLAY NUMBER
CAUSE
The display field that is either being displayed or being
used as the source of a move contains an invalid sign
overpunch.
ACTION
Use either a data field that redefines the display field, or
use the group field that contains the display field.
MESSAGE
INVALID SEPARATE SIGN IN DISPLAY NUMBER
CAUSE
The display field that is either being displayed or being
used as the source of a move contains an invalid separate
sign.
ACTION
Use either a data field that redefines the display field, or
use the group field that contains the display data field.
MESSAGE
TOO MANY ARRAY SUBSCRIPTS, EXPECTED <NUMBER>
CAUSE
There are less tables among the field and its ancestors
than there were subscripts.
Chapter 4
Error Messages Viii C 3
Symbolic Debugger
UE436
ACTION
Determine which fields are tables, and supply <number>
subscripts.
MESSAGE
SUBSCRIPT NUMBER <SUBSCRIPT> OUTSIDE RANGE
<LOW> TO <HIGH>.
CAUSE
Subscript number <subscript> was outside the valid range
of <low> to <high>.
ACTION
Supply a value between <low> and <high>.
Debugger Errors (DB1-DB8)
DB1
DB2
DB3
DB7
Chapter 4
MESSAGE
Assigning to NUM byte object from NUM byte
object; moved NUM bytes
CAUSE
The object on the left side of an assignment was not equal
to the size of the right side of the expression. The debugger
copied a series of bytes equal in size to the left side of the
assignment statement.
ACTION
Re-enter the command, using expressions of equal length,
or else results based on truncation will occur.
MESSAGE
WARNING: "FILE" DOES NOT APPEAR TO HAVE LINE
SYMBOLS
CAUSE
When opening the source file (FILE) associated with a
procedure, no entries in the source line table were found
for the procedure. The procedure may not have any
executable lines, or the object file may have been
corrupted.
ACTION
Recompile the program with the symbolic debugger option.
MESSAGE
WARNING: "FILE1" IS YOUNGER THAN "FILE2"
CAUSE
The source file (FILE1) modification time is newer than
the object file (FILE2) modification time, so the source file
may not correspond to the code in object file.
ACTION
Recompile the source file with the symbolic debugger
option to update the object file.
MESSAGE
WARNING: CODE IS SHARED; YOU CAN'T SET
BREAKPOINTS SO YOU CAN'T RUN.
CAUSE
The object file was set to a shared mode that prevented the
debugger from writing breakpoints into a child process
code in memory. Because an initial breakpoint is required
when starting a child process, you cannot do any useful
debugging without one. If you try to start a child process,
you may receive the message: "Bad access."
ACTION
If possible, modify the object file to no longer be in shared
mode.
173
Error Messages Viii C 3
Sysmain
DB8
MESSAGE
WARNING: "XDBEND" WAS NOT LINKED WITH THIS
PROGRAM
CAUSE
The special procedure "_end_" was not found in the symbol
table during initialization. If xdbend is missing, string
constants and some other values cannot be stored in the
child process address space when required, resulting in an
error at that time.
ACTION
Re-link the program with xdbend.lib.sys.
MESSAGE
WARNING: TOO FEW PARAMETERS
CAUSE
An attempt was made to call a debuggable procedure from
the command line with a different number of parameters
than specified in the symbol table. The procedure can still
be called, but it may lead to odd results which depend on
the language and the called procedure.
ACTION
Use the V (View) command to view the procedure to
determine the correct number of parameters.
MESSAGE
WARNING: TOO MANY PARAMETERS
CAUSE
An attempt was made to call a debuggable procedure from
the command line with a different number of parameters
than specified in the symbol table. The procedure can still
be called, but it may lead to odd results which depend on
the language and the called procedure.
ACTION
Use the V (View) command to view the procedure to
determine the correct number of parameters.
1
MESSAGE
CAN'T ABORT I/O ON A VIRTUAL LOGICAL DEVICE.
(sys 1)
2
MESSAGE
CAN'T ABORT I/O ON A DISC LOGICAL DEVICE.
(sys 2)
3
MESSAGE
NOT A VALID LOGICAL DEVICE. (sys 3)
4
MESSAGE
CAN'T ABORT I/O ON A SPOOLER LOGICAL DEVICE.
(sys 4)
5
MESSAGE
LOGICAL DEVICE IS NOT CONFIGURED. (sys 5)
6
MESSAGE
CAN'T ABORT THIS JOB/SESSION. (sys 6)
DB10
DB11
Sysmain
(sys)
SET 42
174
Chapter 4
Error Messages Viii C 3
Sysmain
7
MESSAGE
INVALID JOB IDENTIFIER. (sys 7)
8
MESSAGE
ALREADY IN SINGLE USER MODE. (sys 8)
9
MESSAGE
CAN'T FORCE LOGOFF. (sys 9)
10
MESSAGE
CURRENTLY IN LOGOFF MODE. (sys 10)
11
MESSAGE
MISSING JOB/SESSION # SPECIFIER. (sys 11)
12
MESSAGE
ALREADY IN MULTI-USER MODE. (sys 12)
13
MESSAGE
LOGON NOT PERMITTED BY DIAGNOSTICS. (sys 13)
14
MESSAGE
CAN'T FORCE LOGON. (sys 14)
15
MESSAGE
NO REQUESTS PENDING. (sys 15)
16
MESSAGE
INVALID RID TYPE. (sys 16)
17
MESSAGE
MISSING PARAMETER. (sys 17)
18
MESSAGE
MISSING PARAMETER LENGTH. (sys 18)
19
MESSAGE
INVALID REPLY IDENTIFIER. (sys 19)
20
MESSAGE
REPLY IS TOO LONG. (sys 20)
21
MESSAGE
PARAMETER IS TOO LONG. (sys 21)
22
MESSAGE
COMMAND NAME IS TOO LONG. (sys 22)
23
MESSAGE
INVALID COMMAND NAME. (sys 23)
24
MESSAGE
CAN'T CREATE THE SYSTEM PORT. (sys 24)
25
MESSAGE
CAN'T CREATE THE REPLY INFORMATION TABLE.
(sys 25)
26
MESSAGE
CAN'T GET A COMMAND. (sys 26)
27
MESSAGE
CAN'T RESTORE ORIGINAL STATE OF CONSOLE. (sys
27)
28
MESSAGE
CAN'T CREATE A STATUS REPLY PORT. (sys 28)
29
MESSAGE
CAN'T RECEIVE STATUS. (sys 29)
30
MESSAGE
CAN'T PURGE STATUS REPLY PORT. (sys 30)
31
MESSAGE
MUST HAVE DI CAPABILITY. (sys 31)
32
MESSAGE
CAN'T ENABLE/DISABLE CONSOLE MODE. (sys 32)
33
MESSAGE
CAN'T SHUT DOWN. (sys 33)
34
MESSAGE
CURRENTLY SHUTTING DOWN. (sys 34)
35
MESSAGE
NO I/O TO ABORT FOR DEVICE !. (sys 35)
36
MESSAGE
HLIO INTERNAL ERROR. COMMAND CANNOT BE
EXECUTED. (sys 36)
37
MESSAGE
THIS JOB/SESSION DOES NOT EXIST. (sys 37)
38
MESSAGE
TOO MANY PARAMETERS WERE GIVEN. (sys 38)
Chapter 4
175
Error Messages Viii C 3
System Disk Load
39
MESSAGE
EXPECTED USER NAME IN USERNAME.ACCTNAME
PARAMETER. (sys 39)
40
MESSAGE
MISSING USER NAME IN USERNAME.ACCTNAME. (sys
40)
41
MESSAGE
PARAMETER EXCEEDS THE LENGTH OF USER/JOB/ACCT
NAMES. (sys 41)
42
MESSAGE
EXPECTED [JOBNAME,]USERNAME.ACCTNAME. (sys
42)
43
MESSAGE
MISSING ACCT NAME IN USERNAME.ACCTNAME
PARAMETER. (sys 43)
44
MESSAGE
INVALID CHARACTER WAS FOUND. (sys 44)
47
MESSAGE
SYSTEM CURRENTLY IN AN UNKNOWN MODE. (sys 47)
100
MESSAGE
UNRECOGNIZED SUBSYSTEM #!, INFO = !. (sys
100)
200
MESSAGE
System State: Initializing Mode. (sys 200)
201
MESSAGE
System State: Multiuser Mode. (sys 201)
202
MESSAGE
System State: Single User Mode. (sys 202)
203
MESSAGE
System State: Single User - No Logon Mode.
(sys 203)
204
MESSAGE
System State: No User Mode. (sys 204)
205
MESSAGE
System State: Terminating Mode. (sys 205)
210
MESSAGE
Reply Information Table has been initialized!
(sys 210)
System Disk Load
(Subsystem 148)
201
202
176
MESSAGE
An error occurred in the file name from tape.
CAUSE
Incorrect file name read from tape.
ACTION
Clean tape drive and retry. Clean tape drive and remake
tape. Determine cause of incorrect file name on tape and
correct.
MESSAGE
The procedure failed to initialize the file
system directory on INSTALL.
CAUSE
Error status returned from DRINIT file system initialize
directory.
Chapter 4
Error Messages Viii C 3
System Disk Load
203
204
205
206
207
208
209
Chapter 4
ACTION
Determine cause of error from DRINIT and correct.
MESSAGE
An internal file number error occurred upon
trying to get the disk address of a boot
file.
CAUSE
File number error while getting disk address. (Internal
error.)
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An error occurred from file system FFILEINFO
getting the disk address of a boot file.
CAUSE
Error returned from FFILEINFO.
ACTION
Determine cause of error from FFILEINFO and correct.
MESSAGE
An error occurred from file system
LM_GET_1ST_EXTENT_INFO getting a disk address
of a boot file.
CAUSE
Error returned from LM_GET_1ST_EXTENT_INFO
ACTION
Determine cause of error from
LM_GET_1ST_EXTENT_INFO and correct.
MESSAGE
An error occurred from I/O system reading the
label for a name file from tape for
RENDEZVOUSIO.
CAUSE
Error returned by RENDEZVOUSIO reading MPEXLDIR
file label.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry. Determine cause of error from
RENDEZVOUSIO and correct.
MESSAGE
An error occurred from I/O system reading the
label for a name file from the tape from
SENDIO.
CAUSE
Error returned by SENDIO reading MPEXLDIR file label.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred reading the label for the
name file. Bad tape or wrong tape position;
not enough data read.
CAUSE
Error in length of data reading MPEXLDIR file label. Tape
read expected 256 bytes and got less than 200 bytes.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry.
MESSAGE
An error occurred from I/O system reading the
name file from the tape from RENDEZVOUSIO.
CAUSE
Error returned by RENDEZVOUSIO reading MPEXLDIR
177
Error Messages Viii C 3
System Disk Load
file data.
210
211
212
213
214
215
216
217
178
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry. Determine cause of error from
RENDEZVOUSIO and correct.
MESSAGE
An error occurred from I/O system reading the
name file from the tape from SENDIO.
CAUSE
Error returned by SENDIO reading MPEXLDIR file data.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred reading the name file from
the tape; bad tape or wrong tape position;
not enough data read.
CAUSE
Error in length of data reading MPEXLDIR file data. Tape
read expected at least 80 bytes and got less than 80 bytes.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry.
MESSAGE
An error occurred from HPFOPEN to create the
name file.
CAUSE
Error from HPFOPEN for MPEXLDIR file.
ACTION
Determine cause of error from HPFOPEN and correct.
MESSAGE
Error from FWRITE on writing name file.
CAUSE
Error from FWRITE for MPEXLDIR file.
ACTION
Determine cause of error from FWRITE and correct.
MESSAGE
An error occurred from FCLOSE on the name
file.
CAUSE
Error from FCLOSE for MPEXLDIR file.
ACTION
Determine cause of error from FCLOSE and correct.
MESSAGE
A failure occurred from INIT_BOOTCMD_AREA.
CAUSE
Error from INIT_BOOTCMD_AREA.
ACTION
Determine cause of error from INIT_BOOTCMD_AREA
and correct.
MESSAGE
A failure occurred from SAVE_BOOTCMD_TO_DISK.
CAUSE
Error from SAVE_BOOTCMD_TO_DISK.
ACTION
Determine cause of error from
SAVE_BOOTCMD_TO_DISK and correct.
MESSAGE
A failure occurred from COMPUTE_FREE_ADDRESS.
CAUSE
Error from COMPUTE_FREE_ADDRESS.
ACTION
Determine cause of error from
Chapter 4
Error Messages Viii C 3
System Disk Load
COMPUTE_FREE_ADDRESS and correct.
218
219
220
221
222
223
224
225
Chapter 4
MESSAGE
This is an invalid free space map address
from COMPUTE_FREE_ADDRESS; conditional debug
compile option.
CAUSE
Incorrect free space bit map address from
COMPUTE_FREE_ADDRESS. Debug code not released.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A failure occurred from SM_CREATE_HASH_TBL.
CAUSE
Error from SM_CREATE_HASH_TBL. Internal storage
management routine.
ACTION
Determine cause of error from SM_CREATE_HASH_TBL
and correct.
MESSAGE
A failure occurred from INSTALL_VOLUME_MGT.
CAUSE
Error from INSTALL_VOLUME_MGT while initializing a
volume.
ACTION
Determine cause of error from INSTALL_VOLUME_MGT
and correct.
MESSAGE
A failure occurred from local routine
LOAD_POST writing to sector 0,1 of disk.
CAUSE
Error from LOAD_POST writing to sector zero and one of
LDEV 1.
ACTION
Determine cause of error from LOAD_POST and correct.
MESSAGE
A failure occurred from local routine
LOAD_POST writing to sector 0,1 of disk.
CAUSE
Error from LOAD_POST writing to sector zero and one of
LDEV 1.
ACTION
Determine cause of error from LOAD_POST and correct.
MESSAGE
A failure occurred from file system
FS_INITIALIZE_FILE_SYSTEM.
CAUSE
Error from FS_INITIALIZE_FILE_SYSTEM.
ACTION
Determine cause of error from
FS_INITIALIZE_FILE_SYSTEM and correct.
MESSAGE
A failure occurred from file system
FS_PROC_INIT.
CAUSE
Error from FS_PROC_INIT, file system initialize routine.
ACTION
Determine cause of error from FS_PROC_INIT and
correct.
MESSAGE
A failure occurred from file system directory
FAKE_LOGON.
179
Error Messages Viii C 3
System Disk Load
226
227
228
229
230
231
232
180
CAUSE
Error from FAKE_LOGON, file system directory routine.
ACTION
Determine cause of error from FAKE_LOGON and correct.
MESSAGE
A failure occurred from file system
FS_TDIRC_INIT.
CAUSE
Error from FS_TDIRC_INIT, file system routine.
ACTION
Determine cause of error from FS_TDIRC_INIT and
correct.
MESSAGE
A failure occurred from local routine
LOAD_POST writing to sector 0,1 of disk.
CAUSE
Error from LOAD_POST writing to sector zero and one of
LDEV 1.
ACTION
Determine cause of error from LOAD_POST and correct.
MESSAGE
A fatal option error occurred (file name
wrong); INSTALL renamed UPDATE.
CAUSE
A copy of the PME INSTALL has been given control from
the option routine with the indication that the command
used to call the PME was not INSTALL. Probably was
UPDATE. Probably a copy of INSTALL was renamed
UPDATE.
ACTION
Use a correct copy of INSTALL.
MESSAGE
Disk sparing failed on LDEV 1.
CAUSE
Error returned from disk sparing of LDEV 1.
ACTION
Determine cause of error from sparing and correct.
MESSAGE
REBOOT_CPU returned control.
CAUSE
The routine REBOOT_CPU has returned control to the
caller. The CPU was probably not rebooted.
ACTION
Determine why control was returned from REBOOT_CPU
and correct. Reboot the CPU and continue.
MESSAGE
Hard loop failed, probably due to compiler or
hardware error, or START/NO START error.
CAUSE
The compiler generated loop to stop the CPU on a nostart
option has exited. Generated code or hardware error.
ACTION
Determine why the code exited and correct. Reboot the
CPU and continue.
MESSAGE
An error occurred upon getting the size of
the disk.
CAUSE
Error from GET_HPE_DISC_SIZE_PAGE. Internal
routine to compute the number of pages on the disk.
ACTION
Determine cause of error from
Chapter 4
Error Messages Viii C 3
System Disk Load
GET_HPE_DISC_SIZE_PAGE and correct.
233
234
235
236
237
238
239
240
Chapter 4
MESSAGE
An error occurred from SM_CREATE_HASH_TBL.
CAUSE
Error from SM_CREATE_HASH_TBL, storage
management routine.
ACTION
Determine cause of error from SM_CREATE_HASH_TBL
and correct.
MESSAGE
An error occurred from START_VOLUME_MGT.
CAUSE
Error from START_VOLUME_MGT, volume management
routine.
ACTION
Determine cause of error from START_VOLUME_MGT
and correct.
MESSAGE
An error occurred from file system
FS_INITIALIZE_FILE_SYSTEM.
CAUSE
Error FS_INITIALIZE_FILE_SYSTEM.
ACTION
Determine cause of error from
FS_INITIALIZE_FILE_SYSTEM and correct.
MESSAGE
An error occurred from file system
FS_PROC_INIT.
CAUSE
Error from FS_PROC_INIT, file system routine.
ACTION
Determine cause of error from FS_PROC_INIT and
correct.
MESSAGE
An error occurred from file system directory
FAKE_LOGON.
CAUSE
Error from FAKE_LOGON, file system directory logon.
ACTION
Determine cause of error from FAKE_LOGON and correct.
MESSAGE
An error occurred from file system
FS_TDIRC_INIT.
CAUSE
Error from FS_TDIRC_INIT, file system routine.
ACTION
Determine cause of error from FS_TDIRC_INIT and
correct.
MESSAGE
This is a fatal option error (filename
wrong); UPDATE renamed INSTALL.
CAUSE
A copy of the PME UPDATE has been given control from
the option routine with the indication that the command
used to call the PME was not UPDATE. Probably was
INSTALL. Probably a copy of UPDATE was renamed
INSTALL.
ACTION
Use a correct copy of UPDATE.
MESSAGE
Disk sparing failed on LDEV 1.
181
Error Messages Viii C 3
System Disk Load
241
242
243
244
245
246
247
182
CAUSE
Error returned from disk sparing of LDEV 1.
ACTION
Determine cause of error from sparing and correct.
MESSAGE
REBOOT_CPU returned control.
CAUSE
The routine REBOOT_CPU has returned control to the
caller. The CPU was probably not rebooted.
ACTION
Determine why control was returned from REBOOT_CPU
and correct. Reboot the CPU and continue.
MESSAGE
Hard loop failed, probably due to compiler or
hardware error, or START/NO START option
error.
CAUSE
The compiler generated loop to stop the CPU on a nostart
option has exited. Generated code or hardware error.
ACTION
Determine why the code exited and correct. Reboot the
CPU and continue.
MESSAGE
Failure from SAVE_BOOT_CMD_TO_DISC.
CAUSE
Error from SAVE_BOOT_CMD_TO_DISC.
ACTION
Determine cause of error from
SAVE_BOOT_CMD_TO_DISC and correct.
MESSAGE
An error was returned by CONFIGURE_DEVICE
configuring the tape drive.
CAUSE
Error from CONFIGURE_DEVICE for tape control.
ACTION
Determine cause of error from CONFIGURE_DEVICE
and correct.
MESSAGE
The procedure found a second IPL on tape; bad
tape.
CAUSE
Found second IPL file on the tape. Invalid tape format.
ACTION
Determine cause of the second IPL on the tape and correct.
Remake the tape and redo the UPDATE or INSTALL.
MESSAGE
An error was returned by ADD_DUMP_FILE.
CAUSE
Error returned from ADD_DUMP_FILE. Internal routine
to add the dump file to the disk and the LIF directory.
ACTION
Determine cause of error from ADD_DUMP_FILE and
correct.
MESSAGE
An error was received from LOAD_POST writing
label sector 0,1 to LDEV 1.
CAUSE
Error from LOAD_POST writing to sector zero and one of
LDEV 1.
ACTION
Determine cause of error from LOAD_POST and correct.
Chapter 4
Error Messages Viii C 3
System Disk Load
248
249
250
251
253
254
255
256
Chapter 4
MESSAGE
No IPL from the tape; disk will not boot.
CAUSE
No IPL file was found on the tape. Invalid tape format.
ACTION
Determine the cause of missing IPL file and correct.
Remake the tape and redo the UPDATE or INSTALL.
MESSAGE
No NL.PUB.SYS from the tape; disk will not
start.
CAUSE
No NL.PUB.SYS file was found on the tape. Invalid tape
format. File is identified by start number in tape file
header.
ACTION
Determine the cause of missing NL.PUB.SYS file and
correct. Remake the tape and redo the UPDATE or
INSTALL.
MESSAGE
An error was received from CREATE_OBJECT for
global area.
CAUSE
Error returned from CREATE_OBJECT for global area.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
An error was received from CREATE_OBJECT for
page 1 buffer.
CAUSE
Error returned from CREATE_OBJECT for page 1 buffer.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
Bad sector table index error.
CAUSE
An internal error occurred in the disk sparing routine
change sector state. Bad sector table index error.
ACTION
Retry the function (INSTALL or UPDATE or START or
mount volume). Write over sector zero to bypass sparing
on this volume and initialize it again. Consult a
Hewlett-Packard System Engineer for help.
MESSAGE
Error on read of TRACK TABLE from
RENDEZVOUSIO.
CAUSE
Error returned from RENDEZVOUSIO for sparing read
track table.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
Error on read of TRACK TABLE from SENDIO.
CAUSE
Error returned from SENDIO for sparing read track table.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
Error on write of TRACK TABLE from
183
Error Messages Viii C 3
System Disk Load
RENDEZVOUSIO.
257
258
259
260
261
262
263
184
CAUSE
Error returned from RENDEZVOUSIO for sparing write
track table.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
Error on write of TRACK TABLE from SENDIO.
CAUSE
Error returned from SENDIO for sparing write track
table.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO reading bad
sector.
CAUSE
Error returned from SENDIO for sparing read sector save
sector.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO writing
sector.
CAUSE
Error returned from SENDIO for sparing write sector save
sector.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO reading
sector from save area.
CAUSE
Error returned from SENDIO for sparing read sector for
restore sector.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from RENDEZVOUSIO
writing sector to new home.
CAUSE
Error returned from RENDEZVOUSIO for sparing write
sector for restore.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
An error was received from SENDIO writing
sector to new home.
CAUSE
Error returned from SENDIO for sparing write sector for
restore sector.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO reading
sector from track.
CAUSE
Error returned from SENDIO for sparing read sector save
track.
Chapter 4
Error Messages Viii C 3
System Disk Load
264
265
266
267
268
269
270
271
Chapter 4
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO writing
sector to save area.
CAUSE
Error returned from SENDIO for sparing write sector save
track.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO reading
sector from track save area.
CAUSE
Error returned from SENDIO for sparing read sector for
restore track.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from RENDEZVOUSIO
writing sector to new home.
CAUSE
Error returned from RENDEZVOUSIO for sparing write
sector for restore track.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
An error was received from SENDIO writing
sector to new home.
CAUSE
Error returned from SENDIO for sparing write sector for
restore track.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
This is a bad SECTOR TABLE index error.
CAUSE
Internal error. Error in sector state in bad sector table.
ACTION
Retry the function (INSTALL, UPDATE, START or mount
volume). Write over sector zero to bypass sparing on this
volume and initialize it again. Call your Hewlett-Packard
Representative.
MESSAGE
An error was received from SENDIO running
sector test.
CAUSE
Error returned from SENDIO for sparing run sector test.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
This is an internal error; error in track
start address.
CAUSE
Internal debug error. Not released. Invalid sector number
from caller for run track test.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An error was received from SENDIO running
track test.
185
Error Messages Viii C 3
System Disk Load
272
273
274
275
276
277
278
282
186
CAUSE
Error returned from SENDIO for sparing run track test.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO running
R.O. track test.
CAUSE
Error returned from SENDIO for sparing run R.O. track
test.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error was received from SENDIO running
controller test.
CAUSE
Error returned from SENDIO for sparing run controller
test.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
This is an invalid sector address.
CAUSE
Internal debug error. Not released. Invalid sector number
from caller for run track test.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An error was received from RENDEZVOUSIO
sparing a sector.
CAUSE
Error returned from RENDEZVOUSIO for sparing spare
sector.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
An error was received from SENDIO sparing a
sector.
CAUSE
Error returned from SENDIO for sparing spare sector.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
This is an internal error in sector state.
CAUSE
Internal error. Error in sector state in bad sector table.
ACTION
Retry the function (INSTALL, UPDATE, START or mount
volume). Write over sector zero to bypass sparing on this
volume and initialize it again. Call your Hewlett-Packard
Representative.
MESSAGE
An error was received from SENDIO sparing a
track.
CAUSE
Error returned from SENDIO for sparing spare track.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
A failure occurred from RENDEZVOUSIO skipping
forward a tape file.
Chapter 4
Error Messages Viii C 3
System Disk Load
283
284
285
286
287
288
289
290
Chapter 4
CAUSE
Error returned from RENDEZVOUSIO for skip tape file.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
A failure occurred from SENDIO skipping
forward a tape file.
CAUSE
Error returned from SENDIO for skip tape file.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
A failure occurred from RENDEZVOUSIO
rewinding tape.
CAUSE
Error returned from RENDEZVOUSIO for rewind tape.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
A failure occurred from SENDIO rewinding
tape.
CAUSE
Error returned from SENDIO for rewind tape.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
A failure occurred from RENDEZVOUSIO
unloading a tape.
CAUSE
Error returned from RENDEZVOUSIO for unload tape.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
A failure occurred from SENDIO unloading a
tape.
CAUSE
Error returned from SENDIO for unload tape.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
A failure occurred from RENDEZVOUSIO reading
file label from tape.
CAUSE
Error returned from RENDEZVOUSIO for read tape file
label. Possible tape read error.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct. Clean tape drive and retry. Clean tape drive,
remake tape and retry.
MESSAGE
A failure occurred from SENDIO reading file
label from tape.
CAUSE
Error returned from SENDIO for read tape file label.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
Not enough data was read from tape reading
the file label.
187
Error Messages Viii C 3
System Disk Load
291
292
293
294
296
297
298
188
CAUSE
Tape read expected 256 bytes and got less than 200 bytes.
Possible tape read error or tape position error.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry.
MESSAGE
A failure was received from RENDEZVOUSIO
skipping backwards on tape.
CAUSE
Error returned from RENDEZVOUSIO for skip record
back.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
A failure was received from SENDIO skipping
backwards on tape.
CAUSE
Error returned from SENDIO for skip record back.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
A second NL.PUB.SYS was found on the boot
tape.
CAUSE
A second NL.PUB.SYS file was found on the tape. Invalid
tape format. File is identified by start number in tape file
header.
ACTION
Determine the cause of the extra NL.PUB.SYS file and
correct. Remake the tape and redo the UPDATE or
INSTALL.
MESSAGE
Can not purge NL.PUB.SYS from disk.
CAUSE
Error returned from HPOPEN for create of NL.PUB.SYS.
File is identified by start number in tape file header.
ACTION
Determine cause of error from HPOPEN and correct.
MESSAGE
A failure occurred from RENDEZVOUSIO reading
user label block.
CAUSE
Error returned from RENDEZVOUSIO for read user label
block of a system file.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct. Clean tape drive and retry. Clean tape drive,
remake tape and retry.
MESSAGE
Length error reading user label block.
CAUSE
EOF read from tape while reading user label data. Invalid
tape. Possible tape read error or tape position error.
ACTION
Determine cause of error and correct. Clean tape drive and
retry. Clean tape drive, remake tape and retry.
MESSAGE
A failure occurred from SENDIO reading user
label block.
Chapter 4
Error Messages Viii C 3
System Disk Load
299
300
301
302
303
304
305
Chapter 4
CAUSE
Error returned from SENDIO for read user label block.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred from FWRITELABEL writing
user label.
CAUSE
Condition code error returned by FWRITE for user label
block.
ACTION
Determine cause of error from FWRITE and correct.
MESSAGE
A failure occurred from RENDEZVOUSIO reading
system file block from tape.
CAUSE
Error returned from RENDEZVOUSIO for read file block.
Possible tape read error or tape position error.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct. Clean tape drive and retry. Clean tape drive,
remake tape and retry.
MESSAGE
This is a premature EOF on tape reading the
system file block.
CAUSE
An EOF was read from the tape before expected while
reading system file data. Invalid tape. Possible tape read
error or tape position error.
ACTION
Determine cause of error and correct. Clean tape drive and
retry. Clean tape drive, remake tape and retry.
MESSAGE
A failure was received from SENDIO reading
system file block.
CAUSE
Error returned from SENDIO for system file block.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred from FWRITE on system file
block.
CAUSE
Condition code error returned by FWRITE for file data
block.
ACTION
Determine cause of error from FWRITE and correct.
MESSAGE
An error occurred from FCLOSE on system file.
CAUSE
Error from FCLOSE for system file.
ACTION
Determine cause of error from FCLOSE and correct.
MESSAGE
There is an error in the number of blocks on
tape for system file; file length error.
CAUSE
Record count error from tape while reading system file
data. Invalid tape. Possible tape read error or tape position
error.
ACTION
Determine cause of error and correct. Clean tape drive and
189
Error Messages Viii C 3
System Disk Load
retry. Clean tape drive, remake tape and retry.
306
307
308
310
311
312
313
314
190
MESSAGE
HPOPEN error occurred for DUMPAREA.
CAUSE
Error returned from HPOPEN for create of
DUMPAREA.MPEXL.SYS.
ACTION
Determine cause of error from HPOPEN and correct.
MESSAGE
An error was received from FWRITE for
DUMPAREA.
CAUSE
Condition code error returned by FWRITE for
DUMPAREA.MPEXL.SYS.
ACTION
Determine cause of error from FCLOSE and correct.
MESSAGE
Error from FCLOSE for DUMPAREA.
CAUSE
Error from FCLOSE for DUMPAREA.MPEXL.SYS file.
ACTION
Determine cause of error from FCLOSE and correct.
MESSAGE
An error was received from HPOPEN for
creating boot file.
CAUSE
Error returned from HPOPEN for create of a boot file.
ACTION
Determine cause of error from HPOPEN and correct.
MESSAGE
An error occurred on reading the tape boot
file block.
CAUSE
Error returned from SENDIO for read file block from tape.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
There was an error in the number of blocks on
the tape for the boot file; file length
error.
CAUSE
User label numbers in tape file label are incorrect. Invalid
tape format. User labels are invalid for a boot file.
ACTION
Determine cause of incorrect numbers and correct.
Remake tape and retry the UPDATE or INSTALL.
MESSAGE
An error was received from FWRITE on the boot
file.
CAUSE
EOF read from tape before expected while reading boot file
data. Invalid tape. Possible tape read error or tape position
error.
ACTION
Determine cause of error and correct. Clean tape drive and
retry. Clean tape drive, remake tape and retry.
MESSAGE
Failure posting page 1 to disk.
CAUSE
Error from LOAD_POST writing to sector zero and one of
LDEV 1.
Chapter 4
Error Messages Viii C 3
System Disk Load
315
316
317
318
319
320
321
Chapter 4
ACTION
Determine cause of error from LOAD_POST and correct.
MESSAGE
An error was received from FCLOSE of boot
file.
CAUSE
Error from FCLOSE for a boot file.
ACTION
Determine cause of error from FCLOSE and correct.
MESSAGE
The procedure failed to add boot file to the
LIF directory.
CAUSE
Error returned from ADD_NEXT_DIR_ENTRY for a boot
file while attempting to add an entry to the LIF directory.
ACTION
Determine cause of error from ADD_NEXT_DIR_ENTRY
and correct.
MESSAGE
There was an error in the number of blocks on
tape for the boot file; file length error.
CAUSE
Record count error from tape while reading boot file data.
Invalid tape. Possible tape read error or tape position
error.
ACTION
Determine cause of error and correct. Clean tape drive and
retry. Clean tape drive, remake tape and retry.
MESSAGE
An error was received from RENDEZVOUSIO
reading first label from tape.
CAUSE
Error returned from RENDEZVOUSIO for read labels.
First read from the tape. Possible tape read error or tape
position error.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct. Clean tape drive and retry. Clean tape drive,
remake tape and retry.
MESSAGE
An error was received from SENDIO reading the
first label from the tape.
CAUSE
Error returned from SENDIO for read labels. First read
from the tape.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred on the first read; not
enough data read.
CAUSE
Tape read expected 256 bytes and got less than 200 bytes.
Possible tape read error or tape position error. First read
from the tape. Reading labels.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry.
MESSAGE
An error was received from RENDEZVOUSIO
reading the second label from the tape.
191
Error Messages Viii C 3
System Disk Load
322
323
324
325
326
327
192
CAUSE
Error returned from RENDEZVOUSIO for read labels.
Second read from the tape. Possible tape read error or tape
position error.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct. Clean tape drive and retry. Clean tape drive,
remake tape and retry.
MESSAGE
An error was received from SENDIO reading the
second label from the tape.
CAUSE
Error returned from SENDIO for read labels. Second read
from the tape.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred on the second read; not
enough data read.
CAUSE
Tape read expected 256 bytes and got less than 200 bytes.
Possible tape read error or tape position error. Second read
from the tape. Reading labels.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry.
MESSAGE
An error was received from RENDEZVOUSIO
reading the LIF directory from the tape.
CAUSE
Error returned from RENDEZVOUSIO for read labels.
Third read from the tape. Possible tape read error or tape
position error.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct. Clean tape drive and retry. Clean tape drive,
remake tape and retry.
MESSAGE
An error was received from SENDIO reading the
LIF directory from the tape.
CAUSE
Error returned from SENDIO for read labels. Third read
from the tape.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
An error occurred reading the LIF directory
from the tape; not enough data.
CAUSE
Tape read expected 256 bytes and got less than 200 bytes.
Possible tape read error or tape position error. Third read
from the tape. Reading labels.
ACTION
Clean tape drive and retry. Clean tape drive, remake tape
and retry.
MESSAGE
This is not an MPE/iX boot tape; LIF label
bad.
CAUSE
LIF label check failed. Not a valid boot tape.
Chapter 4
Error Messages Viii C 3
System Disk Load
328
330
331
332
333
334
335
Chapter 4
ACTION
Retry with a valid boot tape.
MESSAGE
This is not an MPE/iX boot tape; MPE/iX label
bad.
CAUSE
MPE/iX label check failed. Not a valid boot tape.
ACTION
Retry with a valid boot tape.
MESSAGE
An error was received from SENDIO writing
disk page 1.
CAUSE
Error from LOAD_POST writing to sector zero and one of
LDEV 1. First write to sector zero and one of LDEV 1.
ACTION
Determine cause of error from LOAD_POST and correct.
MESSAGE
An error was received from CREATE_OBJECT for
first tape I/O buffer.
CAUSE
Error returned from CREATE_OBJECT for tape I/O
buffer 1.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
An error was received from CREATE_OBJECT for
a second tape I/O buffer.
CAUSE
Error returned from CREATE_OBJECT for tape I/O
buffer 2.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
An error was received from CREATE_OBJECT for
the tape LIF directory buffer.
CAUSE
Error returned from CREATE_OBJECT for tape LIF
directory buffer.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
An error was received from CREATE_OBJECT for
the disk LIF directory buffer.
CAUSE
Error returned from CREATE_OBJECT for disk LIF
directory buffer.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
An error was received from CREATE_OBJECT for
the tape LIF label buffer.
CAUSE
Error returned from CREATE_OBJECT for tape LIF label
buffer.
ACTION
Determine cause of error from CREATE_OBJECT and
193
Error Messages Viii C 3
System Disk Load
correct.
336
337
338
339
340
341
342
343
194
MESSAGE
An error was received from CREATE_OBJECT for
the tape MPE/iX label.
CAUSE
Error returned from CREATE_OBJECT for tape MPE/iX
label buffer.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
An error was received from HPOPEN for
creating LIF directory.
CAUSE
Error from HPOPEN for LIFDIREC file.
ACTION
Determine cause of error from HPOPEN and correct.
MESSAGE
An error was received from FWRITE for the LIF
directory.
CAUSE
Error from FWRITE for LIFDIREC file.
ACTION
Determine cause of error from FWRITE and correct.
MESSAGE
An error was received from FCLOSE, closing
the LIF directory.
CAUSE
Error from FCLOSE for LIFDIREC file.
ACTION
Determine cause of error from FCLOSE and correct.
MESSAGE
An error occurred writing page 1 of the disk.
CAUSE
Error from LOAD_POST writing sector zero and one of
LDEV 1.
ACTION
Determine cause of error from LOAD_POST and correct.
MESSAGE
An error was received from RENDEZVOUSIO
reading the disk labels.
CAUSE
Error returned from RENDEZVOUSIO for read disk page
1, sector zero and one.
ACTION
Determine cause of error from RENDEZVOUSIO and
correct.
MESSAGE
An error was received from SENDIO reading the
disk labels.
CAUSE
Error returned from SENDIO for read disk page 1, sector
zero and one.
ACTION
Determine cause of error from SENDIO and correct.
MESSAGE
This is not an MPE XL disk. UPDATE failed;
INSTALL required.
CAUSE
Disk LDEV 1 is not a valid MPE/iX system master volume.
ACTION
Replace with a valid MPE/iX system master and retry.
Chapter 4
Error Messages Viii C 3
System Logging
Volume cannot be updated, INSTALL is required.
345
346
347
348
349
MESSAGE
System Abort 345
CAUSE
Internal error. Invalid spare state. Debug code not
released.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A failure was received from CREATE_OBJECT for
a semaphore to use to interlock the label.
CAUSE
Error returned from CREATE_OBJECT for volume label
semaphore.
ACTION
Determine cause of error from CREATE_OBJECT and
correct.
MESSAGE
A failure was received from
CREATE_BAD_SECTOR_TABLE.
CAUSE
Error returned from CREATE_BAD_SECTOR_TABLE.
ACTION
Determine cause of error from
CREATE_BAD_SECTOR_TABLE and correct.
MESSAGE
A failure was received from XM_INITXM.
CAUSE
Error from STARTGOLDENXID, transaction
management routine.
ACTION
Determine cause of error from STARTGOLDENXID and
correct.
MESSAGE
A failure was received from XM_INITXM.
CAUSE
Error from ENDGOLDENXID, transaction management
routine.
ACTION
Determine cause of error from ENDGOLDENXID and
correct.
System Logging
(Subsystem 206)
900
Chapter 4
MESSAGE
System logging is not enabled at the present
time.
CAUSE
An attempt was made to log a record, switch the log file,
resume logging, show logging statistics or to shutdown the
logging while the logging facility was not enabled.
ACTION
Enable the logging facility if desired.
195
Error Messages Viii C 3
System Logging
901
902
903
904
905
999
196
MESSAGE
The specified log event cannot be logged
because it has not been enabled via the
SYSGEN program.
CAUSE
System logging cannot log a record because the specified
log event is not enabled.
ACTION
Enable the specified log event type if desired.
MESSAGE
System logging is currently suspended.
CAUSE
System logging is suspended due to an error. It cannot log
a record, switch the log file, show system logging statistics
or shutdown the system logging facility.
ACTION
Resume system logging.
MESSAGE
RESUMELOG cannot be performed since logging
is not currently suspended.
CAUSE
A request to resume the system logging facility was
received when system logging was not suspended. The
request is ignored.
ACTION
User information only. No action required.
MESSAGE
The specified record cannot be logged because
a SWITCHLOG is currently pending.
CAUSE
The system log file is full and cannot accomodate any
additional records. Log records are lost until a new log file
is created.
ACTION
Create a new log file.
MESSAGE
The specified record cannot be logged because
it is larger than the record length of the
system log file.
CAUSE
The log record length is larger than the log file block size.
The record is not logged.
ACTION
User information only. No action required.
MESSAGE
A recover statement was unexpectedly invoked
in a system logging intrinsic.
CAUSE
A recover statement was unexpectedly invoked when
trying to log a record, switch the log file, show system
logging statistics, resume logging or to shutdown the
system logging facility.
ACTION
User information only. No action required.
Chapter 4
5 Error Messages V iii C 4
Table Management
(Subsystem 108)
50
51
53
54
58
59
63
MESSAGE
The entry size is less than the minimum entry
size.
CAUSE
The entry size parameter is too small.
ACTION
Correct the parameter.
MESSAGE
The header is invalid.
CAUSE
Two words at the beginning of the header should point
back to the header.
ACTION
Take a system dump.
MESSAGE
The entry size is greater than the maximum
size.
CAUSE
The entry size is greater than the pool size in a variable
entry size table.
ACTION
Correct the parameter.
MESSAGE
The initial size is greater than the maximum
size.
CAUSE
The pool initial size is greater than the maximum size.
ACTION
Correct the parameter.
MESSAGE
The last free entry is less than the first
free entry.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
The free link offset is greater than the
entry size.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
There is no entry in the pool.
197
Error Messages V iii C 4
Table Management
CAUSE
The pool does not contain any more entries.
ACTION
Create the table with a larger primary or secondary pool of
entries.
MESSAGE
There are no entries in the entire table.
CAUSE
Both primary and secondary pools are empty.
ACTION
Create the table with more entries.
MESSAGE
Attempted to return entry to full pool.
CAUSE
More entries were returned than were originally in the
pool.
ACTION
Check the logic which gets and returns entries.
MESSAGE
The increment size is greater than the
maximum pool size.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
The configured free entries are greater than
the initial size.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
Single object header/body with inconsistent
allocation.
CAUSE
Body and header must both be allocated or not allocated
initially.
ACTION
Correct the parameters.
73
MESSAGE
The primary and secondary pools overlap in
unified pool.
74
MESSAGE
The negative parameter value is illegal.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
Table semaphore type is out of range.
CAUSE
The semaphore specification is not valid.
ACTION
Correct the parameter.
MESSAGE
The entry number is not in the free list.
CAUSE
Monotonic table entry number is outside the range of the
free list.
ACTION
Correct the parameter.
MESSAGE
The entry has not yet been allocated.
64
69
70
71
72
75
76
78
198
Chapter 5
Error Messages V iii C 4
Table Management
79
80
81
82
83
84
85
86
Chapter 5
CAUSE
The desired entry number is either less than zero or
greater than the number of entries now in the body.
ACTION
Correct the parameter.
MESSAGE
Space management WRITE disk error.
CAUSE
sm_write returned an error to post_table.
ACTION
Take a system dump.
MESSAGE
Posting requires a single object.
CAUSE
An attempt was made to create a table with posting
requested, but not with a single object.
ACTION
Correct the parameter.
MESSAGE
There are no allocated entries.
CAUSE
Call to entry_allocated with wrong entry number, or call to
get_next_allocated_entry with a bad start number, or call
to get_next_allocated_entry and entry not found.
ACTION
Take a system dump.
MESSAGE
The allocated entry list does not exist.
CAUSE
Call to entry_allocated, but tbl_allocated_list not in
header options.
ACTION
Correct the parameter.
MESSAGE
The variable table can not have an allocated
list.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameter.
MESSAGE
Can not lock the table semaphore.
CAUSE
An attempt was made to lock the table semaphore while
on the Interrupt Control Stack (ICS), or the cb_lock
procedure failed, or the wait failed if tbl_dont_lock was
used in the header options.
ACTION
Take a system dump.
MESSAGE
Can not mix the allocated list and the
variable table.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
Posting requires a permanent object.
CAUSE
An attempt was made to create a table with the
tbl_post_object procedure without also using the
tbl_permanent_object procedure.
199
Error Messages V iii C 4
Table Management
87
92
98
99
107
157
158
159
200
ACTION
Correct the parameters.
MESSAGE
The PUT WAIT queue requires the table to be
locked.
CAUSE
While in the block_on_resource procedure, the table
semaphore was either unlocked or locked by another
process.
ACTION
Take a system dump.
MESSAGE
Bad allocated list option.
CAUSE
Incompatible options were used with the tbl_allocated list.
ACTION
Correct the parameters.
MESSAGE
The variable initial size is not 4-byte
aligned.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
The variable increment size is not 4-byte
aligned.
CAUSE
There are bad table creation parameters.
ACTION
Correct the parameters.
MESSAGE
Out of disk space.
CAUSE
The attempt to expand the table ran out of disk space.
ACTION
Free up disk space.
MESSAGE
Large Object cannot be created.
CAUSE
A create object request was received that exceeded the
maximum object size supported. This maximum is
currently 128GB.
ACTION
Request a smaller object size that is within legal limits.
MESSAGE
Virtual Space cannot be deallocated.
CAUSE
An error occurred during the deallocation of an object
which prevented the virtual address space from being
recovered.
ACTION
No immediate action need be taken. However, if this
situation happens over a long enough period, available
virtual address space may become scarce. In this case, a
reboot of the system is required to clear the problem.
MESSAGE
Prefetch size exceeded max_prefetch_size
(4GB).
CAUSE
A prefetch request was received which exceeded the
maximum prefetch size, which is currently 4GB.
Chapter 5
Error Messages V iii C 4
TermDSM
160
ACTION
Request a smaller size that is within the legal limits.
MESSAGE
SR5 Objects cannot exceed 1GB.
CAUSE
A request to create an object in SR5 short address space
was received that exceeded the architected maximum SR5
address space of 1GB.
ACTION
Create a smaller object, or create the object in long
pointer space.
MESSAGE
You have entered an unknown or incorrect
command. Please try again. (TDSM 15)
CAUSE
You have entered something that is not a TermDSM
command or a command that is not valid in this context.
ACTION
Commands that are valid at this time are listed in the
prompt. Please try again. Type HELP or refer to the
reference documentation for more information.
MESSAGE
TermDSM has compiled without $partial eval$
in effect. It cannot continue. This problem
must be fixed at the factory. (TDSM 16)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Your security level (3) is too low to use
TermDSM. Please log on with level
0, 1, or 2 security. (TDSM 17)
CAUSE
You do not have the correct user capabilities to use
TermDSM. For level 0, you need SM capability. For level 1,
you need SM or DI capability. For level 2, you need SM or
DI or OP capability.
ACTION
Logon as a user with the correct capabilities for the
TermDSM functions you wish to use. Refer to reference
documentation for the security levels of each command
and subcommand.
MESSAGE
You have entered a bad port number. Port
numbers range from 0 to 7. (TDSM 18)
CAUSE
The value you entered is not a number between zero and
seven.
TermDSM
(TDSM)
15
16
17
18
Chapter 5
201
Error Messages V iii C 4
TermDSM
19
20
21
22
23
24
25
202
ACTION
Enter a valid port number. Check the port number on the
back of the DTC if necessary.
MESSAGE
The port number is missing or invalid. Port
numbers range from 0 to 7. (TDSM 19)
CAUSE
The port number was not entered or is unrecognizable.
ACTION
Enter a valid port number. Refer to the reference
documentation for syntax.
MESSAGE
You have entered an incorrect ldev number.
Ldev numbers are positive integers. (TDSM 20)
CAUSE
The value that you entered as a logical device number is
not a number greater than zero.
ACTION
Enter a valid ldev number. Note that you can also use the
port subcommand.
MESSAGE
The ldev number is missing or invalid. Ldev
numbers are positive integers. (TDSM 21)
CAUSE
The logical device number was not entered or is
unrecognizable.
ACTION
Enter a valid ldev number. Note that you can also use the
port subcommand.
MESSAGE
You have entered an invalid SIC card number.
SIC card numbers range from 0 to 5. (TDSM 22)
CAUSE
The card number that you entered in is not the range zero
to five.
ACTION
Doublecheck the card numbers by looking at the back of
the DTC. Enter the card number again.
MESSAGE
The SIC card number is missing or invalid.
SIC card numbers range from 0 to 5. (TDSM 23)
CAUSE
The card number was not entered or is unrecognizable.
ACTION
Enter the card number again. Refer to the prompt or to the
reference documentation for syntax.
MESSAGE
You have entered an incorrect DTC number.
Please choose a DTC number from
this list. (TDSM 24)
CAUSE
The value entered does not correspond with any DTC on
the system.
ACTION
The DTCs on the system are listed with their numbers.
Enter one of the numbers displayed.
MESSAGE
The DTC number is missing or invalid. Please
choose a DTC number from this list. (TDSM 25)
CAUSE
The DTC number was not entered or is unrecognizable.
Chapter 5
Error Messages V iii C 4
TermDSM
27
32
34
35
Chapter 5
ACTION
The DTCs on the system are listed with their numbers.
Enter one of the numbers displayed.
MESSAGE
TermDSM cannot do the dump because there are
already too many dump files. Please purge
some. Dump files are of the form
TRMnnnaa.PUB.SYS. where nn is a 3 digit
number and aa is 2 alphabetic characters.
(TDSM 27)
CAUSE
The dump files TRMdddAA through TRMdddZZ already
exist. (The sequence ddd is the current Julian date.)
ACTION
Delete some files beginning with the file called TRMdddAA
since this is the oldest file. Note that if all files for this
Julian date already exist, there are over 600 dump files for
today. You can delete most of these files.
MESSAGE
Your security level (3) is too low to take
dumps. Please log on with level 2 security to
dump ports, or level 0 security to dump ports
and DTCs. (TDSM 32) For level 1, you need SM
or DI capability. For level 2, you need SM or
DI or OP capability.
CAUSE
You do not have the correct user capabilities to use this
function.
ACTION
Log on with level 0, 1, or 2 security. Refer to the reference
documentation for the security levels of each command
and subcommand.
MESSAGE
That ldev does not exist. Please check the
ldev number, or dump the associated port
instead. (TDSM 34)
CAUSE
Although you entered a number in a range that could be
an ldev number, that ldev number is not configured on the
system.
ACTION
Verify the ldev number by entering the SHOWJOB
command. You can also dump information associated with
the device by using the PORT subcommand (which uses the
physical address instead of the ldev number).
MESSAGE
That DTC is owned by another person running
TermDSM. You may override that user and
continue. (WARNING : This may have
unpredictable results. It's safer to find the
other user and exit TermDSM. (TDSM 35) Do you
want to override the other user (yes or no)?
CAUSE
More than one person is using TermDSM and directing
operations to the same DTC at the same time.
203
Error Messages V iii C 4
TermDSM
36
37
38
39
42
204
ACTION
It is permissible for two or more users to run TermDSM
simultaneously as long as the users do not reference the
same DTC. In this case, message 35 will not appear. If one
TermDSM user chooses to override another by continuing,
it is likely that the overridden TermDSM will produce
error messages. This facility is provided for the case where
a terminal running TermDSM is hung and therefore
cannot exit the program. Note that if one TermDSM user
resets the port of another TermDSM user, this can cause
the system to go down.
MESSAGE
No ldevs seem to be configured on your
system. (TDSM 356)
CAUSE
Necessary configuration information does not exist on the
system.
ACTION
Make sure the file NMCONFIG.PUB.SYS exists. Bring the
system down and back up again, making sure that the
proper SYSGEN files are used. (The SYSGEN files used
are determined by the boot path. The file
NMCONFIG.PUB.SYS is used automatically.) If the problem
persists, contact your HP support representative.
MESSAGE
The dump process can't find out the length of
the data area. (TDSM 37)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
The data area is longer than TermDSM's dump
buffer. (TDSM 38)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
TermDSM never received a reply to its dump
data area request. (TDSM 39)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
You must have high (1) security to perform
this function.
For level 1, you need SM or DI capability.
(TDSM 42)
CAUSE
You do not have the correct user capabilities to use this
function.
ACTION
Logon as a user with the correct capabilities for the
TermDSM functions you wish to use. Refer to the
reference documentation for the security levels of each
command and subcommand.
Chapter 5
Error Messages V iii C 4
TermDSM
43
44
56
62
64
70
Chapter 5
MESSAGE
You can't do this from your own DTC. Please
run TermDSM from another DTC or from the
console. (TDSM 43)
CAUSE
If you were permitted to selftest, dump, or reset the DTC
to which you are logged on, your session would be aborted
and you would be unable to get the test results.
ACTION
Move to a terminal on another DTC or the system console
to run TermDSM.
MESSAGE
Warning: This will reset all users on that
DTC. As many as 48 terminal users could be
affected. (TDSM 44)
CAUSE
If you continue, all user sessions on this DTC will be
aborted.
ACTION
If you want to continue, you should alert all the users that
their sessions will be aborted.
MESSAGE
Your answer must be at least 1 and no more
than 65535. (TDSM 56)
CAUSE
The value entered is not in the range 1 to 65535.
ACTION
Enter a value in the range. Diagnostic loop counts are
limited to this range.
MESSAGE
Use the CCTL option (:FILE LIST;DEV=LP;CCTL)
when printing this file. (TDSM 62)
CAUSE
Informational message.
ACTION
When printing the dump file, use the CCTL option in the
print file equation. This will format the printed output in
an organized way. Printed output of dump files will be
acceptable if they are not printed with the CCTL option.
MESSAGE
The following two files make up the DTC dump.
Please deliver both to your HP
representative. (TDSM 64)
CAUSE
Informational message.
ACTION
Document the problem (the reason you took a dump), and
deliver it to your HP support representative along with
the dump files, preferably on magnetic tape.
MESSAGE
There are no DTCs configured on your system.
(TDSM 70)
CAUSE
Necessary configuration information does not exist on the
system.
ACTION
Check the NMCONFIG.PUB.SYS file for proper DTC
configuration (using :NMMGR). Bring the system down
and back up again. If the problem persists, contact your
205
Error Messages V iii C 4
TermDSM
HP support representative.
71
80
81
82
86
MESSAGE
There are more DTCs on your system than
TermDSM can reference. Here are the ones
TermDSM can reference. (TDSM 71)
CAUSE
You are using more than 32 DTCs on the system. You will
not be able to perform any TermDSM functions on any
DTCs that are not listed in this message.
ACTION
Contact your HP support representative.
MESSAGE
You can't reset your own port or ldev. Please
run TermDSM from a
different port or ldev to do this. (TDSM 80)
CAUSE
Verify the ldev numbers entered. If you want to reset a
port, you cannot be logged on to that port; the operation
will abort your session.
ACTION
If you want to reset the port you are using, move to
another port or the system console to run TermDSM.
MESSAGE
That ldev is unknown (not configured). Please
check the ldev number, or use
reset port. (TDSM 81)
CAUSE
Although a number was entered in a range that could be
an ldev number, that number is not configured on the
system.
ACTION
Verify the ldev number by entering the SHOWJOB
command. You can also reset ports by using the PORT
subcommand (which uses the physical address instead of
the ldev number).
MESSAGE
You must have high (1) or medium (2) security
to do resets, and high (1)
security to reset DTCs. (TDSM 82)
For level 1, you need SM or DI capability.
For level 2, you need SM or DI
or OP capability.
CAUSE
You do not have the correct user capabilities to do this
function.
ACTION
Logon as a user with the correct capabilities for the
functions you wish to use. Refer to the reference
documentation for the security level of each command and
subcommand.
MESSAGE
You must have high (1) or medium (2) security
to test ports, and high (1)
security to selftest DTCs. (TDSM 86)
For level 1, you need SM or DI capability.
206
Chapter 5
Error Messages V iii C 4
TermDSM
For level 2, you need
SM or DI or OP capability.
93
110
113
114
115
Chapter 5
CAUSE
You do not have the correct user capabilities to do this
function.
ACTION
Logon as a user with the correct capabilities for the
TermDSM functions you wish to use. Use the appropriate
reference materials to determine the security level of each
command and subcommand.
MESSAGE
TermDSM could not open the DTC manager, so
the DTC dump could not be obtained. (TDSM 93)
CAUSE
Internal error, unless another TermDSM was being run
against that same DTC and you chose not to override the
other user. There is no error in this case.
ACTION
Contact your HP support representative (if it is an
internal error).
MESSAGE
You can't test your own port. Please run
TermDSM from another port. (TDSM 110)
CAUSE
Doublecheck the numbers entered. If you wish to test a
port, you cannot be logged on to that port; the operation
will abort your session and you will be unable to obtain the
results of the test.
ACTION
If you want to test the port to which you are logged on,
move to another port or the system console to run
TermDSM.
MESSAGE
Please put a loopback hood on the port,
before answering the "How may times?"
question. (TDSM 113)
CAUSE
The hardware must be present before the diagnostic is
run.
ACTION
Refer to the appropriate TermDSM manual for
information on port loopback tests.
MESSAGE
Please connect and make ready (power on,
remote mode, etc.) a supported terminal,
before answering the "How many times?"
question. (TDSM 114)
CAUSE
The hardware must be present before the diagnostic is
run.
ACTION
Refer to the appropriate TermDSM manual for
information on terminal loopback tests.
MESSAGE
Please connect and make ready (power on,
remote mode, etc.) a supported printer (or
terminal), before answering the "How many
207
Error Messages V iii C 4
TermDSM
times?" message. (TDSM 115)
121
122
170
200
201
208
CAUSE
The hardware must be present before the diagnostic is
run.
ACTION
Refer to the appropriate TermDSM manual for
information on the port test.
MESSAGE
Warning: The LDM dump is suspect. Consecutive
dumps did not match. (TDSM 121)
CAUSE
This message is written to dump files and never appears
as an error message to a user. There was activity during
the dump process, so part of the dump relating to the
Logical Device Manager might be inconsistent with the
rest of the dump.
ACTION
Submit the dump to your HP support representative.
MESSAGE
You can't reset your own SIC. Please run
TermDSM from another SIC or DTC, or from the
console. (TDSM 122)
CAUSE
Your own session is on this SIC (serial interface card). If
you wish to reset a SIC, you cannot be logged onto that
card; the operation will abort your session and you will be
unable to obtain the results.
ACTION
Move to a port on a different DTC or SIC, or to the system
console, to run TermDSM.
MESSAGE
The Distributed Terminal Subsystem software
does not exist. Please verify that the
NMCONFIG.PUB.SYS file is correct and
validated, and the system has booted up
without errors. This situation prevents
TermDSM from continuing. (TDSM 170)
CAUSE
The NMCONFIG.PUB.SYS file does not exist, or has no
DTCs configured.
ACTION
Check the NMCONFIG.PUB.SYS file for proper DTC and
terminal configurations (using NMMGR), then shutdown
and restart the system.
MESSAGE
DTC and mainframe software versions are
incompatible. (TDSM 200)
CAUSE
Incompatibilities were found between subsystem software
on the HP 3000 and subsystem software on the DTC.
ACTION
Contact your HP support representative to check the
DTCM and download file versions with NMMAINT. If this
is not the problem, the cause is an internal error.
MESSAGE
Bad message length. (TDSM 201)
CAUSE
Internal error.
Chapter 5
Error Messages V iii C 4
TermDSM
203
204
205
206
207
208
213
218
219
Chapter 5
ACTION
Contact your HP support representative.
MESSAGE
Invalid operation. (TDSM 203)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Request not supported. (TDSM 204)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Sub request not supported. (TDSM 205)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Entity not supported. (TDSM 206)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
No such entity. (TDSM 207)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
No parm for entity. (TDSM 208)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
The DTC reported an error or failure. (TDSM
213)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
End of Record received. Time = xx msec. (TDSM
218)
CAUSE
Probable hardware failure.
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Too many characters came back. Time = xx
msec. (TDSM 219)
CAUSE
More characters were returned than were sent. Someone
might have pressed a key on the terminal under test, if
this was a terminal loopback. Probable hardware failure.
209
Error Messages V iii C 4
TermDSM
220
221
222
223
226
229
210
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Parity error. Time = xx msec. (TDSM 220)
CAUSE
Probable hardware failure.
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Hardware receive overrun. Time = xx msec.
(TDSM 221)
CAUSE
Probable hardware failure.
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Framing error. Time = xx msec. (TDSM 222)
CAUSE
Probable hardware failure.
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
SIC Buffer overflow. Time = xx msec. (TDSM
223)
CAUSE
Internal error.
ACTION
Contact you HP support representative.
MESSAGE
No record separator in Vplus. Time = xx msec.
(TDSM 226)
CAUSE
Probable hardware failure.
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Read timeout (no data came back). Time = xx
msec. If external loopback, check loopback
hood. If terminal loopback, check
Chapter 5
Error Messages V iii C 4
TermDSM
connections, terminal configuration, etc.
(TDSM 229)
230
231
232
Chapter 5
CAUSE
No or too few characters came back from the loopback.
ACTION
If this is an internal loopback, this indicates a hardware
problem. Contact your HP support representative. You can
obtain additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics. If this is an external loopback, check the
loopback hood to verify that it is securely connected and on
the correct port. If this is a terminal loopback, verify that a
supported, powered on terminal is securely connected to
the proper port. Check baud rate, parity, etc. Note that the
terminal configuration must match the configuration file,
not the state the terminal was in when it was last used. If
this does not help, run internal, then external loopback to
discriminate between a DTC problem and a
terminal/cabling problem.
MESSAGE
Alternate end-of-record received. Time = xx
msec. (TDSM 230)
CAUSE
Probable hardware failure.
ACTION
Contact your HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Subsystem break. Time = xx msec. (TDSM 231)
CAUSE
Probable hardware failure.
ACTION
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
No modem was connected during the operation.
Time = xx msec. (TDSM 232)
CAUSE
During the test, the modem on that port was disconnected.
ACTION
Reconnect the modem and try the test again. If the failure
continues, or if there was no modem in use on that port,
there is a probable hardware failure. Contact your HP
support representative. You can obtain additional
information by running the card selftest (through the SIC
subcommand of the TermDSM RESET command), the DTC
selftest, and the DTC offline diagnostics.
211
Error Messages V iii C 4
TermDSM
234
235
236
238
239
240
241
212
MESSAGE
Console attention. Time = xx msec. (TDSM 234)
CAUSE
Probable hardware failure.
ACTION
Contact your HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
Operation aborted. (TDSM 235)
CAUSE
The operation was aborted by the DTC. Possibly, the
download file is invalid.
ACTION
Verify the version and integrity of the download file.
Contact your HP support representative. You can obtain
additional information by running the DTC selftest DTC
selftest or the DTC offline diagnostic.
MESSAGE
End of dump file encountered. (TDSM 236)
CAUSE
The end of the DTC upload (dump) file was encountered
when there was still more information to write.
ACTION
Verify that there is sufficient disc space (approx. 2200
sectors are required). Otherwise, contact your HP support
representative.
MESSAGE
Security invalid. (TDSM 238)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Bad packet. (TDSM 239)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
During a DTC reset/dump request from the
mainframe. (TDSM 240)
CAUSE
Informational message which can be printed after an error
message. It describes in which phase of an operation the
error occurred.
ACTION
Refer to the cause and action descriptions for the actual
error message preceding message 240.
MESSAGE
During the DTC download operation. (TDSM 241)
CAUSE
Informational message which may be printed after an
error message. It describes in which phase of an operation
the error occurred.
ACTION
Refer to the cause and action descriptions for the actual
error message preceding message 241.
Chapter 5
Error Messages V iii C 4
TermDSM
242
243
244
245
247
248
Chapter 5
MESSAGE
During a DTC upload (dump) operation. (TDSM
242)
CAUSE
Informational message which may be printed after an
error message. It describes in which phase of an operation
the error occurred.
ACTION
Refer to the cause and action descriptions for the actual
error message preceding message 242.
MESSAGE
Bad parameter from TermDSM. (TDSM 243)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Timeout waiting for the DTC to respond. The
DTC may be powered off, malfunctioning, or
misconfigured. (TDSM 244)
CAUSE
The TermDSM command resulted in an instruction being
sent to a DTC, and the DTC did not respond.
ACTION
Note that the DTC list printed by TermDSM is only a list
of the DTCs configured, not a list of installed, powered on,
and working DTCs. If the DTC in question was working,
and no changes were made to the configuration file, ensure
that the DTC is powered on. If so, this error indicates a
probable hardware error. Contact your HP support
representative. If this is a new installation or DTC, which
has never been run before, the above comments can still
apply. However, if the configuration is incorrect, a
functional DTC might still not respond. Check the
configuration file, power to the DTC, connections, etc. If
problems persist, contact your HP support representative.
This error can also be the result of a LAN problem. If other
DTC(s) are working on the same LAN, the problem is
probably related to the DTC or its configuration. If there is
only one DTC, or other DTCs on the same LAN are
unresponsive, then the LAN hardware or software might
be at fault. The LAN diagnostic LANDAD can be run to
investigate LAN problems.
MESSAGE
Write to IEEE 802.3 DAM failed. (TDSM 245)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Bad Network Management packet received from
DTC. (TDSM 247)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
The DTC requested to be downloaded during the
213
Error Messages V iii C 4
TermDSM
operation. (TDSM 248)
249
250
251
252
253
254
255
214
CAUSE
The DTC was trying to power up at the same time you
were trying to access it.
ACTION
Wait for the download, or upload/download, to complete
(as shown by the console messages). Verify then that the
DTC is operational. If not, contact your HP support
representative.
MESSAGE
The DTC requested that it be dumped during
the operation. (TDSM 249)
CAUSE
The DTC detected an internal error at the same time you
were trying to access it through TermDSM.
ACTION
Wait for the download, or upload/download, to complete
(as shown by the console messages). Then verify if the
DTC is operational. If not, contact your HP support
representative.
MESSAGE
DTC and mainframe software versions are
incompatible. (TDSM 250)
CAUSE
Incompatibilities were found between subsystem software
on the HP 3000 and subsystem software on the DTC.
ACTION
Contact your HP support representative.
MESSAGE
Bad RMP packet received from DTC. (TDSM 251)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Could not open the download or dump file.
(TDSM 252)
CAUSE
Files pertaining to this operation cannot be accessed.
ACTION
If this is a dump, verify that sufficient disc space exists to
create the dump file. Approximately 2200 sectors of disc
space is required. If enough disc space is available (or if
you were not trying to perform a dump operation), contact
your HP support representative.
MESSAGE
Unable to get a system timer. (TDSM 253)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Software bug encountered. (TDSM 254)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Dump overflow: DTC sent more data than
expected. (TDSM 255)
Chapter 5
Error Messages V iii C 4
TermDSM
256
257
258
259
260
Chapter 5
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
MPE/XL create object failed. (TDSM 256)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Unknown internal error. (TDSM 257)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Application request timeout occurred. (TDSM
258)
CAUSE
Internal error. This means two users of TermDSM were
directing TermDSM commands to the same DTC at the
same time, and the other TermDSM user answered "yes"
to the override question (see TermDSM message 35).
Other error messages are likely to be printed also, because
your operations were interrupted. These error messages
should be ignored. There is nothing wrong with multiple
users of TermDSM running at the same time, as long as
they do not try to direct commands to the same DTC at the
same time. The message and interlock system of
TermDSM message 35 was designed to prevent this
conflict.''
ACTION
Contact your HP support representative.
MESSAGE
DTC not opened by this TermDSM. Possibly your
TermDSM was overridden by another TermDSM.
(TDSM 259)
CAUSE
Another user of TermDSM has explicitly overridden your
use of TermDSM.
ACTION
Locate and coordinate users of TermDSM. This means two
users of TermDSM were directing TermDSM commands to
the same DTC at the same time, and the other TermDSM
user answered "yes" to the override question (see
TermDSM message 35). Other error messages are likely to
be printed. These error messages should be ignored. There
is nothing wrong with multiple users of TermDSM
running at the same time, as long as they do not try to
direct commands to the same DTC at the same time. The
message and interlock system of message 35 was designed
to prevent this conflict.
MESSAGE
Bad NMP error code received. (TDSM 260)
CAUSE
Unknown error reported by the Distributed Terminal
Subsystem to TermDSM.
215
Error Messages V iii C 4
TermDSM
261
262
263
264
270
216
ACTION
Contact your HP support representative.
MESSAGE
Bad RMP error code received. (TDSM 261)
CAUSE
Unknown error reported by the Distributed Terminal
Subsystem to TermDSM.
ACTION
Contact your HP support representative.
MESSAGE
The DTC subsystem has reported that an error
was detected. (TDSM 262)
CAUSE
This is the standard message that precedes specific error
messages.
ACTION
Follow the instructions for the error message that follows
this message.
MESSAGE
An error of unknown type was reported by the
DTS subsystem. (TDSM 263)
CAUSE
An error unknown to TermDSM was reported by the
Distributed Terminal Subsystem.
ACTION
Contact your HP support representative.
MESSAGE
The DTC reported an unknown status as a
result of the loopback. Time taken=xx. (TDSM
264)
CAUSE
An error unknown to TermDSM was reported by the
Distributed Terminal Subsystem.
ACTION
Contact your HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
The port is malfunctioning, or not present on
that SIC. Modem SICs have ports zero to five,
and all other SICs have ports zero to seven.
(TDSM 270)
CAUSE
The DTC has reported that the port in question is bad or
does not exist.
ACTION
Note the range of ports in the error message. If you are
specified a port that does not exist, verify the information
to determine the correct port. For reset and dump, you can
specify an ldev number instead of the port to do the
operation. If the port does exist, a hardware failure has
probably occurred. Contact your HP support
representative. You can obtain additional information by
running the card selftest (through the SIC subcommand of
the TermDSM RESET command), the DTC selftest, and the
DTC offline diagnostics.
Chapter 5
Error Messages V iii C 4
TermDSM
271
272
273
274
275
Chapter 5
MESSAGE
That SIC is malfunctioning, or not installed.
TermDSM can not always tell the difference
between !!not installed!! and a serious
malfunction. (TDSM 271)
CAUSE
Possible hardware problem or no card is installed in that
slot.
ACTION
Doublecheck that the SIC number you specified is correct.
If it is, it is likely that the SIC is defective. Contact you HP
support representative. You can obtain additional
information by running the card selftest (through the SIC
subcommand of the TermDSM RESET command), the DTC
selftest, and the DTC offline diagnostics.
MESSAGE
The operation was aborted because it was
reset. (TDSM 272)
CAUSE
Another TermDSM user reset the operation while in
progress.
ACTION
See message 246 for a discussion of multiple TermDSM
operations directed against the same DTC.
MESSAGE
The modem on that port disconnected. (TDSM
273)
CAUSE
The modem on that port was disconnected during the
operation.
ACTION
Reconnect the modem and enter the command again. If
there was no modem, then this is an internal problem.
Contact you HP support representative. You can obtain
additional information by running the card selftest
(through the SIC subcommand of the TermDSM RESET
command), the DTC selftest, and the DTC offline
diagnostics.
MESSAGE
The DTC reported that an unexpected event
occurred. (TDSM 274)
CAUSE
A user on that terminal might have entered CTRL Y or
pressed Break.
ACTION
Try the operation again without touching the keys on the
terminal under test. If the is no change, an internal error
or hardware failure is indicated. Contact your HP support
representative. You can obtain additional information by
running the card selftest (through the SIC subcommand of
the TermDSM RESET command), the DTC selftest, and the
DTC offline diagnostics.
MESSAGE
The loopback is too long. (TDSM 275)
CAUSE
Internal error.
217
Error Messages V iii C 4
TermDSM
280
281
282
283
290
300
218
ACTION
Contact your HP support representative.
MESSAGE
Dump failed. Open of DTCM failed, or DTC
owned and not overridden (TDSM 280)
CAUSE
This message is written to dump files, and never appears
as an error message to a user terminal. If the user was
informed the DTC was in use by another TermDSM (see
message 35), and the second user chose NOT to override,
then this message is normal and is not cause for alarm.
Otherwise, it is indicative of an internal error.
ACTION
If the problem persists, take another dump. If you are sure
another user was not involved, contact your HP support
representative.
MESSAGE
Dump failed: Send or Receive of dump request
failed. (TDSM 281)
CAUSE
An internal error. This message is written to dump files
and never appears as an error message to a user.
ACTION
Contact your HP support representative.
MESSAGE
Dump failed: Bad function in internal error
reply to dump request.(TDSM 282)
CAUSE
An internal error. This message is written to dump files
and never appears as an error message to a user.
ACTION
Contact your HP support representative.
MESSAGE
Dump failed. Bad reply (llio) status from
DTCM. (TDSM 283)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Sorry, TermDSM does not provide services for
the console. (TDSM 290)
CAUSE
The user entered the ldev number of the physical console
for a reset or dump. TermDSM cannot act upon the
physical console port because it is not on the DTC.
TermDSM can only operate on ldev numbers and ports
that are on the DTC. Note: The discussion here is for the
physical console, not a terminal which has taken control of
the logical console via the CONSOLE command.
ACTION
Contact your HP support representative.
MESSAGE
IPC message received in wrong subque. (TDSM
300)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
Chapter 5
Error Messages V iii C 4
TermDSM
301
302
303
304
305
306
307
308
309
Chapter 5
MESSAGE
DTCM port data area not initialized. (TDSM
301)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Bad machine type found in RMP packet. (TDSM
302)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Non supported download file type found in RMP
packet. (TDSM 303)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Bad source IEEE 802.3 address found in RMP
packet. (TDSM 304)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Bad session ID found in RMP packet. (TDSM
305)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Bad path id received from NDM. (TDSM 306)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Boot (download) complete message received
before expected. (TDSM 307)
CAUSE
It has finished the download of its operating firmware
before the DTCM expected it.
ACTION
Look on the console for a boot complete message.
Otherwise, enter the command again. If the problem
persists, contact your HP support representative.
MESSAGE
IO-get-frame failed. (TDSM 308)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Unimplemented action called. (TDSM 309)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
219
Error Messages V iii C 4
TermDSM
310
311
312
313
314
315
316
220
MESSAGE
Bad download file type. (TDSM 310)
CAUSE
Possible corrupt download file.
ACTION
Contact your HP support representative.
MESSAGE
Bad reply from memory manager for Aux data
area. (TDSM 311)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
DCC sent bad reply in response to config.
data request. (TDSM 312)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
DTC did not request the configuration to be
download. (TDSM 313)
CAUSE
After a download, the DTC did not request its
configuration.
ACTION
Look at the console for a message saying configuration
complete. Otherwise, enter the command again. If the
problem persists, contact your HP support representative.
MESSAGE
DCC did not reply to configuration data
request. (TDSM 314)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
Unexpected RMP packet received. (TDSM 315)
CAUSE
Internal error.
ACTION
Contact your HP support representative.
MESSAGE
DTC unexpectedly requested configuration
information to be downloaded. (TDSM 316)
CAUSE
Internal error. The DTC requested its configuration
information at a time the DTCM did not expect it.
ACTION
Monitor the console for messages saying the configuration
is complete. Otherwise, enter the command again. If the
problem persists, contact your HP support representative.
Chapter 5
Error Messages V iii C 4
Terminal I/O Manager for Logging
Terminal I/O Manager for Logging
(Subsystem 128)
1
MESSAGE
An interface warning occurred.
2
MESSAGE
An interface nonfatal error occurred.
3
MESSAGE
An interface fatal error occurred.
4
MESSAGE
A system call warning occurred.
5
MESSAGE
A system call nonfatal error occurred.
6
MESSAGE
A system call fatal error occurred.
7
MESSAGE
An internal warning occurred.
8
MESSAGE
An internal nonfatal error occurred.
9
MESSAGE
An internal fatal error occurred.
10
MESSAGE
An internal event occurred.
11
MESSAGE
A protocol error occurred.
12
MESSAGE
A hardware warning occurred.
13
MESSAGE
A hardware nonfatal error occurred.
14
MESSAGE
A hardware fatal error occurred.
15
MESSAGE
A backplane fatal error occurred.
16
MESSAGE
A reset message was received.
17
MESSAGE
A DTC log warning occurred.
18
MESSAGE
A DTC log nonfatal error occurred.
19
MESSAGE
A DTC log fatal error occurred.
101
MESSAGE
! code download started for DTC address !
102
MESSAGE
! code download completed for DTC address !
103
MESSAGE
! code download aborted for DTC address !
107
MESSAGE
! upload started for DTC address !
108
MESSAGE
! upload completed for DTC address !
109
MESSAGE
! upload aborted for DTC address !
111
MESSAGE
DTCMxxxxxxxx SNP card upload started for DTC
address yyyyyyyyyyyy card z. (DTCMINFO111)
CAUSE
This informational message indicates that an operation of
the SNP card upload starts. For example : The card upload
starts on an SNP card in slot 3 of DTC IEEE802.3 address
at 0800090035A4, the console message will be :
Chapter 5
221
Error Messages V iii C 4
Terminal I/O Manager for Logging
DTCMxxxxxxxx SNP card upload started for DTC address
0800090035A4 card 3.
112
113
114
115
222
ACTION
Wait for the SNP card upload to complete. The SNP card
upload completion message will be shown on the console.
MESSAGE
DTCMxxxxxxxx SNP card upload completed for
DTC address yyyyyyyyyyyy card z.
(DTCMINFO112)
CAUSE
This informational message indicates that an operation of
the SNP card upload completes. For example : The card
upload completes on an SNP card in slot 3 of DTC
IEEE802.3 address at 0800090035A4, the console message
will be : DTCMxxxxxxxx SNP card upload completed for
DTC address 0800090035A4 card 3.
ACTION
Deliver the SNP dump file to your HP support
representative. The SNP dump file name is
Sbxxxxxa.PUB.SYS. Where b is the card number in that
DTC, xxxxx is the last 5 characters of the IEEE802.3
address of that DTC and a is a charater in the sequense
a,b,..z to allow multiple dumps.
MESSAGE
DTCMxxxxxxxx SNP card upload aborted for DTC
address yyyyyyyyyyyy card z (DTCMERR113)
CAUSE
This error message indicates that an operation of the SNP
card upload was aborted by the DTC. A problem occured
with the DTC while the SNP card upload were being
performed. For example : The card upload was aborted on
an SNP card in slot 3 of DTC IEEE802.3 address at
0800090035A4, the console message will be :
DTCMxxxxxxxx SNP card upload aborted for DTC address
0800090035A4 card 3.
ACTION
Contact your HP support representative. You can obtain
the additional information by running the card selftest
through the Termdsm.
MESSAGE
DTCMxxxxxxxx SNP card tracing aborted for DTC
address yyyyyyyyyyyy card z (DTCMERR114)
CAUSE
This error message indicates that an operation of the SNP
card tracing was aborted. This may be caused by a DTC
reset/upload or SNP card reset/upload. For example : The
card tracing was aborted on an SNP card in slot 1 of DTC
IEEE802.3 address at 080009003544, the console message
will be : DTCMxxxxxxxx SNP card tracing aborted for
DTC address 080009003544 card 1
ACTION
Contact with the HP support representative.
MESSAGE
DTCMxxxxxxxx MUX card upload started for DTC
address yyyyyyyyyyyy card z (DTCMINFO115)
Chapter 5
Error Messages V iii C 4
Terminal I/O Manager for Logging
116
117
118
Chapter 5
CAUSE
This informational message indicates that an operation of
the MUX 68k card upload starts. For example : The card
upload starts on a MUX 68k card in slot 2 of DTC
IEEE802.3 address at 08000900357D, the console message
will be : DTCMxxxxxxxx MUX card upload started for
DTC address 08000900357D card 2.
ACTION
Wait for the MUX 68k card upload to complete. The MUX
card upload completion message will be shown on the
console.
MESSAGE
DTCMxxxxxxxx MUX card upload completed for
DTC address yyyyyyyyyyyy card z (DTCMINFO116)
CAUSE
This informational message indicates that an operation of
the MUX 68k card upload completes. For example : The
card upload completes on a MUX 68k card in slot 2 of DTC
IEEE802.3 address at 08000900357D, the console message
will be : DTCMxxxxxxxx MUX card upload completed for
DTC address 08000900357D card 2
ACTION
Deliver the MUX 68k dump file to your HP support
representative. The dump file name is
Mbxxxxxa.PUB.SYS. Where b is the card number in that
DTC, xxxxx is the last 5 characters of the IEEE802.3
address of that DTC and a is a charater in the sequense
a,b,..z to allow multiple dumps.
MESSAGE
DTCMxxxxxxxx MUX card upload aborted for DTC
address yyyyyyyyyyyy card z (DTCMERR117)
CAUSE
This error message indicates that an operation of the
MUX 68k card upload is aborted by the DTC. A problem
occurred with DTC while the MUX card upload were being
performed. For example : The card upload is aborted on a
MUX 68k card in slot 2 of DTC IEEE802.3 address at
08000900357D, the console message will be :
DTCMxxxxxxxx MUX card upload aborted for DTC
address 08000900357D card 2
ACTION
Contact your HP support representative. You can obtain
the additional information by running the card selftest
through the Termdsm.
MESSAGE
Now you must restart the MUX Card by
resetting DTC address
yyyyyyyyyyyy card z (DTCMWARN118)
CAUSE
This message indicates that the MUX card is not working
any more after the MUX 68k upload is completed.
Consequently, the user must initiate a MUX reset to
reactivate the MUX card.
ACTION
After the MUX card upload is completed, the user must
223
Error Messages V iii C 4
Transaction Management
initiate a MUX card reset by running the host Termdsm to
restart the MUX card.
123
125
126
MESSAGE
DTCMxxxxxxxx rom code download started for
DTC address yyyyyyyyyyyy (DTCMINFO123)
CAUSE
This informational message indicates that a download
operation of the rom code for a DTC starts. For example :
The rom code download starts on a DTC IEEE802.3
address at 080009280E1C, the console message will be :
DTCMxxxxxxxx rom code download started for DTC
address 080009280E1C
ACTION
Wait for the rom code download to complete. The rom code
download completion message will be shown on the
console.
MESSAGE
DTCMxxxxxxxx rom code download aborted for
DTC address yyyyyyyyyyyy (DTCMERR125)
CAUSE
This error message indicates that a download operation of
the rom code was aborted by the DTC. A problem occured
with the DTC while the download of the rom code was
being performed. For example : The download of the rom
code was aborted on the DTC IEEE802.3 address at
080009280E1C, the console message will be :
DTCMxxxxxxxx rom code download aborted for DTC
address 080009280E1C
ACTION
The appropriate message with the corrective action will be
displayed for the error conditions.
MESSAGE
DTCMxxxxxxxx rom code download completed for
DTC address yyyyyyyyyyyy (DTCMERR126)
CAUSE
This informational message indicates that a download
operation of the rom code completes. For example : The
download of the rom code completed on a DTC IEEE802.3
address at 080009280E1C, the console message will be :
DTCMxxxxxxxx rom code download completed for DTC
address 080009280E1C
ACTION
The rom code is downloaded to the DTC without any
problems, no actions need to be taken.
Transaction Management
(Subsystem 151)
101
224
MESSAGE
An escape occurred when using MOVE_FAST.
Chapter 5
Error Messages V iii C 4
Transaction Management
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
Chapter 5
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; bad control block
has been passed to an internal routine.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; key is not in the
HASH TABLE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; FILE LABEL was
not found.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; FILE MAPPING
failed.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The file is not in the directory.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; invalid RID.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The procedure caused a HARD CRASH.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The procedure returned an invalid CURRENT
TRANSACTION ID.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
System DEADLOCK occurred.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Transaction ID has an ACTIVE SUBTRANSACTION.
225
Error Messages V iii C 4
Transaction Management
1011
1013
1014
1015
1016
1017
1018
1019
1020
1021
226
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The log is FULL.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing XID.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
RECORD not found in the HASH TABLE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The HASH TABLE is FULL.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The record exists in the HASH TABLE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; Log needs to be
OPEN.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Failure to MAP the log occurred.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; failure to add
the LOGSET ID in the system log directory.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
No active transaction identifier.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The file already exists in the system log
directory.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
Chapter 5
Error Messages V iii C 4
Transaction Management
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
Chapter 5
MESSAGE
The HASH TABLE size is too big.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Data goes beyond the end of the file.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Too many LOGSETS were defined.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The file is already attached.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Too many files were attached.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The log has active transaction on files
attached to the log.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; the file does not
have XM PROPERTY.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The stack of errors has errors.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The LOG and the MIRRORLOG are defined in the
same volume.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
System failure was requested from
TRANSACTIONMODULE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The file cannot be attached to any file; the
227
Error Messages V iii C 4
Transaction Management
Log must be defined.
1033
1034
1035
1036
1037
1038
1039
1040
1041
228
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
This is an invalid LOCK request.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The LOCK control data structure cannot be
found.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The LOCK control data structure cannot be
found.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
An internal error occurred; invalid LOCK
PROMOTION.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
System failure occurred; the LOG LABEL is
corrupted.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
LOGSET has active transaction ID's.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The file is not attached.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The file is not a user log; the LOG needs to
be defined.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
LOG already exists.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
Chapter 5
Error Messages V iii C 4
Transaction Management
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
Chapter 5
MESSAGE
There are an invalid number of Transaction
IDs.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
LOCK RANGE is out of bounds.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The buffer contains no STRING.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing MIRROR LOG file name.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing MIRROR LOG file name.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing LOG VOLUME name.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing MIRROR FILE NAME length.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing LOG VOLUME NAME length.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Missing USER FILE name.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid XID.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOCK option.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
229
Error Messages V iii C 4
Transaction Management
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
230
MESSAGE
Invalid OFFSET.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid HASH TABLE size.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid KEY length.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid offset or length. Offset + length
goes beyond EOF.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid NUMBER OF FIELDS for the HASH TABLE
record.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid procedure name.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOG NAME.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid MIRROR LOG NAME.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid access to transaction ID.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid ACCESS to user STATUS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOG VOLUME NAME ACCESS.
CAUSE
Internal error.
Chapter 5
Error Messages V iii C 4
Transaction Management
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
Chapter 5
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid MIRROR VOLUME NAME ACCESS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOG FILE NAME ACCESS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid MIRROR FILE NAME ACCESS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid FILE NAME ACCESS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid VIRTUAL ADDRESS RANGE ACCESS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOCK OPTION ACCESS.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOG NAME LENGTH.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid MIRROR LOG NAME LENGTH.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOG VOLUME NAME LENGTH.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid FILE NAME LENGTH.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
The PIN is not in the HASH TABLE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
231
Error Messages V iii C 4
Traps
1075
1076
1077
1078
1079
2200
MESSAGE
The transaction ID is not in the HASH TABLE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid TRANSACTION TYPE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
It is not MIRROR LOG OF THE LOG.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid buffer length.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
Invalid LOG SIZE.
CAUSE
Internal error.
ACTION
Call your Hewlett-Packard Representative.
MESSAGE
A transaction lasted for longer than two XM
log checkpoints.
CAUSE
Transaction had either a blocked semaphore or a disc fill
took too long.
ACTION
Call your Hewlett-Packard Representative.
Traps
(Subsystem 200)
1
7
8
232
MESSAGE
**** Check true/false trap (TRAPS 1).
CAUSE
Size error on exponentiationin COBOL/XL program.
ACTION
Add size error clause.
MESSAGE
**** 3000 mode packed decimal error. (TRAPS
7).
CAUSE
Error detected by 3000 mode packed decimal procedure.
ACTION
Correct the input to these routines.
MESSAGE
**** Paragraph stack overflow (TRAPS 8).
CAUSE
Recursive performance or invalid exiting of a paragraph.
Chapter 5
Error Messages V iii C 4
Traps
9
10
11
12
13
14
15
16
17
18
Chapter 5
ACTION
Correct the procedure.
MESSAGE
**** Unimplemented condition trap (TRAPS 9).
CAUSE
Unknown trapping execution instruction executed.
ACTION
Change the instruction.
MESSAGE
**** Misaligned or long-to-short pointer
conversion error (TRAPS 10).
CAUSE
Software detected misaligned pointer or pointer
conversion error.
ACTION
Correct the procedure.
MESSAGE
**** Nil pointer (TRAPS 11).
CAUSE
Software detected nil pointer reference.
ACTION
Correct the procedure.
MESSAGE
**** Bound violation or range error (TRAPS
12).
CAUSE
Value not within specified bounds.
ACTION
Correct the procedure.
MESSAGE
**** IEEE invalid operation (TRAPS 13).
CAUSE
Attempted operation is not legal in IEEE format.
ACTION
Correct the procedure.
MESSAGE
**** IEEE divide by zero (TRAPS 14).
CAUSE
Attempted to divide by zero in IEEE format.
ACTION
Correct the procedure, or disable IEEE overflow trap.
MESSAGE
**** IEEE overflow (TRAPS 15).
CAUSE
Attempted operation resulted in an overflow in IEEE
format.
ACTION
Correct the procedure, or disable IEEE overflow trap.
MESSAGE
**** IEEE underflow (TRAPS 16).
CAUSE
Attempted operation resulted in an underflow in IEEE
format.
ACTION
Change the procedure or disable IEEE underflow trap.
MESSAGE
**** IEEE inexact result (TRAPS 17).
CAUSE
Attempted operation resulted in an inexact result in IEEE
format.
ACTION
Correct the procedure or disable inexact result trap.
MESSAGE
**** Decimal divide by zero (TRAPS 18).
CAUSE
Attempted to divide by zero in decimal format.
233
Error Messages V iii C 4
Traps
21
22
23
24
25
26
27
28
29
234
ACTION
Correct the procedure.
MESSAGE
**** Invalid decimal digit (TRAPS 21).
CAUSE
A non-sign, numeric digit was detected in decimal format.
ACTION
Correct the number.
MESSAGE
**** Invalid ASCII digit (TRAPS 22).
CAUSE
A non-sign, numeric digit was detected in decimal format.
ACTION
Correct the number.
MESSAGE
**** Decimal overflow (TRAPS 23).
CAUSE
Attempted operation resulted in an overflow in decimal
format.
ACTION
Correct the procedure.
MESSAGE
**** 3000 mode double floating point divide
by zero (TRAPS 24).
CAUSE
Attempted to divide by zero in 3000 double floating point
format.
ACTION
Correct the procedure.
MESSAGE
**** 3000 mode double floating point
underflow (TRAPS 25).
CAUSE
Attempted operation resulted in an underflow in 3000
double floating point format.
ACTION
Correct the procedure.
MESSAGE
**** 3000 mode double floating point overflow
(TRAPS 26).
CAUSE
Attempted operation resulted in an overflow in 3000
double floating point format.
ACTION
Correct the procedure.
MESSAGE
**** Integer overflow (TRAPS 27).
CAUSE
Attemtped operation resulted in an overflow in integer
format.
ACTION
Correct the procedure.
MESSAGE
**** 3000 mode floating point overflow (TRAPS
28).
CAUSE
Attemtped operation resulted in an overflow in 3000
floating point format.
ACTION
Correct the procedure.
MESSAGE
**** 3000 mode floating point underflow
(TRAPS 29).
Chapter 5
Error Messages V iii C 4
Traps
30
31
50
51
56
57
58
59
60
Chapter 5
CAUSE
Attempted operation resulted in an underflow in 3000
floating point format.
ACTION
Correct the procedure.
MESSAGE
**** Integer divide by zero (TRAPS 30).
CAUSE
Attempt to divide by zero in integer format.
ACTION
Correct the procedure.
MESSAGE
**** 3000 mode floating point divide by zero
(TRAPS 31).
CAUSE
Attempt to divide by zero in 3000 floating point format.
ACTION
Correct the procedure.
MESSAGE
**** Escape executed without enclosing Try
(TRAPS 50).
CAUSE
Program attempted an escape without an executed TRY
statement in Pascal/XL.
ACTION
Change the program.
MESSAGE
**** Check true/false trap (TRAPS 51).
CAUSE
An assertion failed.
ACTION
Change the procedure.
MESSAGE
**** Illegal instruction address (TRAPS 56).
CAUSE
Branch to an illegal virtual code address.
ACTION
Change the procedure.
MESSAGE
**** Instruction memory protection (TRAPS
57).
CAUSE
Invalid access rights or invalid protection ID and the
PSW-Pbit is set for an instruction fetch.
ACTION
Change the procedure.
MESSAGE
**** Illegal instruction trap (TRAPS 58).
CAUSE
An attempt is being made to execute an illegal instruction
or to execute a GATEWAY instruction with the PSW B-bit
(token branch) set.
ACTION
Change the procedure.
MESSAGE
**** Break instruction trap (TRAPS 59).
CAUSE
A break instruction was executed.
ACTION
Change the procedure.
MESSAGE
**** Privileged operation trap (TRAPS 60).
CAUSE
An attempt is being made to execute a privileged
235
Error Messages V iii C 4
Traps
instruction without being at the most privileged level
(PL=10).
61
65
68
69
236
ACTION
Change the procedure.
MESSAGE
**** Privileged register trap (TRAPS 61).
CAUSE
An attempt is being made to write to a privileged space
register or access a privilged control register without being
at the most privilege level (PL=0).
ACTION
Change the procedure.
MESSAGE
**** Illegal data address (TRAPS 65).
CAUSE
Read or Write to an illegal virtual data address.
ACTION
Change the procedure.
MESSAGE
**** Data memory protection trap (TRAPS 68).
CAUSE
An access rights check or a protection ID check that fails;
any load or store instruction with virtual address
translation to unaligned data.
ACTION
Change the procedure.
MESSAGE
**** Unknown trap (TRAPS 69).
CAUSE
Internal error - unknown trap number for message.
ACTION
Notify your Service Representative.
Chapter 5
6 TurboIMAGE/XL V iii C 5
TurboIMAGE/XL issues three different types of error messages:
• Schema Processor Error Messages
• Library Procedure Error Messages
• Utility Error Messages
Schema processor error messages result from errors detected during processing of the
database schema. The library procedure error messages are returned to the calling
program from the library procedures. The utility error messages are caused by errors in
execution of the database utility programs.
Schema Processor Error Messages
The Schema Processor accesses three files:
• The text file (DBSTEXT) containing the schema records and Schema Processor
commands for processing.
• The list file (DBSLIST) containing the schema listing, if requested, and error messages,
if any.
• The root file, if requested, created as a result of an error-free schema.
Any file error which occurs while accessing any of these files causes the Schema Processor
to terminate execution. A message indicating the nature of the error is sent to $STDLIST
(and to the list file, if the list file is different from $STDLIST).
Schema Processor command errors may occur. They neither cause termination nor do they
prohibit the creation of a root file. In some cases, however, the resultant root file will differ
from what might have occurred had the commands been error free. Command errors are
added to an error count which, if it exceeds a limit, will cause the Schema Processor to
terminate execution.
Note that if the LIST option is active, error messages for command errors and syntax
errors appear in the list file following the offending statement. If the NOLIST option is
active, only the offending statement, followed by the error message, is listed.
Schema Processor File Errors
Various file error messages are listed in this section. Each such message is preceded by the
237
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
character string:
****** FILE ERROR ******
Additionally, the Schema Processor prints a standard MPE/iX file information display on
the $STDLIST file.
MESSAGE READ ERROR ON file name
CAUSE
FREAD error occurred on the specified file.
ACTION
Check text file or :FILE command.
MESSAGE FILE ALREADY EXISTS; UNABLE TO CLOSE file name
CAUSE
FCLOSE error occurred on specified file. May be caused by duplicate file in
group with same name as root file.
ACTION
Change database name or purge file of same name. Or, be sure correct file
and file name used. Check :FILE commands used. If other cause, consult
MPE/iX Intrinsics Manual (32650-90028) for similar message.
MESSAGE UNABLE TO USE file name
CAUSE
Specified file cannot be FOPENed or its characteristics make it unsuitable
for its intended use.
ACTION
Change database name or purge file of same name. Or, be sure correct file
and file name used. Check :FILE commands used. If other cause, consult
MPE/iX Intrinsics Manual (32650-90028) for similar message.
MESSAGE UNABLE TO WRITE LABEL OF file name
CAUSE
FWRITELABEL error occurred on specified file.
ACTION
Change database name or purge file of same name. Or, be sure correct file
and file name used. Check :FILE commands used. If other cause, consult
MPE/iX Intrinsics Manual (32650-90028) for similar message.
MESSAGE UNEXPECTED END-OF-FILE ON file name
CAUSE
Call to FREAD or FWRITE on specified file has yielded unexpected end of
file condition.
ACTION
Change database name or purge file of same name. Or, be sure correct file
and file name used. Check :FILE commands used. If other cause, consult
MPE/iX Intrinsics Manual (32650-90028) for similar message.
MESSAGE WRITE ERROR ON file name
CAUSE
FWRITE error occurred on the specified file.
ACTION
Change database name or purge file of same name. Or, be sure correct file
and file name used. Check :FILE commands used. If other cause, consult
MPE/iX Intrinsics Manual (32650-90028) for similar message.
Schema Processor Command Errors
Various Schema Processor command error messages are listed in this section. Each such
message is preceded by the character string:
238
Chapter 6
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
***** ERROR ******
MESSAGE
COMMAND CONTINUATION NOT FOUND
CAUSE
If the schema processor command is continued to the next record, the last
non-blank character of the preceding line must be an ampersand (&) and
the continuation record must start with a dollar sign ($).
ACTION
Examine the schema text file to find any incorrect commands. Edit the text
file and run the Schema Processor again.
MESSAGE
COUNT HAS BAD FORMAT
CAUSE
The numbers in ERRORS, LINES, or BLOCKMAX parameters of the
$CONTROL command are not properly formatted integer values.
ACTION
Examine the schema text file to find any incorrect commands. Edit the text
file and run the Schema Processor again.
MESSAGE
ILLEGAL COMMAND
CAUSE
The Schema Processor does not recognize the command. Valid commands
are $PAGE, $TITLE, and $CONTROL.
ACTION
Examine the schema text file to find any incorrect commands. Edit the text
file and run the Schema Processor again.
MESSAGE
IMPROPER COMMAND PARAMETER
CAUSE
One of the commands in the parameter is not valid.
ACTION
Examine the schema text file to find any incorrect commands. Edit the text
file and run the Schema Processor again.
MESSAGE
MISSING QUOTATION MARK
CAUSE
Character string specified in $PAGE or $TITLE command must be
bracketed by quotation marks (").
ACTION
Examine the schema text file to find any incorrect commands. Edit the text
file and run the Schema Processor again.
MESSAGE
SPECIFIED TITLE IS TOO LONG
CAUSE
Character string in $TITLE or $PAGE command exceeds 104 characters.
ACTION
Examine the schema text file to find any incorrect commands. Edit the text
file and run the Schema Processor again.
Schema Syntax Errors
Database definition syntax errors may be detected by the Schema Processor. Their
existence does not cause termination but does prohibit root file creation. Discovery of one
may trigger others which disappear after the first is corrected. Also, detection of one may
preclude detection of others which appear after the first is corrected. Syntax errors are also
added to an error count which, if excessive, will cause Schema Processor termination.
Various syntax error messages are listed in this section. As with command errors, each
syntax error is preceded by the character string:
Chapter 6
239
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
***** ERROR ******
MESSAGE
AUTOMATIC MASTER DATA SET MUST HAVE SEARCH ITEM ONLY
CAUSE
Automatic master data sets must contain entries with only one data item.
The data item must be a key item.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD CAPACITY OR TERMINATOR
CAUSE
Either the number in the CAPACITY: statement is not an integer between
1 and 2 −1, or a semicolon is missing.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD CHARACTER IN USER CLASS NUMBER
CAUSE
User class number in password is not an integer from 1 to 63.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD DATA BASE NAME OR TERMINATOR
CAUSE
Database name in BEGIN DATA BASE statement is not a valid database
name beginning with an alphabetic character and having up to 6
alphanumeric characters. Or, the name is not followed by a semicolon (;).
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD DATA SET TYPE
CAUSE
The data set type designator is not AUTOMATIC (or A), MANUAL (or M),
or DETAIL (or D).
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD DEVICE CLASS NAME
CAUSE
The device class name specified contains an invalid character. The name
must be less than eight characters and begin with a letter.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD DEVICE CLASS NAME OR TERMINATOR
CAUSE
The device class name specified contains an invalid character or was not
ended with a semicolon ";".
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD LANGUAGE
CAUSE
Language name contains invalid characters, or the language number is
240
Chapter 6
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
not a valid integer.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD PATH CONTROL PART DELIMITER
CAUSE
Data item defined as sort item in detail data set is not properly delimited
with parentheses ().
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD PATH COUNT OR TERMINATOR
CAUSE
The path count in the master data set definition is not an integer from 1 to
16 (for an automatic master), or 0 to 16 (for a manual master). This
message may also mean the path count is not followed by a quotation mark
(").
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD PATH SPECIFICATION DELIMITER
CAUSE
Name of master data set following search item name in detail data set
definition is not followed by a right parenthesis ")", or by a sort item name
in parentheses.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD READ CLASS OR TERMINATOR
CAUSE
Read user class number defined for either a data set or data item is not an
integer from 0 to 63, or it is not terminated by a comma (,) or slash (/).
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD SET NAME OR TERMINATOR
CAUSE
The data set name does not conform to naming rules. (Names must start
with a letter and may have up to 16 alphanumeric characters including + −
* / ? ' # % & @.) Or the data set name is not terminated by the correct
character for the context in which it appears.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD SUBITEM COUNT OR TERMINATOR
CAUSE
Subitem count for a data item defined in schema item part is not an
integer from 1 to 255.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD SUBITEM LENGTH OR TERMINATOR
Chapter 6
241
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
CAUSE
Subitem length for data item defined in schema item is not an integer from
1 to 255.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD TERMINATOR-';' EXPECTED
CAUSE
Password or capacity was not followed by a semicolon.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD TERMINATOR- ';' OR ',' EXPECTED
CAUSE
Items within an entry definition must be separated from each other with
commas and terminated with a semicolon.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD TYPE DESIGNATOR
CAUSE
Data item defined in schema item part is not defined as type I, J, K, R, U,
X, Z, or P.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
BAD WRITE CLASS OR TERMINATOR
CAUSE
Write user class number shown for the data set or data item is not an
integer from 0 to 63, or it is not terminated by a right parenthesis ")" or
comma.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
'CAPACITY:' EXPECTED
CAUSE
CAPACITY statement must follow entry definition in the definition of data
sets in the set part of schema.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
DATA BASE HAS NO DATA SETS
CAUSE
No data sets were defined in the set part of schema. The database must
contain at least one data set.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
DATA BASE NAME TOO LONG
CAUSE
Database name has more than six characters.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
242
Chapter 6
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
MESSAGE
DUPLICATE ITEM SPECIFIED
CAUSE
The same data item name was used more than once in the entry definition
of data sets.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
DUPLICATE SET NAME
CAUSE
The same data set name was used to define more than one data set in the
set part of schema.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
'ENTRY:' EXPECTED
CAUSE
Each set defined in the set part of schema must contain ENTRY:
statement followed by the data item names of the data items in entry.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
ENTRY TOO BIG
CAUSE
The number and size of the data items defined for an entry makes an entry
too big for maximum block size. The block size is specified by $CONTROL,
or BLOCKMAX= command, or default.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
ENTRY TOO SMALL
CAUSE
A detail data set that is not linked to any master data set must have a
data entry length of two or more halfwords. This length is determined by
adding the size in halfwords of each data item defined in the data entry.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
ILLEGAL ITEM NAME OR TERMINATOR
CAUSE
The data item name does not conform to naming rules. (Names must start
with a letter and may have up to 16 alphanumeric characters including + −
? / # ∃ & * @ ). Or if in the item part, it is not followed by a comma.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
ILLEGAL USER CLASS NUMBER
CAUSE
User class number defined in schema password part is not an integer
between 1 and 63.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
ITEM TOO LONG
Chapter 6
243
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
CAUSE
The length of a single data item may not exceed 2047 halfwords.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
'LANGUAGE:' EXPECTED
CAUSE
The Schema Processor expected to find a LANGUAGE statement after the
comma following the BEGIN DATA BASE name statement.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
LANGUAGE NOT SUPPORTED
CAUSE
Language specified is not supported on your system, or is not a valid
language.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
MASTER DATA SET LACKS EXPECTED DETAIL(S)
CAUSE
Master data set was defined with a non-zero data count, but the number of
detail search items which back-referenced the master is less than the
value of the path count.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
MASTER DATA SET LACKS KEY ITEM
CAUSE
A master data set was defined without defining one of the data items in
the set as a key item.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
MORE THAN ONE KEY ITEM
CAUSE
A master data set cannot be defined with more than one key item.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
MORE THAN ONE PRIMARY MASTER
CAUSE
User has defined more than one primary path for a detail data set.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
'NAME:' OR 'END.' EXPECTED
CAUSE
Schema Processor expected, at this point, to find the beginning of another
data set definition, or the end of schema.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
NATIVE LANGUAGE SUPPORT ERROR
244
Chapter 6
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
CAUSE
NLS/3000 returned an error.
ACTION
Notify the system manager
MESSAGE
'PASSWORDS:' NOT FOUND
CAUSE
'PASSWORDS:' statement must immediately follow the BEGIN DATA
BASE statement in schema. If it does not, DBSCHEMA terminates
execution.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
PASSWORD TOO LONG
CAUSE
A password defined in data schema cannot exceed eight characters.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
REFERENCED SET NOT MASTER
CAUSE
The data set referenced by the detail data set search item is another detail
data set instead of a master data set.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
SCHEMA PROCESSOR LACKS NEEDED TABLE SPACE
CAUSE
Schema Processor is unable to expand its data stack to accommodate all of
the translated information which will make up the root file. It continues to
scan the schema for the proper form, but will not perform all of the checks
for correctness nor will it create a root file. To process the schema correctly,
the operating system must be configured with a larger maximum stack
size.
ACTION
Ask system manager to increase maximum stack size.
MESSAGE
SEARCH OR KEY ITEM NOT SIMPLE
CAUSE
All data items defined in data schema as key or search items must be
simple items.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
SEARCH AND KEY ITEMS NOT OF SAME LENGTH
CAUSE
Master key item must be the same length as any related detail data set
search item.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
SEARCH AND KEY ITEMS NOT OF SAME TYPE
CAUSE
Master key item must be of the same type as any related detail data set
search item.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Chapter 6
245
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
Schema Processor again.
MESSAGE
SET HAS NO PATHS AVAILABLE
CAUSE
More detail data set search items have specified a relationship with a
master data set than the number specified in the master set's path count.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
SORT ITEM OF BAD TYPE
CAUSE
Data item defined as sort item must be of type U, K, or X.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
SORT ITEM NOT IN DATA SET
CAUSE
Detail data set's entry definition does not include an item which is
specified as a sort item for another item in the entry.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
SORT ITEM SAME AS SEARCH ITEM
CAUSE
The same item cannot be both a search and a sort item for the same path.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
TOO MANY DATA ITEMS
CAUSE
The item part of schema cannot have more than 1023 data item names
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
TOO MANY DATA SETS
CAUSE
The database cannot have more than 199 data sets.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
TOO MANY ERRORS
CAUSE
The specified or default number of errors has been exceeded. Processing is
terminated.
ACTION
Correct the errors, or increase the ERROR parameter value.
MESSAGE
TOO MANY ITEMS SPECIFIED
CAUSE
The data set entry cannot have more than 255 data items.
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
TOO MANY PATHS IN DATA SET
CAUSE
Detail data set entries cannot have more than 16 search items.
246
Chapter 6
TurboIMAGE/XL V iii C 5
Schema Processor Error Messages
ACTION
Examine the schema text file to find the error and edit the file. Run the
Schema Processor again.
MESSAGE
UNDEFINED ITEM REFERENCED
CAUSE
A data item appearing in the data set definition was not previously defined
in the item part of schema.
ACTION
Examine the schema text file and find the incorrect statement. Edit it and
run the Schema Processor again.
MESSAGE
UNDEFINED SET REFERENCED
CAUSE
Master data set referenced by detail search item was not previously
defined in the set part of schema.
ACTION
Examine the schema text file and find the incorrect statement. Edit it and
run the Schema Processor again.
Chapter 6
247
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
Library Procedure Error Messages
The success of each call to a TurboIMAGE/XL library procedure is reflected upon return to
the user by the condition code and the value of the return status in the first element of the
status area.
If the procedure fails to execute properly, the condition code is set to CCL (Condition Code
Less) and the return status is a negative integer. In this section, "Library Procedure File
System and Memory Management" describes the negative integers resulting from file
system and memory management failures, while "Library Procedure Calling Errors"
describes the negative integers resulting from calling errors and communications errors
respectively.
If the procedure operates properly but encounters an exceptional condition, such as
end-of-file, the condition code is set to CCG (Condition Code Greater) and the return status
is a positive integer. "Library Procedure Exceptional Conditions" describes the positive
integers resulting from exceptional conditions. If the procedure operates properly and
normally, the condition code is set to CCE (Condition Code Equal) and the return status is
zero.
In addition to the return status, all TurboIMAGE/XL library procedures put information
about the procedure call into the fifth through tenth elements of the status area. This
information may be useful in debugging your programs, because it describes the conditions
under which the particular results were obtained. This information is used by
DBEXPLAIN and DBERROR when they are interpreting the results of TurboIMAGE/XL
calls.
In a few cases this information is not returned by the TurboIMAGE/XL procedure because
it uses the same locations in the status area for returning other data. Specifically,
successful execution of DBFIND, DBGET, DBUPDATE, DBPUT, or DBDELETE puts
other information here as described in Chapter 5 of this manual. For all other returns from
a library procedure, the specified elements of the status area have the following contents:
Table 6-1. Status Area Changes for Native Applications
ELEMENT
248
TurboIMAGE/V and Compatibility Mode
TurboIMAGE/XL
5
PB-relative address of the caller.
0
6
Bits 6–15: Intrinsic number of called library
procedure. Bits 0–3: Zero or access mode in which
database is opened.
No change.
7
16-bit address of the database.
First 16 bits of the
database address.
8
16-bit address of the data set name or qualifier.
Second 16 bits of
database address.
9
Value of the mode parameter.
No change.
10
PB-relative address of the library procedure or the
Compatibility Mode switch stub.
0
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
Abort Conditions
In general, four types of error conditions can cause TurboIMAGE/XL to abort the calling
process:
1. A call from a Compatibility Mode user process with the hardware DB register not
pointing to the process stack.
2. A faulty calling sequence.
3. An internal error in an MPE/iX file intrinsic which the calling procedure cannot correct.
4. An internal inconsistency in the database or the DBG, DBB, or DBU discovered by a
library procedure.
In case 1, the procedure prints the standard MPE/iX run-time abort message. In cases 2, 3,
and 4, TurboIMAGE/XL prints additional information on the standard list device about
the error prior to printing the standard MPE/iX abort message. The first line of this
information is:
ABORT: procedure name ON DATABASE name;
where procedure name is the name of the library procedure which caused the abort and
name is the name of the database being accessed at the time of the abort. "Library
Procedure Abort Condition Messages" describes additional lines of information which may
appear prior to the standard MPE/iX abort message.
Some of the abort conditions are due to an error in one of the MPE/iX file intrinsics
FOPEN, FREADLABEL, FREADDIR, FWRITELABEL, FWRITEDIR, or FCLOSE. Aborts
of this type generally occur after the procedure has possibly altered the database so that
the database structure has been damaged in some way. Each of the messages in the section
entitled "Library Procedure Abort Condition Messages," which refer to a TurboIMAGE/XL
data file, are followed by an MPE/iX file information display listing all of the
characteristics of the MPE/iX data set or root file where the error occurred, along with an
MPE/iX error number.
I and J Files
When TurboIMAGE/XL detects an internal inconsistency or other abnormal situation, it
may create special "I" and "J" files before it terminates. The "I" file consists of the user's
stack and procedure call trace markers; the "J" file consists of the TurboIMAGE/XL
database control blocks. TurboIMAGE/XL only creates these "I" and "J" files if a database
user has run DBUTIL and specified ENABLE FOR DUMPING. So, if you want "I" and "J"
files, you must specifically request them through this DBUTIL command. Note that "I" and
"J" files are useful for debugging only if the database is known to be structurally sound.
Library Procedure File System and Memory Management
For return status values -1 through -6, the second element of the calling program's status
area is the data set number for which file error occurred (zero indicates root file). The third
element is MPE/iX failure code returned by FCHECK intrinsic. Refer to MPE/iX
documentation for meaning of this code.
-1
Chapter 6
MESSAGE MPE file error nn returned by FOPEN on root file
249
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
or data set nn
CAUSE
For DBOPEN, error may indicate that database could not
be opened. Possible reasons:
• Database name string not terminated with semicolon
or blank.
• Database does not exist or is secured against access by
its group or account security.
• Database is already opened exclusively or in mode
incompatible with requested mode.
• MPE/iX file system error occurred.
• MPE/iX file system limit has been reached.
For DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE,
DBPUT, and DBDELETE, error may occur if:
• The process has too many files open external to the
database.
• Data set does not exist or is secured against access.
• Some other MPE/iX file system error has occurred.
ACTION
Determine which of probable causes applies and either
modify application program or see system manager about
file system error.
-2
MESSAGE MPE file error nn returned by FCLOSE on root
file or data set nn
CAUSE
This is an exceptional error (should never happen) and is
returned only by DBOPEN or DBCLOSE. Indicates a
hardware or system software failure.
ACTION
Notify system manager of error.
-3
MESSAGE MPE file error nn returned by FREADDIR on root
file or data set nn
CAUSE
This is an exceptional error (as -2 above) and is returned
by DBOPEN, DBFIND, DBGET, DBUPDATE, DBPUT,
DBDELETE.
ACTION
Notify system manager of error.
-4
MESSAGE MPE file error nn returned by FREADLABEL on root
file or data set nn
-5
250
CAUSE
This is an exceptional error (as -2 above) and is returned
by DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE,
DBPUT, DBDELETE.
ACTION
Notify system manager of error.
MESSAGE MPE file error nn returned by FWRITEDIR on root
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
file or data set nn
CAUSE
This exceptional condition could be returned when
DBPUT, DBDELETE, DBUPDATE, or DBCLOSE calls
FWRITEDIR.
ACTION
Notify system manager of error.
-6
MESSAGE MPE file error nn returned by FWRITELABEL on
root file or data set nn
-8
file
-9
CAUSE
This exceptional condition could be returned when
DBPUT, DBDELETE, or DBCLOSE calls
FWRITELABEL.
ACTION
Notify system manager of error.
MESSAGE MPE file error nn returned by FUNLOCK on root
CAUSE
This exceptional condition could be returned when
DBOPENN calls FUNLOCK on a remote database-access
file.
ACTION
Notify system manager of error.
MESSAGE Cannot create control block name: MPE error %nn
CAUSE
This is an exceptional error returned when DBOPEN fails
to call HPFOPEN to create a control block.
ACTION
Notify system manager or HP support personnel.
-10
MESSAGE MPE file error %nn returned by FFILEINFO on root
file or data set nn
CAUSE
This is an exceptional error returned when DBOPEN fails
to call FFILEINFO on the root file.
ACTION
Notify system manager or HP support personnel.
Library Procedure Calling Errors
-11
-12
Chapter 6
MESSAGE Bad base reference
CAUSE
For DBOPEN, the first two characters in base are not
blank, or database name contains special characters other
than period. For all other procedures, either first two
characters in base do not contain the value assigned by
DBOPEN or the parameters passed to the procedure are
incorrect in type, sequence, or quantity.
ACTION
Check application program's procedure call. Correct error
in call.
MESSAGE
intrinsic name called without
covering lock in effect (or see below)
CAUSE
For DBUPDATE, DBPUT, and DBDELETE, database has
251
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
been opened in DBOPEN mode 1 but there is no lock to
cover entry. DBPUT or DBDELETE to master requires
data set or database be locked. In all other cases, entry,
set, or database can be locked.
-12
-13
-14
-15
-21
-21
ACTION
Modify program to apply proper lock or change mode.
MESSAGE
Database must be in logon group and account (or
see above)
CAUSE
For DBOPEN, when the database has been opened in
access mode 2, the database has to be in the user's logon
group and account.
ACTION
Retry call to DBOPEN from group and account containing
database.
MESSAGE
Not allowed; must be creator of root file or
data base
CAUSE
DBOPEN failed because the caller is not the creator of the
database and no maintenance word is specified.
ACTION
Supply the correct maintenance word and retry call to
DBOPEN.
MESSAGE
Illegal intrinsic in current access mode
CAUSE
DBPUT and DBDELETE cannot be used with DBOPEN
mode 2, 5, 6, 7, or 8. DBUPDATE cannot be used with
DBOPEN mode 5, 6, 7, or 8.
ACTION
Modify program or notify current user that operation
cannot be performed.
MESSAGE
Setup for RDBA failed
CAUSE
DBOPEN will issue a DSLINE command and a REMOTE
HELLO on behalf of the user if a DBA file is being used for
RDBA. One of these commands failed.
ACTION
Check your DBA file to make sure the DSLINE and
REMOTE HELLO commands are correct.
MESSAGE
Bad password (or see below)
CAUSE
For DBOPEN, user class granted does not permit access to
any data in database. This is usually due to an incorrect or
null password or maintenance word.
ACTION
Supply correct password and/or maintenance word.
MESSAGE
Bad data set reference (or see below)
CAUSE
For DBINFO (modes 104, 201, 202, 301, and 302),
DBCLOSE, DBFIND, DBGET, DBUPDATE, DBPUT,
DBDELETE, when data set reference is:
• Numeric but out of range of the number of data sets in
252
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
database
• An erroneous data set name
• A reference to data set which is inaccessible to user
class established when database opened
For DBFIND, this error is also returned if referenced data
set is a master. Erroneous data set name may arise when a
terminating semicolon or blank is omitted.
-21
ACTION
Check application program's procedure call. Correct error
in call.
MESSAGE
Bad data item reference (or see above)
CAUSE
For DBINFO (modes 101, 102, and 204), data item
reference is:
• Numeric but out of range of the number of data items
in database
• An erroneous data item name
• A reference to data item which is inaccessible to user
class established when database opened.
An erroneous data item name may arise when a
terminating semicolon or blank is omitted.
-22
-23
-24
-30
Chapter 6
ACTION
Check application program's procedure call. Correct error
in call.
MESSAGE
Maintenance word required
CAUSE
For DBOPEN, maintenance word is required for
non-creator to access the database.
ACTION
Supply the correct maintenance word.
MESSAGE
Data set not writable
CAUSE
For DBPUT and DBDELETE, database has been opened
in DBOPEN mode 1, 3, or 4 and user has read but not
write access to the referenced data set.
ACTION
Modify access mode set in procedure call or notify current
user operation cannot be performed.
MESSAGE
Operation not allowed on automatic master
data set
CAUSE
For DBPUT, the referenced data set is an automatic
master.
ACTION
Modify data set name in call or in data set type in schema.
MESSAGE
ILR enabled and bad access
CAUSE
The database has been ported from MPE V with ILR
enabled. The only allowable access to the database is
253
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
DBOPEN, mode 1–8, or DBUTIL to disable ILR.
ACTION
-31
-32
Open the database with mode 1–8 or disable ILR.
MESSAGE Bad mode
CAUSE
This error occurs in all procedures when the mode
parameter is invalid. For DBGET, mode is 7 or 8 and
referenced data set is a detail, or mode is 5 or 6 and
referenced data set is a detail without search items.
ACTION
Correct mode in procedure call.
MESSAGE Unobtainable mode
CAUSE
For DBOPEN, root file cannot be FOPENed with access
options (AOPTIONS) required for the specified mode.
Second element of calling program's status area is
required AOPTIONS, and third element is the AOPTIONS
granted to DBOPEN by MPE/iX file system.
This error usually occurs either due to concurrent
database access by other users or due to MPE/iX account
or group security provisions.
ACTION
See the MPE/iX Intrinsics Manual (32650-90028) for
meaning of AOPTIONS values.
Action depends on program's design. Normally notify user
that requested access mode is not available.
-33
-51
MESSAGE
Mode 7 diagnostics not allowed
CAUSE
For DBGET, mode 7 is not appropriate for diagnostics.
ACTION
Use a different mode for DBGET when diagnostic item list
is in effect.
MESSAGE Bad list length
CAUSE
For DBGET, DBUPDATE, and DBPUT, the list is too long.
This may occur if list is not terminated with a semicolon or
blank. It may also occur for otherwise legitimate lists
which are too long for TurboIMAGE/XL's work area.
It will never occur for numeric lists.
ACTION
-52
Shorter list array contents. If necessary, change to
numeric list.
MESSAGE Bad list or bad item
CAUSE
For DBGET, DBUPDATE, or DBPUT, the list parameter is
invalid. list either has a bad format or contains a data
item reference which:
• Is out of range of the number of data items in the
database.
• References an inaccessible data item.
254
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
• Duplicates another reference in the list.
For DBFIND, the item parameter contains data item
reference which either:
• Is out of range of the number of data items in the
database.
• Is not a search item for referenced data set.
-53
-60
-80
-81
-90
integer
-91
Chapter 6
ACTION
Check procedure call. Correct error in call or parameter.
MESSAGE
Missing search or sort item
CAUSE
For DBPUT, a search or sort item of referenced data set is
not included in list parameter.
ACTION
Check procedure call. Correct error in call or parameter.
MESSAGE
Illegal file equation on root file
CAUSE
When using a :FILE command with the database name or
a database-access file name, only the file designators and
DEV= parameters are allowed.
ACTION
Reenter :FILE command without illegal parameters.
MESSAGE
Output Deferred not allowed with ILR enabled
CAUSE
DBCONTROL (mode 1) was used to request deferred
output, but deferred output cannot be used when ILR is
enabled. Output deferred is not initiated.
ACTION
Do not use deferred output; or run DBUTIL and disable
ILR.
MESSAGE
Output Deferred not allowed with ROLLBACK
enabled
CAUSE
DBCONTROL (mode 1) was used to request deferred
output, but deferred output cannot be used when
ROLLBACK is enabled. Output deferred is not initiated.
ACTION
Do not use deferred output; or run DBUTIL and disable
ROLLBACK.
MESSAGE Root file bad: unrecognized state: %octal
CAUSE
For DBOPEN, this error is returned if the root file is in an
unrecognized state. The octal integer represents an ASCII
error code.
ACTION
Restore old copy of the root file for the database.
MESSAGE
Bad root modification level
CAUSE
For DBOPEN, the software version of the DBOPEN
procedure is incompatible with version of Schema
Processor which created root file.
255
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-92
ACTION
Check with system manager that you have correct
TurboIMAGE/XL software. If necessary ask HP support
personnel about conversion.
MESSAGE
Data base not created
CAUSE
For DBOPEN, the referenced database has not yet been
created and initialized by the DBUTIL program (in
CREATE mode).
ACTION
Run DBUTIL to create database. Try application program
again.
-94
MESSAGE Data base bad - Output deferred; may not be
accessed in mode nn
-95
-96
-97
-98
256
CAUSE
For DBOPEN, referenced database was damaged while
being modified in output deferred mode.
ACTION
Either DBLOAD from backup tape; or DBUNLOAD to
ERASE data and then DBLOAD.
MESSAGE
Data base bad - Creation was in process
(create again)
CAUSE
For DBOPEN, database was damaged by a file system
failure, system failure, or TurboIMAGE/XL abort while
DBUTIL CREATE command was creating the database.
ACTION
Because database was not created, run DBUTIL CREATE
command to create the database.
MESSAGE
Data base bad - Erase was in process (erase
again)
CAUSE
For DBOPEN, database was damaged by a file system
failure, system failure, or TurboIMAGE/XL abort while
DBUTIL ERASE command was erasing the database.
ACTION
Because data was not erased, run DBUTIL ERASE
command to erase the data from the database.
MESSAGE
Data base bad - ILR enable in process (enable
again)
CAUSE
DBOPEN attempted to open a database but prior disable
of ILR was not complete.
ACTION
Run DBUTIL with DNABLE command to enable ILR.
MESSAGE
Data base bad - ILR disable in process
(disable again)
CAUSE
DBOPEN attempted to open a database, but prior disable
of ILR was not complete.
ACTION
Run DBUTIL with DISABLE command to disable ILR.
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
NOTE
-100
-101
-102
-103
-104
-105
-106
Chapter 6
Return statuses 100 through 107 are communication errors. For 100 through
102, the third element of calling program's status area is the MPE/IX failure
code returned by DSCHECK intrinsics.
MESSAGE
DSOPEN failure
CAUSE
While executing a DBOPEN, TurboIMAGE/XL has
encountered a hardware failure trying to obtain a
communications line.
ACTION
Try opening the database again. If error persists, contact
your HP Support Representative.
MESSAGE
DSCLOSE failure
CAUSE
This is an exceptional error returned by DBOPEN or
DBCLOSE. It indicates a hardware or system software
failure.
ACTION
Notify system manager of problem.
MESSAGE
DSWRITE failure
CAUSE
A line failure has occurred while attempting an operation
on a remote database. May be returned by DBOPEN,
DBFIND, DBGET, DBPUT, DBUPDATE, DBDELETE,
DBLOCK, DBUNLOCK, DBINFO, or DBCLOSE.
ACTION
Try calling the procedure again. If error persists, notify
system manager.
MESSAGE
Remote 3000 stack too small
CAUSE
Command Interpreter on remote HP 3000 cannot obtain
stack space necessary to execute a DBOPEN or DBLOCK.
ACTION
Ask system manager of remote system to increase
available stack size.
MESSAGE
Remote 3000 does not support TurboIMAGE/XL
CAUSE
This is an exceptional error and is returned by DBOPEN
on the remote system.
ACTION
Notify system manager of problem.
MESSAGE
Remote 3000 cannot create TurboIMAGE control
block.
CAUSE
This is an exceptional error and is returned by DBOPEN
on the remote system.
ACTION
Notify system manager of problem.
MESSAGE
Remote 3000 data inconsistent
CAUSE
This is an exceptional error returned by same intrinsics as
102 (see message listed earlier in this chapter). It
257
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
indicates a hardware or system software failure.
-107
-108
-110
-111
-112
-113
-114
-121
258
ACTION
Notify system manager of problem.
MESSAGE
NS 3000 or DS 3000 system error.
CAUSE
This is an exceptional error returned by same intrinsics as
102 (see above). It indicates a hardware or system
software failure.
ACTION
Notify system manager of problem.
MESSAGE
HPUNLOADCMPROCEDURE call failed.
CAUSE
This is an internal error encountered during switching to
Compatibility Mode.
ACTION
Notify HP Support Representative.
MESSAGE
MPE OPENLOG intrinsic failure
CAUSE
OPENLOG returned error number nn to DBOPEN. This
error may occur following a call to DBOPEN when a
database is enabled for logging. Refer to MPE/iX
Intrinsics Manual for listing of second values of status
array and error messages.
ACTION
Notify system manager or HP Support Representative.
MESSAGE
MPE WRITELOG intrinsic failure
CAUSE
When a database is enabled for logging, this error may be
returned by DBOPEN, DBCLOSE, DBPUT, DBUPDATE,
DBDELETE, DBMEMO, DBBEGIN, DBEND.
ACTION
Notify database administrator.
MESSAGE
MPE CLOSELOG intrinsic failure
CAUSE
When a database is enabled for logging, this error may be
returned by DBCLOSE. Or CLOSELOG returned error
number nn to DBCLOSE.
ACTION
Notify database administrator.
MESSAGE FLUSHLOG returned error number nn to DBEND
CAUSE
User called DBEND in mode 2 to write the logging buffer
to disk, but the MPE/iX logging facility returned an error.
ACTION
Notify your database administrator.
MESSAGE
ROLLBACK without logging
CAUSE
DBOPEN has detected that ROLLBACK is enabled but
logging is not.
ACTION
Notify your database administrator or HP Support
Representative.
MESSAGE
Descriptor count error
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-123
-124
-125
-126
-127
-128
-129
-130
Chapter 6
CAUSE
DBLOCK detected an error in the descriptor count (first
element of qualifier array) in locking mode 5 or 6.
ACTION
Count must be a positive integer.
MESSAGE Illegal relop in a descriptor
CAUSE
DBLOCK encountered a relop field containing characters
other than >=, <=, = or =.
ACTION
Check contents of qualifier array.
MESSAGE
Descriptor too short. Must be greater than or
equal to 9
CAUSE
DBLOCK encountered a lock descriptor less than 9
halfwords long.
ACTION
Check contents of qualifier array.
MESSAGE
Bad set name/number
CAUSE
DBLOCK qualifier array contains an invalid data set
name or number. (Refer to error -21 for rules.)
ACTION
Check contents of qualifier array. Be sure names are
delimited by semicolon or space if less than 16 bytes long.
MESSAGE
Bad item name/number
CAUSE
DBLOCK qualifier array contains an invalid data item
name or number. (Refer to error 21 for rules.)
ACTION
Check contents of qualifier array. Be sure names are
delimited by semicolon or space if less than 16 bytes long.
MESSAGE
Attempt to lock using a compound item
CAUSE
DBLOCK does not allow compound items in lock
descriptors.
ACTION
Modify locking strategy to lock on a non-compound item.
MESSAGE
Value field too short in a descriptor
CAUSE
A value field in a DBLOCK lock descriptor must be at least
as long as the data item for which it is specified.
ACTION
Check the length of the value field.
MESSAGE
P-type item longer than P28 specified
CAUSE
DBLOCK does not allow P-type data items longer than 28
in lock descriptors (27 digits plus sign).
ACTION
Modify locking strategy to lock on a different item.
MESSAGE
Illegal digit in a P-type value
CAUSE
DBLOCK has encountered a P-type value in a lock
descriptor with an invalid packed decimal digit.
259
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-131
-132
-133
-134
-135
-136
-151
-152
260
ACTION
Check qualifier array contents to determine why data is
invalid.
MESSAGE
Lowercase character in type-U value
CAUSE
DBLOCK has encountered a lowercase character in a
type-U value specified in a lock descriptor.
ACTION
Check qualifier array contents to determine why data is
invalid.
MESSAGE
Illegal digit in type Z value
CAUSE
Lock descriptor value specified to DBLOCK contains an
invalid zoned decimal digit.
ACTION
Check qualifier array contents to determine why data is
invalid.
MESSAGE
Illegal sign in type Z value
CAUSE
Lock descriptor value specified to DBLOCK contains an
invalid zoned decimal sign.
ACTION
Check qualifier array contents to determine why data is
invalid.
MESSAGE
Two descriptors conflict
CAUSE
DBLOCK has detected two lock descriptors in the same
call that lock the same or part of the same database entity.
(For example, lock on set and database in same request.)
ACTION
Check qualifier array contents for conflicting lock
descriptors.
MESSAGE
Second lock without CAP=MR
CAUSE
A second call to DBLOCK has been made without an
intervening DBUNLOCK call and program does not have
MR capability.
ACTION
Read discussion of multiple calls to DBLOCK in Chapter 4
of this manual if you plan to use CAP=MR.
MESSAGE
Descriptor list exceeds 4094 bytes
CAUSE
DBLOCK allows a maximum length of 4094 bytes for lock
descriptor lists (qualifier array).
ACTION
Change qualifier array contents so lock descriptor list is
shorter.
MESSAGE
Text length greater than 512 bytes
CAUSE
Returned by DBBEGIN, DBEND, or DBMEMO.
ACTION
Modify program.
MESSAGE
DBCLOSE called while a transaction is in
process; DBBEGIN called
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
while a transaction is in process
-153
-160
CAUSE
A transaction is in process.
ACTION
Call DBEND before DBCLOSE. Call DBEND before the
next DBBEGIN.
MESSAGE
DBEND called while no transaction in progress
CAUSE
No DBBEGIN precedes the call to DBEND.
ACTION
Call DBBEGIN before DBEND.
MESSAGE
ILR log file name conflict
CAUSE
There is a user file with the same name as the ILR log file
name.
ACTION
Replace the user file with a valid MPE/iX ILR log file.
-161
MESSAGE Cannot check for an ILR log file conflict: file
system error nn
-166
-167
-168
nn
-169
-170
Chapter 6
CAUSE
DBUTIL DISABLE command or call to DBOPEN failed to
open ILR log file.
ACTION
Check file system error number.
MESSAGE Cannot purge ILR log file: file system error nn
CAUSE
DBUTIL DISABLE, PURGE, or ERASE command could
not purge an ILR log file because of a file system error.
ACTION
Check file system error number.
MESSAGE Cannot begin MPE XL XM transaction: XM error nn
CAUSE
The logical beginning of an MPE/iX transaction failed. nn
is the error number returned.
ACTION
Notify HP Support Representative.
MESSAGE Cannot attach n to MPE XL XM: File system error
CAUSE
Data set n could not be "attached" to the MPE/iX
transaction recovery mechanism. MPE/iX intrinsic
FILEINFO or FLABELINFO failed.
ACTION
Notify HP Support Representative.
MESSAGE
Invalid mode for XM attach options
CAUSE
An internal error has occurred.
ACTION
Notify HP Support Representative.
MESSAGE Cannot open ILR log file: file system error nn
CAUSE
DBUTIL DISABLE command or call to DBOPEN was not
able to open ILR log file due to file system error.
ACTION
Check file system error number.
261
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-172
-173
-174
-175
-176
-177
-178
error nn
-179
262
MESSAGE Cannot read ILR log file: file system error nn
CAUSE
DBUTIL DISABLE command or call to DBOPEN was not
able to read ILR log file due to file system error.
ACTION
Check file system error number.
MESSAGE
Unable to obtain write access
CAUSE
DBOPEN has determined that it is necessary to perform
ILR. The current user does not have write access to the
database.
ACTION
Have the database opened by a user with write access.
MESSAGE
Bad mode for ILR
CAUSE
DBOPEN has determined that it is necessary to perform
ILR. The database must be opened for writing.
ACTION
Open the database in mode 1–4.
MESSAGE Cannot attach n to MPE XL XM: XM error nn
CAUSE
The data set n could not be "attached" to the transaction
recovery mechanism. nn is the MPE/iX error number
returned.
ACTION
Notify HP Support Representative.
MESSAGE Cannot detach n from MPE XL XM: XM error nn.
CAUSE
The data set n could not be "detached" from the
transaction recovery mechanism. nn is the MPE/iX error
number returned.
ACTION
Notify HP Support Representative.
MESSAGE
MPE log file is not in the same volume set as
the database.
CAUSE
MPE/IX transaction recovery requires that the user log file
must reside in the same volume set as the database.
ACTION
Build the MPE/iX user log file in same volume set as
database. NOTE: Because all files in a group are in same
volume set, :LISTGROUP indicates the volume set where
a database resides.
MESSAGE Cannot detach n from MPE XL XM: file system
CAUSE
The data set n could not be "detached" from the MPE/iX
transaction recovery mechanism. The MPE/iX intrinsic
FLABELINFO failed. nn is the file system error number
returned.
ACTION
Notify HP Support Representative.
MESSAGE Cannot begin MPE XL transaction for attach: XM
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
error nn
-180
-181
-182
-183
-184
Chapter 6
CAUSE
Before "attaching" the entire database to the MPE/iX
transaction recovery mechanism, a logical beginning of a
transaction is specified. The beginning of the transaction
failed. nn is the error number returned.
ACTION
Notify HP Support Representative.
MESSAGE
ILR log invalid - internal file name does not
match root file
CAUSE
DBUTIL DISABLE command or call to DBOPEN
attempted to open ILR log file, but file names inconsistent.
Unlikely to occur unless disk corrupted, or
TurboIMAGE/XL root file or ILR log file altered by
privileged mode user.
ACTION
Use DBRESTOR to restore database.
MESSAGE
ILR log file invalid - internal group name
does not match root file
CAUSE
DBUTIL DISABLE command or call to DBOPEN
attempted to open ILR log file, but group names do not
match. (See error −180 for possible cause.)
ACTION
Use DBRESTOR to restore database.
MESSAGE
ILR log invalid - internal account name does
not match root file
CAUSE
DBUTIL DISABLE command or call to DBOPEN
attempted to open ILR log file, but account names do not
match. (See error −180 for possible cause.)
ACTION
Use DBRESTOR to restore database.
MESSAGE
ILR log invalid - internal creation date does
not match root file
CAUSE
DBUTIL DISABLE command or call to DBOPEN was
unable to open ILR log file because its creation date was
not the same as the creation date of the TurboIMAGE/XL
root file. Could be caused by storing the database followed
by a partial restore with MPE/iX :RESTORE that
excluded either the root file or the ILR log file. If there was
an intervening ENABLE or DISABLE, the creation dates
will not match and only a partial DBSTORE/DBRESTOR
occurred.
ACTION
To avoid this problem always store database with
DBSTORE and restore with DBRESTOR. Using these
utilities assures that root file and ILR log file are
consistent.
MESSAGE
ILR log invalid - internal last access data
263
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
access data does not match root file
-187
-188
-189
error nn
-190
-191
-192
-193
-194
264
CAUSE
DBUTIL DISABLE command or call to DBOPEN was
unable to open ILR log file because its last access date does
not match the date in the root file. Possibly caused by a
store and then a partial restore (using MPE/iX
:RESTORE) of database.
ACTION
Always store database with DBSTORE and restore with
DBRESTOR to assure consistent dates in root file and log
file.
MESSAGE
ILR is already enabled for this database
CAUSE
DBUTIL ENABLE command attempted to enable a
database for ILR when ILR was already enabled.
ACTION
Warning only.
MESSAGE
ILR is already disabled for this database
CAUSE
DBUTIL DISABLE command attempted to disable a
database for ILR when ILR was already disabled.
ACTION
Warning only.
MESSAGE Cannot begin MPE XL transaction for detach: XM
CAUSE
Before "detaching" the entire database from the MPE/iX
transaction recovery mechanism, a logical ending of a
transaction is specified. The ending of the transaction
failed. nn is the error number returned.
ACTION
Notify HP Support Representative.
MESSAGE
Bad DBS
CAUSE
The Database System Control Block has been corrupted.
ACTION
Notify HP Support Representative.
MESSAGE
The DBS is full
CAUSE
DBOPEN has detected that there is no more room in the
DBS to hold any more DBG entries.
ACTION
Notify HP Support Representative.
MESSAGE
Invalid DBU
CAUSE
The database user local control block has been corrupted.
ACTION
Notify HP Support Representative.
MESSAGE
DBU control block is full
CAUSE
The database user local control block is full.
ACTION
Notify HP Support Representative.
MESSAGE
Invalid DBB
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-195
-196
-197
-198
-199
-200
-201
-202
NLINFO
CAUSE
The database buffer control block has been corrupted.
ACTION
Notify HP Support Representative.
MESSAGE
Invalid DBG
CAUSE
The database global control block has been corrupted.
ACTION
Notify HP Support Representative.
MESSAGE
DBB control block is full
CAUSE
The database buffer control block is full.
ACTION
Notify HP Support Representative.
MESSAGE
DBG control block is full
CAUSE
The database global control block is full.
ACTION
Notify HP Support Representative.
MESSAGE
Total DBOPEN count/user exceeds limit
CAUSE
The DBU index table, the DBUX, is full. This table is used
to map the baseid to the user's DBU. The DBUX holds a
maximum of 127 entries.
ACTION
Notify HP Support Representative.
MESSAGE Cannot end MPE XL XM transaction: XM error nn
CAUSE
The logical ending of an MPE/iX transaction failed. nn is
the error number returned. Any writes done on behalf of
the intrinsic will be rolled out. NOTE: This error is only
possible from DBPUT, DBDELETE, or DBUPDATE.
ACTION
Notify system manager.
MESSAGE
Data base language not system supported
CAUSE
DBOPEN attempted to open the database and found that
the language of the database is not currently configured.
The collating sequence of the language is unavailable;
DBOPEN cannot open the database.
ACTION
Notify system manager.
MESSAGE
Native Language Support not installed
CAUSE
NLS/3000 internal structures have not been built at
system start-up. The collating sequence table of the
language of the database is unavailable; DBOPEN cannot
open the database.
ACTION
Notify system manager.
MESSAGE MPE Native Language Support error nn returned by
CAUSE
Chapter 6
The error number given was returned by NLS/3000 on a
NLINFO call in DBOPEN.
265
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-206
-208
XM
-209
-210
ACTION
Notify system manager.
MESSAGE
Data base exceeds limits
CAUSE
DBOPEN has detected that the remote TurboIMAGE/XL
database exceeds the local IMAGE limitations. Remote
database access cannot be completed. A TurboIMAGE/XL
database can only be accessed from a local node (which has
IMAGE) if and only if the remote database has not
exceeded the IMAGE/3000 data set and data item
limitations.
ACTION
Access the remote TurboIMAGE/XL database from
another local node which also supports TurboIMAGE/XL.
MESSAGE MPE error nn returned by FLABELINFO for MPE XL
CAUSE
The MPE/iX file system error nn was returned by the
intrinsic FLABELINFO.
ACTION
Notify HP Support Representative.
MESSAGE
Invalid mode for MPE XL XM DETACH
CAUSE
An internal error has occurred.
ACTION
Notify HP Support Representative.
MESSAGE MPE error nn on log file name
CAUSE
MPE/iX file system error nn was returned while trying to
obtain the user log file name.
ACTION
Notify HP Support Representative.
MESSAGE
Internal error returned
CAUSE
Internal error nn occurred while in an intrinsic.
ACTION
Notify HP Support Representative.
-3nn
-1000
-1001
-1002
266
MESSAGE Switch failure, INFO nn, SUBSYS nn
CAUSE
The switch to Native Mode failed. SUBSYS nn is the
subsystem that failed. INFO nn is the error number
returned from that subsystem.
ACTION
Notify HP Support Representative.
MESSAGE
Switch to CM failed on CX'PCBXIMAGE
CAUSE
Internal error. This error is returned when DBOPEN calls
CM CX'PCBXIMAGE and encounters a switch to CM
failure.
ACTION
Notify HP Support Representative.
MESSAGE
HPLOADCMPROCEDURE failed on CX'PCBXIMAGE
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
-1003
CAUSE
Internal error. This error is returned when DBOPEN calls
HPLOADCMPROCEDURE for CM CX'PCBXIMAGE and
fails.
ACTION
Notify HP Support Representative.
MESSAGE Switch to NM failed on DBxxx, INFO nn SUBSYS nn
CAUSE
The switch to Native Mode failed. DBxxx is the
TurboIMAGE/XL intrinsic. SUBSYS nn is the subsystem
that failed. INFO nn is the error number returned from
that subsystem.
ACTION
Notify HP Support Representative.
Library Procedure Exceptional Conditions
10
11
12
13
14
15
Chapter 6
MESSAGE
Beginning of file
CAUSE
DBGET has encountered beginning of file during a
backward serial read. (There are no entries before the one
previously accessed.)
ACTION
Appropriate action depends on program design.
MESSAGE
End of file
CAUSE
DBGET has encountered the end of file during a forward
serial read. (There are no entries beyond the most recently
accessed one.)
ACTION
Appropriate action depends on program design.
MESSAGE
Directed beginning of file
CAUSE
DBGET has been called for a directed read with a record
number less than 1.
ACTION
Appropriate action depends on program design.
MESSAGE
Directed end of file
CAUSE
DBGET has been called for a directed read with a record
number greater than the capacity of data set.
ACTION
Appropriate action depends on program design.
MESSAGE
Beginning of chain
CAUSE
DBGET has encountered end of chain during a backward
chained read.
ACTION
Appropriate action depends on program design.
MESSAGE
End of chain
CAUSE
DBGET has encountered end of chain during a forward
chained read.
ACTION
Appropriate action depends on program design.
267
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
16
17
17
18
MESSAGE
Data set full
CAUSE
DBPUT has discovered that data set is full.
ACTION
Restructure database with larger capacity for this data
set.
MESSAGE
No master entry ( or see below)
CAUSE
DBFIND is unable to locate master data set entry (chain
head) for specified detail data set's search item value.
ACTION
Appropriate action depends on program design.
MESSAGE
No entry (or see above)
CAUSE
DBGET has been called to reread an entry, but no "current
record" has been established or a call to DBFIND has set
the current record to 0. DBGET is unable to locate master
data set entry with specified key item value. DBGET has
discovered that selected record is empty (does not contain
an entry). DBUPDATE or DBDELETE was called when
the "current record" was not established or was empty.
ACTION
Appropriate action depends on program design.
MESSAGE
Broken chain
CAUSE
For DBGET with mode parameter equal to 5 (forward
chained read), the "next entry" on current chain (as
designated by internally maintained forward pointer for
data set) contains backward pointer which does not point
to most recently accessed entry (or zero for first member of
a chain).
For DBGET with mode parameter equal to 6 (backward
chained read), the "next entry" on current chain in a
backward direction (as designated by internally
maintained backward pointer for data set) contains a
forward pointer which does not point to most recently
accessed entry (or zero for last entry in a chain).
This error can occur in DBOPEN access modes 1, 5, and 6
because another user can make database modifications
concurrent with this user's accesses. When this error
occurs, no data is moved to user's stack, although internal
pointers maintained by TurboIMAGE/XL in the DBB are
changed to new "offending" entry. (It becomes the current
entry.) Note that this error check does not detect all
structural changes. DBGET (mode 5 or 6) makes check
only when preceding call on data set was successful
DBFIND or DBGET.
20
268
ACTION
Begin reading chain again from first or last entry.
MESSAGE
Data base locked or contains locks
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
22
23
24
25
41
42
43
Chapter 6
CAUSE
DBLOCK Mode 2: The database cannot be locked. Refer to
value of status element three: if 0, database already
locked; if 1, database contains locked sets or entries. Mode
4, 6: The lock cannot be granted because the whole
database is already locked.
ACTION
Appropriate action depends on program design.
MESSAGE
Data set locked by another process
CAUSE
DBLOCK has detected that the data set is locked by
another process or this process through a different access
path. Returned in DBLOCK modes 4 and 6 only.
ACTION
Appropriate action depends on program design.
MESSAGE
Entries locked within set
CAUSE
DBLOCK has detected that data entries within requested
data set are locked by another process or this process
through a different access path. Returned in DBLOCK
mode 4 only.
ACTION
Appropriate action depends on program design.
MESSAGE
Item conflicts with current locks
CAUSE
Lock descriptors passed to DBLOCK specify a data item
that is different than one used to set existing locks.
TurboIMAGE/XL allows no more than one data item per
data set to be used at one time for locking purposes.
Returned in DBLOCK modes 5 and 6 only.
ACTION
Appropriate action depends on program design.
MESSAGE
Entries already locked
CAUSE
DBLOCK has detected that data entries requested to be
locked are already locked by another process or this
process through a different access path. Returned in
DBLOCK mode 6 only.
ACTION
Appropriate action depends on program design.
MESSAGE
Critical item
CAUSE
DBUPDATE has been asked to change value of search or
sort item.
ACTION
Correct call or notify user cannot update item.
MESSAGE
Read only item
CAUSE
DBUPDATE has been asked to change value of a data
item for which the user does not have write access.
ACTION
Notify user, cannot update item. Or change password in
program.
MESSAGE
Duplicate key item value
269
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
44
49
50
60
61
62
63
270
CAUSE
DBPUT has been asked to insert data entry into a master
data set with a key item value which already exists in data
set.
ACTION
Appropriate action depends on program design.
MESSAGE
Can't delete master entry with non-empty
detail chains
CAUSE
DBDELETE has been asked to delete master data set
entry which still has one or more non-empty chains.
ACTION
Appropriate action depends on program design.
MESSAGE
Illegal buffer address
CAUSE
Calling program's buffer (identified by buffer parameter)
address of DBGET or DBINFO is an unsupported memory
address.
ACTION
Correct the buffer parameter with a valid address. CM
user stack, NM user stack, and the NM heap are valid
memory areas in which to create a buffer parameter.
MESSAGE
Buffer too small
CAUSE
Calling program's buffer (identified by buffer parameter)
is too small to accommodate the amount of information
that DBGET or DBINFO wishes to return without
extending into the parameters area. This message is
returned only if the buffer is the last item in the user's
stack, and will overflow the stack boundaries.
ACTION
Correct procedure call, or change buffer name or size.
MESSAGE
Data base access disabled
CAUSE
DBOPEN has been called when the database has been
disabled for access.
ACTION
Notify database administrator.
MESSAGE
Data base opened more than 63 times by same
process.
CAUSE
DBOPEN has been called when the specified database has
already been opened 63 times by the same process.
ACTION
Correct your program so that DBOPEN does not open the
same database more than 63 times.
MESSAGE
DBG Control Block is Full
CAUSE
Lock area within DBG is full.
ACTION
Notify your database administrator.
MESSAGE
DBG disabled; potential damage; only DBCLOSE
allowed
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
64
65
66
67
68
69
CAUSE
Another process sharing the database has aborted because
of logical inconsistency or internal error in
TurboIMAGE/XL, leaving DBG in potentially inconsistent
state. All user accesses through existing DBG are disabled
(except for DBCLOSE, mode 1). Returned by all intrinsics.
ACTION
Issue a DBCLOSE, mode 1.
MESSAGE
No room for DBG entry in PCBX (MPE/iX portion
of stack)
CAUSE
The PCBX is full.
ACTION
Try again when system resources are available.
MESSAGE
Can't grant buffer request
CAUSE
DBCONTROL cannot increase the number of buffers as
requested by the user. A current count is returned.
ACTION
Request a smaller number of buffers.
MESSAGE
DBG pointed to by root file does not match
CAUSE
Root file is not compatible with DBG.
ACTION
Notify HP Support Representative.
MESSAGE
DBU disabled; potential damage; only DBCLOSE
allowed
CAUSE
The user's control block is in an inconsistent state.
ACTION
Issue a DBCLOSE, mode 1.
MESSAGE
Bad DBB
CAUSE
Another process sharing the database has aborted because
of logical inconsistency or internal error in
TurboIMAGE/XL, leaving DBB in potentially inconsistent
state. All user accesses through existing DBB are disabled
(except for DBCLOSE, mode 1). Returned by all intrinsics.
ACTION
Issue a DBCLOSE, mode 1.
MESSAGE
Bad database
CAUSE
AUTODEFER is active, and the database did not close
normally. The database has been corrupted.
ACTION
Notify your database administrator.
MESSAGE
Missing chain head
CAUSE
User has attempted to add detail data entry with a search
item value that does not match any existing key item
value in corresponding manual master data set. The digits
represented by nn identify the offending path number
established by order in which their search items occur in
1nn
Chapter 6
271
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
set part of schema.
ACTION
Notify user cannot add entry or add manual master entry
and try again.
MESSAGE
Full chain
CAUSE
User has attempted to add detail data entry to a chain
which already contains the maximum allowable
(2,147,483,647) entries. The digits represented by nn
identify the offending path number (as described in 1nn).
ACTION
Consult with database manager. May need to delete some
entries from chain or restructure database.
MESSAGE
Full master
CAUSE
Automatic master data set is full. Therefore, when the
user attempted to add a search item to a detail data set,
the corresponding key value could not be added to the
automatic master data set. The digits represented by nn
identify the offending path number (as described in 1nn).
ACTION
Restructure database, increasing capacity of automatic
master.
MESSAGE
Warning: Assuming no message catalog
CAUSE
No message catalog is available.
ACTION
Notify your system administrator.
2nn
3nn
944
Others
MESSAGE Unrecognized return status: nn
CAUSE
Return status could not be recognized.
ACTION
Notify HP Support Representative.
Library Procedure Abort Condition Messages in I File
MESSAGE
BUFFER SUPPLY CRISIS
CAUSE
Internal software inconsistency caused TurboIMAGE/XL to mismanage its
buffer space.
ACTION
Notify the system manager and possibly HP Support Representative. Save
FID information if it is printed. You may need to perform database
recovery procedures.
MESSAGE CRITICAL LABEL READ ERROR ON data set
CAUSE
Unable to read label of database file.
ACTION
Notify the system manager and possibly HP Support Representative. Save
FID information if it is printed. You may need to perform database
recovery procedures.
272
Chapter 6
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
MESSAGE CRITICAL READ ERROR ON data set
CAUSE
An MPE/iX file read error encountered while reading database file.
ACTION
Notify the system manager and possibly HP Support Representative. Save
FID information if it is printed. You may need to perform database
recovery procedures.
MESSAGE ERROR intrinsic name STATUS return status; DBERROR/DBEXPLAIN
FAILED I info S subsys
CAUSE
The specified intrinsic encountered an error. ERROR displays the
intrinsic. STATUS is the return status from the intrinsic. The application
called either DBERROR or DBEXPLAIN. The switch to Native Mode
failed. I is the error number returned by the subsystem. S is the subsystem
that failed.
ACTION
Notify HP Support Representative.
MESSAGE ESCAPE FROM TURBOIMAGE/XL; PC: $pcode CODE: $escape code
CAUSE
A hardware or software trap occurred. pcode and escape code are hex
numbers. The first four hex digits represent the error code; the last four
represent the subsystem number.
ACTION
Notify the system manager and HP Support Representative if necessary.
Save the escape code number.
MESSAGE HPUNLOADCMPROCEDURE FAILED ON intrinsic name INFO info
SUBSYS subsystem
CAUSE
A problem was encountered when switching to Compatibility Mode (CM).
INFO is the error returned by the subsystem. SUBSYS is the subsystem
which failed.
ACTION
Notify HP Support Representative.
MESSAGE LABEL WRITE ERROR ON data set
CAUSE
Unable to complete the writing of a user label on database file.
ACTION
Notify the system manager and HP Support Representative if necessary.
MESSAGE LOST FREE SPACE IN data set
CAUSE
Internal software inconsistency caused unused record locations in data set
to become lost or unavailable. File information display is printed for the
data set.
ACTION
Notify the system manager and HP Support Representative if necessary.
MESSAGE NEGATIVE MOVE ATTEMPT: n
CAUSE
An internal software inconsistency has been found while attempting to
move data to or from user's stack.
ACTION
Notify the system manager and HP Support Representative if necessary.
MESSAGE THE intrinsic name parm PARAMETER NOT ALIGNED ON A 16-BIT
BOUNDARY
Chapter 6
273
TurboIMAGE/XL V iii C 5
Library Procedure Error Messages
CAUSE
The designated parameter, parm, is 8-bit aligned.
ACTION
Modify your application so that the parm parameter is 16-bit (halfword)
aligned.
MESSAGE
THE USER CANNOT BE IN SPLIT-STACK MODE
CAUSE
An application must be running on the user's stack when calling a
TurboIMAGE/XL intrinsic. It is not permitted to run in split-stack mode.
This message is only applicable if you are running in Compatibility Mode.
ACTION
Modify your Compatibility Mode application so that it is not running in
split-stack mode.
MESSAGE
UNABLE TO CLOSE DATA SET
CAUSE
Unable to close a database file.
ACTION
Modify your application so that the parm parameter is 16-bit (halfword)
aligned.
MESSAGE UNABLE TO OPEN A data set
CAUSE
Unable to open database file.
ACTION
Modify your application so that the parm parameter is 16-bit (halfword)
aligned.
MESSAGE WRITE ERROR ON data set
CAUSE
An MPE/iX file write error found while writing into database file.
ACTION
Modify your application so that the parm parameter is 16-bit (halfword)
aligned.
MESSAGE WRONG NUMBER OF PARAMETERS OR BAD ADDRESS FOR PARAM #n
CAUSE
An address referenced by one of the parameters is not within the user's
stack area in memory. The n is a positional number of the parameter in the
procedure's calling sequence. The first parameter is #1, the second #2, and
so on.
ACTION
Modify your application so that the parm parameter is 16-bit (halfword)
aligned.
274
Chapter 6
7 TurboIMAGE/XL V iii C 5
TurboIMAGE/XL issues three different types of error messages:
• Schema Processor Error Messages
• Library Procedure Error Messages
• Utility Error Messages
275
TurboIMAGE/XL V iii C 5
Utility Error Messages
Utility Error Messages
Two types of error messages are generated by the utility programs. The first type consists
of conditional errors associated with accessing the desired database. For all utility
programs except DBUTIL, errors generating these messages can be corrected without
terminating the run if you are in session mode. DBUTIL errors of this type may terminate
the program. After printing the error message, the DBUTIL program reprompts with two
greater than symbols (>>). Other utilities reprompt with the message"WHICH
DATABASE?", allowing you to reenter the database reference. If you wish to terminate the
utility program at this point, you may type a carriage return with or without leading
blanks. If you are in job mode, conditional errors always cause program termination.
Conditional error messages and their meanings are described in the section entitled
"Utility Program Conditional Messages".
Unconditional errors occur in utility programs after successful execution has already
begun. These errors usually cause program termination. The accompanying messages and
their meanings are described in the section entitled "Utility Program Unconditional
Messages."
Utility Program Conditional Messages
MESSAGE
ACCESS DISABLED UNTIL RECOVERY HAS COMPLETED
CAUSE
Database is disabled for access, and recovery is enabled.
ACTION
Users will be able to access the database after the recovery process has
completed.
MESSAGE
ACCT NAME MORE THAN 8 CHARACTERS
CAUSE
The acctname part of DBNAME2 is too long.
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
APPARENT BACKUP/LOGFILE MISMATCH
CAUSE
A call to DBPUT, DBUPDATE, or DBDELETE, that apparently succeeded
when logging has failed during recovery.
ACTION
Make sure the proper backup database was restored and that the
matching log file was used for recovery.
MESSAGE
AUTODEFER MUST BE DISABLED BEFORE ILR CAN BE ENABLED
CAUSE
AUTODEFER option in DBUTIL has been enabled for the database.
ROLLBACK or ILR cannot be enabled while output deferred mode is
enabled.
ACTION
Run DBUTIL and >>DISABLE AUTODEFER and >>ENABLE ILR or
ROLLBACK for the database.
MESSAGE
AUTODEFER MUST BE DISABLED BEFORE ROLLBACK CAN BE ENABLED
CAUSE
The rollback recovery option cannot be used when the database has been
enabled for AUTODEFER.
276
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
Disable AUTODEFER and enable ROLLBACK using DBUTIL.
MESSAGE
BACKUP DATABASE AND LOG FILE DO NOT MATCH
CAUSE
The logid of the log file and the logid in the database being recovered do
not match; i.e., the correct log file is not being used for recovery.
ACTION
Make sure that the database is using the correct log file.
MESSAGE
BAD DATA BASE REFERENCE
CAUSE
Data base reference following the utility program :RUN command has a
syntax error.
ACTION
Correct the error in session mode or press return to terminate the
program.
MESSAGE
BAD MAINTENANCE WORD
CAUSE
User invoking the utility is not the creator of the referenced database and
has not supplied the correct maintenance word.
ACTION
Correct the error in session mode or press return to terminate the
program.
MESSAGE
CANNOT ENABLE BREAK KEY
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
CANNOT OPEN DATABASE
CAUSE
The database cannot be opened at this time. It may already be open in a
mode that does not allow concurrent access.
ACTION
Try the DBUTIL command again later.
MESSAGE
CANNOT PARSE LOG FILE NAME
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
CAN'T RECOVER DATA BASES IN STATISTICAL MODE
CAUSE
The CONTROL STATS command was entered subsequent to a RECOVER
command.
ACTION
Rerun DBRECOV without using statistical mode, or use statistical mode
without specifying databases or recovery.
MESSAGE CAN'T OPEN DATA BASE- DBERROR message
CAUSE
Database cannot be opened.
ACTION
Check the DBERROR message to determine the problem.
MESSAGE CHECKSUM FAILURE ON LOG RECORD #n -EOF ASSUMED
CAUSE
Chapter 7
May occur if the system failed and a startup recovery is not performed.
Also may occur if a statistical recovery is used against an open log file.
277
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
You may want to use a warmstart recovery in the future, but this is not
absolutely necessary.
MESSAGE
COULD NOT FIND OPEN DATABASE IN DATABASE TABLE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
CURRENT SINGLE TRANSACTION DOESN'T MATCH LOG TRANSACTION
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
CURRENT TRANSACTION DOESN'T MATCH LOG FILE TRANSACTION
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
DATABASE-ACCESS FILE DOES NOT EXIST
CAUSE
No such file exists in the logon user or account.
ACTION
Check the files in group to determine the correct file name.
MESSAGE
DATABASE-ACCESS FILE NAME MAY NOT BE QUALIFIED
CAUSE
The DBA file name cannot be qualified with group and account.
ACTION
Log on in the same group and account as the database-access file.
MESSAGE
DATABASE-ACCESS FILENAME TOO LONG
CAUSE
The file name has more than six characters.
ACTION
Rename the file and try DBUTIL again.
MESSAGE
DATA BASE ALREADY CREATED
CAUSE
You have invoked DBUTIL in the CREATE mode and specified the name of
a database which already exists.
ACTION
In session mode, correct the error or press Return to terminate program.
MESSAGE DATA BASE ALREADY DISABLED FOR option
CAUSE
The option has already been disabled for this database.
ACTION
Press return to terminate the program.
MESSAGE DATA BASE ALREADY ENABLED FOR option
CAUSE
The option has already been enabled for this database.
ACTION
Press return to terminate the program.
MESSAGE
DATA BASE CANNOT BE ERASED UNTIL RECOVERY HAS COMPLETED
CAUSE
Erasing database is attempted when recovery was started but not
completed, or while recovery is in RESTART mode.
ACTION
Press return to terminate program. After the recovery process has
completed, the user can run DBUTIL again.
278
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
DATA BASE CANNOT BE PURGED UNTIL RECOVERY HAS COMPLETED
CAUSE
Purging the database is attempted when recovery was started but not
completed, or while recovery is in RESTART mode.
ACTION
Press return to terminate program. After the recovery process has
completed, the user can run DBUTIL again.
MESSAGE
DATA BASE CONTAINS INVALID LOGGING IDENTIFIER
CAUSE
The log identifier in the database root file does not exist in the MPE/iX
table.
ACTION
Use DBUTIL to set a valid log identifier into the database.
MESSAGE
DATA BASE HAS BEEN MODIFIED SINCE LAST RESTORE
CAUSE
The DBSTORE flag has not been reset. This may mean a backup database
has not been restored, or that there have been modifications since the last
restoration.
ACTION
Restore the backup database, or use the CONTROL NOSTORE option and
reenter the RECOVER command.
MESSAGE DATA BASE n HASN'T BEEN CREATED YET
CAUSE
The database creator must run DBUTIL and CREATE the database.
ACTION
In session mode, correct the error or Return to terminate the program.
MESSAGE
DATA BASE IN USE
CAUSE
Utility program cannot get exclusive access to the referenced database due
to other current users.
ACTION
In session mode, press Return to terminate the program.
MESSAGE
DATA BASE IS NOT EMPTY. LANGUAGE CANNOT BE CHANGED
CAUSE
The language can be changed only on a virgin root file or an empty
database.
ACTION
In session mode, press return to terminate the program.
MESSAGE
DATA BASE IS REMOTE
CAUSE
You must be logged on to the same group and account containing the root
file to use DBUTIL.
ACTION
Do a remote logon and run DBUTIL from your remote session.
MESSAGE
DATA BASE NAME MAY NOT BE QUALIFIED
CAUSE
The database name cannot be qualified with group and account.
ACTION
Log on to the same group and account as the database and reenter the
command.
MESSAGE
DATA BASE NAME TOO LONG
CAUSE
The database name you specified has more than six characters.
ACTION
Try the command again with the correct name.
Chapter 7
279
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
DATA BASE NOT ENABLED FOR RECOVERY
CAUSE
The recovery flag in the database root file is disabled.
ACTION
Be sure you are running recovery against the appropriately restored
database. You can override the disable flag with DBUTIL if necessary.
MESSAGE
DATA BASE LANGUAGE NOT SYSTEM SUPPORTED
CAUSE
The language of the database is not currently configured on your system.
ACTION
Notify the system manager.
MESSAGE
DATABASE OR ACCESS FILE DOES NOT EXIST
CAUSE
No such file exists in logon group or account.
ACTION
Check the files in your group to find the correct file name.
MESSAGE
DATA BASE OR FILE ACCESS NAME REQUIRED
CAUSE
The command must include the database or access file name.
ACTION
Reenter the command.
MESSAGE
DATA BASE OR FILE ACCESS NAME TOO LONG
CAUSE
File name has more than six characters.
ACTION
Reenter the command with the correct name.
MESSAGE
DATA BASE REQUIRES CREATION
CAUSE
The database creator must run the DBUTIL program in CREATE mode
prior to executing DBUNLOAD, DBLOAD, or DBUTIL in ERASE mode.
ACTION
In session mode, correct the error or press return to terminate the
program.
MESSAGE
DATABASE TABLE OVERFLOWED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
DATABASE TABLE TRANSACTION COUNT IS NEGATIVE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE DATA SET n IS MISSING
CAUSE
The data set may have been purged, or was not restored.
ACTION
Contact your database administrator or system manager.
MESSAGE
DBBEGIN FOUND AN ALREADY ACTIVE TRANSACTION
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
DBBEGIN FOUND PROCESS ALIVE, BUT NOT ACTIVE
CAUSE
Internal error.
280
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
Contact your system manager.
MESSAGE
DBEND FOUND TRANSACTION STILL ALIVE AND ACTIVE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
DBEND FOUND TRANSACTION WHICH ALREADY ENDED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
DBNAME DBSTORE OF TIME, DATE REQUIRED
CAUSE
DBSTORE timestamp in database does not match those in DBOPEN
records.
ACTION
Restore the proper database or use the proper log file. You can also use the
NOSTAMP option in recovery.
MESSAGE
DBLOAD TO DIFFERENT DATABASE NAME
MAINTENANCE WORD IS NOT ALLOWED
CAUSE
The DBLOAD database name and maintenance word must be the same as
those used for DBUNLOAD.
ACTION
Use a database name and maintenance word which were used for the
DBUNLOAD.
MESSAGE
DBLOAD TO DIFFERENT GROUP OR ACCOUNT IS NOT ALLOWED.
CAUSE
DBLOAD must be done from the same group and account as the
DBUNLOAD file.
ACTION
Log on to the same group and account from which the DBUNLOAD was
done. Then use DBLOAD again.
MESSAGE
DUPLICATE FILE NAME
CAUSE
The required file name is already assigned to another file. Example: If the
ORDERS database requires six data sets (ORDERS01–ORDERS06), then
a previously defined file ORDERS03 will trigger this message. This can
occur if a database is not purged before running DBRESTOR.
ACTION
In session mode, correct the error or press return to terminate the
program.
MESSAGE
DBNAME1 MORE THAN SIX CHARACTERS
CAUSE
dbname1 is too long.
ACTION
Use EDITOR to change the FILE command.
MESSAGE
'DEV' MISSING
CAUSE
Either the keyword DEV or the following "=" was not found.
ACTION
Use EDITOR to change the FILE command.
MESSAGE
DEVICE NOT 'DISC'
Chapter 7
281
TurboIMAGE/XL V iii C 5
Utility Error Messages
CAUSE
The string following the "#" sign was not "DISC."
ACTION
Use EDITOR to change the FILE command.
MESSAGE
DSDEVICE DOESN'T MATCH FILE COMMAND
CAUSE
The dsdevice name in the DSLINE command was not the same as the
dsdevice name in the FILE command.
ACTION
Use EDITOR to change the command which is in error.
MESSAGE
DSDEVICE NAME MORE THAN 8 CHARACTERS
CAUSE
The dsdevice name is too long.
ACTION
Use EDITOR to change the command which is in error.
MESSAGE
EMBEDDED BLANK IN DBNAME2
CAUSE
One of the periods separating the user name from the group name or the
group name from the account name was preceded or followed by a blank.
ACTION
Use EDITOR to change the file command.
MESSAGE
ERROR READING ROOT FILE LABEL
CAUSE
DBUTIL is unable to read the root file.
ACTION
Contact your HP systems engineer.
MESSAGE
ERROR READING ROOT FILE RECORD
CAUSE
DBUTIL is unable to read a root file record.
ACTION
Contact your HP systems engineer.
MESSAGE
ERROR WRITING ROOT FILE LABEL
CAUSE
DBUTIL found an error while writing the root file label.
ACTION
Contact your HP systems engineer.
MESSAGE
ERROR WRITING ROOT FILE RECORD
CAUSE
DBUTIL found an error while writing to a root file record.
ACTION
Contact your HP systems engineer.
MESSAGE
EXCEEDS ACCOUNT DISC SPACE
CAUSE
Amount of space required by the database plus the space already assigned
to other files exceeds the disk space available to the account.
ACTION
Request system manager to increase account's disk space.
MESSAGE
EXCEEDS GROUP DISC SPACE
CAUSE
The amount of disk space required by the database plus the space assigned
to other files in the group exceeds the amount of disk space available to the
account.
ACTION
Request the system manager to increase the group's disk space.
MESSAGE
EXPECTED DATABASE STATE TO BE "CLOSED"
282
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
FCHECK FAILURE
FCLOSE FAILURE
FCONTROL FAILURE
FENTRY FAILURE
FGETINFO FAILURE
CAUSE
These are exceptional errors indicating a hardware or software failure.
ACTION
Notify your system manager of the failure.
MESSAGE
FFILEINFO INTRINSIC FAILED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
FGETINFO CANNOT VERIFY THAT FILE IS TYPE "LOG"
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
FGETINFO INTRINSIC FAILED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
FILE CODE IS NOT 0.
CAUSE
The database-access file to be activated has a file code of other than 0.
ACTION
Be sure you have the correct EDITOR file.
MESSAGE
FILE EQUATES ARE ILLEGAL FOR DATA BASE AND DATA BASE
ACCESS FILE
CAUSE
DBUTIL does not allow you to equate the name of the database or
database-access file to another file with the :FILE command.
ACTION
Use the :RESET command to cancel the :FILE command. You can either
break and resume execution or exit DBUTIL and run it again.
MESSAGE FILE file name RECSIZE TOO SMALL: LOG(S) TRUNCATED.
CAUSE
User recovery file size is too small to hold the largest log record.
ACTION
Increase record size or use variable length records.
MESSAGE
FILE NAME MAY NOT BE QUALIFIED
CAUSE
The file name may not be qualified with group and account.
ACTION
Log on to the same group and account and reenter the command.
MESSAGE
FILE NAME MORE THAN SIX CHARACTERS
CAUSE
The file name part of dbname2 is too long.
Chapter 7
283
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
FOPEN FAILURE ON logfilename:ferrmsg
CAUSE
You cannot open the log file.
ACTION
Examine ferrmsg to determine the cause.
MESSAGE
FREAD ERROR ON ASCII ACCESS FILE
CAUSE
Exceptional errors indicate a hardware or software failure.
ACTION
Notify the system manager of the error.
MESSAGE
FWRITE ERROR ON filename:ferrmsg
CAUSE
FWRITE failure on user recovery file.
ACTION
Check ferrmsg to determine the cause.
MESSAGE
GROUP NAME MORE THAN 8 CHARACTERS
CAUSE
The group name part of dbname2 is too long.
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
ILR MUST BE DISABLED BEFORE AUTODEFER CAN BE ENABLED
CAUSE
Output deferred option (AUTODEFER) cannot be used when the database
has been enabled for ILR or ROLLBACK.
ACTION
Disable ILR or ROLLBACK and enable AUTODEFER using DBUTIL.
(Refer to the appropriate documentation for more information on
AUTODEFER.)
MESSAGE
INCOMPLETE DBNAME2
CAUSE
The file name or group name is followed by a period and the rest of the
record is empty. Or the next character is a semicolon (;).
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
INCOMPLETE LOCAL PART
CAUSE
The period following the local user name was missing, or the account name
was missing, or a comma followed the account name and the group name
was missing.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
INCOMPLETE REMOTE PART
CAUSE
The period following the rusername was missing, or the raccountname
was missing, or the raccountname was followed by a comma and the
rgroupname was missing.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
INSUFFICIENT DISC SPACE
CAUSE
The amount of disk space required for the database is not available on the
system.
284
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
Consult with the system manager about disk space requirements.
MESSAGE
INSUFFICIENT VIRTUAL MEMORY
CAUSE
Not enough virtual memory is available to open and access the database.
ACTION
Try running the utility later when the system is not as busy.
MESSAGE
INTERNAL ERROR—CURRENT TRANSACTION COUNT IS NEGATIVE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—DATABASE CONTAINS INVALID LOGGING
IDENTIFIER
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—DATABASE SHOULD NOT BE OPEN AT THIS TIME
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—DBBEGIN FOUND PROCESS ALIVE, BUT TRAN
STATE INACTIVE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—EXPECTED DATABASE TO BE OPEN FOR THIS
PROCESS
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—FOPEN FAILS IN F'HEADLOG
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—FREADLABEL FAILS IN F'HEADLOG
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—HEAP STAGING AREA OVERFLOWED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—INVALID DATABASE TABLE ADDRESS
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—INVALID DBTAB'PROC'TAIL
Chapter 7
285
TurboIMAGE/XL V iii C 5
Utility Error Messages
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—INVALID PASSWORD FOR DATABASE LOGGING
IDENTIFIER
CAUSE
Log password does not correspond with the log identifier in the log file.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—INVALID PROCTABLE INDEX FOUND IN
PROC'ACTIVELINK
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—INVALID RECOVERY TABLE ADDRESS
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—LOGID'TO'FNAME FAILURE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—NO PROCESS TABLE ENTRY EXISTS
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—PROBLEM RETURNING HEAP
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—PROCESS NOT IN PROCESS TABLE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—PROCESS TABLE IS FULL
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—RECORD TABLE IS FULL
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INTERNAL ERROR—UNABLE TO ALLOCATE THE HEAP
CAUSE
Internal error.
ACTION
Contact your system manager.
286
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
INVALID ACCESS CLASS NUMBER
CAUSE
The access class should be a number between 1 and 63.
ACTION
Reenter with a valid access class number.
MESSAGE
INVALID CHARACTER IN PASSWORD
CAUSE
Password does not consist of allowed characters.
ACTION
Check the password specified and reenter the command.
MESSAGE
INVALID COMMAND
CAUSE
Command is unknown to the utility.
ACTION
Check spelling or see manual for legal commands.
MESSAGE
INVALID CONTENTS OF ASCII ACCESS FILE ACTIVATION /
DEACTIVATION FAILED
CAUSE
The file specified is either
1. Not a database-access file, or
2. It does not contain the valid format and parameters.
ACTION
Either
1. Verify the correct database-access file, or
2. Use EDITOR to make the required changes and try accessing again.
MESSAGE
INVALID DATA BASE CONTROL BLOCK
CAUSE
TurboIMAGE/XL encountered an inconsistency in the control blocks.
ACTION
Contact your system engineer.
MESSAGE
INVALID DATA BASE ACCESS FILE NAME
CAUSE
The file name or database name must be 1 to 6 characters starting with a
letter.
ACTION
Reenter the command with the correct name.
MESSAGE
INVALID DATA BASE NAME
CAUSE
The file name or database name must be 1 to 6 characters starting with a
letter.
ACTION
Reenter the command with the correct name.
MESSAGE
INVALID DATA BASE NAME OR ACCESS FILE NAME
CAUSE
The file name or database name must be 1 to 6 characters starting with a
letter.
ACTION
Reenter the command with the correct name.
MESSAGE
INVALID DB INTRINSIC CODE IN LOG RECORD CODE FIELD
CAUSE
Internal error.
ACTION
Contact your system manager.
Chapter 7
287
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
INVALID DELIMITER
CAUSE
The command or a space is incorrectly positioned.
ACTION
Use HELP to check command syntax and reenter the command.
MESSAGE
INVALID FIRST LOG FILE NAME
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INVALID FIRST LOG FILE SEQUENCE NUMBER
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INVALID FIRST LOG FILE TIMESTAMP
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INVALID IMAGE LOG RECORD DETECTED
CAUSE
DBRECOV encountered an undefined log record code.
ACTION
Notify the system manager and HP Support Representative.
MESSAGE
INVALID LANGUAGE
CAUSE
Language name or number has invalid characters.
ACTION
Retype the correct language name or number.
MESSAGE
INVALID LOG CODE IN LOG RECORD
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INVALID LOG DEVICE TYPE IN LOG RECORD
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INVALID LOG FILE DEVICE TYPE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
INVALID MAINTENANCE WORD
CAUSE
An incorrect maintenance word was used.
ACTION
Check the maintenance word specified and reenter the command.
MESSAGE
INVALID NUMBER OF BUFFERS SPECIFIED
CAUSE
The number of buffers must be between 4 and 255.
ACTION
Reenter DBUTIL >>SET command with a valid number.
MESSAGE
INVALID NUMBER OF USERS SPECIFIED
288
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
CAUSE
The minimum number of users allowed is 1 and the maximum is 120. The
ranges of users specified must be in ascending order.
ACTION
Reenter DBUTIL >>SET command with a valid number.
MESSAGE
INVALID PARAMETER
CAUSE
You specified an incorrect parameter.
ACTION
Use HELP to check the command format and reenter the command.
MESSAGE
INVALID PASSWORD FOR DATA BASE LOGGING IDENTIFIER
CAUSE
Log password does not correspond with the log identifier used with the
GETLOG command.
ACTION
Use DBUTIL to set the valid log identifier password into the database.
MESSAGE
INVALID SUBSYSTEM ACCESS FLAG IN ROOT FILE
CAUSE
TurboIMAGE/XL detected an invalid value for the subsystem access in the
root file. Valid accesses are READ, R/W, and NONE.
ACTION
Reset the subsystem access flag using DBUTIL >>SET command.
MESSAGE
INVALID TRANSACTION SEQUENCE DETECTED
CAUSE
Internal error. The transaction numbers are not consecutive.
ACTION
Notify your system manager and HP Support Representative.
MESSAGE INVALID (x) IN COLUMN y
CAUSE
The x represents the invalid character found in column y.
ACTION
Use the EDITOR to change the database-access file record which returns
the error message.
MESSAGE
LANGUAGE MUST NOT BE LONGER THAN 16 CHARACTERS
CAUSE
The language name is too long.
ACTION
Retype the correct language name.
MESSAGE
LANGUAGE NOT SUPPORTED
CAUSE
The language is not supported on your system or is not a valid language
name.
ACTION
Check with your system manager for the configuration of the language, or
enter a valid language name or number.
MESSAGE
LESS THAN 3 RECORDS IN FILE!
CAUSE
The database-access file does not contain a FILE, DSLINE, and HELLO
command.
ACTION
Use the EDITOR to create the missing records.
MESSAGE
LOCAL ACCT NAME IS TOO LONG
CAUSE
lacctname is more than eight characters.
ACTION
Use the EDITOR to change the lacctname.
Chapter 7
289
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
LOCAL GROUP NAME IS TOO LONG
CAUSE
lgroupname has more than eight characters.
ACTION
Use the EDITOR to change the lgroupname.
MESSAGE
LOCAL USER NAME TOO LONG
CAUSE
lusername has nore than eight characters.
ACTION
Use EDITOR to change the lusername.
MESSAGE
LOG BUFFER OVERFLOW
CAUSE
There is insufficient buffer space to build the log record.
ACTION
Notify the system manager and HP Support Representative.
MESSAGE
LOG BUFFER OVERFLOW DURING GET NEXT LOGICAL LOG RECORD
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
LOG FILE AND DATABASE IDs DO NOT MATCH
CAUSE
Internal error. Database is not using the correct log file.
ACTION
Contact your system manager.
MESSAGE
LOGFILE AND DATA BASE LOGID'S DO NOT MATCH
CAUSE
The restored database does not match the log file.
ACTION
Be sure the log file and the backup database are properly attached.
MESSAGE
LOG FILE HEADER RECORD IS NOT FIRST RECORD
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
LOGFILE IS EMPTY
CAUSE
The log file has no records.
ACTION
Be sure you have correctly identified the log file.
MESSAGE
LOG FILE OPEN FAILED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
LOG FILE RECORD SIZE IS IMPROPER
CAUSE
Internal error. The records are not 256 bytes with a fixed length.
ACTION
Be sure this file is actually a log file. Contact your system manager.
MESSAGE LOGID:logid IS INVALID
CAUSE
The database logid has been removed from the MPE/iX table.
ACTION
Set the database to an existing logid, or use the GETLOG command to
establish the database logid on the MPE/iX table.
290
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
LOGID MUST NOT BE LONGER THAN 8 CHARACTERS
CAUSE
The logid name is too long.
ACTION
Retype the correct logid to set into the database.
MESSAGE
LOGID PASSWORD IS INCORRECT
CAUSE
The password has been altered, or you are using the wrong password.
ACTION
Set the logid with the correct password into the database.
MESSAGE
LOGGING IS ENABLED, CAN NOT CLEAR LOGID
CAUSE
The logid cannot be changed while logging is in process in order to ensure
validity of recovery and logging.
ACTION
Change the logid after the recovery process has completed.
MESSAGE
LOG PERIOD DOES NOT EQUAL ONE (1)
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
MAINTENANCE WORD CANNOT BE CHANGED UNTIL RECOVERY HAS
COMPLETED
CAUSE
Changing maintenance word was attempted when recovery was enabled.
ACTION
After the recovery process has completed use the DBUTIL>>SET
command to change the maintenance word.
MESSAGE
MAINTENANCE WORD REQUIRED
CAUSE
The user invoking the utility is not the creator of the referenced database
and has not supplied a maintenance word.
ACTION
If DBUTIL, reenter the command with the maintenance word. Otherwise
correct the error or press return to terminate the program.
MESSAGE
MAINTENANCE WORD TOO LONG
CAUSE
The specified maintenance word has more than eight characters.
ACTION
Reenter the command with the correct maintenance word.
MESSAGE
MAXIMUM ERROR COUNT HAS BEEN EXCEEDED
CAUSE
DBRecov keeps track of all the errors that were encountered. If the
number goes past a certain threshold (default is 0, but can be configured
up to a maximum of 3000), DBRecov will abort.
ACTION
Correct the problems causing the errors. If the user specifies an error
count, this count could also be increased.
MESSAGE
MAXIMUM WARNING COUNT HAS BEEN EXCEEDED
CAUSE
DBRecov keeps track of all the warnings that were encountered. If the
number goes past a certain threshold, DBRecov will abort.
ACTION
If the user specifies a warning count, this count could be increased.
Chapter 7
291
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
MISSING!!
CAUSE
The key word FILE is not found in the first record; or the keyword
DSLINE is not found in the second record; or the keyword HELLO is not
found in any of the remaining records.
ACTION
Use the EDITOR to modify the record in the database-access file that
returned the error message.
MESSAGE
MISSING DBNAME1
CAUSE
An equal sign (=), semicolon (;), or end of line followed the keyword FILE.
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
MISSING DBNAME2
CAUSE
dbname1= followed by a semicolon (;) or end of line.
ACTION
Use EDITOR to change the FILE command.
MESSAGE
MISSING DSDEVICE
CAUSE
DEV= was followed by a semicolon (;), #, or the rest of the record was
blank.
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
MISSING LOCAL PART
CAUSE
No characters preceded the =HELLO.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
MISSING REMOTE PART
CAUSE
The remote-ID-sequence of the database-access file is missing.
ACTION
Use the EDITOR to add the remote part.
MESSAGE
MISSING REMOTE PASWD
CAUSE
HELLO was not followed by text, or was followed by a semicolon (;).
ACTION
Using the EDITOR, change the HELLO command.
MESSAGE
MISSING SEMI-COLON
CAUSE
DEV= was not preceded by a semicolon (;)
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
MISSING # SIGN
CAUSE
dsdevice was not followed by a #.
ACTION
Use the EDITOR to change the FILE command.
MESSAGE
MORE THAN ONE (1) LOG FILE HEADER RECORD IS FOUND
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
MULTIPLE LOG IDENTIFIERS NOT ALLOWED
292
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
CAUSE
You tried to simultaneously recover databases that logged to different log
files.
ACTION
Run DBRECOV once for each log file.
MESSAGE
NEGATIVE CURRENT RECORD NUMBER IN BACKSPACE REQUEST
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
NEGATIVE NUMBER OF BACKSPACES REQUESTED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
NLS RELATED ERROR
CAUSE
An error was returned by NLS/3000 on a DBOPEN on the database.
ACTION
Notify the system manager.
MESSAGE
NLINFO FAILURE
CAUSE
An error was returned by NLS/3000
ACTION
Notify system manager.
MESSAGE
NO DATA BASE HAS BEEN SPECIFIED FOR RECOVERY
CAUSE
RUN command has been entered and no databases have been specified for
recovery.
ACTION
Use the RECOVER command to specify database(s) or EXIT to terminate.
MESSAGE
NON-CREATOR ACCESS NOT PERMITTED
CAUSE
You must be the database creator to perform this function, or you must use
the maintenance word.
ACTION
Log on as the database creator, or use the maintenance word with the
command. If the maintenance word is not set, have the creator set one.
MESSAGE
NONEXISTENT LOGID
CAUSE
You are trying to set an unrecognized logid into the database, or the
database logid has been removed from MPE/iX.
ACTION
Use GETLOG to put the database logid into the MPE/iX table, or set an
existing logid into the database.
MESSAGE
NO SUCH DATA BASE
CAUSE
Specified database does not exist in users logon group.
ACTION
Check base name and logon account and group. Press return to terminate
the program.
MESSAGE
NOT A DATA BASE ACCESS FILE
CAUSE
The specified file is not a database-access file.
ACTION
Check the file name and try the command again.
Chapter 7
293
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
NOT A DATA BASE OR DATA BASE ACCESS FILE
CAUSE
The specified database is invalid, or the specified file is not a
database-access file.
ACTION
Check the database or file name and try the command again.
MESSAGE
NOT A DATA BASE ROOT FILE
CAUSE
The specified file is not a database root file.
ACTION
Check the specified database name and try the command again.
MESSAGE
NOT A PRIVILEGED DATA BASE ACCESS FILE
CAUSE
The database-access file has not been activated.
ACTION
Check the command and reenter it correctly.
MESSAGE
NOT ALLOWED; MUST BE CREATOR
CAUSE
The user invoking the utility is not the creator of the database and the
database has no maintenance word.
ACTION
Log on with correct user name, account and group.
MESSAGE
NOT AN UNPRIVILEGED DATA BASE ACCESS FILE
CAUSE
The database-access file is already activated.
ACTION
Check the command and reenter it if necessary.
MESSAGE
OUTMODED ROOT
CAUSE
The root file of the specified database corresponds to a different version of
IMAGE software and is not compatible with the utility program currently
executing.
ACTION
Consult with your system manager to verify the correct version of the
software. Ask HP Support Representative about conversion process.
MESSAGE
PARAMETER EXPECTED
CAUSE
The command you specified calls for another parameter.
ACTION
Use HELP to find the correct command syntax.
MESSAGE
PARAMETER MUST BE A COMMAND
CAUSE
Only command names may be specified with the HELP command.
ACTION
Reenter the command.
MESSAGE
PARAMETER SPECIFIED TWICE
CAUSE
The command specified requires only one parameter entry.
ACTION
Reenter the command.
MESSAGE
PARSE OF FILE REFERENCE FAILED
CAUSE
Internal error.
ACTION
Contact your system manager.
294
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
PASSWORD IS INCORRECT
CAUSE
The logid password in the database is not the same as the password in the
MPE/iX table.
ACTION
Set the logid and correct password into the database. Or, use the MPE/iX
ALTLOG command to alter the password in the MPE/iX table so it
matches the one in the database.
MESSAGE
PASSWORD MUST NOT BE LONGER THAN 8 CHARACTERS
CAUSE
The password is too long so it is incorrect.
ACTION
Retype the correct logid and password.
MESSAGE
PREMATURE EOF ON ASCII ACCESS FILE
CAUSE
DBUTIL encountered an end of file mark before at least one =HELLO
record in the database-access file.
ACTION
Use the EDITOR to change the ASCII file.
MESSAGE
PROCESS TABLE OVERFLOW
CAUSE
At some point more than 180 processes were logging at the same time.
ACTION
Notify your system manager and HP Support Representative.
MESSAGE
RECORD SIZE EXCEEDS 128 CHARACTERS!
CAUSE
The longest record in the database-access file exceeds the allowable length.
ACTION
Use the EDITOR to modify the database-access file.
MESSAGE
RECORDS ARE NUMBERED!
CAUSE
The database-access file is numbered.
ACTION
Use the EDITOR to keep the file unnumbered.
MESSAGE
RECORD TABLE OVERFLOW
CAUSE
More than 1000 detail records have been added and they have been given
relative record numbers different from those originally assigned. Wrong
database may have been restored, or not all modifications to the database
were logged.
ACTION
Run DBRECOV without the NOABORTS option or recover to a point
before the occurrence of the error. Or restore the correct database. Or
restore database and perform DBUNLOAD/DBLOAD.
MESSAGE
RECOVERY TABLE IS FULL
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
RECOVERY TABLE OVERFLOW
CAUSE
You tried to specify more than 100 user recovery files.
ACTION
Reduce the number of recovery files needed.
Chapter 7
295
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
RELEASE OF ENTRY FROM RECOVERY TABLE FAILED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE REMOTE ACCT racctname TOO LONG
CAUSE
racctname is more than eight characters long.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
REMOTE ACCT PASSWORD TOO LONG
CAUSE
rupasw is more than eight characters.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE REMOTE GROUP rgroupname TOO LONG
CAUSE
rgroupname is more than eight characters.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
REMOTE GROUP PASSWORD TOO LONG
CAUSE
rgpasw is more than eight characters.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE REMOTE USER rusername TOO LONG
CAUSE
rusername is more than eight characters.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
REMOTE USER PASSWORD TOO LONG
CAUSE
rupasw is more than eight characters.
ACTION
Use the EDITOR to change the HELLO command.
MESSAGE
RESTART FILE OPEN FAILED
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
ROLLBACK MUST BE DISABLED BEFORE AUTODEFER CAN BE ENABLED
CAUSE
Output deferred option (AUTODEFER) cannot be used when the database
has been enabled for ROLLBACK.
ACTION
Disable ROLLBACK and enable AUTODEFER using DBUTIL. (Refer to
the appropriate documentation for more information on AUTODEFER.)
MESSAGE
ROLLBACK MUST BE DISABLED BEFORE LOGGING CAN BE DISABLED
CAUSE
An attempt was made to disable logging while rollback was still enabled.
ACTION
Use DBUTIL >>DISABLE to disable the database for ROLLBACK, then
logging.
MESSAGE
ROOT FILE DOES NOT EXIST
CAUSE
A root file with the name of the specified database does not exist in the
296
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
logon group and account.
ACTION
Check the database name you specified and reenter the command.
MESSAGE SEQUENCE ERROR ON LOG RECORD #n - EOF ASSUMED
CAUSE
Log record numbers are out of sequence.
ACTION
Notify the system manager and HP Support Representative.
MESSAGE
STAGING FILE OVERFLOW
CAUSE
The staging file is not large enough.
ACTION
Use a file equation to increase the file size.
MESSAGE TIMESTAMP OUT OF SEQUENCE ON LOG RECORD #n - EOF ASSUMED.
CAUSE
Log record timestamps are out of sequence.
ACTION
Notify the system manager and HP Support Representative.
MESSAGE
TOO MANY PARAMETERS
CAUSE
Too many parameters were entered with the command.
ACTION
Reenter the command with the correct number of parameters.
MESSAGE
UNABLE TO COPY GLOBAL AND TABLE INFORMATION TO RESTART
FILE
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
UNABLE TO GET NEXT LOGICAL LOG RECORD
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
UNABLE TO GET PRIOR LOGICAL LOG RECORD
CAUSE
Internal error.
ACTION
Contact your system manager.
MESSAGE
UNKNOWN COMMAND, TRY HELP
CAUSE
DBUTIL does not recognize the command you specified.
ACTION
Enter the HELP command to get the list of DBUTIL commands.
MESSAGE
USER IS NOT CREATOR OF LOGGING IDENTIFIER
CAUSE
A function or activity was attempted by someone other than the creator of
the log identifier.
ACTION
Log on to the system as the user who created the log identifier or as a user
with system manager (SM) or operator (OP) capability.
MESSAGE
WARNING: DATA BASE MODIFIED AND NOT DBSTORED
CAUSE
The database has been enabled for logging but a backup copy has not been
made by executing DBSTORE.
Chapter 7
297
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
Execute DBSTORE to make a backup copy of the database.
MESSAGE
WARNING: THE LANGUAGE OF THE DATA BASE IS DIFFERENT
FROM THE LANGUAGE FOUND ON THE DBLOAD MEDIA.
CONTINUE DBLOAD OPERATION / (Y/N):
CAUSE
The user has changed language of database between DBUNLOAD and
DBLOAD. DBLOAD wants user to be aware of potential differences in
sorted chains of the collating sequence of the two languages. (The
language of database on disk and database on tape are different). In
session mode you are asked if you want to continue operation. In job mode,
DBLOAD will terminate execution.
ACTION
After looking at the information, DBLOAD returns with the result on the
sorted chains in the database. Continue the operation by answering Y
(yes).
MESSAGE
WARNING: THE NUMBER OF DATA SETS DEFINED IN THE SCHEMA IS
LESS THAN (OR GREATER THAN) THE NUMBER OF DATA SETS FOUND
ON THE DBLOAD MEDIA.
CAUSE
You have added or deleted data sets from the database between a
DBUNLOAD and a DBLOAD. DBLOAD will continue with the load, but
data may be lost or put into the wrong sets due to an invalid set change.
ACTION
Stop the DBLOAD, correct the schema, and perform DBLOAD again. Or, if
you are sure the database is not corrupt, allow DBLOAD to continue.
Utility Program Unconditional Messages
MESSAGE AUTOMATIC MASTER IS FULL ON PATH #n
CAUSE
DBLOAD is unable to load a detail entry because the automatic master set
associated with path n of the detail set is full.
ACTION
Re-create the root file with a larger capacity for automatic master. Rerun
the necessary utilities.
MESSAGE
***BAD DATA BASE***
CAUSE
This message is issued by DBSTORE, DBRESTOR, and DBUNLOAD. It
means the database is flagged "bad" because of a known structural error
due to an abnormal termination or to a system crash during DBLOAD or
some other "output deferred" operation. The current operation
(DBSTORE, DBRESTOR, DBUNLOAD) continues to function normally.
DBLOAD additionally prints the message "SERIAL UNLOAD FOLLOWS"
and automatically operates in serial mode. The database on disk retains
its "bad" flag and cannot be accessed through DBOPEN.
ACTION
The database is not usable in its current state. Purge it and restore a
backup copy, or erase it and then load a tape written by DBUNLOAD or
another external copy of the data.
MESSAGE
BROKEN FILE EQUATION CHAIN FOR TAPE FILE
CAUSE
Issued by DBSTORE if, in a chain of file equations, the actual device
298
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
designator cannot be found.
ACTION
Check your :FILE commands and reenter them correctly before running
DBSTORE.
MESSAGE
CANNOT GET EXTRA DATA SEGMENT NECESSARY FOR RESTORE
OPERATION
CAUSE
DBRESTOR was unable to get the extra data segment it needed for the
buffers used in the restore operation.
ACTION
Wait until system resources are available and then try again.
MESSAGE
CANNOT OPEN TERMINAL,
TERMINATING
CAUSE
DBUTIL is unable to access the terminal.
ACTION
Call HP Support Representative.
MESSAGE CAN'T CREATE NEW COPY OF FILE x (FS ERROR #)
CAUSE
MPE/iX intrinsic FOPEN failed while creating a temporary file.
ACTION
Check the file system error. Possible reasons: The specified device does not
exist, or there may be insufficient space on the device specified.
MESSAGE CAN'T GET SPECIFICATIONS VIA FGETINFO FOR THIS FILE x (FS
error #)
CAUSE
MPE/iX intrinsic FGETINFO failed. DBUTIL cannot get information for
the specified file.
ACTION
Check the file system error to determine cause.
MESSAGE CAN'T OPEN FILE x (FS ERROR #)
CAUSE
MPE/iX intrinsic FOPEN failed.
ACTION
Check the file system error to determine cause.
MESSAGE CAN'T PURGE OLD COPY OF FILE x (FS ERROR #)
CAUSE
MPE/iX intrinsic FCLOSE failed while purging the "old" file.
ACTION
Check the file system error to determine cause.
MESSAGE CAN'T RESET MOVE FLAG FOR FILE x IN THE ROOT FILE
CAUSE
Error occurred while writing root file label to reset the database return
status.
ACTION
Contact your system manager.
MESSAGE CAN'T SAVE NEW COPY OF FILE x (FS ERROR #)
CAUSE
MPE/iX intrinsic FCLOSE failed while saving the temporary file.
ACTION
Check file system error to determine the cause.
MESSAGE CAN'T SET MOVE FLAG FOR FILE x IN ROOT FILE
CAUSE
Chapter 7
DBUTIL set the root file flag, and an error occurred while writing the root
299
TurboIMAGE/XL V iii C 5
Utility Error Messages
file label.
ACTION
Contact your system manager.
MESSAGE CHAIN IS FULL ON PATH #n
CAUSE
DBLOAD is unable to load a detail entry because the chain count for path
number n of detail set exceeds 231 −1 (or 2,147,483,647 entries).
ACTION
Delete some of the entries and reload or change the database design.
MESSAGE
***COPY FAILED***
CAUSE
An error occurred while copying the file. DBUTIL has encountered a
problem reading or writing the files. (It is possible the disk pack is bad.)
ACTION
Restore the database and try the move again. Contact your system
manager if the copy fails again.
MESSAGE COULD NOT ATTACH DATA SET n TO XM LOG FILE: FILE SYSTEM ERROR
nn
CAUSE
The data set could not be "attached" to the MPE/iX transaction recovery
mechanism. nn is the file system error number returned.
ACTION
Notify HP Support Representative.
MESSAGE COULD NOT ATTACH DATA SET n TO XM LOG FILE: XM ERROR nn
CAUSE
The data set n could not be "attached" to the MPE/iX transaction recovery
mechanism. nn is the error number returned.
ACTION
Notify HP Support Representative.
MESSAGE COULD NOT DETACH DATA SET n FROM XM LOG FILE: FILE SYSTEM
ERROR nn
CAUSE
The data set n could not be "detached" from the MPE/iX transaction
recovery mechanism. The MPE/iX intrinsic FLABELOPEN failed. nn is
the file system error number returned.
ACTION
Notify HP Support Representative.
MESSAGE COULD NOT DETACH DATA SET n FROM XM LOG FILE:XM ERROR nn
CAUSE
The data set n could not be "detached" from the MPE/iX transaction
recovery mechanism. nn is the error number returned.
ACTION
Notify HP Support Representative.
MESSAGE
COULDN'T OPEN THE DATABASE
CAUSE
There is no root file for the specified file. It is possible that the file specified
is not part of the database.
ACTION
Check the file or database. Try the operation again with the correct file
name.
MESSAGE
DATA BASE STATE DOES NOT ALLOW MOVE TO BE DONE
CAUSE
The database is in a state in which MOVE cannot be performed.
300
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
ACTION
Check the database. If the database has not been created, run DBUTIL
>>CREATE. If the database is damaged, run recovery.
MESSAGE
DATA SET FULL
CAUSE
Data set currently being loaded is full.
ACTION
Re-create root file, increase the data set's capacity and run the utilities
again.
MESSAGE
***DBSTORE FAILED - NO DATA BASE STORED***
CAUSE
A file error or other message follows explaining the problem.
ACTION
Contact your HP Support Representative.
MESSAGE
EOF SEEN, PROGRAM TERMINATING
CAUSE
An :EOF has been entered.
ACTION
Run DBUTIL again.
MESSAGE
FGETINFO FAILURE
CAUSE
DBUTIL received an error when calling MPE/iX FGETINFO.
ACTION
Contact your system manager.
MESSAGE
FILE EQUATE FOR
DBSTORE
DBRESTOR
DBLOAD
DBUNLOAD
ONLY MAY USE DEV
CAUSE
If you specify an input/output file with a :FILE command for any of these
utility programs, only the file designators and DEV= parameters are
allowed.
ACTION
Enter :FILE command again and rerun program.
MESSAGE
FILE NOT ON TAPE
CAUSE
Issued by DBRESTOR if the database to be restored is not on the tape.
ACTION
Check your :FILE command and/or the tape you mounted.
MESSAGE FILE x ALREADY RESIDES ON DEVICE x
CAUSE
The file specified already resides on the device.
ACTION
Continue with the next desired command, or exit from DBUTIL.
MESSAGE
FREADDIR FAILURE
CAUSE
This is an MPE/iX exceptional failure and is returned when DBUTIL calls
FREADDIR.
ACTION
Contact your system manager.
Chapter 7
301
TurboIMAGE/XL V iii C 5
Utility Error Messages
MESSAGE
HARD TERMINAL READ ERROR, TERMINATING
CAUSE
DBUTIL cannot read input from terminal.
ACTION
Notify HP Support Representative.
MESSAGE
***INVALID SET COUNT***
CAUSE
TurboIMAGE/XL found an inconsistency in the data set count.
ACTION
Notify HP Support Representative.
MESSAGE MOVE OF FILE x NOT ALLOWED: FILE IS NOT CORRECT TYPE (FILE
CODE #)
CAUSE
The file specified is not a database file.
ACTION
Try the MOVE operation again with the correct file name.
MESSAGE NO MANUAL ENTRY FOR DETAIL ON PATH #n
CAUSE
DBLOAD is attempting to load detail data set entry n, which is the
number of the detail data set path referencing the manual master in
question.
ACTION
Add entry to manual master with application program or QUERY. Run
DBLOAD again.
MESSAGE RECSIZE MUST BE <=xxxx AND EVENLY DIVISIBLE BY 256.
CAUSE
Issued if REC= recsize parameter for DBSTORE specified a record size not
modulo 256 halfwords, or greater than the configured record size of the
device.
ACTION
Check the REC= recsize parameter and correct it before running
DBSTORE again.
MESSAGE
ROLLBACK LOG FILE MUST BE IN THE SAME VOLUME SET AS THE
DATABASE
CAUSE
MPE/iX transaction recovery requires that the MPE/iX user log file must
reside on the same volume set as the database.
ACTION
Build the MPE/iX user log file in the same volume set as the database.
NOTE: Because all files in a group are in the same volume set, the MPE/iX
command LISTGROUP indicates the volume set where the database
resides.
MESSAGE SWITCH TO NM TO ATTACH DATABASE TO XM LOG FILE FAILED: XM
ERROR nn
CAUSE
It is necessary to switch to NM to "attach" the database to the MPE/iX
recovery system. The switch failed. nn is the switch to NM error number
returned.
ACTION
Notify HP Support Representative.
MESSAGE SWITCH TO NM TO DETACH DATABASE FROM XM LOG FAILED: SWITCH
ERROR nn
CAUSE
302
It is necessary to switch to NM to "detach" the database from the MPE/iX
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
transaction recovery mechanism. The switch failed. nn is the switch to NM
error number returned.
ACTION
Notify HP Support Representative.
MESSAGE
UNABLE TO CONTINUE
CAUSE
DBUTIL program (operating in PURGE mode) cannot continue execution
due to exceptional error in file system. This information is followed by
MPE/iX file information display.
ACTION
Save the file information. Consult with system manager and HP Support
Representative.
MESSAGE UNABLE TO OBTAIN FILE LABEL INFORMATION FOR FILE x
CAUSE
MPE/iX internal procedure failed. DBUTIL cannot obtain information for
the specified file.
ACTION
Contact your system manager.
MESSAGE
UNEXPECTED ROOT FILE STATE
CAUSE
The MOVE process was unable to reset the database flag. The database
may be in an inconsistent state.
ACTION
Contact your system manager.
MESSAGE
WARNING: USER LOG FILE IS NOT IN THE SAME VOLUME SET AS
THE DATABASE
CAUSE
MPE/iX transaction recovery requires that the MPE/iX user log file must
reside on the same volume set as the database.
ACTION
Build the MPE/iX user log file in the same volume set as the database.
NOTE: Because all files in a group are in the same volume set, the MPE/iX
command LISTGROUP indicates the volume set where the database
resides.
Extended Utility Program Unconditional Messages
A set of messages may be returned when an unusual condition causes TurboIMAGE/XL to
fail while a TurboIMAGE/XL utility is executing. In each of the following messages, the
value xxxxx is the location where TurboIMAGE/XL failed.
Error messages 401 through 414 are all TurboIMAGE/XL utility failures caused by failure
of the TurboIMAGE/XL intrinsic specified in the message.
-3
MESSAGE
TURBOIMAGE FAILURE
(FREADDIR FAILURE ON ROOT FILE AT xxxxx)
-4
CAUSE
Root file was not readable. Problem may be in hardware.
ACTION
Notify the system manager of the error.
MESSAGE
TURBOIMAGE FAILURE
(FREADLABEL FAILURE ON ROOT FILE AT xxxxx)
Chapter 7
303
TurboIMAGE/XL V iii C 5
Utility Error Messages
-64
CAUSE
User's label was not readable. Problem may be in
hardware.
ACTION
Notify the system manager of the error.
MESSAGE
SET NUMBERS ARE OUT OF SEQUENCE.
TURBOIMAGE FAILED AT xxxxx
-66
CAUSE
The next set number on the backup volume was not what
DBLOAD expected. Status element 0 has the expected set
number; status element 1 has the next set number on the
backup volume.
ACTION
The schema may have been changed since the last
DBUNLOAD and this DBLOAD. Add any new set the the
end of the schema.
MESSAGE
BLOCK NUMBERS ARE OUT OF SEQUENCE.
TURBOIMAGE FAILED AT xxxxx.
-70
CAUSE
The next block on the backup volume was not what
DBLOAD expected. Status elements 0,1 have the expected
block number; elements 2,3 have the actual next block
number; element 4 has the set number.
ACTION
An error for a known value that was written to tape with
FWRITE was found. There may be a defect in the tape or
the tape drive.
MESSAGE
ENTRY NUMBERS ARE OUT OF SEQUENCE.
TURBOIMAGE FAILED AT xxxxx
-74
CAUSE
The next block on the backup volume was not what
DBLOAD expected. Status elements 0,1 have the expected
block number; elements 2,3 have the actual next block
number; element 4 has the set number.
ACTION
An error for a known value that was written to tape with
FWRITE was found. There may be a defect in the tape or
the tape drive.
MESSAGE
THE RECORD JUST READ IS UNRECOGNIZABLE
TURBOIMAGE FAILED AT xxxxx
CAUSE
The record just read from the backup volume was not what
DBLOAD expected. The record could be an EOF, EOT, etc.
The status element 0 has one of the following codes for the
record expected:
0–
tape head
1–
data file head
304
Chapter 7
TurboIMAGE/XL V iii C 5
Utility Error Messages
2–
data file block
3–
data file end
4–
tape end
97
98
101
401
402
403
Chapter 7
ACTION
An error for a known value that was written to tape with
FWRITE was found. There may be a defect in the tape or
the tape drive.
MESSAGE
ZSIZE ERROR WHILE CONTRACTING AT xxxxx
CAUSE
A TurboIMAGE utility called ZSIZE to contract the Z to
DB area of the stack. xxxxx is the octal location where
TurboIMAGE failed.
ACTION
Notify HP Support Representative.
MESSAGE
ZSIZE ERROR WHILE EXPANDING AT xxxxx
CAUSE
A TurboIMAGE utility called ZSIZE to expand the Z to DB
area of the stack. xxxxx is the octal location where
TurboIMAGE failed.
ACTION
Notify HP Support Representative.
MESSAGE
DBRESTOR FAILURE IN DBRESTOR AT xxxxx
CAUSE
The DBRESTOR utility called MPE/iX RESTORE which
encountered problems while restoring the database. A
detailed error message should follow this message.
ACTION
Take appropriate action depending on the detail message.
MESSAGE
DBOPEN FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBINFO FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBCLOSE FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
305
TurboIMAGE/XL V iii C 5
Utility Error Messages
earlier in this chapter.
404
405
406
407
408
409
410
411
306
MESSAGE
DBFIND FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBGET FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBUPDATE FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBPUT FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBDELETE FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBLOCK FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBUNLOCK FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBCONTROL FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
Chapter 7
TurboIMAGE/XL V iii C 5
User Logging
DBEXPLAIN.
412
413
414
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBBEGIN FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBEND FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
MESSAGE
DBMEMO FAILURE AT xxxxx
CAUSE
A detailed error message can be retrieved by calling
DBEXPLAIN.
ACTION
For more information "Library Procedure Error Messages"
earlier in this chapter.
User Logging
(ulogerr)
1
MESSAGE
Unable to open User Logging file !for
process!(ulogerr 1)
2
MESSAGE
Unable to open User Logging buffer file !for
process !(ulogerr 2)
3
MESSAGE
Can't open User Logging file !for
process!(ulogerr 3)
4
MESSAGE
No data segment available for user logging
process !(ulogerr 4)
5
MESSAGE
File label error on User Logging file !for
process !(ulogerr 5)
6
MESSAGE
Error writing to logging buffer file !for
process !(ulogerr 6)
7
MESSAGE
Error while writing to User Logging file !for
process !(ulogerr 7)
Chapter 7
307
TurboIMAGE/XL V iii C 5
User Logging
8
MESSAGE
End of file on User Logging file !for process
!(ulogerr 8)
9
MESSAGE
Out of disc space for process !(ulogmsg 9)
10
MESSAGE
User logging process !is running (ulogmsg 10)
11
MESSAGE
User logging process !is terminated (ulogmsg
11)
12
MESSAGE
Recovered !records for user logging process
!including !opens and !closes (ulogmsg 12)
13
MESSAGE
Error while recovering user logging file for
process !(ulogmsg 13)
14
MESSAGE
User logging file for process !not recovered
(ulogmsg 14)
15
MESSAGE
Recovering User Logging file !for process
!(ulogmsg 15)
17
MESSAGE
User logging file for process !is empty
(ulogmsg 17)
18
MESSAGE
User logging process !suspended, termination
pending (ulogmsg 18)
19
MESSAGE
Invalid disc user logging file for logid !
(ulogerr 19)
20
MESSAGE
Unable to start user logging process !
(ulogmsg 20)
21
MESSAGE
User logging process !in use, termination
pending (ulogmsg 21)
22
MESSAGE
User logging file for logging process !not
empty (ulogmsg 22)
23
MESSAGE
***** WARNING checksum failure on logging
file for process !***** ***** no End Of File
encountered ***** (ulogmsg 23)
24
MESSAGE
Recovered !records for user logging process !
(ulogmsg 24)
25
MESSAGE
Error reading user logging buffer file for
process !(ulogerr 25)
26
MESSAGE
Error closing user logging file for process !
(ulogerr 26)
27
MESSAGE
Error reading user logging file for process !
(ulogerr 27)
28
MESSAGE
Unable to restart user logging process !
(ulogmsg 28)
29
MESSAGE
User logging file for process !not completely
308
Chapter 7
TurboIMAGE/XL V iii C 5
User Logging
recovered after power fail (ulogerr 29)
30
MESSAGE
Invalid maximum number of users per process
found in log table (ulogerr 30)
31
MESSAGE
User logging file for process !is too small
(ulogerr 31)
32
MESSAGE
Power fail detected on ldev # !. Please put
tape drive back on-line (hit LOAD, RESET,
ON-LINE) (ulogmsg 32)
33
MESSAGE
Unable to open new disc buffer file !for
logid !(ulogerr 33)
34
MESSAGE
Unable to open new log file !for logid
!(ulogerr 34)
35
MESSAGE
New log file !for logid !would be too small
(ulogerr 35)
36
MESSAGE
Write failure on new buffer file !for logid
!(ulogerr 36)
37
MESSAGE
Write failure on new log file !for logid
!(ulogerr 37)
38
MESSAGE
Log file for logid !has been changed from !to
!(ulogmsg 38)
39
MESSAGE
Pending changelog for logid !was lost when
system crashed (ulogerr 39)
40
MESSAGE
Mount new !volume for changelog of logid
!(ulogmsg 40)
41
MESSAGE
Changelog for logid !failed due to error
(ulogerr 41)
42
MESSAGE
Error during changelog for logid !, will try
to return to previous log file !(ulogmsg 42)
43
MESSAGE
New log file !for logid !is a duplicate file
name (ulogerr 43)
44
MESSAGE
File label error on new log file !for logid
!(ulogerr 44)
45
MESSAGE
EOF on new log file !for logid !(ulogerr 45)
46
MESSAGE
Error closing new log file !for logid
!(ulogerr 46)
47
MESSAGE
Out of disc space for new log file !for logid
!(ulogerr 47)
48
MESSAGE
Error closing old disc buffer file !for logid
!(ulogerr 48)
49
MESSAGE
Error closing old log file !for logid
Chapter 7
309
TurboIMAGE/XL V iii C 5
Workstation Configuration
!(ulogerr 49)
50
MESSAGE
Log process for logid !has experienced a
previous error with the log file, and
therefore cannot perform a changelog
(ulogerr50)
51
MESSAGE
Changelog from log file !to !for logid !was
lost when the system went down (ulogmsg 51)
52
MESSAGE
Changelog for logid !was lost when the system
went down (ulogmsg 52)
53
MESSAGE
Power fail detected on ldev # !. Serial disc
recovery in progress. (ulogmsg 53)
54
MESSAGE
User logging power failure recovery
COMPLETED. (ulogmsg 54)
Workstation Configuration
(TTUTIL)
The error messages listed occur while entering data for a terminal-type or printer-type file.
Messages are displayed in inverse video on the bottom line of the screen. If the error(s) are
related to a field (or fields) on the screen, the fields are highlighted in full bright, inverse
video. If more than one field contains an error, only the error message for the first
highlighted field is displayed.
MESSAGE
Character already has other function.
CAUSE
The character entered has been defined elsewhere to have a different
special meaning. Each character can have only one special function.
ACTION
Choose a different character for this special function, or release this
character for use by selecting a different character for the other special
function.
MESSAGE
Character value out of range.
CAUSE
The character input was out of the range of characters allowed for that
function.
ACTION
Input a character within the range.
MESSAGE
File is damaged; checksum error.
CAUSE
The file has been damaged so that the checksum is no longer valid. The
utility still reads the data from the file into the work area, and when
saving the data back to the file, a correct checksum is generated.
ACTION
Press Enter again to go to the form selected. Verify the data on the screen.
310
Chapter 7
TurboIMAGE/XL V iii C 5
Workstation Configuration
MESSAGE
File is not a valid VFC file.
CAUSE
The file name specified is not a valid VFC file.
ACTION
Specify a file which is a VFC file.
MESSAGE
File is not a valid terminal type file.
CAUSE
The file specified is not a valid terminal-type file.
ACTION
Specify a file that is a valid terminal-type file.
MESSAGE
Invalid file name.
CAUSE
The file name specified does not meet the requirements for an HP3000 file
name. It might be because the name starts with a non-alphabetic
character or contains non-alphanumeric characters.
ACTION
Enter a valid file name.
MESSAGE
File converted to MPE XL format.
CAUSE
Informational message only.
ACTION
An action is not required.
MESSAGE
File System Errors.
CAUSE
If a file system error occurred when attempting to open the file specified,
the file system error message is displayed in the error window.
ACTION
An action is not required.
MESSAGE
Invalid file option.
CAUSE
The file option given was not C, M, or V.
ACTION
Enter a valid file option.
MESSAGE
Invalid form identifier.
CAUSE
The letter entered in the form specifier field is not one of the known form
identifiers.
ACTION
Enter one of the listed form identifiers in the field.
MESSAGE
Invalid number.
CAUSE
You attempted to input a character in numerical format, but the number
was not an integer.
ACTION
Input a valid number.
MESSAGE
Maximum number of nn characters allowed is nn.
CAUSE
You have input more than the maximum allowed number of characters for
the specified function.
ACTION
Reduce the number to less than or equal to the maximum specified in the
error message.
MESSAGE
Missing character.
CAUSE
In the input of a string, the program is expecting another character, but
Chapter 7
311
TurboIMAGE/XL V iii C 5
Workstation Configuration
none follows. This is most likely caused by two commas in a row, or a
comma at the end of a line without the ampersand.
ACTION
Remove the extra comma, or insert the appropriate character.
MESSAGE
Modification of data is not allowed.
CAUSE
Enter was pressed after choosing the View file option. In View mode,
modification of data is not allowed.
ACTION
Use only the soft keys.
MESSAGE
MPE/V termtype file; use Form X to convert to MPE XL
format.
CAUSE
The terminal-type file name entered in the Terminal Type File Name field
is in MPE V format.
ACTION
Convert the MPE V termtype file to MPE/iX format.
MESSAGE
Response must be in the range from nn to nn.
CAUSE
The field contains a value that is not within the range specified.
ACTION
Enter a value within the correct range.
MESSAGE
Response must be None, Line, Page, or Both.
CAUSE
The field requires N, L, P, or B as a valid response, but a different value
was input.
ACTION
Change the value to N, L, P, or B.
MESSAGE
Response must be ON or OFF.
CAUSE
The only valid entries for this field are ON and OFF, but some other value
was entered.
ACTION
Change the value to either ON or OFF.
MESSAGE
Response must be YES or NO.
CAUSE
The field requires either a Y or an N as a valid response, but a different
value was input.
ACTION
Change the value to a Y or N.
MESSAGE
Termtype file is already in MPE XL format.
CAUSE
Because the terminal-type file is already in MPE/iX format, there is no
reason to convert it to MPE/iX format.
ACTION
An action is not required.
MESSAGE
The field can only contain digits.
CAUSE
The field is designed to accept only positive integers. The value entered
contains characters other than digits.
ACTION
Enter a positive integer in the field.
MESSAGE
The required field is empty.
312
Chapter 7
TurboIMAGE/XL V iii C 5
Workstation Configuration
CAUSE
The specified field requires a value and nothing was entered.
ACTION
Enter a value in the field.
MESSAGE
There is no next form.
CAUSE
NEXT FORM was pressed when at the last form menu, and there is no next
form.
ACTION
Do not press NEXT FORM at the last form.
MESSAGE
There is no previous form.
CAUSE
PREV FORM was pressed when at the Main Menu, or when the VFC option
was selected (RUN TTUTIL.PUB.SYS). There is no previous form.
ACTION
Do not press PREV FORM at the Main Menu, or when the VFC option is
selected.
MESSAGE
There is no VFC defined.
CAUSE
You specified V for the View file option and to go to the VFC Menu, but this
terminal-type file does not have a VFC file associated with it.
ACTION
Specify a different menu.
MESSAGE
This key is invalid when no file is selected.
CAUSE
The function key pressed is invalid when no file has been specified.
ACTION
Specify a file name first, or press a valid function key.
MESSAGE
This option is invalid when no terminal type is defined.
CAUSE
You used N, the Name Only option, when using the VFC entry point.
Therefore, there is no terminal-type file to store the name.
ACTION
Enter another option (C, M, V) in the VFC Head Menu.
MESSAGE
This option cannot be selected. The termtype currently
displayed is not a printer termtype file.
CAUSE
The indicated field(s) contain invalid data.
ACTION
Either erase the indicated fields or go to another screen. Enter another
option (C, M, V) in the VFC Head Menu.
MESSAGE
This option cannot be changed. The termtype currently
displayed is a Network Printer termtype file, and this
option is non-configurable for this type of file.
CAUSE
You attempted to modify a terminal-type file whose attributes cannot be
reconfigured.
ACTION
Enter the previous value for the indicated fields again, or go to another
screen. Enter another option (C, M, V) in the VFC Head Menu.
MESSAGE
Unknown character.
CAUSE
The character input does not match one of the accepted character input
formats, or the character mnemonic cannot be found in the recognized list.
Chapter 7
313
TurboIMAGE/XL V iii C 5
Workstation Configuration
ACTION
Input a valid character.
MESSAGE
Unknown character input format.
CAUSE
You attempted to input a character, but the character could not be
determined.
ACTION
Input a valid character.
MESSAGE
Unknown string input format.
CAUSE
You attempted to input a string, but the input could not be decoded.
ACTION
Enter in the correct string.
MESSAGE
User does not have write access to file.
CAUSE
You specified M, for the Modify file option, but you do not have write access
to the file. Therefore, you cannot modify it.
ACTION
Specify a different file, or use the View option.
MESSAGE
WARNING: data not saved.
CAUSE
You tried to exit or specify another file name after modifying the current
file but without saving the modifications made.
ACTION
Press SAVE DATA if you want to save the UUmodifications. If not, type
EXIT at the command line or press RETURN a second time, to perform the
desired operation.
314
Chapter 7
">