The Save Library (SAVLIB) command allows you to save a copy of one or more libraries.

When saving to a save file, only one library can be specified.

This command saves the entire library, including the library description, the object descriptions, and the contents of the objects in the library. For job queues, message queues, and logical files, only the object definitions are saved, not the contents. However, logical file access paths can be saved by specifying *YES for the Save access paths (ACCPTH) parameter. The contents of spooled files on output queues can be saved by specifying *ALL for the Spooled file data (SPLFDTA) parameter. The contents of a save file can be saved by specifying *YES for the Save file data (SAVFDTA) parameter or using the Save Save File Data (SAVSAVFDTA) command. The contents of a data queue can be saved by specifying *DTAQ for the Queue data (QDTA) parameter. The libraries and their objects are not affected in the system unless the command specifies that the storage is to be freed. However, unless *NO is specified for the Update history (UPDHST) parameter, the description of each library and each object is updated with the date, place, and time it was last saved. If a group of libraries is saved by specifying *NONSYS, *ALLUSR, or *IBM for the LIB parameter, the date, time, and place are updated in the history information for a data area in QSYS (data area QSAVLIBALL, QSAVALLUSR, or QSAVIBM).

The types of objects saved by this command are the same as those listed in the OBJTYPE parameter description in "Commonly used parameters: Expanded descriptions" in the CL concepts and reference topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter, with the addition of *DTADCT. Certain operating system objects that are not contained in user libraries (such as user profiles) are not saved by this command. They can be saved by the Save System (SAVSYS) or Save Security Data (SAVSECDTA) commands.

Note: This command ignores all file overrides currently in effect for the job, except for the listing file.

Restrictions:

• You must either have save system (*SAVSYS) special authority or the following object authorities:
  • read (*READ) authority for, or be the owner of, each library specified
  • object existence (*OBJEXIST) authority for each object in the library (for spooled file data, *OBJEXIST authority for the output queue)
• If you do not have *SAVSYS special authority, only those libraries and objects that you have authority for are saved.
• When saving to a tape or optical volume, you must have use (*USE) authority to the associated device description.
• When saving to a save file, you must have add (*ADD) and use (*USE) authorities to the save file.
• When using a media definition, you must have *USE authority to the media definition and execute (*EXECUTE) authority to the library where the media definition is located.
• When using the OUTFILE parameter to save to an existing database file, you must have *EXECUTE authority to the output file library.
• No library being saved, or the objects in it, can be updated by a job that is running at the time the save operation occurs unless save-while-active is used.
• When the contents of a save file are being saved to the same save file by specifying SAVFDTA(*YES), only the description of the save file is saved.
• When the contents of a save file are saved, by specifying *YES for the Save file data (SAVFDTA) parameter, the save file must be restored before objects contained in it can be restored.
• When using the Command user space (CMDUSRSPC) parameter, you must have *USE authority to the user space and *EXECUTE authority to the user space library.

Parameters

Keyword	Description	Choices	Notes
LIB	Library	Single values: *NONSYS, *ALLUSR, *IBM, *USRSPC Other values (up to 300 repetitions): Generic name, name	Required, Positional 1
DEV	Device	Single values: *SAVF, *MEDDFN Other values (up to 4 repetitions): Name	Required, Positional 2
VOL	Volume identifier	Single values: *MOUNTED Other values (up to 75 repetitions): Character value	Optional, Positional 3
SEQNBR	Sequence number	1-16777215, *END	Optional
LABEL	Label	Character value, *LIB	Optional
EXPDATE	File expiration date	Date, *PERM	Optional
ENDOPT	End of media option	*REWIND, *LEAVE, *UNLOAD	Optional
STRLIB	Starting library	Name, *FIRST	Optional
SAVF	Save file	Qualified object name	Optional
	Qualifier 1: Save file	Name
	Qualifier 2: Library	Name, *LIBL, *CURLIB
MEDDFN	Media definition	Qualified object name	Optional
	Qualifier 1: Media definition	Name
	Qualifier 2: Library	Name, *LIBL, *CURLIB
OPTFILE	Optical file	Path name, *	Optional
USEOPTBLK	Use optimum block	*YES, *NO	Optional
TGTRLS	Target release	*CURRENT, *PRV, V5R2M0, V5R3M0, V5R4M0	Optional
UPDHST	Update history	*YES, *NO	Optional
CLEAR	Clear	*NONE, *ALL, *AFTER, *REPLACE	Optional
PRECHK	Object pre-check	*NO, *YES	Optional
SAVACT	Save active	*NO, *LIB, *SYNCLIB, *SYSDFN	Optional
SAVACTWAIT	Save active wait time	Element list	Optional
	Element 1: Object locks	0-99999, 120, *NOMAX
	Element 2: Pending record changes	0-99999, *LOCKWAIT, *NOCMTBDY, *NOMAX
	Element 3: Other pending changes	0-99999, *LOCKWAIT, *NOMAX
SAVACTMSGQ	Save active message queue	Qualified object name	Optional
	Qualifier 1: Save active message queue	Name, *NONE, *WRKSTN
	Qualifier 2: Library	Name, *LIBL, *CURLIB
ACCPTH	Save access paths	*SYSVAL, *NO, *YES	Optional
SAVFDTA	Save file data	*YES, *NO	Optional
SPLFDTA	Spooled file data	*NONE, *ALL	Optional
QDTA	Queue data	*NONE, *DTAQ	Optional
STG	Storage	*KEEP, *FREE	Optional
DTACPR	Data compression	*DEV, *NO, *YES, *LOW, *MEDIUM, *HIGH	Optional
COMPACT	Data compaction	*DEV, *NO	Optional
OMITLIB	Libraries to omit	Single values: *NONE, *USRSPC Other values (up to 300 repetitions): Generic name, name	Optional
OMITOBJ	Objects to omit	Single values: *USRSPC Other values (up to 300 repetitions): Element list	Optional
	Element 1: Object	Qualified object name
	Qualifier 1: Object	Generic name, name, *NONE, *ALL
	Qualifier 2: Library	Generic name, name, *ALL
	Element 2: Object type	Character value, *ALL
ASPDEV	ASP device	Name, *, *SYSBAS, *CURASPGRP	Optional
OUTPUT	Output	*NONE, *PRINT, *OUTFILE	Optional
OUTFILE	File to receive output	Qualified object name	Optional
	Qualifier 1: File to receive output	Name
	Qualifier 2: Library	Name, *LIBL, *CURLIB
OUTMBR	Output member options	Element list	Optional
	Element 1: Member to receive output	Name, *FIRST
	Element 2: Replace or add records	*REPLACE, *ADD
INFTYPE	Type of output information	*OBJ, *LIB, *MBR, *ERR	Optional
CMDUSRSPC	Command user space	Qualified object name	Optional
	Qualifier 1: Command user space	Name
	Qualifier 2: Library	Name, *LIBL, *CURLIB

Top

Library (LIB)

Specifies which libraries are saved.

Notes:

1. The system libraries QDOC, QDOCxxxx, QRCYxxxxx, QRECOVERY, QRPLOBJ, QRPLxxxxx, QSPL, QSPLxxxx, QSRV, QSYS, QSYSxxxxx, and QTEMP cannot be saved with this command. xxxx is a basic user ASP number, and xxxxx is an independent ASP number.
2. If you specify *ALLUSR or *IBM on this parameter, this command should be run when the specified libraries are not being used. If objects in a library are in use while the library is being saved, the objects are not saved unless you use SAVACT. To ensure a complete save of all libraries, run this command with the system in a restricted state. For example, if SAVLIB LIB(*ALLUSR) is run when the subsystem QSNADS is active, the QAO* files are not saved in library QUSRSYS. To save the QAO* files, end the QSNADS subsystem before running SAVLIB LIB(*ALLUSR).
3. Doing a SAVLIB LIB(*IBM) and then doing a SAVLIB LIB(*ALLUSR) saves the same libraries as a SAVLIB LIB(*NONSYS), but requires two restore commands.
4. Libraries are saved alphabetically by ASP device name for each value specified. Libraries on independent ASPs are saved before libraries on the system and basic user ASPs. For values *NONSYS and *ALLUSR, libraries QSYS2, QGPL, QUSRSYS, and QSYS2xxxxx (where xxxxx is an independent ASP number) are saved first, if they are located on the ASPs specified by the ASPDEV parameter.

This is a required parameter.

Single values

*NONSYS

All libraries except the system libraries are saved. All subsystems must be ended by the End Subsystem (ENDSBS) or End System (ENDSYS) command before this option is specified.

*ALLUSR

All user libraries are saved. All libraries with names that do not begin with the letter Q are saved except for the following:

#CGULIB     #DSULIB     #SEULIB
#COBLIB     #RPGLIB
#DFULIB     #SDALIB

Although the following Qxxx libraries are provided by IBM, they typically contain user data that changes frequently. Therefore, these libraries are considered "user libraries," and are also saved:

QDSNX       QRCLxxxxx   QUSRIJS     QUSRVxRxMx
QGPL        QSRVAGT     QUSRINFSKR
QGPL38      QSYS2       QUSRNOTES
QMGTC       QSYS2xxxxx  QUSROND
QMGTC2      QS36F       QUSRPOSGS
QMPGDATA    QUSER38     QUSRPOSSA
QMQMDATA    QUSRADSM    QUSRPYMSVR
QMQMPROC    QUSRBRM     QUSRRDARS
QPFRDATA    QUSRDIRCL   QUSRSYS
QRCL        QUSRDIRDB   QUSRVI

*IBM

Saves all IBM-supplied libraries except for the following:

QDOC        QRCYxxxxx   QTEMP       QUSRRDARS
QDOCxxxx    QRECOVERY   QUSER38     QUSRSYS
QDSNX       QRPLOBJ     QUSRADSM    QUSRVI
QGPL        QRPLxxxxx   QUSRBRM     QUSRVxRxMx
QGPL38      QSPL        QUSRDIRCL
QMGTC       QSPLxxxx    QUSRDIRDB
QMGTC2      QSRV        QUSRIJS
QMPGDATA    QSRVAGT     QUSRINFSKR
QMQMDATA    QSYS        QUSRNOTES
QMQMPROC    QSYSxxxxx   QUSROND
QPFRDATA    QSYS2       QUSRPOSGS
QRCL        QSYS2xxxxx  QUSRPOSSA
QRCLxxxxx   QS36F       QUSRPYMSVR

Note: A different library name, in the format QUSRVxRxMx, can be created by the user for each previous release supported by IBM to contain any user commands to be compiled in a CL program for the previous release. For the QUSRVxRxMx user library, VxRxMx is the version, release, and modification level of a previous release that IBM continues to support.

The following libraries with names that do not begin with the letter Q are also saved:

#CGULIB     #DSULIB     #SEULIB
#COBLIB     #RPGLIB
#DFULIB     #SDALIB

*USRSPC

The libraries identified in the user space specified for the Command user space (CMDUSRSPC) parameter are saved. Only one library can be specified in the user space when saving to a save file. Special value *SPLF cannot be specified in the user space.

Other values (up to 300 repetitions)

generic-name

Specify the generic name of the libraries to be saved. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk (*) substitutes for any valid characters. A generic name specifies all libraries with names that begin with the generic prefix, for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete library name.

name

Specify the name of the library to be saved. Only one library name can be saved when saving to a save file. A system library name cannot be specified.

Device (DEV)

Specifies the name of the device used for the save operation. The device name must already be known on the system by a device description.

This is a required parameter.

Single values

*SAVF

The save operation is done using the save file specified for the Save file (SAVF) parameter.

*MEDDFN

The save operation is done using the devices and media identified in the media definition specified for the Media definition (MEDDFN) parameter.

Other values

optical-device-name

Specify the name of the optical device used for the save operation.

tape-media-library-device-name

Specify the name of the tape media library device used for the save operation.

tape-device-name

Specify the names of one or more tape devices used for the save operation. If a virtual tape device is used, it must be the only device specified. If multiple tape devices are used, they must have compatible media formats and their names must be specified in the order in which they are used. Using more than one tape device permits one tape volume to be rewound and unloaded while another tape device processes the next tape volume. To use more than one device in parallel, a media definition must be specified.

Volume identifier (VOL)

Specifies the volume identifiers of the volumes, or the cartridge identifiers of tapes in a tape media library device, on which the data is saved. The volumes must be placed in the device in the same order as specified for this parameter.

Single values

*MOUNTED

The data is saved on the volumes placed in the device. For a media library device, the volume to be used is the next cartridge in the category mounted by the Set Tape Category (SETTAPCGY) command.

Note: This value cannot be specified when using an optical media library device.

Other values (up to 75 repetitions)

character-value

Specify the identifiers of one or more volumes in the order in which they are placed in a device and used to save the data.

Sequence number (SEQNBR)

Specifies, when tape is used, the sequence number to use as the starting point for the save operation.

*END

The save operation begins after the last sequence number on the first tape. If the first tape is full, an error message is issued and the operation ends.

1-16777215

Specify the sequence number of the file to be used for the save operation.

If *NONSYS, *ALLUSR, or *IBM is specified for the LIB parameter, the save operation for the set of libraries begins at the sequence number specified. The first file saved in this set is the QFILE file. The QFILE file contains the list of libraries saved.

Label (LABEL)

Specifies the name that identifies the data file on the tape volume that is to be used for the save operation. If this parameter is used on the save command, the same label must be specified on the restore command.

Note: You cannot specify *SAVLIB on this parameter, since it is a special value for the Label (LABEL) parameter of the restore command and would prevent you from restoring what you saved.

*LIB

The file label is created by the system using the name of the library specified for the Library (LIB) parameter.

character-value

Specify the data file identifier of the data file used for the save operation. A maximum of 17 characters can be used. This option is valid only for a single-library save operation.

File expiration date (EXPDATE)

Specifies the expiration date of the file created by the save operation. If a date is specified, the file is protected and cannot be overwritten until the specified expiration date.

Notes:

1. This parameter is valid for tape and optical files.
2. Specifying this parameter does not protect against a later save operation specifying CLEAR(*ALL).

*PERM

The file is protected permanently.

date

Specify the date when protection for the file ends.

End of media option (ENDOPT)

Specifies the operation that is automatically done on the tape or optical volume after the save operation ends. If more than one volume is used, this parameter applies only to the last volume used; all other volumes are unloaded when the end of the volume is reached.

Note: This parameter is valid only if a tape or optical device name is specified for the DEV parameter. For optical devices, *UNLOAD is the only special value supported, *REWIND and *LEAVE will be ignored.

*REWIND

The tape is automatically rewound, but not unloaded, after the operation has ended.

*LEAVE

The tape does not rewind or unload after the operation ends. It remains at the current position on the tape drive.

*UNLOAD

The tape is automatically rewound and unloaded after the operation ends. Some optical devices will eject the volume after the operation ends.

Starting library (STRLIB)

Specifies the library with which to begin the save operation.

If an unrecoverable media error occurs during the save operation, this parameter can be used to restart the operation.

The basic steps for restarting a save operation are:

1. Check the job log to determine the library where the previous save operation failed. Find the last library saved, which is indicated by a successful completion message.
2. Load the next tape and ensure the tape is initialized.
3. Add the following to your original save command:

     STRLIB(library-name)  OMITLIB(library-name)
   

   where the library-name for the STRLIB and OMITLIB parameters is the last library successfully saved. This starts the save operation on the library after the last successfully saved library.

   To restore the libraries, you will need to perform a separate restore operation for each save operation that was performed.

*FIRST

The save operation begins with the first library value specified for the Library (LIB) parameter. If the first value is a generic name or special value, the save operation begins with the first library that matches this value.

name

Specify the name of the library with which to begin the save operation.

Save file (SAVF)

Specifies the save file that is used to contain the saved data. The save file must be empty, unless *ALL is specified for the Clear (CLEAR) parameter.

Note: A value must be specified for this parameter if *SAVF is specified for the Device (DEV) parameter.

Qualifier 1: Save file

name

Specify the name of save file to be used.

Qualifier 2: Library

*LIBL

All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB

The current library for the thread is used to locate the save file. If no current library entry exists in the library list, the QGPL library is used.

name

Specify the name of the library where the save file is located.

Media definition (MEDDFN)

Specifies the media definition (*MEDDFN) object that identifies the devices and media used to contain the saved data. For information about creating and using a media definition, see the Backup and Recovery book, SC41-5304, and the Create Media Definition API in the System API Reference information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.

If a media definition is specified, the VOL, SEQNBR, SAVF, and OPTFILE parameters cannot be specified. The volume identifiers and sequence numbers are specified in the media definition.

Qualifier 1: Media definition

name

Specify the name of the media definition to be used.

Qualifier 2: Library

*LIBL

All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB

The current library for the thread is searched. If no library is specified as the current library for the thread, the QGPL library is searched.

name

Specify the name of the library to be searched.

Optical file (OPTFILE)

Specifies the path name of the optical file that is used for the save operation, beginning with the root directory of the volume.

For more information on specifying path names, refer to "Object naming rules" in the CL concepts and reference topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.

*

The system generates an optical file name in the root directory of the optical volume.

'optical-directory-path-name/*'

The system generates an optical file name in the specified directory of the optical volume.

'optical-file-path-name'

Specify the path name of the optical file.

Use optimum block (USEOPTBLK)

Specifies whether or not the optimum block size is used for the save operation.

Note: Specifying USEOPTBLK(*YES) may result in a tape that can be duplicated only to a device that supports the same block size.

*YES

The optimum block size supported by the device is used for Save commands. If the block size that is used is larger than a block size that is supported by all device types, then:

• Performance may improve.
• The tape file that is created is only compatible with a device that supports the block size used. Commands such as Duplicate Tape (DUPTAP) do not duplicate files unless the files are being duplicated to a device which supports the same block size that was used.
• The value for the DTACPR parameter is ignored.

*NO

The optimum block size supported by the device is not used. Save commands use the default block size supported by all device types. The tape volume can be duplicated to any media format using the Duplicate Tape (DUPTAP) command.

Target release (TGTRLS)

Specifies the release of the operating system on which you intend to restore and use the object.

When specifying the target-release value, the format VxRxMx is used to specify the release, where Vx is the version, Rx is the release, and Mx is the modification level. For example, V5R3M0 is version 5, release 3, modification 0.

Valid values depend on the current version, release, and modification level of the operating system, and they change with each new release. You can press F4 while prompting this command parameter to see a list of valid target release values.

To specify that an object be saved for distribution to a system at a different release level than the system on which the save operation is to occur, the procedure differs for program or non-program objects and by the release level on which a program object is created. If, for example, you are saving an object for distribution to a target system running on an earlier release, you have the following choices:

For program objects:

• If the program object was created at a release level more current than the targeted earlier release, you must:
  1. create the program object again specifying the targeted earlier release
  2. save the program object specifying the targeted earlier release
  3. restore the program object on the target system.
• If the program object was created at the same release level as the target system, you can:
  1. save the program object specifying the targeted earlier release
  2. restore the program object on the target system.

For non-program objects:

You can:

1. save the object specifying the targeted earlier release
2. restore the object on the target system.

*CURRENT

The object is to be restored to, and used on, the release of the operating system currently running on your system. The object can also be restored to a system with any subsequent release of the operating system installed.

*PRV

The object is to be restored to the previous release with modification level 0 of the operating system. The object can also be restored to a system with any subsequent release of the operating system installed.

character-value

Specify the release in the format VxRxMx. The object can be restored to a system with the specified release or with any subsequent release of the operating system installed.

Notes:

1. If LIB(*NONSYS), LIB(*ALLUSR), or LIB(*IBM) is specified, only the current release can be the target release.
2. Not all objects can be targeted to another release. To find out which objects are supported, see the chart in the Backup and Recovery book, SC41-5304.

Update history (UPDHST)

Specifies whether the save history information of each saved object is changed with the date, time, and location of this save operation. The save history information for an object is displayed using the Display Object Description (DSPOBJD) command. The save history information is used to determine which journal entries are processed when RCVRNG(*LASTSAVE) and FROMENT(*LASTSAVE) or FROMENTLRG(*LASTSAVE) are used on the Apply Journaled Changes (APYJRNCHG) command.

*YES

The last save date, time, and location is updated in each object saved.

*NO

The save history information contained in the description of each object saved is not updated.

Note: UPDHST(*NO) should be used for a save operation that is not intended for recovery. For example, if the save data is sent, record by record, to another system and the save file immediately deleted, the save history information is probably not to be updated.

Clear (CLEAR)

Specifies whether active data on the media is automatically cleared or replaced. Active data is any file on the media that has not expired. For saves to tape, clearing active data will make any files on the tape volume beyond the last file written by the save operation no longer accessible. For saves to optical, the files written by the save operation can be automatically replaced while other files on the volume remain active, or all active files can be automatically cleared. Clearing does not erase the data, it just makes the files no longer accessible.

Notes:

1. Clearing a tape does not initialize it. You should initialize tapes to a standard label format before the save command is issued by using the Initialize Tape (INZTAP) command and specifying a value for the NEWVOL parameter.
2. Clearing an optical volume does initialize it.
3. If a volume that is not initialized is encountered during the save operation, an inquiry message is sent and an operator can initialize the volume.

*NONE

None of the media is automatically cleared. If the save operation encounters active data on a tape volume or in a save file, an inquiry message is sent, allowing the operator to either end the save operation or clear the media. If the save operation encounters the specified optical file, an inquiry message is sent, allowing the operator to either end the save operation or replace the file.

*ALL

All of the media is automatically cleared.

If tapes are used and a sequence number is specified for the SEQNBR parameter, the first tape is cleared beginning at that sequence number. All tapes following that first tape are completely cleared. To clear the entire first tape, SEQNBR(1) must be specified.

*AFTER

All media after the first volume is automatically cleared. If the save operation encounters active data on the first tape volume, an inquiry message is sent, allowing the operator to either end the save operation or clear the media. If the save operation encounters the specified optical file on the first volume, an inquiry message is sent, allowing the operator to either end the save operation or replace the file.

Note: The *AFTER value is not valid for save files.

*REPLACE

Active data on the media is automatically replaced. Optical volumes are not initialized. Other media is automatically cleared in the same way as the *ALL value.

Object pre-check (PRECHK)

Specifies whether the save operation for a library ends if any of the following are true:

1. The objects do not exist
2. The library or the objects were previously found to be damaged
3. The library or the objects are locked by another job
4. The requester of the save operation does not have authority for the library or to save the objects.

*NO

The save operation for a library continues, saving only those objects that can be saved.

*YES

If, after all specified objects are checked, one or more objects cannot be saved, the save operation for a library ends before any data is written. If multiple libraries are specified, the save operation continues with the next library. However, if PRECHK(*YES) and SAVACT(*SYNCLIB) are specified and an object in any library to be saved does not meet the preliminary check conditions, the save operation ends and no objects are saved.

Save active (SAVACT)

Specifies whether an object can be updated while it is being saved.

Note: If your system is in a restricted state and the SAVACT parameter is specified, the save operation is performed as if SAVACT(*NO) was specified.

*NO

Objects that are in use are not saved. Objects cannot be updated while being saved.

*LIB

Objects in a library can be saved while they are in use by another job. All of the objects in a library reach a checkpoint together and are saved in a consistent state in relationship to each other.

*SYNCLIB

Objects in a library can be saved while they are in use by another job. All of the objects and all of the libraries in the save operation reach a checkpoint together and are saved in a consistent state in relationship to each other.

Note: If you specify this value and you are saving many libraries, it can take a long time to reach a checkpoint for all of the objects and libraries in the save operation.

*SYSDFN

Objects in a library can be saved while they are in use by another job. Objects in a library may reach checkpoints at different times and may not be in a consistent state in relationship to each other.

Save active wait time (SAVACTWAIT)

Specifies the amount of time to wait for an object that is in use, or for transactions with pending changes to reach a commit boundary, before continuing the save operation.

Element 1: Object locks

For each object that is in use, specifies the amount of time to wait for the object to become available. If an object remains in use for the specified time, the object is not saved.

120

The system waits up to 120 seconds for each individual object lock before continuing the save operation.

*NOMAX

No maximum wait time exists.

0-99999

Specify the number of seconds to wait for each individual object lock before continuing the save operation.

Element 2: Pending record changes

For each group of objects that are checkpointed together, specifies the amount of time to wait for transactions with pending record changes to reach a commit boundary. The Save active (SAVACT) parameter determines which objects are checkpointed together. If 0 is specified, all objects being saved must be at commit boundaries. If any other value is specified, all objects that are journaled to the same journals as the objects being saved must reach commit boundaries. If a commit boundary is not reached in the specified time, the save operation is ended, unless the value *NOCMTBDY is specified.

*LOCKWAIT

The system waits up to the value specified for Element 1 for transactions with pending record changes to reach a commit boundary.

*NOCMTBDY

The system will save objects without requiring transactions with pending record changes to reach a commit boundary. Therefore, objects may be saved with partial transactions.

If you restore an object that was saved with partial transactions, you cannot use the object until you apply or remove journal changes (APYJRNCHG or RMVJRNCHG command) to reach commit boundaries. You will need all journal receivers that contain information about the partial transactions to apply or remove the changes. Until you apply or remove the changes, any future save of that object will include the partial transactions, even if you do not specify *NOCMTBDY.

Note: This value cannot be specified if the Target release (TGTRLS) parameter value is earlier than V5R3M0.

*NOMAX

No maximum wait time exists.

0-99999

Specify the number of seconds to wait for transactions with pending record changes to reach a commit boundary.

Element 3: Other pending changes

For each library, specifies the amount of time to wait for transactions with other pending changes to reach a commit boundary. Other pending changes include the following:

• Data Definition Language (DDL) object level changes for that library.
• Any API commitment resource that was added without the option to allow normal save processing. For more information, see the Add Commitment Resource (QTNADDCR) API in the System API Reference information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.

If a commit boundary is not reached for a library in the specified time, the library is not saved.

*LOCKWAIT

The system waits up to the value specified for Element 1 for the types of transactions that are listed above to reach a commit boundary.

*NOMAX

No maximum wait time exists.

0-99999

Specify the number of seconds to wait for the types of transactions that are listed above to reach a commit boundary.

Save active message queue (SAVACTMSGQ)

Specifies the message queue that the save operation uses to notify the user that the checkpoint processing for a library is complete. A separate message is sent for each library to be saved when the *SYSDFN or *LIB value is specified for the Save active (SAVACT) parameter. When *SYNCLIB is specified for the SAVACT parameter, one message is sent for all libraries in the save operation.

This parameter can be used to save the objects at a known, consistent boundary to avoid additional recovery procedures following a restore operation. Applications can be stopped until the checkpoint processing complete message is received.

Single values

*NONE

No notification message is sent.

*WRKSTN

The notification message is sent to the work station message queue. This value is not valid in batch mode.

Qualifier 1: Save active message queue

name

Specify the name of the message queue to be used.

Qualifier 2: Library

*LIBL

All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB

The current library for the job is used to locate the message queue. If no library is specified as the current library for the job, the QGPL library is used.

name

Specify the name of the library where the message queue is located.

Save access paths (ACCPTH)

Specifies whether the logical file access paths that are dependent on the physical files being saved are also saved. The access paths are saved only in the case of the following:

• All members on which the access paths are built are included in this save operation.
• The access paths are not invalid or damaged at the time of the save.

The system checks to ensure the integrity of the access paths. Any discrepancies found by the system will result in the access paths being rebuilt.

Informational messages are sent indicating the number of logical file access paths saved with each physical file. All physical files on which an access path is built must be in the same library. This parameter does not save logical file objects; it only controls the saving of the access paths. More information on the restoring of saved access paths is in the Backup and Recovery book, SC41-5304.

ATTENTION: If the based-on physical files and the logical files are in different libraries, the access paths are saved. However, if the logical files and the based-on physical files are in different libraries and the logical files or physical files do not exist at restore time (such as during disaster recovery or the files were deleted) the access paths are not restored. They are rebuilt. For the fastest possible restore operation for logical files, the logical files and the based-on physical files must be in the same library and must be saved at the same time.

*SYSVAL

The QSAVACCPTH system value determines whether to save the logical file access paths that are dependent on the physical files that are being saved.

*NO

Only those objects specified on the command are saved. No logical file access paths are saved.

*YES

The specified physical files and all eligible logical file access paths over them are saved.

Note: Specifying this value does not save the logical files.

Save file data (SAVFDTA)

Specifies, for save file objects, whether the description of a save file, or both the description and the contents of a save file, are saved.

*YES

The description and contents of a save file are saved.

*NO

Only the description of a save file is saved.

Spooled file data (SPLFDTA)

Specifies whether to save spooled file data and attributes for output queues that are saved.

*NONE

No spooled file data is saved.

*ALL

For each output queue that is saved, all available spooled file data on the output queue is saved.

Queue data (QDTA)

Specifies, for queue objects, whether the description of a queue, or both the description and the contents of a queue, are saved.

*NONE

Only the description of a queue is saved.

*DTAQ

The description and contents of a standard data queue are saved. Only the description of a Distributed Data Management (DDM) data queue is saved.

Storage (STG)

Specifies whether the system storage that is occupied by the data portion of the specified members (except for save files), modules, programs, service programs, Structured Query Language (SQL) packages, and journal receivers in the library being saved is freed as part of the save operation. Only the data portion of the objects is freed, not the descriptions of the objects.

*KEEP

The storage occupied by the data portion of the objects being saved is not freed.

*FREE

The storage occupied by the data portion of the specified objects being saved is freed as part of the save operation. The storage for all the objects in a library is freed only after all the objects in that library are saved successfully.

Note: To prevent the possible abnormal end of a program, the program being saved must not be running in the system when *FREE is specified.

Data compression (DTACPR)

Specifies whether data compression is used. If the save is running while other jobs on the system are active and software compression is used, the overall system performance may be affected.

Note: If *DEV is specified for both this parameter and the Data compaction (COMPACT) parameter, only device data compaction is performed if device data compaction is supported on the device. Otherwise, data compression is performed.

If *YES is specified for this parameter and *DEV is specified for the COMPACT parameter, both device data compaction and device data compression are performed if supported on the device.

*DEV

If the save is to tape and the target device supports compression, hardware compression is performed. Otherwise, no data compression is performed.

*NO

No data compression is performed.

*YES

If the save is to tape and the target device supports compression, hardware compression is performed. If compression is not supported, or if the save data is written to optical media or to a save file, software compression is performed. Low software compression is used for all devices except optical DVD, which uses medium software compression.

*LOW

If the save operation is to a save file or optical, software data compression is performed with the SNA algorithm. Low compression is usually faster and the compressed data is usually larger than if medium or high compression is used.

Note: This value is not valid for tape.

*MEDIUM

If the save operation is to a save file or optical, software data compression is performed with the TERSE algorithm. Medium compression is usually slower than low compression but faster than high compression. The compressed data is usually smaller than if low compression is used and larger than if high compression is used.

Note: This value is not valid for tape.

*HIGH

If the save operation is to a save file or optical, software data compression is performed with the LZ1 algorithm. High compression is usually slower and the compressed data is usually smaller than if low or medium compression is used.

Note: This value is not valid for tape.

Data compaction (COMPACT)

Specifies whether device data compaction is performed.

*DEV

Device data compaction is performed if the data is saved to tape and all tape devices specified for the Device (DEV) parameter support the compaction feature.

Note: If *DEV is specified for both the Data compression (DTACPR) parameter and this parameter, only device data compaction is performed if device data compaction is supported on the device. Otherwise, data compression is performed if supported on the device.

If *YES is specified for the DTACPR parameter and *DEV is specified for this parameter, both device data compaction and device data compression are performed if supported on the device.

*NO

Device data compaction is not performed.

Libraries to omit (OMITLIB)

Specifies the names of one of more libraries, or the generic names of each group of libraries, to be excluded from the save operation.

Single values

*NONE

No libraries are excluded from the save operation.

*USRSPC

The libraries identified in the user space specified for the Command user space (CMDUSRSPC) parameter are excluded from the save operation.

Other values (up to 300 repetitions)

generic-name

Specify the generic name of the libraries to be excluded. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk (*) substitutes for any valid characters. A generic name specifies all libraries with names that begin with the generic prefix, for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete library name.

name

Specify the name of the library to be excluded from the save operation.

Objects to omit (OMITOBJ)

Specifies the objects to be excluded from the operation. Up to 300 objects or generic object values can be specified.

Single values

*USRSPC

The objects identified in the user space specified for the Command user space (CMDUSRSPC) parameter are excluded from the save operation.

Other values (up to 300 repetitions)

Element 1: Object

Qualifier 1: Object

*NONE

No objects are excluded from the operation.

*ALL

All objects of the specified object type are excluded from the operation.

generic-name

Specify the generic name of the objects to be excluded.

Note: A generic name is specified as a character string that contains one or more characters followed by an asterisk (*). If a generic name is specified, then all objects that have names with the same prefix as the generic object name are selected.

name

Specify the name of the object to be excluded from the operation.

Qualifier 2: Library

*ALL

The specified objects are excluded from all libraries that are part of the operation.

generic-name

Specify the generic name of the libraries that contain objects to be excluded.

Note: A generic name is specified as a character string that contains one or more characters followed by an asterisk (*). If a generic name is specified, then all objects that have names with the same prefix as the generic object name are selected.

name

Specify the name of the library that contains the object to be excluded from the operation.

Element 2: Object type

*ALL

All object types are excluded from the operation, depending on the value specified for the object name.

character-value

Specify the object type of the objects to be excluded from the operation.

To see a complete list of object types when prompting this command, position the cursor on the field for this parameter and press F4 (Prompt). For a description of the object types, see "Object types" in the CL concepts and reference topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.

ASP device (ASPDEV)

Specifies the auxiliary storage pool (ASP) device to be included in the save operation. This parameter is used to subset the list of objects which qualify for the SAV based on the OBJ parameter.

*

The operation includes the system ASP (ASP number 1), all basic user ASPs (ASP numbers 2-32), and, if the current thread has an ASP group, all independent ASPs in the ASP group.

*SYSBAS

The system ASP and all basic user ASPs are included in the save operation.

*CURASPGRP

If the current thread has an ASP group, all independent ASPs in the ASP group are included in the save operation.

name

Specify the name of the ASP device to be included in the save operation.

Output (OUTPUT)

Specifies whether a list with information about the saved objects is created. The information can be printed with the job's spooled output or directed to a database file.

*NONE

No output listing is created.

*PRINT

The output is printed with the job's spooled output.

*OUTFILE

The output is directed to the database file specified for the File to receive output (OUTFILE) parameter.

Note: You must specify a database file name for the File to receive output (OUTFILE) parameter when OUTPUT(*OUTFILE) is specified.

File to receive output (OUTFILE)

Specifies the database file to which the information is directed when *OUTFILE is specified for the Output (OUTPUT) parameter. If the file does not exist, this command creates a database file in the specified library. If a new file is created, the system uses QASAVOBJ in QSYS with the format name QSRSAV as a model.

Qualifier 1: File to receive output

name

Specify the name of the database file to which output from the command is directed. If this file does not exist, it is created in the specified library.

Qualifier 2: Library

*LIBL

All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB

The current library for the thread is used to locate the file. If no library is specified as the current library for the job, the QGPL library is used.

name

Specify the name of the library to be searched.

Output member options (OUTMBR)

Specifies the name of the database file member to which the output is directed when *OUTFILE is specified for the Output (OUTPUT) parameter.

Element 1: Member to receive output

*FIRST

The first member in the file receives the output. If OUTMBR(*FIRST) is specified and the member does not exist, the system creates a member with the name of the file specified for the File to receive output (OUTFILE) parameter.

name

Specify the name of the file member that receives the output. If OUTMBR(member-name) is specified and the member does not exist, the system creates it.

If the member exists, you can add records to the end of the existing member or clear the existing member and add the records.

Element 2: Replace or add records

*REPLACE

The existing records in the specified database file member are replaced by the new records.

*ADD

The new records are added to the existing information in the specified database file member.

Type of information (INFTYPE)

Specifies the type of information which is printed or directed to the database file.

*OBJ

The list contains an entry for each object requested to be saved.

*ERR

The list contains information about the command, an entry for each library, and an entry for each object that was not successfully saved.

*LIB

The list contains a library entry for each library requested to be saved

*MBR

The list contains an entry for each object, database file member, and spooled file requested to be saved.

Command user space (CMDUSRSPC)

Specifies a user space containing the values for the parameters which have *USRSPC specified for this command. The user space allows up to 32767 list values for each parameter, while the command parameters only allow up to 300 list values. The user space must define the parameters in the format used by the Save Object List (QSRSAVO) API.

Qualifier 1: User space

name

Specify the name of the user space containing the values for the parameters which have *USRSPC specified for this command.

Qualifier 2: Library

*LIBL

All libraries in the library list for the current thread are searched until the first match is found.

*CURLIB

The current library for the job is used to locate the user space. If no library is specified as the current library for the job, the QGPL library is used.

name

Specify the name of the library where the user space is located.

Examples

Example 1: Saving a Library on a Tape Device

SAVLIB   LIB(JOE)  DEV(TAP01)

This command saves the library named JOE on the tape that is in the tape device named TAP01. The storage occupied by JOE in the system is not freed, because the STG parameter default (*KEEP) was assumed.

Example 2: Saving on Multiple Volumes

SAVLIB   LIB(QGPL)  DEV(OPT01)  VOL(ABC DEF GHI)

The general purpose library (QGPL) is saved on the optical volumes in the device named OPT01. The optical volumes used must have the volume names ABC, DEF, and GHI. If the save operation is not finished when volume ABC is full, a message is issued to the operator asking for volume DEF to be placed in the device.

Example 3: Freeing Storage when Saving Data

SAVLIB   LIB(CUSTDATA)  DEV(TAP01)
         VOL(CUSTNM CUSTAD)  STG(*FREE)

The library named CUSTDATA is saved on volumes CUSTNM and CUSTAD, which are put in the tape device TAP01. The storage occupied by the specified members, modules, programs, service programs, SQL packages, and journal receivers in the CUSTDATA library is freed after it is saved.

Example 4: Saving on Multiple Devices Serially

SAVLIB   LIB(USRLIB)  DEV(TAP01 TAP02 TAP03)
         VOL(USRA USRB USRC USRD)  ENDOPT(*UNLOAD)

The library named USRLIB is saved on four tape volumes on three tape devices. The volume named USRA is put on the device named TAP01, the volume named USRB on the device named TAP02, the volume named USRC on the device named TAP03, and the volume named USRD on the device named TAP01. The volume named USRA is rewound, and must be unloaded by the operator when processing is complete so that the device named TAP01 can be used for the volume named USRD.

Example 5: Saving on Multiple Devices in Parallel

SAVLIB   LIB(USRLIB)  DEV(*MEDDFN)  MEDDFN(LIBA/MEDDFNA)

The library named USRLIB is saved on the devices specified in the media definition named MEDDFNA in library LIBA. For information about creating and using a media definition, see the Backup, Recovery, and Availability topic in the Information Center.

Example 6: Saving a Library with a Media File Label

SAVLIB   LIB(LIB1)  DEV(TAP01)  LABEL(MONDAYBACKUP)

This command uses the tape device named TAP01 to save the library named LIB1 on tape. The library is saved with a media file label of MONDAYBACKUP. This label must be specified when restoring the library or any of its objects.

Example 7: Specifying Where the Save Operation Starts

SAVLIB   LIB(*NONSYS)  DEV(TAP01 TAP02)
         STRLIB(MIKESLIB)  ASPDEV(*SYSBAS)

This command saves all libraries that are located on the system and basic user ASPS, beginning with the library named MIKESLIB on tape devices named TAP01 and TAP02. System libraries and libraries that are normally saved first (QSYS2, QGPL, and QUSRSYS) are not saved.

Example 8: Saving User Libraries in an Independent ASP Group

SAVLIB   LIB(*ALLUSR)  DEV(TAP01)  ASPDEV(*CURASPGRP)

This command saves all user libraries on the independent ASPs that are in the ASP group for the current thread. It does not save libraries on the system ASP (ASP number 1) or on basic user ASPs (ASP numbers 2-32).

Example 9: Saving Spooled Files

SAVLIB   LIB(MYLIB)  DEV(TAP01)  SPLFDTA(*ALL)

This command saves the library named MYLIB, including the spooled file data for any output queues in the library.

Error messages

*ESCAPE Messages

CPF3701

&1 objects saved from &3. &2 not saved.

CPF3703

&2 &1 in &3 not saved.

CPF3708

Save file &1 in &2 too small.

CPF3709

Tape devices do not support same densities.

CPF3727

Duplicate device &1 specified on device name list.

CPF3728

Device &1 specified with other devices.

CPF3730

Not authorized to &2 &1 in library &3.

CPF3731

Cannot use &2 &1 in library &3.

CPF3733

&2 &1 in &3 previously damaged.

CPF3735

Storage limit exceeded for user profile &1.

CPF3738

Device &1 used for save or restore is damaged.

CPF3749

Objects from library &2 not saved.

CPF3751

Some libraries not saved.

CPF3767

Device &1 not found.

CPF3768

Device &1 not valid for command.

CPF377D

Save ended because of read error on internal system resource.

CPF377E

Not enough storage for save-while-active request.

CPF377F

Save-while-active request prevented by pending record changes.

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.

CPF378A

Message queue not available.

CPF378C

SAVACTMSGQ(*WRKSTN) not valid for batch job.

CPF378E

Library &1 not saved.

CPF3781

Library &1 not found.

CPF3782

File &1 in &2 not a save file.

CPF3785

Not all subsystems ended.

CPF3789

Only one library allowed with specified parameters.

CPF379E

Not enough storage available to save library &1.

CPF3793

Machine or ASP storage limit reached.

CPF3794

Save or restore operation ended unsuccessfully.

CPF3797

Objects from library &3 not saved. Save limit exceeded.

CPF37AB

*NOCMTBDY not allowed with target release.

CPF37AC

Library not allowed with *NOCMTBDY.

CPF37B1

SPLFDTA not allowed with target release.

CPF37B4

User space &1 in &2 not valid.

CPF380B

Save cannot be completed at this time.

CPF3812

Save file &1 in &2 in use.

CPF3815

Save file &1 in &2 too small for save operation.

CPF3818

Starting library &1 not found.

CPF384E

USEOPTBLK(*YES) not valid for CD-ROM premastering.

CPF3871

No objects saved or restored; &3 objects not included.

CPF388B

Optical file path name not valid.

CPF3892

&2 &1 in &3 not saved.

CPF3894

Cancel reply received for message &1.

CPF38A2

ASP device &1 not correct.

CPF38A3

File &1 in &2 not valid with ASPDEV.

CPF38A4

ASP device &1 not correct.

CPF5729

Not able to allocate object &1.

CPF9809

Library &1 cannot be accessed.

CPF9812

File &1 in library &2 not found.

CPF9814

Device &1 not found.

CPF9820

Not authorized to use library &1.

CPF9822

Not authorized to file &1 in library &2.

CPF9825

Not authorized to device &1.

CPF9833

*CURASPGRP or *ASPGRPPRI specified and thread has no ASP group.

CPFB8ED

Device description &1 not correct for operation.

OPT1332

Optical volume not found in device &1.

*STATUS Messages

CPF3770

No objects saved or restored for library &1.

CPF3771

&1 objects saved from &3. &2 not saved.

CPF3871

No objects saved or restored; &3 objects not included.