CHANGE.DB command

If you specify the keywords SHARELVL, TYPEFP, or TYPEIMS while the database or an area of the DEDB is in use, the command fails.

You can also use the CHANGE.DB command to remove a rare authorization inconsistency between the subsystem (SSYS) record and the database or area (DB/AREA) record. This inconsistency occurs when either the SSYS record still has an entry for the DB/AREA in its authorized databases/areas list but the DB/AREA record no longer contains the SSID entry in its associated subsystem information list or the SSID entry is still in the DB/AREA but the SSYS record either no longer exists in the RECON data set or no longer contains an entry for the DB/AREA. Use the AUTH keyword for this purpose.

Subsections:

• Syntax
• Keywords
• Usage notes
• Example of changing a record for a database identified with the DBD keyword

Syntax

Use one of the following two diagrams for the CHANGE.DB command.

Notes:

• ¹ All four keywords are not mutually exclusive, but the two keywords in each pair are. It is possible to specify DBQUI with DBQUIH.

Or:

Notes:

• ¹ Required if using this command for a Fast Path DEDB.

Notes:

• ¹ Required if using this command for a Fast Path DEDB.

Keywords

ALL | DBD(name)

Mutually exclusive, optional keywords you use to identify the database for which the record is to be changed.

Restriction: If you specify the UNAUTH keyword, you must specify the DBD name. The ALL keyword is not valid with UNAUTH.

ALL

Specifies that you are changing all the databases registered in the RECON data set.

If any of the databases are HALDB masters or partitions, and you have specified any of the restricted keywords (for example, the PINIT or NOPINIT keywords), a warning message is issued and command processing continues.

DBD

Specifies that you are changing the record of a single database.

Restrictions for HALDB databases: For HALDB databases, specifies the name of a HALDB partition or the HALDB master (if you want to change all partitions of the HALDB master). For HALDB databases, you can use the CHANGE.DB command only as defined in the following table:

Table 1. Keyword definitions for HALDB partition and master

CHANGE.DB	name = TYPE=HALDB	name = TYPE=PART
ALTER | NOALTER	Yes	No
AUTH | NOAUTH	Yes (Global)	Yes
DBQUI | NODBQUI	Yes	Yes
DBQUIH | NODBQUIH	Yes	Yes
ICREQ | NOICREQ	Yes	No
NOBACK | BACKOUT	No	Yes
NOFULLSEG | FULLSG	N/A	N/A
NONRECOV | RECOVABL | USERRCOV	Yes	No
OLRBYTES	Yes	Yes
OLRCAP | OLRNOCAP	Yes	No
OLRDBDS(A | M)	No	Yes
OLRIMSID(name) | NOOWNER	No	Yes
OLRREL | OLRNOREL	No	Yes
OLRRGON | OLRRGOFF	No	Yes
OLRROOTS	Yes	Yes
OLRSEGS	Yes	Yes
OSAM8G | NOOSAM8G	Yes	No
PARTSEL | HIKEY	Yes	No
PINIT | NOPINIT	Yes	Yes
READON | READOFF	No	Yes
REORGI | NOREORGI	Yes	Yes
SHARELVL	Yes	No
TYPEFP | TYPEIMS	No	No
UNAUTH	No	Yes

ALTER | NOALTER

Optional keywords that set or remove the ALTER IN PROGRESS status of a HALDB database or a Fast Path DEDB database.

For HALDB databases, the ALTER keyword sets the ALTER IN PROGRESS flag in the RECON records of all of the partitions in the HALDB database. The ALTER COUNT for the HALDB is updated to the number of partitions involved in the alter process. The NOALTER keyword turns off the ALTER IN PROGRESS flag in all of the partition records and clears the counter in the HALDB record.

For DEDB databases, you can specify the ALTER keyword with the AREA keyword that identifies the area that is being altered. If AREA is not specified, this simulates the replace randomizer function, and the ALTER COUNT for the DEDB is updated. The NOALTER keyword resets the alter status for the entire DEDB and, if specified, the AREA keyword is ignored.

The ALTER IN PROGRESS status cannot be changed if any of the partitions in a HALDB or any of the areas in a DEDB are authorized.

AUTH | NOAUTH

Mutually exclusive, optional keywords you use to specify whether the database is authorized to participate in data sharing.

AUTH

Indicates that authorization processing for data sharing is permitted for the database.

NOAUTH

Indicates that authorization processing for data sharing is prohibited for the database.

DBQUI | NODBQUI

Mutually exclusive, optional keywords that you use to specify database quiesce options. These keywords cannot be specified with the ALL keyword.

DBQUI

Specifies that the QUIESCE IN PROGRESS flag for the database is to be set on. If the command is issued for a Fast Path DEDB, the command will set the quiesce in progress flag for all areas of the Fast Path DEDB. If the command is issued for a HALDB master, the command will set the quiesce in progress flag for all partitions of the HALDB.

Restriction: DBQUI and PINIT keywords cannot be specified together.

NODBQUI

Specifies that the QUIESCE IN PROGRESS flag for the database is to be set off. If the command is issued for a Fast Path DEDB, the command will reset the quiesce in progress flag for all areas of the Fast Path DEDB.

If the command is issued for a HALDB master, the command will reset the quiesce in progress flag for all partitions of the HALDB. In either case, the QUIESCE TYPE field will get reset. For a catalog HALDB master, all partitions of the HALDB will also get reset.

Restriction: NODBQUI is valid only if the QUIESCE HELD flag is off or the NODBQUIH keyword is also included in the command.

DBQUIH | NODBQUIH

Mutually exclusive, optional keywords that you use to specify database quiesce options. These keywords cannot be specified with the ALL keyword.

DBQUIH

Specifies that the QUIESCE HELD flag for the database is to be set on. If the command is issued for a Fast Path DEDB, the command will set the quiesce in progress flag for all areas of the Fast Path DEDB.

If the command is issued for a HALDB master, the command will set the quiesce in progress flag for all partitions of the HALDB.

Restriction: DBQUIH is valid only if the QUIESCE IN PROGRESS flag is on or the DBQUI keyword is also included in the command.

NODBQUIH

Specifies that the QUIESCE HELD flag for the database is to be set off. If the command is issued for a Fast Path DEDB, the command will reset the quiesce in progress flag for all areas of the Fast Path DEDB.

If the command is issued for a HALDB master, the command will reset the quiesce in progress flag for all partitions of the HALDB.

FULLSEG | NOFULLSG

Mutually exclusive, optional keywords that specify whether the full segment image is logged in the X'5950' log record when the segment is updated by a Replace (REPL) call. These keywords are valid only for Fast Path DEDBs.

By specifying these keywords, all areas for the specified DEDB are changed to the indicated setting. This setting is saved in the database record for this DEDB and is used as the default setting for any areas that are registered later for this DEDB. These keywords cannot be specified with the ALL keyword.

This setting is not changed in any areas if the specified DEDB is currently authorized, in which case you receive a DSP0045I message. The DEDB must be unauthorized before you can successfully issue the command.

FULLSEG

Indicates that the full segment image is to be logged.

NOFULLSG

Indicates that only the updated portion of a segment is to be logged.

ICREQ | NOICREQ

Mutually exclusive, optional keywords used to specify whether DBRC should enforce the requirement of taking an image copy of a nonrecoverable or user-recoverable database after it has been loaded or reorganized. This option affects all DBDSs within the DB.

ICREQ

Used to reset the IMAGE COPY NEEDED option. When this option is active, DBRC will set IC NEEDED ON in the DBDS record and increment the IMAGE COPY NEEDED COUNT in the DB record following initial load (PROCOPT=L) or a reorganization of the DBDS.

NOICREQ

Used to disable the IC NEEDED requirement. DBRC will not set IC NEEDED ON in the DBDS record or increment the IMAGE COPY NEEDED COUNT in the DB record following initial load or a reorganization of the DBDS. The IC NEEDED flag can still be set manually with the CHANGE.DB ICON command.

Restrictions:

• If the DB is recoverable, NOICREQ cannot be specified without also specifying NONRECOV or USERRCOV.
• NOICREQ will reset all DBDS IC NEEDED values to OFF and the DB IMAGE COPY NEEDED COUNT to 0.
• If the DB is changed to RECOVABL, this option is reset to ICREQ and IC NEEDED is set ON in all DBDSs; and the DB IMAGE COPY NEEDED COUNT is set accordingly.
• ICREQ | NOICREQ cannot be specified with the ALL keyword.

NOBACK SSID (name) | BACKOUT(value) SSID (name)

Mutually exclusive, optional keywords you use to specify whether the database needs backout by any subsystem. Do not use these keywords for a DEDB.

NOBACK

Indicates that the specified subsystem does not need to back out the database. You use this keyword to delete backout information from the specified database record.

If the held AUTH state and ENCODED state are zero, and if the BACKOUT-NEEDED flag is on, using the NOBACK keyword causes the associated subsystem information to be deleted from the database record.

BACKOUT

Indicates that the specified subsystem needs to back out the database the specified number of times. You need to specify the subsystem name with the SSID keyword. If you do not specify the SSID keyword with the BACKOUT keyword, this command fails.

SSID(name)

Required keyword specifying which subsystem encountered the backout errors.

name is any valid subsystem name.

With UNAUTH, SSID indicates which entry is to be removed from the associated subsystem information list of the database specified with the DBD keyword, or which SSYS record is to be changed by removing the specified DB/AREA from the authorized databases/areas list.

SSID is required with either the BACKOUT or UNAUTH keywords If coded without either BACKOUT or UNAUTH, the command fails.

NONRECOV | RECOVABL | USERRCOV

Mutually exclusive, optional keywords used to specify whether update logs of the specified database are recorded in the RECON data set.

NONRECOV

Specifies that no recovery is to be performed on the database. The effect of the NONRECOV keyword for full-function databases is different from that for Fast Path databases . When NONRECOV is specified for full-function databases, IMS logs backout information. When NONRECOV is specified for Fast Path databases, IMS does not log backout information.

RECOVABL

Specifies that the database is recoverable and all updates performed for the DBDSs or areas are to be registered in the RECON data set.

USERRCOV

Specifies that update allocations for the Fast Path DEDB are not to be recorded in the RECON data set. Database updates are logged by IMS, but DBRC cannot be used to manage recovery for the database. Recovery is allowed with JCL manually generated by the user. This keyword is valid only for Fast Path DEDBs.

Notes for USERRCOV:

1. USERRCOV should be used only if a critical need to reduce database open time exists and recoverability is required.
2. USERRCOV requires the user to provide their own manually created JCL for change accumulation and recovery.

Restrictions for NONRECOV, RECOVABL, and USERRCOV:

• HALDB master databases are supported by these keywords, but HALDB partitions are not.
• These keywords are not valid when ALL is specified with the CHANGE.DB command.
• You cannot take concurrent image copies of nonrecoverable or user-recoverable databases.
• If the database is registered as RECOVABL or USERRCOV, VIO data sets cannot be used for the output log (IEFRDER) in any job that updates the database. Temporary log data sets, such as VIO, are deleted at job termination, and therefore are not usable for recovery.
• NONRECOV does not support DEDBs with SDEPs.

OLRBYTES(value)

Optional parameter to specify a RECON value that indicates the number of bytes of a HALDB partition that have been moved by HALDB online reorganization. The value can range 0 - 47244640256. The value can be specified in decimal or hexadecimal equivalent. Hexadecimal values must be enclosed in quotation marks, such as X'B00000000'.

The OLRBYTES keyword is not valid for, or with, the following items:

• ALL, UNAUTH, OLRCAP, and OLRNOCAP keywords
• HALDB master
• HALDB partition that is marked as not capable of running OLR
• Fast Path databases

OLRCAP | OLRNOCAP

Mutually exclusive, optional keywords that specify if the HALDB can be reorganized online using HALDB OLR. There is no default and these keywords are valid only when the DBD is a HALDB master.

OLRCAP

Specifies (in the master database record and the partition database record) that the HALDB is capable of being reorganized online.

OLRNOCAP

Specifies (in the master database record and the partition database record) that the HALDB is not capable of being reorganized online. If the HALDB OLR cursor is active or if any M-through-V and Y DBDSs are active, the command fails. If the command completes successfully and the M-through-V and Y DBDSs and all of their associated records exist in the RECON data set, the M-through-V and Y DBDSs and all of their associated records are deleted from the RECON data set for all partitions.

OLRREL | OLRNOREL

Mutually exclusive, optional keywords that indicate whether the ownership of the HALDB OLR can be resumed by another IMS when the owning IMS abnormally terminates.

Restriction: In order to have the status changed, the HALDB OLR must be owned by an IMS that has abnormally terminated. The updated status is not reflected in a /DISPLAY DB OLR command output until the OLR is resumed.

OLRROOTS(value)

Optional parameter to specify a RECON value that indicates the number of roots of a HALDB partition that have been moved by HALDB online reorganization. The value can range 0 - 2147483647. The value can be specified in decimal or hexadecimal equivalent. Hexadecimal values must be enclosed in quotation marks, such as X'7FFFFFFF'.

The OLRROOTS keyword is not valid for, or with, the following items:

• ALL, UNAUTH, OLRCAP, and OLRNOCAP keywords
• HALDB master
• HALDB partition that is marked as not capable of running OLR
• Fast Path databases

OLRSEGS(value)

Optional parameter to specify a RECON value that indicates the number of segments of a HALDB partition that have been moved by HALDB online reorganization. The value can range 0 - 47244640256. The value can be specified in decimal or hexadecimal equivalent. Hexadecimal values must be enclosed in quotation marks, such as X'B00000000'.

The OLRSEGS keyword is not valid for, or with, the following items:

• ALL, UNAUTH, OLRCAP, and OLRNOCAP keywords
• HALDB master
• HALDB partition that is marked as not capable of running OLR
• Fast Path databases

OLRRGON | OLRRGOFF

Mutually exclusive, optional keywords that specify whether a HALDB OLR is in progress. These keywords are valid only for a HALDB partition.

OLRRGON

Specifies that a HALDB OLR is in progress. Both the A-through-J and the M-through-V data sets contain active data.

OLRRGOFF

Specifies that a HALDB OLR has completed and that either the A-through-J set of data sets or the M-through-V set of data sets contain active data. The flag is changed to indicate that the inactive data sets are now the active data sets. OLREORG CURSOR ACTIVE = NO is set in the DB record. The OLRIMSID is cleared.

Note: You might need to manually delete either the DB (HALDB) records or to add a stop time to them using the DELETE.REORG and NOTIFY.REORG commands.

OLRIMSID(name) | NOOWNER

Mutually exclusive, optional keywords that specify or change the name of the IMS that owns the HALDB OLR.

OLRDBDS(A | M)

Optional keyword that indicates the active set of DBDSs for this partition is either A-through-J and X or M-through-V and Y.

A

Specifies that the A-through-J and X data sets are active.

M

Specifies that the M-through-V and Y data sets are active.

If HALDB OLR is cursor active, this keyword indicates the set of DBDSs that are the input data sets.

OSAM8G | NOOSAM8G

Mutually exclusive, optional keywords that specify in the master database record whether a HALDB PHDAM or PHIDAM database supports up to 4 or 8 gigabytes of data in OSAM database data sets. There is no default, and these keywords are valid only when DBD is specified for a HALDB master.

OSAM8G

Specifies that the maximum capacity of OSAM data sets is 8 gigabytes of data. If the HALDB can be reorganized online (OLR capable), the command fails. Only a database that is not OLR capable can be changed to OSAM8G. If the database is currently OLR capable, you must specify OLRNOCAP and OSAM8G to change the maximum size to 8 gigabytes.

NOOSAM8G

Specifies that the maximum capacity of OSAM data sets is 4 gigabytes of data.

PINIT | NOPINIT

Mutually exclusive, optional keywords used to specify whether a HALDB partition needs to be initialized. Use this keyword after deleting and redefining one or more partition data sets without changing the database definition.

If the database specified by DBD keyword is a HALDB master, the change is made to all partitions. Otherwise, only the partition that is specified is changed.

Restrictions:

1. PINIT and NOPINIT keywords are not valid with ALL.
2. PINIT and DBQUI keywords cannot be specified together.

PINIT

Indicates that the partition needs to be initialized by using the DB Prereorganization utility or the HALDB Partition Data Set Initialization utility.

NOPINIT

Indicates that the partition does not need to be initialized.

RANDOMZR(name) | NORAND

Optional keywords used to change the name of the randomizing module for the Fast Path DEDB. If the keyword is specified and each IMS uses its own dedicated ACB library for ACBSHR=N, Fast Path verifies that the IMS accessing the DEDB is using this randomizer. Specify NORAND if you do not want the randomizer name to be verified. For ACBSHR=Y, randomizer name verification is never performed regardless of which keyword is specified.

RANDOMZR(name)

Specifies the name of the randomizing module for the Fast Path DEDB.

NORAND

Clears the name of the randomizing module for the Fast Path DEDB.

READON | READOFF

Mutually exclusive, optional keywords you use to specify whether the database can be restricted to read-only processing only. Do not use either keyword for a DEDB.

READON

Specifies that the database can be authorized only for read processing.

READOFF

Specifies that the database can be authorized for both read processing and update processing.

SHARELVL(0 | 1 | 2 | 3)

Optional keyword that you use to specify the level of data sharing for which authorized subsystems can share a database. You cannot specify this keyword for authorized DL/I databases.

The numbers 0, 1, 2, and 3 define the four types of data sharing levels.

0

Indicates that the database cannot be shared.

1

Indicates that the database can be shared by one IMS subsystem authorized for update and other IMS subsystems authorized only for read processing (no integrity processing). 1 can also indicate that the database can be shared by multiple IMS subsystems that have been authorized only for read processing. Level 1 is known as database-level sharing.

2

Indicates that the database can be shared by multiple, concurrent subsystems that have been authorized for update in a single-host processor environment. Level 2 is known as intrahost, block-level sharing.

3

Indicates that the database can be shared by multiple, concurrent subsystems that have been authorized for update in a multiple-host processor environment. Level 3 is known as interhost, block-level sharing.

Restrictions:

• The SHARELVL keyword must be greater than 0 for concurrent image copies.
• If you are using IRLM, and have specified SHARELVL 2 or 3, ensure that the VSAM SHAREOPTIONS (3 3) keyword is also specified in the database data set.
• The SHARELVL keyword applies to all areas in the DEDB.
• If you change a DEDB from level 0 or 1 to level 2 or 3, the first coupling facility structure name (CFSTR1) for all VSO areas in the DEDB is set to the name of the area. If you change a DEDB from level 2 or 3 to level 0 or 1, DBRC resets any specified coupling facility structure names to zeros, resets the LKASID keyword to NOLKASID, and resets the MAS keyword to NOMAS.

TYPEFP | TYPEIMS

Mutually exclusive, optional keywords you use to change the RECON record structure to a Fast Path DEDB or a DL/I database.

TYPEFP

Specifies that the database is a Fast Path DEDB and that the record structure in the RECON data set must be changed from IMS to Fast Path.

TYPEIMS

Specifies that the database is a DL/I database and that the record structure in the RECON data set must be changed from Fast Path to IMS.

UNAUTH

Removes an entry from the associated subsystem information list in the database specified by the DBD keyword, or removes an entry from the authorized databases/areas list in the SSYS record specified by the SSID keyword. You must specify the following keywords when you use UNAUTH:

DBD(name)

For the database name

AREA

If the database is a Fast Path DEDB

SSID(name)

For the IMS subsystem ID

Restrictions: The following restrictions apply when you use the UNAUTH keyword:

• If any keywords other than DBD, AREA, and SSID are specified for UNAUTH, the command fails.
• If AREA is specified without UNAUTH, the command fails.
• If the inconsistency between the SSYS and DB/AREA records as described above does not exist, the command fails.

AREA(name)

Required when UNAUTH is specified for a Fast Path DEDB. The name value is the name of the DEDB area. If you specify AREA without UNAUTH, the command fails.

PARTSEL(pgmname) | HIKEY

Mutually exclusive, optional keywords that are used to either identify or delete a user partition selection exit program name for a HALDB database. Deleting the partition selection exit program name causes all of the partition selection strings to be cleared. Adding or changing a partition selection exit program name will leave the partition high keys or partition selection strings intact. In all cases, all of the partitions are marked PINIT (partition initialization needed). The command will fail if NOPINIT is also specified. Use the CHANGE.PART command to specify new partition high keys or partition selection strings.

PARTSEL(pgmname)

Identifies a user Partition Selection Exit program name for a HALDB. The value is a program name that is up to 8 characters long.

Restriction: This keyword is not valid with ALL.

HIKEY

Removes an existing Partition Selection Exit program that is associated with a HALDB.

Restriction: This keyword is not valid with ALL.

REORGI | NOREORGI

Mutually exclusive, optional parameters that are used by online reorganization products (other than the HALDB Online Reorganization function that is delivered with IMS) to inform DBRC they are active (they intend to reorganize the database) to provide data integrity for full function databases. When the REORG INTENT flag is set to ON, database authorization fails for other reorganization products, batch access, and online image copy processes.

REORGI

Indicates that the database is going to be reorganized and sets the REORG INTENT flag to ON in the database record of the RECON data set if the following conditions have been met:

• Database type is valid. Must be full function including HALDB databases.
• The REORG INTENT flag is off.
• No batch jobs are authorized to the database.
• HALDB Online Reorganization (OLR) cannot have cursor active set (OLREORG CURSOR ACTIVE=YES).
• The database cannot be owned by an IMS OLRIMSID=imsid.

NOREORGI

Indicates that the database is not going to be reorganized (or has just completed reorganization) and sets the REORG INTENT flag to OFF in the database record of the RECON data set if the following conditions have been met:

• Database type is valid. Must be full function including HALDB databases.
• The REORG INTENT flag is on.

Usage notes