Using HFSACL, the process is getting unknown error creating a symlink.

Document ID : KB000112731
Last Modified Date : 20/09/2018
Show Technical Document Details
Issue:
We have added additional ACLs to directories and files for a IHSA V9 process. The WAS administrator is trying to create the symlinks via the WAS console for the WAS plugins. The mkdir is working, but the symlinks are failing and we are getting the following error:
makeFSP FTB164 UNIT776 196 776 8 4 8 08/23/18 18.235 11.05.55 FTB1641 PYA2 No extended reason available for indicated return and reason Function: symlink User Type: Local Filename: /usr/local/ftb/ihsasrv9/wecell/plugins/com.ibm.icu.jar File Permissions: Owner: rwx Group: rwx Other: rwx Owning UID: 196 Owning GID: 70100 Volume : File Identifier: 00000001000000E50000000000000020 File Audit Options: User : Read Failure Write Failure Exec/Search Failure Auditor : Read None Write None Exec/Search None makeFSP FTB164 UNIT776 196 776 8 4 8 08/23/18 18.235 11.05.55 FTB1641 PYA2 No extended reason available for indicated return and reason Function: symlink User Type: Local Filename: /usr/local/ftb/ihsasrv9/wecell/plugins/com.ibm.icu.jar File Permissions: Owner: rwx Group: rwx Other: rwx Owning UID: 196 Owning GID: 70100 Volume : File Identifier: 00000001000000E50000000000000020 File Audit Options: User : Read Failure Write Failure Exec/Search Failure Auditor : Read None Write None Exec/Search None All directories and files contain: DEV:FTB021:/usr/local/ftb:>getfacl ihsasrv9 #file: ihsasrv9/ #owner: IHSASRV #group: IHSAGRP user::rwx group::rwx other::r-x user:FTB164:rwx user:IHSATST:rwx DEV:FTB021:/usr/local/ftb:>getfacl -d ihsasrv9 #file: ihsasrv9/ #owner: IHSASRV #group: IHSAGRP default:user:FTB164:rwx default:user:IHSATST:rwx DEV:FTB021:/usr/local/ftb:>getfacl -f ihsasrv9 #file: ihsasrv9/ #owner: IHSASRV #group: IHSAGRP fdefault:user:FTB164:rwx fdefault:user:IHSATST:rwx Need assistance with the issue. 
Environment:
z/os
Cause:
invalid default directory and file settings
Resolution:
The default directory and file settings caused the error with creation of symlink.