Parcel-mode-fetch is a one byte field that specifies whether fetches are to provide the next parcel or the next buffer full of returned data.
|In this language...||The variable name for Parcel-mode-fetch is...|
|This routine...||Does this for Parcel-mode-fetch...|
|DBCHCL||reads (CON; RSUP; IRQ; IWPF; CMD; CRQ)|
|Parcel-mode-fetch is used by...||To...|
Buffer Mode is not allowed with either Varying-length-fetch or Move Mode (that is, Move Mode can only move one parcel at a time).
If buffer Mode is in effect, each fetch results in a new buffer full of parcels. It is assumed that the application has processed the previous buffer full of parcels. Whether any of the parcels have the alternate header depends upon the Request-mode and Request-parcel-format options. To prevent an unexpected alternate parcel header in a returned buffer, CLIv2 will not use the alternate header if Request-mode=P and Parcel-mode-fetch=N are both specified. After the application is adjusted to support the alternate header in a response buffer, Request-parcel-format=A may be specified to allow CLIv2 to use the alternate header if possible.
Parcel-mode-fetch is initialized by DBCHINI to the default value provided for Parcel Mode in the HSHSPB. If the value provided is not appropriate for the application, the program may set Change-options to Y and change Parcel-mode-fetch to either of the following:
|If...||Then set Parcel Mode to...|
|the application wants each fetch to provide the next parcel||Y|
|the application wants each fetch to provide the next buffer full of parcels||N|
- Initiate with Protocol-function
- Initiate Request
Use mnemonics for the codes. Mnemonics are provided in the language definition file for the DBCAREA.