ChadB wrote:
I have seen those types of 'trickle' comm messages during
restricted state for many years on many versions. They
always make me wonder how they get through... <<SNIP>>
The communications activity is done in "system jobs" [SYS jobs] which
remain active irrespective of the /restricted state/ status. The ENDSYS
& ENDSBS *ALL requests will end all "subsystem [monitor] jobs" [SBS
jobs] and all jobs within each subsystem, except the console job in the
controlling subsystem.
To prevent communications activity from taking memory and CPU during
a system backup [or reclaim, or other /dedicated/ activity, vary off all
communication resources\lines [an exception would be what resource the
console requires to communicate]. Increasing the history log size and
holding all access path rebuilds would be other activity to precede such
activities to ensure the best of /dedicated/ operations.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.