Re: SQL insert error - value for column too long

As Rob and Joe pointed out the columns must be in the same positions.
To get this to work with in INSERT statement you would have to list all the
columns.
INSERT INTO wlklib/dshpf34 COLUMNS(col1, col2, ...)
( select a.* from DSHXFR/DSHPF34 a )
make the order of the columns in dshpf34 match the column order of
dshxfr/dshpf34.

Alternatively you could use a CPYF with FmtOpt(*MAP *DRP) and this should
popule correctly

Rob

On Tue, May 28, 2019 at 11:36 AM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:

On 5/28/2019 10:32 AM, Steve Richter wrote:

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.

I think this is your issue.

If I am reading your post correctly, the columns need to be in the same
order.

--
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