Restore autoscript logging when correlationID logging is enabled - reverse IV94052

This is asking for a way that IBM can partially reverse IV94052 by adding a new system property.

Adding a new system property would allow the administrator to restore the correlation logging for automation scripts. This would allow system administrators to see the critical details without affecting the customer(s) which requested IV94052.

Background

==

IV94052 removed the function that logged the script runs when correlation is enabled.

 Older Maximo 7.6 versions would display entries like this when 

“[3/3/17 16:13:56:311 EST] 000000c7 SystemOut     O 03 Mar 2017 16:13:56:311 [INFO] [temweb-cron_1] [CID-MXSCRIPT-88386891] Correlated data: BEGIN evalScriptTime:1 app:null Script:C_WOREPORTDATELOCK MboId: 507729409 MboName:WORKORDER LaunchPoint:C_WOREPORTDATELOCK evalINParamsTime:0 UserName:MAXADMIN evalOUTParamsTime:0 ElapsedTime:1 ms  END”

This information is critical to understand which automation scripts are running and when / what triggered them / related information

Technote says:

"Scripting logging can be used to provide a similar level of log entries."

it does not explain how all of the pieces of information can be gathered.  I don't think it is possible to capture/log some of the details that have been lost e.g. the evalScriptTime / evalINParamsTime

The most obvious method would be to set the automation script logger to DEBUG but that generates a lot more log entries that have been removed.

IBM Support suggest adding in log statements… this would effectively mean changing 100+ scripts with a minimum of 2 lines – 1 to store the time that the script starts and another complex statement to capture/log all the details shown above.