Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


The Print Report using BRM (PRTRPTBRM) command has been enhanced to support the *CTLGRPSTAT value on the Report type (TYPE) parameter. The *CTLGRPSTAT report provides summarized information about backup control groups, specified on the Control group (CTLGRP) parameter, that have been processed by BRMS and meet the other selection criteria specified on the PRTRPTBRM command.

...

NOTE: This parameter is ignored when parameter Type (TYPE) is not *CTLGRPSTAT. 

Retention Information

The output from PRTRPTBRM TYPE(*CTLGRPSTAT) will include a retention section if a value other than *NONE is specified for the CTLGRP parameter.  The retention section will start on a new page with a heading of *RETENTION.  Each control group will have an entry with full and incremental retention information.

To have the retention section included by PRTRPTBRM, data area QTEMP/Q1ARPTRETN must exist.  Use the following command to create the data area:

...


The output from PRTRPTBRM TYPE(*CTLGRPSTAT) OUTPUT(*OUTFILE)  includes the following states:

BSSTAT

Save Status

Description

0

*ERROR

The backup failed.

1

*NOERR

The backup completed with no errors.

2

*QUAL

The backup completed but not all objects were saved.

3

*ACT

The backup is currently running and has not completed.

4

*CANCL

The backup was cancelled.


The output from PRTRPTBRM TYPE(*BKUSTAT) includes the following states:

...

  1. If using the option to synchronize BRMS saved history using Specific System Synchronization System Synchronization support for *SYSBAS, BRMS will not synchronize the backup control group information. In order to get the report for the control groups for these saves, the FROMSYS() parameter will need to be used.

  2. PRTRPTBRM report entries will change after BRMS maintenance is run.

    • When using PRTRPTBRM TYPE(*BKUSTAT) the following entries change:

      • Entries releated to expired volumes will be removed from the report.

    • When using PRTRPTBRM TYPE(*CTLGRPSTAT) the following entries change:

      • Entries with a Save Status of *NOERR or *QUAL are removed one year after the backup history expires, even if the media has been reused.

      • Entries with a Save Status of *ACT are changed to *ERROR if the job no longer exists.

      • Entries with a Save Status of *ERROR or *CANCL are removed after 30 days.

  3. BRMS calculates the GB/HR from the start to stop time of the control group and the approximate amount of data saved minus the size of the access paths.  For example, logical file access paths may be included in the save size even if they are not saved to the media.  This time can include:

    • Delay waiting for subsystems to end and TCP/IP.

    • Wait time for SWA

    • Wait time for locks

    • Possible delays in exits in control groups

    • Wait times for loading multiple cartridges

    • Running CL commands in exits

    • Other activity on the system at the time of the backup

  4. When multiple volumes are used in a control group, the QP1ABS report will list all volumes used by the control group, however it will only list information about the save for the first volume. All other volumes used in the save will have 0's for all values except the additional volume IDs. Similarly, when *NONE is specified for the control group, all volumes used will be listed but only the first volume will have data, the rest will have 0's for all the other values.

  5. The Missed Object count does not include objects not saved if the following occurs:

    • A library is locked and cannot be saved

    • When running incremental or cumulative saves, the only objects in a library that may be candidates to be saved are locked.

    • Does not include missed spooled files. Need to refer to the CPF3771 message in the backup joblog.

  6. The Save Size (MB) reported by BRMS uses 1000 per KB versus 1024 which could represent about a 10% difference.

...

*YES                                                               
Include TSM backups in the report.                             
                                                                       
*NO                                                                
Do not include TSM backups in the report.                                                            

New Expiration date parameter added in the following PTFs for releases 7.2 and later:
7.4 SI72867, 7.3 SI72866, 7.2 SI72865

Expiration date (EXPDATE)             

...