On
z/OS systems, the
SAS Deployment Wizard initially starts the SAS servers under UNIX
System Services (USS) by using scripts that are provided for each
server. After the initial installation and configuration has been
completed and validated, SAS recommends that you stop the servers
and restart them as started tasks.
The SAS Deployment Wizard
creates started task definitions for each server. The definitions
are stored in
SAS-installation-location.W0.SRVPROC.
To deploy the started tasks, see the instructions.html document that
is created by the SAS Deployment Wizard.
After the started tasks
are deployed, you can operate your servers as follows:
-
Log on as the SAS Installer
user (for example, sas).
-
To start a server, use
the following console command:
START started-task-name
To
stop a server, use the following console command.
STOP started-task-name
Note:
-
You can perform the equivalent
of a restart by stopping and then starting a server.
-
Stopping the metadata server stops
other components, including object spawners, OLAP servers,
SAS/CONNECT
spawners, and
SAS/SHARE servers.
-
Messages are written
to the system log when the SAS Metadata Server, the SAS OLAP Server,
or the
SAS/SHARE server is started or stopped. Automated tools can
scan the system log to determine the current operational state of
these servers. The log messages are displayed with the prefix
SAH,
as shown in the following examples:
SAH011001I SAS Metadata Server <(port-number)>, State, starting
SAH011999I SAS Metadata Server <(port-number)>, State, running
SAH019001I SAS Metadata Server <(port-number)>, State, stopping
SAH019999I SAS Metadata Server <(port-number)>, State, stopped
When servers are running
under USS, you can start and stop the servers as follows:
These methods are not recommended for production
environments.
For more information
about using SAS on
z/OS,
see the
SAS Companion for z/OS.