Problems with the SAS IT Resource Management Client

The IT Resource Management Client automatically keeps log files for certain operations such as the following:

creating an IT data mart
running the Adapter Setup wizard
adding staged tables

These log files can be useful to you or to Technical Support personnel, when investigating a problem.

On the client, these log files are located in a directory that is determined based on the APPDATA environment variable.

On Windows XP, this location is typically C:\Documents and Settings\userid\Application Data\SASHome\SASITResourceManagement\3.21.
On Windows 7, this location is typically C:\Users\userid\AppData\Roaming\SASHome\SASITResourceManagement\3.21.

Server Logging Files

All servers, such as the SAS Metadata Server, the object spawner, and the application and workspace servers, can be configured to have logs. These logs can be useful in diagnosing problems. For information about configuring logging for these servers, see “Administering Logging for SAS Servers” in the SAS Intelligence Platform: System Administration Guide.

Turning On Standard Execution-time Debugging (ETLS_DEBUG)

To turn on execution-time debugging in the generated code for SAS Data Integration Studio and SAS IT Resource Management transformations, add the following line to the generated code, before the transformation for which you would like additional debugging information: %LET ETLS_DEBUG=1;

Turning On Additional Execution-time Debugging (LOGGERLEVEL)

To turn on additional execution-time debugging information in the generated code for SAS IT Resource Management transformations, add or edit the following line to the generated code before the transformation for which you would like additional debugging information: %LET LOGGERLEVEL=[level];

Legal values for [level] include: FATAL, ERROR, WARN, INFO, DEBUG, or TRACE. Users who want additional debugging information should set the level to DEBUG: %LET LOGGERLEVEL=DEBUG;

Investigating Problems Using Java from SAS Foundation

Some features that use Java from SAS Foundation. These features include PROC INFOMAPS, the Information Map LIBNAME engine, and the migration of IT Resource Management 2.7 PDBs to IT data marts supported in SAS IT Resource Management 3.2 and later. For problems in running Java from SAS, use the following techniques to investigate whether SAS is configured correctly to use Java:

Make sure that the Java JVM can be started, and that it is the correct version of the JVM. To do so, submit this SAS statement:
```
proc javainfo all; 
run; 
```
The results of this code will include JVM details and properties. This statement can be added to the SAS code of a deployed job, or submitted directly from the ToolsSource Editor menu item in SAS Data Integration Studio.
Check the JREOPTIONS settings to make sure that the Java options are correct, particularly in these elements:
- Memory options such as -Xmx are specified according to the installation and configuration documents.
- To see the current JREOPTIONS, submit this SAS statement:
  proc options option=jreoptions; run;
  
  This statement can be added to the SAS code of a deployed job, or submitted directly from the ToolsSource Editor menu item in SAS Data Integration Studio.

Note: When running jobs in SAS Foundation, make sure that SAS is invoked using the appropriate configuration files because these files have been written specifically for use by SAS IT Resource Management.

Troubleshooting Error Messages in the SAS Log

Error message is displayed in the SAS log: “ERROR: Failed to insert filter” or “ERROR: Failed to insert data source.”

Make sure that the user who is running the job has the proper authorizations. To do so, open the SAS Management Console and perform the following steps:

Set the repository to Foundation.
In the User Manager component, select the user profile of the person who is running the job.
On the Logins tab, locate the entry for the authentication domain of the workspace server that was in use at the time of the error. (Each workspace server has an authentication domain.) The user ID and the password should be specified. The password cannot be left blank.

Note: Whenever the server is reset, the password might not have been saved. (A password field of asterisks does not necessarily contain your password.) In this case, you should manually update your password.