Specifying Physical Files

Overview of Physical Files

Wherever you specify the name of a physical file internally (for example, in a SAS LIBNAME or FILENAME statement, in a LIBNAME or FILENAME function, in a DATA step, or in a SAS procedure), the name can be in any of these forms:

a fully qualified data set name such as 'SAS.SAS9.AUTOEXEC'. A PDS member name, such as 'MY.PDS(MEMBER)', might also be specified, although not for a LIBNAME statement or function.
a partially qualified data set name such as''.CNTL'. SAS inserts the value of the SYSPREF= system option (which is usually user ID by default) in front of the period. For more information, see SYSPREF= System Option: z/OS. In the following example, an OPTIONS statement is used to assign a value of USER12.SAS9 to the SYSPREF= system option. When SAS executes the FILENAME statement, it interprets '.RAW.DATAX' as 'USER12.SAS9.RAW.DATAX'.
```
options syspref=user12.sas9;
filename raw2 '.raw.datax' disp=old;
```
a temporary data set name such as '&MYTEMP'.
a UFS path. It can be a full path that begins with a slash (/) or a tilde (~), as the following examples indicate:
```
filename fullpath '~/subdir/filename.sas';
filename relative 'subdir/filename.sas';
```
a concatenated series of names or a wildcard name consisting of multiple UNIX File System (UFS) files or members of a partitioned data set (PDS, PDSE). For more information, see Concatenating External Files. However, note that the LIBNAME statement and LIBNAME function does not support the wildcard syntax for members of partitioned data sets. It is possible to concatenate SAS libraries. For more information, see LIBNAME Statement: z/OS.

Note: Names of physical files should be enclosed in quotation marks.

For information about encodings for z/OS resources such as data set names and UFS paths, see Encoding for z/OS Resource Names.

Specifying Physical Files with the INCLUDE Command

Here are examples of the INCLUDE command that illustrate the various ways that you can specify physical files:

INCLUDE MYPGM

MYPGM is a fileref that was previously associated with an external file.

INCLUDE MYPGM(PGM1)

PGM1 is a member of the partitioned data set that is associated with the fileref MYPGM.

INCLUDE 'USERID.TEST.PGMS'

This is an example of a sequential data set name.

INCLUDE 'MVS:USERID.TEST.PGMS'

This is an example of a sequential data set name that uses the designator for the MVS file system.

INCLUDE 'USERID.TEST.PGMS(AAA)'

This is an example of a data set name with a member specified.

INCLUDE '.TEST.MYPGM'

Assuming that the FILESYSTEM= system option is set to MVS, SAS adds a prefix to this data set name that contains the value of the SAS system option SYSPREF=, which defaults to your system prefix. If FILESYSTEM=HFS, SAS looks into your default UNIX System Services directory for the “hidden” file .TEST.MYPGM.

INCLUDE 'HFS:/u/userid/mypgms/mypgm1.c'

This is an example of a path to a UNIX File System (UFS) file in the Hierarchical File System (HFS), represented by a fully qualified path. For more information about HFS and UFS, see HFS, UFS, and zFS Terminology.

INCLUDE 'pgms/mypgms/mypgm1.c'

This is an example of a relative path to a UNIX File System file. Any filename containing a slash (/) is assumed to be in UNIX File System, regardless of the value of the FILESYSTEM= system option. If the pathname does not begin with a slash (/), then SAS searches for the file in the default UFS directory for that user.

Handling of Nonstandard Member Names

You can use the SAS system option FILEEXT= to specify how extensions in member names of partitioned data sets are to be handled. For more information, see FILEEXT= System Option: z/OS.