It looks like most of the datasets the system is complaining about are
in their own user catalogs. I should be able to connect the user
catalog to the master catalog on the zOS 1.13 side and be ok.
Tho there is one that is cataloged in the z2.1's master catalog. I may
have to just
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,
Are both z/OS 2.1 and 1.13 running as guests under z/VM?
Lizette
-Original Message-
From: Frank Chu fr...@colesoft.com
Sent: Dec 5, 2014 10:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Setting up a sysplex and OMVS/zFS
Hello,
I am trying to set up sysplex based on the zPDT starter
Yep. zVM 6.2
Frank
On 12/5/2014 12:29 PM, Lizette Koehler wrote:
Are both z/OS 2.1 and 1.13 running as guests under z/VM?
Lizette
-Original Message-
From: Frank Chu fr...@colesoft.com
Sent: Dec 5, 2014 10:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Setting up a sysplex and OMVS
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
Hi John,
There's 3 entries that uses a hard coded mount point, everything else
including the system root and version root are mounted using symbolics.
BPXPRM for zOS 1.13:
MAXASSIZE(1073741824)
MAXPROCSYS(200)
MAXPROCUSER(100)
MAXUIDS(200)
MAXFILEPROC(400)
MAXPTYS(256)
On Fri, Dec 5, 2014 at 12:05 PM, Frank Chu fr...@colesoft.com wrote:
Hi John,
There's 3 entries that uses a hard coded mount point, everything else
including the system root and version root are mounted using symbolics.
​Well, I was totally off-base. Those members look right to me. Like
Hi Frank,
Using tso bpxmtext EF1869CD
Description: Error with issuing a LOCATE call on an HFS-compat aggregate.
Action: Verify that the dataset is properly cataloged and that the catalog is
available
Hi Doug,
Ok, so I need to make the z2.1 dasd volumes that contains the datasets
to be mounted available to the zOS 1.13 system. How would I catalog the
z2.1 datasets in zOS1.13? I haven't found a way to catalog those zFS
datasets.
Any ideas?
Frank
On 12/5/2014 2:33 PM, Doug Henry
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Frank Chu
Sent: Friday, December 05, 2014 2:10 PM
Hi Doug,
Ok, so I need to make the z2.1 dasd volumes that contains the datasets to be
mounted available to the
zOS 1.13 system. How would I catalog the
z2.1
On Fri, Dec 5, 2014 at 2:09 PM, Frank Chu fr...@colesoft.com wrote:
Hi Doug,
Ok, so I need to make the z2.1 dasd volumes that contains the datasets to
be mounted available to the zOS 1.13 system. How would I catalog the z2.1
datasets in zOS1.13? I haven't found a way to catalog those zFS
Hi Frank,
I am aware of 3 ways to solve this problem.
(1) - Ignore the error because these zfs's don't have anything to do with V1R13
(2) - Rename them to have an HLQ on SYS1 and then use IDCAMS DEFINE RECATLOG
in the V1R13 catalog
(3) - We use an EOM product that allows us to update the
It looks like most of the datasets the system is complaining about are
in their own user catalogs. I should be able to connect the user
catalog to the master catalog on the zOS 1.13 side and be ok.
Tho there is one that is cataloged in the z2.1's master catalog. I may
have to just ignore
13 matches
Mail list logo
