Re: HSM recall overwrite other dataset in different sysplex

[Bruce Black]

Restrictions:

   An SMS complex should not span sysplexes. All of the volumes in the 
SMS

complex should be in the same Parallel Sysplex. The cross-system
   sharing functions, such as VSAM record-level sharing (RLS), 
partitioned

data set extended (PDSE) sharing, RACF(TM) security and global
   shared resources (GRS) serialization, only work within the scope of a
single Parallel Sysplex. These functions are not supported when the
   SMS complex extends beyond the Parallel Sysplex in which they are
carried out. 


IMHO, that is a bizarre recomendation.  Although all of our systems are 
now in a single parallel sysplex, we shared the ACDS/COMMDS for a single 
SMS complex across all the systems before they became a sysplex.  Heck, 
we did this before parallel sysplex was invented.


I agree that some of the things the mention will not work across 
sysplexes, but given that you understand those limitations, I see no 
reason that you can't share your SMS configuration, and the ACDS/COMMDS 
across systems in multiple plexes.


Does anyone know of any reasons why this can no longer be done? 


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

HSM recall overwrite other dataset in different sysplex

[Mohd Shahrifuddin]

Hi Listers,

Two Question:
1. Environment
   z/OS v1.4
   SMS v1.3.
   Running Parallel Sysplex
   Shared DASD between 2 sysplex
   2 SMS SCDS
   1 catalog
We implement HSM in 1 sysplex. First phase we cutover 2 storage groups
migration, backup and dump.  When the  dataset is migrate another sysplex
show migrated. We recall from the  HSM sysplex  but some how  in another
sysplex  is overwrite other dataset. Is possible or not? Please advice or
if there any fix or patch?

2. In Manual z/OS v1.3 DFDSSdfp Storage Administration reference SC26-7402-
01
1.5 Running SMS in a Parallel Sysplex Environment

An SMS complex consists of systems or system groups that share a common
configuration. A Parallel Sysplex is made up of systems that share
a cross-system coupling facility (XCF); you can run multiple SMS complexes
within a Parallel Sysplex.

Restrictions:

   An SMS complex should not span sysplexes. All of the volumes in the SMS
complex should be in the same Parallel Sysplex. The cross-system
   sharing functions, such as VSAM record-level sharing (RLS), partitioned
data set extended (PDSE) sharing, RACF(TM) security and global
   shared resources (GRS) serialization, only work within the scope of a
single Parallel Sysplex. These functions are not supported when the
   SMS complex extends beyond the Parallel Sysplex in which they are
carried out.

   Do not set up multiple SMS complexes sharing the same DASD.  This
requires extra work to maintain the duplicate SMS configurations and
   can also create problems such as running out of disk space because one
configuration cannot know about changes made to the other
   configuration, such as data set allocations and deletions, and storage
group and volume status changes.

Mean we cannot shared dasd with two SMS SCDS in 2 sysplex? Please advice
about my understanding. If happen like this what should I do? If need to
fall back to non-sms managed in shared DASD between 2 sysplex.

--
Regards,
Mohd Shahrifuddin Bin Ahmad Masri
Sunflower Consulting and Services Co Ltd
Room 401 Minjin Xiaoyun Bldg.,
Block 7 Xiaoyunli, xiaoyun Road,
Chaoyang District,Beijing 100016,China
Mobile: (86) 1391-176-9704
Fax: (8610) 6466-1840

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