IBM Support

PH18330: MIGRATING A CELL USING THE CLONE OPTION DOESN'T CREATE A DIFFERENT PROFILE KEY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • |TheXCFGroupdefault-BASE-cae286bf-3cbf-4292-9e08-f75388443ae2|
    |TBHF5FF|
    Trace: 2019/10/17 13:51:54.853 02 t=8F8368 c=UNK key=S2 tag=
    (13007004)
      SourceId: com.ibm.ws.xcf.groupservices.GenLivenessPluginZoS
      ExtendedMessage: BBOO0222I: DCSV0003I: DCS Stack
    TheXCFGroupdefault-BASE-cae286bf-3cbf-4292-9e08-f75388443ae2 at
    Member MyHostWAS00Networkndnode1nodeagent: Internal programming
    state information. Internal details:  {Method=XCFGroupName,
    InternalDetails=XCF name for Group
    TheXCFGroupdefault-BASE-cae286bf-3cbf-4292-9e08-f75388443ae2 is
    BTBHF5FF}
    
    ${USER_INSTALL_ROOT}/properties/profileKey.metadata
    contains com.ibm.ws.profile.key
    

Local fix

  • Change one of the cells to not XCF for monitoring application
    server status. To do this, add:
    
    was.xcfmonitor.enabled
    
    set to false for the node agent and App Servers in the admin
    console:
    
    Node agents > nodeagent_name > Process definition > Control >
    Java Virtual Machine > Custom properties
    
    Application servers > server_name > Process definition >
    Control > Java Virtual Machine > Custom properties
    
    Application servers > server_name > Process definition >
    Servant > Java Virtual Machine > Custom properties
    
    Then restart the node agent and servers to pick up the change.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V9.0 Migration Tooling               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Coregroup facility is failing when      *
    *                      configured to use XCF.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Some zOS systems are configured such that their WebSphere
    coregroup facility utilizes XCF.  This configuration uses the
    WebSphere profile key which for clone migrations should not be
    migrated forward.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH18330

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-21

  • Closed date

    2019-11-14

  • Last modified date

    2019-11-14

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R900 PSY

       UP

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

Document Information

Modified date:
14 October 2021