PM33991: 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

  • Miscellaneous DB2 for z/OS installation fixes
    - V10: Correct the message text for SQLCODE -20497 by adding
           "OR EXPLICITLY".  The correct message text is:
             A STRING REPRESENTATION OF A DATETIME VALUE THAT
             CONTAINS A TIME ZONE CANNOT BE IMPLICITLY OR EXPLICITLY
             CAST TO A TARGET DEFINED AS DATETIME WITHOUT TIME ZONE
    - V8, V9, V10: Fix DSNTIJPM (V10) and DSNTIJPA (V8 and V9)
           REPORT4 not to report native SQL procedures as stored
           procedures that are defined to run in a DB2-managed
           stored procedures address space
    - V10: DSNTIJRT job step DSNTRIN ends with return code 12 due
           to SQLCODE -104 errors in CREATE TABLESPACE statements
           caused by invalid STOGROUP or buffer pool name
           specification.  This error occurs only when the options
           specified in the DB2OPT DD input have no leading blanks.
    - V10: DSNTIJRV job step DSNTRVFY ends with return code 4 and
           the message:
              DSNT018I DSNTRVFY - A WARNING WAS ENCOUNTERED
              DURING CALL TO ROUTINE, WARNING = DSNT541I WLM REFRESH
              REQUEST FAILED. RESOURCE PROFILE
              ssid.WLM_REFRESH.ssidWLMG IS UNDEFINED
           when validating the SYSPROC.WLM_REFRESH stored procedure
           on a DB2 data sharing system, because DSNTRVFY passes the
           subsystem ID to WLM_REFRESH rather than the group attach
           name.  In order to be consistent with DB2 documentation
           on use of WLM_REFRESH in data sharing versus non-data
           sharing, DSNTRVFY will be modified to pass the group
           attach name when run on data sharing and the subsystem ID
           when run on non-data sharing.
    - V10: DSNTIJMV currently creates set of WLM address space procs
           for each member of a data sharing group.  This can result
           redundant procs or overlays in data sharing installations
           that use the same proclib for all members.  Therefore,
           the installation CLIST will be modified so that DSNTIJMV
           creates the WLM address space procs only for the first
           member to be installed or migrated.
    - V8, V9, and V10: Job DSNTIJXZ program DSNTXAZP returns an
           incorrect value for OPTRCSIZ
    - V8 and V9: Job DSNTIJPA job step DSNTPMQ ends with return code
           8 and this message:
             I/O error occurred in "Write_source_dsn". Event: EXECIO
             DISKW REPORT10 rc= 1
    - V10: Job DSNTIJPM job step DSNTPMQ ends with return code 8 and
           this message:
             I/O error occurred in "Write_source_dsn". Event: EXECIO
             DISKW REPORT10 rc= 1
    V9 and V10: The catalog queries in member DSNTESP do not match
             those documented in the Monitoring and Tuning DB2
             Performance Guide for "Modeling your production system
             statistics in a test subsystem"
    V8 and V9: DSNTXAZP, the refresh tool for DB2 installation
             CLIST input (DSNTIDxx) members, does not provide
             the setting for the DSNLOGP.OUTBUFF parameter.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DB2 installation in DB2 UDB for *
    *                 z/OS Version 8, DB2 V9 for z/OS, and DB2 10  *
    *                 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) V8, V9, V10: Installation jobs      *
    *                          DSNTIJPM (V10) and DSNTIJPA (V8     *
    *                          and V9) can encounter these         *
    *                          errors:                             *
    *                          - REPORT4 incorrectly includes      *
    *                            native SQL procedures as          *
    *                            stored procedures that are        *
    *                            defined to run in a DB2-managed   *
    *                            stored procedures address space   *
    *                          - Job step DSNTPMQ ends with        *
    *                            return code 8 and this message    *
    *                            when processing REPORT10:         *
    *                              I/O error occurred in           *
    *                               "Write_source_dsn". Event:     *
    *                                EXECIO DISKW REPORT10 rc= 1   *
    *                      (2) V8, V9, V10: Job DSNTIJXZ, program  *
    *                          DSNTXAZP, outputs an incorrect      *
    *                          value for the DSNTIDxx.OPTRCSIZ     *
    *                          (DSN6SYSP.TRACTBL) entry            *
    *                      (3) V8, V9: Job DSNTIJXZ, program       *
    *                          DSNTXAZP, does not output an entry  *
    *                          for DSNTIDxx.LOGOUTPT               *
    *                          (DSN6LOGP.OUTBUFF)                  *
    *                      (4) V9: Job DSNTIJXZ, program           *
    *                          DSNTXAZP, outputs an incorrect      *
    *                          value, SEQUENTIAL, for              *
    *                          DSNTIDxx.SEQCACH when               *
    *                          DSN6SPRM.SEQCACH is set to SEQ      *
    *                      (5) V9, V10: The message text for       *
    *                          SQLCODE -440 is corrected           *
    *                      (6) V10: The message text for SQLCODE   *
    *                          -20497 is corrected                 *
    *                      (7) V9, V10: SQL queries in DSNTESP     *
    *                          do not match those documented in    *
    *                          the topic entitled "Modeling your   *
    *                          production system statistics in a   *
    *                          test subsystem" in the Monitoring   *
    *                          and Tuning DB2 Performance guide.   *
    *                      (8) V10: Installation job DSNTIJMV      *
    *                          generates WLM address space procs   *
    *                          for each member when a DB2 data     *
    *                          sharing group is installed or       *
    *                          migrated.  It should do so only     *
    *                          for the first member.               *
    *                      (9) V10: Installation job DSNTIJRT      *
    *                          job step DSNTRIN ends with return   *
    *                          code 12 due to SQLCODE -104         *
    *                          messages when the options           *
    *                          specified in the DB2OPT DD input    *
    *                          have no leading blanks.             *
    *                      (10) V10: Installation job DSNTIJRV     *
    *                          job step DSNTRVFY ends with return  *
    *                          code 4 and the message:             *
    *                            DSNT018I DSNTRVFY - A WARNING     *
    *                            WAS ENCOUNTERED DURING CALL TO    *
    *                            ROUTINE, WARNING = DSNT541I WLM   *
    *                            REFRESH REQUEST FAILED. RESOURCE  *
    *                            PROFILE                           *
    *                              ssid.WLM_REFRESH.ssidWLMG       *
    *                            IS UNDEFINED                      *
    *                          when validating stored procedure    *
    *                          SYSPROC.WLM_REFRESH on a DB2 data   *
    *                          sharing system                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This APAR concerns the following DB2 for z/OS installation
    issues:
    (1) Jobs DSNTIJPA (V8 and V9) and DSNTIJPM (V10)
        * REPORT4 can contain errors
        * REPORT10 processing can halt processing because of an
          output error.
    
        These identical jobs constitute the DB2 V10 premigration
        health check.
        * REPORT4 identifies stored procedures that are configured
          to run in the DB2-managed stored procedures address space,
          which was deprecated in V8 and eliminated in subsequent
          releases.   Currently, an error in the DB2 catalog query
          for REPORT4 causes it to misidentify native SQL procedures
          as stored procedures that run in the DB2 SPAS.
        * REPORT10 identifies occurrences of explain table
          DSN_PTASK_TABLE with column names that contain a hashmark
          character.  Support for this format of DSN_PTASK_TABLE
          was deprecated by APAR PK65772 and eliminated by APAR
          PK70423.  Currently, processing of REPORT10 can terminate
          with return code 8 and the message
            I/O error occurred in "Write_source_dsn". Event: EXECIO
            DISKW REPORT10 rc= 1
          when running on a DB2 in which content of SYSIBM.SYSTABLES
          column DBNAME, column TSNAME, or both contains trailing
          blanks.
    
    (2) Job DSNTIJXZ (program DSNTXAZP) outputs an incorrect value
        for the OPTRCSIZ entry of the DSNTIDxx member being
        refreshed (V8, V9, V10)
    
        DSNTIJXZ program DSNTXAZP can be used to refresh the
        content of a CLIST input (DSNTIDxx) member.  Currently,
        the value it outputs for the OPTRCSIZ entry of DSNTIDxx is
        1024 times the value of the DSN6SYSP.TRACTBL parameter;
        it should be 4096 times the DSN6SYSP.TRACTBL value.
    
    (3) Job DSNTIJXZ (program DSNTXAZP) does not output an entry
        for LOGOUTPT in the DSNTIDxx member being refreshed (V8
        and V9)
    
        The LOGOUTPT entry in the DSNTIDxx member corresponds to
        the DSN6LOGP.OUTBUFF parameter.  Currently, DSNTXAZP outputs
        an entry for LOGOUTPT in DSNTIDxx in V10 only.  It should
        also output it for V8 and V9.
    
    (4) Job DSNTIJXZ (program DSNTXAZP) outputs an incorrect value
        for the SEQCACH entry of the DSNTIDxx member being
        refreshed (V9)
    
        Currently, when the DSN6SPRM.SEQCACH parameter is set to
        SEQ, the value output for the SEQCACH entry of DSNTIDxx is
        SEQUENTIAL.
    
    (5) The SQL message text returned by GET DIAGNOSTICS and DSNTIAR
        for SQLCODE -440 has changed (V9, V10)
    
        The previous message text for -440 was
          NO routine-type BY THE NAME routine-name HAVING COMPATIBLE
          ARGUMENTS WAS FOUND IN THE CURRENT PATH
    
        The new message text for -440 is
          NO AUTHORIZED routine-type NAMED routine-name HAVING
          COMPATIBLE ARGUMENTS WAS FOUND
    
    (6) The SQL message text returned by GET DIAGNOSTICS and DSNTIAR
        for SQLCODE -20497 has changed (V10)
    
        The previous message text for -20497 was
          A STRING REPRESENTATION OF A DATETIME VALUE THAT CONTAINS
          A TIME ZONE CANNOT BE IMPLICITLY CAST TO A TARGET DEFINED
          AS DATETIME WITHOUT TIME ZONE
    
        The new message text for -20497 is
          A STRING REPRESENTATION OF A DATETIME VALUE THAT CONTAINS
          A TIME ZONE CANNOT BE IMPLICITLY OR EXPLICITLY CAST TO A
          TARGET DEFINED AS DATETIME WITHOUT TIME ZONE
    
    (7) SQL queries in sample member DSNTESP are downlevel (V9 and
        V10)
    
        DB2 performance-related SQL queries in sample member DSNTESP
        are downlevel from what is published in the topic entitled
        "Modeling your production system statistics in a test
        subsystem" in the Monitoring and Tuning DB2 Performance
        guide.
        * The query for obtaining statistics from SYSIBM.SYSTABLES
          does not select the NPAGESF column
        * The query for obtaining statistics from SYSIBM.SYSTABSTATS
          is missing
        * The query for obtaining statistics from SYSIBM.SYSCOLDIST
          is also missing
    
    (8) Job DSNTIJMV creates address space procs for DB2-supplied
        WLM environments for all members of the data sharing group
        (V10)
    
        Beginning in V10, DB2 supplies a number of WLM environments,
        referred to as the 'core' WLM environment, that are suitable
        for initial setup and running of the DB2-supplied stored
        procedures and user-defined funnctions (UDFs).  These WLM
        environments are:
          DSNWLM_DEBUGGER, DSNWLM_DSNACICS, DSNWLM_GENERAL,
          DSNWLM_JAVA, DSNWLM_MQSERIES, DSNWLM_NUMTCB1,
          DSNWLM_PGM_CONTROL, DSNWLM_REXX, DSNWLM_UTILS,
          DSNWLM_WEBSERVICES, and DSNWLM_XML
        See the DB2 Installation and Migration Guide for information
        about the core WLM environments.
    
        Currently, for each member of a DB2 data sharing group being
        installed or migrated, DSNTIJMV creates a set of address
        space procs for the DB2-supplied WLM environments.  Each
        address space proc is named to reflect the subsystem ID of
        that member.  Typically, the extra sets of address space
        procs are unused.
    
    (9) Job DSNTIJRT, program DSNTRIN, ends with return code 12 when
        statements under the DB2OPT DD have no leading blanks (V10).
    
        The DB2OPT DD of DSNTIJRT (program DSNTRIN) accepts certain
        configuration options, such as buffer pools and a
        storage group, for creating databases that support DB2-
        supplied stored procedures and UDFs.  See the DSNTIJRT
        job prolog for more information.  Currently, DSNTIJRT
        will end with return code 12 and error messages if the
        options specified under the DB2OPT DD do not have leading
        blanks.
    
    (10) Job DSNTIJRV, program DSNTRVFY, outputs warning message
        DSNT018I during validation of the SYSPROC.WLM_REFRESH
        stored procedure on a DB2 data sharing group (V10)
    
        The SYSPROC.WLM_REFRESH stored procedure refreshes a WLM
        environment.  To execute the CALL statement, the SQL
        authorization ID of the process must have READ access or
        higher to the z/OS Security Server System Authorization
        Facility (SAF) resource profile
          ssid.WLM_REFRESH.wlm-environment-name
        in resource class DSNR, where
        - 'wlm-environment-name' is the name of the environment to
           be refreshed
        - 'ssid' specifies the subsystem ID of the DB2 subsystem
           with which the WLM environment is associated.  By
           default, this is the subsystem ID of the subsystem on
           which WLM_REFRESH runs but in a data sharing environment,
           it is the group attach name for the data sharing group
           in which WLM_REFRESH runs.
    
        Currently, when validating SYSPROC.WLM_REFRESH in a DB2 data
        sharing environment, DSNTRVFY always calls it using the
        subsystem ID even if a group attach name is available.  This
        is counter to documented use and results in the DSNT018I
        message when the first-level qualifier of the SAF profile
        for SYSPROC.WLM_REFRESH specifies the group attach name.
    

Problem conclusion

  • In response, the following changes are made:
    (1) Jobs DSNTIJPA (V8 and V9) and DSNTIJPM (V10)
        * REPORT4 can contain errors
        * REPORT10 processing can halt processing because of an
          output error.
    
        In V8 and V9 (DSNTIJPA) and V10 (DSNTIJPM), the query
        for REPORT4 is modified to exclude native SQL procedures.
        The query for REPORT10 is modified to strip trailing
        blanks from columns selected from DB2 catalog tables.
    
    (2) Job DSNTIJXZ (program DSNTXAZP) outputs an incorrect value
        for the OPTRCSIZ entry of the DSNTIDxx member being
        refreshed (V8, V9, V10)
    
        In V8, V9, and V10, DSNTXAZP is modified to set the value of
        the OPTRCSIZ entry of DSNTIDxx to be 4096 times the setting
        of the DSN6SYSP.TRACTBL parameter (instead of 1024 times
        that setting).
    
    (3) Job DSNTIJXZ (program DSNTXAZP) does not output an entry
        for LOGOUTPT in the DSNTIDxx member being refreshed (V8
        and V9)
    
        In V8 and V9, DSNTXAZP is modified to output the entry for
        LOGOUTPT in the DSNTIDxx member being refreshed.
        DSNTIDxx.LOGOUTPT corresponds to the DSN6LOGP.OUTBUFF
        parameter.
    
    (4) Job DSNTIJXZ (program DSNTXAZP) outputs an incorrect value
        for the SEQCACH entry of the DSNTIDxx member being
        refreshed (V9)
    
        In V9, DSNTXAZP is modified to set the value of the SEQCACH
        entry of DSNTIDxx to be SEQ rather than SEQUENTIAL when the
        DSN6SPRM.SEQCACH parameter is set to SEQ.
    
    (5) The SQL message text returned by GET DIAGNOSTICS and DSNTIAR
        for SQLCODE -440 has changed (V9, V10)
    
        In V9 and V10, the new message text for -440 is:
          NO AUTHORIZED routine-type NAMED routine-name HAVING
          COMPATIBLE ARGUMENTS WAS FOUND
    
    (6) The SQL message text returned by GET DIAGNOSTICS and DSNTIAR
        for SQLCODE -20497 has changed (V10)
    
        In V10, the new message text for -20497 is
          A STRING REPRESENTATION OF A DATETIME VALUE THAT CONTAINS
          A TIME ZONE CANNOT BE IMPLICITLY OR EXPLICITLY CAST TO A
          TARGET DEFINED AS DATETIME WITHOUT TIME ZONE
    
    (7) SQL queries in sample member DSNTESP are downlevel (V9 and
        V10)
    
        In V9 and V10, DSNTESP is updated as follows:
        * The query for obtaining statistics from SYSIBM.SYSTABLES
          now selects the NPAGESF column
        * The query for obtaining statistics from SYSIBM.SYSTABSTATS
          is now included
        * The query for obtaining statistics from SYSIBM.SYSCOLDIST
          is now included
        For information about these queries, see the topic entitled
        "Modeling your production system statistics in a test
        subsystem" in the Monitoring and Tuning DB2 Performance
        Guide.
    
    (8) Job DSNTIJMV creates address space procs for DB2-supplied
        WLM environments for all members of the data sharing group
        (V10)
    
        In V10, the installation CLIST is modified to create address
        space procs for the DB2-supplied WLM environments only for
        the first member when a data sharing group is being
        installed or migrated.  Related objects for the DB2-supplied
        Java WLM environment, the JAVAWLM file, the environment
        variable file, and the sample JVM startup options file, are
        also created only for the first member.  In addition, if a
        group attach name is available, the address space procs and
        related files are named using the group attach name rather
        than the subsystem name.  For data sharing installations and
        migrations, the DB2SSN parm is set to null rather than to a
        subsystem name.
    
        Note: These changes apply only to the address space procs
        for the DB2-supplied WLM environments.  The address space
        proc for the default WLM environment, DSNWLM, continues to
        be created for each member of group to be installed or
        migrated, and continues to be named as specified in the
        WLM PROC NAME field on installation panel DSNTIPX.
    
    (9) Job DSNTIJRT, program DSNTRIN, ends with return code 12 when
        statements under the DB2OPT DD have no leading blanks (V10).
    
        In V10, program DSNTRIN is modified so that it will not
        terminate with errors when statements specified in the
        DB2OPT DD do not have leading blanks.
    
    (10) Job DSNTIJRV, program DSNTRVFY, outputs warning message
        DSNT018I during validation of the SYSPROC.WLM_REFRESH
        stored procedure on a DB2 data sharing group (V10)
    
        In V10, program DSNTRVFY is modified to use the group attach
        name, when available, when validating SYSPROC.WLM_REFRESH.
        Therefore, in DB2 data sharing environments where a group
        attach name is defined, DSNTRVFY will expect WLM_REFRESH to
        find a SAF resource profile in this format:
            group-attach-name.WLM_REFRESH.group-attach-nameWLMG
        In cases where this resource profile is not available,
        DSNTRVFY will return message DSNT018I when validating
        SYSPROC.WLM_REFRESH.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM33991

  • 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

    2011-03-02

  • Closed date

    2011-07-13

  • Last modified date

    2011-09-01

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

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

    UK69735 UK69736 UK69737

Modules/Macros

  •    DSN@RIN  DSN@RVFY DSN@XAZP DSNTESP  DSNTIAM
    DSNTIJPA DSNTIJPM DSNTINS1 DSNTRIN  DSNTRVFH DSNTRVFM DSNTRVFY
    DSNTXAZH DSNTXAZP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK69735

       UP11/08/03 P F108

  • R810 PSY UK69736

       UP11/08/03 P F108

  • R910 PSY UK69737

       UP11/08/03 P F108

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 #:

PM33991

Modified date:

2011-09-01

Translate my page

Machine Translation

Content navigation