AWSFAF - Installation messages (fix pack)

This section lists error and warning messages that might be issued when using the script to install a fix pack for the product.

The message component code is FAF.

AWSFAF003E

The twspatch script cannot run on this operating system: "operating_system".

See message text.

The twspatch script cannot proceed.

Check in the readme file supplied with the fix pack for details of supported platforms.

readmefile.

AWSFAF004E

Only the user root can run the twspatch script.

See message text

The twspatch script cannot proceed.

Login as the root user and rerun the twspatch script.

AWSFAF005E

No parameters have been specified for twspatch.

The twspatch script needs to be supplied with at least one parameter.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme file supplied with the fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter.

readme file.

AWSFAF007E

The supplied installation type parameter is not correct. It must be one of the following: -install, -undo, -commit, -remove, -repair.

See message text.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme file supplied with the fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter.

readme file.

AWSFAF008E

More than one installation type parameter has been supplied. Supply only one of the following: -install, -undo, -commit, -remove, -repair.

See message text.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme file supplied with the fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter.

readme file.

AWSFAF009E

A parameter to twspatch has been supplied that is not appropriate for the supplied installation type. Specify the "installation_parameter" parameter only when "installation_type" installation type is specified.

The installation_parameter is a parameter that you supplied, that is not appropriate for the supplied installation type.

The installation_type is a list of the only installation types with which you can use the supplied installation_parameter.

The twsinst script cannot proceed.

Check the usage of the twsinst script by referring to the HCL Workload Automation: Planning and Installation Guide, or use the command twsinst -u to the see a list of the available parameters.

Rerun the twsinst script, supplying the correct parameter.

HCL Workload Automation: Planning and Installation Guide

AWSFAF010E

An incorrect value has been supplied for a parameter. The parameter must be as follows: "installation_parameter".

The parameter you have supplied is correct, and is valid for this installation type. However, the value supplied for the parameter is not correct.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme supplied with this fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter value.

readme file.

AWSFAF011E

The following parameter has been supplied more than once: "installation_parameter".

See message text.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme file supplied with this fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter.

readme file.

AWSFAF012E

The twspatch fix pack installation cannot be used because the HCL Workload Automation registry file is missing.

The HCL Workload Automation registry file contains the relevant information that he fix pack installation uses to identify and update the existing instance. Without it, the installation cannot go ahead.

The twspatch script cannot proceed.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF014E

The following is not a recognizable installation parameter "installation_parameter".

See message text.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme file supplied with the fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter.

readme file.

AWSFAF015E

The -uname option is missing.

The indicated parameter is required for this installation type.

The twspatch script cannot proceed.

Check the usage of the twspatch script by referring to the readme supplied with this fix pack, or use the command twspatch -u to the see a list of the available parameters.

Rerun the twspatch script, supplying the correct parameter.

readme file.

AWSFAF016E

You supplied a user account that does not exist on the local computer or that contains an invalid character: "user_account". Create the user account before running twsinst, or verify that it does not contain an invalid character.

See message text.

The twsinst script cannot proceed.

Check that the correct account name was supplied. If it was not, rerun the twsinst script, supplying the correct account name.

If the correct account name was supplied, create the account before rerunning the twsinst script.

AWSFAF017E

The script was unable to locate the home directory of the specified user: "user_account".

See message text.

The twspatch script cannot proceed.

The script has located an entry for the user in the HCL Workload Automation registry, but the directory that the entry points to does not contain an instance of a previous version of HCL Workload Automation. Check that a previous installation of HCL Workload Automation exists in the indicated directory. If the instance for the supplied user exists, but in a different directory, modify the entry in the HCL Workload Automation registry file to identify the correct installation directory and rerun the script.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF019E

The script was unable to determine the installation type from the HCL Workload Automation registry file "file".

See message text.

The twspatch script cannot proceed.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF020E

The script was unable to find the configuration file "configuration_file" of the HCL Workload Automation instance to which you want to apply the fix pack.

See message text.

The twspatch script cannot proceed.

Locate the indicated configuration file and move it to the correct directory (see the documentation for the version you are upgrading for the exact location of the configuration file). Then rerun the twsinst script.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF021E

The script has located an entry for the user in the HCL Workload Automation registry, but the directory that the entry points to does not contain an instance of a previous version of HCL Workload Automation. Check that a previous installation of HCL Workload Automation exists in the directory "directory". If the instance for the supplied user exists, but in a different directory, modify the entry in the HCL Workload Automation registry file to identify the correct installation directory and rerun the script.

See message text.

The twspatch script cannot proceed.

Check that a previous installation of HCL Workload Automation exists in the indicated directory. If the instance for the supplied user exists, but in a different directory, modify the entry in the HCL Workload Automation registry file to identify the correct installation directory and rerun the script.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF022E

The script was unable to determine the installation directory from the HCL Workload Automation registry file "file".

See message text.

The twspatch script cannot proceed.

The script could not find an entry for the user in the HCL Workload Automation registry file. Check that you have entered the user name correctly. Check that the supplied user owns a previous version of HCL Workload Automation installed in his or her home directory. Check that the HCL Workload Automation registry file contains an entry for the installation directory for this user. If you have identified the wrong user, rerun the patch installation. If the correct user has been identified, and owns an old instance of HCL Workload Automation, but the registry has no entry for that user, you cannot install the patch.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF023E

The installed component (workstation type) "installed_component" in the HCL Workload Automation registry file "file" is not valid.

See message text.

The twspatch script cannot proceed.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF025E

No previous instances of HCL Workload Automation belonging to the supplied user "user" have been detected in the HCL Workload Automation registry file "file".

See message text.

The twspatch script cannot proceed.

Check that the supplied user is the correct owner of the instance of HCL Workload Automation on this computer. If not, resubmit the script supplying the correct user.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF027E

The "installation_type" fix pack installation has failed. For more details see the log file "file".

See message text.

The twspatch script stops without successfully installing the fix pack.

This message will have been preceded by other messages explaining the nature of the failure. Follow the Operator Response of those messages to determine the appropriate action.

AWSFAF028W

At least one warning message was issued during the "installation_type" fix pack installation.

See message text.

The twspatch script stops. The fix pack has been installed, but one or more warnings were issued.

This message will have been preceded by the specific warning messages. Follow the Operator Response of those messages to determine the appropriate action.

AWSFAF030E

The twspatch script is being run from the wrong directory.

This depends on the type of installation you are performing:
-install or -repair

You might be attempting to install a fix pack for HCL Workload Automation on a UNIX platform using the twspatch utility copied from the installation CD to the home directory of the TWSuser. This is not allowed.

You can run twspatch from any of the following places:
  • The HCL Workload Automation fix pack CD
  • A disk image of the CD
  • A copy of the twspatch utility and its associated files placed in any local directory other than the home directory of the TWSuser.
-undo, -commit, or -repair

These installation types must be run from the copy of the twspatch utility that has been installed for you in the home directory of the TWSuser.

The twspatch script cannot proceed.

Rerun the fix pack installation from a permitted directory.

AWSFAF032E

The installation script was not able to locate the file "file" needed set up the operation environment "operation_environment".

See message text.

The twspatch script cannot proceed.

If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSFAF033E

The installation script has been run from the wrong directory. You must run the script from the following directory:"directory_name".

The -undo, -commit, or -repair installation types must be run from the copy of the twspatch utility that has been installed for you in the home directory of the TWSuser.

The twsinst script cannot proceed.

Rerun the twsinst installation script from the indicated directory.

AWSFAF034W

The remove operation has been completed successfully. The HCL Workload Automation instance belonging to the user "user" is now unusable. You must recover the previous installation from backup.

See message text.

The twspatch script has completed successfully and has removed the instance of HCL Workload Automation.

You must now recover the previous instance of HCL Workload Automation from backup.

AWSFAF037E

The twspatch script is being run from the wrong directory.

See message.

The twspatch script cannot proceed.

Run twspatch directly from the product CD. If the computer where you are installing the product does not have a CD drive, copy either an image of the CD or just the platform-specific folder to the target computer; place them anywhere other then the home directory of the TWSuser.

AWSFAF046E

The "user_account" user account you supplied does not exist on the local computer. The patching cannot proceed.

The indicated parameter is incorrect.

The twspatch script cannot proceed.

Run the twspatch script again, supplying the correct parameter.

HCL Workload Automation: Planning and Installation Guide

AWSFAF047E

You specified an incorrect password for the user "username".

The indicated parameter is incorrect.

The twsinst script cannot proceed.

Run the twsinst script again, supplying the correct password.

HCL Workload Automation: Planning and Installation Guide

AWSFAF132E

The uninstallation failed. Either you specified an incorrect username or you are running the twspatch script from the wrong directory.

See message text.

The twsinst script cannot proceed.

Either change the value of the username to the same username used during installation, or run the twsinst script from the installation folder. For details see the HCL Workload Automation: Planning and Installation Guide

Rerun the twsinst script, supplying the correct parameter.

AWSFAF161E

There are still jobs running. The twspatch operation cannot continue. Use the coman sj @#@.@ command to verify which jobs are still running.

See text.

The twspatch script cannot proceeds.

  1. >Use the coman sj @#@.@ command to verify which jobs are still running.
  2. Wait for job completion.
  3. Run the twsinst script again.
HCL Workload Automation: Planning and Installation Guide