|
View previous topic :: View next topic
|
| Author |
Message |
shashirbsk
New User
Joined: 18 Jan 2007
Posts: 7
Location: hyderabad
|
|
|
|
| Can anyone explain me the usage of GROUP and USER parameters in a JOB statement? |
|
| Back to top |
|
 |
Aaru
Senior Member
Joined: 03 Jul 2007
Posts: 1287
Location: Chennai, India
|
|
|
|
shash,
From the manuals
| Quote: |
Purpose: Code the USER parameter to identify to the system the person submitting the job. The userid is used by the Resource Access Control Facility (RACF), the system resources manager (SRM), and other system components.
If the installation contains the feature for propagation of the user and group identification, the USER and PASSWORD parameters are required, and the GROUP parameter is optional on JOB statements only for the following:
Batch jobs submitted through an input stream, such as a card reader, (1) if the job requires access to RACF-protected resources or (2) if the installation requires that all jobs have RACF identification.
Jobs submitted by one RACF-defined user for another user. In this case, the JOB statement must specify the other user's userid and may need a password. The group id is optional.
Jobs that execute at another network node that uses RACF protection.
Otherwise, the USER, PASSWORD, and GROUP parameters can be omitted from JOB statements. RACF uses the userid, password, and default group id of the submitting TSO/E user or job. |
|
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| shashirbsk wrote: |
| Can anyone explain me the usage of GROUP and USER parameters in a JOB statement? |
USER parameter is more handy when some sechduler is used, in this JOB card:
| Code: |
//JJJ030C JOB (@),XX.AAAA-DAILY-XX-RUN,
// USER=J088XX,REGION=0M,
// MSGCLASS=J,CLASS=J |
This tells that this JOB is meant for user J088XX (just another node at my shop).
There are some other usage of this, they are as follows
- Jobs submitted to execute at another network node that uses RACF security
- Jobs submitted by one TSO user on behalf of another TSO user. If this is done, the JOB statement must specify the second user's USER= and PASSWORD= values.
- Batch jobs submitted from a non-TSO address space that need to access RACF-protected resources.
When You submit a "test" job with USER not coded, default is Your RACF ID. |
|
| Back to top |
|
|
shashirbsk
New User
Joined: 18 Jan 2007
Posts: 7
Location: hyderabad
|
|
|
|
| Thanks Aaru and Anuj for your explanations. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
You are welcome..  .
If you have further queries, post them, some helping hand would be here..Happy Weekend..(for me it's starting today..  ) |
|
| Back to top |
|
|
|
|
