Script:
Owner:
Subdir: middlewarenews
Blog ID: 93013848
Group ID: User ID: 92249378

My Profile

  • Jennifer
    Jennifer

  • Suneel
    Suneel

  • sudheer
    sudheer

  • kotaru
    kotaru

    Migrating to IBM WebSphere MQ for AIX Version 7.0 - Middleware News

    Tuesday, July 10, 2012, 9:58 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    If you want to migrate to WebSphere MQ Version 7.0, complete this task.

    If you migrate from a previous level of this product without first backing up your system, you cannotrevert to your previous level, so back up your system before you install WebSphere MQ Version 7.0. You can then back out the upgrade if necessary. If you back out the upgrade, however, you cannot recover any work, such as changes to messages and objects, performed by WebSphere MQ Version 7.0.

    Procedure

    1. Stop all MQ applications on the machine and the applications accessing remote machines.
    2. End all WebSphere MQ activity.
      1. Log in as a user in group mqm.
      2. Start of changeUse the dspmq command to display the state of all the queue managers on the system.End of change
      3. Use the endmqm command to stop all running queue managers.
      4. Stop any listeners associated with the queue managers, using the command:
        endmqlsr -m QMgrName
      5. To check that you have stopped all of them, enter the following:
        ps -ef | grep mq
        Check that there are no processes listed that are running command lines beginning amq orrunmq. Ignore any that start with amqi.
    3. Log in as root.
    4. Function supplied by the SupportPacs in Table 1 has been superseded by function in WebSphere MQ Version 7.0. Remove these SupportPacs before installing WebSphere MQ Version 7.0.
      Table 1. SupportPacs superseded by WebSphere MQ Version 7.0
      SupportPac NumberDescription
      MA0Y WebSphere MQ Bridge for HTTP
      Note: If you installed SupportPac MACS, remove the directory /usr/mqm/inc64 and its contents.
      Review any other installed SupportPacs for their applicability to WebSphere MQ Version 7.0.
    5. Start of change If you are migrating from WebSphere MQ Version 5.3 to WebSphere MQ Version 7.0, you must uninstall WebSphere MQ Version 5.3. If you are migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, you do not have to uninstall WebSphere MQ because the installation process does it for you. However, when migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, before installing you must ensure that you manually remove the file sets which have been retired from WebSphere MQ Version 7.0.
      • Remove the following file sets before migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0:
        • mqm.msg.De_DE
        • mqm.msg.Es_ES
        • mqm.msg.Fr_FR
        • mqm.msg.It_IT
      End of change
    6. Install WebSphere MQ Version 7.0 by following the tasks set out in Start of changeInstalling a WebSphere MQ serverEnd of change.
    7. Restart WebSphere MQ.
    0 (0 Ratings)
    [ 703 views ] Leave a Comment

    WebSphere MQ 7.1: How to remove a channel authentication record (CHLAUTH) - Middleware News

    Tuesday, July 10, 2012, 9:54 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    You have added a channel authentication record into a WebSphere MQ 7.1 queue manager:

    DISPLAY CHLAUTH(*) TYPE(USERMAP)
    1 : DISPLAY CHLAUTH(*) TYPE(USERMAP)
    AMQ8878: Display channel authentication record details.
    CHLAUTH(*) TYPE(USERMAP)
    CLNTUSER(rivera) USERSRC(CHANNEL)

    Now you want to remove it and you try executing the following runmqsc command which you constructed using copy and paste from the above output:

    DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) USERSRC(CHANNEL)
    3 : DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) USERSRC(CHANNEL)

    You get the following error:

    AMQ8405: Syntax error detected at or near end of command segment below:-
    DELETE CHLAUTH

    The DELETE CHLAUTH does not exist and after consulting the MQ 7.1 Information Center you read that you have to use the SET CHLAUTH command with the argument ACTION(REMOVE). You try now:

    SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) ACTION(REMOVE)
    19 : SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) ACTION(REMOVE)

    But you get the following error:

    AMQ8884: Channel authentication record not found.

    You specified the attribute CLNTUSER(rivera) as it was shown in the output of the DISPLAY CHLAUTH(*), thus, you think the record should be found. You want to know what is the problem?

    Cause

    See the following section of the MQ 7.1 Information Center:

    publib.boulder.ibm.com/infocenter/wmqv7/...
    WebSphere MQ > Administering > Administering local WebSphere MQ objects > Performing local administration tasks using MQSC commands
    WebSphere MQ object names
    + Case-sensitivity in MQSC commands
    MQSC commands, including their attributes, can be written in upper-case or lower-case. Object names in MQSC commands are folded to upper-case (that is, QUEUE and queue are not differentiated), unless the names are enclosed within single quotation marks. If quotation marks are not used, the object is processed with a name in upper-case. 

    When specifying the SET command with the following value CLNTUSER(rivera) the string 'rivera' will be folded to upper-case resulting in the following value being actually used by runmqsc:
    CLNTUSER(RIVERA)
    And in this case, there is no record for the user RIVERA (the record is for 'rivera').


    Answer

    NOTICE that the userid mentioned in the CLNTUSER field of the output of the DISPLAY CHLAUTH command is NOT surrounded by single quotes.
    However, you MUST include the single quotes when specifying the value during an ACTION(REMOVE):

    SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER('rivera') ACTION(REMOVE)
    1 : set CHLAUTH(*) TYPE(USERMAP) CLNTUSER('rivera') ACTION(REMOVE)
    AMQ8877: WebSphere MQ channel authentication record set.

    Additional Search Words: uppercase lowercase upper lower case

    0 (0 Ratings)
    [ 1572 views ] Leave a Comment

    Uninstalling WebSphere MQ on Linux - Middleware News

    Tuesday, July 10, 2012, 9:51 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    Procedure

    1. Before starting to uninstall, end all WebSphere MQ activity.
      1. Start of changeLog in as a user in group mqm.End of change
      2. Use the dspmq command to display the state of all the queue managers on the system.
      3. Use the endmqm command to stop all running queue managers.
      4. Stop any listeners associated with the queue managers, using the command:
         endmqlsr -m QMgrName
      5. To check that you have stopped all of the necessary WebSphere MQ processes, type:
        ps -ef | grep mq
      6. Check that there are no processes listed that are running command lines beginning amq orrunmq. Ignore any that start with amqi.
    2. Before you uninstall WebSphere MQ for Linux you must find out the names of the packages (components) currently installed on your system. To list all the packages with their version information, enter the following:
      rpm -q -a | grep MQSeries
      rpm -q -a | grep gsk
      Note: If you have applied maintenance to the install, remove these maintenance packages before removing the base install.
    3. Some of the installed packages are dependent on others. The rpm command will not remove a package if others are dependent on it. For this reason you must uninstall the packages in such an order that each one you uninstall has no dependencies from other packages. To list all of the packages on which a named package (for example MQSeriesServer) depends, enter the following:
      rpm -q --requires MQSeriesServer
      Alternatively, remove all the components at the same time by appending all the package names to the rpm command arguments. For example, to remove the runtime, Server and SDK components, enter the following:
      rpm -ev MQSeriesRuntime MQSeriesServer MQSeriesSDK
    4. After uninstalling , you might want to delete the contents of /var/mqm, which is not removed by the uninstallation. Only do this if you do not need your queue manager data. For example, do not delete the content if you plan to migrate to a later version of WebSphere MQ.
    0 (0 Ratings)
    [ 874 views ] Leave a Comment

    Uninstalling IBM WebSphere MQ on AIX - Middleware News

    Tuesday, July 10, 2012, 9:48 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    Uninstalling WebSphere MQ on AIX

    On AIX®, you can uninstall theWebSphere® MQ server or client using the System Management Interface Tool (SMIT) or the installp command.

    Before you begin

    If any updates have been applied, remove them before starting this uninstallation procedure. For more information, see AIX: Restoring the previous maintenance level on WebSphere MQ version 7.1.

    Procedure

    1. Stop all WebSphere MQ applications associated with the installation you are uninstalling.
    2. For a server installation, end any WebSphere MQ activity associated with the installation you are uninstalling:
      1. Log in as a user in the group mqm.
      2. Set up your environment to work with the installation you want to uninstall. Enter the following command:
        . MQ_INSTALLATION_PATH/bin/setmqenv
        where MQ_INSTALLATION_PATH refers to the location where WebSphere MQ is installed.
      3. Display the state of all queue managers on the system. Enter the following command:
        dspmq -o installation
      4. Stop all running queue managers associated with the installation you want to uninstall. Enter the following command for each queue manager:
        endmqm QMgrName
      5. Stop any listeners associated with the queue managers. Enter the following command for each queue manager:
         endmqlsr -m QMgrName
    3. Log in as root.
    4. Uninstall WebSphere MQ using either installp or smit. If WebSphere MQ was installed in a non-default location, you must use installp to uninstall.
      • Uninstall using installp by entering one of the following commands:
        • For an installation in the default location /usr/mqm
          installp -u mqm
        • For an installation in a non-default location:
          installp -R usil -u mqm
          where usil is the path of the User Specified Install Location (USIL) specified when the product was installed.
      • Uninstall using smit:
        1. Select the required smit window using the following sequence:
           Software Installation and Maintenance Software 
          Maintenance and Utilities Remove Installed Software
        2. List the software in the SOFTWARE name field:
          1. Enter .
          2. Press F4
        3. Select the file sets to uninstall from the list (those beginning with mqm), and pressEnter. There is an option at this stage to do a preview. Leave the option set to the default value of Yes to preview the file sets you are uninstalling, or select No to not preview these file sets.
        4. Press Enter on the Remove Installed Software panel, it asks whether you are sure, press Enter.

    What to do next

    • If the product successfully uninstalled, you can delete any files and directories contained in the/usr/mqm directory under the User Specified Install Location (USIL) specified in the installpuninstallation command.
    • Use the lslpp command to check for other products installed in the USIL. If there are no other products installed in the USIL and you do not intend to use it again, you can delete the USIL using the rmusil command.
    • If there are no other WebSphere MQ installations on the system, and you are not planning to reinstall or migrate, you can delete the /var/mqm and /etc/opt/mqm directory trees. Deleting these directories destroys all queue managers and their associated data.

    [Edited By Moderator]

    0 (0 Ratings)
    [ 852 views ] Leave a Comment

    Removing IBM Websphere broker services on AIX, Linux, Solaris - Middleware News

    Tuesday, July 10, 2012, 9:44 AM
    Posted By: Karthick

    Removing IBM Websphere broker services on AIX, Linux, Solaris

    In some situations, you may want to remove broker services from a server where you install IBM® WebSphere® MQ and WebSphere Event Broker. Removing broker services involves deleting the queue manager, the configuration manager, the broker itself, and the database tables used for storing associated information.

    Before you begin

    There are several situations in which you may want to remove the broker services from a Linux® deployment; for example:
    • When you want to replace the WebSphere Event Broker configuration (possibly to use different ports for the listeners)
    • When you are uninstalling WebSphere MQ and WebSphere Event Broker, and you want to be sure you are leaving a clean configuration

    Procedure

    1. Log on to the server hosting WebSphere MQ and WebSphere Event Broker as root.
    2. Remove the broker services as follows:
      1. Open the Message Broker Command Console..
      2. Navigate to the directory where you installed WebSphere Event Broker.
      3. Stop the message broker with the following command:
        su - mqsi -c "mqsistop broker_name"

        For example:

        su - mqsi -c "mqsistop BRKR_SCCS"
      4. Delete the message broker with the following command:
        mqsideletebroker broker_name

        For example:

        mqsideletebroker BRKR_SCCS
      5. Stop the configuration manager with the following command:
        su - mqsi -c "mqsistop config_manager_name"

        For example:

        su - mqsi -c "mqsistop CMGR_SCCS"
      6. Now delete the configuration manager with the following command:
        mqsideleteconfigmgr config_manager_name -n

        For example:

        mqsideleteconfigmgr CMGR_SCCS -n
        You will see a confirmation:
        BIP8071I: Successful command completion. 

        You can verify that the broker has been removed by ensuring that it no longer appears in the results when you run the following command:

        mqsilist
    3. Remove the queue manager as follows:
      1. Open a terminal and navigate to the root of the WebSphere MQ installation.
      1. Stop the queue manager with the following command:
        su - mqsi -c 
        "/opt/mqm/bin/endmqm queue_manager_name"

        For example,

        su - mqsi -c 
        "/opt/mqm/bin/endmqm sccs.queue.manager"
        You will see a confirmation message:
        Quiesce request accepted. 
        The queue manager will stop when all outstanding work is complete.
      2. Delete the queue manager with the following command:
        dltmqm queue_name

        For example:

        dltmqm sccs.queue.manager
        You will see a confirmation message:
        WebSphere MQ queue manager 'sccs.queue.manager' deleted.
    4. Still on the same server, remove the data source for WebSphere Event Broker as follows:
      1. Open the ODBC Tool by clicking Start > Programs > Administrative Tools > DataSources (ODBC).
      2. Click the System DSN - System Data Sources tab.
      3. Select the datasource that you created for WebSphere Event Broker, and then click Remove.
    5. On the IBM DB2® server, open a DB2 Command Window and drop the database that stores WebSphere Event Broker data.
      Note: Make sure the database is not in use; all users must be disconnected from the database before the database can be dropped.

      For example, if your database is called BRKRDB:

      DB2 DROP DATABASE BRKRDB
    0 (0 Ratings)
    [ 600 views ] Leave a Comment

    Migrating to IBM WebSphere MQ for AIX® Version 7.0 - Middleware News

    Monday, July 9, 2012, 8:54 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    Procedure

    1. Stop all MQ applications on the machine and the applications accessing remote machines.
    2. End all WebSphere MQ activity.
      1. Log in as a user ingroup mqm.
      2. Start of changeUse the dspmq command to display the state of all the queue managers on the system.End of change
      3. Use the endmqm command to stop all running queue managers.
      4. Stop any listeners associated with the queue managers, using the command:
        endmqlsr -m QMgrName
      5. To check that you have stopped all of them, enter the following:
        ps -ef | grep mq
        Check that there are no processes listed that are running command lines beginningamqorrunmq. Ignore any that start withamqi.
    3. Log in as root.
    4. Function supplied by the SupportPacs in Table 1 has been superseded by function in WebSphere MQ Version 7.0. Remove these SupportPacs before installing WebSphere MQ Version 7.0.
      Table 1. SupportPacs superseded by WebSphere MQ Version 7.0
      SupportPac NumberDescription
      MA0Y WebSphere MQ Bridge for HTTP
      Note:If you installed SupportPac MACS, remove the directory/usr/mqm/inc64and its contents.
      Review any other installed SupportPacs for their applicability to WebSphere MQ Version 7.0.
    5. Start of change If you are migrating from WebSphere MQ Version 5.3 to WebSphere MQ Version 7.0, you must uninstall WebSphere MQ Version 5.3. If you are migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, you do not have to uninstall WebSphere MQ because the installation process does it for you. However, when migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, before installing you must ensure that you manually remove the file sets which have been retired from WebSphere MQ Version 7.0.
      • Remove the following file sets before migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0:
        • mqm.msg.De_DE
        • mqm.msg.Es_ES
        • mqm.msg.Fr_FR
        • mqm.msg.It_IT
      End of change
    6. Install WebSphere MQ Version 7.0 by following the tasks set out in Start of changeInstalling a WebSphere MQ serverEnd of change.
    7. Restart WebSphere MQ.

    0 (0 Ratings)
    [ 340 views ] Leave a Comment

    IBM WebSphere MQ JMS exception messages - Middleware News

    Tuesday, June 26, 2012, 11:45 PM
    Categories: WebSphere MQ
    Posted By: Karthick

    JMS exception messages

    This section lists most common exceptions that can be generated by WebSphere MQ JMS. It does not include all messages that can be written to a trace file. If you receive an exception message not in this list (except in a trace file), or if the cause seems to be an error in WebSphere MQ JMS, please contact your IBM service representative.

    MQJMS0000 Method {0} has been invoked at an illegal or inappropriate time or if the provider is not in an appropriate state for the requested operation.
    Explanation: The normal reason for this exception is that the SSL certificate stores have not been defined. {0} identifies the method that has caused the problem. 
    User Response: 
    See Using Secure Sockets Layer (SSL) for more information.

    MQJMS0002 JMS Client attempted to set invalid clientId on a connection.
    Explanation: An application attempted to set the clientId property of a valid connection to null, or attempted to set the clientId property of an invalid connection. 
    User Response: 
    The clientId property on a connection can only be set once, only to a non-null value, and only before the connection is used. Ensure that the connection is valid and that the clientId value is not null.

    MQJMS0003 Destination not understood or no longer valid.
    Explanation: The queue or topic may have become unavailable, the application may be using an incorrect connection for the queue or topic, or the supplied destination is not of the correct type for this method. 
    User Response: 
    Check that WebSphere MQ is still running and the queue manager is available. Check that the right connection is being used for your queue or topic.

    MQJMS0004 JMS Client has given JMS Provider a message selector with invalid syntax.
    Explanation: The message selector string is empty or contains an invalid value or syntax. 
    User Response: 
    Check the linked WebSphere MQ exception reason and completion codes for more information.

    MQJMS0005 Unexpected end of stream has been reached when a StreamMessage or BytesMessage is being read.
    Explanation: The byte stream being read is shorter than the buffer supplied. This can also be caused by receiving a corrupt StreamMessage or BytesMessage. 
    User Response: 
    Check the length of buffer supplied. Check system event logs for more information.

    MQJMS0006 JMS Client attempts to use a data type not supported by a message or attempts to read data in the wrong type.
    Explanation: Wrong data types used to read message property types. 
    User Response: 
    Check that the message received and the properties to be read are of the type expected.

    MQJMS0009 JMS Provider is unable to allocate the resources required for a method.
    Explanation: Machine resources may be overloaded, the linked exception may give further information. 
    User Response: 
    Check system resources and load.

    MQJMS0010 Operation invalid because a transaction is in progress.
    Explanation: 
    User Response: 
    Wait for the current transaction to complete. See the linked WebSphere MQ exception for further information.

    MQJMS0011 Call to Session.commit resulted in a rollback of the current transaction.
    Explanation: The transaction failed resulting in a call to rollback to a safe state. See the linked exception for more information.

    MQJMS1000 Failed to create JMS message.
    Explanation: Invalid message type or properties were specified when creating a base message. 
    User Response: 
    Check the linked WebSphere MQ exception Reason and Completion code for more information.

    MQJMS1001 Unknown acknowledgement mode {0}.
    Explanation: Invalid or no parameter {0} set for acknowledgement mode on the session. 
    User Response: 
    See Session for the possible values for acknowledgement mode.

    MQJMS1004 Connection closed.
    Explanation: An operation such as start() or stop() has been called on a connection that is already closed. 
    User Response: 
    Ensure that the connection is open before performing any operation.

    MQJMS1005 Unhandled state transition from {0} to {1}.
    Explanation: The state transition is not valid, see log for more information. 
    User Response: 
    Check the linked WebSphere MQ exception reason and completion code.

    MQJMS1006 Invalid value for {0}: {1}
    Explanation: Invalid value {1} for property {0}. 
    User Response: 
    Check the linked WebSphere MQ exception reason and completion code. SeeTable 11 for a list of valid values for this property.

    MQJMS1008 Unknown value of transportType: {0}.
    Explanation: The value given for transportType could not be used. {0} shows the invalid value. 
    User Response: 
    See Table 11 for a list of valid values for this property.

    MQJMS1010 Not implemented.
    Explanation: The function requested is not implemented. This can be thrown by message acknowledgement, if the session or acknowledgement parameters are invalid or incorrect.

    MQJMS1011 Security credentials cannot be specified when using MQ bindings.
    Explanation: The RRS queue does not support a client connection, and bindings connections do not support the specification of security credentials. 
    User Response: 
    Ensure that you do not try to specify security credentials when using a bindings connection.

    MQJMS1012 No message listener.
    Explanation: The message listener has stopped or was never started. 
    User Response: 
    Restart the message listener and retry.

    MQJMS1013 Operation invalid while session is using asynchronous delivery.
    Explanation: You cannot perform the requested operation while the session is actively using asynchronous delivery mode. 
    User Response: 
    See Asynchronous delivery for further information.

    MQJMS1014 Operation invalid for identified producer.
    Explanation: The QueueSender.send method has been performed on an identified QueueSender, which contradicts the JMS specification 
    User Response: 
    See QueueSender and the JMS specification (java.sun.com/products/jms/docs.html) for further information.

    MQJMS1015 Unknown value of targetClient: {0}.
    Explanation: The value for the targetClient property set by the application for this destination is not recognized by WebSphere MQ JMS. 
    User Response: 
    See Sending a message for valid values of the targetClient property.

    MQJMS1017 Non-local MQ queue not valid for receiving or browsing.
    Explanation: An attempt was made to perform an inappropriate operation on a non-local queue. 
    User Response: 
    Check the queue properties.

    MQJMS1018 No valid connection available.
    Explanation: The queue is busy, there are network problems or a connection has not been defined for the object. 
    User Response: 
    Create a valid connection for this operation.

    MQJMS1019 Invalid operation for non-transacted session.
    Explanation: Commit is not allowed on a session that is not transacted. 
    User Response: 
    Check the linked IllegalStateException for more information. See Session for further information.

    MQJMS1020 Invalid operation for transacted session.
    Explanation: Invalid acknowledgement mode for a transacted session. Acknowledge and Recover are not valid operations in transacted sessions. 
    User Response: 
    See Session for further information.

    MQJMS1021 Recover failed: unacknowledged messages might not get redelivered.
    Explanation: The system was unable to recover from a failure. 
    User Response: 
    Contact your IBM representative.

    MQJMS1022 Failed to redirect message.
    Explanation: Unable to send message onto next destination. 
    User Response: 
    Contact your IBM representative.

    MQJMS1023 Rollback failed.
    Explanation: The system was unable to rollback to a safe state. 
    User Response: 
    Check the linked WebSphere MQ Exception reason and completion codes for further information.

    MQJMS1024 Session closed.
    Explanation: The session timed out or was closed; or either the connection or the queue manager was closed, implicitly closing the session. 
    User Response: 
    Restart the session, and check all required resources are available.

    MQJMS1025 Failed to browse message.
    Explanation: No message was available for browsing. There may be no message on the Queue. 
    User Response: 
    Check the linked WebSphere MQ Exception reason and completion codes. Check that a message is available for browsing.

    MQJMS1026 ExceptionListener threw exception: {0}.
    User Response: Check linked exceptions for further information.

    MQJMS1027 Failed to reconstitute destination from {0}.
    Explanation: A message has been received which contains invalid destination information in the RFH2 header. 
    User Response: 
    Ensure that any messages being sent by non-JMS applications have correctly formatted destination information. In the case of RFH2 headers, pay special attention to the "Rto" (reply to) and "Dst" (destination) elements of the XML portion of the header. Valid destination strings must start either "queue" or "topic".

    MQJMS1028 Element name is null.
    Explanation: A null name string was passed to one of the "get value by name" methods of MapMessage. 
    User Response: 
    Ensure that all name strings being used to retrieve values are non-null.

    MQJMS1029 Property name is null.
    Explanation: The itemExists method of MapMessage was invoked with a null item name; or a null name string was used as an argument to a method which retrieves property values by name from a JMS message. 
    User Response: 
    Ensure that the name strings indicated do not have null values.

    MQJMS1031 An internal error has occurred. Please contact your system administrator.
    Explanation: Internal Error. 
    User Response: 
    Contact your IBM representative.

    MQJMS1032 close() failed because of {0}
    Explanation: Internal Error. {0} indicates the reason for the error. 
    User Response: 
    Contact your IBM representative.

    MQJMS1033 start() failed because of {0}.
    Explanation: {0} indicates why the session failed to start. 
    User Response: 
    Contact your IBM representative.

    MQJMS1034 MessageListener threw: {0}.
    Explanation: A problem has occurred. {0} shows a symptom of the error. 
    User Response: 
    Contact your IBM representative.

    MQJMS1035 Cannot transmit non-MQ JMS messages.
    Explanation: Wrong message type used. This is a possible internal problem. 
    User Response: 
    Check the message type. Contact your IBM representative if there appears to be an internal error.

    MQJMS1036 Failed to locate resource bundle.
    Explanation: The resource bundle is either not present or not in the application's classpath. 
    User Response: 
    Check that the classpath includes the location of property files.

    MQJMS1038 Failed to log error.
    Explanation: Log settings may be incorrect, see the linked LogException. 
    User Response: 
    Check log settings are correct.

    MQJMS1039 Trace file does not exist
    Explanation: Trace settings may be incorrect. 
    User Response: 
    Check trace settings and trace file existence. See Tracing programs for more information on Trace.

    MQJMS1040 Failed to connect to Trace stream.
    Explanation: Trace settings may be incorrect. 
    User Response: 
    See Tracing programs for more information on Trace.

    MQJMS1041 Failed to find system property {0}.
    Explanation: The system property specified in {0} does not exist or was not found in the application's classpath. 
    User Response: 
    Check the classpath settings and the product installation.

    MQJMS1042 Invalid delivery mode.
    Explanation: Either an invalid value was specified for the delivery mode of a message producer, or an invalid delivery mode value was specified when publishing a message. 
    User Response: 
    Check to ensure that the value specified is a valid enumeration for delivery mode.

    MQJMS1043 JNDI failed due to {0}.
    Explanation: {0} gives further information. 
    User Response: 
    Check settings for LDAP, JNDI, and in the JMSAdmin.config file.

    MQJMS1044 String is not a valid hexadecimal number - {0}.
    Explanation: An attempt was made to specify a group ID or correlation ID which starts with the prefix "ID:" but is not followed by a well-formed hex value; or an attempt was made to receive a message which contains an RFH2 property of type bin.hex that does not have a well-formed hex value. 
    User Response: 
    Ensure that a valid hex value always follows the "ID:" prefix when setting group ID or correlation ID values. Ensure that any RFH2 headers generated by non-JMS applications are well-formed.

    MQJMS1045 Number outside of range for double precision S/390 Float {0}.
    Explanation: This is a z/OS & OS/390 specific error.

    MQJMS1046 The character set {0} is not supported.
    Explanation: An attempt was made to send or receive a map message, stream message or text message whose body is encoded using a character set not supported by the JVM. In the case of text messages, this exception may be thrown when the body of the message is first queried, rather than at receive time. 
    User Response: 
    Only set character encoding on a message to values known to be available to the receiving application.

    MQJMS1047 The map message has an incorrect format.
    Explanation: A map message was received, but its RFH2 header information is badly formatted. 
    User Response: 
    Ensure any non-JMS applications are building well-formed RFH2 header information for inclusion in map messages.

    MQJMS1048 The stream message has an incorrect format.
    Explanation: A stream message was received, but its RFH2 header information is badly formatted. 
    User Response: 
    Ensure any non-JMS applications are building well-formed RFH2 header information for inclusion in stream messages.

    MQJMS1049 The JMS client attempted to convert a byte array to a String.
    Explanation: Attempting to receive a byte array from a stream message using the readString method. 
    User Response: 
    Either use the appropriate method to receive the data, or format the data placed into the stream message correctly.

    MQJMS1050 The MQRFH2 header has an incorrect format.
    Explanation: Receiving a message with a badly formed RFH2 header. 
    User Response: 
    Ensure that any non-JMS applications building messages with RFH2 headers create well-formed RFH2 headers.

    MQJMS1053 Invalid UTF-16 surrogate detected {0}.
    Explanation: An invalid UTF-16 surrogate character has been encountered as part of a topic name or RFH2 property. 
    User Response: 
    Ensure that, when specifying UTF-16, topic names or RFH2 properties are well-formed.

    MQJMS1054 Invalid XML escape sequence detected {0}.
    Explanation: An invalid XML escape sequence has been encountered in the RFH2 header of a received message. 
    User Response: 
    Ensure that only valid XML escape sequences are placed into any RFH2 headers built by non-JMS applications.

    MQJMS1055 The property or element in the message has incompatible datatype {0}.
    Explanation: Attempting to retrieve a property from a JMS message using a accessor method which specifies an incompatible type. For example, attempting to retrieve an integer property using the getBooleanProperty method. 
    User Response: 
    Use an accessor method defined by the JMS specification as being able to retrieve property values of the required type.

    MQJMS1056 Unsupported property or element datatype {0}.
    Explanation: This error is caused by one of the following: 
    1. Attempting to set a property of a JMS message using an object which is not one of the supported types. 
    2. Attempting to set or receive a message whose RFH2 contains a element representing a property which does not have a valid type associated with it. 

    User Response: 
    Ensure that when setting message properties, an object type described as being valid in the JMS specification is used. If this exception occurs when receiving a message containing an RFH2 header sent by a non-JMS application, ensure that the RFH2 header is well-formed.

    MQJMS1057 Message has no session associated with it.
    Explanation: An attempt was made to acknowledge a message on a session which is not in an open state. 
    User Response: 
    Ensure that the session associated with the message has been correctly opened. Check that the session has not been closed.

    MQJMS1058 Invalid message property name: {0}.
    Explanation: Attempting to set a property that either does not have a valid property name, or is not a settable property. 
    User Response: 
    Ensure that the property name used is a valid property name in accordance with the JMS specification. If the property name refers to a JMS or provider-specific extension property, ensure that this property is settable.

    MQJMS1059 Fatal error - UTF8 not supported.
    Explanation: The Java runtime environment you are using does not support the UTF-8 character encoding. JMS requires support for this encoding to perform some operations. 
    User Response: 
    Consult the documentation and or provider of your Java runtime environment to determine how to obtain support for the UTF-8 character encoding.

    MQJMS1060 Unable to serialize object.
    Explanation: An attempt has been made to serialize an ObjectMessage which contains a non-serializable object. 
    User Response: 
    Ensure that ObjectMessages only contain serializable objects. If the object placed inside an ObjectMessage references other objects, these must also be serializable.

    MQJMS1061 Unable to deserialize object.
    Explanation: De-serialization of an ObjectMessage failed. 
    User Response: 
    Ensure that the ObjectMessage being received contains valid data. Ensure that the class files representing object data contained within the ObjectMessage are present on the machine deserializing the ObjectMessage. If the object contained within the ObjectMessage references other objects, ensure that these class files are also present.

    MQJMS1066 Invalid message element name: {0}.
    Explanation: Attempting to set a message property using either an invalid property name, or the name of a property which cannot have its value set. 
    User Response: 
    Ensure that the property name specified conforms to the JMS specification. If the property name supplied is that of a JMS property, or a vendor specific extension, ensure that this property name is settable.

    MQJMS1067 Timeout invalid for MQ.
    Explanation: An attempt was made to invoke the receive method on either a QueueReceiver or TopicSubscriber method, specifying a long timeout value which is not valid. 
    User Response: 
    Ensure the timeout value specified is not negative and not greater than the value of Integer.MAX_VALUE.

    MQJMS1068 Failed to obtain XAResource.
    Explanation: JMS failed to create an XA Queue resource due to an error. 
    User Response: 
    See the linked XAException for more information.

    MQJMS1072 Could not inquire upon queue manager name.
    Explanation: In createConnectionConsumer() or createDurableConnectionConsumer(), JMS could not determine the name of the queue manager. 
    User Response: 
    Check your queue manager error logs for problems which may cause this. If there are no other error conditions, contact your IBM representative.

    MQJMS1073 Specified MQ Queue is neither a QLOCAL nor a QALIAS.
    Explanation: createConnectionConsumer() was called, but a queue of the wrong type was specified. Only QALIAS and QLOCALs can be used with the ConnectionConsumer feature. 
    User Response: 
    Specify a queue of the correct type.

    MQJMS1074 Unable to process null message.
    Explanation: Internal error in WebSphere MQ JMS. 
    User Response: 
    Contact your IBM representative.

    MQJMS1075 Error writing dead letter header.
    Explanation: JMS attempted to requeue a message to the dead letter queue, but could not construct a dead letter header. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS1076 Error reading dead letter header.
    Explanation: JMS attempted to interpret a message with a dead letter header, but encountered a problem. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS1077 Connection and Destination mismatch.
    Explanation: An operation was requested, but the Destination class is incompatible with the Connection class. Topics cannot be used with QueueConnections and Queues cannot be used with TopicConnections. 
    User Response: 
    Supply a suitable Destination. This may represent an internal error condition in JMS; in this case contact your IBM representative.

    MQJMS1078 Invalid Session object.
    Explanation: The JMS ConnectionConsumer feature attempted to deliver a batch of messages to a Session. However, the Session contained in the ServerSession object returned by the ServerSessionPool was not a WebSphere MQ JMS Session. 
    User Response: 
    This is an error in the ServerSessionPool. If you have supplied a ServerSessionPool, check its behavior. In a J2EE application server, this may represent an error in the application server; in which case, refer to your application server's documentation.

    MQJMS1079 Unable to write message to dead letter queue.
    Explanation: JMS attempted to requeue a message to the dead letter queue, but failed. 
    User Response: 
    Use the linked exception to determine the cause of this error. If there is no linked exception, check that the queue manager has a defined dead letter queue. Once JMS has sent a message to the dead letter queue, the reason code stored in the message's DLH can be used to determine why the message was dead-lettered.

    MQJMS1080 No Backout-Requeue queue defined.
    Explanation: JMS encountered a message which has been backed out more than the queue's Backout Threshold, however the queue doesn't have a Backout-Requeue queue defined. 
    User Response: 
    Define a Backout-Requeue queue for the queue, or set the Backout Threshold to zero to disable poison message handling. Investigate the repeated backouts.

    MQJMS1081 Message requeue failed.
    Explanation: JMS found an error when requeuing a message which has been backed out more than the queue's Backout Threshold. 
    User Response: 
    Use the linked exception to determine the cause of this error. Investigate the repeated backouts.

    MQJMS1082 Failure while discarding message.
    Explanation: JMS encountered an error while discarding a message, or while generating an exception report for a message to be discarded. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS1083 Invalid message batch size (must be >0).
    Explanation: An invalid batch size parameter was passed to createConnectionConsumer() or createDurableConnectionConsumer(). 
    User Response: 
    Set a batch size greater than zero. In a J2EE application server, this may represent an error in the application server. Refer to your application server's documentation.

    MQJMS1084 Null ServerSessionPool has been provided.
    Explanation: The ServerSessionPool specified on createConnectionConsumer() or createDurableConnectionConsumer() was null. 
    User Response: 
    Set an appropriate ServerSessionPool. In a J2EE application server, this may represent an error in the application server. Refer to your application server's documentation.

    MQJMS1085 Error writing RFH.
    Explanation: JMS attempted to construct an RFH message header, but encountered an error. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS1086 Error reading RFH.
    Explanation: JMS encountered an error while parsing an RFH message header. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS1087 Unrecognized or invalid RFH content.
    Explanation: JMS expected to find an RFH message header, but found it to be missing, malformed or lacking required data. 
    User Response: 
    Investigate the source of the message. This may represent an internal error condition in JMS; in this case, contact your IBM representative.

    MQJMS1088 Mixed-domain consumers acting on the same input is forbidden.
    Explanation: A point-to-point ConnectionConsumer is using the subscriber queue of a publish/subscribe ConnectionConsumer. 
    User Response: 
    Do not attempt to access subscriber queues using the point-to-point ConnectionConsumer facilities of JMS. Check your TopicConnectionFactory and Topic objects to make sure they are not using a QLOCAL intended for use by point-to-point applications as a subscriber queue.

    MQJMS1089 Exception occurred reading message body: {0}.

    Explanation: 
    JMS encountered an exception while reading data from a message. The message being read is likely to be a response message from the publish/subscribe broker. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS2000 Failed to close MQ queue.
    Explanation: JMS attempted to close a WebSphere MQ queue, but encountered an error. The queue may already be closed, or another thread may be performing an MQGET while close() is called. 
    User Response: 
    Use the linked exception to determine the cause of this error. You may be able to perform the close() later.

    MQJMS2001 MQQueue reference is null.
    Explanation: JMS attempted to perform some operation on a null MQQueue object. 
    User Response: 
    Check your system setup, and that all required queue names have been specified. This may represent an internal error condition in JMS; in this case, contact your IBM representative.

    MQJMS2002 Failed to get message from MQ queue.
    Explanation: JMS attempted to perform an MQGET; however WebSphere MQ reported an error. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS2003 Failed to disconnect queue manager.
    Explanation: JMS encountered an error while attempting to disconnect. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS2004 MQQueueManager reference is null.
    Explanation: JMS attempted to perform an operation on a null MQQueueManager object. 
    User Response: 
    Check that the relevant object has not been closed. This may represent an internal error condition in JMS; in this case, contact your IBM representative.

    MQJMS2005 Failed to create MQQueueManager for {0}.
    Explanation: JMS could not connect to a queue manager. {0} gives the name of the queue manager. 
    User Response: 
    Use the linked exception to determine the cause of this error. Check the queue manager is running and, if using client attach, that the listener is running and the channel, port and hostname are set correctly. If no queue manager name has been specified, check that the default queue manager has been defined.

    MQJMS2006 MQ problem: {0}.
    Explanation: JMS encountered some problem with WebSphere MQ. {0} describes the problem. 
    User Response: 
    Use the included text and linked exception to determine the cause of this error.

    MQJMS2007 Failed to send message to MQ queue.
    Explanation: JMS attempted to perform an MQPUT; however WebSphere MQ reported an error. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS2008 Failed to open MQ queue.
    Explanation: JMS attempted to perform an MQOPEN; however WebSphere MQ reported an error.
    User Response: 
    Use the linked exception to determine the cause of this error. Check that the specified queue and queue manager are defined correctly.

    MQJMS2009 MQQueueManager.commit() failed.
    Explanation: JMS attempted to perform an MQCMIT; however WebSphere MQ reported an error. 
    User Response: 
    Use the linked exception to determine the cause of this error.

    MQJMS2010 Unknown value for MQ queue definitionType: {0}.
    Explanation: Unable to delete the temporary queue as the definitionType is not valid. 
    User Response: 
    Check the setting of definitionType.

    MQJMS2011 Failed to inquire MQ queue depth.
    Explanation: WebSphere MQ JMS is unable to tell how many messages are on the queue. 
    User Response: 
    Check that the queue and queue manager are available.

    MQJMS2012 XACLOSE failed.
    Explanation: See linked XAException for more details.

    MQJMS2013 Invalid security authentication supplied for MQQueueManager.
    Explanation: Bad username or password or both. In bindings mode, a supplied user ID does not match the logged in user ID. 
    User Response: 
    Check that the user IDs used by WebSphere MQ are all assigned to the relevant groups and given appropriate user permissions.

    MQJMS3000 Failed to create a temporary queue from {0}.
    Explanation: Creation of temporary queue failed. 
    User Response: 
    See linked exception for more information. Check that the TemporaryModel parameter against the QueueConnectionFactory is set to a valid model queue.

    MQJMS3001 Temporary queue already closed or deleted.
    Explanation: Temporary queue no longer exists or is equal to null. 
    User Response: 
    Check to see that the queue has been created, and that the session is still available.

    MQJMS3002 Temporary queue in use.
    Explanation: Another program is using the queue. 
    User Response: 
    Wait for the temporary queue to become free or create another.

    MQJMS3003 Cannot delete a static queue.
    Explanation: Attempted to delete a queue of type static, where a temporary queue was expected.
    User Response: 
    Check the expected queue type for deletion.

    MQJMS3004 Failed to delete temporary queue.
    Explanation: The temporary queue may be persistent or busy. 
    User Response: 
    See the linked WebSphere MQ exception for more details. Wait if the queue is busy, or delete the queue manually if it is persistent.

    MQJMS3005 Publish/Subscribe failed due to {0}.
    Explanation: General error: {0} shows the reason. 
    User Response: 
    Check the linked WebSphere MQ Exception reason and completion codes for more information. It is possible that the broker and queue manager versions are incompatible.

    MQJMS3006 Topic reference is null.
    Explanation: Topic supplied to a publisher is null. 
    User Response: 
    Use non-null values.

    MQJMS3008 Failed to build command {0}.
    Explanation: Broker message command parameters incorrect. 
    User Response: 
    Check linked exception for cause.

    MQJMS3009 Failed to publish command to MQ queue.
    Explanation: Invalid command, queue unavailable or broker errors. 
    User Response: 
    Check linked WebSphere MQ exception reason and completion codes for more information.

    MQJMS3010 Failed to build publish message.
    Explanation: Unable to build the base message for the broker. 
    User Response: 
    See the linked WebSphere MQ Exception for further details. Check settings and parameters are all correct. See Chapter 11, Programming publish/subscribe applications for more information.

    MQJMS3011 Failed to publish message to MQ queue.
    Explanation: See linked Exception for more information. 
    User Response: 
    Check settings and parameters are all correct. See Chapter 11, Programming publish/subscribe applications for more information.

    MQJMS3013 Failed to store admin. entry.
    Explanation: An add to the admin or status queue failed due to duplication or some other error. See any linked exception for more information. 
    User Response: 
    Check for duplicates and retry.

    MQJMS3014 Failed to open subscriber queue {0}.
    User Response: See linked exception for more information.

    MQJMS3017 Failed to delete subscriber queue {0}.
    Explanation: {0} gives the queue name. See linked exception for more information. 
    User Response: 
    See Chapter 11, Programming publish/subscribe applications for more information on solving publish/subscribe problems.

    MQJMS3018 Unknown durable subscription {0}.
    Explanation: Could not locate the given subscription. For example, during an unsubscribe request. 
    User Response: 
    See Chapter 11, Programming publish/subscribe applications for more information.

    MQJMS3020 TemporaryTopic out of scope.
    Explanation: The current connection ID does not match the connection that created the temporary topic.

    MQJMS3021 Invalid subscriber queue prefix: {0}.
    Explanation: The name specified is not valid. It must begin with SYSTEM.JMS.D for durable subscriptions or SYSTEM.JMS.ND for non-durable subscriptions. 
    User Response: 
    See Chapter 11, Programming publish/subscribe applications for naming conventions.

    MQJMS3022 Durable re-subscribe must use same subscriber queue; specified: {0}, original: {1}.
    Explanation: {0} and {1} show the differing queue names. Unable to get a subscription due to wrong queue manager or queue. 
    User Response: 
    Check settings.

    MQJMS3023 Subscription has an active TopicSubscriber.
    Explanation: Can be caused by a queue open problem or if a subscription already exists on the JVM. If running in WebSphere Application Server there can be other causes. See linked exception, if set, for more information. 
    User Response: 
    Check settings.

    MQJMS3024 Illegal use of uninitialized clientId.
    Explanation: The clientId in the connection has not been set. 
    User Response: 
    Set the clientId before attempting to perform any operation.

    MQJMS3025 TemporaryTopic in use.
    Explanation: Something else is currently using the topic. 
    User Response: 
    Wait until the topic is free or create another topic. Ensure subscribers de-register when finished.

    MQJMS3026 QueueSender is closed.
    User Response: Open or re-open the queue sender if required.

    MQJMS3027 Local transactions not allowed with XA sessions.
    Explanation: Unexpected error. 
    User Response: 
    Contact your IBM representative.

    MQJMS3028 TopicPublish

    [Edited By Moderator]

    0 (0 Ratings)
    [ 4379 views ] Leave a Comment

    How to configure UNIX and Linux systems for IBM WebSphere MQ - Middleware News

    Tuesday, June 19, 2012, 1:03 PM
    Categories: WebSphere MQ
    Posted By: Karthick

    How to configure UNIX and Linux systems for WebSphere MQ

    Problem(Abstract)

    You are planning to install or upgrade a WebSphere MQ server on a UNIX or Linux system and need to know how to tune the operating system parameters, including kernel parameters related to inter-process communication (IPC) resources like shared memory and semaphores.

    Cause

    If you do not configure your operating system parameters properly, the WebSphere MQ server may exhaust system resources when you process your production workload. Depending on the resource which was exhausted, WebSphere MQ could return an error to the application like MQRC_RESOURCE_PROBLEM (2012), write a message to its error logs, create FDC files in the /var/mqm/errors directory, or even terminate.

    Resolving the problem

    IBM Recommendations
    Using the mqconfig Script
    Operating System Notes
    IPC Tuning Parameters
    Older Version for WebSphere MQ 6.0 and 5.3

    IBM Recommendations

    IBM recommends default values in the WebSphere MQ documentation for several operating system kernel parameters and other tuning values:
    WebSphere MQ 7.5 Additional settings for AIX, HP-UX, Linux and Solaris
    WebSphere MQ 7.1 Additional settings for AIX, HP-UX, Linux and Solaris
    WebSphere MQ 7.0 System resource limits for AIX
    WebSphere MQ 7.0 Kernel configuration for HP-UX
    WebSphere MQ 7.0 Kernel configuration for Linux
    WebSphere MQ 7.0 Resource limit configuration for Solaris
    These default limits should enable you to run WebSphere MQ without exhausting any system resources. However, if your system is extremely busy, you may need to increase certain values beyond the IBM recommended defaults. A busy system may be running a large number of queue managers, or just a single queue manager with thousands of connected applications and millions of messages, or it may be running another product with high resource demands such as IBM DB2.

    If you need to increase parameters beyond the IBM WebSphere MQ defaults, bear in mind that modern systems are capable of supporting large amounts of resources. For example, the UNIX IPC interface was designed in the late 1970s on a 16-bit DEC PDP-11 minicomputer, similar to this one used by UNIX designers Dennis Ritchie and Ken Thompson. Modern systems run with a hundred thousand to more than a million times more memory, so doubling and quadrupling IPC parameters to handle your workload will not stress your system. Be generous with these values and refer to the section on IPC parameters below for more information about specific settings.

    Using the mqconfig Script

    The mqconfig script analyzes your system and compares its settings to the IBM recommended values for WebSphere MQ 7.5, 7.1 or 7.0. It displays the results of this comparison in an easy to read format, along with a PASS, WARN, or FAIL grade for each setting. The mqconfig script does not make any modifications to your systems. A version called mqconfig-old is still provided for older versions of WebSphere MQ.

    To use mqconfig, you must first download the script to your system and make it executable (e.g. 'chmod a+x mqconfig'), then run it using the syntax given below. On Solaris 10 you should use the '-p' parameter to identify the projects in which you run WebSphere MQ queue managers. If you omit this parameter, mqconfig will try to determine which projects it should analyze, perhaps incorrectly.

    mqconfigmqconfig

    syntax: mqconfig -?

            mqconfig -v Version

            mqconfig -v Version [-p Project]...   (Solaris 10 only)


            Version: 7.5, 7.1 or 7.0



    mqconfig -v 7.5
    mqconfig -v 7.1 -p group.mqm -p mqdev
    mqconfig -?

    Here is a sample of the mqconfig output showing a Linux system which has four potential tuning issues. The semmni value is half the IBM recommended value, and the nofile soft limit is way too low, which is why both parameters failed. The tcp_keepalive_time limit is unusual in that lower values are better, so here it failed for being too high. Finally, the shmmni value gave only a warning because it is reasonably close to the IBM limit:




    Please note that any values listed in the "Current User Limits" section are resource limits which apply to the user running mqconfig. If you normally start queue managers as the mqm user (or via sudo to mqm) then you should run mqconfig as mqm to verify its user limits. Other members of the mqm group (and perhaps root as well) can also run mqconfig to make sure their user limits are acceptable for starting WebSphere MQ queue managers.

    The mqconfig script may also recommend a change to your shell options in order to avoid a performance problem caused when shells run WebSphere MQ background jobs with reduced priority. If your shell is not susceptible then mqconfig will print nothing. If mqconfig suggests a change you can simply modify your profile; For example, Korn shell users can add the line 'set +o bgnice' to their profile.

    If you note a discrepancy between mqconfig and the WebSphere MQ Information Center, or if you encounter a problem with the mqconfig script, please submit a comment using the link at the bottom of the page.

    Operating System Notes

    AIX
    The AIX kernel is self-tuning with regard to IPC parameters, so WebSphere MQ will not run into a limit on shared memory or semaphores. The mqconfig script can check other basic settings to ensure they are suitable for WebSphere MQ.


    HP-UX 11i
    You can view or change kernel parameters with the System Management Homepage tool (smh) or by using the kctune command. The kctune command can show whether a parameter change takes effect immediately or whether you must restart the system. On HP-UX 11.23 and older, you may use the System Administration Manager tool (sam) instead of smh.


    Linux
    You can view or change kernel parameters dynamically using the sysctl command or using the files under the /proc filesystem. In order to change the parameters permanently you can add your values to the /etc/sysctl.conf file or use a system startup script to modify the parameters on each startup.

    One oddity is that all semaphore tuning parameters are held in a single parameter called sem, rather than individually. The fields in sem correspond to semmsl, semmns, semopm and semmni. All four fields must be set at the same time, even if you wish to change only one value.


    Solaris 9
    Solaris 9 is supported only by WebSphere MQ 7.0 and older versions. You can view kernel parameters by examining the output of the 'sysdef -i' command. To change parameters you must edit the /etc/system file and then reboot the system.


    Solaris 10
    Solaris 10 uses projects to replace the system-wide tuning parameters used in previous versions. The WebSphere MQ Information Center describes how to use the projects, projadd and projmod commands to list, create and modify projects. The previous kernel parameters have received more descriptive names, but note that some begin with 'project' and others with 'process' as shown below:



    Old Name

    New Name

     semmni

    project.max-sem-ids

     semmsl

    process.max-sem-nsems

     semopm

    process.max-sem-ops

     shmmax

    project.max-shm-memory

     shmmni

    project.max-shm-ids



    In order to use the resource limits recommended by IBM, you should configure a project (for example 'group.mqm') and ensure that you start queue managers in that project. You can check your current project using the id command and use the newtask command to run a single command or start a shell in a different project. The following example demonstrates both methods, with the commands on the dark gray background running in the group.mqm project rather than the default project:


     sun10> id -p
     uid=500(justinf) gid=501(dev) projid=3(default)

     sun10> newtask -p group.mqm strmqm SOHO
     WebSphere MQ queue manager 'SOHO' starting.
     The queue manager is associated with installation 'Manhattan'.
     5 log records accessed on queue manager 'SOHO' during the
       log replay phase.
     Log replay for queue manager 'SOHO' complete.
     Transaction manager state recovered for queue manager 'SOHO'.
     WebSphere MQ queue manager 'SOHO' started using V7.1.0.0.

     sun10> id -p
     uid=500(justinf) gid=501(dev) projid=3(default)

     sun10> newtask -p group.mqm


     sun10> id -p
     uid=500(justinf) gid=501(dev) projid=100(group.mqm)

     sun10> strmqm CHELSEA
     WebSphere MQ queue manager 'CHELSEA' starting.
     The queue manager is associated with installation 'Manhattan'.
     5 log records accessed on queue manager 'CHELSEA' during the
       log replay phase.
     Log replay for queue manager 'CHELSEA' complete.
     Transaction manager state recovered for queue manager 'CHELSEA'.
     WebSphere MQ queue manager 'CHELSEA' started using V7.1.0.0.

     sun10> exit


     sun10> id -p
     uid=500(justinf) gid=501(dev) projid=3(default)



    It is easy for WebSphere MQ queue managers to end up running in the default project, for example because an administrator forgot to use the newtask command. You should either configure the default project to satisfy the IBM WebSphere MQ default tuning values, or put processes in place to ensure that WebSphere MQ commands run in the right project.



    IPC Tuning Parameters

    The following parameters control Inter-Process Communication (IPC) semaphore and shared memory resources used by WebSphere MQ. Not all parameters exist on every system; AIX, for example, does not use any of these parameters. Parameters relating the IPC message queues are not listed since WebSphere MQ no longer uses them.

    If you are installing WebSphere MQ on a system with other products that recommend certain IPC parameter settings. In some cases (marked with an asterisk in the table below) you should add up the recommendations of all the products and use the total. For example, if WebSphere MQ recommends 1024 and DB2 recommends 1024, choose a value of 2048 or higher. Otherwise you should use the highest requested value. For example, if WebSphere MQ wants a value of 256 and DB2 asks for 512, you should use the higher value of 512.



    Parameter

    Description

     semmni   *

    The maximum number of semaphore sets on the system. WebSphere MQ queue managers add sets based on workload, so you should check this parameter at runtime to ensure the resource usage is safely within your limit.

     semmsl

    The maximum number of semaphores in a single set.

     semmns   *

    The total number of semaphores in the system. You can calculate the theoretical maximum by multiplying semmni * semmsl, but in practice some sets will have fewer than the maximum number of semaphores.

     semmnu   *

    The maximum number of semaphore undo requests in the system. When a program ends or crashes, the operating system will automatically release semaphores for which "undo" support was requested. WebSphere MQ uses the undo option with some semaphores to ensure they will not get stuck in a locked state.

     semume   *

    The maximum number of semaphore undo requests a single process can make.

     semaem

    The maximum adjustment value the operating system can apply to a semaphore when processing an undo requests. Since WebSphere MQ uses binary rather than counting semaphores, this parameter does not affect it.

     shmmni   *

    The maximum number of shared memory sets on the system. WebSphere MQ queue managers add sets based on workload, so you should check this parameter at runtime to ensure the resource usage is safely within your limit.

     shmseg   *

    The maximum number of shared memory sets a single process can attach. This value should match shmmni so that WebSphere MQ processes can attach all sets, if necessary.

     shmmax

    The maximum size of a shared memory set. Setting a large value will not waste memory on your system since WebSphere MQ starts by allocating small set, and allocates large ones only when it is processing a heavy workload.

     shmmin

    The minimum size of a shared memory set. There is no compelling reason to use any value other than 1.

     shmall   *

    The maximum number of pages available for shared memory on Linux systems.

     semvmx

    The maximum value of a semaphore. WebSphere MQ does not use counting semaphores, so this parameter does not affect it.

    Older Version for WebSphere MQ 6.0 and 5.3

    The mqconfig-old script is an older version for WebSphere MQ 6.0 and 5.3 which will be withdrawn after WebSphere MQ 6.0 ends support on September 30, 2012. To use mqconfig-old, you must first download the script to your system and make it executable (for example 'chmod a+x mqconfig-old'), then run it using the syntax given below. On Solaris 10 you should use the '-p' parameter to identify the projects in which you run WebSphere MQ queue managers. If you omit this parameter, mqconfig-old will try to guess which projects it should analyze.


    mqconfig-oldmqconfig-old


    syntax: mqconfig-old -?

            mqconfig-old [-v 6.0|5.3]

            mqconfig-old [-v 6.0|5.3] [-p Project]...   (Solaris 10 only)

     

     

    [Edited By Moderator]

    0 (0 Ratings)
    [ 2747 views ] Leave a Comment

    Requirements for Remote Administration using the WebSphere MQ Explorer - Middleware News

    Tuesday, June 19, 2012, 12:59 PM
    Categories: WebSphere MQ
    Posted By: Karthick

    Ensure that you have satisfied the following requirements before trying to use the WebSphere MQ Explorer to do remote administration. Verify that:
    1. The WebSphere MQ server and client is installed on the local and the remote machine.
    2. A command server is running for every queue manager.
    3. A TCP/IP listener exists for every queue manager. This can be the WebSphere MQ listener or the inetd daemon as appropriate for your operating system environment.
    4. The server-connection channel, called SYSTEM.ADMIN.SVRCONN, exists on every remote queue manager. This channel is mandatory for every remote queue manager being administered.

    Using the WebSphere MQ Explorer for Remote Administration

    Satisfy all of the requirements for Remote Administration and then you can use the WebSphere MQ to do administration tasks on your local and remote queue managers.

    To show a remote queue manager, right click the WebSphere MQ Explorer Queue Manager folder, select Show/Hide, then select the Add button on the Add Queue Manager screen(see Figure 1then type: Figure 1




    Figure 2




    Reasons for Remote Administration failures:

    1. The Command server is not running on remote queue manager. Message AMQ4042 will be issued.
    2. The Listener is not running on remote queue manager. Message AMQ4043 will be issued.
    3. The SYSTEM.ADMIN.SVRCONN is not defined on remote queue manager. Message AMQ4043 will be issued.
    4. The security check failed on remote queue manager. Message AMQ4043 will be issued.
    5. Prior releases of WebSphere MQ for z/OS (v5.3 and v5.3.1) do not provide this function and any attempt to remotely administer a queue manager will fail. The WebSphere MQ V6.0 product has been enhanced to support the remote administration of a z/OS queue manager using the WebSphere MQ Explorer on Windows and Linux Intel.
    6. Code page conversion failures can cause problems. Message AMQ4043 will be issued. For more information, see technote: Remote Administration through WebSphere MQ Explorer "Show Queue Manager" Fails AMQ4043
    7. The SYSTEM.MQEXPLORER.REPLY.MODEL is not defined on remote queue manager and you are using the V6.0 WebSphere MQ Explorer. Message AMQ4400 will be issued.
    8. The Client attachment feature is not installed on WebSphere MQ for z/OS. The CHIN joblog will contain message CSQX260E. To connect to the z/OS queue manager using the SYSTEM.ADMIN.SVRCONN channel, you need to have the Client Attachment feature installed, which is FMID JMS6007 for WebSphere MQ for z/OS 6.0.0.

      Note:
      In WebSphere MQ V7 for z/OS you can create five “free” client attachments for use with MQ Explorer. These attachments must use the channel name SYSTEM.ADMIN.SVRCONN, which is the default channel name used by the MQ Explorer.

      To use the free client attachments, you must first alter the SYSTEM.ADMIN.SVRCONN channel definition and set the maximum instances (MAXINST) attribute to 5 or less. You should also ensure that your server-connection channel is secured by the usual means.
    3.7 (1 Ratings)
    [ 5179 views ] Leave a Comment

    IBM Websphere MQ - Constants - Middleware News

    Tuesday, June 19, 2012, 12:49 PM
    Categories: WebSphere MQ
    Posted By: Karthick

    Constants

    List of all the constants

    [ 771 views ] Leave a Comment

    Page 6 of 12  •  Prev 1 ... 4 5 6 7 8 ... 12 Next

Member of the Month

    • WebSphere z/OS System Administrator
      CSC