The following is a list of typical errors that can be observed
when working with CIM:
- Error:
BPXP014I ENVIRONMENT MUST
REMAIN CONTROLLED FOR DAEMON (BPX.DAEMON) PROCESSING.
BPXP015I
HFS PROGRAM /usr/lpp/wbem/provider/<provider_library> IS NOT MARKED
PROGRAM CONTROLLED.
- The provider <provider_library> is not marked program controlled.
When or where seen: Messages on the
console.
Solution: Mark the
dynamic load library /usr/lpp/wbem/provider/<provider_library> as
program controlled by using the command extattr +p <fully
qualified dynamic load library name>. Restart the CIM server and
try again.
- Error: CIM_ERR_ACCESS_DENIED
-
Access to a CIM resource was not available to the client:
"Not authorized to run <name of a CIM operation> in the namespace
root/PG_Internal"
When or where seen: Client
application / Details in the CIM server trace log
Solution: Permit the user ID to execute a configuration command with CONTROL access to Security profile CIMSERV in class WBEM.
- Error: CIM runtime environment user ID requires CONTROL
access to profile CIMSERV in class WBEM.
-
When or where seen: The CIM server error
log after CIM server fails to start
Solution: The CIM server startup
fails because the CIM server user ID fails to have CONTROL access
to profile CIMSERV in class WBEM. Grant the CIM server user ID CONTROL access to profile CIMSERV in class WBEM.
- Error: CIM runtime environment user ID requires either READ access to BPX.SERVER or it must be user ID 0.
-
When or where seen:The CIM server error
log after CIM server fails to start
Solution: Either
permit the user ID READ access to BPX.SERVER if BPX.SERVER
is set up, or run the command under a privileged user ID (UID 0).
- Error: CFZ17201W: ACCESS IS NOT ENABLED
FOR REMOTE USERS WITH SUPERUSER AUTHORITY.
-
When or where seen: On
the client side.
Solution: The
remote client uses a local user with UID=0. However, the CIM server is
configured to reject remote access if the local user is a super-user
(parameter enableRemotePrivilegedUserAccess=false). If
you want to enable the local user with remote privileged access, then
switch the parameter to true. Otherwise, change the local user to
a non-super-user by setting the UID ≠ 0.
- Error:
CFZ10033E: The CIM
server is not started:
CFZ00409E: Bind failed:
CFZ07801E: CIM HTTP or HTTPS connection failed to create
the socket.
-
When or where seen: CIM server startup
console messages
Solution: The CIM server cannot
start because it fails to listen on one of the ports 5988 (for http)
or 5989 (for https). Either the CIM server is already running, another
server is listening on one of these ports, or the ports have been
blocked by the TCP/IP configuration.
The httpPort and httpsPort CIM server configuration
properties define the HTTP port and HTTPS port numbers (see CIM server configuration).
See Configuring the ports for the CIM server for more information.
- Error: HTTP Error (401 Unauthorized)
-
When or where seen: Client application
Solution: The user authentication failed. The client
application either did not provide user ID and password on a request
at all, or the supplied user ID and password are not valid for the z/OS system
on which the CIM server is running.
Permit the user ID to execute
a client request with at least READ access to Security
profile CIMSERV in class WBEM. Check the server log for a detailed
error report.
- Error: ICH14080I
-
Warning: RACF® detected
a possible error in the dynamic class descriptor table, entry WBEM,
error code 01. The class is available for further processing. The
class name does not contain a national character nor a number. To
assure IBM® does not create an
IBM-defined class in the future by this same name, you should choose
a class name which contains at least one national character or a number.
When or where seen: RACF setup of dynamic class WBEM
Solution: Ignore
the warning.
- Error:
ICH408I USER(CFZSRV)
GROUP(CFZSRVGP)
NAME(####################)
CL(PROCESS )
INSUFFICIENT
AUTHORITY TO NEWJOBNAME
-
When or where seen: Message
on the console.
Solution: Grant the CIM server user
ID READ access to profile BPX.JOBNAME in class FACILITY
to be allowed to set the job name of the out-of-process agent to CFZOOPA
(see Running providers in separate address spaces).
- Error: IEF450I CFZCIM - ABEND=S1C7 U0000
REASON=FFFF0006
-
When or where seen: Message on the
console.
Solution: Look for CSV042I and
ICH422I program control messages. CSV042I message points out the module
to be marked as program controlled. If no CSV042I and ICH422I messages
occur contact IBM Service.
Example:
CSV042I REQUESTED MODULE BLSUXTID NOT ACCESSED.
THE MODULE IS NOT PROGRAM CONTROLLED
ICH422I THE ENVIRONMENT CANNOT BECOME UNCONTROLLED.
CSV028I ABEND306-42 JOBNAME=CFZCIM STEPNAME=
BPXP014I ENVIRONMENT MUST REMAIN CONTROLLED FOR
DAEMON (BPX.DAEMON) PROCESSING.
IEF450I CFZCIM - ABEND=S1C7 U0000 REASON=FFFF0006 TIME=14.16.12
- Error: JGP00001W: Number of Instances
Exceeded Threshold
- This error message might be issued at enumeration of IBMzOS_Job
instances, when the number of instances to be enumerated is greater
than a configured limit. This limit has been defined to prevent the
CIM server from resource exhaust.
It is recommended to change your
enumeration to a subset of IBMzOS_Job.
To query the current
limit of the IBMzOS_Job provider, receive the IBMzOS_JobsManagementSettings
instance of the CIM server. The property MaxInstances contains
the currently defined limit.
To change the limits, set the property MaxInstances to a new value by modifying the IBMzOS_JobsManagementSettings
instance.
cimcli mi
IBMzOS_JobsManagementSettings.InstanceID=\"IBMzOS:JobsManagementSettings\"
MaxInstances=<new_value>
- Client Side Error: CIM_ERR_ACCESS_DENIED
-
Access to a CIM resource was not available to the
client: "EDC5139I Operation not permitted."
When
or where seen: Client application / Details in the CIM server trace
log
Solution: Permit the CIM server runtime
environment user ID as surrogate for the requesting client user ID
to use the command: PERMIT BPX.SRV.<client uid> CL(SURROGAT)
ID(<CIMServer UID>) ACCESS(READ)
- Client side error: HTTP Error (413 Request
Entity Too Large)
- There wasn't enough memory available to the client to successfully
read the entire response from the server into memory.
When or where seen: Client application, like for
instance cimivp.
Solution: Allow
the client to use more memory. If the application runs within a JOB,
increase the REGION size. If the client runs from a UNIX System Services shell, increase the ASSIZEMAX
value in the OMVS segment of the user running the shell.