× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I tried other methods of sending *INQ messages, but they're still limited to 132 characters. I guess that means the limitation is in an underlying API rather than the command itself.


Jeff, I think you're work-around will get me where I need to go. So far, no one else has even discovered the 132 character limit, so I'll probably just condition this "fix" on my user ID. That way I'll get what I need and no one else will be inconvenienced.

Thanks




-----Original Message-----
From: Jeff Bull [mailto:jeff.nyco@xxxxxxx]
Sent: Thursday, September 25, 2014 9:43 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SNDUSRMSG need reply longer than 132 characters

"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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.