Who is logged on DataStage
Moderators: chulett, rschirm, roy
Who is logged on DataStage
Hi All
We have a 10 user development license. When I try to login, I often get the message stating all 10 development licenses are already in use.
How do I find out which users are logged into DataStage i.e. is there some kind of log in the DataStage engine (Universe database) where I could simply run a select statement to get this information?
We have a 10 user development license. When I try to login, I often get the message stating all 10 development licenses are already in use.
How do I find out which users are logged into DataStage i.e. is there some kind of log in the DataStage engine (Universe database) where I could simply run a select statement to get this information?
ewart,
to add to what Martin said, go into the DEVELOPER and select some project and execute the "command" button, then the LISTU statement.
to add to what Martin said, go into the DEVELOPER and select some project and execute the "command" button, then the LISTU statement.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 614
- Joined: Fri Feb 06, 2004 3:59 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
If you execute LIST.READU instead you can get more information.
Each connected client has a type "RL" lock on an artificial record called !&DS.ADMIN_project&! and a type "RU" lock on a record whose name is made up of the Windows identifier of the client machine then the host name of that machine, followed by a colon and the process ID of its agent process (dsapi_server) on the server machine. The RU locks give you the ability to work out from where each client is connected.
This advice relates to version 7.x, as per the poster's specification. It may not work in earlier versions.
Each connected client has a type "RL" lock on an artificial record called !&DS.ADMIN_project&! and a type "RU" lock on a record whose name is made up of the Windows identifier of the client machine then the host name of that machine, followed by a colon and the process ID of its agent process (dsapi_server) on the server machine. The RU locks give you the ability to work out from where each client is connected.
This advice relates to version 7.x, as per the poster's specification. It may not work in earlier versions.
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.
Oops, sorry, I did mean the ADMINISTRATOR and no the DESIGNER. I should never mix cough medicine, Vodka and operating DataStagekollurianu wrote:Did u mean going to administrator and command button Arnd?
Thank you very much.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>