approach to define an X Disk in the SFS
. I
mean, normally one puts the files accessible to all users on a mini disk
that everybody can access.
How can you do that with SFS? Should it be a directory in the file space
of
MAINT or should I define an extra Virtual Machine for that? What would
year I am working on a z/VM installation and have to catch up with all the
new facilities in VM.
I am wondering what would be best approach to define an X Disk in the SFS. I
mean, normally one puts the files accessible to all users on a mini disk
that everybody can access.
How can you do
We use the P-SFS instead of X-DISK. The name is up to you. Ours is
called: VMSYS:$CMSLIVE.SYSTEM.
The access is done in an exit of SYSPROF calling SYSXPROF EXEC.
We but it under DIRControl so we can put it in an address space.
-Original Message-
From: The IBM z/VM Operating System
System [mailto:[EMAIL PROTECTED] On
Behalf Of Fox Blue
Sent: Friday, February 22, 2008 11:04 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: X Disk in SFS
Dear all,
I am currently busy to understand the capabilities of SFS. Started in
the
late 80ies as system programmer we had VM/SP but there was no SFS
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens
Sent: Friday, February 22, 2008 8:23 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: X Disk in SFS
For the best performance, you
) that explains more of this.
2008/2/22, Stracka, James (GTI) [EMAIL PROTECTED]:
We use the P-SFS instead of X-DISK. The name is up to you. Ours is
called: VMSYS:$CMSLIVE.SYSTEM.
The access is done in an exit of SYSPROF calling SYSXPROF EXEC.
We but it under DIRControl so we can put it in an address
AM
Subject: Re: X Disk in SFS
You've got some catchin' up to do. 8-)
I would not use MAINT as a file space. Reason being, when new releases
of VM come out, you'll have to worry about backing your stuff up and
reloading it.
Taken literally, no need to set up another Virtual Machine (I take
[mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen
Sent: Friday, February 22, 2008 8:16 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: X Disk in SFS
You've got some catchin' up to do. 8-)
I would not use MAINT as a file space. Reason being, when new
releases of VM come out, you'll have
Subject: Re: X Disk in SFS
Definitely early in the sequence. SFS is mission critical here. I have
the AUTOLOG2 machine wait after it AUTOLOGs the SFS servers until it can
access a directory in each critical file pool before it continues with
the rest of the AUTOLOGs. If it cannot access
I am wondering what would be best approach to define an X Disk in the
SFS
. I
mean, normally one puts the files accessible to all users on a mini
disk
that everybody can access.
How can you do that with SFS?
The way we do it is to define a new filepool called TOOLS:, define a
user called
Hello Kris,
Could you send me that doc too?
Ed Martin
330-588-4723
ext 40441
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Friday, February 22, 2008 11:23 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: X Disk in SFS
For the best performance
[mailto:[EMAIL PROTECTED] On
Behalf Of Schuh, Richard
Sent: Friday, February 22, 2008 12:47 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: X Disk in SFS
Not necessarily. You can enroll MAINT in the user file pool as well as
in VMSYS. The user file pool would not be touched by the new releases
22, 2008 10:21 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: X Disk in SFS
What you say is true. Respectfully, for newbies it could be
confusing seeing something with MAINT in the name. Most
newbies learn quickly that MAINT is the su and to treat
things associated with MAINT with respect
Dear all,
Thank you very much indeed for your great contributions and hints on this
issue. I appreciate them very much. And I must say that I am very impress
ed
about this mailing list. It will help me really to improve my knowledge o
n
z/VM. Thanks a lot.
Fox
14 matches
Mail list logo
