Re: swap QTEMPs

The situation I want to get away from is if the sign on
abnormal ends without doing # 4.

Say you do #1, #2, #3... and then go to lunch while it's
running.  Someone else comes along, sees your away,
and ends you job.

Or, you do #1, #2, #3, get called away, get auto disconnected
after an hour.  Forget about it, 4 hours later the job goes bye
bye (that is the times on our system).

In either of these cases the QTEMP pointer is messed up,
as I have come to believe.  Because you were not able to
reinstate the old QTEMP before you ended the job.  That
is the situation I would like to get away from before I could
even think about using this technique.

Pointers pointing to la-la land can be kept on the Windows
operating systems.  We don't need to introduce windows type
bugs to the AS/400.

Regards,

Jim Langston

Leif Svalgaard wrote:

>         [Leif Svalgaard]  I don't think we can "release it back to the
> system",
>         but it is really not necessary to do so. I don't quite understand
> your
>         scenario below, but here is what I do:
>         1) log on (as you do) as another user.
>         2) assign a permanent library as QTEMP (no swapping actually) for
>         the job under test
>         3) let the test proceed
>         4) after the test reinstate the old QTEMP.
>         5) end the job under test
>

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