There are three possible RACF / JESx issues when you use a third party (e.g., Control-M) to submit a job for you.
- Dataset access, which you have already discovered.
- The userid assigned to the submitted job.
- The jobname.
Dataset access. You may be able to do something about this.
- From the TSO READY prompt or ISPF option 6, issue
LISTDSD DATASET('your-dataset-name') GENERIC
Part of the output will be INFORMATION FOR DATASET xxxx (G). The xxxx is the actual RACF profile name used to control access to the dataset. If RACF allows you to list the profile, it may allow you to update the profile. You have two ways to allow Control-M to read the datasets controlled by the profile.
- "Universal" access, to allow anyone (including Control-M) to read the datasets. Use this command.
ALTDSD DATASET('xxxx') UACC(READ)
- Allow Control-M to read the datasets. Use this command.
ALTDSD DATASET('xxxx') ACCESS(READ) ID(the Control-M userid)
The userid assigned to the job. Normally, when you submit a job, it runs under your userid. If you use Control-M to submit a job it will run under Control-M's userid. If you want the job to run under your userid, you have two options.
- Specify your userid and password in the JOB statement.
This is not a Good Idea because you're exposing your password to anyone that can read your datasets, and whenever you change your password you will have to update the JOB statement
- Specify just your userid in the JOB statement.
If you are going to do this, your RACF support will have to update RACF to allow Control-M to submit the job. This may have already been done, but you should check with your RACF support.
The jobname. If you are going to run the job under your userid it probably is not a problem. If you are going to run the job under Control-M's userid it may be a problem, and you will have to discuss this with your RACF support.