Friday, 24 July 2015

More on RTE and the fix for yesterdays problem

An update on this.

To fix, you generally need to choose a unique net listener port for the RTE net listener and then change the RTE OCM’s to point to that port.  You then need to reset the OCM cache for the kernels.

To change the service entry port

, I goto P90701A

image

From here choose the Server Map’s and System’s for the machines that will need to change (anything that is going to do an RTE lookup).  Then change the RTE mapping to the correct port.

For some reason I had to delete the old entries and add new ones, could not make inactive and copy…

Secondly, the cache reset to the network kernels start looking to the right RTE server for message delivery.

To reset the cache From WSJ, goto form advanced choose the server from the list below

image

Choose the server and then

image

Choose the reset cache row exit

Then the cache that you want to reset

image

All done, messages should go to the right port for RTE and everything will start to behave nicely.

Extending JDE to generative AI