Re: Re[4]: SYSTOOLS.SPOOLED_FILE

Subject: Re: Re[4]: SYSTOOLS.SPOOLED_FILE_DATA
From: Rob Berendt <robertowenberendt@xxxxxxxxx>
Date: Mon, 7 Oct 2024 13:02:54 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

<snip>
Until we know the customer and the applications very well, suggesting a
change like that can really cause issues. While Rob is correct that
many have changed that system value mid-day and not looked back, I've
also see havoc raised where the business is down while the issues are
fixed.
</snip>
And this worst case scenario will be the sole point of focus on the "Better
the devil you know than the devil you don't." crowd.

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.

Re: Re[4]: SYSTOOLS.SPOOLED_FILE_DATA