METAPATH= LIBNAME Statement Option

Specifies a list of overflow paths in which to store metadata (.mdf) component files for an SPD Engine data set.

Default:	the primary path specified in the LIBNAME statement
Engine:	SPD Engine only

Syntax

Details

Example

Syntax

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

Required Argument

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

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

Details

The METAPATH= option is specified for space that is exclusively overflow space for the metadata component file. The metadata component file for each data set must begin in the primary path, and overflow occurs to the METAPATH= location when the primary path is full.

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. 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.You cannot change the pathnames of the files. When you specify the DATAPATH=, INDEXPATH=, METAPATH=, or primary path LIBNAME options, make sure that the identical paths that were used when the data set was created are used every time you access the data sets. The names of these locations are stored internally in the data set. If you change any part of the pathname, the SPD Engine might not be able to find the data set or might damage the data set.

Example: Creating Overflow Metadata File Partitions

The following example creates overflow metadata file partitions as needed using the path /DISK1/METAFLOW1.

When /METADISK/METADATA is full, the metadata overflows to /DISK1/METAFLOW1.

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