Save system information

Use the Save system information (SAVSYSINF) command to perform a partial save of the data saved by the Save system (SAVSYS) command.

Note:

The SAVSYSINF command increases the time and complexity it takes to recover your server.
Do not use the SAVSYSINF command as a replacement for the SAVSYS command, and do not use it for a system upgrade or migration. You must have performed a successful SAVSYS before using this command.
The SAVSYSINF command is only intended for customers who cannot bring their server to restricted state and take the necessary downtime it takes to perform a SAVSYS command. A SAVSYSINF should be considered a "partial" of a complete SAVSYS. During a complete system recovery the SAVSYSINF save will also need to be recovered along with the complete SAVSYS.
If you are using the SAVSYSINF command in your backup strategy, the PTF save files must remain on the system until the next SAVSYS command is run. Do not run the Delete Program Temporary Fix (DLTPTF) command unless you run it just before or after the SAVSYS command. For more information see Clean up fixes.

*SAVSYS or *ALLOBJ special authority is required to use the SAVSYSINF command. You can not restore a SAVSYSINF to another existing system. You can use the SAVSYSINF for system recovery when you are recovering a system using the SAVSYS and SAVSYSINF media. The data saved by the SAVSYSINF is cumulative from the last SAVSYS.

When you save your configuration by using the SAVSYSINF command, the server saves the following object types from QSYS:

*JOBD	*JOBQ	*EDTD
*JRN	*JRNRCV	*SBSD
*CLS	*MSGQ	*TBL
*IGCTBL	*DTAARA	*CMD ₁
*MSGF ₁
₁ objects changed since the last SAVSYS

Additional items that are saved include the following:

System reply list	Service attributes	Environment variables
Certain system values	Network attributes	PTFs applied since the last SAVSYS ₁ for 5722SS1 ₂and 5722999 ₂
₁If you load PTFs, you must copy them into SERVICE. This enables SAVSYSINF to find the save files of the PTFs. The Copy PTFs (CPYPTF) service attribute specifies whether to copy PTF save files into SERVICE when PTFs are loaded from a tape or optical device. Use the CHGSRVA CPYPTF(*YES) command to change the service attribute on your system to copy PTF save files when loading PTFs from media.
₂SAVSYSINF will save PTFs for licensed programs 5722SS1 and 5722999 which were temporarily or permanently applied since the last SAVSYS. In addition, for loaded PTFs, the IPL action will be checked to determine if the PTF should be included. Loaded PTFs, scheduled to be applied at the next IPL, (IPL action 1 or 3) will be saved. PTFs scheduled to be removed at the next IPL, (IPL action 2 or 4) will not be saved.

Items that are not saved as part of SAVSYSINF command include the following:

Licensed Internal Code	QSYS library	System values which cannot be changed
Configuration objects (use the SAVCFG command)	System values related to date/time	System values that cannot be saved
Security data (use the SAVSECDTA command)	QPWDLVL (Password level) system values

The SAVSYSINF command may be incorporated into a save strategy once a base SAVSYS in restricted state is successful. It is recommended that a save of the entire system including a SAVSYS be done in restricted state. This can be accomplished by performing a Go Save Option 21, a combination of an Option 22 and 23, or by using the equivalent functions within BRMS.

Once you have a base SAVSYS, you may perform some or all of these save commands to capture changed or updated information:

SAVLIB LIB(*IBM)
SAV OBJ(('/QIBM/ProdData')('/QOpenSys/QIBM/ProdData')) UPDHST(*YES)
SAVSYSINF

These are other save commands that should be used on a daily basis to save user data:

SAVESECDTA
SAVCFG
SAVLIB LIB(*ALLUSR)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*')('/QSYS.LIB'*OMIT)('/QDLS'*OMIT))UPHST(*YES)
SAVSYSINF

Example SAVSYSINF:

This command saves the system information to the save file named SAVF in library QGPL. The save file will be cleared automatically. Information about what was saved will be written to the first member of the file name OUTPUT in library QGPL. The file and member will be created if they do not exist.

SAVSYSINF DEV(*SAVF) SAVF(QGPL/SAVF) CLEAR(*ALL) +
          OUPUT(*OUTFILE) OUTFILE(QGPL/OUPUT)