Hi Warner,
You forgot to mention that this will clear out ALL messages in the Brodcast
dataset. This could be bad, especially if you have something like we had at
P&H Mining. We had a home grown PR system that automatically notified the
person who was the recipient of a problem report. Also, when jobs end that
you submit, you would never get the notify. That could also be a problem.
Also, all the messages from the Clists where you could send a turkey or
something to your fellow worker would be destroyed.
I used to use a program that listed the number of messages for each user
that was in the Brodcast dataset. I would run that every month or 2. We
had some IDs that got messages, but never logged on. The CBT programs
mentioned in a previous post worked great. I used one that displayed all of
the messages to my terminal and deleted them off of the Brodcast dataset.
That way, if there was something usefull, you could screen print it and make
sure you got that info to the right person.
Eric Bielefeld
Sr. z/OS Systems Programmer
Milwaukee, Wisconsin
414-475-7434
----- Original Message -----
From: "Warner Mach" <[EMAIL PROTECTED]>
Just a thought. If more than one user is getting this message
you might try running the following job (We have this job
scheduled to run on a regular basis to avoid 'no space in
brodcast data set' message):
//UPDATE EXEC PGM=IKJEFT01
//SYSUADS DD DSN=SYS1.UADS,DISP=SHR
//SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
ACCOUNT
SYNC
END
/*
----------------------------------------------------------------------
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
