Re: Impact of SQL Packages

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Thomas

An SQL package is an object on a remote system - remote from the system 
where the program is running.

Were the programs moved to the system where the data resides? Then it is 
working with local data, not remote.

There should be a remote-database attribute in your program (module, 
actually) - the program would have to have been created with the RDB 
parameter set - and the name in that parameter would be seen using the 
WRKRDBDIRE command.

You should be able to see all SQL packages using WRKOBJ *ALL/*ALL 
*SQLPKG - we have several, and they are related to requests from Excel 
or Toad or SQL Server or some other client.

There is the PRTSQLINF command - you can use this to see just what is in 
an SQL package.

So check for a couple things -

1. Does your program want to work with data on a different system, or 
the same system, now that they've been moved?
2. Do you have the proper entries in WRKRDBDIRE?
3. Check for ALL SQL packages using WRKOBJ as shown above.
4. Check the source code for your programs for CONNECT statements - if 
data is local, those will likely need to be removed

Have fun!!
HTH
Vern

On 1/9/2015 11:52 AM, Thomas Garvey wrote:
> 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.