Usage Note 20340: Generating a debug file for SAS® Data Integration Studio
Often SAS Technical Support requires a debug file to determine the cause
of an issue that is occurring at a customer site. The following instructions outline the steps you need to perform to create a debug file for SAS Data Integration Studio:
SAS Data Integration Studio 4.2 (and later releases)
Perform the following sequence of steps to create a debug file:
- Go to the SAS Data Integration Studio installation folder on your
client machine. The default installation location for the product is:
C:\Program Files\SASHome\SASDataIntegrationStudio\VERSION
Where VERSION is the version of SAS Data Integration Studio. Examples are 4.2 or 4.3.
- Make a copy of the file distudio.ini and save it so you have a backup of the file prior to modification.
- Open the file distudio.ini with a text editor.
- Go to the MainClass= line (the last line in the file) and add the following at the end of that line:
-debug -serverlog
- Save the changes you have made to the distudio.ini file.
- Launch SAS Data Integration Studio. Please note that when the product initializes a system command window will also appear. This is normal and expected. It is a result of the new options.
- Log into SAS Data Integration Studio and perform the steps necessary to reproduce the problem or unexpected condition. Then close SAS Data Integration Studio.
- Retrieve the SAS Data Integration Studio log file. This file is named DataIntegrationStudio_Log.txt. The location for this file varies depending on the version of Windows on the client machine.
On Windows XP and Windows 2003 Server the file location is:
C:\Documents and Settings\USERID\ApplicationData\SAS\SASDataIntegrationStudio\VERSION
On Windows 7 and Windows 2008 Server the file location is:
C:\Users\USERID\AppData\Roaming\SAS\SASDataIntegrationStudio\VERSION
Where USERID is the user id that is logged into the machine and VERSION is the version of SAS Data Integration Studio.
- Create a ZIP file that contains the DataIntegrationStudio_Log.txt file inside.
- Send this ZIP file as an e-mail attachment to your technical support track.
Note: After performing these steps and sending in the resulting debug log file you should rename the distudio.ini file with the debugging options and then restore the copy of the original that you made in step 2 to turn off debugging. If you need to perform debugging again in the future, just switch back to the file version with the debugging options.
SAS Data Integration Studio 3.4 (and earlier releases)
Perform the following sequence of steps to create a debug file:
- Go to the SAS Data Integration Studio installation folder on your
client machine. The default installation location for the product is:
C:\Program Files\SAS\SASETLStudio\9.1
- Create a new file in this folder, called DI_Debug.bat, and open it
with a text editor (for example, Textpad, Wordpad, Notepad, and so forth.)
- Open the file etlstudio.ini with a text editor. This file is found
in the SAS Data Integration Studio installation folder.
- Copy the entire text string that begins directly after
"CommandToExecute=".
- Go to DI_Debug.bat and paste this string into the first line of the file.
Now enclose the entire text string you just pasted within double quotes.
- Go to etlstudio.ini and copy the entire text string that begins
directly after "CommandLineArgs=".
- Go to DI_Debug.bat, insert a space at the end of the current text
string after the closing double quote, and then paste the CommandLineArgs
value on this same line. Do not enclose this text string
within double quotes.
- Go to the very end of the single line in DI_Debug.bat, and then add a
space and type the following on that same line:
-debug -serverlog > c:\DI_Debug.txt
Note: You can change the "c:\DI_Debug.txt" to a different location if
you like, just be sure the folder already exists.
At this point, you should have one long command, on a single line, in
DI_Debug.bat.
- Save DI_Debug.bat. Remember, it must reside in the SAS Data
Integration Studio installation folder.
- Cancel out of the text editor that you used to open etlstudio.
This prevents you from making any inadvertent changes to this file.
- Execute DI_Debug.bat and launch SAS Data Integration Studio.
When the product initializes, a system command window also appears.
This is normal because you are launching the product via a BAT file.
- Log into SAS Data Integration Studio, and perform the steps
necessary to reproduce the problem or unexpected condition.
Then close SAS Data Integration Studio. At this point, there should be a
debug file in the location specified in step 8.
- Create a ZIP file that contains the debug file inside.
- Send this ZIP file as an e-mail attachment to your technical support track.
Note: If the ZIP file exceeds the maximum allowable size (4 MB)for Technical Support
e-mail attachments, you can upload the file to the SAS Technical
Support Anonymous FTP server by following the instructions in SAS Note 20941 "Uploading Files to the SAS® Technical Support Anonymous FTP Server."
Operating System and Release Information
| SAS System | SAS Data Integration Studio | Microsoft Windows XP Professional | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 3.4 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 3.4 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2012-02-17 10:06:04 |
| Date Created: | 2007-06-05 12:23:11 |