IBM Support

IV89722: JVM SHOULD SET USER.HOME BASED ON USERPROFILE (WINDOWS)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: N/A
    .
    Stack Trace: N/A
    .
    user.home may not be set to what the customer is expecting.
    

Local fix

  • N/A
    

Problem summary

  • Currently, on Windows the VM sets the user.home variable based
    on values taken from the Windows registry. The more appropriate
    way to set user.home is to set it to the value contained in
    Windows environment variable USERPROFILE.
    

Problem conclusion

  • The JVM has been updated to set user.home to match the Windows
    USERPROFILE variable.
    .
    This APAR will be fixed in the following Java Releases:
       8    SR3 FP20  (8.0.3.20)
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, information about the available
    Service Refreshes and Fix Packs can be found at:
               https://www.ibm.com/developerworks/java/jdk/
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV89722

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    270

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-05

  • Closed date

    2016-10-06

  • Last modified date

    2016-10-06

  • 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

    J9 COMMON CODE

  • Fixed component ID

    620700127

Applicable component levels

  • R270 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 February 2022