mainframer wrote:Initially I could submit n-number of jobs. But later it was restricted to 4-5, and just 1 in case of multiple Steps.
I can submit jobs with 250 steps. I guess you mean multiple jobs in one member. Anyway, I've upped the limit a bit, which should be enough for now. But why do you need to keep so many jobs in the output queue, if the output is really required, you can put it in a dataset, rather than SYSOUT=*...
mainframer wrote:I know the fact that spool should be clean & clear. I always do that.(expect some occasions like no login or power issue) As disconnect feature is not working and I have electricity fluctuation in my area, I can not re-connect in few minutes I may miss to purge the Jobs from SPOOL. I have done pre Userid* in spool so I can view only my jobs and clean them and do not miss on this, as I used to do always. I immediately cancel the JOB that enters in Infinite LOOP.(exception is valid here as well)
And why would there be an exception?
To give an example of the things that we have seen: A COBOL program that did a bubble-sort. The input? Five records. The job was canceled when it had clocked up more than
5 hours CPU time... With some exceptions, jobs on this system should not need more than a few seconds of CPU time - I know I am somewhat of a sinner as I have one job that will clock up to half an hour of CPU time, but given its nature, it uses the PL/I "COUNT" option to count executed statements, there is little I can do about it. Hoever, to minimize poblems for others, I run it at
PRTY=1 and at a time (midnight after here in Europe) when there are few other users on the system.
mainframer wrote:Now, my request is : 1) can we disconnect our session so we can login again (Disconnect is not working anymore).
2) Can Jobs in spool be deleted automatically.
and main 3). Can we increase the number of submitting JOBs, at least 10 should be there.(just request)
If it is possible, please let us know. I am not a Trainee, just want to be in touch with Mainframes and FANDeZHI is wonderful.
Jobs are (supposed to be) deleted automatically a few times per day, but this does not always work, so please clear out the spool when you log off. As for the disconnect via the website feature, I'd suggest you send a private message to
sysprog and ask him if he can restore it.
mainframer wrote:You may introduce Warning system !! depending on severity of Crime(
) so users get few chances to divert himself on right path before any harsh action and avoid abuse of our system.
I'm not sure if that is possible on z/OS and besides that, it would put a burden on us to administer it. Revoking someone maybe harsh, but it's far easier...