Question & Answer
Question
Why does a GO SAVE 21 or a full save of the IFS receive MSGCPD37C3?
Cause
There are cases where IBM directories are not being saved during the SAV portion of a full system save. These directories are in the /QIBM/PRODDATA/ directory and are set to ALWSAV = NO. This is because these directories are saved with the SAVSYS and restored or created when the IBM i5OS is installed. You do not want to change them to ALWSAV = YES because it would cause redundant saves or restores. One of the reasons for this has been saving of PTF objects from previous releases and restoring them to a newer release system, causing issues with the product after installation. Some of the directories in question are as follows:
In V7R2M0, IBM i OS Save Restore was enhanced by placing an information message into the joblog for each object that has been marked not saveable (by a user or an application):
CPD37C3 - Message.......: Cannot save /tmp/s.slapd.QUSRDIR.
Cause . . . . . : The ALWSAV attribute on /tmp/s.slapd.QUSRDIR was set to*NO preventing the object from being saved.
Recovery . . . : If the object is not needed for recovery purposes, no recovery is necessary. If the object is needed for recovery purposes, change the ALWSAV attribute to *YES and try the request again.
Additional IBM directories (other than those listed above) that may/will have the ALWSAV attribute set to *NO by default are as follows:
o /QOPT
o /QIBM/ProdData/OS400/Servers/servermap.end
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stdoutA.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stdoutB.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stderrA.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stderrB.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/monitor.log
o /QIBM/UserData/OS/Service/Logs
o /dev/null
o /dev/zero
o /tmp/s.slapd.*
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/registry
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/log/mc
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/soc/mc
Note: The number 437575835 referenced above in the /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/ directory will vary between systems. For each system, a different 9-digit number could be referenced.
o /QIBM/UserData/OS400/QOS/
The QoS directory is for the TCP/IP function of Quality of Service and is created when the QoS function is turned on and policies are made. For information on that, you should refer to the iGSC TCP/IP support team and discuss with them "QoS on System i5". From that teams' documentation, it is stated:
Messages CPD37C3 & CPD37C4 are informational messages created to let you know which IFS objects are not being saved due to the ALWSAV attribute being set to *NO. If there are other directories than those listed in this document that have ALWSAV (Can be saved) attribute set to *NO, you should ensure that those objects will not be needed for recovery. If the object is not needed for recovery purposes, no recovery is necessary. If the object is needed for recovery purposes, you should change the ALWSAV attribute to *YES and try the request again.
If you are using BRMS and would like to suppress the CPD37C3 messages from DSPLOGBRM, refer to Technote N1020237, CPD37C3 in DSPLOGBRM.
Note: Message CPD3775 - Cannot save or restore &1 may also be logged for these same directories. This message may also be ignored if it is for the objects listed in this technote.
| o /QIBM/ProdData/OS/SNMP o /QIBM/ProdData/OS/ClusterResourceServices o /QIBM/ProdData/OS/MRI2924 o /QIBM/ProdData/OS/SQLLIB/bin o /QIBM/ProdData/OS/xlxp/lib |
In V7R2M0, IBM i OS Save Restore was enhanced by placing an information message into the joblog for each object that has been marked not saveable (by a user or an application):
CPD37C3 - Message.......: Cannot save /tmp/s.slapd.QUSRDIR.
Cause . . . . . : The ALWSAV attribute on /tmp/s.slapd.QUSRDIR was set to*NO preventing the object from being saved.
Recovery . . . : If the object is not needed for recovery purposes, no recovery is necessary. If the object is needed for recovery purposes, change the ALWSAV attribute to *YES and try the request again.
Additional IBM directories (other than those listed above) that may/will have the ALWSAV attribute set to *NO by default are as follows:
o /QOPT
o /QIBM/ProdData/OS400/Servers/servermap.end
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stdoutA.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stdoutB.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stderrA.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/stderrB.txt
o /QIBM/ProdData/OS400/iSeriesNavigator/config/MONITOR/monitor.log
o /QIBM/UserData/OS/Service/Logs
o /dev/null
o /dev/zero
o /tmp/s.slapd.*
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/registry
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/log/mc
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/soc/mc
o /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/437575835/lck/mc
o /QIBM/UserData/BRMS/logs
o /QOpenSys/QIBM/ProdData/OS400/NTP
Note: There could be other paths that are not in this list.
Note: The number 437575835 referenced above in the /QIBM/UserData/OS400/ResourceMonitoringControl/var/ct/ directory will vary between systems. For each system, a different 9-digit number could be referenced.
o /QIBM/UserData/OS400/QOS/
The QoS directory is for the TCP/IP function of Quality of Service and is created when the QoS function is turned on and policies are made. For information on that, you should refer to the iGSC TCP/IP support team and discuss with them "QoS on System i5". From that teams' documentation, it is stated:
- Backing up QoS policies
You should back up your quality of service (QoS) policies to eliminate the need to re-create your policies in the event of a system outage or power loss.Your policies can be stored locally or exported to a directory server. You must specifically back up the following integrated file system directory: QIBM/UserData/OS400/QOS/ETC, QIBM/UserData/OS400/QOS/TEMP, and QIBM/UserData/OS400/QOS/USR. You must also back up your directory server publishing agent for the QoS server. The publishing agent contains the directory server name, the distinguished name (DN) for the QoS server, port used to access the directory server, and authentication information. In the event of a loss, your backups can save you the time and work it takes to re-create your policies from scratch.
Messages CPD37C3 & CPD37C4 are informational messages created to let you know which IFS objects are not being saved due to the ALWSAV attribute being set to *NO. If there are other directories than those listed in this document that have ALWSAV (Can be saved) attribute set to *NO, you should ensure that those objects will not be needed for recovery. If the object is not needed for recovery purposes, no recovery is necessary. If the object is needed for recovery purposes, you should change the ALWSAV attribute to *YES and try the request again.
If you are using BRMS and would like to suppress the CPD37C3 messages from DSPLOGBRM, refer to Technote N1020237, CPD37C3 in DSPLOGBRM.
Note: Message CPD3775 - Cannot save or restore &1 may also be logged for these same directories. This message may also be ignored if it is for the objects listed in this technote.
[{"Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000001gnSAAQ","label":"Backup Recovery Install Migration-\u003ESave\/restore"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Type":"MASTER"}]
Was this topic helpful?
Document Information
Modified date:
29 January 2025
UID
nas8N1020112