DSXchange

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

Talk to your SysAdmins about having them add the 'execute' permissions to dsjob your user seems to be missing. Are you sure it's just a permissions problem?

Compare dsjob's file permissions and ownerships as well as users and their groups across both servers.

Does the ID you are credentially mapped belong to the "dstage" security group? (if you stayed with recommended defaults)


Can you paste the error message you are seeing?

@Eric,

I can not compare the credentials across both the servers since this user is not the admin user to check all the details.

@PaulVL

Yes. The user id given in the deployement server belongs to dstage group. But I am helpless.

Please help me.

Please clarify for us exactly what your issue is, as it is a little too nebulous right now. Are you seeing an error? What happens when you try to execute dsjob?

Hi,

I am seeing the error message 'dsjob command not found' when i put DSLogWarn message in my routine.

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.

yes It worked... :D Thanks a ton chulett!!!

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.

It is a solution to the issue.