Andrew,

We have a similar mixed environment.  We approach it probably as Mark does.  
SYSPLEX(YES) on all systems that use the shared SYSPLEX ROOT on the small 
subset of shared DASD (with CDS' and a PARMLIB).  We had one pre-existing 
sysplex that fully shares its DASD.  The rest of the previously monoplex 
systems do not share with this sysplex or with each other (yet).  We have 
one more sysplex merging in on 7/20.  It works, and it's not complicated.

SYSPLEX(YES) only requires a common SYSPLEX ROOT within the Sysplex that 
all systems can get to.  Multiple "HFSPlexes" is not allowed within a Sysplex, 
but there are no rules (that I have found) that state you cannot limit the 
degree of filesystem sharing you exploit, other than the ROOT.

We did get caught by mountpoints and symbolic links for a couple of 
applications that were differrent on our monoplex systems.  Once we 
reconciled the directory structure and BPXPRM mountpoints, we were fine.  
You may have to reconcile your automount policies, too.

The "Merging Systems into a Sysplex" redbook, SG24-6818 is another fine 
reference for HFS and other components.

HTH,
Art Gutowski
Ford Motor Company ITInfrastructure

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

Reply via email to