HP 3000 Manuals HP 3000 Manuals
(Subsystem 98)(Continued)
------------------------------------------------------------
820 MESSAGE Various procedures are either returning a port
description that is already free, obtaining a port
description that has already been assigned, or
accessing a port or port description pointer.
-------------------------------------------------------------
821 MESSAGE Calling CB_SHR_LOCK or CB_SHR_UNLOCK, but the
lock type is not valid.
-------------------------------------------------------------
822 MESSAGE An attempt was made to perform a CM_PENABLE when
the CM_PSDB semaphore was not owned by any process.
-------------------------------------------------------------
823 MESSAGE An attempt was made to perform a CM_PENABLE when
the CM_PSDB semaphore was owned by another process.
-------------------------------------------------------------
824 MESSAGE An attempt was made to perform a CM_PDISABLE, but
the count overflowed. The process has locked the
CM_PSDB semaphore too many times (it is a 16-bit
counter).
-------------------------------------------------------------
825 MESSAGE Unknown error while accessing CM_PSDB semaphore.
-------------------------------------------------------------
900 MESSAGE The CREATE of the HLIO SANCTUM failed.
CAUSE HLIO SANCTUM could not be created.
-------------------------------------------------------------
901 MESSAGE The CREATE of the COMPATIBILITY MODE I/O queue
failed.
CAUSE COMPATIBILITY MODE I/O queue could not be created.
-------------------------------------------------------------
902 MESSAGE The CREATE of the COMPATIBILITY MODE I/O STATE
TABLE failed.
CAUSE COMPATIBILITY MODE I/O STATE TABLE could not be
created.
-------------------------------------------------------------
903 MESSAGE The CREATE of the LOGICAL PATH TABLE failed.
CAUSE The LOGICAL PATH TABLE could not be created.
-------------------------------------------------------------
904 MESSAGE The CREATE of the DATA CHAIN TABLE failed.
CAUSE The DATA CHAIN TABLE could not be created.
-------------------------------------------------------------
905 MESSAGE The CREATE of the TERMINAL BUFFER TABLE failed.
CAUSE The TERMINAL BUFFER TABLE could not be created.
-------------------------------------------------------------
906 MESSAGE The CREATE of the I/O QUEUE TABLE failed.
CAUSE The I/O QUEUE TABLE could not be created.
-------------------------------------------------------------
907 MESSAGE The CREATE of the SERIAL WRITE TABLE failed.
CAUSE The SERIAL WRITE TABLE could not be created.
-------------------------------------------------------------
908 MESSAGE The CREATE of the DISC MESSAGE POOL failed.
CAUSE The DISC MESSAGE POOL could not be created.
-------------------------------------------------------------
909 MESSAGE The CREATE of the DEVICE MESSAGE POOL failed.
CAUSE The DEVICE MESSAGE POOL could not be created.
-------------------------------------------------------------
910 MESSAGE The CREATE of the disk FILL OBJECTS failed.
CAUSE The disk FILL OBJECTS could not be created.
-------------------------------------------------------------
911 MESSAGE The CREATE of the HLIO SURROGATES failed.
CAUSE The HLIO SURROGATES could not be created.
-------------------------------------------------------------
915 MESSAGE The function received was not implemented by this
logical device manager.
CAUSE This logical device manager did not implement the
received function.
-------------------------------------------------------------
920 MESSAGE The SERIAL WRITE MANAGER had an error in the SEND
to the I/O COMPLETION port.
CAUSE A SEND to the I/O COMPLETION port caused an error
to SERIAL WRITE MANAGER.''
-------------------------------------------------------------
921 MESSAGE The SERIAL WRITE MANAGER received an invalid
LDEV.
CAUSE An invalid LDEV was passed to the SERIAL WRITE
MANAGER.
-------------------------------------------------------------
922 MESSAGE The SERIAL WRITE MANAGER had an error in
returning the SERIAL QUEUE entry.
CAUSE Returning the SERIAL QUEUE entry caused an error to
the SERIAL WRITE MANAGER.''
-------------------------------------------------------------
923 MESSAGE The SERIAL WRITE MANAGER could not start the
request because of an error.
CAUSE The request in SERIAL WRITE MANAGER could not be
started.
-------------------------------------------------------------
924 MESSAGE The serial queue is in the wrong state for the
operation requested.
CAUSE Wrong state for requested operation.
-------------------------------------------------------------
925 MESSAGE SENDMMIO must be passed to the request at the
head of the list.
CAUSE SENDMMIO was not passed to the request at the head
of the list.
-------------------------------------------------------------
926 MESSAGE The SERIAL WRITE MANAGER received an unknown
message.
CAUSE An unknown message was passed to the SERIAL WRITE
MANAGER.
-------------------------------------------------------------
930 MESSAGE The MEMORY MANAGER surrogate HASH TABLE is full.
CAUSE Surrogate HASH TABLE in MEMORY MANAGER is full.
-------------------------------------------------------------
931 MESSAGE The MEMORY MANAGER surrogate received a
completion for an unknown RID.
CAUSE Completion received in MEMORY MANAGER for an
unknown RID.
-------------------------------------------------------------
932 MESSAGE The MEMORY MANAGER surrogate swap in FAILED.IN
-------------------------------------------------------------
933 MESSAGE The MEMORY MANAGER surrogate could not send the
completion message to the LDM.
CAUSE Completion message not sent by the MEMORY MANAGER
surrogate to the LDM.
-------------------------------------------------------------
934 MESSAGE The MEMORY MANAGER surrogate received an unknown
message.
CAUSE An unknown message was sent to the MEMORY MANAGER
surrogate.
-------------------------------------------------------------
935 MESSAGE The MEMORY MANAGER surrogate received an error
from MAKE_PRESENT_IO_BUFFER.
CAUSE MAKE_PRESENT_IO_BUFFER sent an error to the MEMORY
MANAGER surrogate.''
-------------------------------------------------------------
940 MESSAGE An error occurred, and HLIO's normal error
recovery was not enabled.
CAUSE HLIO's normal error recovery was not enabled when
an error occurred.
-------------------------------------------------------------
1001 MESSAGE The MEMORY MANAGER initialization module was
unable to allocate a table entry from an object.
-------------------------------------------------------------
1002 MESSAGE The MEMORY MANAGER initialization module was
unable to retrieve a table entry which should be in
the table's free list.
-------------------------------------------------------------
1003 MESSAGE GET_TABLE_INFO returned a bad status to the
MEMORY MANAGER initialization module when the
latter tried to access the PDIR.
-------------------------------------------------------------
1004 MESSAGE The MEMORY MANAGER initialization module received
a bad status from an attempt to validate a resident
object's access rights.
-------------------------------------------------------------
1005 MESSAGE The MEMORY MANAGER initialization module was
unable to create a required table.
-------------------------------------------------------------
1006 MESSAGE The initialization module was unable to create
the nonresident objects required by the MEMORY
MANAGER.
-------------------------------------------------------------
1007 MESSAGE The MEMORY MANAGER was unable to create the page
filler process.
-------------------------------------------------------------
1008 MESSAGE The MEMORY MANAGER was unable to activate the
page filler process.
-------------------------------------------------------------
1009 MESSAGE The MEMORY MANAGER I/O INFORMATION TABLE was out
of entries.
-------------------------------------------------------------
1010 MESSAGE The MEMORY MANAGER alias operation encountered a
bad status while trying to access the I/O
notification queue.
-------------------------------------------------------------
1011 MESSAGE The MEMORY MANAGER alias operation encountered a
bad status while trying to access the I/O
notification queue.
-------------------------------------------------------------
1012 MESSAGE The MEMORY MANAGER was unable to set TRANSACTION
MANAGEMENT post attributes correctly.
-------------------------------------------------------------
1013 MESSAGE The MEMORY MANAGEMENT semaphore for this physical
page is already locked. This should not occur in a
uni-processor environment.
-------------------------------------------------------------
1014 MESSAGE An attempt was made to set TRANSACTION MANAGEMENT
FREEZE attributes on a virtual page which was not
frozen in memory.
-------------------------------------------------------------
1015 MESSAGE The I/O completion port was the wrong port for
this process.
-------------------------------------------------------------
1016 MESSAGE The MEMORY MANAGER detected an error when it
attempted to send a message to the DISPATCHER.
-------------------------------------------------------------
1017 MESSAGE The MEMORY MANAGER detected an error when it
attempted to call NOTIFY_DISPATCHER from
MAKE_IO_BUFFER_PRESENT.
-------------------------------------------------------------
1018 MESSAGE The MEMORY MANAGER was unable to update a
physical page's NO POST count.
-------------------------------------------------------------
1019 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------
1020 MESSAGE The MEMORY MANAGER encountered an error while
trying to send a FETCH message to the DISPATCHER.
-------------------------------------------------------------
1021 MESSAGE NOTIFY_DISPATCHER returned a bad status to
SYSTEM_FETCH_REQUEST.
-------------------------------------------------------------
1022 MESSAGE An attempt was made to UNFREEZE a virtual page
which was not mapped into physical memory.
-------------------------------------------------------------
1023 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------
1024 MESSAGE The MEMORY MANAGER was unable to WRITE pages out
to disk which had been locked in the VPN cache.
-------------------------------------------------------------
1025 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------
1026 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------
1027 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------
1028 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------
1029 MESSAGE The MEMORY MANAGER was unable to access the I/O
notification port.
-------------------------------------------------------------