DS Command

This is some DS commands, but we have to use it wisely especially for unexperienced user, because it sometimes can make your DS become unstable.

DS.TOOLS Menu 
Option Text on Screen 
1 Report on project licenses 
2 Rebuild Repository indices 
3 Set up server-side tracing >> 
4 Check integrity of job files 
5 Administer processes/locks >> 
6 Adjust job tunable properties 

DS.TRACE Menu 
Option Text on Screen 
1 Query trace status 
2 Turn tracing on 
3 Turn tracing off 
4 List trace records 
5 Delete all trace records 

DS.PLADMIN Menu 
Option Text on Screen 
1 List all processes 
2 List state of a process 
3 List state of all processes in a job 
4 List all locks 
5 List locks held by a process 
6 List locks held by all processes in a job 
7 Clear locks held by a process 
8 Clear locks held by all processes in a job 
9 Logout a process 
10 Logout all processes in a job 
11 Clear status file for a job 


DS.TOOLS Menu 
Option Command 
1 DSR_LICENSE REPORT 
2 DS.REINDEX ALL 
3 DS.TRACE 
4 DS.CHECKER JOBS 
5 DS.PLADMIN 
6 DS.TUNEPROPS 

DS.TRACE Menu 
Option Command 
1 TRACE 
2 TRACE ON 
3 TRACE OFF 
4 TRACE LIST 
5 TRACE CLEAR 

DS.PLADMIN Menu 
1 DS.PLADMIN.CMD LIST PIDS * 
2 DS.PLADMIN.CMD LIST PIDS 
3 DS.PLADMIN.CMD LIST PIDS 
4 DS.PLADMIN.CMD LIST LOCKS * 
5 DS.PLADMIN.CMD LIST LOCKS 
6 DS.PLADMIN.CMD LIST LOCKS 
7 DS.PLADMIN.CMD CLEAR LOCKS 
8 DS.PLADMIN.CMD CLEAR LOCKS 
9 DS.PLADMIN.CMD CLEAR PIDS 
10 DS.PLADMIN.CMD CLEAR PIDS 
11 DS.PLADMIN.CMD CLEAR STATUS 

Error APT_PM_CONDUCTOR_TIMEOUT

If you got this error:
main_program: Fatal Error: Service table transmission failed for <Node Machine> (<Node Machine>:Broken pipe.  This may indicate a network problem. Setting APT_PM_CONDUCTOR_TIMEOUT to a larger value (when unset, it defaults to 60) may alleviate this problem.

You can resolve the problem with increasing the value of APT_PM_CONDUCTOR_TIMEOUT with add it into User Defined Variable at Project Environment Variable.

The steps are:

1. Open DataStage Administrator Client
2. Choose your Project Name
3. Click Properties Button
4. Click Environment Button
5. Add APT_PM_CONDUCTOR_TIMEOUT into User Defined Variable
6. Set the value

How to restart DataStage ?

The order in which to stop all services is:

   1. Stop DataStage Engine
   2. Stop the ASB Agent
   3. Stop the WebSphere Application Server (WAS)


Here are the step-by-step instructions for each of the above.

   1. Stop DataStage Engine
          * Log into your UNIX machine as root
          * Make sure that no one is using DataStage.
          * Check if there are any processes left
            ps -ef | grep -i phantom
            ps -ef | grep dsapi
            ps -ef | grep dscs

            These commands should not return any results. If they return results, it means that there are still some processes running. You can wait for the users to stop their processes or kill the processes (using kill -9 PID).
          * Check if dsrpc is running

            netstat -a | grep dsrpc

            If dsrpc is running, then you should get a line with the status LISTEN. If you get more lines it means that there are still some connections and you need to wait. If you see that dsrpc or other connections are in status WAIT then you also need to wait until this it disappears (you can also reboot the machine).
          * Stop DataStage Services using (you have to run this from $DSHOME)

            . ./dsenv
            bin/uv -admin -stop
          * Then see if there is any memory segment left:

            ipcs -mop | grep ade

            For 64-bit Linux, use: ipcs -qms -a

            If you get a result, take note of the PID and remove it (you will need root access)

            ipcrm -m PID
          * Then, check the port again using

            netstat -a | grep dsrpc

            You should not get any result. If you get any results and the dsrpc is in WAIT state, then you need to wait until it disappears (you can also reboot the machine).

   2. Stop the ASB Agent (you need to be root user)
          * Go to <path to>/IBM/InformationServer/ASBNode/bin
          * Run ./NodeAgents.sh stop

            Type 'yes' if you receive the following message:
            rm: remove write-protected regular file `Agent.pid'?
          * Check the agent has stopped:

            ps -ef | grep -i agent
          * On Solaris it may be necessary to run this command if errors similar to this are returned when trying to start the agent.
            "com.ascential.acs.logging.agent.LoggingAgentSocketImpl.main(LoggingAgentSocketImpl.java:115) Caused by: java.net.BindException: Address already in use"

            /usr/ucb/ps -auxww | grep java

3. Stop the WebSphere Application Server (you need to be root user)

          o Go to <path to>/IBM/InformationServer/ASBServer/bin
          o Run ./MetadataServer.sh stop
          o Be sure the java processes go away
          o Now check there are no java processes left behind:

            > ps -ef | grep java

            remove them if any exists with: > kill PID (NO -9)

The order in which to start all services is:

   1. Start WebSphere Application Server
   2. Start ASB Agent
   3. Start DataStage Engine

How to reindex the repository ?

You need to reindex your repository if someday you found that some of files that you've import (backup) is missing when you try to export (restore) it. If that so :

• Open DataStage Administrator Client
• Click Command Button
• Type this command : DS.REINDEX ALL

After that the repository will be reindexes.

How to release lock on your datastage job?

Sometimes you can have condition when your job is locked eventhough all users have been disconnected from the session. There are few things that you can do when you have this condition:

• Open DataStage Administrator Client
• Choose your project
• Click Command Button and type:

1. LIST.READU <For listing all active locked session>
2. SET.FILE UV VOC UV.VOC 
3. COPY FROM UV.VOC TO VOC UNLOCK
4. UNLOCK INODE <INode Number you want to unlock> ALL
5. Or, UNLOCK USER <User Number you want to unlock>

• Repeat all step until the job is released.

Or you can release it with Delete all records from XMETALOCKINFO table