Conversion exception messages

This message appears for each converted object and shows the new name of the object based on the object name pattern that you selected (see Accessing-the-conversion-utility ).

During the conversion, the utility discovered that more than one CSM object would result in having the same object name in the TOM Definition Base. Because in TOM you cannot have two objects with the same name, the utility appends a number to subsequent objects of the same name (for example: TSO.SYSB.1, TSO.SYSB.2, and so on).

The Start (also for Stop/Cancel) command for this object contains CSM
variable. CSM variables are not supported in TOM. Please update the
object and replace all &CSM variables with shared variables.

You can replace the CSM variables with object attribute, status variables, or other shared variables.

The TOM application does not use the CANCEL command. The CSM CANCEL command can be replaced with the STOP RETRY command in TOM (the TOM STOP RETRY command is issued only if the STOP command fails).

Start and Stop events converted to Startup and Shutdown validation
Rules. The TOM validation Rules currently do not support JOB Type.

This informational message explains that the CSM events are now called validations in TOM. The CSM Rules that used the additional fields JOB type, Word in message, Operand and Text string are not supported in the STM events.

Abnormal Termination events converted to Abnormal Termination validation Rules. The TOM validation Rules currently do not support JOB Type, Word in message, Operand and Text string.

This informational message explains that the CSM events are now called validations in TOM. The CSM Rules that used the additional fields JOB type, Word in message, Operand and Text string are not supported in the STM events.

Rules not generated. Object will be considered active when it is
detected that the address space exists. If Rules are desired update the object to include Startup and Shutdown validation.

This informational message explains that the Rules were not generated.

This object has a Post Start EXEC. The EXEC has been converted, however TOM does not pass internally parameters to the EXEC. You may need to modify the EXEC logic. The available variables to the EXEC are as follows: TOM_OBJECT, TOM_OBJTYPE, TOM_SYSNAME and TOM_REQUEST.

See Where-variables-can-be-entered for information about using variables in EXECs that are associated with TOM objects.

This object has a Post Stop EXEC. The EXEC has been converted, however TOM does not pass internally parameters to the EXEC. You may need to modify the EXEC logic. The available variables to the EXEC are as follows: TOM_OBJECT, TOM_OBJTYPE, TOM_SYSNAME and TOM_REQUEST.

See Where-variables-can-be-entered for information about using variables in EXECs that are associated with TOM objects.

The TOM application has no feature equivalent to the CSM TSO Send field.

The TOM application has no feature equivalent to the CSM Contact field.

The TOM application has no feature equivalent to the CSM Info field.

Multiple Calendar Schedules detected. TOM Calendar has different
behavior than CSM. Please review object Schedules for correctness.

In certain cases, the CSM Schedules must be manually re-created for TOM. For information about how to create Calendar dependencies for TOM objects, see Entering-calendar-dependencies.

This object has a parent, which is a Grouping object. TOM does not
support Grouping objects therefore the Grouping object is replaced
with its parent.

TOM does not use grouping objects as they are used in CSM. When the conversion process discovers a grouping object, it is not converted. However the new TOM object has a dependency on the object that was the parent of the CSM grouping object.

This object has multiple servers: '<server_name>'. To achieve the same functionality in TOM update object '<server_name>'. Include the connect command: '<connect_command>' in a Post-start EXEC and the disconnect command: '<disconnect_command>' in a Pre-stop EXEC.

TOM supports one server per object. The object being converted has more than one server. The first client-server entry has been converted. To accommodate the other client-server entries, code the server connect and disconnect commands into Post-start and pre-stop EXECs and define these EXECs as part of the new TOM object definition.

The Start/Stop/Cancel command for this object contains stem variables.
The format was converted to the TOM stem variables format.

Stem variables used in the START, STOP, or CANCEL commands for the CSM object definitions were converted to TOM stem variables format.

This object is eligible for Move to <n> CSM Groups: <group1>(<system1>),<group2>(<system2>),…, <groupn>(<systemn>)

This is an informational message to notify the user that a moveable object was converted and to specify the systems it is eligible to move.

This is a moveable object and was converted as part of its local
group(<LocalGroupName>).

This is an informational message to notify the user that a moveable object was found in this group, but it is not its local group and therefore it was not converted to avoid duplicate objects in the target Definition Base. A CSM moveable object will be only converted within its local group to a single TOM object with multiple VSL (Valid Systems List) entries.