I am posting this here for the benefit of others who are thinking of upgrading to Predict v441. Maybe this will also drive some changes.
We upgraded from v422 to v441, but it was painful. Since we were jumping 2 releases, we did not attempt the inplace conversion but rather did an unload and load. Even though the data passed consistency check, it died on the load’s consistency check, and this was over objects loaded for other SAG products (i.e., Natural Process DB object, SAG-** DDMs, etc.). Why??? When we were able to load everything in, we lost DDMs that pointed to databases other than DBID=0.
Here’s my advice… if you jump from v42 or lower to v44, order all the intermediary releases and do (multiple if necessary) inplace conversions! These went smoothly in comparison and we had no problems afterward. At least none relating to conversion.
Which leads me to my next point. Predict v44 is bad! Any files with D or T format fields generates a change when you do GEN AF! The fields are already 4 or 7 bytes long, but Predict thinks it must issue the ADADBS CHANGE for them. This is painful when the field is fixed width and Adabas says “no way Jose”. Is there a fix coming for this??
Predict v44 also has other problems. A mismatch between SYSDIC & FDT for type A, SYSDIC-EL has 2 different groups with same group name but with different elements. This shouldn’t be.