DSXchange

I'm trying to use DataStage to fire off a separate vendor's ETL process. I've generated a batch file that successfully fires off the job successfully. However, when I use the "execute command" stage in DS to fire off the batch file I get the following message:

Epiphany_Launch_Test..JobControl (@Execute_Epiphany_Job): Executed: \\bgedwapp02\e$\executeepiphany
Reply=0
Output from command ====>
Error - Failed to connect to <\\bgepiphany>, Error = 5

The DS service account has rights to the target server. Is this a port issue?

Any ideas would be helpful.

Thanks,

Bill

The error message says that your DataStage SERVER machine is unable to connect to the mentioned windows path of \\bgedwapp02. Please check whether the user you use to connect to DataStage server has the network connection to that machine and drive.

In short, login to DS Server using your user-id and try to execute the same command from command prompt.

Please note that the required connection is to be setup on your DataStage server machine and provide enough authorisation to execute the script.

It's actually tring to connect to \\bgepiphany. \\bgedwapp02 is the server that DS is running on. I've logged into that server and fired off the batch file using our service account and it runs fine. There's always a possibility that I'm missing something and a different account is being used. I will research and reply.

Thanks!

You could always use executed through ExecDOS or DSExecute.

If the remote computer is your DataStage Server, you may be better-off removing that from your execution call line.

In other words, you can execute saying 'E:\ExecuteEpiphany' (with any parameters if necessary)

So I figured out the security issue but I'm still getting an error:

Epiphany_Launch_Test..JobControl (@Execute_Epiphany_Job): Executed: \\bgedwapp02\e$\executeepiphany.bat
Reply=1
Output from command ====>
Executing on \\bgepiphany: epiphanyruncmd

Error:8 - Internal error = 6

Thoughts?

Ascential support informed me that I needed to use the "start" command prior to the "rcmd" command. Worked flawlessly. :D