IBM Support

PH17649: DB2 & ADABAS DEFAULT DATE CONVERSION WHEN SELECTED USING SQLENINE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In DB2 the Date column can have content of
    01.01.0001 (dd.mm.yyyy) ;
    If DVM studio directly accesses DB2 the correct value is
    returned.
    When DVM map is used, the date is converted to 01.01.1900
    Example DVM studio direct:
    DBTY=DB2
    SQLEnine
    SELECT TEMPID, INTDATE, STARTTIME, ENDTIME, MANAGER, DISP,
    LASTNAME, FIRSTNAME
     FROM DBA9_Q_INTERVIEW where tempid = 500
    returns INTDATE as '1900-01-01'
    
    Example: DVM map:
    SELECT AA_FIELD, D1_FIELD, T1_FIELD
    FROM ADA104_F067_NC
    incorrectly returns null date & timestamp as 1997-12-27
    this should be 0000-00-00
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL USERS                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 &                                   *
    *                      ADABAS default Date                     *
    *                      conversion when selected                *
    *                      using SQLEngine                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    DB2 & ADABAS default Date conversion when
    selected using SQLEngine
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH17649

  • Reported component name

    DATA VIRT MGR Z

  • Reported component ID

    5698DVM00

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-02

  • Closed date

    2020-02-06

  • Last modified date

    2020-03-02

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

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

Modules/Macros

  • AVZCDSAL AVZCDSOP AVZCMTCL AVZCS1HD AVZCSQOP AVZCTVOP AVZICSFX
    AVZIMPDS AVZMCLUP AVZMDTBL AVZO319D AVZO319N AVZO31AD AVZO31AN
    AVZO31BD AVZO31BN AVZO31CD AVZO31CN AVZO31DD AVZO31DN AVZO649D
    AVZO649N AVZO64AD AVZO64AN AVZO64BD AVZO64BN AVZO64CD AVZO64CN
    AVZO64DD AVZO64DN AVZOACDA AVZOBRSQ AVZOBRTV AVZODF9D AVZODF9N
    AVZODFAD AVZODFAN AVZODFBD AVZODFBN AVZODFCD AVZODFCN AVZODFDD
    AVZODFDN AVZODT9N AVZODTAN AVZODTBN AVZODTCN AVZODTDN AVZOICSF
    AVZOINAS AVZOIO31 AVZOIOMG AVZOKY9D AVZOKY9N AVZOKYAD AVZOKYAN
    AVZOKYBD AVZOKYBN AVZOKYCD AVZOKYCN AVZOKYDD AVZOKYDN AVZOLI9D
    AVZOLI9N AVZOLIAD AVZOLIAN AVZOLIBD AVZOLIBN AVZOLICD AVZOLICN
    AVZOLIDD AVZOLIDN AVZOPMS  AVZOPPA  AVZORXST AVZOTBEV AVZOVSSE
    AVZOVSUP AVZPB    AVZSBMIG AVZSEFCK AVZSQ29D AVZSQ29N AVZSQ2AD
    AVZSQ2AN AVZSQ2BD AVZSQ2BN AVZSQ2CD AVZSQ2CN AVZSQ2DD AVZSQ2DN
    AVZSQL9D AVZSQL9N AVZSQLAD AVZSQLAN AVZSQLBD AVZSQLBN AVZSQLCD
    AVZSQLCN AVZSQLDD AVZSQLDN AVZWSCLP AVZWSMFL
    

Fix information

  • Fixed component name

    DATA VIRT MGR Z

  • Fixed component ID

    5698DVM00

Applicable component levels

  • R110 PSY UI67730

       UP20/02/08 P F002

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:
27 March 2020