Specifying where to store the data (UNIT) parameter when creating or changing database files

Note:

Effective for Version 3 Release 6 the UNIT parameter is a no-operation (NOP) function for the following commands:

CRTPF
CRTLF
CRTSRCPF
CHGPF
CHGLF
CHGSRCPF

The parameter can still be coded; its presence will not cause an error. It will be ignored.

The system finds a place for the file on auxiliary storage. To specify where to store the file, use the UNIT parameter. The UNIT parameter specifies:

The location of data records in physical files.
The access path for both physical files and logical files.

The data is placed on different units if:

There is not enough space on the unit.
The unit is not valid for your system.

An informational message indicating that the file was not placed on the requested unit is sent when file members are added. (A message is not sent when the file member is extended.)

Tips for using the UNIT parameter when creating database files

In general, you should not specify the UNIT parameter. Let the system place the file on the disk unit of its choosing. This is usually better for performance, and relieves you of the task of managing auxiliary storage.

If you specify a unit number and also an auxiliary storage pool, the unit number is ignored. For more information about auxiliary storage pools, see the Backup and Recovery book.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]