IBM Support

PH14635: WASPREUPGRADE IN REMOTE MIGRATION JAR DOESN'T WORK ON ZLINUX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WASPreUpgrade in remote migration jar fails with the following
    error message even on the supported zLinux env.
    ?
    <extractedpath_
    of_remotemigration_jar_with_includeJava>/bin/WASPreUpgrade.sh
    The
    system doesn't support running the 64 bit JDK provided by this
    createRemoteMigrJar file.
    You can rerun the createRemoteMigrJar
    script with -includeJava false option.
    WASPreUpgraded
    aborted.........
    Modify the line 43 in WASPreUpgrade from 64 to
    s390x
    

Local fix

  • No local work-around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Configuration Migration Tools on     *
    *                  Linux on s390x                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: WASPreUpgradeJar generated with Java    *
    *                      included on s390x Linux fails to run    *
    *                      claiming the operating system is not    *
    *                      64 bit.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Remote migration jars can be generated either to include a
    Java runtime (-includeJava true on WAS 9.0 or -skipJava false
    on WAS 8.5.5) which creates a jar that can only run on the
    same OS and architecture as the system used to generate it, or
    to include no Java runtime at all, which creates an OS
    agnostic jar capable of using a Java runtime on the target
    system. If Java is included, WASPreUpgrade within the jar runs
    several environment checks to ensure the OS and architecture
    match what it is expecting.
    Among these checks is to verify that the address width of the
    architecture is 64-bit. It does this on Linux by issuing
    &#180;uname -p&#180; and looking for a string with "64" in it. Both
    x86_64 and ppc64le match, but s390x doesn't despite being a 64
    bit architecture.
    

Problem conclusion

  • The remote migration WASPreUpgrade script was updated to
    accept s390x as a 64 bit processor architecture.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.5.1 and 8.5.5.17.  Please refer to the Recommended
    Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Adjust the WASPreUpgrade.sh script to replace the line reading
    "*64*) ;;" with "*s390x*) ;;".
    

Comments

APAR Information

  • APAR number

    PH14635

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-17

  • Closed date

    2019-08-21

  • Last modified date

    2019-08-21

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 October 2021