IBM Support

PQ68311: CHANGE.DB NOAUTH INTEGRATED IN IPR DRIVER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Add new function to, as an option, turn on PROHIBIT
    AUTHORIZATION flag or READ-ONLY flag automatically before
    IPR starts reorganization.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IPR Driver of IMS Parallel      *
    *                 Reorganization for z/OS Version 2 Release 1  *
    *                 (FMID=H25N210).                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR provides a new function to,   *
    *                      as an option, turn on PROHIBIT          *
    *                      AUTHORIZATION flag or READ-ONLY flag    *
    *                      automatically before IPR starts         *
    *                      reorganization.                         *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    This APAR provides a new function to, as an option, turn on
    PROHIBIT AUTHORIZATION flag or READ-ONLY flag automatically
    before IPR starts reorganization.
    

Problem conclusion

Temporary fix

Comments

  • IPR Driver is modified so that it will behave as follows:
    If DBRCAUTHCMD=YES is specified in HPSIN, Reorganization Manager
    issues the CHANGE.DB READON or the CHANGE.DB NOAUTH command
    automatically at the beginning of the reorganization and before
    the name swapping process. The following reports adds in
    Reorganization Manager.
    1. DBRC Authorization Processing for Reorganization Report
    2. DBRC Authorization Processing for Name Swapping Report
    
    ========================
    = DOCUMENTATION CHANGE =
    ========================
    IMS Parallel Reorganization for z/OS Version 2 Release 1 User's
    Guide (Document Number: SC27-1180-01) should be changed as
    follows.
    
    ================================================================
    Chapter 2. IMS Parallel Reorganization Driver
     2.1 Overview
      2.1.2 Reorganization Manager
          :
       - Dynamic allocation of database data sets
       - Allowing DBD change during reorganization
       - Automated IMS command processing during reorganization
    |  - Automated DBRC authorization processing during
    |    reorganization
       - Automated data set name swapping
       - Automated DBRC notification processing after the name
         swapping
          :
    *
       2.1.2.3 Automated IMS Command Processing
          :
    |   If you specify AUTHFAIL=WTOR, WTO messages are issued when
        the above commands are necessary to be issued and
        Reorganization Manager waits for operator responses. For
        details, see "AUTHFAIL Control Statement" in topic 2.7.6.1.
    *
    |  2.1.2.3a Automated DBRC Authorization Processing
    |
    |   If you specify DBRCAUTHCMD=YES, Reorganization Manager does
    |   the following automatically:
    |
    |   - At the beginning of the reorganization, Reorganization
    |     Manager issues either a CHANGE.DB READON command or a
    |     CHANGE.DB NOAUTH command depending on the DBSHARE option.
    |     The CHANGE.DB READON command change "READ ONLY" flag to
    |     the database in RECON and the CHANGE.DB NOAUTH command
    |     change "PROHIBIT AUTHORIZATION" flag to the database in
    |     RECON. Further authorization for the database is
    |     prohibited.
    |
    |   - During data set name swapping, Reorganization Manager
    |     automatically issues a CHANGE.DB NOAUTH command.
    |
    |   These commands are issued through DSPURX00 for DBRC command.
    |   See "DBRCAUTHCMD Control Statement" in topic 2.7.6.1a and
    |   "DBSHARE Control Statement" in topic 2.7.6.2.
    |
    |   If you specify AUTHFAIL=WTOR, WTO messages are issued when
    |   the above commands are necessary to be issued and
    |   Reorganization Manager waits for operator responses. For
    |   details, see "AUTHFAIL Control Statement" in topic 2.7.6.1.
    |
    |   Note: Even if IPR Driver issue DBRC command and
    |   successfully, if the database is used any other IMS system,
    |   authorization can not allow for the database. If you are
    |   using database by online, it is recommend that you authorize
    |   DBRC by IMS command.
    *
     2.5 Restrictions
          :
     +-------------------------------------------------------------+
     | Table 1. DBRC Command Authorization for IPR Driver          |
     +------------+---------------+---------------+----------------+
     |DBRC Command|Process of IPR |Status of the  |User's Response |
     |            |Driver When the|Database after |                |
     |            |User Has No    |Error          |                |
     |            |Authority      |               |                |
     +------------+---------------+---------------+----------------+
          :
     +------------+---------------+---------------+----------------+
     |NOTIFY.UIC  |...            |...            |...             |
     |(If NAMESWAP|               |               |                |
     |=YES)       |               |               |                |
     +------------+---------------+---------------+----------------+
    ||CHANGE.DB   |HPSG0316E and  |When issued    |When issued     |
    ||(If NAMESWAP|HPSG0011E(one  |HPSG0011E(2),  |HPSG0011E(2),   |
    || =YES or    |of 2, 2a, 2b)  |Name swapping  |Issue the       |
    || DBRCAUTHCMD|are issued, and|is completed,  |CHANGE.DB       |
    || =YES)      |the process    |but DBRC       |command         |
    ||            |ends. For      |notification is|according to the|
    ||            |details, check |not completed. |status of the   |
    ||            |the report(4,4a|               |database. (*5)  |
    ||            |,4b).          |               |                |
    ||            |               |               |                |
    ||            |               |When issued    |When issued     |
    ||            |               |HPSG0011E(2a), |HPSG0011E(2a),  |
    ||            |               |reorganization |Change the      |
    ||            |               |is completed,  |authority so    |
    ||            |               |but name       |that the user   |
    ||            |               |swapping is not|can issue the   |
    ||            |               |completed.     |CHANGE.DB       |
    ||            |               |               |command. Or,    |
    ||            |               |               |issue the       |
    ||            |               |               |CHANGE.DB       |
    ||            |               |               |command by a    |
    ||            |               |               |user who has    |
    ||            |               |               |the authority.  |
    ||            |               |               |Or, do manually |
    ||            |               |               |name swapping.  |
    ||            |               |               |                |
    ||            |               |When issued    |When issued     |
    ||            |               |HPSG0011E(2b), |HPSG0011E(2b),  |
    ||            |               |The status of  |Change the      |
    ||            |               |the database is|authority so    |
    ||            |               |the same as    |that the user   |
    ||            |               |before running |can issue the   |
    ||            |               |IPR Driver Step|CHANGE.DB       |
    ||            |               |(not changed). |command. Or,    |
    ||            |               |               |issue the       |
    ||            |               |               |CHANGE.DB       |
    ||            |               |               |command by a    |
    ||            |               |               |user who has    |
    ||            |               |               |the authority.  |
    ||            |               |               |                |
    |+------------+---------------+---------------+----------------+
     | Notes:                                                      |
     | 1.  HPSG0011E REORGANIZATION ABORTED FOR DATABASE dbdname   |
     |                (RC=08, RSN=40010001)                        |
     | 2.  HPSG0011E REORGANIZATION ABORTED FOR DATABASE dbdname   |
     |                (RC=08, RSN=40010004)                        |
    || 2a. HPSG0011E REORGANIZATION ABORTED FOR DATABASE dbdname   |
    ||                (RC=08, RSN=40100002)                        |
    || 2b. HPSG0011E REORGANIZATION ABORTED FOR DATABASE dbdname   |
    ||                (RC=08, RSN=40400002)                        |
     | 3.  For details, check the DATA BASE RECOVERY CONTROL report|
     |     in HPSOUT2.                                             |
     | 4.  For details, check the DBRC NOTIFICATION PROCESSING     |
     |     report in HPSOUT2.                                      |
    || 4a. For details, check the DBRC AUTHORIZATION PROCESSING FOR|
    ||     REORGANIZATION report in HPSOUT2.                       |
    || 4b. For details, check the DBRC AUTHORIZATION PROCESSING FOR|
    ||     NAME SWAPPING report in HPSOUT2.                        |
     | 5.  Refer to "Automated DBRC Notification Processing" in    |
     |     topic 2.1.2.5, and "Manual DBRC Notification Processing"|
     |     in topic 2.9.3.                                         |
     +-------------------------------------------------------------+
    *
     2.7 Control Statements
      2.7.6 Description of Control Statements for Reorganization
            Manager
    |  2.7.6.1a DBRCAUTHCMD Control Statement
    |
    |   DBRCAUTHCMD specifies whether or not Reorganization Manager
    |   issues the CHANGE.DB READON or the CHANGE.DB NOAUTH command
    |   automatically at the beginning of the reorganization and
    |   before the name swapping of data sets.
    |
    |   +----------------------------------------------------------+
    |   |                                                          |
    |   |                    _NO__                                 |
    |   | >>__DBRCAUTHCMD=__|_YES_|_____________________________>< |
    |   |                                                          |
    |   +----------------------------------------------------------+
    |
    |   If you specify DBRCAUTHCMD=YES, Reorganization Manager
    |   issues one of the following DBRC commands at the beginning
    |   of the reorganization:
    |
    |   - CHANGE.DB DBD(name) READON: when you specify DBSHARE=YES
    |   - CHANGE.DB DBD(name) NOAUTH: when you specify DBSHARE=NO
    |
    |   If the database to be reorganized is a HALDB partition, the
    |   command is issued for the partition. If it is an entire
    |   HALDB, the command is issued for each partition.
    |
    |   The CHANGE.DB READON command changes the "READ ONLY" flag of
    |   the database in RECON, and the database can be authorized
    |   only for read processing. The CHANGE.DB NOAUTH command
    |   changes the "PROHIBIT AUTHORIZATION" flag of the database in
    |   RECON, and authorization processing is prohibited for the
    |   database.
    |
    |   Before the name swapping of data sets, IPR Driver must have
    |   exclusive access to the database. If you specify
    |   DBRCAUTHCMD=YES, Reorganization Manager automatically issues
    |   a CHANGE.DB NOAUTH command just before the data set name
    |   swapping.
    |
    |   If IMSCMD=NO, DBRCAUTHCMD=YES and AUTHFAIL=ABORT are
    |   specified and Reorganization Manager fails to get the
    |   required authorization from DBRC, the job is aborted. If
    |   IMSCMD=NO, DBRCAUTHCMD=YES and AUTHFAIL=WTOR are specified,
    |   the AUTHFAIL=WTOR option becomes effective after
    |   Reorganization Manager fails to get the required
    |   authorization from DBRC.
    |
    |   When you specify DBRCAUTHCMD=YES, DBRC must be active and
    |   the database must be registered to DBRC.
    |
    |   If you specify DBRCAUTHCMD=NO, it is recommended that you
    |   specify AUTHFAIL=WTOR.  If you specify DBRCAUTHCMD=NO and
    |   you have not issued CHANGE.DB READON or CHANGE.DB NOAUTH
    |   commands for the database, the AUTHFAIL=WTOR option lets
    |   Reorganization Manager issue a WTOR message HPSG0336A that
    |   states what type of authorization is required for the
    |   database.
    |
    |   If you specify IMSCMD=YES, the DBRCAUTHCMD control statement
    |   is ignored and has no effect.
    |
    |   Note: Even if IPR Driver issue DBRC command and
    |   successfully, if the database is used any other IMS system,
    |   authorization can not allow for the database. If you are
    |   using database by online, it is recommend that you authorize
    |   DBRC by IMS command.
    *
       2.7.6.9 IMSCMD Control Statement
          :
        - /DBD DATABASE name GLOBAL NOFEOV: when you specify
          DBSHARE=YES
        - /DBR DATABASE name GLOBAL NOFEOV: when you specify
    |     DBSHARE=NO
          :
    *
       2.7.6.12 NEWDBD Control Statement
          :
        Considerations for Post-Reorganization Processing:  If DBRC
        is active and you specify NAMESWAP=YES, and specify
    |   IMSCMD=YES or DBRCAUTHCMD=YES, Reorganization Manager turns
        the PROHIBIT AUTHORIZATION flag on before starting the name
        swapping, for the primary database, primary index, and
        secondary indexes if any is defined.
          :
    *
    ================================================================
    E.0 Appendix E. Messages and Codes
     E.3 Messages
      E.3.4 HPSG Messages
          :
      HPSG0229E DBRC MUST BE ACTIVE WHEN statement IS SPECIFIED
    | Explanation:  DBRC must be active when one or both of
    | NAMESWAP=YES and, IMSCMD=YES or DBRCAUTHCMD=YES are specified.
      ...
    *
    | HPSG0316I  CHANGE.DB DBD(dbdname ) parameter
    | Explanation:  The CHANGE.DB command has been successfully
    | completed for the database or HALDB partition dbdname.
    | parameter is one of the following:
    |   READON
    |   NOAUTH
    |   AUTH READOFF
    | System Action:  IPR Driver continues processing.
    | Programmer Response:  None
    *
    | HPSG0316E CHANGE.DB DBD(dbdname) parameter --- ERROR (CC=xx)
      Explanation:  An error occurred when IPR Driver issued the
      CHANGE.DB command for the database or a HALDB partition
      dbdname. The condition code returned from DSPURX00 is xx.
    | parameter     Report of Reference
    | READON        DBRC AUTHORIZATION PROCESSING FOR REORGANIZATION
    | NOAUTH        DBRC AUTHORIZATION PROCESSING FOR REORGANIZATION
    |               or
    |               DBRC AUTHORIZATION PROCESSING FOR NAME SWAPPING
    | AUTH READOFF  DBRC NOTIFICATION PROCESSING
      System Action:  IPR Driver ends with a return code of 8.
      Programmer Response:  Refer to the messages issued from the
      DBRC utility, and identify the cause of the error. The
      messages are printed in the HPSOUT2 data set.
    

APAR Information

  • APAR number

    PQ68311

  • Reported component name

    IMS PARALLEL RE

  • Reported component ID

    5655F7400

  • Reported release

    210

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2002-11-15

  • Closed date

    2002-12-17

  • Last modified date

    2003-01-04

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

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

    UQ72726

Modules/Macros

  • HPSGCM00 HPSGCM20 HPSGGDIB HPSGGIOB HPSGGIO0
    HPSGGRMB HPSGGRM0 HPSGRP10 HPSGRP20 HPSGRS30 HPSGSTMT
    

Publications Referenced
SC27118001    

Fix information

  • Fixed component name

    IMS PARALLEL RE

  • Fixed component ID

    5655F7400

Applicable component levels

  • R210 PSY UQ72726

       UP02/12/20 P F212

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":"SSVL5Q","label":"IMS Database Reorganization Expert for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
06 January 2023