IJ35010: DATABASE ATTRIBUTE TITLE CHANGE ONLY WORK ONCE IN A CLUSTER UNTIL RESTARTS

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  
  Database attribute title change only work once in a cluster
  until restarts.
  
  
  PROBLEM:
  
  In a clustered environment, changing the title of an attribute
  (such as ACTFINISH on WORKORDER from Actual Finish to Actual
  Completion) works the first time, but subsequent changes (such
  as changing it back to Actual Finish) only work on the JVM where
  you made the changes. The other JVMs will persist the first
  title change (Actual Completion) until the server is restarted.
  
  
  PERFORMANCE ISSUE: No.
  
  STEPS TO REPRODUCE:
  
  1) Get a Maximo cluster (just need 2 JVMs, no separation of
  functionality required).
  2) Go to Database Configuration. Open the WORKORDER object and
  change the title of the ACTFINISH attribute to Actual
  Completion.
  3) Apply the Configuration Changes. Being non-structural, this
  will NOT require admin mode. After 2 minutes, go to Work Order
  Tracking on the second JVM, open a WO, and scroll down to the
  ACTFINISH field. You'll see that the title was changed to Actual
  Completion.
  4) On the first JVM, change the title to Actual Finish again and
  apply configuration changes.
  5) After 2 minutes, go to Work Order Tracking (leave the app and
  come back in) on the second JVM, open a WO, and scroll down to
  the ACTFINISH field. You'll see that the title is still Actual
  Completion.
  
  The title change won't be propagated to the second JVM until the
  JVM is restarted. On the first JVM where this change is made,
  the title is reflected properly each time.
  
  
  
  CURRENT ERRONEOUS RESULT:
  
  The title change won't be propagated to the second JVM until the
  JVM is restarted.
  
  
  EXPECTED RESULT:
  
  The title change should be propagated to the second JVM without
  the JVM restart.
  
  
  ENVIRONMENT (SYSTEM INFO):
  
  Tivoli's process automation engine 7.6.1.2-IFIX20210504-1949
  Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-31
  

Local fix

• N/A
  

Problem summary

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: | Release 7.6.1.3 of Base Services
  

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

  MAXIMO SYSTEMS

• Fixed component ID

  5724R46AV

Applicable component levels