-Original Message-
From: Robin Sandlin
Sent: Monday, October 12, 2015 1:43 PM
To: 'IBM Mainframe Discussion List' <IBM-MAIN@LISTSERV.UA.EDU>
Subject: RE: IOEZ00807I when OMVS initializes at Disaster Recovery site
Hi Dave,
We're trying to teach some of our Java programmers M
Searched the archives and saw others had this issue, but never saw a good
answer.
We recently implemented ZFS file sharing for the first time here.
We run GDPS/XRC to replicate our dasd from HQ to DR site and then often "flash"
the farm to a set we can IPL our recovery system from.
Because
r/o at the live site.
>
> Kind Regards,
>
> Rajesh
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Dave Butts
> Sent: Thursday, October 08, 2015 11:40 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Su
Seems like they should be able to create a BPX parm to tell OMVS to ignore the
check.
Very frustrating.
We may need to pursue mounting just what we need to IPL to a base level, and
mount the rest after as you suggest.
Thanks,
Dave
On Thu, 8 Oct 2015 11:21:09 -0500, Dave Butts wrote:
>Seems like they should be able to create a BPX parm to tell OMVS to ignore the
>check.
>Very frustrating.
>We may need to pursue mounting just what we need to IPL to a base level, and
>mount the rest after as you
@LISTSERV.UA.EDU] On Behalf
Of Dave Butts
Sent: Thursday, October 08, 2015 11:40
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IOEZ00807I when OMVS initializes at Disaster Recovery site
Searched the archives and saw others had this issue, but never saw a good
answer.
We recently implemented ZFS file sharing
UA.EDU] On
> Behalf Of Dave Butts
> Sent: Thursday, October 08, 2015 8:40 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IOEZ00807I when OMVS initializes at Disaster Recovery site
>
> Searched the archives and saw others had this issue, but never saw a good
> answer.
>
> We rece
the file systems at the
time of the flash copy.
FWIW,
Bart
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Dave Butts
Sent: Thursday, October 08, 2015 12:21
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IOEZ00807I when OMVS initializes
We use the following setup to circumvent this to some degree:
We start OMVS with parms of (TH,FS,ZS)
BPXPRMTH contains the Threshold values etc.
BPXPRMFS contains the FileSystem definitions - ZFS, CINET etc.
BPXPRMZS contains the mounts for those ZFS datasets supplied as part of z/OS -
no
Agreed. We will be pursuing opening a request to IBM for sure.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Thanks, Bart.
In my pmr with IBM, they confirmed that ensuring those match are not enough to
guarantee it will avoid the wait.
Here is what IBM told us:
--
Just finished discussing this with my defect folks and unfortunately
using the same SYSNAME and SYSPLEX name on the
I submitted my vote for the RFE.
--- dbutt...@gmail.com wrote:
From: Dave Butts <dbutt...@gmail.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IOEZ00807I when OMVS initializes at Disaster Recovery site
Date: Thu, 8 Oct 2015 14:12:57 -0500
Thanks, Bart.
In
ERV.UA.EDU] On
> Behalf Of Dave Butts
> Sent: Thursday, October 08, 2015 11:40
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: IOEZ00807I when OMVS initializes at Disaster Recovery site
>
> Searched the archives and saw others had this issue, but never saw a good
> answer.
>
> We
In
,
on 10/08/2015
at 03:14 PM, Mike Schwab said:
>I made this comment on the RFE. Perhaps it should be a new RFE.
>For the MOUNT command and in SYS1.PARMLIB(BPXPRMxx), add a NOWAIT and
>/ or DEFER
: IOEZ00807I when OMVS initializes at Disaster Recovery site
Thanks, Bart.
In my pmr with IBM, they confirmed that ensuring those match are not enough to
guarantee it will avoid the wait.
Here is what IBM told us:
--
Just finished discussing this with my defect folks
15 matches
Mail list logo