I prefer to propagate using UtilityWarningToLog() in a Routine activity. This means that I can retain control right back to the top level, which can instigate some diagnostic activity if required. Never abort!
To answer the actual question, the second argument to subroutines like DSLogInfo and DSLogWarn - I never use the other one! - is the value that appears in parentheses in the subject line of a logged event - which you can see in summary view. For example:
Code: Select all
Call DSLogInfo("Resizing completed", "Cleanup")
will log the following event, assuming from job named Resize job control routine:
Resize..Job Control (Cleanup): Resizing completed
This can be useful when you use the log functions for diagnostic purposes. For example:
Code: Select all
$IFDEF DEBUGGING
Call DSLogInfo("Value of loop counter is " : LoopIndex, "*Debugging*")
$ENDIF
It's then clear which messages relate to debugging in the job log.