|
I've been trying to get this going as well. *IF* what I understand is correct, the message itself has to be a properly formatted Stream file in the IFS. In my mind that means I need to develop the stream file, in my case on the fly to incorporate dynamic content. Given this scenario, it is simple enough to include a carraige return by writing x'0D25' to the Stream File. If this is not the way this API works I would appreciate someone letting me know, I've been spinning my wheels a little. My biggest problem right now is that the example I found uses the following /copy for the API data structure error call: * copy error structure from QSYSINC /copy qsysinc/qrpglesrc,qusec d Qdata 17 216 * set pointer to Error structure d pErr s * Inz(%addr(QUSEC)) I get an error because it cannot find the /copy, and I haven't been able to find the DS description at the API website Search for QtmmSendMail here: http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/apis/apifinder.htm I got my project done by reverting to SNDDST for the time being, but eventually I would like to get this working. Joel http://www.rpgnext.com On Tue, 2003-10-28 at 14:40, Malchow, Grizzly wrote: > I'm using the QtmmSendMail API to send emails. Is there a way to put a > carriage return into the message so the formatting looks a little > better? Could I use HTML tags? > > _______________________________________________ > 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 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.