IBM Support

LI72637: SQL0100W, NO JAR INSTALLED WHEN CALL SQLJ.INSTALL_JAR() REMOTELY FROM V8 CLIENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If sysadm or non-sysadm  ID called sqlj.install_jar() remotely
    from the v8 client or locally with non-sysadm ID, then it fails
    with SQL0100W and jar is not being installed.
    

Local fix

  • Run sqlj.install_jar() locally with the sysadm ID.
    

Problem summary

  • Users affected: All developing JDBC stored procedures
    Problem summary: SQL0100W AND NO JAR INSTALLED WHEN CALL
    SQLJ.INSTALL_JAR() REMOTELY FROM V8 CLIENT
    Problem details: The same
    

Problem conclusion

  • First fixed in v9.1FP5, s080512
    

Temporary fix

  • Run sqlj.install_jar() locally on the server with sysadmin
    userID
    

Comments

APAR Information

  • APAR number

    LI72637

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-02

  • Closed date

    2008-08-29

  • Last modified date

    2008-08-29

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

    LI72636

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

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 August 2008