There are global configuration considerations for Unix System Services and the security server (RACF) when implementing the OAM file system support. Utilizing the OAM file system support requires that the OAM address space be started. As a result, the security server (RACF) must be configured to allow the OAM address space to access files and directories in the Unix file system hierarchy as described in Security configuration for the file system. To facilitate this use of Unix System Services by the OAM address space, resources associated with the OAM address space must be factored into your planning for Unix System Services configuration. This resource-related Unix System Services configuration can be accomplished through Unix System Services and, in some cases, the security server (RACF). In general, Unix System Services parameters can be set in a BPXPRMxx PARMLIB member and these values can also be changed dynamically with the SETOMVS or SET OMVS operator commands. BPXPRMxx is described in z/OS MVS Initialization and Tuning Reference and dynamically changing values in BPXPRMxx is described in z/OS UNIX System Services Planning; SETOMVS and SET OMVS are described in z/OS MVS System Commands. Consult your security server (RACF) documentation (for example, z/OS Security Server RACF Command Language Reference) for Unix System Services related configuration. Note that the security server (RACF) settings override the BPXPRMxx settings.
| BPXPRMxx keyword | Security Server (RACF) keyword | Description | Configuration for OAM |
|---|---|---|---|
| System Level Settings | |||
| MAXPROCSYS(nnnnn) | N/A | Maximum number of processes that the system allows. | OAM may require up to 20 additional processes. |
| MAXUIDS(nnnnn) | N/A | Maximum number of z/OS Unix user IDs that can operate concurrently. | OAM requires 1 additional user ID. |
| MAXFILESIZE(nnnnn|NOLIMIT) | N/A | Maximum file size that a process can create. | OAM requires a value equivalent to the largest value your installation has used for the MOS= specification on the IEFSSNxx member of PARMLIB (up to 2000M as of z/OS V1R10), or NOLIMIT. |
| Process Level Settings | |||
| MAXPROCUSER(nnnnn) | PROCUSERMAX | Maximum number of processes that a single z/OS UNIX user ID can have concurrently active. | OAM may require up to 20 additional processes. |
| MAXFILEPROC(nnnnnn) | FILEPROCMAX | Maximum number of descriptors for files, directories, etc. that a single process can have concurrently active or allocated. | OAM requires a value of at least 4. |
OAM should not be started until the required file system infrastructure is in place. The file system infrastructure must persist for as long as OAM is running.