Re: How would a QZDASOINIT job end up with a funky library list?

[Nathan Andelin <nandelin@xxxxxxxxx>]

After client applications connect to QZDASOINIT Jobs, they can invoke the
CHGLIBL command and other APIs which affect QZDASOINIT Jobs. Seems like a
common requirement to me.





On Wed, Mar 15, 2017 at 11:34 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

> That can be set in the ODBC connection properties as outlined in
> https://godzillai5.wordpress.com/2015/07/08/setting-a-
> default-sql-library-and-library-list-on-a-odbc-connection-for-a-ibmi-db2-
> connection-in-windows-and-linux/
>
> I also saw something in a "libraries property attribute on the JDBC
> properties object" to set this.  I'd post a link but it's one of those
> sites where you have to register.  Granted I did register ficticiously and
> didn't require a confirmation email.
>
> And there's nothing stopping you from calling a custom CL program to set
> it.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   03/15/2017 01:13 PM
> Subject:        How would a QZDASOINIT job end up with a funky library
> list?
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> I witnessed something on a customer box that I can't explain:
>
> it seems that one of their QZDASOINIT SQL server jobs tripped a trigger
> program with a CPF4101 on a file that would be in the default user
> library list.
>
> On inspection I found that while the other eleven QZDASOINIT jobs in the
> system all had default library lists, which include the one where the
> file in question resides, the one QZDASOINIT job had a completely
> different library list.
>
> How would the library list on a QZDASOINIT job get changed in the first
> place?
>
> --
> JHHL
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD