How to protect a project/projects
Moderators: chulett, rschirm, roy
How to protect a project/projects
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.
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.
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.
Hopefully someone knows.
-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:
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?
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?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What's hard about it?
Wait till there are no connected client processes before restarting.
Code: Select all
uv -admin -stop
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
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?
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?
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.
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.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers