|
View previous topic :: View next topic
|
| Author |
Message |
nareshb6
New User
Joined: 03 Mar 2005
Posts: 5
|
|
|
|
| Is there any keword called USER in job card... |
|
| Back to top |
|
 |
mcmillan
Site Admin
Joined: 18 May 2003
Posts: 1210
Location: India
|
|
|
|
Dear Naresh,
Yes, we have a Parameter called USER in JobCard.
| Quote: |
Code the USER parameter to identify to the system the person submitting the job. The userid is used by 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
Do not specify this parameter for a started task; if USER is specified, the job will fail.
The USER parameter has no function in an APPC scheduling environment. If you code USER, the system will check it for syntax and ignore it. |
|
|
| Back to top |
|
|
ankyhunk
Moderator
.jpg)
Joined: 05 May 2005
Posts: 98
Location: Navi Mumbai, India
|
|
|
|
| The user & password parameters allow you to get the privileges of the specified user for the job. The owner of the job is the userid specified. |
|
| Back to top |
|
|
spanda
New User
Joined: 31 Aug 2005
Posts: 48
Location: U.K.
|
|
|
|
The USER parameter specifies your RACF user id. The user id is used
during the job's processing by RACF and JES to identify the user who
submitted the job for security checking purposes.
The USER, the PASSWORD, and, optionally, the GROUP parameters are
required on JOB statements in these circumstances:
1. Jobs submitted to execute at another network node that uses RACF
security
2. 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.
3. Batch jobs submitted from a non-TSO address space that need to
access RACF-protected resources
For cases other than those above, the USER=, PASSWORD=, and GROUP= parameters aren't required on JOB statements. RACF uses the userid, password, and default group id of the submitting TSO user or job.
Hope this helps,
Panda. |
|
| Back to top |
|
|
|
|
