dick scherrer wrote:Why can each user not have one job name and upload run specifics (including which datasets and jcl) when they want to submit a job.
Each user would have a single "incoming control" dataset and the system schedule would be set up to submit when this dataset is created.
If you have 1000 users this would still be a lot of one-time setup.
There aren't rules that put restrictions to jobs names and datasets names so I cannot create a static and pre configured environment. And it is difficult to change users habits
dick scherrer wrote:The last several clients I've supported allow users to submit their own jobs. . . fwiw.
For internal policy users cannot submit their jobs unless their jobs are not submitted by someone authorized to sumbit arbitrary jobs, and I cannot change this policies.
I need a dynamic environment and I have no problem to manage this on server side I have problems to submit an arbitrary job to z/os and get its return code.