System Aborts

Ran out of memory before PAGE and HASH TABLES were properly initialized.

Ran out of physical memory; address is outside the range of the machine.

Could not create the table header for the PDIR and/or the PDIR could not set up as a standard system table.

Failure occurred when calling the CREATE_TABLE to create the PDIR header.

Could not free up entries in the PDIR corresponding to memory below the PME during PDIR initialization.

Failure occurred when calling RELEASE_TABLE_ENTRY to release all PDIR TABLE entries.

Could not find a free entry in memory in the PDIR using the GENESIS MEMORY MANAGER.

Failure occurred when calling GET_TABLE_ENTRY to find a free entry in memory in the PDIR.

Could not release an entry in the PDIR using the GENESIS MEMORY MANAGER during a GET_MEMORY call.

Failure occurred when calling the RELEASE_TABLE_ENTRY to return the table entry corresponding to the given page number to the free pool.

Could not find a page with the proper alignment for the memory request for a virtual address that has not already been assigned a page.

Page alignment incorrect.

The procedure could not find a set of contiguous pages of the correct alignment (for example, not enough memory left).

Set of contiguous with the correct alignment are not available.

The procedure could not find a free page with the correct alignment using the GENESIS MEMORY MANAGER.

Unable to find a free page correctly aligned.

A contiguous assignment request for memory on a virtual range could not be honored when some area of the range already had pages assigned to it.

Duplicate memory assignment range request.

Could not release an entry in the PDIR using the GENESIS MEMORY MANAGER during a RELEASE_MEMORY call.

Failed when calling RELEASE_TABLE_ENTRY for releasing page from PDIR TABLE.

Could not initialize the resident PORTS facility.

Failed when calling INIT_RES_PORT_FACILITY to initialize ports.

Could not initialize the TIMERS facility.

Failed when calling INITIALIZE_TIMERS to initialize timers facility.

Could not configure primary I/O devices.

Failed when calling CONFIGURE_FOR_GENESIS to configure the system disk and console.

PRIMIO device not configured.

Low Level I/O returned error when configuring device.

CONFIGURE_HLIO_DEVICE configuration not done.

High Level I/O returned error when configuring device.

An error occurred in IO_INIT.

Low Level I/O returned error when setting up primary I/O environment.

An error occurred in CONFIGURE_LPT.

High Level I/O returned an error when setting up primary I/O environment.

An error occurred in CONFIGURE_DEVICE (halt; not system abort).

Problem occurred configuring console (will appear in front panel message - halt).

An error occurred in CONFIGURE_DEVICE.

Problem occurred configuring device other than the console.

SENDIO to read from SYSDISC failed.

I/O code returned a disk error.

Call your support representative. The dump may be restarted.

RENDEZVOUSIO to read from SYSDISC failed.

I/O returned a disk error.

Call your support representative. The dump may be restarted.

SENDIO to READ from disk failed.

I/O code returned a disk error.

Call your support representative. The dump may be restarted.

REWIND_TAPE_ONLINE of dump device failed.

I/O code returned a tape error.

Call your support representative. The dump may be restarted.

RENDEZVOUSIO returned error on rewind tape online.

I/O code returned a tape error.

Call your support representative. The dump may be restarted.

REWIND_TAPE of dump device failed.

I/O code returned a tape error.

Call your support representative. A dump may be restarted. If the failure occurred on the final, or only reel of tape, the current dump may be valid.

RENDEZVOUSIO returned error on REWIND_TAPE.

I/O code returned a tape error.

Call your support representative. The dump may be restarted. If the failure occurred on the final, or only reel of tape, the current dump may be valid.

FORCE_WRITE end of file to dump device failed.

I/O code returned a tape error.

Call your support representative. The dump may be restarted.

SENDIO to FORCE_WRITE to dump device failed.

I/O code returned a tape error.

Call your support representative. The dump may be restarted.

WRITE end of file to dump device failed.

I/O code returned a tape error.

Call your support representative. The dump may be restarted.

SENDIO to READ from dump device failed.

A non-recoverable tape READ error occurred.

Call your support representative. The dump may be restarted.

SENDIO to WRITE to dump device failed.

A non-recoverable tape WRITE error occurred.

SENDIO for tape GET_DEVICE_STATUS failed.

I/O code returned error trying to get tape device status; did not occur during tape READ or WRITE.

Call your support representative. The dump may be restarted.

The procedure BUILD_DIAGMON_PORT failed to build the diagnostic monitor port.

Failed when calling BUILD_DIAGMON_PORT to build diagnostic monitor port.

The procedure LOAD_SYSTEM_SL failed to load the system SL.

System SL was not loaded by the LOAD_SYSTEM_SL procedure.

The procedure INITIALIZE_DISPATCHER failed to initialize the DISPATCHER.

DISPATCHER was not initialized.

The procedure SM_CREATE_HASH_TBL failed to create the HASH TABLE.

HASH TABLE was not created.

The procedure READ_HPE_VOL_POINTERS failed to READ from LDEV 1.

Procedure could not be read from LDEV 1.

The procedure READ_HPE_VOL_INFO_UFID failed to READ the UFID from LDEV 1.

The UFID could not be read.

The procedure READ_HPE_VOL_FREE_ADDR failed to READ the first free address from LDEV 1.

The first free address could not be read.

The procedure GET_HPE_DISC_SIZE_PAGE is unable to access LDEV 1.

LDEV 1 could not be accessed.

The procedure START_VOLUME_MGT failed to START VOLUME MANAGEMENT.

VOLUME MANAGEMENT was not started with the required procedure.

The procedure GET_SYSLIB_UFID is unable to GET the system library UFID.

The system library UFID could not be accessed.

The procedure MAKE_OBJECT_SWAPPABLE is unable to MAKE SXRT swappable.

SXRT is not swappable.

The procedure MAKE_OBJECT_SWAPPABLE is unable to MAKE LST component swappable.

LST component is not swappable.

The feature ALTER_OBJECT_SIZE failed to INCREASE the SXRT object size.

The SXRT objective could not be increased.

The feature LOAD_NON_RES_SYSTEM failed to LOAD the nonresident system.

The nonresident system could not be loaded.

The procedure INIT_NONRES_PORT_FACILITY failed to initialize the nonresident port facility.

The nonresident port facility was not initialized.

The procedure READ_HPE_VOL_COLDL_ID failed to READ the cold load ID from LDEV 1.

The cold load ID was not read from LDEV 1.

The procedure WRITE_HPE_VOL_COLDL_ID failed to WRITE the cold load ID from LDEV 1.

The cold load ID was not written from LDEV 1.

The procedure FS_INITIALIZE_FILE_SYSTEM failed to initialize the file system.

The file system was not initialized.

The procedure FS_PROC_INIT failed to initialize the PROCESS information block extension area.

The PROCESS information block extension area was not initialized.

The procedure FAKE_LOGON failed to OPEN the file system directories (PLFDs).

The file system directories (PLFDs) were not opened.

The procedure INIT_LOADER failed to initialize the LOADER.

LOADER was not initialized.

The procedure ADD_CLASS is unable to SWITCH to CM.

ADD_CLASS could not SWITCH to CM.

The procedure ADD_DEVICE is unable to SWITCH to CM.

ADD_DEVICE could not SWITCH to CM.

The procedure ADD_DEVICE is unable to add the system disk (LDEV 1) through ADD_DEVICE for CM.

The system disk could not be added through ADD_DEVICE for CM.

The procedure ADD_DEVICE is unable to ADD the system console through ADD_DEVICE for CM.

The system console could not be added through ADD_DEVICE for CM.

The procedure ADD_VIRTUAL_LDEVS is unable to SWITCH to CM.

ADD_VIRTUAL_DEVICE could not be switched to CM.

The procedure CLEAN_CM_DEVICE_TABLES is unable to SWITCH to CM.

CLEAN_CM_DEVICE_TABLES could not SWITCH to CM.

The procedure INIT_CM_DEVICE_TABLES is unable to SWITCH to CM.

INIT_CM_DEVICE could not SWITCH to CM.

The procedure IO_INIT failed to initialize the low level I/O system.

The low level I/O system was not initialized.

Activation of JOBMAIN process failed.

Activation of SESSIONMAIN process failed.

Creation of JOBMAIN process failed.

Creation of JOBMAIN_PORT failed.

Creation of JOBQUEUE_PORT failed.

Creation of SESSIONMAIN process failed.

Creation of SESSIONMAIN_PORT process failed.

Opening JOBMAIN_PORT process failed.

Opening JOBQUE_PORT process failed.

Opening SESSIONMAIN_PORT process failed.

The information and subsystem escape is passed as the second parameter.

Had an unexpected escape from the operating system to the SESSIONMAIN outerblock. The information and subsystem that escaped are passed to the system abort as the second parameter.

Had an unexpected escape from the operating system to the JSMAIN outerblock.

Port status is passed as the second parameter.

Port status is passed as the second parameter.

Port status is passed as the second parameter.

Management failed to post data from memory to
disk.

DSM attempted to post 16 pages with the MAKE_ROC option after a sequential read. The exact conditions that caused an error to be returned are unknown to the DSM.

During a file open, the GUFD semaphore could not be initialized.

A call to CB_INIT returned bad status.

During a file open, the FLOCK semaphore could not be initialized.

A call to CM_INIT returned bad status.

During a file open, the FOPEN semaphore could not be initialized.

A call to CB_INIT returned bad status.

Prefetch of needed data for a READ/WRITE request could not be made.

VSM reported address or range given to be invalid or out of bounds.

Attempted to CLOSE a file which is not OPEN.

File system lock algorithm failed.

The procedure could not open the system library (the NL).

Boot image or LABEL TABLE is corrupted.

Take a system dump and reinstall if necessary.

CREATE_OBJECT failed to create the SM KSO.

The procedure was unable to obtain the HASH TABLE lock.

CB_INIT returned bad status trying to initialize the UFID HASH TABLE semaphore; start image is bad.

Recreate the boot image. Take a system dump and call your support representative.

The procedure was unable to obtain the LRU lock.

CB_INIT returned bad status trying to initialize the LRV semaphore; start image is bad.

Recreate the boot image. Take a system dump and call your support representative.

A pascal recover block was entered unexpectedly.

Cause is usually associated with software or hardware traps which have been tripped because of invalid addresses, invalid access rights, or arithmetic underflow/overflow.

Offset of entry is not within the LABEL TABLE.

LABEL TABLE has been corrupted.

The entry referenced is not an extent block type.

LABEL TABLE has been corrupted.

Extent block does not point to the correct PARENT label.

LABEL TABLE has been corrupted.

Two file offsets in the extent block are the same.

LABEL TABLE has been corrupted.

An extent block that is expected to be a free entry is not free.

LABEL TABLE has been corrupted.

A POST of a LABEL TABLE entry failed.

MEMORY MANAGER failed to port a LABEL TABLE entry.

Reboot the system, and run FSCHECK to see if a reinstall of the system is necessary.

The number of EXTENTS in the block exceeds the maximum allowable.

LABEL TABLE has been corrupted.

The file system encountered a trap.

An operating system software error caused a trap.

The file system encountered an unexpected ESCAPE.

An internal operating system module called ESCAPE unexpectedly.

The file system was unable to release a resource.

Due to an operating system software error, the file system was not able to release one or more system resources.

An error was encountered while creating FILE SYSTEM GLOBAL AREA during file system initialization.

An error was encountered while creating GPDP TABLE during file system initialization.

An error was encountered while creating FILE OPEN COUNT TABLE during file system initialization.

An error was encountered while creating BASIC IPC (BIPC) TIMER server ports during file system initialization.

An error was encountered while initializing STORE/RESTORE LATENCY TABLE during file system initialization.

An error occurred in the file system during process termination.

The file system detected an operating system software error while cleaning up file system data structures during process termination.

An internal STORAGE MANAGEMENT error was encountered while attempting to CLOSE (FCLOSE) a file.

Due to an operating system software error STORAGE MANAGEMENT was not able to CLOSE the file.

FCLOSE was not able to delete a file's access rights entry from the FILE ACCESS RIGHTS TABLE.

A file system error occurred during file OPEN or the FILE ACCESS RIGHTS TABLE has been corrupted.

An error was encountered while attempting to return an allocated GPDP to the free list while trying to CLOSE (FCLOSE) a file.

The GDPD TABLE has been corrupted.

The file system detected a counter underflow in a GUFD.

The GUFD has been corrupted.

The FILE ACCESS RIGHTS TABLE counters are inconsistent.

The FILE ACCESS RIGHTS TABLE has been corrupted.

The procedure can not decrement the PDISABLE count; it is unexpectedly zero.

The CB was unlocked by a PIN different from the PIN that locked it.

The VECTOR TABLE in the CB is corrupt.

Failure in creating File IO State Tables

System failed to create one of the File IO State Tables during system initialization.

Contact your Hewlett-Packard Representative.

Failure in creating one of the local socket tables.

System failed to create one of the local socket tables during system initialization.

Contact your Hewlett-Packard Representative.

Various port primitive procedures have experienced an unexpected escape, probably due to a trap while in system code.

The procedure REL_PORT_FREEZE_DESC can not release freeze descriptor entry; bad status from RELEASE_TABLE_ENTRY.

The procedure RELEASE_PORT_OBJECT can not release port object; unexpected status from RELEASE_OBJECT.

The procedure RETURN_PORT_DESC can not release port descriptor; bad status from RELEASE_TABLE_ENTRY.

There are waiters on the demolished message pool.

The procedure DEMOLISH_POOL can not delete the pool's directory entry from the port directory; bad status from STDELID.

The procedure DEMOLISH_PORT can not access the delayed port purger process.

The procedure DEMOLISH_PORT detected an error in deleting delayed messages.

The procedure DEMOLISH_PORT can not send DEMOLISH message to PFP port.

There are waiters on the demolished port.

The procedures DEMOLISH_PORT, PFP_NAME_TO_PORT_NUM, and OPEN_PORT can not lock the port directory; bad status from STLOCK.

The procedure DEMOLISH_PORT can not delete the port directory entry; bad status from STDELID.

The procedures DEMOLISH_PORT and UNLOCK_DIRECTORY can not unlock the port directory; bad status from STUNLOCK.

At process termination time (DEMOLISH_PORT), an error from TABLE MANAGEMENT occurred when releasing the standard ports entry to the table.

The procedure DELETE_PORT_BASE can not release the semaphore port; bad status from RECEIVE_FROM_SEMAPHORE_PORT.

The procedure DELETE_PORT_ACCESS is still holding the semaphore port after release.

The procedure LOSE_PORT can not flush waiting process from the specified wait queue of the semaphore port being purged; bad status from REPLY_TO_WAITER.

The procedure CHANGE_OWNERSHIP corrupted the port ownership list; port's ownership information inconsistent with PIB's.

The procedure CHANGE_OWNERSHIP detected a corrupted port ownership list; port's ownership information does not agree with PIB's.

Various procedures caused an unexpected status from PREP_PORT.

The procedure DEC_PFP_COUNT detected an error accessing PFP upon CREATE_PORT error; can not decrement PFP's use count.

The procedure LOCATE_PORT_ENTRY can not read port directory entry; bad status from STREADKEY.

The procedures FAST_RELEASE_MSG_FRAME, SEND_MSG,
REL_MSG_FRAME,DO_SERVER(SCHEDULE_SERVER), and RELEASE_FRAME cannot release message frame; bad status from RELEASE_TABLE_ENTRY.

The procedures FAST_CONTINUE_SERVER_IN_PFP and FAST_EXECUTE_SERVER_IN_PFP can not send message to PFP port.

There is a problem with the message frame in the GPO cache.

The port's server caused an unexpected escape.

The procedure INTERNAL_SEND can not get message frame for internal send.

The procedure INTERNAL_SEND can not send to internal facility port; bad status from SEND_MSG.

The PORT FACILITY PROCESS is not available yet.

The procedure DELAYED_AWAKE_PROCESS can not send the delayed awake message to PFP.

The decrement of the port's total freeze count causes it to become negative.

The port is already totally frozen, but partial freeze failed; no reason for this to happen.

The procedure INITIATE_UNBLOCKED_MAKE_PRESENT (2) can not get message frame for make present port; bad status from GET_MSG_FRAME.

The procedures INITIATE_UNBLOCKED_MAKE_PRESENT and PORT_MAKE_PRES can not
cleanup the message on the make present port and give it back to the message pool; bad status from RETRIEVE_MSG.

The procedure BLOCKED_MAKE_PRESENT can not get FREEZE reply from MEMORY MANAGER for MAKE_PRESENT; bad status from EXTEND_RECEIVE.

The procedure BLOCKED_MAKE_PRESENT detected a bad FREEZE reply message from MEMORY MANAGER.

The FREEZE count is zero; can not hold FREEZE since port is not totally frozen.

The FREEZE count is zero; cannot release FREEZE because the port must be totally frozen when called.

The procedure CHECK_PORT_DESCRIPTOR detected an unknown port type in the port descriptor.

The procedure ENABLE_TIMEOUT can not alter the standard message port for time out; bad status from CHANGE_SUBQUEUE.

The procedure ENABLE_TIMEOUT can not get timer for time out; bad status from GET_TIMER.

The procedure DISABLE_TIMEOUT can not access the standard message port for time out; bad status from PORT_INFO.

The procedure DISABLE_TIMEOUT can not release timer; unexpected status from RELEASE_TIMER.

The timer has popped. Expected a reply message, but RECEIVE failed; bad status from EXTEND_RECEIVE.

The procedure INCREASE_PROCESS_PRIORITY can not hold or increase process's priority; bad status from NOTIFY_DISPATCHER.

The procedure BOOST_SERVER_PRIORITY can not boost server's priority; server's PIN is nil according to the SCB.

The procedure DECREASE_CALLERS_PRIORITY can not decrease caller's priority; bad status from NOTIFY_DISPATCHER.

The procedure DROP_SERVER_PRIORITY can not drop server's priority because server has nil PIN.

The caller wanted to WAIT, but can not WAIT while program is on the ICS.

The procedure INTERRUPT_TARGET_PROCESS can not AWAKE process blocked on port WAIT; bad status from NOTIFY_DISPATCHER.

The system is trying to IMPEDE the process by waiting for the unimpede message on the impede subqueue of the process standard message port; SEND_MSG failed.

The system is trying to UNIMPEDE the process by sending a wakeup message to its standard message port, but SEND_MSG failed.

The procedure CLEAR_WWS can not CLEAR the wake up waiting switch; bad status from PORT_CONTROL.

Unexpected status was received from IPC_WAIT_PROCESS.

Unexpected status was received from IPC_AWAKE_PROCESS.

The procedure DELAYED_SEND can not perform the actual delayed send; bad status from EXTEND_SEND or INSERT_MSG.

Received unexpected status from EXTEND_RECEIVE while receiving the delayed purge message.

An unrecoverable error occurred during PORT_PURGE_PROCESS.

An error occurred while initializing PFP.

Bad status occurred from RECEIVE_MSG in PORT_FACILITY_PROCESS.

Received an unexpected PFP message type.

Received bad status from internal operation.

Received message from an invalid subqueue on the MAKE PRESENT port.

Requested MEMORY MANAGEMENT to MAKE PRESENT a port entity; MEMORY MANAGEMENT'S reply indicates the MAKE PRESENT was unsuccessful.

Received unexpected message type in MAKE PRESENT message.

The procedure GET_SHR_OWNER_ENTRY can not get free entry from the shared owner list pool; shared owner list exhausted.

The processes WAIT_FOR_RESOURCE and WAKE_UP_HEAD_WAITER can not block process to wait for semaphore; bad status from NOTIFY_DISPATCHER while blocking process.

Either the dispatcher or interrupts were disabled after awaking from a CB WAIT.

The owner of the semaphore being blocked is NIL_PIN.

Various procedures caused the system to abort in an attempt to access unknown semaphore type.

The procedure GIVE_TO_NEXT_WAITERS can not give ownership of the semaphore to waiter; bad status from NOTIFY_DISPATCHER while unblocking process.

The procedures CB_SHR_LOCK and CB_SHR_UNLOCK caused a system abort because use of sharable lock while on ICS is not allowed.

The procedures CB_SHR_UNLOCK and CB_FAILER caused a system abort because the caller is not the owner of the semaphore and can not unlock it.

The procedure CB_FAILER caused a system abort because multiple lock of the standard semaphore is not allowed.

The procedure CB_FAILER resulted in an unconditional lock failing while on the ICS.

The procedure CB_FAILER detected an attempt to unlock an unowned semaphore.

The procedure CB_FAILER caused a system abort in an attempt to unlock an unowned semaphore on the ICS.

The procedure CB_FAILER caused a system abort because access of this semaphore type is not supported.

The procedure CB_FAILER caused a system abort because the semaphore access procedure is not allowed on the ICS.

The procedure CB_FAILER caused an unknown error while accessing the semaphore.

The procedure SEM_INIT resulted in bad status from CB_INIT.

The CM pseudo count is less than zero.

The procedure CM_PSDB_CLEAR resulted in bug catcher, clearing PSDB count; not blocking on port WAIT.

The procedure GET_POOL_ITEM can not access message pool table header; bad status from GET_TABLE_INFO.

The procedure FLUSH_SEM_WAIT_QUEUE can not flush all waiting processes from the semaphore's wait queue; bad status from REPLY_TO_WAITER.

The procedure CREATE_STD_PFP_PORTS caused an unexpected escape; creation of standard PFP port was unsuccessful.

The procedure INIT_RES_PORT_FACILITY can not initialize INTERRUPT or MAKE_PRESENT semaphore for global port object.

The procedure can not allocate port descriptor for the known global ports; bad
status from MAKE_GLOBAL_DESC.

Initialization of the resident port facility failed due to an unexpected escape from the procedure.

The procedure can not create the port directory object; bad status received from CREATE_OBJECT.

The procedure can not create HPIMAGE port; bad status received from CREATE_PORT.

The procedure INIT_NONRES_PORT_FACILITY caused a system abort because initialization of a non-resident port facility failed, causing an unexpected escape from the procedure.

The procedure CREATE_PORT_PROCESS caused a system abort because creation of standard port process failed, causing an unexpected escape from the procedure.

The procedure INITIALIZE_SEMAPHORES can not initialize CM PSDB semaphore.

The procedure INITIALIZE_SEMAPHORES can not initialize the COMPARE and SWAP semaphore for the database.

The procedure INITIALIZE_SEMAPHORES can not create the shared semaphore owner list.

The procedures CHECK_PEND_LEVEL and GET_HIGHEST_PEND_LEVEL can not access the process interrupt port; bad status from PORT_INFO.

The procedure DELETE_INT_MSG can not return the message frame to PI port's free pool; bad status from RETRIEVE_MSG.

The procedure CHANGE_INT_LEVEL can not change the allowable process interrupt levels for this process; bad status from CHANGE_SUBQUEUE.

Various procedures can not notify the dispatcher so that we will re-enter PI later; bad status from NOTIFY_DISPATCHER.

The procedure GET_INTERRUPT_MSG can not obtain the next interrupt message, yet port is not empty; unexpected status from RETRIEVE_MSG.

The procedure QUEUE_INTERRUPT_message can not queue interrupt message from the process' standard PI port; bad status from SEND_MSG.

The procedure WAIT_FOR_ACTIVE_PORT can not WAIT the process; bad status from NOTIFY_DISPATCHER.

The procedure DEQUEUE_MSG caused a system abort in an attempt to take the message from an empty subqueue.

The procedure OBTAIN_MSG caused a system abort when trying to get the message from a non-message port.

The procedure WAIT_UP_WAITER can not wake up the process that is waiting on this semaphore port.

The procedure RECEIVE_FROM_SEMAPHORE_PORT detected that the semaphore port's number of free messages is greater than the maximum number of messages.

The procedure RECEIVE_FROMSEMAPHORE_PORT detected that the semaphore owner's queue is empty; semaphore is not on its owner's list.

The procedure MOVE_MSG detected an error in recover; unable to queue the message from back to its original position; unexpected escape from QUE_MSG.

The procedure GET_HIGHEST_PRIORITY_PORT detected an unexpected interrupt server queue; can not find next eligible queued ICS port.

The procedure SCHEDULE_SERVER detected an error scheduling procedure server, causing an unexpected escape.

The procedure WAKE_UP_PROCESS_SERVER can not process interrupt the process server; bad status from CAUSE_PROCESS_INTERRUPT.

The procedure WAKE_UP_PROCESS_SERVER can not AWAKE the process server that is waiting for a message; bad status from NOTIFY_DISPATCHER.

The procedure RELEASE_WAIT_ENTRY can not return WAIT queue entry to the free list; bad status from RELEASE_TABLE_ENTRY.

The procedure PUT_WAIT_QUEUE can not put calling process on the wait queue; illegal to do so while on the ICS.

The procedures PUT_WAIT_QUEUE and REPLY_TO_WAITER detect that the wait queue's semaphore must be locked by the caller upon entry of this procedure.

The procedure PUT_WAIT_QUEUE can not get a free wait queue entry; bad status from GET_TABLE ENTRY.

The procedure WAIT_FOR_RESOURCE detected that interrupts are disabled when trying to block the process for a control block.

The procedure WAIT_FOR_ACTIVE_PORT detected that interrupts are disabled when trying to block a process on the port wait.

The procedure WAIT_FOR_ACTIVE_PORT detected that either the dispatcher was disabled, or interrupts are off when awaken from an IPC WAIT.

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.

Calling CB_SHR_LOCK or CB_SHR_UNLOCK, but the lock type is not valid.

An attempt was made to perform a CM_PENABLE when the CM_PSDB semaphore was not owned by any process.

An attempt was made to perform a CM_PENABLE when the CM_PSDB semaphore was owned by another process.

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).

Unknown error while accessing CM_PSDB semaphore.

The CREATE of the HLIO SANCTUM failed.

HLIO SANCTUM could not be created.

The CREATE of the COMPATIBILITY MODE I/O queue failed.

COMPATIBILITY MODE I/O queue could not be created.

The CREATE of the COMPATIBILITY MODE I/O STATE TABLE failed.

COMPATIBILITY MODE I/O STATE TABLE could not be created.

The CREATE of the LOGICAL PATH TABLE failed.

The LOGICAL PATH TABLE could not be created.

The CREATE of the DATA CHAIN TABLE failed.

The DATA CHAIN TABLE could not be created.

The CREATE of the TERMINAL BUFFER TABLE failed.

The TERMINAL BUFFER TABLE could not be created.

The CREATE of the I/O QUEUE TABLE failed.

The I/O QUEUE TABLE could not be created.

The CREATE of the SERIAL WRITE TABLE failed.

The SERIAL WRITE TABLE could not be created.

The CREATE of the DISC MESSAGE POOL failed.

The DISC MESSAGE POOL could not be created.

The CREATE of the DEVICE MESSAGE POOL failed.

The DEVICE MESSAGE POOL could not be created.

The CREATE of the disk FILL OBJECTS failed.

The disk FILL OBJECTS could not be created.

The CREATE of the HLIO SURROGATES failed.

The HLIO SURROGATES could not be created.

The function received was not implemented by this logical device manager.

This logical device manager did not implement the received function.

The SERIAL WRITE MANAGER had an error in the SEND to the I/O COMPLETION port.

A SEND to the I/O COMPLETION port caused an error to SERIAL WRITE MANAGER.''

The SERIAL WRITE MANAGER received an invalid LDEV.

An invalid LDEV was passed to the SERIAL WRITE MANAGER.

The SERIAL WRITE MANAGER had an error in returning the SERIAL QUEUE entry.

Returning the SERIAL QUEUE entry caused an error to the SERIAL WRITE MANAGER.''

The SERIAL WRITE MANAGER could not start the request because of an error.

The request in SERIAL WRITE MANAGER could not be started.

The serial queue is in the wrong state for the operation requested.

Wrong state for requested operation.

SENDMMIO must be passed to the request at the head of the list.

SENDMMIO was not passed to the request at the head of the list.

The SERIAL WRITE MANAGER received an unknown message.

An unknown message was passed to the SERIAL WRITE MANAGER.

The MEMORY MANAGER surrogate HASH TABLE is full.

Surrogate HASH TABLE in MEMORY MANAGER is full.

The MEMORY MANAGER surrogate received a completion for an unknown RID.

Completion received in MEMORY MANAGER for an unknown RID.

The MEMORY MANAGER surrogate swap in FAILED.IN

The MEMORY MANAGER surrogate could not send the completion message to the LDM.

Completion message not sent by the MEMORY MANAGER surrogate to the LDM.

The MEMORY MANAGER surrogate received an unknown message.

An unknown message was sent to the MEMORY MANAGER surrogate.

The MEMORY MANAGER surrogate received an error from MAKE_PRESENT_IO_BUFFER.

MAKE_PRESENT_IO_BUFFER sent an error to the MEMORY MANAGER surrogate.''

An error occurred, and HLIO's normal error recovery was not enabled.

HLIO's normal error recovery was not enabled when an error occurred.

The MEMORY MANAGER initialization module was unable to allocate a table entry from an object.

The MEMORY MANAGER initialization module was unable to retrieve a table entry which should be in the table's free list.

GET_TABLE_INFO returned a bad status to the MEMORY MANAGER initialization module when the latter tried to access the PDIR.

The MEMORY MANAGER initialization module received a bad status from an attempt to validate a resident object's access rights.

The MEMORY MANAGER initialization module was unable to create a required table.

The initialization module was unable to create the nonresident objects required
by the MEMORY MANAGER.

The MEMORY MANAGER was unable to create the page filler process.

The MEMORY MANAGER was unable to activate the page filler process.

The MEMORY MANAGER I/O INFORMATION TABLE was out of entries.

The MEMORY MANAGER alias operation encountered a bad status while trying to access the I/O notification queue.

The MEMORY MANAGER alias operation encountered a bad status while trying to access the I/O notification queue.

The MEMORY MANAGER was unable to set TRANSACTION MANAGEMENT post attributes correctly.

The MEMORY MANAGEMENT semaphore for this physical page is already locked. This should not occur in a uni-processor environment.

An attempt was made to set TRANSACTION MANAGEMENT FREEZE attributes on a virtual page which was not frozen in memory.

The I/O completion port was the wrong port for this process.

The MEMORY MANAGER detected an error when it attempted to send a message to the DISPATCHER.

The MEMORY MANAGER detected an error when it attempted to call NOTIFY_DISPATCHER from MAKE_IO_BUFFER_PRESENT.

The MEMORY MANAGER was unable to update a physical page's NO POST count.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER encountered an error while trying to send a FETCH message to the DISPATCHER.

NOTIFY_DISPATCHER returned a bad status to SYSTEM_FETCH_REQUEST.

An attempt was made to UNFREEZE a virtual page which was not mapped into physical memory.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER was unable to WRITE pages out to disk which had been locked in the VPN cache.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER was unable to access the I/O notification port.

An attempt was made to FREEZE an invalid virtual address.

An attempt was made to FREEZE an invalid virtual address.

The MEMORY MANAGER was unable to access the I/O notification port.

The MEMORY MANAGER LOCALITY LIST TABLE was out of entries.

The locality list is not empty after all entries were supposed to have been
deleted from the list.

Some virtual pages which were to be removed from the locality list do not all fall within the range of an individual locality list entry.

A process is currently accessing a page of an object which is being deleted.

The MEMORY MANAGER was unable to get an entry from the LOCALITY LIST TABLE.

The MEMORY MANAGER was unable to get an entry from the LOCALITY LIST TABLE.

The MEMORY MANAGER is attempting to delete an entry from the locality list which still needs to be swapped in.

The MEMORY MANAGER could not find the specified locality entry in the locality list.

The MEMORY MANAGER could not find the specified locality entry in the locality
list.

The MEMORY MANAGER allows prefetching on only one range of pages.

The process's locality list contains more than the maximum number of entries.

The process's locality list contains more than the maximum number of entries.

The MEMORY MANAGER was unable to send a message to the logical device manager port while trying to complete swapping in the page.

The MEMORY MANAGER encountered low level I/O errors while trying to swap in a page.

The MEMORY MANAGER encountered a page fault while interrupts were disabled.

The MEMORY MANAGER encountered a date page fault while the DISPATCHER was disabled.

The MEMORY MANAGER encountered a code page fault while the DISPATCHER was disabled.

The MEMORY MANAGER encountered a page fault on the ICS.

This system failure is only used for internal debugging and should not be seen in the field.

The MEMORY MANAGER can not allocate the header entry for the I/O notification queue, despite the fact that the process could be impeded for resources.

The MEMORY MANAGER can not allocate the header entry for the I/O INFO queue, despite the fact that the process could be impeded for resources.

The MEMORY MANAGER can not SETUP the header entry for the I/O request queue, despite the fact that the process could be impeded for resources.

The MEMORY MANAGER has been requested to cancel a user WRITE; this is not permitted.

The MEMORY MANAGER has been requested to cancel a user WRITE; this is not permitted.

The MEMORY MANAGER was unable to send a message to the I/O completion port.

An I/O request, upon which other requests are dependent, has a bad status.

A bad status was returned from an attempt to POST a page out to the disk.

An attempt was made to FREEZE a page which was not mapped into physical memory.

The MIB's last quad link in the MIB is corrupt.

An attempt to set up an I/O request entry failed.

An attempt to ADD an entry to a READ I/O notification queue failed.

An attempt to ADD an entry to a WRITE I/O notification queue failed.

An attempt to SEND a message to an I/O completion port failed.

An attempt to ADD an entry to a READ I/O notification queue failed.

The MEMORY MANAGER is trying to initiate the READ of a virtual page before the page can be brought into memory.

An attempt to initiate a READ from virtual memory failed.

An attempt to initiate a READ from virtual memory failed.

The MEMORY MANAGER semaphore for this page is already locked.

An unknown status was returned from SET_UP_READ.

The MEMORY MANAGER was unable to RESERVE a physical page while trying to FETCH a virtual page.

The MEMORY I/O COMPLETION PORT SERVER was unable to SEND a message in order to invoke the page READ or page WRITE completor.

An error occurred while low-level I/O attempted to READ a NATIVE MODE stack page in from secondary storage.

An error occurred while low-level I/O attempted to WRITE a NATIVE MODE stack page out to secondary storage.

The MEMORY MANAGER detected an error when trying to POST a page out to the disk.

The MEMORY MANAGER was unable to allocate an I/O INFO entry.

The MEMORY MANAGER was unable to allocate an I/O notification queue entry.

The MEMORY MANAGER detected an error while trying to set up an I/O request entry.

An error was detected while trying to POST a MIB to a secondary storage.

A virtual page whose post must be POSTPONED is already on its way to disk.

The MEMORY MANAGER received an error when it attempted to RECEIVE from its I/O notification port.

The MEMORY MANAGER tried to DELETE an entry from the PDIR which was not found in the HASH TABLE chains.

The MEMORY MANAGER was unable to CREATE one of its required ports.

The MEMORY MANAGER detected an error while scanning the PDIRX for recently unreferenced pages.

The MEMORY MANAGER was unable to FIND a block of contiguous physical memory.

The MEMORY MANAGER detected an error while scanning the PDIRX for recently unreferenced pages.

The MEMORY MANAGER detected an error while trying to set up an I/O request entry.

The MEMORY MANAGER detected an error while trying to identify a block of contiguous physical pages.

The MEMORY MANAGER was not able to GET a MIB for this request.

The MEMORY MANAGER detected an error while trying to kick out a block of contiguous physical pages.

The MEMORY MANAGER was unable to add an entry to the I/O notification queue.

A block of contiguous physical memory was requested for virtual pages which were not virgin.

The MEMORY MANAGER was unable to allocate an I/O notification queue entry.

The MEMORY MANAGER was unable to set up an I/O INFO entry.

The MEMORY MANAGER received an error when writing a page to secondary storage.

The MEMORY MANAGER received an error when it attempted to RECEIVE from its I/O notification port.

A block of physical pages which the MEMORY MANAGER tried to make memory-resident contained a page which was not present.

The critical PAGE POOL is empty.

The MEMORY MANAGER was unable to REPLENISH the critical PAGE POOL.

The MEMORY MANAGER received an error when it attempted to RECEIVE from its I/O notification port.

The MEMORY MANAGER could not find a memory-resident PAGE entry in the PDIRX.

The MEMORY MANAGER could not find a memory-resident PAGE entry in the PDIRX.

The MEMORY MANAGER was unable to get a PDIR entry from TABLE MANAGEMENT.

Inserting an entry at the head of a chain in the KO HASH TABLE is the only supported method.

Inserting an entry at the head of a chain in the PSEUDO PRESENT HASH TABLE is the only supported method.

The MEMORY MANAGER was unable to lock the PDIRX when attempting to CHANGE a page to a recoverable overlay candidate.

A user-requested WRITE is in progress on a stack page above SP.

An error was detected while trying to send a message to the MEMORY MANAGER PAGE filler port.

The MEMORY MANAGER detected an error while trying to get a clean page to add to the filled page pool.

An error was detected whie trying to RECEIVE a message from the MEMORY MANAGER PAGE filler port.

The MEMORY MANAGER was unable to LOCK to PDIRX.

The MEMORY MANAGER detected an error while attempting to WRITE pages to
secondary storage.

The MEMORY MANAGER can not find a page which has not been referenced since the last traverse of physical memory.

The MEMORY MANAGER was unable to LOCK the PDIRX.

The MEMORY MANAGER was unable to LOCK the PDIRX.

The MEMORY MANAGER encountered a STACK OVERFLOW while trying to handle a STACK OVERFLOW condition.

The MEMORY MANAGER was unable to ADD a page to a process's minimum locality.

The MEMORY MANAGER detected an error while trying to get PLABEL information about a system entry point.

The MEMORY MANAGER was unable to CREATE an object in the safe stack.

The MEMORY MANAGER was unable to lock an object in the safe stack.

The MEMORY MANAGER attempted to MAP in a VIRGIN page which was already in the process of being mapped in from secondary storage.

The TOS of STACK POINTER (SP) is not word-aligned.

The MEMORY MANAGER was unable to FREEZE pages in the SAFE stack.

The MEMORY MANAGER was unable to release an object from the SAFE stack.

A PAGE fault which was no a TOS trap occurred while interrupts were disabled.

A PAGE fault occurred while the DISABLED TOS trap count was nonzero.

The MEMORY MANAGER was unable to get an entry from the GREY PAGE TABLE.

The physical PAGE POOL used for mapping in TOS pages was empty.

The MEMORY MANAGER was unable to get an entry from the GREY PAGE TABLE.

A virtual page which should have been frozen in memory was found to be absent.

The MEMORY MANAGER was unable to LOCK a portion of the process stack in the VPN cache.

The MEMORY MANAGER was unable to get a valid PLABEL from the loader.

FETCH pages could not obtain the resources that it needs.

FETCH PAGES out of service clean up has detected an inconsistency.

An attempt was made to FREEZE a virtual page which was not mapped into physical memory.

An attempt was made to UNFREEZE a virtual page which was not mapped into physical memory.

The MEMORY MANAGER either was given a bad locality list entry number, or found a bad entry in the locality list.

The MEMORY MANAGER's semaphore for this page is already locked. This should not occur in a uni-processor environment.

A frozen page is absent.

A frozen page is absent.

An uninitialized semaphore is used in a lock request.

An attempt was made to lock the stack below the currently locked area.

We were asked to map in a page for a page that was present.

If we force a KO page absent, it should have a present version.

An error was detected in changing from VPS to KO.

The PDIRX entry could not be locked.

SEND MESSAGE failed in background posts.

A bug occurred in stale page bug catcher.

Page VP state detected in CHANGE VPS STATE.

MM_TT_ZERO_VALUED_FIRST_INTERRUPT_MKR for MEMORY MANAGER.

First CM interrupt marker in TCB is set to zero.

The procedure CREATE_PROCESS_SWITCH_OBJ is unable to create process SWITCH OBJECT.

Unable to create an object for the CM procedure name to the plabel table.

The procedure CREATE_PROCESS_SWITCH_OBJ is unable to create HASH TABLE.

Unable to create the CM procedure name to the plabel table.

The procedure ALLOCATE_CM_PROCEDURE received bad status from SWITCH_TO_CM.

SWITCH_TO_CM could not call LOADPROC.

The procedure DEALLOCATE_CM_PROCEDURE received bad status from SWITCH_TO_CM.

SWITCH_TO_CM could not call UNLAODPROC.

The procedure DELETE_SCM_HASH_ENTRY failed to find entry.

Could not find a name in the CM procedure name to plabel table.

The procedure DELETE_SCM_HASH_ENTRY received bad status from RELEASE_TABLE_ENTRY.

A table management error occured while releasing a table entry in the CM procedure to the plabel table.

The procedure GET_PROCESS_SCM_PLABEL received bad status from RELEASE_TABLE_ENTRY.

A table management error occured while releasing a table entry in the CM procedure name to the plabel table.

The procedure SWITCH_TO_CM received bad status from RELDATSEG.

Unable to release a data segment previously created in SWITCH_TO_CM.

TIMER entry had an illegal state.

The current process had no standard signal port.

GET_TIMEREQ: get_global_port_num returned no number for the standard signal port.

An invalid code was received from compatibility TIMEREQ.

GET_TIMEREQ: invalid timer code parameter received.

Bad TABLE MANAGEMENT status was received when the timer entry was released.

The current process had no standard signal port.

PROC_PAUSE: get_global_port_num returned no number for the standard signal port.

The procedure INITIALIZE_TIMERS failed to create TIMER ENTRY TABLE.

The call to create_table failed.

The procedure INITIALIZE_TIMERS failed to create TIMER global area.

The call to create_object failed.

PDC TOD read failed.

PDC_TIME: call to get_pdc_tod failed.

PDC TOD write failed.

SET_PDC_TIME: call to pdc_access_4 failed.

Can not read PDC TOD calib.

PDC_TIMER_CAL: call to get_pdc_timer failed.

Can not read PDC TOD calib.

PDC_TIMER_ACC: call to get_pdc_timer failed.

CLOCK_SYNC WRITE failed.

SYBC_CLOCKS: call to set_pdc_timer failed.

The procedure failed to create port for clock sync.

INIT_HARDWARE_CLOCK_UPDATES: call to create_port failed.

The procedure failed to get TIMER for clock sync.

INIT_HARDWARE_CLOCK_UPDATES: call to get_timer failed.

Clock failed to notify a port of a clock interrupt.

TIMER_INTERRUPT HANDLER: call to send_msg failed and the system was not in the shutdown state.

An attempt was made to release timer entry zero.

RELEASE_TIMER: timer entry zero was received as an input parameter.

A high priority machine check occurred.

A low priority machine check occurred.

ILLEGAL INSTRUCTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

ILLEGAL INSTRUCTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

A BREAK instruction occurred on the INTERRUPT CONTROL STACK (ICS).

PRIVILEGED OPERATION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

PRIVILEGED REGISTER TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

OVERFLOW TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

CONDITIONAL TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

ASSIST EXCEPTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

DATA MEMORY PROTECTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

CM STACK OVERFLOW procedure occurred while DISABLED OR PDISABLED.

CM STACK OVERFLOW occurred while handling CM STACK OVERFLOW.

CM STACK OVERFLOW failed to change break range.

ASSIST EMULATION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

HIGH PRIVILEGE TRANSFER TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

LOW PRIVILEGE TRANSFER TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

TAKEN BRANCH TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).

CREATE_TABLE failed.

CREATE_MIB: bad status from create_table.

One or more parameters are bad.

Check for correct options before calling get_short_int_entry.

Bad MIB address.

Check that mib_state is allocated_mib before calling rel_short_int_entry.

Bad status returned for GET_TABLE entry.

Bad status returned from FAST_RELEASE_TABLE_ENTRY.

REL_SHORT_INT_ENTRY: bad status from tbl_fast_release_table_entry.

Bad status returned from FAST_RELEASE_TABLE ENTRY.

REL_LONG_INT_ENTRY: bad status from release_table_entry.

External interrupt handler failed to initialize its EXTERNAL INTERRUPT TABLE (EXT_INT_TABLE).

There is a problem with VSM in CREATE_OBJECT interface.

Can not send interrupt message to the system.

SEND MESSAGE failure.

Could not create the system logging globals area.

LOG process could not successfully create the system logging global object.

The procedure could not get standard message port for the system logging process.

LOG process could not get standard message port.

The current system log file and its label are inconsistent.

When LOG process tries to post a block to the current system log file, it finds that the log file is not consistent with its label.

Internal table pool resource is corrupted.

Internal table entry link is corrupted in the procedure REL_LONG_MIB_ENTRY.

Internal table entry link is corrupted in the procedure REL_SHORT_MIB_ENTRY.

A process is executing the procedure PM_CLEANUP other than the process MANAGEMENT CLEANUP process.

After the system has completed its boot up, an attempt to make selected system process stacks swappable failed.

After the system has completed its boot up, an attempt to lock the system processes stacks in the VPN cache failed.

During system boot, an attempt to create the CLEANUP process failed.

A process holding a SIR has been terminated.

The trap handling procedure encountered a trap while processing a trap.

A system process is being terminated due to a trap.

A critical process is being terminated due to a trap.

A trap occurred on a process whose state is not ALIVE.

We are terminating a process whose state is not ALIVE.

We continued to execute in TERMINATE_PROCESS after giving up the CPU.

While the system is booting, we were unable to obtain a pointer to the PCB TABLE (CONVERT_DST).

While the system was booting, we were unable to initialize the port for the BOOT process (SETUP_PORTS).

While the system was booting, a release object failed on the temporary PIB for the BOOT process (RELEASE_OBJECT).

While the system was booting, we were unable to allocate a process ID for the BOOT process (ALLOCATE_PID).

While the system was booting, we were unable to schedule the BOOT process for execution (NOTIFY_DISPATCHER).

While the system was booting, we were unable to allocate space in BANK 0 for the PCB TABLE (ALLOC_B0_SUB_OBJECT).

While the system was booting, we were unable to get a long pointer to the PCB TABLE (CONVERT_DST).