Troubleshooting
This appendix describes frequently occurred errors and their solutions.
-
Failed to get the structure size.
Cause
Occurs when the target module’s input/output structure has not been compiled and Dlupdated.
Action
Check if the target module’s input/output structure has been compiled and Dlupdated normally.
-
Cannot find the structure property.
Cause
Occurs when the target module’s input/output structure has been deleted.
Action
Check if the target module’s input/output structure has been deleted.
-
Service parameter table inquiry error.
Cause
Occurs when Tx code has not been entered in pfm_sm_ext and pfm_svc_ext.
Action
Check if the service’s physical name and Tx code have been entered in pfm_sm_ext and pfm_svc_ext.
-
ProFrame error occurred. [The input struct length registered in Mapper and the returned set_data length are different.]
Cause
Occurs when failed to change meta registered in a structure.
Action
Check if meta registered in a structure has been changed. If changed, compile or Dlupdate the changed structure, or recover the structure and then compile or Dlupdate it.
-
[WEBT-1105][000000] socket connection timeout [TPETIME:13]
Cause
Occurs when the port number defined in TestFrameWorkConfig.jsp is not the same as that of Tmax server. Or, Tmax server is not connected.
Action
Set the port number defined in TestFrameWorkConfig.jsp and that of Tmax server identically.
TestFrameWorkConfig.jsp is located in the following path.
$JEUS_HOME/webhome/app_home/pfmdevsvr/webAdmin/TestFrameWorkConfig.jspCheck if Tmax server boots.
-
Cannot find TX_CODE.
Cause
Occurs when Tx code has not been inserted into the PFM_SVC table.
Action
Check if the service’s Tx code has been inserted into the PFM_SVC table.