MVSFORUMS.com

[djf]

Hello.

We are trying to run DB2 V8 and DB2 V5 in the same LPAR.

V5 is the default in the linklist. The install for V8 went fine.

We added the V8 subsystem entry with the SETSSI command.

V8 is getting abend 0D7's in module DSNAPRHX, which is part of DSN3EPX.
DSN3EPX is the module referenced by subsystem initialization.

I am starting to think that you can have only one flavor of DSN3EPX on the system, and it must be the latest and greatest.
Does anybody know more about this?

[kolusu]

djf,

I think you need an APAR PQ48486 to have 2 versions of DB2 on the same LPAR.

http://blogs.ittoolbox.com/database/db2zos/archives/v8-compat-mode-what-about-coexistence-6163

Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[djf]

K,

Thanks much. Do you know if it will support V8 and V5?
It seems everything is oriented towards running V8 and V7/V6.

If you're not sure, no biggie, we will be talking to support center soon.

regards,
djf

[djf]

K,

Thanks, but I'm pretty sure that's not it. We are not doing a migration, the goal is to have two separate DB2 regions running... One V8 and one V5. No catalog sharing, no data sharing, no stogroup sharing. Simple DB unloads from V5 and reloads into V8.
IBM says it should work, but it looks like V8 doesn't like the V5 version of DSN3EPX, which is some kind of subsystem communication module.

I'm just hoping either the V8 version supports V5, or we can rename the V8 version to something else and initialize his subsystem with that name.

[CICS Guy]