We're trying to get this setup on a system it hasn't been used before and need help with running into C1G0510E error. We have another system where this works ok and can't figure out what different is needed.
Add USS Element fails with the below errors:
C1G0510E USS OPN ERROR - RC=0000006F, REASON CODE=EF076015, RETURN VALUE=FFFFFFFF, PERMISSION IS DENIED
C1G0000I PATH /path/System/Type/
C1G0000I FILE /path/System/Type/EFP*
C1G0510E USS OPN ERROR - RC=0000006F, REASON CODE=EF076015, RETURN VALUE=FFFFFFFF, PERMISSION IS DENIED
All Supported Releases
When ENABLE_ALTID_USS_SECURITY ON:
- USS file is always created under ALTID, regardless of the interface
When ENABLE_ALTID_USS_SECURITY OFF:
- in batch, element is always created under ALTID
- in ISPF, element is always created under SUPERUSER, even if user/ALTID doesn't have authority to become superuser
- footprint file (EFP*) in USS base is always created with an ownership of the user who performed first add to that base directory
What happened at customer site:
- they have ENABLE_ALTID_USS_SECURITY enabled;
- they are experiencing an error in batch when trying to add an element to USS base
Some time ago, when the ALTID optional feature was disabled, the first element was added via ISPF and the fingerprint file was created with SUPERUSER ownership. Now, when a user adds an element to the base, ALTID doesn't have authority to edit an element that belongs to SUPERUSER and ADD action fails with an error.
Ask customer to run chown and chmod commands on footprint file and verify ADD action again:
chown <ALTID> /path/System/Type/EFP* <- replace <ALTID> with actual ID
chmod 755 /path/System/Type/EFP*