|
This was the fix that I had to apply for a problem with Intrusion Detection
on the IBM i. Intrusion Detection can send a notification email when a
potential event is found. After applying the CUME package, I stopped
receiving those email notifications.
Because Intrusion Detection uses QSYSARB to send the email messages, to
restart the job so it would use the PTF fix, I had to IPL the system.
This error had far reaching consequences.
Jim Essinger
Western Power Sports
Boise ID
On Wed, Jul 30, 2014 at 6:37 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:
Thanks for this info, Brad. I have downloaded SI53118 and will stage itwrote:
for apply the same time I apply the cume.
On Tue, Jul 29, 2014 at 11:37 PM, Bradley Stone <bvstone@xxxxxxxxx>
too
Well, this PTF fixed the problem. Whew... I hope this doesn't get
http://www-912.ibm.com/systems/electronic/support/a_dir/as4ptf.nsf/ALLPTFS/SI53118far into the population before the fix is included in the latest CUME.wrote:
Brad
www.bvstools.com
On Tue, Jul 29, 2014 at 5:39 PM, Bradley Stone <bvstone@xxxxxxxxx>
That's exactly the PTF that IBM is suggesting now (talking with the
customer and IBM):
afon
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
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
PTFsBradley
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
wasonfrom
V7R1 machine.
This appears to have broken the QtmmSendMail API. Here's the info
_Cthe
job log:
MCH3601 Escape 40 07/29/14 17:45:57.123654
QC2POSIX
QSYS *STMT QTMMCUTL QTCP *STMT
From module . . . . . . . . :
QC2PFMO
From procedure . . . . . . :
82PSX
dofmto
Statement . . . . . . . . . :
74To module . . . . . . . . . :
QTMMFILE
To procedure . . . . . . . :
FileLinkWithTempName__FPcN21PPc
Statement . . . . . . . . . :
set*PRCLT
Message . . . . : Pointer not
for location referenced.
Cause . . . . . : A pointer
setused, either directly or as a basing
pointer, that has not been
toQ
QLEAWIan
address.
CEE9901 Escape 30 07/29/14 17:45:57.124062
QSYS *STMT F.MAILTOOL MAILTOOL *STMT
From module . . . . . . . . :
QLEDEH
From procedure . . . . . . :
isLE175
leDefaultEh2
Statement . . . . . . . . . :
instruction1468To module . . . . . . . . . :
F.MAILTOOL
To procedure . . . . . . . :
#MAILTOOL_SENDMAIL
Statement . . . . . . . . . :
Message . . . . : Application
error.
MCH3601 unmonitored by QC2POSIX at
statement 0000000082,
applicationX'0000'.
Cause . . . . . : The
Theended abnormally because an exception
occurred and was not handled.
name of the program to which the
unhandled exception is sent
IfQC2POSIX QC2PFMO _C PSX dofmto. The program
was stopped at the high-level
language statement number(s) 0000000082 at the
time the message was sent.
themore
determined.than one statement number is shown, the
program is an optimized ILE
program.
Optimization does not allow a single
statement number to be
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
again.cause
of the exception. Correct any errors,
and then try the request
catching
The first part is the error, the second one is my application
bypassthethe
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
latestfirst one to have this issue. And it's after the install of the
isPTFs. 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
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
mailingIBM's
SMTP server for now, but this is very discouraging.
Brad
www.bvstools.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailingtake alist
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
http://archive.midrange.com/midrange-lmoment to review the archives at
.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
listlist--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
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.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.