ZZ00300: INSTANCE NUMBER RANGE OF SCALING IN/OUT

IBM Cloud Orchestrator Fix Pack 2 (2.4.0.2) for 2.4
IBM Cloud Orchestrator Fix Pack 3 (2.4.0.3) for 2.4
IBM Cloud Orchestrator Fix Pack 1 (2.4.0.1) for 2.4
IBM Cloud Orchestrator Interim Fix 1 for 2.4.0.2

APAR status

• Closed as program error.

Error description

• we have verified that this is an initialization error setting
  the slider
   instance range as an array of numbers and not a string.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:
  All users of IBM Cloud Orchestrator 2.4 using
  SCOrchestrator_Support_vSys_Next_Toolkit (SCOVSYN)
  
  ****************************************************************
  * PROBLEM DESCRIPTION:
  While executing the human service "Collect Single VSysNext
  Pattern Deployment Parameters" the building block "Get VsysNext
  Details" get called.
  This building block reads all available pattern attributes and
  parse it to a format to be usable for furhter processing.
  The instance scaling range is passed as a string and not as
  expected as an array with minimum and maximum value.
  This gets wrong interpreted in the coach view where the
  resulting number array has a null as minimum and 10 as the
  default values.
  If the slider gets moved both values, minimum and maximum are
  returned as expected.
  This is the workaround to be used until the fixed toolkit is
  avaiable.
  
  ****************************************************************
  * RECOMMENDATION:
  Apply IBM Cloud Orchestrator 2.4 Fixpack 1 when available.
  

Problem conclusion

• ****************************************************************
  * PROBLEM CONCLUSION:
  The SCOrchestrator_Support_vSys_Next_Toolkit (SCOVSYN) providing
  processes configuring vSys next virtual application patten with
  instance scaling range configuration.
  If the slider setting the scaling range is not moved to a
  different position else it is initially shown the minimum
  instance number does not get initialized and the deployment
  fails.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | IBM Cloud Orchestrator 2.4 FixPack 1
  

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

  SMRTCLOUD ORCHS

• Fixed component ID

  5725H2800

Applicable component levels

• R240 PSY

     UP

• R220 PSN

     UP

• R230 PSN

     UP