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

My Profile

  • Jennifer
    Jennifer

  • Suneel
    Suneel

  • sudheer
    sudheer

  • kotaru
    kotaru

    Clearing WebSphere MQ shared memory resources - Middleware News

    Saturday, August 18, 2012, 11:51 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    When a WebSphere MQ queue manager is ended normally, the queue manager removes the majority of the IPC resources that it was using. A small number of IPC resources remain and this is as designed: some of the IPC resources are intended to persist between queue manager restarts. The number of IPC resources remaining varies to some extent, depending on the operating conditions.End of change
    Start of changeThere are some situations when a larger proportion of the IPC resources in use by a queue manager might persist after that queue manager has ended:

        If applications are connected to the queue manager when it stops (perhaps because the queue manager was shut down using endmqm -i or endmqm -p), the IPC resources used by these applications might not be released.
        If the queue manager ends abnormally (for example, if an operator issues the system kill command), some IPC resources might be left allocated after all queue manager processes have terminated.

    In these cases, the IPC resources are not released back to the system until you restart (strmqm) or delete (dltmqm) the queue manager. End of change

    Start of changeIPC resources allocated by WebSphere MQ are maintained automatically by the allocating queue managers. You are strongly recommended not to perform manual actions on or remove these IPC resources. End of change

    Start of changeHowever, if it is necessary to remove IPC resources owned by mqm, follow these instructions. WebSphere MQ provides a utility to release the residual IPC resources allocated by a queue manager. This utility clears the internal queue manager state at the same time as it removes the corresponding IPC resource. Thus, this utility ensures that the queue manager state and IPC resource allocation are kept in step. To free residual IPC resources, follow these steps:End of change
    Start of changeStart of change

        End the queue manager and all connecting applications.
        Log on as user mqm.
        Type the following:
        On Solaris, HP-UX, and Linux:

        /opt/mqm/bin/amqiclen -x -m QMGR

        On AIX:

        /usr/mqm/bin/amqiclen -x -m QMGR

        This command does not report any status. However, if some WebSphere® MQ-allocated resources could not be freed, the return code is nonzero.
        Explicitly remove any remaining IPC resources that were created by user mqm.

    End of change
    Note: Start of changeIf a non-mqm application attempted to connect to WebSphere MQ before starting any queue managers, there might still be some WebSphere MQ IPC resources remaining even after following the above steps. These remaining resources were not created by user mqm and there is no straightforward way to reliably recognize them. However, these resources are very small and are reused when WebSphere MQ is next restarted.End of change
    0 (0 Ratings)
    [ 641 views ] Leave a Comment

    SSL CipherSpecs supported by IBM WebSphere MQ - Middleware News

    Saturday, August 18, 2012, 11:49 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    The following table lists the CipherSpecs supported by WebSphere MQ. Specify the CipherSpec name in the SSLCIPH property of the SVRCONN channel on the queue manager and in MQEnvironment.SSLCipherSpec

    Table 1. Supported CipherSpecsCipherSpec

    DES_SHA_EXPORT
    DES_SHA_EXPORT1024
    NULL_MD5
    NULL_SHA
    RC2_MD5_EXPORT
    RC4_56_SHA_EXPORT1024
    RC4_MD5_US
    RC4_MD5_EXPORT
    RC4_SHA_US
    TRIPLE_DES_SHA_US
    0 (0 Ratings)
    [ 548 views ] Leave a Comment

    AMQ9213 2009 MQRC_CONNECTION_BROKEN on IBM MQ clients - Middleware News

    Thursday, August 2, 2012, 8:31 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    You have WebSphere MQ clients which connect to several different MQ servers. The MQ clients are quite frequently disconnected with rc=2009, MQRC_CONNECTION_BROKEN. The clients are able to reconnect immediately. The queue managers are running well. You see no problems when issuing 'runmqsc' commands on the server.

    Symptom

    On the MQ server side you see the following message in the queue manager's error log, AMQERR01.LOG:

    AMQ9213: A communications error for TCP/IP occurred.
    EXPLANATION: An unexpected error occurred in communications.
    ACTION: The return code from the TCP/IP(select) [TIMEOUT] 660 seconds call was 11 (X'B'). Record these values and tell the systems administrator.

    Cause

    There was a parameter recently added in your qm.ini file called ClientIdle that was set to 600 secs. This caused the client connections to end after they were idle for the specified period of time + 60 seconds. After the connection is terminated at the server, the next attempt to send a request from the client side results in rc=2009.

    Resolving the problem

    You can either remove the ClientIdle parameter from the Channels stanza of your qm.ini files or you can set it to a value, which is higher than you expect your clients will be idle between calls. 
    The default path for the qm.ini file is /var/mqm/QMGRs//
    3.7 (1 Ratings)
    [ 2007 views ] Leave a Comment

    IBM Leap Second may cause Linux to freeze

    Tuesday, July 24, 2012, 12:01 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    After adding the leap second in Linux on 30 June, 2012, your WebSphere MQ queue manager has many FDC files related to resource issues or constraints and they will commonly report rc=xecP_E_NO_RESOURCE. You may also see your queue manager hang or freeze or there may be high cpu. The FDC's are being generated on a daily basis and may have probes of XY348010 or XC272003 from xcsCreateThread but there could be other FDC's with different probes also.

    Content

    On 30 June, the Network Time Protocol (NTP) daemon scheduled a leap second to occur at midnight, meaning that the final minute of the day was 61 seconds long. We have seen several problems with otherwise unexplainable high CPU usage on Linux systems caused by the leap second at the end of June.

    WebSphere MQ does not directly make calls which experience the problem, but we do use the pthreads library (NPTL), which in turn uses futexes ("fast userspace mutexes"), which can hit this problem. Busy systems running WebSphere MQ and other products are susceptible to this problem. You can read more about the problem at these links:

    Anyone else experiencing high rates of Linux server crashes during a leap second day?

    Leap Seconds in Red Hat Enterprise Linux

    Leap second: Linux can freeze

    This problem is solved by either applying Operating System (Linux) patches, resetting the date or rebooting the system. The resolution is dependent on your level of Linux and your environment. Please consult your Linux provider for details of the solution appropriate for your system.

    As a workaround you can follow these steps

    1. Check the Linux kernel version. In theory only 2.6.22 and newer levels should be affected:
      All: uname -r
    2. Switch to root or log in as root at the console
    3. Check to see if NTP is running:
      RHEL: service ntpd status
      SLES: /etc/init.d/ntp status
    4. If NTP is running, disable it:
      RHEL: service ntpd stop
      SLES: /etc/init.d/ntp stop
    5. Set the system clock to the current time:
      All sntp -P no -r pool.ntp.org
      Or: ntpdate 0.us.pool.ntp.org
    6. If NTP was running, reenable it:
      RHEL: service ntpd start
      SLES: /etc/init.d/ntp start
    0 (0 Ratings)

    Removing IBM DB2 products using the db2_deinstall command (UNIX) - Middleware News

    Tuesday, July 10, 2012, 10:01 AM
    Posted By: Karthick

    This task provides steps for removing DB2 Version 8 products using the db2_deinstall command. The db2_deinstall command removes all DB2 products from your system. If you want to remove a subset of DB2 products, use your operating system's native tools to remove DB2 components, packages, or file sets.

    Prerequisites

    Before you remove DB2 products from your UNIX system:

    • Ensure that you have performed all steps outlined in Removing DB2 on UNIX before removing DB2 products from your UNIX system.
    • You must have root authority to remove DB2 products.
    • You will need your product CD-ROM to use the db2_deinstall command. The db2_deinstall command is found in the root directory on the DB2 Version 8 product CD-ROM.
    Procedure

    To remove DB2 products from your UNIX system:

    1. Log in as user with root authority.
    2. Mount the DB2 Version 8 product CD-ROM.
    3. Run the db2_deinstall -n command from the root directory of your DB2 Version 8 product CD-ROM. The -n parameter makespkgrm non-interactive. The -n parameter is only on System V (Solaris).

      This command will remove all DB2 products from your system.

    There are alternative methods for removing DB2 products from your operating system. You may employ one of these methods if you only want to remove a subset of DB2 products from your system. Alternative methods for removing DB2 products include:

    AIX
    You can use the System Management Interface Tool (SMIT) to remove some or all DB2 products. If you use SMIT to remove DB2, DB2 Version 8 products can be identified by their prefix of db2_08_01. You can also remove all DB2 products from AIX systems using theinstallp command by entering installp -u db2_08_01.
    HP-UX
    You can use the swremove command to remove some or all DB2 products.
    Linux
    You can use the rpm command to remove some or all DB2 products.
    Solaris Operating Environment
    You can remove some or all DB2 products using the pkgrm command.
    0 (0 Ratings)
    [ 642 views ] Leave a Comment

    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)
    [ 739 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)
    [ 1681 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)
    [ 963 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)
    [ 899 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)
    [ 628 views ] Leave a Comment

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

Connect w/ Others

Member of the Month

    • WebSphere z/OS System Administrator
      CSC