Tracking down problems when setting up daemons and servers

This section describes possible problems you might encounter when setting up daemons and servers.

This table lists the problems that you might encounter when setting up daemons and servers.

Problem	Reference
A user or daemon is not properly defined with an OMVS segment.	Verifying the user OMVS segment
A group is not properly defined with an OMVS segment.	Verifying the group OMVS segment
A module that is not defined to program control was loaded into the daemon's address space.	Using external links to access MVS load libraries
The daemon module is coming from the file system. The sticky bit might be off or the program might not be in the MVS™ search order.	Verifying that the sticky bit is on and Using external links to access MVS load libraries
The executable file being loaded from the file system does not have the program control extended attribute set.	Finding modules that were not defined to program control
The file system containing a program control executable file was mounted with the NOSETUID option. This makes the entire file system uncontrolled.	Finding modules that were not defined to program control
The daemon does not have READ or higher permission to BPX.DAEMON.FACILITY.	Checking the daemon authority
The server does not have READ or higher permission to BPX.SERVER.FACILITY.	Checking the server setup
The in-storage data that is managed by RACF® might be out of date.	Refreshing RACF in-storage data
The server might not have been defined to the BPX.SRV.uuuuuuuu SURROGAT class profile.	Checking the SURROGAT class profile