Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see LOADPLUS for DB2 13.1.

Load jobs that invoke DSNUTILB

LOADPLUS enables certain features by invoking DSNUTILB. This topic describes considerations that apply when LOADPLUS invokes DSNUTILB.

Important

LOADPLUS invokes DSNUTILB to enable new features quickly. LOADPLUS generally will provide native support for these features (without invoking DSNUTILB) in a later version of the product or via PTF. You cannot use the DSNUTILB option (or any other option) to request that LOADPLUS invoke DSNUTILB for a feature that LOADPLUS supports natively.

Related topics

Operational-considerations

Enabling-LOADPLUS-to-invoke-DSNUTILB

Example 22 — Running a DSNUTILB load

LOADPLUS features that require DSNUTILB

For this version, LOADPLUS invokes DSNUTILB to enable loading data when any of the following conditions exist:

  • Participating indexes contain a key derived from certain expressions.

    LOADPLUS natively supports some indexes on expression. For more information, see Indexes-on-expression.

  • Participating indexes contain keys with random ordering.
  • Participating indexes are defined with EXCLUDE NULL KEYS.
  • You are loading a table that is defined as ORGANIZE BY HASH.
  • You are loading a temporal table and the following conditions exist:
    • You specify INDEX UPDATE.
    • A participating index is defined with BUSINESS_TIME WITHOUT OVERLAPS.
    • Any SHRLEVEL value is in effect except SHRLEVEL CHANGE SQLAPPLY.
  • You are loading a table that contains columns that are defined with a CCSID specification.
  • You are loading LOB or XML data in either of the following cases:
    • You are running an SQLAPPLY load.
    • You are running a two-phase load (PRELOAD CONTINUE).
  • You are loading LOB data in any of the following cases:
    • You are loading a partition-by-growth table space.
    • You are loading from a referenced file of a different type than the column type (for example, from a BLOB-referenced file to a CLOB column).
  • You are loading XML data in any of the following cases:
    • You are loading XML data from a DBCLOB-referenced file.
    • You are loading an XML column that is defined with an XML schema.
    • You are loading a table that contains a user-defined XML index, and the index is defined with DEFINE NO and is not yet materialized.
  • You are performing certain data translations. For more information, see Data-translation.

  • (SPE2104

    ) You are loading LOB tablespace with compression

  • (SPE2104

    ) You are loading a table with an INDEX with DECFLOAT column

  • (BMC.DB2.SPE2204)

    If the table space is a partition-by-range (PBR) relative page number (RPN) table space and one of the following conditions exists:

    • The table contains a lob column.
    • The table contains an XML column.
    • The table contains a compression on any Index.
  • (BMC.DB2.SPE2210)  Table spaces that contain a mixture of fixed length and Huffman compression across the partitions.

General restrictions for a DSNUTILB load

The following general restrictions apply when running a DSNUTILB load:

  • LOADPLUS invokes DSNUTILB after the UTILINIT phase. Therefore, most of the processing that LOADPLUS normally does to validate, load, and copy your data is handled by the IBM Db2 LOAD utility for these jobs. Functionality is limited to those features that are available in the Db2 LOAD utility.
  • If any table in the table space that you are loading (regardless of whether you are loading that table) uses a feature that LOADPLUS supports via DSNUTILB, LOADPLUS invokes DSNUTILB for that load job.
  • Do not specify FREE=CLOSE for your SYSPRINT data set.
  • LOADPLUS ignores any SYSPRIN2 DD statement in your JCL.

This section includes the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*