Re: SQL insert SQL code 404 - value too long for the destination column

Why "of course"? Why not just do that?
To me this sounds a lot more safe and granular than trying to find the
exact message id, find the message file and see if you can find an
automatic reply to see if it will allow it to automatically truncate.
An alternative would be to change the target table to have the column be a
variable sized string but many people are reluctant to use any column types
or attributes which were not available on the S/36.

On Tue, Nov 19, 2024 at 2:20 AM Dave <dfx1@xxxxxxxxxxxxxx> wrote:

Hello,

Is there any way I can avoid this error when Inserting from a table to a
physical file? I would like the data to simply be truncated. A part from
adding the substring function of course.

Thanks
--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.