2024 new-function APARs for Db2 Admin Tool 13.1
The following APARs were delivered in 2024. They introduced enhancements to Db2 Admin Tool 13.1 since the General Availability (GA) date.
Db2 13 FL506: Support for non-disruptive clearing of data partitions with LOAD
PH63985, PH63986 - November, 2024
Db2 13 FL 506 Db2 13 function level 506 introduced the NOKEYDELETE option for the LOAD utility to improve the elapsed time and availability when emptying data partitions by using an empty input data set. NOKEYDELETE postpones the deletion of key entries from the associated logical partition of the nonpartitioned secondary index (NPSI).
Db2 Admin Tool supports this new keyword. You can specify it on the Specify Utility Options - LOAD (ADB2UTC) panel:
ADB2UTC n ------------- DD1A Specify Utility Options - LOAD ------------- 18:36
Command ===>
Execute utility on table ELACZ.TBTEST1
using the following options:
Utility ID . . . . . LOAD01
Unloaded data . . . <DUMMY>
Unloaded how? . . . U (U - Unload utility, R - Reorg utility)
Table/Col info . . .
PART . . . . . . . . 1 (1-4)
...
INDEXDEFER . . . . . NPI (A - ALL, N - NPI, NO - NONE)
NONUNIQUE . . . . (Yes/No)
NOKEYDELETE . . . YES (Yes/No)
...
When you run LOAD to empty partitions by specifying <DUMMY> in the Unloaded data field, Db2 Admin Tool can optionally unload the partition or table before emptying it so that you have a backup of the data. You will be prompted whether you want this unload.
If you also specify NOKEYDELETE when emptying a partition, Db2 Admin Tool can optionally generate a REORG INDEX operation to clear the resulting REBUILD-pending empty (RBDPM) status on the logical partitions of the NPSI. Again, you will be prompted as to whether you want this REORG operation generated.
The new RBDPM status can also be cleared by using the REPAIR utility. To perform this operation in Db2 Admin Tool, use the Specify Utility Options - REPAIR INDEX (ADB2UXN) panel:
ADB2UXN n DD1A Specify Utility Options - REPAIR INDEX 13:27
Option ===>
Execute utility on index SYSIBM.DSNACX01
using the following options:
More: +
1 - Reset COPY-pending status (NOCOPYPEND)
2 - Reset RECOVER-pending status (NORCVRPEND)
3 - Reset REBUILD-pending status (NORBDPEND)
3E – Reset REBUILD-pending empty status (NORBDPM)
3P - Set PAGE SET REBUILD-pending status (PSRBDPEND)
3S - Set REBUILD-pending status (RBDPEND)
4 - Reset CHECK-pending status (NOCHECKPEND)
5 - Reset Advisory REORG-pending (AREOR) (NOAREORPEND)
6 - Reset Advisory REORG-pending (AREO*) (NOAREORPENDSTAR)
8 - Validate CATALOG
TEST . . . . . . . . . . (Yes/No)
9 - Locate data that is to be repaired
PAGE . . . . . . . . . . Decimal or hex (D/H)
VERIFY . . . . . . . . . (Yes/No)
OFFSET . . . . . . . . Decimal or hex (D/H)
DATA byte-string . . .
DATA char-string . . .
DUMP . . . . . . . . . . (Yes/No)
DUMP . . . . . . . . . . (Yes/No)
OFFSET . . . . . . . . Decimal or hex (D/H)
LENGTH . . . . . . . . Decimal or hex (D/H)
PAGES . . . . . . . . *, decimal or hex (D/H)
REPLACE . . . . . . . . (Yes/No)
OFFSET . . . . . . . . Decimal or hex (D/H)
DATA byte-string . . .
DATA char-string . . .
RESET . . . . . . . . (Yes/No)
SHRLEVEL CHANGE . . . . (Yes/No)
Repair Utility options:
LOG . . . . . . . . . (Yes/No)
CLONE . . . . . . . . (Yes/No) As with any use of REPAIR, run REPAIR SET with caution.
Support for loading partitions
PH63985, PH63986 - November, 2024
When you run the LOAD utility in Db2 Admin Tool, you now specify an individual partition instead of the entire table. To do so, specify the PART option:
ADB2UTC n ------------- DD1A Specify Utility Options - LOAD ------------- 18:36
Command ===>
Execute utility on table ELACZ.TBTEST1
using the following options:
Utility ID . . . . . LOAD01
Unloaded data . . . <DUMMY>
Unloaded how? . . . U (U - Unload utility, R - Reorg utility)
Table/Col info . . .
PART . . . . . . . . 2 (1-4)
...
UPDMAXASSIGNEDVAL . (Yes/No)
FORCE . . . . . . . (N - NONE, R - READERS, A - ALL)
DEFINEAUX . . . . . (Yes/No)
KEEP EMPTY PAGES . . (Yes/No)
COPYDICTIONARY . . . (1-4)
Notice that this panel also now supports the LOAD options that are relevant only when PART is specified: KEEP_EMPTY_PAGES and COPYDICTIONARY.
Db2 13 FL506: Support for multi-row INSERT
PH63985, PH63986 - November, 2024
Db2 13 FL 506 Db2 13 function level 506 introduced the capability to specify more than one row in the VALUES form of the INSERT statement. This capability increases portability of applications by adding support in Db2 for z/OS® for syntax that is already supported by Db2 on other platforms. This new INSERT syntax is supported by Db2 Admin Tool.
Ability to specify utility templates and other CM batch options for multi-target changes
PH63146 - November, 2024
You can use the Change Management (CM) feature of Db2 Admin Tool to make a multi-target change, or a change that can be imported to multiple target systems. For these multi-target changes, you can now specify utility templates and other CM batch options, such as utility options, when you analyze the change by using the ANO line command. To do so, use the new Data set for CM batch parms and Data set for templates fields on the Generate Multi-target Analyze Job (ADBPCMTA) panel:
ADBPCMTA ----------------- Generate Multi-target Analyze Job -------------- 13:45
Command ===>
Specify the following for Analyze:
More: +
Base version method . . . . . A
Change reporting options . . Yes (Yes/No)
PDS for WSL . . . . . . . . . DSNB.RUN.WSL
PDS for analyze job . . . . . DSNB.ANALYZE.JCL
Prefix for data sets . . . . SYSADM
Existing data set action . . REPLACE (Conditional, Replace, Stop)
Change tag type . . . . . . . NAME (ID, Name, Owner)
Run SQLID . . . . . . . . . . <NONE> (Blank, a SQLID, or <NONE>)
Object Grantor . . . . . . . (Blank or a SQLID)
Validate WSL . . . . . . . . YES (Yes/No)
Use utility options . . . . . YES (Yes/No)
Generate templates . . . . . YES (Yes/No)
Authorization Switch ID . . . SYSADM (SQLID to connect, <SQLID> or blank)
SECADM Authorization ID . . . SYSADM (SQLID to connect or blank)
Stop on conversion error. . . YES (Yes/No)
Content of apply job(s) . . . DDL (All, DDL)
Unload method . . . . . . . . P (Unload, Parallel unload, HPU)
Use DEFER YES . . . . . . . . YES (Yes/No)
Allow rotate parts . . . . . NO (Yes/No)
Retain GENERATED ALWAYS:
For ROWID . . . . . . . . . YES (Yes/No)
For ROW CHANGE TIMESTAMP. . YES (Yes/No)
IDENTITY START value . . . . COMPUTED (Original, Computed)
SEQUENCE RESTART value . . . COMPUTED (Original, Computed)
Disable REORG optimization . YES (Yes/No)
Run CHECK DATA . . . . . . . YES (Yes/No)
Take an image copy . . . . . R (after: Reload/Alter/Both/None)
Run REORG/REBUILD . . . . . . M (Mandatory, All relevant, None)
Run RUNSTATS . . . . . . . . R (after: Reload/Alter/Both/Min/None)
Run REBIND . . . . . . . . . M (Mandatory, All relevant, None)
Generate ALL options . . . . (Yes/No, default is NO)
Data set for templates . . .
Data set for CM batch parms .
BP - Change batch job parameters
CO - Change options common to change functions
Use the Data set for CM batch parms field to specify the data set that contains the CM batch parameters that you want added to the generated CM batch job. Use the Data set for templates field to specify the data set that contains the utility templates that you want added to the generated CM batch job. For additional details about these fields, see Analyzing a multi-target change in batch by using panels.
Simplified option selection in Db2 Object Comparison Tool
PH63721 (Db2 Admin Tool), PH63722 (Object Comparison Tool) - October, 2024
Db2 Object Comparison Tool runs as an extension of Db2 Admin Tool. When you use Object Comparison Tool to compare objects, you can specify a number of compare job options on the Generate Compare Jobs (GOC5) panel:
GOC5 ---------------- Generate Compare Jobs ----------------------------------
Command ===>
Specify the following for DB2 Object Comparison Tool:
Worklist information:
Worklist name . . . . . . . PQ76055N (also used as middle qualifier in DSNs)
Compare options:
Suppress DROP of objects . NO (Yes/No)
Drop FKs not in source . . NO (Yes/No)
Suppress DROP of columns . NO (Yes/No)
Suppress adding columns . . NO (Yes/No)
Run SQLID . . . . . . . . . (Blank, an SQLID, or <NONE>)
Object Grantor . . . . . . (Blank or an SQLID)
Run Validate. . . . . . . . V (Validate, None)
Allow implicit drop of
excluded objects . . . . NO (Yes/No)
Enable auth-switching . . . YES (Yes/No)
Disable REORG optimization YES (Yes/No)
Scope Warning Messages . . YES (Yes/No)
Change reporting options . . YES (Yes/No)
Save compare results . . . . YES (Yes/No)
Data set information:
PDS for batch jobs . . . . CMP.PQ76055N
Prefix for data sets . . . NBRON
Changes file data set name.
Member name . . . . . . . (if Changes file is an existing PDS)
Options:
Generate online . . . . . . YES (Yes/No)
Single compare job . . . . NO (Yes/No)
Member name . . . . . . . COMPARE (default COMPARE)
Allow deferred restart . . NO (Yes/No)
Generate apply jobs . . . . YES (Yes, No, or (Delta) Change)
Generate one job. . . . . YES (Yes, No, or (Per) Process)
Member prefix . . . . . APPLY (default APPLY)
As work statement list . YES (Yes/No to append to work stmt list)
Embed IFF into WSL . . NO (Yes/No)
Use customized util opts. YES (Yes/No)
Content of apply job(s) . ALL (All, DDL)
Unload method . . . . . : P (Unload, Parallel unload, HPU)
Generate templates. . . . NO (Yes/No)
Stop on conversion error. NO (Yes/No)
Use DEFER YES . . . . . YES (Yes/No)
Allow rotate parts . . . . YES (Yes/No)
Retain GENERATED ALWAYS:
For ROWID . . . . . . . . YES (Yes/No)
For ROW CHANGE TIMESTAMP. YES (Yes/No)
Retain START and RESTART values:
For sequence object . . . (Yes/No)
IDENTITY START value . . . ORIGINAL (Original, Computed)
Mask ignored fields . . . . NO (Yes/No)
Optional jobs after Reload or Alter:
Run CHECK DATA . . . . YES (Yes/No)
Take an image copy . . R (after: Reload/Alter/Both/None)
Run REORG/REBUILD . . . M (Mandatory, All relevant, None)
Run RUNSTATS . . . . . R (after: Reload/Alter/Both/Min/None)
Run REBIND . . . . . . M (Mandatory, All relevant, None)
REBIND options . . . YES (Yes/No)
BP - Change batch job parameters
TU - Specify TEMPLATE usage
UO - Customize utility options
CO - Change options common to change functions 
To simplify the process of specifying these options, this panel now has a simple display mode, which displays only the essential options that must be specified for the comparison:
GOC5 re -------------------- Generate Compare Jobs ---------------------------
Command ===>
Specify the following for DB2 Object Comparison Tool:
More: +
Worklist information:
Worklist name . . . . . . . GOC1 (also used as middle qualifier in DSNs)
Compare options:
Run SQLID . . . . . . . . . (Blank, an SQLID, or <NONE>)
Change reporting options . . YES (Yes/No)
Data set information:
PDS for jobs . . . . . . . TS6462.GOC.JCL
Prefix for data sets . . . TS6462.GOC
Changes file data set name. TS6462.GOC.CHANGE1
Member name . . . . . . . (if Changes file is an existing PDS)
Options:
Compare job member name . . COMP1 (default COMPARE )
Generate apply jobs . . . . NO (Yes, No, or (Delta) Change)
Generate one job . . . . YES (Yes, No, or (Per) Process)
Member prefix . . . . . APPL1 (default APPLY )
Use customized util opts NO (Yes/No)
Generate templates. . . . YES (Yes/No)
BP - Change batch job parameters
TU - Specify TEMPLATE usage
UO - Customize utility options
CO - Change options common to change functions
ADV - Advanced options You can still view or change other options by switching to the advanced display mode. The advanced display mode includes all compare job options. To toggle between the simple and advanced display modes, use the new SIM and ADV commands. You can also change the display mode in the Db2 Admin Tool display options on the Panel Display Options (ADBPPDO) panel
When you first install Db2 Admin Tool, as a new user, the Generate Compare Jobs (GOC5) panel will be initially displayed in simple display mode. When you upgrade Db2 Admin Tool, this panel will be initially displayed in advanced display mode.
Simplified way to run utilities on all table spaces or indexes in a database
PH63545 - October 2024
In Db2 Admin Tool, you can now use a single line command on the Databases (ADB21D) panel to run a Db2 utility on all table spaces or indexes in a database.
Simply use the catalog navigation feature to navigate to the database that you want. (From the main menu, select option 1 and then option D on the subsequent panel.) On the Databases (ADB21D) panel, specify one of the following new line commands:
- US
- Run a utility on all table spaces within the selected database.
- UX
- Run a utility on all indexes within the selected database.
On the subsequent Table Space Utilities (ADB2US) panel or Index Utilities (ADB2UX) panel, select the utility that you want to run.
Alternatively, you can use one of the following line commands to directly select the utility and skip the Table Space Utilities (ADB2US) panel or Index Utilities (ADB2UX) panel:
- US.C
- Invoke the COPY utility on all table spaces in the selected database.
- US.O
- Invoke the REORG utility on all table spaces in the selected database.
- US.R
- Invoke the RUNSTATS utility on all table spaces in the selected database.
- US.Q
- Invoke the QUIESCE utility on all table spaces in the selected database.
- US.N
- Invoke the REPAIR utility on all table spaces in the selected database.
- UX.C
- Invoke the COPY utility on all indexes in the selected database.
- UX.O
- Invoke the REORG utility on all indexes in the selected database.
- UX.R
- Invoke the RUNSTATS utility on all indexes in the selected database.
- UX.RB
- Invoke the REBUILD INDEX utility on all indexes in the selected database.
- UX.N
- Invoke the REPAIR utility on all indexes in the selected database.
Support for viewing and managing accelerated packages
PH63372 - September, 2024
Accelerated packages are Db2 packages that are bound with the QUERYACCELERATION and GETACCELARCHIVE bind options. Information about these packages is stored in the Db2 table SYSACCEL.SYSACCELERATEDPACKAGES.
You can now view these accelerated packages in Db2 Admin Tool by specifying the new option AK (Display/manage accelerated packages) on the System Administration (ADB2Z) panel. After you enter any optional filtering criteria on the subsequent panel, accelerated package information from SYSACCELERATEDPACKAGES is listed on the Display Accelerated Packages (ADBPZAPK) panel:
ADBPZAPK DD1A Display Accelerated Packages Row 1 to 15 of 15
Command ===> Scroll ===> DATA
More: >
Line commands:
AC - Accelerator K - Package ST - Accelerated statements
DET - Details DEL - Delete ? - Show all line commands
Preferred Q G
Sel Collection Name Accelerator Version T A A
--- ----------------> ----------------> -----------------> -----------> - - -
PN18819X PN18819LONGNAME01 V1 E
KK506504 KK506504 IDAAZ17 V1
TS3483TEST SP521091 V1 N
EMGTEST1 ADB2CON V13.1.0.0000 E
EMGCOL EMGREST2 V6 Y
EMGCOL EMGREST2 V5 Y
EMGCOL EMGREST2 V4 Y
EMGCOL EMGREST2 V3 Y
EMGTEST ADB2CON IDAAZ17 V13.1.0.0000 F Y
EMGCOL EMGREST2 V1 A Y
EMGTEST AKNAME V1
AKCOL AKRES2 IDAAZ17 V1 L N
EMGTEST ADBGMP V13.1.0.0000 L
EMGTEST EMGTEST V13.1.0.0000 E N
KA7COL ADBCMRQ V13.1.0.0000 You can then view additional information about these accelerated packages by using the available line commands or delete a package from SYSACCELERATEDPACKAGES by using the DEL line command.
- When you view the detailed package information by using the DET or BET line commands,
acceleration details are also now included, if applicable. For example, if you use the
DET line command on an accelerated package, the Details for object(s)
(ADBPD) panel includes the following
information:
Acceleration details: Query acceleration behavior . : L - Elligible Data retrieval behavior . . . : Yes - archive data is retrieved Preferred accelerator . . . . : No accelerator specified Acceleration delay . . . . . . : -1.0 - When you view the detailed package information by using the DET or BET line commands, the STATUS and VALID values from SYSPACKSTMT are also listed for each statement, if applicable. VALID is applicable only for Db2 13 or later.
- You can view detailed information about each statement in a package by using the new ST line command. This command displays information from the Db2 catalog table SYSPACKSTMT.
- You can view the collection for a package by using the new L line command.
Db2 Admin Tool also now supports specifying the bind option ACCELERATIONWAITFORDATA on any of the following panels when binding or rebinding packages:
- Bind package (ADB21KB) panel
- Rebind package (ADB21KR) panel
- Bind Rest Service (ADB21RSB) panel
Enhancements to the CAT command
PH62040, PH62041 - September, 2024
You can use the CAT command (or ? for short) from any Db2 Admin Tool panel to navigate the Db2 system catalog. This command is intended as a shortcut for the system catalog feature of Db2 Admin Tool (option 1 on the main menu).
For example, you can use the following command to see a list of table spaces (type S) that begin with TS in database MYDB:
?s MYDB.TS*As a result of this command, those table spaces are displayed on the Table Spaces (ADB21S) panel:
ADB21S in DD1A Table Spaces Row 1 to 12 of 27
Command ===> Scroll ===> DATA
More: >
Commands: GRANT MIG DIS STA STO ALL CT DROP MOVETB
Line commands:
T - Tables D - Database A - Auth G - Storage group ICS - Image copy status
DIS - Display table space STA - Start table space STO - Stop table space
? - Show all line commands
C
Select Name DB Name Parts Bpool L E S I C Tbls Act pages Segsz T L O
* * * * * * * * * * * * * * *
------ -------- -------- ------ ------ - - - - - ----- ----------- ------ - - -
TS1SCFGC MYDB 1 BP0 R N A N Y 1 -1 32 G Y
TS2CFGLS MYDB 0 BP0 A N A N Y 1 -1 0 O Y
TS3SCFGS MYDB 1 BP0 R N A N Y 1 -1 32 G Y This APAR enhances the CAT (or ?) command for all object types. You can now qualify this command with additional search criteria by using the following syntax:
CAT xx [qual.]name[,column oper value]where oper can be =, != ,!< !>, >, >=, <, <=, <>, IN, or NOT IN.
Note that the syntax [,column
oper
value] is new.
Also note that xx is the object option listed on the System Catalog (ADB21) panel, such as G, D, S, T, and K.
For example, the following command returns a list of packages with version V13R1:
?K *.*,VERSION=V13R1And the following command returns the package TS5816.ADB_MT_CHANGE_UPDATE with the given consistency token:
?K TS5816.ADB_MT_CHANGE_UPDATE,CONTOKEN=#HEX(1BA43D1C1C2BF540)Additionally, on the System Catalog (ADB21) panel, you can now specify hexadecimal values in the Value field in the selection criteria. To specify a hexadecimal value on this panel, use the format X'hexstring'.
Ability to generate DDL for hidden ROWID columns
PH63073 (Db2 Admin Tool), PH63074 (Object Comparison Tool) - September, 2024
Previously, when Db2 Admin Tool generated DDL for a table with an implicitly generated ROWID column, the ROWID column was not included in the generated CREATE TABLE statement. With this APAR, you can now specify that you want the generated CREATE TABLE statement to include the ROWID column with the IMPLICITLY HIDDEN attribute. This behavior is useful if you need to replicate tables from one subsystem to another subsystem and ensure that the column definitions are the same.
You can specify that you want these ROWID columns included in the DDL by using the new Generate hidden ROWID columns option on one of the following panels:
- Generate SQL from DB2 catalog (ADB2GENB) panel
- Generate SQL from DB2 catalog (ADBP8MG) panel (when migrating objects)
- Options for Change Functions (ADB2PCO) panel (when comparing objects, altering objects, or using Change Management)
You can also use the new Change Management (CM) batch parameter GENERATE_HIDDEN_ROWID_COLUMNS to specify this behavior.
You can specify that you want the implicitly generated ROWID column to always be included in the CREATE TABLE statement (ALWAYS), to be included only if it is not the last column in the table (ONLY), or to not be included (NO). By default, the ROWID column is not included in the CREATE TABLE statement.
TCz option to separate GRANT statements
PH62395 - August, 2024
- If your shop manages security with an external security tool, GRANT statements do not need to be run during customization. Isolating these statements to a separate job allows you to avoid running them.
- When the Db2 subsystem parameter SEPARATE SECURITY is set to YES, GRANT operations need to be run by a user with SECADM authority. In this case, the new ADBGRANT job can be run by this SECADMN user without requiring that user to run all of the generated TCz jobs.
If you set the new Generate a separate job for security field to YES on the Product Parameters (CCQPPRD) panel, an ADBGRANT job is generated. This new job contains all of the GRANT statements for the requested privileges in Db2 Admin Tool. If the Generate a separate job for security field is set to NO (the default value), the ADBGRANT job is not generated, and the GRANT statements continue to be generated in various existing TCz jobs.
Ability to ignore column order when comparing tables
PH62527 (Db2 Admin Tool), PH62528 (Object Comparison Tool) - August, 2024
When you use Db2 Object Comparison Tool to compare tables, you can now specify that you want column order to be ignored. When column order is not relevant, ignoring it can help minimize any resulting changes. In some cases, where column order is the only difference, no changes will be needed. In other cases, column changes can be made by using ALTER operations rather than dropping and recreating the table.
For example, consider the case where the source table has one more column than the target table and the source table columns are in a different order. If column order is not ignored, the target table will be dropped and recreated to achieve the changes. If column order is ignored, the change can be achieved by an ALTER TABLE statement.
To specify that you want to ignore column order, set the new Change Management batch option IGNORE_COLUMN_ORDER to YES or set the new panel option Ignore source column order to YES on the Options for Change Functions (ADB2PCO) panel:
ADB2PCO n Options for Change Functions 14:19
Command ===>
DB2 System: DD1A
Recreate accelerated tables . . . . . YES (Yes/No. Default is Yes)
Restore replication of tables . . . . YES (Yes/No. Default is Yes)
Reload accelerated tables . . . . . . YES (Yes/No. Default is Yes)
Restore acceleration of tables . . . . YES (Yes/No. Default is Yes)
Remove deleted accelerated tables . . YES (Yes/No. Default is Yes)
Load accelerated tables LOCKMODE . . . NONE (Default is TABLESET)
Load accelerated tables DETECTCHANGES DATA (Default is DATA)
Unload altered tables . . . . . . . . NO (Yes/No/Des. Default is YES)
Preserve all data . . . . . . . . . . YES (Yes/No. Default is YES)
Enable WSL authorization switching . . NO (Yes/No. Default is No)
Object processing order . . . . . . . H (T - Object type, H - DB hierarchy.
Default is H)
Statement validation exit name . . . . (Name of EXEC used to validate
statements in WSL Validate)
Allow PBR2 to PBR changes . . . . . . NO (Yes/No. Default is No)
DB2 release number . . . . . . . . . . 1215 (Use VVRM format)
DB2 function level . . . . . . . . . . 504 (E.g. 100, 500, 501, 5nn)
GRANT processing order . . . . . . . . C (C - CREATE prefix for GRANT
P - POSTUTIL prefix for GRANT
Default is C )
Auto view regenerate . . . . . . . . . NO (Yes/No. Default is No)
Ignore source column order . . . . . . NO (Yes/No. Default is No)Ability to alter implicit table spaces using ALT
PH61198 - August, 2024
Previously, you could alter implicit table spaces in Db2 Admin Tool only by using the AL line command. Now, you can use the ALT line command as an alternative method for altering implicit table spaces. ALT allows you to group changes and run utilities immediately after the change if needed.
Note that Db2 restricts certain alterations for implicit table spaces. For example, you cannot change the table space name or owner. Any attributes that are restricted by Db2 for implicit table space alters are not changeable on the Db2 Admin Tool panels when using AL or ALT for implicit table spaces.
Ability to view RUNSTATS profile text
PH62129 - July, 2024
You can now view the RUNSTATS profile text in a readable format by using the new BT line command on the Manage RUNSTATS Profiles (ADBPZRP) panel:
ADBPZRP n ------- DD1A Manage RUNSTATS Profiles --------- Row 1 to 12 of 1,000
Command ===> Scroll ===> DATA
Line commands:
I - Interpret D - Delete SH - Show history BH - Backup to history
U - Update INS - Insert S - Show object BT - Browse text
? - Show all line commands
Table Table
Sel Name Schema T Text Updated Used
* * * * * *
--- -------> -------- - --------------------> ---------------> --------------->
BIGINT3 ADMF001 T COLUMN ("C1") COLGROU 2023-08-31-04.47 2023-08-31-04.47
BTEST2 ADMF001 T COLGROUP ("EMP_ID") H 2023-10-27-02.24 2023-10-27-02.24
BTEST3 ADMF001 T COLGROUP ("EMP_ID") H 2023-10-27-02.24 2023-10-27-02.24
CHAR8 ADMF001 T COLUMN ("C1") COLGROU 2023-08-31-04.47 2023-08-31-04.47
BT CHARDATE ADMF001 T COLUMN ("C1", "CC", " 2023-08-31-04.47 2023-08-31-04.47
COMMITTE ADMF001 T COLUMN ("I1") COLGROU 2023-08-31-01.02 2023-08-31-01.02
CUSTOMER ADMF001 T COLUMN ("CID") COLGRO 2023-08-31-00.47 2023-08-31-00.47
DATE10 ADMF001 T COLUMN ("C2") COLGROU 2023-08-31-04.47 2023-08-31-04.47
DECIMAL4 ADMF001 T COLUMN ("C1") COLGROU 2023-08-31-04.47 2023-08-31-04.47
FLOAT6 ADMF001 T COLUMN ("C1") COLGROU 2023-08-31-04.47 2023-08-31-04.47
INT2 ADMF001 T COLUMN ("C1") COLGROU 2023-08-31-04.47 2023-08-31-04.47
J2034 ADMF001 T COLUMN ("C1") COLGROU 2023-10-27-02.24 2023-10-27-02.24After entering this line command, the profile text is displayed on a new panel:
ADBPZRPU ------- DD1A RUNSTATS Profile Text ------------ Columns
Command ===> Scroll ===> PAGE
********************************* TOP OF DATA **********************************
COLUMN ("C1", "CC", "DD")
COLGROUP ("C1") FREQVAL
COLGROUP ("CC") FREQVAL
COLGROUP ("DD") FREQVAL
INDEX (*) KEYCARD
******************************** BOTTOM OF DATA ********************************Previously, on the Manage RUNSTATS Profiles (ADBPZRP) panel, the profile text could be viewed only by scrolling within the column field, using the EXPAND command, or using the U (Update) line command on the profile.
Support for new REORG and CHECK DATA utility options
PH62122 (Db2 Admin Tool), PH62123 (Object Comparison Tool) - July, 2024
Db2 Admin Tool now supports the DISCARD clause for the REORG utility. You can specify DISCARD and the related options on the Specify Utility Options - REORG (ADB2USO) panel:
ADB2USO n ---------- DD1A Specify Utility Options - REORG -------------- 09:41
Command ===>
Execute utility on table space DSN8DD1P.DSN8SD1B
using the following options:
...
OFFPOSLIMIT . . . . (integer)
INDREFLIMIT . . . . (integer)
REPORTONLY . . . (Yes/No)
UNLOAD . . . . . . (C - Continue, P - Pause, O - Only, E - External)
DISCARD . . . . . . (Yes/No)
NOPAD . . . . . . (Yes/No)
FROM TABLE . . . (? to look up or C to clear)
>
WHEN . . . . . . > (? to insert column name)
... WHEN . . . . . . column_name > 100 > (? to insert column name)Additionally, the Change Management (CM) batch parameter UTIL_CHECK_SHRLEVEL is added so that you can specify SHREVEL for the CHECK DATA utility.
Support for redirected recovery of indexes
PH61707 - June, 2024
Db2 Admin Tool added the ability to perform redirected recovery of indexes, which is a feature of the Db2 RECOVER utility. To perform this recovery, use the new options FROM, CREATOR, and INDEX NAME on the Specify Utility Options - RECOVER INDEX (ADB2UXV) panel:
ADB2UXV n --------- DD1A Specify Utility Options - RECOVER INDEX -------- 15:12
Command ===>
Execute utility on index SYSIBM.DSNDB01X
using the following options:
More: +
REUSE . . . . . . . (Yes/No)
BACKOUT . . . . . . (Yes/No)
TORBA . . . . . . .
TOLOGPOINT . . . .
LOGONLY . . . . . . (Yes/No)
TOCOPY . . . . . . (or ?)
TOVOLUME . . . .
TOSEQNO . . . . .
TOLASTCOPY . . . . (Yes/No)
TOLASTFULLCOPY . . (Yes/No)
ERROR RANGE . . . . (Yes/No)
LOCALSITE . . . . . (Yes/No)
RECOVERYSITE . . . (Yes/No)
CURRENTCOPYONLY . . (Yes/No)
PARALLEL . . . . . (Yes/No)
TAPEUNITS . . . . (0-32767)
DSNUM . . . . . . . > (1-4096 or ALL)
FROM
Creator . . . . . > (Default is TS6462)
Index name . . . > (? to look up)
LOGRANGES . . . . . (Yes/No)
VERIFYSET . . . . . (Yes/No)
ENFORCE . . . . . . (Yes/No)
SCOPE . . . . . . . (Updated,All)
FLASHCOPY PPRCP . . (NO,PMNO,PMPREF or PMREQ)
ALTERNATE CP . . .
NOSYSCOPY . . . . . (YES,INLCOPY or FCCOPY)
CLONE . . . . . . . (Yes/No)
RESTOREBEFORE . . .
FROMDUMP . . . . . (Yes/No)
DUMPCLASS . . . . > GEN option to preserve the physical partition order
PH61704 - June, 2024
When you use GEN to generate DDL for a table space, you can now specify that you want to use the physical partition order instead of the logical partition order. To do so, specify YES for the new option Physical part order on the Generate SQL from DB2 catalog (ADB2GENB) panel:
ADB2GENB -------------- DD1A Generate SQL from DB2 catalog ------------- 11:34
Option ===>
Generate SQL statements for database DBFSSGEN DB2 System: DD1A
DB2 SQL ID: ADM001
SQL statement types to be generated from the DB2 catalog:
CREATE DATABASE . . . . Y (Y,N) GRANT access ON DATABASE . . Y (Y,N,A,R)
CREATE TABLESPACE . . . Y (Y,N) GRANT access ON TABLESPACE . Y (Y,N,A,R)
CREATE TABLE . . . . . . Y (Y,N) GRANT access ON TABLE . . . Y (Y,N,A,R)
CREATE VIEW . . . . . . Y (Y,N,D) GRANT access ON VIEW . . . . Y (Y,N,A,R)
CREATE INDEX . . . . . . Y (Y,N) ALTER TABLE ADD FOREIGN KEY. Y (Y,N,D)
CREATE SYNONYM . . . . . Y (Y,N) LABEL ON . . . . . . . . . . Y (Y,N)
CREATE ALIAS . . . . . . Y (Y,N) COMMENT ON . . . . . . . . . Y (Y,N)
CREATE TRIGGER . . . . . Y (Y,N,D,A,R)
REBIND PLAN/PACKAGE . . . . Y (Y,N,D)
CREATE MASK . . . . . . Y (Y,N) ALTER TABLE ACTIVATE CONTROL Y (Y,N)
CREATE PERMISSION . . . Y (Y,N)
CREATE STORAGE GROUP . . Y (Y,N) GRANT use OF STORAGE GROUP . Y (Y,N,A,R)
New names/values for generated SQL: (leave blank to use current values)
Object schema . . . . . > Run SQLID . . . . . . . .
Object grantor . . . . . >
Alloc TS size as . . . . DEFINED (DEFINED, USED, or ALLOC)
Database name . . . . .
Storage group for TS . . > Storage group for IX . . . >
Target DB2 version . . . (Current DB2 version: 1115)
Target Function Level. . 500 (Current DB2 FL: 501)
Use Masking . . . . . . NO (Yes/No)
Use Exclude Spec . . . . NO (Yes/No)
Target cat qualifier . . > (Default is SYSIBM)
Generate catalog stats . NO (Yes,No,Only)
Statistics tables . . ALL (All or Select. Default is All)
Include DB2 pending chgs NO (Yes,No,Alter,Only)
PBG NUMPARTS value . . . EXISTING (Defined, Existing)
PBG LOB objects . . . . COMPUTED (Computed, Implicit)
Generate index cleanup . (Yes,No,Only)
Physical part order . . YES (Yes/No)
SQL output data set and execution mode:
Add to a WSL . . . . . . NO (Yes/No)
Data set name . . . . .
Data set disposition . OLD (OLD, SHR, or MOD)
Execution mode . . . . . BATCH (BATCH or TSO)
Commit statements per . (Db, tS, Tb, All, None. Default is All)
DB2 defaults handling . (Keep, or Remove. Default is Keep)
Prompt to run SQL . . . NO (Yes/No. For TSO mode and no WSL)
Include SQL comments . . NO (Yes/No. For BATCH mode and no WSL)
DB2 Command output data set:
Data set name . . . . .
Data set disposition . OLD (OLD, SHR, or MOD)
BP - Change batch job parameters
G - Change additional parameters Db2 13 FL505: Support for temporal versioning for security-related Db2 catalog tables
PH61291, PH61292 - May, 2024
Db2 13 FL 505 Db2 13 function level 505 introduced temporal versioning for security-related Db2 catalog tables. This enhancement provides the ability to access information about authorizations and privileges at a point in time in the past.
To support this enhancement, Db2 Admin Tool has two new primary commands to set the system time and business time. The new command SYSTIME sets the CURRENT TEMPORAL SYSTEM_TIME special register. Similarly, the new command BUSTIME sets the CURRENT TEMPORAL BUSINESS_TIME special register. You can use these commands with any supported Db2 version to set the relevant special register before querying temporal tables. For example, you can set the system time to 1 month ago by issuing the following command:
SYSTIME - 1 MONTHIn addition to specifying a duration of time, you can also specify a timestamp. For example, the following command sets the business time to the requested timestamp:
BUSTIME 2024-04-21-13.49.16.162399000000For syntax details, see BUSTIME and SYSTIME.
Although these commands can be used with any supported version of Db2, the SYSTIME command is particularly useful for Db2 13 function level 505 when temporal relationships are enabled for security-related Db2 catalog tables. This command allows you to easily change the system time and then view the authorizations and privileges that were in effect for Db2 objects and users at that time. See Viewing Db2 authorizations for a past point in time.
When you change the business time or system time, an indication that it was changed is displayed on the DB2 Administration Menu (ADB2) panel:
ADB2 dmin -------------- DB2 Administration Menu 13.1.0 ------------------ 00:49
Option ===> 1
1 - DB2 system catalog DB2 System: DD1A
2 - Execute SQL statements DB2 SQL ID: ADM001
3 - DB2 performance queries Userid : ADM001
4 - Change current SQL ID DB2 Schema: ADM001
5 - Utility generation using LISTDEFs and TEMPLATEs DB2 Rel : 1315
P - Change DB2 Admin parameters DB2 F.Lvl : V13R1M501
DD - Distributed DB2 systems Max ApplC : V13R1M501
E - Explain ApplCompat: V13R1M501
Z - DB2 system administration Cat Level : V13R1M501
SM - Space management functions Loc. : DB2B11
W - Manage work statement lists Sys. time : CHANGED
X - Exit DB2 Admin Bus. time : CHANGED
CC - DB2 catalog copy version maintenance
CM - Change management
Interface to other DB2 products and offerings:
I DB2I DB2 Interactive
C DB2 Object Comparison Tool
ADB2STAT ------------------ DB2X DB2 Admin Status ---------------------- 11:07
Option ===>
Current DB2 Admin status: Accessing the local system
More: +
Local DB2 subsystem name: DB2X
Userid : ISTJE
Current SQL ID : ISTJE
DB2 release : 1315
DB2 product : DB2
Catalog qualifier : SYSIBM - running directly on catalog tables
DDF location : (blank) - running locally
Current server : CPHMVS1_DB2X - local server
Remote subsystem name : n/a
Current temporal system time : 2024-04-22-16.35.19.456018000000
Current temporal business time : 2024-04-22-16.35.10.044526000000
Execution totals Counts Counts
Prepare : 4 Execute dynamically : 0
Describe : 6 - Set : 0
Open : 4 - Insert : 0
Fetch : 1039 - Update : 0
Close : 4 - Delete : 0
Commit : 4 - Create : 0
Rollback : 0 - Drop : 0
Connect : 0 - Alter : 0
Set : 2 - Comment : 0
User rows affected : 0 - Label : 0
- Grant : 0
- Revoke : 0
- Rename : 0
- Commit : 0
- Rollback : 0
- Other dynamic : 0
Use the RESET command to reset the counts
By default, the system time and business time is reset for each session of Db2 Admin Tool. To retain this value across sessions, set the Reset to Def. at Startup field to NO on the DB2 Admin Defaults (ADB2P2) panel.
Db2 13 FL505: Support for ZAI trace destination
PH61154 - May, 2024
Db2 13 FL 505 Db2 13 function level 505 added the new trace destination ZAI, which can be specified on the Db2 commands START TRACE, STOP TRACE, and DISPLAY TRACE. Db2 Admin Tool supports this new trace destination. You can specify ZAI in the DEST field on the Trace Functions (ADB2Z2TS) panel:
ADB2Z2TS DD1A Trace Functions 15:30
Command ===>
More: +
-START
TRACE . . . . . . . . . (STat, ACctg, AUdit, PErfm or MOnitor)
CLASS . . . . . . . . . >
DEST . . . . . . . . . > (SMF, GTF, ZAI, OPn, OPX, SRV)
SCOPE . . . . . . . . . (L - Local, G - Group)
IFCID . . . . . . . . . >
BUFSIZE . . . . . . . . (8-1024)
TDATA CORRELATION
Include cor header . . (Yes/No)
Include CPU header . . (Yes/No)
Include trace hdr . . (Yes/No)
Include dist hdr . . . (Yes/No)
COMMENT . . . . . . . .
RMID . . . . . . . . .
AUDTPLCY . . . . . . .
Specify the filters to include or exclude below:
Include Exclude Support for STATIME_DDF zparm
PH61154 - May, 2024
Db2 added the new subsystem parameter (zparm) STATIME_DDF to control the interval of location statistics trace records. This parameter is valid in Db2 12 and Db2 13.
In Db2 Admin Tool, you can now view and update this parameter on the System Parameters - Tracing and Data Installation (ADB2ZZTR) panel and the System Parameters — System Parameters (ADB2ZZMN) panel:
ADB2ZZTR --- DD1A System Parameters - Tracing and Data Installation -----
Command ===>
DB2 System: DD1A
DB2 SQL ID: TS6462
More: +
Start audit trace . . . . . . . . . . . . . . . > (AUDITST )
Resident trace table size, 4K multiple . . . . . . (TRACTBL )
Start SMF accounting . . . . . . . . . . . . . > (SMFACCT )
Start SMF statistics . . . . . . . . . . . . . > (SMFSTAT )
Statistics interval . . . . . . . . . . . . . . . . . (STATIME ) *
DDF statistics interval . . . . . . . . . . . . . . . (STATIME_DDF ) *
Synchronize statistics recording . . . . . . . . . . . (SYNCVAL ) *
Time between resetting of dataset stats . . . . . . . (DSSTIME ) *
Start monitor trace . . . . . . . . . . . . . . > (MON )
Monitor buffer size . . . . . . . . . . . . . . . . (MONSIZE )
Include UNICODE information in IFC records . . . . . . (UIFCIDS ) *
Rollup accting aggregation fields . . . . . . . . . . (ACCUMUID ) *
System checkpoint frequency (LOGLOAD) . . . . . . (CHKFREQ ) *
UR checkpoint threshold . . . . . . . . . . . . . . . . (URCHKTH ) *
Local trace table size, 4K multiplier . . .. . . . (TRACLOC )
ICF catalog name . . . . . . . . . . . . . . . . . (CATALOG ) *
Pseudo close timer . . . . . . . . . . . . . . . . . (PCLOSET ) *
Roll up parallel task's accounting trace . . . . . . . (PTASKROL ) * ADB2ZZMN DD1A System Parameters - System Parameters 15:34
Command ===>
DB2 System: DD1A
(*) Online changeable parameter DB2 SQL ID: TS6462
More: - +
Maximum size of SORT pool (K) . . . . . . . . . . . 10000 (SRTPOOL ) *
Star join queries . . . . . . . . . . . . . . . . . DISABLE (STARJOIN ) *
Storage limit(MB) for sorting single column COLGROUPs. 10 (STATCLGSRT ) *
Statistics profile feedback . . . . . . . . . . . . . . YES (STATFDBK_PROFI.) *
Scope of statistics feedback . . . . . . . . . . . ALL (STATFDBK_SCOPE ) *
Statistics history default . . . . . . . . . . . ALL (STATHIST ) *
Statistics interval. . . . . . . . . . . . . . . . . . 30 (STATIME ) *
Main statistics interval . . . . . . . . . . . . . . . . 60 (STATIME_MAIN ) *
DDF statistics interval . . . . . . . . . . . . . . . . 0 (STATIME_DDF ) *
RUNSTATS using page-level sampling default . . . . . SYSTEM (STATPGSAMP ) *
Statistics rollup default . . . . . . . . . . . . . . . YES (STATROLL ) *
RTS statistics timer interval. . . . . . . . . . . . . 15 (STATSINT ) *
Abends alllowed . . . . . . . . . . . . . . . . . . . . 255 (STORMXAB ) *
Timeout value . . . . . . . . . . . . . . . . . . . 180 (STORTIME ) *
SUBSTR built-in function behavior . . . . . . . . PREVIOUS (SUBSTR_COMPATI.) *
Suppress logrec error recording . . . . . . . . . . . . YES (SUPERRS ) *
Suppress SQL 394 & 395 for STMT/PLAN_TABLE for dyn SQL NO (SUPPRESS_HINT_.) *
Single volume DASD archives . . . . . . . . . . . . . . YES (SVOLARC ) *SQL Data Insights support
PH61157 - May, 2024
Db2 13 introduced SQL Data Insights (SQL DI), a feature of Db2 that brings some machine learning capability to Db2 SQL. This feature provides the capability to run semantic queries that can find insights hidden in Db2 data. Db2 Admin Tool now provides limited support for SQL DI. You can add an SQL DI object, create SQL DI queries, view information about the SQL DI artifacts, and view and call the SQL DI stored procedures.
ADB2ZDI n ---------------- DD1A SQL Data Insights Menu ----------------- 12:22
Option ===>
Db2 System: DD1A
Db2 SQL ID: TS6462
O - Objects M - Models
J - Training jobs C - Configurations
Enter standard selection criteria:
Name . . . . Creator . . . >
Schema . . . > Object Id . . >
From this panel, you can view various SQL DI artifacts, such as a objects and models. You can also add a user table or view to SQL DI by selecting option O on this panel and then issuing the INSERT command. You can then use the SQL DI web application to train a model and enable the object for SQL DI.
After an object is enabled for SQL DI, you can then build SQL DI queries in Db2 Admin Tool by using the prototyping facility. On the Build SQL SELECT Prototype (ADB21TSE) panel, issue the new SQLDI command. Then, on the subsequent SQL DI - Select Prototyping (ADB21AIS) panel, you can specify SQL DI functions as needed:
ADB21AIS DD1A SQL DI - Select Prototyping 15:47
Command ===>
Caps: ON
Prototype SQL DI function using the following options:
Function . . . . . . . (A - AI_ANALOGY, C - AI_COMMONALITY,
S - AI_SIMILARITY, R - AI_SEMANTIC_CLUSTER)
Expression 1 . . . . . > (? for lookup)
USING MODEL COLUMN . > (? for lookup)
Expression 2 . . . . . > (? for lookup)
USING MODEL COLUMN . > (? for lookup)
Expression 3 . . . . . > (? for lookup)
USING MODEL COLUMN . > (? for lookup)
Expression 4 . . . . . > (? for lookup)
USING MODEL COLUMN . > (? for lookup)
AS . . . . . . . . . . > Additionally, you can navigate to a list of the SQL DI stored procedures by selecting the new option DO on the System Administration (ADB2Z) panel.
Ability to view and alter DSSIZE for indexes and index partitions
PH60436 - May, 2024
You can now easily display and alter the data set size (DSSIZE) for an index or index partition in Db2 Admin Tool. Previously, you could view the DSSIZE only by using the DDL line command to generate DDL for the index or by using the B (BROWSE) command on the Indexes (ADB21X) panel or the Index Parts (ADB21XP) panel.
Now you can view DSSIZE, if applicable to the index type, on one of the following panels:
- Index Parts (ADB21XP) panel
- The following example panel is scrolled one page to the
right:
ADB21XP n -- DD1A Index Parts for HAAQA.I12804AA ------- Row 1 to 3 of 3 Command ===> Scroll ===> DATA More: < > Line commands: C - Columns T - Tables D - Database G - Storage group X - Index P - Plans DIS - Display database STA - Start database STO - Stop database ? - Show all line commands Data Leaf Select Set Size Far Of Pos Near Of Pos Distance Limit Key * * * * * ------ ----------- ----------- ----------- ----------- ------------------------ 5242880 -1 -1 -1 6291456 -1 -1 -1 7340032 -1 -1 -1 ******************************* END OF DB2 DATA *******************************This panel is also updated to include other columns from the Db2 catalog table SYSINDEXPART.
- Interpretation of an Object in SYSINDEXPART (ADB21XPI) panel
-
ADB21XPI -------- DD1A Interpretation of an Object in SYSINDEXPART ----- 13:22 Option ===> More: + Details for index : I12804AA (partition 1) Index schema . . . . . . : HAAQA Storage allocation type : I - Implicitly defined Name of storage group . : DB2EA VSAM catalog name . . . . . : DD1A Global buffer pool option: Changed Index DSN instance qualifier: I Oldest data version . . : 0 Alter timestamp . . . . : 2022-07-13-02.59.43.629697 Create timestamp . . . . : 2022-07-13-02.59.43.629697 RBA format . . . . . . . : E - Extended Page numbering format . : R Storage allocation in units of 4K blocks: Primary space quantity . : 64 Secondary space quantity : 131 Table space load options : Loaded pages/free page . : None Percent free space/page : 10 Statistical data : No valid data available Number of index rows in TS partition : Rows referenced near optimal position : Rows referenced far from opt position : Number of data sets . . . . . . . . . : Number of extents . . . . . . . . . . : Number of pseudo deleted entries . . : Number of leaf pages near previous . : Number of leaf pages far from previous: Allocated space (KB) . . . . . . . . : Average key length . . . . . . . . . : Statistics has not been gathered Max partitioned index data set size for a table space with relative page numbers (KB) . . . . : 5242880 Press ENTER to display data related to partitioning.
You can also now alter the DSSIZE for an index or partition. When you issue the AL line command on an index, the following panel is displayed, where you can specify a new DSSIZE value if applicable for the index type. You can specify this new value for the entire index or one or more partitions.
ADB21XA n ------------------ DD1A Alter Index ---------------- Row 1 to 3 of 3
Command ===> Scroll ===> DATA
Commands: ADDCOL
ALTER INDEX HAAQA.I12804AA (No. of Partitions: 3 )
Buffer Pool . . . BP0 Close Rule . . . . YES Copy Allowed . . . YES
Piece Size . . . . Cluster . . . . . YES Padded . . . . . .
Compress . . . . . NO
Sel Part Pqty Sqty FP PF Erase ST VCAT Stogroup GBPCach DSSIZE
--- ------ ----------- ------- --- -- ----- -- -------- -------> ------- ------
All Parts: 256 524 0 10 NO I DD1A DB2EA CHANGED 8G
1 256 524 0 10 NO I DD1A DB2EA CHANGED 5G
2 256 524 0 10 NO I DD1A DB2EA CHANGED 6G
3 256 524 0 10 NO I DD1A DB2EA CHANGED 7G
******************************* END OF DB2 DATA *******************************Improved consistency in CM batch utility parameter values
PH61155 - May, 2024
New values are added for many Change Management (CM) batch utility parameters to help ensure consistency. Valid values for these parameters should include both a long value (such as YES) and a short value (such as Y), where applicable.
For example, for UTIL_LOAD_PRESORT, you can specify YES, Y, NO, or N. However, for UTIL_LOAD_RESUME, you could previously specify only YES or NO. And for UTIL_REORG_FASTSWITCH, you could previously specify only Y or N. With this enhancement, you can now specify YES, Y, NO, or N for UTIL_LOAD_RESUME and for UTIL_REORG_FASTSWITCH.
The following CM batch utility parameter values are added by this APAR:
| CM batch utility parameter | New values added |
|---|---|
| UTIL_CHECK_XMLSCHEMA | Y, N |
| UTIL_COPY_CHANGELIMIT | YES, ANY |
| UTIL_COPY_CHANGELIMIT_REPORTONLY | YES, NO |
| UTIL_COPY_CHECKPAGE | YES, NO |
| UTIL_COPY_CONCURRENT | YES, NO |
| UTIL_COPY_FLASHCOPY | YES, NO, CON |
| UTIL_COPY_FULL | YES, NO |
| UTIL_LISTDEF_PARTLEVEL | YES, NO |
| UTIL_LOAD_ENFORCE | Y, N |
| UTIL_LOAD_FLASHCOPY | YES, NO, CON |
| UTIL_LOAD_KEEPDICTIONARY | Y, N |
| UTIL_LOAD_LOG | Y, N |
| UTIL_LOAD_PARALLEL | Y |
| UTIL_LOAD_REPLACE | Y, N |
| UTIL_LOAD_RESUME | Y, N |
| UTIL_LOAD_REUSE | Y, N |
| UTIL_REORG_AUX | Y, N |
| UTIL_REORG_DRAIN_ALLPARTS | Y, N |
| UTIL_REORG_DROP_PART | Y, N |
| UTIL_REORG_FASTSWITCH | YES, NO |
| UTIL_REORG_FLASHCOPY | YES, NO, CON |
| UTIL_REORG_INDEX_CLONE | YES, NO |
| UTIL_REORG_INDEX_FASTSWITCH | YES, NO |
| UTIL_REORG_INDEX_FLASHCOPY | YES, NO, CON |
| UTIL_REORG_INDEX_PREFORMAT | YES, NO |
| UTIL_REORG_INDEX_REPORTONLY | YES, NO |
| UTIL_REORG_INDEX_REUSE | YES, NO |
| UTIL_REORG_KEEPDICTIONARY | YES, NO |
| UTIL_REORG_LOG | YES, NO |
| UTIL_REORG_LOGRANGES | Y, N |
| UTIL_REORG_NOSYSREC | YES, NO |
| UTIL_REORG_PARALLEL | Y |
| UTIL_REORG_PREFORMAT | YES, NO |
| UTIL_REORG_RECLUSTER | Y, N |
| UTIL_REORG_REUSE | YES, NO |
| UTIL_REORG_SORTDATA | YES, NO |
| UTIL_REORG_SORTKEYS | YES, NO |
| UTIL_REORG_STATISTICS | YES, NO |
| UTIL_REORG_STATISTICS_FORCEROLLUP | YES, NO |
| UTIL_REORG_STATISTICS_INDEX_HISTOGRAM | YES, NO |
| UTIL_REORG_STATISTICS_INVALIDATECACHE | YES, NO |
| UTIL_REORG_STATISTICS_REPORT | YES, NO |
| UTIL_REORG_STATISTICS_USE_PROFILE | YES, NO |
| UTIL_RUNSTATS_INVALIDATECACHE | YES, NO |
| UTIL_RUNSTATS_REPORT | YES, NO |
| UTIL_UNLOAD_FORMAT_INTERNAL | Y |
| UTIL_UNLOAD_NOPAD | YES, NO |
| UTIL_UNLOAD_NOSUBS | YES, NO |
| UTIL_UNLOAD_PARALLEL | Y |
| UTIL_UNLOAD_SKIP_LOCKED_DATA | Y, N |
| UTIL_UNLOAD_SPANNED | Y, N |
Utility history enhancements
PH60926 - April, 2024
When you use Db2 Admin Tool to view Db2 utility history, additional options are now available for grouping and viewing this history. These options can help you better analyze the data.
Previously in Db2 Admin Tool, you could group the utility history only by utility. You can now also group the utility history by date, job name, or user ID. To do so, use the new options 5D, 5J, and 5U on the Display Utility History (ADB2Z2H) panel. Additionally, you can further investigate one of the grouped items by grouping a second time. For example, if you group utility history by user ID, you can then select a specific user ID and group that history by date. To do so, use the new SD (Show by date) line command on the Utility History Summary by (ADB2Z2H5) panel. Similarly, you can also use the new line commands SJ (Show by jobname), SN (Show by utility), or SU (Show by userid) on that panel to further group a specific date, job name, user ID, or utility. When grouping utility history, you can also now view the history for only those utilities that failed by using the new SF (Show Failed) line command.
You can also view the top 25 objects that have the highest Db2 utility CPU time by using the new option 3O on the Display Utility History (ADB2Z2H) panel. And you can view all of the utilities that were active at a particular timestamp by using the new Active at field.
All of these new options (5D, 5J, 5U, 3O and Active at) are shown in the following screen:
ADB2Z2H n DD1A Display Utility History 15:15
Option ===>
More: +
Enter option and optional criteria: UTILITY_HISTORY zparm:OBJECT
1 - Display utility history rows
Utility . . . . . . (RUNSTATS, REORG, ? to lookup))
Event Id . . . . .
Inserted by . . . . (DB2 or other product name)
Userid . . . . . .
Jobname . . . . . .
Utility ID . . . .
Return code >= . .
Status . . . . . . (A-Active, E-Ended, T-Term., F-Forced)
Start time within . (e.g. n DAYS or n MONTHS)
Age >= . . . . . . (e.g. n DAYS or n MONTHS)
CPU time >= . . . . (in msecs)
Elapsed time >= . . (in msecs)
Active at . . . . . (timestamp)
Includes obj type . (T-Tablespace I-Index)
Database LIKE .
Space name LIKE .
2 - Delete Utility history rows
Status . . . . . . (E-Ended, T-Terminated, F-Forced)
Age >= . . . . . . (e.g. n DAYS or n MONTHS)
Predefined queries:
3 - Show top 25 completed utilities with longest CPU time 3O - top 25 objs
4 - Show top 25 completed utilities with longest elapsed time
5 - Show all utilities group by utility/ 5D - date 5J - jobname 5U - userid
6 - Show top 25 active utilites with longest elapsed time
7 - Show top 25 utilities with return code >= 8
Start time within . (e.g. n DAYS or n MONTHS)
Create own query:
8 - Use the SELECT prototype on SYSUTILITIES
Display exceptions:
9 - Show utilities that differs from the average
Start time within . (e.g. n DAYS or n MONTHS)
CPU time >= . . . . (in msecs, default 1000)
Std deviations . . (1-9, default 3) Additionally, when viewing a utility history event, you can view utilities that ran at the same time, utilities that ran against the same objects, or both by using the new line commands USO, UST, and UTO on the Utility History (ADB2Z2H1) panel.
Non-disruptive ADD COLUMN NOT NULL with no default
PH60828 - April, 2024
When you compare objects with Object Comparison Tool, and the resulting changes to the target include appending a column that is NOT NULL with no default, that change is no longer disruptive. Previously, such a change was made by dropping and recreating the table. Now, this change is accomplished by altering the table as follows:
ALTER TABLE table ADD COL NOT NULL WITH DEFAULT
REORG TABLESPACE table_space
ALTER TABLE table ALTER COL DROP DEFAULTNote that a REORG operation is needed in this case to clear the restrictive state. Therefore, set the Run REORG/REBUILD option on the Generate Compare Jobs (GOC5) panel to M or A. Or, if you are using CM batch, set the RUN_REORG_REBUILD parameter to M or A.
- For tables with DATA CAPTURE CHANGES
- For base tables with materialized query tables
- If the appended column is part of a check constraint or a business period
Ability to specify the ADBTEP2 MAXE value in CM batch
PH60855 (Db2 Admin Tool), PH60856 (Object Comparison Tool) - April, 2024
The batch restart program ADBTEP2 has a parameter, MAXE, that specifies the maximum number of errors (specifically DSN command failures) that can occur before the batch job terminates. You can now also specify this value when using Change Management (CM) batch by using the new CM batch parameter ADBTEP2_MAXE.
Additional column information available when altering tables
PH60528 - April, 2024
When you alter a table by using the ALT command in Db2 Admin Tool, you can now easily see whether a column is part of an index, check constraint, foreign key, primary key, or unique key. Knowing whether a column is part of a constraint or index can help you determine any additional actions you might need to take.
This information is reported on the ALTER Table (ADB27C) panel in the new C and X columns:
ADB27C in ------------------- DB2N ALTER Table -------------- Row 1 to 5 of 14
Command ===> Scroll ===> PAGE
New schema . . DSN8D10 > Old schema: DSN8D10
New name . . . EMP > Old name : EMP
New owner . . DSN8D10 > Type: (U/R) Old owner : DSN8D10
Partitions . : 5 New DB . . DSN8DD1A
Rows per page: 41 New TS . . DSN8SD1E
Commands: NEXT CONSTRAINTS TBLOPTS SHORTNAMES ALTPART HASH
Line commands:
I - Insert U - Update D - Delete R - Repeat LAB - Label COM - Comment
M - Move A - After B - Before X - Index RES - Reset update
? - Show all line commands
Col Old
Sel Column Name No Col Type Length Scale N D C X ColNo
* * * * * * * * * *
--- ------------------------------ --- -------- ----------- ----- - - - - -----
EMPNO 1 CHAR 6 0 N N P 1
FIRSTNME 2 VARCHAR 12 0 N N 2
MIDINIT 3 CHAR 1 0 N N 3
LASTNAME 4 VARCHAR 15 0 N N 4
WORKDEPT 5 CHAR 3 0 Y Y F X 5The new C column lists whether the table column is part of any constraints. It can have the following values:
- P
- Primary key
- F
- Foreign key
- U
- Unique key
- C
- Check constraint
- M
- Multiple constraints
If this C column is blank, the table column is not part of any constraints.
The new X column lists whether the table column is part of any indexes. It can have the following values:
- U
- Unique index. If a column is part of a unique index and one or more other indexes, a U is displayed.
- X
- Other index
If this X column is blank, the table column is not part of any indexes.
Support for EXPLAIN table enhancements
PH60390, PH60391 - April, 2024
Db2 for z/OS updated the format of the Db2 EXPLAIN tables to support IBM Db2 AI for z/OS. Db2 APAR PH44421 added new EXPLAIN table columns, and Db2 APAR PH48053 provided support for converting EXPLAIN tables to the new format.
Db2 Admin Tool provides support for these changes. You can use the panel interface to upgrade your EXPLAIN tables to the current format. Db2 Admin Tool performs this upgrade by calling the new Db2 stored procedure ADMIN_EXPLAIN_MAINT.
The EXPLAIN (ADB2E) panel has been simplified to accommodate these changes:
ADB2E min Explain 23:33
Option ===>
E - Explain an SQL statement DB2 System: DD1A
L - List PLAN_TABLE Q - List SYSQUERY explain info DB2 SQL ID: ADM001
Schema . . . . . . . . . > (default is ADM001)
Plan name . . . . . . . > (optional)
DBRM/package name . . . > (optional)
Collection ID . . . . . > (optional)
DPS - Dynamic Plan Stability
SCT - Statement Cache Table
MNT - Create, upgrade, or drop EXPLAIN tables via ADMIN_EXPLAIN_MAINT stored
procedure The new MNT option replaces the options that were previously available for creating and updating EXPLAIN objects, as shown in on the following old version of this panel:
ADB2E min --------------------------- Explain --------------------------- 10:05
Option ===>
E - Explain an SQL statement DB2 System: DD1A
L - List PLAN_TABLE Q - List SYSQUERY explain info DB2 SQL ID: ADM001
Schema . . . . . . . . . > (default is ADM001)
Plan name . . . . . . . > (optional)
DBRM/package name . . . > (optional)
Collection ID . . . . . > (optional)
DPS - Dynamic Plan Stability
SCT - Statement Cache Table
CT - Create a table used by EXPLAIN
CX - Create an index for the table
UT - Upgrade a table to current DB2 version
CA - Create an alias for the table
For the above create and upgrade options:
Schema . . . . . . . . . . . . ADM001 > (default is ADM001)
Table . . . . . . . . . . . . . 1. PLAN_TABLE
2. DSN_STATEMNT_TABLE
3. DSN_FUNCTION_TABLE
4. DSN_STATEMENT_CACHE_TABLE
5. DSN_QUERYINFO_TABLE
6. DSN_PREDICAT_TABLE
7. DSN_USERQUERY_TABLE
8. DSN_PREDICATE_SELECTIVITY Previously, you specified an action, such as CT, CX, UT, or CA, and a number for the EXPLAIN table on which you wanted to perform that action.
Now, on the revised EXPLAIN (ADB2E) panel, you simply specify the MNT (or abbreviated M) option. Then, on the subsequent panel, you specify the action (such as CREATE or UPGRADE) and the tables on which you want to perform this action:
Manage EXPLAIN Tables & Aliases (ADB2EM1) panel
ADB2EM1 n DD1A Manage EXPLAIN Tables & Aliases Row 1 to 12 of 23
Command ===> Scroll ===> PAGE
Commands: Run Preview SelAll UnselAll SelDiag Options
Line commands: S - Select U - Unselect M - Show message T - Table
DT - Drop table
Input for ADMIN_EXPLAIN_MAINT stored procedure:
Action . . CREATE (Create/Upgrade/Dropall) Manage alias . . NO (Yes/No)
Schema . . TS6462 >
LC S W EXPLAIN Table Schema Owner
* * *
-- - - -------------------------- -------------> ------------->
S PLAN_TABLE Not found
S DSN_STATEMNT_TABLE Not found
S DSN_STATEMENT_CACHE_TABLE Not found
DSN_QUERYINFO_TABLE Not found
DSN_PREDICAT_TABLE Not found
DSN_FILTER_TABLE Not found
DSN_DETCOST_TABLE Not found
DSN_COLDIST_TABLE Not found
DSN_KEYTGTDIST_TABLE Not found
DSN_VIRTUAL_INDEXES Not found
DSN_VIRTUAL_KEYTARGETS Not found
DSN_FUNCTION_TABLE Not found
DSN_PGRANGE_TABLE Not found
DSN_PGROUP_TABLE Not found
DSN_PREDICATE_SELECTIVITY Not found
DSN_PTASK_TABLE Not found
DSN_QUERY_TABLE Not found
DSN_SORTKEY_TABLE Not found
DSN_SORT_TABLE Not found
DSN_STAT_FEEDBACK Not found
DSN_STRUCT_TABLE Not found
DSN_USERQUERY_TABLE Not found
DSN_VIEWREF_TABLE Not found You can perform actions on multiple tables, such as creating all of the diagnostic EXPLAIN tables or upgrading all of your EXPLAIN tables. This revised interface includes all 23 EXPLAIN tables; the previous interface included only a subset of these tables.
All of the necessary indexes are created as part of the create or upgrade process. You can also optionally create aliases as part of these processes.
Also, note that because Db2 Admin Tool now calls the Db2 stored procedure ADMIN_EXPLAIN_MAINT to create and upgrade the EXPLAIN tables, using Change Management for these actions is no longer supported.
Support for new IDAA trace data options
PH60534 - April, 2024
IBM Db2 Analytics Accelerator for z/OS (IDAA) version 7 introduced new options for collecting accelerator trace data. Specifically, the IDAA stored procedure SYSPROC.ACCEL_CONTROL_ACCELERATOR has the following new values for the <getTraceData> element:
- ADDITIONALSUPPORTINFO
- BACKENDENVIRONMENTFILE
- CURRENTTASKS
- DATAUSAGE
- SYSTEMUTILIZATION
- SYSTEMUTILIZATIONHISTORY
- TASKMANAGER
- TASKMANAGERHISTORY
- REPLICATION
- REPLICATIONHISTORY
These options are now supported by Db2 Admin Tool. You can select them when requesting trace data on the DB2 Accelerator Trace Details (ADBPZATR) panel as shown:
ADBPZATR ------------ DB2X Accelerator Trace Details ------------ 07:24
Command ===>
Trace details for accelerator : IDAAZ17
Save to output data set . . RHP.TRACE1.OUT
Specify the type of content to save:
Accelerator . . . . . . . . . (Yes/No)
Appliance . . . . . . . . . . (Yes/No)
Additional support info . . . YES (Yes/No)
Since last save only . . . YES (Yes/No)
Backend environment file . YES (Yes/No)
Current tasks . . . . . . . . (Yes/No)
Data usage . . . . . . . . . (Yes/No)
System utilization . . . . . (Yes/No)
System utilization history . (Yes/No)
Task manager . . . . . . . . (Yes/No)
Task manager history . . . . (Yes/No)
Replication . . . . . . . . . (Yes/No)
Repliation history . . . . . (Yes/No)
OR
Any other trace type . . . . . As an alternative to specifying YES in one of the trace type fields, you can specify a value in the new Any other trace type field. This field provides the flexibility to specify a value that is not yet listed on the panel. For example, if IDAA adds support for a <getTraceData> value of XYZ in the future, you can specify XYZ in this field. You can also specify one of the values already supported on this panel, such as CURRENTTASKS or DATAUSAGE. The Any other trace type value is passed to SYSPROC.ACCEL_CONTROL_ACCELERATOR as is; Db2 Admin Tool does not check whether the value is valid.
Support for CREATE TABLE LIKE statements when comparing DDL
PH60527 - April, 2024
Db2 Object Comparison Tool now supports CREATE TABLE LIKE statements in DDL that is used for comparisons.
When you specify source and target objects for a comparison, one way to specify the object definitions is to use DDL. Previously, CREATE TABLE LIKE statements were not supported in this DDL. This restriction is now removed. The DDL that is used for source or target object definitions can now contain CREATE TABLE LIKE statements. However, the table in the LIKE clause must be defined in the same DDL.
Support for more granular filtering in MONITOR CONNECTIONS FOR SECURITY profiles
PH60529 - April, 2024
Db2 for z/OS APAR PH57811 introduced a capability to apply security profile rules more precisely. With this APAR, you can specify the following additional values in the LOCATION column for profiles that use the MONITOR product-type CONNECTIONS FOR SECURITY keyword:
- A fully qualified domain name
- IPv4 or IPv6 IP address
- IPv4 or IPv6 subnet address
Db2 Admin Tool supports these values when creating and updating profiles on the Insert/Update Profile (ADB2Z2PP) panel.
Support for new REPAIR utility options
PH60526 - April, 2024
Db2 Admin Tool has added support for the following options for the Db2 REPAIR utility:
- For table spaces:
- INSERTVERSIONPAGES
- LOCATE
- SET NOAREORPEND, PRO and NOPRO
- DBD
- SHRLEVEL CHANGE
- For indexes: LOCATE
You can specify these new options on the Specify Utility Options - REPAIR TABLESPACE (ADB2USN) panel and the Specify Utility Options - REPAIR INDEX (ADB2UXN) panel.
N - Repair nocopypend NA - Repair nocheckpend NB - Repair norcvrpend
NC - Repair catalog NR - Repair noreorgpend
NW - Repair Auxwarn NX - Repair Auxcheckpend N - Repair nocopypend NA - Repair nocheckpend NB - Repair norcvrpend
NC - Repair Catalog NR - Repair norbdpend
NO - Repair noareorgpend N* - Repair noareorpendstar N - Repair When you select this N option, the relevant utility options panel, Specify Utility Options - REPAIR TABLESPACE (ADB2USN) panel or Specify Utility Options - REPAIR INDEX (ADB2UXN) panel, is automatically displayed so that you can select which REPAIR function you want to run.
Improved error detection for CREATE TABLE and ALTER TABLE statements
PH59776 - March, 2024
Some processes in Db2 Admin Tool accept DDL as input. The DDL is parsed to identify the keywords and values, but currently the syntax, semantics, and values are not verified. Therefore, errors will not be detected until the DDL is applied to Db2 much later in the process.
The Db2 Admin Tool parser is being enhanced in stages to detect and report basic errors in the parsed DDL. This APAR adds the following checks for CREATE and ALTER TABLE statements:
- Check whether an attribute is specified more than once.
- Verify that exclusive options for ALTER TABLE (such as DROP COLUMN) are not specified with any other option.
- Verify value ranges for some options. For example:
- DSSIZE is in the range of 1-1024
- Length attribute for a CHAR column is in the range of 1-255
- Verify that CREATE GLOBAL TEMPORARY TABLE does not contain options that are not valid (such as AUDIT).
- Verify that some options (such as LOGGED) in CREATE TABLE are valid only if the table is created in an implicit table space.
Automatic rebinds when running ADBTEP2 jobs
PH59774 , PH59775 - February, 2024
The ADBTEP2 program is used by Db2 Admin Tool to run various operations in batch, such as altering objects and running utilities. This program has been enhanced so that it can now automatically rebind any packages that are invalidated by an SQL statement in the ADBTEP2 job. This enhancement can help prevent execution errors caused by missing rebinds. Such errors are more likely to occur if a significant amount of time passes between generating and running the ADBTEP2 job.
- the new Auto Rebind field on Batch Job Utility Parameters (ADB2UPA) panel
- the new Change Management (CM) batch parameter ADBTEP2_AUTOREBIND
Both values, YES and ALL, enable automatic rebinds when packages are invalidated by processed statements. The difference is that if you specify ALL, an additional REBIND command is generated when a new index is created on the table, so that the access paths are refreshed for dependent packages. The default value is NO; ADBTEP2 will not perform any automatic rebinds.
- If you are using the Batch Job Utility Parameters
(ADB2UPA) panel, specify
any REBIND options in the new fields after Auto
Rebind:
Auto Rebind . . . . . NO (Yes/No/All) APREUSE . . . . . . (None, Warn, Error) EXPLAIN . . . . . . (Yes/No/Only) OWNER . . . . . . . > OWNERTYPE . . . . . (Role, User) Additional options . > - If you are using CM batch, specify any REBIND options by using the following new parameters:
- ADBTEP2_AUTOREBIND_APREUSE
- ADBTEP2_AUTOREBIND_EXPLAIN
- ADBTEP2_AUTOREBIND_OWNER
- ADBTEP2_AUTOREBIND_OWNERTYPE
- ADBTEP2_AUTOREBIND_ADDITIONAL_OPTS
Ability to pass parameters to user-defined primary commands
PH59323, PH59324 - January, 2024
In Db2 Admin Tool, you can define your own primary commands by using the CMDS command and the subsequent panels to create your own command list. This CMDS functionality is enhanced so that your commands can now accept parameters. Additionally, to improve usability, you can now provide descriptions for your commands.
For example, you can define the following command to check the status of a batch job:
ADBPMCEI DD1A Insert Command --- 15:01
Command ===>
Commands: CANCEL
Command definition:
Command . . . . MYST
Description . . Check status >
Admin cmds . . ISPF SELECT CMD(STATUS &ZOPT) > The
name of this new command is MYST. When MYST is issued, the command that is specified in the
Admin cmds field will be run. Previously, any values in this field
had to be hardcoded. Now, this command can include parameters. These parameters are
represented by the new specification &ZOPT. When the command is run,
&ZOPT will be replaced with the specified value. So, for this example, if you specify
the primary command MYST DSNTMSTR on any panel in Db2 Admin Tool, the following command is run:
ISPF SELECT CMD(STATUS DSNTMSTR)You can also now specify
descriptions for your commands. In this example, the description is Check
status. These descriptions are displayed on the Edit Command List
(ADBPMCE) panel:
ADBPMCE n DD1A Edit Command List Row 1 to 2 of 2
Command ===> Scroll ===> PAGE
More: >
Command list member: MYCOMMS Data set: TS6462.TEST.COMMANDS
Commands: CANCEL
Line commands: R - Run U - Update I - Insert D - Delete
? -Show all line cmds
Select Command Description
*
------ -------- ---------------------------------------------------------------
* UTILDB1G Display utilities DB1G
* MYST Check status
******************************* END OF DB2 DATA *******************************New primary commands
PH59323, PH59324 - January, 2024
The following commands have been added to the default primary command list, ADBSCMDL, that is shipped with Db2 Admin Tool:
| Command | Description |
|---|---|
| CHKPT | Display ADBTEP2 checkpoints |
| MYTABS | My tables |
| OC1 | Object compare |
| SPUFI | Run SPUFI |
| SQLEXPR | Test an SQL expression |
| SYS | System administration |
| UTILHIST | Db2 13 FL 501 Display utility history |
- Since the release of these APARs, the OC command has been changed to OCT by APARs PH62122 and PH62123.
To view a list of all commands in ADBSCMDL, issue the CMDS primary command and then specify the S (Show command list) next to ADBSCMDL.
ALTER VIEW REGENERATE after altering columns
PH55470 (Db2 Admin Tool), PH59334 (Object Comparison Tool) - January, 2024
When any change function in Db2 Admin Tool, such as ALT or Compare, alters the data type, length, precision, or scale of a column, Db2 Admin Tool can now automatically regenerate any views that reference those columns in that table. To request this behavior, set the new Auto view regenerate option on the Options for Change Functions (ADB2PCO) panel. When you set this option to YES, Db2 Admin Tool generates ALTER VIEW REGENERATE statements after the ALTER operation on the table. The default setting is NO; views are not automatically regenerated.
You can also control this behavior in Change Management (CM) batch by using the new CM batch option AUTO_VIEW_REGENERATE. The default for this option is also NO.