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



Hi,

just an other comment:
--recreate DDS keyed logicals needed by RPG programs so that the keyed
logical shares the 64k access path from one of the SQL indexes.

You do not have to recreate the keyed logical files, as long as you don't use field selections, joins or select/omit clauses. It is possible to access SQL indexes like any other logical file with native I/O.

With release V5R4 it is also possible to specify the page size for both SQL indexes and DDS described logical files. The page size can be specified between 8 K and 512 K which may quite helpful for accessing very small and very large files. The default values for the page size did not change, i.e. keyed DDS described logical files are created with 8K page size per default, while SQL indexes are created with 64K by default.

And there is also an quite helpful enhancement in the CREATE TABLE and the CREATE VIEW statements. With both statments a record format can be specified which differs from the table name. You simply have to add RCDFMT FormatName to the create statement

Birgitta

----- Original Message ----- From: "Wilt, Charles" <CWilt@xxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, September 21, 2006 14:07
Subject: RE: Simple Display file problem


Note that this entire article is about exactly what Joe was talking
about.

--Instead of using DDS to define your physical files, you should be
using SQL DDL.

--Create appropriate SQL indexes

--recreate DDS keyed logicals needed by RPG programs so that the keyed
logical shares the 64k access path from one of the SQL indexes.

--all of the above can be done without needed to recompile your current
RPG apps.

--You can continue to use native RPG I/O with an SQL DDL defined
database and see significant improvements over a DDS defined database.

--The article says nothing about native RPG I/O vs. SQL I/O.




HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Wednesday, September 20, 2006 9:00 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Simple Display file problem

<snip>

This has some interesting details.....
http://www-03.ibm.com/servers/eserver/iseries/db2/pdf/Performa
nce_DDS_SQ
L.pdf#search=%22iseries%20ddl%20vs%20dds%20performance%22
</snip>



I think this article says it all or at least a hell of lot better than
me. This is one of the articles from IBM on SQL and DDS that were
originally published in Iseries Network. Thanks.





--
This is the RPG programming on the AS400 / iSeries (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-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.