Hello Brian,
$PXEQ and then $SXEQ... this will tag all active WLM initiators and shut
each one down when it's batch has completed. The $SXEQ will allow new work
to start in new WLM inits.
Seems like I said that earlier this weekdeja vu?
Regards
Bruce Hewson
Thanks all.
The $PXEQ and $SXEQ suggestions have sorted the problem of the residual state
data in the WLM initiators.
The problem seems to have been caused because job(s) that abended were using
PDSEs. This uses DIV apparently, and some control blocks got left behind in the
initiator I guess.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Perryman, Brian
[ snip ]
Sorry for not responding sooner, I'd left the office (now
10:30pm here in The 51st State).
You're in Iraq??
-jc-
SNIP
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of Chase, John
You're in Iraq??
UNSNIP
With Blair in charge, it feels like it - similar infrastructure, but without
the sunshine..
This e-mail message is for the sole use of the intended recipient(s)and may
contain
Thanks John,
That may be in the right area, we did indeed have a lot of jobs die overnight
with tape timeouts and IOS errors/abends, and also some operator cancels.
However we're WLM goal mode and don't use initiators as such. I've been
watching the BPXAS tasks and they have cleared down to
This is weird.
We have WLM-managed initiators on and all JES initiators are normally drained.
WLM service classes are assigned according to the userid of the submitted batch
job.
If I submit a batch job with a development userid, which gets a development
service class and a WLM-managed
On Wed, 1 Jun 2005 16:57:07 +0100, Perryman, Brian [EMAIL PROTECTED]
wrote:
This is weird.
We have WLM-managed initiators on and all JES initiators are normally
drained. WLM service classes are assigned according to the userid of the
submitted batch job.
If I submit a batch job with a
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 06/01/2005
11:57:07 AM:
We have WLM-managed initiators on and all JES initiators are
normally drained. WLM service classes are assigned according to the
userid of the submitted batch job.
If I submit a batch job with a
If the virtual tape product Brian originally mentioned is CA:VTAPE, it is a
*heavy* user of DIV.
Bob
Jim Mulder wrote:
I would start with
SLIP SET,A=SVCD,ML=1,C=A78,RE=1C,ID=DA78,END
Does the job in question use DIV? If not, maybe some DIV
infrastucture somehow was not cleaned up by
SNIP__
* through termination.*
* RECOMMENDATION: *
Repeated
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 06/01/2005
04:44:38 PM:
SNIP__
* through termination.*
* RECOMMENDATION:
Ed -
I believe that FINREVERSAL is used when an APAR closes FIN but then one or
most customers requests that it be fixed in the current release and IBM
agrees to do that. IBM documents this by opening a new APAR and marking
it as a FINREVERSAL of the old APAR.
Larre Shiller
US Social Security
12 matches
Mail list logo
