CLIv2 constructs the correct parcel sequences to the Teradata Database software based on the information supplied in the DBCAREA. The application should only be concerned with the response parcels returned from the Teradata Database through CLIv2.
The following table explains parcel return sequences for various combinations of connect types and return code fields.
Connect Type. |
Return Code field is... |
And... |
Then... |
R |
33 |
code is 33 at the time the Fetch function is issued for the connect request |
the response parcels do not have to be scanned. |
R |
0 |
|
the parcel returned is one of the following: Failure parcel (flavor 9) Error parcel (flavor 49) |
C |
non-zero |
|
the response parcels do not have to be scanned. |
C |
0 |
there is a problem establishing the connection |
the parcel returned will be one of the following: Failure parcel (flavor 9) Error parcel (flavor 49) |
C |
0 |
the connection is successfully established |
the parcels returned will be both of the following: Success parcel (flavor 8) or ResultSummary (flavor 171) EndRequest parcel (flavor 12) |