Non-RACF Restrictions

The following restrictions apply only to the execution of commands processed in the background when RACF® is not installed on your system.

The IBM-supplied installation exit rejects the CANCEL, RECEIVE, and OUTPUT commands because no user ID is available in the background.
You must specify operands on the STATUS command. The system issues an error message if none is supplied.
A PROFILE command with a PREFIX (user_id) operand is required if you want a user ID to be prefixed to all data-set-names, or if something other than a null value is required for the CLIST symbolic variable, &SYSPREF.
The CLIST symbolic variable &SYSUID has a null value.
When a data set containing a job to be submitted in the background does not contain a JOB statement, SUBMIT generates one. It attempts to construct the job name using the value on the USER operand. If there is no value with the USER operand, the system issues a warning message and uses the default job name SUBMIT JB.
When generating a JOB statement, SUBMIT does not insert a NOTIFY=user ID operand.

Note: In a system with RACF installed, there are fewer restrictions for users that are both RACF and TSO/E defined. When RACF is installed, TSO/E can establish profile attributes for a background job, provided the JOB statement contains a value for the USER operand. TSO/E accesses the UADS entry associated with the user identified on the USER operand on the JOB statement.

For more information about processing considerations for RACF and non-RACF systems, see the PROFILE command in z/OS TSO/E Command Reference.