Authorizing SYSOUT

You can control the processing of SYSOUT at your installation based on the userid, groupid, or security label associated with the inbound SYSOUT.

If when running in RACF® warm mode, you receive message $HASP186 indicating an access violation [to devices, external writers, or SYSOUT Application Programming Interface (SAPI) requests], and you require further diagnostic information, set DEBUG SECURITY=YES and see z/OS JES2 Diagnosis.

To authorize or restrict SYSOUT entering your system from another node, ask your security administrator to define a profile that identifies the criteria upon which SYSOUT is accepted. Provide your security administrator with the following information:

The node name(s) from which you expect SYSOUT.
The userid(s), groupid(s), and security labels from which you expect SYSOUT.
The universal access value, which determines how RACF assigns an owner to the SYSOUT. RACF can assign ownership based on either the userid and node that created the SYSOUT or the userid and node that submitted the job that created the SYSOUT. Table 1 shows the universal access values you can assign and defines the validation that RACF performs.