Re: Status ot communications during restricted state

----- Original Message -----
From: rob@xxxxxxxxx
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Re: Status ot communications during restricted state
Date: Tue, 12 May 2009 14:09:00 -0400


And what's even worse is when you use the wrong severity state and your
system goes into a break message during a full system save, or reclaim
storage 5 minutes after you leave the room and before you come back after
a long dinner, etc.

Vary the lines off. Good habit to get into. Especially if you ever get
anything in WRKNWSD which really should be varied off before a full system
save.

Now, if you have a messaging product that claims to work in a restricted
state to alert your cell phone or pager if the save goes into a MSGW or
completes then see the products instructions about what lines (like the
lan) they want you to leave alone.



Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
CRPence <CRPbottle@xxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
05/12/2009 02:00 PM
Subject:
Re: Status ot communications during restricted state
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Albert York wrote:

I need to make sure that any communication lines (like SDLC
lines) are inactive when the system is in a restricted state,
even if the lines are not varied off. I'm assuming this is
the case because there are no active subsystems but can
anyone verify this?

Restricted state will prevent a new user jobs being initiated on
the communications line; i.e. they are effectively /inactive/.
However unless the lines are varied off, those lines still consume
memory and other system resources because the line is still being
serviced by the /system jobs/ which are not ended while in
restricted state. Those system jobs will continue reacting to all
incoming requests, however only to give negative response codes to
whoever is attempting to initiate communication to the i.

An obvious and irritating side effect is the list of messages
logged in QHST while in restricted state; recording all of those
failed attempts of, for example, a PC in a retry\repeat coded loop
to initiate contact to a system which is not responding [due to its
being in restricted state]. If the lines are varied off, the PC
gets no response and there is no logging of the incident to clutter
the log which ideally would be limited only to what maintenance was
being performed while in restricted state.

Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.