Application programming
Using the message queue interface (MQI)
Limiting the size of a message
Choosing client or server coded character set identifier (CCSID)
CCSID and encoding fields - multiple puts
Designing applications
Using MQINQ
Using syncpoint coordination
Using MQCONNX
Shared connection handles on MQCONNX
Building applications for WebSphere MQ clients
Running applications in the WebSphere MQ client environment
Triggering in the client environment
Process definition
Trigger monitor
CICS applications (non-z/OS)
Linking C applications with the WebSphere MQ client code
Linking C++ applications with the WebSphere MQ client code
Linking COBOL applications with the WebSphere MQ client code
Linking Visual Basic applications with the WebSphere MQ client code
Running applications on WebSphere MQ clients
Using environment variables
Using the MQCNO structure
Using DEFINE CHANNEL
Role of the client channel definition table
Multiple queue managers
Queue-sharing groups
Examples of MQCONN calls
What the examples demonstrate
Example 1. Queue manager name includes an asterisk (*)
Example 2. Queue manager name specified
Example 3. Queue manager name is blank or an asterisk (*)
Preparing and running extended transactional client applications
Preparing and running CICS and Tuxedo applications
Sample programs
Error log messages
Preparing and running Microsoft Transaction Server applications
Preparing and running WebSphere MQ JMS applications
Solving problems
WebSphere MQ client fails to make a connection
Stopping WebSphere MQ clients
Error messages with WebSphere MQ clients
Using trace on Windows
File names for trace files
How to examine First Failure Support Technology (FFST) files
Using trace on UNIX systems
File names for trace files
How to examine First Failure Support Technology (FFST) files
Using trace on AIX
(R)
Notices
|
Downloads
|
Library
|
Support
|
Feedback
p03