If the
job does not complete successfully, then you might want to examine
the logs for each loop in the job. Failures in the main flow of the
job are often caused by failures in one or more of the loop SAS sessions.
Examine the
Status tab to determine where
the error occurred and refer to the log for that part of the job.
A SAS log is saved for each pass through the loops in the Multiple
Log Template Job. These logs are placed in a folder called
Process Logs under the
Loop1 and
Loop2 folders in the structure that
is created by the template setup job.
In order
to know which file you are looking for, you should understand the
naming conventions for these log files. The files in the
ProcessLogs folder are named L
nn_x.log, where
nn is a unique
number for this particular Loop transformation and
x is a number that represents the iteration of
the current loop. For example, if you process 200 Web logs, then the
ProcessLogs folder for
Loop1 (Clickstream Log transformation and Clickstream Parse transformation)
contains 200 logs named L
nn_1.log to L
nn_200.log (where
nn is some constant number).
The
ProcessLogs folder for
Loop2 (Clickstream Sessionize transformation) has the same naming convention.
However, the log folder for
Loop2 contains
one log for each group. For example, if the Clickstream Parse transformation
in the first loop generated five groups, then the logs are named L
nn_1.log
to L
nn_5.log (where
nn is a constant number).
Note: The log files
in the
Process Logs folder are not overwritten
during subsequent runs of this job. Consider clearing the
Process Logs folder between runs during job development
to avoid accumulating a large number of logs.