Administering Logging for SAS Servers

Collecting ARM Log Information for SAS Data Integration Studio Jobs

About Collecting ARM Log Information for SAS Data Integration Studio Jobs

When jobs are run interactively in SAS Data Integration Studio, ARM logging is used to collect performance-related events, which are displayed in the SAS Data Integration Studio application. You do not need to change the initial server configuration to enable the capture and display of these events.

To collect performance-related events for SAS Data Integration Studio jobs that are run in batch mode, you must change the configuration of the SAS DATA step batch server that executes the jobs. The logging configuration files for SAS DATA step batch servers include specifications for collecting ARM log information and sending it to a log file. However, logging is not enabled by default for these servers. You must configure your server so that logging is enabled.

If you have selected the Collect Runtime Statistics option for a SAS Data Integration Studio job, but ARM logging is not configured correctly for the DATA step batch server, then messages similar to the following will appear in the log when the job is run:

WARNING: ARMINIT: Negative appid returned - check macro parameters, appid=-1(0xFFFFFFFF)

Configure DATA Step Batch Servers on Windows or UNIX to Collect ARM Log Information

To configure your DATA step batch server on Windows or UNIX so that ARM logging is enabled for SAS Data Integration Studio Jobs, follow these steps:

Log on to SAS Management Console as a user who has the appropriate credentials to create or update server metadata (see Who Can Do What in the Server Manager Plug-in).
Expand the Server Manager node.
Expand the node for the application server that executes your SAS Data Integration Studio jobs (for example, SASApp). Then expand the node for the logical DATA step batch server (for example, SASApp - Logical DATA Step Batch Server).

Note: You cannot use the SASMeta application server to run SAS Data Integration Studio jobs. It is intended only for use in running metadata utilities.
Right-click the node for the physical DATA step batch server (for example, SASApp - SAS DATA Step Batch Server, and select Properties.
Select the Options tab, and add the following expression to the contents of the Command Line field:
```
-logconfigloc "file-specification"
```
In file-specification, provide the fully qualified path to the logging configuration file. Here is an example command line for a Windows system with the logging option added:
```
C:\SAS\Config\Lev1\SASApp\BatchServer\sasbatch.bat 
-logconfigloc "C:\SAS\Config\Lev1\SASApp\BatchServer\logconfig.xml"
```
Here is an example command line for a UNIX system with the logging option added:
```
/opt/SAS/Lev1/SASApp/BatchServer/sasbatch.sh 
-logconfigloc "/opt/SAS/Lev1/SASApp/BatchServer/logconfig.xml"
```
On the Options tab, click Advanced Properties. In the Advanced Properties dialog box, delete the contents of the Rolling Log Options field and replace them with a single underscore character (_).
Click OK to close the Advanced Properties dialog box, and click OK to close the Options tab.

Configure DATA Step Batch Servers on z/OS to Collect ARM Log Information

You can use the following procedure to configure your DATA step batch server on z/OS so that ARM logging is enabled for a SAS Data Integration Studio job:

Create a configuration file with the following contents:

***************************** Top of Data ************************
000001 logconfigloc=/<SAS-configuration-directory>/+
000002 Lev1/SASApp/BatchServer/logconfig.xml
000003 log=/<SAS-configuration-directory>/+
000004 Lev1/SASApp/BatchServer/Logs/<name-of-job>
**************************** Bottom of Data **********************

Note:
- Replace <SAS-configuration-directory> with the location that is specified in the CONFIG_DIR environment variable.
- If your application server has a name other than SASApp, then replace SASApp with the appropriate characters (for example, SASMain).
- Replace <name-of-job> with the name of the SAS Data Integration Studio job for which you want to collect ARM log information.
Save the configuration file in your SAS installation location.
In the JCL for each job that you want to collect ARM log information for, modify the //SASSTEP statement as follows so that it refers to the configuration file:

//SASSTEP EXEC PROCENW0,CONFIG=<SAS-installation-location>.<configuration-filename>(DSBS)

For example:

//SASSTEP EXEC PROCENW0,CONFIG=SVS02.V920.KJB.CONFIG(DSBS)

Top of Page