Request Processing Option - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
15.10
Language
English (United States)
Last Update
2018-10-07
dita:id
B035-2418
lifecycle
previous
Product Category
Teradata Tools and Utilities

Request Processing Option

Usage Notes

The Request Processing Option field specifies whether the Teradata Database is to return:

  • The data described in the request string, or
  • Information about the data described in the request string, or
  • BOTH.
  •  

    Language

    Variable Name

    COBOL:

    DBCAREA-REQ-PROC-OPT

    C: DBCAREA.H:

    req_proc_opt

     

    Routine

    Action Taken

    DBCHINI:

    writes

    DBCHCL:

    reads (CON; RSUP: IRQ)

     

    Used by

    Action Taken

    application program

    writes

    Request Processing Option is initialized by DBCHINI to the default value provided for Request Processing Option in the site’s SPB.

    If the value provided is not appropriate for the application, before calling DBCHCL for the Connect, Run Startup, or Initiate Request options, the application program may set:

  • Change Options to Y, and
  • Request Processing Option to:
  • E, if the Teradata Database is to execute the request in the request string and send back the returned data,
  • P, if the Teradata Database is to analyze the request in the request string, and if:
  • Request is valid, send back a time estimate and format information about the data that it would return if the request were executed (the time estimate is the same as EXPLAIN returns)
  • Request is invalid, send back an Error or Failure parcel (the same as if Request Processing Option is set to E).
  • S, analyze each statement in the request.
  • The statements may contain parameterized SQL. If the request is valid, the Teradata server 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.
  • The difference between the P and S mode is that P mode cannot contain a parameterized SQL request.
  • B, analyze each statement in the request, then execute the request. The statements may contain parameterized SQL. If the request is valid, the Teradata server 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. The time estimate is the same as EXPLAIN returns.
  • B option is supported both in buffer and parcel modes.

    Note: Segmented requests(TDSP) are not supported in S, B, and P modes. If these requests are submitted in either the S, B or P modes, the Teradata Database would return a failure parcel with the error code set to 3749.

    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.