IBM Support

JR30369: JCC TYPE 4 CONNECTION HANGS WHEN GOING TO A DB2 CONNECT TO A ISERIES (V6R1)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The problem is best seen by looking at the trace file
    fmtAsClient.fmt. At connect time, the JCC client sent the ACCRDB
    request with TYPDEFNAM = QTDSQLASC. It received the ACCRDBRM
    from the gateway with TYPDEFNAM = QTDSQLX86. Later, at trace
    record 3447, gateway got the PRPSQLSTT + OPNQRY request, sent it
    to iSeries, go the reply at 3627 and sent the reply back to JCC
    at 4052, but it also inserted TYPDEFNAM = QTDSQL400 before
    QRYDSC. This is normal if the gateway is a Windows machine.
    
    The problem here is that JCC remembered the last TYPDEFNAM of
    QTDSQL400 and applied it to the next reply for the subsequent
    CNTQRY request. That next reply was only an SQLCARD, but the
    TYPDEFNAM = QTDSQL400 was only in effect for the life of the
    reply in which it was flown. The separate reply containing only
    SQLCARD (see trace point 4418 where gateway sends it to JCC)
    didn't have any TYPDEFNAM, so the TYPDEFNAM to be applied is the
    one negotiated at connect time, i.e. the one flown by the
    gateway to JCC in ACCRDBRM (TYPDEFNAM = QTDSQLX86). The sqlcode
    in the SQLCARD at 4418 is byte-reversed , which is correct for
    TYPDEFNAM = QTDSQLX86 (little endian). JCC needs to convert this
    sqlcode to big endian because it connected using TYPDEFNAM =
    QTDSQLASC.
    

Local fix

  • Avoid using DB2 Connect server. Connect directly to DB2 for i
    server.
    

Problem summary

  • JCC type 4 connection will hang if you go from DB2 Connect to a
    I-Series <V6R1> Will be first fixed in v9.5 fp3
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR30369

  • Reported component name

    DB2 CEE WINDOWS

  • Reported component ID

    5765F3001

  • Reported release

    950

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-08-28

  • Closed date

    2009-04-16

  • Last modified date

    2009-04-16

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

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

    JR30427

Fix information

Applicable component levels

  • R950 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950"}]

Document Information

Modified date:
07 October 2021