Troubleshooting
Problem
This document provides a quick way to verify if GO SAVE Option 21 was successful. This document is not intended to verify other types of backups.
Diagnosing The Problem
This document provides a quick way to verify if GO SAVE Option 21 was successful. This document is not intended to verify other types of backups.
GO SAVE Option 21 contains the following save commands:
The following are the completion messages, which can be found in the History Log or joblog:
When you perform a Go Save Option 21, 22, 33, and so on, whether it is successful or whether it fails, you will see one of the following messages:
CPC2356 - Save or restore option completed successfully.
CPF2361 - Error occurred with the option.
You can display the history log and the above messages with the following command (CPC3701 and CPC3722 were not included in the command below because if CPC3707 is logged, this is enough to verify all libraries saved successfully):
where hh:mm:ss is the time and mm/dd/yy is the date (the format will differ, depending on the QDATE system value). If any of the above CPCxxxx messages are missing, that portion of the save did not complete successfully.
Note: If an error occurred with the option, you will need to review the complete joblog of the save to determine what was not saved and why. The following are some additional messages which may be logged in the joblog that may help determine why the save failed for some objects. This is not a complete list.
CPD33A4 - Spooled file &1 number &2 in job &5/&4/&3 previously damaged.
CPD33A8 - Spooled file &1 number &2 in job &5/&4/&3 not available for save.
CPF3741 - &2 &1 in &3 not saved.
CPF32B3 - Cannot allocate object for file &1 in &2.
CPF3761 - Cannot use &2 &1 in &3.
CPF3763 - &2 &1 in library &3 previously damaged.
CPF0625 - Data portion of save file &1 damaged.
CPF3285 - Damage found on file &1 in library &3.
CPF8111 - &8 damage on member &9 file &4.
MCH3202 - Permanent machine error &2. Internal dump identifier (ID) &2.
CPF701A - Journal receiver not eligible for operation.
CPF8A89 - Document &2 in folder &1 is logically damaged.
CPF909A - Document &2 in folder &1 is damaged.
CPF90AC - Document &1 not saved from folder &2.
CPF8A06 - Document &2 or folder &3 partially created in folder &1.
CPFA09E - Object in use. Object is &1.
CPD3823 - File "&1" not saved.
GO SAVE Option 21 contains the following save commands:
| Command | Description |
| ENDSBS SBS(*ALL) | Ends system to a restricted state |
| SAVSYS | Saves Licensed Internal Code, Operating System, User Profiles and their private authorities, and Configuration objects |
| SAVLIB LIB(*NONSYS) | Saves *IBM and *ALLUSR libraries |
| SAVDLO | Saves documents and folders |
| SAV | Saves directories and objects in the Integrated File System |
The following are the completion messages, which can be found in the History Log or joblog:
| Command | Completion Message |
| ENDSBS | CPF0994 - ENDSBS SBS(*ALL) command being processed. CPF0968 - System ended to restricted condition. |
| SAVSYS | CPC3702 - Save System (SAVSYS) command has completed processing. CPF3772 - SAVSYS completed. One or more objects not saved. |
| SAVLIB | CPC3701 - &1 objects saved from library &3. CPC3707 - &1 libraries saved at &3. CPC3722 - &1 objects saved from library &3. CPC3704 - &1 objects saved from library &3. &8 objects not included. CPF3751 - Some libraries not saved. CPF3763 - &2 &1 in library &3 previously damaged. CPF3770 - No objects saved or restored for library &1. CPF3771 - &1 objects saved from &3. &2 not saved. CPF3777 - &1 libraries saved, &6 partially saved, &2 not saved. |
| SAVDLO | CPC9410 - &1 document library objects saved. CPF9410 - &1 document library objects saved. &10 not saved. CPF902E - &1 document library objects saved. &10 not saved. |
| SAV | CPC370C - &1 objects saved. CPF3837 - &1 objects saved. &2 not saved. |
When you perform a Go Save Option 21, 22, 33, and so on, whether it is successful or whether it fails, you will see one of the following messages:
CPC2356 - Save or restore option completed successfully.
CPF2361 - Error occurred with the option.
You can display the history log and the above messages with the following command (CPC3701 and CPC3722 were not included in the command below because if CPC3707 is logged, this is enough to verify all libraries saved successfully):
- CALL QCMD
- DSPLOG PERIOD(('hh:mm:ss' 'mm/dd/yy') ('hh:mm:ss' 'mm/dd/yy')) MSGID(CPF0994 CPF0968 CPC3702 CPF3772 CPC3707 CPC9410 CPC370C CPC2356 CPF3763 CPF3770 CPF3771 CPF3777 CPF9410 CPF902E CPF3837 CPF2361)
where hh:mm:ss is the time and mm/dd/yy is the date (the format will differ, depending on the QDATE system value). If any of the above CPCxxxx messages are missing, that portion of the save did not complete successfully.
Note: If an error occurred with the option, you will need to review the complete joblog of the save to determine what was not saved and why. The following are some additional messages which may be logged in the joblog that may help determine why the save failed for some objects. This is not a complete list.
CPD33A4 - Spooled file &1 number &2 in job &5/&4/&3 previously damaged.
CPD33A8 - Spooled file &1 number &2 in job &5/&4/&3 not available for save.
CPF3741 - &2 &1 in &3 not saved.
CPF32B3 - Cannot allocate object for file &1 in &2.
CPF3761 - Cannot use &2 &1 in &3.
CPF3763 - &2 &1 in library &3 previously damaged.
CPF0625 - Data portion of save file &1 damaged.
CPF3285 - Damage found on file &1 in library &3.
CPF8111 - &8 damage on member &9 file &4.
MCH3202 - Permanent machine error &2. Internal dump identifier (ID) &2.
CPF701A - Journal receiver not eligible for operation.
CPF8A89 - Document &2 in folder &1 is logically damaged.
CPF909A - Document &2 in folder &1 is damaged.
CPF90AC - Document &1 not saved from folder &2.
CPF8A06 - Document &2 or folder &3 partially created in folder &1.
CPFA09E - Object in use. Object is &1.
CPD3823 - File "&1" not saved.
Resolving The Problem
Let's take a look at a real world example.
A customer has recently run a GO SAVE 21 to restore their entire system, and wants to verify that everything completed normally. The help text for GO SAVE shows the command option 21 runs:
..............................................................................
: Option 21 - Help :
: :
: This option runs the following commands: :
: :
: ENDTCPSVR SERVER(*ALL) :
: ENDHOSTSVR SERVER(*ALL) ENDACTCNN(*DATABASE *FILE) :
: DLYJOB JOB(number-of-seconds) :
: ENDTCP CONFIRM(*NO) :
: DLYJOB JOB(number-of-seconds) :
: ENDSBS SBS(*ALL) OPTION(*IMMED) :
: SAVSYS :
: SAVLIB LIB(*NONSYS) ACCPTH(*YES) :
: SAVDLO DLO(*ALL) FLR(*ANY) :
: SAV OBJ(('/*') ('/QSYS.LIB' *OMIT) :
: ('/QDLS' *OMIT)) UPDHST(*YES) :
: STRSBS SBSD(controlling-subsystem) :
: :
:............................................................................:
And while the section above demonstrates the use of the DSPLOG command to check all of the error messages to look for in a SO SAVE 21, it is possible to narrow it down to one section. So if we want to check that the SAVDLO completed normally, we can reference that the SAVDLO messages are CPC9410, CPF9410, and CPF902E. So the command we run to check if DLO saved properly is:
DSPLOG PERIOD(('hh:mm:ss' 'mm/dd/yy') ('hh:mm:ss' 'mm/dd/yy')) MSGID(CPC9410 CPF9410 CPF902E)
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z000000cwp6AAA","label":"Save Restore"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
387819982
Was this topic helpful?
Document Information
Modified date:
22 July 2023
UID
nas8N1015410