RE: monitor for restricted state condition

No, you can issue ENDSBS *ALL from any job, but doing so from any job but
the system console job will kill the job.

Al, your "loop ENDSBS until no longer get CPF1035": do you prefer this over
the QWCRSSTS API?

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of vhamberg@attbi.com
Sent: Tuesday, May 28, 2002 6:27 PM
To: midrange-l@midrange.com
Subject: Re: monitor for restricted state condition


Dumb question - does your job prevent the subsystem
you're in from shutting down, so you can't get to
restricted state? You need to run this from console,
right?
>
> Execute the command for ENDSBS *ALL *IMMED
>
> Then go into a loop, re-issuing the command every 15 seconds.  If you get
a
> CPF1035 message you are not yet down, so keep re-looping.
>
> Once you no longer get the message, you are in a restricted state.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax