rgz
Active Member
Found this in the new iseries redbook...
especially for AS/400, but will also aid other platforms:
5.5.3 Check kernel setting
While the Enterprise Server is running, it passes messages between the
network jobs and the kernel jobs. By default, the network job will verify
that each of the call object kernels is running, every 10th time it sends or
receives a message. J.D. Edwards has released an enhancement in SAR #5128281
with SP16.1, which enables you to customize this verification to occur less
frequently. This change reduces the amount of overhead within the Enterprise
Server and improves the overall response time. You can choose to check for a
kernel’s health every 1,000 times there is a message or, say, 5,000 times
there is a message; the trade-off is performance versus prompt knowledge of
a kernel problem. While you do want to continue to monitor your kernels, if
you have a heavy load of transactions, you might consider increasing this
number to have it check for kernel health less frequently. In the [JDENET]
section, add the new line, checkKrnlHealth with the value that you choose,
as in the example below.
100 user example:
[JDENET]
checkKrnlHealth=1000
especially for AS/400, but will also aid other platforms:
5.5.3 Check kernel setting
While the Enterprise Server is running, it passes messages between the
network jobs and the kernel jobs. By default, the network job will verify
that each of the call object kernels is running, every 10th time it sends or
receives a message. J.D. Edwards has released an enhancement in SAR #5128281
with SP16.1, which enables you to customize this verification to occur less
frequently. This change reduces the amount of overhead within the Enterprise
Server and improves the overall response time. You can choose to check for a
kernel’s health every 1,000 times there is a message or, say, 5,000 times
there is a message; the trade-off is performance versus prompt knowledge of
a kernel problem. While you do want to continue to monitor your kernels, if
you have a heavy load of transactions, you might consider increasing this
number to have it check for kernel health less frequently. In the [JDENET]
section, add the new line, checkKrnlHealth with the value that you choose,
as in the example below.
100 user example:
[JDENET]
checkKrnlHealth=1000
