If a USER profile ABC123 with an OWNER + DFTLGRP DEPT110 should be in your administration scope, CKGRACF and CKRCARLA look for a profile protecting
CKG.SCP.ID.ABC123.DEPT110.DEPT110
Three variable qualfiers.
If this profile is not found, CKGRACF and CKRCARLA look for the OWNER of DEPT110, and continue chasing the OWNER chain until they get to SYS1, in which case a profile is searched for resource CKG.SCP.G.owner1.owner2....DEPT110, where owner1 is the last group before SYS1.
If there is a USER in the OWNER chain, the chain stops and a profile is found for CKG.SCP.U.owner1.owner2....DEPT110, where owner1 is the USER ID.
Now, if you are going to execute commands on a GROUP, like a CONNECT command, CKGRACF and CKRCARLA do not have a DFLTGRP value to check, the first profile to check is CKG.SCP.ID.
group.
ownerTwo variable qualifiers. And CKG.SCP.G and CKG.SCP.U profiles work similar to the USER case.
CKGRACF has a DEBUG command that illustrates the way these SCP profiles are checked. Go to SE.T (Trace or Debug options), select the "Collect CKGRACF diagnostics" option. This adds the DEBUG command into the CKGRACF command parameters. Output is written to CKGPRINT.
------------------------------
Rob van Hoboken
------------------------------