In <[EMAIL PROTECTED]>,
on 11/04/2005
at 08:06 AM, "Knutson, Sam" <[EMAIL PROTECTED]> said:
>This is perfectly safe since z/VM will enforce read only access if
>that is the way a disk is attached you are not violating any sharing
>rules.
FSVO safe. It will certainly protect the R/O volumes, bu
Thank you to everyone for your help and advice
Crispin Hugo
Systems Programmer, Macro 4
http://www.macro4.com/
Macro 4 plc, The Orangery, Turners Hill Road, Worth, Crawley, RH10 4SS
Direct Line: +44 (0)1293 872121 Switchboard: +44 (0) 1293 872000
Fax: +44 (0) 1293 872001
This message contai
In the TMON lab we always ran new ESP releases of z/OS under z/VM just
so we could have read only access to our existing DASD in the Sysplex
before toleration service was available to actually bring the guests
into the Sysplex. This worked well you just have to have some volumes
exclusive under z
On Nov 3, 2005, at 2:32 PM, Crispin Hugo wrote:
Thanks Ed. I am unsure about what MVS will think of Read only. I
don't think
it understands it.
The dataset may be read only but what about the VTOC (date last
used) ?
Ed
-
I got a note from a friend who works for a disk vendor that confirms
that when they have disks in r/o mode, MVS open for INPUT works just
fine, no DSCB update errors.
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales in
TECTED]
Sent: 03 November 2005 21:23
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Sharing z/OS DASD under VM
Crispin Hugo wrote:
>Thanks Ed. I am unsure about what MVS will think of Read only. I don't
think
>it understands it.
>
>
We do it all the time. You get an IOS message (cmd
Crispin Hugo wrote:
Thanks Ed. I am unsure about what MVS will think of Read only. I don't think
it understands it.
We do it all the time. You get an IOS message (cmd reject) written to
the console when z/OS attempts to write to a read-only device.
--
vember 2005 21:05
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Sharing z/OS DASD under VM
>
>
>Oh, I'm not too sure how well z/OS will tolerate a "read only" disk. I
>remember doing it long ago with MVS 3.8j and VM/370. I'd get some
>strange I/O errors at times.
>
Oh, I'm not too sure how well z/OS will tolerate a "read only" disk. I
remember doing it long ago with MVS 3.8j and VM/370. I'd get some
strange I/O errors at times.
Even when you open a dataset for just INPUT, OPEN may want to rewrite
the F1 DSCB to update the last reference date if is not al
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Crispin Hugo
> Sent: Thursday, November 03, 2005 2:14 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Sharing z/OS DASD under VM
>
>
> Quick question to the experts
---Original Message-
From: Edward E. Jaffe [mailto:[EMAIL PROTECTED]
Sent: 03 November 2005 20:18
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Sharing z/OS DASD under VM
Crispin Hugo wrote:
>Quick question to the experts,
>Is there an easy way to share a DASD between 5 or more z/OS systems under
>
Crispin Hugo wrote:
Quick question to the experts,
Is there an easy way to share a DASD between 5 or more z/OS systems under
z/VM. We would like to put some files on DASD that can then be read by
another other z/OS system who has access to the DASD. I don't want more than
1 machine to write to a
Quick question to the experts,
Is there an easy way to share a DASD between 5 or more z/OS systems under
z/VM. We would like to put some files on DASD that can then be read by
another other z/OS system who has access to the DASD. I don't want more than
1 machine to write to any file. Sort of read o
13 matches
Mail list logo
