Middleware News

IBM Websphere MQ Channel Long-Term History attributes - Middleware News Use the Channel Long-Term History attributes to detect channel performance problems. This attribute group provides channel performance information for each monitored channel within a queue manager. These attributes are informational only; they cannot be used to create situations. Batches Complete The number of logical units of work (LUWs) that this channel has processed after it is initialized. This attribute is not available for CICS® channels. Valid format is an integer. Buffers Received The total number of buffers that are received during the current interval or aggregation period. Valid format is an integer. Buffers Sent The total number of buffers that are sent during the current interval or aggregation period. Valid format is an integer. Bytes Received The total number of bytes that are received during the current interval or aggregation period. Valid format is an integer. Bytes Sent The total nu

Websphere MQ Message Summary attributes - Middleware News Use the Message Summary attributes to detect problems with messages. This group provides the backout count (which if high can indicate a problem), the correlation and message IDs, the message expiration time, the message length, message type (which can be request, reply, report, or datagram), persistence (which indicates whether the message is recoverable), priority (which can be used for selective retrieval), date and time the message was created, and the reply-to queue and queue manager names. These attributes are informational only; they cannot be used to create situations. If multiple headers are generated, subsequent headers are prefixed with the IBM® WebSphere® MQ ID of the associated header. For example, subsequent dead letter queue headers are prefixed with DLH and subsequent transmit queue headers are prefixed with XQH. For more information, see the IBM WebSphere MQ Application Programming Reference manual. Accou

ISO 20022 made simple - Middleware News

Watch - Business Intelligence @ SWIFT - Middleware News

SWIFT for banks - Middleware News

The maths behind international banking codes (IBAN's) - Middleware News

MQGET for SYSTEM.ADMIN.COMMAND.QUEUE failed with reason code 2071 - Middleware News Command server fails to start or fails shortly after it receives a message in the SYSTEM.ADMIN.COMMAND.QUEUE. No FDC files are generated. the error received is AMQ8506: Command server MQGET failed with reason code 2071. EXPLANATION: An MQGET request by the command server, for the WebSphere MQ queue SYSTEM.ADMIN.COMMAND.QUEUE, failed with reason code 2071. Symptom 2071 0x00000817 MQRC_STORAGE_NOT_AVAILABLE Cause Well designed MQ server applications typically assume a relatively small initial buffer size, and then heuristically tune the required buffer size based upon the sizes of the messages consumed. For example both the repository manager and the pubsub broker adopt such a scheme. The MQ command server however allocates a fixed size buffer based upon the MAXMSGL defined for the SYSTEM.ADMIN.COMMAND.QUEUE and then issues it's MQGET's using this buffer size. Because the comma

Channels intermittently go into a status of INITIALIZING - Middleware News You see that intermittently your channels go into a status of INITIALIZING. To resolve the problem, you have to end the queue manager and IPL the system. Symptom You receive RC2071: 2071 0x00000817 MQRC_STORAGE_NOT_AVAILABLE FDC has the following information: Probe Id :- ZX010020 Application Name :- MQM Component :- zxcCreateParmFile Program Name :- AMQZXMA0 QMQM Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Minor Errorcode :- OK Probe Type :- MSGAMQ6119 Probe Severity :- 2 Probe Description :- AMQ6119: An internal MQSeries error has occurred(The value specified for the argument is not correct.: fopen: /QIBM/UserData/mqm/qmgrs/QM_DBQFMSP1/startprm/ip5684:) Comment1:- The value specified for the argument is not correct.: fopen: /Q Cause The existence of ip## files in the startprm directory. It appears the ip## file was orphaned by either a shutdown that did not end cleanly, or by a

AMQ5615 on queue manager start up after running security programs - Middleware News You run an application that altered file permissions. You reboot the server, and now the WebSphere MQ queue manager will not start. You receive the following error message: AMQ5615 - Default objects cannot be created. rc 2071 2071 0x00000817 MQRC_STORAGE_NOT_AVAILABLE The return code indicates a shortage of storage, however the system has plenty of space and you are able to create new qmgrs and objects. Cause Altered file permissions on the queue manager directories. Resolving the problem Restore file permissions for the queue manager to the original settings to provide the mqm group and users the access required. The security tab for the directory/file properties should show the mqm group with full control. The mqm group needs full access to the data, log and code directories.

WebSphere MQ Dumps and FFSTs are written to the following locations - Middleware News Directions for finding WebSphere MQ Dump and FFST records. Resolving the problem Dumps and FFST records contain important information that can be used in problem solving. If you have a WebSphere MQ problem, you may receive Dumps and FFSTs, that record details related to the failure. Select one of the following platforms to find the location of the MQ Dumps and FFSTs: HP NSS i5/OS OpenVMS UNIX and Linux VSE Windows z/OS HP NSS FFSTs are located in the following directory: /var/mqm/errors These errors are normally severe, unrecoverable errors, and indicate either a configuration problem with the system or a WebSphere MQ internal error. The files are named AMQccppppp.nn.FDC, where cc is the number of the CPU in which the process that reported the error was running, ppppp is the process identification number (PIN) of the process that reported the error, and nn is a sequence nu

WebSphere MQ error logs - Middleware News Directions to find WebSphere MQ and MQSeries error logs. Note: The MQ error logs are by default located in the following directories, however it may have been changed at install time: Resolving the problem The messages that are recorded in the error logs and job logs are the most important information that you can provide when reporting an MQ problem. Select one of the following platforms to find the location of the MQ error logs: HP NSS i5/OS OpenVMS UNIX and Linux VSE Windows z/OS HP NSS The WebSphere MQ for HP NSS error logs are located in the following directories: /var/mqm/errors /var/mqm/qmgrs/ /errors The error log files are named; AMQERR01.LOG, AMQERR02.LOG and AMQERR03.LOG. Notes: If the queue manager name is not known then the error message is written to an error log file in the errors subdirectory. For example, if the default prefix is /usr/ibm/wmq/GA/var/mqm, the error message is written to an error l

You see in the AIX error log, errors with a label format of AMQFFSTx, such as AMQFFST1, AMQFFST3, AMQFFST4. Symptom An example is shown below: LABEL: AMQFFST3 IDENTIFIER: 8xxxxxxx Date/Time: Sun Dec 31 11:31:18 EST Sequence Number: 3770 Machine Id: 00FFFFFF Node Id: pppppdc Class: S Type: UNKN Resource Name: MQSeries NONE Description SOFTWARE PROGRAM ABNORMALLY TERMINATED Probable Causes UNDETERMINED Failure Causes SOFTWARE PROGRAM Recommended Actions REVIEW DETAILED DATA CONTACT APPROPRIATE SERVICE REPRESENTATIVE Detail Data DETECTING MODULE xcsCloseEventSem SOFTWARE ERROR CODE 0000 0001 FILE NAME /var/mqm/errors/AMQ30656.0.FDC Cause Sometimes, WebSphere MQ errors will cause the AIX operating system to put entries into the AIX error log that have the label of AMQFFSTx, such as AMQFFST1, AMQFFST3, AMQFFST4. Resolving the problem For more details on the MQ problem, review the file mentioned at the end of the error entry in the AIX errpt, such as: FILE

WEBSPHERE MQ V6 QUEUE MANAGER ON OPENVMS DOES NOT START LISTENER OR OTHER SERVICES AT STARTUP DUE TO KN246001 FDC IN AMQZXMA0.EXE - Middleware News Error Description: WebSphere MQ v6 queue managers use a program called the process manager (AMQZMGR0.EXE) to start and monitor services such as listeners and the command server. In certain environments this process manager can fail to start queue manager services due to an unexpected condition. The queue manager may generate FDCs showing symptoms like the following: . Probe Id :- KN246001 Component :- kpiAncillaryProcessStartup Program Name :- AMQZXMA0.EXE Major Errorcode :- zrcX_INVALID_OBJECT_TYPE VMS Errorcode :- -RMS-E-FNF, file not found (00018292) . Probe Id :- KN246002 Component :- kpiAncillaryProcessStartup Program Name :- AMQZXMA0.EXE Major Errorcode :- ocmRC_UNEXPECTED_CSV_STATE VMS Errorcode :- -RMS-E-FNF, file not found (00018292) . Probe Id

Limiting RUNMQSC authority for certain users - Middleware News You want to provide limited access to RUNMQSC for non-mqm users. You want to make sure that they can only DISPLAY information about a queue manager and the queue manager's objects. Cause WebSphere MQ is configured so that only "mqm" users can use runmqsc. The runmqsc program is shipped with the following permission settings: -r-sr-s--- 1 mqm mqm Resolving the problem Create a non mqm user setmqaut -m -t qmgr -p +dsp +connect Create a copy of runmqsc with execute permission set to all. When the permissions are changed to -r-sr-sr-x this means any user can run runmqsc but when it runs, it runs as user mqm, group mqm due to the Set-user-ID-on-execution and Set-group-ID-on-execution permissions. cd /var/mqm/qmgrs/ /@ipcc chmod +r AMQCLCHL.TAB chmod +r AMQRFCDA.DAT

SWIFT MT 100 and 102 and 200 and 205 and 201 and 202 and 299 and 203 and 202 and 204? - Middleware News The MT100 is an Interbank Message Which Basically the Sending Bank Advises the Receiving Bank to Expect Fun...

Queue status - Middleware News For queue status, the following information is always returned for each queue that satisfies the selection criteria, except where indicated: Queue name Type of information returned (TYPE parameter) On platforms other than z/OS®, current queue depth (CURDEPTH parameter) On z/OS only, the queue-sharing group disposition (QSGDISP parameter) The following parameters can be specified for TYPE(QUEUE) to request additional information for each queue. If a parameter is specified that is not relevant for the queue, operating environment, or type of status information requested, that parameter is ignored. CURDEPTH The current depth of the queue, that is, the number of messages on the queue. This includes both committed messages and uncommitted messages. IPPROCS The number of handles that are currently open for input for the queue (either input-shared or input-exclusive). This does not include handles that are open for browse. For shared queues, the

Removing a cluster queue from a queue manager - Middleware News Note: For changes to a cluster to be propagated throughout the cluster, at least one full repository must always be available. Ensure that your repositories are available before starting this task. Scenario: The INVENTORY cluster has been set up as described in Task 3: Adding a new queue manager that hosts a queue. It contains four queue managers. LONDON and NEWYORK both hold full repositories. PARIS and TORONTO hold partial repositories. The inventory application runs on the systems in New York and Toronto and is driven by the arrival of messages on the INVENTQ queue. Because of reduced workload, you no longer want to run the inventory application in Toronto. You want to disable the INVENTQ queue hosted by the queue manager TORONTO, and have TORONTO feed messages to the INVENTQ queue in NEWYORK. Network connectivity exists between all four systems. The network protocol is TCP. Procedure Follow these steps t

Messages do not appear when expected - Middleware News If messages do not appear on the queue when you are expecting them, check for the following: Has the message been put onto the queue successfully? Did WebSphere® MQ issue a return and reason code for the MQPUT, for example: Has the queue been defined correctly, for example is MAXMSGL large enough? (reason code 2030). Can applications put messages on to the queue (is the queue enabled for MQPUT calls)? (reason code 2051). Is the queue already full? This could mean that an application could not put the required message on to the queue (reason code 2053). Is the queue a shared queue? Have Coupling Facility structures been defined successfully in the CFRM policy data set? Messages held on shared queues are stored inside a Coupling Facility. Have you activated the CFRM policy? Is the queue a cluster queue? If it is, there might be multiple instances of the queue on different queue managers. This means the messages coul

Problems with missing messages when using distributed queuing - Middleware News If your application uses distributed queuing, consider the following points: Has distributed queuing been correctly installed on both the sending and receiving systems? Ensure that the instructions about installing the distributed queue management facility in the WebSphere MQ for z/OS® System Setup Guide have been followed correctly. Are the links available between the two systems? Check that both systems are available, and connected to WebSphere® MQ for z/OS. Check that the LU 6.2 or TCP/IP connection between the two systems is active or check the connection definitions on any other systems that you are communicating with. Start of changeSee Monitoring WebSphere MQ for more information about trace-route messaging in a network.End of change Is the channel running? Issue the following command for the transmission queue: DISPLAY QUEUE (qname) IPPROCS If the value for IPPROCS is 0, this means

Moving a non-shared queue - Middleware News To move queues and their messages from one page set to another, use the MQSC MOVE QLOCAL command (described in WebSphere® MQ Script (MQSC) Command Reference). When you have identified the queue or queues that you want to move to a new page set, follow this procedure for each of these queues: Ensure that the queue you want to move is not in use by any applications (that is, IPPROCS and OPPROCS values from the DISPLAY QSTATUS command are zero) and that it has no uncommitted messages (the UNCOM value from the DISPLAY QSTATUS command is NO). Note: The only way to ensure that this state continues is to change your security settings temporarily. If you cannot do this, later stages in this procedure might fail if applications start to use the queue despite precautionary steps such as setting PUT(DISABLED). However, messages can never be lost by this procedure. Prevent applications from putting messages on the queue being moved by altering th

Are some of your queues failing? - middleware News If you suspect that the problem occurs with only a subset of queues, check the local queues that you think are having problems: Display the information about each queue. You can use the MQSC command DISPLAY QUEUE to display the information. Use the data displayed to do the following checks: If CURDEPTH is at MAXDEPTH, the queue is not being processed. Check that all applications are running normally. If CURDEPTH is not at MAXDEPTH, check the following queue attributes to ensure that they are correct: If triggering is being used: Is the trigger monitor running? Is the trigger depth too great? That is, does it generate a trigger event often enough? Is the process name correct? Is the process available and operational? Can the queue be shared? If not, another application could already have it open for input. Is the queue enabled appropriately for GET and PUT? If there are no application processes getting messages from the

Determining whether your application has the queue open - Middleware News If you have a problem with a queue, check whether your application has the queue open About this task Perform the following steps to determine whether your application has the queue open: Procedure Ensure that the application that is running against the queue is the application that you expect. Issue the following command for the queue in question: DISPLAY QSTATUS(Q1) TYPE(HANDLE) ALL In the output, look at the APPLTAG field, and check that the name of your application is shown. If the name of your application is not shown, or if there is no output at all, start your application. If the queue is a transmission queue, look in the output at the CHANNEL field. If the channel name is not shown in the CHANNEL field, determine whether the channel is running. Ensure that the application that is running against the queue has the queue open for input. Issue the following command: DISPLAY QSTATUS(Q1) TYPE

IPPROCS or OPPROCS greater than 0 in a queue prevents normal termination of queue manager by "endmqm QmgrName" - Middleware News Question You notice that when the queue attributes of IPPROCS or OPPROCS are greater than 0, and try to end the queue manager by issuing "endmqm QmgrName", then the queue manager goes into "quiescing" but it does not fully terminate. Is there a way to speed up the shutdown of the queue manager? Answer If "endmqm QMgrName" does not effectively end the queue manager, you can try to speed up the shutdown process by adding the flag -i such as: endmqm -i QMgrName Background: The following page from the WebSphere MQ V7 Information Center has more information about the IPPROCS and OPPROCS attributes for a queue: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.explorer.doc/e_status_queue.htm Queue status attributes: Attribute: Open input count Meaning: This is the numb