Skip to main content

IBM Websphere MQ Tools - Middleware News

MQ tools

Tool / file name Purpose
amqsaicq.c Create a local queue using the MQ Administration Interface (MQAI)
amqsaiem.c Event monitor using the MQ Admin Interface (MQAI)
amqsailq.c Inquire the current depth of all local queues using MQAI
amqsaxe0.c ApiExit which traces MQAPI calls
amqsbcg0.c Browse messages, text and header (use amqsgbr for text only)
amqsblst.c Bandwidth and connectivity tester
amqscnxc.c Client connection information on MQCONNX
amqsecha.c Echo messages to reply to queue (triggered program) (sent by amqsreq, maybe)
amqsgbr0.c Browse messages, text only (use amqsbcg for text and header)
amqsget0.c Get a message
amqsgrma.c Get reference messages from a queue. Checks that the objects, identified in the messages, exist
amqsinqa.c MQINQ sample (triggered program)
amqsldpc.c Look up the MQ host name, channel name and queue name in an LDAP directory + MQPUT
amqsmon0.c Get an statistics or accounting message
amqsprma.c Create a reference message
amqsptl0.c Put messages to a list of queues
amqsput0.c Put a message
amqsqrma.c Channel message exit program to process reference messages
amqsreq0.c Put request messages to a queue, and show the reply message (sent by amqsecha, maybe)
amqsseta.c MQSET sample (triggered program)
amqsspin.c SSPI Channel Exit routines (Security)
amqsstop.c Inquire on all the connections for a selected process and request them to be stopped
amqstrg0.c Trigger monitor - read an initiation queue, and start the program associated with trigger message
amqstxgx.c Get transaction for Tuxedo
amqstxpx.c Put transaction for Tuxedo
amqstxsx.c Server for Tuxedo
amqsvfc0.c Skeleton of a Data Conversion exit
amqswlm0.c CLWL exit that chooses a destination QMgr
amqsxae0.c Sample Encina program
amqsxrma.c Channel message exit to process reference messages
amquregn.c Dump MQ values from Registry (NT)
amqzscgn.c CICS GLobal User Exit (GLUE) program for the CICS Task termination user exit (UE014015)
amqzscin.c XA switch program for CICS XA Initialisation
Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
143 comments
Read more