m: "Dennis Longnecker"
To: IBM-MAIN@bama.ua.edu
Sent: Tuesday, May 19, 2009 3:52:34 PM GMT -08:00 US/Canada Pacific
Subject: Re: PDSE Anomaly?
Exactly right two monoplex LPARS.
In my situation on
LPAR 1 DB2PROD.SDSNLOAD is cataloged on SYS033
LPAR 2 DB2PROD.SDSNLOAD is cataloged
du
Date:
05/19/2009 07:01 PM
Subject:
Re: PDSE Anomaly?
Sent by:
IBM Mainframe Discussion List
Exactly right two monoplex LPARS.
In my situation on
LPAR 1 DB2PROD.SDSNLOAD is cataloged on SYS033
LPAR 2 DB2PROD.SDSNLOAD is cataloged on SYS033
On LPAR 1, I copied a load module from
On Tue, 19 May 2009, Longnecker, Dennis wrote:
> Exactly right two monoplex LPARS.
>
> In my situation on
>
> LPAR 1 DB2PROD.SDSNLOAD is cataloged on SYS033
> LPAR 2 DB2PROD.SDSNLOAD is cataloged on SYS033
>
> On LPAR 1, I copied a load module from DSN910.SDSNLOAD to the
> DB2PROD.SDSNLOA
: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Linda Mooney
Sent: Monday, May 18, 2009 3:36 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: PDSE Anomaly?
Hi Dennis,
Mark is right in his comments. This could be bad if you are in a sysplex. In
my response I was assuming two mon
da Pacific
Subject: Re: PDSE Anomaly?
Hi Dennis,
We have to watch out for this too. If you have a same name dataset on two
different lpars and the alias is related to one user catalog one one lpar and
to a different user catalog on the other lpar, you will see this behavior as
each lpar w
: IBM-MAIN@bama.ua.edu
Sent: Monday, May 18, 2009 1:53:48 PM GMT -08:00 US/Canada Pacific
Subject: PDSE Anomaly?
On my test lpar I applied some DB2 maintenance to a module. I could browse
the module and indeed the fix was on.
On my production LPAR, I wanted to copy that module over to the product
lib
On Mon, 18 May 2009 13:53:48 -0700, Longnecker, Dennis
wrote:
>On my test lpar I applied some DB2 maintenance to a module. I could
browse the module and indeed the fix was on.
>
>On my production LPAR, I wanted to copy that module over to the product
libraries, so I did a TSO =3.3 copy and plac
On my test lpar I applied some DB2 maintenance to a module. I could browse
the module and indeed the fix was on.
On my production LPAR, I wanted to copy that module over to the product
libraries, so I did a TSO =3.3 copy and placed it in the production load
library. I browsed that productio
8 matches
Mail list logo