PM92730: MISCELLANEOUS DB2 FOR Z/OS INSTALLATION FIXES

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • (1) DB2 11: The DBM1 address space proc created by installation
    job DSNTIJMV currently includes the SDSNLOD2 target library
        in the STEPLIB concatenation. This is incorrect since DB2
        itself does does not reference modules in that library.
    (2) DB2 10: The following error is seen when running the
        installation CLIST in ENFM mode to complete migration from
        DB2 8:
          DSNT489I CLIST EDITING 'prefix.NEW.SDSNSAMP(DSNTESC)
            SAMPLE DATA
          IKJ52504I LINE NUMBER 37 NOT FOUND
    (3) DB2 11: In UPDATE mode, option 31 of the selection menu
        on panel DSNTIPB presents panel DSNTIP61 (DB2 Utilities
        parameters panel 2) instead of DSNTIP62 (DB2 Utilities
        parameters panel 3)
    (4) DB2 10, 11: Remarks in prolog of job DSNTIJNH refer to the
        ENFM job as DSNTIJNE but the correct name is DSNTIJEN
    (5) DB2 11: DSNTINSV does not check fields on install panel
        DSNTIPRL for SYSPROC.ADMIN_COMMAND_MVS
    (6) DB2 9, 10, 11: DSNTEJ67 needs to note that it must run
        at the site where DSNTEJ65 created DSN8.DSN8ES2
    (7) DB2 9, 10, 11: DB2 installation CLIST member DSNTINST
        halts with these messages
          IF GE = & THEN
          IKJ56545I THIS STATEMENT HAS AN EXPRESSION WITH OPERATORS
                    OUT OF SEQUENCE
        when the RLFSUFF entry in the DSNTIDxx input member is set
        to a value that happens to be a CLIST logical operator, such
        as GE, GT, LT, LT, EQ, NE, etc.
    (8) DB2 11: In DSNTIJCB, change the BSDS data data set
        allocation from from KILOBYTES(9000 240) to MEGABYTES(15 1)
    .
    KEYWORD:  DB2MIGV11/K
    .
    

Local fix

  • (1) Edit your DB2 11 DBM1 address space proc and remove the
        SDSNLOD2 library from the STEPLIB concatenation.
    (2) Edit prefix.SDSNCLST(DSNTINS3) and change this line
          DELETE 37
        to
         DELETE * 37
    (3) Edit prefix.SDSNSPFP(DSNTIPB) and change this line
          31, 'DSNTIP61'
        to 1, 'DSNTIP62'
          31, 'DSNTIP62'
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DB2 installation in DB2 9 for   *
    *                 z/OS, DB2 10 for z/OS, and DB2 11 for z/OS   *
    *                 are affected by this change.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Customers using the DB2 for z/OS        *
    *                      installation process can encounter one  *
    *                      or more of the following issues:        *
    *                      (1) DB2 9, 10, 11: After display of     *
    *                          panel DSNTIPA1, the installation    *
    *                          CLIST halts with these messages:    *
    *                            IF GE = & THEN                    *
    *                            IKJ56545I THIS STATEMENT HAS AN   *
    *                                      EXPRESSION WITH         *
    *                                      OPERATORS OUT OF        *
    *                                      SEQUENCE                *
    *                          when the RLFSUFF entry in the       *
    *                          DSNTIDxx input member is set to a   *
    *                          value that happens to be a CLIST    *
    *                          logical operator, such as GE, GT,   *
    *                          LE, LT, EQ, NE, etc.                *
    *                      (2) DB2 9, 10, 11: Job DSNTEJ67 ends    *
    *                          with return code 8 in job step      *
    *                          PH067S04.  These messages appear    *
    *                          in the SYSTSPRT DD output:          *
    *                            *SQLPLSRC* Error obtaining        *
    *                              Source, SQLPL procedure was     *
    *                              not found                       *
    *                            *SQLPLSRC* RC=6                   *
    *                            DSNTEJ67 Cannot extract SQL       *
    *                              procedure source                *
    *                      (3) DB2 10, 11: Remarks in prolog of    *
    *                          job DSNTIJNH refer to the enabling  *
    *                          new-function mode (ENFM) job as     *
    *                          DSNTIJNE but the correct name is    *
    *                          DSNTIJEN                            *
    *                      (4) DB2 10: The installation CLIST      *
    *                          outputs the message                 *
    *                            IKJ52504I LINE NUMBER 37 NOT      *
    *                              FOUND                           *
    *                          during ENFM edit mode of part       *
    *                          DSNTESC for completing migration    *
    *                          from DB2 8                          *
    *                      (5) DB2 11: The DBM1 address space      *
    *                          proc created by installation job    *
    *                          DSNTIJMV includes the SDSNLOD2      *
    *                          target library in the STEPLIB       *
    *                          concatenation.                      *
    *                      (6) DB2 11: The installation CLIST      *
    *                          UPDATE mode selection panel,        *
    *                          DSNTIPB, presents panel DSNTIP61    *
    *                          (DB2 Utilities parameters panel 2)  *
    *                          instead of DSNTIP62 (DB2 Utilities  *
    *                          parameters panel 3)                 *
    *                      (7) DB2 11: The installation CLIST does *
    *                          not validate fields on install      *
    *                          panel DSNTIPRL for stored procedure *
    *                          SYSPROC.ADMIN_COMMAND_MVS           *
    *                      (8) DB2 11: Job DSNTIJCB defines the    *
    *                          DATA segment of the VSAM data sets  *
    *                          for the BSDSes with a size of       *
    *                          KILOBYTES(9000 240) instead of      *
    *                          MEGABYTES(15 1)                     *
    *                      (9) DB2 10, 11: The create statement    *
    *                          the SYSPROC.ADMIN_INFO_SMS stored   *
    *                          procedure in sample member DSNTESR  *
    *                          fails with SQLCODE -104 due to      *
    *                          invalid symbol, "%".                *
    *                      (10) DB2 11: Job DSNTIJNF does not      *
    *                          warn that running it can cause      *
    *                          DB2 to rebuild the Shared           *
    *                          Communications Area (SCA)           *
    ****************************************************************
    * RECOMMENDATION: Apply the fixing PTF for this APAR.          *
    ****************************************************************
    This APAR addresses the following DB2 for z/OS installation
    issues:
    
    (1) DB2 9, 10, 11: The installation CLIST halts when the RLFSUFF
        setting is a CLIST logical operator:
    
        When the CLIST reads a DSNTIDxx member to obtain initial
        configuration settings it uses the CLIST &SYSNSUB function
        to check for an ampersand character (&) in the first byte of
        the setting of each entry. This is necessary to avoid errors
        caused by unexpected symbolic substitution.  Currently, if
        the string passed for inspection is by coincidence a CLIST
        logical operator such as GE, GT, LE, LT, EQ, NE, etc., the
        result of the &SYSNSUB call is interpreted as an operator
        rather than data.  This causes the CLIST to halt with the
        messages noted in the Problem Description section of this
        APAR.
    
    (2) DB2 9, 10, 11: Job DSNTEJ67 ends with return code 8 in job
        step PH067S04 because the SQL procedure source cannot be
        located:
    
        DSNTEJ67 is a DB2 sample job that shows a way to convert an
        external SQL procedure to a native SQL procedure.  By way of
        example, it converts the DSN8.DSN8ES2 sample external SQL
        procedure prepared by job DSNTEJ65 into a native SQL
        procedure.  The DSNTEJ67 prolog lists running DSNTEJ65 as a
        dependency.  However, DSNTEJ65 can be configured to create
        DSN8.DSN8ES2 on either the local DB2 or a remote DB2 whereas
        DSNTEJ67 operates only on the local DB2.  If DSN8.DSN8ES2 is
        not present on the local DB2, DSNTEJ67 ends in job step
        PH067S04 with the symptoms noted in the Problem Description
        section of this APAR.
    
    (3) DB2 10, 11: The DSNTIJNH prolog refers to the ENFM job as
        DSNTIJNE rather than DSNTIJEN:
    
        DSNTIJNH is a DB2 installation job that can be used to halt
        enabling-new-function mode (ENFM) processing by job
        DSNTIJEN.  Currently, the prolog of DSNTIJNH uses the wrong
        name for DSNTIJEN.
    
    (4) DB2 10: The installation CLIST reports that a line number
        cannot be found during ENFM editing of DSNTESC:
    
        DSNTESC contains DDL for creating sample DB2 explain tables.
        and additional SQL statements that show how to migrate
        tables in the previous-release format to tables in the new-
        release format.  Currently, when the CLIST is run in ENFM
        mode for completion of migration from DB2 8 only, the CLIST
        halts because of a syntax error in a DELETE statement.
    
    (5) DB2 11: The DBM1 address space proc created by DSNTIJMV
        allocates prefix.SDSNLOD2 in the STEPLIB concatenation:
    
        DSNTIJMV creates the JCL procedures for DB2 address space
        startup, including DBM1.  Currently, the STEPLIB DD
        concatenation includes the prefix.SDSNLOD2 library.
        This is unnecessary because that address space does not
        reference any modules in SDSNLOD2.
    
    (6) DB2 11: The installation CLIST UPDATE mode selection menu
        panel presents the wrong panel for option 31.
    
        In UPDATE mode, the selection menu on panel DSNTIPB lists
        option 31 for DB2 Utilities parameters panel 3 (DSNTIP62).
        However, because of a syntax error in DSNTIPB, option 31
        presents DB2 Utilities parameters panel 2 (DSNTIP61).
    
    (7) DB2 11: The installation CLIST does not validate fields on
        install panel DSNTIPRL for SYSPROC.ADMIN_COMMAND_MVS:
    
        Installation panels for DB2-supplied stored procedures and
        user-defined functions are supposed to check the syntax of
        field entries for each routine's WLM environment name,
        access list, and package owner.  Currently, this check is
        not performed for SYSPROC.ADMIN_COMMAND_MVS.
    
    (8) DB2 11: Job DSNTIJCB defines the DATA segment of the BSDS
        data sets with the wrong size:
    
        DSNTIJCB is a DB2 installation job that can be used to
        convert the BSDSes to a new format introduced in DB2 11
        new-function mode.  Existing BSDSes are not converted in
        place but converted into new data sets defined by DSNTIJCB.
        Currently, the AMS statements for defining the new BSDSes
        specify a size of KILOBYTES(9000 240) for the DATA segment.
        The size should be MEGABYTES(15 1).
    
    (9) DB2 10, 11: The create statement for SYSPROC.ADMIN_INFO_SMS
        in DSNTESR fails with SQLCODE -104:
    
        Sample member DSNTESR illustrates the basic SQL and bind
        statements that can be generated by program DSNTRIN when
        you run installation job DSNTIJRT to install and configure
        the DB2-supplied routines.  Currently, the sample create
        statement in DSNTESR for the SYSPROC.ADMIN_INFO_SMS stored
        procedure contains an invalid name, '%s', in the WLM
        ENVIRONMENT clause.  If you attempt to process this create
        statement outside of DSNTIJRT/DSNTRIN, it will fail with
        SQLCODE -104.  Note: It is recommended to use DSNTIJRT and
        DSNTRIN rather than DSNTESR to install and configure your
        DB2-supplied routines.
    
    (10) DB2 11: Job DSNTIJNF does not warn that running it can
        cause DB2 to rebuild the SCA:
    
        Installation job DSNTIJNF can be used to activate new-
        function mode (NFM) on an NFM-enabled DB2 subsystem or
        data sharing group.  In DB2 11 data sharing, the first time
        you run DSNTIJNF, DB2 will rebuild the SCA after converting
        the SCA structure to accommodate 10-byte RBA and LRSN
        values.  Also, before running DSNTIJNF, you need to disable
        any duplexing of SCA structures (you can re-enable
        duplexing after the job completes).  These considerations
        need to be noted in the DSNTIJNF job prolog.
    

Problem conclusion

  • In response, this APAR makes the following changes:
    
    (1) DB2 9, 10, 11: The DB2 installation CLIST halts when the
        RLFSUFF setting is a CLIST logical operator:
    
        The installation CLIST is modified to treat the RLFSUFF
        setting as data only.
    
    (2) DB2 9, 10, 11: Job DSNTEJ67 ends with return code 8 in job
        step PH067S04 because the SQL procedure source cannot be
        located:
    
        The job prolog now advises that DSNTEJ67 must be run on the
        same DB2 where DSNTEJ65 created the DSN8.DSN8ES2 sample SQL
        procedure.
    
    (3) DB2 10, 11: The DSNTIJNH prolog refers to the ENFM job as
        DSNTIJNE rather than DSNTIJEN:
    
        The job prolog now refers to DSNTIJEN.
    
    (4) DB2 10: The installation CLIST reports that a line number
        cannot be found during ENFM editing of DSNTESC:
    
        The CLIST now edits the part correctly.
    
    (5) DB2 11: The DBM1 address space proc created by DSNTIJMV
        allocates prefix.SDSNLOD2 in the STEPLIB concatenation:
    
        DSNTIJMV has been modified so that the DBM1 proc STEPLIB
        no longer allocates prefix.SDSNLOD2.
    
    (6) DB2 11: The installation CLIST UPDATE mode selection menu
        panel presents the wrong panel for option 31.
    
        UPDATE option 31 now presents the correct panel, DSNTIP62.
    
    (7) DB2 11: The installation CLIST does not validate fields on
        install panel DSNTIPRL for SYSPROC.ADMIN_COMMAND_MVS:
    
        DSNTINSV now validates the WLM ENV NAME, GRANT EXECUTE, and
        PACKAGE OWNER fields for SYSPROC.ADMIN_COMMAND_MVS.
    
    (8) DB2 11: Job DSNTIJCB defines the DATA segment of the BSDS
        data sets with the wrong size:
    
        DSNTIJCB now defines the BSDS data sets with a size of
        MEGABYTES(15 1) for the DATA segment.
    
    (9) DB2 10, 11: The create statement for SYSPROC.ADMIN_INFO_SMS
        in DSNTESR fails with SQLCODE -104:
    
        In DSNTESR, the sample create statement stored procedure
        SYSPROC.ADMIN_INFO_SMS is corrected to specify WLM
        ENVIRONMENT DSNWLM_GENERAL.
    
    (10) DB2 11: Job DSNTIJNF does not warn that running it can
        cause DB2 to rebuild the SCA:
    
        Notes are added to the DSNTIJNF prolog to warn data
        sharing users that the first run of the job will cause
        DB2 to rebuild the SCA and that any duplexing of the
        SCA should be disabled before running DSNTIJNF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM92730

  • 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-07-11

  • Closed date

    2013-10-03

  • Last modified date

    2013-11-04

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

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

    UK98195 UK98196 UK98197

Modules/Macros

  • DSNTEJ67 DSNTESR  DSNTIJCB DSNTIJMV DSNTIJNF DSNTIJNH DSNTINST
    DSNTINSV DSNTINS1 DSNTINS3 DSNTIPB
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK98195

       UP13/10/20 P F310

  • RB10 PSY UK98196

       UP13/10/18 P F310

  • R910 PSY UK98197

       UP13/10/20 P F310

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

Document information


More support for:

DB2 for z/OS

Software version:

910

Reference #:

PM92730

Modified date:

2013-11-04

Translate my page

Machine Translation

Content navigation