RE: SQLerror on field but shouldn't reference it

["Tyler, Matt" <mattt@xxxxxxxxxxxxxx>]

Rick,
        What you may be seeing is the SQL engine converting the sub-select
into a join query, in which case the sub-select is run at the same time.
You are receiving a data decimal error from SQL.  The "OR" is also a cause.
The query would have stopped at "lnstst<>'C'" had you used "AND" instead.

Thank you,
Matt Tyler
WinCo Foods, Inc
mattt@wincofoods.com

-----Original Message-----
From: Chevalier, Rick [mailto:Rick.Chevalier@americredit.com]
Sent: Thursday, February 06, 2003 14:57
To: Midrange Mailing List (E-mail)
Subject: SQLerror on field but shouldn't reference it

I am receiving an error running the following SQL statement:
select lnnote, lnstat, lnpnbr from lnp00301                      
where lnstat <> 'C' or lnnote in                                 
(select lnnote from lnp00301 where (lnstat = 'C' and

days(substr(lnpnbr, 1, 4) || '-' || substr(lnpnbr, 5, 2) || '-' ||
substr(lnpnbr, 7, 2)) > (days(char(curdate())) - 365)))          
order by lnstat desc, lnpnbr                                     

The error I receive is 'Selection error involving field LNPNBR.'  Displaying
the message identifies the record number and refers me to the job log.  The
job log contains this message:
Message ID . . . . . . :   CPD4019       Severity . . . . . . . :   10

Message type . . . . . :   Diagnostic

Date sent  . . . . . . :   02/06/03      Time sent  . . . . . . :   15:31:34



Message . . . . :   Select or omit error on field LNPNBR member LNP00301.

Cause . . . . . :   A select or omit error occurred in record 1042912,
record
  format LNP0031, member number 1 of file LNP00301 in library BNKPRD08,

  because of condition 6 of the following conditions:

    6 - A data mapping error occurred on the field before the select or omit
operation was attempted.

The values for record 1042912 are:
Record#  LNBK LNNOTE        LNSTAT LNPNBR    
1042912    8     123456789                  

My question is this.  I realize that LNPNBR is blank for this record and
would not be valid for the days function in the subselect but the LNSTAT
field is blank also so it would pass the initial test of LNSTAT <> 'C'.  Why
is SQL trying to perform a numeric operation on this record?  It seems to me
that it would stop after passing the LNSTAT <> 'C' test.  What am I missing?


Rick Chevalier
Sr. Programmer Analyst

rick.chevalier@americredit.com

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.