PH42721: BACKUP PROGRESS REPORTING: LOCK MANAGEMENT UPDATES

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New function - Backup job DUMP tasks can now report progress
  toward completion via a new message BKRWPU9632I.
            This message documents progress as number of files,
            data blocks, or cylinders.
  
            This function is disabled by default.
  
            Customers may choose to enable this function by
            configuring progress reporting parameters in
            BKRSYSTM CONFIG. Examples are provided in a new
            version of BKRSYSTM CONFSAMP shipped as part of
            this update.
  
            Refer to new content in "IBM Backup and Restore
            Manager for z/VM - Administration Guide" for
            details of configuring in-job progress reporting
            and variations of new message BKRWPU9632I.
  
  Messages: One new message, BKRWPU9632I, may be displayed
            in backup job logs when this function is enabled.
  
            Examples:
  
            BKRWPU9632I <owner> <vdev> hh:mn:ss mm/dd/yy ...
            ... CKD track <current> of maximum <maximum>
            ... EDF file <current> of maximum <maximum>
            ... 4K block <current> of maximum <maximum>
            ... FBA block <current> of maximum <maximum>
  
  
  
  New function - Job template "EOJ" statement syntax
  
             Syntax for the job template "EOJ" (End-Of-Job)
             statement has been enhanced. Prior to this
             change, any parameters for the EOJ statement
             were ignored.
  
             With this update, EOJ supports one option:
  
               - SUMMARY -- Default; when EOJ is processed,
                 a job activity summary report is displayed.
  
               - NOSUMMARY -- Use the NOSUMMARY parameter to
                 suppress display of the end-of-job summary
                 report.
  
             Note that this change only affects behavior
             around processing of the EOJ statement. A final
             end-of-job summary report will continue to be
             displayed upon full termination of a backup or
             restore job.
  
  
  Enhancement - More efficient SFS lock management during
            backup catalog updates.
  
            This change improves efficiency of SFS lock
            management during insertion of new backup
            catalog entries. Heavily loaded / performance-
            constrained systems may derive improved
            throughput during catalog entry creation due
            to avoidance of some serialization conflicts.
  
  
  
  Enhancement - Circumvention of a bug in CMS "TAPE"
            command parameter parsing.
  
            This change circumvents a bug in CMS "TAPE"
            command parameter parsing which occurs only
            when SET LANG UCENG is in effect. If the
            UCENG repository is active, "TAPE" parsing
            to avoidance of some serialization conflicts.
  
  
  
  Enhancement - Circumvention of a bug in CMS "TAPE"
            command parameter parsing.
  
            This change circumvents a bug in CMS "TAPE"
            command parameter parsing which occurs only
            when SET LANG UCENG is in effect. If the
            UCENG repository is active, "TAPE" parsing
            incorrectly rejects four-digit virtual tape
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of Backup & Restore Mgr 1.3.0      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Progress reporting; Catalog lock mgmt   *
  ****************************************************************
  New function - Backup job DUMP tasks can now report progress
            toward completion via a new message BKRWPU9632I.
            This message documents progress as number of files,
            data blocks, or cylinders.
  
            This function is disabled by default.
  
            Customers may choose to enable this function by
            configuring progress reporting parameters in
            BKRSYSTM CONFIG. Examples are provided in a new
            version of BKRSYSTM CONFSAMP shipped as part of
            this update.
  
            Refer to new content in "IBM Backup and Restore
            Manager for z/VM - Administration Guide" for
            details of configuring in-job progress reporting
            and variations of new message BKRWPU9632I.
  
  Messages: One new message, BKRWPU9632I, may be displayed
            in backup job logs when this function is enabled.
  
            Examples:
  
            BKRWPU9632I <owner> <vdev> hh:mn:ss mm/dd/yy ...
            ... CKD track <current> of maximum <maximum>
            ... EDF file <current> of maximum <maximum>
            ... 4K block <current> of maximum <maximum>
            ... FBA block <current> of maximum <maximum>
  
  
  
  New function - Job template "EOJ" statement syntax
  
             Syntax for the job template "EOJ" (End-Of-Job)
             statement has been enhanced. Prior to this
             change, any parameters for the EOJ statement
             were ignored.
  
             With this update, EOJ supports one option:
  
               - SUMMARY -- Default; when EOJ is processed,
                 a job activity summary report is displayed.
  
               - NOSUMMARY -- Use the NOSUMMARY parameter to
                 suppress display of the end-of-job summary
                 report.
  
             Note that this change only affects behavior
             around processing of the EOJ statement. A final
             end-of-job summary report will continue to be
             displayed upon full termination of a backup or
             restore job.
  
  
  
  Enhancement - More efficient SFS lock management during
            backup catalog updates.
  
            This change improves efficiency of SFS lock
            management during insertion of new backup
            catalog entries. Heavily loaded / performance-
            constrained systems may derive improved
            throughput during catalog entry creation due
            to avoidance of some serialization conflicts.
  
  
  
  Enhancement - Circumvention of a bug in CMS "TAPE"
            command parameter parsing.
  
            This change circumvents a bug in CMS "TAPE"
            command parameter parsing which occurs only
            when SET LANG UCENG is in effect. If the
            UCENG repository is active, "TAPE" parsing
            incorrectly rejects four-digit virtual tape
            device addresses with message DMSPCL394E and
            then terminates with return code 24.
  
            This error does not occur if TAPE is invoked
            from an EXEC while "Address COMMAND" is in
            effect. Additional information will be made
            available once an APAR has been created.
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI78527

Modules/Macros

• BAKSRVR  BKRBFSTL BKRJOBEX BKRSYSTM BUILDCAT CATSRVR  DUMPCKD
  DUMPEDF  DUMPFBA  DUMPSFS  EUMDREOV EUMDRMNT EUMDRUMT SAMPDDR
  SAMPDR   SAMPFULL SAMPINCR SAMPLNX  SFSBFS   SMPLNXOM WRKSRVR
  ZVM71L2
  

Fix information

• Fixed component name

  BACKUP RESTORE

• Fixed component ID

  5697J0600

Applicable component levels

• R130 PSY UI78527

     UP21/12/20 P 2112

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.