Request-parcel-format specifies whether CLIv2 uses alternate parcel headers to build request parcels when supported by the database.
The following table describes the Request-parcel-format variable.
| In this language... | The variable name for Request-parcel-format is... |
|---|---|
| COBOL | DBRIRPF |
| PL/I | DBRIRPF |
| C, C++ | dbriRPF |
| IBM Assembler | DBRIRPF |
| This routine... | Does this for Request-parcel-format... |
|---|---|
| DBCHINI | writes |
| DBCHCL | reads (CON; RSUP; IRQ; IWPF) |
| Request-parcel-format is used by... | To... |
|---|---|
| applications | write |
Set one of the following values before calling the Fetch function:
| If Request-parcel-format is set to... | Then Request-parcel-format... |
|---|---|
| 'A' | allows CLIv2 to use whichever parcel header is supported by Teradat8a Database. |
| 'D' | ('D' is a deprecated value now treated as 'A') |
| 'O' | forces use of original parcel headers |
- For new applications, Request-parcel-format should always be set to ‘A‘.
- Use mnemonics for the codes. Mnemonics are provided in the language definition file for the DBCAREA.