Re: SQL States - expected exceptions

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I had one I created at another job...

But my PC is still en-route :)

I looked around quickly for another one, but couldn't find one.

Charles


On Mon, Jan 9, 2017 at 12:54 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

> I do not know of any.
>
> Is there a popular /copy module people use for sql states?
>
>
> 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:   Charles Wilt <charles.wilt@xxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   01/09/2017 02:51 PM
> Subject:        SQL States - expected exceptions
> Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
>
>
>
> All,
>
> Is there a list of possible/likely SQL state codes for various SQL
> statements?
>
> Basically looking for the SQL equivilent of CL's
> Error messages for CHGLIBL
>
>     *ESCAPE Messages
>     CPF2106     Library list not available.
>     CPF2110     Library &1 not found.
>     CPF2113     Cannot allocate library &1.
>     CPF2176     Library &1 damaged.
>     CPF2182     Not authorized to library &1.
>     CPF2184     Library list not replaced.
>
>
> For example,
> DROP TABLE
>
> If I expect the table to possible not be there, I'd check for SQLSTATE =
>      d NOT_FOUND...
>      d                 c                   const('01532')
>      d UNDEFINED_OBJECT_NAME...
>      d                 c                   const('42704')
>
> (not sure which actually gets set )
>
> In particular, I'm curious if
> SET SCHEMA
> and
> COMMIT
>
> could return any warning codes.
>
> I'm also using CREATE TABLE and UPDATE.
>
> For the CREATE TABLE, I'm checking for
>      d CREATED_NOT_JOURNALED...
>      d                 c                   const('01567')
>
>
>
> Thank you,
> Charles
> --
> 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