PM83787: VALUE OF DSHARE SHOULD BE USED TO CUSTOMIZE DSNTIJUZ

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • This APAR addresses problems in DSNTXAZP:
    (1) DSNTXAZP does not enforce level checking.  For example, you
        can run the DB2 10 DSNTXAZP module on DB2 9.1.  This can
        result in DSNTIDxx members that are not acceptable to the
        installation CLIST
    (2) If DSNTXAZP has the DSHARE parameter in the input member,
        it updates the value with the correct information from the
        running DB2 and puts the right value for DSHARE in the
        output member. If the CLIST is  invoked in UPDATE mode, the
        CLIST should use this value from DSHARE to customize
        DSNTIJUZ, but it is using the other parameter DATASHR.
    (3) DSNTXAZP blanks out all or part of the data in JOBx cards
        that begin with '/*'
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the DSNTXAZP tool in DB2 9 for  *
    *                 z/OS and DB2 10 for z/OS are affected by     *
    *                 this change.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: One or more of the following errors     *
    *                      occurs when the DB2 installation CLIST  *
    *                      is run with an input member that has    *
    *                      been refreshed by the DSNTXAZP tool:    *
    *                      (1) DB2 9 and DB2 10: In UPDATE mode,   *
    *                          when editing job DSNTIJUZ, the      *
    *                          CLIST unexpectedly sets the         *
    *                          DSN6GRP.DSHARE parameter to NO      *
    *                      (2) DB2 9 and DB2 10: In INSTALL,       *
    *                          MIGRATE, ENFM, or UPDATE mode, the  *
    *                          CLIST writes a blank or incomplete  *
    *                          job card when a job card line is    *
    *                          expected to begin with a slash      *
    *                          followed by an asterisk.            *
    *                      (3) DB2 10 only: In MIGRATE mode, one   *
    *                          or more of the following            *
    *                          installation fields contains blanks *
    *                          and must be updated in order to     *
    *                          continue to the next installation   *
    *                          panel:                              *
    *                            * Panel DSNTIPN:                  *
    *                              - AUDIT TRACE                   *
    *                              - TRACE AUTO START              *
    *                              - SMF STATISTICS                *
    *                              - MONITOR TRACE                 *
    *                            * Panel DSNTIPO:                  *
    *                              - WTO ROUTE CODES               *
    *                            * Panel DSNTIPP1:                 *
    *                              - SECURITY ADMIN 1              *
    *                              - SECURITY ADMIN 2              *
    *                      (4) DB2 10 only: In MIGRATE mode, when  *
    *                          migrating the second or subsequent  *
    *                          member of a data sharing group,     *
    *                          short message "Invalid length"      *
    *                          appears on panel DSNTIPP1 and the   *
    *                          cursor is placed in the SECURITY    *
    *                          ADMIN 1 field.  That field          *
    *                          contains SECADMN (or SECADMNULLNULL *
    *                          on expansion) and cannot be updated *
    *                          because it is locked.  The CLIST    *
    *                          cannot continue to the next panel.  *
    ****************************************************************
    * RECOMMENDATION: Apply the fixing PTF for this APAR.          *
    ****************************************************************
    DSNTXAZP is a program that can be used to refresh a DB2 CLIST
    input (DSNTIDxx) member with DB2's current subsystem parameter,
    DSNHDECP parameter, and buffer pool settings.
    
    Currently, one or more of the following errors can occur when
    you run the DB2 installation CLISTs with a DSNTIDxx input member
    that has been refreshed by the DSNTXAZP tool:
    
    (1) DB2 9 and DB2 10: In UPDATE mode, when editing job
        DSNTIJUZ for a member of a data sharing group, the CLIST
        unexpectedly sets the DSN6GRP.DSHARE parameter to NO.
    
        In UPDATE mode, the installation CLIST obtains the setting
        for DSN6GRP.DSHARE from DSNTIDxx entry DATASHR. Currently,
        a bug in DSNTXAZP unconditonally sets DATASHR to NO, so
        DSN6GRP.DSHARE is always assigned NO, even for a data
        sharing member.
    
    (2) DB2 9 and DB2 10: In INSTALL, MIGRATE, ENFM, or UPDATE
        mode, the CLIST writes a blank or incomplete job card when
        a job card line is expected to begin with a slash followed
        by an asterisk.
    
    (3) DB2 10 only: In MIGRATE mode, one or more of the
        installation panel fields noted in the PROBLEM DESCRIPTION
        section of this APAR contains blanks and must be updated in
        order to continue to the next installation panel.
    
        These problems occur when the following events take place:
        (a) A DB2 9 DSNTIDxx member is refreshed by executing the
            DB2 10 DSNTXAZP tool on DB2 9.
    
        (b) The DB2 10 installation CLIST is run in MIGRATE mode
            and the DB2 9 DSNTIDxx member that was refreshed in
            step (a) is specified as the migration input member, in
            the DATA SET(MEMBER) NAME field of panel DSNTIPA1.
    
        Running the DB2 10 DSNTXAZP tool on DB2 9 causes certain
        entries -- those corresponding to the fields noted in the
        PROBLEM DESCRIPTION section -- to be outputted in a format
        that the DB2 10 CLIST expects to find only in DB2 10
        DSNTIDxx members.  Because the DB2 10 CLIST necessarily
        interprets the migration input DSNTIDxx member in DB2 9
        format, fields having the DB2 10 format are ignored or
        otherwise mishandled.
    
    (4) DB2 10 only: In MIGRATE mode, when migrating the second or
        subsequent member of a data sharing group, the SECURITY
        ADMIN 1 field contains an unexpected value of SECADMN (or
        SECADMNULLNULL on expansion) but cannot be updated.  If the
        SEC ADMIN 1 TYPE field contains AUTH, then short message
        "Invalid length" appears on panel DSNTIPP1 for the SECURITY
        ADMIN 1 field.
    
        This is a specific case of problem (3).  Users can work
        around problem (3) by entering values in the blanked-out
        fields.  However, when migrating the second or subsequent
        member of a data sharing group, panel DSNTIPP1 locks the
        SECURITY ADMIN 1 field because the same setting is required
        for all members of the group.  When the DB2 9 DSNTIDxx
        migration input member has the DB2 10 format, the SECURITY
        ADMIN 1 field picks up a corrupted setting that cannot be
        corrected.
    

Problem conclusion

  • In response, this APAR modifies DSNTXAZP as follows:
    
    (1) The bug affecting the DATASHR setting in DSNTIDxx is
        corrected.  DATASHR will now be assigned DB2's current
        DSN6GRP.DSHARE setting.
    
    (2) The bug that blanks out or corrupts DSNTIDxx JOBx entries
        that begin with slash followed by an asterisk is corrected.
        Such JOBx entries will now be handled correctly.
    
    (3) A check is added to verify that the DSNTXAZP code version
        matches the version of DB2 where it is running.  If not,
        execution ends with return code 12 and message DSNT017I
        with error-text = THE DB2 VERSION AND THE VERSION OF
        DSNTXAZP ARE NOT THE SAME
    
        This check will prevent accidental mixing of DSNTIDxx
        formats.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83787

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-28

  • Closed date

    2013-04-10

  • Last modified date

    2013-05-03

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

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

    UK93311 UK93312

Modules/Macros

  •    DSN@XAZP DSNTXAZP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK93311

       UP13/04/27 P F304

  • R910 PSY UK93312

       UP13/04/27 P F304

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

910

Reference #:

PM83787

Modified date:

2013-05-03

Translate my page

Machine Translation

Content navigation