Database Events Report
The Database Events Report allows you to compose a report of database event data based on the information that is important to you.
You choose the database fields to display and their sort order. You can also state filter
criteria to limit the records to include in the report. Filter criteria include any of the database
fields except for CC Name. The following table describes the data fields available for the Database
Events Report:
| Column | Description |
|---|---|
| Action | Name of an action that is called by a rule. |
| Actions completed | Indicates whether the IBM® Sterling Control Center
Monitor
actions are completed. The following are possible values: Null=Actions not completed Timestamp=Actions completed This element is used for restarts. |
| Alert | Indicates whether an alert was triggered. The following are possible values: Null=No alert 0-3=Alert severity |
| Handled comments | Comments that are entered by the user when the alert was deleted. |
| Alert handled | A flag that is indicating whether the alert was handled. The following are the possible
values: Y=Alert handled N=Alert not handled |
| Alert handled (by) | User ID of the IBM Sterling Control Center Monitor user that handled the alert. |
| Alert updated | Time that the alert was updated, in Java epoch time stamp format. |
| Data Visibility Group | Data visibility group for this event. |
| Date time | Date and time that the event was generated. Format yyyy/mm/dd hh:mm:ss.msmsms. |
| Destination file | Destination file name in a copy operation. |
| Email flag | This field is used by IBM Sterling Control Center
Monitor
for recovery purposes. When a rule matches an event, the associated action is run. If the action
includes sending an email, this flag updates after the email is sent. The values: 0=No email sent >0=email sent The value is set to zero if nothing was done, but is set to the Timestamp if something was done. |
| Event ID | ID number that is assigned by the system to each event. |
| Event type | Code indicating the type of event. |
| File size | Size of the file that is transferred by the Sterling Connect:Direct® Process or Sterling Connect:Enterprise® batch. |
| From node | Server that sent the file. P=Pnode was sending server. S=Snode was sending server. |
| MSG ID | IBM Sterling Control Center Monitor message ID issued with the event. |
| Node ID | Server name of alias. |
| Node type | Code indicating the type of server. The server types: 0=IBM Sterling Control Center Monitor 1=Sterling Connect:Direct 2=Sterling Connect:Enterprise 3=Sterling B2B Integrator 4=FTP Server 5=Sterling Connect:Express 7=MQ MFT |
| Orig node | The server that initiated the Process. |
| Percent complete | Percentage of a Sterling Connect:Direct Copy Process that is complete. |
| Process ID | Sterling Connect:Direct Process or Sterling Connect:Enterprise batch number. |
| Process name | Sterling Connect:Direct Process name or Sterling Connect:Enterprise batch name. |
| Remote node | Name of the remote server that is involved in the Process or file transfer. |
| Return code | Specifies a numeric code that is returned from a completed Process or file transfer that
indicates failure or success. The standard return codes: 0=Successful completion 4=Warning 8=Error 16=Unrecoverable error |
| Rule ID | Name of the rule that is triggered by the event. |
| RULE_INSTANCE_ID | Unique identifier for rule matching instances. |
| SEQ_NUM | A number that is used to uniquely identify events that are generated at the same time. |
| Server Metadata 1 | Server metadata field 1. |
| Server Metadata 2 | Server metadata field 2. |
| Server Metadata 3 | Server metadata field 3. |
| Server Metadata 4 | Server metadata field 4. |
| Server Metadata 5 | Server metadata field 5. |
| Server Metadata 6 | Server metadata field 6. |
| Server Metadata 7 | Server metadata field 7. |
| Server Metadata 8 | Server metadata field 8. |
| Server Metadata 9 | Server metadata field 9. |
| Server Metadata 10 | Server metadata field 10. |
| Short msg | Message text that is associated with the Message ID. |
| SLC flag | Internally used by IBM Sterling Control Center
Monitor for
recovery purposes. When an event is generated, it is sent to the SLC subsystem. This flag indicates
whether the event successfully sent to that subsystem. The values: 0=Event was not sent >0=Event was sent |
| SLC_ID | System-assigned name for each SLC window. |
| SLC_INSTANCE_ID | Unique identifier for each SLC window. |
| SLC_SOURCE_1 | Internal field that is used for SLC recovery. |
| SLC_SOURCE_2 | Internal field that is used for SLC recovery. |
| SLC_SRC_EVENT_ID | EVENT_ID of the event that triggered the SLC. |
| Source file | Source file name in a copy. |
| Step name | Name of the Sterling Connect:Direct Process step. |
| Submitter | User ID of the Process submitter. |
| Trap flag | Internally used by IBM Sterling Control Center
Monitor for
recovery purposes. When a rule matches an event, the associated action is run. If the action
includes sending an SNMP trap, this flag updates after the SNMP trap is sent. The values: 0=No trap generated >0=Trap generated The value is set to zero if nothing was done, but is set to the Timestamp if something was done. |
| USER_DATA_1 | User metadata field 1. |
| USER_DATA_2 | User metadata field 2. |
| USER_DATA_3 | User metadata field 3. |
| USER_DATA_4 | User metadata field 4. |
| USER_OP_FLAG | Internally used by IBM Sterling Control Center
Monitor for
recovery purposes. When a rule matches an event, the associated action is run. If the action
includes starting an OS command script, this flag is updated after starting the OS command script.
The values: 0=No OS command started >0=OS command started The value is set to zero if nothing was done, but is set to the Timestamp if something was done. |
| XML STRING | An XML representation of the event. |