8 guardian procedures, Error ranges and error handling, Guardian procedures – HP Integrity NonStop J-Series User Manual
Page 113: Support for smf are described in, Section 8, guardian procedures, Fup is described in the, System procedure, see, Section 8, guardian, Procedures
HP NonStop Storage Management Foundation User's Guide—523562-007
8-1
8
Guardian Procedures
Several Guardian procedures are available for programmatically operating on storage
pools, virtual disks, and physical volumes associated with storage pools. Some of the
procedures are exclusively for use on SMF subsystem objects, while others are more
generic Guardian procedures that return SMF status information or contain new
options for SMF features.
This section contains these topics:
Error Ranges and Error Handling
Guardian Procedures Unique to SMF
Format of Information Returned
Error Ranges and Error Handling
File system operations for files handled in the VDP environment return errors in the
range 5000 to 5999. These error numbers indicate a “VDP-specific” problem in
handling the operation. Any function that handles or expects certain file errors explicitly
must be able to handle errors in this range. In general, errors in the SMF error range
are exceptional conditions that indicate a problem with the SMF subsystem itself,
rather than something that could be handled within an application. The VDP also
returns the usual file system errors for normal file operational events, such as file level
security violations.
Detailed contextual information for errors in the 5000-5999 error range cannot be
included in the return codes for file system procedures. To assist in resolving error
conditions, SMF also provides detailed messages through the Event Management
Service (EMS).
For example, if the VDP cannot update its ANT file while processing a CREATE
operation, the file system CREATE procedure returns an error 5011 (ERROR
ACCESSING NAME TABLE). In addition to this file system error, more information is
provided, including the actual error that the VDP encountered, through an EMS
message (indicating, for example, that the disk on which the ANT file resides is down).
Programs and operational procedures for evaluating and handling error conditions
might require changes to support this extended error reporting mechanism.
SMF EMS messages are described in
.