Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

WebSphere MQ - Channel Watch Logger and Activated Channel Watch

IP.com Disclosure Number: IPCOM000033257D
Original Publication Date: 2004-Dec-02
Included in the Prior Art Database: 2004-Dec-02
Document File: 2 page(s) / 36K

Publishing Venue

IBM

Abstract

This program generates a list of all unique Channel/hostname combinations which have been activated since program execution, over an extended period of time. This information is critical to catalogue MQ environment clients for many uses and was previously unavailable.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

WebSphere MQ - Channel Watch Logger and Activated Channel Watch

A program is disclosed that generates a list of all unique Channel/hostname combinations which have been activated since program execution, over an extended period of time. This new information was previously unavailable to an MQ administrator.

Flow of Current Method used by MQ Administrator :
1. Admin executes list active channel command --> 2. List of all currently active channels output (including multiple instances of channels) --> 3. Admin can review this information on the screen or save to a file
Flow of MQ Channel Watch Program 's Routine:
1. Active channel list requested --> 2. List of active channels returned --> 3. Hostname of channels retrieved --> 4. Program logic returns unique Channel/hostname combinations --> 5. Unique Channel/hostname combinations found compared to previously stored unique Channel and hostname combinations --> 6. Program generates list of all unique Channel/hostname combinations which have been activated since program execution.

Number 6 summarizes the novel contribution of the invention, generation of previously unavailable information. This information is critical to catalogue MQ environment clients for many uses, including: newly acquired outsourcing contracts with undocumented client lists, troubleshooting scenarios, channel removals that may affect multiple/unknown applications, or upgrade planning to generate lists of active MQ client servers that connect to Queue Managers. Items 3-6 are all new operations.

The program may be adapted from the first to provide an MQ support person the ability to monitor all channels that may have started at any point since the script was executed in a QMGR connection verification scenario. The polling time cycles and re-execution time cycle are user modifiable via time variables and the CRON entry used. After each run cycle, the program records its findings intermediary files and a final output file. The program can be run for extended periods of time (days, even months) in order to capture MQ applications that may only execute at certain time intervals i.e. weekly, monthly. The program output continues to grow as new unique client/channel activations are discovered, but does not include redundant data. Here is a stripped down example of the final output of the program after several days of operation: QMGR.CCLIENT 9.17.221.196 db116.boulder.ibm.com QMGR.CCLIENT 9.17.221.200 db115.boulder.ibm.com QMGR.CCLIENT 9.17.221.204 db114.boulder.ibm.com EDGE.ATP.CLIENT 9.17.220.76 app101.boulder.ibm.com EDGE.EDESIGN.CLIENT 9.17.220.76 app101.boulder.ibm.com EDGE.INTER.CLIENT 9.17.220.76 app101.boulder.i...