CA SDM Log (stdlog.0) Syntax

Installing › How to Install and Configure the CA SDM and CA NSM Integration › Verify the Post-Integration Considerations › Filter Rule Considerations › CA SDM Log (stdlog.0) Syntax

CA SDM Log (stdlog.0) Syntax

The syntax for entries in the stdlog.0 file is:

genDate genTime genNode genProc PID level codefile linenum msgID
:::msgDomain\msgNode::: ::: :::msgGenDomain\msgGenUser:::domainID
:::msgDate msgTime:::eventID arg tag::: :::IPaddr:filter:filterNum
:::majorSrc::: :::msgSrc:::msgType:::msgSrcNum::: :::platform

where:

Fields in the rule are separated by three colons (:::).

genDate: Specifies the month and day (from the system clock) on which the log incident was generated.
genTime: Specifies the time (from the system clock) at which the log incident was generated.
genNode: Specifies the node name that generated the log incident. The value is typically the first eight characters of the generating node’s DNS name. This value is always the same, because stdlog.0 only contains entries from processes running on the same node.
genProc: Specifies the name of the process (for example, ehwriter) that generated the log incident. The process name is operating environment-dependent, but should correspond to the name that appears in the Task Manager processes list (Windows) or in output from a ps command (UNIX).
PID: Specifies the numeric process identifier from the Task Manager processes list (Windows) or in output from a ps command (UNIX). The PID is critical when multiple processes are running with the same process name. For example, multiple database agents typically run concurrently with the same process name.
level: Specifies the programmer’s estimation of the significance of the message. Possible values include FATAL, EXIT, RESTART, SIGNIFICANT, SEVERE, ERROR, MINIMUM, WARNING, INFORMATION, MILESTONE, TRACE, and VERBOSE.
codefile: Specifies the name of the code source file from which the message was generated.
lineum: Specifies the number of the line in the code source file at which the message was generated.
msgID: Specifies the ID assigned to a TNG event.
msgDomain: Specifies the name of the domain from which the message originated.
msgNode: Specifies the name of the node from which the message originated.
msgGenDomain: Specifies the domain from which the user identified by the msgGenUser value generated the TNG message.
msgGenUser: Specifies the user ID of the user that generated the TNG message.
domainID: Specifies the ID of the domain from which the TNG message was generated.
msgDate: Specifies the month and day (from the system clock) on which the TNG message was generated.
msgTime: Specifies the time (from the system clock) at which the TNG message was generated.
eventID: Specifies the source event string or sed-style regular expression that triggered the event.
arg: Specifies a variable entered in the text string of a message action. For example, if the text field on a message action is entered as “ahd.dll AHD_Call help me,” the argument in stdlog.0 appears as “args=help me.”
tag: Specifies tag data associated with the TNG message.
IPaddr: Specifies the IP address of the host that generated the TNG message.
filter: Specifies the process name for the filter rule file.
filterNum: Specifies the number of the filter rule file.
majorSrc: Specifies the major source (or converter type). This is a string that identifies the source application ID. That is, whether events come from Unicenter TNG for Windows (in which case the value is tng), from Unicenter for UNIX (in which case the vale is uni), or from an internal daemon (in which case the value is -).
msgScr: Specifies the message source. Possible values are CNV (converter), FLT (filter), NOS (no source), and WRT (writer).
msgType: Specifies the message type. Possible values are CRT (create), DSC (discovery), TRM (terminate), and UPD (update).
msgSrcNum: Specifies the message source number.
platform: Specifies the operating environment from which the message originated. Possible values are AIX, AS400, DECOSF1, DGUX, DYNIX, HPUX, IRIX, MISERVER, MPRAS, MVS, NETWARE, SINIX, SOLARIS, SVR4MP, TANDEM, UNIXWARE, WNT (Windows), or any value defined by the UNIX agents.