MQSeries.net :: View topic - New and updated MQSeries Family SupportPacs 18/10/2001

kolban · Posted: Thu Oct 18, 2001 9:10 am Post subject:

The following MQSeries SupportPacs have been released:
MA0P: MQSeries FTP client

This SupportPac provides a basic FTP client for MQSeries. The supplied mqftp command uses the File Transfer Protocol (FTP) to transfer files between the local queuemanager and a remote host. It can be used in an environment where you need to transfer data between the local queuemanager and a remote host when the remote host only has the FTP protocol available. The SupportPac provides the following functions:

- Log in to a remote system
- Display local help information
- Display remote help information
- Change local queue
- Change local queuemanager
- Change the persistence state of the message
- Get a remote file and put the data on a local queue
- Get a message from a local queue and put it into a remote file
- Display the current queue depth

Versions are supplied for AIX, HP-UX, Linux, Sun Solaris and Windows. A version for use in the OS/400 environment is planned for a future release.

MS0F: Resolve MQSeries objects across multiple platforms (mqsnoop)

In multi-queue manager environments it can be time consuming resolving MQSeries objects across queue managers and determining the location of problems. This Category 4 SupportPac provides a command line program called mqsnoop which helps reduce the effort by taking a queue name and dynamically resolving it to its ultimate destination or destinations. The state of all intermediate objects is also displayed. The program provides three functions:

- When supplied with a queue name, mqsnoop will interrogate all queue objects on all queue managers between the original queue and the ultimate destination queue object. It will display relevant information about the destination object and all intervening objects (queues, xmitsqs, channels and qmgrs) - for example, qdepth for xmitqs, channel status and trigger information for triggered queues. Clustered objects and xmitqs serviced by multiple channels are also handled.

- When supplied with a cluster name, mqsnoop will interrogate the cluster and display all consituent queue managers along with relevant state information about each of the cluster managers.

- mqsnoop can perform a cluster communication test. It will confirm that all queue managers in a cluster can communicate with all other queue managers in the cluster.

The queue resolution feature can be used for tracing message pathways to discover potential problems. For example, a qremote APPQ1 on queue manager QM1 resolves to qalias APPQ2 on queue manager QM2 which reolves to a triggered queue APPQ3. Running mqsnoop against APPQ1 will display information about:

- APPQ1
- The transmit queue QM2 specified in the APPQ1 definition
- The sender channel which serves the transmit queue
- The queue alias APPQ2 on queue manager QM2
- The local queue APPQ3 and associated trigger status (initiation queue and process)

The displayed information can be used to check:

- Whether the channel is active
- The trigger queue depth
- Whether the initiation queue has an input count greater than zero
- Etc.

Used with the basic output option, mqsnoop displays information about the final object (the local queue) only. The cluster communication feature provides a simple check of cluster queue manager inter-connectivity. This could be used as the first step when investigating problems involving clusters.

MS0G: MQSeries cluster utilities

This SupportPac supplies a number of utilities for reporting, diagnosing and repairing MQSeries clusters. The utilities can be used to:

- Capture the state of a cluster and report it.
- To clean up unwanted references to objects within a cluster
- To handle unwanted messages on the SYSTEM.CLUSTER.TRANSMIT.QUEUE

The following MQSeries SupportPacs have been updated:

MA74: MQSeries for Windows 32-bit platforms - Queue manager/Client presence autodetect

Normally when an application is moved from a machine with a local queue manager to a machine running as a client or vice versa, the application must be relinked with the appropriate DLL. This SupportPac provides a DLL which removes this requirement. It allows an MQSeries application to be run unchanged when moved from an environment that has a local queue manager to a client environment. Similarly when moved in the reverse direction, no relinking of the users application is necessary. It has been updated to include the MQCONNX API.

WA82: MQSeries Workflow - Web credit example

The Web credit example illustrates the use of the MQSeries Workflow Web Client. It shows how to start a workflow process from a web application, access backend data (DB2 Database) from Java Server Pages invoked as part of a business process from the Web Client and how to store data back to the DB2 database through a User-defined Program Execution Server. The User-defined Program Execution Server is provided as a Java program and as an MQSeries Integrator Message Flow. Complete source code is provided. The following changes have been made in this release:

- Raised prerequisite level to MQSeries Workflow V3.3 ServicePack 1.
- Added installation instructions for WebSphere V4.
- MQSeries Workflow V3.3 Service Pack 2 or higher is required for WebSphere V4 support.
- Fixed bug in DisplayCreditHistory.jsp. Used hardcoded name of root URL instead of WebClient convenience function - JSP did not work on root URLs other then '/MQWFClient'.
- Fixed queue manager configuration scripts - the old scripts did not add triggering for the channels.
- Fixed database creation script - the old script had errors on newer DB2 V6 Service Packs. Consolidated DB2 V6 and V7 scripts into one script.
- Split the FDL into one generic FDL and one FDL for the UPES definition.
- Fixed bugs in FDL that User IDs did not have correct authorizations.

IBM MQSeries SupportPacs may be accessed at:

http://www.ibm.com/software/mqseries/txppacs