View previous topic :: View next topic
|
Author |
Message |
yujindl
New User
Joined: 20 Jun 2007 Posts: 2 Location: ChengDu,SiChuan,China
|
|
|
|
HI, Everyone.
I am giving MF training to students. They are always submit too many jobs and forget to purge they. This will dramaticly make the PRINT QUEUE full and can not submit any jobs more.
How can i avoid this:
1.is there any options that specify that system will purge the jobs sumbitted like ,one days ago?
2.is it possible to purge the jobs by JCL, what should I code?I have no idea.
or is there any other way to avoid?
the way I am doing is to purge jobs using '//P ** //', but it is too hard to control.
Thanks
-------Jin |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
normally there is a msgclass that will not print and will purge every 24 hours. X is typically this class, but you need to ask your mf ops people because it is site specific. Also, insure that you are not inadvertently picking an auto-archival class.
Also, if you are giving mf classes, the first thing I would teach is 'how not to disrupt the OP-Sys'. |
|
Back to top |
|
|
yujindl
New User
Joined: 20 Jun 2007 Posts: 2 Location: ChengDu,SiChuan,China
|
|
|
|
Hi, Dick
Thank you for your information.
Usually, we used MSGCLASS = A in JCL. Did you say that MSGCLASS = X(typically) will not print and will purge every 24hour? if i change my jobs to MSGCLASS = X, Could i get the SYSPRINT information? And can i specify the system will purge not 24 hour but 12 hour? what are auto-archival class?
I am on a training system, and the there in no OPS people. the sysadmin seems too busy to answer my question.
Thanks again and welcome your first 'how not to disrupt the OP-Sys'
|
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello yujindl and welcome to the forums,
As Dick mentioned, the msgclass you want might be X, but it would be better to varify which class(es) you should use for your training.
Your other questions are system-specific (but they should be documented somewhere). Auto-archived happens automatically and it is not what you want for your student exercises - once you find out which class(es) are auto-archived, you will want to make sure they are not used.
If you cannot get the system support people to answer your questions, you may need to have your manager ask. When i've run into this, it is usually because they are just unwilling to take a few minutes - not because they are that busy 100% of the time. |
|
Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005 Posts: 2358 Location: Israel
|
|
|
|
You can use Batch SDSF Commands to purge jobs (and actually - to do anything under SDSF). Search this board for "batch SDSF" to see some examples.
O. |
|
Back to top |
|
|
kumaresh.M
New User
Joined: 17 Feb 2006 Posts: 64 Location: Bangalore
|
|
|
|
Hi yujindl,
I thing non of the developers id is not having the authority to purge there jobs.
Before purging there is lot of considerations has to be takencare.
1)check the amount of SPOOL volume
2) we have to take the SPOOL offload and take a backup
3) and Move this jobs to internal DASD's
4) then we have to make a copy and kept this in offsite.
for this all we are having some deadlines.we did althose things and purging in every night.
Someother ways to clear the spool is
Recycling JES2 with cold start
doing on coldstart IPL's
But for doing everything you need a authority id.I cant get you how you can puge it by yourself????
Cheers,
Kumaresh.M |
|
Back to top |
|
|
stodolas
Active Member
Joined: 13 Jun 2007 Posts: 632 Location: Wisconsin
|
|
|
|
We purge our own TEST jobs all the time. The production jobs are another story. The OP is talking about test jobs. |
|
Back to top |
|
|
|