Here is
why you should use ROPTIONS= instead of OPTIONS= in your libnames.parm
file.
ROPTIONS=
specifications override any corresponding options that your SAS users
include in their programs. Example 3 demonstrates explicit control
of disk usage by the system administrator. In the example, even if
SAS users specify file systems using LIBNAME DATAPATH= and INDEXPATH=
LIBNAME options during their LIBNAME connection, the administrator's
use of DATAPATH= and INDEXPATH= with ROPTIONS= overrides the SAS users'
specifications.
In contrast,
when you (the administrator) use OPTIONS=, a keyword that is syntactically
the same as ROPTIONS=, you are not overriding a user specification.
Instead, you are supplementing the user-specified options. In this
case, if a user specifies an option, the user's setting is implemented.
If the user omits an option, your OPTIONS= specification in the libnames.parm
file is used.
System
Administration recommendation: Do not specify DATAPATH=, INDEXPATH=,
and METAPATH= with OPTIONS=. If you use OPTIONS=, the disk allocation
results cannot be predicted. Instead, use ROPTIONS= to explicitly
control disk usage at your site.