INCREASE: Increase Last Associator or Data Storage Data Set Size

The INCREASE function increases the size of the last data set currently being used for the Associator or Data Storage. This function may be executed any number of times for the Associator. The maximum of 99 Data Storage Space Tables (DSSTs) somewhat limits Data Storage increases before all 99 Data Storage extents must be combined into a single extent with either the REORASSO or REORDB function of the ADAORD utility.

Notes:

  1. The Associator and Data Storage data set sizes must be increased separately. It is not possible to increase both with a single operation.
  2. After an INCREASE operation is completed, the INCREASE function automatically ends the current nucleus session. This allows for the necessary Associator or Data Storage formatting with ADAFRM before a new session is started. An informational message occurs to tell you that the nucleus has been stopped.

graphics/util_adadbs_increase.png

This document covers the following topics:

Essential Parameter

ASSOSIZE | DATASIZE: Size to Be Increased

The additional number of blocks or cylinders needed by the Associator or Data Storage data set. To specify blocks, add a "B" after the value; for example, DATASIZE=50B.

Optional Parameters

NOUSERABEND: Termination without Abend

When a parameter error or a functional error occurs while this utility function is running, the utility ordinarily prints an error message and terminates with user abend 34 (with a dump) or user abend 35 (without a dump). If NOUSERABEND is specified, the utility will not abend after printing the error message. Instead, the message "utility TERMINATED DUE TO ERROR CONDITION" is displayed and the utility terminates with condition code 20.

Note:
When NOUSERABEND is specified, we recommend that it be specified as the first parameter of the utility function (before all other parameters). This is necessary to ensure that its parameter error processing occurs properly.

TEST: Test Syntax

Use the TEST parameter to test the operation syntax without actually performing the operation. Only the syntax of the specified parameters can be tested; not the validity of values and variables. See Syntax Checking with the TEST Parameter for more information about using this parameter.

Example

The Associator is to be increased by 400 cylinders.

ADADBS INCREASE ASSOSIZE=400

General Procedure

Start of instruction setThe general procedure for increasing the size of the Associator or Data Storage is as follows:

  1. Back up the database using the ADASAV utility. This step is optional but recommended.

  2. Execute the ADADBS INCREASE function.

  3. Format the additional space being added to the data set with the ADAFRM utility.

z/OS Procedures

The data set may be extended and the new blocks formatted by specifying the DISP=MOD parameter in the JCL. The SPACE parameter for the data set being increased should be set to

SPACE=(CYL,(0,n))

where n is the amount of space (in cylinders) being added. The ADAFRM control statement should also specify the number of cylinders being added.

If sufficient space is available on the volume or volumes currently comprising the data set, follow example 1. If additional volumes are required to satisfy the increase request, follow example 2 (for non DFSMS-managed data sets) or 3 (for DFSMS-managed data sets).

Example 1: INCREASE not requiring additional volumes

400 cylinders are to be added to an Associator data set. The control statement for the INCREASE function would be: 

ADADBS INCREASE ASSOSIZE=400

The following JCL example increases the Associator data set using ADAFRM:

//DDASSOR1  DD 
DSN=ADA.DB123.ASSOR1,DISP=MOD,SPACE=(CYL,(0,400))

and the actual ADAFRM control statement would be

ADAFRM ASSOFRM SIZE=400

Example 2: INCREASE requiring additional volumes (not DFSMS-managed)

400 cylinders are to be added to a single-volume Associator data set on volume VOL001. For the increase, the data set needs to extend to volume VOL002. The control statement for the INCREASE function would be: 

ADADBS INCREASE ASSOSIZE=400

Include the following step after the INCREASE step but before the FORMAT step to uncatalog the data set: 

//UNCATLG  EXEC PGM=IEFBR14
//DDASSOR1  DD  DSN=ADA.DB123.ASSOR1,DISP=(SHR,UNCATLG)

The following JCL example recatalogs the data set with the additional volume and increases the Associator data set using ADAFRM: 

//DDASSOR1  DD  DSN=ADA.DB123.ASSOR1,
//   DISP=(MOD,CATLG),VOL=SER=(VOL001,VOL002),SPACE=(CYL,(0,400))...

and the actual ADAFRM control statement would be:

ADAFRM ASSOFRM SIZE=400

To provide the increase in example 1 for multiple volumes, specify the volumes in the JCL: 

//DDASSOR1  DD  DSN=...
//             
DISP=(MOD,CATLG),VOL=SER=(V1,V2,...),SPACE=(CYL,(0,400))...

Include the following step after the INCREASE step but before the FORMAT step to ensure a correct catalog entry: 

//UNCATLG  EXEC PGM=IEFBR14
//DDASSOR1  DD  DSN=...,DISP=(SHR,UNCATLG)

Example 3: INCREASE requiring additional volumes (DFSMS-managed)

400 cylinders are to be added to a DFSMS-managed Associator data set. For the increase, the data set needs to extend onto another candidate volume belonging to the DFSMS Storage Group. The control statement for the INCREASE function would be: 

ADADBS INCREASE ASSOSIZE=400

Include the following step after the INCREASE step but before the FORMAT step to add further candidate volumes to the catalog entry for the data set: 

//ADDVOL EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ALTER ADA.DB123.ASSOR1 ADDVOLUMES(*)
/*

The following JCL example increases the Associator data set using ADAFRM:

//DDASSOR1  DD  DSN=ADA.DB123.ASSOR1,DISP=MOD,SPACE=(CYL,(0,400))...

and the actual ADAFRM control statement would be:

ADAFRM ASSOFRM SIZE=400