Right.

The syntax is:

Poolname colon rootname period
and, if necessary backslash subdirectory backslash subdirectory etc

Poolname: is only needed if it is not the same pool that is specified as
your default poolname.
'SET FILEPOOL VMSYSU:'   (in my user direct)

Rootname defaults to your CMS userid but you still need the period.
Assuming you are logged on as MAINT:

ACCESS . W
is the same as:
ACCESS MAINT. W
is the same as:
ACCESS VMSYSU:. W
is the same as:
ACCESS VMSYSU:MAINT. W

Tom Duerbusch
THD Consulting

On Fri, Nov 6, 2015 at 1:31 PM, Will, Chris <[email protected]> wrote:

> Well it appears to be a typo in the cookbook.  I added a "." after vwmm2
> and it works.
>
> access vmpsfs:vmww2. z (forcerw
>
> I was getting the following error without the dot.
>
> access vmpsfs:vmww2 z (forcerw
> DMSPCL389E Invalid operand: VMPSFS:VMWW2
>
> Chris Will
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
> Duerbusch, Tom
> Sent: Friday, November 06, 2015 11:30 AM
> To: [email protected]
> Subject: Re: Change common service filepool name from POOL1 to VMPSFS -
> New z/VM cookbook questions
>
> To split hairs.....
>
> You don't have to create a CMS user (i.e. in the USER DIRECT or DIRMAINT)
> in order to ENROLL USER (create a SFS user).
>
> Process is:
>
> 1.  Optionally create a CMS user.
> 2.  Enroll the SFS user which creates the default root directory.
> 3.  Optionally create subdirectories on that root directory.
> 4.  If directories/subdirectories/files are to be access by any
> NON-SFS-ADMIN user, or the base user that was created in step 1, then you
> need to GRANT authorizations those userids.
>
> Q LIMITS ALL  will show all the users that are enrolled.
>
> Filepool VMSERVS is the IBM filepool.  It will get replaced by IBM.  Not a
> good place to store your stuff.
>
> Filepool VMSERVU is setup as the default for users.  As shipped, it
> doesn't have much disk space.
>
> If you use VMSERVU, the first thing you need to do is add disk space.   If
> you create your own, you need to generate it with lots of disk space.
>
> Once SFS became available (VM/SP 5), I would never want to operate without
> it <G>.
>
> Tom Duerbusch
> THD Consulting
>
> On Fri, Nov 6, 2015 at 7:29 AM, Will, Chris <[email protected]> wrote:
>
> > SFS is new for us.  I have been happy using regular minidisks in the
> > past but if there is a good reason to start looking at SFS (better for
> > SSI, LGR, DR, etc.), we will try to get up to speed on it.  Another
> > question about the redbook is creation of the files under VMWW2.
> > Would you not have to define a userid VMWW2 and create a directory
> > prior to accessing the directory?  Here is the portion of the redbook in
> question.
> >
> > ===> enroll user vmww2 vmpsfs ( blocks 5000  << there is no step in
> > the book to create a user.
> > ===> access vmpsfs:vmww2 z (forcerw << shouldn't there be a step to
> > create the directory?
> > ===> copy VMWW2 VMARC M = = Z
> > ===> erase VMWW2 VMARC M
> >
> > Chris Will
> >
> > -----Original Message-----
> > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
> > Alan Altmark
> > Sent: Friday, November 06, 2015 4:28 AM
> > To: [email protected]
> > Subject: Re: Change common service filepool name from POOL1 to VMPSFS
> > - New z/VM cookbook questions
> >
> > On Thursday, 11/05/2015 at 12:06 EST, "Will, Chris" <[email protected]>
> > wrote:
> > > I have been going through the new z/vm 6.3 cookbook that uses sfs
> > > for
> > many
> > > functions.  I set up a 2 member SSI cluster using the previous z/vm
> > > 6.3
> > redbook
> > > but used name "POOL1" for the common service filepool name during
> > > the
> > install
> > > and would like to change it to VMPSFS.  Any way to change this?
> > > Also,
> > in the
> > > redbook they format a disk for use by vmses/e (address 1564/label
> > > vv1564
> > in the
> > > book) but then it is never referenced again.
> >
> > If an answer doesn't appear soon, I suggest opening a PMR.
> >
> > Alan Altmark
> >
> > Senior Managing z/VM and Linux Consultant Lab Services System z
> > Delivery Practice IBM Systems & Technology Group
> > ibm.com/systems/services/labservices
> > office: 607.429.3323
> > mobile; 607.321.7556
> > [email protected]
> > IBM Endicott
> >
> > ----------------------------------------------------------------------
> > For LINUX-390 subscribe / signoff / archive access instructions, send
> > email to [email protected] with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > ----------------------------------------------------------------------
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
> >
> > The information contained in this communication is highly confidential
> > and is intended solely for the use of the individual(s) to whom this
> > communication is directed. If you are not the intended recipient, you
> > are hereby notified that any viewing, copying, disclosure or
> > distribution of this information is prohibited. Please notify the
> > sender, by electronic mail or telephone, of any unintended receipt and
> > delete the original message without making any copies.
> >
> >  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan
> > are nonprofit corporations and independent licensees of the Blue Cross
> > and Blue Shield Association.
> >
> > ----------------------------------------------------------------------
> > For LINUX-390 subscribe / signoff / archive access instructions, send
> > email to [email protected] with the message: INFO LINUX-390 or
> > visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
> > ----------------------------------------------------------------------
> > For more information on Linux on System z, visit
> > http://wiki.linuxvm.org/
> >
>
>
>
> --
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [email protected] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit http://wiki.linuxvm.org/
>
>
> The information contained in this communication is highly confidential and
> is intended solely for the use of the individual(s) to whom this
> communication is directed. If you are not the intended recipient, you are
> hereby notified that any viewing, copying, disclosure or distribution of
> this information is prohibited. Please notify the sender, by electronic
> mail or telephone, of any unintended receipt and delete the original
> message without making any copies.
>
>  Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
> nonprofit corporations and independent licensees of the Blue Cross and Blue
> Shield Association.
>



--

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to