IBM Support

PH17441: DBRC STAGING DIRECTORY COMMAND SUPPORT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New function for DBRC Staging Directory command support
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IMS 15 DBRC users registering databases that have not    *
    * been imported to the active catalog directory.               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Databases cannot be registered in RECON until after the      *
    * database definitions have been imported from the staging     *
    * directory into the active directory.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    When a new database is registered with DBRC in an IMS
    managed-ACB environment before it is imported into the active
    catalog directory, DBRC only looks at the active directory.
    Since the database is in the staging directory, DBRC is unable
    to locate the database and returns RC=12.
    
       INIT.DBDS  DBD(DBSX1252) DDN(DDSX1252) -
                   DSN(RSTEST.RGECAT01.DBSX1252) -
    
                   GENMAX(3) -
    
                   CATALOG(DFSCD000)
    
    DSP1273E  THE REQUEST TO CATALOG DFSCD000 DID NOT COMPLETE
    SUCCESSFULLY
    DSP1276A  DATABASE DBSX1252 IS NOT DEFINED IN CATALOG DFSCD000
    
    DSP0209I  PROCESSING TERMINATED WITH CONDITION CODE = 12
    
    When a new data set group is added or a new index is added, DBRC
    should open the staging directory for new definitions.
    
    DFSURGL0 supports DFSACBPD DD to request loading DMB from the
    staging.
    

Problem conclusion

  • The following DBRC commands have been changed to support the
    staging catalog directory.  New mutually exclusive keywords
    ACTIVE and STAGING are added.
    
    This line item adds new keywords STAGING|ACTIVE to the following
    DBRC RECON commands so that Managed ACB users can use either the
    staging directory or the active directory for the databases
    specified by them:
       - INIT.DBDS
       - CHANGE.DBDS
       - NOTIFY.REORG
       - INIT.DB
       - INIT.PART
       - CHANGE.PART
    
      ACTIVE | STAGING
        Mutually exclusive, optional keywords that you use to
    specify whether the active or staging catalog directory is to be
    used.        These keywords cannot be explicitly specified if
    DBDLIB is to be used. If the directory is being used, the active
    directory is     read by default.
    
        ACTIVE
          Specifies that the command uses the specified active IMS
    catalog directory.
        STAGING
          Specifies that the command uses the specified staging IMS
    catalog directory.
    
    
    New message DSP1279E is added indicating whether the ACTIVE or
    STAGING directory is in use when a Catalog API error is
    encountered.  The API function as well as its return code and
    reason code is displayed.
    
      DSP1279E  func CATALOG API ERROR ON THE status DIRECTORY name
                RC=retcode RSN=rsncode
    
      Explanation:
      An error was encountered when accessing the catalog directory
    identified by name.
    
      status indicates whether the ACTIVE or STAGING directory was
    being used by this operation.
    
      func identifies the function being processed by the IMS
    Catalog API.
    
      retcode and rsncode indicate the return and reason codes from
    the IMS Catalog API.
    
      System action:
      Processing is terminated.
    
      Programmer Response:
      Prior error message(s) may be issued to help with diagnosing
    the problem.  Also, refer to the return and reason code sections
    of    the identified IMS Catalog API (DFS3CATQ) function for
    more information on the error.  Contact IMS support if more help
    is   required.
    
      Problem determination: 2,3,8, and the listings of the RECON
    data sets.
    
      Modules:  DSPUCQ00
    
    
    The explanation of the message DSP0141I is changed.
    
      DSP0141I  parameter PARAMETER SHOULD NOT BE SPECIFIED
    
      The following new situation can also cause this error:
    
        - The STAGING or ACTIVE keyword was specified, and the job
    is using DBDLIB instead of the IMS directory.
    
    
    The following modules are changed:
    
    DSPKWTBL - DBRC Command Keyword Table
    --------
    Add ACTIVE and STAGING keywords to the supported commands
    
    DSPUSTB2 - DBRC Message Text
    --------
    Add new message DSP1279E.
    
    DSPUCQ00 - DBRC Catalog API Services
    --------
    The Catalog is opened at the beginning of DBRC command
    processing and closed at the end.  If a subsequent command
    switches to the other directory (active or staging), the
    currently open directory is closed and the directory specified
    is opened.  It is best for performance if the input stream of
    commands works for one of the directories to avoid the
    close/open overhead.
    
    The command modules below are changed to use the desired catalog
    directory, ACTIVE or STAGING.  DSP0141I will be issued if ACTIVE
    or STAGING are explicitly specified when DBDLIB is being used
    instead of the directory.
    
    DSPURMPT - CHANGE.PART command processor
    --------
    
    DSPURM60 - CHANGE.DBDS command processor
    --------
    
    DSPURSPT -INIT.PART command processor
    --------
    
    DSPURS00 - INIT.DBDS command processor
    --------
    
    DSPURS10 - INIT.DB command processor
    --------
    
    DSPURT00 - NOTIFY.REORG command processor
    --------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH17441

  • Reported component name

    IMS V15

  • Reported component ID

    5635A0600

  • Reported release

    500

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-27

  • Closed date

    2020-06-02

  • Last modified date

    2020-07-06

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

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

    UI69829

Modules/Macros

  • DSPKWTBL DSPUCQ00 DSPURM60 DSPURSPT DSPUSTB2 DSPURS00 DSPURS10
    DSPURT00 DSPURMPT
    

Publications Referenced
SC276782GC276794GC276790  

Fix information

  • Fixed component name

    IMS V15

  • Fixed component ID

    5635A0600

Applicable component levels

  • R500 PSY UI69829

       UP20/06/04 P F006

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"15","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 December 2023