File System (MSMF) Messages › MSMF0001-0035

MSMF0001-0035

MSMF0001I

Starting up CA CSM USS file systems.

Reason:

Startup processing of all USS file systems registered to CA CSM started.

Action:

No action is required. This message is informational.

MSMF0010I

Initializing CA CSM USS file systems.

Reason:

Initialization processing of all USS file systems registered to CA CSM started.

Action:

No action is required. This message is informational.

MSMF0011I

Initializing CA CSM application USS file systems.

Reason:

Initialization processing of USS file systems required by CA CSM started.

Action:

No action is required. This message is informational.

MSMF0020I

Verifying CA CSM managed product USS file systems.

Reason:

CA CSM started verifying managed product USS file systems created during a base installation of a product or added during SMP/E environment migration.

Action:

No action is required. This message is informational.

MSMF0021I

Verifying whether CA CSM managed product in SMP/E environment csi_data_set_name has USS file system file_system_name mounted to system_path.

Reason:

CA CSM started verifying a particular managed product USS file system.

Action:

No action is required. This message is informational.

MSMF0025I

Verifying CA CSM deployment snapshot USS file systems.

Reason:

CA CSM started verifying deployment snapshot USS file systems created during deployment.

Action:

No action is required. This message is informational.

MSMF0026I

Verifying whether CA CSM deployment snapshot has USS file system file_system_name mounted to system_path.

Reason:

CA CSM started verifying a particular deployment snapshot USS file system.

Action:

No action is required. This message is informational.

MSMF0027I

Verifying CA CSM software catalog USS file systems.

Reason:

CA CSM verifies software catalog USS file systems.

Action:

No action is required. This message is informational.

MSMF0028I

Verifying whether CA CSM software catalog has USS file system file_system_name mounted to system_path.

Reason:

CA CSM started verifying a particular software catalog USS file system.

Action:

No action is required. This message is informational.

MSMF0030W

CA CSM managed product USS file system file_system_name to be mounted to system_path could not be found by CA CSM.

Reason:

The CA CSM server found a particular managed product USS file system not to be mounted and then could not find the USS file system container of the managed USS file system.

Action:

Verify the SMP/E environment which uses the file system. If the SMP/E environment resources have been deleted or moved, you can remove the SMP/E environment from CA CSM which verifies that the USS file system is also removed from CA CSM, and the warning does not appear.

If the file system exists but is not visible to CA CSM, mount the file system to the system path specified.

MSMF0031W

CA CSM managed product USS file system file_system_name to be mounted to system_path could not be accessed by CA CSM.

Reason:

The CA CSM server found a particular managed product USS file system not to be mounted and then could not access the USS file system container of the managed USS file system.

Action:

Mount the file system to the system path specified.

MSMF0032W

CA CSM managed product mount point system_path for USS file system file_system_name could not be found by CA CSM.

Reason:

The CA CSM server found a particular managed product USS file system not to be mounted and then could not find the mount point pathname of the managed USS file system.

Action:

Verify the SMP/E environment which uses the mount point. If the SMP/E environment resources have been deleted or moved, you can remove the SMP/E environment from CA CSM which verifies that the USS file system is also removed from CA CSM, and the warning does not appear.

If the mount point exists but is not visible to CA CSM, mount the file system to the system path specified.

MSMF0033W

Managed product mount point system_path for USS file system file_system_name is found to be invalid: reason.

Reason:

The CA CSM server found a particular managed product USS file system not to be mounted and then found that the mount point pathname of the managed USS file system exists, but is not a directory.

Action:

Review the mount point system_path and reason. If applicable, correct the situation and either mount the file system to the mount point or restart CA CSM to attempt automounting.

MSMF0034E

Managed product USS file system file_system_name should be mounted to system_path. CA CSM found other_file_system_name to be mounted.

Reason:

The CA CSM server found that a mount point for a particular managed product USS file system has a different USS file system mounted to it. CA CSM verifies mounted USS file systems against the records created during a base installation or SMP/E environment migration.

Action:

If there is an operational reason for other_file_system_name to be mounted to system_path, remove the SMP/E environment to which the USS file system belongs from CA CSM and then migrate it back to CA CSM. This helps ensure that old records related to USS file systems used by the SMP/E environment are replaced with the current USS file systems.

If the other_file_system_name USS file system is incorrectly mounted to the system_path mount point, unmount it and mount the file_system_name.

MSMF0035E

Managed product USS file system file_system_name is not mounted to system_path.

Reason:

The CA CSM server found a particular managed product USS file system not to be mounted.

Action:

Mount file_system_name to system_path.