 |
» |
|
|
|
|  | |
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.
| | | | |
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- CAUSE
GET_TIMEREQ: invalid timer code parameter received.
- 1323
- MESSAGE
Bad TABLE MANAGEMENT status was received when the timer entry was released.
- 1324
- MESSAGE
The current process had no standard signal port.
- CAUSE
PROC_PAUSE: get_global_port_num returned no number for the standard signal port.
- 1325
- MESSAGE
The procedure INITIALIZE_TIMERS failed to create TIMER ENTRY TABLE.
- CAUSE
The call to create_table failed.
- 1326
- MESSAGE
The procedure INITIALIZE_TIMERS failed to create TIMER global area.
- CAUSE
The call to create_object failed.
- 1327
- MESSAGE
PDC TOD read failed.
- CAUSE
PDC_TIME: call to get_pdc_tod failed.
- 1328
- MESSAGE
PDC TOD write failed.
- CAUSE
SET_PDC_TIME: call to pdc_access_4 failed.
- 1329
- MESSAGE
Can not read PDC TOD calib.
- CAUSE
PDC_TIMER_CAL: call to get_pdc_timer failed.
- 1330
- MESSAGE
Can not read PDC TOD calib.
- CAUSE
PDC_TIMER_ACC: call to get_pdc_timer failed.
- 1331
- MESSAGE
CLOCK_SYNC WRITE failed.
- CAUSE
SYBC_CLOCKS: call to set_pdc_timer failed.
- 1332
- MESSAGE
The procedure failed to create port for clock sync.
- CAUSE
INIT_HARDWARE_CLOCK_UPDATES: call to create_port failed.
- 1333
- MESSAGE
The procedure failed to get TIMER for clock sync.
- CAUSE
INIT_HARDWARE_CLOCK_UPDATES: call to get_timer failed.
- 1334
- MESSAGE
Clock failed to notify a port of a clock interrupt.
- CAUSE
TIMER_INTERRUPT HANDLER: call to send_msg failed and the system was not in the shutdown state.
- 1335
- MESSAGE
An attempt was made to release timer entry zero.
- CAUSE
RELEASE_TIMER: timer entry zero was received as an input parameter.
- 1340
- MESSAGE
A high priority machine check occurred.
- 1341
- MESSAGE
A low priority machine check occurred.
- 1342
- MESSAGE
ILLEGAL INSTRUCTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1343
- MESSAGE
ILLEGAL INSTRUCTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1344
- MESSAGE
A BREAK instruction occurred on the INTERRUPT CONTROL STACK (ICS).
- 1345
- MESSAGE
PRIVILEGED OPERATION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1346
- MESSAGE
PRIVILEGED REGISTER TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1347
- MESSAGE
OVERFLOW TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1348
- MESSAGE
CONDITIONAL TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1349
- MESSAGE
ASSIST EXCEPTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1350
- MESSAGE
DATA MEMORY PROTECTION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1351
- MESSAGE
CM STACK OVERFLOW procedure occurred while DISABLED OR PDISABLED.
- 1352
- MESSAGE
CM STACK OVERFLOW occurred while handling CM STACK OVERFLOW.
- 1353
- MESSAGE
CM STACK OVERFLOW failed to change break range.
- 1355
- MESSAGE
ASSIST EMULATION TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1356
- MESSAGE
HIGH PRIVILEGE TRANSFER TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1357
- MESSAGE
LOW PRIVILEGE TRANSFER TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1358
- MESSAGE
TAKEN BRANCH TRAP occurred while on the INTERRUPT CONTROL STACK (ICS).
- 1360
- MESSAGE
CREATE_TABLE failed.
- CAUSE
CREATE_MIB: bad status from create_table.
- 1361
- MESSAGE
One or more parameters are bad.
- ACTION
Check for correct options before calling get_short_int_entry.
- 1362
- MESSAGE
Bad MIB address.
- ACTION
Check that mib_state is allocated_mib before calling rel_short_int_entry.
- 1365
- MESSAGE
Bad status returned for GET_TABLE entry.
- 1366
- MESSAGE
Bad status returned from FAST_RELEASE_TABLE_ENTRY.
- CAUSE
REL_SHORT_INT_ENTRY: bad status from tbl_fast_release_table_entry.
- 1367
- MESSAGE
Bad status returned from FAST_RELEASE_TABLE ENTRY.
- CAUSE
REL_LONG_INT_ENTRY: bad status from release_table_entry.
- 1380
- MESSAGE
External interrupt handler failed to initialize its EXTERNAL INTERRUPT TABLE (EXT_INT_TABLE).
- CAUSE
There is a problem with VSM in CREATE_OBJECT interface.
- 1401
- MESSAGE
Can not send interrupt message to the system.
- CAUSE
SEND MESSAGE failure.
- 1410
- MESSAGE
Could not create the system logging globals area.
- CAUSE
LOG process could not successfully create the system logging global object.
- 1411
- MESSAGE
The procedure could not get standard message port for the system logging process.
- CAUSE
LOG process could not get standard message port.
- 1412
- MESSAGE
The current system log file and its label are inconsistent.
- CAUSE
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.
- 1421
- MESSAGE
Internal table pool resource is corrupted.
- 1422
- MESSAGE
Internal table entry link is corrupted in the procedure REL_LONG_MIB_ENTRY.
- 1423
- MESSAGE
Internal table entry link is corrupted in the procedure REL_SHORT_MIB_ENTRY.
- 1451
- MESSAGE
A process is executing the procedure PM_CLEANUP other than the process MANAGEMENT CLEANUP process.
- 1452
- MESSAGE
After the system has completed its boot up, an attempt to make selected system process stacks swappable failed.
- 1453
- MESSAGE
After the system has completed its boot up, an attempt to lock the system processes stacks in the VPN cache failed.
- 1454
- MESSAGE
During system boot, an attempt to create the CLEANUP process failed.
- 1455
- MESSAGE
A process holding a SIR has been terminated.
- 1456
- MESSAGE
The trap handling procedure encountered a trap while processing a trap.
- 1457
- MESSAGE
A system process is being terminated due to a trap.
- 1458
- MESSAGE
A critical process is being terminated due to a trap.
- 1459
- MESSAGE
A trap occurred on a process whose state is not ALIVE.
- 1460
- MESSAGE
We are terminating a process whose state is not ALIVE.
- 1461
- MESSAGE
We continued to execute in TERMINATE_PROCESS after giving up the CPU.
- 1462
- MESSAGE
While the system is booting, we were unable to obtain a pointer to the PCB TABLE (CONVERT_DST).
- 1463
- MESSAGE
While the system was booting, we were unable to initialize the port for the BOOT process (SETUP_PORTS).
- 1464
- MESSAGE
While the system was booting, a release object failed on the temporary PIB for the BOOT process (RELEASE_OBJECT).
- 1465
- MESSAGE
While the system was booting, we were unable to allocate a process ID for the BOOT process (ALLOCATE_PID).
- 1466
- MESSAGE
While the system was booting, we were unable to schedule the BOOT process for execution (NOTIFY_DISPATCHER).
- 1467
- MESSAGE
While the system was booting, we were unable to allocate space in BANK 0 for the PCB TABLE (ALLOC_B0_SUB_OBJECT).
- 1468
- MESSAGE
While the system was booting, we were unable to get a long pointer to the PCB TABLE (CONVERT_DST).
- 1469
- MESSAGE
While the system was booting, we were unable to create the PCB TABLE within the PCB SUB-OBJECT (CREATE_TABLE).
- 1470
- MESSAGE
While the system was booting, we were unable to CREATE the PIB TABLE.
- 1471
- MESSAGE
While the system was booting, we were unable to allocate a data segment for the
PROCESS/JOB CROSS REFERENCE TABLE (ALLOCATE_DST).
- 1472
- MESSAGE
While the system was booting, we were unable to obtain a pointer for the PROCESS/JOB CROSS REFERENCE TABLE (CONVERT_DST).
- 1473
- MESSAGE
While the system was booting, we were unable to create the PROCESS ID LIST (CREATE_TABLE).
- 1474
- MESSAGE
While the system was booting, we were unable to create the PROTECT ID LIST (CREATE_TABLE).
- 1475
- MESSAGE
While the system was booting, we were unable to create a virtual space domain for the temporary PIB and PIBX TABLES (CREATE_VIRTUAL_SPACE_DOMAIN).
- 1476
- MESSAGE
While the system was booting, we were unable to create a temporary PIB TABLE (CREATE_OBJECT).
- 1477
- MESSAGE
While the system was booting, we were unable to create a temporary PIBX TABLE (CREATE_TABLE).
- 1478
- MESSAGE
While the system was booting, we were unable to build PROGENS CM STACK (BUILD_CM_STACK).
- 1479
- MESSAGE
While the program was booting, we were unable to obtain a pointer to PROGENS STACK (CONVERT_DST).
- 1480
- MESSAGE
While the system was booting, we were unable to determine the size of the PROGENS STACK (GET_DST_SIZE).
- 1481
- MESSAGE
While the system was booting, we were unable to set the size of the PROGENS STACK (MAX_DST_SIZE).
- 1482
- MESSAGE
An attempt is being made to set a process's critical depth count to less than zero.
- 1483
- MESSAGE
An attempt is being made to set a process's system code depth to less than zero.
- 1484
- MESSAGE
The value of the OLDSTATE parameter passed to RESETCRITICAL is invalid.
- 1485
- MESSAGE
The recover block in a PROCESS MANAGEMENT intrinsic encountered an unexpected escape code.
- 1486
- MESSAGE
A trap occurred in the operating system during system boot.
- 1487
- MESSAGE
A trap occurred while a process was terminating.
- 1501
- MESSAGE
The procedure PROCESS_SYSTEM_FETCH_PAGES_MSG caused bad status from FETCH_PAGES.
- 1502
- MESSAGE
The procedure PROCESS_FETCH_IO_PAGES_MSG caused bad status from SWAP_IN.
- 1503
- MESSAGE
The procedure DISP_TIMER_SERVER caused quantum to expire; NOTIFY_DISPATCHER returned bad status.
- 1504
- MESSAGE
The procedure AWAKEN_PROCESS caused unexpected BLOCKED_REASON.
- 1505
- MESSAGE
The procedure BLOCK_CURRENT_PROCESS caused BLOCK_EVENT in DSP_MEMORY_WAIT; bad build.
- 1506
- MESSAGE
The procedure BLOCK_CURRENT_PROCESS caused the request to block on memory WAIT.
- 1507
- MESSAGE
The procedure NOTIFY_DISPATCHER means NOTIFY DISPATCHER is called with nil PIN.
- 1508
- MESSAGE
The procedure NOTIFY_DISPATCHER is unable to set the watchdog timer to prevent runaway CPU usage; unexpected status from RESET_TIMER.
- 1509
- MESSAGE
The procedure SET_PROC_SCHEDULING_CLASS caused bad status from NOTIFY_DISPATCHER.
- 1510
- MESSAGE
The procedure FORMAT_DISPATCHER_GLOBALS can not get a timer entry for the timeslice watchdog; bad status from GET_TIMER.
- 1511
- MESSAGE
The procedure X_INITIALIZE_DISPATCHER can not create the dispatcher timer port; error from CREATE_PORT.
- 1512
- MESSAGE
The procedure SWAP_IN_PROCESS (initiate_swap_in) caused an unknown status from SWAP_IN.
- 1513
- MESSAGE
Processes are ready to be launched but the DISPATCHER is missing them.
- 1514
- MESSAGE
The procedure PROCESS_DISPATCHER_MSGS can not receive the dispatcher message to the process; unknown status from RECEIVE_MSG.
- 1515
- MESSAGE
The procedure EXAMINE_ACTIVE_PROCESS caused a long waited process on the dispatcher queue.
- 1516
- MESSAGE
NOTIFY_DISPATCHER requests to change priority of a
dead process.
- CAUSE
An attempt was made to change priority of a dead
process.
- 1517
- MESSAGE
Unknown request to NOTIFY_DISPATCHER.
- CAUSE
An unknown DISPATCH request has been sent to NOTIFY_DISPATCHER.
- 1701
- MESSAGE
UPDATE_SYSTEM_QUAD_ALLOCATION_MAP - The counters which hold the number of units in the free or allocated state went below zero.
- 1702
- MESSAGE
ALLOCATE_SYS_QUAD_SPACE - The call to UPDATE THE ALLOCATION MAP returned a bad status.
- 1703
- MESSAGE
DEALLOCATE_SUB_SR6_SR7_SPACE - The call to UPDATE ALLOCATION MAP returned a bad status.
- 1704
- MESSAGE
DEALLOCATE_SUB_SR6_SR7 - The quad of the address to DEALLOCATE was not SR6 or SR7.
- 1705
- MESSAGE
INIT_ALLOCATION-INFO of INIT_VIRTUAL SPACE_MANAGEMENT - An invalid status was returned from the ALLOCATION routine when attempting to mark the space
assigned to the BOOT objects allocated.
- 1706
- MESSAGE
CREATE_VSM_OBJECT of INIT VIRTUAL_SPACE MANAGEMENT - An invalid status was returned from the ALLOCATION routine when attempting to allocate a space for
a VSM object.
- 1707
- MESSAGE
INIT_ALLOCATION_ INFO of INIT_VIRTUAL_SPACE_MANAGEMENT - An invalid status was
returned when calling the ALLOCATION MAP UPDATE routine to mark the unavailable space at the end of the quad as allocated.
- 1708
- MESSAGE
DEL_FROM_LOCALITY_TABLE - The entry requested to be deleted from the INDIRECT LOCALITY TABLE was not found.
- 1709
- MESSAGE
VSM_LOAD_CODE_FILE - This code file has already been loaded as a single SOM file. The maximum number of SOMs specified in the previous load was 1.
- 1710
- MESSAGE
VSM_LOAD_CODE_FILE - The object for this file was created with variable access rights, and the loader specified single access rights in the parameters to this
procedure.
- 1711
- MESSAGE
VSM_UNLOAD_CODE_FILE - No object was found which contains the pointer to the file to unload.
- 1712
- MESSAGE
VSM_UNLOAD_CODE_FILE - The specified code file was not previously loaded using VSM_LOAD_CODE_FILE.
- 1713
- MESSAGE
VSM_UNLOAD_CODE_FILE - There was an error status returned when the INIT POINTER (LOCALITY) TABLE was attempted to be locked into the VPN cache.
- 1714
- MESSAGE
VSM_UNLOAD_CODE_FILE - An error was returned from the RELEASE_OBJECT call when attempting to release the INDIRECT LOCALITY TABLE.
- 1715
- MESSAGE
PAGE_FLT_LOCK_IN_VPN_CACHE - The recover block for this procedure was unexpectedly entered.
- 1716
- MESSAGE
INIT_2_VIRTUAL_SPACE MANAGEMENT - An error occurred when making the VS allocation information object swappable.
- 1717
- MESSAGE
UNLOCK_RANGE_FROM_CACHE - The VPN and length to unlock was outside of the bounds of the cache entry pointer that was passed in.
- 1722
- MESSAGE
TRANSLATE_VSM_TABLE_ERROR - Received an error from TABLE MANAGEMENT that is not a recoverable error. The table may be corrupted.
- 1723
- MESSAGE
TRANSLATE_VSM_TABLE_ERROR - Received an error from TABLE MANAGEMENT that is not an error expected for the particular table, such as no secondary storage for a
resident table.
- 1724
- MESSAGE
RELEASE_VSM_TABLE_ENTRY - An error occurred releasing a table entry; table may be corrupt.
- 1725
- MESSAGE
GET_KSO_TABLE_ENTRY_PTR - An error was returned from GET_KJO_TABLE_PTR.
- 1726
- MESSAGE
GET_KSO_TABLE_ENTRY_PTR - An error was returned from GET_KPO_TABLE_PTR.
- 1727
- MESSAGE
GET_KSO_TABLE_ENTRY_PTR - This is an invalid KSO/KJO/KPO number.
- 1728
- MESSAGE
ANALYZE_BALANCE of DELETE_FROM_B_TREE - FATHER NODE is not the root of the B-TREE when it must be; B-TREE may be corrupt.
- 1729
- MESSAGE
BALANCE_ROOT of DELETE_FROM_B_TREE - The node count is not zero when it must be; B-TREE may be corrupt.
- 1730
- MESSAGE
DELETE_FROM_SUB_B_TREE of DELETE_FROM_B_TREE - the specified entry to delete is not in the B-TREE.
- 1731
- MESSAGE
ANALYZE_INSERTION of INSERT_IN_B_TREE - Illegal B-TREE detected. Node has no brothers when it must have them.
- 1732
- MESSAGE
INSERT_IN_SUB_TREE of INSERT_IN_B_TREE - Tried to insert a new node with a key that is already in the B-TREE.
- 1733
- MESSAGE
INSERT_IN_B_TREE - An error occurred while trying to recover from an error.
- 1734
- MESSAGE
SEARCH_EXTENT_B_TREE - VPN not found when it must be in the extent B-TREE.
- 1735
- MESSAGE
INSERT_IN_EXTENT_B_TREE - Extent bounds not within the bounds of the object.
- 1736
- MESSAGE
FLUSH_VA_RANGE - The object being flushed has dying object option set.
- 1737
- MESSAGE
FLUSH_VA_RANGE - An error occurred deallocating object.
- 1738
- MESSAGE
TRUNCATE_EXTENT_B_TREE - Tried to truncate a permanent, non-file object.
- 1739
- MESSAGE
TRUNCATE_EXTENT_B_TREE - FILE LABEL MANAGEMENT error occurred truncating a file
object.
- 1740
- MESSAGE
FILL_ALLOCATED_SEC_STORAGE - FILL_DISC returned an error.
- 1741
- MESSAGE
LOCK_VPN_CACHE - VPN cache is already locked. Recursive locking is not allowed.
- 1742
- MESSAGE
UNLOCK_FROM_VPN_CACHE - VPN cache is not locked.
- 1743
- MESSAGE
ALLOC_CACHE_ENTRY_HOLD_CB - An error was received from CB_INIT.
- 1744
- MESSAGE
ADD_TO_OVERLAY_LIST - Tried to add an entry to the VPN CACHE OVERLAY LIST that has a lock count that is not zero.
- 1745
- MESSAGE
REMOVE_FROM_OVERLAY_LIST - Found an entry on the VPN CACHE OVERLAY LIST with a lock count that is not zero.
- 1746
- MESSAGE
INSERT_IN_VPN_CACHE - The procedure tried to insert an entry in the VPN cache that was already there, and a duplicate entry recovery was not specified.
- 1747
- MESSAGE
DELETE_FROM_VPN_CACHE - The entry to delete was not found in the VPN cache.
- 1748
- MESSAGE
ALLOC_CACHE_ENTRY_QUEUE_CB - An error occurred allocating a VPN CACHE entry queue control block.
- 1749
- MESSAGE
ALLOC_CACHE_ENTRY_QUEUE_CB - Error from CB_INIT.
- 1750
- MESSAGE
QUEUE_ON_VPN_CACHE_ENTRY - The VPN cache entry already has a process queued on it being taken off of an overlay hold list. Only one process may be queued on
an entry.
- 1751
- MESSAGE
GET_OVERLAY_HEAD_ENTRY - Entry found on overlay list with a lock count that was not zero.
- 1752
- MESSAGE
MAYBE_UPDATE_DESCRIPTOR - A shared page VPN cache entry was found with an extent length that is not one.
- 1754
- MESSAGE
FIND_VPN_CACHE_ENTRY - The procedure was called when VPN cache is not locked.
- 1755
- MESSAGE
SCAN_VPN_CACHE - The procedure was called when VPN cache is not locked.
- 1756
- MESSAGE
MAP_OUT_CACHE_ENTRIES- A VPN cache entries' lock count will not go to zero after flushing the physical page and MEMORY MANAGER LOCALITY LIST, caused by the number of locks/unlocks on pages of this extent being out of sync.
- 1757
- MESSAGE
SET_UP_SHR_PAGE_DESC - An error was received from CB_INIT.
- 1758
- MESSAGE
ADD_TO_PAGE_SHR_DESC - The specified VPN does not match the VPN in the shared page descriptor.
- 1759
- MESSAGE
REMOVE_FROM_SHR_PAGE_DESC - The specified VPN does not match the VPN in the shared page descriptor.
- 1760
- MESSAGE
REMOVE_FROM_SHR_PAGE_DESC - The shared page use count will go negative.
- 1761
- MESSAGE
ALLOCATE_SHARED_VS_UNIT - Bad DO NOT PACK virtual address assigned.
- 1762
- MESSAGE
ADVANCE_SHARED_VS_UNIT - About to allocate a shared page descriptor for a page that already has one.
- 1763
- MESSAGE
LOCK_VS_DOMAIN_DESC - An error was returned from GET_KJO_TABLE_PTR.
- 1764
- MESSAGE
LOCK_VS_DOMAIN_DESC - An error was returned from GET_KPO_TABLE_PTR.
- 1765
- MESSAGE
DEALLOCATE_VS - The shared VS UNIT DESCRIPTOR ID was not supplied, and it should be.
- 1766
- MESSAGE
GET_DOMAIN_ENTRY - The shared VS UNIT DESCRIPTOR was already allocated for SR5
in this domain.
- 1767
- MESSAGE
ALLOCATE_VS_OD - An error was received from CB_INIT.
- 1768
- MESSAGE
DEALLOCATE_OBJECT - An error occurred releasing memory for a resident.
- 1769
- MESSAGE
CREATE_OBJECT_ERROR_CLEAN_UP of CREATE_OBJECT - An error occurred during error recovery.
- 1770
- MESSAGE
VSM_DEALLOCATE_GU_FD - The file object is not mapped out of virtual space.
- 1771
- MESSAGE
VSM_MAP_IN_FILE - The file object was already mapped into virtual space.
- 1772
- MESSAGE
VSM_MAP_IN_FILE - An error was received from CB_INIT.
- 1773
- MESSAGE
VSM_MAP_IN_FILE - An error occurred while doing error recovery.
- 1774
- MESSAGE
VSM_MAP_OUT_FILE - Map out on file with object dying option set.
- 1775
- MESSAGE
MAP_IN_EXTENT_MAP - An invalid extent descriptor was found in the file label.
- 1776
- MESSAGE
VSM_MAP_IN_LABEL_OBJ - An error was received from CB_INIT.
- 1777
- MESSAGE
VSM_MAP_IN_LABEL_OBJ - An error occurred doing error clean up.
- 1778
- MESSAGE
CALC_EXTENT_PLACEMENT of ALLOCATE_EXTENT - Bad placement was calculated.
- 1779
- MESSAGE
UPDATE_FIRST_SHARED_PAGE_DESC of ALLOCATE_EXTENT - The first shared page is already allocated.
- 1780
- MESSAGE
UPDATE_LAST_SHARED_PAGE_DESC of ALLOCATE_EXTENT - The first shared page is
already allocated.
- 1781
- MESSAGE
ALLOCATE_EXTENT - The VPN_TO_LEFT, VPN_TO_RIGHT, and VPN to allocate do not make sense.
- 1782
- MESSAGE
ALLOCATE_EXTENT - The extent that was allocated has bad virtual bounds.
- 1783
- MESSAGE
ALLOCATE_EXTENT - The current amount of secondary storage exceeds the maximum.
- 1784
- MESSAGE
ERROR_CLEANUP of ALLOCATE_VSM_OBJECT_EXTENT - Extent to clean up not found in
the VPN cache.
- 1785
- MESSAGE
CHECK_IF_IN_B_TREE of FIND_EXTENT_ENTRY - Extent not found in an EXTENT B-TREE when it must be there.
- 1786
- MESSAGE
FIND_EXTENT_ENTRY - The procedure tried to find an extent descriptor for a memory-resident object.
- 1787
- MESSAGE
FIND_EXTENT_ENTRY - The VPN to find the extent descriptor is not within the bounds of the object.
- 1788
- MESSAGE
FIND_EXTENT_ENTRY - Extent fault on VSM cache object.
- 1789
- MESSAGE
UNLOCK_RANGE_FROM_CACHE - The VPN not found in the VPN CACHE.
- 1790
- MESSAGE
DEC_CACHE_ENTRY_LOCK_COUNT - The lock count on a VPN cache entry will go negative.
- 1791
- MESSAGE
RETURN_VS_LL_HEADER_NUM - The range crosses the object bounds.
- 1792
- MESSAGE
GET_CODE_LOCALITY_BOUNDS - Bad locality range was found. The known locality that was found does not contain the page that was faulted on.
- 1793
- MESSAGE
PROCESS_REMEMBERED_CACHE_ENTRIES - Can not find a VPN cache entry that could not be kept in the local list and must be re-found.
- 1794
- MESSAGE
PAGE_FLT_LOCK_IN_VPN_CACHE - An MIB LIST was built that does not cover the range that is to be implicitly prefetched.
- 1795
- MESSAGE
UPDATE_MIB_STATE_FROM_CACHE - The VPN cache entry has a lock count of zero.
- 1796
- MESSAGE
ADD_TO_MIB_LIST - The procedure cannot allocate MIB and can not recover from
error.
- 1797
- MESSAGE
ICS_LOCK_IN_VPN_CACHE - A VPN in the range was not in the VPN cache.
- 1798
- MESSAGE
CACHED_VPN_TO_SECONDARY_ADDRESS - The VPN in the range was not in the VPN
cache.
- 1799
- MESSAGE
FLAG_PAGES_AS_VIRGIN - The VPN in the range was not in the VPN cache.
- 1801
- MESSAGE
ICS_BUILD_MIB_LIST - The VPN in the range was not found in the VPN cache.
- 1803
- MESSAGE
ICS_GET_EXTENT_MIB - The VPN was not found in the cache.
- 1804
- MESSAGE
MIB_UNLOCK_FROM_VPN_CACHE - The VPN cache entry lock count will go negative.
- 1805
- MESSAGE
TRUNCATE_SWAPPABLE_OBJECT - The starting offset of the truncation starts in the first shared page of the object and we did not decide to fill any bytes.
- 1806
- MESSAGE
TRUNCATE_SWAPPABLE_OBJECT - The procedure can not refind VS_OD for object. This is a higher level synchronization problem.
- 1807
- MESSAGE
GET_KPO_PTR - An error occurred, and return status was not supplied.
- 1808
- MESSAGE
SET_KPO_PTR - An error occurred, and return status was not supplied.
- 1809
- MESSAGE
GET_KJO_PTR - An error occurred, and return status was not supplied.
- 1810
- MESSAGE
SET_KJO_PTR - An error occurred, and return status was not supplied.
- 1811
- MESSAGE
UNLOCK_OBJECT_FROM_VPN_CACHE - An invalid pointer was specified.
- 1812
- MESSAGE
CREATE_VIRTUAL_SPACE_DOMAIN - An error was received from CB_INIT.
- 1813
- MESSAGE
VSM_SET_FILE_PID_HANDLING - The procedure called on a variable access rights
file, and this is not yet supported.
- 1814
- MESSAGE
DECODE_LOAD_OR_STORE - A logic error decoding instruction or bad instruction
was received.
- 1815
- MESSAGE
MEMORY_PROTECTION_TRAP - INSTRUCTION MEMORY PROTECTION TRAP not yet
implemented.
- 1816
- MESSAGE
MAKE_VSM_CACHED_OBJECT_SWAPPABLE - This is an invalid object pointer.
- 1817
- MESSAGE
MAKE_VSM_CACHED_OBJECT_SWAPPABLE - The object was not marked as will become
swappable.
- 1818
- MESSAGE
MAKE_VSM_CACHED_OBJECT_SWAPPABLE - An error occured allocating an extent for
the object.
- 1819
- MESSAGE
INIT_2_VIRTUAL_SPACE_MANAGEMENT - An error occurred making VS DOMAIN DESCRIPTOR
TABLE swappable.
- 1820
- MESSAGE
INIT_2_VIRTUAL_SPACE_MANAGEMENT - An error occurred making VS RECOVERY TABLE
swappable.
- 1821
- MESSAGE
CREATE_VSM_OBJECT of INIT_VIRTUAL_SPACE_MANAGEMENT - An error occurred
allocating main memory.
- 1822
- MESSAGE
ADD_VS_OD of INIT_VIRTUAL_SPACE_MANAGEMENT - An error occurred allocating
VS_OD.
- 1823
- MESSAGE
ADD_VS_OD of INIT_VIRTUAL_SPACE_MANAGEMENT - An error was received from
CB_INIT.
- 1824
- MESSAGE
ADD_VS_OD of INIT_VIRTUAL_SPACE_MANAGEMENT - An error was received from INSERT_IN_VS_B_TREE.
- 1825
- MESSAGE
CREATE_VSM_CONTROL_OBJ of INIT_VIRTUAL_SPACE_MANAGEMENT - An error was received
from CB_INIT.
- 1826
- MESSAGE
CREATE_VSM_CONTROL_OBJ of INIT_VIRTUAL_SPACE_MANAGEMENT - An error was received
from CB_INIT.
- 1827
- MESSAGE
CREATE_VSM_CONTROL_OBJECT of INIT_VIRTUAL_SPACE_MANAGEMENT - An error was
received from CB_INIT.
- 1828
- MESSAGE
CREATE_VSM_TABLE of INIT_VIRTUAL_SPACE_MANAGEMENT - CREATE_TABLE error
occurred.
- 1829
- MESSAGE
VALIDATE_COMPILE_CONSTANTS of INIT_VIRTUAL_SPACE_MANAGEMENT - The compile time
constants are out of sync.
- 1830
- MESSAGE
INIT_VIRTUAL_SPACE_MANAGEMENT - SR6 or SR7 must have specific space IDs.
- 1832
- MESSAGE
INIT_VIRTUAL_SPACE_MANAGEMENT - An error was received from CREATE_VIRTUAL_SPACE_DOMAIN.
- 1833
- MESSAGE
VSM_MAP_IN_SYS_LIB - VD_OD is already mapped in.
- 1834
- MESSAGE
VSM_MAP_IN_SYS_LIB - An error was received from ALLOCATE_VS_LL_HEADER.
- 1835
- MESSAGE
VSM_MAP_IN_SYS_LIB - An error was received from CB_INIT.
- 1836
- MESSAGE
VSM_MAP_IN_SYS_LIB - An error was received from INSERT_IN_VS_B_TREE.
- 1837
- MESSAGE
VSM_MAP_IN_SYS_LIB - An error was received from MAP_IN_EXTENT_MAP.
- 1838
- MESSAGE
VSM_MAP_IN_SYS_LIB - An error was received from
LOCK_IN_VPN_CACHE.
- 1839
- MESSAGE
CREATE_OSINFO_OBJECT - The CREATE OBJECT call failed when creating the operating system information object.
- 1840
- MESSAGE
BUILD_VSM_DATA_STRUCTURE_DESCRIPTION - The ALLOCATE_OSINFO_ENTRY call failed when attempting to allocate space in the operating system information object for the VSM DATA STRUCTURE DESCRIPTOR.
- 1841
- MESSAGE
PROBE_FILE_PIB_HANDLING - This procedure was called and the FILE ID parameter was specified. The object was neither OBJ_FILE_PID_HANDLING nor OBJ_PROCESS_PID_HANDLING.
- 1842
- MESSAGE
VSM_CLEAN_UP_FILE_USER - DELETE_PROTECTID was called to remove the PID of the file from the process's PID LIST. It returned a bad status.
- 1843
- MESSAGE
VPN_TO_SECONDARY_ADDRESS - The recover block caught an unexpected escape.
- 1844
- MESSAGE
SCAN_VS_OD_TABLE - The recover block caught an unexpected escape.
- 1845
- MESSAGE
GET_KPO_POINTER - The recover block caught an unexpected escape.
- 1846
- MESSAGE
SET_KPO_POINTER - The recover block caught an unexpected escape.
- 1847
- MESSAGE
GET_KJO_POINTER - The recover block caught an unexpected escape.
- 1848
- MESSAGE
SET_KJO_POINTER - The recover block caught an unexpected escape.
- 1849
- MESSAGE
GET_OBJECT_ATTRIBUTE - The recover block caught an unexpected escape.
- 1850
- MESSAGE
ALTER_OBJECT_SIZE - The recover block caught an unexpected escape.
- 1851
- MESSAGE
ALTER_OBJECT_SIZE_DISABLED - The recover block caught an unexpected escape.
- 1852
- MESSAGE
ALTER_OBJ_ACCESS_RIGHTS - The recover block caught an unexpected escape.
- 1853
- MESSAGE
ALTER_OBJECT_PROTECTION - The recover block caught an unexpected escape.
- 1854
- MESSAGE
LOCK_OBJ_IN_VPN_CACHE - The recover block caught an unexpected escape.
- 1855
- MESSAGE
UNLOCK_OBJ_FROM_VPN_CACHE - The recover block caught an unexpected escape.
- 1856
- MESSAGE
ALLOCATE_PID - The recover block caught an unexpected escape.
- 1857
- MESSAGE
DEALLOCATE_PID - The recover block caught an unexpected escape.
- 1858
- MESSAGE
CREATE_VIRTUAL_SPACE_DOMAIN - The recover block caught an unexpected escape.
- 1859
- MESSAGE
RELEASE_VIRTUAL_SPACE_DOMAIN - The recover block caught an unexpected escape.
- 1860
- MESSAGE
VSM_SET_FILE_PID_HANDLING - The recover block caught an unexpected escape.
- 1861
- MESSAGE
VSM_CLEAN_UP_FILE_USER - The recover block caught an unexpected escape.
- 1862
- MESSAGE
VSM_TRUNCATE_FILE - The recover block caught an unexpected escape.
- 1863
- MESSAGE
VSM_FILE_EOF_CUT_BACK - The recover block caught an unexpected escape.
- 1864
- MESSAGE
PROBE_OBJECT - The recover block caught an unexpected escape.
- 1865
- MESSAGE
MEMORY_PROTECTION_TRAP - The recover block caught an unexpected escape.
- 1866
- MESSAGE
VSM_GET_FILE_ATTRIBUTES - The recover block caught an unexpected escape.
- 1867
- MESSAGE
GET_CONTIGUOUS_BLOCK_INFO - The recover block caught an unexpected escape.
- 1868
- MESSAGE
SET_OBJECT_CLASS_DUMPWORTHY - The recover block caught an unexpected escape.
- 1869
- MESSAGE
ALLOCATE_OBJ_SEC_STORAGE - The recover block caught an unexpected escape.
- 1870
- MESSAGE
ALLOCATE_OSINFO_ENTRY - The recover block caught an unexpected escape.
- 1871
- MESSAGE
VSM_LOAD_CODE_FILE - The recover block caught an unexpected escape.
- 1872
- MESSAGE
VSM_UNLOAD_CODE_FILE - The recover block caught an unexpected escape.
- 1873
- MESSAGE
REATE_OBJECT - The recover block caught an unexpected escape.
- 1874
- MESSAGE
MAP_PERMANENT_OBJECT_EXTENT - The recover block caught an unexpected escape.
- 1875
- MESSAGE
RELEASE_OBJECT - The recover block caught an unexpected escape.
- 1876
- MESSAGE
VSM_ALLOCATE_GU_FD - The recover block caught an unexpected escape.
- 1877
- MESSAGE
VSM_DEALLOCATE_GU_FD - The recover block caught an unexpected escape.
- 1878
- MESSAGE
VSM_MAP_IN_FILE - The recover block caught an unexpected escape.
- 1879
- MESSAGE
VSM_MAP_OUT_FILE - The recover block caught an unexpected escape.
- 1880
- MESSAGE
VSM_MAP_IN_LABEL_OBJ - The recover block caught an unexpected escape.
- 1881
- MESSAGE
VSM_ADD_LABEL_EXTENTS - The recover block caught an unexpected escape.
- 1882
- MESSAGE
MAKE_OBJECT_SWAPPABLE - The recover block caught an unexpected escape.
- 1883
- MESSAGE
UNLOCK_FROM_VPN_CACHE - The recover block caught an unexpected escape.
- 1884
- MESSAGE
UNLOCK_FROM_VPN_CACHE_WITH_CACHE_ENTRY_PTR - The recover block caught an unexpected escape.
- 1885
- MESSAGE
CONVERT_OBJECT_CLASS - The recover block caught an unexpected escape.
- 1886
- MESSAGE
VSM_MAP_IN_SYS_LIB - The recover block caught an unexpected escape.
- 1887
- MESSAGE
PAGE_FLT_LOCK_IN_VPN_CACHE - The recover block caught an unexpected escape.
- 1888
- MESSAGE
ICS_LOCK_IN_VPN_CACHE - The recover block caught an unexpected escape.
- 1889
- MESSAGE
FLAG_PAGE_AS_NOT_VIRGIN - The recover block caught an unexpected escape.
- 1890
- MESSAGE
FLAGS_PAGES_AS_VIRGIN - The recover block caught an unexpected escape.
- 1891
- MESSAGE
CACHED_VPN_TO_SECONDARY_ADDRESS - The recover block caught an unexpected escape.
- 1892
- MESSAGE
ICS_BUILD_MIB_LIST - The recover block caught an unexpected escape.
- 1893
- MESSAGE
BUILD_WRITE_MIB_LIST - The recover block caught an unexpected escape.
- 1894
- MESSAGE
ICS_GET_EXTENT_MIB - The recover block caught an unexpected escape.
- 1895
- MESSAGE
UPDATE_MIB_FROM_VPN_CACHE - The recover block caught an unexpected escape.
- 1896
- MESSAGE
MIB_LOCK_VIRGIN_IN_VPN_CACHE - The recover block caught an unexpected escape.
- 1897
- MESSAGE
MIB_UNLOCK_FROM_VPN_CACHE - The recover block caught an unexpected escape.
- 1898
- MESSAGE
GET_VPN_CACHE_ENTRY_PTR - The recover block caught an unexpected escape.
- 1899
- MESSAGE
LOCK_IN_VPN_CACHE - The recover block caught an unexpected escape.
- 1900
- MESSAGE
COUNT_MAIN_MEM_PAGES - The recover block caught an unexpected escape.
- 1901
- MESSAGE
GET_NEXT_SR5_OFFSET - The recover block caught an unexpected escape.
- 1902
- MESSAGE
VSM_UNLOAD_ENTIRE_CODE_FILE - The recover block caught an unexpected escape.
- 1903
- MESSAGE
INIT_2_VIRTUAL_SPACE_MANAGEMENT - An error was returned from processing all
VS_ODs to make swappable and convert the access rights.
- 1904
- MESSAGE
FIND_EXTENT_ENTRY - A duplicate extent or an out of bounds extent occurred during the extent allocation of a non-file object.
- 1905
- MESSAGE
In FIND_EXTENT_ENTRY, a duplicate extent or an out of bounds extent occurred during the extent allocation of a non-file object.
- 1906
- MESSAGE
In INIT_2_VIRTUAL_SPACE_MANAGEMENT, an error was returned from processing all
VS_ODs to make all swappable objects swappable.
- 1907
- MESSAGE
The extent B-TREE node count went to zero.
- 1908
- MESSAGE
The entry is already on the overlay list.
- 1909
- MESSAGE
The entry is not on the overlay list.
- 1910
- MESSAGE
The entry is on the overlay list.
- 1911
- MESSAGE
A memory protection trap occurred for which there is no remedy.
- CAUSE
There is a bug in the protection mechanism.
- 2000
- MESSAGE
POST_PAGE_MAP - An error was received from PORT.
- 2001
- MESSAGE
GET_EXTENT_OF_SEC_STORAGE - An error was received updating PAGE MAP.
- 2002
- MESSAGE
ALLOCATE_SEC_STORAGE - An error was received from FILL_DISC.
- 2003
- MESSAGE
DEALLOCATE_SEC_STORAGE - A bad parameter was specified.
- 2004
- MESSAGE
GET_SPECIFIC_SET_STORAGE - A bad parameter was specified.
- 2005
- MESSAGE
GET_SPECIFIC_SEC_STORAGE - An error was returned updating PAGE MAP.
- 2006
- MESSAGE
UPDATE_PARTIAL_PAGE_INDICATORS - All fragments are not free and should be.
- 2007
- MESSAGE
UPDATE_PARTIAL_PAGE_INDICATORS - An error occurred updating PAGE MAP.
- 2008
- MESSAGE
UPDATE_PARTIAL_PAGE_INDICATORS - The page is not a permanent page and it should be.
- 2009
- MESSAGE
UPDATE_PARTIAL_PAGE_INDICATORS - The page is not a partial page and it should be.
- 2010
- MESSAGE
SEARCH_FOR_FRAGMENT - No fragment was found and there should be one.
- 2011
- MESSAGE
FIND_PARTIAL_PAGE_FREE - An error occurred updating PAGE MAP.
- 2012
- MESSAGE
GET_PARTIAL_PAGE - The fragment size is greater than the page size.
- 2013
- MESSAGE
REL_PARTIAL_PAGE_OF_SEC_STORAGE - A bad parameter was specified.
- 2014
- MESSAGE
REL_PARTIAL_PAGE_OF_SEC_STORAGE - The fragment was already free.
- 2015
- MESSAGE
FORMAT_SEC_STORAGE_MAP - FILL_DISC error occurred.
- 2016
- MESSAGE
FORMAT_SEC_STORAGE_MAP - A partial PAGE MAP POST error occurred.
- 2017
- MESSAGE
FORMAT_SEC_STORAGE_MAP - PAGE MAP and HEADER POST error occurred.
- 2018
- MESSAGE
REMOVE_RESERVED_SEC_STORAGE - An error occurred updating the map.
- 2019
- MESSAGE
CREATE_SSM_MAP_OBJECTS - The map address is not on the page boundary.
- 2020
- MESSAGE
CREATE_SSM_MAP_OBJECTS - An error occurred while doing an error clean up.
- 2021
- MESSAGE
MARK_SSM_MAP - An error was received from POST.
- 2022
- MESSAGE
INIT_SSM_DEV_INFO_AREA - VLM_GET_SSM_DEV_AREA error occurred.
- 2023
- MESSAGE
INIT_SSM_DEV_INFO_AREA - CB_INIT error occurred.
- 2024
- MESSAGE
MOUNT_SSM_DEVICE - An error occurred creating map objects.
- 2025
- MESSAGE
MOUNT_SSM_DEVICE - An error occurred releasing PAGE MAP object.
- 2026
- MESSAGE
MOUNT_SSM_DEVICE - An error occurred releasing partial PAGE MAP object.
- 2027
- MESSAGE
DISMOUNT_SSM_DEVICE - An error occurred releasing PAGE MAP object.
- 2028
- MESSAGE
DISMOUNT_SSM_DEVICE - An error occurred releasing partial PAGE MAP object.
- 2029
- MESSAGE
INIT_SSM_DEVICE - An error occurred creating map objects.
- 2030
- MESSAGE
INIT_SSM_DEVICE - An error occurred replaying log.
- 2031
- MESSAGE
CHANGE_SSM_DEVICE_LIMITS - An error was received from POST.
- 2032
- MESSAGE
GET_FREE_SPACE_HISTOGRAM - An error was received from PREFETCH.
- 2033
- MESSAGE
REMAP_SSM_MAP - An error occurred in creating the objects for the new SSM MAP.
- 2034
- MESSAGE
REMAP_SSM_MAP - An error occurred when updating the disk volume label with the
sector offset of the new SSM MAP.
- 2035
- MESSAGE
UPDATE_SEC_STORAGE_MAP - One of the page counters went negative after the secondary storage map was updated. This is currently a bug catcher, but may
become permanent.
- 2036
- MESSAGE
VALIDATE_SEC_STORAGE - This is a bad LDEV parameter.
- 2037
- MESSAGE
VALIDATE_SEC_STORAGE - This is a bad DISC_ADDRESS parameter.
- 2038
- MESSAGE
VALIDATE_SEC_STORAGE - The parameter number of bytes is less than zero.
- 2039
- MESSAGE
VALIDATE_SEC_STORAGE - The ending page to be validated exceeded the last page of the device.
- 2040
- MESSAGE
VALIDATE_SEC_STORAGE - The number of byte MOD PAGE_SIZE is not zero.
- 2041
- MESSAGE
VALIDATE_SEC_STORAGE - The page being validated was not a permanent page.
- 2042
- MESSAGE
VALIDATE_SEC_STORAGE - A trap occurred during VALIDATE_SEC_STORAGE.
- 2043
- MESSAGE
SSM_REPLAY_LOG - A trap occurred while XM was recovering the SSM MAP.
- 2044
- MESSAGE
DISMOUNT_SSM_DEVICE - A trap occurred during DISMOUNT_SSM_DEVICE.
- 2045
- MESSAGE
SSM_VERIFY_MAPS_FOR_MOUNTED_SYS_VOLS page counts in map header does not match
the bit map count.
- 2046
- MESSAGE
SSM_SA_VERIFY_ENTIRE_MAP - An error was received from PREFETCH in SSM_SA_VERIFY_ENTRE_MAP.
- 2047
- MESSAGE
SSM_SA_INIT_SSM_GLOBAL_AREA - CB_INIT failed.
- 2048
- MESSAGE
SSM_SA_INIT_SSM_GLOBAL_AREA - CREATE_OBJECT failed.
- 2049
- MESSAGE
SSM_SA_UPDATE_SEC_STORAGE_MAP - VERIFY_MAP failed.
- 2050
- MESSAGE
UPDATE_SEC_STORAGE_MAP - One of the page counters went negative before the SECONDARY STORAGE MAP was updated. This is currently a bug catcher, but may
become permanent.
- 2051
- MESSAGE
UPDATE_SEC_STORAGE_MAP - UPDATE_SEC_STORAGE_MAP failed.
- 2100
- MESSAGE
A general system abort occurred for XM (used only until new aborts are added to DSYSFAIL).
- 2101
- MESSAGE
The procedure XM_RECOVERY detected an unknown record type in an XM log.
- 2102
- MESSAGE
The procedure XM_RECOVERY received bad status from SM_OPEN_FD.
- 2103
- MESSAGE
The procedure XM_RECOVERY received bad status from SM_OPEN_OBJECT.
- 2104
- MESSAGE
The procedure XM_CLOSE_RESIDUAL received bad status from SM_CLOSE.
- 2105
- MESSAGE
The procedure XM_CLOSE_RESIDUAL received bad status from POST.
- 2106
- MESSAGE
The procedure XM_RECOVERY detected key is not in the HASH TABLE.
- 2107
- MESSAGE
The procedure XM_RECOVERY_POST_AND_CLOSE received bad status from SM_CLOSE.
- 2108
- MESSAGE
The procedure XM_RECOVERY_POST_AND_CLOSE received bad status from POST.
- 2109
- MESSAGE
The procedure XM_RECOVERY_SETUP detected a failure in CREATE_OBJECT.
- 2110
- MESSAGE
The procedure XM_RECOVERY_SETUP detected a failure in LM_GET_MAGIC_UFID.
- 2111
- MESSAGE
The procedure XM_RECOVERY_SETUP detected a failure in SM_OPEN_FD.
- 2112
- MESSAGE
The procedure XM_RECOVERY_SETUP detected a failure in SM_OPEN_OBJECT.
- 2113
- MESSAGE
The procedure XM_RECOVERY_SETUP detected a bad pointer for the SSM free space map.
- 2114
- MESSAGE
The procedure XM_RECOVERY_SETUP detected a bad pointer for a label table.
- 2115
- MESSAGE
The procedure XM_DB_PROC detected a bad convert in the DST.
- 2116
- MESSAGE
The procedure XM_CLOSELOGFILES received bad status.
- 2117
- MESSAGE
The procedure XM_RECOVERY received bad status from XM_MAP_IN_LT_EXT.
- 2118
- MESSAGE
The procedure XM_MAN_IN_LT_EXT received a bad status from VSM.
- 2119
- MESSAGE
The procedure XM_RECOVERY hit a bugcatcher.
- 2120
- MESSAGE
The procedure XM_ADDACTXID detected an overflow in the number of pool entries.
- 2121
- MESSAGE
The procedure XM_ADDGUFD detected too many GUFD entries.
- 2122
- MESSAGE
The procedure XM_GETBIT_N_LABELUFID received bad FILE ID.
- 2123
- MESSAGE
The procedure XM_PINGOINAWAY received bad status from XM_FINDTRANSROW.
- 2124
- MESSAGE
The procedure XM_GETPOINTER received bad status from STMGT.
- 2125
- MESSAGE
The procedure XM_DEFERDETACH received bad status from XM_GETXID.
- 2126
- MESSAGE
The procedure XM_DEFERDETACH release of file from log was unsuccessful.
- 2127
- MESSAGE
The procedure XM_ABORTUSERXA received bad status from XMABORTTRAN.
- 2128
- MESSAGE
The procedure XM_ABORTUSERXA received bad status from FINDPINROW.
- 2129
- MESSAGE
The procedure XM_DELETEOBJID detected an invalid record type.
- 2130
- MESSAGE
The procedure XM_ALLOCATEBLOCK detected no more disk space.
- 2131
- MESSAGE
The procedure XM_RELEASEPOINTER received bad status from SM_CLOSE.
- 2132
- MESSAGE
The procedure XM_CLOSE detected an unrecognized option; bad input parameter.
- 2133
- MESSAGE
The procedure XM_ALLOCATERECORD detected no more room to allocate records.
- 2134
- MESSAGE
The procedure XM_ALLOCATERECORD detected an unassigned or invalid parameter.
- 2135
- MESSAGE
The procedure XM_DEALLOCATERECORD detected the entry was already released.
- 2136
- MESSAGE
The procedure XM_DEALLOCATERECORD detected an unrecognizable or invalid
parameter.
- 2137
- MESSAGE
The procedure XM_DELETETRANSROW detected an invalid input parameter.
- 2138
- MESSAGE
The procedure XM_DELETETRANSROW detected an invalid input parameter.
- 2139
- MESSAGE
The procedure XM_ADDLSROW received bad status from CB_INIT.
- 2140
- MESSAGE
The procedure XM_DELETELSROW received bad status from XM_DEALLOC_PAGE_CACHE.
- 2141
- MESSAGE
The procedure XM_ADDTRLS_CB received bad status from XM_FINDLSROW.
- 2142
- MESSAGE
The procedure XM_W_COMMITRECORD received bad status from SM_CLOSE.
- 2143
- MESSAGE
The procedure XM_RE_ABORTTRANS received bad status from VLM_VOLUME_ID_TO_MV_ID.
- 2144
- MESSAGE
The procedure XM_RE_ABORTTRANS received bad VOLUME ID as a parameter.
- 2145
- MESSAGE
The procedure XM_RE_ABORTTRANS received bad status from SM_OPEN_FD.
- 2146
- MESSAGE
The procedure XM_RE_ABORTTRANS received bad status from SM_OPEN_OBJECT.
- 2147
- MESSAGE
The procedure XM_END_SYSTEM_TRANS detected a bad input UI pointer.
- 2148
- MESSAGE
The procedure XM_END_SYSTEM_TRANS detected a bad input pointer.
- 2149
- MESSAGE
The procedure XM_ENDGOLDENXID detected a bad input UI pointer.
- 2150
- MESSAGE
The procedure XM_ABORTGOLDENXID detected a bad input UI pointer.
- 2151
- MESSAGE
The procedure CHECK_FOR_CROSS_LOG_HALF received bad status from SM_GET_GUFD.
- 2152
- MESSAGE
The procedure CHECK_FOR_CROSS_LOG_HALF received bad status from VLM_GET_SSM_DEV_AREA.
- 2153
- MESSAGE
The procedure CHECK_FOR_CROSS_LOG_HALF received bad status from SM_OPEN_FD.
- 2154
- MESSAGE
The procedure CHECK_FOR_CROSS_LOG_HALF received bad status from SM_OPEN_OBJECT.
- 2155
- MESSAGE
The procedure XM_GETVOLSETINDEX received bad status from VLM_VOL_ID_TO_MVST_X.
- 2156
- MESSAGE
The procedure XM_DETACHUFIDFROMLOG received bad status from a STORAGE MANAGEMENT routine.
- 2158
- MESSAGE
The procedure XM_BUMPCOUNTER received bad status from POST.
- 2159
- MESSAGE
The procedure XM_UNLOCKRESOURCE received bad status from REPLY_TO_WAITER.
- 2160
- MESSAGE
The procedure XM_UNLOCKOBJECT detected an invalid option for this parameter.
- 2161
- MESSAGE
The procedure XM_UNLOCKOBJECT detected an invalid option for this parameter.
- 2162
- MESSAGE
The procedure XM_UNLOCK received bad status from POST.
- 2163
- MESSAGE
The procedure XM_TAPEIO received bad status from POST.
- 2164
- MESSAGE
The procedure XM_UNLOCKONEOBJECT detected an invalid option for this parameter.
- 2165
- MESSAGE
The procedure XM_UNLOCKONEOBJECT detected an invalid option for this parameter.
- 2166
- MESSAGE
The procedure XM_UNLOCKONEOBJECT received bad status from REPLY_TO_WAITER.
- 2167
- MESSAGE
The procedure XM_CLOSESYSLOG failed to close the XM System Log.
- 2168
- MESSAGE
The procedure XM_CHECKOWNER detected that the PIN resource was already owned.
- 2169
- MESSAGE
The procedure XM_FREEZE received bad status from TIM_FREEZE.
- 2170
- MESSAGE
The procedure XM_PIN_CACHE received bad status from GET_TIMER.
- 2171
- MESSAGE
The procedure XM_PIN_CACHE received bad status from RESET_TIMER.
- 2172
- MESSAGE
The procedure XM_LAUNCH_IO received bad status from POST.
- 2173
- MESSAGE
The procedure XM_LOG_POST_COMPLETOR received bad MM status.
- 2174
- MESSAGE
The procedure XM_DO_IO received bad status from POST.
- 2175
- MESSAGE
The procedure XM_BUILDACTRECORD received an unexpected escape from MOVE_FAST.
- 2176
- MESSAGE
The procedure XM_BUILDACTRECORD detected a bad parameter option.
- 2177
- MESSAGE
The procedure XM_COMMITIOGRECORD detected a bad parameter option.
- 2178
- MESSAGE
The procedure XM_CHECKPOINT_SSM_MAPS detected a routine failure.
- 2179
- MESSAGE
The procedure XM_CHECKPOINT_SERVER received bad status from EXTEND_RECEIVER.
- 2180
- MESSAGE
The procedure XM_CREATE_CHECKPOINT_SERVER received bad status from SIMPLE_CREATE_PROCESS.
- 2181
- MESSAGE
The procedure XM_CREATE_CHECKPOINT received bad status from IPC_AWAKE_PROCESS.
- 2182
- MESSAGE
The procedure XM_CHECK_POINT_FILES received bad status from POST.
- 2183
- MESSAGE
The procedure XM_SEND_CHECK_POINT_FILES received bad status from
GET_MSG_FRAME.
- 2184
- MESSAGE
The procedure XM_SEND_CHECK_POINT_FILES received bad status from SEND_MSG.
- 2185
- MESSAGE
The procedure XM_RECOVERY received bad status from VLM_ALLOW_DISC_ALLOCATION.
- 2186
- MESSAGE
The procedure XM_CREATION_OF_SYSLOG received bad status from POST.
- 2187
- MESSAGE
The procedure XM_START_SYSTEM_TRANS received an invalid parameter.
- 2188
- MESSAGE
The function XM_LSID_TO_LSROW failed.
- 2189
- MESSAGE
The procedure XM_ABORT_SYSTEM_TRANS received a bad PTR as a parameter.
- 2190
- MESSAGE
The routine XM_CLOSESYSLOG failed because an unexpected escape occurred.
- 2191
- MESSAGE
The procedure recovery received a bad status from DISC_SM_START_READ.
- 2192
- MESSAGE
The procedure XM_RECOVERY_SETUP received a bad status from CREATE_OBJECT.
- 2193
- MESSAGE
Unexpected escape into routine XM_CHECKPOINT system log.
- 2194
- MESSAGE
The procedure STARTINSTALL had an unexpected escape.
- 2195
- MESSAGE
The procedure RESETINSTALL had an unexpected escape.
- 2196
- MESSAGE
The procedure SYSLOGMEMO received a bad volume ID from VOLUME MANAGEMENT.
- 2197
- MESSAGE
The procedure SYSLOGMEMO had an unexpected escape.
- 2198
- MESSAGE
An error was received from NOTIFY DISPATCHER.
- 2199
- MESSAGE
XM_ABORT_SYSTEM_TRANS procedure had an unexpected escape.
- 2200
- MESSAGE
Procedure XM_ABORT_STALLED_TRANSACTION was invoked.
- 2201
- MESSAGE
The procedure XM_RECOVERY had an unexpected escape from MOVE_FAST.
- 2401
- MESSAGE
An unexpected escape was encountered in CM_PROCESS_SERVER.
- 2402
- MESSAGE
PREP_CM_SERVER can not copy the message into a message frame from the target port's pool.
- 2403
- MESSAGE
PREP_CM_SERVER encountered an unexpected escape from SWITCH.
- 2404
- MESSAGE
The message threshold of the target port can not be changed; bad status from PORT_CONTROL.
- 2405
- MESSAGE
Creation of CM_PORT failed.
- 2406
- MESSAGE
An unexpected escape was encountered in CREATE_CM_SVR.
- 2407
- MESSAGE
Creation of a PFP port was unsuccessful.
- 2409
- MESSAGE
CREATE_PORT_DST can not create CONTEXT AREA TABLE for the DST.
- 2410
- MESSAGE
CREATE_PORT_DST can not create the message pool for the DST.
- 2411
- MESSAGE
CREATE_PORT_DST can not release the data segment while recovering from an
error.
- 2412
- MESSAGE
CREATE_PORT_DST can not release the port DST extension area while recovering from an error.
- 2413
- MESSAGE
DISCARD_REF can not release the caller's message frame.
- 2414
- MESSAGE
GET_MSG_REF can not locate the port's DST.
- 2415
- MESSAGE
GET_MSG_REF can not get message frame from the port's message pool.
- 2416
- MESSAGE
GET_MSG_REF_NW can not locate the port's DST.
- 2417
- MESSAGE
GET_MSG_REF_NW can not get a message frame from the port's message pool.
- 2418
- MESSAGE
KILL_PFP_CM got an unexpected error from KILL_PFP.
- 2419
- MESSAGE
The type of information requested by the caller is unknown to NEW_PORT_STATUS.
- 2420
- MESSAGE
NEW_PORT_STATUS can not locate the caller's DST.
- 2421
- MESSAGE
NEW_PORT_STATUS encountered an unexpected escape.
- 2422
- MESSAGE
NO_CHK_SEND_DB can not send a message to the target port.
- 2423
- MESSAGE
NO_CHK_SEND_Q can not send message to the target port.
- 2424
- MESSAGE
NO_CHK_SEND_REF can not send a message to the target port.
- 2425
- MESSAGE
NO_CHK_SEND_S can not send a message to the target port.
- 2426
- MESSAGE
PORT_DST_STAT can not locate the caller's DST; bad status was returned by
CONVERT_DST.
- 2427
- MESSAGE
PORT_DISABLE can not disable CM port; bad status was returned by CHANGE_PORT_STATE.
- 2428
- MESSAGE
PORT_ENABLE can not enable CM port; bad status was returned by CHANGE_PORT_STATE.
- 2429
- MESSAGE
PORT_MASK_DIS can not disable subqueues requested by the caller; bad status from CHANGE_SUBQUEUE.
- 2430
- MESSAGE
PORT_MASK_EN can not enable the subqueues request by the caller; bad status was
returned by CHANGE_SUBQUEUE.
- 2431
- MESSAGE
RECEIVE_DB can not enable the port's subqueues; bad status was returned by
CHANGE_SUBQUEUE.
- 2432
- MESSAGE
RECEIVE_DB can not get the length of the caller's DST; bad status was returned by MAX_DST_SIZE.
- 2433
- MESSAGE
RECEIVE_DB can not locate the caller's DST; bad status was returned by CONVERT_DST.
- 2434
- MESSAGE
RECEIVE_DB can not get a message from the target port due to an unexpected error in RECEIVE_MESSAGE.
- 2435
- MESSAGE
RECEIVE_DB can not restore the port's original subqueue mask.
- 2436
- MESSAGE
RECEIVE_Q can not enable the port's subqueues as requested by the caller.
- 2437
- MESSAGE
RECEIVE_Q can not get a message from the target port due to a unexpected error in RECEIVE_MSG.
- 2438
- MESSAGE
RECEIVE_Q can not restore the port's original subqueue mask.
- 2439
- MESSAGE
RECEIVE_S can not enable the port's subqueues as requested by the caller.
- 2440
- MESSAGE
RECEIVE_S can not get a message from the target port due to an unexpected error in RECEIVE_MSG.
- 2450
- MESSAGE
RECEIVE_S can not restore the port's original subqueue mask as requested by the caller.
- 2451
- MESSAGE
RECEIVE_REF can not enable the port's subqueues as requested by the caller.
- 2452
- MESSAGE
RECEIVE_REF can not get a message from the target port due to an unexpected error in RECEIVE_MSG.
- 2453
- MESSAGE
RECEIVE_REF can not restore the port's original subqueue mask as requested by the caller.
- 2454
- MESSAGE
GET_DB_MSG(RECEIVE_W_DB) can not get the length of the caller's DST; bad status
was returned by MAX_DST_SIZE.
- 2455
- MESSAGE
GET_DB_MSG(RECEIVE_W_DB) can not locate the caller's DST; bad status was
returned by CONVERT_DST.
- 2456
- MESSAGE
GET_DB_MSG(RECEIVE_W_DB) can not receive a message from the target port as requested by the caller.
- 2457
- MESSAGE
RECEIVE_W_DB can not enable the port's subqueues as requested by the caller.
- 2458
- MESSAGE
RECEIVE_W_DB can not restore the port's original subqueue mask.
- 2459
- MESSAGE
GET_Q_MSG(RECEIVE_W_Q) can not receive a message from the target port; bad status was received from RECEIVE_MSG.
- 2460
- MESSAGE
RECEIVE_W_Q can not enable the port's subqueues as requested by the caller.
- 2461
- MESSAGE
RECEIVE_W_Q can not restore the port's original subqueue mask; bad status was
returned by CHANGE_SUBQUEUE.
- 2462
- MESSAGE
The procedure GET_S_MSG(RECEIVE_W_S) can not receive a message from the target port; bad status was returned by RECEIVE_MSG.
- 2463
- MESSAGE
RECEIVE_W_S can not enable the port's subqueues requested by the caller.
- 2464
- MESSAGE
RECEIVE_W_S can not restore the port's original subqueue mask; bad status was
returned by CHANGE_SUBQUEUE.
- 2465
- MESSAGE
REPLACE_DB can not insert a message to the target port; bad status was returned
by INSERT_MSG.
- 2466
- MESSAGE
REPLACE_Q can not insert a message to the target port; bad status was returned
by INSERT_MSG.
- 2467
- MESSAGE
REPLACE_REF can not insert a message to the target port; bad status was returned by INSERT_MSG.
- 2468
- MESSAGE
REPLACE_S can not insert a message to the target port; bad status was returned
by INSERT_MSG.
- 2469
- MESSAGE
SEND_DB can not send a message to the target port; bad status was returned by SEND_MESSAGE.
- 2470
- MESSAGE
SEND_Q can not send a message to the target port; bad status was returned by SEND_MSG.
- 2471
- MESSAGE
SEND_REF can not send a message to the target port; bad status was returned by
SEND_MSG.
- 2472
- MESSAGE
SEND_S can not send a message to the target port; bad status was returned by SEND_MSG.
- 2473
- MESSAGE
SET_PORT_MASK can not change a port's subqueue mask; bad status was returned by CHANGE_SUBQUEUE.
- 2474
- MESSAGE
STUFF_RIGHT_HALF_WORD is too large a number to fit into a shortint.
- 2475
- MESSAGE
IOWAIT_PORT_SERVER caused an unexpected escape.
- 2476
- MESSAGE
CHANGE_IOWAIT_NM caused an unexpected escape.
- 2477
- MESSAGE
CHECK_IO_COUNT caused an unexpected escape.
- 2478
- MESSAGE
CREATE_IOWAIT failed for reasons other than an exhausted port DST.
- 2479
- MESSAGE
CREATE_IOWAIT can not release the acquired resources after creation of the port failed due to an exhausted port DST.
- 2480
- MESSAGE
CREATE_TO_WAIT_COMPLETOR can not create the context area for the completor; bad status was returned by CREATE_OBJECT.
- 2481
- MESSAGE
CREATE_IO_WAIT_COMPLETOR failed and can not release the context area; bad status was returned by RELEASE_OBJECT.
- 2482
- MESSAGE
CREATE_IO_WAIT_COMPLETOR failed, causing an unexpected escape while releasing
resources.
- 2483
- MESSAGE
ABORT_CM_TIMER could not abort an unarmed timer entry; possibly already
released.
- 2484
- MESSAGE
ABORT_CM_TIMER caused an unexpected escape.
- 2485
- MESSAGE
DISABLE_IOWAIT caused an unexpected escape.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2486
- MESSAGE
ENABLE_IOWAIT caused an unexpected escape.
- 2487
- MESSAGE
INC_IO_COUNT was unable to convert IOWAIT port number to completion index; bad status was returned by HASH_FIND.
- 2488
- MESSAGE
INIT_CM_PORT can not create CM PORT object; bad status returned by CREATE_OBJECT.
- 2489
- MESSAGE
INIT_CM_PORT caused an unexpected escape; could be from creating IOWAIT HASH TABLE, IOWAIT COMPLETOR TABLE, dictionary structure, or CM PORT DESCRIPTOR TABLE; cause of escape in second parameter.
- 2490
- MESSAGE
INVOKE_CM_COMPLETOR(INVOKE_IOWAIT) can not get message from the completor's port; bad status returned by RECEIVE_MSG.
- 2500
- MESSAGE
INVOKE_CM_COMPLETOR(INVOKE_IOWAIT) can not find the length of the data segment; bad status returned by MAX_DST_SIZE.
- 2501
- MESSAGE
INVOKE_CM_COMPLETOR(INVOKE_IOWAIT) just finished executing CM COMPLETOR in an attempt to release message frame; bad status returned by REL_MSG_FRAME.
- 2502
- MESSAGE
REL_CM_TIMER caller is trying to release an unarmed timer; possibly already released.
- 2503
- MESSAGE
REL_CM_TIMER can not release timer due to unexpected error in RELEASE_TIMER.
- 2504
- MESSAGE
REL_CM_TIMER can not release CM Timer entry to CMPORTS TIMER TABLE; bad status returned by
RELEASE_TABLE_ENTRY.
- 2505
- MESSAGE
START_CM_TIMER can not get timer; bad status returned by GET_TIMER.
- 2506
- MESSAGE
START_CM_TIMER can not get entry from CM TIMER TABLE; escape caused by GET_TABLE_ENTRY.
- 2507
- MESSAGE
CREATE_CM_PORT_DICTIONARY is unable to create symbol data for the CMPORTS dictionary; unexpected escape from either CREATE_OBJECT or SYMBOL TABLE.
- 2508
- MESSAGE
CREATE_CM_PORT_CLASS_DICTIONARY is unable to create SYMBOL TABLE for Class Name Dictionary; unexpected escape received from either CREATE_OBJECT or SYMBOL
TABLE.
- 2509
- MESSAGE
DICT_ADD can not lock CMPORTS Dictionary; bad status returned by STLOCK.
- 2510
- MESSAGE
DICT_ADD can not unlock CMPORTS Dictionary; bad status returned by STUNLOCK.
- 2511
- MESSAGE
DICT_DELETE can not lock CMPORTS Dictionary; bad status returned by STLOCK.
- 2512
- MESSAGE
DICT_DELETE can not unlock CMPORTS Dictionary; bad status returned by STUNLOCK.
- 2513
- MESSAGE
DICT_FIND can not lock CMPORTS Dictionary; bad status returned by STLOCK.
- 2514
- MESSAGE
DICT_FIND can not unlock CMPORTS Dictionary; bad status returned by STUNLOCK.
- 2515
- MESSAGE
DICT_UPDATE can not lock CMPORTS Dictionary; bad status returned by STLOCK.
- 2516
- MESSAGE
DICT_UPDATE can not unlock CMPORTS Dictionary; bad status returned by STUNLOCK.
- 2517
- MESSAGE
DICT_SEND can not lock CMPORTS Dictionary; bad status returned by STLOCK.
- 2518
- MESSAGE
DICT_SEND can not unlock CMPORTS Dictionary; bad status returned by STUNLOCK.
- 2519
- MESSAGE
DICT_SEND is unable to send a message to the port for reasons other than non-existent port; bad status returned by SEND_MSG.
- 2520
- MESSAGE
ADD_CMPORT_CLS can not lock SYMBOL TABLE for CMPORTS Class Name Dictionary; bad
status returned by STLOCK.
- 2521
- MESSAGE
ADD_CMPORT_CLS can not add key to CMPORTS CLASS NAME SYMBOL TABLE; bad status
returned by STADDKEY.
- 2522
- MESSAGE
ADD_CMPORT_CLS can not unlock CMPORTS CLASS NAME SYMBOL TABLE; bad status returned by STUNLOCK.
- 2523
- MESSAGE
DEL_CMPORT_CLS can not lock SYMBOL TABLE for CMPORTS Class Name Dictionary; bad
status returned by STLOCK.
- 2524
- MESSAGE
DEL_CMPORT_CLD can not delete key from CMPORTS CLASS NAME SYMBOL TABLE; bad
status returned by STDELKEY.
- 2525
- MESSAGE
DEL_CMPORT_CLS can not unlock CMPORTS CLASS NAME SYMBOL TABLE; bad status
returned by STUNLOCK.
- 2526
- MESSAGE
BUILD_CM_PORT_DESC can not create CMPORTS descriptor object; bad status
returned by CREATE_OBJECT.
- 2527
- MESSAGE
BUILD_CM_PORT_DESC is unable to build DESCRIPTOR TABLE; unexpected escape
caused by HASH_CREATE_TABLE or CREATE_TABLE.
- 2528
- MESSAGE
DEALLOCATE_CM_PORT_DESC_ENTRY can not deallocate CMPORTS descriptor entry due
to an unexpected escape.
- 2529
- MESSAGE
CREATE_CM_PORT can not lock Class Name Dictionary to get the parameters needed
to call CREATE_CM_SVR; bad status returned by STLOCK.
- 2530
- MESSAGE
The port is already created, but can not unlock the Class Name Dictionary; bad
status returned by STUNLOCK.
- 2531
- MESSAGE
CREATE_IO_WAIT can not lock Class Name Dictionary to get the parameters needed
to call CREATE_IOWAIT; bad status returned by STLOCK.
- 2532
- MESSAGE
The port already has been created, but can not unlock the Class Name Dictionary; bad status returned by STUNLOCK.
- 2533
- MESSAGE
The IOWAIT port still has outstanding I/O; cannot be deleted.
- 2534
- MESSAGE
DELETE_PORT just finished purging the port in the process of releasing its DST, but PURGE_POOL failed.
- 2535
- MESSAGE
DELETE_CMPORT can not release the port's DST (purge pending and no longer in use); bad status returned by RELDATASEG.
- 2536
- MESSAGE
DELETE_CMPORT can not release the port's DST extension area; bad status returned by RELEASE_OBJECT.
- 2537
- MESSAGE
The port is an NM IOWAIT port, and a context area was created for it; can not
release that context area; bad status returned by RELEASE_OBJECT.
- 2538
- MESSAGE
DELETE_CMPORT escaped due to an unknown cause.
- 2539
- MESSAGE
DEL_CMPORT_DST can not get address of the DST to be deleted; bad status
returned by CONVERT_DST.
- 2540
- MESSAGE
DEL_CMPORT_DST can not purge the message pool in the DST; bad status returned by PURGE_POOL.
- 2541
- MESSAGE
DEL_CMPORT_DST can not release the port DST; bad status returned by RELDATASEG.
- 2542
- MESSAGE
DEL_CMPORT_DST can not release the DST expansion area; bad status returned by
RELEASE_OBJECT.
- 2543
- MESSAGE
PORT_IS_CM_PORT is trying to find port in CMPORTS DESCRIPTOR HASH TABLE; expect status=ALL_OK if port is found, or status=ENTRY_NOT_FOUND if it isn't, but the status we get from the HASH TABLE is neither of the two.
- 2550
- MESSAGE
GETSIR returned a bad status to the fast switch stub.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2551
- MESSAGE
RELSIR returned a bad status to the fast switch stub.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2559
- MESSAGE
A COMPATIBILITY MODE sudden death has occurred. The error number displayed on the console is the sudden death number.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2560
- MESSAGE
ALTER_STACK_LIMITS failed when changing the CM stack's virtual address.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2561
- MESSAGE
ALTER_OBJECT_SIZE failed when changing the size of the CM stack's virtual object.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2562
- MESSAGE
DBG_RESET_TOS_DATA_BP failed when setting the data BP for CM stack overflow.
- CAUSE
Either the operating system software or an operating system data structure has
been corrupted.
- 2563
- MESSAGE
ALTER_STACK_LIMITS failed when changing the size of the CM stack's data segment.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2564
- MESSAGE
A routine called by BUILD_CM_STACK returned an error when it should not have.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2565
- MESSAGE
LOCK_OBJ_IN_VPN_CACHE failed when locking a newly active PCBX page into the VPN cache.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2584
- MESSAGE
GET_TABLE_ENTRY returned a DST entry which was already in use.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2585
- MESSAGE
LOCK_OBJ_IN_VPN_CACHE failed when creating a new data segment.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2586
- MESSAGE
RELEASE_OBJECT failed when releasing the virtual object for a data segment.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2587
- MESSAGE
RELEASE_TABLE_ENTRY failed when releasing a DST entry.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2588
- MESSAGE
RELEASE_OBJECT failed when releasing the virtual object for a CSTX.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2589
- MESSAGE
GET_TABLE_ENTRY returned a CST entry which was already in use.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2590
- MESSAGE
RELEASE_TABLE_ENTRY failed when releasing a CST entry.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2591
- MESSAGE
CREATE_OBJECT failed when creating the temporary CST for the CME.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2592
- MESSAGE
CREATE_OBJECT failed when creating the DST.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2593
- MESSAGE
CREATE_TABLE failed when initializing the free list of the CST.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2594
- MESSAGE
CREATE_TABLE failed when initializing the free list of the DST.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2595
- MESSAGE
LOCK_OBJ_IN_VPN_CACHE failed when locking the SL into the VPN cache.
- CAUSE
Either the operating system software or an operating system data structure has been corrupted.
- 2900
- MESSAGE
Buffer header corruption is detected.
- CAUSE
TURBO IMAGE/XL internal error.
- 2901
- MESSAGE
NM'DBPROCTERM failed to deallocate DBU.
- CAUSE
TURBO IMAGE/XL internal error.
- 2902
- MESSAGE
NM'DBPROCTERM failed to deallocate DBR.
- CAUSE
TURBO IMAGE/XL internal error.
- 3020
- MESSAGE
The NS/3000-XL Network Interface (NI) module has detected a fatal error.
- 3040
- MESSAGE
The NS/3000-XL Internet Protocol (IP) module has detected a fatal error.
- 3060
- MESSAGE
The NS/3000-XL MAPPING TABLE module has detected a fatal error.
- 3080
- MESSAGE
The NS/3000-XL Transmission Control Protocol (TCP) has detected a fatal error.
- 3081
- MESSAGE
Unknown SIP message received by TCP PM.
- 3082
- MESSAGE
Unknown XPORT message received by TCP PM.
- 3083
- MESSAGE
Unknown buffer manager message received by TCP PM.
- 3084
- MESSAGE
Unknown net IPC message received by TCP PM.
- 3085
- MESSAGE
Unknown message received by TCP PM.
- 3086
- MESSAGE
TCP PM received a data packet while closed.
- 3087
- MESSAGE
TCP PM received a data packet while listening.
- 3088
- MESSAGE
TCP PM received a data packet while SYN'RECVD1.
- 3089
- MESSAGE
Invalid buffer in reply message to TCP PM.
- 3090
- MESSAGE
Message received by TCP PM before initialization.
- 3091
- MESSAGE
TCP PM has no free retransmission queue entries.
- 3092
- MESSAGE
Appending one TCP PM packet to another failed.
- 3093
- MESSAGE
Appending one TCP PM receive queue entry to another failed.
- 3094
- MESSAGE
Getting TCP PM receive queue entry failed.
- 3095
- MESSAGE
Removing TCP PM dictionary entry failed.
- 3096
- MESSAGE
Bad TCP PM acknowledgement timer popped.
- 3097
- MESSAGE
Bad TCP PM retransmission timer popped.
- 3098
- MESSAGE
Bad TCP PM connection assurance timer popped.
- 3099
- MESSAGE
No TCP PM receive queue entries available.
- 3100
- MESSAGE
Updating TCP PM receive queue entry link failed.
- 3101
- MESSAGE
TCP PM generates a connection assurance packet when one already exists.
- 3102
- MESSAGE
TCP PM received unexpected GET_BUFFER error.
- 3103
- MESSAGE
TCP PM data SEND to net IPC failed.
- 3104
- MESSAGE
TCP PM SEND to IP failed.
- 3105
- MESSAGE
TCP PM urgent data SEND to net IPC failed.
- 3106
- MESSAGE
TCP PM fragment SEND to IP failed.
- 3107
- MESSAGE
TCP PM failed to get valid user data pointer.
- 3108
- MESSAGE
TCP PM reply to net IPC failed.
- 3109
- MESSAGE
TCP PM has too many data descriptors.
- 3110
- MESSAGE
Bad TCP PM wait timer popped.
- 3200
- MESSAGE
Invalid control message received by PXP SIP.
- 3201
- MESSAGE
Invalid SIP message received by PXP SIP.
- 3202
- MESSAGE
Invalid XPORT message received by PXP SIP.
- 3203
- MESSAGE
Invalid net IPC message received by PXP SIP.
- 3204
- MESSAGE
Invalid message received by PXP SIP.
- 3205
- MESSAGE
Message received by PXP SIP before initialization.
- 3206
- MESSAGE
Deleting PXP SIP DST TABLE entry failed.
- 3207
- MESSAGE
Adding a PXP SIP socket queue element failed.
- 3208
- MESSAGE
Invalid SIP close message received by PXP SIP.
- 3209
- MESSAGE
Adding PXP SIP DST TABLE entry failed.
- 3210
- MESSAGE
Deleting a PXP SIP socket queue element failed.
- 3211
- MESSAGE
Deleting the PXP SIP dictionary entry failed.
- 3212
- MESSAGE
Adding the PXP SIP dictionary entry failed.
- 3300
- MESSAGE
Message received by PXP PM before initialization.
- 3301
- MESSAGE
Unknown SIP message received by PXP PM.
- 3302
- MESSAGE
Unknown buffer manager message received by PXP PM.
- 3303
- MESSAGE
Unknown net IPC message received by PXP PM.
- 3304
- MESSAGE
Unknown message received by PXP PM.
- 3305
- MESSAGE
Unknown XPORT message received by PXP PM.
- 3306
- MESSAGE
Getting a PXP PM retransmission queue element failed.
- 3307
- MESSAGE
Incorrect number of PXP PM data descriptors.
- 3308
- MESSAGE
Copying send data failed in PXP PM.
- 3309
- MESSAGE
Building the PXP PM reply header failed.
- 3310
- MESSAGE
Copying data for first reply message failed in PXP PM.
- 3311
- MESSAGE
Copying data for reply message failed in PXP PM.
- 3312
- MESSAGE
Deleting a PXP PM retransmission queue element failed.
- 3313
- MESSAGE
Getting a PXP PM receive queue element failed.
- 3314
- MESSAGE
Invalid buffer reply message received by PXP PM.
- 3315
- MESSAGE
Accessing a PXP PM retransmission queue element failed.
- 3316
- MESSAGE
Accessing a PXP PM receive queue element failed.
- 3317
- MESSAGE
Deleting a PXP PM dictionary entry failed.
- 3400
- MESSAGE
Message received by TCP SIP before initialization.
- 3401
- MESSAGE
Unknown CONTROL message received by TCP SIP.
- 3402
- MESSAGE
Unknown SIP message received by TCP SIP.
- 3403
- MESSAGE
Unknown XPORT message received by TCP SIP.
- 3404
- MESSAGE
Unknown net IPC message received by TCP SIP.
- 3405
- MESSAGE
Adding TCP SIP socket queue entry failed.
- 3406
- MESSAGE
Adding TCP SIP dictionary entry failed.
- 3407
- MESSAGE
Removing call socket dictionary entry failed.
- 3408
- MESSAGE
Removing call socket dictionary entry because of a failure error.
- 3409
- MESSAGE
Purging a TCP PM port failed.
- 3410
- MESSAGE
Deleting TCP SIP connection queue entry failed.
- 3411
- MESSAGE
Removing TCP SIP dictionary entry failed.
- 3412
- MESSAGE
Creating initiating TCP PM port failed.
- 3413
- MESSAGE
Adding initiating TCP PM connection queue entry failed.
- 3414
- MESSAGE
Unknown buffer manager message received by TCP SIP.
- 3415
- MESSAGE
Adding responding TCP PM connection queue entry failed.
- 3416
- MESSAGE
Creating responding TCP PM port failed.
- 5050
- MESSAGE
An irrecoverable internal error occurred within the DHCF/XL subsystem after the console operator specified the system should fail in such an event.
- CAUSE
The DHCF/XL trap handler was invoked after the subsystem had been started with "ERROPT=SYS" specified in the DHCF CONTROL START command.
- ACTION
Take a system dump; restart your system using the default "ERROPT=SUB" parameter and the system will continue operating.
|
