Hi Lennie,
I am not sure exactly what you mean by UID=0. From a CA 7 perspective, I will assume you are talking about the UID value on the CPU JOB DEFINITION panel (DB.1).
If you are referring to this as the UID field, 0 mean the job is not protected and all users can access the job and demand/run the job if authorize to demand/run any job. This is regardless of how they logon to CA 7. If you change the UID value, it is possible users can be affect.
I recommend you open a support case and we can discuss/review before you make any changes.
Original Message:
Sent: Jan 21, 2025 03:23 PM
From: Lennie Currington
Subject: Using UID=0
I have someone who has found an old article stating that UID=0 is needed for any job being submitted by REXX, CLIST, or ROSCOE. This article that was found was from 2009. I figure this would have been under release 11 or even further back and would think that by release 12 this would not be the case. The person is in a panic as we are changing about 12,000 jobs that they have had under UID=0 and they want to make sure that using UID=0 is not needed for anything (even though they have no REXX or CLIST jobs kicking off other jobs)