Search results for query: *

Oh boy ! You never, never, NEVER !, can connect two QMGR's with the same name !!!!

Please show me the definitions of qmgr1: - remote queue 'display qr(...) all' - xmit queue 'display ql(...) all' - channel 'display chl(...) all' and of qmgr2: - qmgr 'display qmgr(...) all' - destination q 'display ql(...) all' You do this by the command interface 'runmqsc...

Hi Ibreton, to find the reason code is a little bit difficult: the message text begins with 00000000: 444C 4820 0000 0001 0000 0827 4C54 522E 'DLH .......'LTR.' This is the beginnig of the Dead Letter Header=DLH (described in the WMQ Application Programming Reference). The third word is the...

Hi Paul, you're right, this is the upper limit - 2 GB virtual storage. The MSTR adress space tells the CHIN the maxmsglen when a queue is opened, and the CHIN increases the connection buffer, if it's too low for a new open (we still talk about one connection - one buffer) . Regards, Norbert

Paul, I was not speaking of disk storage but of main storage. The CHIN reserves a buffer in the range of the biggest messagelength used by the connection. Therefore it results the same, if all users open the same queue or maybe everyone has ist own dynamic queue. Regards, Norbert

Hi sundrop, I just can speak of z/OS, where we recently had problems, as a queue, used by about 900 workstations per client channel, had been set to 4MB. The CHIN-adress-space was filled up until its margin of 2 GB virtual storage, then it rejected all further connections. HTH

Hi Jamey, you have to format the message data itself in a form described in the MQS Application Programming Guide: http://www-3.ibm.com/software/ts/mqseries/library/manuals/csqzal/CSQZAL3M.HTM Since this is not trivial, we use a conversion program always running on the mainframe (get wait...

You can modifiy and utilize the IBM DLQ handler, as described in the MQSeries System Administration: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/AMQZAG01/12.1.1?SHELF=AMQZA906&DT=19981214172539

The QMGR also has a Option MAXMSGL; have a look at AS/400 "display qmgr maxmsgl".

First stop the channel from mainframe to NT. Put a message to see if it waits in the Xmit-Queue. If so, start the channel to see if the XmitQ gets empty and the Dead Letter Queue on the mainframe remains empty. This will be the insurance, that the sending qmgr works right.

You can make a "display qmgr cmdlevel", which works on every platform

Hi Alex, in the softpac, Paul Clarke has described how to configure his tool (mqmon.pdf)

Hi John, to remotely administer QMGR's you do not need a QMGR on your NT workstation, just the MQS Client http://www-4.ibm.com/software/ts/mqseries/txppacs/mac5.html or http://www-4.ibm.com/software/ts/mqseries/txppacs/mack.html as a prerequisite. Next you define manually a reply-to-queue...

Hi. As I understand, the MQSeries Application Programming Guide( ftp://ftp.software.ibm.com/software/ts/mqseries/library/books/csqzak05.pdf ) Chapter 13, page 216, describes MQPMO_NEW_MSG_ID is just a litte help for the programmer to not coding prior to the MQPUT: move MQMI_NONE to MQMD-MSGID...