RE: Impact of SQL Packages

Thomas,
Someone else on this list will reply in more depth, but my simplistic
understanding is the iSeries uses SQL packages to store info about
specific SQL statements and how best to run them.
Older packages are routinely replaced and updated and I know
that, under some circumstances, deleting a specific package can
"solve" a problem. Other than that, people like myself can, usually,
work in "happy ignorance" . . . but, you can see more detail by running
in Debug mode and inspecting the job log.
iSeries Navigator is also a good source of SQL information about SQL,
including recommendations on indexes that can be created to improve
performance.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Friday, January 09, 2015 10:53 AM
To: Midrange Systems Technical Discussion; RPG programming on the IBM i (AS/400 and iSeries)
Subject: Impact of SQL Packages

Hi,

I have a number of RPGLE programs with embedded SQL that were created and compiled on one system, then moved to another system.

The original object library on the original system and the destination library on the destination system are not named the same.
The 'DB2 for IBM i module attributes:' section has a reference to SQL Package Name which includes the original library name.

This library does not exist on the current system.

I am trying to track down why the program does not work correctly on the current system (The SQL statements are not selecting any records from the data file).
When I simply recompile the program on the current system, the only thing that's different is the SQL Package Name Library reference (it now points to the object's library), the program works fine.

I know nothing about SQL Packages, how or why they are created, or why my program has a reference to one (which is not found anywhere on either system, at least using an object type of *SQLPKG).

Could this difference be my problem? If so, why?

Thanks for any advice.