×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Is SNADS running on the system that is 98%? Most likely not. There are
internal communication buffers that are not directly accessible. What
has happened, most likely, Source system has sent, via ANYNET, the save
file to the destination system. SNADS was not running on the
destination system so they do not show up under WRKNETF *ALL. Because
you are now over the threshold, SNADS will not run so the files are not
copied from the communication buffers to the WRKNETF queues. The queues
you see with WRKDSTQ are the sending queues, not those pesky hidden
receive queues. (These are used for receiving files and restarting
after failed communications.)
Change your threshold to almost nil or get your disk below 90%. Once a
file is received, that is copied from internal queue to WRKNETF queue,
you may run above your threshold again.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
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.
midrange.com
