INIT CXX/FXX/IXX/LXX/WXX/Data Area

You must run the INIT function to format space allocated to these areas before the area can be used by Datacom/DB. You do not need to format the Statistics and Diagnostics Area (PXX).
datacom
You must run the INIT function to format space allocated to these areas before the area can be used by
Datacom/DB
. You do not need to format the Statistics and Diagnostics Area (PXX). See each option for a description.
INIT Restrictions
You can initialize a database Index
only
if no task is actively processing the database. You can use the ACCESS option (see ACCESS (Restricting Opens or Maintenance) for details) to prevent opens for a database that contains the index that you want to initialize.
A data area or index area data set cannot be shared by two CXXs. This can result in data integrity problems and index corruption.
Multivolume INITs
You can initialize these areas across multiple extents on multiple volumes. For a description of how the operating system handles secondary allocations, see your operating system JCL manual.
VOLUMES=4multivolumeINITs (15.0)
If the keyword VOLUMES= is specified with a number value that is less than the number of volumes provided, the INIT function only initializes the number specified in the VOLUMES= keyword. For example, for a DD statement with VOL=SER=(VOL001,VOL002,VOL003), without the VOLUMES= keyword DBUTLTY initializes 1 to 16 extents on VOL001, 1 to 16 extents on VOL002, and 1 (or more) extents on VOL003. But with the VOLUMES= keyword set as VOLUMES=2, DBUTLTY initializes 1 to 16 extents on VOL001 and one (or more) extents on VOL002. Unused extent possibilities on VOL002 and VOL003 are available for dynamic extend.