Please forgive me, but I am not a Unix expert. I'm supporting SAP r/3 and we are trying to run an external command from SAP to read a file at the unix level. When we perform the more command on the following two files, we are succesful in reading the bws file, but unsucessful in reading the bws1 file.

The user running the more command is sidadm. sidadm is defined in both the sapdata and siddata group. Any idea why we cannot read the second file?

-rw-r----- 1 txfer sapdata 9 Apr 23 20:16 bws
-rw-r----- 1 txfer siddata 9 Apr 23 20:21 bws1

If we change the owner of bws1 to sidadm, we can read the file. If we change the group to sapdata, we can read the file. Is it possible for a group to have 'corrupt' data in it?

We don't have a lot of AIX members around I guess. But I'll take a shot in the dark based on general unix knowledge.

My best guess is that you're wrong in saying that user is a member of both groups. Try running the "groups" command (if AIX has one). It should display your group memberships.

Thank you for responding. I checked both groups and the user id defined in both. The only difference I notice in the groups is that the Administrator List is defined as ROOT in the group that is NOT working, and blank in the group that is working. Do you know if this has any relevance?

I don't know what an administrator list is, so I can't comment on that.

What technique did you use to "check both groups"? Did you try the "groups" command? What happened when you ran it?

When I run the groups command on both groups I get the following message:
The specified user is not known.
Check the /etc/passwd file for all known users.

I used SMIT to view the groups. Thanks.

You don't use "groups" like that.

Sign on as the user in question.

Type "groups".

What do you see?

I know it may be different in AIX, but in Solaris you dont need to sign on as the user in question. You can just type groups username.