SET SAVE command

Controls the saving of settings, breakpoints, and monitor specifications.

Read syntax diagramSkip visual syntax diagramSETSAVE SETTINGSNOAUTOAUTOONCEFILE*setfileidBPSNOAUTOAUTOFILE*bpfileidMONITORSNOAUTOAUTO ;
SETTINGS
Indicates that SET values and WINDOW SIZE and WINDOW CLOSE settings are to be saved. The following SET values are not saved:
  • SET DBCS
  • SET FREQUENCY
  • SET NATIONAL LANGUAGE
  • SET PROGRAMMING LANGUAGE
  • FILE operand of SET RESTORE SETTINGS
  • SET QUALIFY
  • SET SOURCE
  • SET TEST
BPS
Indicates that breakpoints and LOADDEBUGDATA (LDD) specifications are to be saved. The following breakpoints are saved:
  • APPEARANCE breakpoints
  • CALL breakpoints
  • DELETE breakpoints
  • ENTRY breakpoints
  • EXIT breakpoints
  • GLOBAL APPEARANCE breakpoints
  • GLOBALCALL breakpoints
  • GLOBAL DELETE breakpoints
  • GLOBAL ENTRY breakpoints
  • GLOBAL EXIT breakpoints
  • GLOBAL LABEL breakpoints
  • GLOBAL LOAD breakpoints
  • GLOBAL STATEMENT and GLOBAL LINE breakpoints
  • LABEL breakpoints
  • LOAD breakpoints
  • OCCURRENCE breakpoints
  • STATEMENT and LINE breakpoints
  • TERMINATION breakpoint
MONITORS
Indicates that all monitor and LOADDEBUGDATA (LDD) specifications are to be saved.
NOAUTO
Indicates that at z/OS® Debugger termination, the specified settings, breakpoint, or specifications are not to be saved. NOAUTO is the default until AUTO is specified.
AUTO
Indicates that, if possible, the specified data is to be saved at z/OS Debugger termination.
ONCE
Indicates that the settings information is to be saved once. The settings information is saved at the termination of the current debugging session but the saved value for SET SAVE SETTINGS is NOAUTO. This enables you save the settings of the current debugging session and not have the settings updated at the termination of subsequent debug sessions.
*
Indicates that the default file name is to be used to save settings, breakpoints, and monitor specifications at termination. The default name is userid.DBGTOOL.SAVESETS for settings and userid.DBGTOOL.SAVEBPS for breakpoints and monitor specifications. You can modify the default names by specifying the EQAOPTS commands SAVESETDSN and SAVEBPDSN.
FILE setfileid
Indicates the data set name to be used to save and restore settings. The data set must exist before running this command.

In z/OS, setfileid is a DD name or a fully-qualified data set name (without apostrophes (')). In CICS®, setfileid is a fully-qualified data set name.

If setfileid is less than nine characters in length and does not contain a period, z/OS Debugger assumes it is a DD name. Otherwise, it is assumed to be a fully-qualified data set name.

In batch mode, the data set name is ignored. Use the INSPSAFE DD statement to indicate the name of the data set to use to restore and save settings.

This data set must be a sequential data set with a record format (RECFM) of VB and with a record length (LRECL) greater than or equal to 3204.

FILE bpfileid
Indicates the data set to be used to save breakpoints and monitor specifications. The data set must exist before running this command.

In z/OS, bpfileid is a DD name or a fully-qualified data set name (without apostrophes (')). In CICS, bpfileid is a fully-qualified data set name.

If bpfileid is less than nine characters in length and does not contain a period, z/OS Debugger assumes it is a DD name. Otherwise, it is assumed to be a fully-qualified data set name.

In batch mode, the data set name is ignored. Use the INSPBPM DD statement to indicate the name of the data set to use to save breakpoints and monitor specifications.

This data set must be a PDS or PDSE (a PDSE is recommended) and you cannot specify a member name. This data set must have a record format (RECFM) of VB and with a record length (LRECL) greater than or equal to 3204. z/OS Debugger assigns a member name that is the load module name at enclave start. The breakpoints for each enclave are saved in a separate member of the PDS or PDSE. If you want to discard any saved breakpoints, LDD specifications, and monitor specifications, you can delete the member that has the name of the load module that started the enclave. Do not alter the contents of the member.

Usage notes

  • You cannot use AUTO when you are debugging a CICS program and you are logged in with the same user ID as the default user ID.
  • When you are debugging a CICS program, the CICS region must have update authorization to the SAVE SETTINGS and SAVE BPS data sets.
  • When you enter the QUIT or QQ command from a nested enclave and the SET SAVE BPS AUTO, SET SAVE MONTORS AUTO, or both are in effect, only the data for the lowest level enclave is saved. No data for the higher level enclaves is saved.
  • If you are debugging Db2® stored procedures, you must do one of the following tasks:
    • Ensure that the default data set does not exist.
    • Ensure that the name of the default data set is NULLFILE.
    • Change the name of the data set by using the SET SAVE SETTINGS command.

    Because multiple users share the same default data set, other users can alter the settings in that data set. You can specify that NULLFILE be the name of the default data set through the EQAOPTS commands SAVESETDSN and SAVEBPDSN.

  • Specifying setdsn for SAVE SETTINGS does not change the name of the data set from which AUTO RESTORE SETTINGS is done. It only changes the name of the data set used by AUTO SAVE SETTINGS and the RESTORE SETTINGS commands. AUTO RESTORE SETTINGS is always done from the default data set or DD name, depending on the environment.
  • If the EQAOPTS commands SAVESETDSNALLOC and SAVEBPDSNALLOC are specified, z/OS Debugger creates the data sets, if they don't exist, and then runs the corresponding SET SAVE SETTINGS AUTO or SET SAVE BPS AUTO commands to enable their usage. To learn how to specify the EQAOPTS commands SAVESETDSNALLOC and SAVEBPDSNALLOC, see EQAOPTS commands.

Refer to the following topics for more information related to the material discussed in this topic.

  • Related tasks
  • IBM® z/OS Debugger User's Guide