Technical data

5–62 Event Reporting: Templates and Codes
02A20100 Pubs not one when transportable
02A30100 No available data buffers. If the cache module exists then this is true after testing the whole
cache. Otherwise there were no buffers allocated from BUFFER memory on the controller
module.
02A40100 A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when allocating VAXDs.
02A50100 A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when allocating DILPs.
02A60100 A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when allocating Change
State Work Items.
02A70100 A call to EXEC$ALLOCATE_MEM_ZEROED failed to return memory when allocating VA Request
Items.
02A90100 Too many pending FOC$SEND requests by the Cache Manager. Code is not designed to handle
more than one FOC$SEND to be pending because there’s no reason to expect more than one
pending.
02AA0100 An invalid call was made to CACHE$DEALLOCATE_CLD. Either that device had dirty data or it
was bound to a RAIDset.
02AB0100 An invalid call was made to CACHE$DEALLOCATE_SLD. A RAIDset member either had dirty data
or write-back already turned on.
02AC0100 An invalid call was made to CACHE$DEALLOCATE_SLD. The RAIDset still has data (strip nodes).
02AD0180 The FX detected a compare error for data that was identical. This error has always previously
occurred due to a hardware problem.
02AE0100 The mirrorset member count and individual member states are inconsistent. Discovered
during a mirrorset write or erase.
02AF0102 An invalid status was returned from VA$XFER() in a write operation.
■ Last Failure Parameter[0] contains the DD address.
■ Last Failure Parameter[1] contains the invalid status.
Table 5–3 Last Failure Codes (Continued)
Code Description