On Wed, 9 Jul 2008 08:22:52 -0500, Mark Zelden
[EMAIL PROTECTED] wrote:
I obviously agree (I think you were commenting on my post when you wrote
very similar sharing here), but it is far from iron-clad. For example,
RESERVE won't keep 2 people from updating the same PDS (or PDS member)
from
Very similar level of sharing here. We used to have some application sharing
across sysplex boundaries, but it caused far too many problems versus what it
solved, so we replicated the data and apps spend a few minutes on the BDT
pipe over FCTC's or the ftp pipe over Hipersockets.
We share
On Wed, 9 Jul 2008 08:00:25 -0500, Arthur Gutowski [EMAIL PROTECTED] wrote:
Very similar level of sharing here.
snip
Bottom line: It can be done if you're careful, understanding and
mitigating the
risks. RESERVE/RELEASE has been around for a very long time, and while not
the most efficient
Hi all,
We have a shared dasd that hold a shared user catalog and there are a third
party software installed on that dasd, occasionally we met a problem that a
LPAR will reserve the dasd and there are IOS071I meesage appeared in
syslog/operlog, how can we avoid the problem?
Is it suggested to
]
(office) 301.986.3574
Think big, act bold, start simple, grow fast...
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Victor Zhang
Sent: Tuesday, July 08, 2008 3:36 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Sharing catalog among systems
We choose to not allow any shared DASD across Sysplex boundaries.
It eliminates a whole class of problems.
We also chose to do the same thing in the mid-1990's.
And, at that time, the point was that DASD was cheap enough (especially
compared to the integrity problems) then.
Now, there is very
Nothing wrong with Sam's point of view and agree it is the safest.
On Tue, 8 Jul 2008 10:47:43 +, Ted MacNEIL [EMAIL PROTECTED] wrote:
Now, there is very little argument for sharing.
In a few cases, we have to. Our Sun/STK VSMs and tape libraries are shared
across sysplexes, so their
Sharing DASD was around long before sysplex...
There are two falacies regarding technology:
1. This is old, therefore good.
2. This is new, therefore better.
Shared DASD has been around for a long time, but I will only share within
SYSPLEX boundaries.
Sharing outside a SYSPLEX (or a Single
On Tue, 8 Jul 2008 13:38:06 +, Ted MacNEIL wrote:
... I will only share within SYSPLEX boundaries.
So how do you deal with the issues that Mark mentioned?
--
Tom Marchant
--
For IBM-MAIN subscribe / signoff / archive
So how do you deal with the issues that Mark mentioned?
I have only dealt with three or less SYSPLEX systems.
I have also dealt with mostly financial institutions.
In those cases the integrity issues were more important than the cost of data
duplication.
(PS: I was only giving my opinion based
a reserve and not hurt
anything.
HTH
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Victor Zhang
Sent: Tuesday, July 08, 2008 2:36 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Sharing catalog among systems,benefits or trouble?
Hi all,
We have
Victor Zhang [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
Hi all,
We have a shared dasd that hold a shared user catalog and there are a
third
party software installed on that dasd, occasionally we met a problem
that a
LPAR will reserve the dasd and there are IOS071I meesage
12 matches
Mail list logo
