| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| migrating to MQWF 3.5 |
« View previous topic :: View next topic » |
| Author |
Message
|
| SpitFire |
 Posted: Tue Sep 27, 2005 12:10 am Post subject: migrating to MQWF 3.5 |
 |
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
Hi all,
I'm trying to migrate an application running on MQWF 3.3 to MQWF 3.5. The exact current and new configs/versions are as shown.
Current Config:
MQ Series 5.2.1
DB2 7.2 (fix pack 4)
MQ Workflow 3.3.0
New Config:
MQ Series 5.3 (Fix pack 10)
DB2 8.1 (Fix pack 2)
MQ Workflow 3.5
I exported the flows from Buildtime by exporting to an FDL. I also took the runtime database backup, as mentioned in the migration procedure part of MQWF installation handbook.
Later I migrated MQ, migrated DB2 (installed DB2, updated with fixpacks, migrated the DB), and finally, installed MQWF 3.5.
I dropped the existing buildtime database, migrated the runtime DB and finally recreated the buildtime DB, as follows.
fmcbdcdb -o=db -y <configID>
fmczm350 -d -c -b -n <runtime DB name>
fmcbdcdb -d=<buildtime DB name> -y <config ID>
fmcbcimp -y <config ID>
Now when I open the new buildtime, and imported the old FDL, it happens peacefully. I saved and verified it, and also exported it.
Now when I run fmcibie on the FDL, it hangs... 
9/27/2005 12:43:28 PM FMC24500I fmcibie is starting.
9/27/2005 12:43:28 PM FMC24510I Import uses options
System Group name : FMCGRP
import file : Sample.fdl
log file : C:\FMCIBIE_LOG.txt
9/27/2005 12:43:28 PM FMC20500I Start parsing Sample.fdl.
9/27/2005 12:43:29 PM FMC25100I REPLACE STRUCTURE 'Default Data Structure' finished.
9/27/2005 12:43:29 PM FMC25100I REPLACE STRUCTURE 'PersonDetails' finished.
9/27/2005 12:43:29 PM FMC25100I REPLACE PROCESS_CATEGORY 'PassportApp' finished.
>>> (hangs here... No response from fmcibie henceforth)
How do I solve this problem?
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
 |
| hos |
| Posted: Tue Sep 27, 2005 7:35 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
have you applied the latest ServicePack for MQWF 3.5? I do not know whether your problem is related to a known bug, but it is ALWAYS a good idea to apply ServicePacks not only to DB2 and MQ but also to MQWF!
If this does not solve your problem you should open a PMR. |
|
| Back to top |
|
|
| SpitFire |
| Posted: Tue Sep 27, 2005 10:13 pm Post subject: fmczchk output |
|
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
Thanks for the suggestion. Do you mind enlightening me on PMR??
I have also included the output of fmczchk here... hope with that I can get some help here 
WebSphere MQ Workflow Configuration-checking Utility
--------------------------------------------------------------------------------
Table of Contents
0.1 About the WebSphere MQ Workflow Configuration-checking Utility
0.2 Command-line options
0.3 Configuration checker messages
FMC34010I Configuration checker version version started.
FMC34011I Performing
FMC34012I ==> component checks.
FMC34013I ==> component found, checks started.
FMC34014I ==> component (filename) is 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 loading libname: errorcode.
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.
FMC34037E Error adding key=value to file: message.
FMC34038E Error erasing key from file: message.
FMC34100I Messages have been written to filename.
FMC34101I The Operating System is opsys.
FMC34102I Assuming name as the
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 is 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
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
FMC34132I The XPG4 locale is locale.
FMC34133I The ANSI code page is ansi_cp, the OEM code page is oem_cp.
FMC34134I The locale file 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 file 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 code page 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 compatibility variable name has an incorrect value 'value'.
FMC34151E The locale files name could not be loaded.
FMC34152I Using non-standard installation directory 'name'.
FMC34153W Installed Version is installed version, checks requested for Version specified version.
FMC34154I
FMC34155E The current configuration 'name' does not exist.
FMC34156E Required patch patchID-required version is not installed, installed version is: installed version.
FMC34157I Patch patchID-installed version is installed, minimum required version is required version.
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
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 configured correctly.
FMC34317I Need root user authority to create a raw socket for ping.
FMC34318I Your TCP/IP does not support raw sockets.
FMC34319W Ping failed because the network or host is unreachable.
FMC34320W Ping timeout after nns.
FMC34321E Server host serverhost is unreachable.
FMC34322E Ping expected ICMP_ECHOREPLY, got message type msgtype (code msgcode).
FMC34323E Server host 'serverhost' not found.
FMC34324I Ping serverhost successful.
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 The MQSeries component version is installed.
FMC34405E The MQSeries component actual version is installed, you need to upgrade to required version.
FMC34406W MQSeries appears not to be installed.
FMC34407W User user ID does not have connect authority.
FMC34408I User user ID has connect authority.
FMC34409W Got error 'error' reading configuration of queue manager qmgr in location.
FMC34410I Channel table filename has num entries.
FMC34411I index: status; Queue Manager qmgr connecting to name through protocol.
FMC34412E The IPCC base address address for Queue Manager qmgr conflicts with Java 2.
FMC34413I The IPCC base address for Queue Manager qmgr is address.
FMC34414W The environment variable name is set to 'actual value', but it must be set to 'required value'.
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 set to 'YES').
FMC34517E Variable name is set to 'value' (should be set to '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.
FMC34531I DB2 authentication is through db2instance user.
FMC34532E ODBC data source name (odbc name) must be the same as the 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.
FMC34536W The installation of component appears to be incomplete.
FMC34537E Package package has isolation level actual level, should have required level.
FMC34538E Instance for qmgr is qmInst, but DB2INSTANCE is set to envInst.
FMC34539E The TP monitor (library) must not be set on this platform.
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 'user ID' for service name.
FMC34627E The service name does not exist.
FMC34628E 'option' is not a valid option for the 'scm' command.
FMC34629I Account 'user ID' 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 user ID 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, run the command again.
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.
FMC34639I Service 'name' does not exist, assuming oracle client installation.
FMC34640E Oracle SID not specified for the 'scm' command.
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 not valid.
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 defined 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.
FMC34812E The Java Agent locator is not set in the profile.
FMC34813W The JDK version is version, you need to upgrade to Version 1.1.6.8.
FMC34998I See fmczchk.htm for more information on the messages.
FMC34999I Configuration checker ended: num1 error(s), num2 warning(s), rc = code.
--------------------------------------------------------------------------------
0.1 About the WebSphere MQ Workflow Configuration-checking Utility
The WebSphere MQ Workflow Configuration-checking Utility, hereafter referred to as configuration checker, verifies your WebSphere MQ Workflow installation. Start the configuration checker after having installed WebSphere MQ Workflow and after having changed your WebSphere MQ 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.
--------------------------------------------------------------------------------
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:
-332,-340,-350
Specify the version of checks that you want to use. The default is the version the configuration checker was built with. Depending on the WebSphere MQ 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 runs as a background process.
-d
Show debug messages. These are intended for use by the WebSphere MQ 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 WebSphere MQ 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 used for writing the log file. If this file already exists, the messages are appended and do not overwrite existing entries in the file.
-y qualifier / ID
Allows to specify a configuration ID other than the default that is to be used for the checks.
-c command[;...]
Perform command(s). The following commands are valid:
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 shows 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.
sca:[filemask;...]
Specify this command to scan all WebSphere MQ 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 that are required for the WebSphere MQ Workflow service. It also creates or updates the MQSeries Workflow service in the SCM database according to the options you specified. In MQSeries Workflow Version 3.2.0 and subsequent release levels, each configuration uses 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 you want to use.
If the optional argument u is not specified, the account information for the WebSphere MQ Workflow service will be set to SYSTEM, and the starter of the IBM MQSeries service will be left unchanged. If u is specified without the optional argument uid, the account information (user ID and password) for the WebSphere MQ Workflow and IBM MQSeries services is taken from the WebSphere MQ Workflow profile.
If the optional argument db2inst is not specifed, the configuration checker uses the value of the DB2INSTANCE variable.
The start type of the WebSphere MQ Workflow service will be set to manual, unless you specify the a option. If you specify the a option, 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 WebSphere MQ Workflow service from the Windows NT Service Control Manager database. The following is valid for WebSphere MQ Workflow Version 3.2.0 and subsequent release levels only: If you want to delete the service for any other 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][,split][,flipflop][,filesize]
To enable tracing, specify a trace level in the range of 1 through 3. Optionally, you can specify a trace file (without the log extension) and the split and flipflop flags. In the case of flipflop, you can optionally specify a file size (in KBs). Trace file splitting and flipflop tracing are enabled by setting the respective flags to 1.
fmczchk -c trc:1
fmczchk -c trc:3,/tmp/traces/my_trace
fmczchk -c trc:1,/tmp/traces/my_trace,1,1,5000
fmczchk -c trc:2,,1
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
Note that for Version 3.2.2 and subsequent release levels, the format of the response file has changed. You must now prefix the commands with the -c option.This allows you to specify other options as well. For example,
-c prf:Language,enu
-y FMC1
--------------------------------------------------------------------------------
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 WebSphere MQ 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
Explanation: This message shows the WebSphere MQ 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 WebSphere MQ Workflow component component was found and is being checked.
Response: None.
--------------------------------------------------------------------------------
FMC34014I ==> component (filename) is not installed.
Explanation: The WebSphere MQ Workflow component component was not found and cannot be checked.
Response: Install the component if required.
--------------------------------------------------------------------------------
FMC34015I ==> component found, no checks defined.
Explanation: The WebSphere MQ 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 WebSphere MQ 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 WebSphere MQ Workflow development.
--------------------------------------------------------------------------------
FMC34018E Error reading file 'filename'.
Explanation: One of the following occurred: The configuration checker could not open file filename to read its contents or the configuration checker encoutered problems 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 WebSphere MQ 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 WebSphere MQ Workflow is 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 loading libname: errorcode.
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 occurred.
Response: If the problem cannot be solved, contact the WebSphere MQ Workflow development team.
--------------------------------------------------------------------------------
FMC34026E Error opening profile: message.
Explanation: The WebSphere MQ Workflow profile could not be opened.
Response: Check the message and try again.
--------------------------------------------------------------------------------
FMC34027E profile: Line number is corrupt.
Explanation: The WebSphere MQ 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 occurred 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 occurred 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 occurred when the configuration checker tried to repair the WebSphere MQ Workflow profile.
Response: Check message and try again.
--------------------------------------------------------------------------------
FMC34031I Successfully loaded description library name.
Explanation: The configuration checker successfully loaded a library required by WebSphere MQ Workflow.
Response: None.
--------------------------------------------------------------------------------
FMC34032E Cannot load description library name: errormsg (rc = errorcode).
Explanation: Error errormsg 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 WebSphere MQ 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 WebSphere MQ 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 WebSphere MQ Workflow profile filename could not be opened.
Response: Check the access rights of filename and try again.
--------------------------------------------------------------------------------
FMC34037E Error adding key=value to file: message.
Explanation: An error occurred when the configuration checker tried to add key to the profile file.
Response: Check the message and try again.
--------------------------------------------------------------------------------
FMC34038E Error erasing key from file: message.
Explanation: An error occurred when the configuration checker tried to erase key from the profile file.
Response: Check the message and try again..
--------------------------------------------------------------------------------
FMC34100I Messages have been written to filename.
Explanation: filename indicates the fully qualified path name of the file that is used by the configuration checker to write the 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
Explanation: No entry for the installation directory was found in the WebSphere MQ Workflow profile. The current directory is therefore tken as the WebSphere MQ Workflow bin directory.
Response: Make sure that WebSphere MQ 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, WebSphere MQ 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 is 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 the version is incorrect.
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 WebSphere MQ 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 WebSphere MQ 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 WebSphere MQ 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
Explanation: The configuration checker did not find the directory where WebSphere MQ Workflow is installed.
Response: Install WebSphere MQ 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: The following applies to WebSphere MQ Workflow Version 3.1.2 and previous release levels: The setting of FMC_SYSTEM_QUALIFIER being used by the configuration checker is qualifier.
The following applies to WebSphere MQ Workflow Version 3.2.0 and subsequent release levels: The configuration being checked is name.
Response: You can use the -y command-line option to specify any other name than 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 WebSphere MQ Workflow message catalog files. NLSPATH must at least contain the WebSphere MQ 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 (for WebSphere MQ Workflow Version 3.1.2 including preceding release levels) or configuration ID (for WebSphere MQ Workflow Version 3.2.0 and subsequent release levels) 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
Explanation: WebSphere MQ 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 code page conversions.
Response: None.
--------------------------------------------------------------------------------
FMC34133I The ANSI code page is ansi_cp, the OEM code page is oem_cp.
Explanation: Windows systems use two code pages. The ANSI code page for Window applications, and the OEM code page for DOS applications. WebSphere MQ Workflow uses the ANSI code page ansi_cp for code page conversions. The OEM code page oem_cp is only used by the WebSphere MQ Workflow command-line utilities to display messages.
Response: None.
--------------------------------------------------------------------------------
FMC34134I The locale file 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 code page conversion are taken from name.
Response: None.
--------------------------------------------------------------------------------
FMC34135I The type profile is name.
Explanation: The WebSphere MQ Workflow profiles are stored as flat files for this platform. The name of the type profile file is name.
Response: None.
--------------------------------------------------------------------------------
FMC34136I The user profile for user is name.
Explanation: The WebSphere MQ 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 WebSphere MQ Workflow to locate the user profile. This problem can occur 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 profile of the previous user.
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 taken 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 code page conversion tables.
Response: Make sure the LOCPATH environment variable is set correctly.
--------------------------------------------------------------------------------
FMC34140E The locale file 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 file 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. On Windows, make sure the Regional settings in the Control Panel are set up correctly for the language you are using. If the system is set up correctly and you still get this message, you might have an unsupported combination of locale and code page.
--------------------------------------------------------------------------------
FMC34141E No default configuration ID set.
Explanation: There is no default configuration defined. WebSphere MQ Workflow cannot be used.
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. WebSphere MQ Workflow cannot be used.
Response: For WebSphere MQ Workflow Version 3.1.2 and preceding release levels: Set the environment variable FMC_SYSTEM_QUALIFIER to configuration you defined (see message FMC34145I).
For WebSphere MQ Workflow Version 3.2.0 and subsequent release levels: Use the configuration utility to define the default configuration which will be used as current configuration unless it is 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 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. WebSphere MQ Workflow cannot be used.
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 (also refer to message FMC34121I) or to edit the available configurations.
Response: None.
--------------------------------------------------------------------------------
FMC34146I The current code page is cp.
Explanation: The name of the current code page is cp.
Response: None.
--------------------------------------------------------------------------------
FMC34147E The Unicode converters are not installed.
Explanation: The components for code page conversion to Unicode are not installed. WebSphere MQ Workflow cannot be used if Unicode code page 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. However, the online documentation name is not in the current directory, that is, the directory of the HTML log file. Therefore, the hyperlinks in the HTML log file will not work.
Response: Change to the directory where WebSphere MQ Workflow is installed (where fmczchk.htm is located) and run the configuration checker again.
--------------------------------------------------------------------------------
FMC34149I The FlowMark V2 API compatibility setting name is set to value.
Explanation: The WebSphere MQ Workflow setting name required for the FlowMark V2 compatibilty API is set to value.
Response: None.
--------------------------------------------------------------------------------
FMC34150E The FlowMark V2 API compatibility variable name has an incorrect value 'value'.
Explanation: The WebSphere MQ Workflow setting name has a value that cannot be used. Possible values are DEFAULT, PRESENT, and PRESENTHERE.
Response: Change the value of name in the WebSphere MQ 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 you use MS Windows as operating system and this problem occurs, make sure that the library fmcwmthi.dll is installed and can be loaded.
--------------------------------------------------------------------------------
FMC34152I Using non-standard installation directory 'name'.
Explanation: You have set the environment variable FMC_INSTALLATION_DIRECTORY to point to a non-default installation directory, name.
Response: None.
--------------------------------------------------------------------------------
FMC34153W Installed Version is installed version, checks requested for Version specified version.
Explanation: The version of the WebSphere MQ Workflow Configuration-checking Utility you are using is not built for the version of WebSphere MQ Workflow you have installed or you specified another version on the command line than you have installed.
Response: Specify the installed version on the command line of the WebSphere MQ Workflow Configuration-checking Utility.
--------------------------------------------------------------------------------
FMC34154I
Explanation: The installed version appears to be installed version of MQSeries Workflow.
Response: None.
--------------------------------------------------------------------------------
FMC34155E The current configuration 'name' does not exist.
Explanation: The current configuration ID is set to name, but this configuration does not exist. WebSphere MQ Workflow cannot be used.
Response: Use the -y command-line option to specify another configuration name to be used.
--------------------------------------------------------------------------------
FMC34156E Required patch patchID-required version is not installed, installed version is: installed version.
Explanation: A required patch is not installed or the installed version is too old.
Response: Install at least the required version of the patch patchID
--------------------------------------------------------------------------------
FMC34157I Patch patchID-installed version is installed, minimum required version is required version.
Explanation: A required patch was found.
Response: None.
--------------------------------------------------------------------------------
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 WebSphere MQ Workflow version in filename.
Response: This check does not work with non-WebSphere MQ 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
Explanation: The configuration checker found a core file but did not analyze it. The failure was not caused by an WebSphere MQ 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 WebSphere MQ 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 disconnected only temporarily from the network. If this is the case, TCP/IP lookup functions, such as gethostname will not work. This is a restriction of the Windows TCP/IP implementation.
Response: 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 hostname of the machine is set in the TCP/IP configuration.
--------------------------------------------------------------------------------
FMC34316E The local IP address is not configured correctly.
Explanation: The configuration checker tried to determine the IP address of the machine but got an error code was received from TCP/IP.
Response: Make sure the IP address of the machine is defined correctly in the TCP/IP configuration.
--------------------------------------------------------------------------------
FMC34317I Need root user authority to create a raw socket for ping.
Explanation: If you want to do a ping on a UNIX systems, you need root user authority.
Response: Either run the configuration checker from the root account or make sure that the SetUID permission of root is set for the configuration checker.
--------------------------------------------------------------------------------
FMC34318I Your TCP/IP does not support raw sockets.
Explanation: The configuration checker tried to do a TCP/IP ping, but the TCP/IP product you are using does not support raw sockets which are required for this.
Response: You have to check the TCP/IP connection manually, using the ping program that comes with the TCP/IP product you are using.
--------------------------------------------------------------------------------
FMC34319W Ping failed because the network or host is unreachable.
Explanation: The configuration checker tried to ping another host but either the network or the host are currently unreachable.
Response: Make sure TCP/IP is up and running then try again.
--------------------------------------------------------------------------------
FMC34320W Ping timeout after nns.
Explanation: A timeout occurred after nn seconds when the configuration checker tried to establish a connection with a server.
Response: Make sure that the connections in your network are active and that the server can be reached.
--------------------------------------------------------------------------------
FMC34321E Server host serverhost is unreachable.
Explanation: The configuration checker tried to establish a connection with the server serverhost but received a return code from TCP/IP indicating that the server currently cannot be reached.
Response: Check your network configuration.
--------------------------------------------------------------------------------
FMC34322E Ping expected ICMP_ECHOREPLY, got message type msgtype (code msgcode).
Explanation: The configuration checker got an unexpected response, trying to establish a connection with a server.
Response: Run the the configuration checker again.
--------------------------------------------------------------------------------
FMC34323E Server host 'serverhost' not found.
Explanation: The host name of a server could not be resolved.
Response: Check if the name server is configured correctly. Use the nslookup or ping command to check if the server can be found using native TCP/IP.
--------------------------------------------------------------------------------
FMC34324I Ping serverhost successful.
Explanation: The configuration checker successfully established a TCP/IP connection with a server.
Response: None.
--------------------------------------------------------------------------------
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 is 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.
-----------------------------------------------------------------------------
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
|
| SpitFire |
| Posted: Wed Sep 28, 2005 1:58 am Post subject: is uninstallation required? |
|
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
One silly question...
As far as the migration document from IBM is considered, it doesn't mention an uninstallation of the previous version (i.e., MQWF 3.3) before installing MQWF 3.5, the latest version required, in Windows. The uninstallation procedure is only mentioned for UNIX flavors. Is this wrong?
Is it necessary to remove the old version prior to installing the new one? Right now, I've both the versions displayed in my "Add/Remove Programs" list, in Windows 2000 Advanced Server. I feel that the uninstallation is required. Am I overlooking something ?(as usual???).
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
|
| fidelio |
| Posted: Wed Sep 28, 2005 12:43 pm Post subject: Re: is uninstallation required? |
|
|
Apprentice
Joined: 14 Sep 2005
Posts: 45
Location: AttainBPM
|
| _z33 wrote: |
One silly question...
As far as the migration document from IBM is considered, it doesn't mention an uninstallation of the previous version (i.e., MQWF 3.3) before installing MQWF 3.5, the latest version required, in Windows. The uninstallation procedure is only mentioned for UNIX flavors. Is this wrong?
Is it necessary to remove the old version prior to installing the new one? Right now, I've both the versions displayed in my "Add/Remove Programs" list, in Windows 2000 Advanced Server. I feel that the uninstallation is required. Am I overlooking something ?(as usual???). |
I don't know if uninstalling the old version is required, but it certainly helps. I always do... |
|
| Back to top |
|
|
| SpitFire |
| Posted: Wed Sep 28, 2005 8:49 pm Post subject: Service Pack - of no use |
|
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
I am yet to try the uninstallation of MQWF 3.3, prior to installing MQWF 3.5. Hope at least that works.
I tried in fact, installing Service Pack 5 for MQWF 3.5, and then tried migration; It still doesn't work! Not even an iota of improvement
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
