Thanks all for the info. We're a simple 2 LPAR Monoplex (3rd Linux soon) and
I didn't explain myself well on one point - a problem I suffer from :)...
I too believe in keeping it simple. It was a mistake/poor choice in creating
my initial IODF with a SYS1 HLQ. The SYS0 HLQ we previously used was i
We have two IODF's for our entire shop, and run mulitple sysplexes
(unfortunately). While we're looking toward merging systems, we will continue
to have a test (sandbox) and PPRC watchdog systems that are logically
separate from our production sysplex, but share gadgets (we do not have the
fun
On Fri, 30 May 2008 15:07:44 -0700, Jerry Whitteridge
<[EMAIL PROTECTED]> wrote:
>As you can't share datasets outside of a sysplex boundary (safely) I'd
>like to know how you do that.
>
1) This is VSAM. PDSE and HFS can't be shared across sysplex
boundry.
2) Sharing datasets between systems pre
>As you can't share datasets outside of a sysplex boundary (safely) I'd like to
>know how you do that.
First: I didn't say it; the OP did (and, I admit -- I missed that).
Second: MIM allows it.
Third: I have only once run more than one SYSPLEX at a site.
Fourth: Sorry, if I confused anybody. But,
As you can't share datasets outside of a sysplex boundary (safely) I'd
like to know how you do that.
On Fri, 2008-05-30 at 22:04 +, Ted MacNEIL wrote:
> >We run multiple Sysplexes on a single CEC and use common IODF files, but a
> >seperate physical copy for each one.
>
> I always have disli
>We run multiple Sysplexes on a single CEC and use common IODF files, but a
>seperate physical copy for each one.
I always have disliked maintaining multiple copies of something you have to
keep in synch!
I have always maintained one IODF copy at a time.
-
Too busy driving to stop for gas!
--
On Fri, 2008-05-30 at 15:50 -0500, Johnston, Robert E wrote:
>
> So, from the same work IODF, I created a prod SYS1.IODF05 and a prod
> SYS0.IODF05 and wrote them to 2 different IOCDS's in the z9. I did a
> hardware
> and software activate on Prod using SYS1.IODF05. Activate was
> successful and
I think you are making things a little more complicated than they should be.
I would use the same IODF for all systems. This would cause the IODF to be
shared. One benefit is that an error which affects one system can be fixed
from the other system.
I have a HLQ for my IODF which keeps it out o
rsity Medical Center
Senior System Programmer
(312) 942-8386
[EMAIL PROTECTED]
"Johnston, Robert E" <[EMAIL PROTECTED]>
Sent by: IBM Mainframe Discussion List
05/30/2008 03:50 PM
Please respond to
IBM Mainframe Discussion List
To
IBM-MAIN@BAMA.UA.EDU
cc
Subject
IODF questions
We converted from a z800 to a z9BC in February (z/OS 1.7). We had been using
a shared SYS0 IODF for years, but when I created the IODF for the z9 I used
SYS1 from the PROD z800 LPAR (thinking keep it separate). This SYS1 IODF was
used to create the z9 IOCDS, which was used to POR the z9 and IPL the
10 matches
Mail list logo
