Readiness report message prefixes

Each message type has a unique prefix describing the nature of the message, as described in the following table:

Prefix

Description

ERR

Error

Error messages indicate that job processing definitions contain values that are inconsistent with new version formats. These values might affect job scheduling.

You must manually correct the errors identified in job processing definitions before continuing the migration.

Errors in a job in Production must be corrected, or the job must be removed from the Active Jobs database. If you can, manually correct the errors. If not, the job can be removed by the New Day procedure at the beginning of the next day. Otherwise, you can manually request the job to be deleted during the next daily maintenance.

INFO

Information

These messages indicate that the data contains values that are no longer relevant or supported in the new version. The data is automatically corrected during the "import" process. In most cases, no manual changes are required or accepted. The automatic changes do not affect your scheduling environment in the new version.

PLN

PLN Warning

These messages warn that job processing definitions in your current environment contain an improper combination of basic scheduling parameters that affect the job’s scheduling plan in the new version.

PLN messages are always accompanied by an ERR99 message, which is a general error message indicating job scheduling plan differences in the new version.

The data cannot be migrated until the scheduling plan differences are resolved. Control-M Migration cannot determine what corrections to make. You must perform the required changes manually.

If ERR99 is issued without any PLN warnings, notify BMC Software Customer Support.

WRN

Warning

These messages indicate that job processing definitions in your current environment contain statements that have no production meaning. For example, an ON statement with no DO action, or a SHOUT statement with no new version.

You can correct these warning situations (for example, you can add a DO action to an ON statement, or a destination to a SHOUT statement). However, if you choose not to correct these warnings, the problematic statements are removed during the "import" process to the new version. These changes do not affect your scheduling environment.

Parent Topic

Readiness report messages