× 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.


  1.  Home
  2. MIDRANGE-L
  3. August 2018

RE: SMTPR4 and SIGALRM

The send will sit there forever. That is why you have to have the
timeout and the alarm. The alarm should only be killing the send.
Nothing else. The code that you are showing looks to me to be inside the
sendtext function in smtpr4. At least in my case, that gets called one
of two ways. Either all wrapped up in SMTPSend mail, or as individual
calls to the various pieces of an SMTP transaction. If you are calling
sendtext() directly, then it is up to you to deal with getting the
errors and handling them.

Either
hsmtp = SMTP_new('mail.i-55.com');

if ( SMTP_connect(hsmtp) = FAIL );
ErrMsg = SMTP_error();
// Error handling goes here.
endif;

if ( SMTP_from(hsmtp: 'blah.blah@xxxxxxxxx') = FAIL );
ErrMsg = SMTP_error();
// Error handling goes here.
endif;

Or
SMTPSendMail( FileName
: %len(FileName)
: fromAddr
: %len(fromAddr)
: recip
: %elem(recip)
: NullError );
// Check nullerror for errors.


The unix api documentation on the IBM site is very barebones, but to be
fair, I have the Stevens book on unix network programming and it is over
1000 pages and that is only volume 1. Scott's wrapper hides all of that
complexity from you, so that you should just have to make the calls to
his high level routines and check for errors that he returns.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Don Brown
Sent: Sunday, August 19, 2018 5:25 PM
To: Midrange Systems Technical Discussion
Subject: RE: SMTPR4 and SIGALRM


Kevin you will notice in the code snippet I sent that the time out is
being
received on the

slen = send(SMTP.sock: %addr(buf): len: 0);

So the problem I have is not checking the error data structures, the
problem
is that the alarm time out has been set and the send times out and the
SIGAMRM is sent that kills the job.

Will the send(...) wait indefinitely ? and that is why the alarm is
used to kill
the job if that occurs ?

If I increase the time out will the send(...) eventually fail so i can
check the
error data structure ?

The documentation in the knowledge centre is not, in my opinion, very
easy
to understand.

Thanks you for your reply.


Don Brown






From: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 17/08/2018 10:13 PM
Subject: RE: SMTPR4 and SIGALRM
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I has been a while since I played with that, but I don't think you can
avoid
having that job canceled. What does the send look like? Are you doing
the
individual calls, or using one of the wrappers that does all the calls
for you?
Both ways have error reporting. SMTPSendMail or SMTP_Sendmail both
have an error data structure that you need to check.
If you are doing individual calls like SMTP_connect, SMTP_from, etc,
you
need to check the return from SMTP_error.





Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On
Behalf Of
Don Brown
Sent: Thursday, August 16, 2018 11:11 PM
To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
Subject: SMTPR4 and SIGALRM



We are using SK's SMTPR4 to send emails.

We have a payment process that charges credit cards via an external
payment gateway and sends an email with the transaction result.

The problem we have is occasionally the job will be cancelled with
CPC1224 as
per following ...

CPC1224 Completion 50 06/08/18 08:17:38.219994
QWTPITP2
QSYS 0645 *EXT *N
Thread . . . . : 00000001
Message . . . . : Job ended
abnormally.
Cause . . . . . : A SIGALRM
signal
was received for the job. The action for
the signal was to terminate
the
job.


I have tracked this back to the SMTPR4 service program that does the
following;

/free
DebugMsg(text);
len = e2a(SMTP: text: buf: %size(buf));
alarm(SMTP.timeout);
slen = send(SMTP.sock: %addr(buf): len: 0);
alarm(0);
if (slen < len);
SetUnixError( SMTP_ERR_SEND: 'send()' );
return *OFF;
endif;
return *ON;
/end-free

So my understanding is the alarm(...) is setting the timeout to 60
seconds.

The send(...) must be failing causing a delay of 60 seconds or more
which
causes the alarm to be signaled/processed. I presume the signalling
was
used as the send(...) would wait indefinitely ?

The the job is then cancelled which leaves the payment process
incomplete.

I have not been able to identify why the email server is not
responding and
while increasing the timeout could be done I don't think that is the
best
option.

As the SIGALRM is external to the job how can I detect failure of
the
email to
send but not have the entire job cancelled ?

Appreciate any assistance or suggestions.

Would also appreciate any links to signalling for dummies or similar
so I can
bet a better understanding of what and how they work.

Thanks

Don Brown


--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

__________________________________________________________
____________
This email has been scanned by the Symantec Email Security.cloud
service.
For more information please visit http://www.symanteccloud.com
__________________________________________________________
____________

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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.