How to check how many clients are connected to the project?

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Bilwakunj
Participant
Posts: 59
Joined: Fri Sep 10, 2004 7:00 am

How to check how many clients are connected to the project?

Post by Bilwakunj »

Hi,
Before exporting the job/project how to determine is anybody else is connected to it or not? Is it done through the UNIX command or datastage has that routine/Macro for it?

Thanks in advance!!
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

There's no exact way. "ps -ef |grep dsapi" will tell you of any clients connected on that server, there's no way to tell the project that they are in.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

You can try 'netstat -na | grep 31538'

It must not return any rows.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Actually, being connected will not prevent an export; it's only when they have objects open for editing that that object is skipped by the export process. It is sufficient, therefore, to check for locked design objects (though safer not to have any user connected).

You can determine both using the command

Code: Select all

$DSHOME/bin/list_readu
This will show you who's connected, the identification of their client machine, and whether they have any design objects open for editing. To see just the latter, use

Code: Select all

$DSHOME/bin/list_readu | grep RU | grep -v :
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

ray.wurlod wrote:Actually, being connected will not prevent an export; it's only when they have objects open for editing that that object is skipped by the export process. It is sufficient, therefore, to check for locked design objects (though safer not to have any user connected).

You can determine both using the command

Code: Select all

$DSHOME/bin/list_readu
This will show you who's connected, the identification of their client machine, and whether they have any design objects open for editing. To see just the latter, use

Code: Select all

$DSHOME/bin/list_readu | grep RU | grep -v :
And all of these commands will STILL NOT tell you which project. Since a job can be locked in project A, but you're exporting in project B, you will be unable to distinguish whether you need this lock release or not.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
T42
Participant
Posts: 499
Joined: Thu Nov 11, 2004 6:45 pm

Post by T42 »

Sainath.Srinivasan wrote:You can try 'netstat -na | grep 31538'

It must not return any rows.
That will not work with certain versions of DataStage. 'netstat -na |grep dsrpc' will work better. You only wish to have a single listener.

Ray and Ken also have great advices. Further steps are to go into uvsh, but this is an advanced option, and should not be trifled with without care (and ability to search the forums for detailed explainations.)
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The devno and inode columns in the list_readu report can be decoded from a map of such information gathered by regular monitoring with utilities such as ACCOUNT.FILE.STATS (that's the one that I use). This also contains the project (account) name if collected globally across all projects.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply