× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


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

Dan,

You're misunderstanding me - you are correct that there is no implicit way
to do this.  One can program a method of copying one job's QTEMP to the
QTEMP of a job that it submits, without requiring anything "magical" (like
MI) to do it.  For example, have the submitting job create a uniquely named
save file, do a SAVOBJ of QTEMP to it, then when submitting pass the name of
the save file as a parameter.  The submitted job then does RSTOBJ and
deletes the save file.  This method may not be elegant, but it's simple and
reliable, and requires only CL.

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
instructions.

-----Original Message-----
From: D.BALE@handleman.com [mailto:D.BALE@handleman.com]

Well, now I'll have to bite.  There is an IBM-supported method of
"inheriting"
another job's QTEMP?

By all means, please describe it.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Dan,

Actually, it wouldn't have to use MI, either. <grin>  Smoke and mirrors
help, though.

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
instructions.

-----Original Message-----
From: D.BALE@handleman.com [mailto:D.BALE@handleman.com]

<sigh>  Ya know, I even winced when I wrote that "nothing ever, EVER ...".
I
know better.  OK, from here on out, I'll use "nothing, short of using an MI
solution, ever, EVER ..." <g>

The misconception I was taking aim at was the idea that there is an
IBM-supported method of "inheriting" another job's QTEMP, akin to the LDA.
It
seems to be a popular notion.  This same question popped up last week.

I think my generic response would be, "Yes, it can be done.  However, if
there
is a flaw in the design, it would be better to correct the design than to
convolute it any further."

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
> >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
alive
> only for the job (i.e. each different job number is a distinct job).
Doesn't
> matter whether you sign off or not, nothing ever, EVER copies from one
job's
> 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.