Our VSE lock file mdisk belongs to OPERATOR, which runs PROP and is disconnected shortly after IPL. All VSE guests tests the lock file in their PROFILE EXEC and if it needs to be initialized, does it. So any guest can come up first and set up the lock file. All OPERATOR does is have the mdisk entry in the DIRECT.
On Tue, Mar 8, 2011 at 12:05 PM, David Boyes <dbo...@sinenomine.net> wrote: > On 3/8/11 12:57 PM, "Wandschneider, Scott" > <scott.wandschnei...@infocrossing.com> wrote: > >>I have a SVM called VDISKS the creates and initializes a virtual lock >>file for four VSE guest to use. After a short time, VDISKS is logged off >>by the system. All is fine if at least one VSE remains logged on, >>however if all are logged off the virtual lock file goes away also. How >>can I keep VDISKS from being logged off by the system? > > Simplest answer: have the VDISKS userid run PROP in it's PROFILE EXEC (see > Running Guest Operating Systems Under VM manual for PROP setup). If you > never send it any commands or anything to act on, the VDISKS users will > take up almost no resources, and PROP's always there on the basic system. > > The theory here is that a creator of a VDISK has to stay logged in if you > want the VDISK to survive the last user of the VDISK logging off. As > you've observed, the userid creates the vdisk and then other users link > it. If the creator logs off, but another user has the VDISK linked, then > the VDISK survives until the last user linked to it logs off, then CP > destroys it. In this case PROP is a simple way to keep the VDISKS userid > logged in (thus protecting the VDISK from destruction because the creator > is still logged on), but PROP is well behaved enough to pretty much take > no resources at all if it's not being actively used. >
