Updates to DB2 High Performance Unload for z/OS, Version 4.1

Product documentation


Abstract

Updates that apply to DB2® High Performance Unload for z/OS®, Version 4.1 User's Guide (SC19-3169-02)

Content



Update 5
Date of change: February 10, 2012
Topic: DB2 HPU output data parameters
Change description:The following subparameter has been added to the VUU030/ULOPTNS PARMLIB parameter:

GBLPARAL_MAXPART_SET_NULL(YES) or GBLPARAL_MAXPART_SET_NULL(NO)
Processing subsets of partitions (when you use MAXPART or ULMAXPAR when the specified value is less than the number of partitioned to be unloaded) and unloading without parallelism because GBLPARAL (NO) is specified are incompatible.

When VUU060/ULMAXPAR n and VUU036/GBLPARAL NO are specified together and are applicable to the unload in progress, GBLPARAL NO is ignored, and the data is unloaded without parallelism at the partition level unless GBLPARAL_MAXPART_SET_NULL(YES) is specified.

Specify GBLPARAL_MAXPART_SET_NULL(YES) to disable the processing of the subset of partitions and unload the data without partition parallelism instead. If you specify either the PARALLELISM or the MAXPART keyword in the UNLOAD statement, specifying GBLPARAL_MAXPART_SET_NULL(YES) does not affect parallelism.




Update 4
Date of change: February 10, 2012
Topic: DB2 HPU messages
Change description:The following message has been added:

INZU244I IN SELECT STARTING AT ( line , col ) TABLESPACE dbname . tsname MAXPART OPTION IS SET TO 0 DUE TO GBLPARAL_MAXPART_SET_NULL(YES) IN VUU030/ULOPTNS PARMLIB VARIABLE

Explanation: The value of the VUU060/ULMAXPAR was ignored because GBLPARAL_MAXPART_SET_NULL(YES) was specified for VUU030/ULOPTNS. The value is ignored only for the indicated unload.
User response: If you want to use the ULMAXPAR setting, consider removing the GBLPARAL_MAXPART_SET_NULL(YES) specification or add the MAXPART option to your UNLOAD statement.
Return code: 0




Update 3
Date of change: February 10, 2012
Topic: OPTIONS block syntax and description
Change description: In the TEMPLATESET description, the following line:

When the variables do not apply :COLNUM and :SELNUM are set to 00000, :RECNUM is set to 0000000, and :COLNAME is set to UNKNOWN.

has been changed to the following description:

When these variables cannot be evaluated, :COLNUM and :SELNUM are set to 00000; :RECNUM is set to 0000000; and :COLNAME is set to COL n, where n is a sequential number. This sequential number ensures unity, but it does not have a specific meaning regarding the actual database or the table space that it represents.




Update 2
Date of change: February 10, 2012
Topic: TEMPLATE block syntax and description
Change description: In the Notes section, the following line:
    The &DB, &TS, and &SN variables are set to UNKNOWN.

has been changed to the following description:
    The &DB, &TS, and &SN variables are set to DB n, TS n, LOB n or XML n, depending on the table space type, where n is a sequential number. This sequential number ensures unity, but it does not have a specific meaning regarding the actual database or the table space that it represents.




Update 1
Date of change: November 18, 2011
Topic: DB2 HPU output data parameters
Change description: The following parameter is added in APAR PM35959:

* SPECIFIES THAT A CHARACTER STRING CONSTANT IS UNLOADED AS A CHAR OR
* VARCHAR VALUE IN NATIVE MODE.
* CAUTION : WHEN THE SELECT IS PROCESSED BY DB2, A CHARACTER STRING
* CONSTANT IS UNLOADED AS A VARCHAR VALUE, SO TO MAINTAIN THE SAME
* OUTPUT FORMAT, IT IS RECOMMENDED TO SPECIFY VARCHAR.
* NOTE : SPECIFYING CHAR HAS NO EFFECT ON OUTPUT IF THE STRICT OPTION
* OF DSNTIAUL FORMAT IS REQUESTED.
* TO GET STRING CONSTANTS HANDLED AS CHAR DATA WHEN THE DNSTIAUL
* FORMAT IS REQUESTED, MAKE SURE THE STRICT OPTION IS NOT USED EITHER
* BY SPECIFYING DSNTIAUL STRICT IN THE UNLOAD COMMAND OR DSNTIAUL
* STRICT IN THE INZTVAR MEMBER.
* MANDATORY : NO
* ALLOWED VALUE(S) : CHAR/VARCHAR
* DEFAULT VALUE : CHAR
  VUU064 STRNGCST CHAR

VUU064/STRNGCST
This parameter is optional. It specifies whether string constants in the SELECT statements are handled as CHAR or VARCHAR data when the SELECT statement is processed in native mode.

CHAR
The string constants are handled as CHAR data unless the DSNTIAUL STRICT format is requested either by specifying DSNTIAULSTRICT(NO) as a subparameter of the ULOPTNS INZTVAR parameter or by using the FORMAT DSNTIAUL STRICT option in the UNLOAD command. When you specify CHAR, the output for expressions that have string constants might depend on whether the unload is performed in native or in SQL mode.

VARCHAR
The string constants are handled as VARCHAR data. When you specify VARCHAR, the output for expressions that have string constants does not depend on whether the unload is processed in native or in SQL mode. Consider specifying VARCHAR for unloads that use the DB2 YES option.

Important: If some of your processes use strings that are handled as CHAR data when DB2 HPU processes the unload in native mode, use the default value. Otherwise, specify VARCHAR to ensure that the output of the unload for expressions that have string constants do not depend on the processing mode of the unload.

If you want to specify VARCHAR so that string constants are processed as VARCHAR data in native mode or SQL mode but you have some jobs that expect string constants to be processed as CHAR data, consider changing the SELECT statements for these unloads by replacing any string constant string_constantt with CHAR( string_constant).

The default value is CHAR.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Tools for z/OS
DB2 High Performance Unload

Software version:

4.1.0

Operating system(s):

z/OS

Reference #:

7020561

Modified date:

2011-05-20

Translate my page

Machine Translation

Content navigation