My guess is the way you did the chmod......?
the chmod command.
suid = 4
sgid = 2
link = 1
To add the suid permissions to the preceding example, the command is:
chmod 4764 <file_name>
or chmod 2764 <filename> for the group ID?
to remove
if the sgid bit is set on a directory, the symbolic mode must be used to unset it:
chmod g-s <file_name> or chmod g-S <file_name>
-------------------------------
s Not used in the owner position. For the group
position, this becomes the group inheritance bit (SGID).
Any files created in this directory have the same group
as the directory entry. In AIX, when a new filesystem is
created, this bit is set by default. This also means the
search (x) bit is set for the group.
S Same as the lowercase s but means the search
(x) permission is not set for the group.
SETUID Behavior in AIX
A fix for a potential security risk dealing with the use of the SETUID and SETGID
permission bits on shell scripts was included in AIX 3.1.7 (which corresponds
to update level 2007). Prior to 3.1.7, when a shell script was
executed whose permissions included the SETUID bit (set user-id), the shell
script ran with the permissions of the shell script's owner. Similarly, if the
SETGID bit (set group-id) was set, the shell script ran with the permissions of
the shell script's group. Beginning with AIX 3.1.7, the SETUID and SETGID
permission bits are no longer supported for shell scripts. This change
does NOT affect compiled programs.