× 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: Cannot resolve to QTEMP at level 50
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Mon, 11 Jun 2001 10:36:38 -0500


----- Original Message ----- 
From: <Gene_Gaunt@ReviewWorks.com>
To: <MI400@midrange.com>
Sent: Monday, June 11, 2001 8:10 AM
Subject: Re: Cannot resolve to QTEMP at level 50


> 
> Compare the existence attribute (temporary/permanent) of QTEMP objects
> between level 40 and level 50.

Thanks Gene,

OK, makes sense for other job's QTEMP for security reasons.
I just didn't think it applied to my own QTEMP. But with hindsight
it has to be so, because the QTEMP names are recycled for
later jobs (performance reasons, presumably).
Not a big problem, one can get a system pointer to QTEMP
from the PCO (but then *this* circumvents the prohibition
against resolving one's own QTEMP). Ah, well: who says
things have to be consistent?




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

Replies:

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.