I'm in a non-data-sharing shop which went to V11CM about four
months ago. We had a couple of problems, but nothing specifically
attributable to NFM. If you use Websphere or any similar
external-connect products, you should already have run into most of
1) Particularly, check the Java JDBC module class and level to make
sure that you're running Type 4 calls to DB2. Type 3 are deprecated
and most are obsolete-incompatible. Also,
2) If you have date-partitioned tables for which you SELECT
LIMITKEY FROM SYSIBM.SYSTABLEPART, be aware that after any ALTER to
the LIMITKEY, or any creation of new date-partitioned tables or new
partitions for existing tables... the new LIMITKEY values for these
dates will have delimiting apostrophes (single quotes), but
unaltered partitions will still have un-delimited date values. The
STRIP() function helps re-standardize the data.
We didn't spend more than the minimum time in ENFM and encountered
no problems; and we did a -STOP DB2 and a -START DB2 when going to
NFM. Again, no problems. Hope this helps.
From: MARTIN, MIKE [mailto:[login to unmask email]
Sent: Tuesday, January 16, 2018 3:46 PM
To: [login to unmask email]
Subject: [DB2-L] - DB2 z/OS - enabling NFM
We have been running V11 CM for several months now. (Our migration
from V10 went smoothly)
We are now preparing for NFM. I have a few questions...
* Is there any danger of existing application code having problems
when we go to NFM? We will not be taking advantage of new V11
features, just continuing to run what had been running in V10 and
is now successfully running in V11 CM.
* Is there any reason to run in ENFM for a while before going to
* If we have to fallback to CM* is this the same as CM (as far as
the applications are concerned) ? I understand we cannot fallback
to V10 from CM*.
* Any need to restart our DB2 subsystems for any of this? (say like
after running job DSNTIJNG which reassembles/links a module?)
Any other tips/gotchas are greatly appreciated. We are z/OS V11 CM
without data sharing.
This email may contain confidential and privileged material for the
sole use of the intended recipient. If you are not the intended
recipient, please contact the sender and delete all copies. Any
review or distribution by others is strictly prohibited. Personal
emails are restricted by policy of the State Employees' Credit
Union (SECU). Therefore SECU specifically disclaims any
responsibility or liability for any personal information or
opinions of the author expressed in this email.
-----End Original Message-----
**This e-mail, including any attachments, may be confidential,
privileged, or otherwise legally protected. It is intended only for
the addressee. If you received this e-mail in error or from someone
who was not authorized to send it to you, do not disseminate, copy,
or otherwise use this e-mail or its attachments. Please notify the
sender immediately by reply e-mail and delete the e-mail from your