Working with the Save-While-Active Message Queue

Instead of using the MONSWABRM command to monitor SWA activity, you can instruct the SWA message queue to send a message when the libraries reach synchronization. It is recommended that you use this approach rather than letting BRMS default to *LIB. This allows better control by monitoring a specific message queue rather than one created by the name of the first library that BRMS saves. For example, if you want BRMS to save the first entry in the control group on certain days, the message queue would vary from day-to-day.

                     Edit Backup Control Group Entries               RCHAS400   
                                                                                
 Group . . . . . . . . . . : SAMPLE                                             
 Default activity  . . . . . *BKUPCY                                            
 Text  . . . . . . . . . . . Sample control group                               
                                                                                
 Type information, press Enter.                                                 
                                                                                
                                  Weekly   Retain Save     SWA                  
      Backup     List ASP         Activity Object While    Message    Sync      
 Seq  Items      Type Device      SMTWTFS  Detail Active   Queue      ID        
                                                                                
   10 *EXIT                       *DFTACT                                       
   20 LIBA            *SYSBAS     *DFTACT  *NO    *SYNCLIB OPER01     *NONE     
   30 LIBB            *SYSBAS     *DFTACT  *NO    *SYNCLIB *LIB       *NONE     
   40 LIBC            *SYSBAS     *DFTACT  *NO    *SYNCLIB *LIB       *NONE     
   50 LIBD            *SYSBAS     *DFTACT  *NO    *SYNCLIB *LIB       *NONE     
   60 LNKLIST    *LNK *ALLAVL     *DFTACT  *NO    *YES     *LIB       *NONE     
   70 *EXIT                       *DFTACT                                       
                                                                                
                                                                         Bottom 
 F3=Exit    F5=Refresh    F10=Change item    F11=Display exits                  
 F12=Cancel    F14=Display client omit status    F24=More keys

In this example, the system uses the OPER01 message queue to log the following messages:

• 0 of 4 libraries processed. Started LIBA at 02/03/05 10:20:06.
• 1 of 4 libraries processed. Started LIBB at 02/03/05 10:20:07.
• 2 of 4 libraries processed. Started LIBC at 02/03/05 10:20:078.
• 3 of 4 libraries processed. Started LIBD at 02/03/05 10:20:09.

BRMS uses the first message queue (at LIBA) to monitor for the synchronization. Even if you specify different message queues for each of the other libraries, the SWA synchronization message still goes to message queue OPER01.

If you require synchronization messages to go to different message queues, you must separate the control group entries for libraries with values such as *EXIT or *LOAD. BRMS also separates the library groups if it detects a change of value in the Retain object detail, Weekly activity, and Save-while-active fields.

For more detailed information about the SWA feature, see Recovering your system.