The CIM server is unable to bind the socket.

None.

The reason for the bind failure is described in the subsequent message.

Report this problem to your system programmer.

The value that was specified for the configuration property is not valid. See CIM server configuration for the correct values of configuration properties.

None.

None.

Re-enter the command specifying a correct value for the configuration property.

The configuration property name cannot be changed dynamically for a running CIM server. Instead the change has to be made as a planned value to become effective after a CIM server restart. See cimconfig or MODIFY console command for details on how to change planned values.

None.

None.

Change the planned configuration value and restart the CIM server.

The mentioned configuration property is no longer supported.

The CIM server ignores this setting and continues.

Please remove the mentioned configuration property from the planned configuration of the CIM server's
/etc/wbem/cimserver_planned.conf.

None.

A provider module was registered with a UserContext value of value, but that value is not supported by this version of the CIM server. Valid values are 2 for "Requestor" and 3 for "Designated User".

The provider module is not registered.

Check the provider registration MOF and replace the invalid UserContext value with a value that is valid on z/OS.

Contact your system programmer.

A provider module was registered with a UserContext value of 3 ("Designated User"). The user ID of the designated user has to be specified in DesignatedUserContext, but no value was found (see PG_ProviderModule).

The provider module is not registered.

Check the provider registration MOF and add a valid user ID for the DesignatedUserContext property to all provider modules that are registered with a UserContext value of 3.

Contact your system programmer.

A CIM-XML operation exceeds the server's memory.

Stop the CIM-XML operation.

Look for message CFZ08101E identifying the source of the CIM-XML request. Contact the owner of the application issuing the request and analyze the reason for the size of the operation. Limit the result objects for this request. Restart the server to clean it up.

Contact your system programmer.

The user ID that invoked CIM operation operation is not authorized to run this operation in namespace namespace of the CIM server.

The CIM request is denied.

Check the system console for further detailed error messages that indicate which authorization is missing for user user-ID. In most cases, the user has no UPDATE authority for profile CIMSERV in class WBEM.

Contact your system administrator for obtaining the required level of authorization.

The command that was entered in the system console is not supported by the CIM server.

None.

None.

None.

The CIM server received the STOP command from the console.

The CIM server is shutting down.

None.

None.

The CIM server cannot start the thread handling commands issued at the console. For a description of error error-text with error number error-number and the last four digits of the reason code X'reason-code', see z/OS® UNIX System Services Messages and Codes, or enter the reason code in the BPXMTEXT TSO command.

None.

The CIM server cannot be stopped using the console command. To stop the CIM server, purge the address space or use a privileged UNIX user ID to issue the command cimserver -s from the UNIX System Services command prompt.

Contact your system programmer.

The CIM server is connected to the system console by using the Console Communication Service. The CIM server received the unrecoverable error error-text. For a description of error error-text with errno error-number and the last four digits of the reason code X'reason-code, see , or enter the reason code in the BPXMTEXT TSO command.

CIM server shuts down.

Errno error-number and the last four digits of the reason code X'reason-code' point out the reason for the error. Check the console for more messages indicating the problem.

None.

A MODIFY command was entered for the CIM server that could not be recognized due to invalid syntax.

None.

None.

Enter the command with the correct syntax.

This messages describes the expected format for CIM server MODIFY command.

None.

None.

None.

The CIM server failed to update a configuration value that was entered through the system console.

None.

Look for other messages indicating the problem.

Look for other messages indicating the problem.

A configuration value for a running CIM server has immediately been updated. The changed value will stay in effect as long as the CIM server is running. After a restart the value is reset to either the default or to the planned configuration value.

The change requested by the MODIFY command is now in effect.

None.

None.

A configuration value has been updated for the planned configuration of the CIM server. It will become active after the CIM server is restarted. This change is persistent until the planned value is changed again.

The change requested by the MODIFY command becomes effective after the next CIM server restart.

None.

None.

The change requested by the MODIFY command will not be in effect until the CIM server is restarted.

None.

None.

None.

A configuration update requested through the MODIFY command failed. The detailed cause is indicated by message.

None.

None.

None.

The configuration property name is not recognized by the CIM server as a valid configuration property.

None.

None.

Use the correct name for the configuration property and enter the command again.

When you have issued the MODIFY APPL=ENV command, this message displays the current list of all environment variables that are active for the CIM server address space along with their current values.

None.

None.

None.

When you have issued the MODIFY APPL=ENV,variable-name command, this message displays the current value of the environment variable specified by variable-name.

None.

None.

None.

When you have issued the MODIFY APPL=ENV,variable-name command, this message indicates that no environment variable with the name variable-name is defined in the CIM server address space.

None.

None.

None.

The CIM server was unable to create a socket.

None.

Check the PORT and PORTRANGE statements in the PROFILE.TCPIP configuration file to ensure that the ports specified by the httpPort and httpsPort CIM server configuration properties are accessible by the CIM server. Check the security product configuration to ensure that the CIM server is able to access the ports specified by the httpPort and httpsPort CIM server configuration properties.

For example, OEM security product ACF2 may require "Stack & Port security authorization" for the CIM server. Use the TCP/IP NETSTAT ALLCONN PORT command to check for servers using the ports specified by the httpPort and httpsPort CIM server configuration properties.

Example:

TSO NETSTAT ALLCONN (PORT 5988

Report this problem to your system programmer.

Before listening on network port port-number the CIM server failed to bind the socket with error-code and 0xreason-code. It therefore will not be able to communicate over this network port. Probably the port is already in use by another program or has been reserved by the TCP/IP configuration.

The CIM server does not start.

Error code error-code and the last four digits of the reason code 0xreason-code point out the reason for the error.

For a description of error error-text with error code error-code and the last four digits of the reason code 0xreason-code, see z/OS UNIX System Services Messages and Codes, or enter the reason code in the BPXMTEXT TSO command.

None.

The CIM server is not able to set the permission on socket file socket for local communication.

The CIM server does not start.

Error codeerror-code and the last four digits of the reason code 0xreason-code point out the reason for the error. For a description of error error-text with error code error-code and the last four digits of the reason code 0xreason-code, see z/OS UNIX System Services Messages and Codes, or enter the reason code in the BPXMTEXT TSO command.

None.

The CIM server failed to listen on socket socket-number. It therefore will not be able to communicate over this network port. Probably the port is already in use by another program or has been reserved by the TCP/IP configuration.

The CIM server does not start.

Error codeerror-code and the last four digits of the reason code 0xreason-code point out the reason for the error. For a description of error error-text with error code error-code and the last four digits of the reason code 0xreason-code, see z/OS UNIX System Services Messages and Codes, or enter the reason code in the BPXMTEXT TSO command.

None.

The CIM server or a CIM client could not connect to a CIM indication listener or CIM server on host:port.

None.

None.

Check that the target of the connection is a valid hostname, IP connectivity exists to that host and that a CIM indication listener or a CIM server is listening on port of the target system.

An unrecoverable error occurred during the communication with the client connected by IP-address.

The connection is closed.

This message provides the affected IP address. Look for a previous CFZ message describing details of the internal error.

Contact your system programmer.

The TCP/IP stack used by the CIM server is not available.

The CIM server is waiting for a restart of the TCP/IP stack. The CIM server will be not able to handle any commands and requests until the restart of the TCP/IP stack has completed. Currently processed requests are terminated.

Restart the TCP/IP stack the CIM server was using. If this stack is no longer used, restart the CIM server.

None.

The CIM server detects that another instance of the CIM server is already running. There can be only one running CIM server.

None.

Do not start the CIM server again. If you want to start a new CIM server on the system, use the stop command at the system console (/p cfzcim ) or look for the CIM server running in the UNIX System Services (/d omvs,a=all ) and cancel the process (/c cfzcim).

None.

The CIM server is starting up and will listen on port port-number for incoming requests from clients. For information about how to configure the CIM server's HTTP connections see CIM server configuration.

None.

None.

None.

The CIM server is starting up and will listen on port port-number for incoming requests from clients using SSL encryption. Please note that special TCP/IP configuration settings are required for enabling the CIM server to support SSL encryption for HTTPS. For information about how to configure the CIM server's HTTPS connections see Configuring the CIM server HTTPS connection using AT-TLS.

None.

None.

None.

The CIM server is starting up and will listen for incoming requests from clients. For information about how to configure the CIM server's HTTP connections see CIM server configuration.

None.

None.

None.

The CIM server is now started and accepts CIM client requests.

None.

None.

None.

The CIM server is now stopped. CIM client requests are no longer accepted.

None.

None.

None.

The CIM server was not started due to an error condition described in subsequent message.

The CIM server is not started.

See the error condition as described in the subsequent message.

Report this problem to your system programmer.

The CIM server repository contains files tagged with the wrong CCSID. The CIM server tried to set the right CCSID (ISO8859-1) tag on this file, but was not successful.

The CIM server stops.

Look for previously issued messages (CFZ10035E or equivalent LE messages) about access violations for path /var/wbem. Grant the denied access right to the user ID running the CIM server. Restart the CIM server.

None.

The CIM server is not able to change the file tag for the file file-name. For the reason, see the system error number error-number and the system error message error-message.

The CIM server stops.

Correct the reason for failing to change the file tag. The reason is indicated by the system error number error-number and the system error message error-message.

None.

The CIM server was able to restore the correct CCSID (ISO8859-1) file tag for a number of number repository files.

None.

Repository file tags were missing or wrong. Please revise procedures handling files located in /var/wbem to preserve file tags. If file tags are preserved, this message will not be displayed again.

None.

The CIM server is not able to open the directory repository-directory containing the repository.

The CIM server does not start.

Error code error-code and the last four digits of the reason code 0xreason-code point out the reason for the error. For a description of error error-text with error code error-code and the last four digits of the reason code 0xreason-code, see z/OS UNIX System Services Messages and Codes, or enter the reason code in the BPXMTEXT TSO command.

None.

The subscription request for a CIM indication failed because there is no CIM indication provider that accepts the query contained in the indication filter. Either the filter contains an invalid or unsupported query, or an error has occurred during subscription processing.

The indication subscription fails and the subscription is not persistent on the CIM server.

Check the z/OS console for other error messages that indicate the cause of the subscription failure.

Check the query in the indication filter and make sure this query is supported by the target CIM server. If the problem persists contact the system programmer of the target system.

During startup the CIM server has failed to re-establish a persistent CIM indication subscription because there is no CIM indication provider that accepts the query contained in the indication filter. Either the filter contains an invalid or unsupported query, or an error has occurred during subscription processing.

The subscription name is inactive.

Check the z/OS console for other error messages that indicate the cause of the subscription failure. Correct the error(s) and then restart the CIM server.

None.

The CIM server was unable to deliver a CIM indication to a subscribed indication listener. See message-details for the potential cause.

The CIM indication is not delivered and discarded.

Ensure the destination system of the indication subscription is available and reachable. To remove obsolete indication subscriptions use the cimsub command (see cimsub).

None.

The CIM server runs on a system with Enhanced Security and thus does not load dynamic libraries which are not audited by a system programmer.

The system does not load the named dynamic library.

Set the program control flag on the dynamic library using the UNIX System Services command extattr +p <filename>.

Contact a system programmer to audit the dynamic library and set the program control flag.

The CIM server detected an incomplete security setup.

The CIM server does not start.

Complete the security setup by defining the profile CIMSERV in class WBEM. Refer to CIM server security setup for further details.

Contact your system programmer.

The CIM server user ID must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be a privileged user.

The CIM server stops.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

The CIM server loaded a dynamic library that is not program controlled. Either the security setup is not complete or a dynamic library has been changed without a system programmer's audit.

The CIM server stops.

Check all dynamic libraries for their program control flag and ensure that no library changed. Make sure that the Language Environment® libraries SCEERUN and SCEERUN2 are program controlled.

Contact your system programmer.

The CIM server user ID must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be privileged.

The CIM server stops.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

The CIM server user ID must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be privileged.

The CIM server stops.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

The CIM server has loaded a dynamic library that is not program controlled. Either the security setup is not complete or a dynamic library has been changed without a system programmer's audit.

The CIM server stops.

Check all dynamic libraries for their program control flag and ensure that no library has changed. Make sure the Language Environment libraries SCEERUN and SCEERUN2 are program controlled.

Contact your system programmer.

A request sent from the user ID could not be processed. The CIM server does not have access to act as surrogate for the requesting user ID.

The user request is ignored and an error message is sent to the client.

To permit the CIM server user ID to act as a surrogate for the client user, grant the user ID running the CIM server READ access to the RACF® profile BPX.SRV.user-ID as described in Switching identity (surrogate).

Contact your system programmer.

The CIM server was not able to delete the thread level security built for a specific request.

None.

None.

None.

The user ID that starts the CIM server must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be a privileged user.

The CIM server does not start.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

The CIM server loaded a dynamic library that is not program controlled during startup. Probably the security setup is not complete or a dynamic library has been changed without a system programmer's audit.

The CIM server does not start.

Check all dynamic libraries for their program control flag and ensure that no library changed. Make sure the Language Environment libraries SCEERUN and SCEERUN2 are program controlled.

Contact your system programmer.

The user ID that starts the CIM server must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be a privileged user.

The CIM server does not start.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

The CIM server detected an incomplete security setup on startup.

The CIM server does not start.

To complete the security setup, define the profile CIMSERV in class WBEM. Refer to CIM server security setup for further details.

Contact your system programmer.

The CIM server user ID requires CONTROL access to security profile CIMSERV in CLASS WBEM.

The CIM server does not start.

To permit the CIM server user ID to perform administrative CIM tasks, give it CONTROL permission to profile CIMSERV in class WBEM. Refer to CIM server security setup for further details.

Contact your system programmer.

A provider defined a security profile at registration that is not defined for RACF class WBEM.

None.

Create the RACF profile in class WBEM and permit users who should have access to the provider.Verify if the security profile is defined for RACF and make sure that the class WBEM has been refreshed. Verify if the provider really should be registered with the mentioned security profile and if it should be checked.

Contact your system programmer.

User user-ID is not authorized to perform CIM operation operation involving the provider provider-name. The user needs access-type access to SAF security profile profile-name that is defined in class WBEM.

The request is not processed and an "Access Denied" notification is sent to the client.

Verify if the user should be permitted to perform the current request. If so, grant the user access-type access to the profile profile-name.

None. Access has been denied to a user with insufficient authority.

The CIM server user ID must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be a privileged user.

The CIM server stops.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

None.

The security component of the CIM server detected an invalid operation context that does not contain a username.

The request is not processed and an "Access Denied" notification is sent to the client.

None.

None.

During startup, the CIM server received the unrecoverable error error-text. For a description of error error-text with error number error-number and the last four digits of the reason code 0xreason-code, see , or enter the reason code in the BPXMTEXT TSO command.

The CIM server does not start.

Error number error-number and the last four digits of the reason code 0xreason-code point out the reason for the error. Check the console for more messages indicating the problem.

Contact your system programmer.

The provider agent determined that the Must Stay Clean flag was not set. The provider agent startup is not processed by the CIM server.

The provider agent does not start.

Ensure that the provider agent can only be started by the CIM server.

Contact your system programmer.

During startup, the provider agent received the unrecoverable error error-text. For a description of error error-text with error number error-number and the last four digits of the reason code X'reason-code', see , or enter the reason code in the BPXMTEXT TSO command.

The provider agent does not start.

Error number error-number and the last four digits of the reason code X'reason-code' point out the reason for the error. Check the console for more messages indicating the problem.

Contact your system programmer.

The user ID that runs the provider agent must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be a privileged user.

The provider agent does not start.

Permit the user ID to run the CIM server by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

The provider agent has loaded a dynamic library that is not program controlled. Either the security setup is not complete or a dynamic library has been changed without a system programmer’s audit.

The provider agent does not start.

Check all dynamic libraries for their program control flag and ensure that no library has changed. For details on program control look at UNIX System Services Planning and z/OS Security Server RACF Security Administrator’s Guide.

Contact your system programmer.

The user ID that runs the provider agent must have READ access to the security profile BPX.SERVER, or, if BPX.SERVER is not defined on your system, must be a privileged user.

The provider agent does not start.

Permit the user ID to run the provider agent by either giving it READ access to profile BPX.SERVER, or, if not running in an Enhanced Security environment, set the UID to 0.

Contact your system programmer.

A provider module was registered with a UserContext value of value, but that value is not supported by this version of the CIM server. Valid values are 2 ("Requestor") and 3 ("Designated User").

The addressed provider module is not correctly registered. The request fails and an error is sent back to the requestor.

Identify the failing provider module, remove the provider using the cimprovider utility (see cimprovider) and re-register the provider with a correct provider registration MOF.

Contact your system programmer.

A provider module was registered with a UserContext value of 3 ("Designated User"). The user ID of the designated user has to be specified in DesignatedUserContext, but no value was found (see PG_ProviderModule).

The request that is directed against the provider module in error will fail and an error is sent back to the requestor.

Identify the failing provider module, remove the provider using the cimprovider utility (see cimprovider) and re-register the provider with a correct provider registration MOF.

Contact your system programmer.

The CIM server failed to switch the security context to user-ID for a provider configured with a designated user context. The user user-ID defined for the provider's security context is not defined to the system or does not have an OMVS segment.

The request fails and an authorization error is sent back to the requestor/client.

Check if the user user-ID is the right user ID to run with or check for the existence of the user user-ID within your security product with the appropriate OMVS segment. If the problem persists you may want to remove the failing provider using the cimprovider utility and re-register the provider with the correct designated user defined in the provider registration MOF.

None.

The CIM server failed to switch to user-ID for the designated user context of a provider.

The request fails and an authorization error is sent back to the requestor/client.

Error code error-code and the last four digits of the reason code 0xreason-code point out the reason for the error. For a description of error error-text with error code error-code and the last four digits of the reason code 0xreason-code, see z/OS UNIX System Services Messages and Codes, or enter the reason code in the BPXMTEXT TSO command.

None.

A SAF authorization error has occurred. The message returns the SAF specific reason code. For RACF, the two rightmost bytes contain the RACF return code and the RACF reason code.

Example: For reason code 0x0BE80820, the RACF return code is 08 and the RACF reason code is 20.

The CIM server terminates the user request.

Use the reason-code for your SAF RACROUTE EXTRACT service to find more details to resolve the authorization error.

For RACF: For details of the authorization error, use the RACF return code and reason code. See the UNIX System Services Programming: Assembler Callable Services Reference , table "RACF return and reason codes", for the specific reason of the failure.

Report this problem to your system programmer.

The attempt of user user-ID to shut down the CIM server has failed because the user does not have the required permissions.

Shutting down the CIM server requires CONTROL access to the CIMSERV profile in class WBEM. For information about other required but missing permissions, use the bpxmtext command along with the reasoncode.

The CIM server is not stopped

None.

Obtain the required permissions or use a different user ID.

The CIM server successfully registered to the Automatic Restart Manager.

None.

None.

None.

The CIM server failed to register with the Automatic Restart Manager using the element name CFZ_SRV_system-name.

None.

If you do not want to use the Automatic Restart Manager, you can ignore this message. If you want to use ARM, use X'error-number' and X'reason-code' to look up the return and reason codes for the IXCARM macro in the z/OS MVS Programming: Sysplex Services Reference for the reason to fail to register with ARM.

None.

The user ID requesting an administrative task, for example, cimconfig or cimprovider, does not have the required permission.

The request is not processed and an "Access Denied" notification is sent to the client.

Permit the user to perform administrative CIM tasks by giving him CONTROL permission to profile CIMSERV in class WBEM.

Contact your system programmer.

A client with the named user ID has sent a CIM request for a CIM write operation (SetProperty, InvokeMethod, CreateInstance, ModifyInstance, DeleteInstance) to the CIM server without having the appropriate access rights.

The request is not processed and an "Access Denied" notification is sent to the client.

None.

If you need to perform CIM write operations, ask your system programmer to grant you at least UPDATE access to profile CIMSERV CL(WBEM).

AT-TLS reset the connection with the client due to a handshake failure.

The connection is closed.

This message documents an unsuccessful connect to AT-TLS. If this prevents a connection from a client to the server, switch on tracing at the AT-TLS policy to find the reason for this closure.

Contact your system programmer.

While querying the AT-TLS connection using ioctl(), the CIM server received an unknown error. For a description of error error-text with error number error-number and the last four digits of the reason code X'reason-code', see , or enter the reason code in the BPXMTEXT TSO command.

The connection is closed.

Contact IBM® support.

Contact your system programmer.

The CIM server is configured to use HTTPS by defining the configuration property enableHttpsConnection, but the AT-TLS policy is not configured correctly for the CIM server.

The connection is closed.

Please refer to CIM server security setup for information about how to configure AT-TLS for the CIM server.

Contact your system programmer.

The value of the property ApplicationControlled defined in the AT-TLS policy for the CIM server is ON. Hence, the CIM server is only aware of AT-TLS but does not control it.

The connection is closed.

Change the property ApplicationControlled to OFF in the AT-TLS policy defined for the CIM server. Refer to CIM server security setup for information about how to configure AT-TLS for the CIM server.

None.

The property HandshakeRole defined in the inbound AT-TLS policy for the CIM server is not configured correctly.

The connection is closed.

Change the property HandshakeRole to ServerWithClientAuth or to the server at the inbound AT-TLS policy defined for the CIM server. Refer to CIM server security setup for information about how to configure AT-TLS for the CIM server.

None.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. No actual migration action was run, because the basic setup is not correct.

The CIM server does not start.

To find out the reason for this error, check the previously issued message. Correct the basic setup and restart the CIM server.

None.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Migration started and ran to a certain point. Though they failed, the accomplished migration actions were successfully rolled back.

The CIM server does not start.

To find out the reason for this error, check the previously issued message. Correct the setup problem and restart the CIM server.

Contact your system programmer.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Migration started and ran into a critical break. The attempt to roll back the taken actions failed. Manual user intervention is required to roll back taken migration actions.

The CIM server does not start.

To find out the reason for this error, check the previously issued message. fallback the taken migration actions as described in that message. Fix the setup problem and restart the CIM server.

None.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Processing of the named command failed with error error-number.

The CIM server will roll back already taken migration actions. The CIM server does not start.

Investigate why the named command cannot perform successfully. Fix the system setup and restart the CIM server.

You can find further details in STDERR and STDOUT of the job output.

Contact your system programmer.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. The processing of the named command failed with status status-code.

The CIM server will roll back the already taken migration actions. CIM server does not start.

Investigate why the named command cannot perform successfully. Fix the system setup and restart the CIM server.

Further details can be found in STDERR and STDOUT of the job output.

Contact your system programmer.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Renaming of source directory to target directory failed.

The CIM server will roll back already taken migration actions. CIM server does not start.

Investigate the reason of the renaming failure. Possible reasons are missing file access rights, a full file system or missing access right to run a program in an extra UNIX System Services address space.

Contact your system programmer.

The CIM server failed to write the repository status file while automatically migrating the old repository in /var/wbem to the new schema level. The migration is nearly complete, but writing the repository status file failed. The repository status file serves to avoid repeated attempts to migrate the repository.

A message is logged to the system console. The CIM server startup continues.

Either fix the reason for the failed write of the repository status file and stop and restart the CIM server, or copy the file supplied in /usr/lpp/wbem/ to /var/wbem.

Contact your system programmer.

The CIM server will start to migrate the old repository to the new schema level.

The CIM server starts to migrate the repository.

None.

None.

The CIM server could not locate the new repository at location directory-name. No actual migration action was run, because basic setup is not correct.

The CIM server does not start.

Check the SMP/E installation. Directory and files should have been copied to the named location in the SMP/E APPLY step.

Contact your system programmer.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Even though migration successfully created the new repository, renaming the old repository for backup failed.

The CIM server will remove the new repository to roll back the taken migration actions. The CIM server does not start.

Investigate why the CIM server was unable to rename the directory /var/wbem/repository to the directory directory-name. Probable causes are insufficient disk space or missing access rights.

None.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Even though migration successfully created the new repository and backed up the old repository, renaming the new repository to /var/wbem/repository failed.

The CIM server tries to roll back the taken migration actions and also removes the new repository and renames the backed up version to /var/wbem/repository.

Investigate why the CIM server was unable to rename the directory. Probable reasons are insufficient disk space or missing access rights. If fallback actions fail (indicated by message CFZ12547E), manually remove the directory named /var/wbem/repository_new and rename the latest backed up repository version to /var/wbem/repository.

None.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level.

The CIM server will try to roll back the taken migration actions.

Check former and further messages for details and possible required actions.

None.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. Removing the new, migrated repository failed.

The CIM server does not start.

Remove the directory /var/wbem/repository_new and its subfolders and files. Check the system log for earlier messages for details on the actual migration step that failed. Fix the situation and restart the CIM server. The most common reason for this problem is insufficient disk space at /var/wbem.

None.

The CIM server tried to roll back the migration actions. Renaming the backed up copy of the old repository to target directory name failed.

The CIM server does not start.

Rename the source directory to the target directory name. Investigate the reason for the failure of the automatic repository migration by checking the system log for former error messages. Fix the system setup and restart the CIM server.

Contact your system programmer.

The CIM server failed to write the repository status file while automatically migrating the old repository in /var/wbem to the new schema level. The migration is nearly complete, but writing the repository status file failed. The repository status file serves to avoid repeated tries to migrate the repository.

A message is logged to the system console. The CIM server startup continues.

Either fix the reason for the failed write of the repository status file and stop and restart the CIM server, or copy the file supplied in /usr/lpp/wbem/ to /var/wbem.

Contact your system programmer.

The CIM server failed to automatically migrate the old repository in /var/wbem to the new schema level. No actual migration action was run, because the basic setup is not correct. The old repository found at directory-name is not a z/OS 1.8 level repository.

The CIM server does not start.

Use migration job CFZRCUST to migrate the repository.

Contact your system programmer.

The CIM server successfully migrated the old repository to the new schema level. A backup copy of the old repository is stored at directory-name. The copy should be backed up and then can be deleted to free up disk space.

The CIM server startup continues.

You may want to backup the old repository, and delete the copy on hard disk.

None.

The CIM server successfully migrated the old repository to the new schema level.

The CIM server startup continues.

None.

None.

The CIM server failed to determine information about the file system at path-name. The cause of the failure was error error-text.

Automatic repository upgrade continues.

None.

None.

The file system available at path-name should be at least 100MB large or be able to extend to that size. The CIM server might run out of space when automatically upgrading the repository.

Automatic repository upgrade continues.

Make sure that there is enough space for data to be stored in the file system at path-name. Recommended is a system specific data set with at least 100MB space mounted at /var/wbem.

None.

The CIM server detected less than 60MB space available in the file system path-name. The CIM server might run out of space when automatically upgrading the repository.

Automatic repository upgrade continues.

Make sure that there is enough space for data to be stored in the file system at path-name. Recommended is a system specific data set with at least 60MB space mounted at /var/wbem.

None.

The CIM server is configured to use HTTPS by defining the configuration property enableHttpsConnection, but the Communication Server Policy Agent was not enabled on the stack the CIM server is using when AT-TLS policy mapping was performed for the connection.

The connection is closed.

Ensure that Communication Server Policy Agent is configured for the TCP/IP stack the CIM server is listening. Please refer to CIM server security setup for information about how to configure AT-TLS for the CIM server.

Contact your system programmer.

The CIM server is configured to use HTTPS by defining the configuration property enableHttpsConnection, but the Communication Server Policy Agent did not find an AT-TLS policy for the CIM server when AT-TLS policy mapping was performed for the connection.

The connection is closed.

Ensure that a Communication Server Policy Agent policy is defined for CIM server. Please refer to CIM server security setup for information about how to configure AT-TLS for the CIM server.

Contact your system programmer.

CIM server successfully created the directory /var/wbem.

None.

None.

None.

CIM server failed to create the directory /var/wbem with error error-message.

The CIM server does not start.

Check the system setup for a system-specific data set mounted at path /var/wbem with 100Mb space. Fix the problem and restart the CIM server.

Contact your system programmer.

CIM server failed to read information from the repository status file at /var/wbem.

CIM server startup proceeds and the repository is automatically migrated to the latest level available from /usr/lpp/wbem.

Check the error condition described by error-message and fix the indicated problem in the system setup.

Contact your system programmer.

CIM server found quote characters in file file-name. Quotes can cause environment variable setup problems.

CIM server tries to remove all quotes. The CIM server does not start.

None.

Restart the CIM server.

CIM server failed to open file-name for writing. The reason is named in error-message. CIM server found quote characters in the environment variable setup file for the started task procedure. CIM server tried to open the environment variable setup file to remove all quotes.

CIM server does not start.

Remove all quotes in file file-name manually or check the error condition described by error-message and fix the indicated problem in the system setup. Restart the CIM server.

Contact your system programmer.

CIM server failed to write to file-name for the reason named in error-message. CIM server found quote characters in the environment variable setup file for the started task procedure. CIM server tried to write the environment variable setup file with all quote removed, but the file was written partially.

CIM server does not start.

Check the error condition described by error-message and fix the indicated problem in the system setup. Create a new environment variables setup file file-name using the default shipped in /usr/lpp/wbem/install. Restart the CIM server.

Contact your system programmer.

CIM server removed all quote characters from file file-name. Quotes can cause environment variable setup problems for the started task procedure. To avoid issues caused by partially setup environment variables the CIM server is stopped and needs to be restarted.

CIM server does not start.

Restart the CIM server.

Restart the CIM server.

On CIM server startup the automated migration procedure detected that path /var/wbem does not exist.

CIM server creates the directory /var/wbem.

None.

None.

An error occurred when the CIM server process tried to establish eligibility for running on zIIP processors.

RC=0x00000408 and

RC=0x00000508

indicate a problem with the CIM server installation in the z/OS UNIX file system.

RC=0x00000708

indicates that CIM server library libcfzsys.so located in /usr/lpp/wbem/lib is not APF authorized.

The CIM server process with all its threads is executing on CP processors.

For RC=0x00000708, use the command

extattr +a /usr/lpp/wbem/lib/libcfzsys.so

to restore the extended attribute to APF authorize the library.

All other return codes indicate a general problem during program execution, please contact IBM for service.

Contact your system programmer.

CIM server process has successfully established eligibility for running on zIIP processors.

The CIM server process with all its threads is executing on zIIP processors.

None.

None.

The user ID requesting a CIM operation using a remote connection is not permitted to use the CIM server.

The request is not processed and an "Access Denied" notification is sent to the client.

Permit the user to perform CIM requests by giving the user ID READ access to profile CIMSERV CL(WBEM).

Contact your system programmer to permit your user ID to perform CIM requests. Repeat your request.

The user ID requesting a CIM operation using a local connection is not permitted to use the CIM server.

The CIM request is not processed and an "Access Denied" notification is sent to the client.

Permit the user to perform CIM requests by giving the user ID READ access to profile CIMSERV CL(WBEM).

Contact your system programmer to permit your user ID to perform CIM requests. Repeat your request.

The CIM server failed to process the out-of-process provider agent caused by the problem error-text. For further details, see the description of error number error-number and the last four digits of the reason code X'reason-code' in UNIX System Services Messages and Codes.

None.

Stop the CIM server. Error number error-number and the last four digits of the reason code X'reason-code' point out the reason for the error. Check the console for more messages indicating the problem.

Contact your system programmer.

The authentication for user user-ID against the z/OS system failed. Either the user ID or password contained in a request was invalid or revoked, or the user ID has not been authorized to use CIM.

The CIM request is denied.

None.

Check that you are using a valid user ID and password and that the user ID has been authorized to use CIM. If the problem persists, contact the system programmer of the target system to check for more detailed authentication error messages on the system console.

The CIM server refused login for user user-ID, because user-ID is a superuser (UID=0), and the current CIM server configuration prohibits superuser logins (the configuration option enableRemotePrivilegedUserAccess is false).

The CIM request is denied.

To allow superuser logon to the CIM server set the enableRemotePrivilegedUserAccess configuration option to true, as described in CIM server configuration.

Either use a non-superuser user ID for logon to the CIM server, or contact your system administrator to enable superuser login for the CIM server.

The user ID requesting a CIM operation using a remote connection is not permitted to use the CIM server.

The request is not processed and an "Access Denied" notification is sent to the client.

Permit the user to perform CIM requests by giving the user READ access to profile CIMSERV CL(WBEM).

Contact your system programmer to permit your user ID to perform CIM requests and afterwards repeat your request.

A request was sent to the CIM server with user user-ID but no password was specified.

The request is rejected as unauthorized.

None.

Specify a password with your request.

The CIM server is using the application ID 'OMVSAPPL' for authentication.

Application ID 'OMVSAPPL' is used for authentication.

If the usage of application ID 'OMVSAPPL' is intended, no action has to be taken.

Otherwise, if you want to use the application ID 'CFZAPPL',

1. Set the configuration property enableCFZAPPLID to true
2. Restart the CIM server

None.

The authentication for user user-ID issued by the IP address IP-address against the z/OS system failed. Either the user ID or password contained in a request was invalid or revoked, or the user ID has not been authorized to use CIM.

The CIM request is denied.

None.

Check that you are using a valid user ID and password and that the user ID has been authorized to use CIM. If the problem persists, contact the system programmer of the target system to check for more detailed authentication error messages on the system console.

The user ID requesting a CIM operation using a local connection is not permitted to use the CIM server.

The request is not processed and an "Access Denied" notification is sent to the client.

Permit the user to perform CIM requests by giving the user READ access to profile CIMSERV CL(WBEM).

Contact your system programmer to permit your user ID to perform CIM requests and afterwards repeat your request.

The CIM server cannot change the ownership of a file to the user requesting local authentication. The file is located at /tmp and the file name matches the pattern: cimclient_<USERID>_*. The file is only valid for a short time. The server should remove this file automatically. It can be deleted.

The request is not processed and an "Access Denied" notification is sent to the client.

Either define CHOWN.UNRESTRICTED in RACF, or grant the CIM server runtime environment user ID READ access to the SUPERUSER.FILESYS.CHOWN resource in the UNIXPRIV RACF class. For details refer to Configuring the CIM server's resource authorization model.

Contact your system programmer.

Audit logging is enabled.

The CIM server starts writing SMF 86 records. These records are only recorded if the SMF configuration contains record 86 and the security is set up accordingly. For details see Audit logging with SMF record 86.

None.

None.

Audit logging is disabled.

The CIM server stops writing SMF 86 records.

None.

None.

The CIM server failed to register itself as a service for the Service Location Protocol (SLP). Clients will not be able to detect the CIM server on the local networking using the SLP protocol.

None.

Check the system log for further messages indicating CIM server configuration problems or general communication problems. This message usually indicates an issue with the CIM server setup.

None.

The CIM server has successfully registered itself as a service for the Service Location Protocol (SLP). Clients using the SLP protocol can now detect this CIM server on the local network.

None.

None.

None.

Initialization of the Java™ Virtual Machine failed due to environment variable CLASSPATH not being set. The CIM client request cannot be answered as JMPI (Java Managed Provider Interface) providers do not run without a correctly set CLASSPATH.

None.

Set the CLASSPATH as described by the provider.

Contact your system programmer.

A WS-Management operation exceeds the server's memory.

Stop the WS-Management operation.

Look for message CFZ08101E identifying the source of the WS-Management request. Contact the owner of the application issuing the request and analyze the reason for the size of the operation. Limit the result objects for this request. Restart the server to clean it up.

Contact your system programmer.

An unspecified internal error occurred. The requested operation could not be completed.

No action was performed.

None.

No action required. The function may be successful if invoked again.

An unspecified internal error occurred. The requested operation might have been partly or completely processed.

Operation was partly or fully completed.

None.

Check the system state. If the operation was not fully completed, the function may be successful if invoked again.

Storage is not available for the requested operation. The requested operation could not be performed.

No action was performed.

None.

There is a storage shortage. The function may work successfully later on.

Unsupported operating system environment. The WLM CIM provider requires z/OS V1R10 or higher. It cannot be used on z/OS V1R9 or lower.

No action was performed.

Install WLM CIM provider on z/OS V1R10 or higher.

None.

One or several CIM provider method parameters are not valid.

No action was performed.

None.

Check the parameters passed to CIM provider methods.

The caller is not authorized to perform the requested operation. The RACF facility class is active and a profile has been defined for the MVSADMIN.WLM.POLICY RACF facility class profile to which the caller does not have sufficient read or update access.

No action was performed.

Grant user appropriate access for RACF profile MVSADMIN.WLM.POLICY.

Contact the System Programmer to get the required authorization.