Task 1 - Start the save storage procedure

Related reference
Save configuration information

Do These Things Before You Begin:

  • Initialize at least three more tapes than you think that you will need to complete the save operation. Initialize them as standard-labeled tapes and specify the maximum density for the tape unit you are using. The number of tapes that you need depends on the size of the server, the number of objects, and the capacity of the tape.

    Each tape should have a volume ID of SAVEDS and an external label that allows you to easily identify the tape. Ensure that each of the tapes support the same density.

  • Clean the read/write heads of the tape unit.
  • Apply any program temporary fixes (PTFs).
  • Print a list of all the PTFs currently on the server. Type the following and press the Enter key:
    DSPPTF LICPGM(*ALL) OUTPUT(*PRINT)
  • Ensure that you saved the hardware configuration information from the server. Use the Save Configuration (SAVCFG) command or the Save System (SAVSYS) command to save the configuration objects. The restore storage procedure uses the SAVSYS media volume or the SAVCFG media volume to restore the hardware configuration information.
  • Print a list of the current network attributes. Type the following and press the Enter key:
    DSPNETA OUTPUT(*PRINT)
    Keep this Network Attributes list with the tapes that are written during the save storage operation.
Attention logical partitioning users:
  • Using the Save Storage (SAVSTG) command will cause your server to perform an IPL. If you are running this command on the primary partition, you must quiesce the secondary partitions before continuing.
  • In order to save your entire system configuration, you must save each logical partition individually.
  1. Sign on at the console with a user profile that has *SAVSYS special authority.
  2. Notify users that the server will be unavailable.
  3. Change the QSYSOPR message queue to break mode:
    CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK) SEV(60)
  4. Type the following to bring the server to a restricted state:
    ENDSBS SBS(*ALL) OPTION(*CNTRLD) DELAY(600)
    Note: For the delay parameter, specify a number of seconds that allows your server time to bring most jobs to a normal end. On a large, busy server, you may need a longer delay.

    The server sends messages to the QSYSOPR message queue. These messages indicate that the subsystems ended, and the server is in a restricted state. When the subsystems have ended, continue with the next step.

  5. Load the first media volume of the SAVSTG media, and make the media device ready.
  6. Check the control panel on your processor to ensure that the server is in normal mode.
  7. If you are not using logical partitioning, continue with the next step. Otherwise, if you are performing this operation from the primary partition, be sure to power down all secondary partitions.
  8. Enter the save storage command, such as:
    SAVSTG DEV(TAP01) CLEAR(*ALL)

    You can also enter an expiration date (EXPDATE(mmddyy)).

  9. Press the Enter key. The server will power down with a restart IPL. This is similar to PWRDWNSYS OPTION(*IMMED) RESTART(*YES). This means that when you enter the command, the server will power down and perform an automatic IPL.

    When the IPL occurs, a dedicated service tools (DST) function starts saving storage. If the operator correctly loads the media volume and the expiration date check passes, the operator does not need to be present for the first media volume.

    If you load the media volume correctly, the following save status display continually displays the progress of the save operation.
                                   Function Status
     
                           You selected to save storage.
     
     
     
                                     1 % Complete

    The Percent saved field on the display estimates the progress of the total amount of saved sectors. However, this estimate does not accurately predict the time it takes to save or the number of tapes that you need to complete the save operation. The reason is that the server does not save unused sectors.