WebSphere MQ for Linux for Intel and Linux for zSeries, V5.3 README
Welcome to WebSphere MQ for Linux, Version 5.3.
This README file applies to WebSphere MQ books dated October 2002.
The content of this readme applies to the WebSphere MQ for Linux for Intel and WebSphere MQ for Linux for zSeries products unless otherwise stated.
This README file contains information that was not available in time for our publications. In addition to this file, README.TXT, you can find more information on the WebSphere MQ Web site:
http://www.ibm.com/software/products/en/ibm-mq
The SupportPac™ web page is here:
http://www.ibm.com/software/integration/support/supportpacs/
For current information on known problems and available fixes, see the Support Summary page of the WebSphere MQ web site here:
http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006037
Web documentation updates
The latest updates to the web-based WebSphere MQ documentation are now available from the WebSphere MQ Web site here:
http://www.ibm.com/software/integration/wmq/library/
Note that latest changes are shown in red and earlier changes are shown in blue.
The Change History is located at the bottom of the page.
WebSphere MQ for Linux Electronic Software Download installation
Introduction
These instructions apply to installing WebSphere MQ for Linux for Intel and Linux for zSeries V5.3 from an installation image downloaded from IBM. Use it with the Quick Beginnings manual for this release. A version of the Quick Beginnings book is available from the download site; it has a description of 'WebSphere MQ V5.3.1 Install Doc'. The installation image is provided as a compressed tape archive (tar) file.
Installation Steps
- Copy the WebSphere MQ tar file to a suitable directory accessible to the machines where the software is to be installed. This directory must be on a file system with at least 310MB of free space (Linux for Intel), or 150MB of free space (Linux for zSeries). This is in addition to the disk space required for the product, as detailed in the Quick Beginnings publication).
- Make this directory the current directory and use the appropriate command :
tar -xvf MQ53ClientSSL_LinuxIntel.tar
tar -xvf MQ53ClientSSL_LinuxzSeries.tar
to create the appropriate installation image.
- After this operation succeeds, you can delete the .tar file
- Use the WebSphere MQ for Linux Intel and Linux zSeries V5.3 Quick Beginnings manual to install and configure the product. Replace any references to the CD drive by the directory used in the steps above.
All other instructions remain the same.
WebSphere MQ for Linux for Intel and Linux for zSeries V5.3 Quick Beginnings
Chapter 1, "Planning to install WebSphere MQ for Linux products"
In the section "Prerequisite software" subsection "Operating System, Linux for zSeries" the RedHat distribution tested is RedHat Linux release V7.2. in the "SSL" section add:
If you want to use SSL channels on WebSphere MQ for Linux for Intel, you must install the following C++ runtime libraries:
libgcc_s.so
libstdc++.so.3
These libraries are installed with the GNU C++ compiler, version 3 and are available separately from your distribution vendor.
If you want to build C++ client applications that use SSL channels, you must use the GNU C++ compiler, version 3.
In the section "Compiler runtime environment, Linux for Intel", the section describes the g++ version 3.0 compiler and its runtime libraries as a prerequisite if you want to use the SSL support with MQ. If your distribution does not come with this compiler or these libraries, this section describes how you can download the source for the compiler and build the required components. However, there are a few preparations you must make to ensure that, once complete, the new versions of these components are available for use by MQ:
By default the compiler is installed in the directory prefix of:
/usr/local, so the compiler executables are installed into
/usr/local/bin and the runtime support libraries into /usr/local/lib.
If you build the compiler with this default, you might need to take some additional steps to ensure that the runtime support libraries can be found by MQ. You can do this by doing one of:
- Updating /etc/ld.so.config to include /usr/local/lib in the search path for libraries. (This may already be defined, depending on your distribution.)
- Copying and linking the runtime support libraries (libgcc_s.so and libstdc++.so.3) in /usr/local/lib to /usr/lib.
If you modify /etc/ld.so.config, you need to run the ldconfig command for the changes to take effect. Refer to the manual page for ldconfig for details.
Another option is to change the prefix used to build the compiler to /usr instead of /usr/local using the --prefix option on the configure command. However, doing this overwrites the executable files for the previously installed compiler.
We recommend that you create backup copies of the compiler executable files. These are gcc and g++ for the C and C++ compilers, but there might be others if you are using the GNU Fortran or GNU Java™ Compilers.
Create the backup copies by copying them to gcc-<version> and g++-<version> respectively (replacing <version> with the version number of the existing compiler). In this way you can compile programs with the previous version of the compiler by using the compiler name suffixed with the version string. Using
this method you can have multiple versions of the compiler installed.
Also, if you choose to build the compiler support rather than installing it from pre-built rpm files, the rpm database is not updated to reflect that these libraries have now been installed, so you might still get an error that this dependency is missing when you try to install the gskit rpm file.
In this case install the gskit component using the additional option --nodeps, which does not perform the dependency checking while installing that rpm.
Replace the text in the section "Compiler runtime environment, Linux for zSeries" with:
WebSphere MQ for Linux for zSeries is built using the GNU C and C++ compilers, version 2.95.3. If you want to use the C++ Bindings provided with WebSphere MQ then you must use this level of the compiler to build your C++ applications.
The SSL channels have a dependency on the C++ runtime provided with version 2.95.2 of the g++ compiler, called libstdc++-libc6.1.2.so.3 and normally found in /usr/lib. If you intend to run SSL channels you should ensure that this library is available on your system. If this is not available it can be obtained by installing the 'libstdc++' compat library provided by your distribution vendor.
In the section "Optional software", subsection "Compilers, Linux for Intel" in the "Java applications" add
IBM 32-bit SDK for Linux on Intel, Java 2 Technology Edition.Version 1.4
After section "Databases, Linux for Intel"
Add
Databases, Linux for zSeries
The following database is supported:
DB2(R) Universal Database V7.2, Fixpak 6
Chapter 3, "Installing the WebSphere MQ for Linux for Intel and Linux for zSeries server"
In the section "Kernel configuration", after the section "Shared memory", add:
System V IPC message queues
WebSphere MQ uses two System V IPC message queues for each queue manager using linear logging. The default is 16 in the Linux 2.4 kernel, although some distributions increase this. For example, the default on RedHat 7.3 is 128; the default on SuSE is 16. If you need to define several queue managers with linear logging, check that the number of System V IPC message queues is adequate.
To view the current value, enter the command:
cat /proc/sys/kernel/msgmni
To change this (for example to 128), enter the command:
echo 128 > /proc/sys/kernel/msgmni
We recommend that you add this command to a startup script.
In the section "Installation procedure", aAfter step 4, add:
If you are going to use the server verification procedure described in Chapter 4, install the samples programs:
Linux for Intel
rpm -i MQSeriesSamples-5.3.0-1.i386.rpm
Linux for zSeries.
rpm -i MQSeriesSamples-5.3.0-1.s390.rpm
The IBM 32-bit SDK for Linux on Intel, Java 2 Technology Edition.Version 1.4 is included on the Linux for Intel server CD. It is supplied in Red Hat Package Manager ( RPM ) format and is located in the same directory as the WebSphere MQ packages in both server and client installation images.
It can be installed by using the command:
rpm -i IBMJava2-SDK-1.4-0.0.i386.rpm
Chapter 5, "Installing the WebSphere MQ for Linux for Intel and Linux for zSeries client
In the section "Installation procedure" after step 5, add:
If you are going to use the client verification procedure described in Chapter 6, install the samples programs:
Linux for Intel
rpm -i MQSeriesSamples-5.3.0-1.i386.rpm
Linux for zSeries.
rpm -i MQSeriesSamples-5.3.0-1.s390.rpm
Chapter 7. Applying maintenance to the WebSphere MQ for Linux products
In the section "Installing a PTF" replace steps 4, 5, and 7 with:
4. Use the ls command to list the available updates.
For example, if there are level 3 updates for the runtime, SDK, server, and client filesets, this lists:
MQSeriesRuntime-<ptfname>-5.3.0-3.i386.rpm
MQSeriesSDK-<ptfname>-5.3.0-3.i386.rpm
MQSeriesServer-<ptfname>-5.3.0-3.i386.rpm
MQSeriesClient-<ptfname>-5.3.0-3.i386.rpm
5. To find out which filesets are installed on your machine, enter the following:
rpm -q -a | grep MQSeries
For example, if you have the runtime and server filesets at level 2, and the SDK and Man filesets at level 1, this returns:
MQSeriesRuntime-5.3.0-1
MQSeriesRuntime-<ptfname>-5.3.0-2
MQSeriesSDK-5.3.0-1
MQSeriesServer-5.3.0-1
MQSeriesServer-<ptfname>-5.3.0-2
MQSeriesMan-5.3.0-1
7. Repeat step 5 to show that the runtime, SDK, and server filesets are now at level 3 (the Man fileset remains at level 1):
MQSeriesRuntime-5.3.0-1
MQSeriesRuntime-<ptfname>-5.3.0-2
MQSeriesRuntime-<ptfname>-5.3.0-3
MQSeriesSDK-5.3.0-1
MQSeriesSDK-<ptfname>-5.3.0-3
MQSeriesServer-5.3.0-1
MQSeriesServer-<ptfname>-5.3.0-2
MQSeriesServer-<ptfname>-5.3.0-3
MQSeriesMan-5.3.0-1
In the section "Restoring the previous service level" replace steps 2, 3, and 4 with:
2. To find out which filesets are installed on your machine, enter the following:
rpm -q -a | grep MQSeries
Using the example given in "Installing a PTF" on page 41, this returns:
MQSeriesRuntime-5.3.0-1
MQSeriesRuntime-<ptfname>-5.3.0-2
MQSeriesRuntime-<ptfname>-5.3.0-3
MQSeriesSDK-5.3.0-1
MQSeriesSDK-<ptfname>-5.3.0-3
MQSeriesServer-5.3.0-1
MQSeriesServer-<ptfname>-5.3.0-2
MQSeriesServer-<ptfname>-5.3.0-3
MQSeriesMan-5.3.0-1
3. Remove all the updates applied at level 3 with the following commands:
rpm -e MQSeriesRuntime-<ptfname>-5.3.0-3
rpm -e MQSeriesSDK-<ptfname>-5.3.0-3
rpm -e MQSeriesServer-<ptfname>-5.3.0-3
4. Repeat step 2 to check that the filesets have been returned to their original
levels:
MQSeriesRuntime-5.3.0-1
MQSeriesRuntime-<ptfname>-5.3.0-2
MQSeriesSDK-5.3.0-1
MQSeriesServer-5.3.0-1
MQSeriesServer-<ptfname>-5.3.0-2
MQSeriesMan-5.3.0-1
WebSphere MQ V5.3 Intercommunication
Chapter 1, "Concepts of intercommunication"
In the section "Distributed queuing components", subsection "Channel initiators and listeners", add the following subsection:
New channel behavior in WebSphere MQ
By default, in WebSphere MQ 5.3, threaded channels started by the channel initiator or a listener do not run under that process, but under a process called AMQRMPPA, otherwise known as a pool process.
To revert to the MQSeries 5.2 behavior, and have channels run under the originating process, define an environment variable MQNOREMPOOL. The existence of this variable, set to any value, runs the channel threads as part of the listener or channel initiator process. This can be useful when trying to
isolate one or more channels from the rest of the configuration, for example when testing channel exits.
Chapter 6, "Channel attributes"
In the section "Channel attributes in alphabetical order", subsection "KeepAlive Interval (KAINT)", add the following:
You can set the KeepAlive Interval (KAINT) parameter for channels on a per-channel basis. You can access and modify the parameter, but it is only stored and forwarded on non-z/OS platforms; there is no functional implementation of the parameter.
If you need the functionality provided by the KAINT parameter, use the Heartbeat Interval (HBINT) parameter, as described in "Heartbeat interval (HBINT)".
Chapter 46, "Channel-exit programs"
Add a section
Compiling Channels Exits on WebSphere MQ for Linux (Intel and zSeries)
Note:
Before you use an existing user exit for the first time on WebSphere MQ for Linux, you must recompile it to enable it to take advantage of thread-safe system calls. If your user exits use thread-unsafe system calls, you will need to modify them before using them on this platform.
The exit is a dynamically loaded object that must be written in C. To ensure that it can be loaded when required, specify the full path name in the DEFINE CHANNEL command or enter the path name in the ExitPath stanza of the QM.INI file. If the exit is on a Linux client, specify the path name in the
ClientExitPath stanza of the MQS.INI file. The value in the ExitPath stanza of the QM.INI file or the ClientExitPath stanza of the MQS.INI file defaults to /var/mqm/exits. You can change this value or you can override it by specifying a full path name on the DEFINE CHANNEL command.
Define a dummy MQStart() routine in the exit and specify MQStart as the entry point in the module. The following example shows how to set up an entry to your program:
#include <cmqc.h>
#include <cmqxc.h>
void MQStart() {;} /* dummy entry point */
void MQENTRY ChannelExit ( PMQVOID pChannelExitParms,
PMQVOID pChannelDefinition,
PMQLONG pDataLength,
PMQLONG pAgentBufferLength,
PMQVOID pAgentBuffer,
PMQLONG pExitBufferLength,
PMQPTR pExitBufferAddr)
{
... Insert code here
}
The following example shows the compiler and loader commands for channel-exit programs on Linux.
$ gcc -c -fPIC exit.c
$ gcc -shared exit.o -o exit
$ cp exit /usr/xmp/lib # (or wherever you require)
Chapter 47, "Channel-exit calls and data structures"
In the section "MQCD - Channel definition", add to the fields SSLPeerNamePtr and SSLPeerNameLength the following note:
When a certificate is received during a successful SSL handshake, the
Distinguished Name of the subject of the certificate is copied into the
MQCD field accessed by SSLPeerNamePtr at the end of the channel which
receives the certificate. It overwrites the SSLPeerName value for the channel
if this is present in the local user's channel definition.
If a security exit is specified at this end of the channel it will receive the
Distinguished Name from the peer certificate in the MQCD.
WebSphere MQ V5.3 Application Programming Reference
Chapter 20, "MQSCO - SSL configuration options"
In the section "fields", in the CryptoHardware field, the GSK_PKCS11 string should be described as
GSK_PKCS11= <the PKCS #11 driver path and filename>; <the PKCS #11 token label>;<the PKCS #11 token password>;
Add the following description of this string
The PKCS #11 driver path is an absolute path to the shared library providing support for the PKCS #11 card. The PKCS #11 driver filename is the name of the shared library. An example of the value required for the PKCS #11 driver path and filename is /usr/lib/pkcs11/PKCS11_API.so
The PKCS #11 token label must be entirely in lower case. Note that if you have configured your hardware with a mixed case or upper case token label you must reconfigure it with this lower case label.
Appendix H, "Code page Conversion"
Cyrillic:
Add Linux to the platforms that use CCSIDs 878 and 915 as a Native CCSID.
Japanese Latin SBCS:
Add Linux to the platforms that support 943 and 5050 as Native CCSIDs.
Linux does not support conversion from 943 or 5050 to 1027
(as for Solaris).
Japanese Katakana SBCS:
Add Linux to the platforms that support 943 and 5050 as Native CCSIDs.
Linux does not support conversion from 943 or 5050 to 290 or 897
(as for Solaris).
Japanese Kanji/Latin Mixed and Japanese Kanji/Katakana MIXED:
Add Linux to the platforms that support 943 and 5050 as Native CCSIDs.
Korean:
Add Linux to the platforms that support 970 as Native CCSID.
Simplified Chinese:
Add Linux to the platforms that support 1383 as Native CCSID.
WebSphere MQ V5.3 Security
Chapter 12, "Working with the Secure Sockets Layer (SSL) on UNIX systems"
In the section "Setting up a key repository", note that, on Linux you must not create key repositories on a file system that does not support file level locks, such as NFS version 2.
The IKEYCMD command documented for creating a new CMS key database file does not produce the password stash file, which is essential for successful SSL message transfer. To create a key database file and a password stash file use the following IKEYCMD commands:
gsk6cmd -keydb -create -db <filename> -pw <password> -type cms -expire <days>
gsk6cmd -keydb -stashpw -db <filename> -pw <password>
where:
-db <filename> is the fully qualified path name of a CMS key database.
-pw <password> is the password for the CMS database.
-type cms is the type of database.
-expire <days> is the expiration time in days of the database password.
The default is 60 days for a database password.
In the section "Adding personal certificates to a key repository" before step 1: "Execute the gsk6ikm command to start the iKeyman GUI." add a step 0.5: Ensure that the certificate file to be imported has write permission for the current user
In the section "Configuring for cryptographic hardware" add a new last paragraph (just above the section "Managing Certificates on PKCS #11 hardware"):
If you have configured cryptographic hardware which uses the PKCS #11 interface using any of these methods, you must store the personal certificate for use on your channels in the key database file for the cryptographic token you have configured. This is described in "Managing Certificates on PKCS #11 hardware".
In the section "Managing Certificates on PKCS #11 hardware" replace point 8 by
8. Click OK. The Personal Certificates field shows the label of the new
personal certificate you added. You will note that this label is formed by
adding the cryptographic token label before the label you supplied.
WebSphere MQ V5.3 SCRIPT (MQSC) Command Reference
Chapter 2, "The MQSC commands"
SSL CipherSpecs TLS_RSA_WITH_AES_128_CBC_SHA and
TLS_RSA_WITH_AES_256_CBC_SHA are available for the Linux for Intel platform.
In the table "CipherSpecs that can be used with WebSphere MQ SSL support", Note 7 should read "Available for AIX, HP-UX, and Linux Intel platforms only".
In the "ALTER AUTHINFO" section change the description to: Use ALTER AUTHINFO to alter an authentication information object. These objects contain the definitions required to perform Certificate Revocation List (CRL) checking using LDAP servers, except on OS/400 where these are defined by the
Digital Certificate Manager for each Certification Authority. Note that LDAP CRL functionality is not supported on Linux for zSeries channels.
In the section "ALTER QMGR", parameter SSLCRLNL(nlname) description change the list which describes when changes become effective to:
- On Windows and UNIX systems (apart from Linux for zSeries), when a new outbound single channel process first runs an SSL channel.
- On Windows and UNIX systems (apart from Linux for zSeries), when a new inbound TCP/IP single channel process first receives a request to start an SSL channel.
- On Windows and UNIX systems (apart from Linux for zSeries), for channels that run as threads of a process pooling process (amqrmppa), when the process pooling process is started or restarted and first runs an SSL channel. If the process pooling process has already run an SSL channel, and you want the change to become effective immediately, restart the queue manager.
- On Windows and UNIX systems (apart from Linux for zSeries), for channels that run as threads of the channel initiator, when the channel initiator is started or restarted and first runs an SSL channel. If the channel initiator process has already run an SSL channel, and you want the change to become effective immediately, restart the queue manager.
- On Windows and UNIX systems (apart from Linux for zSeries), for channels that run as threads of a TCP/IP listener, when the listener is started or restarted and first receives a request to start an SSL channel.
- On z/OS, when the channel initiator is restarted.
Add, after the list:
- On OS/400 queue managers this parameter is ignored, however it is used to determine what authentication information objects are written to the client channel definition table.
- On Linux for zSeries queue managers this parameter must not be specified when channels are started, however it is used to determine what authentication information objects are written to the client channel definition table. Note that changes to SSLCRLNL, or to the names in a previously specified namelist, or to previously referenced authentication information objects are reflected
immediately in the client channel definition table.
In the "DEFINE AUTHINFO" section add:
Note that LDAP CRL functionality is not supported on Linux for zSeries
channels.
In the section "ALTER QMGR" add the following description of the GSK_PKCS11
value of the SSLCRYP parameter:
The PKCS #11 token label must be entirely in lower case. Note that if you have
configured your hardware with a mixed case or upper case token label you must
reconfigure it with this lower case label.
WebSphere MQ V5.3 Programmable Command Formats and Administration Interface
SSL CipherSpecs TLS_RSA_WITH_AES_128_CBC_SHA and
TLS_RSA_WITH_AES_256_CBC_SHA are available for the Linux for Intel platform.
In the table "CipherSpecs that can be used with WebSphere MQ SSL support", Note 7 should read "Available for AIX, HP-UX, and Linux Intel platforms only".
Chapter 3, "Definitions of Programmable Command Formats"
In the "Change Queue Manager" and "Inquire Queue Manager (Response)" sections add the following description of the GSK_PKCS11 value of the SSLCryptoHardware parameter:
The PKCS #11 token label must be entirely in lower case. Note that if you have configured your hardware with a mixed case or upper case token label you must reconfigure it with this lower case label.
Chapter 4. Definitions of Programmable Command Formats
At the start of the "Change, Copy, and Create Authentication Information Object" section add:
Authentication objects contain the definitions required to perform Certificate Revocation List (CRL) checking using LDAP servers, except on OS/400 where these are defined by the Digital Certificate Manager for each Certification Authority. Note that LDAP CRL functionality is not supported on Linux for
zSeries channels.
In the "Change Queue Manager" section, parameter SSLCRLNL(nlname) description change the list which describes when changes become effective to:
- On Windows and UNIX systems (apart from Linux for zSeries), when a new outbound single channel process first runs an SSL channel.
- On Windows and UNIX systems (apart from Linux for zSeries), when a new inbound TCP/IP single channel process first receives a request to start an SSL channel.
- On Windows and UNIX systems (apart from Linux for zSeries), for channels that run as threads of a process pooling process (amqrmppa), when the process pooling process is started or restarted and first runs an SSL channel. If the process pooling process has already run an SSL channel, and you want the change to become effective immediately, restart the queue manager.
- On Windows and UNIX systems (apart from Linux for zSeries), for channels that run as threads of the channel initiator, when the channel initiator is started or restarted and first runs an SSL channel. If the channel initiator process has already run an SSL channel, and you want the change to become effective immediately, restart the queue manager.
- On Windows and UNIX systems (apart from Linux for zSeries), for channels that run as threads of a TCP/IP listener, when the listener is started or restarted and first receives a request to start an SSL channel.
- On z/OS, when the channel initiator is restarted.
Add, after the list:
- On OS/400 queue managers this parameter is ignored, however it is used to determine what authentication information objects are written to the client channel definition table.
- On Linux for zSeries queue managers this parameter must not be specified when channels are started, however it is used to determine what authentication information objects are written to the client channel definition table. Note that changes to SSLCRLNL, or to the names in a previously specified namelist, or to previously referenced authentication information objects are reflected immediately in the client channel definition table.
WebSphere MQ V5.3 Using Java
Chapter 4, "Using WebSphere MQ classes for Java Message Service"
In the section "Running the sample applet", subsection "Running the applet as an
application", before running the applet using the command:
java JMSTestApplet
compile the applet using the command:
javac JMSTestApplet.java
Chapter 5, "Using the WebSphere MQ JMS administration tool"
In section "Administering JMS objects" add a note to Table 11 "Property names and valid values":
In certain environments, specifying the same queue name for both the brokerDurSubQueue and brokerCCDurSubQueue attributes on an MQTopic object can result in a JMSException being thrown. It is advised that separate queues are used for these two attributes."
Chapter 11, "Programming publish/subscribe applications"
In the section "Solving publish/subscribe problems" add a new section at the end, as follows:
"Other Considerations"
When connecting to WebSphere MQ Event Broker V2.1 on a Microsoft Windows system, with a large number of JMS clients using TCP/IP sockets (that is with a JMSAdmin property type of TRANSPORT(DIRECT)), note the following.
If a large number of connections happen almost simultaneously, a java.net.BindException Address in use exception might be thrown in response to a TopicConnection call. You can try to avoid this by catching the exception and retrying, or by pacing the connections.
WebSphere MQ V5.3 Using C++
Appendix A, "Compiling and linking"
In the section "Linux", the libraries (v2.95.2) should state:
-L/opt/mqm/lib/2.95.2 -Wl,-rpath=/opt/mqm/lib/2.95.2
\ -limqb23gl[_r] -limq{c|s}23gl[_r]
and the libraries (v3.0.3) should state:
-L/opt/mqm/lib/3.0.3 -Wl,-rpath=/opt/mqm/lib/3.0.3
-limqb23gl[_r] -limq{c|s}23gl[_r]
WebSphere MQ Application Programming Guide
Appendix A. Language compilers and assemblers
replace the existing Table 61. Language compilers and assemblers for WebSphere MQ for Linux for Intel and Linux for zSeries by Table 61a. Language compilers and assemblers for WebSphere MQ for Linux for Intel
| Language | Compiler/ Assembler |
| C++ | GNU g++ V2.95.2 or V3 |
| C | GNU gcc V3 |
and
Table 61b. Language compilers and assemblers for WebSphere MQ for Linux for zSeries
| Language | Compiler/ Assembler |
| C++ | GNU g++ V2.95.3 |
| C | GNU gcc V2.95.3 |
Trademarks
The following terms are trademarks of the IBM Corporation in the
United States, or other countries, or both:
IBM AIX MQSeries SupportPac WebSphere
ActiveX, Microsoft, Visual Basic, Visual C++, Windows, and Windows NT are
trademarks or registered trademarks of Microsoft Corporation in the United
States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries,
or both.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Other company, product, and service names may be trademarks or service marks
of others.
Last updated: 7 October 2005
|