IBM Support

II11505: SQL0332N AFTER MIGRATING TO DB2 FOR OS/390 V5.1

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • 5740XYR00 HDB5510 HDB6610
    As an example, consider the following configuration:
      Client           Primary Server        Secondary Server
      CCSID 437        DB2 OS/390            CCSID 933
                       CCSID 37
    
    The client application Connects to the Primary server using
    DRDA protocols and then executes SQL that references a table at
    yet another server (secondary server).  The secondary server
    returns CCSID 933 data back to the primary server.
    If the primary server is DB2 for OS/390 V4.1 or earlier,
    then the DB2 primary server first will translate the CCSID 933
    data to CCSID 37 before forwarding the data to the client
    which will then have to translate the CCSID 37 data to
    CCSID 437.
    If the primary server is DB2 for OS/390 V5.1, behavior will
    change which could lead to sqlcode -332.  DB2 for OS/390 V5.1
    includes a performance enhancement that causes the primary
    server to no longer translate the CCSID 933 data to CCSID 37.
    Rather, the CCSID 933 data is forwarded directly to the client.
    That is, instead of translating the CCSID 933 data to CCSID
    37, and sending it (at which time, the client would have to
    translate again from CCSID 37 to CCSID 437), DB2 now simply
    sends the client the CCSID 933 data and leaves to to the client
    to do the proper translation.  The client will have to do
    translation anyway so DB2 for OS/390 V5 felt it could improve
    its performance by skipping its translation.
    As a result, the client system will now have to translate from
    CCSID 933 to 437 which was not a requirement until the
    DB2 for OS/390 primary server was migrated to V5.1. If no such
    translation ability exists at the client, SQLCODE -332 will be
    returned to the client application.
    
    What this means is that when a client (any client regardless of
    its local CCSID) connects to a DB2 for OS/390 V5 server
    (primary server), the client will now have to contain all
    translation mechanisms for any target data whether
    the data exists directly on the target system (primary server)
    or if it was obtained by yet another target system (secondary
    server), which is the case here.
    ******************************************
    Additional Symptoms and keywords:
      CCSID Code Page translation SYSTRINGS
      DB2 MVS OS390 V510 V51 V5 510 51 5 5.1.0 5.1
      SQL0332N SQLCODE332 SQLCODE0332 -332
    

Local fix

  • Correct client to contain all CCSID translation mechanisms
    for all target data.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  •  Informational APAR
    

APAR Information

  • APAR number

    II11505

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1998-10-30

  • Closed date

    1998-10-30

  • Last modified date

    1998-10-30

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]

Document Information

Modified date:
10 September 2020