Re: swap QTEMPs -- MI400

I understand that, and I'm sure you understand that. I stressed the
point because others here might find the technique intriguing and wish
to use it, but understandably may not have in-depth info on MI and
system internals. And while we may strive to restore the original
pointer, it might not be for one reason or another, forgetfulness
perhaps, or a canceled job, etc. Our best intent can't handle a
situation in which the job is canceled. And once the job is canceled the
only way I know to fix the problem is to IPL (at least I think that
fixes the problem!). 

While I find the technique intriguing and even useful, it's not to be
taken lightly. It's too bad the pointer is not refreshed upon each use
of the job structure. That would obviate this problem.

Gary Guthrie




Leif Svalgaard wrote:
> 
> 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
> +---


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