DSXchange

If you can't even get your test.sh script to run successfully, most likely the installation of the grid_enabled components is not configured correctly.

How many jobs in your job sequence? In each job in the job sequence, you must set the $APT_GRID_ENABLE to NO. Did you specify the Compute Nodes and Partitions parameters in your Execute Command Activity stage? Then your downstream job activity stages using the expressing: Field(stagename.$CommandOut...

What resource management software are you using? PBS Pro, IBM LoadLeveler, or SUN Grid Engine? Basically the main use of any workload management software is to do the queuing, scheduling, and monitoring the system resources and enforcing the usage policy. I love to use the PBS Pro; especially its Jo...

What you should do now is
lsof -P | grep 31531.

By default, 31531 is the port number used by the ASB Node agent. So, you need to start your ASB Node agent.

Do a search on "catalog tcpip", you will find the detailed steps in my post regarding how to connect to AS/400.

What you need to do is to create users and assign the roles accordingly. Don't understand why you even use "root" to access the DS?

The performance may be less because you don't know what the performance impact will be by the workload of other instances on the same hardware node.

Good thing about grid is that jobs don't run on the head node. So no big deal for using virtual server or physical server for the head node.

The problem is that fin_wait_2 has already occurred and stuck on the server side before you even realize there is a problem. You have to clear up this problem first manually. Of course IF you can get "ALL" the client sessions closed/killed prior to shutting down the DataStage engine, then ...

Still that wouldn't solve your fin_wait_2 problem.

You issue a
1. lsof -P
2. find the pid of that fin_waite2
3. kill that pid
4. restart the DS.

In your case, stay with the Windows. Let me ask you a simple question, would you promote an application into production knowing it has no support?

What you can do is
1.) lsof -P | grep 31533
2.) Find pid
3.) Kill pid
4.) Restart Ds

I have always built NAS-based configuration grid environment because it's much lower cost and simpler to implement multiple head nodes and HA. Make sure compute nodes have multiple NIC cards for public and private network connections. And the host name of the nodes is translated correctly in the pri...

Another way to do it is to set up JDBC on the WebSphere App. Server side. Just go to App. Server Admin Console-->Resources-->JDBC providers. You can even implement advanced function such as JDBC connection pool data source.