Re: PDSE Anomaly?

On Mon, 18 May 2009 13:53:48 -0700, Longnecker, Dennis
<Dennis.Longnecker@xxxxxxxxxxxxx> 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 placed it in the production load
library. I browsed that production load library, and the fix was not on.
I browsed the original library, and the fix was not on. The original
library is cataloged to the same volume (usercat), so I know it was pointing
to the same place.


Are the 2 systems in the same sysplex? If not, did you do the 3.3 copy from
test to prod on the prod system or the test system? If they aren't in the same
sysplex, then you can really get yourself in trouble here if you did the
copy from the test system (write to prod from test as opposed to read from
test on prod).

Is PDSESHARING set to normal or extended? Are both system set up the
same way? This question assumes they are both in the same sysplex.


I tried LLA, refreshes, inactivating LLA, and even IPL'ing, but could not
see the fix on the load libraries from my production LPAR (still looked good
in test).


Is the library in the LNKLST on either system? Which one(s)? Is it in
LLA on either system? A library can be in LLA without being in LNKLST.

Finally, on the TSO =1 screen, I entered the dataset name AND the volser
and then I could see that the fix was on. I went out and went back in
without specifying the volser, and the fix was STILL on.

It appears it was cached or something, even through an IPL....? Any
suggestions?


Something... but not sure what. Most likely a user error of some kind.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zelden@xxxxxxxxxxxx
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • Re: COBOLs Influence on C
    ... environment that relies on having scads of libraries that must be ... Deployment to production is controlled by a third group: ... Then fix the real problem rather than ranting about how it is everyone ... third party, which calls C from another third party. ...
    (comp.lang.cobol)
  • Re: Vista
    ... It's sort of like going back and modifying the "2am fix" to standardize it with the rest of the code. ... Especially dealing with the DRM fixes, it could be that someone left an inefficient tight loop in one of the libraries. ... A man who believes in a God he doesn't see, ...
    (comp.lang.cobol)
  • Re: Simulink crashes in R2007a on linux
    ... Also, looking at those error messages, it looks like libxft1 should ... post on this thread which has a fix for a glibc problem that worked ... font libraries, and that looks like what your error is saying, so ...
    (comp.soft-sys.matlab)
  • Configure script fails when building many ports (e.g. mozilla, spacehulk)
    ... Same error whether using make or portupgrade. ... In which case what do I put where to fix it. ... Is it because my libraries got screwed / optimised or whatever? ... Is it "something to do with pthreads" as the config.log output seems ...
    (freebsd-questions)