RE: QZDASOINIT impact -- MIDRANGE-L

× 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.

Subject: RE: QZDASOINIT impact
From: "Urbanek, Marty" <Marty_Urbanek@xxxxxxxxxxxx>
Date: Tue, 29 Mar 2005 09:33:07 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Bryan,

Where do you do this in Ops Nav? This could be very useful?

Thanks,
-Marty

------------------------------

date: Tue, 29 Mar 2005 07:38:51 -0500
from: Bryan Dietz <BDietz@xxxxxxxxxx>
subject: RE: QZDASOINIT impact

You isolate the QZDASOINIT jobs into their own subsystem.  You can also go
so far as to isolate only those jobs from specific IP addresses.  You have
to use Ops Navigator to config this, but it works great.



----------------------------
Bryan Dietz
Aktion Associates

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.