IBM Support

JR25457: INCLUDE A JCC PROPERTY CONNECTNODE TO SPECIFY WHICH NODE TO CONNECT TO ON THE SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We need to include a JCC property connectNode to specify which
    node to connect to on the server.
    
    This property is useful when the JCc application needs to
    connetc to a particular node on he database server. For example,
    the Workbench Center is a utility that would benefit fro this
    addition. There is a restriction when building stored
    procedures: to build a stored procedure you must be conencted to
    the catalog database partition. If the catalog database
    partition for the database IS NOT the logical port number 1, and
    you attempt to create the procedure form Workbench Center, it
    will fail as Workbench Center connects by default (using JCC
    Driver) to the partition on logical port number 1. If the
    catalo database partition is not on logical port 1,
    creating the procedure from Workbench Center will fail, unless
    there is a way to tell Workbench Center to connect to the
    catalog database partition that is not in logical port 1. There
    is no such functionality in Workbench Center as it uses JCC to
    make the connection and JCc does not have that functionality of
    specifying a particular node to connect to.
    
    In v8, with the Development Cneter, this was possible as we used
    the Type 2 Application Driver which reads the db2cli.ini file
    and in this file we could specify CONNECTNODE cli parameter.
    

Local fix

Problem summary

  • Users Affected: All
    Problem Description:
    We need to include a JCC property connectNode to specify which
    node to connect to on the server.
    
    This property is useful when the JCc application needs to
    connetc to a particular node on he database server. For example,
    the Workbench Center is a utility that would benefit fro this
    addition. There is a restriction when building stored
    procedures: to build a stored procedure you must be conencted to
    the catalog database partition. If the catalog database
    partition for the database IS NOT the logical port number 1, and
    you attempt to create the procedure form Workbench Center, it
    will fail as Workbench Center connects by default (using JCC
    Driver) to the partition on logical port number 1. If the
    catalo database partition is not on logical port 1,
    creating the procedure from Workbench Center will fail, unless
    there is a way to tell Workbench Center to connect to the
    catalog database partition that is not in logical port 1. There
    is no such functionality in Workbench Center as it uses JCC to
    make the connection and JCc does not have that functionality of
    specifying a particular node to connect to.
    
    In v8, with the Development Cneter, this was possible as we used
    the Type 2 Application Driver which reads the db2cli.ini file
    and in this file we could specify CONNECTNODE cli parameter.
    
    Problem Conclusion:
    We need to include a JCC property connectNode to specify which
    node to connect to on the server.
    

Problem conclusion

  • 'First fixed in DB2 UDB Version 8, FixPak 16'
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR25457

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-12-06

  • Closed date

    2008-02-27

  • Last modified date

    2008-02-27

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

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

    JR26156

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R810 PSY

       UP

  • R820 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 February 2008