> On 12 July 2020, at 03:50, Israel Wagshal <wagsh...@hotmail.com> wrote:
>
> On Sat, 11 Jul 2020 17:09:32 -0500, Al Ferguson <afergu...@neptunescove.org>
> wrote:
>
> Thank you for the insights.
>
> How do you change dynamically root filesystem's mount mode to R/W and back to
> R/O?
Using ISHELL as “root” (UID=0 or SU Command), under the FILE_SYSTEMS Dropdown,
you will be able to list all the mounted filesystems. Selecting the one you
want to change via the “m” selection option will allow you to change how it is
mounted.
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.f54u200/umfs8.htm
<https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.f54u200/umfs8.htm>
or
From a TSO Command line:
UNMOUNT FILESYSTEM(MVS.FILE.SYSTEM.NAME) REMOUNT(READ|RDWR)
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxa500/tsoumo.htm
<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxa500/tsoumo.htm>
> What do you mean by saying "the IBM Root Filesystem is actually mount at
> /ipl-vol/ "?
> The Version root has to be mounted R/O off a mountpoint at the Sysplex root.
> We do not place any VSAM dataset on the iplvol. Only non-VSAMs are placed
> there, because we use symbolic cataloging via &SYSRS1 and &SYSRS2, which
> isn't possible (I think) for VSAM datasets.
In a Sysplex (even a monoplex) you can use IBM’s SYSPLEX Shared Filesystem
configuration. This is a combination of BPXPRM00 options and Filesystem
mounting, see:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb200/abstract.htm
<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb200/abstract.htm>
An example can be viewed at:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb200/filesing.htm
<https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb200/filesing.htm>
I Build pair of IPL Volumes: The first is the actual IPLVOL will all the copies
of all the SMP/E zOS Files on it, the volume is formatted with a zOS Boot
Sector. The second has copies of all the SMP/E ZFS Files for that maintenance
level and is formatted with the appropriate STAND ALONE DUMP sector (the STAND
ALONE DUMP should match the same SMP/E Level as the Boot Sector and the zOS
Files to ensure 100% compatibility). The Mount Point for the SMP/E SYSTEM Root
defaults in a Sysplex File Sharing environment to root Mount Point “/&VERSION”,
which defaults to the IPLVOL (&SYSR1).
Using naming standards for the ZFS Filesystem names such as:
SYS1.&SYSR1..OMVS.ROOT.ZFS will allow you to have the BPXPRM00 set to mount and
SMP/E Filesystems related to the IPLVOL (even though not really on IPLVOL).
While the VSAM ZFS Filesystem files are not cataloged with the Symbolic, each
file is named to correspond with an actual IPLVOL (either in use, or slated to
be in use).
Remember, GOOD naming standards are your friends and make a Sysprogs life much
easier. :^) I have a handful of JOBs I use to build my IPLFOL Pairs (&SYSR1 and
&SYSR2) to copy everything from the SMP/E Target environment, add any Unix file
links to the zFS Filesystems (e.g. /usr/lpp/CA/caldap ) for 3rd Party Products,
Open Source products (e.g. /usr/local/… products downloaded from Rocket), setup
zOS Boot Sectors & Stand Alone Dump sector, … etc. They take about 10-15
minutes to run on a small machine with current DASD Technology. In combination
with Techie LPARs/SYSPLEX I can pull down maintenance, apply it, build these
volumes, and to a test IPL normally in a morning; except for the IPLVOL name
and the IBM Shopz Maintenance info, the JOBs do not really change between
tests. Occasionally and IBM SMP/E ACTION Hold will indicate a File Name or USS
Path change; but those normally correspond to a new zOS Release, either pre-IPL
prep-work on the current zOS, or with the new zOS release.
If you are interested, I do have XMIT files of how I migrated to ZFS Sysplex
File Sharing and my zOS Build Process from when I last did this with zOS 2.2.
The build process JOBs were only slightly modified to work with zOS 2.3 and
2.4; but to see how they all fit together they are all packaged around 2.2.
Send an email to the email in my signature and I will send you a ZIPed version
the XMIT files (about 175KB in size for all 5 related files). Or if you email
system filters these out, I can put them on my GITHUB site for download.
>
>> Isreal,
>>
>>
>>> On 11 July 2020, at 15:30, Paul Gilmartin
>>> <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>>>
>>> On Sat, 11 Jul 2020 12:51:04 -0500, Israel Wagshal wrote:
>>>>
>>>> I'm installing a software that has to have its own zFS aggregate mounted
>>>> and available
>>>>
>>>> Looking into the USS filesystem I can see many IBM products' zFS
>>>> aggregates mounted off /usr/lpp.
>>>> I can see no foreign aggregate mounted off /usr/lpp.
>>>>
>>> I believe LPP abbreviated Licensed Program Products.
>>
>>
>> That is what IBM has designated it. IBM though does not say it is for IBM
>> Licensed Program Products. CA (now Broadcom) uses /usr/lpp/CA/product_name
>> quit a bit; as do a few others.
>>
>>
>>> The convention elsewhere seems to be /usr/local:
>>> https://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY
>>
>> The common place to put most Open Source tools is /usr/local/tool_name;
>> particularly in Linux installations. Occasionally some 3rd Party Products
>> use this as well (though they also end up in /var and /opt quite a bit).
>>
>>
>>>> However, /usr/lpp is in IBM's Version root which is mounted R/O.
>>
>> This is recommended configuration
>>
>>
>>>>
>>>> Is it proper to change Version root's mount mode temporarily to R/W and
>>>> mkdir another mountpoint off /usr/lpp for the product I'm installing, or
>>>> should this be avoided and made elsewhere?
>>>> Is there a general recommendation where to mount aggregates for non-IBM
>>>> products?
>>>> The vendor says nothing about this.
>>>>
>>>> Can mount mode of the Version root be changed on the fly by some command
>>>> or will this require bouncing the system?
>>
>> You can dynamically change the IBM Root Filesystem (or any mounted
>> Filesystem) from r/o to r/w and back again (line commands or via ISHELL
>> Filesystem utility), you do need to be root (either via “su” command or your
>> UID being 0).
>>
>> What I have found to do to try to align with IBM’s intentions is the
>> following:
>>
>> 1. Create a mount point in the root filesystem to mount 3rd party products,
>> say /products.
>> I use a Automount to dynamically mount filesystems here. With proper naming
>> standards you can code a general rule in the /etc/automount/product config
>> file (or just hard code then as needed and refresh vial the automount
>> command).
>>
>> 2. Copy the 3rd Party Product to a Filesystem of its own.
>> If the vendor, say CA, suggests /usr/lpp/CA/caldap/...; I install it at the
>> /caldap/… level at the Filesystem.
>>
>> 3. Mount the filesystem so it is available, say the Filesystem is mounted at
>> /products/CALDAP … the product directory would be at /products/CALDAP/caldap.
>>
>> 4. Dynamically change root filesystem to r/w
>>
>> 5. Create a Soft Link in the /usr/lpp directory (e.g. “ln -sf
>> /products/CALDAP/caldap /usr/lpp/CA/caldap”)
>>
>> 6. Verify it is available via “ls -alF /usr/lpp/CA/caldap”
>>
>> 7. Dynamically change root filesystem back to r/o
>>
>> I prefer to do it this way for a couple of reasons:
>>
>> 1. Under Unix (USS is Posix 3 Unix) this wil behave exactly like it was
>> mounted at /usr/lpp/CA/caldap
>> 2. I want to keep the IBM root Filesystem as close to what is coming out of
>> SMP/E as possible
>> 3. I do not want to mount Filesystems on the IBM Root Filesystem, if
>> possible*
>> 4. May products (I have seen this with IBM, CA, Rocket, …) have
>> configuration files that point to their “suggested” mount point and these
>> are not alway documented and/or auto configured correctly.
>> 5. It is always easier talking with a vendors support is everything looks to
>> be configured as closely to the manual as possible.
>>
>> * I run in a Sysplex, with a share Sysplex Root Filesystem and the IBM Root
>> Filesystem is actually mount at /ipl-vol/
_______________
Al Ferguson | mailto:afergu...@neptunescove.org
Milwaukee, WI USA | http://www.neptunescove.org
Dulcius ex Asperis
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
