MQSeries Workflow Configuration-checking Utility


Table of Contents

0.1 About the MQSeries Workflow Configuration-checking Utility
0.2 Command-line options
0.3 Configuration checker messages
  • FMC34010I Configuration checker version version started.
  • FMC34011I Performing MQSeries Workflow version version.release.modlevel checks.
  • FMC34012I => component checks.
  • FMC34013I => component found, checks started.
  • FMC34014I => component (filename) not installed.
  • FMC34015I => component found, no checks defined.
  • FMC34016E System call failed: call() returned errorcode.
  • FMC34017E System call failed: call(parameter) returned errorcode.
  • FMC34018E Error reading file 'filename'.
  • FMC34019E Cannot open file 'filename' for writing.
  • FMC34020E The what file 'filename' does not exist.
  • FMC34021W The what directory 'name' does not exist.
  • FMC34022E Cannot move filename1 to filename2.
  • FMC34023E Error errorcode loading libname.
  • FMC34024E Cannot load procedure functionname() from libname.
  • FMC34025E exception.
  • FMC34026E Error opening profile: message.
  • FMC34027E profile: Line number is corrupt.
  • FMC34028E Error adding key=value: message.
  • FMC34029E Error erasing key: message.
  • FMC34030E Error repairing profile: message.
  • FMC34031I Successfully loaded description library name.
  • FMC34032E Cannot load description library name: errormsg (rc = errorcode).
  • FMC34033E System call call() failed: errormsg (rc = errorcode).
  • FMC34034E System call call(parameter) failed: errormsg (rc = errorcode).
  • FMC34035W Key key to erase not found in the type profile.
  • FMC34036E Error opening profile filename.
  • FMC34100I Messages have been written to filename.
  • FMC34101I The Operating System is opsys.
  • FMC34102I Assuming name as the MQSeries Workflow directory.
  • FMC34103I Local time is time.
  • FMC34104I Universal time coordinated (UTC) is time.
  • FMC34105W Variable TZ is not set.
  • FMC34106W Syslevel file 'filename' is not valid.
  • FMC34107I product, Vversion.release installed.
  • FMC34108I CSD: 'csdlevel'.
  • FMC34110E Typelib for server not found at server.
  • FMC34111E Typelib for server is version actual version, at least version required version is required.
  • FMC34113I Language specification is 'name' (from the server).
  • FMC34115I The message catalog is name.
  • FMC34116E Message catalog filename not found.
  • FMC34117I Message catalog filename is installed.
  • FMC34118E MQSeries Workflow seems not to be installed.
  • FMC34119I No command line options specified.
  • FMC34120I Command line options specified: options
  • FMC34121I The current configuration is 'name'.
  • FMC34122I Environment variable name is set to 'value'.
  • FMC34123E Environment variable name is not set.
  • FMC34124E 'name' is not a valid configuration ID.
  • FMC34125E 'name' is not a valid system name.
  • FMC34126E 'name' is not a valid system group name.
  • FMC34127E 'name' is not a valid queue manager name.
  • FMC34128E The screen resolution is vertresxhorzres, must be at least 800x600.
  • FMC34129I The screen resolution is set to vertresxhorzres.
  • FMC34130I The default font for the graphical user interface is 'fontname'.
  • FMC34131I The MQSeries Workflow installation directory is name.
  • FMC34132I The XPG4 locale is locale.
  • FMC34133I The ANSI codepage is ansi_cp, the OEM codepage is oem_cp.
  • FMC34134I The locale location used is name.
  • FMC34135I The type profile is name.
  • FMC34136I The user profile for user is name.
  • FMC34137E The HOME environment variable is envHome, should be pwdHome.
  • FMC34138I Using system default name 'path'.
  • FMC34139E The LOCPATH environment variable is not set.
  • FMC34140E The locale location name could not be found in the LOCPATH.
  • FMC34141E No default configuration ID set.
  • FMC34142E The current configuration is not defined.
  • FMC34143I The default configuration is 'name' (from the location).
  • FMC34144E The default configuration 'name' does not exist
  • FMC34145I The following configurations are available: list.
  • FMC34146I The current codepage is cp.
  • FMC34147E The Unicode converters are not installed.
  • FMC34148W The online documenation name does not exist.
  • FMC34149I The FlowMark V2 API compatibility setting name is set to value.
  • FMC34150E The FlowMark V2 API compatiblity variable name has an incorrect value 'value'.
  • FMC34151E The locale files name could not be loaded.
  • FMC34200I Scanning filename...
  • FMC34201I -> version string
  • FMC34202I No version information found in filename.
  • FMC34203I No files found (filemask).
  • FMC34204I Core file found, failing executable: 'filename'.
  • FMC34205W Core file found, but the debugger (dbx) is not contained in the PATH.
  • FMC34206W dbx message.
  • FMC34207W filename is not an MQSeries Workflow program file. The core file is ignored.
  • FMC34208I File 'name' is dated date time
  • FMC34209I Use the '-d' option to analyze the core file.
  • FMC34210I Sanning core files not yet implemented for opsys (filename).
  • FMC34300E WinSock error: errormsg.
  • FMC34301I WinSock version: version.
  • FMC34302E TCP port portname not found.
  • FMC34303I TCP port portname found at number portnumber.
  • FMC34304W TCP port portname found at wrong number portnumber1 (should be portnumber2).
  • FMC34305I TCP port name has been added to filename.
  • FMC34306I The local listener for port number is active.
  • FMC34307I The local listener for port number is not running.
  • FMC34308W Connect to local port number timed out.
  • FMC34309I Alternative IP address found: IP address (interface).
  • FMC34311E Loopback adapter missing or no network connection.
  • FMC34312E The line of port in file is not valid.
  • FMC34313E Could not resolve IP address for host hostname.
  • FMC34314I The local IP address is address.
  • FMC34315E The local hostname is not configured.
  • FMC34316E The local IP address is not correctly configured.
  • FMC34400E The MQSeries configuration file mqs.ini could not be found.
  • FMC34401E Queue Manager qmgr not found in filename or qm.ini for qmgr not found.
  • FMC34402W Unrecognized product CSD level in filename: csdlevel.
  • FMC34403E No version information found for MQSeries component.
  • FMC34404I MQSeries component version is installed.
  • FMC34405E MQSeries component actual version is installed, upgrade to required version.
  • FMC34406W MQSeries seems not to be installed.
  • FMC34500I ==> Database Manager configuration for instance.
  • FMC34501I ==> Database configuration for name.
  • FMC34502I ==> Database connection to name.
  • FMC34503E command: message
  • FMC34504W command: message
  • FMC34505I name is value.
  • FMC34506E name is value, should be at least minimum.
  • FMC34507I The TP monitor (library) need not be set on this platform.
  • FMC34508I name is value.
  • FMC34509E name is value, must be at least minimum.
  • FMC34510I The DBMS name is name (version version).
  • FMC34511I The database driver is name (version version).
  • FMC34512I The database name for alias 'logical name' is 'internal name'.
  • FMC34513I The following databases are available:
  • FMC34514I dbname (description)
  • FMC34515I Connect to dbname was successful (user ID 'ID').
  • FMC34516E Variable name is not set (should be 'YES').
  • FMC34517E Variable name is set to 'value' (should be 'YES').
  • FMC34518E The TP monitor (TP_MON_NAME) is not set.
  • FMC34519I key is 'value' in the name section of filename.
  • FMC34520E key should be 'value' in the name section of filename.
  • FMC34521E QueryTimeoutValue must be at least 60 in the 'Common' section of filename.
  • FMC34522E Fixpack for DB2 is not installed.
  • FMC34523I component version.release.level has fixpack fixpack installed.
  • FMC34524I component version.release.level is installed.
  • FMC34525W Inconsistent path setting in Registry: pathname and path.
  • FMC34526W DB2INSTANCE is 'envInst' but DB2 returns 'db2Inst' as current instance.
  • FMC34527E Database name not found.
  • FMC34528W The database manager has not been started.
  • FMC34529W DB2INSTANCE is db2Inst, but dbname's node is node.
  • FMC34530W You should run fmczchk under the user ID 'db2instance user' instead of 'current user'.
  • FMC34531I DB2 authentication is through authentication.
  • FMC34532E ODBC data source name (odbc name) must be the same as DB name (db2 name).
  • FMC34533E user ID has no authorization for BT database db name.
  • FMC34534E DB2INSTANCE is incorrect or not set.
  • FMC34535I Service 'name' does not exist, assuming DB2 client installation.
  • FMC34600I ==> Executing commands.
  • FMC34601E 'cmd' is not a valid command for version version.release.modlevel.
  • FMC34602W Unnecessary argument for the 'cmd' command: arguments.
  • FMC34603E Key is required for the 'prf' command.
  • FMC34604I key erased from the type profile.
  • FMC34605I key = 'value' inserted into the type profile.
  • FMC34606E Profile type is required for profile command.
  • FMC34607E Incorrect profile type type specified for profile command.
  • FMC34608I No errors found in the profile.
  • FMC34609I profile(number): action 'line'.
  • FMC34610E Service is required for for the 'tcp' command.
  • FMC34611E Port is required for the 'tcp' command.
  • FMC34612E Incorrect port port (number) specified for the 'tcp' command.
  • FMC34613E System is required for the 'fml' command.
  • FMC34614E DB2INSTANCE not found for the 'scm' command.
  • FMC34615I DB2INSTANCE db2inst is being used for dependency checking.
  • FMC34616I All service startup dependencies are up-to-date.
  • FMC34617I Changed start type to 'automatic' for service name.
  • FMC34618I Added service to dependencies list of service name.
  • FMC34619I Successfully added system,qmgr to key in the type profile.
  • FMC34620I Successfully changed system to qmgr in key in the type profile.
  • FMC34621I Successfully removed system from key in the type profile.
  • FMC34622W No entry for system in key in the type profile found.
  • FMC34623W Removed incorrect entry system in key in the type profile.
  • FMC34624W Removed duplicate entry system,qmgr in key in the type profile.
  • FMC34625I The service 'name' has been successfully deleted.
  • FMC34626I Changed account to 'userID' for service name.
  • FMC34627E The service name does not exist.
  • FMC34628E 'option' is not a valid option for the 'scm' command.
  • FMC34629I Account 'userID' will be used for services 'MQ service' and 'MQ Workflow service'.
  • FMC34630E Key 'key' not found in profile.
  • FMC34631I The service 'name' has been created successfully.
  • FMC34632E The account userID is not valid.
  • FMC34633E Level is required for the 'trc' command.
  • FMC34634E Level 'level' is not valid for the 'trc' command.
  • FMC34635I The SCM database had to be updated, please re-run the command.
  • FMC34636E Cannot create service 'service' because the file filename does not exist.
  • FMC34637W Account user ID of service 'service' had to be reset.
  • FMC34638I MQWF 3.2.0 service 'service' has been successfully updated.
  • FMC34700I ==> Service Control Manager configuration.
  • FMC34701I The Administration Server cannot be started as a service.
  • FMC34702W Dependency of service1 on service2 not registered.
  • FMC34703E The service name is disabled.
  • FMC34704E The service name does not exist.
  • FMC34705W No autostart script registered with MQSeries.
  • FMC34800W The JAVA_HOME environment variable is not set.
  • FMC34801I The Java Agent startup scripts will use the JRE from directory.
  • FMC34802I The Java Agent startup scripts will use the JDK from directory.
  • FMC34803E The Java Agent name is not set in the profile.
  • FMC34804I The Java Agent name will use locator policy policy.
  • FMC34805E The locator policy policy for name is invalid.
  • FMC34806I setting used by the policy policy for Agent name is set to 'value'.
  • FMC34807W The setting setting is not used by the policy policy for Agent name.
  • FMC34808W Java could not be found in the PATH.
  • FMC34809I The Java installation directory is 'name'.
  • FMC34810I The Java system property name is 'value'.
  • FMC34811E The Java version version is not supported by the MQWF Java API.
  • FMC34999I Configuration checker ended: num1 error(s), num2 warning(s), rc = code.

  • 0.1 About the MQSeries Workflow Configuration-checking Utility

    The MQSeries Workflow Configuration-checking Utility, hereafter referred to as configuration checker, verifies your MQSeries Workflow installation. Start the configuration checker after having installed MQSeries Workflow and after having changed your MQSeries Workflow configuration.

    The configuration checker is a command-line utility offering several options. For more information, see chapter 0.2, "Command-line options". You can start the configuration checker without any options to perform the standard checks. The configuration checker creates a log file, called fmczchk.log. This log file contains all messages, in addition to the messages that are displayed on the screen. With the -html command-line option you can create an HTML file as an alternative to the standard log file. The HTML file contains hyperlinks to the online documentation fmczchk.htm.

    If you have any comments regarding the documentation or the program itself, please contact me. I am especially interested to hear about your suggestions for further checks to be included in the configuration checker.

    Erich Fussi (fussi@de.ibm.com)
    MQSeries Workflow development


    0.2 Command-line options

    Command-line options start with a slash (/) or minus (-) symbol and can be followed by an argument. Arguments to options can be separated from the option letter by '' (an empty string), ' ' (a blank), ':' (a colon), or '=' (an equals sign). Options are not case sensitive. The following options are available:

    -31,-310,-311,-312,-32,-320,-321
    Specify the version of checks that you want to use. The default is the version the configuration checker was built with. Depending on the MQSeries Workflow version you specify, the checks that are available are displayed, when you start the configuration checker.
    -b
    Do not display messages on the console. This is useful if the configuration checker is being run as a background process.
    -d
    Show debug messages. These are intended for use by the MQSeries Workflow development team only and are, therefore, not described in chapter 0.3, "Configuration checker messages". Always use the -d option for files that you want to send to the MQSeries Workflow development team.
    -e
    Show error messages only. The default is to show error and warning messages and to suppress informational messages.
    -i
    Show all messages (error, warning, and informational messages).
    -htm,-html
    Write fmczchk0.htm instead of fmczchk.log. This file will then contain links to the online documentation, fmczchk.htm. For these to work fmczchk0.htm must be in the same directory as fmczchk.htm.
    -l filename
    Name of the log file to write. If this file already exists, the messages will be appended rather than overwriting the file.
    -y qualifier / ID
    Allows to specify a system qualifier (MQSeries Workflow releases up to 3.1.2) or a configuration ID (MQSeries Workflow release 3.2.0 and later) other than the default that is to be used for the checks.

    MQSeries Workflow releases up to 3.1.2 only: If this option is not used, the value of the FMC_SYSTEM_QUALIFIER environment variable applies. The default for this environment variable is 'FMC'.

    -c command[;...]
    Perform command(s). The following commands are valid:

    fix:(m|u)
    Fixes corrupted MQSeries Workflow profiles. This works only on platforms where the profile is in flat ASCII format, for example AIX. Note: This command is only valid for MQSeries Workflow releases up to 3.1.2.

    fml:(m|u),system[,qmgr]
    Adds or removes an entry from the profile variable FMLConnectName. system is a two-part key consisting of SystemGroupName.SystemName and qmgr is the name of the queue manager to add. If you do not specify qmgr, then the entry will be removed. For example,
      fmczchk -c fml:u,SYS_GRP.FMSRVTST,QMTEST
    
    will add the queue manager QMTEST to FMLConnectName. If you want to remove it again, run
      fmczchk -c fml:u,SYS_GRP.FMSRVTST
    
    The above example described how to handle FMLConnectName in the user profile. To change the machine profile, you have to prefix the key with an m. instead of a u. Note: This command is only valid for MQSeries Workflow releases up to 3.1.2.

    prf:(m|u),key[,value]
    Allows to set or delete a key in the MQSeries Workflow profile. To delete a key, specify the key name only:
      fmczchk -c prf:u,Language
    
    To set a key, you need to specify its value also:
      fmczchk -c prf:u,Language,enu
    
    The above examples describe how to handle keys in the user profile. To change the machine profile, you have to prefix the key with an m instead of a u.
      fmczchk -c prf:m,DatabaseName,FMDB
    
    Note: If you just want to see the profile values, start the configuration checker with the -d option. Note: This command is only valid for MQSeries Workflow releases up to 3.1.2.

    sca:[filemask;...]
    Specify this command to scan all MQSeries Workflow executables for the version string. You can restrict the scanning by specifying your own file mask as an optional argument:
      fmczchk -c sca:dll\fmck*.dll;bin\fmce*.exe
    

    scm:[u[=uid][,p=pwd]][,a][,i=db2inst]
    Updates the Windows NT Service Control Manager database with the startup dependencies required for the MQSeries Workflow service and creates or updates the MQSeries Workflow service in the SCM database according to the options specified. In MQSeries Workflow releases 3.2.0 and later, each configuration has its own MQSeries Workflow service. If you want to create or update the service for another than the current configuration you have to use the -y option to specify the configuration to be used.

    If the optional argument u is not specified, the account information for the MQSeries Workflow service will be set to SYSTEM, and the starter of the IBM MQSeries service will be left unchanged. If u is specified but not the optional argument uid, the account information (user ID and password) for the MQSeries Workflow and IBM MQSeries services will be taken from the profile.

    If the optional argument db2inst is not specifed, the configuration checker uses the value of the DB2INSTANCE variable.

    The start type of the MQSeries Workflow service will be set to manual, unless you specify the a option. In the latter case, the start type will be set to automatic.

    To create an automatic service for configuration FMC with starter SYSTEM enter:

      fmczchk -y FMC -c scm:a
    
    To create an automatic service for the default configuration with the starter taken from the profile enter:
      fmczchk -c scm:u,a
    
    To create a manual service for the default configuration with a given starter enter:
      fmczchk -c scm:u=uid,p=password
    
    Note that in this case the uid must be a valid Windows NT account.

    scm:d
    Deletes the MQSeries Workflow service from the Windows NT Service Control Manager database. MQSeries Workflow releases 3.2.0 and later only: If you want to delete the service for another than the default configuration, use the -y command line option to specify a configuration. For example, to delete the MQSeries Workflow service for configuration FMC enter:
      fmczchk -y FMC -c scm:d
    

    tcp:service,port
    Adds a port to the TCP/IP services file. For example,
      fmczchk -c tcp:MQSeries,1414
      fmczchk -c tcp:MQSeries1,1415
    
    will add port definitions for MQSeries to your services file. This will be done automatically during installation.

    trc:level[,file]
    To enable tracing, specify a trace level in the range 1..3 and optionally a trace file (without the log extension):
      fmczchk -c trc:1
      fmczchk -c trc:3,/tmp/traces/my_trace
    
    To disable tracing, specify a trace level of 0:
      fmczchk -c trc:0
    

    @cmdfile
    Alternatively, you can specify a file containing commands to be executed. For example, if you have a file fmczchk.cmd with the following lines in it
      prf:Language,enu
      prf:m,DatabaseName,FMDB
      tcp:MQSeries,1414
    
    You can start the configuration checker as follows:
      fmczchk @fmczchk.cmd
    

    0.3 Configuration checker messages

    This chapter describes the messages that are displayed by the configuration checker. The last character of the message identifier denotes the message type. The possible values are:

    I
    Informational message, no action is required.
    W
    Warning message, an action can be required. Check the message description to see if any further action is required.
    E
    Error message, an action is required. Check the message description on how to fix the problem.
    In addition, messages can be displayed that start with 'FMC34nnn' or 'FMC34-DBG'. These messages are internal messages for use by the MQSeries Workflow development team only. Therefore, no explanation is given here.

    FMC34010I Configuration checker version version started.

    Explanation: The configuration checker has started.

    Response: None.


    FMC34011I Performing MQSeries Workflow version version.release.modlevel checks.

    Explanation: This message shows the MQSeries Workflow version and the checks that are performed for this version.

    Response: None.


    FMC34012I => component checks.

    Explanation: The checks for the component component have been started.

    Response: None.


    FMC34013I => component found, checks started.

    Explanation: The MQSeries Workflow component component was found and is being checked.

    Response: None.


    FMC34014I => component (filename) not installed.

    Explanation: The MQSeries Workflow component component was not found and cannot be checked.

    Response: Install the component if required.


    FMC34015I => component found, no checks defined.

    Explanation: The MQSeries Workflow component component was found but currently there are no checks defined for it.

    Response: None.


    FMC34016E System call failed: call() returned errorcode.

    Explanation: A system call failed with the error code errorcode.

    Response: This message contains additional information for MQSeries Workflow development.


    FMC34017E System call failed: call(parameter) returned errorcode.

    Explanation: A system call failed with the error code errorcode.

    Response: This message contains additional information for MQSeries Workflow development.


    FMC34018E Error reading file 'filename'.

    Explanation: Either the configuration checker could not open file filename to read its contents or the configuration checker encoutered problems while reading filename.

    Response: Make sure that the file permissions allow reading and the file is not locked by another process.


    FMC34019E Cannot open file 'filename' for writing.

    Explanation: The configuration checker could not open file filename to write.

    Response: Make sure that the file permissions allow writing and the file is not locked by another process. If this is a new file, the directory permissions must allow to create files.


    FMC34020E The what file 'filename' does not exist.

    Explanation: The file filename does not exist.

    Response: Check whether the file name is correct and all required MQSeries Workflow components are installed correctly. Create the file if necessary.


    FMC34021W The what directory 'name' does not exist.

    Explanation: The directory name does not exist.

    Response: Check whether you have specified the correct directory. If what is 'MQSeries Workflow', then the configuration checker could not find the directory where MQSeries Workflow has been installed. If what is the name of an environment variable, make sure this variable does not point to directories which do not exist.


    FMC34022E Cannot move filename1 to filename2.

    Explanation: The configuration checker created a temporary file for updates and cannot move the temporary file to the file to be updated.

    Response: Check whether, for example, the disk is full. If the disk is full move the temporary file manually.


    FMC34023E Error errorcode loading libname.

    Explanation: The configuration checker could not load the library libname.

    Response: Make sure that the library is installed and that the path is contained in the LIBPATH (AIX and OS/2), LD_LIBRARY_PATH (Sun Solaris), SHLIB_PATH (HP-UX) or PATH (Windows) statement.


    FMC34024E Cannot load procedure functionname() from libname.

    Explanation: The configuration checker could not load procedure functionname from library libname.

    Response: Make sure that the correct version of the library is installed and that the path is contained in the LIBPATH (AIX and OS/2), LD_LIBRARY_PATH (Sun Solaris), SHLIB_PATH (HP-UX) or PATH (Windows) statement.


    FMC34025E exception.

    Explanation: An internal error occured.

    Response: Check whether the problem persists and if this is the case, contact the MQSeries Workflow development team.


    FMC34026E Error opening profile: message.

    Explanation: The MQSeries Workflow profile could not be opened.

    Response: Check message and try again.


    FMC34027E profile: Line number is corrupt.

    Explanation: The MQSeries Workflow profile contains an incorrect line - probably it has been edited manually.

    Response: Try the fix command of the configuration checker to repair the profile.


    FMC34028E Error adding key=value: message.

    Explanation: An error occured when the configuration checker tried to add key to the profile.

    Response: Check message and try again.


    FMC34029E Error erasing key: message.

    Explanation: An error occured when the configuration checker tried to erase key from the profile.

    Response: Check message and try again.


    FMC34030E Error repairing profile: message.

    Explanation: An error occured when the configuration checker tried to repair the MQSeries Workflow profile.

    Response: Check message and try again.


    FMC34031I Successfully loaded description library name.

    Explanation: The configuration checker successfully loaded a library required by MQSeries Workflow.

    Response: None.


    FMC34032E Cannot load description library name: errormsg (rc = errorcode).

    Explanation: Error errormsg occured while the configuration checker tried to load the library name.

    Response: Make sure all components are properly installed.


    FMC34033E System call call() failed: errormsg (rc = errorcode).

    Explanation: A system call failed with the error code errorcode. The message text for errorcode is errormsg

    Response: This message contains additional information for MQSeries Workflow development.


    FMC34034E System call call(parameter) failed: errormsg (rc = errorcode).

    Explanation: A system call failed with the error code errorcode. The message text for errorcode is errormsg.

    Response: This message contains additional information for MQSeries Workflow development.


    FMC34035W Key key to erase not found in the type profile.

    Explanation: You tried to erase key key from the type profile, but the key could not be found.

    Response: Correct the name of the key to be erased.


    FMC34036E Error opening profile filename.

    Explanation: The MQSeries Workflow profile filename could not be opened.

    Response: Check the access rights of filename and try again.


    FMC34100I Messages have been written to filename.

    Explanation: filename indicates the fully qualified path name of the file where the configuration checker has written all messages. Note that you do not necessarily see all messages on the screen depending on the message level (please see chapter 0.2, "Command-line options").

    Response: None.


    FMC34101I The Operating System is opsys.

    Explanation: This message indicates the operating system and its release level.

    Response: None.


    FMC34102I Assuming name as the MQSeries Workflow directory.

    Explanation: No entry for the installation directory was found in the MQSeries Workflow profile. The current directory is therefore tken as the MQSeries Workflow bin directory.

    Response: Make sure that MQSeries Workflow is installed before you start the configuration checker.


    FMC34103I Local time is time.

    Explanation: This message indicates the current local date and time.

    Response: None.


    FMC34104I Universal time coordinated (UTC) is time.

    Explanation: This message indicates the current universal date and time.

    Response: Check whether this is correct. If not, verify that you have configured your operating system's time zone settings correctly.


    FMC34105W Variable TZ is not set.

    Explanation: The TZ environment variable is not set.

    Response: If this variable is not set, MQSeries Workflow cannot compute your timezone correctly. Check message FMC34104I whether this is the case and set the TZ environment variable if necessary.


    FMC34106W Syslevel file 'filename' is not valid.

    Explanation: The configuration checker tried to read the syslevel file filename, but this file seems to be corrupted.

    Response: Make sure that the product, to which the syslevel file belongs, is installed correctly.


    FMC34107I product, Vversion.release installed.

    Explanation: The configuration checker identified the product's syslevel file and that version version.release is installed.

    Response: None.


    FMC34108I CSD: 'csdlevel'.

    Explanation: The configuration checker identified from a syslevel file that CSD csdlevel is installed.

    Response: None.


    FMC34110E Typelib for server not found at server.

    Explanation: The configuration checker could not find the typelib for server at key in the Windows Registry.

    Response: Make sure server is correctly installed and has been registered using the regsvr32 command.


    FMC34111E Typelib for server is version actual version, at least version required version is required.

    Explanation: The configuration checker found the typelib for server in the Windows Registry, but it has an incorrect version.

    Response: Make sure the correct version of server is installed and has been registered using the regsvr32 command.


    FMC34113I Language specification is 'name' (from the server).

    Explanation: The language setting for MQSeries Workflow is lang and was retrieved from the location.

    Response: None.


    FMC34115I The message catalog is name.

    Explanation: The configuration checker found the message catalog file filename.

    Response: None.


    FMC34116E Message catalog filename not found.

    Explanation: The configuration checker could not find the message catalog file filename.

    Response: Make sure the message catalog file is installed and check the NLSPATH environment variable. It must contain the directory where the MQSeries Workflow message catalog file resides. Also make sure the Language setting has been correctly specified (check message FMC34113I).


    FMC34117I Message catalog filename is installed.

    Explanation: The configuration checker did not find the required message catalog file but the MQSeries Workflow message catalog filename was found instead.

    Response: If you want to use the message catalog filename, change the Language setting in the profile using the prf command of the configuration checker.


    FMC34118E MQSeries Workflow seems not to be installed.

    Explanation: The configuration checker did not find the directory where MQSeries Workflow is installed.

    Response: Install MQSeries Workflow before running the configuration checker.


    FMC34119I No command line options specified.

    Explanation: The configuration checker has been started without any command-line options.

    Response: None.


    FMC34120I Command line options specified: options

    Explanation: The configuration checker has been started with command-line options options.

    Response: None.


    FMC34121I The current configuration is 'name'.

    Explanation: MQSeries Workflow releases up to 3.1.2: The setting of FMC_SYSTEM_QUALIFIER being used by the configuration checker is qualifier.

    MQSeries Workflow releases 3.2.0 and later: The configuration being checked is name.

    Response: You can use the -y command-line option to specify another name then the default configuration to be used.


    FMC34122I Environment variable name is set to 'value'.

    Explanation: The environment variable name is set to the recommended or required value value.

    Response: None.


    FMC34123E Environment variable name is not set.

    Explanation: The environment variable name is not set although it is needed to locate the MQSeries Workflow message catalog files. NLSPATH must at least contain the MQSeries Workflow bin directory followed by %N, for example d:\fmcwinnt\bin\%N.

    Response: Set the environment variable and run the configuration checker again.


    FMC34124E 'name' is not a valid configuration ID.

    Explanation: You specified an incorrect system qualifier (MQSeries Workflow releases up to 3.1.2) or configuration ID (MQSeries Workflow releases 3.2.0 and later) using the -y command line option.

    Response: Be sure to use a valid name when using the -y command line option.


    FMC34125E 'name' is not a valid system name.

    Explanation: You tried to add an entry to FMLConnectName using the fml command, but the system name you specified is incorrect.

    Response: Correct the system name.


    FMC34126E 'name' is not a valid system group name.

    Explanation: You tried to add an entry to FMLConnectName using the fml command, but the system group name you specified is incorrect.

    Response: Correct the system group name.


    FMC34127E 'name' is not a valid queue manager name.

    Explanation: You tried to add an entry to FMLConnectName using the fml command, but the queue manager name you specified is incorrect.

    Response: Correct the queue manager name.


    FMC34128E The screen resolution is vertresxhorzres, must be at least 800x600.

    Explanation: The current screen resolution is too low. Buildtime requires a minimum screen resolution of 800x600 pixels.

    Response: Change the system's screen resolution.


    FMC34129I The screen resolution is set to vertresxhorzres.

    Explanation: The current screen resolution is vertresxhorzres pixels.

    Response: None.


    FMC34130I The default font for the graphical user interface is 'fontname'.

    Explanation: The current default font is set to fontname.

    Note: In Windows 9x there is a feature called 'Font Mapping'. Therefore, the font that is displayed can be different from the configured font.

    Response: None.


    FMC34131I The MQSeries Workflow installation directory is name.

    Explanation: MQSeries Workflow is installed; the configuration checker found that the installation directory is name.

    Response: None.


    FMC34132I The XPG4 locale is locale.

    Explanation: The currently configured locale is locale. This setting is important for codepage conversions.

    Response: None.


    FMC34133I The ANSI codepage is ansi_cp, the OEM codepage is oem_cp.

    Explanation: Windows systems use two codepages. The ANSI codepage for Window applications, and the OEM codepage for DOS applications. MQSeries Workflow uses the ANSI codepage ansi_cp for codepage conversions. The OEM codepage oem_cp is only used by the MQSeries Workflow command-line utilities to display messages.

    Response: None.


    FMC34134I The locale location used is name.

    Explanation: The configuration checker scanned the LOCPATH for name containing the tables for the current locale (see message FMC34132I). The tables needed for codepage conversion are taken from location name.

    Response: None.


    FMC34135I The type profile is name.

    Explanation: The MQSeries Workflow profiles are stored as flat files on this platform. The name of the type profile file is name.

    Response: None.


    FMC34136I The user profile for user is name.

    Explanation: The MQSeries Workflow profiles are stored as flat files on this platform. The name of the user profile file for user is name.

    Response: None.


    FMC34137E The HOME environment variable is envHome, should be pwdHome.

    Explanation: The HOME environment variable is not set correctly. This variable is needed by MQSeries Workflow to locate the user profile. This can happen if you change user IDs through the su <user> command instead of using the su - <user> command. Then the HOME variable will retain its previous value, envHome, although the correct value for the new user ID would be pwdHome. The current user might not have the appropriate authorizations to access the previous user's profile.

    Response: Make sure the HOME environment variable is set correctly so that the correct user profile will be used..


    FMC34138I Using system default name 'path'.

    Explanation: The name environment variable is not set. The configuration checker will use the system default value path.

    On AIX, the default value name is read from /etc/services.

    Response: None.


    FMC34139E The LOCPATH environment variable is not set.

    Explanation: The LOCPATH environment variable is not set and there is no system default for it. This variable is needed to locate the codepage conversion tables.

    Response: Make sure the LOCPATH environment variable is set correctly.


    FMC34140E The locale location name could not be found in the LOCPATH.

    Explanation: The configuration checker scanned the LOCPATH for name containing the tables for the current locale (see message FMC34132I). But the location name could not be found.

    Response: Make sure LOCPATH is set correctly. If name is C, also check whether LANG (or LC_ALL) is set correctly.


    FMC34141E No default configuration ID set.

    Explanation: There is no default configuration defined. MQSeries Workflow will not run.

    Response: Use the configuration utility to define the default configuration ID.


    FMC34142E The current configuration is not defined.

    Explanation: There is no current configuration defined. MQSeries Workflow will not run.

    Response: MQSeries Workflow releases up to 3.1.2: Set the environment variable FMC_SYSTEM_QUALIFIER to a defined configuration (see message FMC34145I).

    MQSeries Workflow releases 3.2.0 and later: Use the configuration utility to define the default configuration which will be used as current configuration unless overwritten by the -y command-line option.


    FMC34143I The default configuration is 'name' (from the location).

    Explanation: The default configuration is set to name and was retrieved from the location. Use the configuration utility if you want to change it.

    Response: None.


    FMC34144E The default configuration 'name' does not exist

    Explanation: The default configuration ID is set to name, but this configuration does not exist. MQSeries Workflow will not run.

    Response: Use the configuration utility to set up the configuration name or to change the default configuration ID.


    FMC34145I The following configurations are available: list.

    Explanation: The configurations defined are list. Use the configuration utility to select a configuration from this list (see also message FMC34121I) or to edit the available configurations.

    Response: None.


    FMC34146I The current codepage is cp.

    Explanation: The name of the current codepage is cp.

    Response: None.


    FMC34147E The Unicode converters are not installed.

    Explanation: The components for codepage conversion to Unicode are not installed. MQSeries Workflow will not run if Unicode codepage conversion is not available.

    Response: Install the Unicode conversion components of your operating system. On AIX, this is fileset bos.iconv.ucs.com.


    FMC34148W The online documenation name does not exist.

    Explanation: You were using the -html command line option and the log file has been written in HTML format. But since the online documentation name is not in the current directory (the directory of the HTML log file), the hyperlinks in the HTML log file will not work.

    Response: Change to the directory where MQSeries Workflow is installed (were fmczchk.htm is located) and run the configuration checker again.


    FMC34149I The FlowMark V2 API compatibility setting name is set to value.

    Explanation: The MQSeries Workflow setting name required for the FlowMark V2 compatibilty API is set to value.

    Response: None.


    FMC34150E The FlowMark V2 API compatiblity variable name has an incorrect value 'value'.

    Explanation: The MQSeries Workflow setting name has a value that is not allowed. The allowed values are DEFAULT, PRESENT, and PRESENTHERE.

    Response: Change the value of name in the MQSeries Workflow profile.


    FMC34151E The locale files name could not be loaded.

    Explanation: The files name are required for the current locale but they cannot be loaded.

    Response: If this problem occurs on Windows, make sure that the library fmcwmthi.dll is installed and can be loaded.


    FMC34200I Scanning filename...

    Explanation: You specified the -s command-line option, and the configuration checker is currently scanning filename for version information.

    Response: None.


    FMC34201I -> version string

    Explanation: Using the '-s' option of the configuration checker the version string was found in the same module as mentioned in message (FMC34200I).

    Response: None.


    FMC34202I No version information found in filename.

    Explanation: The configuration checker could not find the MQSeries Workflow version in filename.

    Response: This check does not work with non-MQSeries Workflow files.


    FMC34203I No files found (filemask).

    Explanation: Using the '-s' option of the configuration checker to scan files for their version information, no files were found matching filemask.

    Response: Correct the filemask and try again.


    FMC34204I Core file found, failing executable: 'filename'.

    Explanation: The configuration checker found a core file and the failing executable was filename.

    Response: Check the messages following this one.


    FMC34205W Core file found, but the debugger (dbx) is not contained in the PATH.

    Explanation: The configuration checker found a core file, but the path for the debugger could not be found. However, this is needed to analyze the file.

    Response: Make sure dbx is installed and is contained in the PATH if you want the core file to be analyzed.


    FMC34206W dbx message.

    Explanation: The configuration checker found a core file to analyze, but the debugger ignored it because of dbx message.

    Response: The core file might be older than the executable program file. Delete the core file.


    FMC34207W filename is not an MQSeries Workflow program file. The core file is ignored.

    Explanation: The configuration checker found a core file but did not analyze it. The failure was not caused by an MQSeries Workflow executable program file.

    Response: Delete the core file if you do not need it.


    FMC34208I File 'name' is dated date time

    Explanation: The configuration checker found the core file name of date time.

    Response: None.


    FMC34209I Use the '-d' option to analyze the core file.

    Explanation: The configuration checker found a core file but did not extract the stack contents.

    Response: If you need to extract the stack contents from the core file start the configuration checker again using the -d command-line option.


    FMC34210I Sanning core files not yet implemented for opsys (filename).

    Explanation: The configuration checker found a core file (filename) but core file scanning has not yet been implemented for platform opsys.

    Response: None.


    FMC34300E WinSock error: errormsg.

    Explanation: When the WinSock library was initialized, a problem occurred. WinSocket error errormsg was returned.

    Response: Check the WinSock documentation for information on how to fix the problem.


    FMC34301I WinSock version: version.

    Explanation: The WinSock library has been found and initialized. The WinSocket version is version.

    Response: None.


    FMC34302E TCP port portname not found.

    Explanation: The services file does not contain a required port definition. This error can occur if the directory where your services file is located could not be determined during the installation of MQSeries Workflow.

    Response: Use the tcp command of the configuration checker to update the services file or apply the changes manually. For details, see chapter 0.2, "Command-line options".

    If the port definition in the services file exists and you also got a message FMC34312E, see the explanation for this additional message.


    FMC34303I TCP port portname found at number portnumber.

    Explanation: This message states the port definitions in your services file.

    Response: None.


    FMC34304W TCP port portname found at wrong number portnumber1 (should be portnumber2).

    Explanation: Your services file contains incorrect port definitions.

    Response: Use the tcp command of the configuration checker' to update the services file or apply the changes manually. For details, see chapter 0.2, "Command-line options".


    FMC34305I TCP port name has been added to filename.

    Explanation: You started the configuration checker with the tcp command. TCP/IP's services file filename has been updated.

    Response: None.


    FMC34306I The local listener for port number is active.

    Explanation: The configuration checker successfully connected to the listener on port number.

    Response: None.


    FMC34307I The local listener for port number is not running.

    Explanation: The configuration checker tried to connected to port number but the listener process is not running.

    Response: Start the listener process for number.


    FMC34308W Connect to local port number timed out.

    Explanation: The configuration checker tried to connected to port number but the request timed out.

    Response: Make sure the listener process for number is started and try again.


    FMC34309I Alternative IP address found: IP address (interface).

    Explanation: Your machine has more than one IP address. The configuration checker lists the alternative IP addresses through which your machine can be reached.

    Response: None.


    FMC34311E Loopback adapter missing or no network connection.

    Explanation: If you have a stand-alone configuration, you must at least have the loopback adapter installed. Alternatively, you can install the Remote Access Service.

    Note that this error can also occur on Windows if you temporarily disconnected from the network. In this case TCP/IP lookup functions like gethostname will not work. This is a restriction of the Windows TCP/IP implementation.

    Response: Either install the Remote Access Service or go to the 'Adapters' page of the Network settings in the Control Panel and add the loopback adapter.


    FMC34312E The line of port in file is not valid.

    Explanation: The configuration checker could not find port port because its line in TPC/IP's services file file does not end with a newline character.

    Response: Add a newline character to the line of port in TCP/IP's services file.


    FMC34313E Could not resolve IP address for host hostname.

    Explanation: The configuration checker could not determine the IP address for host hostname

    Response: If you have configured DHCP, make sure it is working properly.


    FMC34314I The local IP address is address.

    Explanation: The configuration checker found that the IP address of the local host is address.

    Response: None.


    FMC34315E The local hostname is not configured.

    Explanation: The configuration checker tried to determine the local machine's hostname but got an error code from TCP/IP.

    Response: Make sure the machine's hostname is set in the TCP/IP configuration.


    FMC34316E The local IP address is not correctly configured.

    Explanation: The configuration checker tried to determine the local machine's IP address but got an error code from TCP/IP.

    Response: Make sure the machine's IP address is correctly set in the TCP/IP configuration.


    FMC34400E The MQSeries configuration file mqs.ini could not be found.

    Explanation: The configuration checker could not find the MQSeries configuration file mqs.ini.

    Response: Make sure MQSeries has been installed correctly.


    FMC34401E Queue Manager qmgr not found in filename or qm.ini for qmgr not found.

    Explanation: The queue manager qmgr was not found in the MQSeries configuration file filename or the queue manager configuration file qm.ini for queue manager qmgr could not be found.

    Response: Make sure that the queue manager qmgr is registered in filename and the qm.ini configuration file for this qmgr exists.


    FMC34402W Unrecognized product CSD level in filename: csdlevel.

    Explanation: The configuration checker checked MQSeries' syslevel file filename to verify that the correct CSD level has been installed and found an unrecognized CSD level.

    Response: Please send the file filename to the lab for a fix.


    FMC34403E No version information found for MQSeries component.

    Explanation: The configuration checker could not find version information for MQSeries when it tried to verify that the correct CSD level has been installed.

    Response: Make sure MQSeries component has been correctly installed.


    FMC34404I MQSeries component version is installed.

    Explanation: The configuration checker checked the CSD level of MQSeries compoenent and found that version version is installed.

    Response: None.


    FMC34405E MQSeries component actual version is installed, upgrade to required version.

    Explanation: The configuration checker checked the CSD level of MQSeries component and found that actual version is installed.

    Response: You must upgrade to required version for MQSeries Workflow to run correctly.


    FMC34406W MQSeries seems not to be installed.

    Explanation: You have an MQSeries Workflow component installed that requires MQSeries but MQSeries itself seems not to be installed.

    Note that this error is likely to happen when you installed the samples which contain the Runtime Client which in turn requires MQSeries to run. If you installed the samples but do not intent to use the Runtime Client, you can safely ignore this message.

    Response: Either install the MQSeries product or, if you do not actually need it, remove the MQSeries Workflow component that caused this error.


    FMC34500I ==> Database Manager configuration for instance.

    Explanation: The Database Manager configuration for instance is being checked.

    Response: None.


    FMC34501I ==> Database configuration for name.

    Explanation: The configuration for database name is being checked.

    Response: None.


    FMC34502I ==> Database connection to name.

    Explanation: The connection to database name is being checked.

    Response: None.


    FMC34503E command: message

    Explanation: Database error message occured when executing command.

    Response: See message for more details.

    If the message is [ODBC Driver Manager] Connection not open, you need to register the database using the ODBC settings of the Windows Control Panel.

    If you are using DB2, first check that DB2 has been started (use the db2start command). If you need to register the database, you can use the Client Configuration Assistent (Click 'Properties...'). Alternatively, you can issue the DB2 CATALOG SYSTEM ODBC DATA SOURCE <dbname> command.

    If the message is [ODBC Microsoft Access Driver] Couldn't find file '(unknown)', this means that the database file does not exist. Create the database and try again.


    FMC34504W command: message

    Explanation: Database warning message occured when executing command.

    Response: Check message if an action is required.


    FMC34505I name is value.

    Explanation: The Database Manager setting name is set to value.

    Response: None.


    FMC34506E name is value, should be at least minimum.

    Explanation: The Database Manager setting name is set to value but it should be at least minimum.

    Response: Use the db2 update dbm cfg command to increase the value of name.


    FMC34507I The TP monitor (library) need not be set on this platform.

    Explanation: The Database Manager setting TP_MON_NAME is set, although it is not needed on this platform.

    Response: You can remove the TP_MON_NAME setting. It is only needed for OS/2 and Windows.


    FMC34508I name is value.

    Explanation: The database configuration setting name is set to value.

    Response: None.


    FMC34509E name is value, must be at least minimum.

    Explanation: The database configuration setting name is set to value but it must be at least minimum. Note that if you are using the debug version of the configuration checker (check message FMC34010I at the very beginning), you can ignore this error if name is one of log file size, default application heap, or SQL statement heap.

    Response: Use the db2 update db cfg for <dbname> using <name> <value> command to increase the value of name. For example, use the db2 update db cfg for FMCDB using APPLHEAPSZ 256 command to set the value for the default application heap size.


    FMC34510I The DBMS name is name (version version).

    Explanation: A connection to the database was opened and the Database Management System is name, version version.

    Response: None.


    FMC34511I The database driver is name (version version).

    Explanation: A connection to the database was opened and the database driver (ODBC or CLI) is name, version version.

    Response: None.


    FMC34512I The database name for alias 'logical name' is 'internal name'.

    Explanation: A connection to database logical name was established and its internal name is displayed.

    Response: None.


    FMC34513I The following databases are available:

    Explanation: A connection to the MQSeries Workflow database you specified could not be established. The configuration checker will list the available databases. However, the databases listed are not necessarily MQSeries Workflow databases.

    Response: Change the MQSeries Workflow configuration to use one of the MQSeries Workflow databases listed below this message.


    FMC34514I dbname (description)

    Explanation: Database dbname is available through the database driver.

    Response: See message FMC34513I.


    FMC34515I Connect to dbname was successful (user ID 'ID').

    Explanation: The configuration checker successfully connected to database dbname as ID.

    Response: None.


    FMC34516E Variable name is not set (should be 'YES').

    Explanation: The environment variable name is not set but it is recommended to be set to YES for MQSeries Workflow. This can significantly reduce the deadlock probability. Please note that this setting is valid for the entire DB2 instance. If you have other databases besides the MQSeries Workflow database in this instance, you might experience other problems.

    Usually, this variable is set in the ~<db2instance>/sqllib/db2profile file where ~<db2instance> denotes the home directory of the DB2 instance user..

    Response: Set the enviroment variable DB2_RR_TO_RS to YES.


    FMC34517E Variable name is set to 'value' (should be 'YES').

    Explanation: The environment variable name is set to value but it should be set to YES. See message FMC34516E for more details.

    Response: Set the enviroment variable DB2_RR_TO_RS to YES.


    FMC34518E The TP monitor (TP_MON_NAME) is not set.

    Explanation: The Database Manager setting TP_MON_NAME is not set, but it is requied by MQSeries Workflow on this platform.

    Response: Set TP_MON_NAME in your Database Manager configuration.


    FMC34519I key is 'value' in the name section of filename.

    Explanation: The key in the DB2 configuration file filename is set to the recommended or required value value.

    Response: None.


    FMC34520E key should be 'value' in the name section of filename.

    Explanation: To avoid problems with large dynamic queries (such as staff resolution), set key to the recommended value value in the name section of the DB2 configuration file filename.

    Response: Edit filename and add an entry

    [<name>]
    <key>=<value>
    

    FMC34521E QueryTimeoutValue must be at least 60 in the 'Common' section of filename.

    Explanation: To avoid timeout problems with large Buildtime queries, set QueryTimeoutValue to at least 60 in the 'Common' section of the DB2 configuration file filename.

    Note: This problem is fixed with MQSeries Workflow versions 3.1.1 or later.

    Response: Edit filename and add an entry

    [Common]
    QueryTimeoutValue=60
    

    FMC34522E Fixpack for DB2 is not installed.

    Explanation: Buildtime requires at least fixpack WR09024 for DB2 5.0.

    Response: Make sure the required DB2 level is installed.


    FMC34523I component version.release.level has fixpack fixpack installed.

    Explanation: The DB2 component component is installed and fixpack fixpack has been applied.

    Response: None.


    FMC34524I component version.release.level is installed.

    Explanation: The DB2 component component is installed.

    Response: None.


    FMC34525W Inconsistent path setting in Registry: pathname and path.

    Explanation: The Windows Registry contains two different entries for the DB2 path name: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\DB2 Path Name=pathname and HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\GLOBAL_PROFILE\DB2PATH=path. The configuration checker will continue using pathname.

    Response: Make sure DB2 is installed correctly.


    FMC34526W DB2INSTANCE is 'envInst' but DB2 returns 'db2Inst' as current instance.

    Explanation: The environment variable DB2INSTANCE is set to envInst, but DB2 reports db2Inst as the current instance. The configuration checker will continue using db2Inst.

    Response: Make sure your environment is set up correctly.


    FMC34527E Database name not found.

    Explanation: The configuration checker tried to check the settings for DB name, but the database could not be found.

    Response: Make sure the DB name specified in the MQSeries Workflow profile is correct and the database exists.


    FMC34528W The database manager has not been started.

    Explanation: The configuration checker tried to check the database settings but it cannot connect to the database because the database manager has not been started. The configuration checker will not be able to perform all checks.

    Response: Run the db2start command to start the database manager and run the configuration checker again.


    FMC34529W DB2INSTANCE is db2Inst, but dbname's node is node.

    Explanation: DB2 reports db2Inst as current instance, but the database being checked, dbname, is catalogued on node node.

    Response: ??? (is this a problem at all?)


    FMC34530W You should run fmczchk under the user ID 'db2instance user' instead of 'current user'.

    Explanation: You are running MQSeries Workflow Configuration-checking Utility under current user which is different from the user ID db2instance user that will be used by DB2. That is, MQSeries Workflow Configuration-checking Utility cannot check the actual environment that will be used by DB2.

    Response: Log in as user db2instance user and run MQSeries Workflow Configuration-checking Utility again.


    FMC34531I DB2 authentication is through authentication.

    Explanation: DB2 authentication will be done through authentication. You can change this setting on the Authentication page of the DB2 instance.

    Response: None.


    FMC34532E ODBC data source name (odbc name) must be the same as DB name (db2 name).

    Explanation: The ODBC data source name is not the same as the DB2 database name of the Buildtime database. Otherwise you will not be able to remotely connect to this database.

    Response: Use the ODBC settings of the Windows Control Panel to change the ODBC data source name of the Buildtime database to be the same as the DB2 database name. You also must adjust the BTODBCDataSourceName setting in the MQSeries Workflow profile.


    FMC34533E user ID has no authorization for BT database db name.

    Explanation: The configuration checker successfully connected to the Buildtime database, but the current user user ID does not have access authorization to the contents of the database. The user user ID will not be able to work with the Buildtime database db name.

    Response: If you are using DB2, make sure you have granted user ID the appropriate access rights to db name. To do so, you can use the DB2 Control Center to add a new user to the database db name and to define its access authorizations.


    FMC34534E DB2INSTANCE is incorrect or not set.

    Explanation: The configuration checker tried to determine the active DB2 instance but got an error from DB2 indicating that the value of DB2INSTANCE is either incorrect or not set at all.

    Response: Make sure you have installed and configured DB2 correctly.


    FMC34535I Service 'name' does not exist, assuming DB2 client installation.

    Explanation: The Windows NT service for the DB2 instance name does not exist. The configuration checker will skip the service dependency checks for that instance. If this is not a DB2 client only installation, make sure that the DB2 instance has benn correctly created and re-run the configuration checker.

    Response: None.


    FMC34600I ==> Executing commands.

    Explanation: The configuration checker started executing the commands specified on the command-line or in the response file.

    Response: None.


    FMC34601E 'cmd' is not a valid command for version version.release.modlevel.

    Explanation: The configuration checker encountered an incorrect command. Use the -h command-line option to get a list of valid commands or refer to the online documentation, fmczchk.htm.

    Note that some commands availalbe in earlier releases may have been deprecated in later releases.

    Response: Correct the command and try again.


    FMC34602W Unnecessary argument for the 'cmd' command: arguments.

    Explanation: You ran the 'cmd' command and specified arguments. The command has been executed but the unnecessary arguments have been ignored.

    Response: Do not specify arguments the next time you run cmd.


    FMC34603E Key is required for the 'prf' command.

    Explanation: You tried to run the prf command but did not specify a key.

    Response: Correct the command and try again.


    FMC34604I key erased from the type profile.

    Explanation: The configuration checker successfully executed the prf command and erased key from the type profile.

    Response: None.


    FMC34605I key = 'value' inserted into the type profile.

    Explanation: The configuration checker successfully executed the prf command and inserted key with value into the type profile.

    Response: None.


    FMC34606E Profile type is required for profile command.

    Explanation: You tried to run a profile command, e.g. fix, but did not specify the profile type.

    Response: Correct the command and try again.


    FMC34607E Incorrect profile type type specified for profile command.

    Explanation: You tried to run a profile command, e.g. fix, but did not specify a valid profile type.

    Response: Correct the command and try again.


    FMC34608I No errors found in the profile.

    Explanation: The configuration checker executed the fix command against the profile but it did not contain any errors.

    Response: None


    FMC34609I profile(number): action 'line'.

    Explanation: The configuration checker executed the fix command against profile and corrected line number by performing action on line.

    Response: Check whether a required key was erased and add it again, if necessary (using the prf command).


    FMC34610E Service is required for for the 'tcp' command.

    Explanation: You tried to run the tcp command but did not specify a service.

    Response: Correct the command and try again.


    FMC34611E Port is required for the 'tcp' command.

    Explanation: You tried to run the tcp command but did not specify a port.

    Response: Correct the command and try again.


    FMC34612E Incorrect port port (number) specified for the 'tcp' command.

    Explanation: You tried to run the tcp command but did not specify a valid port - number must be a positive integer.

    Response: Correct the command and try again.


    FMC34613E System is required for the 'fml' command.

    Explanation: You tried to run the fml command but did not specify a system.

    Response: Correct the command and try again.


    FMC34614E DB2INSTANCE not found for the 'scm' command.

    Explanation: You tried to run the scm command but either you did not specify the db2inst argument or the configuration checker was unable to determine the default DB2INSTANCE.

    Response: Specify a db2inst argument or correct the error that occured when the configuration checker tried to determine the default DB2INSTANCE. Then try to start the scm command again.


    FMC34615I DB2INSTANCE db2inst is being used for dependency checking.

    Explanation: You ran the smc command and the instance db2inst was used for startup dependency checking.

    Response: None.


    FMC34616I All service startup dependencies are up-to-date.

    Explanation: You ran the scm command to update the service startup order but there were no changes required.

    Response: None.


    FMC34617I Changed start type to 'automatic' for service name.

    Explanation: You ran the scm command to update the service control manager database and the start type for service name was changed to automatic.

    Response: None.


    FMC34618I Added service to dependencies list of service name.

    Explanation: You ran the scm command to update the service control manager database and service has been added to the dependencies list of service name.

    Response: None.


    FMC34619I Successfully added system,qmgr to key in the type profile.

    Explanation: You ran the fml command to update the FMLConnectName setting and system,qmgr has been added to key in the MQSeries Workflow type profile.

    Response: None.


    FMC34620I Successfully changed system to qmgr in key in the type profile.

    Explanation: You ran the fml command to update the FMLConnectName setting and the queue manager for system has been changed to qmgr in key in the MQSeries Workflow type profile.

    Response: None.


    FMC34621I Successfully removed system from key in the type profile.

    Explanation: You ran the fml command to update the FMLConnectName setting and the queue manager for system has been removed from key in the MQSeries Workflow type profile.

    Response: None.


    FMC34622W No entry for system in key in the type profile found.

    Explanation: You ran the fml command to update the FMLConnectName setting but the type profile does not contain an entry for system in key.

    Response: Correct the system argument of the fml command and try again.


    FMC34623W Removed incorrect entry system in key in the type profile.

    Explanation: You ran the fml command to update the FMLConnectName setting and the entry for system in key in the MQSeries Workflow type profile had no queue manager specified. The incorrect entry has been removed.

    Response: Check whether the type profile contains the intended entries in key.


    FMC34624W Removed duplicate entry system,qmgr in key in the type profile.

    Explanation: You ran the fml command to update the FMLConnectName setting and the configuration checker found a duplicate entry for system in key in the MQSeries Workflow type profile. The duplicate entry has been removed.

    Response: Check if the type profile contains the intended entries in key.


    FMC34625I The service 'name' has been successfully deleted.

    Explanation: You ran the scm command with the d otpion to delete the MQSeries Workflow service namefrom the service control manager database and it has been removed successfully.

    Response: None.


    FMC34626I Changed account to 'userID' for service name.

    Explanation: You ran the scm command to update the service control manager database and the user id for service name was changed to userID.

    Response: None.


    FMC34627E The service name does not exist.

    Explanation: The MQSeries Workflow service name which you tried to delete using the scm command does not exist. Either it has already been deleted or it never was created.

    Response: None.


    FMC34628E 'option' is not a valid option for the 'scm' command.

    Explanation: The configuration checker encountered the unknown option option for the scm command.

    Response: Correct the syntax of the cmd command and try again.


    FMC34629I Account 'userID' will be used for services 'MQ service' and 'MQ Workflow service'.

    Explanation: You ran the smc command and the user ID userID will be set for the MQSeries service MQ service and for the MQSeries Workflow service MQ Workflow service. If a service already has userID assigned, it will not be changed.

    Response: None.


    FMC34630E Key 'key' not found in profile.

    Explanation: You ran the smc command with the u option to update the account information for the MQSeries service and for the MQSeries Workflow service but the configuration checker could not find the required value for key in the profile.

    Response: Make sure your MQSeries Workflow system is configured correctly.


    FMC34631I The service 'name' has been created successfully.

    Explanation: You ran the smc command and the configuration checker found that the service name for MQSeries Workflow did not yet exist. Therefore it created the service name with the parameters as specified.

    Response: None.


    FMC34632E The account userID is not valid.

    Explanation: You ran the smc command with the u option, but the account information userID is not valid. The user ID specified must be a valid Windows account. Note that if you do not specify an argument for the u option, the account information will be taken from the profile.

    Response: Make sure the user ID and password used by the scm command are valid and try again.


    FMC34633E Level is required for the 'trc' command.

    Explanation: You tried to run the trc command but did not specify a trace level.

    Response: Correct the command and try again.


    FMC34634E Level 'level' is not valid for the 'trc' command.

    Explanation: You tried to run the trc command but did not specify a valid trace level. Either level is not numeric or outside the allowed range 0..3.

    Response: Correct the command and try again.


    FMC34635I The SCM database had to be updated, please re-run the command.

    Explanation: The configuration checker has found inconsistent MQSeries Workflow settings in the Service Control Manager database which have been corrected. The scm command you specified has probably not been executed.

    Response: Check if you still need to execute the scm command after the Service Control Manager database updates performed by the configuration checker. If yes, simply run the configuration checker with the same command-line options again.


    FMC34636E Cannot create service 'service' because the file filename does not exist.

    Explanation: You specified the scm command to create an entry in the Service Control Manager database. However, the service service could not be created because the prerequiste file filename cannot be found.

    Response: Make sure you the Administration Server is installed and try again.


    FMC34637W Account user ID of service 'service' had to be reset.

    Explanation: You had set up the service service to run using the user ID account. This account information could not be migrated by the configuration checker since the password is protected.

    Response: Run the configuration checker again with the scm:u=UID,p=PWD command to change the account information back if necessary.


    FMC34638I MQWF 3.2.0 service 'service' has been successfully updated.

    Explanation: The configuration checker detected and updated an inconsistent entry for MQSeries Workflow release 3.2.0 in the Service Control Manager database. This entry has been successfully corrected.

    Response: None.


    FMC34700I ==> Service Control Manager configuration.

    Explanation: The service control manager configuration is being checked.

    Response: None.


    FMC34701I The Administration Server cannot be started as a service.

    Explanation: The Administration Server is either not registered with the Windows NT service control manager or it is currently disabled.

    Response: If you want to run the Administration Server as a service, make sure it is installed and its Startup Type is set to either 'Manual' or 'Automatic'. You should use the scm command of the configuration checker to ensure all dependencies are correctly registered.


    FMC34702W Dependency of service1 on service2 not registered.

    Explanation: A required startup dependency has not been registered with the Windows NT service control manager.

    Response: Use the scm command of the configuration checker to ensure all dependencies are correctly registered.


    FMC34703E The service name is disabled.

    Explanation: The MQSeries Workflow Administration Server cannot be started automatically as a Windows NT service because the service name is currently disabled.

    Response: Open 'Services' from the Control Panel and set the Startup Type of name to either 'Manual' or 'Automatic'.


    FMC34704E The service name does not exist.

    Explanation: The service name which is required to run MQSeries Workflow as a Windows NT service could not be found in the service control manager database.

    Response: Make sure the prerequisite services as well as MQSeries Workflow have been installed. Currently, the DB2 service and the MQSeries service are prerequisite.


    FMC34705W No autostart script registered with MQSeries.

    Explanation: The MQSeries Workflow Administration Server is configured to be started as a Windows NT service. For this to work, you must register an autostart script with MQSeries which starts the Queue Manager, Trigger Monitor, and TCP/IP Listener processes required by the Administration Server.

    Response: Create a file fmcstart.cmd in the MQSeries directory with the following contents:

    strmqm <qmgr>
    runmqlsr -t tcp -p 1414 /M <qmgr>
    runmqtrm /M <qmgr>
    
    Then register this autostart script with MQSeries by issuing the following command:
    scmmqm -a -s <path>\fmstart.cmd <qmgr>
    
    In the examples above, you must replace <qmgr> with the actual queue manager name. Also verify whether you need to use a TCP/IP port other than the default 1414.

    FMC34800W The JAVA_HOME environment variable is not set.

    Explanation: The environment variable JAVA_HOME required by the Java Agent startup scripts that are created by the configuration utility is not set.

    Note that this environment variable is only necessary for MQSeries Workflow release 3.2.0. Later releases (including 3.2.1) allow to set the JDK path with the configuration utility.

    Response: Make sure the JAVA_HOME environment variable is set and points to the directory where the JVM to be used by the Java Agent startup scripts is installed. Note that either rj.jar or classes.zip must exist in the lib subdirectory of JAVA_HOME.


    FMC34801I The Java Agent startup scripts will use the JRE from directory.

    Explanation: The Java Virtual Machine used by the Java Agent startup scripts is the JRE installed in directory.

    Response: None.


    FMC34802I The Java Agent startup scripts will use the JDK from directory.

    Explanation: The Java Virtual Machine used by the Java Agent startup scripts is the JDK installed in directory.

    Response: None.


    FMC34803E The Java Agent name is not set in the profile.

    Explanation: The required profile setting Agent.Name is not set for the current configuration.

    Response: Use the configuration utility to specify a name to be used for the Java Agent.


    FMC34804I The Java Agent name will use locator policy policy.

    Explanation: The Java Agent name will use the locator policy policy as specified in the MQSeries Workflow profile.

    Response: None.


    FMC34805E The locator policy policy for name is invalid.

    Explanation: The locator policy for the Java Agent name specified in the MQSeries Workflow profile is invalid. Note that the LOC_LOCATOR policy must only be used with the Java API and may not be set in the profile.

    Response: Use the configuration utility to correct the Agent.Locator setting in the MQSeries Workflow profile.


    FMC34806I setting used by the policy policy for Agent name is set to 'value'.

    Explanation: The setting setting required by the locator policy policy for Agent name is set to value.

    Response: None.


    FMC34807W The setting setting is not used by the policy policy for Agent name.

    Explanation: The MQSeries Workflow profile contains Java Agent settings that are not used by the currently configured locator policy.

    Response: None.


    FMC34808W Java could not be found in the PATH.

    Explanation: The configuration checker tried to find the Java installation directory but did not find java nor jre in the PATH.

    Response: The configuration checker will continue by trying to dynamically load the Java library.


    FMC34809I The Java installation directory is 'name'.

    Explanation: The configuration checker found that Java is installed in the directory name.

    Response: None.


    FMC34810I The Java system property name is 'value'.

    Explanation: The name property of Java is set to value.

    Response: None.


    FMC34811E The Java version version is not supported by the MQWF Java API.

    Explanation: The configuration checker found that Java version version is installed. This version of Java is currently not supported by MQSeries Workflow

    Response: Make sure you are using Java version 1.1.x where x>=6.


    FMC34999I Configuration checker ended: num1 error(s), num2 warning(s), rc = code.

    Explanation: The configuration checker has finished with num1 errors and num2 warnings.

    Response: If there are errors or warnings, search the fmczchk.log file for the appropriate message suffix (E: or W: , respectively) and check the online documentation, fmczchk.htm, how to solve each problem.