PACK
Purpose
The PACK command enables the ability to send multiple IMPORT data file records with an SQL request. BTEQ uses this factor to indicate an upper limit when determining how many records to pack into the USING Data buffer sent with the SQL request.
Syntax
where
|
Syntax Element |
Specification |
|
n |
An integer in the range of 0.999900. 0 is the default value. Zero means that use of a PACK factor has not been specified, and PACK statistics are not generated for the import. Note: Entering an invalid n value prompts the following error message: *** Error: Pack factor value must be in the 0.999900 range. |
Usage Notes
The pack factor is reducible to prevent a USING data buffer overflow. BTEQ packs as many records into the request buffers as will fit. To prevent CLI buffer overflow errors, BTEQ considers both the upper limit, indicated by the pack factor, and CLI's maximum message size. When a pack factor is used, statistics are created for the average and largest factor used as part of the summary messages for the request's result.
A pack factor is established by using the PACK command or by using a PACK clause for the REPEAT command. See “REPEAT” on page 266 for more information about the REPEAT command.
Note: Large pack factors should be used judiciously. A significant amount of memory is allocated for the associated underlying data pointers, which might require advance planning, particularly for z/OS BTEQ use. Also consider the underlying multi-data-parcel protocol limits imposed by the DBS as well as CLI, which can further constrain the usability of a large pack factor. The PACK factor setting is ignored if the database being used does not support iterated requests.