If you are having communications issues, you can see some of the internal comms messages that are generated by iCluster behind the scenes to assist in problem resolution. Just create a new message queue on the node that appears to be having the problem called DMKMSGQ in the iCluster product library (almost always ICLUSTER).
CRTMSGQ MSGQ(ICLUSTER/DMKMSGQ) MSGQFULL (*WRAP)
Then after a period of time, use DSPMSGQ DMKMSGQ to display the messages and send them to support. You can keep the message queue active if you like or delete it once the problem is solved.
The following two tabs change content below.
iCluster Tech Tuesday
iCluster TechTuesday is a set of posts covering technical tips and techniques to help get the most out of your Rocket iCluster installation.
Latest posts by iCluster Tech Tuesday (see all)
- iCluster and Mobility Part 4: Deploying the Mobile Monitor - July 28, 2015
- iCluster and Mobility Part 3: Apache Tomcat for Dummies - July 21, 2015
- iCluster and Mobility Part 2 Getting Started - July 14, 2015
No comments yet.