Multiple Session Example
Each horizontal item in Table 2 represents a call to DBCHCL with the function code set as in the left column.
|
Function |
Description |
|
Connect/Fetch |
Same as for a single session. Note: A Connect and Fetch must be done for each session. |
|
Initiate Request (Session 1) |
Send Teradata SQL request to the Teradata Database. Application must set address and length of Teradata SQL request and optional using data. DBCHCL adds response parcel and sends request. Application must save the output request and output session identifiers. |
|
Initiate Request (Session 2) |
Same as for session 1, probably with different data. |
|
Fetch (Session 1 and 2) |
Same as for a single session: |
|
End Request |
Clean up request‑related context. (Stream 1 and 2) |
|
Disconnect (for each session) |
Log off the Teradata Database and free the session‑related control blocks. |