Re: ENDSBS *ALL in a batch job

Help me with this thought process...

First, when QUPSDLYTIM kicks in, does it do
- PWRDWNSYS *CNTRLD DELAY(...), which, after the delay kicks in, converts
to *IMMED.
- PWRDWNSYS *IMMED
- some unique process?

I am thinking that if I have a job stuck that requires ENDJOBABN to kill
it that the following: ENDSBS, ENDSYS, PWRDWNSYS are all held up until
that job is killed with ENDJOBABN.
Since my previous ENDSBS *ALL *CNTRLD DELAY(120) has already went past
it's DELAY(120) and converted itself to *IMMED and still didn't die; that
I've already killed everything that's going to go down 'normally'. All
that should be left is:
- The controlling subsystem with no jobs but the UPS job.
- The subsystem containing the job needing ENDJOBABN. With the only job
in that subsystem being that job needing ENDJOBABN.
- The actual job needing ENDJOBABN.
Since running ENDJOBABN automatically flags your next IPL as abnormal why
should I take the effort to list out all jobs, and run ENDJOBABN on any
non subsystem job left? Again, all that should be left are one or two
subsystem jobs and the job needing ENDJOBABN. That job is going to go
down hard either way.

However, if there isn't some unique process down by QUPSDLYTIM, and it
requires some iteration of PWRDWNSYS to run (internal or otherwise) then a
hard slam may not flush cache? Or does PWRDWNSYS not really flush cache
anyway?
In that case then perhaps I should do the job listing thing.



Rob Berendt