IBM Support

PH19160: ALLOWS COLLID/SCHEMA NAME AS INPUT WHEN PROVISIONING AN INSTANCE IN DOE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • DOE should allow users to provide collid/schema name
    as input in provision as optional path. When users provision a
    new
    instance, there are situations to use the existing objects(like
    packages) under existing collid/schema name instead of always
    generating
    of packages under their collid, instead of the collid of master
    copy,
    while they may have packages bound ahead under a pre-allocated
    collid,
    they would want DOE to take collid value input instead of
    dynamically
    generating another one, because Java stored procedures require
    some JDBC
    driver pkgs to be bound as well under that collid, besides the
    packages
    of the static SQLs in the stored procedures themselves, and
    users don't
    want to dynamically bind those JDBC driver packages manually
    each time
    after provisioning an instance in DOE. Furthermore, users may
    also want
    to limit the total number of collid for this case for different
    reasons.
    Sample DDL:
    CREATE PROCEDURE GETEMPD (IN WORKDEPT CHARACTER(4))
    EXTERNAL NAME 'GETEMPD:getEmpD.getEmpDResult'
    LANGUAGE JAVA
    PARAMETER STYLE JAVA
    COLLID DSNJDBC
    PROGRAM TYPE SUB
    DYNAMIC RESULT SETS 1
    WLM ENVIRONMENT WLMJAVA
    a new schema name or a new collid (of course, DOE doesn't
    generate a new
    collid today anyway). For example, when users provision an
    instance from
    application which contains Java stored procedures like below,
    the collid
    is one of keyword of the ddl, and users do want to use their own
    version
    

Local fix

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION: Fixed: Added support for providing      *
    *                      collid/schema name as input when        *
    *                      provisioning an instance.               *
    ****************************************************************
    .
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH19160

  • Reported component name

    DB2 DEVOPS EXPR

  • Reported component ID

    5698DEX00

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-14

  • Closed date

    2019-12-08

  • Last modified date

    2020-01-03

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

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

Modules/Macros

  • ADB2000  ADB27AC  ADB27ACR ADB28MC  ADB2CIX  ADB2CMP  ADB2GDP
    ADB2GEN  ADB2RE   ADB2ZPV  ADB5000  ADB7000  ADB9000  ADBCDCX
    ADBCEXX  ADBCVEZ  ADBRPTL  ADBTEP2  ADBTEPX  ADBUPGRD DOEALA
    DOEALLOC DOEDSCVR DOESAMP  DOESERVE DOEUI    DOEZFS   GOC2DTC
    GOCCCM
    

Fix information

  • Fixed component name

    DB2 DEVOPS EXPR

  • Fixed component ID

    5698DEX00

Applicable component levels

  • R110 PSY UI66862

       UP19/12/18 P F912

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2020