MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

Re: Latest CUME, Group, hyper install breaks QtmmSendMail?



fixed

Thanks for this info, Brad. I have downloaded SI53118 and will stage it
for apply the same time I apply the cume.



On Tue, Jul 29, 2014 at 11:37 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Well, this PTF fixed the problem. Whew... I hope this doesn't get too
far into the population before the fix is included in the latest CUME.

Brad
www.bvstools.com


On Tue, Jul 29, 2014 at 5:39 PM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

That's exactly the PTF that IBM is suggesting now (talking with the
customer and IBM):



http://www-912.ibm.com/systems/electronic/support/a_dir/as4ptf.nsf/ALLPTFS/SI53118




On Tue, Jul 29, 2014 at 5:26 PM, Helge Bichel <hbi@xxxxxxx> wrote:

I had another problem with the IBM mail api's resulting in a MCH1001 on
object QTMMCUTL.
IBM advised 5770TC1 SI53118, maybe it can solve your problem too.

Brgds
Helge


-----Oprindelig meddelelse-----
Fra: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] På vegne af
Bradley
Stone
Sendt: 30. juli 2014 00:11
Til: Midrange Systems Technical Discussion
Emne: Latest CUME, Group, hyper install breaks QtmmSendMail?

Just had a customer that install the latest CUME, group and hyper PTFs
on
V7R1 machine.

This appears to have broken the QtmmSendMail API. Here's the info from
the
job log:

MCH3601 Escape 40 07/29/14 17:45:57.123654
QC2POSIX
QSYS *STMT QTMMCUTL QTCP *STMT
From module . . . . . . . . :
QC2PFMO
From procedure . . . . . . : _C
PSX
dofmto
Statement . . . . . . . . . : 82
To module . . . . . . . . . :
QTMMFILE
To procedure . . . . . . . :
FileLinkWithTempName__FPcN21PPc
Statement . . . . . . . . . : 74
*PRCLT
Message . . . . : Pointer not set
for location referenced.
Cause . . . . . : A pointer was
used, either directly or as a basing
pointer, that has not been set to
an
address.
CEE9901 Escape 30 07/29/14 17:45:57.124062
QLEAWI
QSYS *STMT F.MAILTOOL MAILTOOL *STMT
From module . . . . . . . . :
QLEDEH
From procedure . . . . . . : Q
LE
leDefaultEh2
Statement . . . . . . . . . : 175
To module . . . . . . . . . :
F.MAILTOOL
To procedure . . . . . . . :
#MAILTOOL_SENDMAIL
Statement . . . . . . . . . :
1468
Message . . . . : Application
error.
MCH3601 unmonitored by QC2POSIX at
statement 0000000082, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled.
The
name of the program to which the
unhandled exception is sent is
QC2POSIX QC2PFMO _C PSX dofmto. The program
was stopped at the high-level
language statement number(s) 0000000082 at the
time the message was sent. If
more
than one statement number is shown, the
program is an optimized ILE
program.
Optimization does not allow a single
statement number to be
determined.
If *N is shown as a value, it means the
real value was not available.
Recovery . . . : See the low level messages
previously listed to locate the
cause
of the exception. Correct any errors,
and then try the request again.

The first part is the error, the second one is my application catching
the
error. I've traced it from the line number to the call to the
QtmmSendMail
API.

Now, keep in mind this is running on many many machines, and this is the
first one to have this issue. And it's after the install of the latest
PTFs. This is running on machines from V4xxx to V7xxx without issue
(except
this machine of course). And has run for over 10 years. :)

Just wondering if anyone else has seen anything like this. My guess is
it's
a boo boo on IBM's part, and I have a feeling that if it breaks
QtmmSendMail
it will be a huge deal for those applying the latest PTFs.

I'm going to have this customer move to using MAILTOOL Plus to bypass
IBM's
SMTP server for now, but this is very discouraging.

Brad
www.bvstools.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: 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.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact