Installing and Configuring SAS Grid Manager Client Utility

Installation Overview

The SAS Grid Manager Client Utility has been added in the second maintenance release after SAS 9.2. This utility enables users to submit SAS programs to a grid for processing without having SAS installed on the machine performing the submission.

If you install SAS Grid Manager for the first time using the second maintenance release after SAS 9.2, the SAS Grid Manager Client Utility is automatically installed and configured using the SAS Deployment Wizard if the utility is in the plan file.

Installation Prerequisites

The configuration for the SAS Grid Manager Client Utility assumes that all of the following actions have been performed:

The grid control server has already been installed. The configuration must retrieve the logical grid server definition from metadata.
The user name under which jobs are submitted is defined in metadata. If not, jobs submitted to the grid will fail.
A shared directory or shared file system is available to the client machine and the grid machines.
You have copied the SID file used to install the grid control server to the GRIDWORK directory and you have renamed the file to license.sasgsub. The SID file must have the Grid Manager product enabled in it.

Using the SASGSUB Configuration File

Most of the options that are used by the SAS Grid Manager Client Utility are contained in the sasgsub.cfg file, which is automatically created by the SAS Deployment Wizard. These options specify the information that the SAS Grid Manager Client Utility uses every time it runs. The sasgsub.cfg file is located in the Applications/SASGridManagerClientUtility/<version> directory of the configuration directory. The following information from the SAS Deployment Wizard is collected in the sasgsub.cfg file:

information to connect to the SAS Metadata Server (SAS Metadata Server name, port, user ID, and password). By default, the metadata password value is set to _PROMPT_, and the user is prompted for a password.
the path to the shared file system used to share files between the user and the grid.
the name of the SAS Application Server that contains the logical grid server definition.

If you are using a grid provider other than Platform Suite for SAS and are using the SAS Deployment Wizard in Expert mode, you can also specify these options:

the grid user and password, if required by the grid provider that you are using. If you specify the user name, the default value for the password is _PROMPT_, and the user is prompted for a password.
the path to any additional JAR files required by the grid provider.

The SAS Grid Manager Client Utility configuration assumes a location and name for the license file containing the SAS Grid Manager license. Move the SID text file to the GRIDWORK directory and rename the file to license.sasgsub.

Modifying the SASGRID Script File

If you installed your grid using SAS 9.2 before the second maintenance release, you must change the sasgrid script file. Follow these steps to change the file:

Edit the sasgrid.cmd file (Windows) or the sasgrid file (UNIX). The file is located in the GridServer directory under the configuration directory.

Note: If you are using Windows, the editor that you use must save the file using carriage return/line feed as the line termination characters.
Locate the SASEXEFILE environment variable and change the @sas.exec.file@ value to the path to the SAS executable file on all of the grid machines. For example, you might change the Windows sasgrid.cmd file from
```
set SASEXEFILE="@sas.exec.file@"
```
to
```
set SASEXEFILE="C:\Program Files\SAS\SASFoundation\9.2\sas.exe"
```
Save the file.
Copy the script file to each machine in the grid. The file should be located in the GridServer directory under the SAS configuration directory associated with the SAS Application Server used by the SAS Grid Manager Client Utility. For example, under Windows, you should copy the sasgrid.cmd file to C:\SASConfig\Grid\Lev1\SASApp\GridServer if the SAS configuration directory is C:\SASConfig\Grid\Lev1 and the application server is SASApp.

Note: If you do not update the script file on all machines in the grid, the SASGSUB -GRIDGETSTATUS command does not report the correct status for a job submitted to the grid. The job always appears to be in a “Submitted” state.