Re: Integer type on SQL Server vs. AS400 Database

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Carel, I was testing this stuff this morning, and I think I used DDS 
to create fields of type B - binary. B 9 0 ended up as a 4-byte 
integer, and it even accepted a 10-digit number using an SQL INSERT, 
IIRC. B 10 0 resulted in an 8-byte integer. To me, this is all very 
odd. Probably non-SQL interfaces would fail to write a 10-digit 
number to a B 9 0 - maybe it is because you cannot put all 9's in a 
4-byte integer - the reasons why are usually a futile exercise to ascertain.

Interesting

At 11:43 AM 11/16/2005, you wrote:

> Ricky,
>
> Have you looked at the file with DSPPFM and display hex with F10?
>
> Perhaps that tells you more.
>
> I assume the file has been created with SQL. DDS based files do not 
> support integer data types (, yet).
>
> Regards,
> Carel Teijgeler.
>
> *********** REPLY SEPARATOR  ***********
>
> On 15-11-05 at 12:43 Ricky Thompson wrote:
>
> >I created a DB on the ISeries to match a MS SQL Server database so that we
> >could create a DTS package to transfer data between the two systems.  The
> >problem is the SQL Server number in a integer field is 10 long but when we
> >transfer it to the AS/400 it drops the first position.  If you do a RUNQRY
> >on the file it replaces the integer value with ******. I thought an integer
> >was from -2147483648 to +2147483647.
>
>
>
> --
> 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.