On Thu, Jun 29, 2017 at 1:34 PM, Jesse 1 Robinson <[email protected]> wrote:
I get a few of these. From jobs which are submitted by CA-7 and whose JCL has NOTIFY=&SYSUID I had two reasons for suppressing superfluous NOTIFY attempts. > > -- Several junk messages in syslog each time about trying to find the user > log, failing, and discarding the message. Over and over for the same > handful of userids hard-coded into countless jobs. > > -- Some obvious though probably trivial overhead of checking for a data > set that does not now and most likely never will exist. > > I did not want to substitute my own overhead. (Note that RACF would not > know whether the user log exists; only the catalog.) > > So I just built a small table of known problem userids. Scan the table. If > it matches, put out one line of doc. All without the rigmarole of trying to > change maybe thousands of job streams that have been around for decades. > > $HASP954 Exit 16 suppressed NOTIFY for xxxxxxx > > . > . > 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] > > -- Veni, Vidi, VISA: I came, I saw, I did a little shopping. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
