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


  1.  Home
  2. MIDRANGE-L
  3. August 2005

Re: v5r2 question

But this DOES work from V5R2 on, so I guess IBM decided to change the design. And I just verified that the table is still not in QSYS2/SYSTABLES. Not sure what that means, but the long name-short name relationship is stored somewhere - there is also no SYSTABLES in QTEMP to hold it. 

Hmmm!

At 08:32 PM 8/12/2005, you wrote:



On 12/08/2005, at 11:31 PM, vhamberg@xxxxxxxxxxx wrote:
On our V5R1 machine I get the same results as you do. But if I use the system name TESTI00001, it works fine. And if I create the long-name view into a permanent library, it works. Looks like a PTF needed. 

It also fails with CREATE TABLE - and short name works.
I think this is business as usual (or working as designed in IBM parlance). Files created in QTEMP are not added to the catalogue tables so there is no way to convert the long SQL name into the real system file name hence the "cannot find" error. 

Why is this so?
1) Performance - QTEMP files are by their nature temporary and visible only to the job owning QTEMP so why update global reference files twice (once when created and once when QTEMP is cleared at job end)? 2) COLLECTION/SCHEMA/LIBRARY names are restricted to 10 characters so how could the catalogue tables distinguish between one job's QTEMP and another? Although the catalogue tables allow for longer schema names (and QTEMP libraries are distinguished by hidden long names) there is no external access to the QTEMP internal long names. At the least this could cause conflicts where one job creates file STUFF in QTEMP and another job tries to create a file with the same name and gets told it already exists because an entry is found in the catalogue tables. Attempts to access a QTEMP file could result in file not found errors even though a catalogue entry exists. Also potential problems with files that have the same name but different record layout. 3) Recovery - less likely to require a reclaim of the catalogue tables in the event of system failure if QTEMP stuff is not in them. 

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

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.