Text Format for Catalogic DPX Logs
Catalogic DPX log files are formatted in plain text. Typically, every line has 9 columns that are separated with a pipe (|), and it is structured as shown:
date|module|jobid|taskid|pid|threadid|MODnnnnT|article|message
These columns are defines as shown:
date
A timestamp of the event that. It is formatted in yyyy/mm/dd hh:mm:ss.nnn, where nnn represents milliseconds.
module
The identifier corresponding to the module logging the message. This is the actual module name or, in some cases, a common library routine.
jobid
The job ID. Or, fill “xxxxxxxxx” instead if none of job IDs is applicable for the event,
taskid
The task ID within a particular job ID. Or, fill “xxxxxxxx” if none of task IDs is applicable for the event.
Tip. The combination of jobid|taskid is unique within a file.
pid
The process ID.
threadid
The thread ID. Or, fill “xxxxxxxx” instead if none of task IDs is applicable or if the UNIX system is used.
MODnnnnnnT
The module ID, the message ID, and the message class letter. The message classes are represented by the following letters:
D
Debug
E
Error
F
Fatal
U
Information
W
Warning
S
Host operating system error code transaction
For example, the message ID JH_003527I is an information message for the module ID “JH” and the message ID “003527”.
article
The article number of Catalogic Software Knowledge Base that is relevant to the message. Or, fill “xxxxxxx” instead if there is no relevant Knowledge Base article.
message
A human-readable description of the event. This may include information such as job tasks, task start-stop times, tape drives involved, error reports, and so on.
The following screenshot depicts an example output of the log file that you see in Catalogic DPX:
Last updated
