You would have to have hard-coded "pairs" of jobs for that to ever
work....and I don't thinks that would be very practical.
If you did not have hard-coded pairs of jobs, the 2nd job would have one
hell of a time trying to figure out which file it was supposed to
read...JOBA(1) creates a unique file, but it's name would not be known to
JOBB(1)...now multiply that problem by several instances of JOBA(#).
> -----Original Message-----
> From: Jonathan M. Backus [SMTP:[log in to unmask]]
> Sent: Thursday, May 24, 2001 7:52 AM
> To: 'Shahan, Ray'; [log in to unmask]
> Subject: RE: Passing HPSTREAMEDBY from one job to another.
>
> Ray,
>
> You have the "Originating job" create a data file with a unique name
> which
> the "created" job knows. For example, the originating job can determine
> its
> job number (HPJOBNUM) and create a uniquely named file (JP#####) - Perhaps
> JP for Job Pipe and the job number. Part of the HPSTREAMEDBY variable
> value
> available to the created job shows the job number of the originating job.
> So, the created job would be able to figure out the "job pipe" file name.
> Plus it would be unique for each originating job.
>
> 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 Shahan, Ray
> Sent: Thursday, May 24, 2001 8:27 AM
> To: [log in to unmask]
> Subject: Re: Passing HPSTREAMEDBY from one job to another.
>
>
> Assuming that the file you echo to is named, how would you stop two jobs
> of
> the same name designed to create the file from stepping on the file/data,
> and how do you insure that two downstream jobs of the same name don't read
> the wrong file/data?
>
> EXAMPLE:
>
> JOBA(1) creates fileA at 5:00am and streams JOBB(1)
> JOBA(2) overwrites fileA at 5:02 and streams JOBB(2)
>
> JOBA(1) can't log until 5:05, so it reads filea with JOBA(2) data rather
> than JOBA(1) data.
>
> > -----Original Message-----
> > From: Jonathan M. Backus [SMTP:[log in to unmask]]
> > Sent: Thursday, May 24, 2001 6:38 AM
> > To: [log in to unmask]
> > Subject: Re: Passing HPSTREAMEDBY from one job to another.
> >
> > Robert,
> >
> > While you are echoing to create the second job, why don't you
> echo
> > HPSTREAMBY to a file and then have the second job INPUT that file into a
> > variable?
> >
> > 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 Robert Mills
> > Sent: Thursday, May 24, 2001 7:22 AM
> > To: [log in to unmask]
> > Subject: Passing HPSTREAMEDBY from one job to another.
> >
> >
> > Hi everyone,
> >
> > We have a command file, called jobtell, that uses MPEX's %WARNF command
> to
> > display a message over the function keys of the session who :STREAMed it
> > (extracts the session number from the HPSTREAMEDBY variable). It works
> and
> > the users love it. Hurrah!!!!!!!! I now have to get a job :STREAMed by
> > another job to send a message to the session that started it all (hope
> > that
> > this makes sense to you). This means that I have to somehow pass the
> first
> > jobs HPSTREAMEDBY to all subsequent jobs.
> >
> > Apart from getting the first job to build the second job (echo commands
> to
> > a
> > temporary file) and then :STREAM it I can see no other solution at the
> > moment.
> >
> > Any ideas?
> >
> > regards,
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > |Robert W.Mills (Systems Development Manager) |
> > |Windsong Services, St. Mary Cray, ENGLAND |
> > |Tel : +44 (0)1689 870622 x3005 |
> > |Fax : +44 (0)1689 899026 |
> > |Email: [log in to unmask] |
> > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > * 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 *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
