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



Chuck,

I'm not going to doubt your word on it, you probably looked at the code :-)

On page 10 of the document in the following link, Dan Cruikshank says it
wasn't on the S/38, and you had to use REFACCPTH.

http://www-03.ibm.com/servers/eserver/iseries/db2/pdf/Performance_DDS_SQL.pd
f

http://tinyurl.com/3889l6

I worked on the S/36 and S/38 prior to moving over to the /400 in '89.
Unfortunately, my poor old head can't remember that far back (or perhaps it
is the foggy recollection that are that far back), but I could have sworn
that it was something that wasn't on the earlier releases on OS/400. Perhaps
what I am remembering is seeing it on the AS/400 when I had not seen it on
the S/38...

Anyway, thanks for putting me straight on that one :-)

Crispin.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, March 13, 2008 8:33 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Are we insane? Unique use of native DB2

Well over two decades since Access Path sharing was introduced on the
R7 of S/38. I thought the REFACCPTH was a carry-over from the S/38 and
that it was deprecatory usage, but seems it was new on V1R1M0. It is
the ACCPTH keyword usage that is deprecatory; maybe only allowed on the
LF38, since I can not find it in the DDS manual? An ACCPTHMBR parameter
was on S/38 CRTLF, but none for OS/400.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.