MVSFORUMS.com

[djf]

Question.

We are preparing to upgrade to z/OS 1.8

Current environment is z/OS 1.6 running DB2 V8


Now when DB2 was generated, we had the foresight (if you can call it that) to catalog all the DSN810 datasets, etc in a certain catalog. Just for example, we called the cat CAT.UDB

Now when we ran the DSNZPARM gen, the high level on the catalog parm was DB2DAT. We aliased that hlq to a different catalog, CAT.DB2DAT

Can I, for reasons of testing under z/OS 1.8, keep the pointer to the DSN810 and gen a new DSNZPARM with a different cat parm, and alias that to a third catalog?

The it would pick up new BSDS's and new DSNDB06 stuff and all the DB2 data files it creates would have a different HLQ and we can test simultaneously while production is up.

I have already run two DB2 subsystems in the same LPAR using this approach, I am just curious about it and wonder if there are any pitfalls.

Thanks!

[videlord]

You can run several DB2 subsystem in one MVS image, but be careful about the central storage usage.

I think you are talking about ICF user catalog. Why you think it's related to DSNZPARM? They are total different thing. You can change to any ICF user catalog.
When you create a new DB2 subsystem, you can decide use a new ICF user catalog or share with old one.
And current ICF catalog can be splitted if you want.

[djf]

Because in the DSNZPARM gen there is a statement CATALOG=XXXXXXXX

And whatever you specify as XXXXXXXX becomes the high level qualifier of all the datasets DB2 creates