Troubleshooting Interprocess Communications

This subsection explains how to troubleshoot problems that can occur with Interprocess Communication (IPC).

Issue	Resolution
JD Edwards EnterpriseOne jobs cannot communicate with one another with these symptoms: The PORTTEST program fails. The security server on the IBM i fails. UBE submissions fail. If you activated ipcTrace in the [JDEIPC] section of the server jde.ini file, an error similar to this should appear in the JDEDEBUG.log: IPC2100017 createIPC Msgq (name Port6005) failed, errno=3484: A damaged object was encountered	This could be because the IBM i release is pre-V4R2. In these releases, damaged IPC message queues might result when you end JD Edwards EnterpriseOne jobs using the command ENDJOB* IMMED. Use the CNTRLD option to end an IBM i job. Note:* You might still have damaged IPC message queues if the IBM i-controlled ending times out. Run these program to verify whether a damaged message queue exists. You must have V4R1 PTF# SF45946. CALL QPOZIPCS PARM('-aqE') This program generates a spool file called IPCS that contains information about message queues on the system. Look for these output: KEY MODE 0x00000000 -------- 0x00000000 --RW------- 0x00000000 --RW------- 0x00000000 --RW-------- 0x00001234 D-RW----RW- In this example, the message queue 0x00001234 is damaged. To fix, stop, and restart JDENET using these commands: ENDNET CLRIPC STRNET Also, if the ipcTrace setting in the [JDEIPC] section of the jde.ini file on the server is not set, activate the setting and run the PORTTEST program to determine whether any message queues are damaged. Look for the word damage in the JDEDEBUG.log file. Note: Some of the message queues might be damaged even if the JDEDEBUG.log file does not indicate that any damage exists.

Issue

Resolution

JD Edwards EnterpriseOne jobs cannot communicate with one another with these symptoms:

The PORTTEST program fails.
The security server on the IBM i fails.
UBE submissions fail.

If you activated ipcTrace in the [JDEIPC] section of the server jde.ini file, an error similar to this should appear in the JDEDEBUG.log:

IPC2100017 createIPC Msgq (name Port6005) failed, errno=3484: A damaged object was encountered

This could be because the IBM i release is pre-V4R2. In these releases, damaged IPC message queues might result when you end JD Edwards EnterpriseOne jobs using the command ENDJOB* IMMED.

Use the *CNTRLD option to end an IBM i job.
Note: You might still have damaged IPC message queues if the IBM i-controlled ending times out.
Run these program to verify whether a damaged message queue exists. You must have V4R1 PTF# SF45946.

CALL QPOZIPCS PARM('-aqE')

This program generates a spool file called IPCS that contains information about message queues on the system. Look for these output:

KEY MODE

0x00000000 --------

0x00000000 --RW-------

0x00000000 --RW--------

0x00001234 D-RW----RW-

In this example, the message queue 0x00001234 is damaged. To fix, stop, and restart JDENET using these commands:

ENDNET

CLRIPC

STRNET

Also, if the ipcTrace setting in the [JDEIPC] section of the jde.ini file on the server is not set, activate the setting and run the PORTTEST program to determine whether any message queues are damaged. Look for the word damage in the JDEDEBUG.log file.

Note: Some of the message queues might be damaged even if the JDEDEBUG.log file does not indicate that any damage exists.