|
View previous topic :: View next topic
|
| Author |
Message |
Prasanthhere
Active User
Joined: 03 Aug 2005
Posts: 306
|
|
|
|
When i am using the USER paramater in the JCL i am getting a SEC error directly .Is there any way to resolve the SEC error .If So please share your views on this?
 |
|
| Back to top |
|
 |
gskulkarni
New User
Joined: 01 Mar 2006
Posts: 70
|
|
|
|
| details please. u can give us your code and return message that u are getting. possibility of getting quicker response that way. |
|
| Back to top |
|
|
Prasanthhere
Active User
Joined: 03 Aug 2005
Posts: 306
|
|
|
|
The Jcl is like this its basically for transfering a file to another server
//jobname job,, class=A,
// msgclass=x,
// User=User-id
When i am running in the first step we are getting a SEC error what might be the possible reason for that????? |
|
| Back to top |
|
|
Bharanidharan
New User
Joined: 20 Jun 2005
Posts: 86
Location: Chennai, India
|
|
|
|
Are you trying to submit with user-ID from another address space? May be RACF prevents you from submitting with that user ID unless you provide it the TSO password (PASSWORD= option).
Here is what my manual says:
| Code: |
The USER parameter specified 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:
o Jobs submitted to execute at another network node that uses RACF
security
o 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.
o 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.
|
|
|
| Back to top |
|
|
|
|
