The following table lists the remaining routines and describes how they are used.
| Routine | Description | |
|---|---|---|
| DBCHME | What | Adds master event in place of session event |
| Why | For the convenience of the application | |
| DBCHMEC | What | A deprecated routine now replaced by DBCHME. |
| Why | For the convenience of the application | |
| DBCHPEC | What | Posts an ECB |
| Why | To return control to the application when some event occurs (like terminal attention) | |
| Why | To enable the application to obtain environmental information | |
| DBCHSAD | What | Stores specified value at specified address |
| Why | To provide pointer support in languages that do not support pointer manipulation | |
| DBCHUE | What | Adds user-provided event to CLIv2‘s internal wait list |
| Why | To provide a mechanism for the application to regain control if some event is detected (like terminal attention) | |
| DBCHUEC | What | A deprecated routine now replaced by DBCHUE. |
| Why | To provide a mechanism for the application to regain control if some event is detected (like terminal attention) | |
| DBCHWAT | What | Waits for event to occur (an event refers to the arrival of some response from the Teradata Database) If DBCHUE has been invoked, an event also refers to the occurrence of some application-defined event |
| Why | To provide a mechanism for explicit waits for events; also simplifies handling of concurrent sessions | |
| DBCHWL | What | Waits for one of a list of events to occur. |
| Why | To provide a mechanism to explicitly wait for only some events. | |