cd
command,
which will change the current directory of your SAS session: data _null_; call system ('cd /users/smith/report'); run;The search for any relative (partial) filenames during the SAS session will now begin in the
/users/smith/report
cd
, pwd
, setenv
,
or umask
and, if so, executes the SAS equivalent
of these commands. The SAS cd
and pwd
commands
are equivalent to their Bourne shell counterparts. The SAS setenv
command
is equivalent to its C shell namesake. The SAS umask
command
is equivalent to the numeric mode of the umask
command
supported by the Bourne, Korn, and C shells. These four commands are
built into SAS because they affect the environment of the current
SAS session. When executed by SAS software, they affect only the
SAS environment and the environment of any shell programs started
by the SAS session. They do not affect the environment of the shell
program that began your SAS session.
cd
, pwd
, or setenv
,
SAS starts a shell in which it executes the command that you specified.
The shell that is used depends on the SHELL environment variable.
If the command is umask
, but you do not specify
a mask, then SAS passes the
command to the shell in which the current SAS session was started.
For more information about the umask
command,
see Changing the File Permissions for Your SAS Session.cd
, pwd
, setenv
,
or umask
commands, as it does when a command
is specified by itself (without semicolons).
cd
, pwd
, setenv
,
or umask
commands, see How SAS Processes a Single UNIX Command.umask
. The umask
command
applies a new “mask” to a file, that is, it sets new
file permissions for any new file that you create. In this way, the umask
command
can provide file security by restricting access to new files and directories
for the current process.
umask
varies.
Some systems, like Secure Linux, use a default of 220. Other systems
use 022 as the default. System administrators can set their own default
value and you can check your default and change it in your own .kshrc,
.cshrc, or .profile files. These values affect all child processes
that are executed in the shell. Any subsequent file that you create
during the current SAS session will inherit the permissions that you
specified. The permissions of a file created under a given mask are
calculated in octal representation.