Log File Name and Format
As described below, each log file contains the date in its name, and no logs are written to the file after 11:59:59.999 p.m. After midnight, new log files – with the new date in their names – are created as needed.
The path and name of the log file is:
or, if SSCMSGSIZE is set, the path and name of the log file is:
where:
product-directory
the directory where the product is installed.
hostname
the name of the node. Any domain qualification is removed from the name. For example, “myserver.us.abc.com” becomes just “myserver”.
yyyymmdd
the date.
filenum
an indicator of how many log files were generated that day for the node. The first log file has filenum = 1, the second has filenum = 2, etc. Filenum is a four digit number left-padded with zeros.
The format of each log message is:
where:
date
yyyy/mm/dd hh:mm:ss.nnn, where nnn represents milliseconds. This field is 23 characters.
module
the identifier corresponding to the module logging the message. This is the actual module name or, in some cases, a common library routine. This field is 8 characters.
jobid
the job ID. This is a 10 digit number when known and “xxxxxxxxxx” when unknown.
taskid
the task ID within a particular job ID. This is an 8 digit number when known and “xxxxxxxx” when unknown. The combination of `jobid
pid
the process ID. This is an 8 digit number left-padded with zeros.
threadid
the thread ID. This is an 8 digit number left-padded with zeros when known and “xxxxxxxx” when unknown. UNIX systems do not use thread ID.
MODnnnnnnT
a three-part message identifier. MOD = The three-letter identifier for the module. nnnnnn = the six digit message ID. T = a letter to indicate the class of message as follows: D - debug, E - error, F - fatal, I - Informational, W - warning, S - Host Operating System Error Code Translation.
the Knowledge Base article number associated with the message. “xxxxxxx” is used if there is no Knowledge Base article.
message
a meaningful message that describes the activity or observation. This may include information such as job tasks, task start-stop times, tape drives involved, error reports, etc.
In the log files, pipes are used as delimiters, and columns are aligned for easy interpretation.
Note. The above file name and format information applies only to the node-based model.
The following is an illustration of a small, truncated section of a node-based log file:
Last updated
