DSXchange

Hello Everyone,

We are getting "Error calling subroutine " while opening the Director. There are multiple errors one after another:

Error calling subroutine: DSR_EXECJOB (Action=23); check DataStage is set up correctly in project DSTESTPROJECT
(The connection is broken (81002))

Error calling subroutine: *DataStage*DSR_SELECT (Action=3); check DataStage is set up correctly in project DSTESTPROJECT
(The connection is broken (81002))

Error calling subroutine: *DataStage*DSR_PROJECT (Action=7); check DataStage is set up correctly in project DSTESTPROJECT
(The connection is broken (81002))

Here are some observations:

- This is specific is one project. All other projects are fine
- Error is in Director only. Designer is working fine- I can open the jobs in designer etc.
- All users are getting this error in director.
- Disk space seems to be fine

This is what I have done so far:

1. Use "Reindex all" for rebuilding the indexes - used DS.TOOLS for this
2. clearing &PH& directory: Used CLEAR.FILE command


Any help will be deeply appreciated:
Can there be an issue with RT log files?- How can I check that?

Please share your thoughts.
Thanks in advance.

In one of the post I saw that

"project may need re-indexing (using DS.REINDEX ALL next time you can get exclusive access to the project)."

what does exclusive access means ?
-no clients should be open at all and connected to any projects?
- or no one should be connected to the project I need to rebuild indexes on? or
what are other requirements to get exclusive access?

Thanks

81002 might be as simple as your inactivity timeout triggering.

Thanks Ray!
Yeah from previous posts- I checked time out setting from General tab of Administrator main window. It is set to " Do Not Time Out"

Thanks,

Mine is to but I get the same issue now and then.
I look in Process explorer and I can see the designer or director processes its just that they loose the connection to the dsapi_server and slave process.

I usually just close the client and reconnect and its fine.
This usually happens when I leave them open all night. But its not consistant!!

I know thats not an answer, but I share your pain.
Maybe some day I will run that accross support when I am talking to them.

If I get an answer I will pass it on.

Any other suggestions or ideas will be greatly appreciated!

is "Global Session Properties" in web console ( Administration>Session Management) has some bearing on it also?

Our settings are:

Inactive Session Timeout: 900 seconds
Check Inactive Sessions Every:120 seconds
Maximum Sessions: 60
Current Sessions: 28

We do get the same issue as Gregg and as said closing and opening the client will solve this issue. And this is regardless of Designer or Director..

In our case- it is just occurring in Director. Designer is working fine- we can even run jobs from designer. Closing and then opening is not making any difference either.

Hi,
We are experiencing same issue except that the issue on our side is happening with DataStage designer, not director...

Can you tell us what you did? or did this issue ever get resolved for you?

Thank you,
Kiran

It's not the same issue, similar perhaps but not the same. Please start a new post with the gory details of your particular issue.

I just opened a new topic.

Thanks

just4geeks wrote:Any other suggestions or ideas will be greatly appreciated!

is "Global Session Properties" in web console ( Administration>Session Management) has some bearing on it also?

Our settings are:

Inactive Session Timeout: 900 seconds
Check Inactive Sessions Every:120 seconds
Maximum Sessions: 60
Current Sessions: 28

Yes it may be related!

Have some coffee Roy, you replied to a post from 2011.