Internal Component (MMI) Messages › MMI0050-0095

MMI0050-0095

MMI0050S

A message has been received indicating that the remote end is terminating due to a serious error.

Reason:

This is a summary message that follows error messages that have been generated when the remote end is terminating due to a serious error.

Action:

• Review other log messages that explain the cause of the problem.
• Contact CA Support.

MMI0051S

The class_name class does not implement function_name of interface interface_name.

Reason:

An internal error occurred.

Action:

Contact CA Support.

MMI0052S

Buffer overflow while buffer_activity from bbbbbbbb. Buffer size: ttB.

Reason:

An internal error occurred. bbbbbbbb is the buffer address. tt is the buffer size.

Action:

Contact CA Support.

MMI0053S

Buffer overflow while buffer_activity from bbbbbbbb.

Reason:

An internal error occurred. bbbbbbbb is the buffer address.

Action:

Contact CA Support.

MMI0054S

Authentication of username failed.

Reason:

Authentication of the user failed. The password is invalid.

Action:

Log in with the valid password.

MMI0055S

username is not authorized to access message_namemmmmmmmm

Reason:

The user is not authorized to use the specified CA CSM facility. mmmmmmmm is the message ID.

Action:

Review other log messages that explain the cause of the problem. If the problem is caused by an invalid password, log out of CA CSM and log in again with the valid password.

MMI0084S

Initialization of CAGIMAPI address space failed.

Reason:

CAGIMAPI address space has been spawned but did not respond to the initial handshake.

Action:

Contact CA Support.

MMI0085S

A serious error has occurred while starting CAGIMAPI: Additional diagnostic information has been written to CAGIMAPI_InitError file in server's home directory

Reason:

The CAGIMAPI program failed to start up successfully. This is usually because of storage shortage or inability to attach to the shared memory region used to transfer GIMAPI data.

Action:

• Inspect the CAGIMAPI_InitError file found in the USS home directory of the user running CA CSM server.
• Contact CA Support.

MMI0087S

A serious error has occurred while starting CAGIMAPI: Detected build number mismatch between the CA CSM server and CAGIMAPI

Reason:

Because CAGIMAPI is executed in a spawned process, it contains a build number and, every time it starts, it tests this number against the build number of CA CSM to verify version consistency. This error occurs when the version of CA CSM is incompatible with the version of CAGIMAPI, indicating possible problems during deployment.

Action:

Verify that all components of CA CSM are correctly deployed.

MMI0090S

An error has occurred while fetching GIMAPI - program was not loaded. Reason: reason_text

Reason:

CA CSM was not able to load the GIMAPI program that is used to extract information from SMP/E CSI, for one of the following reasons:

1. CA CSM was not able to load GIMAPI. The module was not found in LINKLIST.
2. CA CSM was not able to load the GIMAPI program that is used to extract information from SMP/E CSI because GIMAPI is not program controlled.
3. CA CSM was not able to load the GIMAPI program that is used to extract information from SMP/E CSI because another program used by GIMAPI is not program controlled and no detailed reason information was available.

Action:

Depending on the reason, do one of the following:

1. Verify that the data set containing the GIMAPI program is in LINKLIST.
2. Change the security settings for GIMAPI so that it is program controlled.
3. Look in the SYSLOG to determine the program used by GIMAPI and make it program controlled.

MMI0095S

Loaded GIMAPI program of version program_version. Expecting version expected_program_version or greater.

Reason:

The version of the GIMAPI program loaded by CA CSM is below the minimum expected version.

Action:

Verify that you run the minimum expected version of SMP/E (3.4.24).