Hello everybody,
can anybody tell me what this error message mean?
" Error Calling Subroutine:*DataStage*DSR_SELECT (Action=3): check DataStage is setup correctly in project XXX
(The connection is broken (81002))
Is this something that popsup if we dont use datastage for sometime or something related to administrative issue....
Thanks in advance...
DS Repository Interface error
Moderators: chulett, rschirm, roy
Re: DS Repository Interface error
This can mean lots of things.
In order:
1) Try to just restart your DataStage client. It could just be one of your DataStage admins kicked you out e.g.
2) Try to bounce your DataStage server
3) Check for other things
Ogmios
In order:
1) Try to just restart your DataStage client. It could just be one of your DataStage admins kicked you out e.g.
2) Try to bounce your DataStage server
3) Check for other things
Ogmios
Re: DS Repository Interface error
You'd have to tell us... does it? Do you have a connection timeout specified for the server? Timeout is enabled by default, so unless someone has changed it you do. Check in Administrator, if you do then you will get disconnected and see error messages much like this after that period of inactivity.kab123 wrote:Is this something that pops up if we don't use datastage for sometime?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
<rant>
It would help to diagnose these errors generated by helper subroutines (such as DSR_RECORD, DSR_SELECT and so on) if the error message included the other input argument values.
You can get them in a server-side trace, so why not?
Then you could figure out (from DSINCLUDE) what Action 3 is supposed to do, and the other argument values could tell you on which object it was supposed to be acting. This could lead to much more accurate diagnosis and rapid remediation.
</rant>
It would help to diagnose these errors generated by helper subroutines (such as DSR_RECORD, DSR_SELECT and so on) if the error message included the other input argument values.
You can get them in a server-side trace, so why not?
Then you could figure out (from DSINCLUDE) what Action 3 is supposed to do, and the other argument values could tell you on which object it was supposed to be acting. This could lead to much more accurate diagnosis and rapid remediation.
</rant>
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.