Error Message When Performing a Full System Save

Data Management and Security (Hardware) Hardware Error Message When Performing a Full System Save

This document provides technical guidance for users of the Flex system regarding messages encountered during a Full System Save (CMCSAVSYS) backup. It clarifies common “error” messages that are, in fact, informational and outlines steps to verify backup completion and identify unencrypted or unsaved files.

1. Introduction to Full System Save Messages

When performing a Full System Save (CMCSAVSYS) in the Flex system, it is common to receive messages that appear to be errors but are actually informational alerts. These messages indicate that certain files could not be encrypted or saved during the backup process.

1.1 Common Informational Messages

The following messages are examples of informational alerts, not critical errors, for the CMCSAVSYS backup:

  • Error with Encryption save of libraries.
  • Error with SAV (IFS) portion of save.

1.2 Reason for Informational Messages

These messages occur because the encryption utility used for backups identifies files that cannot be encrypted. This can include:

  • Damaged files
  • Internet shortcuts
  • Unknown files
  • Temporary files (.tmp)
  • Log files (.log)
  • TCP-related files (.tcp)

When the Full System Save detects these types of files, it generates these informational alerts to notify the user.

2. Verifying Full System Save Completion

To ensure that your Full System Save backup completed normally, you should review the CMCSAVLOG.

2.1 Accessing the CMCSAVLOG

  1. On a command line in the Flex system, type:
    DSPPFM CMCSAVLOG

  2. Press Enter.
  3. To navigate to the most recent backup alerts, type B in the Control Line and press Enter.
  4. Use Page Up or Page Down as needed to review all alerts.

2.2 Expected Completion Messages

A normally completed backup should display a sequence of messages similar to the following in the CMCSAVLOG:

  • Submitted Job has started.
  • System save to run immediately
  • Monitor is starting up.
  • Save tape has been initialized.
  • Shutdown of online services has started.
  • Shutdown of online services has completed.
  • Monitor is shutting down upon request.
  • System save has started.
  • TCPIP has ended.
  • Encryption backup used for member data.
  • TCPIP is active.
  • Dedicated portion of system save has completed.
  • Online services are starting up.
  • Monitor is starting up.
  • DOCMAN save has started.
  • Encryption backup used for member data.
  • DOCMAN save has completed.
  • System Save has completed.
  • Data encrypted completed successfully.

Note: The messages Error with Encryption save of libraries. and Error with SAV (IFS) portion of save. may appear within this sequence and still indicate a successful overall backup.

3. Viewing Details of Unencrypted or Unsaved Files

To see additional details about which specific files were not encrypted or saved, you can view the backup log file. This procedure must be performed within 7 days of the save.

3.1 Accessing the Job Log

  1. On a command line in the Flex system, type:
    WRKOUTQ QEZJOBLOG

  2. Press Enter.
  3. Locate the file named QPJOBLOG with User Data as CMCSAVSYS.

3.2 Searching for Unsaved Objects

  1. With the QPJOBLOG file displayed, type Error with SAV or not saved in the Find field.
  2. Press Shift + F4 to search for the first occurrence.
  3. Continue to press Shift + F4 to navigate through all instances of objects or libraries that were not saved.

3.3 Examples of Unsaved Objects

The displayed results will show messages indicating files that could not be saved, often including their paths and reasons. Examples of such messages include:

  • Cannot save /OTCPTMM/TMP.
  • Cannot save /QTCPTMM/DATA00432E.
  • Cannot save /tmp/s.
  • Object in use. Object is /tomcat/logs/tomcat.log.
  • Cannot open object /tomcat/logs/tomcat.log.

These entries provide specific information about files that were skipped during the save process, typically due to being in use, temporary, or otherwise inaccessible at the time of backup.