Re: PWRDWNSYS -- 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.

a question I have is:
why, when you do a PWRDWNSYS, would you EVER really want cache data left behind?
I would think that the 99% choice would be to flush the cache.
When I IPL my system, it is after a ton of unrelated batch processing, and a full system save. what is in the cache will be no real help when I restart my machine for normal business operations.

On 1/17/2013 9:05 AM, Paul Fenstermacher wrote:

This topic ended up, as it should have, focused on flushing cache. As I think about it, if ENDSBS *ALL does not completely flush the disk cache and it isn't completely flushed until a PWRDWNSYS *CNTRLD is done then every restricted state backup ever done is potentially invalid UNLESS all the save commands somehow save the information in the disk cache. Thoughts, again?

Paul Fenstermacher | Sys/NW Admin,Sr | Corporate Systems - POWER Systems Administration | Jack Henry& Associates, Inc.(r)
663 West Highway 60 | Monett, MO 65708 | Ph. 417.235.6652 | x177389 | pfenstermacher@xxxxxxxxxxxxx

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.