HP 3000 Manuals HP 3000 Manuals
(Subsystem 98) (contd.)
1466 MESSAGE While the system was booting, we were unable to
schedule the BOOT process for execution
(NOTIFY_DISPATCHER).
---------------------------------------------------------------
1467 MESSAGE While the system was booting, we were unable to
allocate space in BANK 0 for the PCB TABLE
(ALLOC_B0_SUB_OBJECT).
---------------------------------------------------------------
1468 MESSAGE While the system was booting, we were unable to
get a long pointer to the PCB TABLE (CONVERT_DST).
---------------------------------------------------------------
1469 MESSAGE While the system was booting, we were unable to
create the PCB TABLE within the PCB SUB-OBJECT
(CREATE_TABLE).
---------------------------------------------------------------
1470 MESSAGE While the system was booting, we were unable to
CREATE the PIB TABLE.
---------------------------------------------------------------
1471 MESSAGE While the system was booting, we were unable to
allocate a data segment for the PROCESS/JOB CROSS
REFERENCE TABLE (ALLOCATE_DST).
---------------------------------------------------------------
1472 MESSAGE While the system was booting, we were unable to
obtain a pointer for the PROCESS/JOB CROSS
REFERENCE TABLE (CONVERT_DST).
---------------------------------------------------------------
1473 MESSAGE While the system was booting, we were unable to
create the PROCESS ID LIST (CREATE_TABLE).
---------------------------------------------------------------
1474 MESSAGE While the system was booting, we were unable to
create the PROTECT ID LIST (CREATE_TABLE).
---------------------------------------------------------------
1475 MESSAGE While the system was booting, we were unable to
create a virtual space domain for the temporary PIB
and PIBX TABLES (CREATE_VIRTUAL_SPACE_DOMAIN).
---------------------------------------------------------------
1476 MESSAGE While the system was booting, we were unable to
create a temporary PIB TABLE (CREATE_OBJECT).
---------------------------------------------------------------
1477 MESSAGE While the system was booting, we were unable to
create a temporary PIBX TABLE (CREATE_TABLE).
---------------------------------------------------------------
1478 MESSAGE While the system was booting, we were unable to
build PROGENS CM STACK (BUILD_CM_STACK).
---------------------------------------------------------------
1479 MESSAGE While the program was booting, we were unable to
obtain a pointer to PROGENS STACK (CONVERT_DST).
---------------------------------------------------------------
1480 MESSAGE While the system was booting, we were unable to
determine the size of the PROGENS STACK
(GET_DST_SIZE).
---------------------------------------------------------------
1481 MESSAGE While the system was booting, we were unable to
set the size of the PROGENS STACK (MAX_DST_SIZE).
---------------------------------------------------------------
1482 MESSAGE An attempt is being made to set a process's
critical depth count to less than zero.
---------------------------------------------------------------
1483 MESSAGE An attempt is being made to set a process's
system code depth to less than zero.
---------------------------------------------------------------
1484 MESSAGE The value of the OLDSTATE parameter passed to
RESETCRITICAL is invalid.
---------------------------------------------------------------
1485 MESSAGE The recover block in a PROCESS MANAGEMENT
intrinsic encountered an unexpected escape code.
---------------------------------------------------------------
1486 MESSAGE A trap occurred in the operating system during
system boot.
---------------------------------------------------------------
1487 MESSAGE A trap occurred while a process was terminating.
---------------------------------------------------------------
1501 MESSAGE The procedure PROCESS_SYSTEM_FETCH_PAGES_MSG
caused bad status from FETCH_PAGES.
---------------------------------------------------------------
1502 MESSAGE The procedure PROCESS_FETCH_IO_PAGES_MSG caused
bad status from SWAP_IN.
---------------------------------------------------------------
1503 MESSAGE The procedure DISP_TIMER_SERVER caused quantum to
expire; NOTIFY_DISPATCHER returned bad status.
---------------------------------------------------------------
1504 MESSAGE The procedure AWAKEN_PROCESS caused unexpected
BLOCKED_REASON.
---------------------------------------------------------------
1505 MESSAGE The procedure BLOCK_CURRENT_PROCESS caused
BLOCK_EVENT in DSP_MEMORY_WAIT; bad build.
---------------------------------------------------------------
1506 MESSAGE The procedure BLOCK_CURRENT_PROCESS caused the
request to block on memory WAIT.
---------------------------------------------------------------
1507 MESSAGE The procedure NOTIFY_DISPATCHER means NOTIFY
DISPATCHER is called with nil PIN.
---------------------------------------------------------------
1508 MESSAGE The procedure NOTIFY_DISPATCHER is unable to set
the watchdog timer to prevent runaway CPU usage;
unexpected status from RESET_TIMER.
---------------------------------------------------------------
1509 MESSAGE The procedure SET_PROC_SCHEDULING_CLASS caused
bad status from NOTIFY_DISPATCHER.
---------------------------------------------------------------
1510 MESSAGE The procedure FORMAT_DISPATCHER_GLOBALS can not
get a timer entry for the timeslice watchdog; bad
status from GET_TIMER.
---------------------------------------------------------------
1511 MESSAGE The procedure X_INITIALIZE_DISPATCHER can not
create the dispatcher timer port; error from
CREATE_PORT.
---------------------------------------------------------------
1512 MESSAGE The procedure SWAP_IN_PROCESS (initiate_swap_in)
caused an unknown status from SWAP_IN.
---------------------------------------------------------------
1513 MESSAGE Processes are ready to be launched but the
DISPATCHER is missing them.
---------------------------------------------------------------
1514 MESSAGE The procedure PROCESS_DISPATCHER_MSGS can not
receive the dispatcher message to the process;
unknown status from RECEIVE_MSG.
---------------------------------------------------------------
1515 MESSAGE The procedure EXAMINE_ACTIVE_PROCESS caused a
long waited process on the dispatcher queue.
---------------------------------------------------------------
1516 MESSAGE NOTIFY_DISPATCHER requests to change priority of
a dead process.
CAUSE An attempt was made to change priority of a dead
process.
---------------------------------------------------------------
1517 MESSAGE Unknown request to NOTIFY_DISPATCHER.
CAUSE An unknown DISPATCH request has been sent to
NOTIFY_DISPATCHER.
---------------------------------------------------------------
1701 MESSAGE UPDATE_SYSTEM_QUAD_ALLOCATION_MAP - The counters
which hold the number of units in the free or
allocated state went below zero.
---------------------------------------------------------------
1702 MESSAGE ALLOCATE_SYS_QUAD_SPACE - The call to UPDATE THE
ALLOCATION MAP returned a bad status.
---------------------------------------------------------------
1703 MESSAGE DEALLOCATE_SUB_SR6_SR7_SPACE - The call to UPDATE
ALLOCATION MAP returned a bad status.
---------------------------------------------------------------
1704 MESSAGE DEALLOCATE_SUB_SR6_SR7 - The quad of the address
to DEALLOCATE was not SR6 or SR7.
---------------------------------------------------------------
1705 MESSAGE INIT_ALLOCATION-INFO of INIT_VIRTUAL
SPACE_MANAGEMENT - An invalid status was returned
from the ALLOCATION routine when attempting to mark
the space assigned to the BOOT objects allocated.
---------------------------------------------------------------
1706 MESSAGE CREATE_VSM_OBJECT of INIT VIRTUAL_SPACE
MANAGEMENT - An invalid status was returned from
the ALLOCATION routine when attempting to allocate
a space for a VSM object.
---------------------------------------------------------------
1707 MESSAGE INIT_ALLOCATION_ INFO of
INIT_VIRTUAL_SPACE_MANAGEMENT - An invalid status
was returned when calling the ALLOCATION MAP UPDATE
routine to mark the unavailable space at the end of
the quad as allocated.
---------------------------------------------------------------
1708 MESSAGE DEL_FROM_LOCALITY_TABLE - The entry requested to
be deleted from the INDIRECT LOCALITY TABLE was not
found.
---------------------------------------------------------------
1709 MESSAGE VSM_LOAD_CODE_FILE - This code file has already
been loaded as a single SOM file. The maximum
number of SOMs specified in the previous load was
1.
---------------------------------------------------------------
1710 MESSAGE VSM_LOAD_CODE_FILE - The object for this file was
created with variable access rights, and the loader
specified single access rights in the parameters to
this procedure.
---------------------------------------------------------------
1711 MESSAGE VSM_UNLOAD_CODE_FILE - No object was found which
contains the pointer to the file to unload.
---------------------------------------------------------------
1712 MESSAGE VSM_UNLOAD_CODE_FILE - The specified code file
was not previously loaded using VSM_LOAD_CODE_FILE.
---------------------------------------------------------------
1713 MESSAGE VSM_UNLOAD_CODE_FILE - There was an error status
returned when the INIT POINTER (LOCALITY) TABLE was
attempted to be locked into the VPN cache.
---------------------------------------------------------------
1714 MESSAGE VSM_UNLOAD_CODE_FILE - An error was returned from
the RELEASE_OBJECT call when attempting to release
the INDIRECT LOCALITY TABLE.
---------------------------------------------------------------
1715 MESSAGE PAGE_FLT_LOCK_IN_VPN_CACHE - The recover block
for this procedure was unexpectedly entered.
---------------------------------------------------------------
1716 MESSAGE INIT_2_VIRTUAL_SPACE MANAGEMENT - An error
occurred when making the VS allocation information
object swappable.
---------------------------------------------------------------
1717 MESSAGE UNLOCK_RANGE_FROM_CACHE - The VPN and length to
unlock was outside of the bounds of the cache entry
pointer that was passed in.
---------------------------------------------------------------
1722 MESSAGE TRANSLATE_VSM_TABLE_ERROR - Received an error
from TABLE MANAGEMENT that is not a recoverable
error. The table may be corrupted.
---------------------------------------------------------------
1723 MESSAGE TRANSLATE_VSM_TABLE_ERROR - Received an error
from TABLE MANAGEMENT that is not an error expected
for the particular table, such as no secondary
storage for a resident table.
---------------------------------------------------------------
1724 MESSAGE RELEASE_VSM_TABLE_ENTRY - An error occurred
releasing a table entry; table may be corrupt.
---------------------------------------------------------------