Using Tokens in Job Log Names

When you specify the Logging information for a job, you can include tokens in the Log file name. This enables you to identify the source of the log file and when the job was run.

By default, the file name of job log is set to:

$OPERTYPE_$HOST_$DDMMYY.LOG.

So, for example, if you submitted an Update Hardware Inventory operation, to Scheduler S1 for 20 July 2004, this would create a log file called HWINV_S1_200704.LOG

You can create a log file name using any combination of the following tokens:

$RETRY

The job retry number. If the name of the log file does not contain the $RETRY token, the system adds the retry number to the end of the name. For example, HWINV.LOG becomes HWINV_1.LOG for the first retry.

$MAXRETRY

The maximum number of retries. You can include this with the $RETRY token to create job log files such as HWINV_1_OF_5.LOG, HWINV_2_of_5.LOG.

$OPERTYPE(n)

The short operation type name, such as HWINV for Hardware Inventory.

$JOBNAME(n)

The name of the job as specified in the Submit Job dialog’s Job tab.

$HOST(n)

The name of the Scheduler managing the job.

$USERNAME(n)

The Username used by the Scheduler.

$FROMHOST(n)

The name of the Console that submitted the job.

If you specify a value after a token, the name returned is restricted to the first n characters. For example, if the job name is MySoftwareInventory, $JOBNAME(6) returns MySoft.

Date and Time Tokens

Use the date and time tokens to add the date and time when the job was run to the file name of a job log:

$DATE

$HHMM

$DDMMYY

$MMDDYY

$YYMMDD