changing the primary group of a DataStage Server on UNIX

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
goffinw
Participant
Posts: 27
Joined: Thu Nov 18, 2004 6:50 am
Location: Belgium

changing the primary group of a DataStage Server on UNIX

Post by goffinw »

Would it be possible to change the primary group of a datastage server the following way:
  • - Stop the DataStage server.
    - As superuser, change the group (chgrp) id of all directories and files which having the old groupId to then new groupId.
    - As superuser, change the primary group of the dsadm to the new groupId
    - Restart the DataStage server.
Thanks in advance,
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

Yes. Some binaries are owned by root. So do not chown on these. You will have problems.
Mamu Kim
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Changing groups should be OK. However, most of the executables in the DataStage bin directory must be owned by root and have the setuid bit set (mainly because they need to access shared memory segments owned by other processes). So steer well clear of any chmod or chown command that might affect the bin directory's contents.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

I absolutely agree with Ray.
Mamu Kim
goffinw
Participant
Posts: 27
Joined: Thu Nov 18, 2004 6:50 am
Location: Belgium

Post by goffinw »

Thanks to all replyers.

We have executed the procedure and everything indeed seems to continue to work correctly.
We found the following extra difficulties:
1) As we are operating in a mixed non-ldap - ldap environment. Changing groups in one environment had an impact on other systems.
2) Files created during ETL had the group name of the old dsadm primary group. In order to tidy up the system, we also changed the groupid of thes files.
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

That is probably wise. LDAP complicates everything because you can be out of sync on your servers. Local users override LDAP. You need to use LDAP on all servers.
Mamu Kim
Post Reply