Prerequisites:
Host:
Version: v5r3
Support. net
Client:
Software: Client Access
Version: v5r3
Service Pack: si21917 <this is the latest Service Pack>
All of our previous Program All of our SQL statements are
Select fielda, fieldb from libraryname. tablename
If it is written in this way, it is not conducive to system migration.
How can we improve system migration?
Of course, migration does not mean that iseries is not needed. Instead, we can strip some non-core services, such as query services, to Oracle. For a small amount of data, the query speed is definitely better than iseries.
Currently, in iseries, we have used this capability to permanently remove our SQL statements from library restrictions.
Create librarylist ~~ in connectionstring ~~
Just like librarylist in the rpgle program.
Its Mechanism = top priority of the List ~~
For example, see dataaccess of my framework. iseries. connectionbuilder // There are actually modifiable places in this place. For example, if it is used for query, we set it to readonly = true for connection, which can greatly improve the performance.
The Set query statement is changed
Select name from account
Haha, is it the same as other databases ~~
Usually, we set librarylist = * usrlibl, librarya, libraryb
If there are objects with the same name in the librarylist, pay attention to the sequence. Of course, a table with the same name is a bad design ~~
Use this to query the qsys object that has been qsys2 ~~
