Creating and Starting the Default Service

Overview of Creating the Default Service

You must create a default Application Dispatcher service to run any of the sample programs supplied with SAS/IntrNet software. Before you create the service, you must reserve a TCP/IP port number for your default Application Dispatcher service. Consult your system administrator or check your services definition file to find an available port number.

You should create the default service with the Create Socket Service Task under SAS/IntrNet Service Tasks in the SAS Deployment Manager. This utility is available for

After you create and start the service, continue with Adding the Default Service Definition to the Application Broker configuration file.

Windows Platforms

Services can be created on Windows platforms using the SAS Deployment Manager. Perform the following steps to create and start the default service:

From the Start menu, select ProgramsSASSAS Deployment Manager. The SAS Deployment Manager window appears.
Select Create Socket Service. Click Next to continue.
The default service name default appears in the service name page. Click Next to continue.
Specify the directory where you want the SAS Deployment Manager to place your service directory and control files. The default location (under your SASHOME directory) is recommended. Click Next to continue.
Enter the TCP/IP port number that you reserved for the default Application Dispatcher service. Click Next to continue.
A password is not necessary for the default service. You can add an administrator password later if you use this service for production applications. Click Next to continue.
The Stage 1: Create Socket Service page displays. Click Start to create the service.
The Deployment Complete page displays. If there is a green check mark next to 1. SAS/IntrNet, click Finish to complete the set up of the default service. If there is a yellow exclamation point or a red X next to 1. SAS/IntrNet, check the log to see the warning or error. The log is in the <SASHOME>\InstallMisc\InstallLogs directory, where <SASHOME> is the path to the SAS home directory.
From the Start menu, select ProgramsSAS (or another program group where SAS is installed)IntrNetdefault ServiceStart Interactively. Your default Application Server should now be running.

UNIX Platforms

Services can be created on UNIX platforms using the SAS Deployment Manager. Perform the following steps to create and start the default service:

From a system prompt, submit the following command:
```
<SASHOME>/SASDeploymentManager/9.3/sasdm.sh
```
where <SASHOME> is the path to the SAS home directory. The Choose Language window appears. Select the desired language and click OK. The SAS Deployment Manager window appears.
Select Create Socket Service, and then click Next to continue.
The default service name default appears in the service name page. Click Next to continue.
Specify the directory where you want the SAS Deployment Manager to place your service directory and control files. The default location (under your UNIX $HOME directory) is recommended. Click Next to continue.
Enter the TCP/IP port number that you reserved for the default Application Dispatcher service. Click Next to continue.
A password is not necessary for the default service. You can add an administrator password later if you use this service for production applications. Click Next to continue.
The Stage 1: Create Socket Service page displays. Click Start to create the service.
The Deployment Complete page displays. If there is a green check mark next to 1. SAS/IntrNet, click Finish to complete the set up of the default service. If there is a yellow exclamation point or a red X next to 1. SAS/IntrNet, check the log to see the warning or error. The log is in the <SASHOME>/InstallMisc/InstallLogs directory, where <SASHOME> is the path to the SAS home directory.
The SAS Deployment Manager has created a start.sh file to start the default Application Server. Change to the service directory path and start the server by submitting the following command:
```
./start.sh
```

z/OS Platform

The configuration utility provided for z/OS is a batch job. It is installed as a member named INETCFG in the CNTL data set that you created as the first step in the installation of your SAS software. To use the utility, you must edit the parameter file (member INETEDTP in the CNTL data set), edit the INETCFG job, and then submit the INETCFG job. The INETEDTP member contains the parameters necessary for creating a service.

To create and start the default service on z/OS, perform the following steps:

Edit the INETEDTP member.
Verify the name of the service that you are creating. The service name is defined by the line beginning with ISVC= and should be DEFAULT.
Verify that the service is a socket service. The line containing ISVCTYP=%SOCKETTYP should be uncommented.
Locate the line I$PORT1. Change the value 5001 to the correct port number or network service name for your Application Server.
Save and close INETEDTP.
Edit INETCFG to verify the job header information. Verify that the service name is DEFAULT. If you make changes, be sure to save them. Do not change SASEDITP to INETEDTP because this is your original SAS installation parameters file.
Submit the INETCFG JCL job for processing. The INETCFG job submits another job (INETCFGA). Verify that both jobs completed with a return code of 0. If they completed successfully, you now have the data sets and members necessary for running the default service. If the INETCFG job failed, examine the messages and sysprint members for error messages. You might have supplied a pathname in one of your INETEDTP parameters that is too long if you see a message that reads as follows:
```
ERROR: THIS REPLACEMENT CAUSES RESULT TO EXCEED OUTPUT LRECL
```
Try shortening this pathname and rerun INETCFG.
Note: Before you run INETCFG again, you must delete any data sets created by the previous failure of INETCFG. You can find these data sets by looking in the namespace determined by your original SAS installation. For example, if your SAS software was installed with the prefix name SYS.SAS and your failed INETCFG was trying to create the DEFAULT service, then delete all data sets beginning with the name prefix SYS.SAS.WEB.DEFAULT before running INETCFG again.
The configuration utility creates a server root in a partitioned data set (PDS) named prefix.WEB.DEFAULT, where prefix is the data set prefix that you supplied during your SAS installation. The PDS contains any JCL procedures and server start-up code required for starting the service. Find the following members:

APSTRT1

contains the JCL necessary to run the corresponding @APSTX1 file as a started task. You should move this file to your started task library and enable it as a started task.

@APSTX1

contains the SAS code that invokes the server. This file is called by the JCL in the corresponding APSTRT1 file. This SAS program must remain in the PDS where it was created.

In addition to the server root PDS, the configuration utility creates an empty PDS named prefix.WEB.DEFAULT.TDIR, where prefix is the data set prefix that you supplied during your SAS installation. The Application Server uses this PDS as a scratch location.
You must modify the permissions for the data sets created here so that the server can write to them as necessary. To modify the permissions, create a special RACF data set profile that applies to all the data sets in this service (prefix.WEB.DEFAULT.*). The RACF data set profile should also grant write access to the user ID of the Application Server.
Issue a START command from the system console to start the default Application Server.