HP3000-L Archives

June 2001, Week 3

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:
"Johnson, Tracy" <[log in to unmask]>
Reply To:
Johnson, Tracy
Date:
Tue, 19 Jun 2001 13:04:17 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
There's always the old fashioned ;INPRI= parameter coupled
with a job LIMIT of 1 and a JOBFENCE of 0.

You're GUARANTEED to be able to sequence at least 14 jobs
this way (15 if you toss in an early job with the ;HIPRI
parameter.)

    ;^)

Tracy Johnson
MSI Schaevitz Sensors


-----Original Message-----
From: Jonathan M. Backus [mailto:[log in to unmask]]
Sent: Tuesday, June 19, 2001 11:53 AM
To: [log in to unmask]
Subject: Re: Getting jobs to run in proper sequence


Jay,

        From a purchased solution side of things, all the major job
scheduling
packages will allow you to do this.  Short of that, I created a command file
that would do basically what you are talking about.  The command file
basically pauses as long as it finds a job executing with the name (or
partial name) specified.  For example the command "JOBWAIT fred@" in a job
stream would cause the job to wait until there was no other jobs with the
name fred+"anything" executing and then it would continue.

Thanx,
  Jonathan (Jon) M. Backus, MPE-CSM ~ President
  Tech Group ~ 15 Catawba Place ~ Hagerstown, MD ~ 21742-6515
  Email: [log in to unmask] ~ AIM: JMBackus
  Vmail: 301.988.0614 ~ Fmail: 301.714.1854
  Web: www.TechGroupMD.com


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Jay Willis
Sent: Tuesday, June 19, 2001 11:40 AM
To: [log in to unmask]
Subject: Getting jobs to run in proper sequence


Hi all,

I am seeking suggestions on how we might get a series of jobs to run in the
proper sequence. Currently the jobs, in turn, build/check for the existence
of/purge dummy files. I don't care for this approach since a file may
inadvertently be renamed, purged, etc. between jobs. This happened to us
recently when a job aborted, thus not building the dummy file that the
subsequent job was to check for, allowing the user to stream a job out of
sequence. The users can make changes to the data, based on the reports the
jobs produce, so that after job A runs, they go over the reports, make
changes, then stream job B, and so forth.

Any ideas/thoughts gleefully accepted.
Jay

* 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 *

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

ATOM RSS1 RSS2