Actually, we solved this problem - many users wanting to write CMS files to the same disk - a long time ago by switching to a process that sent the files to the reader of a service machine that does nothing but disk load (yes it was that long ago) - or receive - the files onto the mindisk, which only the one service machine CMS user has in write mode. Little longer, but still using this approach many years later.
On 5/1/07, Ian S. Worthington <[EMAIL PROTECTED]> wrote:
That's interesting, but conflicts with what some other folks have said here earlier. We are under CMS, and I don't want to do simultaneous update to a single file, just allow several service machine to write their output files to single location, which requires a mw-tolerant directory. Apparently we can't convert the minidisks we're using to SFS. NFS, as mentioned earlier might be an option: I'm trying to find out if its enabled. ian ------ Original Message ------ Received: Tue, 01 May 2007 05:29:09 PM BST From: "Schuh, Richard" <[EMAIL PROTECTED]> To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Link Multiple Write safely > There is a very big one at this shop that is mode 6, and has been shared > for the 9+ years that I have been here and, I think, about 6 years > before that. With mode 6, you can update in place so long as you do not > change the record length of an existing record. We have a source control > system that uses ISPF panels that requires that all users get the disk > having this pseudo maclib MW. > > In any event, the updating of a record in place requires no changes that > will corrupt the disk if it is MW by several users, in our case, over > 50, at the same time. So if that is how you intend to use the disk, MW > is perfectly safe under CMS. > > Regards, > Richard Schuh > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Ed Zell > Sent: Tuesday, May 01, 2007 9:06 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Link Multiple Write safely > > > Mode 6 files can be shared so long as the software takes > > care not to have record collisions. ISPF handles sharing > > its fake MACLIBs that way under CMS. > > > I don't think this is the case. None of our ISPF MACLIB's > are file mode 6. > > I was under the impression that ISPF handles sharing by forcing > all updates to go through the ISPVM virtual machine. But I > could be wrong (as has happened many times in the past!). > > > Ed Zell > Illinois Mutual Life > (309) 674-8255 x-107 > . > > > CONFIDENTIAL NOTICE: This communication, including any attachments, is > intended only for the use of the individual or entity to which it is > addressed and contains information which may be confidential. If you > are not the intended recipient, any distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, notify the sender immediately, delete the > communication and destroy all copies. Thank you for your compliance. >
