Page 1 of 2

How to protect a project/projects

Posted: Mon Nov 10, 2008 3:24 pm
by vipson
I have about 50 projects on my DataStage environment.
I need to apply patch/fix and I need to make sure that no one is connected to DataStage. As usual, developers don't listen to the communication that I send out for downtime/maintenance.

I know that if I were to protect the project, they can not log in (correct me if I am wrong). I have not tried it yet...

Is there any way I can protect all the projects at command line (uv shell/dssh)?

I know that I can do that from Admin client=> properties...but I am looking for command line.

Posted: Mon Nov 10, 2008 3:43 pm
by chulett
That won't stop anyone from logging on, just keep them from doing much with the jobs while there. Do you actually need DataStage up for this "patch/fix"? With earlier versions, I think you'd just need to disable dsrpcd to stop client connections but in 8.x? No clue.

Hopefully someone knows.

Posted: Mon Nov 10, 2008 4:28 pm
by ray.wurlod
Stopping dsrpcd will do it even in version 8.x.

Posted: Mon Nov 10, 2008 5:18 pm
by vipson
I have been working with IBM on one of the parallel job issue and the fix that they have been providing has either failing on our server (later confirmed by IBM) or does not do what it is suppose to do or breaks something else...
This time I am getting running out of memory error for Java.
And, I asked IBM that is that because I have people logged in into the server?
And, the guy goes, you have to have server up and running and no should be using it..except dsadm/root who is performing patch/fix....

Anyway that is my story...

So basically, I will stop the server after taking few precautions...and than disable dsrpcd...than I start the server while in LISTEN mode..
Is that correct?

How do I stop dsrpcd? Pardon my ignorance...
And how do I start back it again?

Posted: Mon Nov 10, 2008 5:52 pm
by Novak
To stop dsrpcd - run 'services.msc' on the server machine, and in the list of the services displayed right click the one you want and choose stop.
You will do the same to run it again, except for choosing 'start' after right clicking.

Regards,

Novak

Posted: Mon Nov 10, 2008 5:56 pm
by chulett
That would only be true on a Windows server. For UNIX, I'm afraid I don't know how to stop it gracefully other than by shutting down DataStage. :(

Posted: Mon Nov 10, 2008 6:32 pm
by Novak
Apologies Vipson,

That IS true for Windows. I missed out on the fact that your DataStage is on Unix.

Regards,

Novak

Posted: Mon Nov 10, 2008 6:37 pm
by vipson
I have always wondered that why DataStage is so "behind" on UNIX...anyway...

I have root capabilities on UNIX (off course you would know that)...isn't there a way to stop and start dsrpcd?

Posted: Mon Nov 10, 2008 9:10 pm
by chulett
Behind? Whatever... I'm sure there's a way, just saying I've never needed to do so outside of the normal start/stop processing, so don't know about the stopping part. I'm sure others do. Starting is easy, however.

Posted: Mon Nov 10, 2008 10:23 pm
by ray.wurlod
What's hard about it?

Code: Select all

uv -admin -stop
Wait till there are no connected client processes before restarting.

Posted: Tue Nov 11, 2008 12:04 am
by vipson
I thought that command will stop/start ds engine...May be I need to have my tea....

Posted: Tue Nov 11, 2008 12:23 am
by chulett
Ray, we were talking about just stopping dsrpcd, not the whole shebang.

Posted: Tue Nov 11, 2008 7:19 am
by ray.wurlod
The OP needs to apply a patch/fix, which ordinarily requires DataStage to be shut down. This will include terminating dsrpcd. Otherwise examine the ds.rc script in the sample directory to learn the individual commands.

Posted: Tue Nov 11, 2008 10:39 am
by vipson
Ray,

Help me out with this investigation, if you can...

I found two scripts that will stop and start DS related services:
/etc/rc0.d/K99ds.rc
/etc/rc2.d/S99ds.rc


Basically it kills the dsrpcd daemon during the shutdown..
kill -15 $rlist > /dev/null 2>&1
****I could not understand "-15" option

To start it uses:
nohup $DSHOME/bin/dsrpcd > /dev/null 2>&1 &


What do you think of this:
Once I stop and restart my DS to prepare the patch installation; I kill the dsrpcd (means no one can connect now); finish up my patching and restart the DS...
Should this work?

Posted: Tue Nov 11, 2008 10:43 am
by chulett
OK, was wondering if all that it did was "kill" the process.

This should help with the different signals:

http://www.faqs.org/qa/qa-831.html

You won't be able to restart DataStage when you are done as it is already running. Simply restart dsrpcd with the nohup command you posted.