Re: swap QTEMPs

>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!). 

IPL does fix it, but see below.

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

RPLQTMP works like this:

RPLQTMP lib job user nbr

a pointer to the old (real) QTEMP is saved before the new library 
is installed. At this point also save the pointer to the internal job 
description. At any time later RPLQTMP *OLD can then restore 
the saved lib in the saved job description even if the job has ended. 

There is still a chance if you wait too long that another job will have
gotten the altered job description, so I have not really solved the
problem just improved the chances.

 


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