OnDemand for z/OS V7R1 and DB2 V8 New Function Mode

[Jon.Bauer@bcbsks.com]

We have been having db2 locking issues since we migrated to DB2 V8 Compatibility Mode.  We were told by IBM that this would be corrected by going to DB2 V8 NFM and binding the ODBC package with the REOPT(ONCE) option, but we are still getting the locking.  Has anyone ran into this issue when going to DB2 V8 and running Content Manager OnDemand for z/OS V7R1?  Thanks, Jon

[hakan_carlberg]

Hi,

We're running with REOPT(NONE), as seen from syspackage for DSNCLINF.
And we're not having any problem.

But  we're a little backlevel (UK06883) for ODBC, since we're in the process of upgrading to V9

Regards
/Carlberg

[Jon.Bauer@bcbsks.com]

Thanks for responding...  Do you know if DSNCLINF was bound with a specific ISOLATION option or was it left to default to RR?  Thanks for your time, Jon

[hakan_carlberg]

The DSNCLINF was bound with ISOLATION (space/not supplied)  pointing to the PLAN which is bound witt
ISOLATION=RR
/Carlberg