Submitting a Backup to the Controlling Subsystem

The BRMS console monitor is an interactive process that emulates batch processing. If you run IPL quite often, you will need to sign on to the system console and start the console monitor to be prepared for the next backup scheduled for the console monitor. This can be a cumbersome task if you run IPL nightly and your backups are otherwise fully automated.

Beginning with V5R3M0, BRMS offers a new alternative which allows for true batch processing of restricted state backups in the controlling subsystem and does not require you to sign on to the system console or start the console monitor. To select this option, you specify the special value *CTLSBS on the Submit to batch (SBMJOB) parameter on the STRBKUBRM command. When you use this special value, BRMS creates the QBRM/Q1ACTLSBS job queue if it does not exists, adds the job queue as a job queue entry in the subsystem description of the controlling subsystem, then submits the backup job directly to this job queue.

The controlling subsystem cannot run more than one job when in restricted state. If you are running a backup in either the batch job or in the interactive job, any attempt to end all subsystems from one job will end the other job. This is important because it implies that if you are running a backup in batch and that backup requires all subsystems to be ended, the interactive session on the system console will be ended. Therefore, any backups submitted to batch in the controlling subsystem must be fully automated. You will not be able to respond to inquiry messages such as tape mount requests when running in batch mode. Always perform a test backup using *CONSOLE for the SBMJOB parameter of the STRBKUBRM command to assure automation before making the transition to the *CTLSBS special value.

System reference code A900 3C70 is displayed on the system operator panel while running in batch restricted state. Normal system operations will resume and the interactive session on the system console is restarted when subsystems are started following the backup. Should a problem occur and the subsystem cannot be started by BRMS, there are two methods by which you can terminate the batch backup job and restart the interactive session on the system console.

  1. Select option 21 from the operator panel to start DST then select Option 14 — End batch restricted state.
  2. Change the time limit for the Restricted state time limit prompt on the BRMS System Policy to a value which is comparable to your backup window. If the backup hangs and subsystems are not restarted in this time limit, the backup job is ended and the controlling subsystem is restarted.
Notes:
  1. Because of the implications of using batch restricted state, this function is not automatically enabled. You must set the Allow backups in batch prompt on the BRMS System Policy to *YES to enable this function.
  2. Due to the nature of batch restricted state processing, which ends the system console session, BRMS ignores Signoff Exception processing when running in this mode.
  3. If you submit a backup job to the controlling subsystem which ends all subsystems, the controlling subsystem will be automatically restarted by i5/OS when the backup job ends.


[ Top of Page | Previous Page | Next Page | Contents | Index ]