IBM Support

Saving a Server Storage Space to a Previous Release Fails with Message CPD376D

Technote (FAQ)


Question

This document describes the difference between current releases when saving a storage space with previous release parameter ( TGTRLS )specified.

Cause

IBM i 6.1 and 7.2 NWSSTG (Network Storage Space) are not compatible with the previous previous release, so save to previous release is not allowed for the nwsstg at these releases.

Answer

When you save a Network Storage Space and specify a previous release on the TGTRLS parameter on the SAV command, it will fail on IBM i 6.1 & IBM i 7.2 with message CPD376D, while it will work on IBM i 7.1. When the previous release is IBM i 6.1, it will also fail when the TGTRLS V5R4M0 is specified. It will also work on IBM i 7.3 when the TGTRLS parameter set to V7R2M0, but fails with TGTRLS set to V7R1M0.

Save to previous release is a release-by-release behavior. The ability to save a network storage space to a previous release is dependent upon whether the network storage space format is compatible with the previous release. Because IBM i 6.1 and 7.1 are compatible, the operating system will allow the IBM i 7.1 storage to be saved to a target release of IBM i 6.1. On the other hand, 6.1 and 7.2 network storage spaces are not compatible with their previous release, so it is not allowed to save them to the previous release. There are no plans as of right now to fix this. This is a limitation.

See the examples and their out come below..

Example (SAVF being used in this example) on IBM i 7.3 with TGTRLS V7R2M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V7R1M0)
Will result in the messages:
1 objects saved. -->> CPC370D - 1 objects saved
Note: It reads 1 object saved, but in fact it saved all the files (like QFPCLTSTG1, QFPCONTROL,
QFPSIDEFIL) belonging to this network storage space. Each NWSSTG is associated with multiple
objects, and some objects may not even exist under the storage space directory (eg. Storage spaces
in iASP), so it is only allowed to save the storage space as a whole, and not each separate file, to
avoid a storage space being saved partially by mistake.

Example (SAVF being used in this example) on IBM i 7.3 with TGTRLS V7R1M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V6R1M0)
Will result in the messages:
Not able to save /qfpnwsstg/NWSSTG. -->> CPD376D RC0 - Objects of type *DIR cannot be saved for
the release specified on the TGTRLS
parameter.
No objects saved or restored. -->> CPF3823 - No objects saved or restored.

Example (SAVF being used in this example) on IBM i 7.2 with TGTRLS V7R1M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V7R1M0)
Will result in the messages:
Not able to save /qfpnwsstg/NWSSTG. -->> CPD376D RC0 - Objects of type *DIR cannot be saved for
the release specified on the TGTRLS
parameter.
No objects saved or restored. -->> CPF3823 - No objects saved or restored.

Example (SAVF being used in this example) on IBM i 7.2 with TGTRLS V6R1M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V6R1M0)
Will result in the messages:
Not able to save /qfpnwsstg/NWSSTG. -->> CPD376D RC0 - Objects of type *DIR cannot be saved for
the release specified on the TGTRLS
parameter.
No objects saved or restored. -->> CPF3823 - No objects saved or restored.

Example (SAVF being used in this example) on IBM i 7.1 with TGTRLS V5R4M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V5R4M0)
Will result in the messages:
Not able to save /qfpnwsstg/NWSSTG. -->> CPD376D RC0 - Objects of type *DIR cannot be saved for
the release specified on the TGTRLS
parameter.
No objects saved or restored. -->> CPF3823 - No objects saved or restored.

Example (SAVF being used in this example) on IBM i 7.1 with TGTRLS V6R1M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V5R4M0)
Will result in the messages:
1 objects saved. -->> CPC370D - 1 objects saved
Note: It reads 1 object saved, but in fact it saved all the files (like QFPCLTSTG1, QFPCONTROL,
QFPSIDEFIL) belonging to this network storage space. Each NWSSTG is associated with multiple
objects, and some objects may not even exist under the storage space directory (eg. Storage spaces
in iASP), so it is only allowed to save the storage space as a whole, and not each separate file, to
avoid a storage space being saved partially by mistake.

Example (SAVF being used in this example) on IBM i 6.1 with TGTRLS V5R4M0:
SAV DEV('/qsys.lib/qtemp.lib/savf.file')
OBJ(('/qfpnwsstg/NWSSTG'))
TGTRLS(V5R4M0)
Will result in the messages:
Not able to save /qfpnwsstg/NWSSTG. -->> CPD376D RC0 - Objects of type *DIR cannot be saved for
the release specified on the TGTRLS
parameter.
No objects saved or restored. -->> CPF3823 - No objects saved or restored.

Cross reference information
Segment Product Component Platform Version Edition
Operating System IBM i 7.2
Operating System IBM i 7.1
Operating System IBM i 6.1
Operating System IBM i 7.3

Document information

More support for: IBM i
Save/Restore

Software version: 6.1, 6.1.0, 6.1.1, 7.1, 7.1.0, 7.2, 7.2.0, 7.3

Operating system(s): IBM i

Reference #: N1020563

Modified date: 20 June 2016