DataStage (DS) information and files to collect

-
DataStage (DS) information and files to collect

 AIX, Solarix, Linux, or HP-UX
Files and Data to collect
Description
Server Machine

<USER_HOME>/ds_logs/*.*
Not always present.
DataStage SERVER Machine

<CRED_USER_HOME>/ds_logs/*.*
All files contained in the ds_logs directory.
<IS_HOME>/Server/DSEngine/dsenv

<IS_HOME>/Server/DSEngine/uvconfig 
<IS_HOME>/Server/DSEngine/.odbc.ini
or the file pointed by the environment variable ODBCINI		ODBC.ini file
<IS_HOME>/Server/DSEngine/errlog 
<IS_HOME>/Server/DSEngine/DSAuditTrace.log 
<IS_HOME>/Server/PXEngine/etc/jobmon_ports 
<IS_HOME>/Server/PXEngine/java/JobMonApp.log.nnnAll historical logs
<IS_HOME>/Server/PXEngine/java/JobMonApp.logCurrent log
<IS_HOME>/Server/PXEngine/etc/operator.apt* 
<IS_HOME>/Server/DSEngine/orbtrc.<DATE>.txt
<IS_HOME>/Server/DSEngine/orbmsg.<DATE>.txt
Not always present
<IS_HOME>/Server/DSEngine/bin/orbtrc.<DATE>.txt
<IS_HOME>/Server/DSEngine/bin/orbmsg.<DATE>.txt
Not always present
<IS_HOME>/Server/Projects/_Project_Name_/&COMO&/*.*
Only present if tracing is enabled in the Administration client
<IS_HOME>/Server/Projects/_Project_Name_/heapdump.*
<IS_HOME>/Server/Projects/_Project_Name_/javacore.*
<IS_HOME>/Server/Projects/_Project_Name_/Snap.*
<IS_HOME>/Server/Projects/_Project_Name_/orbtrc.<DATE>.txt
<IS_HOME>/Server/Projects/_Project_Name_/orbmsg.<DATE>.txt		Heapdump, java core, and orb log files in the project
Windows
Files and Data to collect
Description
Client Machine

 <USER_HOME>\ds_logs\*.*
DataStage logs from the client user folders
 <IS_HOME>\Clients\Classic\orbtrc.<DATE>.txt
Not always present
 <IS_HOME>\Clients\Classic\orbmsg.<DATE>.txt
Not always present
 <IS_HOME>\Clients\Classic\javacore*Not always present
 <IS_HOME>\Clients\Classic\Snap*.trcNot always present
Client Machine, Information Server 8.5 and above

<USER_HOME>\Application Data\IBM\Information Server\DataStage Client\
<ClientTagID>\ErrorReports\*.zip		The ClientTagID is located in the <IS_HOME>\Version.xml file,
for example:<InstallType client="true"
clientTagId="652e77e8-ea1e-4850-a8b2-11e6a33dd884"
currentVersion="8.5.0.0" document="false" domain="true"
engine="true" repository="true"/>
Server machine

 <USER_HOME>\ds_logs\*.*
Not always present.
DataStage SERVER Machine

<CRED_USER_HOME>\ds_logs\*.*
Credential-mapped user logs
<IS_HOME>\Server\DSEngine\uvconfig 
<IS_HOME>\Server\DSEngine\.odbc.ini 
<IS_HOME>\Server\DSEngine\javacore*<IS_HOME>\Server\DSEngine\heapdump*Java Core and heap dump files, created by OutOfMemoryErrors: there may be several, collect the most recent ones
<IS_HOME>\Server\PXEngine\etc\jobmon_ports 
<IS_HOME>\Server\PXEngine\java\JobMonApp.log.nnnAll historical logs
<IS_HOME>\Server\PXEngine\java\JobMonApp.logCurrent log
<IS_HOME>\Server\etc\operator.apt* 
<IS_HOME>\Server\DSEngine\orbtrc.<DATE>.txt
<IS_HOME>\Server\DSEngine\orbmsg.<DATE>.txt
Not always present
<IS_HOME>\Server\DSEngine\bin\orbtrc.<DATE>.txt
<IS_HOME>\Server\DSEngine\bin\orbmsg.<DATE>.txt
Not always present
<IS_HOME>\Server\projects\_Project_Name_\&COMO&\*.*
Only present if tracing is enabled in the Administration client
<IS_HOME>\Server\Projects\_Project_Name_\heapdump.*
<IS_HOME>\Server\Projects\_Project_Name_\javacore.*
<IS_HOME>\Server\Projects\_Project_Name_\Snap.*
<IS_HOME>\Server\Projects\_Project_Name_\orbtrc.<DATE>.txt
<IS_HOME>\Server\Projects\_Project_Name_\orbmsg.<DATE>.txt		Heapdump, java core, and orb log files in the project
DataStage Operations Console (Information Server 8.7 and above only)
Files and Data to collect
Description
<IS_HOME>/Server/DSODB/*.cfg<IS_HOME>/Server/DSODB/logs/AppWatcher*.log<IS_HOME>/Server/DSODB/logs/JobRuntime.err<IS_HOME>/Server/DSODB/logs/JobRuntime.log<IS_HOME>/Server/DSODB/logs/EngMonApp*.log<IS_HOME>/Server/DSODB/logs/ResMonApp*.log<IS_HOME>/Server/DSODB/logs/handler*.log<IS_HOME>/Server/DSODB/logs/odbqueryapp*.log<IS_HOME>/Server/DSODB/logs/odbqapp*.log<IS_HOME>/Server/PXEngine/DSResourceTracker/Tracker*.log<IS_HOME>/ASBNode/asbagent_startup.out<IS_HOME>/ASBNode/asbagent_startup.err<IS_HOME>/ASBNode/bin/Agent.out<IS_HOME>/ASBNode/bin/LoggingAgent.out<WAS_IS_PROFILE>/logs/datastage_console_web.log<WAS_IS_PROFILE>/logs/datastage_api_restservices.log<WAS_IS_PROFILE>/logs/datastage_api_services.log
Log and configuration files used by DataStage Operations Console
<IS_HOME>/Server/DSODB/events/<YYYYMMDDHH_date>/*
Collect all files inside the most recent folder. Folder name is in YYYYMMDDHH format, for example '2011092813'
DataStage Operational Metadata (Information Server 11.3 and above only)
Files and Data to collect
Description
<IS_HOME>/Server/DSOMD/logs/*.log
Log files used by DataStage Operational Metadata
<IS_HOME>/Server/DSOMD/xml/*.xml*
XML files used by DataStage Operational Metadata


Collecting DataStage specific information
DataStage can create logging and tracing information at multiple layers and in different components:
DataStage Client-Server Tracing
This traces calls made from the DataStage clients (such as Designer) to the DSServer engine helper programs. Tracing can be turned on at the project level. When tracing is turned on, all clients that attach to that project produce a large trace file. Also, each time a client attaches to DataStage, a warning message displays indicating that tracing is turned on. Click OK  to proceed.
Command
  1. Start up Administrator.
  2. Navigate to Project > Properties > Tracing.
  3. Ensure that Server Side Tracing is enabled.
  4. Open the Designer. A message displays that tracing is turned on. Click OK.
  5. Replicate the steps in the application that produce the error that you want to report to IBM Support
  6. Close the Designer.
  7. In the Administrator, uncheck the Server Side Tracing flag again (so you do not leave it on by mistake).
  8. Ensure that the project directory on the server "&COMO&". i.e.,C:\IBM\InformationServer\Server\Projects\yourproject\&COMO&  now contains a DSR_TRACE_username-number file.
Files and Data to collect
<IS_HOME>\Server\projects\_Project_Name_\&COMO&\*.*

DataStage Client-JuggerNet Proxy Tracing
Use the JuggerNet Proxy Tracing to detect Codemesh problems. JuggerNet Proxy Tracing is set on a per-client basis.
Command
Set the following environment variables:
    XMOG_TRACE_LEVEL=TraceVerbose
    XMOG_TRACE_FILE=C:\xmogtrace.txt
Files and Data to collect
C:\xmogtrace.txt

DataStage Client-Spy Tracing
The Spy trace shows calls made from the Java layer of the client. It is turned on for individual clients.
Command
  1. Create a file named newrepos.debug.properties that contains the following environment variable:  
    NewRepos.spy.trace=true
  2. Save the file on the client machine in the  <IS_HOME>\ASBNode\conf  folder.
The logs are written to <USER_HOME>\ds_logs\dstage_wrapper_spy_NN.log where NN is a number from 1 to 20.
Files and Data to collect
<USER_HOME>\ds_logs\dstage_wrapper_spy_NN.log     where NN is a number from 1 to 20

 Increase Log Detail
 Increase the detail included in the client side log files.
Command
Create a file named newrepos.debug.properties that contains the following environment variables:  
  • log4j.logger.com.ascential.dstage.impactanalysis=DEBUG
  • log4j.logger.com.ascential.dstage.advancedfind=DEBUG
  • log4j.logger.com.ascential.dstage.proxies=DEBUG
  • log4j.logger.com.ibm.datastage.repository=DEBUG
Files and Data to collect
<USER_HOME>\ds_logs\*.*

DataStage Trace File Location
For InfoSphere Information Server 8.1 through 9.1.x, trace files may be generated in the current folder when some DataStage tools are run. If present, these trace files should be included in the data gathered for IBM Support.
Command
The following commands may generate log files and atrifacts to collect:
    DSXImportService
    dsjobs
    ISTools
Files and Data to collect
orbtrc.<DATE>.txt from the current folder
orbmsg.<DATE>.txt from the current folder

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more