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
On Thu, 24 Sep 2009 07:30:38 -0500, Darth Keller darth.kel...@assurant.com
wrote:
Has anyone asked why the original poster has 2 SMSPlexes? His cleanest
solution might be to merge the 2.
Good point.
Sounds like he has at least some shared DASD - in a previous incarnation,
we had a similar
Thanks everyone for your input.
Has anyone asked why the original poster has 2 SMSPlexes? His cleanest
solution might be to merge the 2.
Good point.
The bronze sysplex is fairly recently merged from seperate sysplexes to take
advantage of licensing savings. Merging the 2 completely to a
We have 2 SMSPLEXES within a bronze SYSPLEX.
GRS is common to all LPARS, but most everything else is not.
Now we have a new DB2 application coming that will require application
datasets which will be required to be written to from all LPARS in the PLEX.
I've shared volumes before by having a
: www.rocketsoftware.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Brian Fraser
Sent: 23 September 2009 16:22
To: IBM-MAIN@bama.ua.edu
Subject: Sharing Data between SMSPLEXES.
We have 2 SMSPLEXES within a bronze SYSPLEX.
GRS is common
Given the constraints you have imposed, I would suggest a 3rd
('platimum') SMSplex for this data.
i.e. shared ucat,. Volumes, SMS cds's, HSMplex,...
Comments interspersed:
We have 2 SMSPLEXES within a bronze SYSPLEX.
GRS is common to all LPARS, but most everything else is not.
Now we have a
On Wed, 23 Sep 2009 23:21:45 +0800, Brian Fraser brianmfra...@gmail.com wrote:
We have 2 SMSPLEXES within a bronze SYSPLEX.
GRS is common to all LPARS, but most everything else is not.
Now we have a new DB2 application coming that will require application
datasets which will be required to be
snip
Since GRS is common, you don't have to worry about data set integrity or
issues with sharing PDSE / HFS across SMS.
/snip
I thought that PDSE didn't work inter-SYSPLEX no matter what you did
with GRS but only intra-SYSPLEX. Wrong again?
Jack Kelly
202-502-2390 (Office)
On Wed, 23 Sep 2009 15:10:55 -0400, John Kelly
john_j_ke...@ao.uscourts.gov wrote:
snip
Since GRS is common, you don't have to worry about data set integrity or
issues with sharing PDSE / HFS across SMS.
/snip
I thought that PDSE didn't work inter-SYSPLEX no matter what you did
with GRS but only
Brian ,
We have 2 SMSPLEXES within a bronze SYSPLEX.
GRS is common to all LPARS, but most everything else is not.
Now we have a new DB2 application coming that will require application
datasets which will be required to be written to from all LPARS in the PLEX.
I've shared volumes before by
zSoftware Group / Emerging Technologies
Office: # 614-213-3467
Cell: # 412-519-2592
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Brian Fraser
Sent: Wednesday, September 23, 2009 11:22 AM
To: IBM-MAIN@bama.ua.edu
Subject: Sharing Data
Data between SMSPLEXES.
We have 2 SMSPLEXES within a bronze SYSPLEX.
GRS is common to all LPARS, but most everything else is not.
Now we have a new DB2 application coming that will require application
datasets which will be required to be written to from all LPARS in the
PLEX.
I've shared volumes
On Wed, 23 Sep 2009 15:25:45 -0400, John Kington
john.king...@convergys.com wrote:
SMS keeps space utilization information for each managed volume in the
communications dataset. By allowing multiple SMSplexes to allocate, extend
and delete datasets on the same volume(s), you will likely get
Mark,
SMS keeps space utilization information for each managed volume in the
communications dataset. By allowing multiple SMSplexes to allocate, extend
and delete datasets on the same volume(s), you will likely get these stats
out of whack. The result would be something like never allocating a
On Wed, 23 Sep 2009 16:51:12 -0400, John Kington
john.king...@convergys.com wrote:
Mark,
SMS keeps space utilization information for each managed volume in the
communications dataset. By allowing multiple SMSplexes to allocate, extend
and delete datasets on the same volume(s), you will likely get
: 23 September 2009 20:14
To: IBM-MAIN@bama.ua.edu
Subject: Re: Sharing Data between SMSPLEXES.
On Wed, 23 Sep 2009 15:10:55 -0400, John Kelly john_j_ke...@ao.uscourts.gov
wrote:
snip
Since GRS is common, you don't have to worry about data set integrity
or issues with sharing PDSE / HFS across
16 matches
Mail list logo
