Good catch on the message number. If I ever open that code again, I'll change it to the designated range. I have not had to update the userid table in years.
The exit's main virtue is the very short path length as opposed to the incessant attempt to locate a nonexistent user log. I put out the message just so people--including me--don't waste time looking for an expected notify. Since I implemented this code, not one person ever called to question it. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: Friday, June 30, 2017 3:31 AM To: [email protected] Subject: (External):Re: JES2 Exit 16 (was Re: how to keep messages in the sys1.broadcast for ever) Jesse 1 Robinson wrote: >So I just built a small table of known problem userids. Scan the table. If it >matches, put out one line of doc. Ok, just a little table lookup and be finished. Thats Quick and Dirty. The way I like it. > $HASP954 Exit 16 suppressed NOTIFY for xxxxxxx Groan, had to look it up just to discover this is not used by JES2, but for customer's use... ;-D Actually that reference is for 900-949, but yes, the rest of 9??? messages are also for customers too, actually they're listed as 'sample installation exit messages' with the usual caution of conflicting message headers. Thanks for you reply. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
