On Wed, Aug 27, 2008 at 6:42 PM, Marcy Cortes
[EMAIL PROTECTED] wrote:
Please check out apar VM6 if you are diving deep into ISFC. I'd
feel better if you did :)
In a recent conversation I claimed that ISFC has always had stability
problems when building a mesh network. We've always been
Dear all,
Last month I was asking to establish a ISCF connection between two z/VM
systems. I got the information that the resources of the SFS have to be
unique and that VMSYSx filepools are local.
I have now the necessary CTCs and wanted to activate the IS-links. Howeve
r I
saw with q
A CRR declares many resources:
q resource user vmservr
Resource: VMSYSRType: Local Owning Userid: VMSERVR
Service: 30F0F2F9 Type: Local Owning Userid: VMSERVR
Service: 06F2 Type: System Owning Userid: VMSERVR
Service: 30F0F2F7 Type: Local Owning Userid: VMSERVR
Resource:
Hi Kris,
Thank you very much. This helped me a lot.
Best regards,
Florian
On Wed, 27 Aug 2008 14:08:52 +0200, Kris Buelens [EMAIL PROTECTED]
wrote:
A CRR declares many resources:
q resource user vmservr
Resource: VMSYSRType: Local Owning Userid: VMSERVR
Service: 30F0F2F9 Type:
] On
Behalf Of Florian Bilek
Sent: Wednesday, August 27, 2008 2:53 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] CSE and VMSERVx
Dear all,
Last month I was asking to establish a ISCF connection between two z/VM
systems. I got the information that the resources of the SFS have to be
unique
On Wed, Jul 23, 2008 at 10:03 PM, Rick Troth [EMAIL PROTECTED] wrote:
I also find (aside from where Tom's suggestion is needed)
that it is helpful for the VMID of the SFS server to match
the name of the filepool it serves.
Helpful is an understatement in this context.It is very effective in
I think it is reasonable to use VMSYS and VMSYSU in the same manner that
IBM
uses them in the 'default' RMSMASTER configuration. For applications that
are LOCAL to this system, I put control type information (config files) i
n
VMSYS and use VMSYSU for work and logfiles. At disaster recovery, I
On Jul 25, 2008, at 7:36 AM, Rob van der Heij wrote:
Resist the idea to use VMSYS* filepools for other purposes. Any time
saved by hijacking the VMSERVU configuration to hold your own data is
normally paid back later at a less convenient moment.
I consider myself more than usually tolerant of
Of Adam Thornton
Sent: Friday, July 25, 2008 7:04 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: CSE and VMSERVx
On Jul 25, 2008, at 7:36 AM, Rob van der Heij wrote:
Resist the idea to use VMSYS* filepools for other purposes.
Any time
saved by hijacking the VMSERVU configuration to hold
On Jul 25, 2008, at 10:40 AM, Schuh, Richard wrote:
It doesn't seem that difficult, just follow the instructions. It may
be
drudgery, but the cookbook does work ;-)
OK. Compare to adding more storage to ZFS or adding more storage
to a Linux LVM2 volume.
Sure, I'm not having to manually
the predecessor systems
like SFS and DB2.
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton
Sent: Friday, July 25, 2008 9:26 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: CSE and VMSERVx
On Jul 25
I think it is reasonable to use VMSYS and VMSYSU in the same manner
that
IBM
uses them in the 'default' RMSMASTER configuration. For applications
that
are LOCAL to this system, I put control type information (config
files) i
n
VMSYS and use VMSYSU for work and logfiles. At disaster
Beg to differ...
The restriction on the VMSYS_ filepools is well publicized if not well
known, and there are installations with a standard node: filepool
already and in some cases they're global.
--Mike
Given that IBM discourages use of the VMSYSx: pools for real user data,
would it make
On Friday, 07/25/2008 at 10:05 EDT, Adam Thornton
[EMAIL PROTECTED] wrote:
I consider myself more than usually tolerant of system-administration-
related pain, butdamn, SFS doesn't make defining new pools exactly
*easy*, does it?
If it isn't easy, I don't think defining SFS filepools is
I also find (aside from where Tom's suggestion is needed)
that it is helpful for the VMID of the SFS server to match
the name of the filepool it serves.
-- R;
Dear all,
What is the right approach to define VMSERVx machines to work in CSE?
When the directory is shared and the names of those machines MUST be the
same on all the z/VM instances there is a conflict since they use all the
same minidisks. I couldn't find too much information about this.
The VMSERVx servers can be started on one VM only at a time.
But, they can be reached by users on other VM systems: you'd make a
CTC connection between the VM systems and use ACTIVATE ISLINK to make
the CP's talk to eachother. Global resources are then available
throughout the ISFC collection.
Kris,
thank you for this info. But isn't it the case that e.g. DFSMS/VM need th
ose
SFS servers and if so, I thought the name MUST always be the original one
.
If this is not the case than fine. Does it mean that the DFSMS an be run
from other SFS servers as well?
Best regards,
Florian
Another approach - the one I use - is to add each of the VMSERV[S|U|R]
systems to the XSPOOL input and output exclude lists in SYSTEM CONFIG. This
prevents them from participating in the shared spool configuration, but
allows them to log on to multiple VM systems in the CSE cluster
concurrently.
DFSMS wants to have a VMSYS server. VMSYS filepool IDs are local, so
each VM system would need one.
When you use CSE with a shared CP directory,SASAFFIN records in the
directory can make that users in one system have other minidisks than
users in other systems. So, even with CSE, you can have
That doesn¹t deal with the write-enabled minidisks owned by those users,
though. You¹d need to use SYSAFFIN to isolate minidisks to specific LPARs,
and if you did this, your filepools wouldn¹t actually be shared. If you
don¹t do something with SYSAFFIN and just allow all the systems to access
the
Each system should have its own VMSYS filepool, but nothing requires that
it
be in a userid named VMSERVS. In a shared directory, make multiple userid
s
like VMASERVS, VMBSERVS, VMCSERVS, and you can configur each to provide t
he
VMSYS filepool for their own system. You do need to make sure the
22 matches
Mail list logo
