Re: monitor for restricted state condition

["Al Barsa" <barsa@xxxxxxxxxxxxxxxxxxx>]

You need to do it from the console.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                      vhamberg@attbi.com
                      Sent by:                  To:       
midrange-l@midrange.com
                      midrange-l-admin@m        cc:
                      idrange.com               Subject:  Re: monitor for 
restricted state condition


                      05/28/02 06:27 PM
                      Please respond to
                      midrange-l






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
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>
>
>
>
>
>                       "Dan Bale"
>                       <dbale@samsa.com>         To:
> <midrange-l@midrange.com>
>                       Sent by:                  cc:
>                       midrange-l-admin@m        Subject:  monitor for
restricted
> state condition
>                       idrange.com
>
>
>                       05/28/02 03:07 PM
>                       Please respond to
>                       midrange-l
>
>
>
>
>
>
> I'm almost certain this has been discussed before, but an archive search
> turned up nothing.  If someone has the direct link, please let me know.
>
> I am writing a CL program which will, among other things, perform ENDSBS
> *ALL.  How does one test for whether the system is in a restricted state?
>
> TIA.
>
> - Dan Bale
> (I am *NOT* "Dale"
> http://archive.midrange.com/midrange-l/200105/msg00281.html )
> SAMSA, Inc.
> 989-790-0507
> DBale@SAMSA.com
>   Quiquid latine dictum sit altum viditur.
>   (Whatever is said in Latin seems profound.)
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.