Using the SYSUID system symbol

As long as you observe the rules listed in "Rules for Coding Symbols in JCL," you can code the SYSUID system symbol anywhere in your JCL where you would code a user ID except on the keywords and statements listed in the topic Restrictions on coding SYSUID. The system replaces &SYSUID with the user ID under whose authority the job will run, which is normally one of the following:

The USER parameter from the JOB statement, if specified, or
The user ID from which the job was submitted.

Note: If userid propagation does not occur, (for example a security product is not active or the submitting userid is not allowed to propagate), SYSUID will be null. A security product is considered "not active" in OS/390® if it has been disabled. If RACF® is running in a fail soft mode, the security product is considered "active."

Note: If RACF is active and the job is running with a user ID not defined to RACF, the system provides substitute characters for &SYSUID and may fail the job because of this JCL error. The same results may occur if &SYSUID is not resolved to a valid user when RACF is not active.

You can, for example, use &SYSUID as a generic qualifier in a data set name specified in a transaction program profile that will be invoked by a transaction program. Code SYSUID on the DSNAME parameter as the high-level qualifier of the data set name:

   //DD1   DD  DSNAME=&SYSUID..PROFILE,DISP=(NEW,KEEP)

The system replaces the symbol with the userid of the transaction program invoker. If userid ROGERS invokes the transaction program, the system will create the data set name ROGERS.PROFILE.