"DIY versioning system" sounds like you may have access to the (CL?) code.
Could you add a series of looped-SNDUSRMSG messages until the user returns a
blank reply, or some kind of special-value?
Tacking the replies together into a single field would potentially give you
TYPE(*CHAR) LEN(9999).
It's not an ideal solution I know. It depends on how tolerant your end users
are, and how badly you need >132 characters.
Jeff Bull
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: 25 September 2014 14:48
To: MIDRANGE-L (midrange-l@xxxxxxxxxxxx)
Subject: SNDUSRMSG need reply longer than 132 characters
We have a DIY versioning system that uses SNDUSRMSG to get the change
descriptions used for check-ins. That works fine except for the 132
character limit for the reply parameter. Anyone know of a way to get a
longer reply to an *INQ message?
--
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.
midrange.com
