Re: Embedded SQL inserts to wrong library

[Robert Clay <zreclay@xxxxxxxxx>]

Someone else will need to chime in on this, but in your answer to 
Birgitta, I noticed a SQLPKG value. Could the data in that SQLPKG be 
relevant?  We don't use SQL packages except for SAP and on those 
systems, we delete those whenever there is a change to programs, 
database changes, OS /changes/, PTFs, etc.

Maybe there is something that isn't making the journey from 5.4 to 7.1 
in relation to that SQL package?

Robert
"Contrariwise, if it was so, it might be; and if it were so, it would 
be; but as it isn't, it ain't. That's logic."--Tweedledee

On 05/14/2014 11:55 AM, Jacob Smallwood wrote:
> Hi Birgitta,
>
> Yes, we did create the program with system naming convention (by
> virtue of that being the default; we don't explicitly specify that
> anywhere). I was under the impression that that's what I wanted,
> however, because the link I was looking at made me think that was
> necessary for library list changes to be detected in this scenario. Is
> that not correct? We don't have a default schema set and I couldn't
> find anywhere that we a do a SET SCHEMA in a scan of our codebase.
>
> For reference, here's what DSPPGM shows as the SQL attributes of this
> module/program:
> DB2 for IBM i module attributes:
>    Number of SQL statements . . . . . . . . . . . :   19
>    Commitment control . . . . . . . . . . . . . . :   *NONE
>    Relational database  . . . . . . . . . . . . . :   *LOCAL
>    Naming convention  . . . . . . . . . . . . . . :   *SYS
>    Allow copy of data . . . . . . . . . . . . . . :   *OPTIMIZE
>    Allow blocking . . . . . . . . . . . . . . . . :   *ALLREAD
>    Delay PREPARE  . . . . . . . . . . . . . . . . :   *NO
>    Close SQL cursor . . . . . . . . . . . . . . . :   *ENDACTGRP
>    Date format  . . . . . . . . . . . . . . . . . :   *ISO
>    Date separator . . . . . . . . . . . . . . . . :   /
>    Time format  . . . . . . . . . . . . . . . . . :   *HMS
>    Time separator . . . . . . . . . . . . . . . . :   :
>    Default Collection name  . . . . . . . . . . . :   *NONE
>    SQL package name . . . . . . . . . . . . . . . :   LNNOTE
>      Library  . . . . . . . . . . . . . . . . . . :     QTEMP
>    Dynamic user profile . . . . . . . . . . . . . :   *USER
>    SQL sort sequence table  . . . . . . . . . . . :   *HEX
>    SQL language identifier  . . . . . . . . . . . :   ENU
>    Connection method  . . . . . . . . . . . . . . :   *DUW
>    SQL Path . . . . . . . . . . . . . . . . . . . :   *LIBL
>
> Thanks,
>
> Jacob Smallwood
>
> On Wed, May 14, 2014 at 11:08 AM, Birgitta Hauser
> <Hauser@xxxxxxxxxxxxxxx> wrote: