HP3000-L Archives

October 2004, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Dave Powell, MMfab" <[log in to unmask]>
Reply To:
Dave Powell, MMfab
Date:
Tue, 5 Oct 2004 10:29:55 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (74 lines)
Job queues have been a huge help here, with NO problems.  No reboot required,
but you need to re-set them after a reboot.  Just put all the commands into a
job, and have sysstart stream it.  Whenever you  add a queue or change a
limit, change the job, then stream it manually.  Just out of routine paranoia,
we stream ours daily in case 'someone' fiddles with a limit and forgets to
change it back.

Ours is:
!JOB STARTJQ,MANAGER/_____.SYS;OUTCLASS=,1;HIPRI
!ALLOW MANAGER.SYS;COMMANDS=LIMIT
!LIMIT
!CONTINUE
!LIMIT  1; JOBQ=HPSYSJQ
!LIMIT 15
!CONTINUE
!NEWJOBQ     SLEEPER;    LIMIT=10
!CONTINUE
!NEWJOBQ     QUICKIE;    LIMIT=1
!CONTINUE
!NEWJOBQ     USER;       LIMIT=1
!CONTINUE
!NEWJOBQ     EMAIL;      LIMIT=1
!CONTINUE
!LIMIT  10;  JOBQ    =   SLEEPER
!CONTINUE
!LIMIT   1;  JOBQ    =   QUICKIE
!CONTINUE
!LIMIT   1;  JOBQ    =   USER
!CONTINUE
!LIMIT   1;  JOBQ    =   EMAIL
!TELLOP JOB QUEUES ARE SET UP
....
----- Original Message -----
From: "Greg Stigers" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, October 05, 2004 09:52
Subject: [HP3000-L] Job limit vs. jobs queues


> Someone replied to me privately to the effect that the example I have seems
> to be ready for multiple job queues.
>
> Well, I did write:
> > Come January, I want to create a single-job queue. In the mean time,
> > I will probably rewrite some jobs to
> > STREAM SOMEJOBA.GROUP
> > PAUSE JOB=!HPLASTJOB
> > STREAM SOMEJOBB.GROUP
> > PAUSE JOB=!HPLASTJOB
>
> Is there any conceivable reason * not * to implement a SINGLEQ that allows
> only one job? Do we risk anything, anything at all, doing this? No reboot
> required, right? I do need to read up on the job queues (less-than-obvious
> URLs welcome). The only issues I can think of are resource utilization
> (which I assume to be minimal), adjusting limits where and how needed, and
> of course the herculean task of editing those few jobs that must run
> exclusively. OK, one other issue just now occurs to me: jobs that do not
> themselves run exclusively, but which should not run while other
> single-threaded jobs are running. I have in mind here our database
> reindexing and reorg jobs. At this point, am I back to resetting job limits,
> or having some other job pause while these execute?
>
> There is always the option to use a job scheduler to manage jobs as events,
> but that's another thread for later.
>
> Greg Stigers
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2