DATAPATH= LIBNAME Statement Option

Specifies a list of paths in which to store data partitions (.dpf) for an SPD Engine data set.

Default:	The primary path specified in the LIBNAME statement
Interactions:	PARTSIZE= LIBNAME Statement Option
Interactions:	PARTSIZE= Data Set Option
Engine:	SPD Engine Only

Syntax

Required Argument

Details

Example

Syntax

DATAPATH=('path1' <'path2'>...)

Required Argument

'path'

is a complete pathname in single or double quotation marks within parentheses. Separate multiple arguments with spaces.

Note: The pathnames specified in the DATAPATH= option must be unique for each library. Librefs that are different but reference the same pathnames can result in lost data.

Note: If your data is in the zFS file system, only one path specification is required. The zFS system automatically spreads the partitions across multiple logical volumes.

Details

The SPD Engine creates as many partitions as needed to store all the data. The size of the partitions is set using the PARTSIZE= option, and partitions are created in the paths specified using the DATAPATH= option in a cyclic fashion.

Note: If you are planning to store data in locally mounted drives and access the data from a remote computer, use the remote pathname when you specify the LIBNAME. For example, if /data01 and /data02 are locally mounted drives on the localA computer, use the pathnames /nfs/localA/data01 and /nfs/localA/data02 in the LIBNAME statement.

Example: DATAPATH= for First Partition

The path for the first partition is randomly selected and then continues in a cyclical fashion:

libname mylib spde '/metadisk/metadata'
   datapath=('/disk1/dataflow1' '/disk2/dataflow2' '/disk3/dataflow3');

For example, if /disk2/dataflow2 is randomly selected as the first path, the first partition is located there. The second partition is located in /disk3/dataflow3, the third partition is located in /disk1/dataflow1, and so on.