Chapter 121 TMF Messages

For each message, the applicable text (presented in this chapter) immediately follows the above message header in the target log.

Cause  The TMF Management Process (TMP) was ready to write audit information to the specified active audit volume, but could not because a file-system error occurred.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 audit disk process (ADP) attempted to write audit information to the specified active audit volume, but could not because the volume is in an invalid state.

Effect  The TMF subsystem crashes.

Recovery  Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF subsystem has shut down.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The audit disk process (ADP) tried to flush audit information from a buffer to the specified active audit volume, but could not because a file-system error occurred.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 process that started the specified transaction failed.

Effect  The transaction is aborted.

Recovery  Informational message only; no corrective action is needed. If a large number of these messages are generated, however, there might be a problem with the application.

Cause  The audit disk process (ADP) tried to write audit information to the specified active audit volume, but could not because a file-system error occurred.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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  As part of subsystem startup, the TMF subsystem attempted to repair the end of file (EOF) marker of the specified audit-trail file, but could not because a file-system error occurred.

Effect  The TMF subsystem does not start.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued a START TMF command, but the TMF subsystem cannot start because of problems with an audit trail.

Effect  The TMF subsystem does not start until the problem has been corrected.

Recovery  There should be preceding error messages in the Event Management Service (EMS) log indicating more clearly what the problem is. Attempt to correct the situation and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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  While attempting to access the specified audit-trail file, the TMF subsystem detected that the status code in the file label is inconsistent with the type of TMF volume on which the file resides.

Effect  The TMF subsystem crashes.

Recovery  Contact your service provider and provide all relevant information as follows:

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  While attempting to access the specified audit-trail file, the TMF subsystem detected that the specified file attribute, stored in the file label, is invalid.

Effect  The TMF subsystem crashes.

Recovery  Contact your service provider and provide all relevant information as follows:

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  While attempting to access the specified audit-trail file, the TMF subsystem detected that the file is corrupt.

Effect  The TMF subsystem crashes.

Recovery  Contact your service provider and provide all relevant information as follows:

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 prevented the TMF subsystem from accessing the specified audit-trail file.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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  While attempting to access an audit-trail file, the TMF subsystem detected that the audit-trail file has an invalid initialization sequence number in its file label.

Effect  The TMF subsystem crashes.

Recovery  Contact your service provider and provide all relevant information as follows:

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 prevented the TMF subsystem from accessing the audit information (AUDINFO) file, which is located in the $SYSTEM.ZTMFCONF subvolume.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued an ALTER AUDITTRAIL command changing the number of files per volume, but the TMF subsystem could not do so on the specified volume because a file-system error occurred.

Effect  The ALTER AUDITTRAIL command fails.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and reissue the command. If the problem persists, contact your service provider and provide all relevant information as follows:

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  While the TMF subsystem was attempting to open an audit-trail file, a file‑system error occurred.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 prevented the TMF subsystem from performing an operation to the disk process for the specified active audit volume.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued an ADD AUDITTRAIL command, but the command failed and some of its effects could not be undone.

Effect  The previous audit-trail configuration might be corrupted, further audit-trail configuration might not be possible, and you might not be able to start the TMF subsystem.

Recovery  Attempt to determine why the command failed. Delete the TMF subsystem and add all the audit trails again. If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued an ALTER AUDITTRAIL command, but the command failed and some of its effects could not be undone.

Effect  The previous audit-trail configuration might be corrupted, further audit-trail configuration might not be possible, and you might not be able to start the TMF subsystem.

Recovery  Issue an INFO AUDITTRAIL command to determine the content of the current configuration. If you can ascertain what the problem is, issue an ALTER AUDITTRAIL command to fix it. If the problem persists, contact your service provider and provide all relevant information as follows:

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 prevented the TMF subsystem from performing an operation on the specified audit-trail file.

Effect  The TMF subsystem crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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  As part of subsystem startup, the TMF subsystem could not find any audit-trail files on the configured active audit volume or volumes for the specified audit trail.

Effect  The TMF subsystem does not start.

Recovery  Contact your service provider and provide all relevant information as follows:

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  As part of subsystem startup, the specified audit trail is configured for audit dumping, but has no configured restore audit volumes.

Effect  The TMF subsystem does not start.

Recovery  Configure at least one restore audit volume for the specified audit trail and then try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued an ADD AUDITTRAIL command, defining the specified audit trail as indicated in the message.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITTRAIL command, redefining the FILESPERVOLUME attribute as shown in the message.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITTRAIL command, redefining the OVERFLOWTHRESHOLD attribute as indicated in the message.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITTRAIL command, redefining the BEGINTRANSDISABLE attribute as indicated in the message.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITTRAIL command, redefining the AUDITDUMP attribute as indicated in the message.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITTRAIL command, adding the specified disk volume to the specified audit trail as indicated in the message.

Effect  The disk volume is added to the audit trail as the specified type.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITTRAIL command, deleting the specified disk volume from the specified audit trail as indicated in the message.

Effect  The disk volume is deleted from the audit trail as the specified type.

Recovery  Informational message only; no corrective action is needed.

Cause  A file-system error occurred while the TMF subsystem was purging one or more files on the specified active audit volume. As a result, the volume might have unwanted audit-trail files on it.

Effect  None. This message typically occurs while an active audit volume is being deleted from the TMF configuration.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF subsystem detected an invalid type of file in the ZTMFAT subvolume on the designated active audit volume.

Effect  The volume is not allowed to be added to the TMF configuration.

Recovery  Try moving or deleting the offending file from the ZTMFAT subvolume. Alternatively, choose a different volume to hold audit-trail files.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 designated audit trail has no overflow audit volumes.

Effect  None. If all of the audit-trail files become filled and are “pinned” on disk, however, transaction processing stops until either the files become free or you add an overflow audit volume to the audit-trail configuration.

Recovery  Informational message only; no corrective action is needed. It is advisable, however, to always configure at least one overflow audit volume for each trail.

Cause  The operator issued a START TMF command without having configured any audit trails.

Effect  The TMF subsystem does not start.

Recovery  Add at least a master audit trail (MAT) with two or more files per volume, then reissue the START TMF command.

Cause  A file-system error prevented the TMF subsystem from performing a FIND_START_ operation for the designated file.

Effect  The TMF subsystem crashes (or does not start, if you are trying to start TMF).

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 prevented the TMF subsystem from performing a FIND_NEXT_ operation for the designated file.

Effect  The TMF subsystem crashes (or does not start, if you are trying to start the TMF subsystem).

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem and restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF subsystem was attempting to prepare the next audit-trail file for a rollover, but could not because there were no available files.

Effect  Transaction processing eventually stops if an audit-trail file does not become available.

Recovery  If the audit-trail files are “pinned” on the disk because audit dumping is disabled, you could reenable audit dumping to free up some files. You also could issue an ALTER AUDITTRAIL command to add another active audit volume or to increase the FILESPERVOLUME attribute value.

Cause  The TMF subsystem found an available audit-trail file, and the rollover was successful.

Effect  Transaction processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  While the TMF subsystem was waiting for an audit-trail file to become available, an operator issued a STOP TMF command.

Effect  The TMF subsystem stops.

Recovery  Informational message only; no corrective action is needed.

Cause  The audit trail rolled over from the previous audit-trail file to the designated one.

Effect  Transaction processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The designated audit-trail volume, which was down, has come back up.

Effect  Transaction processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The designated audit-trail volume is down.

Effect  Audit-trail performance could be degraded.

Recovery  If you can, bring the volume back up. If the volume contains no files, or is a restore audit volume, try deleting it from the TMF configuration and adding another disk volume in its place.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 its volume came up, the specified audit-trail file was missing.

Effect  The TMF subsystem crashes.

Recovery  Contact your service provider and provide all relevant information as follows:

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  While attempting to start the TMF subsystem, or when a configured active audit volume comes up, a series of audit-trail files (beginning with the designated file) was out of sequence.

Effect  The TMF subsystem crashes (or does not start, if you are trying to start TMF).

Recovery  Contact your service provider and provide all relevant information as follows:

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 designated audit-trail volume is down.

Effect  Audit-trail performance could be adversely affected.

Recovery  If you can, bring the volume back up. If the volume contains no files, or is a restore audit volume, try deleting it from the TMF configuration and adding another disk volume in its place.

If the problem persists, contact your service provider and provide all relevant information as follows:

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  While starting a version of TMF that only supports Format 1 audit trail files, the TMP detected that the specified audit trail file is a Format 2 file.

Effect  The START TMF command fails.

Recovery  Delete TMF (which deletes all audit trail files, including the specified Format 2 file), and then restart this version of TMF.

Cause  The operator issued a START TMF command.

Effect  The TMF subsystem is starting.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a START TMF command.

Effect  The TMF subsystem is started.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a STOP TMF command.

Effect  The TMF subsystem is stopping.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a STOP TMF command.

Effect  The TMF subsystem is stopped.

Recovery  Informational message only; no corrective action is needed.

Cause  A file-system error prevented the TMF subsystem from performing the designated operation on the specified configuration file.

Effect  The TMF Management Process (TMP) cannot be created. If the error occurs after the TMP is started, the TMP abends because it cannot create other TMF processes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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 specified TMF process could not be started, or it failed, because a file-system error occurred.

Effect  The TMF Management Process (TMP) attempts to recreate the TMF process, at incremental time intervals of up to five minutes, until the process is successfully started.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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  This is an action completion message associated with TMF message 125. It is generated each time the TMF Management Process (TMP) attempts to recreate the failed TMF process.

Effect  The TMP attempts to recreate the TMF process, at incremental time intervals of up to five minutes, until the process is successfully started.

Recovery  See the preceding TMF message 125. For a definition of the error specified in the preceding 125 message, including recovery actions, see Appendix B. For a more detailed definition of the specified error, including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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  While attempting to start the specified process, the TMF subsystem found that the configuration record for the process had the wrong version number.

Effect  The process cannot be started.

Recovery  Contact your service provider and provide all relevant information as follows:

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 operator issued a DISABLE DATAVOL command, disabling the specified data volume for transaction processing.

Effect  The data volume is disabled and cannot be used for transaction processing until it is reenabled.

Recovery  Informational message only; no corrective action is needed. To restart the volume for transaction processing, issue an ENABLE DATAVOL command.

Cause  The specified data volume went down for TMF transaction processing.

Effect  The volume is disabled and cannot be used for transaction processing until it is reenabled.

Recovery  See the description of DISK message 5012. If the problem persists, contact your service provider and provide all relevant information as follows:

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.

When the problem has been corrected, issue an ENABLE DATAVOL command to restart the volume for transaction processing.

Cause  The operator issued an ADD DATAVOL command, successfully adding the specified volume to the TMF configuration as a data volume. If the operator has specified the IGNOREPREVIOUSCONFIG option when adding the volume, that fact is logged.

Effect  The volume is configured as a TMF data volume and remains as such until it is explicitly deleted (DELETE DATAVOL command) or until the entire TMF configuration is deleted (DELETE TMF command).

Recovery  Informational message only; no corrective action is needed.

Cause  The specified data volume has been started for transaction processing.

Effect  The data volume can be used for audited database access.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER DATAVOL command, changing the specified data volume’s attribute values as indicated in the message.

Effect  The new attribute values take effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified data volume was shut down in conjunction with stopping the TMF subsystem.

Effect  The volume is no longer available for transaction processing, but it can be used for nonaudited activities.

Recovery  Informational message only; no corrective action is needed. The volume is restarted as an audited data volume the next time the TMF subsystem is started.

Cause  The data volume has been disabled, either by operator command (DISABLE DATAVOL) or due to an unexpected failure. This error message is always preceded in the Event Management Service (EMS) log by another error message (TMF 128, 129, 137, or 139), which specifies why the volume was disabled.

Effect  The data volume is disabled and cannot be used for transaction processing until it is reenabled.

Recovery  See the recovery text associated with the preceding TMF error message in the EMS log.

Cause  The operator issued an ENABLE DATAVOL command, enabling the specified data volume.

Effect  The TMF subsystem attempts to start the data volume for transaction processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a DELETE DATAVOL command, successfully deleting the specified data volume from the TMF configuration. The status of the volume is clean or dirty, as indicated. (A dirty volume could contain inconsistent data.) If the operator has specified the ALLOWINCONSISTENCY option when deleting the volume, that fact is logged.

Effect  The data volume is no longer in the TMF configuration.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified data volume could not be started for transaction processing because a file-system error occurred.

Effect  The data volume is disabled and cannot be used for transaction processing until it is reenabled.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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.

When the problem has been corrected, issue an ENABLE DATAVOL command to have the TMF subsystem restart the data volume.

Cause  The physical disk drive is not the one the TMF subsystem expected to find with the specified volume name.

Effect  The data volume cannot be used for transaction processing.

Recovery  Mount the correct disk pack or mirror. If the volume was renamed, rename it to the expected name. If the currently mounted disk pack is used for transaction processing:

Cause  The specified data volume could not be enabled for transaction processing because a fatal error occurred during volume recovery.

Effect  The data volume is disabled and cannot be used for transaction processing until it is reenabled.

Recovery  See previous error messages in the Event Management Service (EMS) log that pertain to volume recovery. If the problem persists, contact your service provider and provide all relevant information as follows:

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.

When the problem has been corrected, issue an ENABLE DATAVOL command to have the TMF subsystem restart the data volume.

Cause  The operator issued a START TMF command, but the TMF subsystem would not start.

Effect  The TMF subsystem is down.

Recovery  Examine the preceding error messages in the Event Management Service (EMS) log and try to diagnose what happened. After attempting to correct the situation, issue another START TMF command.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued a DELETE TMF command.

Effect  The current TMF configuration is being deleted.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a START TMF command, but the TMF subsystem would not start because the primary TMF Management Process (TMP) failed.

Effect  The TMF subsystem is down.

Recovery  Examine preceding error messages in the Event Management Service (EMS) log and try to diagnose what happened. If the TMP failed due to an unrelated processor failure, for example, issue another START TMF command immediately.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 operator issued a DELETE TMF command.

Effect  The TMF configuration is deleted.

Recovery  Informational message only; no corrective action is needed.

Cause  The primary TMF Management Process (TMP) failed, and the backup TMP either could not be started or also failed.

Effect  There is no backup TMP.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Examine the preceding error messages in the Event Management Service (EMS) log and try to diagnose what happened. If the situation is caused by a processor failure, for example, then the backup TMP is started after the processor has been reloaded. If the situation is caused by insufficient disk space for the extended data segment (file-system error 143), then make more disk space available.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 primary TMF Management Process (TMP) failed.

Effect  The backup TMP attempts to take over.

Recovery  Usually an informational message only; no corrective action is needed. However, if the process terminated abnormally, an internal error has occurred; see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Contact your service provider and provide all relevant information as follows:

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 operator issued a START TMF command, but the TMF subsystem would not start because the primary TMF Management Process (TMP) failed and the backup TMP was not yet able to take over.

Effect  The TMF subsystem is down.

Recovery  Issue another START TMF command. If the error condition persists, contact your service provider and provide all relevant information as follows:

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 primary TMF Management Process (TMP) failed, and the backup TMP has successfully taken over.

Effect  Transaction processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a START TMF command.

Effect  The TMF subsystem starts.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a STOP TMF or STOP TMF, ABRUPT command.

Effect  The TMF subsystem stops.

Recovery  Informational message only; no corrective action is needed.

Cause  While TMF was attempting to start, a file-system error occurred for the specified configuration file.

Effect  TMF crashes.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 specified configuration file has a version number that is not consistent with the version number of the installed TMF software.

Effect  TMF crashes.

Recovery  Contact your service provider and provide all relevant information as follows:

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 prevented the TMF subsystem from allocating an extended segment on the specified disk volume.

Effect  The TMF process abends.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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  TMF was attempting to prepare the next preallocated audit trail file in anticipation of a rollover, but could not.

Effect  The file-creation operation is retried, and transaction processing continues. When the active audit trail becomes too full, however, transaction processing in conjunction with that audit trail ceases until a rollover can be performed successfully.

Recovery  Determine why the preallocated file could not be created (look at some of the preceding messages in the EMS log for clues), and then correct the problem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 attempting to open an audit-trail file.

Effect  An attempt is made to retry opening the audit-trail file.

Recovery  Informational message only; no corrective action is needed.

Cause  A preceding operation listed in the Event Management Service (EMS) log has begun.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  A preceding operation listed in the Event Management Service (EMS) log has finished.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  During a file recovery operation, a file-system error occurred while the TMF Management Process (TMP) was attempting to execute the specified command.

Effect  The TMP abends.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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 requested operation has been cancelled.

Effect  Transaction processing continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The TMP received an unexpected error from a disk process.

Effect  Unspecified. This event should not occur.

Recovery  Contact your service provider and provide all relevant information as follows:

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 file recovery list process has selected these files to be recovered. Up to 10 files are listed in each event.

Effect  None

Recovery  Informative message only; no corrective action is needed.

Cause  The file recovery process has successfully recovered the listed files. Up to 10 files are listed in each event.

Effect  None

Recovery  Informative message only; no corrective action is needed.

Cause  This is a summary message specifying how many database tables or files were successfully recovered, and how many were not.

Effect  None

Recovery  Informative message only; no corrective action is needed.

Cause  A volume or file recovery operation was interrupted by a disk process takeover for the specified volume.

Effect  Because all TMF recovery operations use buffered writes, a disk process takeover means that some updates to data blocks in cache within the last 10 minutes might not have reached disk. Therefore, the recovery process backs up to a preceding location within the audit trail and resumes processing. The preceding location is specified in the error message.

Recovery  Informational message only; no corrective action is needed.

Cause  A backout operation was interrupted by a disk process takeover for the specified volume.

Effect  Because all TMF recovery operations use buffered writes, a disk process takeover means that some updates to data blocks in cache within the last 10 minutes might not have reached disk. The backout process immediately terminates work on its current set of transactions and informs the TMF Management Process (TMP) that it performed no work. The TMP then resubmits the same set of transactions to the backout process, plus any new aborted transactions that it may have acquired.

Recovery  Informational message only; no corrective action is needed.

Cause  A file-system error occurred against the specified file while a recovery process was attempting the specified operation. The affected audit record is located at the position specified in the error message.

Effect  The effect of this error depends on which recovery process was used.

For backout, this error message is accompanied by a second message (171 or 172) that indicates the effect.

For volume or file recovery, this error message is accompanied by message 171. The file is marked either “redo-needed” or “undo-needed” and is no longer available for transaction processing.

Recovery  If the backout process was involved and the error message is accompanied by message 172, then some type of recovery action may be required, depending upon the status indicated by message 172. If the status is “ignored,” then no recovery action is needed immediately (although the affected file is no longer consistent). If the status is “retried,” then no recovery action is needed unless the transaction becomes “hung.” In the latter case, see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If either the volume recovery process or the file recovery process was involved, then the error is serious and file recovery is needed.

Cause  A file-system error occurred for the specified file while a recovery process was attempting the specified operation.

Effect  The effect of this error depends on which recovery process was used.

For backout, this error message is accompanied by a second message (171 or 172) that indicates the effect.

For volume or file recovery, this error message is accompanied by message 171. The file is marked either “redo-needed” or “undo-needed” and is no longer available for transaction processing.

Recovery  If the backout process was involved and the error message is accompanied by message 172, then some type of recovery action may be required, depending upon the status indicated by message 172. If the status is “ignored,” then no recovery action is needed immediately (although the affected file is not in a consistent state). If the status is “retried,” then no recovery action is needed unless the transaction becomes “hung.” In the latter case, see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If either the volume recovery process or the file recovery process was involved, then the error is serious and file recovery is needed.

Cause  A file-system error affecting the entire volume occurred while a recovery process was attempting the specified operation.

Effect  The recovery process immediately terminates any further operations on the specified volume. The volume is not available for transaction processing. If the volume is subsequently specified in a ENABLE DATAVOL command, the volume recovery process automatically attempts to recover the volume.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 process has encountered an error for the specified file and has terminated recovery of the file. The preceding error message in the Event Management Service (EMS) log generated by the recovery process (message 168 or 169) specifies the particular error and other related information.

Effect  See the effect text associated with the preceding error message generated by the particular recovery process (168 or 169).

Recovery  See the recovery text associated with the preceding error message generated by the particular recovery process (168 or 169).

Cause  The backout process encountered an error while attempting to undo the transaction. This error message is always preceded by either operator message 168 or 169, which lists the error.

Effect  The transaction is retried or ignored, as indicated in the message.

If the status is “retried,” then the backout process terminates work on this transaction and the TMF Management Process (TMP) resubmits the transaction identifier to the backout process to try again to undo the transaction. If the TMP has already submitted the transaction identifier to the backout process three times, then the TMP hangs the transaction.

If the status is “ignored,” then the backout process ignores the error on the affected file and continues to perform any other undo on behalf of the specified transaction.

Recovery  To determine if the transaction is “hung,” issue a STATUS TRANSACTION command, specifying the particular transaction identifier.

If the transaction is “hung,” see the Guardian Procedure Errors and Messages Manual for a definition of the specified error and to see if the file-system error can be corrected. If recovery is possible, perform the corrective action, then issue an ABORT TRANSACTION command, specifying the particular transaction identifier.

If the status indicated by this error message is “ignored,” then no recovery action is immediately needed, but the affected file is not in a consistent state. If the problem persists, contact your service provider and provide all relevant information as follows:

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  One of the TMF recovery processes encountered a problem while attempting to read an audit-trail file.

Effect  The recovery process abends.

In the case of volume recovery, the process is not restarted. The affected data volume is flagged as needing recovery and is disabled for transaction processing.

In the case of backout or file recovery, the TMF Management Process (TMP) restarts the process. If the error was transitory, the recovery operation continues to completion. If the error persists, the recovery process abends again and is restarted. The restart attempts occur at successively longer time intervals.

Recovery  If the audit read error is FORMAT2FILE or FORMAT2REC, it means that the current version of TMF supports only Format 1 audit trail files and that the recovery process encountered a Format 2 file or record. You should do either of the following:

For all other audit read exceptions, this is a serious event. If a data volume is disabled, its unavailability could degrade the performance of one or more applications. If either backout or file recovery is retried many times, audit-trail files could get pinned on the disk, causing the audit trail to reach the overflow threshold.

Contact your service provider and provide all relevant information as follows:

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 backout process could not back out the specified transaction, and stopped after retrying the maximum number of times.

Effect  The process ceases to retry backing out the specified transaction.

Recovery  Try aborting the transaction. If the error persists, contact your service provider and provide all relevant information as follows:

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  File recovery to a timestamp, or to the first purge record, was performed on the specified file, and an online dump was not made immediately afterwards.

Effect  The specified file can only be recovered to a timestamp before the previous file recovery operation. All audit information for the specified file following the file hiatus record in the audit trail is inaccessible.

Recovery  After performing file recovery to a timestamp or to first purge, make an online dump of the file immediately.

Cause  While a recovery operation was in progress, the TMF Management Process (TMP) stopped.

Effect  The recovery process abends.

Recovery  If a file recovery operation was in progress, restart the process by issuing another RECOVER FILES command. If a volume recovery operation was in progress, issue an ADD DATAVOL[S] command to add the affected volumes to the configuration again. If a backout operation was in progress, the backout process automatically restarts when the TMP is restarted.

Cause  The configured process file segment (PFS) size is too small to enable the recovery process to recover all files.

Effect  The recovery process abends.

Recovery  Issue an ALTER PROCESS command to increase the process’s extended segment size.

If the configured extended segment size is already set to its maximum value, limit the number of files that the process needs to recover, as follows:

Cause  The TMF recovery program files cannot recover NonStop SQL/MP objects because they are not licensed.

Effect  The recovery process abends.

Recovery  License the TMF recovery program files: TMFBOUT (backout), TMFVRCV (volume recovery), and TMFFRCV (file recovery).

Cause  Either the sno or rba entered with the TOMATPOSITION option of a FILE RECOVERY command falls below the sno or rba of the online dump.

Effect  The specified file can only be recovered to an audit trail and rba position after the end of the online dump. No files will be recovered.

Recovery  Change the audit trail sequence number or rba in the TOMATPOSITION option of the RECOVER FILES command and reexecute the command.

Cause  The TMF Management Process (TMP) failed, and its backup could not successfully take over.

Effect  The TMF subsystem crashes.

Recovery  Try to determine why the TMP failed (because of a processor failure, for example). Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF subsystem crash just finished.

Effect  The TMF subsystem is down.

Recovery  Examine preceding error messages in the Event Management Service (EMS) log and try to determine why the TMF subsystem crashed. Try to restart the TMF subsystem. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF Management Process (TMP) failed or could not be started because a file-system error occurred.

Effect  The TMF subsystem is down.

Recovery  See Appendix D, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. The subsystem periodically attempts to restart the TMP.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 designated TMFMON2 process failed or could not be started because a file-system error occurred.

Effect  The processor being reloaded failed.

Recovery  See Appendix D, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Try to resolve the problem.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 Process_Create error occurred while the TMF subsystem was attempting to create a TMFMON2 process in the specified processor.

Effect  The TMF subsystem does not start.

Recovery  See Appendix D, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 specified audit-trail file is pinned on the disk.

Effect  None. If all of the audit-trail files become filled and are pinned on disk, however, transaction processing stops until one or more of them become free.

Recovery  Consider the reason specified in the message, and try to correct the situation (if audit dumping is disabled, enable it; if the active audit volume is down, bring it back up). If several audit-trail files become pinned simultaneously, add another overflow audit volume to the audit-trail configuration.

Cause  The TMF subsystem is trying to stop, but there is a Remote Duplicate Database Facility (RDF) process running which has requested that the TMF subsystem not stop until either the RDF subsystem or the particular RDF process stops.

Effect  The TMF subsystem cannot stop. This message is repeated every 10 seconds until the TMF subsystem can stop.

Recovery  Usually this situation is transitory because the RDF subsystem is not very far behind the TMF subsystem in reading recently generated audit information. If the condition does not go away within a reasonable period of time (usually not more than 30 minutes), however, you might want to consider manually shutting down the RDF.

Cause  The audit disk process (ADP) is suspending audit generation requests because the specified audit trail is full.

Effect  Unless space in the audit trail is made available, audit-generating events will be suspended.

Recovery  Try to determine why the oldest audit-trail file is pinned on disk. If the problem cannot be resolved, configure an overflow volume for the audit trail. The oldest audit-trail files will then automatically be copied to the overflow audit volume, freeing space in the audit trail. Alternatively, increase the size of the audit trail by either increasing the FILESPERVOLUME attribute or adding an active audit volume.

Cause  Space has been made available in the audit trail, and normal processing has resumed. This message documents the resolution of TMF action event 187 (see message 187).

Effect  The TMF subsystem resumes normal operations.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified file was included in a RECOVER FILES command, but a file‑system error occurred while the TMF subsystem was searching for an appropriate entry in the TMF catalog.

Effect  File recovery is not attempted on the specified file.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If the problem persists, contact your service provider and provide all relevant information as follows:

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 specified file was included in a RECOVER FILES command, but the TMF subsystem could not find a valid entry for it in the TMF catalog.

Effect  File recovery is not attempted.

Recovery  Contact your service provider and provide all relevant information as follows:

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 specified files were included in a RECOVER FILES command, but the TMF subsystem could not find valid entries for them in the TMF catalog.

Effect  File recovery is not attempted.

Recovery  Contact your service provider and provide all relevant information as follows:

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 specified file was included in a RECOVER FILES command, but the TMF subsystem could not find a valid entry for it in the TMF catalog.

Effect  File recovery is not attempted.

Recovery  Contact your service provider and provide all relevant information as follows:

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 operator issued a RECOVER FILES command without including either the FROMARCHIVE attribute or the TIME attribute (which automatically invokes FROMARCHIVE).

Effect  The file is not recovered.

Recovery  Reissue the RECOVER FILES command and include either the FROMARCHIVE or TIME attribute.

Cause  The specified file was marked bad, crashopen, or crashlabel; and the operator did not include either the FROMARCHIVE attribute or the TIME attribute (which automatically invokes FROMARCHIVE) in the RECOVER FILES command.

Effect  The file is not recovered.

Recovery  Reissue the RECOVER FILES command and include either the FROMARCHIVE or TIME attribute.

Cause  The specified file was included in a RECOVER FILES command, but it is already being recovered as the result of a preceding RECOVER FILES command.

Effect  The existing file recovery process recovers the file.

Recovery  Informational message only; no corrective action is needed.

Cause  The TMF file recovery list (TMFFRLS) process tried to add the specified file name to the file recovery list file, but could not because a file-system error occurred.

Effect  The TMFFRLS process terminates, then is automatically restarted by the TMF Management Process (TMP).

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF subsystem could not search the specified volume during a RECOVER FILES operation. The volume was either not configured or not started as a TMF data volume.

Effect  File recovery is not attempted on the specified volume.

Recovery  If the volume has files that need to be recovered, use a STATUS DATAVOLS command to determine why the volume is not started for TMF processing. Resolve the problem and reissue the RECOVER FILES command for the volume. If the volume does not contain files to be recovered, consider removing it from future RECOVER FILES commands to avoid this event.

Cause  The specified recovery time is as old as, or older than one or more file dump entries in the catalog.

Effect  TMF does not recover any file whose dump entry “Date and Time” is not at least one second more recent than the TIME option specified in the RECOVER FILES command.

Recovery  Identify those files that were not recovered by comparing the “Date and Time” field from the INFO DUMPS, DETAIL command with the specified TIME option in the RECOVER FILES command. Issue another recovery operation for those files using an appropriately later TIME.

Cause  The TMF catalog shows that there are no more scratch tapes available.

Effect  You cannot make any new audit dumps or online dumps until a sufficient number of scratch tapes are available.

Recovery  Add more scratch tapes to the catalog, or change the status of existing tapes in the catalog that are no longer needed to SCRATCH.

Cause  Scratch tapes have been added to, or made available within, the TMF catalog.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  See the cause section for the specified dump/restore message.

Effect  See the effect section for the specified dump/restore message.

Recovery  See the recovery section for the specified dump/restore message.

Cause  See the cause section for the specified dump/restore message.

Effect  See the effect section for the specified dump/restore message.

Recovery  See the recovery section for the specified dump/restore message.

Cause  See the cause section for the specified archive tape message.

Effect  See the effect section for the specified archive tape message.

Recovery  See the recovery section for the specified archive tape message.

Cause  See the cause section for the specified archive tape message.

Effect  See the effect section for the specified archive tape message.

Recovery  See the recovery section for the specified archive tape message.

Cause  See the cause section for the specified archive tape message.

Effect  See the effect section for the specified archive tape message.

Recovery  See the recovery section for the specified archive tape message.

Cause  See the cause section for the specified archive tape message.

Effect  See the effect section for the specified archive tape message.

Recovery  See the recovery section for the specified archive tape message.

Cause  The specified audit trail has been dumped to tape.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The dump/restore process encountered an error.

Effect  The dump/restore process abends. The TMF Management Process (TMP) periodically attempts to recreate the dump/restore process until successful.

Recovery  Referring to the supplied text and to preceding messages in the Event Management Service (EMS) log, try to diagnose what happened. If the problem persists, contact your service provider and provide all relevant information as follows:

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 specified audit trail has been dumped to disk.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The online dump with the specified dump serial number has been dumped successfully to tape.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The online dump with the specified dump serial number has been dumped successfully to disk.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The TMF subsystem could not locate the specified disk online-dump file in conjunction with a RECOVER FILES operation. This error message is reissued every 10 minutes until the file is available.

Effect  The RECOVER FILES operation cannot continue.

Recovery  If the specified dump file has been backed up on tape or moved to another disk volume, restore the file to its original location.

Cause  The TMF subsystem could not locate the specified disk audit-dump file in conjunction with a RECOVER FILES operation. This error message is reissued every 10 minutes until the file is available.

Effect  The RECOVER FILES operation cannot continue.

Recovery  If the specified dump file has been backed up on tape or moved to another disk volume, restore the file to its original location.

Cause  This is an action completion message associated with operator message 213. It is issued 10 minutes after the preceding message 213.

Effect  The RECOVER FILES operation cannot continue.

Recovery  If the specified dump file has been backed up on tape or moved to another disk volume, restore the file to its original location.

Cause  This is an action completion message associated with operator message 214. It is issued 10 minutes after the preceding message 214.

Effect  The RECOVER FILES operation cannot continue.

Recovery  If the specified dump file has been backed up on tape or moved to another disk volume, restore the file to its original location.

Cause  The specified files are to be dumped.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  An operator or subsystem control program (SPI requester) issued a DUMP FILES command, specifying the DISKMEDIA attribute and a list of disk or tape volumes.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  An operator or subsystem control program (SPI requester) issued a DUMP FILES command, specifying the TAPEMEDIA attribute, plus new BLOCKSIZE, COPIES, SYSTEM, and VERIFYTAPE attribute values.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The dump of the specified file is being continued onto another tape.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  A dump/restore error occurred.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The dump process has begun dumping to the specified tape drive.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The dump process has begun dumping to the specified tape volume or volumes.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The dump process has begun dumping to the specified disk dump file.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The dump of the specified file is being continued on the next disk dump file.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  A dump to disk is finished.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  An online dump has completed.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  After an online dump completes, this message states how many database tables and files were successfully dumped and how many were not, as well as an indication of the total number of data bytes dumped. Label bytes are not included in this count.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  During the online restore phase of a file recovery operation, the specified audited file could not be found in the specified online dump.

Effect  The file is not restored.

Recovery  Determine the correct dump serial number and then retry the restore operation.

Cause  During the online restore phase of a file recovery operation, the specified audited file could not be restored because an archive tape error occurred.

Effect  The file is not restored.

Recovery  Determine which archive tape error occurred, correct the error condition, and then retry the restore operation.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new COPIES attribute value.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new SERIES/PARALLEL attribute value.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new VERIFYTAPE attribute value.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new BLOCKSIZE attribute value.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  A Subsystem Programmatic Interface (SPI) Alter-AuditDump command was executed, specifying a new UNLOAD value.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new MEDIUM attribute value.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new first node value for the SYSTEM attribute.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ALTER AUDITDUMP command, specifying a new second node value for the SYSTEM attribute.

Effect  The new attribute value takes effect immediately.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued a DISABLE AUDITDUMP command.

Effect  Audit dumping is disabled for the specified audit trail.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator issued an ENABLE AUDITDUMP command.

Effect  Audit dumping is enabled for the specified audit trail.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified disk volume was deleted from the dump configuration for the designated audit trail.

Effect  The disk volume is no longer used for receiving audit dumps for the designated audit trail.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified disk volume was added to the dump configuration for the designated audit trail.

Effect  The disk volume is used for receiving audit dumps for the designated audit trail.

Recovery  Informational message only; no corrective action is needed.

Cause  Something prevented all requested copies of an audit dump from being made.

Effect  The dump is retried.

Recovery  Informational message only; no corrective action is needed.

Cause  The TMF subsystem attempted to dump the specified audit-trail file, but could not.

Effect  The dump is retried.

Recovery  Examine preceding error messages in the Event Management Service (EMS) log and try to determine why the dump failed. If the problem persists, contact your service provider and provide all relevant information as follows:

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 audit dump of the specified audit-trail file finished successfully.

Effect  None

Recovery  Informational message only; no corrective action is needed.

Cause  The TMF subsystem attempted to copy the specified audit-trail file to an overflow audit volume, but could not because of an error on the file.

Effect  The overflow operation is retried.

Recovery  Examine preceding error messages in the Event Management Service (EMS) log and try to determine why the overflow operation failed. If the problem persists, contact your service provider and provide all relevant information as follows:

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 TMF subsystem attempted to copy an audit-trail file to the specified file, but could not because of an error on the destination file.

Effect  The overflow operation is retried.

Recovery  Examine preceding error messages in the Event Management Service (EMS) log and try to determine why the overflow operation failed. If the problem persists, contact your service provider and provide all relevant information as follows:

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.