PK85026: DRF INTERFACE ENHANCEMENTS

APAR status

• Closed as program error.

Error description

• This APAR will be used to fix various DRF/IB problems as well as
  enhance the interface
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IMS Database Recovery Facility  *
  *                 who invoke any of the Auxiliary Utilities    *
  *                 (Index Builder, DFSPREC0, Pointer Checker,   *
  *                 Image Copy) from a DRF job.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DRF interfaces to many of the       *
  *                      auxiliary utilities need to be enhanced *
  *                      in order to eliminate various problems  *
  *                      and to make these interfaces easier     *
  *                      to use.                                 *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  This APAR makes the following changes
  to the DRF Auxiliary Utility interface:
  
  1. Creates an ACEE in the IB/DFSPREC0
     address space to match the ACEE
     used to submit the DRF master job.
     This allows all RACF authority
     from the DRF MAS to be associated
     with the IB/DFSPREC0 address space,
     eliminating any special RACF rules
     for giving the address space
     authority.
  
  2. Skip calls to IB/DFSPREC0 for any
     FP DEDBs in the recovery list.
  
  3. Allow customer to specify any
     combination of the IB() keywords
     BLD_PRIMARY, BLD_SECONDARY, and
     HALDB for any databases in the
     recovery list and DRF will
     determine the database type and
     only call IB/DFSPREC0 as needed.
     The user no longer needs to tailor
     the IB() statements on each
     command to the type of database
     ADD() specified.
  
  4. Added new optional naming rules
     for the auxiliary utility address
     spaces which DRF spawns.  The
     ASPREF(), IBPREF(), and PRPREF()
     keywords currently allow a 4
     character prefix to be specified
     and the spawned jobname is
     pppp#### where pppp is the prefix
     and #### is a number from 0001
     through 0099, incremented for
     each new spawned job.  This method
     may cause duplicate jobs to be
     created if multiple DRF jobs are
     run in parallel.  This can lead to
     DBRC signon failures for IB and PC
     jobs.
  
     In order to prevent duplicate jobs,
     the ASPREF(), IBPREF() and PRPREF()
     keywords now allow a 2 character
     prefix to be specified.  When any
     of these keywords specify a 2
     character prefix, the spawned
     jobname is ppnnnn## where pp is
     the 2 character prefix, nnnn is
     the JES jobnumber associated with
     the DRF master job which spawned
     the job, and ## is a number from
     01-99, incremented with each new
     job.  This format prevents duplicate
     jobnames and eliminates DBRC signon
     failures.
  
     The new method for job naming is
     only used when ASPREF(), IBPREF(),
     or PRPREF() specify a 2 character
     prefix.  Each keyword is independent
     of the other keywords and some may
     specify 4 a character prefix while
     others specify a 2 character prefix.
  
     Whether 2 character or 4 character
     prefixes are specified, it is highly
     recommended that unique names be
     specified for each keyword.  Not
     doing so could lead to DBRC signon
     failures.
  
  5. A new PCPREF() keyword was added to
     be used instead of PCJOBNM() if
     desired.  PCPREF() and PCJOBNM() are
     mutually exclusive.  If PCJOBNM()
     is specified, then it is a 4-8
     character name which is used as the
     PC jobname which is spawned.  If
     PCPREF() is specified, it is a 4
     character prefix to be used to create
     the PC jobnane which will be ppppnnnn
     where pppp is the prefix specified and
     nnnn is the JES jobnumber associated
     with the DRF master job which spawned
     the job.
  

Problem conclusion

• This APAR enhances the existing DRF interface to many of the
  auxiliary utilities in order to make their use easier.
  

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:

  UK46737

Modules/Macros

• FRXEDRF  FRXEDRF0 FRXEPSS0 FRXEWSP  FRXLSTS0
  FRXMTRM1 FRXRVGB  FRXRWCE  FRXRWSP  FRXSDR20 FRXTAU00 FRXTPIB0
  FRXTSIB0 FRXVSTA0 FRXVSTA2 FRXVWSP
  

Fix information

• Fixed component name

  IMS DB RECOVERY

• Fixed component ID

  5655I4400

Applicable component levels

• R310 PSY UK46737

     UP09/05/21 P F905