Elaine,
you cannot have the same filesystem mounted twice(or more) in different spots
in the directory tree in sysplex filesystem. As mentioned before, you really
dont want to define user home directories in the root filesystem supplied by
IBM. What we have done is created a automount managed directory in the
sysplex root called /home that all user filesystems get mounted off from.
Then from any system in the sysplex, the user is accessing the same filesystem
from all systems.
here is my sysplex tree structure at the highest level. &version in BPXPRM
maps to &SYSR1 the SYSRES - in our case RS* packs, then we have a few other,
like vendor sysres (VS*), we automount NFS mounts, and then have system
specific mount points (TEC*) that system specific stuff hangs off from.
TEC1:$ ls -al
total 200
lrwxrwxrwx 1 OMVSKERN OMVSGRP 9 Jun 4 2013 $SYSNAME -> $SYSNAME/
lrwxrwxrwx 1 OMVSKERN OMVSGRP 9 Jun 4 2013 $VERSION -> $VERSION/
drwxr-xr-x 24 OMVSKERN OMVSGRP 8192 Dec 15 07:28 .
drwxr-xr-x 24 OMVSKERN OMVSGRP 8192 Dec 15 07:28 ..
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Jun 4 2013 ...
drwxr-xr-x 5 OMVSKERN OMVSGRP 8192 Jun 6 2013 NFS
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Dec 11 2013 RSM01A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Dec 11 2013 RSM02A
drwxr-xr-x 14 OMVSKERN OMVSGRP 8192 Dec 21 08:05 RST01A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Jun 6 2013 RST02A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Aug 12 2013 RST03A
drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Jun 6 2013 ServiceCICS
drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Jun 6 2013 ServiceDB2
drwxr-xr-x 3 OMVSKERN OMVSGRP 8192 Aug 26 2020 ServiceQREP
drwxr-xr-x 8 OMVSKERN OMVSGRP 8192 Jan 14 14:10 TEC1
drwxr-xr-x 9 OMVSKERN OMVSGRP 8192 Sep 19 2018 TEC2
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Aug 27 2013 VSM01A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Aug 27 2013 VSM02A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Aug 27 2013 VSM03A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Aug 27 2013 VST01A
drwxr-xr-x 6 OMVSKERN OMVSGRP 8192 Jan 14 09:56 VST02A
drwxr-xr-x 6 OMVSKERN OMVSGRP 8192 Jan 14 09:56 VST02A
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Aug 27 2013 VST03A
drwxr-xr-x 53 OMVSKERN OMVSGRP 8192 Aug 26 2020 altroot
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 bin -> $VERSION/bin
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 dev -> $SYSNAME/dev
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 etc -> $SYSNAME/etc
dr-xr-xr-x 36 OMVSKERN TTY 0 May 20 08:49 home
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 lib -> $VERSION/lib
drwxr-xr-x 2 OMVSKERN OMVSGRP 0 Jun 19 2014 null
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 opt -> $VERSION/opt
lrwxrwxrwx 1 OMVSKERN OMVSGRP 25 Jun 6 2013 remote ->
$SYSSYMA/NFS/&ENV./remot
lrwxrwxrwx 1 OMVSKERN OMVSGRP 16 Jun 4 2013 samples ->
$VERSION/samples
drwxr-xr-x 4 OMVSKERN OMVSGRP 8192 Dec 10 10:56 shared
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 tmp -> $SYSNAME/tmp
lrwxrwxrwx 1 OMVSKERN OMVSGRP 10 Jun 6 2013 u -> $SYSNAME/u
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 usr -> $VERSION/usr
lrwxrwxrwx 1 OMVSKERN OMVSGRP 12 Jun 4 2013 var -> $SYSNAME/var
lrwxrwxrwx 1 OMVSKERN OMVSGRP 15 Aug 27 2013 vendor -> $SYSSYMA/&VNDV1
TEC1:$
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
