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



That's why it is important to restore the QTEMP to its original value before
the job ends. My little program allows you to do just that.

> -----Original Message-----
> From: Gary Guthrie [SMTP:GaryGuthrie@home.com]
> Sent: Monday, December 20, 1999 10:57 AM
> To:   MI400@midrange.com
> Subject:      Re: swap QTEMPs
> 
> I want to reiterate a point I made when I originally commented on the
> technique.
> 
> Failure to restore the proper library pointers in the job structure can
> result in HIGHLY UNDESIRABLE results. Leaving a bogus QTEMP pointer in
> the job structure when the job ends means that another job can (and
> likely will) use the changed job structure, and this job will be
> completely unaware that it has a bogus QTEMP pointer. Not a good thing!
> 
> Gary Guthrie
> 
> 
> 
> Jim Langston wrote:
> > 
> > That sounds exactly like what I would like to do.
> > 
> > Create a library such as DEBUG and be able to
> > attach job's QTEMP to this library instead of QTEMP.
> > 
> > Would you have any sample source on how to do this?
> > 
> > If it already passed in this message list, could someone
> > repost it?  I seemed to have missed.
> > 
> > Regards,
> > 
> > Jim Langston
> > 
> > leif@attglobal.net wrote:
> > 
> > > <SNIP>
> > > This is a great debugging feature. You start a batch job and now
> > > you want to check what is writes to its QTEMP. Start an interactive
> > > job, create a permanent library, say, DEBUG, then attach DEBUG
> > > as QTEMP for the batch job and watch what the batch job is
> > > doing by inspecting files in DEBUG.
> > 
> > +---
> > | This is the MI Programmers Mailing List!
> > | To submit a new message, send your mail to MI400@midrange.com.
> > | To subscribe to this list send email to MI400-SUB@midrange.com.
> > | To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> dr2@cssas400.com
> > +---
> +---
> | This is the MI Programmers Mailing List!
> | To submit a new message, send your mail to MI400@midrange.com.
> | To subscribe to this list send email to MI400-SUB@midrange.com.
> | To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> dr2@cssas400.com
> +---
+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.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.