For SDSF operation, IBM SDSF Operation and Customization Guide says that users need access to JESSPOOL resource locnode.+MASTER+.SYSLOG.SYSTEM.sysname.
But, with CA Top Secret acids, they need access to locnode.*BYPASS*.SYSLOG.SYSTEM.sysname.
The second qualifier in a JESSPOOL resource is the userid that owns the SYSOUT data being protected. With CA Top Secret, it is normally an acid name.
CA Top Secret usually does not allow ACEEs to be created for undefined users.
+MASTER+ is undefined in RACF, but RACF does allow ACEEs to be created for undefined users.
CA Top Secret makes a specific exception for userids starting with a '+' in a handful of FACILITYs, but CA Top Secret treats these as bypass users and uses a userid of *BYPASS* in the ACEE that is created.
When a JESSPOOL resource name is constructed, it uses the userid from the ACEE. The *BYPASS* ACEE will result in a JESSPOOL resource owned by *BYPASS*.
You can use *BYPASS* in the PERMIT command, but CA Top Secret will interpret the '*'s as masking characters. For that reason, use +BYPASS+ in the PERMIT.
It's still a masking character, but there are fewer resource names that will match.
Changing the way CA Top Secret creates an ACEE in a situation where it is creating a bypass user to make the JESSPOOL resource name match like RACF
would require a major design change..
It is recommended to adjust the PERMIT command to the CA Top Secret form.