IBM Support

PI21144: Cell profile creation using Z-PMT tool fails when ports are blocked by RACF

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In an environment where access to many ports is blocked by RACF,
    cell profile creation might fail with:
    
    INSTCONFFAILED: The profile could not be created.
    
    <WASHOME>/logs/manageprofiles/default/createDefaultServer.log
    will show this error message:
    
    WASX7015E: Exception running command: "$AdminTask
    createApplicationServer aaaaa {-name bbbbb -specificShortName
    BBBBB -generic
    com.ibm.websphere.management.exception.ConfigServiceException:
    Resolved port number 65536 is out of range.
    

Local fix

  • Use genUniquePorts to cause the port scanner code to not run.
    Here are the steps to use this:
    
    1) In the <WAS_HOME>/profileTemplates directory, locate this
    file and make a backup copy:
    
    cell\dmgr\actions\createDefaultServer.ant
    
    2) Open the original in an editor and towards the bottom, you
    will find a line:
    
    command="$AdminTask createApplicationServer ... -bitmode
    ${bits}}"
    
    3) change the end of it from }}"
    (bracket, bracket, quote)
    
    to } -genUniquePorts false}"
    (bracket, space, -genUniquePorts, space, false, bracket, quote)
    
    4) Save the file and run profile creation.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cell profile creation fails with a      *
    *                      port number out of range message, even  *
    *                      though all ports are explicitly         *
    *                      supplied by the user.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Cell profile creation scans for available ports for the default
    application server.  This behavior is consistent with
    distributed platforms, but on Z/OS it can occur even when all
    ports have been explicitly specified by the Z-PMT tool. In a
    restricted environment, the unnecessary port availability
    checking could cause profile creation to fail.
    

Problem conclusion

Temporary fix

  • In the WAS_HOME/profileTemplates directory,
    within cell/dmgr/actions/createDefaultServer.ant,
    change:
    ${z.appserver.cluster.transition.name}
    to:
    ${z.appserver.cluster.transition.name}  -genUniquePorts false
    

Comments

APAR Information

  • APAR number

    PI21144

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-01

  • Closed date

    2014-08-04

  • Last modified date

    2014-08-04

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022