The setting of the Variable-length-request option affects the setting of the following:
- Logon-pointer
- Logon-length
- Mechanism-data-ptr
- Mechanism-data-length
- Run-pointer
- Run-length
- Request-pointer
- Request-length
- Session-desc-pointer
- Session-desc-length
- USING-data-pointer
- USING-data-length
- Workload-pointer
- Workload-length
| Setting | Result |
|---|---|
| N | The xxxx_pointer contains the starting address of the actual logon string, run string, Teradata SQL request, or using data. The xxxx_length is set to the length of the corresponding data. |
| Y | The xxxx_pointer contains the address of a two-byte length, which must immediately precede the actual text or data. The length provided measures only the length of the text or data and does not include the two bytes of its own length. The xxxx_length field is ignored. |
If the Maximum-parcel option is set to H, then the two-byte length is considered to be an unsigned value. Because PL/I does not support unsigned integers, you cannot use the Variable-length-request option to allow the PL/I VARYING attribute for the Request-pointer or the USING-data-pointer for requests greater than 32767.
Since the maximum value that can be contained in the two-byte length is 65535, larger lengths cannot use Variable-length-request.