You might want to post the contents of your BPXPRMnn members being
activated at IPL from each system. Just from looking at the error messages,
I would guess that you are running with a SYSPLEX(YES) in the BPXPRMnn
member of PARMLIB. This would mean a three part UNIX root. The sysplex
root, the version root (/Z113h mountpoint), and the system root (/S0W2
mountpoint). I further guess that your z/OS 2.1 system has entries of these
in it's version of the active BPXPRMnn member. Which means that the 1.13(?)
system root and version root are mounted on your z/OS 2.1 system. On my
system, I have two systems in a sysplex with SYSPLEX(YES) UNIX. The root
entries look like:
/* sysplex root */
ROOT FILESYSTEM('OMVS.SYSPLEX.&SYSPLEX..ROOT.ZFS')
TYPE(ZFS)
AUTOMOVE
MODE(READ)
/* version root */
MOUNT FILESYSTEM('OMVS.&SYSR1..ROOT')
TYPE(ZFS)
MODE(READ)
AUTOMOVE
MOUNTPOINT('/$VERSION')
/* system specific root */
MOUNT FILESYSTEM('OMVS.SYSTEM.ROOT.&SYSNAME..ZFS')
TYPE(ZFS)
MODE(RDWR)
UNMOUNT
MOUNTPOINT('/&SYSNAME.')
I am also guessing that instead of something like &SYSNAME. you have the
actual "hard coded" system name, maybe S0W2? And the "hard coded" version
name instead of /$VERSION (which is a type of symbolic even though it
doesn't really look like it).
Again, posting your BPXPRMnn members, the ones being activated at IPL, for
each system would be very helpful.
On Fri, Dec 5, 2014 at 11:24 AM, Frank Chu <[email protected]> wrote:
> Hello,
>
>
>
> I am trying to set up sysplex based on the zPDT starter system between zOS
> 2.1 and zOS 1.13. Everything generally works except when attempting to
> mount various OMVS/zFS datasets on the second system I bring up. Both
> systems have their own volumes containing their own OMVS/zFS system, so I'm
> not attempting to mount a single dataset on two different systems.
>
>
> After zVM and zOS 2.1 has been brought online, I IPL zOS 1.13. Everything
> goes until the zFS/OMVS starts. Then I get around 10 of the following
> messages:
>
>
> N 4020000 S0W2 14333 19:37:00.97 STC00206 00000090 IOEZ00046E Error 129
> received while attaching aggregate ZFS.Z21H.FONTS
> M 4000000 S0W2 14333 19:37:01.05 00000090 BPXF221I FILE SYSTEM
> ZFS.Z21H.FONTS 265
> D 265 00000090 FAILED TO 4 LOCALLY.
> D 265 00000090 RETURN CODE = 00000081, REASON CODE = EF1869CD
> D 265 00000090 THE FILE SYSTEM IS ACCESSIBLE ON THIS SYSTEM THROUGH
> E 265 00000090 A MOUNT ON A REMOTE SYSTEM.
>
>
> N 4020000 S0W2 14333 19:37:01.76 STC00206 00000090 IOEZ00046E Error 129
> received while attaching aggregate CSQ800.ZFS
> M 4000000 S0W2 14333 19:37:01.85 00000090 BPXF221I FILE SYSTEM CSQ800.ZFS
> 267
> D 267 00000090 FAILED TO MOUNT LOCALLY.
> D 267 00000090 RETURN CODE = 00000081, REASON CODE = EF1869CD
> D 267 00000090 THE FILE SYSTEM IS ACCESSIBLE ON THIS SYSTEM THROUGH
> E 267 00000090 A MOUNT ON A REMOTE SYSTEM.
>
>
>
>
> All the messages refer to datasets at are only available to the zOS 2.1
> system. They are not being mounted on the zOS 1.13 system and I don't want
> them to be. The RETURN CODE indicates that the "file was not found", does
> that mean I should mount the z2.1 dasd volumes in zOS 1.13?
>
>
>
>
>
> I'm also getting messages on the zOS 1.13 system indicating that the file
> system it is attempting to mount is already mounted. Which doesn't make
> sense. IBM doc says to correct the error in BPXPRMxx but I don't see
> anything wrong with it and the zOS 1.13 system IPLs just fine by itself
> with this BPXPRMxx member.
>
>
>
> BPXF237I FILE SYSTEM ZFS.ADCD113H.SYSTEM 326
> WAS ALREADY MOUNTED ON PATHNAME
> /S0W2.
>
>
>
> BPXF237I FILE SYSTEM ZFS.Z113H.VERSION 327
> WAS ALREADY MOUNTED ON PATHNAME
> /Z113H.
>
>
>
>
>
>
> Any ideas or suggestions?
>
>
> Thanks
> Frank
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Development Programmer
> ColeSoft Marketing
> www.colesoft.com
> Phone : 540.456.6164
> Email : [email protected]
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
The temperature of the aqueous content of an unremittingly ogled
culinary vessel will not achieve 100 degrees on the Celsius scale.
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
