Updates to DB2 Automation Tool V4.1 User's Guide

Manual


Abstract

Updates that apply to DB2® Automation Tool Version for z/OS® 4.1 User's Guide (SC19-2752-02)

Content

The most recent update is listed first.




Update 3
Date of change: 5/7/2014
Topic: Messages
Change description: The following message was changed for APAR PI07676.

HAAB366W Group Parts By for utility detected. However, PARALLEL NO was specified or ZPARM REORG_LIST_PROCESSING is SERIAL | Group Parts By for utility detected. However, LISTPARTS 1 was specified | Group Parts By for utility detected. However, LISTPARTS is blank and ZPARM REORG_LIST_PROCESSING is SERIAL

Explanation: Group Partitions By job or step was specified in a utility profile, but one of the following is true:

  • The functionality will be limited due to the maximum number of list partitions that were specified.
  • Group Partitions by has been turned off for one of the following reasons. The reason is displayed in the message text.
    • DB2 V8 | V9 LISTDEF does not support more than one PARTLEVEL number
    • PARALLEL NO was specified or ZPARM REORG_LIST_PROCESSING is SERIAL
    • LISTPARTS 1 was specified
    • LISTPARTS is blank and ZPARM REORG_LIST_PROCESSING is SERIAL
The following text may appear in conjunction with the message text to provide additional information:

    parameter overrides Grouping of partitioned objects.

where parameter can be LISTDEF, LISTPARTS, or PARALLEL NO. If LISTPARTS or PARALLEL NO, grouping of objects will be performed but DB2 will process those objects serially.

User response: No response is required. Processing continues; however, Group By Partitions may be disabled or limited depending on the conditions.




Update 2
Date of change: 5/7/2014
Topic: Messages
Change description: The following messages were changed or added for APAR PI11278.

Message HAAB524W has been changed from a warning to an error message. The new message is as follows:

HAAB524E space_type creator|database space_name partition_number LOB validation failed for this TS. Incomplete LOB related TS set. Object excluded for REORG utility

Explanation: Dependency checking failed for the object listed in the message. Either the dependent table space or the base table space for the listed LOB was not found. The object is excluded from processing.

User response: Ensure that if one member of a LOB referentially related table space set is present in the object profile, all members in that set are present.

The following new message was added:

HAAB213I Severity of HAAB524 message has been overridden to Info | Warning

Explanation: The severity of the HAAB524E message has been manually overridden to either an informational message or a warning message (as stated in the message text).

User Response: No action is required.





Update 1
Date of change: 5/7/2014
Topic: DB2 version migration considerations
Change description: The following topics replace the topic titled “DB2 version migration considerations”:

DB2 version migration and fallback
When a DB2 subsystem that is being used with DB2 Automation Tool is migrated to a later version, or must be reverted to a prior version, follow these steps.

After your subsystem has been migrated to a later version of DB2, you can port your repository statistics to the new subsystem. For example, you can port the statistics repository from a DB2 V9 subsystem to a DB2 V10 subsystem. Information about migration is also provided in this topic.

DB2 version migration and fallback instructions
These steps must be performed when a DB2 subsystem that has been customized for use with DB2 Automation Tool is migrated to a later DB2 version, or must be reverted to a previous DB2 version.



Publication number

SC19-2752-02

Copyright date

1996, 2014

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
DB2 Automation Tool

Software version:

4.1.0

Operating system(s):

z/OS

Reference #:

7023537

Modified date:

2014-05-07

Translate my page

Machine Translation

Content navigation