UniAccess Server Issues Trace File shows “Failed in function [mmopen] in UAMM”

Knowledge Base: UniAccess Server Issues

Problem: The following error appears in the UniAccess Trace File: “Failed in function [mmopen] in UAMM, pid [pid #], other info [7] in trace file”.
Solution: This error indicates that a PID is not able to initiate with UAMM (i.e., mmopen). Any attempt to open a PID will result in a UAMM error 7, which is unable to allocate a MMPROC. There are two situations that can cause a UAMM process (mmproc) to hang:
If UniAccess aborts the connection and does not receive an abort confirm [see the Unisys OS 2200 Communications Management System (CMS 1100) Programming Reference Manual], the PID and mmproc will remain busy. Some cases in which UniAccess will attempt to abort the connection are when a PID is terminated with the operator keyin (UACS TERM PID,)are when UACS is terminated with active PIDs, and when a connection timeout (COMSRV CONTIMOUT parameter) occurs. If a transaction errors without the UniAccess contingency routine getting control, the mmproc will remain busy. (For example, a transaction may error prior to connecting to the UniAccess Fixed-gate subsystem–UAFG.) If this situation occurs, a print file should be created for the erring transaction.
Since the UAMM process slots are maintained in UAFG, they are not released when UACS is terminated. Therefore, hung mmprocs can collect over time. The only way to release the hung mmproc is by deactivating the UniAccess Fixed-gate subsystem and reloading it. (See the UniAccess System Administration Guide for information on activating, deactivating, and reinitializing UAFG.) Note that the number of UAMM process slots is defined by the PROCCNT parameter of the UAMM configuration statement.

Knowledge Base: UniAccess Server Issues