You have to have installed DataStage 6.0 as the dsadm user. There is a separate chapter in the installation guide on this.
The dsadm user is not the superuser, and does not have superuser privileges or effective user ID of 0. All the required adjustments are made to DataStage executables at installation time.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
We just did a couple installations of version 7.x on Solaris, the software was installed by the root user and afterwards the DataStage server could be stopped and started by the dsadm user. As Ray suggested you need to read the DataStage Upgrade Guide for the pre-installation steps for Solaris that outline setting up the dsadm user correctly so it can correctly administer your DataStage environment.
I wonder dsadm can stop and start DataStage v6.0 on Sun Solaris 8 platform
Is dsadm the supper user?
So dsadm is not the super user. If you install DataStage as root some binaries are 'setuid'ed and run under root permissions but dsadm on itself is pretty harmless for the rest.
The setuid thing happens even when installed by root.
You can also (in version 7.0 and later), install so that any other user ID "impersonates" the Administrator user. It's all in the manual. We've just installed 7.0 on AIX using user datastg as the Administrator.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod wrote:The setuid thing happens even when installed by root.
...
This is what I meant, when you install as root some binaries get setuid to root and as a result the DataStage subprocesses are able to run using the userid that logs on to DataStage (root authority is required to switch ids).
When you don't install as root I doubt the subprocesses will run under the id you logged on with, they will "only" run under the dsadm user id as the DataStage server process won't be able to switch user ids on the subprocesses.
I have not yet installed a DataStage without being root.
Can you check if your dsadm user id created properly. I mean it should have 'dstage' as the primary group. Also check if 'dsadm' has execute access on 'uv' script in $dshome/bin directory.
That means I have done the right thing because I am using root to install datastage.
Please tell me in detail how can I make dsadm to be able to stop and start DS. I am using Sun Solaris and I am not very good at Sun Solaris, please guide me step by step.
What do you mean by correctly setup dsadm?
I have done this
1.) create the dstg directory
2.) create user dsadm but not manage to assign dstg as home directory
3.) use root to install datastage
4.) manage to assign dstg directory as dsamd's home directory
Now dsadm cannot stop and start. It looks like the step is wrong. But is there a way for solve the problem instead of reinstall?
How to give dsadm the permission?
You need to contact your unix administrator:
Ask him the following:
1] Create user group 'dstage' and user id 'dsadm'.
2] make dstage as the primary group of dsadm
3] give read and write access to group 'dstage' for datastage directory in which you are installing dastage.
Now you can install with root.
There is nothing else you have to do so as 'dsadm' can get engine stop/start right..