Giving daemon authority to vendor-written programs

If you are writing a program that uses z/OS UNIX services to change user identity (such as using setuid and seteuid and so forth), you should refer to Setting up the UNIX-related FACILITY and SURROGAT class profiles to determine whether your program's use of these services requires it to have DAEMON authority.

If you determine that your program requires DAEMON authority, then you need to do the following:

Document the requirement to assign a user ID to the daemon which has a UID of 0.
Document the requirement to permit the daemon to the BPX.DAEMON FACILITY class profile.
Document how to start the daemon from /etc/rc or as a started procedure.
The main program and all programs that it loads must be marked program controlled in the file system or be loaded from an MVS™ program controlled library. For more information about marking programs program-controlled, see Customizing the system for IBM-supplied daemons. For more information about placing your programs into MVS libraries, see Moving z/OS UNIX executables into the LPA. This section describes steps to move a program into LPA; similar steps can be followed to move a program into a system linklist library or a step library. If you decide to use MVS libraries, you need to also see Steps for defining programs from load libraries to program control.