We modified SUBNOID=YES to SUBNOID=NO, and recycled CA7.
After some time, we noticed that a dummy job had R-NOUID issue:
JOBA REQ 0176 169/0505 169/0500 169/0510 *NOEX* 007 AUTO 001 R-NOUID
LQ,JOB=JOBA
LIST=STATUS JOB=JOBA DATE=23.169 PAGE 0001
JOB QUEUE CA-7 -DAY(DDD) AND TIME(HHMM)-- CPU SCH ENTRY MSTR JOB
NAME NAME JOB# DEADLINE SUB/START DUE-OUT SPEC/RUN ID MODE REQ STATUS
JOBA REQ 0176 169/0505 169/0500 169/0510 *NOEX* 007 AUTO 001 R-NOUID
------------------------- REQUIREMENTS STATUS -------------------------
_______ USERID UNAVAILABLE FOR JOB SUBMISSION
SLIF-00 REQUEST COMPLETED AT 05:04:20 ON 23.169
Release : 12.1
If you are setting up the CA 7 Init file and your environment require that every job has a USER= on the job card and you have NOEX Jobs, you will need to set your rules to reflect the following sample setup:
SECURITY,NAME=SASSSECI,
EXTERNAL=(LOGON,COMMAND,DATASET),
SUBUID=(OWNER,REQ,QJCL,CA7),SUBNOID=NO
The above sample has what is called a SUBUID Hierarchy. It is needed because of the SUBNOID=NO value. The SUBNOID value determines whether CA 7 will submit a job if there is no USER= located for the job when it enters the REQ Q. SUBNOID=YES indicates a job can submit without a user id. SUBNOID=NO indicated a job cannot submit without a userid. The SUBUID hierarchy allows a userid to be extracted from the OWNER of the JOB as defined on the DB.1 panel. The REQ allows the 'USERID' be extracted from the requester of the job via a DEMAND, RUN or LOAD. The QJCL allows the 'USERID' to be extracted from a authorized user when a QJCL Edit is performed. Last, the CA7 value allows CA 7 to extract an associated 'USERID' and submit the job if none of the previous candidates are applicable. CA7 should alway be coded last, as it will always have the ability to submit a job. If you do not code CA7 last within the hierarchy for your selection and none of the previous selections are made, the job will remain in the REQ Q with a R-NOUID in the STATUS column.