Error Lists - HP Guardian Errors Manual

Recovery Wait and retry the operation by bringing the SMF process to an UP state. If the problem
persists, contact your service provider.
5076
Cause When the NonStop Storage Management Foundation (SMF) subsystem attempted to perform
recovery processing after an SMF process failed, an invalid operation code was found in the
PENDOPS (pending operations) file.
Effect The requested operation failed and recovery processing is aborted.
Recovery Contact your service provider.
5313
Cause During processing of a file-system request (create, open, purge, rename, alter, or information
inquiry) on a NonStop Storage Management Foundation (SMF) logical file, the virtual disk process
encountered an error.
Effect The requested operation is not performed.
Recovery Appropriate recovery varies according to the specific error. Refer the event log to
determine the specific file-system error and take appropriate action.

Error Lists

If you are using the Subsystem Programmatic Interface (SPI) to send commands to a subsystem,
you might receive a file-system error list in a response. HP subsystems return such an error list when,
in performing your request, they call a file-system procedure directly or indirectly and an error
occurs on the call.
The contents of the error list depend on which procedure was called. The standard SPI token
ZSPI-TKN-PROC-ERR, which is present in every file-system error list, identifies the procedure.
Each error list always includes the unconditional tokens listed under its description in this subsection.
In addition, each error list can include any of the conditional tokens listed under its description
and in Table
If you are designing a subsystem that uses SPI, follow these guidelines when constructing a file-system
error list:
Include all unconditional tokens listed in the error-list description.
Make the ZFIL-TKN-XFILENAME token value null if you cannot obtain a valid file name, such
as when these errors occur:
◦
File-system error 16 (file not opened). This error indicates a coding error.
◦
File-system error 26 (no outstanding I/O requests) when it is returned by an AWAITIO
call in which file-number is equal to - 1 .
◦
File-system error 40 (operation timed out) when it is returned by an AWAITIO call in
which file-number is equal to - 1 .
Optionally include any or none of the conditional tokens listed in
listed might not be appropriate for every file-system error. To obtain values for the tokens, use
FILE_GETINFOLIST_ or FILEINFO and pass the procedure a valid file number, or use
FILE_GETINFOLISTBYNAME_ or FILEINFO and pass the procedure a valid file name.
(%11724) An invalid operation code was found in the
PENDOPS table; the PENDOPS entry is invalid.
(device type: 3.36, 25.0, or 52.0)
(%12301) A virtual disk process encountered an error when
trying to perform the requested operation.
(device type: 3.36)
5.
Table 5. Note that the tokens
Error Lists 87