CMCSAVSYS Failure

Data Management and Security (Hardware) Hardware CMCSAVSYS Failure

This document provides a comprehensive guide to troubleshooting common failures of the CMCSAVSYS backup process within the Flex system.

1. Overview of CMCSAVSYS Failures

The CMCSAVSYS job is critical for system backups. Failures can occur due to various reasons, primarily related to tape drive issues, exceeding backup time limits, or incorrect job submission.

2. Common Failure Scenarios and Troubleshooting Steps

2.1 Tape Drive Issues

Tape drive problems are a frequent cause of CMCSAVSYS failures. These can include:

  • Disconnected, Off, or Damaged Tape Drive (TAP01)
  • Incorrect Cartridge Type Used

Troubleshooting Steps:

  1. Check CMCSAVSYS Log for Errors:
    • Run the command: dsppfm cmcsavlog
    • Enter B in the control line to navigate to the last page of the log.
    • Look for messages indicating the system save did not complete, such as “Monitor is shutting down CMCSAVSYS not found.”
  2. Examine System Log (DSPLOG) for Specific Error Codes:
    • Run the command: dsplog + F4
    • Enter the Beginning time (e.g., 230000) and Beginning date (e.g., 020621) corresponding to the backup attempt.
    • For Incorrect Cartridge Type:
      • Look for messages like: CPF6763 received by procedure CMCSAVSYS. (C D I R)
      • Place the cursor on any CPF6763 message and press F1 for more details. This will often confirm if the wrong type of cartridge was used.
    • For Disconnected/Off Tape Drive:
      • Look for messages like:
        Device resource name TAP01 not found.
        CPF6718 received by procedure CMCSAVSYS. (C D I R)

      • Place the cursor on any CPF6718 message and press F1 for more details. This will indicate that the device TAP01 cannot be allocated.
  3. Verify Tape Drive Hardware Status:
    • Physical Check: Ensure the tape drive is physically plugged in and turned on.
    • Hardware Resource Check:
      • Run the command: wrkhdwrsc *stg
      • Locate the tape drive card (e.g., 57B3 or 57B4).
      • Enter 9 in front of the Storage Controller (e.g., DC04 57B3-001) to check its status.
      • Verify that both the card and the TAP01 unit are in Operational status.
        Opt  Resource        Type-model  Status                Text
                DC04               57B3-001   Operational             Storage Controller
                TAP01              3580-007   Operational             Tape Unit

    • Tape Compatibility: Confirm that the correct type of Ultrium tape is being used based on the tape drive model:
      • 3580-007 tape drive: Use ULT 6 or ULT 7 tapes.
      • 3580-006 tape drive: Use ULT 5 or ULT 6 tapes.
      • 3580-008 tape drive: Use ULT 7 or ULT 8 tapes.
  4. Additional Tape Drive Indicators:
    • Cleaning Required: If the tape drive displays a C in front of its status, it indicates that the drive needs to be cleaned with a cleaning tape.
    • Error Lights/Codes: Check for any amber lights or specific number codes displayed on the front of the tape drive, as these can indicate hardware issues.

2.2 Maximum End Time Reached

The CMCSAVSYS job may end prematurely if it exceeds the MAX END TIME configured for the batch restricted state.

Troubleshooting Steps:

  1. Check CMCSAVSYS Log for Completion:
    • Run the command: dsppfm cmcsavlog
    • Enter B in the control line to navigate to the last page.
    • A successful backup will typically show completion messages.
  2. Examine System Log (DSPLOG) for Time Limit Expiration:
    • Run the command: dsplog + F4
    • Enter the Beginning time and Beginning date corresponding to the backup attempt.
    • Page down until you find messages similar to:
      Job 494937/QSECOFR/CMCSAVSYS was ended by user QSYS.
      Batch restricted state ended, reason code 1.
      Job 494937/QSECOFR/CMCSAVSYS ended on 02/07/21 at 11:08:48; 75.738 seconds us
      Subsystem QCTL in library QSYS starting.

    • Place the cursor on the Batch restricted state ended, reason code 1 message and press F1 for Additional Message Information.
    • Verify the Technical description states: “The batch time limit specified on the End Subsystem (ENDSBS) command expired.”
  3. Resolution:
    • Advise the Customer Unit (CU) to extend the MAX END TIME for future backups to prevent premature termination.

2.3 Other Reasons for Backup Failure

Beyond tape drive and time limit issues, other factors can cause CMCSAVSYS to fail:

  • Job Submission Issues:
    • CMCSAVSYS job not submitted.
    • CMCSAVSYS job submitted with wrong date and/or times.
    • CMCSAVSYS job submitted twice with different times but the same date.
  • System Operations:
    • CMCSAVSYS job ended due to a scheduled IPL (Initial Program Load) in wrkjobscde.
    • CMCSAVSYS job intentionally ended from wrkactjob.
    • System IPLed while the backup was running.
  • Environmental/Hardware Issues:
    • Power outage during the backup.
    • Tape accidentally ejected during the backup.
    • Tape damaged during the backup.

3. Contact and Support

If you encounter persistent issues with CMCSAVSYS failures after following these troubleshooting steps, please contact Flex support with detailed logs and error messages for further assistance.