Or you can try just reformating ans syncronizing the current broadcast dataset first:
//IKJEFT EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=A //SYSUADN DD DSN=SYS1.UADS,DISP=SHR //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //SYSLBC DD DSN=SYS1.BRODCAST,DISP=SHR //SYSTSIN DD * UADSREFM SYNC BOTH END /* 2008/8/5 Angel Tamayo <[EMAIL PROTECTED]> > Recently I had a similar situation but the problem was that my default > SYS1.BRODCAST dataset was damaged and I had to redefine and reformat it. If > this is your case you should receiving messages as this after your job > finish and user is logof from TSO: > IKJ144I > IKJ574I > > To solve this problem I did next steps: > > - DEFINE NEW BROADCAST DATASET//ALLOC EXEC > PGM=IEFBR14 > //NEWFILE DD DISP=(NEW,CATLG),DSN=SYS1.BRODCAST.NEW, > // UNIT=3390,VOL=SER=volser, > // SPACE=(CYL,40),DCB=SYS1.BRODCAST > - FORMAT AND SYNCRONIZE BROADCAST AND UADS DATASETS > //IKJEFT EXEC PGM=IKJEFT01 > //SYSTSPRT DD SYSOUT=A > //SYSUADN DD DSN=SYS1.UADS,DISP=SHR > //SYSUADS DD DSN=SYS1.UADS,DISP=SHR > //SYSLBC DD DSN=SYS1.BRODCAST.NEW,DISP=SHR > //SYSTSIN DD * > UADSREFM > SYNC BOTH > END > /* > - COPY SYS1.PARMLIB(IKJTSO00) TO SYS1.PARMLIB(IKJTSO01) > - MODIFY SYS1.PARMLIB(IKJTSO01): > LOGNAME(SYS1.BRODCAST.NEW) > BROADCAST(DATASET(SYS1.BRODCAST.NEW) > - SWITCH TO IKJTSO01 -> SET IKJTSO=01 > - VERIFY CHANGES AND ENTER Y NEXT MESSAGE > *IKJ732I REQUEST TO SWITCH BROADCAST DATA SET DETECTED WHILE 819 > PROCESSING PARMLIB MEMBER IKJTSO07. CONFIRM THE SWITCH > FROM SYS1.BRODCAST ON VOLUME volser > TO SYS1.BRODCAST.NEW ON VOLUME volser. > *11 IKJ733A REPLY YES TO SWITCH, NO TO CANCEL PROCESSING OF THIS > PARMLIB MEMBER. > > To keep the original dataset name you can use the last 3 steps. > > Angel > > 2008/8/5 Lizette Koehler <[EMAIL PROTECTED]> > > Is this system setup for individual Broadcast data sets or do they all >> Default to SYS1.Brodcast? >> >> Do all jobs "send" completion messages or do some users not submit with >> USER= in the jobcard? >> >> Are the users able to logon to more than one system? >> >> Is this a sysplex or a shared MAS with multiple LPARS? >> >> Is the configuration such that it is (Broadcast, Sysplex, etc...) so that >> all users would normally receive their SEND messages and you have a select >> group that is not receiving messages? >> >> >> I am not sure why the users would not receive their SEND messages from >> batch >> jobs when they are logged off. >> >> Maybe someone else has an idea. >> >> >> Lizette >> >> >> > >> > Thanks again for the info, Lizette. >> > >> > Actually, the problem I am trying to address here is that users on this >> > particular system do net get messages about the jobs that have >> > completed >> > while they were logged off. For this I need to set the option to MAIL >> > (instead of NOMAIL). Since, the users here don't get a full screen >> > logon >> > panel, I can't have them enable/disable the NOMAIL option. >> > >> > I have further found out that this client uses a TSO logon pre-prompt >> > exit >> > and it looks like the MAIL option is not being set (the default is OFF) >> > in >> > the exit. >> > >> > Hence, I believe my only option would be to either modify the exit or >> > to >> > include a TSO LISTBC command in the logon proc such that it would be >> > executed automatically when the user logs on. >> > >> >> ---------------------------------------------------------------------- >> 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 >> >> > ---------------------------------------------------------------------- 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
