The RecursiveMnt option for Mount resource, creates directories with 700 file perms (umask 077) even though umask is 022.

Mount resource configuration:

Mount MNT_est-ax100-d_mqdata01 (
		Critical = 0
		MountPoint = "/.stateless/tmpfs/data/VCS/t/mqdata01"
		BlockDevice = "nfsserver:/vol/nfsv4_vol01/mqdata01"
		FSType = nfs4
		MountOpt = "sec=sys"
		CreateMntPt = 2
		MntPtPermission = 755
		MntPtOwner = root
		RecursiveMnt = 1
		)

The following message is seen in engine_A.log:

 Mount:MNT_t_mqlog01:online:MountPoint </.stateless/tmpfs/data/VCS/t/mqlog01> successfully created
2011/10/21 13:09:15 VCS WARNING V-16-10031-5558 (test01) Mount:MNT_t_mqlog01:online:MountPoint </.stateless/tmpfs/data/VCS/t/mqlog01> created with default permission masks 077. It may not be accessible to all users

The actual mount point may appear to have the expected permissions as it reflects the permissions of the mounted file system, but it and its parent directories are created with umask 077 whereas root's default umask is 022 as per .profile.

[]# find -exec ls -ld {} \;|grep VCS
drwx------ 3 root root 60 Oct 21 13:09 ./VCS
drwx------ 4 root root 80 Oct 21 13:09 ./VCS/t
drwxr-xr-x 2 mqm mqm 4096 Oct 21 11:58 ./VCS/t/mqdata01
-rw-rw-r-- 1 mqm mqm 0 Oct 20 16:42 ./VCS/t/mqdata01/file
-rw-rw-r-- 1 mqm mqm 0 Oct 21 11:58 ./VCS/t/mqdata01/file2
drwxr-xr-x 2 mqm mqm 4096 Oct 20 16:00 ./VCS/t/mqlog01

/etc/profile:
if [ "`id -gn`" = "`id -un`" -a `id -u` -gt 99 ]; then
        umask 002
else
        umask 022
fi

Defining the umask to be 022 in the vcsenv file does not change this behavior.