PH04616: GEOTAGS AND FINITE CACHE LIMIT BEHAVIOR IS NOT CONSISTENT FOR AGENT RELAY INSTALLATIONS/UPGRADE.

APAR status

• Closed as program error.

Error description

• When you install agent relay for 6.2.7.1 , Combination of
  geotags/versionstatuses value as "*" and finite cache limit on
  relay with some value is not allowed .
  But there are some cases where this behavior is not consistent :
  Case 1: Fresh 6.2.7.1 relay installation does have following
  validation condition.  But before starting the agent relay, they
  
               can edit agentrelay.properties file and set * to
  agentrelay.codestation.geotags property which is kind of not
               correct.
  Case 2:
  2.1) v6.2.3.0 agent relay (say relay A) is installed on machine
  A with geotags=* and fixed cache size.
  
  2.2) Upgrade the relay to 6.2.7.1. agentrelay's properties
  remains the same (geotags=* and fixed cache size).
  
  2.3) Attempts to install another 6.2.7.1 agent relay (say relay
  B) to machine B with geotags=* and fixed cache size but it
  failed. So the relay B is installed with empty geotags.
  Now the relay A and the relay B have different values for the
  geotags property. From the property management and operation
  perspective, this is not a good practice.
  
  It'd be better to apply the same checking logic to fresh
  install, upgrade, start time consistently.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * UrbanCode Web UI Users                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Geotags and finite cache limit behavior is not consistent    *
  * for agent relay installations/upgrade.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fix is provided in IBM UrbanCode Deploy 7.3.1.0              *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 7.3.1.0
  

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