PM17928: DATABASE THAT IS STOPPED AT THE START OF ORF IS NOT RESTARTED

APAR status

• Closed as new function.

Error description

• This APAR will address the following issues/enhancements:
  - ORF needs a method to start a database that was stopped when
    ORF started.
  - Currently there is no method to limit the number of WTORs
    issued to stop BMPs.
  - ORF needs a way to surpress dump intercepting software so
    problems can be analyzed properly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: User's of IMS Online Reorg Facility V1.2     *
  ****************************************************************
  * PROBLEM DESCRIPTION: ORF needs a method to start a database  *
  *                      that was stopped when ORF was started.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This APAR is adding the following enhancements:
  1.  DBSTART=Y|N
   When a database is stopped prior to ORF, it will remain stopped
   at the end of ORF.  This can be overridden by:
    Specifying DBSTART=Y|N in HRFSETOP and/or
    specifying DBSTART(Y|N) in the HRFSYSIN control cards.
   The specification in HRFSETOP will serve as a default, which
  maybe overidden by the specification in the HRFSYSIN control
  cards.
  "N" will not start the database if the database was stopped
  prior to the ORF job; This is the default in HRFSETOP.
  "Y" will start the database in takeover, even if the database
  is found prior to the ORF job.
  2.  BMPRETRY=nnn
  When a WTOR is issued to stop BMPs, it will be repeated
  every 10 seconds.
  There is currently no limit on those repeats prior to this
  option.  BMPRETRY can now be specified in HRFSETOP (it is not
  allowed on HRFSYSIN).
  It is a numerical value that specifies how many retries
  are accepted (nnn * 10 seconds).
  When that number is exceeded, ORF will terminate with an
  error message (HRF01570E Waiting for BMPs has expired) and
  the original database will be made available again in the
  same state before ORF started.
  3. When dump intercepting software is installed, ORF now
  suppresses those by dynamically allocating the appropriate DD
  statement to allow the dump to be produced. This is currently
  in affect for ABENDAID and DUMPMASTER.
  

Problem conclusion

Temporary fix

Comments

• The has been modified to add the above enhancements.
  

APAR Information

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

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

  UK58756

Modules/Macros

• HRFOAPLY HRFOLEV0 HRFOREO0 HRFOREO2 HRFOREO3
  HRFOREO8 HRFSET   HRFYCCDF HRFYSTRT
  

Fix information

• Fixed component name

  IMS ONLINE REOR

• Fixed component ID

  5655H9700

Applicable component levels

• R120 PSY UK58756

     UP10/08/04 P F008