Activates and deactivates a user event.
Input Data
| Element | Data Type | Description |
|---|---|---|
| IndByte | BYTE | Indicator bits that specify which fields to treat as NULL if you are using indicator mode. Each bit in the byte corresponds to one field in the input data. If data is supplied for that field, set the bit to zero. If the data for that field is NULL (that is, there is no data supplied for that field), set the bit to 1. The IndByte field is only required if the CLIv2 request is submitted in indicator mode.
|
| mon_ver_id | SMALLINT NOT NULL |
MONITOR software version ID. This can be version 6 or later. For a general explanation of monitor version choices, see MONITOR VERSION. |
| Request Type | SMALLINT NOT NULL |
Type of request specified:
|
| Event Name | VARCHAR (30) | The name of the user event. Maximum of 30 characters. Must be padded with blanks. Case-sensitive. |
| Duration | INTEGER NOT NULL |
Time, in minutes, that this user event remains active. This field is valid for active requests only. A value of zero means the event is true. The evaluation of all events, including user events, is based on the System Event Timer. If not a multiple of the System Event timer, the Duration value is rounded to the next System Event timer value.
|
Monitor Privileges
To use this request, you must have the ABORTSESSION and MONSESSION privileges as part of your default role or both privileges must be granted directly to you.
- Using Roles to Manage User Privileges
- Teradata JDBC Driver Reference, available at https://teradata-docs.s3.amazonaws.com/doc/connectivity/jdbc/reference/current/frameset.html
Usage Notes
User Events are defined externally only by the name and the attribute of being active or inactive. User Events also have an optional duration time. The event times out at the end of the duration time unless the event is de-activated or re-activated. A Duration value of zero indicates the Activate (a Request Type value of 1) is persistent and lasts until explicitly made inactive by another User Event call. User Events persist across a TPA restart or system failure.
User Event names are global, or system wide and, therefore, you must make sure that no conflicting usages of User Event Control request calls occur.
CLIv2 Response Parcels
The following table lists information about the parcels for the USER EVENT CONTROL request.
| Parcel Sequence | Number | Field Length | Comments and Key Parcel Body Fields |
|---|---|---|---|
| Success | 8 | 18 to 273 | StatementNo=1 ActivityCount = 1 ActivityType = PCLUSEREVENTCONTROLSTMT (169) |
| DataInfo | 71 | 6 to 64100 | Optional: this parcel is present if request was IndicData parcel. |
| Record | 10 |
|
Depending on the request (Data or IndicData) data is returned in record or indicator mode. This is the only record returned. |
| EndStatement | 11 | 6 | StatementNo = 2-byte integer |
| EndRequest | 12 | 4 | None |
For an example of how the PM/API request, built in Java, appears when sent to the database server, see Teradata JDBC Driver Reference, available at https://teradata-docs.s3.amazonaws.com/doc/connectivity/jdbc/reference/current/frameset.html.
Response
The response to the USER EVENT CONTROL request returns a single Record parcel containing the result of the request.
| Field/Column Name | Data Type | Description |
|---|---|---|
| User-Defined Event Status | INTEGER NOT NULL |
Current status of the user-defined event:
|
| Previous User-Defined Event Status | INTEGER NOT NULL |
Previous status of the user-defined event:
|
The USER EVENT CONTROL request can be used to activate or inactivate a single, specific User Event.
The response indicates if the operation was successful. For successful operations, the result (Previous User-Defined Event Status) shows the previous value of this User Event. This allows the user to know if the User Event was previously active or not. For example, a successful operation, can return any of the following results:
| Result | Meaning |
|---|---|
| 1,0 | Current User Event is Active and was previously Inactive. |
| 1,0 | Current User Event is Inactive and was previously Active. |
| 1,2 | Current User Event is Active and was previously not defined. |