Filter
Top Products
Optional software
v IBM Directory and Security Server for OS/2 Warp, Version 4 or later
compatible versions. This must be the U.S. Domestic version supporting
DES encryption if the user wishes to run the MQSeries-supplied DCE send,
receive, or message exits.
v If used as a DCE server this software is known to run adequately in the
following environment:
– On a Pentium
®
processor running 90 MHz or faster
– On a machine with 64 MB or more of memory
– Using OS/2 Warp Server, Version 4.0 or later
v MQSeries DCE names and security modules are provided as part of the
MQSeries for OS/2 Warp product.
Compilers for MQSeries Applications on OS/2 Warp Clients
The following compilers are supported:
v IBM VisualAge
®
COBOL for OS/2 Warp, Version 1.1 and Version 2.2
v Micro Focus COBOL compiler, Version 4.0 (32 bit)
v IBM VisualAge C++ for OS/2 Warp, Version 3.0
v Borland C++ compiler, Version 2.0 and Version 5.02 (C bindings only)
v IBM C and C++ compilers, Version 3.6
v IBM PL/I for OS/2 Warp, Version 1.2
v IBM VisualAge for PL/I for OS/2 Warp
v IBM VisualAge Java Enterprise Edition for OS/2 Warp, Version 2.0
v IBM VisualAge Java Professional Edition for OS/2 Warp, Version 2.0
Components for OS/2 Warp
MQSeries Client
The MQSeries client code for your platform.
MQSeries Development Toolkit
This includes:
v Sample programs
v Header files that you can use when writing applications to run on
the client
MQSeries Client for Java
This allows Java applets running on your client machine to
communicate with MQSeries. It includes security exits for encryption
and authentication of messages sent across the Web by the MQSeries
Client for Java. These exits consist of some Java classes. To use the
client for Java you need Java 1.1.1 (or later compatible version)
runtime code on your machine. On Windows NT, you require
Microsoft Windows NT Version 4. On OS/2 Warp the MQSeries client
Hardware and Software, OS/2 Warp
Chapter 6. Planning to Install MQSeries Clients 51