 |
» |
|
|
 |
|  |  |
(Subsystem 98) |  |
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. |  |  |  |  |
- 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.
|