Has anyone asked why the original poster has 2 SMSPlexes?  His cleanest 
solution might be to merge the 2.

Sounds like he has at least some shared DASD - in a previous incarnation, 
we had a similar situation and I did NOT want 2 SMSPlexes controlling 
volumes.  So I 'merged' the code - basically I took the 2 pieces of code & 
surrounded them with checks for the SysID.  If (SYSID1 or SYSID3), then 
fall into this code segment, if not fall into the 2nd piece. 

Then I moved all the construct definitions into the same SCDS - the only 
issue I had was there were a couple of constructs with the same name on 
both sides.  I resolved that by merging the constructs and using what ever 
criteria gave the most service, i.e. - if the MgmtClas on 1 side said 
migrate after 7 days and on the other side said 15 days, I gave the 
'merged' MgmtClas 15 days.  StorGrps with the same name, I just renamed 
one.  The StorGrps were still owned & managed by the original LPAR.

I put the shared COMMDS & CDS's on shared DASD.  We use GRS.

There were a few steps ahead of SMS, like I merged the catalog 
environments - my choice, I think I could have gotten SMS to work anyway. 
Since then I've re-written the code so that we truly have 1 SMSPlex.


**************************************************************************************
This e-mail message and all attachments transmitted with it may contain legally 
privileged and/or confidential information intended solely for the use of the 
addressee(s). If the reader of this message is not the intended recipient, you 
are hereby notified that any reading, dissemination, distribution, copying, 
forwarding or other use of this message or its attachments is strictly 
prohibited. If you have received this message in error, please notify the 
sender immediately and delete this message and all copies and backups thereof.

Thank you.
**************************************************************************************

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to