dsjob command not executing in my deployment environment
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
dsjob command not executing in my deployment environment
Hi All,
I have usedd dsjob command to trigger the jobs in Server routines. Everything is working fine in my development environment. When I moved all the jobs into deployment environment there is no access to user to execute the dsjob command. What permissions to be given to the user to access the dsjob command and how to apply the required permissions?
Thanks in advance
I have usedd dsjob command to trigger the jobs in Server routines. Everything is working fine in my development environment. When I moved all the jobs into deployment environment there is no access to user to execute the dsjob command. What permissions to be given to the user to access the dsjob command and how to apply the required permissions?
Thanks in advance
Regards,
Sai Krishna
Sai Krishna
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
You should have led with that, this has nothing to do with "access" in the sense we were all thinking you meant. This just means that your $DSHOME/bin directory (where the command lives) is not in your PATH statement. So, either update your PATH in the dsenv file to include that directory or fully path the executable in your routine.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
Hi All,
I have added the below code snippets in my routine code before the dsjob call:
cmd$DSENV = "cd '":p_DSHOME_DIR:"'":char(10) ;
cmd$DSENV := ". ./dsenv":char(10) ;
Then to the above statements the actual dsjob command will be appended as below:
outputJob$Trigger = cmd$DSENV
outputJob$Trigger := "dsjob --all the params required for dsjob--"
This is the workaround for the issue.
I have added the below code snippets in my routine code before the dsjob call:
cmd$DSENV = "cd '":p_DSHOME_DIR:"'":char(10) ;
cmd$DSENV := ". ./dsenv":char(10) ;
Then to the above statements the actual dsjob command will be appended as below:
outputJob$Trigger = cmd$DSENV
outputJob$Trigger := "dsjob --all the params required for dsjob--"
This is the workaround for the issue.
Regards,
Sai Krishna
Sai Krishna