If Broadcast was filled, wouldn't the "SE 'hh.mm.ss Jesjobid
$HASP165...'..." message still be issued? Check SYSLOG.
Could it be possible that an exit or vendor product is removing the NOTIFY=?
Could the message be sent to an identical userid on another LPAR? I logon
with the same userid to multiple systems and quite often the NOTIFY message
is sent to another LPAR.
DanD
-----Original Message-----
From: Ed Gould
Sent: Wednesday, September 29, 2010 3:59 PM Subject: Re: JES2 $HASP165
(Notify) not seen
There could be several issues at play here.1. Brodcast is filled up. You may
need to do a sync (subcommand of account)2. If Broadcast is really filled
up and the above doesn't work you may need to do a scratch and reallocate
(IPL may be needed).3. There are some broadcast utilities on the CBT tape
that might help you clean broadcast up. Hey its free and it works and
probably no need to IPL.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
