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

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

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...

Installing IBM Integration Bus on Linux - Middleware News

Before you begin Check the readme.html file for any updates to these installation instructions; see the product readmes web page. Check that you have enough memory and disk space; see IBM Integration Bus system requirements. Check that you have completed any prerequisite steps; see Preparing the system. If you are using Red Hat Linux 6.5 with WebKitGTK version webkitgtk.x86_64 1.2.6-5.el6, complete the steps in the following topic to work around problems with the Eclipse SWT browser: IBM Integration Toolkit on RedHat 6.5 crashes with "JVM terminated. Exit code=160" error. If you are using Red Hat Linux 6.x or 7.x, you might need the GTK2 32-bit drivers installed on Linux; for more information, see IBM Integration Toolkit on Linux becomes unresponsive after opening a DFDL or XSD file. If you are using Red Hat Linux 7.1, complete the steps in the following topic to work around problems with the Eclipse SWT browser: Internal web browser in IBM Integration Toolkit ...