IBM Support

II13339: MIGRATION FROM JAVA 118 TO 131 SUFFERS PERFORMANCE DEGRADATION ON G4 HARWARE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • Customer was perfoming a system upgrade:
    OS/390 2.8 --> OS/390 2.10
     Java 1.1.8 --> Java 1.3.1 SERVICE REFRESH (SR13) ptf UQ62958
     WAS 1.2    --> WAS 3.5
     JDBC JDBC6612 Driver 2 --> the same but with ptfs applied for
                                WAS 3.5 support
     DB2 6.1 not changed.
    Hardware:
     9672-RA5 with 1 processor, generation 4 with 256 MB of real mem
    After the migration it was noticed that the CPU consumption
    had increased from 1.6% to 22.4% by jobs running USS scripts.
    These scripts use JDBC to connect to DB2.
    

Local fix

  • The ASKQ Q&A item was the first clue:
     RTA000167245 PRO (DATE/20011203) whose title is:
       What is the effect on Java servlet performance when moving
       from WAS 3.02 to WAS 3.5 on a G4 machine if floating point
       operations are used?
    
    Our customer has a Generation 4 machine without the HW feature:
      IEEE binary floating point support for advanced Domino and
           Java performance
    
    IBM recommends G5 hardware and above for use with IBM Java on
    z/OS SDK 130 and above.
    This will exploit the built in IEEE binary floating point
    support and avoid the costly software emulation which can
    increase CPU cycles and degrade system throughput.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • closing as cancelled
    

APAR Information

  • APAR number

    II13339

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2002-08-12

  • Closed date

    2012-05-23

  • Last modified date

    2012-05-23

  • 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
23 May 2012