Problems during configuration

This topic provides troubleshooting tips for resolving problems related to the configuration and setup of z/OSMF.

Troubleshooting topics are included for the following problems and scenarios:

IZUSEC job fails with an authorization failure for the issuer
A z/OSMF script fails because no z/OS UNIX processes are available
You receive message EDC5134I: Function not implemented
RACDCERT or another RACF command abends during configuration.

A problem in the configuration of z/OSMF might be indicated by error messages from the common event adapter (CEA) component of z/OS®. For a description of configuration-related CEA reason codes, which might be useful in diagnosing problems in your z/OSMF setup, see Common event adapter (CEA) reason codes.

IZUSEC job fails with an authorization failure for the issuer

Symptom: The job IZUSEC fails with an authorization failure message for the z/OSMF issuer’s user ID.

Possible Cause: Your installation uses the RACF® PROTECT-ALL option to protect its data sets, but you did not define the CEA.* RACF profile.

Corrective Action: If your installation uses PROTECT-ALL, you must define a CEA.* data set profile to RACF and permit CEA and the z/OSMF installer user ID. For example:

ADDSD 'CEA.*' UACC(NONE) 
PERMIT 'CEA.*' ID(CEA) ACCESS(ALTER) 
PERMIT 'CEA.*' ID(USER-ID) ACCESS(ALTER)

A z/OSMF script fails because no z/OS UNIX processes are available

Symptom: A script fails with a message indicating that no z/OS UNIX processes are available for the user ID that was used to run the script.

Possible Cause: The user ID exceeds the MAXPROCUSER setting for your system. MAXPROCUSER specifies the maximum number of z/OS UNIX processes that a single user can have active concurrently. Typically, an installation sets a system-wide limit through the MAXPROCUSER setting in the BPXPRMxx member of parmlib, and then sets higher limits for individual users and processes through PROCUSERMAX, a value in the OMVS segment. Though z/OSMF by itself does not add significantly to the number of z/OS UNIX processes for the user, the MAXPROCUSER setting can be reached when the user is also running a number of other processes on the system besides z/OSMF.

Corrective Action: Use the RACF ADDUSER or ALTUSER command (or an equivalent command for your security product) to specify a PROCUSERMAX value for the user ID that is higher than the MAXPROCUSER setting. Try adding 20 to the value that is currently specified through the MAXPROCUSER setting.

Suppose, for example, that your installation has specified a MAXPROCUSER value of 80 in the BPXPRMxx member. Here, you would set the PROCUSERMAX value for this user ID to 100, to allow a greater number of processes for the user ID. For example:

ALTUSER USER-ID OMVS(PROCUSERMAX(100))

If the problem persists, repeat this process by increasing the PROCUSERMAX value by an additional 20, taking care not to exceed any limits that are appropriate for your installation; check with your security administrator.

You receive message EDC5134I: Function not implemented

Symptom: You receive the following message and error code:

atoe_getcwd error: EDC5134I Function not implemented. (errno2=0x052C04DC)

Possible Cause: The error code indicates that the system root directory is not mounted. However, this message is also issued if the OMVS home settings for a user ID include a root directory (/) specification, but the user ID does not have access to the root directory.

Corrective Action: Verify that the system root directory is mounted and that the user ID OMVS home settings are correct.

RACDCERT or another RACF command abends during configuration

Symptom: A RACF command abends with code S684 or code 047 during the configuration process. On checking the script log, you find a message such as the following:

Script izutsoz.rexx returned with reason code -1668

Possible Cause: The RACF command is not defined in AUTHCMD section of your active IKJTSOxx parmlib member.

Corrective Action: Verify that the IKJTSOxx member defines the required RACF commands. See the list of IKJTSOxx parmlib updates in the z/OS Program Directory. The AUTHCMD section of member IKJTSOxx should list RACDCERT and a number of other RACF commands. You can update the IKJTSOxx member dynamically through the TSO command: PARMLIB UPDATE(xx) where xx is the correct suffix.