Request Processing Option - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Call-Level Interface Version 2
Release Number
15.00
Language
English (United States)
Last Update
2018-09-28
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Request Processing Option

Request Processing Option is a one byte field that specifies whether the Teradata Database is to return the data described in the request string or return information about the data described in the request string.

 

In this language...

The variable name for Request Processing Option is...

COBOL

DBCAREA‑REQ‑PROC‑OPT

PL/I

REQ_PROC_OPT

C

req_proc_opt

IBM Assembler

DBOFUNT

 

This routine...

Does this for Request Processing Option...

DBCHINI

writes

DBCHCL

reads (CON; RSUP; IWPF; CMD; IRQ)

 

Request Processing Option is used by...

To...

applications

write

Request Processing Option is initialized by DBCHINI to the default value provided for Request Processing Option in the HSHSPB.

When the value for Request Processing Option is not appropriate for the application, you should perform the following procedure before calling DBCHCL for the Connect, RunStartUp, Command, Initiate with Protocol‑Function, or Initiate Request function:

1 Set Change Options to ‘Y‘.

2 Change Request Processing Option as follows:

 

If the Teradata Database is to...

Then change the value for Request Processing Option to...

execute the request and send back the returned data

E

Analyze each statement in the request. The statements may not contain parameterized SQL.

If the request is valid, the Teradata Database will send back a time estimate and format information about the data that it would return if the request were executed.

Note that the time estimate is the same as EXPLAIN returns.

P

Analyze each statement in the request. The statements may contain parameterized SQL. If the request is valid, the Teradata Database will return a time estimate and format information about the data that would be returned if the request were executed. The time estimate is the same as EXPLAIN returns.

S

Analyze each statement in the request, then execute the request. The statements may contain parameterized SQL. If the request is valid, the Teradata Database will return not only a time estimate and format information about the data that would be returned if the request were executed, but also the data resulting from the executed request. Note that the time estimate is the same as EXPLAIN returns.

B

The difference between "P" and "S" is that "P" does not support parameterized SQL while "S" does.

Use mnemonics for the codes. Mnemonics are provided in the language definition file for the DBCAREA.

If the request is not valid, the Teradata Database sends back an Error, StatementError, or Failure parcel, the same as if Request Processing Option is set to E.

If "S" or "B" is specified but the Teradata Database does not support that option, a Failure parcel with error code 3749 will be returned.

Request Processing Option is read by the call to DBCHCL for the Connect function and stored in the appropriate control blocks but is not used during the connect.