DSXchange

Is there any way to see the jobs from Director as a DS Operator.

Not able to see the jobs (both server & parallel jobs) in DataStage EE 7.5.2 Director as a "DataStage Operator" (Role).

Does it use same TZ environment variable for both the DS 7.5 and DS 8.0.1. Where can I find these TZ Env variable.

We have both DS 7.5 and DS 8.0.1 on the same Unix(AIX) box. DS 7.5 Server time is in sync with OS time but DS 8.0.1 Server time is 5 Hours ahead of OS time.
Is there any clue on it.

Thanks

Are you able to connect to any other Database(s) using Oracle Enterprise Stage.

There could be many reasons. One of the reason could be low memory at the client machine(s). Preferably over 1GB RAM.

We intentionally brought-down the ASB Node Agent(s) (for test). Tried login/continue working with DS8.0.1 Designer/Director. We have successfully logged-in and continued working with DS8.0.1 Designer/Director save/compile/run jobs, with ASB Node Agent down. We are wondering that how is this possible.

That is true. Can we continue working on existing connection and do save/compile/run jobs. Can we make new logins/connections.

Can we login and continue working (save/compile/Run) with DataStage 8.0.1 Designer/Director, when ASBNode agent(s) is down. If yes or no why?

Regards
VS

If you are not able to see that lock from DS Director, go to DS Administrator, select the project, click on command button, issue command LIST.READU ALL, look for the user and inode for that particular locked process, issue command UNLOCK USER <user number> ALL , or UNLOCK <inode number> ALL. But, y...

If you are not able to see that lock from DS Director, go to DS Administrator, select the project, click on command button, issue command LIST.READU ALL, look for the user and inode for that particular locked process, issue command UNLOCK USER <user number> ALL , or UNLOCK <inode number> ALL. But, y...

Which user compiled the jobs? and which user is running jobs? See if you have any user group (unix) level permission issues.

Yes, XMETALOCKINFO table has all these hanging session info. We got a script from IBM support to clear these kind of locks from that XMETA table.

It is RESOLVED.

Thanks

DSEngine, Node Agent and Websphere server processes are running and have enough DS user licences. We are not getting any trace on it.

we are having a repeated problem: Some users(and admin) are not able to login to DataStage 8.0, but existing/established users/connections are working fine. If anybody tried to login to DS8.0, its throwing following error, DataStage Repository Interface Failed to connect to DataStage Server: <server...