|
|
Natural should be able to detect the problem with having the MF value and the static generation value different and either
1. automatically adjust in some fashion
2. at least, give a message that identifies the problem,
so we don't have to spend 2 months trying different things to identify the problem
Many thanks for this request, It have been delivered via FIX.
https://getsupport.softwareag.com/browse/SI-460535
related incident and linked channel and itrac are in the ticket.
We do have an incident - SI-460535 NAT3700 after upgrading
The DB2 MF>0 was put into the Development regions with a prior upgrade, but it didn���t make it into the production build. Apparently, in development, they didn���t prepare programs for static execution, so no issues were reported. When we upgraded Production from Nat911 to Nat912, we also picked up the DB2 MF>0, and production programs started failing, so the upgrade had to be backed out. It took 2 months of experimenting in development to recreate the issue and determine that it was related to DB2 MF>0.
Thanks,
Jay Baucher
Technology Consultant, MF Database Management System Support
DXC Technology
T +1.470.754.9174
M +1.419.422.7578
Jay.Baucher@dxc.com
DXC.COM
[cid:image001.png@01D85885.22591DF0]
Hello Jay, thank you for submitting this idea.
We will need some more information about your idea so we can validate it.
Did you already have an incident on this idea? if yes, could you please share the incident number?
When did you find the missing information? Is it during the binding process?
Any additional information would be helpful.