Chapter 91 SMF (Storage Management Foundation) Messages

Cause  An invalid startup parameter for SMCONVRT or SMREVERT was specified, or an invalid parameter was specified when defining a virtual disk process.

Effect  The program terminates. No files are converted.

Recovery  Restart the program and specify a valid parameter.

Cause  A new name was specified for a physical disk to be converted that already exists.

Effect  The program terminates. No files are converted.

Recovery  Restart the program and specify a unique device name.

Cause  A name for a physical disk, virtual disk, or storage pool was specified, but was the wrong type or subtype.

Effect  The program terminates. No files are converted.

Recovery  Restart the program and specify a device name of the correct device type and subtype.

Cause  The device was not in a valid state for the operation.

Effect  The program terminates. No files are converted.

Recovery  Place the device in the indicated state and restart the program.

Cause  The volume specified for a virtual disk catalog table is not a member of the specified disk pool.

Effect  The program terminates. No files are converted.

Recovery  Restart the program and specify the indicated storage pool. Alternatively, EXCLUDE the volume from the current storage pool, INCLUDE the volume in the indicated storage pool and restart the program.

Cause  An error occurred when a file system procedure was called.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  An attempt to allocate memory from the heap failed.

Effect  The program terminates. No files are converted.

Recovery  Run the program with the MAXEM option specified.

Cause  The program received an error reply from another process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  The volume to be converted is in a storage pool.

Effect  The program terminates. No files are converted.

Recovery  Use PUP to EXCLUDE the volume from the pool, then restart the program.

Cause  A virtual disk process (VDP) with the specified name already exists.

Effect  The program terminates. No files are converted.

Recovery  Use another name and retry the operation.

Cause  An end-of-file signal was received in response to a user prompt.

Effect  The program terminates. No files are converted.

Recovery  Informational message only; no corrective action is needed.

Cause  The physical volume being converted contains more files than can be placed on a single virtual disk process.

Effect  The program terminates. No files are converted.

Recovery  Remove some files from the volume and restart the program.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A file system error occurred while SMF attempted to convert a file.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An SMF file was found on a volume being migrated.

Effect  The program terminates. No files are converted.

Recovery  Use SMFIXUP to remove the file and restart the program.

Cause  A file system error was received from the disk process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error was received from the disk process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  The volume could not be placed in the UP SPECIAL state.

Effect  The program terminates. No files are converted.

Recovery  The volume is a TMF data volume. Issue a TMFCOM DISABLE DATAVOL command to disable the volume cleanly. Issue a PUP DOWN command. Restart the program.

Cause  A file system error was received from the disk process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error was received from the disk process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to purge the catalog files for a virtual disk process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to create the catalog files for a virtual disk process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to add an entry to the virtual disk ANT.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  An internal program exception has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program exception has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A file system error occurred while SMF attempted to rename a disk volume.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to place a disk volume in the DOWN state.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  There are more files on the physical volume than can be converted.

Effect  The program terminates. No files are converted.

Recovery  Remove some files from the physical volume and restart the program.

Cause  A file system error occurred during catalog file creation.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A SQL catalog file was not converted.

Effect  The program terminates. No files are converted.

Recovery  Correct the cause of the conversion failure and restart the program.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The user has aborted a conversion operation.

Effect  The program terminates. No files are converted.

Recovery  Informational message only; no corrective action is needed.

Cause  A file system error occurred while SMF attempted to open $RECEIVE.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to communicate with a PUP process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to communicate with a PUP process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to communicate with a PUP process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to communicate with a PUP process.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A prompt from a PUP process was not received when expected.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  An internal program error was received.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program error was received.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An SMCONVERT operation has run to a successful completion.

Effect  The volume is converted to a virtual disk.

Recovery  Informational message only; no corrective action is needed.

Cause  A file system error occurred while SMF attempted to place a disk volume in the UP state.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  The volume specified for a catalog table is not in a pool.

Effect  The program terminates. No files are converted.

Recovery  Use PUP to INCLUDE the volume in a disk pool and restart the program.

Cause  A file system error occurred while SMF attempted to convert a file.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to delete an ANT entry.

Effect  The program terminates. No files are converted.

Recovery  Restart the program using the NOUPDATEANT option. The ANT will not be updated and will have to be deleted manually.

Cause  An SMREVERT operation has been aborted the user.

Effect  The SMREVERT operation does not complete.

Recovery  Informational message only; no corrective action is needed.

Cause  An SMREVERT operation has completed successfully.

Effect  The virtual disk is reverted back to a physical volume.

Recovery  Informational message only; no corrective action is needed.

Cause  A file system error occurred while SMF attempted to add an SQL protection view to the virtual disk’s DEPOBJ.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  The volume name specified for the new physical disk name of a volume to be converted is 8-characters long.

Effect  The program terminates. No files are converted.

Recovery  Specify a volume name of 7-characters or less and restart the program.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal program error has occurred.

Effect  The program terminates. No files are converted.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A file system error occurred while SMF attempted to invalidate the online dump of a TMF-audited file.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  A file system error occurred while SMF attempted to obtain information about a device.

Effect  The program terminates. No files are converted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  The SCF process returned a file system error.

Effect  The migration is aborted.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  SMF received a request it could not process. The requestor is most likely at a version level earlier than D40.00.

Effect  The request is not processed.

Recovery  The requestor’s system must be upgraded before the request can be processed.

Cause  A request to create a logical file was rejected because the target physical volume was being deleted from a storage pool.

Effect  The logical file is not created.

Recovery  Create the logical file on a physical volume still associated with a storage pool.

Cause  A request to exclude a physical disk was rejected because logical file creation is enabled on that volume.

Effect  The physical volume is not excluded.

Recovery  Disable file creation for the physical volume and then exclude it.

Cause  A request to associate a physical volume with a storage pool was rejected because the physical volume is already associated with another storage pool.

Effect  The request is not processed.

Recovery  Disassociate the physical volume from the storage pool it is associated with before attempting to associate it with a different storage pool.

Cause  A request specified a physical volume that is not associated with a storage pool.

Effect  The request is rejected.

Recovery  Associate the physical volume with a storage pool before using SMF to operate on it.

Cause  A request was received by a storage pool process to operate on a physical volume not associated with the storage pool.

Effect  The request is rejected.

Recovery  Ensure that the physical volume is associated with the desired storage pool. Redefine the storage pool if necessary so that the correct physical volumes are associated with it.

Cause  An attempt was made to purge or alter an SMF catalog file by some means other than PUP or SMFIXUP.

Effect  The operation could not be performed.

Recovery  Use PUP or SMFIXUP to operate on SMF catalog files.

Cause  A thread needed to process a request could not be launched because an internal SMF error occurred, most likely because memory could not be allocated.

Effect  The request is not processed.

Recovery  If the thread could not be launched because the thread manager was handling a large number of simultaneous requests, resubmitting the request at a later time may result in success. If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal resource problem caused the thread manager to fail, most likely when it tried to process an operation that had been queued.

Effect  The thread manager stops running.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The lock manager attempted to lock an object, usually a file, in order to process a create, purge, or alter request. The object could not be locked because another process had locked it.

Effect  The request cannot be processed.

Recovery  Retry the operation later. If the problem persists, investigate the source of the existing lock and attempt to resolve it; a deadlock situation may exist that requires stopping other applications to eliminate lock contention. If the locking problem cannot be resolved, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A file system request, such as purging or renaming a file, could not be performed because name mapping using the ANT catalog file was unsuccessful.

Effect  The request could not be processed.

Recovery  Follow the recommendations provided in the Guardian Procedure Errors and Messages Manual for the specific file system error generated.

Cause  A file system failure occurred when the PENDOPS catalog file was being used to complete an outstanding operation. The PENDOPS file is used when SMF needs to recover outstanding operations in progress when an interruption, such as a CPU failure, occurs.

Effect  The operation could not be recovered, but SMF retries.

Recovery  If SMF is unsuccessful after retrying recovery, try to determine why, using the file system error number as a guide; see the Guardian Procedure Errors and Messages Manual for the specific file system error generated. As a last resort, you can use SMFIXUP to purge and recreate the PENDOPS catalog file, but none of the pending operations about which it contains information will be recoverable.

Cause  A logical file name could not be derived on a physical volume because the maximum number of file names that can be associated with the physical volume has been reached. The maximum number of file names available on a given physical volume is (365)(367 x 26).

Effect  The file placement operation on the physical volume fails.

Recovery  The storage pool with which the physical volume is associated may need more physical volume resources. Associate more physical volumes with the storage pool, and move some of the files from the exhausted physical volume to other volumes in the pool.

Cause  An attempt to create a logical file failed because the storage pool’s physical volume characteristics are incompatible with those of the file’s. For example, an audited file cannot be created in a storage pool unless the pool is configured to support audited physical volumes.

Effect  The file could not be created.

Recovery  Redefine the storage pool to support physical volumes that are compatible with your file creation needs.

Cause  A DP2 failure interrupted an operation involving physical file renaming, purging, or altering.

Effect  The file operation could not be performed.

Recovery  Restart the virtual disk process involved in this error. Upon restart, SMF uses information in the PENDOPS catalog file to attempt to recover the incomplete operation.

Cause  A file system error occurred while SMF attempted to delete a POOLTABL entry in response to a request to delete a storage pool.

Effect  The storage pool is not deleted.

Recovery  Retry the operation. If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred while accessing catalog.

Effect  The operation that caused the access attempt did not succeed.

Recovery   If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  When attempting to process a file creation, purge, or alteration operation on a physical file, DP2 returned a message that SMF could not interpret, most likely because the versions of DP2 and SMF are incompatible.

Effect  The file operation is not performed.

Recovery  Ensure that the versions of DP2 and SMF are compatible before retrying the operation.

Cause  An invalid mapping for a VDP catalog was discovered.

Effect  Catalog is not usable.

Recovery  Redefine VDP with correct catalog or use SMFIXUP to update mappings.

Cause  A checkpoint operation could not be performed because the required memory could not be allocated.

Effect  SMF ignores the condition, and processing continues.

Recovery  Typically this situation arises when there are a large number of outstanding requests. As the requests are handled, the memory pressure should disappear. If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause   A backup process received a checkpoint, but it could not be processed because the backup process experienced an internal error.

Effect  SMF ignores the condition, and the primary process continues to run.

Recovery  The recovery operation depends on the error number; see the Guardian Procedure Errors and Messages Manual for information on the file system error number returned. If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The versions of the requestor and the virtual disk or storage pool process that received its request are not compatible.

Effect  The request could not be processed.

Recovery  Determine the versions of requestor processes, including DP2, and SMF processes, and correct incompatibilities before retrying the request.

Cause  A storage pool process experienced an internal communication error because of a shared services problem.

Effect  The request could not be processed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A storage pool could not be redefined, because either a POOLTABL lock could not be obtained or the POOLTABL entry for the storage pool could not be updated.

Effect  The storage pool is not redefined.

Recovery  Examine the event log for a related file system error, and proceed according to the type of error you find. See the Guardian Procedure Errors and Messages Manual for information about the file system error.

Cause  A storage pool or virtual disk process or $ZSMS could not be initialized when attempting to transition from the SPECIAL to the UP state or from the DOWN state to the UP SPECIAL state. This error may be the result of a failure to obtain a lock or the lack of sufficient internal resources.

Effect  The process state does not change.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  SMF encountered a situation it did not know how to handle.

Effect  SMF cannot perform normally.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An SMF backup process was the target of a switch request that could not be processed because only a primary process can handle such a request.

Effect  The request is ignored.

Recovery  Retry the request, specifying the name of a primary process.

Cause  A received message could not be read.

Effect  The request is not processed. The request may or may not be retried.

Recovery  Follow the recommendations in the Guardian Procedure Errors and Messages Manual for the specific file system error returned.

Cause  An invalid request was received.

Effect  The request is not processed.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The SMF pool has no physical volumes.

Effect   The VDP cannot be created.

Recovery  Include a physical volume in the pool, and retry the failed operation.

Cause  An SMF process is not able to allocate enough memory.

Effect  The process does not run.

Recovery  Ensure that there is enough swap space, and retry the operation.

Cause  An internal resource problem occurred.

Effect  An SMF process is not initialized.

Recovery  Examine the event log for events immediately preceding this event. Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A COUP START command could not be processed because adequate memory for startup parameters could not be obtained.

Effect  The process does not start.

Recovery  Retry the operation. If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The thread manager process could not start because sufficient internal resources are not available.

Effect  SMF cannot operate normally.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The thread manager could not obtain the resources required to process a request.

Effect  The request is not processed.

Recovery  Retry the request. If you continue to be unsuccessful, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred while SMF attempted to start a backup process.

Effect  The backup process was not started.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  SMF is attempting to start a backup process.

Effect  Requests that require the process are not processed until the backup process is available.

Recovery  Informational message only; no corrective action is needed.

Cause  The maximum number of retries for starting a backup process has been reached, but the backup process has not started.

Effect  Requests that depend on the process are not handled until the backup process is available.

Recovery  Ensure that any command issued to explicitly start the backup process contained correct parameters. If the failure is not the result of an incorrect command, a configuration or internal resource problem may exist. Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A backup process could be created, but could not receive its startup message.

Effect  The backup process cannot start.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An SMF backup process is starting.

Effect  Requests are now handled by the backup process.

Recovery  Informational message only; no corrective action is needed.

Cause  Memory required to change the state of a process could not be obtained.

Effect  The process state is not changed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A request could not be processed because its target storage pool or virtual disk process was in a state incompatible with the request.

Effect  The request is not processed.

Recovery  Retry the operation after ensuring the target process is in the correct state.

Cause  A catalog file creation, purge, rename, or alter operation could not be performed.

Effect  The request that requires catalog access is not processed.

Recovery  Determine the meaning of the file system error obtained and take appropriate actions. Information about file system errors appears in the Guardian Procedure Errors and Messages Manual.

Cause  Shortage of TLEs was detected in the configured primary CPU.

Effect  The configured backup process will work as primary for next 30 minutes. Even after correcting the resource problem in the configured primary CPU, configured backup will continue to work as primary for 30 minutes. It will then switch to backup.

Recovery  Correct the TLE-related problem in the configured primary CPU.

Cause  The version of SMF is incompatible with the process that issued a request.

Effect  The request is not processed.

Recovery  Determine the versions of requestor processes, including DP2, and SMF processes, and correct incompatibilities before retrying the request.

Cause  An attempt to switch to a backup process failed because the backup process is not running.

Effect  The backup process switch over cannot occur.

Recovery  Start the backup process, then switch to it.

Cause  SMF could not map a logical file to a physical file, most likely because of file code or file type discrepancies.

Effect  The request for which file mapping is required cannot be processed.

Recovery  Determine the correct file attributes, and resubmit the request. If required, delete and recreate the file.

Cause  A transaction could not be started when the PENDOPS catalog file was being used to complete an outstanding operation. The PENDOPS file is used when SMF needs to recover outstanding operations in progress when an interruption, such as a CPU failure, occurs.

Effect  Recovery is not completed, but SMF retries.

Recovery  If SMF is unsuccessful after retrying recovery, try to determine why by using the file system error as a guide. See the Guardian Procedure Errors and Messages Manual for information on the file system error that occurred. As a last resort, you can use SMFIXUP to purge and recreate the PENDOPS catalog file, but none of the pending operations about which it contains information will be recoverable.

Cause  Internal memory resources sufficient to allocate a required buffer were not available. This error can be the result of a large number of concurrent requests.

Effect  The request for which a buffer could not be allocated is not processed.

Recovery  Retry the operation later. If the problem persists and cannot be traced to a large number of outstanding requests, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred while SMF attempted to process a request.

Effect  The request is not processed.

Recovery  If the problem persists, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The version of SMF is incompatible with the process that issued a request.

Effect  The request is not processed.

Recovery  Determine the versions of requestor processes, including DP2, and SMF processes, and correct incompatibilities before retrying the request.

Cause  An internal resource problem prevented a thread required to process a request from being created.

Effect  The request is not processed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The lock manager could not obtain the locks required to process a request, most likely because there are a large number of concurrent requests being processed for a particular object.

Effect  The request is not processed.

Recovery  Re-issue the request after the number of concurrent transactions diminishes. If the problem persists, an internal error may have occurred. Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A request contained a semantically or syntactically invalid parameter. Either the value of a parameter was invalid or an operation could not be performed for configuration reasons, as when an attempt is made to add a remote volume to a storage pool or to associate a volume with a storage pool that is not configured for a volume of that type.

Effect  The request is not processed.

Recovery  Resubmit the request, using a valid parameter value.

Cause  The current maximum of 50 opens of a catalog file for a particular object has been reached.

Effect  The request is processed after some delay.

Recovery  Informational message only; no corrective action is needed.

Cause  A storage pool or virtual disk could not be added, deleted, or redefined because the transaction required to update the catalog files could not be ended.

Effect  The transaction is rolled back and the operation is not performed.

Recovery  See the Guardian Procedure Errors and Messages Manual for recovery procedures appropriate for the file system error number returned by TMF in another event in the event log.

Cause  The SAFE.GUARD file for a VDP is not available or cannot be read.

Effect  All file access attempts are denied.

Recovery  Make the SAFE.GUARD file available to the VDP.

Cause  A storage pool process encountered a problem while communicating with $ZSMS or DP2, most likely because of a version incompatibility.

Effect  SMF cannot function normally.

Recovery  Ensure that all versions of products with which SMF interacts are compatible with the version of SMF you are using. If you are unable to fix the problem by adjusting version levels, contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A request could not be processed because a version incompatibility exists or a storage pool or virtual disk process was in a state inappropriate for a particular request.

Effect  The request is not processed.

Recovery  Ensure that all version compatibility requirements are satisfied, or ensure that a process is in the state appropriate for the request.

Cause  A request to redefine, delete, or otherwise configure a storage pool process could not be processed because the storage pool process is not fully defined.

Effect  The request is rejected.

Recovery  Configure the storage pool process completely and put it into a state appropriate for the request before resubmitting the request.

Cause  A file system error occurred during storage pool process definition.

Effect  The storage pool could not be defined.

Recovery  Follow the suggestions associated with the file system error number in the Guardian Procedure Errors and Messages Manual.

Cause  $ZSMS received a request it could not process because of a version incompatibility problem.

Effect  The request could not be processed.

Recovery  Resolve the version compatibility problem before resubmitting the request.

Cause  An error occurred when opening and scanning the PENDOPS file to recover an incomplete operation. Usually this event is associated with an internal resource problem.

Effect  The recovery operation could not be performed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error occurred when opening and scanning the PENDOPS file to recover an incomplete operation. Usually this event is associated with an internal resource problem.

Effect  The recovery operation could not be performed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A virtual disk process could not be defined because a file system error occurred.

Effect  The process is not defined.

Recovery  See the Guardian Procedure Errors and Messages Manual for suggestions on handling the file system error returned.

Cause  A virtual disk process rejected a request to place one of its catalog files in a particular subvolume, most likely because the subvolume name is invalid.

Effect  The catalog file cannot be placed in the subvolume specified.

Recovery  Retry the request, using a valid subvolume name.

Cause  An invalid backup CPU number was specified in a request.

Effect  The request is rejected.

Recovery  Retry the request, specifying a valid backup CPU number.

Cause  An incorrect catalog volume was specified in a request.

Effect  The request is not processed.

Recovery  Resubmit the request, specifying a volume name that exists on the local system.

Cause  An invalid value for EMS error reporting mode was specified in a request.

Effect  The request is rejected.

Recovery  Specify either NOISY or QUIET for the EMS reporting mode parameter value when resubmitting the request.

Cause  A request specified an invalid $ZSMS process name.

Effect  The request is not processed.

Recovery  Retry the request, specifying a legal $ZSMS process name on the local system.

Cause  An attempt to recover from a previously incomplete request failed. The request is typically a file system request (to create or otherwise operate on a physical file) or a request to delete or redefine a storage pool or virtual disk process. The failure may have been caused because a lock could not be obtained, or it may be the result of an internal problem.

Effect  The SMF process that experienced the failure stops running.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A recovery operation could not be completed because a PENDOPS semaphore could not be obtained. This error is caused by an internal resource problem.

Effect  Recovery is not completed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A minor inconsistency occurred while SMF attempted to recover from an incomplete include or exclude operation on a storage pool process.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A volume could not be included in or excluded from a storage pool because a file system error occurred when SMF attempted to access the MVTABLE catalog file.

Effect  The request is not performed.

Recovery  Recovery depends on the file system error. Consult the Guardian Procedure Errors and Messages Manual for recovery suggestions based on the error number associated with this event.

Cause  The PENDOPS table is invalid or corrupted.

Effect  Recovery operations cannot be performed.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internal error in the thread manager occurred.

Effect  The thread manager stops running.

Recovery  Contact your service provider and provide this information:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A backup process has started.

Effect  A backup process exists.

Recovery  Informational message only; no corrective action is needed.

Cause  A mismatch was detected between the configured and the actual primary CPU.

Effect  The primary will switch to the configured CPU.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt was made to run an SMF process with a version of the operating system that does not support SMF.

Effect  The process is stopped.

Recovery  Load correct version of operating system and retry the operation.

Cause  An error occurred while processing a PENDOPS recovery operation.

Effect  The recovery operation is not completed.

Recovery  The operation is retried automatically. If the operation fails, attempt abandon or completion operation using the SMFIXUP ABANDONPENDOPS or COMPLETEPENDOPS commands. If the abandon or completion operation fails, suspend the PENDOPS operation and attempt the abandon and completion operation again.

Cause  An attempt was made to delete either a pool process that still contains volumes, or a VDP that still contains logical files.

Effect  The process is not deleted from the system.

Recovery  For a VDP: Use COUP to delete all of the files on the VDP. If the files are inaccessible, use the SMFIXUP ZOT command to remove the file entries in the ANT file. Note that if the COUP DELETE ! option is used, the SMF catalog files and the files on the VDP will be left intact. This situation might result in orphaned files left on the physical disk.

For a pool process: Issue a PUP EXCLUDE command to exclude all the volumes from the pool. However, note that excluding volumes might result in an error if VDPs that have registered interest in the pool are not accessible. For an exclude to function correctly, VDPs should not have files on the physical volume. Also, note that performing an exclude with the ! option might result in orphaned files on the volume.

A second option for pool processes is to delete the pool with a ! option. This should be attempted in extreme cases; that is, when VDPs cannot be deleted before deleting the pool.

Cause  An attempt has been made to delete an SMF process that has pending operations in the PENDOPS table.

Effect  The delete operation is completed even though there are some objects on which recovery is pending.

Recovery  No recovery is possible. The ! option was used with the DELETE command.

Cause  The SMF process has started to delete its catalog files.

Effect  The catalog files will be deleted.

Recovery  Informational message only; no corrective action is needed.

Cause  The SMF process has successfully deleted a catalog file.

Effect  If no errors are encountered, the operation will run to completion.

Recovery  Informational message only; no corrective action is needed.