Installation (MSMI) Messages › MSMI0005-0044

MSMI0005-0044

MSMI0005E

Property property_name is not available in file archive_file_name

Reason:

A problem with the packaging occurred. One or more of the following CA CSM archives could not be found:

• AEG1SHSC
• AEGPHFS
• AEGPJAR
• AEG1JAR

Action:

Contact CA Support.

MSMI0006E

property_name path folder_name does not exist

Reason:

CA CSM installation folders do not exist on USS. property_name may not appear.

Action:

1. Verify that the USS paths are defined in MSMSetupOptionsFile.properties.
2. Verify that the USS paths exist on USS.

Note: For more information, see the Installation Guide and the Site Preparation Guide.

MSMI0007E

property_name path user_name does not have write permissions

Reason:

The user does not have write permission to one or more CA CSM installation folders on USS. property_name may not appear.

Action:

1. Verify that USS paths defined in MSMSetupOptionsFile.properties exist on USS.
2. Verify that the current user has write access to the USS paths.

MSMI0008E

The options file is empty

Reason:

The MSMSetupOptionsFile.properties file is blank.

Action:

Input properties into the MSMSetupOptionsFile.properties file.

MSMI0009E

Failed to establish an FTP connection with host host_name

Reason:

The specified host name is unable to connect to the host system where CA CSM is to be installed.

Action:

1. Verify that the specified host name is entered correctly.
2. Verify that the specified host name is online.

MSMI0010E

Failed to close the FTP connection with host host_name

Reason:

The specified host name could not log out or finish the FTP session with host where CA CSM is installed.

Action:

Contact the administrator of the host computer to verify that there are no connectivity issues.

MSMI0011E

User user_name failed to log in to host host_name

Reason:

The user credentials are invalid.

Action:

Verify that the user credentials are correct, and then attempt another login.

MSMI0012E

The host name for the FTP connection is empty in file host_name

Reason:

The hostname of the system where CA CSM is to be installed has not been entered.

Action:

Enter the HOSTNAME property in the MSMSetupOptionsFile.properties file.

MSMI0013E

The length of property_name should not be greater than number_of characters

Reason:

The character length of the text for the property specified is longer than the allowed character length.

Action:

Edit the property name in the MSMSetupOptionsFile.properties file so that it contains the valid number of characters specified.

MSMI0014E

property_name should be in the character_name_1 character_name_2 character_name_3 range

Reason:

The property specified contains invalid characters.

Action:

Edit the property name in the MSMSetupOptionsFile.properties file so that it contains the valid characters.

MSMI0015E

Both username and password are required

Reason:

The user has not entered the user name and password values in the login verification step in the installation process.

Action:

Verify that the correct user name and password values have both been entered when prompted during the installation.

MSMI0016E

job_name cannot begin with a digit

Reason:

The job name specified in the MSMSetupOptionsFile.properties file begins with a digit. Job names cannot begin with a digit.

Action:

Edit the JOBNAME property in the MSMSetupOptionsFile.properties file so that the job name does not begin with a digit.

MSMI0017E

The length of property and the length of property should not be greater than number of characters

Reason:

The lengths of the properties specified are greater than the length allowed.

Action:

Edit the properties in the MSMSetupOptionsFile.properties file to verify that they are less than the maximum characters allowed.

MSMI0018E

installer_property and path installer_property_value do not exist

Reason:

The two USS folders specified do not exist.

Action:

Verify that the folders specified in MSMSetupOptionsFile.properties exist on the system where CA CSM is to be installed.

MSMI0019E

Path USS_path_1 is the same as path USS_path_2. message_text

Reason:

The two USS folders specified are the same.

Action:

Verify that the msminstall, msm, msmruntime, and mpm folders are all unique. message_text provides additional instructions to resolve the issue.

MSMI0020E

property_name should be either value_1 or value_2

Reason:

The user has specified a value other than value_1 or value_2 for the property property_name.

Action:

Change the property in MSMSetupOptionsFile.properties so that it contains one of the two values specified.

MSMI0021E

The CA CSM port value CA_CSM_port is not unique

Reason:

The port number CA_CSM_port is not unique.

Action:

Change the port number CA_CSM_port so that it is not the same as any of the other ports specified in MSMSetupOptionsFile.properties.

MSMI0022E

NULL_value should not be empty

Reason:

The value NULL_value inside MSMSetupOptionsFile.properties cannot be null.

Action:

Change the value NULL_value inside MSMSetupOptionsFile.properties so that it contains a value, which is also valid for that property.

MSMI0023I

installer_property should be a number; a default value will be assigned.

Reason:

An invalid value was specified for the installer_property. A default value will be assigned.

Action:

No action is required. This message is informational.

MSMI0024E

property_1 and property_2 should be in the range_1 range_2 range_3 range

Reason:

property_1 and property_2 contain one or more characters that are not in the ranges specified by range_1, range_2, and range_3.

Action:

Change both properties inside MSMSetupOptionsFile.properties to contain valid characters.

MSMI0027E

For each data set name segment of installer_hlq, the length cannot exceed number_of characters

Reason:

The data set name installer_hlq is invalid because one or more name segments contain more than the maximum number of characters.

Action:

Change the data set name installer_hlq inside MSMSetupOptionsFile.properties so that it is valid.

MSMI0028E

For each data set name segment of installer_hlq, the length cannot exceed hlq_max_length characters. current_hlq

Reason:

The data set name installer_hlq is invalid because one or more name segments contain more than hlq_max_length characters.

Action:

Change the data set name installer_hlq inside MSMSetupOptionsFile.properties so that it is valid. The current data set name is included in the message.

MSMI0029E

For each data set name segment of key_value, the first character must be in range range_1 range_2

Reason:

The property specified as a key-value pair does not start with the valid characters in the ranges specified.

Action:

Change the property value inside MSMSetupOptionsFile.properties so it is valid.

MSMI0030E

The data set segment segment inside property property_name begins with a character that is not alphabetic or a national character (@ $ #)

Reason:

The property specified does not start with the valid characters in the ranges specified.

Action:

Change the property value inside MSMSetupOptionsFile.properties so it is valid.

MSMI0031E

The second to the eighth characters of the data set segment segment assigned to options file property property_name is not alphanumeric, a national character (@ $ #), or a hyphen

Reason:

The data set segment or property in MSMSetupOptionsFile.properties contains a character that is not in the ranges specified.

Action:

Change the property value inside MSMSetupOptionsFile.properties so it is valid.

MSMI0032E

The second to the eighth characters of the data set segment segment assigned to options file property property_name is not alphanumeric, a national character (@ $ #), or a hyphen. previous_error_messages

Reason:

The data set segment or property in MSMSetupOptionsFile.properties specified by installer_property contains a character that is not in the ranges.

Action:

Change the property installer_property in MSMSetupOptionsFile.properties so it is valid.

MSMI0033E

installer_property_key=installer_property_value, the data set does not exist

Reason:

The data set specified by installer_property_key does not exist on the host system.

Action:

Verify that the data set installer_property_key exists on the host system and is valid.

MSMI0034E

installer_property_key=installer_property_value, the data set is not in the proper record format

Reason:

• The data set is in an incorrect format. The correct format is as follows:

      //data_set
  

• The data set contains a POSIX or HFS filepath, which is not allowed.

Action:

• Verify that the data set installer_property_key is in the correct format.
• Verify that the data set installer_property_key is not a POSIX/HFS filepath.

MSMI0035E

installer_property_key=installer_property_value, the data set already exists

Reason:

The data set exists and is cataloged on the current system.

Action:

Specify a different data set name.

MSMI0037E

zOS_version is nonnumeric

Reason:

The installer script received a nonnumeric value for the z/OS version. The problem occurred either because of JRE, or because of some other internal problem in the operating system.

Action:

None. If the problem persists, contact the system administrator.

MSMI0038I

For upgrades, MVSHFSDsnPrefix and MountPath in the previous and current versions of the options file are expected to be the same

Reason:

The values of MVSHFSDsnPrefix and MountPath are expected to be the same.

Action:

No action is required. This message is informational.

MSMI0038W

MVSHFSDsnPrefix and MountPath are not the same in the current and previous versions of the options file

Reason:

The values for the CA CSM HFS file system and mount point folder for the previous CA CSM installation are different from the values specified for the current installation or the version you are upgrading to.

Action:

Verify that the user has proper access to the file systems and folders, and MSMSetup.sh is being executed as root user. Also, verify that the CA CSM HFS file system is mounted properly to the MountPath folder.

MSMI0039E

SMP/E environment zone names cannot be the same: zone_name

Reason:

The keywords TargetZoneName and DlibZoneName in the MSMSetupOptionsFile.properties file are the same.

Action:

Verify that the keywords TargetZoneName and DlibZoneName in the MSMSetupOptionsFile.properties file are unique.

MSMI0039I

If MVSHFSDsnPrefix and MountPath in the previous and current versions of the options file are different, you will be prompted to:
Continue the upgrade (migrate the database with acceptable values)
Modify the installation to a new installation (no database migration)
Exit the installation

Reason:

The values of MVSHFSDsnPrefix and MountPath are different.

Action:

No action is required. This message is informational.

MSMI0039W

MVSHFSDsnPrefix is not the same in the current and previous versions of the options file

Reason:

The value for the CA CSM HFS data set for the previous CA CSM installation is different from the value specified for the current installation or the version you are upgrading to.

Action:

Verify that the CA CSM HFS data set is mounted properly onto the MountPath folder. Also, verify that MSMSetup.sh is being executed as root user.

MSMI0040I

The values provided in this version of the options file will overwrite the above files

Reason:

The data sets and files listed will be overwritten if they exist and have been selected for the current installation.

Action:

No action is required. This message is informational.

MSMI0040W

MountPath is not the same in the current and previous versions of the options file

Reason:

The value for the mount point folder for the previous CA CSM installation is different from the value specified for the current installation or the version the user is upgrading to.

Action:

Verify that the user has proper access to the folder specified in the previous version. Also, verify that MSMSetup.sh is being executed as root user.

MSMI0041I

These files may belong to the previous version of CA CSM, or they may be left over from a prior installation of the same version

Reason:

The files that you have selected for the current installation exist.

Action:

No action is required. This message is informational.

MSMI0041W

The following ports are either in use or reserved

Reason:

Another program is using one of the ports specified in MSMSetupOptionsFile.properties, or the port is a reserved port which cannot be used.

Action:

Use a different port number for one or more ports in MSMSetupOptionsFile.properties.

MSMI0042E

Unsupported Java SDK addressing mode

Reason:

An unsupported 31-bit Java SDK was used to launch the installer.

Action:

Change the JAVAPATH value in MSMSetupOptionsFile.properties so that it contains the path to an IBM 64-bit Java SDK 1.7.

MSMI0043E

installer_property_key=installer_property_value, the data set could not be accessed

Reason:

The installer was unable to access or open the specified data set.

Action:

Verify that the user running the installer has the required permissions to access the data set.

MSMI0044E

installer_property_key option was not found in MSMSetupOptionsFile.properties

Reason:

The specified setup option was not found in the MSMSetupOptionsFile.properties file during validation.

Action:

Verify that the option exists in the properties file, and that it is not commented out.