EventList | el

In a client/server configuration, lists events from a specified data access service or from a specified event trace file.

{eventlist | el} service_name | [remote]file=event_trace_file_name [details] [ [{service | srvc}] | [{session | sess}] | [{statement | stmt}] | [{transaction | trans}] | [{network | net}] | [{error | err}] | [{other | oth}] ] ] [count=[{ + | - }] {all | number}] [offset={begin | end} [{ + | - }]number] [query=’custom_event_filter_string’]

where:

service_name is the name of a data access service. The event trace file for this specified service will be listed. Service names can be obtained using the ServiceList | sl command.

event_trace_file_name is the path and name of the event trace file you want to list.

number is the event number of events to list when used with the count option. When used with the offset option, number is the number of the event from which to start listing events. For example, if offset=10, OpenAccess SDK would list all events starting with event 10. Another example, if you specify count=20 and offset=begin, OpenAccess SDK will list the first 20 events. If you specify count=20 and offset=5, OpenAccess SDK will list 20 events starting from event 5.

custom_event_filter_string is an event filter statement.

custom_event_filter_string is an event filter statement. See Filtering Events for more information.

Details: If you specify Details, OpenAccess SDK will list detail information about the event.

Event Types: You can specify one or more of the following event groups for which to list event information: Service, Session, Statement, Transaction, Network, Error, or Other. When you specify one or more of the event groups, OpenAccess SDK Manager lists all the events of the type you specified. For example, if you specify Service, OpenAccess SDK lists all service events such as Service Started and Service Stopping (these events start with "Service"). Event names that do not start with Service, Session, Network, Error, Statement, or Transaction are Other events (for example, Cursor Closed).

Local host or remote configuration examples:

Example A: The following example lists detailed event information for the OpenAccess SDK Agent service:

Example B: The following example lists detailed event information for all service events starting with event number 10 in the event trace file associated with the OpenAccessSDK810_C data access service:

Example C: The following example defines a query for the information it will list for the OpenAccessSDK810_C data access service. The query returns all SQL statements that do not return a return code of 0.

Example D: The following example lists event information for the first 10 events in the local file named OpenAccessSDK810_C.trc:

Example E: The following example lists detailed event information for only service events in the remote file named OpenAccessSDK810_C.trc:

Offline configuration examples:

Example A: The following example lists event information from the local file named OpenAccessSDK810_C.trc file:

Example B: The following example lists event information for the first 10 events in the local file named OpenAccessSDK810_C.trc:

Example C: The following example lists event information from the local file named OpenAccessSDK810_C.trc, starting from the end of the file and listing all events:

Example D: The following example lists only session and service event information from the local file named OpenAccessSDK810_C.trc, starting with the fifth event:

Example E: The following example lists detailed event information for service events only from the local file named OpenAccessSDK810_C.trc: