PMDF System Manager's Guide

In order to send a message, PMDF needs to read configuration files and create message files in the PMDF message queue directories. Configuration files must be readable to the user, which generally implies world read access on the files in the PMDF table directory. During installation, proper protections are assigned to these files. PMDF utilities and procedures which create configuration files also assign proper protections. If the files are reprotected by the system manager or other privileged user or through some site-specific procedure, PMDF can not be able to read configuration information. This will result in "File open" errors or unpredictable behavior. The pmdf test -rewrite utility will report additional information when it encounters problems reading configuration files. See pmdf test -rewrite for information on using this utility.

If PMDF appears to function from privileged accounts but not from unprivileged accounts, then file protections in the PMDF table directory are likely to blame. Check the protections on configuration files and their directories. The only files that should be protected against world read access in the table directory are the queue cache database and PhoneNet script files or other channel option files which can contain password information.

"File create" errors usually indicate a problem while creating a message file in a PMDF message queue directory. See Section 34.2.2 for procedures to aid in diagnosing file creation problems.