Robust Automation Script Logging

To provide robust and reliable logging of Automation Scripts, we have developed a custom logger function named zLog() to write to the Maximo log files. In Automation Scripts, this function provides advanced functionality and reliability beyond Jython print statements. Many times, print statements failed when the scripts abended. Additionally, we couldn't fully control logging for various log levels (as set in Logging and Automation script modules).

The following is the main function, zLog(), and the required imports. This is in Jython. There are also MBO specific extender functions which provide additional MBO specific logging (see below).

External link:
https://www.ibm.com/developerworks/community/forums/html/topic?id=2552664f-0646-410a-b0fb-33cd6181a474

Getting the list of SIGOPTION NAMES and APPLICATION NAMES which use specific CONDITION

select APP as "Application", OPTIONNAME as "Signature Option", GROUPNAME as "Security Groups"
from CTRLGROUP where CTRLGROUPID in
(
  select CTRLGROUPID from CTRLCONDITION where
   CONDITIONNUM in (select CONDITIONNUM from CONDITION where
    CLASSNAME = 'com.ibm.tivoli.maximo.script.ScriptCustomCondition')
);

In this example, we are looking for any application and sig.option name which use condition, which use automation script with Condition Launch Point.


FYI: Condition UI Table list:

select * from CTRLGROUP;
select * from CTRLCONDITION;
select * from CTRLCONDPROP;