16.20 - Changing the Value for Request-mode - Teradata Tools and Utilities

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

Teradata Tools and Utilities
September 2019
Programming Reference

Request-mode is initialized to the default value provided for Request-mode (IBOQMOD) in the HSHSPB.

When the value for Request-mode is not appropriate for the application, you should perform the following procedure before calling DBCHCL for the Initiate Request function:

  1. Set Change-options to ‘Y‘.
  2. Change the value for Request-mode as follows.
    If the application is passing to CLIv2... Then change the value for Request-mode to...
    the Request parcel body and, optionally, the Using Data parcel body and parcel elements in a DBCAREA extension P
    a pre-built buffer containing parcels B

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

An application that uses Buffer Mode is responsible for setting the Keep-response option and Response Buffer Size options consistent with the response parcel provided in the pre-built request buffer. If any of the request parcels have the alternate parcel header then any of the response parcels may also have the alternate header. If the response requires use of the alternate header because the size of the parcel body will exceed 65535 bytes, then at least one of the request parcels built by the application must use the alternate header.

The parcels included are sent to Teradata Database. The application is responsible for building the parcel as demanded by the protocol being used.

This option is used by some of the defined protocols of Teradata, such as FastLoad, Hut, and MultiLoad. It is not recommended for use in Teradata sessions.

Varying-length-request Mode is supported with either Request-mode.

Request-mode is read by the call to DBCHCL for the connect and runstartup options and stored in the appropriate control blocks, but it is not used during either function.