PI50946: DEFAULT PARAMETERS NOT OVERRIDDEN WHEN PROVISIONING A VSYS.NEXT PATTERN

IBM UrbanCode Deploy Fix Pack 2 (6.2.0.2) for 6.2
IBM UrbanCode Deploy Interim Fix 1 for 6.2.0.2
IBM UrbanCode Deploy Fix Pack 2 (6.2.1.2) for 6.2.1

APAR status

• Closed as program error.

Error description

• When you provision a vsys.next pattern which includes the UCD
  script package via the Create Environment step, the UCD script
  package default parameters are not automatically overridden as
  it is the case when
  provisioning via the UI. This will happen to the hostname and
  agent
  names.
  As a result the agents installed in the provisioned image will
  not
  be able to connect to the UCD server because they will not have
  the
  right hostname. You will also see that all provisioned agents
  have the same
  name resulting in naming conflicts.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When you provision a vsys.next pattern which includes the    *
  * UCD                                                          *
  * script package via the Create Environment step, the UCD      *
  * script                                                       *
  * package default parameters are not automatically overridden  *
  * as                                                           *
  * it is the case when                                          *
  * provisioning via the UI. This will happen to the hostname    *
  * and                                                          *
  * agent names.                                                 *
  * As a result the agents installed in the provisioned image    *
  * will not                                                     *
  * be able to connect to the UCD server because they will not   *
  * have                                                         *
  * the right hostname. You will also see that all provisioned   *
  * agents                                                       *
  * have the same name resulting in naming conflicts.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to UCD version 6.2.0.2                               *
  ****************************************************************
  

Problem conclusion

• Fixed in UCD version 6.2.0.2
  

Temporary fix

Comments

APAR Information

• 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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels

• R600 PSN

     UP

• R600 PSY

     UP

• R601 PSN

     UP

• R601 PSY

     UP

• R610 PSN

     UP

• R610 PSY

     UP

• R611 PSN

     UP

• R611 PSY

     UP

• R612 PSN

     UP

• R612 PSY

     UP

• R613 PSN

     UP

• R613 PSY

     UP

• R620 PSN

     UP

• R620 PSY

     UP