|
View previous topic :: View next topic
|
| Author |
Message |
NathanReese
New User
Joined: 18 Sep 2024
Posts: 3
Location: United States
|
|
|
|
We are having difficulty trying enable access for a new userID (Yxxxxxx) that can submit job via FTP by using the SITE FILETYPE=JES NOJESGETBYDSN command.
The user can submit the job however when we examine the JCL SDSF we see the system modify the JCL to include USER=YP00 at the end of the job card. (the user should remain Yxxxxxx).
If a job is submitted via TSO – it works fine. So only appears limited jobs submitted via FTP.
Other users (Wxxxxxx) are able to successfully submit jobs via FTP without the USER being modified, so its limited to this new userID.
Do you know have some ideas how we could fix our Yxxxxxx userID? |
|
| Back to top |
|
 |
NathanReese
New User
Joined: 18 Sep 2024
Posts: 3
Location: United States
|
|
|
|
We did some additional troubleshooting and discovered that that the UserID set is always the first 2 characters of the jobname in from the job card.
Example: submitted via FTP by user Yxxxxxx
| Code: |
| //ABC12345 JOB 10010... |
the user would be set to:
| Code: |
| //ABC12345 JOB 10010...USER=AB00 |
From every other userID when a job is submitted the Job Name is updated, and the User remains the same as user that login via FTP to submit the job
Example: job submitted via FTP by user Wxxxxxxx
| Code: |
| //ABC12345 JOB 10010... |
Job card becomes in SDSF:
| Code: |
| //Wxxxxxxx JOB 10010... |
The User isn't explicit added to the JCL but shows up in user's job queue. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2586
Location: Silicon Valley
|
|
|
|
How are the TSO profiles different between the working userid and the failing userid?
Does the job card already have USER= parameter and a second one is added or is the value changed. What happens if you explicitly provide it?
Where are you FTPing from? Try from TSO vs from OMVS vs from Windows.
Why does this userid have a different naming convention?
Are there any IEFUJV exits in use? This exit is capable of modifying the job card.
Are there any JES2 exits 2, 3, or 4 implemented? One of these exits is capable of modifying the job card.
Do you have an exit for the TSO SUBMIT command? |
|
| Back to top |
|
|
NathanReese
New User
Joined: 18 Sep 2024
Posts: 3
Location: United States
|
|
|
|
Thank Pedro for the reply.
If I explicitly add the USER= parm the system will another USER= parm at the end and the job will fail with:
| Code: |
IEFC009I KEYWORD USER IS MUTUALLY EXCLUSIVE WITH KEYWORD USER ON THE
HASP110 user identity for the job already set |
FTP is being done from Windows
W - userID is designed for human operator
Y - userID is designed for automated process
Thanks for the info about the JES/IEFUJV exits - that sounds very promising!
I'll try to get our support/security group to look them as appears I don't have access to browse the current setup. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2586
Location: Silicon Valley
|
|
|
|
re: Y - userID is designed for automated process
I think this is the beginning of the robot uprising. |
|
| Back to top |
|
|
|
|
