Skip to main content

Channels intermittently go into a status of INITIALIZING - Middleware News

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 job that abended.


Resolving the problem

To resolve the WMQ concern, stop all channels and use the RMVLNK command to delete the ip## object(s). After the ip## objects have been deleted you should be able to restart the channels.


Additional information

The purposes of the ip* files:

When the execution controller (AMQZXMA0) starts an agent for an application, it needs to pass more parameters than are shown on the agent's command line, so, the EC writes them to a file in the queue manager's 'startprm' subdirectory called 'ip##' (where the ## starts at one and increases by one). It contains all of the agent's parameters. The agent is then started and given the name of it's initialization parameter file on the command line, which it opens, reads, and deletes.

Note: Originally the enduser encountered the problem when they attempted to rename the ip## object under the startprm sub-directory. They received messages MCH3402, CPDA1CC and CPFA0A2. This indicates a possible problem in the Integrated file system, and should be reported to the Rochester Support Team.

Comments

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...

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...

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 ...