A customer had set the LMFCOMM environment variable indicating a custom location for the LMF long-lived named pipe, as described in the documentation in the section "Relocating the Long-lived Named Pipe" in the Development System Licensing Guide Chapter 2, Administering the License Management Facility.  The customer had set this environment variable in each user's .profile, as well as setting it in /etc/mflmrcscript, so each time the machine booted, and the LMF license manager was started, the named pipe would be created in the location specified by LMFCOMM, but they sometimes still received the error LMF - 010: Unable to contact license manager. But if the LMF manager stopped, and they manually re-started it using the command "mflmman" from the operative LMF directory, then the error message occurred again, because LMFCOMM had not been set prior to the execution of, or inside, the "mflmman" script.

The solution was to modify the "mflmman" script, adding the correct specification of LMFCOMM, and then whenever the script was run manually, LMFCOMM would be set and the LMF - 010 error would no longer occur.