IBM Support

Updates to IBM® DB2® Utilities Enhancement Tool for z/OS® V2.2 User's Guide (SC19-3417-04)

Product Documentation


Abstract

Updates that apply to IBM® DB2® Utilities Enhancement Tool for z/OS® V2.2 User's Guide (SC19-3417-04)

Content

The most recent update is listed first.





Update 2
Date of change: November 10, 2015
Topics:
1. "What's new"
2. "Messages"

1. "What's new"
DB2 UET now detects when a DB2 subsystem starts if the SSID is referenced by a DB2 UET policy. Messages ABPS0607I, ABPS0608W, and ABPS0609I were added for this enhancement. Messages ABPS0607I, ABPS0608W, and ABPS0609I support this enhancement.

2. "Messages"
Add messages as follows:

ABPS0607I TCB: <tcb_address>, DB2 subsystem <db2_ssid>, startup detected.
    Explanation: The DB2 Utilities Enhancement Tool started task detected that a DB2 system that is referenced in the policy has started.

    User response: No action is required.


ABPS0608W TCB: <tcb_address>: Count of DB2 systems exceeds 256. Startup detection disabled for SSID <db2_ssid>.
    Explanation: The DB2 Utilities Enhancement Tool started task detected that the number of DB2 subsystems referenced by the policy exceeds the maximum of 256.

    User response: Refine the policy to reduce the number of referenced DB2 subsystems.


ABPS0609I TCB: <tcb_address>: DB2 system <db2_ssid> is the primary subsystem for this instance.
    Explanation: The DB2 Utilities Enhancement Tool started task is using the DB2 system as its primary subsystem. All log and audit records are inserted using the connection established for this DB2. If this DB2 system is stopped while the DB2 Utilities Enhancement Tool started task is running, the started task will terminate.

    User response: No action is required.





Update 1
Date of change: October, 2015
Topics:


Topic: "What's new"

Enhancements to processing with the SHRLEVEL REFERENCE and IFDISCARDS extended syntax options
for the DB2 LOAD utility are as follows. For more information, see "Loading a table space in RO access mode (SHRLEVEL REFERENCE option)" and "Validating records before committing changes (IFDISCARDS option)".

- To prevent RESOURCE UNAVAILABLE errors when two or more LOAD utilities run simultaneously
against different partitions of the same partitioned table space, the option
DSNUTILB_RETRY_COUNT was added to the options module. You set the value for "DB2 utility count"
on the Tools Customizer panel "Product Parameters." The option controls the number of times
that DB2 UET retries running the REPAIR utility before timing out.

- When the SHRLEVEL REFERENCE or IFDISCARDS option is specified for the DB2 LOAD utility, during processing the
production object is placed in read only (RO) status. However, DB2 still allows DDL to be
executed against the production object. When the LOAD utility has completed, DB2 UET checks the
table’s DDL in the DB2 catalog to verify that the production object did not change while the
LOAD utility executed on the shadow object. If DB2 UET detects a change in the table’s
definition, it stops processing against the shadow object and issues a message to indicate that
the production object’s definition changed. To support this enhancement, column ALTEREDTS was
added to table ABPTABLES in table space ABPPRETB.

If you enable this enhancement in an existing installation via PTF, complete the following
steps to drop and recreate the table space and table with the added column.

1. Run Tools Customizer.
2. On panel "Product Parameters", select the following items to generate job ABPOBJAL:
- Step "Create customized DB2 UET jobs."
- Task "Update existing DB2 UET objects."
3. Submit job ABPOBJAL.

- DB2 UET provides improved processing of compressed image copies and inline copies to tape.
DB2 UET detects that an inline image copy is present within the LOAD utility syntax and removes
the syntax for the inline image copy. The LOAD utility runs on the shadow object as normal. DB2
UET then runs a full image copy against the shadow object as a separate utility step. This
process enables the image copies to be either allocated to tape or allocated to compressed DASD
packs.

- Enhanced table versioning checks are as follows when you specify the SHRLEVEL REFERENCE or
IFDISCARDS option:
* When you specify LOAD REPLACE and
- All partitions, or the object is nonpartitioned: DB2 UET continues to load the table
space and no expanded versioning checks are required.

- A subset of partitions: DB2 UET performs a check to determine whether the non-loaded
partitions were altered since the last reorganization. If some non-loaded partitions were
altered but not reorganized, DB2 UET stops processing and issues a message to indicate that
partitions should be reorganized. You must reorganize the partitions that are not being loaded.

* When you specify LOAD RESUME and a subset of partitions, DB2 UET performs a check on
all partitions. If partitions were altered since the last reorganization, DB2 UET stops
processing and issues a message to indicate that partitions should be reorganized. You must
reorganize all partitions.

* If the versioning requirements described in this section are met, DB2 UET internally
accommodates table versioning by performing a versioning ALTER on the shadow object to bring it
to the current version.

Options for the DFSMSdss COPY command were added for SHRLEVEL REFERENCE processing:
- FCTOPPRCP: The value for this option is gathered from ZPARM parameter FLASHCOPY PPRC.
- FASTREP: The value for this option is gathered from the options module option
COPY_FASTREP.
- DEBUG: The value for this option is gathered from the options module option
COPY_DEBUG.

A message is issued to display the output of the DFSMSdss COPY command.

DB2 APAR PI08421 provided the DB2 LOAD utility with the parameter BACKOUT YES, which determines
the action to be taken if data rows are found in violation during the data validation phase.
DB2 UET runs the LOAD REPLACE SHRLEVEL REFERENCE extended functionality on a shadow object,
which is a copy of the production object. Since BACKOUT YES is not necessary to run on a shadow
object, DB2 UET now detects this parameter and stops the LOAD utility. A message is issued to
explain the incompatibility of this parameter with SHRLEVEL REFERENCE.

DB2 UET has improved ability to estimate available memory for multiple, simultaneous DFSMSdss
copy tasks. This improvement reduces the need for you to manually specify the DSCOPY_LIMIT
parameter.


Topic: "What does DB2 UET do?"
Add the following statement:
DB2 UET only supports the syntax structure of the utility commands as they are documented in
the DB2 for z/OS Utility Guide and Reference.


Topic: "Set up your environment prior to customization"
Update minimum software requirements as follows:

Ensure that you are using one of the following versions of DB2 for z/OS:
DB2 V10
This is the minimum version that supports all DB2 UET features.

DB2 V10 (5605-DB2)
DB2 Value Unit Edition V10.1 (5697-P31)

Required maintenance:

APAR PM93789
APAR UI28994

DB2 V11

DB2 V11 (5615-DB2)
DB2 Value Unit Edition V11.1 (5697-P43)

Required maintenance: APAR UI28995


Ensure that you are using a supported version of the following software:
- IBM Tools Base for z/OS V01.04.00 (5655-V93) or later

To use the SHRLEVEL REFERENCE extended syntax option, ensure that you have applied the DB2 COPY
utility APAR PI43298.



Topic: "Worksheets: Gathering parameter values for Tools Customizer"
Add parameters as follows:

COPY command FASTREPLICATION keyword

Specifies whether the use of DFSMSdss fast replication (FlashCopy®) is preferred, required, or
not to be used. The value specified for this option does not affect concurrent copy or virtual
concurrent copy processing. Valid values are as follows:

- PREFERRED specifies that you want to use a fast replication method, if possible. If fast
replication cannot be used, DFSMSdss completes the operation using traditional data movement
methods.

- REQUIRED specifies that fast replication must be used. DFSMSdss stops processing the current
data set if fast replication cannot be used. However, DFSMSdss continues processing the rest of
the data sets using fast replication. When the DEBUG(FRMSG(MIN|SUM|DTL)) keyword is not
specified, DFSMSdss still
issues summarized information regarding why a fast replication method cannot be used as though
DEBUG(FRMSG(SUMMARIZED)) had been specified. The DEBUG(FRMSG(MIN | SUM | DTL)) keyword
determines the amount of information provided for why you cannot use a fast replication method.

- NONE specifies that fast replication should not be used. DFSMSdss does not attempt to use
fast replication and
completes the operation using traditional data movement methods.

For more information about FASTREPLICATION, see the explanation of COPY command keywords in the
IBM z/OS DFSMSdss Storage Administration documentation.

Discovered? Yes
Default value: PREFERRED


COPY command DEBUG keyword

Specifies whether you want to use DEBUG as a diagnostic tool. The value for this field can be
detected by the DISCOVER EXEC. Valid values are as follows:

- NONE: DEBUG is not used.

- FRMSG: DFSMSdss issues messages that explain why you cannot use fast replication or Preserve
Mirror operation
during COPY processing. Specify DEBUG(FRMSG) with one of the following sub-keywords:
* FRMSG(MINIMAL): DFSMSdss issues a message with a minimal level of information.
* FRMSG(SUMMARIZED): DFSMSdss issues an informational message with summary information.
* FRMSG(DETAILED): DFSMSdss issues a message with detailed information When applicable,
detailed information
regarding ineligible volumes is provided in the message text.

- SMSMSG: DFSMSdss displays ACS WRITE statements to the job output.

For more information about DEBUG, see the explanation of COPY command keywords in the IBM z/OS
DFSMSdss
Storage Administration documentation.

Discovered? Yes
Default value: NONE


DB2 utility count

Specifies the number of times that DB2 UET retries running the REPAIR utility on a production
object during SHRLEVEL REFERENCE processing. Valid values are in the range 0 - 100. The value
0 is treated as 1.

Discovered? Yes
Default value: 100


Topic: "Validating records before committing changes (IFDISCARDS option)"
Update processing steps and usage considerations and restrictions.
Refer to the following PDF for details:
Update_1_revised_chapters.pdf


Topic: "Loading a table space in RO access mode (SHRLEVEL REFERENCE option)"
Update processing steps and usage considerations and restrictions; add information for using
DFSMSdss COPY options.
Refer to the following PDF for details:
Update_1_revised_chapters.pdfUpdate_1_revised_chapters.pdf


Topic: "Stopping the started task"
Add prerequisite as follows:

Before you begin

Before stopping the started task, make sure that no DB2 utilities are running that use the
started task. Stopping the started task when a DB2 utility is running will cause the utility
job to end with return code 8. To list information on currently active sessions, issue the
DISPLAY SESSIONS command as described in Console
commands for the started task.


Topics: "Basic JCL statements", "Descriptions of global parameters", "Examples of thread-cancel and thread-blocker job steps"
Add single quotation marks to all occurrences of the PARM value variable, as follows:

To implement a thread-blocker action, you must add a PARM to the EXEC statement as follows:
//EXECABP EXEC PGM=ABPBMAIN,REGION=0M,DYNAMNBR=1000,
// PARM=’blocker_id,action’



Topic: "Setting up the initialization options member"
Add option to the example abpidOPTS member:

DSNUTILB_RETRY_COUNT="100"


Topic: "Messages"
Add messages as follows:

ABPU5355E SYSREC <sysrec_name> was specified but no TEMPLATE or job step allocation was found.

Explanation: The utility statement syntax specified SYSREC but the name did not match any TEMPLATE or job step allocation.

User response: Provide a TEMPLATE or DD statement that matches the SYSREC name specified in
the utility syntax.


ABPU5552I <copy_output>

Explanation: COPY command output is displayed.

User response: No action is required.


ABPU5553E Table space <tablespace_name> is a simple table space. Simple table spaces are not supported.

Explanation: If a table space is neither segmented nor partitioned, and it is not a LOB table space, DB2 Utilities Enhancement Tool considers it a simple table space. Simple table spaces are not supported when you specify SHRLEVEL REFERENCE or IFDISCARDS.

User response: Specify another table space for the load job.

ABPU5556E Partition <partition_number> should be reorganized. Explanation: DB2 Utilities Enhancement Tool has detected that an alter has been performed on the specified partition
since the last REORG utility was run. To make sure that the version is reset, run another REORG utility on the table space. User response: Run a DB2 REORG utility on the specified partition before running the DB2 LOAD utility with the extended syntax. ABPU5557E The required DB2 PTF <ptf_number> is not applied.

Explanation: When image copies are requested to be taken during the LOAD process, the DB2 Utilities Enhancement Tool prevalidation feature (part of processing when you specify SHRLEVEL REFERENCE or IFDISCARDS), requires the following DB2 PTFs:
- DB2 10: UI28994
- DB2 11: UI28995

User response: Apply the required DB2 PTF for the version of DB2 that you are running.

ABPU5559I Secondary LOAD utility with empty input file issued to create data sets for DEFINE NO.

Explanation: A secondary LOAD should be called for a DEFINE NO table space when you specify either the IFDISCARDS extended syntax option or the SHRLEVEL REFERENCE extended syntax option.

User response: No action is required.


ABPU5560I Secondary LOAD finished.

Explanation: A secondary LOAD should be called for a DEFINE NO table space when you specify either the IFDISCARDS extended syntax option or the SHRLEVEL REFERENCE extended syntax option.

User response: No action is required.

Publication Number

SC19-3417-04

Related Information

[{"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"DB2 Utilities Enhancement Tool","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021

UID

swg27038584