Altering Database Default Options

Modifying database defaults is equivalent to modifying the value of the attribute for each item or structure in the database for which the attribute is appropriate. When defaults are changed, the user must ensure that the new value is valid for all affected items and structures. The defaults can be overridden for any individual structure.

Allowed Changes to Database Default Options details the changes that can be made to the database default options. Numbers in parentheses refer to explanatory notes following the table.

Table 20. Allowed Changes to Database Default Options

Option

Model

Update

File Format Conversion (No Item Changes)

Record Format Conversion (Item Changes)

BUFFERS

Yes

Yes (3)

Yes

Yes

CCSVERSION

No

No

Yes

Yes

CHECKSUM

No

No

Yes

Yes

DATAENCRYPT

No

No

Yes

Yes

DATAENCRYPTKEYSET

No

No

Yes

Yes

DATAMASK

No

No

Yes

Yes

DIGITCHECK

No

Yes

Yes

Yes

DUMPSTAMP

No

No

Yes

Yes

LOCK TO MODIFY DETAILS

No

Yes (1)

Yes

Yes

Disk/pack

No

Yes (2, 4)

Yes (4)

Yes (4)

INITIALVALUE

No

Yes (1)

Yes

Yes

OBFUSCATIONLEVEL

No

No

Yes

Yes

REBLOCK

No

Yes (1)

Yes

Yes

REBLOCKFACTOR

Yes

Yes (3)

Yes

Yes

RECORDCOUNT

No

No

Yes

Yes

SECURITYGUARD

Yes

Yes

Yes

Yes

STRENCRYPT

No

No

Yes

Yes


Explanatory Notes

  1. Recompile the DMSUPPORT library.

  2. If a control file specification is not used, you must recompile user programs and tailored data management software. Recompilation of the DMSUPPORT library is not necessary.

  3. Recompilation of tailored data management software is not necessary.

  4. When the disk/pack option is changed, the system searches for any affected structures on the new device. The structures can be copied from the old device to the new device using library maintenance. If the structure is in a permanent directory, the permanent directory must exist on the new device or be created manually before copying the structures.