UniAccess Server Issues Hung PID

Knowledge Base: UniAccess Server Issues

Problem: There are a number of situations that may result in hung PIDs. The hung PID may initially be identified as a problem connecting additional client applications or as the result of a UACS STATUS keyin. The most common of these situations are:

  • UACS TERM PID,<pid> does not terminate the PID, but it places the PID in an ERROR state.
  • UACS successfully schedules a UASL transaction, but the transaction does not execute.
  • UACS successfully schedules a UASL transaction, but the transaction error terminates prior to performing the TDINIT call.
  • The client application terminates without notifying the server.
Solution: Both the client and server side of a UniAccess transaction must be closed to release a PID. There are a number of configuration parameters that can detect a potential hung PID and automatically resolve the problem. These parameters are:

  • CONTIMOUT on the COMSRV statement
  • KEEPALIVE on the COMSRV statement
  • NWRTIMOUT on the COMSRV statement
  • NWWTIMOUT on the COMSRV statement.

When it becomes necessary to terminate a PID using the UACS TERM PID,keyin, always follow with a UACS STATUS PID, keyin to ensure that the connection was properly closed. If the PID has not closed, a second UACS TERM PID, keyin is required. The UniAccess Trace File, with traces on HIGH, will provide information that is useful in determining the cause of hung PIDs.

Knowledge Base: UniAccess Server Issues