IV05507: INSTALL PROBLEM WITH HJVA601 AND HJVB601

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error Message:
    
    Problem can be exhibted in two different symptoms:
    
    Install log messages for Symptom 1:
    ----------------------------------
    
     J6.0.1/JDK_INSTALL_OK
     pax command completed successfully.
     rm AJVG1601
     rm AJVG1601 command completed successfully
     rm AJVG2601
     rm AJVG2601 command completed successfully
     :
     SHELL SCRIPT AJVGSCR OUTPUT FOR HFS AJVG2601
    SEQ
    NUM 000007
     :
     SHELL SCRIPT AJVGSCR OUTPUT FOR HFS AJVG2601
    SEQ
    NUM 000009
     Starting script processing...
     Directory /usr/lpp/java/J6.0.1/bin already exists.
     Attempting to delete J6.0.1 directories and components using
     rm command.
     :
     rm command completed successfully
     File /usr/lpp/java/J6.0.1/JDK_INSTALL_OK has been deleted.
     ls: FSUM6785 File or directory
    "/usr/lpp/java/J6.0.1/IBM//AJVG1601" is
    not found
     AJVG1601 is not installed in file system yet
     pax cannot be executed at this time
     script will be invoked again when AJVG1601 is installed
    
    .
    Error messages for Symptom 2:
    -----------------------------
       GIM39302E ** SHELL SCRIPT AJVGSCR PROCESSING FOR THE HFS
    AJVG1601 IN THE
            SAJV16G LIBRARY FAILED FOR SYSMOD UK72318. SEQUENCE
    NUMBER 000009.
       GIM30236I    APPLY PROCESSING FAILED FOR SYSMOD UK72318.
    SHELL SCRIPT
            PROCESSING FAILED FOR AN ELEMENT IN SYSMOD UK72318.
       ....
       pax: decompress: FSUM6639 compressed file is corrupt
       pax: checksum error on tape (got 13bfb, expected 0)
       pax: decompress: FSUM6639 compressed file is corrupt
       CEE5213S The signal SIGPIPE was received.
    
    ** pax command failure: pax ended with status 1
    
       Exiting script with status 1
    
    ----------------
    
    Stack Trace: N/A
    .
    
    If the installation of the PTFs failed, then it retains the SDK
    build parts in the <JAVA_HOME>/IBM directory.
    
    While trying to install the PTFs again, it can result in a
    failure.
    
    The problem can be exhibited with one of the following
    symptoms:
    
    1) The installed JDK gets deleted even though the install job
    ends successfully.
    
    2) Install error indicating the compressed file (pax) is
    corrupt.
    

Local fix

  • Manually delete the SDK build parts alone from <JAVA_HOME>/IBM
    path and apply both the parts again.
    The part names are AJVH1601 and AJVH2601
    DO NOT DELETE THE INSTALL SCRIPTS, only
    the PTF PARTS.  This problem can occur with
    Java 6, 601, or 7: the bypass steps apply to
    all versions.
    

Problem summary

  • when user installed the two PTFs first time, it might have
    abended due to some reason, space shortage and the system
    retained the build parts (AJVG1601 & AJVG2602) in
    <JAVA_HOME>/IBM
    
    When customer tried to apply the PTFs again, while applying the
    first PTF, it found the the build part corresponding to Co-Req
    PTF is already available in the system
    
    Hence the install script extracted the pax files into the
    system,installed the JDK into the system and delete both the
    PTFs from the SMP/E environment.
    
    When SMP/E apply the second PTF, it found that the JDK is
    installed and it removed the existing JDK first. Then while
    validating the Co-Reqs PTF, it could not find the other PTF in
    the system (as it was deleted in the first step). Hence the
    install script came out and waited for the other PTF.
    
    If the retained build parts is of an older PTF level, the build
    parts is not compatible with the new installing part and it
    throws an error while extracting the pax files after joining the
    parts.
    

Problem conclusion

  • .
    
    The PTF size limit is enhanced and the JDK 6.0.1 and 70 are
    packaged in single PTF to avoid the dependency between the hfs
    parts and avoid any install errors.
    .
    The problem is fixed by applying the following PTFs or its
    superceed.
    
    ==========================
    |  JDK Version |   PTF   |
    ==========================
    | 6.0.1 31-bit | UK92396 |
    -------------------------
    | 6.0.1 64-bit | UK92439 |
    --------------------------
    | 7.0.0 31-bit | UK92405 |
    -------------------------
    | 7.0.0 64-bit | UK92406 |
    -------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV05507

  • Reported component name

    JAVA CLASS LIBS

  • Reported component ID

    620700130

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-15

  • Closed date

    2011-10-17

  • Last modified date

    2013-03-28

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

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

Fix information

  • Fixed component name

    JAVA CLASS LIBS

  • Fixed component ID

    620700130

Applicable component levels

  • R600 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Runtimes for Java Technology
Java Class Libraries

Software version:

6.0

Reference #:

IV05507

Modified date:

2013-03-28

Translate my page

Machine Translation

Content navigation