OMJDBNET in the F98611

Michael L.

Well Known Member
List,

Last week we had a very peculiar issue in that one of our five iSeries 400 partitions running J.D. Edwards services became unusable in that the services weren’t able to communicate with our Production Enterprise server. The reason being is that 9 of our 92 data sources (four of them our shared data sources) in the Data source Master table (F98611) somehow had the OMJDMNET field changed from an ‘N’ to a ‘Y. Once we figured this out, changed the field back to ‘N’, everything functioned correctly.

Has anybody had a similar issue and if so any idea(s) how this field in this table could be changed from a ‘N’ to a ‘Y’?

Thanks in advance for any ideas.

811 SP1, 8.98.3.3, IBM i 7.1, WAS 6.1
 
I have run into this before. Usually this is a residual from starting out with JDBNET somewhere on a data source in planner.

Later on down the road somebody runs another planner and it updates all of F98611 and F986101.

Check JDEPLAN for the culprit.
 
Back
Top