Topic
  • 2 replies
  • Latest Post - ‏2014-02-06T08:02:01Z by jan_v
jan_v
jan_v
2 Posts

Pinned topic How to exclude entries of automationscript execution times from the STDOUT.log

‏2014-02-05T08:41:50Z |

Hello,

Every time an automation script runs, we get an entry in the stdout.log file with the execution time for the script.

Like this:

05 feb 2014 08:16:29:935 [INFO] The total time taken to execute the SAVEROLEPERSGRP script for the SAVEWFASSIGN  launch point is 90 ms.
05 feb 2014 08:16:29:942 [INFO] The total time taken to execute the SAVEROLEPERSGRP script for the SAVEWFASSIGN  launch point is 7 ms.
05 feb 2014 08:16:29:948 [INFO] The total time taken to execute the SAVEROLEPERSGRP script for the SAVEWFASSIGN  launch point is 6 ms.
05 feb 2014 08:16:29:953 [INFO] The total time taken to execute the SAVEROLEPERSGRP script for the SAVEWFASSIGN  launch point is 5 ms.
05 feb 2014 08:16:29:960 [INFO] The total time taken to execute the SAVEROLEPERSGRP script for the SAVEWFASSIGN  launch point is 6 ms.
 

This makes our log file big and unclear to see the real errors.

- All loglevels are set to ERROR (for the rootloggers and on the automation script)

- I tried to use an appender to save the automation script logs to another log, but now the entries go to the newly configured .log file and the STDOUT.log. So they are logged twice.

 

Is there a way to exclude these messages from the STDOUT.log file?

Thank you for any help I can get on this issue.

 

  • SASHULL
    SASHULL
    303 Posts

    Re: How to exclude entries of automationscript execution times from the STDOUT.log

    ‏2014-02-05T18:37:26Z  

    This is something I opened a PMR for and this uses the Maximo Root Logger intentionally (per a comment in the code according to the Developer I spoke with). There are other events that are logged depending on the launch point (like if it's an action launch point it also logs:

    23 Oct 2013 10:11:30:032 [WARN] [MXServer] [] BMXAA7785W - The property
    mxe.script.actionextention does not exist in the MAXPROP or            
    MAXPROPVALUE tables


    He agreed that the actionextension thing would be removed in a future release but was unsure about whether or not the one you mention would be able to be moved to the automation script logger since it was intentionally configured to use the Maximo root logger. The APAR I have is IV51220 if you want to see when a fix is available (one currently isn't)

  • jan_v
    jan_v
    2 Posts

    Re: How to exclude entries of automationscript execution times from the STDOUT.log

    ‏2014-02-06T08:02:01Z  
    • SASHULL
    • ‏2014-02-05T18:37:26Z

    This is something I opened a PMR for and this uses the Maximo Root Logger intentionally (per a comment in the code according to the Developer I spoke with). There are other events that are logged depending on the launch point (like if it's an action launch point it also logs:

    23 Oct 2013 10:11:30:032 [WARN] [MXServer] [] BMXAA7785W - The property
    mxe.script.actionextention does not exist in the MAXPROP or            
    MAXPROPVALUE tables


    He agreed that the actionextension thing would be removed in a future release but was unsure about whether or not the one you mention would be able to be moved to the automation script logger since it was intentionally configured to use the Maximo root logger. The APAR I have is IV51220 if you want to see when a fix is available (one currently isn't)

    Thank you SASHULL. We opened a PMR too.

    Updated on 2014-02-06T08:03:53Z at 2014-02-06T08:03:53Z by jan_v