Re: VSE lock file question
Don, The problem in VSE with multiple paths to dasd was corrected at least 20 years ago. :) [EMAIL PROTECTED] wrote: However, I remembered a problem I had with a new external lock file in a multiple CPU and VSE environment 24 years ago. The problem was the result of one of the CPUs having more than one path to the DASD where the lock file resided. Is this still a problem? Each CPU here has at least 4 paths to all the DASD. -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: VSE lock file question
Cant use VDISK with a system on a separate processor. Or at least not until VM gets XMS and CF support (somewhere over the rainbowmusic swells) David Boyes Sine Nomine Associates . Why wouldn't you use VDISK for the LOCK file? You could see a performance hit with regular DASD. Steve G. Former VSE sys.prog and missing it.
Re: VSE lock file question
You are certainly correct. However, I didn't read that into the original email. It just mentioned 'systems'. Systems can be CPU, it can be VSE, it can be applications. Oh, well. Steve G. David Boyes [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/26/2006 03:19 PM Please respond to The IBM z/VM Operating System To:IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: VSE lock file question Can't use VDISK with a system on a separate processor. Or at least not until VM gets XMS and CF support (somewhere over the rainbowmusic swells) David Boyes Sine Nomine Associates . Why wouldn't you use VDISK for the LOCK file? You could see a performance hit with regular DASD. Steve G. Former VSE sys.prog and missing it.
