Middleware News

How does the MQ parameter of expiry work ? - Middleware News Symptom Your messages are expiring from the MQ queue before your MQ applications have accessed them. Fix Following is a section from the IBM WMQ API reference on message expiry. To summarize, messages that expire continue to contribute to a queue's depth (message count) until they are browsed, an attempt is made to transport them to another queue is made, or an MQGET command is executed against them. When some action is taken against the expired message sitting on the queue, it is discarded at that point. The only version of WMQ 5.3 that has the option of automatically removing expired messages from a queue (without having to browse, get, etc.) is the z/OS version. Expiry (MQLONG) Message lifetime. This is a period of time expressed in tenths of a second, set by the application that puts the message. The message becomes eligible to be discarded if it has not been removed from the destination

Resolving problems with MQSC commands - Middleware News If you cannot get MQSC commands to run, use the following information to see if any of these common problems apply to you. It is not always obvious what the problem is when you read the error generated. When you use the runmqsc command, remember the following: Use the < operator to redirect input from a file. If you omit this operator, the queue manager interprets the file name as a queue manager name, and issues the following error message: AMQ8118: WebSphere MQ queue manager does not exist. If you redirect output to a file, use the > redirection operator. By default, the file is put in the current working directory at the time runmqsc is invoked. Specify a fully-qualified file name to send your output to a specific file and directory. Check that you have created the queue manager that is going to run the commands. To do this on Windows systems, use the WebSphere MQ Explorer to display a list of queue manager

Running MQSC commands from text files - Middleware News Running MQSC commands interactively is suitable for quick tests, but if you have very long commands, or are using a particular sequence of commands repeatedly, consider redirecting stdin from a text file. (See Standard input and output for information about stdin and stdout.) To do this, first create a text file containing the MQSC commands using your usual text editor. When you use the runmqsc command, use the redirection operators. For example, the following command runs a sequence of commands contained in the text file myprog.in: runmqsc < myprog.in Similarly, you can also redirect the output to a file. A file containing the MQSC commands for input is called an MQSC command file. The output file containing replies from the queue manager is called the output file. To redirect both stdin and stdout on the runmqsc command, use this form of the command: runmqsc < myprog.in > myprog.out This command invokes th

Running MQSC commands from batch files - Middleware News If you have very long commands, or are using a particular sequence of commands repeatedly, consider redirecting stdin from a batch file. To do this, first create a batch file containing the MQSC commands using your usual text editor. When you use the runmqsc command, use the redirection operators. The following example: Creates a test queue manager, TESTQM Creates a matching CLNTCONN and listener set to use TCP/IP port 1600 Creates a test queue, TESTQ Puts a message on the queue, using the amqsputc sample program Example script for running MQSC commands from a batch file export MYTEMPQM=TESTQM export MYPORT=1600 export MQCHLLIB=/var/mqm/qmgrs/$MQTEMPQM/@ipcc crtmqm $MYTEMPQM strmqm $MYTEMPQM runmqlsr -m $MYTEMPQM -t TCP -p $MYPORT & runmqsc $MYTEMPQM << EOF DEFINE CHANNEL(NTLM) CHLTYPE(SVRCONN) TRPTYPE(TCP) SCYEXIT('amqrspin(SCY_NTLM)') DEFINE CHANNEL(NTLM) CHLTYPE(CLNTCONN) QMNAME('$M