Error : DSR_ExecJob (Action=5) when running a job

I got how to resolve this issue from IBM Support

Problem(Abstract)

In DataStage Director, the following errors occur when try to view folders in a project:

Error calling subroutine: DSR_EXECJOB (Action=5); check DataStage is set up correctly in project <project name> (The connection is broken (81002))

Error calling subroutine: *DataStage*DSR_SELECT (Action=3); check DataStage is set up correctly in project <project name> (The connection is broken (81002))

Cause

The errors were received because the Logging Agent was not running.

Diagnosing the problem

1. Check permission's on the project. Verify the user has RWX permission's on the files in the project.
2. Verify the Agents, Logging Agent and ASB Agent, are running:
   • On Unix/Linux execute the following:
     
     ps -ef | grep java | grep Agent
     
     If the Agents are not running they need to be started. When the Agents are running you would see entries similar to the following:
     
     $ ps -ef | grep java | grep Agent
     
     root 295106 1 0 Feb 03 - 9:09 ./../apps/jre/bin/java -Djava.security.auth.login.config=./../conf/auth.conf -Dcom.ibm.CORBA.ConfigURL=file:./../conf/sas.client.props -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Djava.util.logging.configureByServer=true -classpath ./../conf:./../lib/java/ACS_client.jar:./../lib/java/ACS_common.jar:./../lib/java/ASB_utils.jar:./../lib/java/ASB_util_client.jar:./../lib/java/WASClient.jar com.ascential.acs.logging.agent.LoggingAgentSocketImpl
     
     root 413844 1 0 Feb 03 - 76:25 /opt/IBM/InformationServer/ASBNode/bin/RunAgent -Xbootclasspath/a:conf -Djava.ext.dirs=apps/jre/lib/ext:lib/java -Djava.class.path=conf -Djava.security.auth.login.config=/opt/IBM/InformationServer/ASBNode/conf/auth.conf -Dcom.ibm.CORBA.ConfigURL=file:/opt/IBM/InformationServer/ASBNode/conf/sas.client.props -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Djava.util.logging.configureByServer=true -class com/ascential/asb/agent/impl/AgentImpl
     
   • On Windows go to Control Panel > Administrative Tools > Services and verify the ASB Agent and Logging Agent services are started.

Resolving the problem

To start the Agents:

• On Unix/Linux run the following command as root to start the ASB Agent and the Logging Agent.
  
  /opt/IBM/InformationServer/ASBNode/bin/NodeAgents.sh start
  
  The path shown in this command assumes that the product is installed in the default location. Your path will vary if you installed IBM Information Server in a different location. Then verify the Agents are now running (see step 3 above). If the Agents did not start successfully you can check the directory ../u2/IS810/IBM/InformationServer/ASBNode for the following files which may have additional information:
  
  asbagent_startup.err
  asbagent_startup.out
  logging-agent.err
  logging-agent.out
• On Windows go to Control Panel > Administrative Tools > Services and start the ASB Agent and Logging Agent.

How to solve Error:No conductor nodes found in export node pool

If you find this error when you want to write to a sequential stage, it usually happens when conductor node has different pool with other (process) nodes or APT_PM_CONDUCTOR_NODENAME may has been set manually.

To solve this problem, you may try to add machine_name before the file path. For example:
<Machine_Name>:<Filename Path>
eq: ETL_Machine_1:/my_etl_source/output/my_dest_filename.txt

What is SIGINT error on DataStage?

Error found: 
main_program: ORCHESTRATE step execution terminating due to SIGINT 


SIGNIT is actually an UNIX signal (Signal Interrupt) which is encountered when u perform and non -permissible operation . Please look the warnings generated before the fatal error. If not it may be because memory issues.  


it can be caused by permission issue, some things need to be checked when you found this kind of error:

• Mostly because of permission issues
• If it followed with different error, e.q SIGSEV then you have to watch this error too

source: ittoolbox datastage forum

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