Why Does JDENET_K Keep Open Data Paths?

[InHoc]

Can anybody help explain why the JDENET_K jobs keep open hundreds of data paths? Sometimes notice the number of open data paths grows to over 700 per job/kernel before services are restarted each day.

Not closing tables would seem to interfere with performance, lead to memory leaks or interfere with file pointers with multiple users per job/kernel?

Running XE/WTS 'W' environments with ALL BSFN's on iSeries AS/400. One user per kernel, but planning to change for up to 5 users per kernel.

Your input is greatly appreciated!

 

[altquark]

ok - first of all, we need to talk. Your use of the "W" environment is flawed, and there are many reasons why you're having so many open paths. More than likely, you've got an issue - the kernels should be closing the paths after use, and in your case you've obviously entered into a known CNC issue.

 

[Tom_Davidson]

Jon,

Is there a patch that will force the JDE kernels to close the paths. I regularly have kernels that have > 10K ODP's. It has done this since time immorial.

Tom

 

[InHoc]

Hi Jon, thanks for your reply. I should clarify that the 'W' environments have BSFN's mapped to the server as the DEFAULT. But there are approx. 400 individual BSFN's that are mapped LOCAL. Most of the "business" related BSFN's are mapped to the server (ex. B4200310, B4200311, etc. are defaulted to the server, where B98xxxxx's, etc. are mapped LOCAL).

Could you please explain the known CNC issue...where the kernels don't properly close the open data paths...what is the cause...and what to do about it.