Updates to DB2 Administration Tool for z/OS V10.2 User's Guide

Product documentation


Abstract

Updates that apply to DB2 Administration Tool for z/OS V10.2 User's Guide (SC19-3778-06)

Content

The most recent update is listed first.




Table of Contents

Update 4: October 30, 2014
Update 3 : August 29, 2014
Update 2: June 19, 2014
Update 1 : May 15, 2014




Update 4
Date of change: October 30, 2014

Topic: DB2 Admin primary commands
Change description: The DUTIL is primary command.


Start of changeDUTIL End of change Start of change End of change Start of changeDisplays the Display or Terminate Utilities panel (ADB2Z2U2). On the panel, you can view a list of utilities that are running and select utilities to stop running. End of change

Topic: Utility Template panel
Change description: Add new field 'Device type' to identify whether the UNIT is on a removable device.

Figure 1. Utility Template panel (ADB25TE)
DB2 Admin -------------------- DB2X Utility Template -------------------- 11:20
Command ===>                                                                  
                                                                               
Enter name and optional remark.  Press Enter to save.                          
                                                                               
TEMPLATE . . . .            (Template name)                                    
Remark . . . . .                                                              
                                                                              >
Common options:                                                                
  UNIT . . . . .            (Device number, type or group name)                
 
Start of change Device type  .            (DASD or TAPE, default is DASD) End of change                    
  DSN  . . . . .                                                              
                                                                                                                                                             
  Change other common options  . .     (Yes/No)                                
  Change disk options  . . . . . .     (Yes/No)                                
  Change tape options  . . . . . .     (Yes/No)                                
                                                                               
Statement  . . . TEMPLATE                          
                           
.

.
.
Start of changeDevice type End of change
Start of changeUse this field to specify the device type for the data set. End of change                                                            
Topic: Parameter definitions: Change Management batch interface (APAR 39045)
Change description: Add new field 'Device type' to identify whether the UNIT is on a removable device.

Start of changeutil_template_workddn1_devtype End of change
Start of changeThe util_template_workddn1_devtype parameter specifies whether the WORKDDN1 template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
blank
End of change

Start of changeutil_template_errddn_devtype End of change
Start of changeThe util_template_errddn_devtype parameter specifies whether the ERRDDN template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
blank
End of change

Start of changeutil_template_mapddn_devtype End of change
Start of changeThe util_template_mapddn_devtype parameter specifies whether the MAPDDN template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
blank
End of change

Start of changeutil_template_workddn1_devtype End of change
Start of changeThe util_template_workddn1_devtype parameter specifies whether the WORKDDN1 template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
blank
End of change

Start of changeutil_template_workddn2_devtype End of change
Start of changeThe util_template_workddn2_devtype parameter specifies whether the WORKDDN2 template is on a tape-like device, or on a DASD device.
Values:
TAPE
A removal media device, such as 3490 tape, or a 3490E tape drive.
DASD
A magnetic disk storage device, such as a direct access storage device (DASD).
Default:
blank
End of change

Topic: Generic ignore field specifications
Change description: Added the PBG_NUMPARTS ignore specification

The generic ignore specifications are:
  • Bufferpool
  • Space
  • Storage
  • Partitioning
  • Start of changeKey targetsEnd of change
  • Start of changeBusiness timeEnd of change
  • Start of changeSystem timeEnd of change
  • Source pending changes
  • Row permissions
  • Column masks
  • Include columns
  • Start of changePBG numpartsEnd of change
  • Start of changeHash organizationEnd of change
  • XML modifier
.
.
.
Start of changeIf you specify the PBG_NUMPARTS generic ignore specification, the following DB2 catalog table field is ignored: SYSTABLESPACE.PARTITIONS. End of change


Update 3

Topic: Customizing DB2 Admin, Optional: Define Reverse Engineering stored procedure for CC/390

Change description: New topic that describes how to apply Reverse Engineering to additional software products such as Control Center OS/390 (CC/390).

You can apply Reverse Engineering to additional software products such as Control Center OS/390 (CC/390).

Complete the following steps:
1. Run job ADBREST. ADBREST creates the Reverse Engineering stored procedure ADB2RE. ADB2REST also creates the required temporary tables and bind package for the stored procedure on the DB2 subsystem that will use the Reverse Engineering facility.
2. Copy load module members ADB2RE and ADB2LM from the SADBLLIB load library to one of the libraries defined as STEPLIB in the Work Load Manager (WLM)-managed stored procedure address space. The ADB2RE stored procedure dynamically allocates output data sets, as specified by the CC/390 user.

The ADB2RE stored procedure must be defined with the SECURITY USER clause. Procedures that are specified with the SECURITY USER clause cannot run in the non-WLM-managed stored procedure address space (ssidSPAS). Instead, the stored procedure must run in a WLM-managed stored procedure address space.


Change description: State clearly that objects generated by the Change Management job ADBCHANG are required. Error message are generated when the ADBCHANG job is not run.

Topic: Worksheets: Gathering parameter values for Tools Customizer, Task: Change Management database

Jobs generated
This task generates the following jobs:

  • ADBCHAab, where ab are alphanumeric characters assigned by Tools Customizer. This job is based on the ADBCHANG template and is in the job_sequence_numberCHANDB2_entry_ID member. Start of changeThe job creates several objects. The objects are required. You can see the list of created objects in the generated job.End of change
  • ADBCMBAT. This job is based on the ADBCMBAT template and is in the job_sequence_numberCMBAT member.
  • ADBCMBab, where ab are alphanumeric characters assigned by Tools Customizer. This job is based on the ADBCMBSS template and is in the job_sequence_numberCMBSDB2_entry_ID member.

Topic: Jobs created by Tools Customizer, Table 1. DB2 Admin customization jobs

Create Change Management database (required)

Start of changeSeveral objects are created. The objects are required. You can see the list of created objects in the generated job.End of change

A5CHANnn ADBCHANG SYSADM or equivalent

Change description: Clarification of CM Batch parameters auto reorg and auto rebuild in adbtep2 automated utilities.

Topic:
Making changes using Change Management batch interface, Parameter definitions
adbtep2_advisoryautorebuild
The adbtep2_advisoryautorebuild parameter specifies whether the product, when a change is run, initiates a REBUILD when an object is in certain rebuild pending states. For the complete description and list of values see Using the Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REBUILD if the object is in the ARBDP state.

Start of changeHowever, if the parameter run_reorg_rebuild was specified as 'A - All relevant' to generate an explicit REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REBUILD that duplicates the explicit REBUILD.End of change

NO
The product does not automatically attempt a REBUILD if the object is in the ARBDP state.
Default:
NO
adbtep2_advisoryautoreorg
The adbtep2_advisoryautoreorg parameter specifies whether the product, when a change is run, initiates a REORG when an object is in certain reorganization-pending states. For the complete description see Using the Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The production automatically attempts a REORG if the object is in AREOR or AREO* state.

Start of changeHowever, if the parameter run_reorg_rebuild was specified as 'A - All relevant' to generate an explicit REORG during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG that duplicates the explicit REORG. End of change

NO
DB2 Admin does not automatically attempt a REORG if the object is in AREOR or AREO* state.
Default:
NO
adbtep2_autorebuild
The adbtep2_autorebuild parameter specifies whether the product, when a change is run, initiates a REBUILD when an object is in certain rebuild pending states. For the complete description see Using the Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
YES
The product automatically attempts a REBUILD if the object is in one of these states: RBDP, RBDP*, or PSRBD state.

Start of changeHowever, if the parameter run_reorg_rebuild was specified as 'M - Mandatory' or 'A - All relevant' to generate an explicit REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REBUILD that duplicates the explicit REBUILD.End of change

NO
The product does not automatically attempt a REBUILD if the object is in one of these states: RBDP, RBDP*, or PSRBD state.
Default:
YES
adbtep2_autoreorg
The adbtep2_autoreorg parameter specifies whether the product, when a change is run, initiates a REORG when an object is in certain reorganization-pending states. For the complete description see Using the Batch Restart programs: ADBTEP2 and ADBTEPA.
Values:
Start of change
YES
The product automatically attempts a REORG if the object is in the REORP state.

However, if the parameter run_reorg_rebuild was specified as 'M - Mandatory' or 'A - All relevant' to generate an explicit REORG during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG that duplicates the explicit REORG.

NO
The product does not automatically attempt a REORG if the object is in the REORP state.
End of change
Default:
YES

Topic:
Parameters passed to the ADBTEP2 program
Parameters passed under the DD name of ADBTEPIN

The following parameters are generated automatically and are passed to the ADBTEP2 program in a data set with a DD name of ADBTEPIN:

Advisory Auto Rebuild
The Advisory Auto Rebuild parameter determines if the Batch Restart Program initiates a REBUILD of an index when an object is in the ARBDP state.

  • Start of changeYES - A REBUILD is attempted. However, if the parameter Run REORG/REBUILD was specified as 'A - All relevant' to generate an explicit REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REBUILD that duplicates the explicit REBUILD. End of change
  • NO - A REBUILD is not attempted.

No is the default.

For more information about the rebuild-pending states, see the DB2 V10 Utilities Guide.

Tip: To prevent the ADBTEP2 program from scheduling any automatic REBUILDs, you must set both the Auto Rebuild and Advisory Auto Rebuild parameters to No.
Advisory Auto Reorg
The Advisory Auto Reorg parameter determines if the Batch Restart Program initiates a REORG of a table space when an object is in the AREOR,AREO* state.

  • Start of changeYES - A REORG is attempted. However, if the parameter Run REORG/REBUILD was specified as 'A - All relevant' to generate an explicit REORG during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG that duplicates the explicit REORG. End of change
  • NO - A REORG is not attempted.

No is the default.

For more information about the rebuild-pending states, see the DB2 V10 Utilities Guide.

Tip: To prevent the ADBTEP2 program from scheduling any automatic REORGs you must set both the Auto Reorg and Advisory Auto Reorg parameters to No.
Auto Rebuild
The Auto Rebuild parameter determines if the Batch Restart Program initiates a REBUILD of an index when an object is in the RPDB. RPDB*, or PSRBD state.

  • Start of changeYES - A REBUILD is attempted. However, if the parameter Run REORG/REBUILD was specified as 'M - Mandatory' or 'A - All relevant' to generate an explicit REBUILD during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REBUILD that duplicates the explicit REBUILD. End of change
  • NO - A REBUILD is not attempted.

No is the default.

For more information about the rebuild-pending states, see the DB2 V10 Utilities Guide.

Tip: To prevent the ADBTEP2 program from scheduling any automatic REBUILDs, you must set both the Auto Rebuild and Advisory Auto Rebuild parameters to No.
Auto Reorg
The Auto Reorg parameter determines if the Batch Restart Program initiates a REORG of a table space when an object is in the REORP state.

  • Start of changeYES - A REORG is attempted. However, if the parameter Run REORG/REBUILD was specified as 'M - Mandatory' or 'A - All relevant' to generate an explicit REORG during the change flow, then the value NO is passed to ADBTEP2. The NO value prevents an automatic REORG that duplicates the explicit REORG.End of change
  • NO - A REORG is not attempted.

No is the default.

For more information about the reorg-pending states, see the DB2 V10 Utilities Guide.

Tip: To prevent the ADBTEP2 program from scheduling any automatic REORGs you must set both the Auto Reorg and Advisory Auto Reorg parameters to No.






Update 2

Topic: Making changes using Change Management batch interface, Parameter definitions

Change description: The following new or modified CM Batch parameter
can be used to manage the data set attribute identified by each
parameter.

admin_dataset_bufno
The admin_dataset_bufno parameter specifies the BUFNO attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The BUFNO attribute is for the number of buffers to be assigned for data control blocks. For more information, see the admin_dataset_type parameter.
Values:
An integer value 1-255, blank
blank
The BUFNO attribute is not specified for the ALLOCATE statement.
Default:
blank

admin_dataset_dataclas
The admin_dataset_dataclas parameter specifies the DATACLAS attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The DATACLAS attribute is for the data class name. For more information, see the admin_dataset_type parameter.
Values:
A valid data class name
DB2 Admin does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted. DB2 Admin then sets the RECFM, LRECL, and BLKSIZE attributes by specifying these attributes on the ALLOCATE statement. By default, DB2 Admin specifies the space attributes on the allocate statement but you can omit the space attributes from the ALLOCATE statement by specifying admin_dataset_space_priqty = '<NONE>' for the DB2 Admin.
blank
The DATACLAS attribute is not specified for the ALLOCATE statement.
Default:
blank

admin_dataset_device_unit
The admin_dataset_device_unit parameter specifies the device unit for the DB2 Admin data set. For more information, see the admin_dataset_type parameter.
Values:
A valid device unit, <NONE>
<NONE>
Specifies that the UNIT clause is omitted from the ALLOCATE statement.
Default:
space_unit_name

admin_dataset_dir
The admin_dataset_dir parameter specifies the DIR attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The DIR attribute is for the number of directory blocks. For more information, see the admin_dataset_type parameter. This parameter is only used for the following types of DB2 Admin data sets: IFF, DELTA, DDL SRCVF, TGTVF, MTC.

If the SPACE(priqty,secqty) clause is omitted, then no default value is specified.

Values:
An integer greater than zero, blank
blank
If the SPACE(priqty,secqty) clause is not to be omitted, specifies that the following default values are used for the DB2 Admin data set type that is in effect:

  • IFF: 60. A user specified value for directory blocks that you specify only if the DB2 Admin default is insufficient for the change that is being analyzed.
  • DELTA: 60
  • DDL: 60
  • SRCVF: 60
  • TGTVF: 60
  • MTC: 60
Default:
blank

  admin_dataset_dsntype
The admin_dataset_dsntype parameter specifies the DSNTYPE attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The DSNTYPE attribute is for the type of data set. For more information, see the admin_dataset_type parameter. This parameter is only used for the following types of DB2 Admin data sets: IFF, DELTA, DDL SRCVF, TGTVF, MTC.
Values:
LIBRARY, PDS, blank
blank
For data set type IFF, the default is PDS. Otherwise the DSNTYPE attribute is not added to the ALLOCATE statement.
Default:
blank

admin_dataset_expdt
The admin_dataset_expdt parameter specifies the EXPDT attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The EXPDT attribute is an expiration date. For more information, see the admin_dataset_type parameter. This parameter is mutually exclusive with the admin_dataset_retpd parameter.
Values:
A valid expiration date as defined for the EXPDT attribute for the TSO ALLOCATE statement, blank
blank
The EXPDT attribute is not specified for the ALLOCATE statement.
Default:
blank

admin_dataset_maxvol
The admin_dataset_maxvol parameter specifies the MAXVOL attribute of the TSO ALLOCATE statement for the DB2 Admin data set. For more information, see the admin_dataset_type parameter.
Values:
A valid maxvol value as defined by the TSO ALLOCATE statement
DB2 Admin does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted.
blank
The MAXVOL attribute is not specified for the ALLOCATE statement.
Default:
blank
   
admin_dataset_mgmtclas
The admin_dataset_mgmtclas parameter specifies the MGMTCLAS attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The MGMTCLAS attribute is for the management class name. For more information, see the admin_dataset_type parameter.
Values:
A valid management class name
DB2 Admin does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted.
blank
The MGMTCLAS attribute is not specified for the ALLOCATE statement.
Default:
blank

admin_dataset_retpd
The admin_dataset_retpd parameter specifies the RETPD attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The RETPD attribute is a retention period specified in number of days. For more information, see the admin_dataset_type parameter. This parameter is mutually exclusive with the admin_dataset_expdt parameter.
Values:
An integer value representing the number of days, blank
blank
The RETPD attribute is not specified for the ALLOCATE statement.
Default:
blank

admin_dataset_space_priqty
The admin_dataset_space_priqty parameter specifies the primary quantity for the DB2 Admin data set. For more information, see the admin_dataset_type parameter.
Values:
A valid PRIQTY value, Start of change<NONE>, End of changeblank
Start of change<NONE> End of change
Specifies that the SPACE(priqty,secqty), unit of space clauses, and space directory attributes be omitted from the ALLOCATE statement.
blank
Specifies that the following default values are to be used for the indicated DB2 Admin data set type that is in effect:
  • CHG: 10
  • DDL: 10
  • DELTA: 10
  • IFF: 2
  • MTC: 10
  • SRCVF: 10
  • TGTVF: 10
Default:
blank

admin_dataset_storclas
The admin_dataset_storclas parameter specifies the STORCLAS attribute of the TSO ALLOCATE statement for the DB2 Admin data set. The STORCLAS attribute is for the storage class name. For more information, see the admin_dataset_type parameter.
Values:
A valid storage class name
DB2 Admin does not validate this value. If an invalid value is specified, an error message is generated from TSO when the allocate of the data set is attempted.
blank
The STORCLAS attribute is not specified for the ALLOCATE statement.
Default:
blank

admin_dataset_volume
The admin_dataset_volume parameter the VOLUME attribute of the TSO ALLOCATE statement for the DB2 Admin data set. For more information, see the admin_dataset_type parameter.
Values:
One or more serial numbers separated by a comma, blank
blank
The VOLUME attribute is not specified for the ALLOCATE statement.
Default:
blank

util_clone_template_punchddn_name
The util_clone_template_punchddn_name parameter specifies the user provided template name for the PUNCHDDN file of the REORG utility.
Values:
a DB2 template name; 1 to 8 characters
Default:
CPUNCH

util_clone_template_punchddn_use
The util_clone_template_punchddn_use specifies whether to use a user provided template for the PUNCHDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the util_clone_template_punchddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_clone_template_unlddn_name

The util_clone_template_unlddn_name parameter specifies the user provided template name for the UNLDDN file of the REORG utility.
Values:
a DB2 template name; 1 to 8 characters
Default:
CUNL

util_clone_template_unlddn_use
The util_clone_template_unlddn_use specifies whether to use a user provided template for the UNLDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the util_clone_template_unlddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_clone_template_unload_punchddn_name
The util_clone_template_unload_punchddn_name parameter specifies the user provided template name for the PUNCHDDN file of the UNLOAD utility.
Values:
a DB2 template name; 1 to 8 characters
Default:
CUPUNCH

util_clone_template_unload_punchddn_use
The util_clone_template_unload_punchddn_use specifies whether to use a user provided template for the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_clone_template_unload_punchddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_clone_template_unload_punchddnc_name
The util_clone_template_unload_punchddnc_name parameter specifies the user provided template name for the DB2 Admin converted version of the PUNCHDDN file of the UNLOAD utility. Some types of changes require that the unloaded data be converted by DB2 Admin before the data is loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
a DB2 template name; 1 to 8 characters
Default:
CUPUNCHC

util_clone_template_unload_punchddnc_use
The util_clone_template_unload_punchddnc_use specifies whether to use a user provided template for the DB2 Admin converted version of the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_clone_template_unload_punchddnc_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y. Some types of changes require that the unloaded data be converted by DB2 Admin before the data is loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_clone_template_unload_unlddn_name
The util_clone_template_unload_unlddn_name parameter specifies the user provided template name for the UNLDDN file of the UNLOAD utility.
Values:
a DB2 template name; 1 to 8 characters
Default:
CUUNL

util_clone_template_unload_unlddn_use
The util_clone_template_unload_unlddn_use specifies whether to use a user provided template for the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_clone_template_unload_unlddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_clone_template_unload_unlddnc_name
The util_clone_template_unload_unlddnc_name parameter specifies the user provided template name for the DB2 Admin converted version of the UNLDDN file of the UNLOAD utility. Some types of changes require that the unloaded data to be converted by DB2 Admin before the data can be loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
a DB2 template name; 1 to 8 characters
Default:
CUUNLC

util_clone_template_unload_unlddnc_use
The util_clone_template_unload_unlddnc_use specifies whether to use a user provided template for the DB2 Admin converted version of the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_clone_template_unload_unlddnc_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y. Some types of changes requires the unloaded data to be converted by DB2 Admin before it can be loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
a non-blank value
a non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_template_punchddn_name
The util_template_punchddn_name parameter specifies the user provided template name for the PUNCHDDN file of the REORG utility.
Values:
A DB2 template name
The DB2 template name can be 1 to 8 character in length.
Default:
PUNCH

util_template_punchddn_use
The util_template_punchddn_use specifies whether to use a user provided template for the PUNCHDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the util_template_punchddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_template_unlddn_name
The util_template_unlddn_name parameter specifies the user provided template name for the UNLDDN file of the REORG utility.
Values:
A DB2 template name
The DB2 template name can be 1 to 8 character in length.
Default:
UNL

util_template_unlddn_use
The util_template_unlddn_use parameter specifies whether to use a user provided template for the UNLDDN file of the REORG utility. If a non-blank value is specified, the template name is determined from the util_template_unlddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_template_unload_punchddn_name
The util_template_unload_punchddn_name parameter specifies the user provided template name for the PUNCHDDN file of the UNLOAD utility.
Values:
A DB2 template name
The DB2 template name can be 1 to 8 character in length.
Default:
UPUNCH

util_template_unload_punchddn_use
The util_template_unload_punchddn_use specifies whether to use a user provided template for the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_template_unload_punchddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_template_unload_punchddnc_name
The util_template_unload_punchddnc_name parameter specifies the user provided template name for the DB2 Admin converted version of the PUNCHDDN file of the UNLOAD utility. Some types of changes require that the unloaded data to be converted by DB2 Admin before the data is loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
A DB2 template name
The DB2 template name can be 1 to 8 character in length.
Default:
UPUNCHC

util_template_unload_punchddnc_use
The util_template_unload_punchddnc_use specifies whether to use a user provided template for the PUNCHDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_template_unload_punchddnc_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y. Some types of changes requires the unloaded data to be converted by DB2 Admin before it can be loaded. This parameter controls the user provided template for the converted load control card for the unloaded data.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_template_unload_unlddn_name
The util_template_unload_unlddn_name parameter the user provided template name for the UNLDDN file of the UNLOAD utility.
Values:
A DB2 template name
The DB2 template name can be 1 to 8 character in length.
Default:
UUNL

util_template_unload_unlddn_use
The util_template_unload_unlddn_use specifies whether to use a user provided template for the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_template_unload_unlddn_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S

util_template_unload_unlddnc_name
The util_template_unload_unlddnc_name parameter specifies the user provided template name for the DB2 Admin converted version of the UNLDDN file of the UNLOAD utility. Some types of changes require that the unloaded data to be converted by DB2 Admin before the data is loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
A DB2 template name
The DB2 template name can be 1 to 8 character in length.
Default:
UUNLC

util_template_unload_unlddnc_use
The util_template_unload_unlddnc_use specifies whether to use a user provided template for the DB2 Admin converted version of the UNLDDN file of the UNLOAD utility. If a non-blank value is specified, the template name is determined from the util_template_unload_unlddnc_name parameter. This parameter is in effect only if the generate_templates parameter is set to Y. Some types of changes require that the unloaded data to be converted by DB2 Admin before the data is loaded. This parameter controls the user provided template for the converted data set for the unloaded data.
Values:
A non-blank value
A non-blank value indicates that the template name is used if the generate_templates parameter is set to Y and the template exists in the ADBTEMPL file.
Default:
S




Update 1
Change description: Checking syntax and the semantics of SQL statements

Topic: The Change Management process, Analyzing a change

Analyzing a change
A normal change must be analyzed before the change can be applied to the objects. When you issue the command to analyze a change, DB2 Admin generates a batch job that you submit.
The batch job analyzes how the change modifies existing objects, both in DB2 and in any of the prerequisite changes, and creates a work statement list (WSL) that will be used to run the changes. During the analyze process, the embedded SQL statements semantics are checked and DB2 Admin automatically generates two new base versions:
  • A target version, which represents the objects in the DB2 catalog plus any prerequisite changes
  • A source version, which is the target version plus the changes for the change that being analyzed
DB2 Admin then invokes DB2 Object Comparison Tool to compare the source and target base versions to generate a WSL that will be used in the run process to apply the changes. The base versions that are used in this process are temporary and are not saved.

Topic: Modifying a change

Modifying a change
You can modify the change statements in an existing change if the change is in INITIAL, DEFINED, or ANALYZED status.

About this task
However, modifying an existing change is considered a manual intervention and is not recommended for several reasons. When you modify an existing change, DB2® Admin cannot apply virtual changes or determine whether pending changes exist. Modifying an existing change can also impact other existing changes substantially. For example, the change you are modifying might be a pending change that was applied when another change was created.
During the process of modifying a change, DB2 Admin checks only the syntax of each change statements. When you modify change statements through the Change Statements panel (ADB2C1S) panel, for example, syntax checking is completed at the time that you exit the panel. Semantic checking is done during the analyze process.

Topic: Importing changes

Importing changes
You can create a change by importing SQL statements from a data set. When you import the statements, a new change is created and registered. You can import multiple delta changes as a group in one change.

About this task
When importing changes:

  • You can import SQL statements (DDL) and you can import delta changes as generated by the DB2® Object Comparison Tool.
  • DB2 Object Comparison Tool will create a delta change if "CHANGE" is specified for "Generate apply jobs" on panel GOC5 (this generates parameter CMDELTA for GOC2CMP).
  • Importing an DB2 Object Comparison Tool change data set that is not generated as a delta change can have unwanted side effects. This cannot be checked during import.
  • You can import a mix of SQL statements and delta changes (as long as they logically relate).

If the imported SQL statements affect objects for which pending changes exist, you determine whether the imported change becomes a prerequisite change for those pending changes or not.

You can create a single change by importing multiple files at the same time. Each file must be one of the types mentioned in the following list. All types can be part of the same Import.

The data sets from which you are importing the SQL statements must be either:

  • The delta changes data set that was generated when changes were promoted with Change Management from another system. Thus, you can import the changes that were promoted from another system that uses Change Management.
  • The delta changes data set that DB2 Object Comparison Tool generated when objects were compared. DB2 Object Comparison Tool uses the worklist name for this data set (qualifier1.worklist_name.CHG). The worklist name will be generated by specifying CHANGE in the "Generate apply jobs" field on panel GOC5. You can specify a data set name and optionally specify a member name if the data set is partitioned.
  • A data set that contains SQL statements that meets these requirements:
  • A fixed-block sequential data set (RECFM=Fx,LRECL=80)
  • A member of a partitioned data set with a logical record length of 80 (RECFM=Fx,LRECL=80)

During the import process, the syntax of each change statements in imported SQL statements is checked. However, semantic checking is done during the analyze process.

If you are importing a delta changes data set, the data set must represent one generated delta changes file. Concatenating or merging multiple data sets into one can cause unpredictable results because statements are reordered during the import process.

When you import SQL statements into a change, the version of DB2 that is on the system must support the SQL statements that you are importing.

Publication number

SC19-3778-06

Copyright date

1995, 2014

Original publication date

1995/1/1

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
DB2 Administration Tool

Software version:

10.2.0

Operating system(s):

z/OS

Reference #:

7041313

Modified date:

2014-10-29

Translate my page

Machine Translation

Content navigation