Gil Not to delete the dataset, but to empty the dataset.
If you want to expand it, I would create a new one, put it in the MSTJCL00 and IPL. Then Delete the old one, Allocate a new one with the original name (if desired) and then IPL again. I have not heard of any issues with multiple logons and the individual brodcast datasets. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf > Of Paul Gilmartin > Sent: Wednesday, January 02, 2013 9:39 AM > To: [email protected] > Subject: Re: IKJ574I NO SPACE IN BROADCAST DATA SET FOR MAIL > > On Wed, 2 Jan 2013 09:10:27 -0700, Lizette Koehler wrote: > > >Do you have DISP=OLD or DISP=SHR in MSTJCL00? For Brodcast. > > > >If SHR, then you can manually delete the dataset. > > > ??? How? Even if it's allocated SHR, you need to ENQ EXC to delete it. > Unless you zap > the VTOC. (Ugh.) > > >I would recommend that you go to individual TSO Broadcast data sets. > >It reduces this type of issue. > > > >Only impact is lost notifications to TSO users on jobs ending or SEND > >messages (I think) > > > Would this be an impediment to hacks or possible future enhancements that > might > allow concurrent logons? (Is the individual BCDS temp DSN or catalogued?) > > >The CBT software can delete your messages on the fly. There should be > >an ISPF Panel that will provide a table to delete any or all messages. > > > >But you definitely need to empty SYS1.BRODCAST. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
