RE: QtmmSendMail - broke now we are on V5R3...

This is the direction we are going this morning...
We are taking the jobs that use this api and converting
Them to use the spltool and mailtool commands.  We have quite
A mix of applications sending mail here....
SNDDST, spltool/mailtool, QTMMSENDMAIL, a standalone fax/mail server
That reads spool files, COMPLEO.....

Those programs that use spltool/mailtool are working.... (thanks
Brad...)



The bad news for me is that I am the one who was championing the use
Of the sendmail api, because if the ability to quickly wrapper data in 
A mime packet, send to many recipients, attach many documents...




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brad Stone
Sent: Monday, July 25, 2005 9:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: QtmmSendMail - broke now we are on V5R3...

I have two options (and haven't ran into your issue yet).

My MAILTOOL utility (in it's standard form) uses the
QtmmSendMail API.  It's been through the ringer with
thousands of installs over the past few years.  so most
errors like this have been caught.

I also have an "addon" to MAILTOOL called MAILTOOL Plus!
which totally bypasses the IBM STMP server and this
infamous API (I also quicky grew unfond of the API, but
even more so of the IBM SMTP server).  It sends the mails
with it's own API, logs errors, allows resends, etc.  Much
more useful (and better support!  LOL!)

Combined with SPLTOOL and you've got emailing spooled files
in one command with or without the IBM SMTP server...
whichever you choose.  Add AFPTOOL and you can also email
AFPDS spooled files in one command.

www.bvstools.com is where you'll find these goodies.

I use these tools daily myself so it's also in my best
interest to support them. :)

Brad
www.bvstools.com

On Mon, 25 Jul 2005 17:08:11 -0500
 "Gerald Magnuson" <gmagnuson@xxxxxxxxxxxxx> wrote:
> We do have a product from symtrax called compleo which
> Takes normal old spool files and mails them. 
> 
> We went to this api because we had trouble at times with
> The SNDDST command...   (besides trying to get away from
> SNADS)...
> 
> Now I have burned a whole day, have had about 100 emails
> with
> Important data not sent, and I still don't know what
> direction
> To fix this problem...
> 
> Should I go back to SNDDST?   
> Should I try to find a new method to implement the
> SendMail api?
> Should I change the processes that output to a flat file
> for mime
> processing
> back to spool files and use either spltool or compleo?
> 
> 
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> pnelson@xxxxxxxxxx
> Sent: Monday, July 25, 2005 4:52 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: QtmmSendMail - broke now we are on V5R3...
> 
> Sounds like a lot of maintenance work. Have you checked
> out what you can
> 
> do with SEQUEL/Viewpoint? Emailing stuff is built in.
> -- 
> 
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978  Cell
> pnelson@xxxxxxxxxx
> 
> 
> 
> 
> 
> "Gerald Magnuson" <gmagnuson@xxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 07/25/2005 04:45 PM
> Please respond to Midrange Systems Technical Discussion
>  
>         To:     "Midrange Systems Technical Discussion" 
> <midrange-l@xxxxxxxxxxxx>
>         cc: 
>         Subject:        RE: QtmmSendMail - broke now we
> are on V5R3...
> 
> 
> Correctly trim???
> 
> How in the world could this process work before when we
> were on
> V5R1?????
> 
> 
> Looks like I will have to start at ground zero with these
> programs.
> We have about 15 to 20 report programs that send output
> via email
> That uses this process.....
> 
> I am not familiar with the iconv api...
> 
> I take it you do the whole process in one program...
> Create MIME file, Send to IFS, Send MIME to SendMail
> api???
> 
> We have a program to create a database file with mime
> headers and then
> The data, another program then send to the IFS with the
> CPYTOSTMF
> command, and then another program to process the SendMail
> api...
> 
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Scott Klement
> Sent: Monday, July 25, 2005 4:30 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: QtmmSendMail - broke now we are on V5R3...
> 
> 
> > I see the ccsid's of our files are 1252 (for the most
> part)...
> > I see that I can set them on the CPYTOSTMF command....
> > (it still doesn't work though....)
> 
> CPYTOSTMF?!  Hmmm.. I never thought of using that. Does
> it correctly
> trim 
> off the trailing blanks from each of the records you're
> copying from?
> 
> >
> > How do I set the ccsid of the Parms???
> >
> 
> I translate mine using the iconv() API.
> 
> 
> -- 
> 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.
> 
> 
> -- 
> 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.
> 
> 
> -- 
> 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.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com