FORCE (Force Keyword Values) › How to Use

How to Use

Use an alternate (additional) SYSIN with a DBUTLTY FORCE function to force a keyword value and ignore a different user specification. That is, using FORCE forces the value you specify to be used, preventing other users from performing any overrides.

►►FORCE INIT_IXX_BLKSIZE=nnnn ───────────────────────────────►◄

Command

FORCE

Invokes the function to force certain keyword values.

Use no blank before FORCE when you specify it in columns 1-7. Follow FORCE with one blank (and use no continue lines).

Required Keyword

INIT_IXX_BLKSIZE=nnnn

INIT_IXX_BLKSIZE=nnnn gives you the ability to force a value nnnn for the block size during an INIT function with AREA=IXX used to initialize an index area (IXX or multiple data set index).

Example

Suppose an alternate SYSIN contained the following statement:

FORCE INIT_IXX_BLKSIZE=5555

With that statement, 5555 becomes the block size used for an INIT of an index area, even if the non-alternate SYSIN contains a different BLKSIZE value.

Consider the following:

• The alternate (additional) SYSIN can be overridden for any step by having a JOB/STEPLIB pointing to a different DBIN1PR module.
• If the DBIN1PR module indicates a data set, the additional SYSIN can be overridden for any step by having a DD statement pointing to a different input.
• All DBIN1PR input is echoed to the console without option, for example: DB10096I - DBIN1PR PROCESSED - FORCE INIT_IXX_BLKSIZE=5555.
• Even with the use of the FORCE function, you have to enter a valid value if you specify the option.

  For example if you set a keyword with an invalid value of BLUE (BLKSIZE=BLUE) for an index INIT, that error is flagged and the function fails until the error is removed or corrected. If the value is correct, however, the FORCE is of course appropriately applied.

• The use of FORCE does not force an error.

Sample Report

Following is a sample report page. For an example report header, see Sample Report Headers.