This does require a JES2 exit to be implemented. I actually had done this too many years ago to remember.
Unfortunately, I do not remember which exit it was, but I seem to remember I got the base code either from an old Redbook on JES2 or from the Share or JES2 mods tape. Thanks Bill Bishop Specialist Mainframe Support Group Server Development & Support Toyota Motor Engineering & Manufacturing North America, Inc. bill.bis...@tema.toyota.com (502) 570-6143 -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc Sent: Tuesday, May 12, 2015 1:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Notify for XMIT On 12 May 2015 at 10:57, Steve Thompson <ste...@copper.net> wrote: > It seems to me, from years gone by, that if someone were to message me > via TSO XMIT, that the next time I caused an interrupt (AID key of any > kind), I would get notification that I needed to do a RECEIVE. I just sent a dataset from one system to another. When I hit enter on the receiving system, I got: $HASP549 MAIL FROM(nodename/userid) RECORDS(656) CN(INTERNAL) I have a vague memory that a JES2 exit needs to be configured to do this, but like many such memories these days, it's very vague. Nonetheless it seems to do what you want and remember on our systems here. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
