Re: Can I prevent RCYCNL status by forcing the *LIN to VARY *OFF?

[Pete Hall <pbhall@xxxxxxxxxx>]

At 16:40 05/25/2001, Gerald Kern wrote:

>Is there a way to prevent a BSC *LIND from going into RCYCNL? Or, should I
>say, is it possible to configure the line so that if it goes into RCYCNL
>that it can be automatically varied off? I'm a communications novice so I
>may not have provided enough detail to get a usable reply. What I'm trying
>to accomplish is to determine if I can change the configuration on a BSC
>line so that if it were to go to RCYCNL, I'd prefer it to simply vary itself
>off.

If nobody else has any better ideas, what I used to do back in the stone 
age was submit a job when I started the communication process, which would 
wake up periodically and check the status of the line. If the status wasn't 
satisfactory, it would reset the line/device. At least at that time, there 
didn't seem to be any way of getting the communication process to manage 
itself, but the monitor job didn't have to do much, so the overhead was 
minimal.
Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---