Content of control groups

A backup control group can contain just one item or a group of items.

Consider grouping the following items together in a control group:
  • All of the libraries that belong to a particular application.
  • Selected objects, such as those that change on a regular basis (instead of using an *INCR save for the objects, which must identify the changed objects).
  • Libraries that comprise a database network.
  • Byte stream files that form part of the application data.
  • Spooled files that you may need later (for example, invoices or pay slips).
  • Items with similar retention periods.
  • Critical applications that you need to restore before others.
  • Noncritical applications or libraries that you can restore at a later time.
The following table provides an overview of the items you can place in a control group:
Table 1. Backup control group backup items
Named Items Special Values Special Operations
  • Library names
  • Generic library names
  • Backup list names
    • Object list
    • Folder list
    • Link list
    • Spooled file list
  • *ALLCHGRCV
  • *ALLDLO
  • *ALLDTCRCV
  • *ALLPROD
  • *ALLTEST
  • *ALLUSR
  • *ASPnn
  • *DLOnn
  • *IBM
  • *LINK
  • *LNKOMTLTS
  • *LNKOMTONL
  • *LTSOMTONL
  • *QHST
  • *SAVCFG
  • *SAVSECDTA
  • *SAVSYS
  • *SAVSYSINF
  • *EXIT
  • *LOAD
  • *SETASPGRP

A control group might contain one library or several; one special value or several; configuration and security data; or special operations such as *LOAD or *EXIT. In short, you can save any of the items that are listed in Table 1 in a control group. Grouped items may be of the same type (all libraries or all special values), or they may be of different types (for example, libraries, special values, and special operations).

Use special operations and special values as backup items to call system functions. They direct BRMS to perform predefined actions or to assume predefined values in a field. You can also use a backup list as an entry in a control group. Backup lists are particularly useful for separating critical data and applications for easier recovery. They also make it easier to manage groups of data. You can find detailed information about designing backup lists in a later section of this chapter.

The following list provides a short description of the special operations and special values that can be used as Backup Item entries in control groups. Refer to the online help information for more information about these items.

Special Operations

*EXIT
Performs user command processing
*LOAD
Begins a new tape
*SETASPGRP
Sets an auxiliary storage pool group to the job running the backup. Any previously set auxiliary storage pool group is automatically unset. The name of a primary auxiliary storage pool defining the auxiliary storage pool group must be specified in Auxiliary Storage Pool Device prompt.

Special Values

*ALLDLO
Saves all folders, documents, and mail in all ASPs
Note: *MAIL data is backed up as a separate item whenever a cumulative or incremental save of *ALLDLO is performed. BRMS issues a SAVDLO DLO(*MAIL) SAVTYPE(*FULL) for the *ALLDLO.
*DLOnn
Saves all folders, documents, and mail in a specified ASP
*ALLUSR
Saves all user libraries
*ALLPROD
Saves all *PROD type user libraries
*ALLTEST
Saves all *TEST type user libraries
*ASPnn
Saves a specified ASP (user library type objects only)
*IBM
Saves all IBM libraries
*LINK
Saves all objects not in /QSYS.LIB and /QDLS directories
*LNKOMTLTS
Saves all integrated file system directories and files except all Lotus server files and files in /QSYS.LIB and /QDLS directories.
*LNKOMTONL
Saves all integrated file system directories and files except online Lotus server backup files and files in /QSYS.LIB and /QDLS directories.
*LTSOMTONL
Saves all Lotus server files except online Lotus server files.
*QHST
Saves history information
*SAVCFG
Saves configuration
*SAVSECDTA
Saves security data
*SAVSYS
Saves the operating system
*ALLCHGRCV
Saves journal receivers that have not been saved since they were last changed. Only journal receivers associated with journals in user libraries that do not start with 'Q' are processed.

Object list QCHGJRNRCV can be used to indicate which journal receivers should be processed by *ALLCHGRCV. If QCHGJRNRCV does not exist, all receivers in libraries that do not start with 'Q' are processed.

Note: Objects, that are journaled to the journal associated with these journal receivers, must be saved with retain object detail *YES, *OBJ or *MBR. If the object detail for the objects is not retained, *ALLCHGRCV saves all of the changed journal receivers every time it is run after BRMS maintenance has run instead of saving only the recently changed receivers.
*ALLDTCRCV
Saves detached journal receivers that have not been saved since they were detached. Only journal receivers associated with journals in user libraries that do not start with 'Q' are processed.

Object list QDTCJRNRCV can be used to indicate which journal receivers should be processed by *ALLDTCRCV. If QDTCJRNRCV does not exist, all receivers in libraries that do not start with 'Q' are processed.

Note: Objects, that are journaled to the journal associated with these journal receivers, must be saved with retain object detail *YES, *OBJ or *MBR. If the object detail for the objects is not retained, *ALLDTCRCV saves all of the detached journal receivers every time it is run after BRMS maintenance has run instead of saving only the recently detached receivers.
*SAVSYSINF
Saves a subset of operating system data and object information saved by the *SAVSYS backup item.
Note:
  1. This backup item does not require restricted state and is not to be used for system upgrades or migrations.
  2. This backup item does not replace the *SAVSYS backup item.
  3. A *SAVSYS must have been performed on the system in order to use this backup item.