Re: Status ot communications during restricted state

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