Fill in the job card information, according to your installation
requirements. For each job, the dialog generates a jobname and
the "JOB" keyword to match the member name of the PDS, but you specify the
rest. Note: If you need to run these jobs on a particular system in the sysplex
(for example, JES2 MAS or JES3 complex), you should specify the necessary
Scheduling Environment (SCHENV), JES2 JOBPARM, or JES3 //*MAIN statement at
this time.
Example of a job card entry://jobname JOB 1234,USER1,NOTIFY=????,MSGCLASS=O,REGION=0M
//* USER=SYSADM1,PASSWORD=SYSADM1
/*JOBPARM SYSAFF=SYSB
Note: This example is useful for jobs that require
a user ID other than that of the logged-on TSO user. (This is typically a
user ID with UID=0.) In that case, you can just put a comma at the end of
the first line, put in the correct user ID on the second line, then uncomment
that second line.
You might want to use RACF SUBMIT authority to avoid
having to keep passwords in your configuration data sets.