Hello Listers,
 
We are in the process of adding some new linux guests. Now in the past
we had some issues with sharing DASD in our VSE environment, the DASD
must be set to shared to be able to run VSE on shared DASD. A few
linuxguests also run on shared DASD that actually has been set SHARED. I
wonder if that is really required. I had some discussion on this topic a
while ago and it was said that Linux guests do not require DASD to be
set to shared. VSE does require this because of the reserve/release it
does on it's DASD. So from that view DASD need not to be set to shared
when in use for Linux guests.
 
A reason for having DASD not set to shared is to make use of MDC (our
selling point is that we do not want guests to cache filesystem data
because we have MDC). But when guests are running in multiple VM systems
would this hurt in any way? I do know that whenever a guest has to be
moved to a different VM the MDC need to be flushed. But what would it do
to the multiple guests running in the various VM's? In theory we could
end up running guests in 4 LPAR's while all of them share minidisks on
one single DASD volume. I do not like to find out the hard way that we
shouldn't have done that.
 
What are your experiences with sharing DASD? Do you set DASD to SHARED?
What are your reasons for either set SHARED or not set SHARED?
 

Met vriendelijke groet/With kind regards, 
Berry van Sleeuwen 
Flight Forum 3000 5657 EW Eindhoven

( +31 (0)6 22564276

                 



Atos Origin <http://www.atosorigin.com/> 

MO OC Mainframe Services

 

 

 

 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

<<image001.gif>>

<<image003.jpg>>

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to