5 projects tagged "Apache 2.0"
Updated 12 Apr 2011
MQRC2
| Pop | 26.91 |
|---|---|
| Vit | 1.02 |
MQRC2 is an application that can interpret an MQ reason code number (i.e. 2035), an MQ reason code symbol (i.e. MQRC_OBJECT_IN_USE), or an AMQ message number (i.e. AMQ4005) and display the relevant information from the WebSphere MQ Messages manual.
Updated 28 Dec 2010
xdf
| Pop | 89.83 |
|---|---|
| Vit | 2.02 |
The Exquisite `df' (xdf) is a souped-up version of df(1) rewritten from scratch and focused on flexibility of field selection and output format. It offers HTML and CSV outputs, besides the traditional text-based console output. It is fit for system administrators who are tired of post-processing df(1) output through shell or Perl scripts in order to avoid broken lines or to get a simple total/summary line.
Updated 27 Nov 2009
MQWhat
| Pop | 17.80 |
|---|---|
| Vit | 1.02 |
MQWhat is a tool for documenting which MQ components are installed and active on a particular server. Since MQ component information is contained in various files and/or output by MQ programs, MQWhat is designed to collect and summarize the MQ information and present the information to the user's screen in a concise manner.
Updated 12 Apr 2011
Message Router
| Pop | 40.66 |
|---|---|
| Vit | 1.36 |
The Message Router (MRTR) application will move a message from a central WebSphere MQ queue to a specific application WebSphere MQ queue. The destination queue that the message will be placed into will be based on a keyword in the message. Context information is maintained. MRTR will look in the message for a Start Keyword and an End Keyword. The value between these two keywords is the Keyword Value (inifile Token). MRTR will search its ini file for that particular Keyword Value. The field value associated with the looked-up keyword value is the destination queue name. MRTR performs each MQGET and the subsequent MQPUT under a Unit of Work (UOW) so that message integrity is kept.
Updated 12 Apr 2011
Message Multiplexer
| Pop | 42.28 |
|---|---|
| Vit | 1.36 |
The Message Multiplexer (MMX) application will get a message from a WebSphere MQ queue and output it to one or more queues. Context information is maintained across the message put(s). MMX can move messages from a single source queue to (up to) 99 target queues. Messages put to each target queue are an exact replicate of the original message from the source queue (including the message's MQMD). MMX performs each MQGET and the subsequent "n" MQPUT(s) under a Unit of Work (UOW), so that message integrity is kept.
