I should have mentioned that we still have SYSLBC in MSTJCL00, so our case may not the paradigm you're after. I'm still wary of what would happen with an MVS SEND/SAVE command. Just ignore the save action? Save only to userlogs that are DASD resident?
The historical problem with SYS1.BRODCAST was getting filled up with undelivered--maybe undeliverable--user-directed messages. You have solved that problem already. Is deleting SYS1.BRODCAST so important? Just asking. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Tuesday, June 21, 2016 8:55 AM To: [email protected] Subject: Re: (External):SYS1.BRODCAST I agree, however, I set USERSEND OPERSEND and SAVE to NO in IKJTSO00. We do not use the SEND command as a general rule. I still have a couple of more things to try in my sandbox, but want to avoid a falling into a major hole (if possible) before attempting these. <snip> From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson I see SYS1.BRODCAST allocated to *MASTER* on all systems in the GRSPLEX. I never tried running without it, but I'm pretty sure that's where true general broadcast messages go. Not the 'send/notify' messages to individual users, but the message(s) that everyone sees at logon time. If you think about it, where else would they go? Userlogs get migrated. An MVS SEND command could not recall them all. ...snippage I recently converted to TSO/E user logs and IPL'ed. All is working but I still have an allocation for SYS1.BRODCAST by *MASTER*. I *DID* check MSTJCL00 and the SYSLBC DD statement is not present. The only trace I can find of SYS1.BRODCAST is in the GRSRNL list. RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSDSN) RNAME(SYS1.BRODCAST) Q. Is anyone out there running *WITHOUT* a SYS1.BRODCAST dataset? If so, what is necessary to accomplish this? </snip> This email ? including attachments ? may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
