DSXchange

I know many discussions have been done regarding the issue Status code = -14 DSJE_TIMEOUT and we have read many of the comments.
We did increase the DSWaitResetTimeout and DSWaitResetStartup, restarted our server and DataStage.
But we still have this issue when we start dsjob -run project job
Whatever we try with newer or older DS projects.
However when using user dsadm, job is running fine.
When using user dsops, job times out.

Any help will be appreciated.
Thanks.

Welcome.

If you gone through all of the posts here and already done what you can then we can dispense with all of that and go straight to the heart of the matter. So, you're down to the fact that dsadm has no such issue while dsops causes the timeout? Can you go into detail about how you setup this user which I assume is one you created leveraging the Operator role.

I would imagine you'll end up needing to involve your official support provider to see if they have any insight into this issue... unless someone here comes along that has seen / solved a similar issue in the past.

This seems likely to come down to a permissions issue. You will need to work with your Information Server and DataStage Admins since resolving it will very likely depend on how user and group security is set up and administered for your installation.

Some thought starters:
Using internal registry or some other registry?
Credential mapping for dsops?
Suite roles for dsops?
DataStage roles for dsops?
Group membership for dsops?
Group membership for dsadm?

Mike

Also, is your setup a stand alone server or a cluster/grid environment?

Thanks Craig and Mike, will pass on those infos to the DS Admin and let him verify the permissions that have been granted to the dsops user. This user has already been able to start the dsjob -run.
Paul, I'm not sure about the setup.

Also I have found this IBM Technote that may be helpful.
http://www-01.ibm.com/support/docview.w ... wg21437510

Well worth checking out... let us know if that turns out to be your issue!

We found why the user dsops was not able to start the dsjob -run command.
When we started the dsjob command, we were connected on Unix with user dsops and password A.
That user dsops in DataStage admin had password B.
So the DS job was not starting ... and did not give any wrong password message.

We started successfully dsjob by passing credential parameters:
dsjob -server servername -user dsops -password B -run project job

Thanks everyone for your help.

Very... interesting. Glad you figured it out.

Still having a question ... regarding the above.

User dsops is defined in DataStage Admin as developer with password A
We are logged to Unix DS server with user dsops and password A

When issuing from the folder /opt/IBM/InformationServer/Server/DSEngine/bin/ the commands :
dsjob -server servername -user dsops -password A -run project job
job is running fine

dsjob -run project job
job timeout Status code = -14 DSJE_TIMEOUT

It seems the credentials are not passed properly.
Where can we investigate those ?

Thanks again for your help.

Enter the dsjob command without any options and review the syntax requirements. There are multiple options for authentication.

In your working example, you have authenticated directly with the engine tier.

In your timeout example, it does not appear that you have provided any of the acceptable authentication options.

Mike

Thanks Mike.

In our timeout example (dsjob -run project job), when we connect to server with user dsadm, it is working fine.
So the credentials are correct for user dsadm.

However for user dsops, we time out, so credentials are certainly wrong.
Where should we look to find those credentials ?

Cyrille

From what you posted, it would seem it times out when your credentials are missing - not that they are 'certainly wrong'. This is why Mike noted "In your timeout example, it does not appear that you have provided any of the acceptable authentication options".

Emphasis mine.

Thanks Craig for feedback.
I do understand that when we run as-is the command "dsjob -run project job" no authentication is provided.
However when we run that exact same command with user dsadm it works but it does not with user dsops.
It means when connecting to DS server with dsadm, authentification must be done in the background.

That's because dsadm is generally recognized as the administrator account for the most part.

When you start using other accounts, it will still try to use dsadm instead, but the authentication doesn't work. You need to explicitly define your authentication method. If you are concerned with showing your password in cleartext, use a password file instead:

http://www.ibm.com/support/knowledgecen ... ml?lang=en

-T.J.