Common Tops log messages (0201) | DNC Logs 17 |
0002/001A Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] but could not. The entry definition in [Sending_PRU_name] was not found, OR push/pull was invoked when not in entry. User action is required.
Description: The sending PRU could not communicate with the receiving
PRU because the software version in each were not the same.
Action: The user must reinstall both PRUs from the load tape. If the problem persists, then contact NT.
0002/001B Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] but could not. The result was a communication failure.
Description: The sending PRU can not communicate with the receiving PRU because the receiving PRU is not there. It is the responsibility of the sending PRU to recover from the error or to declare itself faulty.
Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, document the problem, restart both sending and receiving PRUs, and then contact NT.
0002/001C Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] but could not. The result was that the location address of the receiver was invalid.
Description: The sending PRU could not communicate with the receiving PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then document the problem, and restart both sending and receiving PRUs. If necessary, restart the SRUs in which both PRUs reside. Record all action taken, and then contact NT.
0002/001D Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] but could not. The result was an interval timer error.
Description: The sending PRU could not communicate with the receiving PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.
Action: If the PRU is in the working state, no action is required. If the PRU is in the faulty state, then document the problem, and restart both sending and receiving PRUs. If necessary, restart the SRUs in which both PRUs reside. Record all action taken, and then contact NT.
0002/001E Message: [Sending_PRU_name] was trying to communicate with [Receiving_ PRU_name] but could not. The problem is the sender [Sending_PRU_name] could not obtain control blocks. User action is required.
Description: The sending PRU could not communicate with the receiving PRU. It is the responsibility of the sending PRU to recover from the error by resending the message or to declare itself faulty.