AWSBJH - Migration messages
This section lists error and warning migration messages that might be issued.
The message component code is BJH.
AWSBJH005E The datamigrate parameter "parameter" has been supplied more than once.
Explanation
You have supplied a parameter to the datamigrate command more than once. For example, you might have supplied the -path parameter more than once.
parameter is the parameter that has been supplied more than once.
System action
The datamigrate command cannot be processed.
Operator response
Check the syntax of the command. Issue the command datamigrate -u to see the usage of the command, or consult the Planning and Installation Guide.
Reissue the command, supplying each parameter only once.
AWSBJH006E An incorrect value has been supplied for a parameter.
Explanation
You have supplied a parameter to the datamigrate command that has an incorrect value.
System action
The datamigrate command cannot be processed.
Operator response
Check the syntax of the command. Issue the command datamigrate -u to see the usage of the command, or consult the Planning and Installation Guide.
Reissue the command, supplying the correct parameters.
AWSBJH009E More than one object type parameter has been supplied.
Explanation
The datamigrate command can import all mozart database objects or objects of one specified type. It cannot import more than one specified object type.
System action
The datamigrate command cannot be processed.
Operator response
Reissue the command, supplying either no object types (to import all objects) or specifying just one object type.
AWSBJH011E The parameter "parameter" is not a recognized datamigrate parameter.
Explanation
See message.
parameter is the parameter that is not recognized.
System action
The datamigrate command cannot be processed.
Operator response
Check the syntax of the command. Issue the command datamigrate -u to see the usage of the command, or consult the Planning and Installation Guide.
Reissue the command, supplying the correct parameters.
AWSBJH012E One or more required parameters of the datamigrate command have not been supplied.
Explanation
See message.
System action
The datamigrate command cannot be processed.
Operator response
Check the syntax of the command. Issue the command datamigrate -u to see the usage of the command, or consult the Planning and Installation Guide.
Reissue the command, supplying the correct parameters.
AWSBJH013E Two or more incompatible parameters of the datamigrate command have been supplied.
Explanation
See message.
System action
The datamigrate command cannot be processed.
Operator response
Check the syntax of the command. Issue the command datamigrate -u to see the usage of the command, or consult the Planning and Installation Guide.
Reissue the command, supplying the correct parameters.
AWSBJH014E The supplied input file "input_file" does not exist.
Explanation
You have run the datamigrate command to import mozart database objects from an input file. The input file ought to have been created from the previous instance of HCL Workload Automation using the composer create command. However, datamigrate could not find the file using the supplied file name.
System action
The datamigrate command cannot be processed.
Operator response
Check the supplied file name. Check that the file exists and that the path is supplied correctly. Check that if the path includes spaces, you have enclosed the whole path and file name in double quotes. Check that the user ID performing the import has read permission for the file.
Correct any errors and retry the command.
If the file has not been created, create it using the composer create command, and then rerun datamigrate. Alternatively, import the database objects directly from the previous instance of HCL Workload Automation.
The correct syntax for the composer create command to create the required input file depends on the type of object you want to import. Use one of the following:composer create <topology_filename> from cpu=@composer create <prompts_filename> from promptscomposer create <calendar_filename> from calendarscomposer create <parms_filename> from parmscomposer create <resources_filename> from resourcescomposer create <jobs_filename> from job=@#@composer create <scheds_filename> from sched=@#@The composer create option for users exports user details without their passwords, so to include the passwords, use the following:migrutility get_users <TWS_8.x.x_user_mozart_file> <users_filename>
AWSBJH016E The supplied "prev_install_dir" does not identify a previous instance of HCL Workload Automation from which to import data.
Explanation
You have run the datamigrate command to import mozart database objects directly from a previous instance of HCL Workload Automation. However, datamigrate could not find the instance using the supplied directory.
prev_install_dir is the supplied directory name that does not contain a previous HCL Workload Automation instance.
System action
The datamigrate command cannot be processed.
Operator response
Check the supplied directory name. Check that the directory exists and that the path is supplied correctly. Check that if the path includes spaces, you have enclosed the whole path in double quotes. Check that the user ID performing the import has read permission for the directory.
Correct any errors and retry the command.
Alternatively, use the composer create command in the previous instance of HCL Workload Automation to create input files of the objects to import, and import them using the appropriate datamigrate commands.
The correct syntax for the composer create command to create the required input file depends on the type of object you want to import. Use one of the following:composer create <topology_filename> from cpu=@composer create <prompts_filename> from promptscomposer create <calendar_filename> from calendarscomposer create <parms_filename> from parmscomposer create <resources_filename> from resourcescomposer create <jobs_filename> from job=@#@composer create <scheds_filename> from sched=@#@The composer create option for users exports user details without their passwords, so to include the passwords, use the following:migrutility get_users <TWS_8.x.x_user_mozart_file> <users_filename>
AWSBJH018E The temporary directory "temporary_directory" does not exist.
Explanation
You have supplied the optional -tmppath option, but the directory associated with the option does not exist.
System action
The datamigrate command cannot be processed.
Operator response
Check the supplied directory name. Check that the directory exists and that the path is supplied correctly. Check that if the path includes spaces, you have enclosed the whole path in double quotes. Check that the user ID running datamigrate has write permission for the directory.
Correct any errors and retry the command.
AWSBJH022E The import of object type "object_type" has failed.
Explanation
See message.
object_type is the type of object you were trying to import.
System action
The datamigrate command has finished but no objects have been imported.
Operator response
Check the log to determine why the import failed. Correct any errors and rerun the command.
AWSBJH023W The import of object type "object_type" has completed with one or more warnings.
Explanation
See message.
object_type is the type of object you were importing.
System action
The datamigrate command has finished. Objects have been imported, but datamigrate found one or more ambiguities in the input data.
Operator response
Check the log and examine the warnings. For each warning message you must decide whether you can and want to fix the problem that was found using HCL Workload Automation version 8.4, or whether you can and want to correct the problem in the previous instance of the product and rerun the import.
AWSBJH024W No object of type "object_type" has been found.
Explanation
You have run the datamigrate command to import mozart database objects from an input file. The input file was created from the previous instance of HCL Workload Automation using the composer create command. However, the file contains no objects of the indicated object_type.
System action
The datamigrate command has finished but no objects of the indicated type have been imported.
Operator response
See the next message.
AWSBJH026E The import of object type "object_type" has completed with one or more errors.
Explanation
See message.
object_type is the type of object you were importing.
System action
The datamigrate command has finished. Objects have been imported, but datamigrate found one or more errors in the input data.
Operator response
Check the log and examine the errors. For each error message you must decide whether you can and want to fix the problem that was found using HCL Workload Automation version 8.4, or whether you can and want to correct the problem in the previous instance of the product and rerun the import.
AWSBJH029E The supplied input file !1 is not readable by the user !2 that is performing the data migration.
Explanation
The user might not have the correct access rights to the specified file, or the file does not have the correct permissions.
System action
The datamigrate command has finished. Objects have been imported, but the data in the indicated input file has not been migrated.
Operator response
Modify the permissions of the file or use a different user that has the correct permissions to read the file. Rerun the migration.
AWSBJH031E The application server is not running. The import cannot continue.
Explanation
See message.
System action
The datamigrate command stops without migrating any data. If the application server stops in the middle of the migration, the data is partially migrated.
Operator response
Start the application server and then rerun the datamigrate utility.
AWSBJH035E The migration was unable to export the data from the previous instance of HCL Workload Automation, because it could not copy the dataexporter program into the directory: "directory".
Explanation
See message.
System action
The datamigrate command cannot be processed.
Operator response
Check that there is sufficient space in the fileset where the directory resides, and that the user running datamigrate has write permission for the directory.
Correct any errors and retry the command.
AWSBJH104E The supplied object type "incorrect_object_type"is not a recognized object type.
Explanation
See message.
incorrect_object_type is the supplied object type that is not correct.
System action
The getmozart utility stops. No data is exported.
Operator response
Retry the command, supplying a valid object type. Permitted values are topology, calendars, parms, prompts, resources, users, jobs, and schedules.