Purpose
Releases or aborts a specific request or session on the Teradata dynamic workload management software delay queue.
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 Flag | SMALLINT | Indicator that the request or session was aborted or released:
|
| Host ID | SMALLINT | ID of the host number upon which the session containing the delayed request was established. |
| Reserved | SMALLINT | Mod-4 alignment padding. |
| Session Number | INTEGER | Number of the session in which the delayed request was submitted. A unique session number is assigned by the host (or client) at logon. |
| Request Number | INTEGER | Active request number. This field is not used if Request Flag is either 2 or 3.
|
| Workload Class Id | INTEGER | Workload ID for the delayed request. If the request is from the context delay queue (where there is no workload ID), the field value is zero. This field is not used if Request Flag is either 2 or 3.
|
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.
- Teradata Vantage™ - Database Administration, B035-1093
- Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100
- Teradata JDBC Driver Reference, available at https://teradata-docs.s3.amazonaws.com/doc/connectivity/jdbc/reference/current/frameset.html
Usage Notes
The TDWM DELAY REQUEST CHANGE request allows requests or sessions to be processed out of the normal first-in-first-out (FIFO) order.
If the identified request or session is not found in the Teradata dynamic workload management software delay queue, an error is returned. This condition is expected since requests or sessions are normally released from the delay queue whereas the information in the TDWM STATISTICS request could be outdated.
CLIv2 Response Parcels
| Parcel Sequence | Parcel Flavor | Length (Bytes) | Comments/Key Parcel Body Fields |
|---|---|---|---|
| Success | 8 | 18 to 273 | StatementNo=1 ActivityCount=0 ActivityType= 155 (PCLTWMDELRQSTCHGSTMT) |
| EndStatement | 11 | 6 | StatementNo = 2-byte integer=1 |
| EndRequest | 12 | 4 | None |
Sample Input - CLIv2 Request
The following example shows how the parcels for a TDWM DELAY REQUEST CHANGE request, built by CLIv2, appear when sent to the database server.
| Flavor | Length | Body | ||
|---|---|---|---|---|
| Num | Name | Bytes | Field | Value |
| 0001 | Req | 16 | Request | TDWM DELAY REQUEST CHANGE |
| 0003 | Data | 24 | MonVerID Request Flag Host Id Request Number Session Number Workload Class Id |
7 0 1 5 1000 10 |
| 0004 | Resp | 6 | BufferSize | 64000 |
Sample Input - Teradata JDBC Driver Request
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 .
Sample Output
- Request Flag = 0
- Host Id =1
- Request Number = 5
- Session Number = 1000
- Workload Class Id = 10
The TDWM DELAY REQUEST CHANGE request commonly returns values in text character format. Your application program may return the values in a different format or display.
Success parcel: StatementNo: 1 ActivityCount: 1 ActivityType: 155 FieldCount: 1 DataInfo parcel: FieldCount: 1 EndStatement. EndRequest.