On Sun, 23 Nov 2008 12:13:25 -0400, Shmuel Metz (Seymour J.) <[EMAIL PROTECTED]> wrote:
>In <[EMAIL PROTECTED]>, on 11/21/2008 > at 12:06 AM, Larry Burch <[EMAIL PROTECTED]> said: > >>That, however, was not the original point. Just how, easiest, to prevent >> NOTIFYs from being accumulated. > >A JES2 exit to fail jobs that have NOTIFY for dead user ids? Shmuel >Goleb's broadcast manager? Convert off of SYS1.BRODCAST? > >-- Have just rediscovered the BCMUSDEL function of Jim Marshall/Sam Golog's Broadcast Manager suite; it seems that I last used that function back in 2002. (Maybe I perhaps had sort of forgotten it.) It deletes a specified user-id from the broadcast dataset, along with any/all msgs for that id. I did not delete the id from RACF, so I guess if anyone issues a Sync command, the id will be in broadcast again. Our end-of-mainframe is "expected" middle of next year, and little chance of another Sync before then. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
