Re: SQL insert error - value for column too long

[Steve Richter <stephenrichter@xxxxxxxxx>]

I think the DSPFFD is too long to post completely.  64 columns.   Both
tables have the same number of columns. The same record length.  But
columns are not in the same sequence in the buffer.

here is the AUTOSEND846 column in the from table:
AUTOS00001 CHAR            1       1       716        Both     AUTOSEND846

  Alternative name  . . . . . . . . . . . . :       AUTOSEND846

  Default value . . . . . . . . . . . . . . :        'N'

  Coded Character Set Identifier  . . . . . :     37

and the to table:
AUTOS00001 CHAR            1       1       685        Both     AUTOSEND846
  Alternative name  . . . . . . . . . . . . :    AUTOSEND846

  Default value . . . . . . . . . . . . . . :      'N'

  Coded Character Set Identifier  . . . . . :     37


notice the columns are identical.  But their positions in the buffer are
different.   The to table is pos 685.  The from table is at pos 716.
( this is because I have been adding columns over time.  But sometimes I
might not add them to both tables in the same sequence. )

interesting to note that in pos 685 of the from table is a 10 character
field.  And the SQL insert error message says I am copying from length of
10 to length of 1.

           Data        Field  Buffer    Buffer        Field    Column
Field      Type       Length  Length  Position        Usage    Heading
PATHNAMING CHAR           10      10       685        Both     PATHNAMING
  Default value . . . . . . . . . . . . . . :  None
  Coded Character Set Identifier  . . . . . :     37




On Tue, May 28, 2019 at 11:12 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> I believe that text belongs to
> DSPMSGD RANGE(SQL0404) MSGF(QSQLMSG)
>
> Can you supply a DSPFFD of the from column, and the to column?
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Steve Richter
> Sent: Tuesday, May 28, 2019 10:44 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: SQL insert error - value for column too long
>
> running an SQL insert:
>
> insert into wlklib/DSHPF34
> ( select  a.*  from    DSHXFR/DSHPF34 a )
>
> get error:  Value for column or variable AUTOSEND846 too long.
>
> the help text says:  the  length of AUTOSEND846 is 1 and the length of the
> string is 10.
>
> but the from field length is 1.  To prove it I use the HEX function to
> dump the column value:
>
> select  hex(a.autosend846)  from   dshxfr/dshpf34 a
>
> and the result is :
> HEX
> D5
>
> why this error?
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://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: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://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: https://amazon.midrange.com