We end the HTTP sever before nightly backups. Among the many jobs started when HTTP is re-started are jobs QZSOSIGN and QZDASOINIT for user QSECOFR. I have some idea what these jobs do. My question is, what initiates these jobs, or at least the sign on job? I don't like the idea of jobs running with the QSECOFR profile unless absolutely necessary.
Announcement
Collapse
No announcement yet.
Jobs starting with userid QSECOFR
Collapse
X
-
These are prestart jobs. You can check the configuration in the QUSRWRK subsystem description. The normal user profile to use is QUSER, but the jobs should swap to the connecting user profile when executing useful work. Since they are using QSECOFR now, it is likely that you will encounter authority errors when running under QUSER, so need to find out what authorities are needed before doing the change, or if you can't, you would have to switch and then grant based on any errors discovered. Alternatively, you can use another ID with *ALLOBJ privilege.
Comment