Previous Topic: MSMI0400-0416Next Topic: MSMI0563E

Installation (MSMI) Messages › MSMI0553-0599

MSMI0553-0599

MSMI0553E

file_name does not exist

Reason:

A JCL job or XML file used by Apache Tomcat does not exist.

Action:

  1. Verify that the file is in the proper location.
  2. Download a newer build of the installer, if the file cannot be found in the packaging.
  3. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMI0554E

custom_JCL does not have read permissions

Reason:

A JCL customized by the installer does not have read permission.

Action:

  1. Verify the JCL has read permissions under the appropriate USS path.
  2. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMI0555E

file_name does not have write permissions

Reason:

A file customized by the installer does not have write permissions.

Action:

  1. Verify the JCL has write permissions under the appropriate USS path.
  2. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMI0556E

Error while writing to file file_name

Reason:

The installer could not customize the file to be submitted.

Action:

  1. Verify the JCL has write permissions under the appropriate USS path.
  2. If unable to resolve the problem, save the error message content and problem recreation steps and contact CA Support.

MSMI0557I

JCL_name is created at location USS_path

Reason:

The runtime JCL was copied to the runtime JCL as an MVS data set.

Action:

No action is required. This message is informational.

MSMI0558E

Error while closing the reader on file_name

Reason:

The installer script encountered an internal error while attempting to close the file after reading its contents.

Action:

Restart the CA CSM installer script, and select 'retry' to continue from the last failed location.

MSMI0560E

Error in removing or renaming file zOS_file

Reason:

The installer script encountered an internal error while attempting to rename or delete an MVS file.

Action:

Restart the CA CSM installer script, and select 'retry' to continue from the last failed location.

MSMI0561E

Problem converting from input_file to output_file

Reason:

The installer script failed to open input_file, output_file or both for reading. The specified character encoding is not supported on the system that MSMSetup.sh is running on.

Action:

Contact CA Support.

MSMI0562S

File file_name is not available in the package

Reason:

The installer script could not process the file file_name in the CA CSM installer packaging because it does not exist.

Action:

Contact CA Support.