System Abort messages are issued when the MPE/iX system encounters an error
from which recovery is not possible. Rather than continue to operate and risk
data integrity, the operating system halts the computer. This chapter presents
a list of system abort messages in numerical order.
NOTE: Unless otherwise indicated, the probable cause of an abort is an
internal error, and the action you should take is to take a system dump, call
your HP support representative, and reboot your system.
System Abort Errors 1 - 399
2
MESSAGE
Ran out of memory before PAGE and HASH TABLES were properly initialized.
CAUSE
Ran out of physical memory; address is outside the range of the machine.
3
MESSAGE
Could not create the table header for the PDIR and/or the PDIR
could not set up as a standard system table.
CAUSE
Failure occurred when calling the CREATE_TABLE to create the PDIR header.
4
MESSAGE
Could not free up entries in the PDIR corresponding to memory
below the PME during PDIR initialization.
CAUSE
Failure occurred when calling RELEASE_TABLE_ENTRY to release all PDIR TABLE entries.
5
MESSAGE
Could not find a free entry in memory in the PDIR using the GENESIS MEMORY MANAGER.
CAUSE
Failure occurred when calling GET_TABLE_ENTRY to find a free entry in memory in the PDIR.
6
MESSAGE
Could not release an entry in the PDIR using the GENESIS MEMORY
MANAGER during a GET_MEMORY call.
CAUSE
Failure occurred when calling the RELEASE_TABLE_ENTRY to return the
table entry corresponding to the given page number to the free pool.
7
MESSAGE
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.
CAUSE
Page alignment incorrect.
8
MESSAGE
The procedure could not find a set of contiguous pages of the
correct alignment (for example, not enough memory left).
CAUSE
Set of contiguous with the correct alignment are not available.
9
MESSAGE
The procedure could not find a free page with the correct
alignment using the GENESIS MEMORY MANAGER.
CAUSE
Unable to find a free page correctly aligned.
10
MESSAGE
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.
CAUSE
Duplicate memory assignment range request.
11
MESSAGE
Could not release an entry in the PDIR using the GENESIS MEMORY
MANAGER during a RELEASE_MEMORY call.
CAUSE
Failed when calling RELEASE_TABLE_ENTRY for releasing page from PDIR TABLE.
12
MESSAGE
Could not initialize the resident PORTS facility.
CAUSE
Failed when calling INIT_RES_PORT_FACILITY to initialize ports.
13
MESSAGE
Could not initialize the TIMERS facility.
CAUSE
Failed when calling INITIALIZE_TIMERS to initialize timers facility.
14
MESSAGE
Could not configure primary I/O devices.
CAUSE
Failed when calling CONFIGURE_FOR_GENESIS to configure the system
disk and console.
50
MESSAGE
PRIMIO device not configured.
CAUSE
Low Level I/O returned error when configuring device.
51
MESSAGE
CONFIGURE_HLIO_DEVICE configuration not done.
CAUSE
High Level I/O returned error when configuring device.
52
MESSAGE
An error occurred in IO_INIT.
CAUSE
Low Level I/O returned error when setting up primary I/O environment.
53
MESSAGE
An error occurred in CONFIGURE_LPT.
CAUSE
High Level I/O returned an error when setting up primary I/O environment.
54
MESSAGE
An error occurred in CONFIGURE_DEVICE (halt; not system abort).
CAUSE
Problem occurred configuring console (will appear in front panel message - halt).
55
MESSAGE
An error occurred in CONFIGURE_DEVICE.
CAUSE
Problem occurred configuring device other than the console.
70
MESSAGE
SENDIO to read from SYSDISC failed.
CAUSE
I/O code returned a disk error.
ACTION
Call your support representative. The dump may be restarted.
71
MESSAGE
RENDEZVOUSIO to read from SYSDISC failed.
CAUSE
I/O returned a disk error.
ACTION
Call your support representative. The dump may be restarted.
72
MESSAGE
SENDIO to READ from disk failed.
CAUSE
I/O code returned a disk error.
ACTION
Call your support representative. The dump may be restarted.
73
MESSAGE
REWIND_TAPE_ONLINE of dump device failed.
CAUSE
I/O code returned a tape error.
ACTION
Call your support representative. The dump may be restarted.
74
MESSAGE
RENDEZVOUSIO returned error on rewind tape online.
CAUSE
I/O code returned a tape error.
ACTION
Call your support representative. The dump may be restarted.
75
MESSAGE
REWIND_TAPE of dump device failed.
CAUSE
I/O code returned a tape error.
ACTION
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.
76
MESSAGE
RENDEZVOUSIO returned error on REWIND_TAPE.
CAUSE
I/O code returned a tape error.
ACTION
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.
77
MESSAGE
FORCE_WRITE end of file to dump device failed.
CAUSE
I/O code returned a tape error.
ACTION
Call your support representative. The dump may be restarted.
78
MESSAGE
SENDIO to FORCE_WRITE to dump device failed.
CAUSE
I/O code returned a tape error.
ACTION
Call your support representative. The dump may be restarted.
79
MESSAGE
WRITE end of file to dump device failed.
CAUSE
I/O code returned a tape error.
ACTION
Call your support representative. The dump may be restarted.
80
MESSAGE
SENDIO to READ from dump device failed.
CAUSE
A non-recoverable tape READ error occurred.
ACTION
Call your support representative. The dump may be restarted.
81
MESSAGE
SENDIO to WRITE to dump device failed.
CAUSE
A non-recoverable tape WRITE error occurred.
82
MESSAGE
SENDIO for tape GET_DEVICE_STATUS failed.
CAUSE
I/O code returned error trying to get tape device status; did not
occur during tape READ or WRITE.
ACTION
Call your support representative. The dump may be restarted.
100
MESSAGE
The procedure BUILD_DIAGMON_PORT failed to build the diagnostic monitor port.
CAUSE
Failed when calling BUILD_DIAGMON_PORT to build diagnostic monitor port.
101
MESSAGE
The procedure LOAD_SYSTEM_SL failed to load the system SL.
CAUSE
System SL was not loaded by the LOAD_SYSTEM_SL procedure.
102
MESSAGE
The procedure INITIALIZE_DISPATCHER failed to initialize the DISPATCHER.
CAUSE
DISPATCHER was not initialized.
103
MESSAGE
The procedure SM_CREATE_HASH_TBL failed to create the HASH TABLE.
CAUSE
HASH TABLE was not created.
104
MESSAGE
The procedure READ_HPE_VOL_POINTERS failed to READ from LDEV 1.
CAUSE
Procedure could not be read from LDEV 1.
105
MESSAGE
The procedure READ_HPE_VOL_INFO_UFID failed to READ the UFID from LDEV 1.
CAUSE
The UFID could not be read.
106
MESSAGE
The procedure READ_HPE_VOL_FREE_ADDR failed to READ the first free address from LDEV 1.
CAUSE
The first free address could not be read.
107
MESSAGE
The procedure GET_HPE_DISC_SIZE_PAGE is unable to access LDEV 1.
CAUSE
LDEV 1 could not be accessed.
108
MESSAGE
The procedure START_VOLUME_MGT failed to START VOLUME MANAGEMENT.
CAUSE
VOLUME MANAGEMENT was not started with the required procedure.
109
MESSAGE
The procedure GET_SYSLIB_UFID is unable to GET the system library UFID.
CAUSE
The system library UFID could not be accessed.
110
MESSAGE
The procedure MAKE_OBJECT_SWAPPABLE is unable to MAKE SXRT swappable.
CAUSE
SXRT is not swappable.
111
MESSAGE
The procedure MAKE_OBJECT_SWAPPABLE is unable to MAKE LST component swappable.
CAUSE
LST component is not swappable.
112
MESSAGE
The feature ALTER_OBJECT_SIZE failed to INCREASE the SXRT object size.
CAUSE
The SXRT objective could not be increased.
113
MESSAGE
The feature LOAD_NON_RES_SYSTEM failed to LOAD the nonresident system.
CAUSE
The nonresident system could not be loaded.
114
MESSAGE
The procedure INIT_NONRES_PORT_FACILITY failed to initialize the nonresident port facility.
CAUSE
The nonresident port facility was not initialized.
115
MESSAGE
The procedure READ_HPE_VOL_COLDL_ID failed to READ the cold load ID from LDEV 1.
CAUSE
The cold load ID was not read from LDEV 1.
116
MESSAGE
The procedure WRITE_HPE_VOL_COLDL_ID failed to WRITE the cold load ID from LDEV 1.
CAUSE
The cold load ID was not written from LDEV 1.
117
MESSAGE
The procedure FS_INITIALIZE_FILE_SYSTEM failed to initialize the file system.
CAUSE
The file system was not initialized.
118
MESSAGE
The procedure FS_PROC_INIT failed to initialize the PROCESS information block extension area.
CAUSE
The PROCESS information block extension area was not initialized.
119
MESSAGE
The procedure FAKE_LOGON failed to OPEN the file system directories (PLFDs).
CAUSE
The file system directories (PLFDs) were not opened.
120
MESSAGE
The procedure INIT_LOADER failed to initialize the LOADER.
CAUSE
LOADER was not initialized.
121
MESSAGE
The procedure ADD_CLASS is unable to SWITCH to CM.
CAUSE
ADD_CLASS could not SWITCH to CM.
122
MESSAGE
The procedure ADD_DEVICE is unable to SWITCH to CM.
CAUSE
ADD_DEVICE could not SWITCH to CM.
123
MESSAGE
The procedure ADD_DEVICE is unable to add the system disk
(LDEV 1) through ADD_DEVICE for CM.
CAUSE
The system disk could not be added through ADD_DEVICE for CM.
124
MESSAGE
The procedure ADD_DEVICE is unable to ADD the system console through ADD_DEVICE for CM.
CAUSE
The system console could not be added through ADD_DEVICE for CM.
125
MESSAGE
The procedure ADD_VIRTUAL_LDEVS is unable to SWITCH to CM.
CAUSE
ADD_VIRTUAL_DEVICE could not be switched to CM.
126
MESSAGE
The procedure CLEAN_CM_DEVICE_TABLES is unable to SWITCH to CM.
CAUSE
CLEAN_CM_DEVICE_TABLES could not SWITCH to CM.
127
MESSAGE
The procedure INIT_CM_DEVICE_TABLES is unable to SWITCH to CM.
CAUSE
INIT_CM_DEVICE could not SWITCH to CM.
128
MESSAGE
The procedure IO_INIT failed to initialize the low level I/O system.
CAUSE
The low level I/O system was not initialized.
System Abort Errors 400 - 599
450
MESSAGE
Activation of JOBMAIN process failed.
451
MESSAGE
Activation of SESSIONMAIN process failed.
452
MESSAGE
Creation of JOBMAIN process failed.
453
MESSAGE
Creation of JOBMAIN_PORT failed.
454
MESSAGE
Creation of JOBQUEUE_PORT failed.
455
MESSAGE
Creation of SESSIONMAIN process failed.
456
MESSAGE
Creation of SESSIONMAIN_PORT process failed.
457
MESSAGE
Opening JOBMAIN_PORT process failed.
458
MESSAGE
Opening JOBQUE_PORT process failed.
459
MESSAGE
Opening SESSIONMAIN_PORT process failed.
460
MESSAGE
The information and subsystem escape is passed as the second parameter.
461
MESSAGE
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.
462
MESSAGE
Had an unexpected escape from the operating system to the JSMAIN outerblock.
463
MESSAGE
Port status is passed as the second parameter.
464
MESSAGE
Port status is passed as the second parameter.
465
MESSAGE
Port status is passed as the second parameter.
500
MESSAGE
Management failed to post data from memory to disk.
CAUSE
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.
501
MESSAGE
During a file open, the GUFD semaphore could not be initialized.
CAUSE
A call to CB_INIT returned bad status.
502
MESSAGE
During a file open, the FLOCK semaphore could not be initialized.
CAUSE
A call to CM_INIT returned bad status.
503
MESSAGE
During a file open, the FOPEN semaphore could not be initialized.
CAUSE
A call to CB_INIT returned bad status.
504
MESSAGE
Prefetch of needed data for a READ/WRITE request could not be made.
CAUSE
VSM reported address or range given to be invalid or out of bounds.
505
MESSAGE
Attempted to CLOSE a file which is not OPEN.
CAUSE
File system lock algorithm failed.
506
MESSAGE
The procedure could not open the system library (the NL).
CAUSE
Boot image or LABEL TABLE is corrupted.
ACTION
Take a system dump and reinstall if necessary.
508
MESSAGE
CREATE_OBJECT failed to create the SM KSO.
509
MESSAGE
The procedure was unable to obtain the HASH TABLE lock.
CAUSE
CB_INIT returned bad status trying to initialize the UFID HASH TABLE semaphore; start image is bad.
ACTION
Recreate the boot image. Take a system dump and call your support representative.
511
MESSAGE
The procedure was unable to obtain the LRU lock.
CAUSE
CB_INIT returned bad status trying to initialize the LRV semaphore; start image is bad.
ACTION
Recreate the boot image. Take a system dump and call your support representative.
514
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.
551
MESSAGE
Offset of entry is not within the LABEL TABLE.
CAUSE
LABEL TABLE has been corrupted.
552
MESSAGE
The entry referenced is not an extent block type.
CAUSE
LABEL TABLE has been corrupted.
553
MESSAGE
Extent block does not point to the correct PARENT label.
CAUSE
LABEL TABLE has been corrupted.
554
MESSAGE
Two file offsets in the extent block are the same.
CAUSE
LABEL TABLE has been corrupted.
555
MESSAGE
An extent block that is expected to be a free entry is not free.
CAUSE
LABEL TABLE has been corrupted.
556
MESSAGE
A POST of a LABEL TABLE entry failed.
CAUSE
MEMORY MANAGER failed to port a LABEL TABLE entry.
ACTION
Reboot the system, and run FSCHECK to see if a reinstall of the system is necessary.
557
MESSAGE
The number of EXTENTS in the block exceeds the maximum allowable.
CAUSE
LABEL TABLE has been corrupted.
System Abort Errors 600 - 799
613
MESSAGE
The file system encountered a trap.
CAUSE
An operating system software error caused a trap.
614
MESSAGE
The file system encountered an unexpected ESCAPE.
CAUSE
An internal operating system module called ESCAPE unexpectedly.
615
MESSAGE
The file system was unable to release a resource.
CAUSE
Due to an operating system software error, the file system was not
able to release one or more system resources.
616
MESSAGE
An error was encountered while creating FILE SYSTEM GLOBAL AREA
during file system initialization.
617
MESSAGE
An error was encountered while creating GPDP TABLE during file
system initialization.
618
MESSAGE
An error was encountered while creating FILE OPEN COUNT TABLE
during file system initialization.
619
MESSAGE
An error was encountered while creating BASIC IPC (BIPC) TIMER
server ports during file system initialization.
620
MESSAGE
An error was encountered while initializing STORE/RESTORE
LATENCY TABLE during file system initialization.
621
MESSAGE
An error occurred in the file system during process termination.
CAUSE
The file system detected an operating system software error while
cleaning up file system data structures during process termination.
650
MESSAGE
An internal STORAGE MANAGEMENT error was encountered while
attempting to CLOSE (FCLOSE) a file.
CAUSE
Due to an operating system software error STORAGE MANAGEMENT was not
able to CLOSE the file.
651
MESSAGE
FCLOSE was not able to delete a file's access rights entry from
the FILE ACCESS RIGHTS TABLE.
CAUSE
A file system error occurred during file OPEN or the FILE ACCESS
RIGHTS TABLE has been corrupted.
652
MESSAGE
An error was encountered while attempting to return an allocated
GPDP to the free list while trying to CLOSE (FCLOSE) a file.
CAUSE
The GDPD TABLE has been corrupted.
653
MESSAGE
The file system detected a counter underflow in a GUFD.
CAUSE
The GUFD has been corrupted.
654
MESSAGE
The FILE ACCESS RIGHTS TABLE counters are inconsistent.
CAUSE
The FILE ACCESS RIGHTS TABLE has been corrupted.
655
MESSAGE
The procedure can not decrement the PDISABLE count; it is unexpectedly zero.
656
MESSAGE
The CB was unlocked by a PIN different from the PIN that locked it.
657
MESSAGE
The VECTOR TABLE in the CB is corrupt.
658
MESSAGE
Failure in creating File IO State Tables
CAUSE
System failed to create one of the File IO State Tables during
system initialization.
ACTION
Contact your Hewlett-Packard Representative.
659
MESSAGE
Failure in creating one of the local socket tables.
CAUSE
System failed to create one of the local socket tables during system
initialization.
ACTION
Contact your Hewlett-Packard Representative.
700
MESSAGE
Various port primitive procedures have experienced an unexpected
escape, probably due to a trap while in system code.
701
MESSAGE
The procedure REL_PORT_FREEZE_DESC can not release freeze
descriptor entry; bad status from RELEASE_TABLE_ENTRY.
702
MESSAGE
The procedure RELEASE_PORT_OBJECT can not release port object;
unexpected status from RELEASE_OBJECT.
703
MESSAGE
The procedure RETURN_PORT_DESC can not release port descriptor;
bad status from RELEASE_TABLE_ENTRY.
704
MESSAGE
There are waiters on the demolished message pool.
705
MESSAGE
The procedure DEMOLISH_POOL can not delete the pool's directory
entry from the port directory; bad status from STDELID.
706
MESSAGE
The procedure DEMOLISH_PORT can not access the delayed port purger process.
707
MESSAGE
The procedure DEMOLISH_PORT detected an error in deleting delayed messages.
708
MESSAGE
The procedure DEMOLISH_PORT can not send DEMOLISH message to PFP port.
709
MESSAGE
There are waiters on the demolished port.
710
MESSAGE
The procedures DEMOLISH_PORT, PFP_NAME_TO_PORT_NUM, and
OPEN_PORT can not lock the port directory; bad status from STLOCK.
711
MESSAGE
The procedure DEMOLISH_PORT can not delete the port directory
entry; bad status from STDELID.
712
MESSAGE
The procedures DEMOLISH_PORT and UNLOCK_DIRECTORY can not unlock
the port directory; bad status from STUNLOCK.
713
MESSAGE
At process termination time (DEMOLISH_PORT), an error from TABLE
MANAGEMENT occurred when releasing the standard ports entry to the table.
714
MESSAGE
The procedure DELETE_PORT_BASE can not release the semaphore
port; bad status from RECEIVE_FROM_SEMAPHORE_PORT.
715
MESSAGE
The procedure DELETE_PORT_ACCESS is still holding the semaphore port after release.
716
MESSAGE
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.
717
MESSAGE
The procedure CHANGE_OWNERSHIP corrupted the port ownership
list; port's ownership information inconsistent with PIB's.
718
MESSAGE
The procedure CHANGE_OWNERSHIP detected a corrupted port
ownership list; port's ownership information does not agree with PIB's.
719
MESSAGE
Various procedures caused an unexpected status from PREP_PORT.
720
MESSAGE
The procedure DEC_PFP_COUNT detected an error accessing PFP upon
CREATE_PORT error; can not decrement PFP's use count.
721
MESSAGE
The procedure LOCATE_PORT_ENTRY can not read port directory
entry; bad status from STREADKEY.
722
MESSAGE
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.
723
MESSAGE
The procedures FAST_CONTINUE_SERVER_IN_PFP and
FAST_EXECUTE_SERVER_IN_PFP can not send message to PFP port.
724
MESSAGE
There is a problem with the message frame in the GPO cache.
725
MESSAGE
The port's server caused an unexpected escape.
726
MESSAGE
The procedure INTERNAL_SEND can not get message frame for internal send.
727
MESSAGE
The procedure INTERNAL_SEND can not send to internal facility
port; bad status from SEND_MSG.
728
MESSAGE
The PORT FACILITY PROCESS is not available yet.
729
MESSAGE
The procedure DELAYED_AWAKE_PROCESS can not send the delayed awake message to PFP.
730
MESSAGE
The decrement of the port's total freeze count causes it to become negative.
731
MESSAGE
The port is already totally frozen, but partial freeze failed; no reason for this to happen.
732
MESSAGE
The procedure INITIATE_UNBLOCKED_MAKE_PRESENT (2) can not get
message frame for make present port; bad status from GET_MSG_FRAME.
733
MESSAGE
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.
734
MESSAGE
The procedure BLOCKED_MAKE_PRESENT can not get FREEZE reply from
MEMORY MANAGER for MAKE_PRESENT; bad status from EXTEND_RECEIVE.
735
MESSAGE
The procedure BLOCKED_MAKE_PRESENT detected a bad FREEZE reply
message from MEMORY MANAGER.
736
MESSAGE
The FREEZE count is zero; can not hold FREEZE since port is not totally frozen.
737
MESSAGE
The FREEZE count is zero; cannot release FREEZE because the port
must be totally frozen when called.
738
MESSAGE
The procedure CHECK_PORT_DESCRIPTOR detected an unknown port type in the port descriptor.
739
MESSAGE
The procedure ENABLE_TIMEOUT can not alter the standard message
port for time out; bad status from CHANGE_SUBQUEUE.
740
MESSAGE
The procedure ENABLE_TIMEOUT can not get timer for time out; bad status from GET_TIMER.
741
MESSAGE
The procedure DISABLE_TIMEOUT can not access the standard
message port for time out; bad status from PORT_INFO.
742
MESSAGE
The procedure DISABLE_TIMEOUT can not release timer; unexpected status from RELEASE_TIMER.
743
MESSAGE
The timer has popped. Expected a reply message, but RECEIVE failed; bad status from EXTEND_RECEIVE.
744
MESSAGE
The procedure INCREASE_PROCESS_PRIORITY can not hold or increase
process's priority; bad status from NOTIFY_DISPATCHER.
745
MESSAGE
The procedure BOOST_SERVER_PRIORITY can not boost server's
priority; server's PIN is nil according to the SCB.
746
MESSAGE
The procedure DECREASE_CALLERS_PRIORITY can not decrease
caller's priority; bad status from NOTIFY_DISPATCHER.
747
MESSAGE
The procedure DROP_SERVER_PRIORITY can not drop server's priority because server has nil PIN.
748
MESSAGE
The caller wanted to WAIT, but can not WAIT while program is on the ICS.
749
MESSAGE
The procedure INTERRUPT_TARGET_PROCESS can not AWAKE process
blocked on port WAIT; bad status from NOTIFY_DISPATCHER.
750
MESSAGE
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.
751
MESSAGE
The system is trying to UNIMPEDE the process by sending a wakeup
message to its standard message port, but SEND_MSG failed.
752
MESSAGE
The procedure CLEAR_WWS can not CLEAR the wake up waiting switch; bad status from PORT_CONTROL.
753
MESSAGE
Unexpected status was received from IPC_WAIT_PROCESS.
754
MESSAGE
Unexpected status was received from IPC_AWAKE_PROCESS.
755
MESSAGE
The procedure DELAYED_SEND can not perform the actual delayed
send; bad status from EXTEND_SEND or INSERT_MSG.
756
MESSAGE
Received unexpected status from EXTEND_RECEIVE while receiving
the delayed purge message.
757
MESSAGE
An unrecoverable error occurred during PORT_PURGE_PROCESS.
758
MESSAGE
An error occurred while initializing PFP.
759
MESSAGE
Bad status occurred from RECEIVE_MSG in PORT_FACILITY_PROCESS.
760
MESSAGE
Received an unexpected PFP message type.
761
MESSAGE
Received bad status from internal operation.
762
MESSAGE
Received message from an invalid subqueue on the MAKE PRESENT port.
763
MESSAGE
Requested MEMORY MANAGEMENT to MAKE PRESENT a port entity;
MEMORY MANAGEMENT'S reply indicates the MAKE PRESENT was unsuccessful.
764
MESSAGE
Received unexpected message type in MAKE PRESENT message.
765
MESSAGE
The procedure GET_SHR_OWNER_ENTRY can not get free entry from
the shared owner list pool; shared owner list exhausted.
766
MESSAGE
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.
767
MESSAGE
Either the dispatcher or interrupts were disabled after awaking from a CB WAIT.
768
MESSAGE
The owner of the semaphore being blocked is NIL_PIN.
769
MESSAGE
Various procedures caused the system to abort in an attempt to access unknown semaphore type.
770
MESSAGE
The procedure GIVE_TO_NEXT_WAITERS can not give ownership of the
semaphore to waiter; bad status from NOTIFY_DISPATCHER while unblocking process.
771
MESSAGE
The procedures CB_SHR_LOCK and CB_SHR_UNLOCK caused a system
abort because use of sharable lock while on ICS is not allowed.
772
MESSAGE
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.
773
MESSAGE
The procedure CB_FAILER caused a system abort because multiple
lock of the standard semaphore is not allowed.
774
MESSAGE
The procedure CB_FAILER resulted in an unconditional lock failing while on the ICS.
775
MESSAGE
The procedure CB_FAILER detected an attempt to unlock an unowned semaphore.
776
MESSAGE
The procedure CB_FAILER caused a system abort in an attempt to
unlock an unowned semaphore on the ICS.
777
MESSAGE
The procedure CB_FAILER caused a system abort because access of
this semaphore type is not supported.
778
MESSAGE
The procedure CB_FAILER caused a system abort because the
semaphore access procedure is not allowed on the ICS.
779
MESSAGE
The procedure CB_FAILER caused an unknown error while accessing the semaphore.
780
MESSAGE
The procedure SEM_INIT resulted in bad status from CB_INIT.
781
MESSAGE
The CM pseudo count is less than zero.
782
MESSAGE
The procedure CM_PSDB_CLEAR resulted in bug catcher, clearing
PSDB count; not blocking on port WAIT.
783
MESSAGE
The procedure GET_POOL_ITEM can not access message pool table
header; bad status from GET_TABLE_INFO.
784
MESSAGE
The procedure FLUSH_SEM_WAIT_QUEUE can not flush all waiting
processes from the semaphore's wait queue; bad status from REPLY_TO_WAITER.
785
MESSAGE
The procedure CREATE_STD_PFP_PORTS caused an unexpected escape;
creation of standard PFP port was unsuccessful.
786
MESSAGE
The procedure INIT_RES_PORT_FACILITY can not initialize
INTERRUPT or MAKE_PRESENT semaphore for global port object.
787
MESSAGE
The procedure can not allocate port descriptor for the known
global ports; bad status from MAKE_GLOBAL_DESC.
788
MESSAGE
Initialization of the resident port facility failed due to an
unexpected escape from the procedure.
789
MESSAGE
The procedure can not create the port directory object; bad
status received from CREATE_OBJECT.
790
MESSAGE
The procedure can not create HPIMAGE port; bad status received
from CREATE_PORT.
791
MESSAGE
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.
792
MESSAGE
The procedure CREATE_PORT_PROCESS caused a system abort because
creation of standard port process failed, causing an unexpected escape
from the procedure.
793
MESSAGE
The procedure INITIALIZE_SEMAPHORES can not initialize CM PSDB
semaphore.
794
MESSAGE
The procedure INITIALIZE_SEMAPHORES can not initialize the
COMPARE and SWAP semaphore for the database.
795
MESSAGE
The procedure INITIALIZE_SEMAPHORES can not create the shared
semaphore owner list.
796
MESSAGE
The procedures CHECK_PEND_LEVEL and GET_HIGHEST_PEND_LEVEL can
not access the process interrupt port; bad status from PORT_INFO.
797
MESSAGE
The procedure DELETE_INT_MSG can not return the message frame to
PI port's free pool; bad status from RETRIEVE_MSG.
798
MESSAGE
The procedure CHANGE_INT_LEVEL can not change the allowable
process interrupt levels for this process; bad status from CHANGE_SUBQUEUE.
799
MESSAGE
Various procedures can not notify the dispatcher so that we will
re-enter PI later; bad status from NOTIFY_DISPATCHER.
System Abort Errors 800 - 999
800
MESSAGE
The procedure GET_INTERRUPT_MSG can not obtain the next
interrupt message, yet port is not empty; unexpected status from
RETRIEVE_MSG.
801
MESSAGE
The procedure QUEUE_INTERRUPT_message can not queue interrupt
message from the process' standard PI port; bad status from SEND_MSG.
802
MESSAGE
The procedure WAIT_FOR_ACTIVE_PORT can not WAIT the process; bad
status from NOTIFY_DISPATCHER.
803
MESSAGE
The procedure DEQUEUE_MSG caused a system abort in an attempt to
take the message from an empty subqueue.
804
MESSAGE
The procedure OBTAIN_MSG caused a system abort when trying to
get the message from a non-message port.
805
MESSAGE
The procedure WAIT_UP_WAITER can not wake up the process that is
waiting on this semaphore port.
806
MESSAGE
The procedure RECEIVE_FROM_SEMAPHORE_PORT detected that the
semaphore port's number of free messages is greater than the maximum
number of messages.
807
MESSAGE
The procedure RECEIVE_FROMSEMAPHORE_PORT detected that the
semaphore owner's queue is empty; semaphore is not on its owner's list.
808
MESSAGE
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.
809
MESSAGE
The procedure GET_HIGHEST_PRIORITY_PORT detected an unexpected
interrupt server queue; can not find next eligible queued ICS port.
810
MESSAGE
The procedure SCHEDULE_SERVER detected an error scheduling
procedure server, causing an unexpected escape.
811
MESSAGE
The procedure WAKE_UP_PROCESS_SERVER can not process interrupt
the process server; bad status from CAUSE_PROCESS_INTERRUPT.
812
MESSAGE
The procedure WAKE_UP_PROCESS_SERVER can not AWAKE the process
server that is waiting for a message; bad status from NOTIFY_DISPATCHER.
813
MESSAGE
The procedure RELEASE_WAIT_ENTRY can not return WAIT queue entry
to the free list; bad status from RELEASE_TABLE_ENTRY.
814
MESSAGE
The procedure PUT_WAIT_QUEUE can not put calling process on the
wait queue; illegal to do so while on the ICS.
815
MESSAGE
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.
816
MESSAGE
The procedure PUT_WAIT_QUEUE can not get a free wait queue
entry; bad status from GET_TABLE ENTRY.
817
MESSAGE
The procedure WAIT_FOR_RESOURCE detected that interrupts are
disabled when trying to block the process for a control block.
818
MESSAGE
The procedure WAIT_FOR_ACTIVE_PORT detected that interrupts are
disabled when trying to block a process on the port wait.
819
MESSAGE
The procedure WAIT_FOR_ACTIVE_PORT detected that either the
dispatcher was disabled, or interrupts are off when awaken from an IPC WAIT.
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.
System Abort Errors 1000 - 1199
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.
1030
MESSAGE
An attempt was made to FREEZE an invalid virtual address.
1031
MESSAGE
An attempt was made to FREEZE an invalid virtual address.
1032
MESSAGE
The MEMORY MANAGER was unable to access the I/O notification port.
1033
MESSAGE
The MEMORY MANAGER LOCALITY LIST TABLE was out of entries.
1034
MESSAGE
The locality list is not empty after all entries were supposed
to have been deleted from the list.
1035
MESSAGE
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.
1036
MESSAGE
A process is currently accessing a page of an object which is being deleted.
1037
MESSAGE
The MEMORY MANAGER was unable to get an entry from the LOCALITY LIST TABLE.
1038
MESSAGE
The MEMORY MANAGER was unable to get an entry from the LOCALITY LIST TABLE.
1039
MESSAGE
The MEMORY MANAGER is attempting to delete an entry from the
locality list which still needs to be swapped in.
1040
MESSAGE
The MEMORY MANAGER could not find the specified locality entry in the locality list.
1041
MESSAGE
The MEMORY MANAGER could not find the specified locality entry in the locality list.
1042
MESSAGE
The MEMORY MANAGER allows prefetching on only one range of pages.
1043
MESSAGE
The process's locality list contains more than the maximum number of entries.
1044
MESSAGE
The process's locality list contains more than the maximum number of entries.
1045
MESSAGE
The MEMORY MANAGER was unable to send a message to the logical
device manager port while trying to complete swapping in the page.
1046
MESSAGE
The MEMORY MANAGER encountered low level I/O errors while trying to swap in a page.
1047
MESSAGE
The MEMORY MANAGER encountered a page fault while interrupts were disabled.
1048
MESSAGE
The MEMORY MANAGER encountered a date page fault while the DISPATCHER was disabled.
1049
MESSAGE
The MEMORY MANAGER encountered a code page fault while the DISPATCHER was disabled.
1050
MESSAGE
The MEMORY MANAGER encountered a page fault on the ICS.
1051
MESSAGE
This system failure is only used for internal debugging and should not be seen in the field.
1052
MESSAGE
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.
1055
MESSAGE
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.
1058
MESSAGE
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.
1060
MESSAGE
The MEMORY MANAGER has been requested to cancel a user WRITE; this is not permitted.
1061
MESSAGE
The MEMORY MANAGER has been requested to cancel a user WRITE; this is not permitted.
1062
MESSAGE
The MEMORY MANAGER was unable to send a message to the I/O completion port.
1063
MESSAGE
An I/O request, upon which other requests are dependent, has a bad status.
1064
MESSAGE
A bad status was returned from an attempt to POST a page out to the disk.
1065
MESSAGE
An attempt was made to FREEZE a page which was not mapped into physical memory.
1066
MESSAGE
The MIB's last quad link in the MIB is corrupt.
1067
MESSAGE
An attempt to set up an I/O request entry failed.
1068
MESSAGE
An attempt to ADD an entry to a READ I/O notification queue failed.
1069
MESSAGE
An attempt to ADD an entry to a WRITE I/O notification queue failed.
1070
MESSAGE
An attempt to SEND a message to an I/O completion port failed.
1072
MESSAGE
An attempt to ADD an entry to a READ I/O notification queue failed.
1073
MESSAGE
The MEMORY MANAGER is trying to initiate the READ of a virtual
page before the page can be brought into memory.
1074
MESSAGE
An attempt to initiate a READ from virtual memory failed.
1075
MESSAGE
An attempt to initiate a READ from virtual memory failed.
1076
MESSAGE
The MEMORY MANAGER semaphore for this page is already locked.
1098
MESSAGE
An unknown status was returned from SET_UP_READ.
1099
MESSAGE
The MEMORY MANAGER was unable to RESERVE a physical page while trying to FETCH a virtual page.
1100
MESSAGE
The MEMORY I/O COMPLETION PORT SERVER was unable to SEND a
message in order to invoke the page READ or page WRITE completor.
1101
MESSAGE
An error occurred while low-level I/O attempted to READ a NATIVE
MODE stack page in from secondary storage.
1102
MESSAGE
An error occurred while low-level I/O attempted to WRITE a
NATIVE MODE stack page out to secondary storage.
1103
MESSAGE
The MEMORY MANAGER detected an error when trying to POST a page out to the disk.
1104
MESSAGE
The MEMORY MANAGER was unable to allocate an I/O INFO entry.
1105
MESSAGE
The MEMORY MANAGER was unable to allocate an I/O notification queue entry.
1106
MESSAGE
The MEMORY MANAGER detected an error while trying to set up an I/O request entry.
1107
MESSAGE
An error was detected while trying to POST a MIB to a secondary storage.
1108
MESSAGE
A virtual page whose post must be POSTPONED is already on its way to disk.
1109
MESSAGE
The MEMORY MANAGER received an error when it attempted to RECEIVE from its I/O notification port.
1110
MESSAGE
The MEMORY MANAGER tried to DELETE an entry from the PDIR which was not found in the HASH TABLE chains.
1111
MESSAGE
The MEMORY MANAGER was unable to CREATE one of its required ports.
1112
MESSAGE
The MEMORY MANAGER detected an error while scanning the PDIRX for recently unreferenced pages.
1113
MESSAGE
The MEMORY MANAGER was unable to FIND a block of contiguous physical memory.
1114
MESSAGE
The MEMORY MANAGER detected an error while scanning the PDIRX for recently unreferenced pages.
1115
MESSAGE
The MEMORY MANAGER detected an error while trying to set up an I/O request entry.
1116
MESSAGE
The MEMORY MANAGER detected an error while trying to identify a block of contiguous physical pages.
1117
MESSAGE
The MEMORY MANAGER was not able to GET a MIB for this request.
1118
MESSAGE
The MEMORY MANAGER detected an error while trying to kick out a block of contiguous physical pages.
1119
MESSAGE
The MEMORY MANAGER was unable to add an entry to the I/O notification queue.
1120
MESSAGE
A block of contiguous physical memory was requested for virtual pages which were not virgin.
1121
MESSAGE
The MEMORY MANAGER was unable to allocate an I/O notification queue entry.
1122
MESSAGE
The MEMORY MANAGER was unable to set up an I/O INFO entry.
1123
MESSAGE
The MEMORY MANAGER received an error when writing a page to secondary storage.
1124
MESSAGE
The MEMORY MANAGER received an error when it attempted to RECEIVE from its I/O notification port.
1125
MESSAGE
A block of physical pages which the MEMORY MANAGER tried to make
memory-resident contained a page which was not present.
1126
MESSAGE
The critical PAGE POOL is empty.
1127
MESSAGE
The MEMORY MANAGER was unable to REPLENISH the critical PAGE POOL.
1128
MESSAGE
The MEMORY MANAGER received an error when it attempted to RECEIVE from its I/O notification port.
1129
MESSAGE
The MEMORY MANAGER could not find a memory-resident PAGE entry in the PDIRX.
1130
MESSAGE
The MEMORY MANAGER could not find a memory-resident PAGE entry in the PDIRX.
1131
MESSAGE
The MEMORY MANAGER was unable to get a PDIR entry from TABLE MANAGEMENT.
1132
MESSAGE
Inserting an entry at the head of a chain in the KO HASH TABLE is the only supported method.
1133
MESSAGE
Inserting an entry at the head of a chain in the PSEUDO PRESENT HASH TABLE is the only supported method.
1134
MESSAGE
The MEMORY MANAGER was unable to lock the PDIRX when attempting to CHANGE a page to a recoverable overlay candidate.
1135
MESSAGE
A user-requested WRITE is in progress on a stack page above SP.
1136
MESSAGE
An error was detected while trying to send a message to the MEMORY MANAGER PAGE filler port.
1137
MESSAGE
The MEMORY MANAGER detected an error while trying to get a clean page to add to the filled page pool.
1138
MESSAGE
An error was detected whie trying to RECEIVE a message from the MEMORY MANAGER PAGE filler port.
1139
MESSAGE
The MEMORY MANAGER was unable to LOCK to PDIRX.
1140
MESSAGE
The MEMORY MANAGER detected an error while attempting to WRITE pages to secondary storage.
1141
MESSAGE
The MEMORY MANAGER can not find a page which has not been referenced since the last traverse of physical memory.
1142
MESSAGE
The MEMORY MANAGER was unable to LOCK the PDIRX.
1143
MESSAGE
The MEMORY MANAGER was unable to LOCK the PDIRX.
1144
MESSAGE
The MEMORY MANAGER encountered a STACK OVERFLOW while trying to handle a STACK OVERFLOW condition.
1145
MESSAGE
The MEMORY MANAGER was unable to ADD a page to a process's minimum locality.
1146
MESSAGE
The MEMORY MANAGER detected an error while trying to get PLABEL information about a system entry point.
1147
MESSAGE
The MEMORY MANAGER was unable to CREATE an object in the safe stack.
1148
MESSAGE
The MEMORY MANAGER was unable to lock an object in the safe stack.
1149
MESSAGE
The MEMORY MANAGER attempted to MAP in a VIRGIN page which was
already in the process of being mapped in from secondary storage.
1150
MESSAGE
The TOS of STACK POINTER (SP) is not word-aligned.
1151
MESSAGE
The MEMORY MANAGER was unable to FREEZE pages in the SAFE stack.
1152
MESSAGE
The MEMORY MANAGER was unable to release an object from the SAFE stack.
1153
MESSAGE
A PAGE fault which was no a TOS trap occurred while interrupts were disabled.
1154
MESSAGE
A PAGE fault occurred while the DISABLED TOS trap count was nonzero.
1156
MESSAGE
The MEMORY MANAGER was unable to get an entry from the GREY PAGE TABLE.
1157
MESSAGE
The physical PAGE POOL used for mapping in TOS pages was empty.
1158
MESSAGE
The MEMORY MANAGER was unable to get an entry from the GREY PAGE TABLE.
1159
MESSAGE
A virtual page which should have been frozen in memory was found to be absent.
1160
MESSAGE
The MEMORY MANAGER was unable to LOCK a portion of the process stack in the VPN cache.
1161
MESSAGE
The MEMORY MANAGER was unable to get a valid PLABEL from the loader.
1163
MESSAGE
FETCH pages could not obtain the resources that it needs.
1164
MESSAGE
FETCH PAGES out of service clean up has detected an inconsistency.
1165
MESSAGE
An attempt was made to FREEZE a virtual page which was not mapped into physical memory.
1166
MESSAGE
An attempt was made to UNFREEZE a virtual page which was not mapped into physical memory.
1167
MESSAGE
The MEMORY MANAGER either was given a bad locality list entry number, or found a bad entry in the locality list.
1168
MESSAGE
The MEMORY MANAGER's semaphore for this page is already locked. This should not occur in a uni-processor environment.
1169
MESSAGE
A frozen page is absent.
1170
MESSAGE
A frozen page is absent.
1171
MESSAGE
An uninitialized semaphore is used in a lock request.
1172
MESSAGE
An attempt was made to lock the stack below the currently locked area.
1174
MESSAGE
We were asked to map in a page for a page that was present.
1175
MESSAGE
If we force a KO page absent, it should have a present version.
1176
MESSAGE
An error was detected in changing from VPS to KO.
1177
MESSAGE
The PDIRX entry could not be locked.
1178
MESSAGE
SEND MESSAGE failed in background posts.
1179
MESSAGE
A bug occurred in stale page bug catcher.
1180
MESSAGE
Page VP state detected in CHANGE VPS STATE.
1181
MESSAGE
MM_TT_ZERO_VALUED_FIRST_INTERRUPT_MKR for MEMORY MANAGER.
CAUSE
First CM interrupt marker in TCB is set to zero.
1187
MESSAGE
di_mm_alloc received bad status from send_io.
1188
MESSAGE
di_mm_alloc received bad status from extend_receive.
1190
MESSAGE
The unsupported procedure alias_vp was called.
1193
MESSAGE
psuedo_map io attempted on a swappable or non-present page.
1197
MESSAGE
Bad status returned from reserve_page_for_gp_use.
1199
MESSAGE
Bad status returned from notify_dispatcher while doing pseudo mapped io.
System Abort Errors 1200 - 1474
1200
MESSAGE
Bad completion status while doing pseudo mapped io.
1201
MESSAGE
A ko_ipdir or an imi_ipdir entry has a bad virtual address.
1203
MESSAGE
Could not change the state of a page.
1204
MESSAGE
page in the page deallocation table with a double bit error could not be put on the unuseable_list.
1205
MESSAGE
Some critical code locations could not be modified.
1206
MESSAGE
A call to pdc_model to get processor version information failed.
1207
MESSAGE
pdc would occupy greater than 4 mb in memory.
1208
MESSAGE
The black hole page is in high memory, > 4gb.
1209
MESSAGE
Bad data received from pdc_pat_mem.
1210
MESSAGE
build_mm_osinfo received bad status from allocate_osinfo_entry.
1300
MESSAGE
The procedure CREATE_PROCESS_SWITCH_OBJ is unable to create process SWITCH OBJECT.
CAUSE
Unable to create an object for the CM procedure name to the plabel table.
1301
MESSAGE
The procedure CREATE_PROCESS_SWITCH_OBJ is unable to create HASH TABLE.
CAUSE
Unable to create the CM procedure name to the plabel table.
1302
MESSAGE
The procedure ALLOCATE_CM_PROCEDURE received bad status from SWITCH_TO_CM.
CAUSE
SWITCH_TO_CM could not call LOADPROC.
1303
MESSAGE
The procedure DEALLOCATE_CM_PROCEDURE received bad status from SWITCH_TO_CM.
CAUSE
SWITCH_TO_CM could not call UNLAODPROC.
1304
MESSAGE
The procedure DELETE_SCM_HASH_ENTRY failed to find entry.
CAUSE
Could not find a name in the CM procedure name to plabel table.
1305
MESSAGE
The procedure DELETE_SCM_HASH_ENTRY received bad status from RELEASE_TABLE_ENTRY.
CAUSE
A table management error occured while releasing a table entry in the CM procedure to the plabel table.
1306
MESSAGE
The procedure GET_PROCESS_SCM_PLABEL received bad status from RELEASE_TABLE_ENTRY.
CAUSE
A table management error occured while releasing a table entry in the CM procedure name to the plabel table.
1307
MESSAGE
The procedure SWITCH_TO_CM received bad status from RELDATSEG.
CAUSE
Unable to release a data segment previously created in SWITCH_TO_CM.
1320
MESSAGE
TIMER entry had an illegal state.
1321
MESSAGE
The current process had no standard signal port.
CAUSE
GET_TIMEREQ: get_global_port_num returned no number for the standard signal port.
1322
MESSAGE
An invalid code was received from compatibility TIMEREQ.