This already implies that one should not interfere with this presumption by ASM
by placing other datasets with (heavy) load on the same volume. ASM assumes 2
private paths and if WLM does not assign more aliasses, the non-paging I/O will
influence the paging I/O negatively.
I agree with that. It makes no sense to put heavily-used datasets on
the same volume as paging datasets. But lightly used datasets should
not be a problem, with the caveat that even a "lightly-used" dataset can
be heavily used in short bursts.
I have found more than one customer who has placed shared datasets
subject to RESERVE, such as catalogs, on th same volume as paging
datasets. That is just foolish!
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
