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
Connection Error
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
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.
In short, login to DS Server using your user-id and try to execute the same command from command prompt.
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
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!
Thanks!
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You could always use executed through ExecDOS or DSExecute.
Code: Select all
AT \\computername hh:mm "command"
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Problem solved
Ascential support informed me that I needed to use the "start" command prior to the "rcmd" command. Worked flawlessly. :D