Migration Status Messages

You may receive status messages at the end of the migration process, which report any problems that were encountered during migration.

Any status messages appear in the Status Messages field in the Migration Summary page.
Table 1. Migration Status Messages
Message Description
Value-1 for property interactionVerb is not valid

Explanation: The value of "-1" is not valid for this property, and the migration tool subsititutes it with the value 1.

Actions: No action is required, unless you want to set the value of this property to some other value than "1". In this case you need to modify the generated code manually, after the J2C Java bean is generated.

Property 'commitmode' is specified both as a fixed value and as a property exposed as an input parameter for the method.

Explanation: The commitmode parameter has been defined both as a fixed value and exposed as an input parameter. Only one definition is permitted.

Actions: It will be treated as a property exposed as an input parameter for the method.

Property 'functionName' is specified both as a fixed value and as a property exposed as an input parameter for the method.

Explanation: The functionName parameter has been defined both as a fixed value and exposed as an input parameter. Only one definition is permitted.

Actions: It will be treated as a property exposed as an input parameter for the method.

Class name 'CustomerProject/sample.cics/CustomerInfo.java' is duplicate.

Explanation: The xxx.java class is already generated in the package sample.cics, under the xxx project.

Actions: The migration tool will overwrite the original xxx.java class. If you do not want the orginial xxx.java to be overwritten, do not proceed with the migration process and press cancel.

Data type mapping error

Explanation: One possible cause of a data mapping error is that the Binding WSDL file is corrupted.

Actions: Cancel the migration and check your Binding WSDL files.

TheWSDL file must contain at least one </service> defintion.

Explanation: One possible cause of this error is that the service WSDL file selection for migration is invalid. It does not contain a <server> </server> definition.

Actions: Cancel the migration and check your Binding WSDL files.

Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.