× 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 didn't put that code out here, but mentioned it. I have a command already
on the RPG.

I have a command call an RPG program wrapper for a subprocedure.


On 6/19/07, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:

Hi Mike,

> I know about the issue of passing long text fields from one program to
> another but I didn't think it would be a problem from a program to a
> subprocedure. I have a command call an RPG program wrapper for a
> subprocedure.

It's not a problem from a program to a subprocedure. You have an
*ENTRY PLIST in your program -- I'm pretty sure that the garbage
characters are entering your program from that *ENTRY PLIST. They're
being passed along to the subprocedure because they're already in the
variables.

Make a command front-end for your program that declares fromAddress,
toAddress, ccAddress, bccAddress, subject and body to be the correct
lengths, and call the program through that command.

Welcome to FAQ land.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.