• Subject: RE: Oops JOBQ perceptions
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Wed, 1 Nov 2000 09:29:14 -0500


This is nit-picky, and I'm not certain my source was authoritative, but
doesn't the system delete and re-create QTEMPs (like the /38 did) at Level
50 security?  Thanks!

Dave Shaw
Spartan International, Inc.
Spartanburg, SC
To subscribe to the MAPICS-L mailing list send email to
MAPICS-L-SUB@midrange.com or go to www.midrange.com and follow the

-----Original Message-----
From: Leif Svalgaard [mailto:leif@attglobal.net]

> >1) If I put stuff in QTEMP before launching JOBQ, then I sign
> >off, does the batch job have access to that QTEMP story like
> >it has access to what was in the LDA when I launched it, or
> >is any QTEMP access by a batch job totally independent of the
> >interactive job that created the job?
> A lot of people seem to have a hard time believing this, but QTEMP is
> only for the job (i.e. each different job number is a distinct job).
> matter whether you sign off or not, nothing ever, EVER copies from one
> QTEMP to another job's QTEMP.  Can't be done.

not quite correct Dan,

QTEMPs live on forever and are being reused from job to job
(but are emptied when the job ends). On the MI400 list a while
back there were postings showing how to do what you just can't
be done. Now, it ain't easy...
But possible.
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].