When you get 'terminated at end of memory', all bets are off. This generally happens when the address space has run out of storage to the point that recovery routines cannot run. No recovery, no message processing, no preservation of sysout, etc. Your MPF entries indicate user exit processing. Probably not going to happen.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Brad Wissink Sent: Friday, September 18, 2015 2:05 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: MPF message processing not started for msg I have a batch job that abended with the following messages . N C000000 H50A 2015260 17:03:16.08 J0684125 00000000 $HASP310 U0051299 TERMINATED AT END OF MEMORY M 4000000 H50A 2015260 17:03:16.25 00000000 IEF402I U0051299 FAILED IN ADDRESS SPACE 0058 892 E 892 00000000 SYSTEM ABEND S04F - REASON CODE F30901 I have two MPF message exits defined for one for each message. /* $HASP310 - JOBNAME TERMINATED AT END OF MEMORY */ $HASP310,SUP(NO),USEREXIT(SY159) /* IEF402I - JOBNAME FAILED IN ADDRESS SPACE SYSTEM ABEND SXXX */ IEF402I,SUP(NO),USEREXIT(SY147) I did a 'D MPF' to make sure the exits were defined and active. Does anyone have an idea on why the exits were not called? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
