Thanks everyone - This must be one of those "I'm an idiot" days. I defined the TEXTMsg160 variable and did the EVAL from the variable field to the fixed field and then went ahead and typed the name of the variable length field in the PLIST definition.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam Glauser
Sent: Wednesday, February 06, 2008 1:58 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: passing an RPG variable length field to a CL as fixed length
Mike Cunningham wrote:
Shouldn't the EVAL that moves the string from the variable length
field to the fixed length field also remove the length part of the
variable length field?
The code is ...
C EVAL TEXTMsg160 = '(PCTAlerts) ' +
C %trim(TEXTMsg)
C CALL 'UTJSMSMSG' SndSmsMsg
Yes, if TEXTMsg is 'My message', TEXTMsg160 should be '(PCTAlerts) My
message' (with a bunch of trailing whitespace), as opposed to
'(PCTAlerts) xxMy message', where xx is the length of 'My message' in hex.
However, it's hard to say why your UTJSMSMSG program is not getting the
data you expect without knowing how the SndSmsMsg PLIST is defined.
--
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.
As an Amazon Associate we earn from qualifying purchases.