HP 3000 Manuals HP 3000 Manuals
(Subsystem 98)(Continued)
------------------------------------------------------------
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.
-------------------------------------------------------------