chunk_id string | chunk string |
|---|---|
1fd9b9818736e45dae6ec5838df5b461_1 | CVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]
DESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM OS Image for Red Hat Linux Systems 2.0.0.1 and earlier.
IBM OS Image for AIX 2.0.0.1 and earlier.
REMEDIATION/FIXES
The deployed Red Hat Linux-based and AIX virtual machines on IBM PureApplication Systems types are affected. The solution is to apply the following IBM PureApplication System fix to the deployed virtual machines. |
1fd9b9818736e45dae6ec5838df5b461_2 | Java Update for Linux
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_Linux_2++&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_Linux_2++&includeSupersedes=0]
Java Update for AIX
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_AIX_2++&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_AIX_2++&includeSupersedes=0] |
1fd9b9818736e45dae6ec5838df5b461_3 | 1. Import the fix into the Emergency Fix catalogue.
2. For deployed instances, apply this emergency fix on the VM. The IBM Java SDKwill be upgraded to IBM Java JDK 7.0 SR8 FP10 interim fix and IBM Java JDK 6.0 SR16 FP3 interim fix
3. Restart the deployed instance after the fix is applied.
You should verify applying this fix does not cause any compatibility issues. WORKAROUNDS AND MITIGATIONS
None
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
ACKNOWLEDGEMENT
None |
1fd9b9818736e45dae6ec5838df5b461_4 | CHANGE HISTORY
23 July 2015: Original Version Published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
88a19e97c66272260386cc0ed5e8bef0_0 | IBM ITCAM Agent for WebSphere DataPower Applications: 7.1.0-TIV-ITM_WDP-FP0003 - United States DataPower; BN; KBN DOWNLOADABLE FILES
ABSTRACT
This fix resolves the enhancements listed in the "Problems Fixed"
section below.
DOWNLOAD DESCRIPTION
Copyright International Business Machines Corporation 2016.
All rights reserved.
Component: IBM(R) Tivoli(R) Composite Application Manager Agent for WebSphere DataPower Appliance
Version 7.1 Fix Pack 3
Component ID: 5724SOADP
Fix Pack: 3, 7.1.0-TIV-ITM_WDP-FP0003
Date: Revised January 8, 2016
Contents:
1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices |
88a19e97c66272260386cc0ed5e8bef0_1 | 1.0 General description
=======================
This fix resolves the RFEs, APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.6.
2.0 Problems fixed
==================
The following problems are addressed by this fix.
2.1 APARs:
----------
N/A
2.2 Defects
--------------
Defect: 61583
Abstract: Increase java heap size and thread pool size.
Additional Information: In order to support monitoring more DPs per instance, we increased the maximum heap size from 512M to 1024M. And the thread pool size is changed from 5 to 10.
To enable the new maximum heap size, agent need to be restarted. |
88a19e97c66272260386cc0ed5e8bef0_2 | To enable the new thread pool size:
1. Re-config the instances.
2. Modify the agent's config file and restart the agent instances.
--For UNIX/LINUX
Modify the file "bn_<instanceName>.config", change the item "CDP_DP_THREAD_POOL_SIZE" to "10".
--For Windows
Modify the file "KBNENV_<instanceName>", change the item "CDP_DP_THREAD_POOL_SIZE" to "10".
2.3 Enhancements:
-----------------
Enhancement: RFE: 68385
Abstract: AMEX - Additional DataPower monitoring capabilities to monitor new capabilities in V6/V7 of firmware
Additional Information:
Priority 1- Link Aggregation - First available in V7 firmware. This is at the network layer. Can add monitoring for the network connections to ensure there are no failures in link aggregation.
Priority 1- IMS Connect - Can monitor up/down connection monitoring in SNMP files.
Lower priority - On Demand Router - Load balancing for Websphere. Can add monitoring for the network connections and load balancing work its doing. |
88a19e97c66272260386cc0ed5e8bef0_3 | 4 new attribute groups were introduced in FP3.
-IMS_Connect:
IMSConnect, Domain, Requests, Responses, RequestErrors, ResponseErrors
4 queries:
--IMS Connect Status: Use the IMSConnect attributes to obtain information about IMS connect status on the monitored DataPower appliance.
--IMS Connect Requests Top 10: Provides the top 10 requests IMS Connect.
--IMS Connect Responses Top 10: Provides the top 10 responses IMS Connect.
--IMS Connect Request Errors Top 10: Provides the top 10 request errors IMS Connect.
--IMS Connect Response Errors Top 10: Provides the the top 10 response errors IMS Connect. |
88a19e97c66272260386cc0ed5e8bef0_4 | -Link_Aggregation:
Index, Name, MgmtName, MTU, Mode, Status, Primary, Active, LACPHashPolicy, LACPDURate, LACPSelectionPolicy, LACPAggregatorID, LACPNumPorts, LACPActorKey, LACPPartnerKey, LACPPartnerMAC, MIIStatus
3 queries:
--Link Aggregation Status: Use the Link Aggregation Status attributes to obtain information about Link Aggregation Status on the monitored DataPower appliance.
--Link Aggregation Status No-link: Provides all No-link status for Link Aggregation.
--Link Aggregation MIIStatus No-link: Provides all No-link MIIStatus for Link Aggregation.
-Link_Aggregation_Member_Status:
AggregateIndex, AggregateName, MgmtName, MemberIndex, MemberName, AggregatorID
1 query:
--Link Aggregation Member Status: Use the Link Aggregation Member Status attributes to obtain information about Link Aggregation Member Status on the monitored DataPower appliance. |
88a19e97c66272260386cc0ed5e8bef0_5 | -Load_Balancer:
Group, Domain, Server, Port, Health, Weight, AdminState
3 queries:
--Load Balancer Status: Use the Load Balancer Status attributes to obtain information about Load Balancer status on the monitored DataPower appliance.
--Load Balancer Groups Down: Provides all Down status groups for Load Balancer.
--Load Balancer Groups Softdown: Provides all Softdown status groups for Load Balancer.
Enhancement: (internal) Remove the UE dependance
Abstract: Remove the UE dependance
Additional Information: Details as below:
ax is upgraded to 06.30.04.00
gs is upgraded to 08.00.50.20
jr is upgraded to 07.07.00.00
ui is upgraded to 06.30.04.00
2.4 Superseded fixes
-------------------------
None.
2.5 APARs and defects included from superseded fixes
----------------------------------------------------
None. |
88a19e97c66272260386cc0ed5e8bef0_6 | 3.0 Architecture and prerequisites
=================================
Supported operating systems are shown in the system requirements reports
for the DataPower agent. You can access these reports here:
- Prerequisites topic in Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/prerequisites/apps721_systemreqs.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/prerequisites/apps721_systemreqs.html]
- Software Product Compatibility Reports (SPCR)
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]
3.1 Prerequisites for this fix
--------------------------------
There is no prerequisite level for this fix.
Because this fix is cumulative, it can be installed on any fix level
for the version, release, and modification level above the prerequisite. |
88a19e97c66272260386cc0ed5e8bef0_7 | 4.0 Image directory contents
============================
Physical Part Number: ITCAM Apps Agent for WebSphere DataPower Appliance CBNR3ML
Electronic Part Number: ITCAM Apps Agent for WebSphere DataPower Appliance CN8KBML
5.0 Installation instructions
=============================
When this fix pack image is downloaded from the IBM Software Support website,
these rules apply:
* You can install the fix pack only locally on a system that hosts a
licensed copy of IBM Tivoli Monitoring for Databases already. Similar to other
upgrade software, you can install the fix pack image locally on a
computer where the product software is not already installed.
* You can populate agents to the depot.
* You can deploy agents remotely to existing or new installations. |
88a19e97c66272260386cc0ed5e8bef0_8 | When this fix pack image is downloaded from Passport Advantage, these rules
apply:
* You can install the fix pack locally on a system that hosts a
licensed copy of IBM Tivoli Monitoring for Databases already.
* You can install the fix pack locally on a system that does not host
a licensed copy of IBM Tivoli Monitoring for Databases already.
* You can populate agents to the depot.
* You can deploy agents remotely to existing or new installations.
5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Upgrade prerequisites
for this fix' must be installed when upgrading.
- For the purpose of this README, the <CANDLEHOME> symbol is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\ibm\itm'
on Windows systems. |
88a19e97c66272260386cc0ed5e8bef0_9 | - If you customize the Extended Monitoring Agent for WebSphere DataPower Appliance
bn.ini file on a UNIX system, back up this file before installing the fix.
After this fix is installed, edit the latest bn.ini file and merge
your modifications into this bn.ini file.
5.2 Local agent install and update (including silent installation)
--------------------------------------------------------------
1. Transfer the appropriate archive file to a
temporary directory on the system that contains the agent code to be
updated. For the purpose of this README, the <TEMP> symbol represents
the fully qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.
2. Expand the archive file by using the tar command on UNIX systems or
an unzip utility on Windows systems. This expansion creates a directory
structure that contains fixes for all supported platforms. |
88a19e97c66272260386cc0ed5e8bef0_10 | 3. Use the procedures in the "IBM Tivoli Monitoring, Version 6.3 FP3
Installation and Setup Guide" to install the agent.
4. Use the procedures in the specific monitoring agent user's
guide to complete the installation and configuration.
5.3 Remote agent update and installation
----------------------------------------
1. Make sure that all potential targets of the remote deployment are
running version 6.2.3 Fix Pack 4 or later of the OS monitoring
agent.
2. Transfer the appropriate archive file to
a temporary directory on the Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
<TEMP> symbol represents the fully qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.
3. Expand the archive file by using the tar command on UNIX systems or an
unzip utility on Windows systems. This expansion creates a directory structure
that contains fixes for all supported operating systems. |
88a19e97c66272260386cc0ed5e8bef0_11 | 4. To add the fix pack bundles to the remote deployment depot, use the
tacmd addBundles command found in $CANDLEHOME/bin on UNIX systems
or in %CANDLE_HOME%\bin on Windows systems. For more information
about the tacmd addBundles command, see the "IBM Tivoli
Monitoring Command Reference."
On a UNIX system: if the fix was expanded to
<TEMP>/<PARTNUMBER>:
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/<PARTNUMBER>/WINDOWS/Deploy -t bn -f
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/<PARTNUMBER>/unix -t bn -f
where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, for example, bn
represents the Extended Monitoring Agent for WebSphere DataPower Appliance
-f shows that the actions are complete and confirmation is not requested |
88a19e97c66272260386cc0ed5e8bef0_12 | On a Windows system: if the fix was expanded to
<TEMP>/<PARTNUMBER>:
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\<PARTNUMBER>\WINDOWS\Deploy -t bn -f
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\<PARTNUMBER>\unix -t bn -f
where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, for example, bn
represents the Extended Monitoring Agent for WebSphere DataPower Appliance
-f shows that the actions are complete and confirmation is not requested
5. To login to the Tivoli Enterprise Monitoring server and deploy
the fix to the appropriate nodes where the agent is running, use
the following tacmd commands. For more information about the
tacmd login and updateAgent commands, see the "IBM Tivoli
Monitoring Command Reference."
On a UNIX system:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems |
88a19e97c66272260386cc0ed5e8bef0_13 | The output shows the managed system name for the OS agent on the
remote system to be installed/update. Use this value as the target of the
tacmd addsystem/updateAgent command.
> $CANDLEHOME/bin/tacmd addsystem -t bn
-n <Managed system name>
-p <Configration Info>
> $CANDLEHOME/bin/tacmd updateAgent -t bn
-n <Managed system name>
-v 071003000
On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%/bin/tacmd listSystems
The output shows the managed system name for the OS agent on the
remote system to be installed/updated. Use this value as the target of the
tacmd addsystem/updateAgent command.
> $CANDLEHOME%\bin\tacmd addsystem -t BN
-n <Managed system name>
-p <Configration Info> |
88a19e97c66272260386cc0ed5e8bef0_14 | > %CANDLE_HOME%\bin\tacmd updateAgent -t BN
-n <Managed system name>
-v 071003000
Note:
- The component (-t) for the updateAgent command is specified as
two characters (bn), not three characters (kbn).
- The node (-n) for the updateAgent command is the managed system
name of the operating system (OS) agent to be updated. The
target node for an updateAgent command is always an OS agent.
- The component (-p) for the addsystem command is for agent's configuration info.
Here is an example:
INSTANCE="value"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_PORT="162"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_SECURITY_LEVEL="authPriv"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_USER_NAME="admin"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_AUTH_PROTOCOL="SHA"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_AUTH_PASSWORD="value"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_PRIV_PROTOCOL="DES"
KQZ_SNMPEVENT.KQZ_SNMPEVENT_PRIV_PASSWORD="value"
DPS:<Managed_System_Name>.SOAP_HOST="value"
DPS:<Managed_System_Name>.DP_PORT="5550"
DPS:<Managed_System_Name>.DP_UID="admin" |
88a19e97c66272260386cc0ed5e8bef0_15 | DPS:<Managed_System_Name>.DP_PASSWORD="value"
DPS:<Managed_System_Name>.KBN_LOG_FILE="value"
DPC:<Managed_System_Name>.SNMP_VERSION="snmpV2"
DPC:<Managed_System_Name>.SNMP_HOST="value"
DPC:<Managed_System_Name>.SNMP_PORT="161"
DPC:<Managed_System_Name>.SNMP_COMMUNITY="public" |
88a19e97c66272260386cc0ed5e8bef0_16 | - The following error might occur with the updateAgent command on
Linux and UNIX endpoints; however, the agent is successfully
updated. This error does not occur on Windows endpoints.
KUICUA011I: Updating the bn agents.
KUICUA015E: The updateAgent command did not complete because an
error occurred. Refer to the following error
returned from the server:
The monitoring server encountered an error while updating the
managed system type.
The kuiras1.log file might provide more information about
this error. If you require further assistance to resolve the
error, contact IBM Software Support.
A timeout occurred while waiting for an agent task to complete on
{node name}.
The agent task did not complete within the configured
time out period.
Verify that the target system is online. Increase the
time out value and try the operation again. |
88a19e97c66272260386cc0ed5e8bef0_17 | 5.4 Agent support update
------------------------
Fix 7.1.0-TIV-ITM_WDP-FP0003 included changes to the agent
support files that must be installed. If you installed these updates already, there are no additional installation
steps. Otherwise, use the following steps to update the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or
Tivoli Enterprise Portal Desktop.
1. Transfer the appropriate archive file
to the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli
Enterprise Portal Servers, or Tivoli Enterprise Portal desktops.
2. Expand the archive file by using the tar command on UNIX systems or an
unzip utility on Windows systems.
3. Use the procedures in the "IBM Tivoli Monitoring, Version 6.3 FP3
Installation and Setup Guide."
4. Use the procedures in the specific monitoring agent user's
guide to complete the installation and configuration. |
88a19e97c66272260386cc0ed5e8bef0_18 | 5. If the Tivoli Enterprise Monitoring Server that is updated is remote (not a
Hub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise
Monitoring Server.
6.0 Additional installation information
========================
6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.
6.2 Additional information on new configuration item "KBN_SOMA_PROTOCOL"
------------------------------------------------------------------------
A new configuration item "KBN_SOMA_PROTOCOL" is introduced to support TLS.
The value should be SSL/TLSv1/TLSv1.1/TLSv1.2. The default value is "TLSv1".
If you want to support TLSv1.1/TLSv1.2, please change it manually.
1. For Windows platform:
The new item "KBN_SOMA_PROTOCOL" is in KBNENV and KBNENV_<instanceName>. |
88a19e97c66272260386cc0ed5e8bef0_19 | a. Agent instance must be restarted to enable the new configuration change.
b. The vaule of "KBN_SOMA_PROTOCOL" in KBNENV_<instanceName> will be updated to
the same vaule of "KBN_SOMA_PROTOCOL" in KBNENV while the instance is re-configured.
2. For Linux/Unix platform:
The new items "KBN_SOMA_PROTOCOL" is in bn.ini and bn_<instanceName>.config.
a. Agent instance must be restarted to enable the new configuration change.
b. The vaule of "KBN_SOMA_PROTOCOL" in bn_<instanceName>.config will be updated to
the same vaule of "KBN_SOMA_PROTOCOL" in bn.ini while the instance is re-configured.
6.3 Verifying the update
----------------------------
1. To verify that the agent was updated correctly, use the tacmd command
to view the current version of the agent after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server before viewing the agent version. |
88a19e97c66272260386cc0ed5e8bef0_20 | For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory, the default location is '/opt/IBM/ITM'.
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t or
On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems -t bn
Note: The component (-t) for the tacmd listSystems command is
specified as two characters (bn), not three characters (kbn).
When the agent update is successful, the agent version is:
07.10.03.00
After the agent is restarted, you can also use the GUI to verify
that the agent was successfully updated.
For the agent on Windows systems, the version number is
07.10.03.00.
For the agent on UNIX systems, the version number is
07.10.03.00. |
88a19e97c66272260386cc0ed5e8bef0_21 | 2. To verify that the agent support files were updated correctly, use the
kincinfo command on Windows systems or the cinfo command on
Linux or UNIX systems. The sample output below shows the versions
of the Tivoli Enterprise Portal Server, Tivoli Enterprise
Monitoring Server, or Tivoli Enterprise Portal Desktop systems
after this fix has been successfully applied.
Note: The date shown for the build might not be accurate. This
is a known problem.
On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:
./cinfo -i
*********** Fri Mar 18 13:23:02 CST 2011 ******************
User: root Groups: root bin daemon sys adm disk wheel
Host name : myaixsys Installer Lvl:06.30.04.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
Monitoring Agent for WebSphere DataPower Appliance update: |
88a19e97c66272260386cc0ed5e8bef0_22 | bn ITCAM Agent for WebSphere DataPower Appliance
lx8266 Version: 07.10.03.00
.
.
.
Tivoli Enterprise Monitoring Server update:
bn ITCAM Agent for WebSphere DataPower Appliance
tms Version: 07.10.03.00
.
.
.
On Windows systems:
---------------------
To validate that all components have been installed, run the
following command:
For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i
kincinfo output:
*********** Wednesday, January 8, 2014 3:46:34 PM ***********
User : Administrator Group : NA
Host Name : IBM-8B96EE78239 Installer : Ver: 063004000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
.
.
.
[ Tivoli Enterprise Monitoring Server |
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal Desktop] update:
BN DataPower Agent Support
WINNT Version: 07.10.03.00 Build:
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal
Desktop update: |
88a19e97c66272260386cc0ed5e8bef0_23 | BN DataPower Agent Support
WINNT Version: 07.10.03.00 Build:
ITCAM Agent for WebSphere DataPower Appliance update:
BN ITCAM Agent for WebSphere DataPower Appliance
WINNT Version: 07.10.03.00 Build:
Note:
- The date of the build that is shown might not be accurate. This
problem is known and is being addressed.
- The kincinfo and cinfo command output examples in the sections
that follow show all components that you can update. If you install only
some of these components then only the components that you install are
shown in the output of these commands.
7.0 Known problems and workarounds
==================================
None.
8.0 Additional product information
=================================
None. |
88a19e97c66272260386cc0ed5e8bef0_24 | 9.0 Notices
===========
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for information
on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to: |
88a19e97c66272260386cc0ed5e8bef0_25 | IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you. |
88a19e97c66272260386cc0ed5e8bef0_26 | Trademarks and service marks
------------------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].
Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.
Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both. |
88a19e97c66272260386cc0ed5e8bef0_27 | Other company, product, or service names may be trademarks or service
marks of others.
DOWNLOAD PACKAGE
HOW CRITICAL IS THIS FIX?
RFE:68385
PROBLEMS SOLVED
Introduce new attribute groups:IMS_Connect, Link_Aggregation, Link_Aggregation_Member_Status and Load_Balancer.
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.1.0.0-TIV-ITM_WDP-FP0003 8 Jan 2016 English 1717046972 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Applications&fixids=7.1.0.0-TIV-ITM_WDP-FP0003&source=SAR] [ ] |
3f22d47806b295a6df851a2bdb3ce3d1_0 | IBM Developer for z Systems and Rational Developer for z Systems Backward/Forward compatibility - United States RDz; compatible; backward; forward; IDz; Debug Tool: Debugger TECHNOTE (FAQ)
QUESTION
What levels of the IBM Developer for z Systems and Rational Developer for z Systems host and client are compatible?
ANSWER
Client/Server Compatibility
In general, IBM Developer for z Systems, Rational Developer for z Systems and Rational Developer for System z follow a two level backward and forward compatibility tolerance for basic Client /Server functionality.
IBM Developer for z Systems v14.1.x host/client is compatible with IBM Developer for z Systems v14.1.x client/host, IBM Developer for z Systems v14.0.x client/host and Rational Developer for z Systems v9.5.x client/host. |
3f22d47806b295a6df851a2bdb3ce3d1_1 | IBM Developer for z Systems v14.0.x host/client is compatible with IBM Developer for z Systems v14.1.x client/host, IBM Developer for z Systems v14.0.x client/host, Rational Developer for z Systems v9.5.x client/host and Rational Developer for System z v9.1.x client/host.
Rational Developer for z Systems v9.5.x host/client is compatible with IBM Developer for z Systems v14.1.x client/host, IBM Developer for z Systems v14.0.x client/host, Rational Developer for z Systems v9.5.x client/host and Rational Developer for System z v9.1.x, and v9.0.x client/host.
Rational Developer for System z v9.1.x host/client is compatible with IBM Developer for z Systems v14.0.x client/host, Rational Developer for z Systems v9.5.x client/host and Rational Developer for System z v9.1, v9.0.x, and v8.5.x client/host.
Rational Developer for System z v9.0.x host/client is compatible with versions v9.5.x, v9.1.x, v9.0.x, v8.5.x and v8.0.x client/host. |
3f22d47806b295a6df851a2bdb3ce3d1_2 | Rational Developer for System z v8.5.x host/client is compatible with versions v9.1, v9.0, v8.5, v8.0.x, and v7.6.x client/host.
Basic Client/Server functionality includes:
• Connecting to a z/OS System
• Allocating z/OS Data sets
• Creating a z/OS Project
• Working with z/OS COBOL & Pl/I remote assets – edit, syntax check, submit, execute, debug and view the output
• Basic CARMA functionality
• Compatibility between service levels within a release is also supported (for example, using the v9.5 client to access a v9.5.1 server).
As an example, if you upgrade your Developer for z Systems host to 14.0.x, client versions v9.1.x, v9.5.x, v14.0 and v14.1.x are compatible with the 14.0.x server.
Likewise, if you upgrade your Developer for z Systems client to 14.0.x, server versions v9.1.x, v9.5.x, v14.0.x and v14.1.x are compatible with the 14.0.x client.
Note: Server enhancements that are client-dependent are not available to developers using earlier versions of the client. |
3f22d47806b295a6df851a2bdb3ce3d1_3 | Client enhancements that are server-dependent are not available to developers accessing earlier versions of the server.
For Debugger, |
3f22d47806b295a6df851a2bdb3ce3d1_4 | [/support/docview.wss?uid=swg21568844&aid=1]
Developer for System z v9.0.1.x (host)
Developer for System z v9.1.x (host)
Developer for System z v9.5.x (host)
Developer for z Systems v14.0.x (host)
Developer for z Systems v14.1.x (host)
Debug for z Systems v14.0.x (host)
Debug for z Systems v14.1.x (host) Debug Tool v12 Debug Tool v13
Developer for System z v9.0.1.x (Client) X [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] X X
Developer for System z v9.1.x (Client) X X X X X X X X X
Developer for System z v9.5.x (Client) X X X X X X X [/support/docview.wss?uid=swg21568844&aid=1] X
Developer for System z v14.0.x (Client) X(1) X(1) X X X X X X X |
3f22d47806b295a6df851a2bdb3ce3d1_5 | Developer for System z v14.1.x (Client) X(1) X(1) X X X X X X X * (1) Launch configurations and JCL Generation not supported for these host versions.
*
*
*
*
*
* Workspace Data Compatibility
*
*
*
*
*
*
* |
8249f2f61257a69c8d381105e427102a_0 | IBM Reducing the size of Decision Warehouse trace when running scenario suites - United States TECHNOTE (FAQ)
QUESTION
When running a Decision Validation Service scenario suite in Rule Team Server can the optional trace be filtered to reduce its size ?
ANSWER
It is possible to customize the Decision Warehouse (DW) trace that is used by the Scenario Suite Provider (SSP) when a Decision Validation Service (DVS) scenario suite is executed in Rule Team Server. The customization can filter out information that is not necessary to keep in the DW. A sample implementation is provided that removes information about all the rules that are not fired, which helps keep the size of the trace small when there is a large number of rules in the ruleset and typically a much smaller number of rules actually fire. Also, only the DW persisted trace is smaller, the original larger trace is still used by DVS to perform the tests involved in the scenario suite.
Instructions: |
8249f2f61257a69c8d381105e427102a_1 | 1. Unjar the attached jrules-ssptrace-src.jar to a local directory
2. Edit the file ./jrules-ssptrace/build.xml and modify the properties to reflect your environment setup ( in particular the jrules.home directory path, the sspInput and sspOutput file paths )
3. Using a command line from the directory ./jrules-ssptrace execute: ant repackage-ssp
4. Deploy the customized SSP (available as the sspOutput file path)
jrules-ssptrace-src.jar [/support/docview.wss?uid=swg21438208&aid=2] [/support/docview.wss?uid=swg21438208&aid=1]
Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.5, 8.0.1, 8.0, 7.5 |
b038e4830839292ea8625ee9881a251b_0 | IBM Security Bulletin: Vulnerabilities in OpenSSL affect IBM MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178) - United States SECURITY BULLETIN
SUMMARY
OpenSSL vulnerabilities were disclosed on September 22 and 26, 2016 by the OpenSSL Project. OpenSSL is used by IBM MQ Advanced Message Security on the IBM i platform only. IBM MQ Advanced Message Security has addressed the applicable CVEs. |
b038e4830839292ea8625ee9881a251b_1 | VULNERABILITY DETAILS
CVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]
DESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the incorrect use of pointer arithmetic for heap-buffer boundary checks. By leveraging unexpected malloc behavior, a remote attacker could exploit this vulnerability to trigger an integer overflow and cause the application to crash.
CVSS Base Score: 5.9
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) |
b038e4830839292ea8625ee9881a251b_2 | CVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]
DESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DSA implementation that allows the following of a non-constant time codepath for certain operations. An attacker could exploit this vulnerability using a cache-timing attack to recover the private DSA key.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ V8
Maintenance versions 8.0.0.0 through 8.0.0.5 are affected.
IBM MQ V9
9.0.0.0 only
REMEDIATION/FIXES
IBM MQ V8
Apply fixpack 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100]
IBM MQ V9 |
b038e4830839292ea8625ee9881a251b_3 | Apply fixpack 9.0.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048059]
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
13 March 2017: Original version published
24 May 2017: Details for 9.0.0.1 added
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
b038e4830839292ea8625ee9881a251b_4 | DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22000474] |
f6bb73edb8884456921278ff7937276f_0 | IBM Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917) - United States SECURITY BULLETIN
SUMMARY
IBM Dojo Toolkit is vulnerable to cross-site scripting and affects IBM Image Construction and Composition Tool.
VULNERABILITY DETAILS
CVEID: CVE-2014-8917 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8917]
DESCRIPTION: IBM Dojo Toolkit is vulnerable to cross-site scripting, caused by improper validation of user-supplied input.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99303 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99303] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM Image Construction and Composition Tool v2.2.1.3
IBM Image Construction and Composition Tool v2.3.1.0
IBM Image Construction and Composition Tool v2.3.2.0 |
f6bb73edb8884456921278ff7937276f_1 | REMEDIATION/FIXES
The solution is to apply the following IBM Image Construction and Composition Tool version fixes.
Upgrade the IBM Image Construction and Composition Tool to the following fix levels or higher:
For IBM Image Construction and Composition Tool v2.2.1.3 *
*
*
*
* http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=1.1.0.5&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.2.1.3-28&includeSupersedes=0
For IBM Image Construction and Composition Tool v2.3.1.0 *
*
*
*
* http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.1.0-38&includeSupersedes=0 |
f6bb73edb8884456921278ff7937276f_2 | For IBM Image Construction and Composition Tool v2.3.2.0 *
*
*
* http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.1.0.0&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.2.0-12&includeSupersedes=0
WORKAROUNDS AND MITIGATIONS
None
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
REFERENCES
Complete CVSS v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
ACKNOWLEDGEMENT
None
CHANGE HISTORY
17 June 2015: Original version published |
f6bb73edb8884456921278ff7937276f_3 | *The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
b84960ea39a02426d29343304a1e3508_0 | IBM Security Bulletin: A security vulnerability has been identified in IBM Tivoli Network Manager IP Edition shipped with WebSphere Application Server (CVE-2017-1194) - United States SECURITY BULLETIN
SUMMARY
WebSphere Application Server is shipped with IBM Tivoli Network Manager IP Edition. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin.
VULNERABILITY DETAILS
Please consult the security bulletin Cross-site request forgery in WebSphere Application Server (CVE-2017-1194) [http://www-01.ibm.com/support/docview.wss?uid=swg22001226] for vulnerability details and information about fixes.
AFFECTED PRODUCTS AND VERSIONS
IBM Tivoli Network Manager 3.9, 4.1, 4.1.1 and 4.2
REMEDIATION/FIXES
Refer to the following security bulletins for vulnerability details and information about fixes addressed by WebSphere Application Server which is shipped with Network Manager IP Edition. |
b84960ea39a02426d29343304a1e3508_1 | Principal Product and Version(s) Affected Supporting Product and Version IBM Tivoli Network Manager 3.9 Fixpack 1 - Fixpack 5 Bundled the TIP version 2.1.0.x, which bundles IBM WebSphere version 7.0.0.x. IBM Tivoli Network Manager 4.1 Bundled the TIP version 2.2.0.x, which bundles IBM WebSphere version 7.0.0.x. IBM Tivoli Network Manager 4.1.1 FixPack 1 - Fixpack 2 Bundled the TIP version 2.2.0.x, which bundles IBM WebSphere version 7.0.0.x. IBM Tivoli Network Manager 4.2.0 - Fix Pack 1 - Fixpack 3. IBM Tivoli Network Manager 4.2 requires to install IBM Websphere Application Server Version 8.5.5.5 or later version separately. Users are recommended to apply IBM WebSphere version 8.5.5.5 Security Interim Fixes..
WORKAROUNDS AND MITIGATIONS
None
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. |
b84960ea39a02426d29343304a1e3508_2 | REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]
RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
4 May 2017: Original Version Published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
b84960ea39a02426d29343304a1e3508_3 | DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
b011e8bd52483c23d4ec933a077b799e_0 | IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805) - United States SECURITY BULLETIN
SUMMARY
IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS). |
b011e8bd52483c23d4ec933a077b799e_1 | VULNERABILITY DETAILS
CVEID:CVE-2017-7805 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7805]
DESCRIPTION:Network Security Services could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free in TLS 1.2 generating handshake hashes. By persuading a victim to visit a specially-crafted website, a remote attacker could exploit this vulnerability using unknown attack vectors to execute arbitrary code on the vulnerable system or cause a denial of service.
CVSS Base Score: 8.8
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/132749 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132749]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ Appliance 8.0
Maintenance levels between 8.0.0.0 and 8.0.0.7
IBM MQ Appliance 9.0.x Continuous Delivery (CD) Release |
b011e8bd52483c23d4ec933a077b799e_2 | Continuous delivery updates between 9.0.1 and 9.0.3
REMEDIATION/FIXES
IBM MQ Appliance 8.0
Apply fixpack 8.0.0.8 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&function=textSearch&text=8.0.0.8]
IBM MQ Appliance 9.0.x Continuous Delivery (CD) Release
Apply Continuous Delivery Release 9.0.4 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&function=textSearch&text=9.0.4]
WORKAROUNDS AND MITIGATIONS
None
GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.
REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] |
b011e8bd52483c23d4ec933a077b799e_3 | RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]
CHANGE HISTORY
12 December 2017 Original version published
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. |
b011e8bd52483c23d4ec933a077b799e_4 | DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. |
58708d3565b29ca0dffa3503cef07c40_0 | IBM Installing IBM Tivoli Directory Server Version 6.3 on RHEL 6 operating system - United States Tivoli Directory Server 6.3 on RHEL6; installing Tivoli Directory Server 6.3 on RHEL6 TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
This document describes the points that you must consider when installing IBM Tivoli Directory Server Version 6.3 on Red Hat Enterprise Linux 6 (RHEL 6) operating system.
RESOLVING THE PROBLEM
For a comprehensive list of the current recommended fix levels for IBM Tivoli Directory Server, see http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778 [http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778].
Use this document to find the following information:
* Prerequisites for installing Tivoli Directory Server 6.3 on RHEL 6 systems.
* Instructions to install Tivoli Directory Server 6.3 and upgrade to Tivoli Directory Server 6.3 fix pack 10.
* Known issues and their work around. |
58708d3565b29ca0dffa3503cef07c40_1 | * #RHEL6PREREQPREREQUISITE FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 ON RED HAT ENTERPRISE LINUX 6 (RHEL 6) OPERATING SYSTEM
* #INSTALLUPGRADEFP10INSTRUCTIONS FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 AND UPGRADING TO TIVOLI DIRECTORY SERVER VERSION 6.3 FIX PACK (FP) 10
* #KIRHEL6KNOWN ISSUES AND THEIR WORK AROUND
PREREQUISITE FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 ON RED HAT ENTERPRISE LINUX 6 (RHEL 6) OPERATING SYSTEM |
58708d3565b29ca0dffa3503cef07c40_2 | * The Korn shell (ksh) is required on Linux operating systems.
* Before installing Tivoli Directory Server Version 6.3 client or server packages on RHEL 6, the following prerequisite packages must be present on the RHEL 6 system.
You must upgrade the listed packages to the latest patch levels. See the Red Hat support site at http://rhn.redhat.com [http://rhn.redhat.com] for patches for Red Hat Enterprise Linux. You must install the following packages that are included with the Linux operating system. Red Hat Enterprise Linux (RHEL) Server 6 on x86-32 (x86/IA32) platform Red Hat Enterprise Linux (RHEL) Server 6 on x86-64 (AMD64/EM64T) platform Red Hat Enterprise Linux (RHEL) Server 6 on System z Red Hat Enterprise Linux (RHEL) Server 6 on POWER System (System i and System p) * compat-libstdc++-33 and its dependencies
* gcc
* gcc-c++
* glibc
* glibc-common
* glibc-devel
* glibc-headers
* libgcc |
58708d3565b29ca0dffa3503cef07c40_3 | * compat-libstdc++-33 and its dependencies
* gcc
* gcc-c++
* glibc
* glibc-common
* glibc-devel
* glibc-headers
* libgcc
* compat-libstdc++-33 (install both 32 and 64-bit versions) and the dependencies
* gcc
* gcc-c++
* glibc
* glibc-common
* glibc-devel
* glibc-headers
* libgcc
* compat-libstdc++-33 and its dependencies
* gcc
* gcc-c++
* glibc
* glibc-common
* glibc-devel
* glibc-headers
* libgcc
* On RHEL 6, DB2 V9.7 FP4 is required for Tivoli Directory Server Version 6.3. To install DB2 V9.7 FP4 on RHEL6, the required minimum level of compat-libstdc++ is 1.3.1. On System z Linux, you must install the compat-libstdc++-33-3.2.3-47.3.s390x.rpm or higher version package before you install DB2. |
58708d3565b29ca0dffa3503cef07c40_4 | See the following DB2 websites for information about the DB2 prerequisites on RHEL 6. * https://www-304.ibm.com/support/docview.wss?uid=swg24031170 [https://www-304.ibm.com/support/docview.wss?uid=swg24031170]
* https://www.ibm.com/developerworks/wikis/display/im/Red+Hat+Enterprise+Linux+%28RHEL%29+6+-+DB2+9.7 [https://www.ibm.com/developerworks/wikis/display/im/Red+Hat+Enterprise+Linux+%28RHEL%29+6+-+DB2+9.7] |
58708d3565b29ca0dffa3503cef07c40_5 | #ibm-contentBack to top
INSTRUCTIONS FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 AND UPGRADING TO TIVOLI DIRECTORY SERVER VERSION 6.3 FIX PACK (FP) 10 |
58708d3565b29ca0dffa3503cef07c40_6 | On RHEL 6, you can install Tivoli Directory Server 6.3 using native operating system utilities only. To use Tivoli Directory Server 6.3 on RHEL 6, you must perform the following steps: 1. Install Tivoli Directory Server 6.3 General Availability (GA) version using native operating system utilities.
2. Upgrade DB2 V9.7 FP2 (provided with Tivoli Directory Server 6.3 GA ) to DB2 V9.7 FP4 level.
3. If you are using SSL or TLS enabled versions of TDS 6.3.0.10, you must install GSKit 8.0.14.14 or higher fix pack level. |
58708d3565b29ca0dffa3503cef07c40_7 | 4. Upgrade Tivoli Directory Server 6.3 GA to Tivoli Directory Server 6.3 FP 10 or higher fix pack level. See the following website for more information. * See the readme file for the required fix pack level at http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Directory+Server&release=All&platform=All&function=all [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Directory+Server&release=All&platform=All&function=all].
* See http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778 [http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778] to obtain the latest fixes for IBM Tivoli Directory Server. |
58708d3565b29ca0dffa3503cef07c40_8 | Notes: * Tivoli Directory Server 6.3 installation using GUI installation program is not supported on RHEL 6.
* Tivoli Directory Server 6.3 White pages installation using GUI installation program is not supported.
* If you encounter an issue with the graphical user interface (GUI) tools such as the Instance Administration tool (idsxinst) and the Configuration tool (idsxcfg), use the appropriate command-line tool to complete the task.
Supported Tivoli Directory Server Version 6.3 fix pack 10 components on RHEL 6 operating system: Operating system Supported 64-bit Directory server components Supported 32-bit Directory server components Supported DB2 levels Supported co-requisite software Red Hat Enterprise Linux (RHEL) Server 6 on x86-64 (AMD64/EM64T) Client
Server
Proxy server
Web Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14*
* WebSphere Application Server 7.0.0.15 or higher fix pack version
* Java 1.6 SR9 |
58708d3565b29ca0dffa3503cef07c40_9 | Red Hat Enterprise Linux (RHEL) Server 6 on x86-32 (x86/IA32) Not applicable Client
Server
Proxy server
Web Administration tool V9.7 WSE FP4 * GSKit 8.0.14.14*
* WebSphere Application Server 7.0.0.15 or higher fix pack version
* Java 1.6 SR9
Red Hat Enterprise Linux (RHEL) Server 6 on System z Client
Server
Proxy server
Web Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14*
* WebSphere Application Server 7.0.0.15 or higher fix pack version
* Java 1.6 SR9
Red Hat Enterprise Linux (RHEL) Server 6 on POWER System (System i and System p) Client
Server
Proxy server
Web Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14*
* WebSphere Application Server 7.0.0.15 or higher fix pack version
* Java 1.6 SR9
Red Hat Enterprise Linux (RHEL) Desktop 6 on x86-64 Client Not applicable Not applicable * GSKit 8.0.14.14*
* Java 1.6 SR9
Red Hat Enterprise Linux (RHEL) Desktop 6 on x86-32 Not applicable Client Not applicable * GSKit 8.0.14.14*
* Java 1.6 SR9 |
58708d3565b29ca0dffa3503cef07c40_10 | *Note: You must upgrade the GSKit version to 8.0.14.22 or higher fix pack levels. The upgrade is required because of a known SSL/TLS related memory leak issue in GSKit version earlier than 8.0.14.22, which is fixed in GSKit 8.0.14.22 and higher fix pack levels.
Supported browsers for Web Administration tool: * Mozilla Firefox 3.5.10
#ibm-contentBack to top
KNOWN ISSUES AND THEIR WORK AROUND |
58708d3565b29ca0dffa3503cef07c40_11 | On RHEL6 systems, the following issues were found. The tech notes with identified issues and their work around are listed. * APARs: * The idsbulkload command fails on RHEL 6 with GLPBLK108E error message. See the APAR IO15265 description at http://www-01.ibm.com/support/docview.wss?uid=swg1IO15265 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO15265] for more information.
* A return code, rc=-1, operations error is returned even after the ibmdirctl command starts ibmslapd on RHEL 6. See the APAR IO15910 description at http://www-01.ibm.com/support/docview.wss?uid=swg1IO15910 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO15910] for more information.
* The Instance Administration tool (idsxinst) might throw an error when setting the LOCPATH environment variable with an invalid value. See the APAR IO16724 description at http://www-01.ibm.com/support/docview.wss?uid=swg1IO16724 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO16724] for more information. |
58708d3565b29ca0dffa3503cef07c40_12 | * Tech notes: * Starting the ibmslapd or ibmdiradm process automatically using the inittab method on RHEL 6 does not work. See the tech note at http://www-01.ibm.com/support/docview.wss?uid=swg21588061 [http://www-01.ibm.com/support/docview.wss?uid=swg21588061] for more information.
* Before installing DB2 V9.7, install compat-libstdc++ package on the system, if not present. If the required compat-libstdc++ package is not found on the system, DB2 exits installation with following error messages. * WARNING:
*
* Required minimum level of libstdc++ is 1.3.1
*
* Actual version of the library file detected : CXXABI_1.3
*
* Check the following web site for the up-to-date system requirements of IBM DB2 9.7
*
* http://www.ibm.com/software/data/db2/udb/sysreqs.html [http://www.ibm.com/software/data/db2/udb/sysreqs.html]
*
* http://www.software.ibm.com/data/db2/linux/validate [http://www.software.ibm.com/data/db2/linux/validate] |
58708d3565b29ca0dffa3503cef07c40_13 | *
* Aborting the current installation ...
*
* Run installation with the option "-f sysreq" parameter to force the installation |
58708d3565b29ca0dffa3503cef07c40_14 | #ibm-contentBack to top |
72aa4e086fca6870bff7a24a42e76f4f_0 | IBM The off-line backup command could fail even when the database is quiesced on DB2 V10.1 and later. - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Offline-backup against the quiesced database failed with the error, SQL1035N.
It did not occur with V9.7. And it came to happen after migrating to V10.1 or later from V9.7.
SYMPTOM
The following example shows this situation.
1) In CLP 1 under the user having DBADM authority, execute quiesce database command on the database, sample.
$ db2 connect to sample
Database Connection Information
Database server = DB2/AIX64 10.5.7
SQL authorization ID = E105Q7A
Local database alias = SAMPLE
$ db2 quiesce database immediate force connections
DB20000I The QUIESCE DATABASE command completed successfully.
$ db2 terminate
DB20000I The TERMINATE command completed successfully.
2) In CL 2 under the user having only connect privilege on sample database.
Run the following shell repeating connect to sample.. |
72aa4e086fca6870bff7a24a42e76f4f_1 | $ cat connect.sh
#!/bin/sh
count=0
while [ $count -lt 1000 ]; do
db2 connect to $db
count=`expr $count + 1`
done
db2insth $ sh -x loop.sh
+ count=0
+ [ 0 -lt 1000 ]
+ db2 connect to sample
SQL20157N User with authorization ID "USER1" failed to attach to a
quiesced instance, or connect to a quiesced database or a database in a
quiesced instance which is in the following quiesce mode: "QUIESCE DATABASE"
SQLSTATE=08004
+ + expr 0 + 1
count=1
+ [ 1 -lt 1000 ]
+ db2 connect to sample
<snippet>
* connect to sample continues to fail with the error, SQL20157N because the database, sample is quiesced.
3) In CLP 1, execute the off-line backup command while executing the shell script under CLP2.
$ db2 backup db sample
SQL1035N The operation failed because the specified database cannot be
connected to in the mode requested. SQLSTATE=57019
* The backup command failed. But this error does not happen on V9.7. |
72aa4e086fca6870bff7a24a42e76f4f_2 | For avoiding the error in offline-backup, use quiesce instance command with restricted access option.
CAUSE
Because of the code change in V10.1 GA, the off-line backup command could be blocked for short period of time while connect database command is executed.
RESOLVING THE PROBLEM
Please use quiesce instance command with the "restricted access" option instead of the quiesce database command.
Or please retry off-line backup command after getting SQL1035N error.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21980030] |
092a11d21512d313f9e23733243c4fee_0 | IBM Portal 7.0.0.1 migration may fail with error EJPPH0044E EJPPH0001E ADMC0009E while running upgrade-profile task. - United States upgrade-profile; migration; EJPPH0044E; EJPPH0001E; ADMC0009E; was.notification.timeout TECHNOTE (TROUBLESHOOTING)
PROBLEM
One may find the following in the configtrace.log file ---
wps.dynamicui.transformationapp.webmod.xml to consolidated deployment
script
[echo] Deploying consolidated web-app update script
[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10056/wps/config/ |
092a11d21512d313f9e23733243c4fee_1 | [xmlaccess] EJPXB0004I: Writing output file
/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc
cessResult.xml
[xmlaccess] EJPXB0002I: Reading input file
/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/config/work/consolida
tedXMLAccess.xml
[xmlaccess] EJPXB0019E: Server response indicates an error. For status
and details of the XmlAccess error look at file
/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc
cessResult.xml.
[xmlaccess] EJPXB0019E: Server response indicates an error. For status
and details of the XmlAccess error look at file
/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc
cessResult.xml.
from the consolidatedXMLAccessResult.xml file, it fails at -- |
092a11d21512d313f9e23733243c4fee_2 | <!-- 55 [web-app com.ibm.wps.portlets.policystatus
uid=com.ibm.workplace.policystatus.PolicyStatus] -->
<request build="wp7001CF07_001_14" type="update" version="7.0.0.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="PortalConfig_7.0.0.xsd">
<status element="[web-app com.ibm.wps.portlets.policystatus
uid=com.ibm.workplace.policystatus.PolicyStatus]" result="failed">
<message
id="EJPXA0043E">com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E:
An error occurred while creating or updating the resource. [web-app
com.ibm.wps.portlets.policystatus
uid=com.ibm.workplace.policystatus.PolicyStatus]</message>
<message
id="EJPPD0015E">com.ibm.wps.command.CommandFailedException: EJPPD0015E:
Portlet application manager failed when user xmlaccess scripting user
executed command UpdateWebApplication.
WrappedException is:
com.ibm.wps.pe.mgr.exceptions.AppServerWarUpdateException: EJPPH0044E:
Redeployment of Web Module id in WAR file |
092a11d21512d313f9e23733243c4fee_3 | /opt/IBM/WebSphere/APP/WP7/wp_profile/PortalServer/deployed/appPolicySta
tus.war (application display name: PA_Policy_Status) didi not complete
successfully when invoking the WebSphere Application Server
administration interface.</message>
<message
id="EJPPH0044E">com.ibm.wps.pe.mgr.exceptions.AppServerWarUpdateExceptio
n: EJPPH0044E: Redeployment of Web Module id in WAR file
/opt/IBM/WebSphere/APP/WP7/wp_profile/PortalServer/deployed/appPolicySta
tus.war (application display name: PA_Policy_Status) didi not complete
successfully when invoking the WebSphere Application Server
administration interface.</message>
<message
id="EJPPH0001E">com.ibm.wps.pe.mgr.exceptions.AppServerAdminListenerExce
ption: EJPPH0001E: Adding Notification Listener for MBean AppManagement
failed. (Application Name: PA_Policy_Status).</message> |
092a11d21512d313f9e23733243c4fee_4 | <message>com.ibm.websphere.management.exception.ConnectorException:
ADMC0009E: The system failed to make the SOAP RPC call:
queryNames</message>
</status>
</request>
RESOLVING THE PROBLEM
To resolve the issue increase the was.notification.timeout to 1200 (seconds) in WP DeploymentService either from WebSphere Admin Console or Dmgr.
If the property is not listed under custom properties, please add the above property.
Re-run the upgrade-profile task to proceed with migration. |
a9b50476206e9b9bc50b92215b2267b8_0 | IBM MQ 7.1 and later: How to remove a channel authentication record (CHLAUTH) - United States TECHNOTE (FAQ)
QUESTION
You have added a channel authentication record into a WebSphere MQ 7.1 or later queue manager:
SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL) ACTION(ADD)
AMQ8877: WebSphere MQ channel authentication record set.
Then you display it:
DISPLAY CHLAUTH(*) TYPE(USERMAP)
1 : DISPLAY CHLAUTH(*) TYPE(USERMAP)
AMQ8878: Display channel authentication record details.
CHLAUTH(*) TYPE(USERMAP)
CLNTUSER(testuser) 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(testuser) USERSRC(CHANNEL)
3 : DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)
You get the following error:
AMQ8405: Syntax error detected at or near end of command segment below:-
DELETE CHLAUTH |
a9b50476206e9b9bc50b92215b2267b8_1 | 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(testuser) ACTION(REMOVE)
19 : SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)
But you get the following error:
AMQ8884: Channel authentication record not found.
You specified the attribute CLNTUSER(testuser) 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? |
a9b50476206e9b9bc50b92215b2267b8_2 | CAUSE
See the following section of the MQ 7.1 documentation:
WebSphere MQ > Administering > Administering local WebSphere MQ objects > Performing local administration tasks using MQSC commands
WebSphere MQ object names [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/fa11060_.htm]
+ 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(testuser) the string 'testuser' will be folded to upper-case resulting in the following value being actually used by runmqsc:
CLNTUSER(TESTUSER)
And in this case, there is no record for the user TESTUSER (the record is for 'testuser'). |
a9b50476206e9b9bc50b92215b2267b8_3 | 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('testuser') ACTION(REMOVE)
1 : set CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)
AMQ8877: WebSphere MQ channel authentication record set.
++ Example of record with more attributes
Let's examine the case when a record has more attributes, such as:
SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(ADD)
AMQ8877: WebSphere MQ channel authentication record set.
display CHLAUTH(MY.CHANNEL)
9 : display CHLAUTH(MY.CHANNEL)
AMQ8878: Display channel authentication record details.
CHLAUTH(MY.CHANNEL) TYPE(USERMAP)
DESCR( ) CUSTOM( )
ADDRESS(*) CLNTUSER(client_1)
MCAUSER(user_1) USERSRC(MAP) |
a9b50476206e9b9bc50b92215b2267b8_4 | You want to delete the record and you try the following command which is based on the command that worked well for a simpler case. But this time, it fails:
SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') ACTION(REMOVE)
AMQ8884: Channel authentication record not found.
You try the original command that created the record, but changing the action to REMOVE:
SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(REMOVE)
AMQ8885: Parameter not allowed for this action on a channel authentication record.
The attribute USERSRC is not a valid parameter for the REMOVE action (see table below).
Therefore, by removing this attribute, then the following command worked successfully to remove the record:
SET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('mengano') ADDRESS('*') ACTION(REMOVE)
AMQ8877: WebSphere MQ channel authentication record set. |
a9b50476206e9b9bc50b92215b2267b8_5 | See:
WebSphere MQ 8.0.0 > IBM MQ > Reference > Administration reference > MQSC reference > The MQSC commands >
SET CHLAUTH [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q086630_.htm]
.
+ begin excerpt
.
Usage notes
The following table shows which parameters are valid for each value of ACTION:
.
Action
Parameter ADD or REMOVE REMOVEALL
REPLACE
CHLAUTH X X X
TYPE X X X
CMDSCOPE X X X
ACTION X X X
ADDRESS X X
ADDRLIST X X
CHCKCLNT X
CLNTUSER X X
MCAUSER X
QMNAME X X
SSLCERTI X X
SSLPEER X X
USERLIST X X
USERSRC X
WARN X
DESCR X
.
+ end excerpt
Additional Search Words: uppercase lowercase upper lower case
PRODUCT ALIAS/SYNONYM
WMQ MQ MQSeries |
95267a40c2e753ddba4c24ded56849b4_0 | IBM SQL1763N error with Reason Code 11 while running "Alter Tablespace" command to reclaim unused storage space against DMS or automatic storage tablespaces. - United States SQL1763N; Alter Tablespace; reclaimable storage; DMS; Automatic storage table spaces; MON_GET_TABLESPACE; RECLAIMABLE_SPACE_ENABLED; SMS; DB2 Version 9.7; lower high water mark TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Receiving SQL1763N error with Reason Code 11 while running "Alter Tablespace" command to reclaim unused storage space against DMS or automatic storage tablespaces.
SYMPTOM
Following reasons apply:
* If the DMS or automatic storage tablespaces are not created in DB2 Version 9.7 or later, as the "Reclaimable Storage" is not available in tablespaces created in earlier versions(V9.1/V9.5) of the DB2 product.
* Trying to alter a SMS tablespace as this feature is not supported on SMS tablespaces.
Example testcase on a TEMPSPACE1 SMS tablespace. |
95267a40c2e753ddba4c24ded56849b4_1 | *
*
* DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1763N Invalid ALTER TABLESPACE statement for table space "TEMPSPACE1" due to reason "11" SQLSTATE=429BC
*
DIAGNOSING THE PROBLEM
MON_GET_TABLESPACE table function and RECLAIMABLE_SPACE_ENABLED monitor element can be used to identify whether the tablespace is enabled for reclaimable storage or not. Example:
db2 "SELECT varchar(tbsp_name, 30) as tbsp_name, tbsp_type, RECLAIMABLE_SPACE_ENABLED FROM TABLE(MON_GET_TABLESPACE('',-2))"
Snippet of the output:
TBSP_NAME TBSP_TYPE RECLAIMABLE_SPACE_ENABLED
----------------- ----------- -------------------------
SYSCATSPACE DMS 1
TEMPSPACE1 SMS 0
USERSPACE1 DMS 1
If the RECLAIMABLE_SPACE_ENABLED monitor element returns a value of 1, then the tablespace is enabled for reclaimable storage. Otherwise, it returns a value of 0. |
95267a40c2e753ddba4c24ded56849b4_2 | RESOLVING THE PROBLEM
To use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later. Example testcase on SYSCATSPACE DMS tablespace which has reclaimable storage enabled.
*
*
*
*
*
Note:
Tablespaces migrated from DB2 V9.1/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature. RELATED INFORMATION
Reclaimable storage [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html] |
1447e3705efb0e543c76245053918a61_0 | IBM Levels of JRE and GSkit bundled with IBM MQ - United States RELEASE NOTES
ABSTRACT
This page gives you access to the details of the levels of JRE and GSKit included with various maintenance levels of IBM MQ, by version.
CONTENT |
1447e3705efb0e543c76245053918a61_1 | IBM MQ V9.0 Continuous Delivery GSKit Level JRE Level IBM Security Directory Server Client Level 9.0.5 (Windows, Linux, AIX) 8.0.50.88 8.0.5.10 6.4.0.14 9.0.4 (Windows, Linux, AIX) 8.0.50.82 8.0.4.11 6.4.0.12 9.0.3 (Windows, Linux) 8.0.50.78 8.0.4.5 6.4.0.11 9.0.2 (Windows, Linux) 8.0.50.77 8.0.3.20 6.4.0.11 9.0.1 (Windows, Linux) 8.0.50.70 8.0.3.12 6.4.0.9
IBM MQ V9.0 Long Term Support GSKit Level JRE Level IBM Security Directory Server Client Level 9.0.0.4 (Windows, Linux, AIX) 8.0.50.88 8.0.5.11 6.4.0.15 9.0.0.4 (Solaris) 8.0.50.88 8.0.5.10 6.4.0.15 9.0.0.4 (HP) 8.0.50.88 8.0.5.10 6.3.1.23 9.0.0.3 (Windows, Linux, AIX, Solaris ) 8.0.50.88 8.0.5.10 6.4.0.14 9.0.0.3 (HP) 8.0.50.88 8.0.5.5 6.3.1.22 9.0.0.2 (Windows, Linux, AIX, Solaris, HP) 8.0.50.77 8.0.4.10 6.4.0.12 9.0.0.1 (Windows, Linux, AIX) 8.0.50.77 8.0.4.1 6.4.0.11 9.0.0.1 (HP, Solaris) 8.0.50.77 8.0.4.5 6.4.0.11 9.0.0.0 (Solaris, Windows, Linux, AIX) 8.0.50.65 8.0.3.0 6.4.0.6 9.0.0.0 (HP) 8.0.50.65 8.0.2.14 6.3.1.15 |
1447e3705efb0e543c76245053918a61_2 | IBM MQ V8.0 GSKit Level JRE Level IBM Security Directory Server Client Level 8.0.0.9 (Windows, Linux, AIX) 8.0.50.88 7.1 SR4 FP20 6.4.0.15 8.0.0.9 (Solaris) 8.0.50.88 7.0 SR10 FP20 6.4.0.15 8.0.0.9 (HP) 8.0.50.88 7.0 SR10 FP15 6.3.1.23 8.0.0.8 (Windows, Linux, AIX) 8.0.50.83 7.1 SR4 FP10 6.4.0.13 8.0.0.8 (Solaris, HP) 8.0.50.83 7.0 SR10 FP10 6.3.1.21 8.0.0.7 (Windows, Linux, AIX) 8.0.50.79 7.1 SR4 FP5 6.4.0.11 8.0.0.7 (Solaris, HP) 8.0.50.79 7.0 SR10 FP5 6.3.1.20 8.0.0.6 (Windows, Linux, AIX) 8.0.50.71 7.1 SR3 FP60 6.4.0.10 8.0.0.6 (Solaris) 8.0.50.71 7.0 SR9 FP60 6.4.0.10 8.0.0.6 (HP) 8.0.50.71 7.0 SR9 FP50 6.3.1.19 8.0.0.5 (Windows, Linux, AIX) 8.0.50.65 7.1 SR 3 FP 40 6.4.0.8 8.0.0.5 (Solaris) 8.0.50.65 7.0 SR 9 FP 40 6.4.0.8 8.0.0.5 (HP) 8.0.50.65 7.0 SR 9 FP 32 6.3.1.17 8.0.0.4 (Windows, Linux, AIX) 8.0.50.52 7.1 SR 3 FP 10 6.3.1.12 (6.4.0.4 Linux) 8.0.0.4 (Solaris, HP) 8.0.50.52 7 SR 9 FP 10 6.3.1.12 8.0.0.3 (Windows, Linux, AIX) 8.0.50.42 7.1 SR 3 6.3.1 8.0.0.3 (Solaris) |
1447e3705efb0e543c76245053918a61_3 | 8.0.50.42 7 SR 9 6.3.1 8.0.0.3 (HP) 8.0.50.42 7 SR 8 6.3.1 8.0.0.2 (Windows, Linux, AIX) 8.0.50.34 7.1 SR 2 6.3.1 8.0.0.2 (Solaris, HP) 8.0.50.34 7 SR 8 6.3.1 8.0.0.1 (Solaris, Windows, Linux, AIX) 8.0.50.31 7 SR 7 FP 1 6.3.1 8.0.0.1 (HP) 8.0.50.31 7 SR 6 FP 1 6.3.1 8.0.0.0 (Solaris, Windows, Linux ,HP, AIX) 8.0.50.16 7 SR 6 6.3.1 |
1447e3705efb0e543c76245053918a61_4 | IBM WebSphere MQ V7.5 GSKit Level JRE Level 7.5.0.8 (Windows, Linux, AIX, HP, Solaris) 8.0.50.79 6.0 SR16 FP45 7.5.0.7 (HP) 8.0.50.66 6.0 SR16 FP22 7.5.0.7 (Windows, Linux, AIX) 8.0.50.66 6.0 SR16 FP26 7.5.0.7 (Solaris) 8.0.50.66 6.0 SR16 FP25 7.5.0.6 (HP) 8.0.14.53 1.6 SR16 FP16 7.5.0.6 (Solaris, Windows, Linux, AIX) 8.0.14.53 1.6 SR16 FP20 7.5.0.5 (Solaris, Windows, Linux, HP, AIX) 8.0.14.48 1.6 SR 16 FP 3 Interim Fix 7.5.0.4 (Solaris, Windows, Linux, AIX) 8.0.14.43 1.6 SR 16 7.5.0.4 (HP) 8.0.14.43 1.6 SR 15 FP 1 7.5.0.3 (Solaris, Windows, Linux ,HP, AIX) 8.0.14.28 1.6 SR 15 7.5.0.2 (Solaris, Windows, Linux, AIX) 8.0.14.28 1.6 SR 13 FP 2 7.5.0.2 (HP) 8.0.14.28 1.6 SR 13 FP 1 7.5.0.1 (Solaris, Windows, Linux, HP, AIX) 8.0.14.26 1.6 SR 12 7.5.0.0 (Solaris, Windows, Linux, HP, AIX) 8.0.14.21 1.6 SR 10 FP 1 |
1447e3705efb0e543c76245053918a61_5 | IBM WebSphere MQ V7.1 GSKit Level JRE Level 7.1.0.9 (Solaris, Windows, Linux, HP, AIX) 8.0.50.83 1.6 SR16 FP50 7.1.0.8 (Solaris, Windows, Linux, HP, AIX) 8.0.50.69 1.6 SR16 FP30 7.1.0.7 (Solaris, Windows, Linux, HP, AIX) 8.0.14.50 1.6 SR 16 FP 5 7.1.0.6 (Solaris, Windows, Linux, HP, AIX) 8.0.14.44 1.6 SR 16 FP 1 7.1.0.5 (Solaris, Windows, Linux, HP, AIX) 8.0.14.35 1.6 SR 15 FP 1 7.1.0.4 (Solaris, Windows, Linux, HP, AIX) 8.0.14.28 1.6 SR 14 7.1.0.3 (Solaris, Windows, Linux, AIX) 8.0.14.28 1.6 SR 13 FP 2 7.1.0.3 (HP) 8.0.14.28 1.6 SR 13 FP 1 7.1.0.2 (Solaris, Windows, Linux, HP, AIX) 8.0.14.22 1.6 SR 10 FP 1 7.1.0.1 (Solaris, Windows, Linux, HP, AIX) 8.0.14.14 1.6 SR 10 7.1.0.0 (Solaris, Windows, Linux, HP, AIX) 8.0.14.12 1.6 SR 9 FP 1 |
1447e3705efb0e543c76245053918a61_6 | IBM WebSphere MQ V7.0.1 GSKit Level JRE Level 7.0.1.14 (Solaris, Windows, Linux, HP, AIX) 7.0.5.6, 8.0.14.53 1.5 SR 16 FP 14 7.0.1.13 (Solaris, Windows, Linux, HP, AIX) 7.0.5.6, 8.0.14.49 1.5 SR 16 FP 9 7.0.1.12 (Solaris, Windows, Linux, HP, AIX) 7.0.4.48, 8.0.14.34 1.5 SR 16 FP 4 7.0.1.11 (Solaris, Windows, Linux, HP, AIX) 7.0.4.45, 8.0.14.28 1.5 SR 16 FP 3 7.0.1.10 (Solaris, Windows, Linux, HP, AIX) 7.0.4.44, 8.0.14.26 1.5 SR 15 7.0.1.9 (Solaris, Windows, Linux, HP, AIX) 7.0.4.41, 8.0.14.22 1.5 SR 13 FP 1 7.0.1.8 (Solaris, Windows, Linux, HP, AIX) 7.0.4.38, 8.0.14.14 1.5 SR 13 7.0.1.7 (Solaris, Windows, Linux, HP, AIX) 7.0.4.33, 8.0.14.9 1.5 SR 12 FP 5 7.0.1.6 (Solaris, Windows, Linux, HP, AIX) 7.0.4.33, 8.0.14.9 1.5 SR 12 FP 4 7.0.1.5 (Solaris, Windows, Linux, HP, AIX) 7.0.4.29, 8.0.14.9 1.5 SR 12 FP 3 7.0.1.4 (Solaris, Windows, Linux, HP, AIX) 7.0.4.29, 8.0.14.7 1.5 SR 11 7.0.1.3 (Solaris, Windows, Linux, HP, AIX) 7.0.4.27 1.5 SR 11 7.0.1.2 (Solaris, Linux, HP, AIX) 7.0.4.27 1.5 |
1447e3705efb0e543c76245053918a61_7 | SR 11 7.0.1.2 (Windows) 7.0.4.27 1.5 SR 5 7.0.1.1 (Solaris, Linux, HP, AIX) 7.0.4.23 1.5 SR 10 7.0.1.1 (Windows) 7.0.4.23 1.5 SR 5 7.0.1.0 (Solaris, Windows, Linux, HP, AIX) 7.0.4.23 1.5 SR 5 7.0.0.2 (Solaris, Windows, Linux, HP, AIX) 7.0.4.20 1.4.2 SR 12 7.0.0.1 (Solaris, Windows, Linux, HP, AIX) 7.0.4.20 1.4.2 SR 12 7.0.0.0 (Solaris, Windows, Linux, HP, AIX) 7.0.4.14 1.4.2 SR 12 |
1447e3705efb0e543c76245053918a61_8 | PRODUCT ALIAS/SYNONYM
WMQ MQ |
163fce203114e196366efb6d4e29d7d8_0 | IBM Filter Analyzer and Filters comparing ObjectServer fields - United States netcool; impact; netcool/impact; nci; event; reader; eventreader; omnibus; omnibuseventreader; object; server; objectserver; field; fields; compare; contrast; comparison; use; filter; filters; filtering; analyse; analyze; analyser; analyzer; filteranalyser; filteranalyzer; rule; includes; unsupported; expression; include; including; support; supporting; supported; restriction; ExecutionException; Execution; Exception; consolidate; consolidatefilters; concurrent; expressions; expression TECHNOTE (FAQ)
QUESTION
The Filter Analyzer reports the error:
"rule includes an unsupported expression"
when comparing two ObjectServer fields against each other and/or a field against GetDate within an EventReader Filter |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.