The original poster didn't mention why they would want to force root's
profile to be sourced.

If it is for some beneficial environment variable setup (for instance
variables for proper application operation),
then I think it would be easier to set up a script that defined these
environment variables before
running the applications that required them.

If the reason is for some rudimentary security control, or tracking
root user access,
then your method is very inadequate.
I would suggest looking at sudo. (Ideally with syslog logging off of
the machine in question, and with only
priv's granted that are really needed, etc)

If you insist that there is another reason that you would want to
force root's profile being sourced,
and decide to move su, I would highly recommend looking at the command
epkg for tracking your
changes. This will lock the lpp that contains su, so that you don't
inadvertantly upgrade and suddenly
lose your scripts and configuration.
(For more information, consult your friendly manual page, or:
http://publib.boulder.ibm.com/infoce...cmds2/epkg.htm
)

Hope this helps,
Casey