Return codes from the installer

The WebSphere® MQ File Transfer Edition installer provides return codes to indicate whether installation tasks have successfully completed.

Retrieving the return codes

When the installer has completed, you can find the return code by one of the following methods:
  • Look in the installation log file. This file is located at install_directory/IBM_WebSphere_MQ_File_Transfer_Edition_-_component_InstallLog.log
  • If you are using the console or silent installer, type the following command immediately after installation has completed to determine the return code:
    • On Windows
      echo %ERRORLEVEL%
    • On Linux or UNIX
      echo $?

If you receive a return code from your installation that is not included in the following tables, see the documentation for your operating system.

Return codes on Windows platforms

The following table lists the installer return codes with their meanings:
Table 1.
Return code Description
0 Success: The installation completed successfully without any warnings or errors.
1 The installation completed successfully, but one or more of the actions from the installation sequence caused a warning or a non-fatal error.
-1 One or more of the actions from the installation sequence caused an unrecoverable error.
1000 The installation was canceled by the user.
1001 The installation includes an invalid command-line option.
2000 Unhandled error.
2001 The installation failed the authorization check, this error might indicate an expired version.
2002 The installation failed a rules check. A rule placed on the installer itself failed.
2003 An unresolved dependency in silent mode caused the installer to exit.
2004 The installation failed because not enough disk space was detected during the execution of the Install action.
2005 The installation failed while trying to install on a Windows 64-bit system, but installation did not include support for Windows 64-bit systems.
2006 The installation failed because it was launched in a UI mode that is not supported by this installer.
3000 Unhandled error specific to a launcher.
3001 The installation failed due to an error specific to the lax.main.class property.
3002 The installation failed due to an error specific to the lax.main.method property.
3003 The installation was unable to access the method specified in the lax.main.method property.
3004 The installation failed due to an exception error caused by the lax.main.method property.
3005 The installation failed because no value was assigned to the lax.application.name property.
3006 The installation was unable to access the value assigned to the lax.nl.java.launcher.main.class property.
3007 The installation failed due to an error specific to the lax.nl.java.launcher.main.class property.
3008 The installation failed due to an error specific to the lax.nl.java.launcher.main.method property.
3009 The installation was unable to access the method specified in the lax.nl.launcher.java.main.method property.
4000 A Java™ executable can not be found at the directory specified by the java.home system property.
4001 An incorrect path to the installer jar file caused the relauncher to launch incorrectly.

Return codes on Linux and UNIX platforms

The following table lists the installer return codes with their meanings:
Table 2.
Return code Description
0 Success: The installation completed successfully without any warnings or errors.
1 The installation completed successfully, but one or more of the actions from the installation sequence caused a warning or a non-fatal error.
3 The license agreement was declined. The installation did not complete.
160 A Java executable can not be found at the directory specified by the java.home system property.
161 An incorrect path to the installer jar file caused the relauncher to launch incorrectly.
184 Unhandled error specific to a launcher.
185 The installation failed due to an error specific to the lax.main.class property.
186 The installation failed due to an error specific to the lax.main.method property.
187 The installation was unable to access the method specified in the lax.main.method property.
188 The installation failed due to an exception error caused by the lax.main.method property.
189 The installation failed because no value was assigned to the lax.application.name property.
190 The installation was unable to access the value assigned to the lax.nl.java.launcher.main.class property.
191 The installation failed due to an error specific to the lax.nl.java.launcher.main.class property.
192 The installation failed due to an error specific to the lax.nl.java.launcher.main.method property.
193 The installation was unable to access the method specified in the lax.nl.launcher.java.main.method property.
208 Unhandled error.
209 The installation failed the authorization check, this error might indicate an expired version.
210 The installation failed a rules check. A rule placed on the installer itself failed.
211 An unresolved dependency in silent mode caused the installer to exit.
212 The installation failed because not enough disk space was detected during the execution of the Install action.
213 The installation failed while trying to install on a Windows 64-bit system, but installation did not include support for Windows 64-bit systems.
214 The installation failed because it was launched in a UI mode that is not supported by this installer.
232 The installation was canceled by the user.
233 The installation includes an invalid command-line option.
255 One or more of the actions from the installation sequence caused an unrecoverable error.

Reference Reference

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/installer_return_codes.htm