Mt thought would be to place it on a shared catalog volume, since
coupling datasets are far more linkly to move around as new ones are
formatted and implemented. Also, I *might* be concerned about
RESERVE/RELEASE and general I/O levels to the Couple datasets. I would
tend to be very leery about ANYTHING that might have any effect on I/O
performance to Couple datasets.
HTH............... Rick
-----------------------------------------------------------------
Chase, John wrote:
Hi, All,
Are there any "compelling" reasons to place a shared PARMLIB on a volume
that holds a sysplex couple dataset?
Are there any "compelling" reasons NOT to place it there?
Please expound a little for answers other than "No".
TIA,
-jc-
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
