IJ40423: PROPERTY MXE.SCRIPT.RELOADPERSCRIPT SOMETIMES IGNORED WHEN PUSHING AUTOMATION SCRIPT.

APAR status

• Closed as program error.

Error description

• Problem Desscription:
  
  When creating a new script via MIF, everything is fine, only
  this script is reloaded. When updating an existing script, the
  whole ScriptCache is reloaded, as it was before setting
  mxe.script.reloadperscript to true.
  
  While the ScriptCache reloads, most of the automations do not
  work.
  
  
  Steps to reproduce
  
  1. Set  mxe.script.reloadperscript property to true.
  
  2. Create a simple script:
  
  pass
  
  # Just a Test
  
  
  3. And for the Update:
  
  pass
  
  # Just a Second Test
  
  
  Current results:
  
  If script is created/updated this via the UI, the following log
  messages can be seen:
  
  
  [2/8/22 10:02:18:999 CET] 0000042c SystemOut O [INFO]
  [CL_ICD_DEAS112FSCCD01] [] [maximo] BMXAA6447I - Reload
  RELOADTEST3 from SCRIPT into the maximo cache.
  [2/8/22 10:03:04:993 CET] 0000056d SystemOut O [INFO]
  [CL_ICD_DEAS112FSCCD01] [] [maximo] BMXAA6447I - Reloading
  RELOADTEST3 from SCRIPT to the Maximo cache.
  
  If script is created/updated this via MIF, the following message
  shows:
  
  [2/8/22 10:04:49:879 CET] 0000060a SystemOut O [INFO]
  [CL_ICD_DEAS112FSCCD01] [] [maximo] BMXAA6447I - Reloading
  RELOADTEST4 from SCRIPT into the Maximo cache.
  [2/8/22 10:05:15:456 CET] 00000609 SystemOut O [INFO]
  [CL_ICD_DEAS112FSCCD01] [] [maximo] BMXAA6444I - Reloading
  SCRIPT into the Maximo cache.
  
  On update the ScriptCache for this script needs to be reloaded.
  With the introduction of systemproperty
  mxe.script.reloadperscript, this should be only the script that
  got changed. This is ways faster and less interrupting. For ~700
  Scripts active and reloading all takes between 8 and 15 seconds
  (depends on the current server load). Reloading a single script
  is done within milliseconds and also does not affect all other
  scripts. In those 8 to 15 seconds, nearly no script works
  correctly.
  
  Expected results:
  
  The script reload should work even if updated from UI.
  
  Environment:
  
  Tivoli's process automation engine 7.6.1.2
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When `mxe.init.reloadperscript` is enabled and an existing   *
  * auto script is updated via MIF, the entire scripting cache   *
  * is reloaded.                                                 *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR will be contained in a future release.
  

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 ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels