Startup error on node3 connecting with conductor

[sam paul]

Seems to be Unix server side connection issue. Check the contents of Node3 of your config file and reach out to Unix Admin with the 'fastname' and error message, they should be able to resolve.
If no luck, you may need to provide a different server as your Node3.

[joycerecacho]

Hi Sam!!!

All nodes are located on the same server, fastname is the same for all nodes.
We also followed the recommendations from the technote
http://www-01.ibm.com/support/docview.w ... wg21434065
But the problem is still happening.

Any other tip?

Thanks for your help!!!

Best Regards,
Joyce

[sam paul]

Oh, Unix/datastage admin who actually installed datastage need to have a look I think.

Couple of questions:
1)Is the issue occurring only with 'node3' always. If yes, try analyzing what's unique with the node3 content.
2)Does it occur with every job, every time. Has any job run successfully ever in this configuration.
3) What happens if you just rename 'node3' to some other name? Datastage some times behave weird too!
4) How many nodes your config file has? If you just remove 'node3' from your config file, what is the impact? (anyways, your nodes are logical since all nodes have same fastname)


You can do these basic analysis and reach out to admin team. If no luck, you may need to remove the node3 and raise a PMR with IBM.