Datasets:

manu

/

tech_qa

like 0

[ "IBM Switching Business Process Choreographer Explorer back to using HTTP from HTTPS - United States DOWNLOADABLE FILES\n\nABSTRACT\n In Business Process Manager Advanced Version 8.0.1, the default protocol used by Business Process Choreographer Explorer was changed to use HTTPS. You can switch it back to HTTP. \n\nDOWNLOAD DESCRIPTION\nWhen Business Process Choreographer Explorer uses the default secure HTTPS protocol, any attempts to access Business Process Choreographer Explorer using HTTP are redirected to use HTTPS. If you need Business Process Choreographer Explorer to support insecure HTTP connections, you can use the unsecureExplorer.ant script to switch the protocol used from HTTPS to HTTP. \n\nAttention: It is not recommend to use the insecure HTTP protocol. Using HTTP for the Business Process Choreographer Explorer can open your organization to possible security problems.\n\nSwitching to HTTP", "If you need to switch Business Process Choreographer Explorer from HTTPS to use HTTP, complete the following actions:", "1. Download the unsecureExplorer.ant script file, which is attached near the bottom of this page.\n \n \n 2. If you previously switched Business Process Choreographer Explorer to use HTTP, but are performing this task again because you are installing an interim fix, fix pack, or refresh pack that updated Business Process Choreographer Explorer has reverted it back to the default HTTPS protocol, you must first delete the old (invalid) backup EAR file before running the script.\n \n * On Linux, UNIX-based and z/OS platforms, delete the install_root/ProcessChoreographer/internal/bpcexplorer_secure_backup.ear file. \n * On Microsoft Windows platforms, delete the\n install_root\\ProcessChoreographer\\internal\\bpcexplorer_secure_backup.ear file.", "3. Run the script to patch the bpcexplorer.ear file. In a network deployment environment, you must run the script on the deployment manager. * On Linux, UNIX-based and z/OS platforms, enter the following command:\n install_root/ws_ant.sh -f unsecureExplorer.ant \n * On Windows platforms, enter the following command:\n install_root\\ws_ant.bat -f unsecureExplorer.ant\n Note: A backup copy of the original EAR file is created named bpcexplorer_secure_backup.ear.\n \n \n \n \n 4. Deploy the patched bpcexplorer.ear file by updating the profile. For more information about updating profiles for an interim fix, see one of the following documents: * For version 8.0.1.x: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21608414].", "* For version 8.5 and later: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21637449].", "Remember: In the future, if you install an interim fix, fix pack, or refresh pack that updates the Business Process Choreographer Explorer, it will revert to using the default secure HTTPS protocol. If that happens and you still need the Business Process Choreographer Explorer to use the HTTP protocol, you must complete these steps again to re-enable the HTTP protocol. \n\n\n\nSwitching back to HTTPS", "If you need to switch Business Process Choreographer Explorer back from HTTP to HTTPS, complete the following actions: 1. Change to the directory where the backup EAR file is located. * On Linux, UNIX-based and z/OS platforms, its location is \n install_root/ProcessChoreographer/internal \n * On Windows platforms, its location is \n install_root\\ProcessChoreographer\\internal\n \n \n \n \n 2. In that directory, copy or rename the backup EAR file bpcexplorer_secure_backup.ear to bpcexplorer.ear and overwrite any existing copy.\n \n \n 3. Deploy the original HTTPS version by updating the profile. For more information about updating profiles for an interim fix, see one of the following documents: * For versions 8.0.1.x: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21608414].", "* For version 8.5 and later: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21637449].", "Download file unsecureExplorer.ant [/support/docview.wss?uid=swg24034421&aid=2]unsecureExplorer.ant [/support/docview.wss?uid=swg24034421&aid=1]\n\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n BPM" ]

[ "1. Download the unsecureExplorer.ant script file, which is attached near the bottom of this page.\n \n \n 2. If you previously switched Business Process Choreographer Explorer to use HTTP, but are performing this task again because you are installing an interim fix, fix pack, or refresh pack that updated Business Process Choreographer Explorer has reverted it back to the default HTTPS protocol, you must first delete the old (invalid) backup EAR file before running the script.\n \n * On Linux, UNIX-based and z/OS platforms, delete the install_root/ProcessChoreographer/internal/bpcexplorer_secure_backup.ear file. \n * On Microsoft Windows platforms, delete the\n install_root\\ProcessChoreographer\\internal\\bpcexplorer_secure_backup.ear file.\n \n \n \n \n 3. Run the script to patch the bpcexplorer.ear file. In a network deployment environment, you must run the script on the deployment manager. * On Linux, UNIX-based and z/OS platforms, enter the following command:\n install_root/ws_ant.sh -f unsecureExplorer.ant \n * On Windows platforms, enter the following command:\n install_root\\ws_ant.bat -f unsecureExplorer.ant\n Note: A backup copy of the original EAR file is created named bpcexplorer_secure_backup.ear.\n \n \n \n \n 4. Deploy the patched bpcexplorer.ear file by updating the profile. For more information about updating profiles for an interim fix, see one of the following documents: * For version 8.0.1.x: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21608414]. \n * For version 8.5 and later: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21637449]." ]

[]

[ "IBM New IBM License Metric Tool online Support experience! - United States NEWS\n\nABSTRACT\n IBM Security Support announced in October, 2017, that changes to your online IBM License Metric Tool (ILMT) Support experience were coming. See below for the text of the mailing to that was sent to Support customers. \n\nCONTENT\n\nDear IBM License Metric Tool Customer,\n\nIn addition to the recently announced LMT forum process [http://ibm.biz/ILMTforumAnnounce], we are excited to announce that we are launching a new online Support experience. Most IBM Security products, including IBM License Metric Tool, will go live with this new technology at the end of October, 2017. \n\nThe move to this new online Support experience should be seamless for you.", "* As announced earlier this year, IBM dW Answers [https://developer.ibm.com/answers/index.html] should still be your first avenue to Support. \n * The e-mail and phone support channels offered to you today will remain unchanged. \n * Your bookmarks and existing access methods will automatically connect to the new online Support experience once you’ve selected your IBM Security product or you can use a new URL to reach the new online Support experience directly: https://www.ibm.com/mysupport [https://www.ibm.com/mysupport]. \n * Any existing PMRs will be automatically converted to “Cases” in the new experience. Simply choose “cases” from the Security product support landing page to see status or make updates. \n\n\nIf you are experiencing a problem with the portal (such as a login issue, etc.), we are here to help. You can submit your issue via our Support page [https://www.ibm.com/mysupport/s/] by clicking “Email IBM Support”, or by emailing [email protected].", "Should you have any questions, please send email to [email protected] [[email protected]?subject=Changes%20to%20your%20IBM%20Support%20experience]. [/support/docview.wss?uid=swg22009938&aid=1] IBM Security Support Team \n\nPRODUCT ALIAS/SYNONYM\n LMT" ]

[ "In addition to the recently announced LMT forum process [http://ibm.biz/ILMTforumAnnounce], we are excited to announce that we are launching a new online Support experience. Most IBM Security products, including IBM License Metric Tool, will go live with this new technology at the end of October, 2017." ]

[ 0 ]

[ "IBM Security Bulletin: IBM API Connect is affected by Node.js tough-cookie module vulnerability to a denial of service (CVE-2016-1000232) - United States SECURITY BULLETIN\n\nSUMMARY\n API Connect has addressed the following vulnerability. \n\nNode.js tough-cookie module is vulnerable to a denial of service, caused by a regular expression error. By using a sufficiently large HTTP request Cookie header, a remote attacker could exploit this vulnerability to cause the application to consume an overly large amount of CPU resources. \n\n\nVULNERABILITY DETAILS", "CVEID:CVE-2016-1000232 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000232]\nDESCRIPTION:Node.js tough-cookie module is vulnerable to a denial of service, caused by a regular expression error. By using a sufficiently large HTTP request Cookie header, a remote attacker could exploit this vulnerability to cause the application to consume an overly large amount of CPU resources.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119038 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119038]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected API Connect Affected Versions IBM API Connect 5.0.6.0-5.0.6.5 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0 REMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation / First Fix IBM API Connect", "5.0.0.0-5.0.6.5 5.0.6.6 LI79986 Addressed in IBM API Connect V5.0.6.6.\n\nFollow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.5&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\n5.0.7.0-5.0.7.2 5.0.8.1 LI79986 Addressed in IBM API Connect V5.0.8.1.\n\nFollow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] IBM API Connect", "5.0.8.0 5.0.8.1 LI79986 Addressed in IBM API Connect V5.0.8.1.\n\nFollow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]", "CHANGE HISTORY\n 19 February 2018: original document published \n\n*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. \n\nDISCLAIMER\nAccording 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." ]

[ "CVEID:CVE-2016-1000232 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000232]\nDESCRIPTION:Node.js tough-cookie module is vulnerable to a denial of service, caused by a regular expression error. By using a sufficiently large HTTP request Cookie header, a remote attacker could exploit this vulnerability to cause the application to consume an overly large amount of CPU resources.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119038 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119038]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected API Connect Affected Versions IBM API Connect 5.0.6.0-5.0.6.5 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0" ]

[ 1 ]

[ "IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers - United States wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server. WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows.\n\nNotice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory.\nReference:\nUsing the WASServiceHelper utility to create Windows services for application servers\nhttps://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]", "See DeveloperWorks article for detailed information: (Link at the bottom of this document) \n\nSYMPTOM\nCreating and removing a WebSphere service in Windows is confusing and error prone.\n\n\nCAUSE\nThis application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\n\n\n\n 1. Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors.", "[/support/docview.wss?uid=swg21397335&aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf] \n\nNote: This also creates an entry in the WASServiceCmd.log in the current directory which contains the actual WASService.exe command used to create the service. \n\nExample of a log entry: \n\n[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\" \n-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"\n-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"\n-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" \n-startType manual \n-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2]", "Notice: Some browsers are having trouble downloading this file and getting docview.wss instead. Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip). You can now access the utility. \nSee DeveloperWorks article for more information: \nThe Support Authority: Take the confusion (and errors) out of creating Windows services for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/techjournal/1005_supauth/1005_supauth.html] \n\n\nSee TroubleShooting: WebSphere Application Server (Windows Services) problems for V6.0, V6.1 and V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21232884] if you are still having a problem with Windows services." ]

[ "Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors." ]

[ 1 ]

[ "IBM EJB WIMServiceHome cannot be found even after .ear file is installed successfully - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nThe ConfigEngine wp-add-property fails with the following error:\n\nCannot find EJB: ejb/com/ibm/websphere/wim/ejb/WIMServiceHome\n[wplc-add-property] javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: \"corbaloc:iiop:<host name>:<port number>\". \n\n\nCAUSE\nIn a cluster, the .ear file must be installed on the Deployment Manager (DMGR). For more information, refer to Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381]. If originally installed elsewhere, subsequent attempts to install it on the DMGR will appear to succeed but attempts to add properties (ConfigEngine task, wp-add-property) continue to fail with a \"Cannot find EJB\" message similar to the one above.\n\nENVIRONMENT\nClustered WebSphere Portal\n\nDIAGNOSING THE PROBLEM", "-- Confirm that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.UnknownHostException: <host name>:host=<host name>,port=9809 vmcid: IBM minor code: E02 completed: No]\n\n-- Check the results of the wp-la-install-ear file in the ConfigTrace.log to determine if the .ear file was already installed:", "* Command line arguments: ... wp-la-install-ear\n * \n * ...\n * \n * Target started: wp-la-install-ear\n * \n * \n * wp-la-install-ear:\n * \n * ...\n * \n * [wplc-create-ear]\n * \n * earfile=\"/prod/sys/Portal61/WebSphere/AppServer/systemApps/wim.ear/wimejb.jar\"\n * \n * [wplc-create-ear] null\n * [wsadmin] WASX7209I: Connected to process \"dmgr\" on node <node name> using SOAP connector; The type of process is: DeploymentManager \n [wsadmin] 'dmgr(cells/<cell name>/nodes/<node name>/servers/dmgr|server.xml#Server_1)' \n [wsadmin] Enterprise application WIMSYSTEM already exists. \n ... \n * BUILD SUCCESSFUL", "-- Inspect the serverindex.xml files to confirm that the .ear file is installed on a non-DMGR node in the cluster: \n * \n * <serverEntries serverDisplayName=\"dmgr\" serverName=\"dmgr\" serverType=\"DEPLOYMENT_MANAGER\" xmi:id=\"ServerEntry_1\"> \n * <deployedApplications>\n * \n * ...\n * (contains no references to WIMSYSTEM.ear) \n \n * \n * <serverEntries serverName=\"WebSphere_Portal\" serverType=\"APPLICATION_SERVER\" \n * ...\n * \n * <deployedApplications>WIMSYSTEM.ear/deployments/WIMSYSTEM</deployedApplcations>\n\nRESOLVING THE PROBLEM\nYou must first uninstall the WIMSYSTEM enterprise application from the WebSphere_Portal server (using the WebSphere Administrative console). Then follow the steps in Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381] to install the .ear file on the DMGR.\n\nRELATED INFORMATION\n Incorrect providerURL causes wp-add-property failure [http://www.ibm.com/support/docview.wss?uid=swg21358381]" ]

[ "You must first uninstall the WIMSYSTEM enterprise application from the WebSphere_Portal server (using the WebSphere Administrative console). Then follow the steps in Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381] to install the .ear file on the DMGR." ]

[ 3 ]

[ "IBM Finding if Table created as NOT LOGGED INITIALLY - United States TECHNOTE (FAQ)\n\nQUESTION\n How to find if Table was Created as NOT LOGGED INITIALLY? \n\nANSWER\nWe can use either of the following methods to Check if Table was created as 'Not Logged Initially'\n1)Using db2cat,\n\ndb2cat -db <dbname> -n <TableName> -s <Schema> -t | grep \"Table not logged\"\nWhich can confirm if given table was created as NLI or not.\n\nSample Output \n----------------------\nConnecting to the Database.\nConnect to Database Successful.\nTable not logged : 0\n----------------------\nTable not Logged showing '0' represent Table was not created as NLI, if it returns '1' then that is table was created as NLI.\n\n2)Using db2look \nUsing db2look command to get DDL information on the table which would show you if \nthe table was created as \"NOT LOGGED INITIALLY\" \n\nExample: \ndb2look -d <database_name> -t <table_name> -e -o <output_file_name.out>", "NOTE: Table Alter with ACTIVATE NOT LOGGED INITIALLY will not be listed in these above commands as it will activate NLI only for current Unit of work.\n\nNOTE:In DB2 V8 the LOG_ATTRIBUTE column in the SYSCAT.TABLES table was used to \ncheck if a table was created as NOT LOGGED INITIALLY.\nBut Starting from DB2 V9 this column is no longer being used and will always have a value of 0.\n\nRELATED INFORMATION\n NOT LOGGED INITIALLY [http://www.ibm.com/support/knowledgecenter/SSAE4W_7.1.0/com.ibm.etools.iseries.langref2.doc/rbafzmst484.htm]" ]

[ "We can use either of the following methods to Check if Table was created as 'Not Logged Initially'\n1)Using db2cat,\n\ndb2cat -db <dbname> -n <TableName> -s <Schema> -t | grep \"Table not logged\"\nWhich can confirm if given table was created as NLI or not.\n\nSample Output \n----------------------\nConnecting to the Database.\nConnect to Database Successful.\nTable not logged : 0\n----------------------\nTable not Logged showing '0' represent Table was not created as NLI, if it returns '1' then that is table was created as NLI.\n\n2)Using db2look \nUsing db2look command to get DDL information on the table which would show you if \nthe table was created as \"NOT LOGGED INITIALLY\" \n\nExample: \ndb2look -d <database_name> -t <table_name> -e -o <output_file_name.out>" ]

[ 0 ]

[ "IBM DataPower off-device logging: a configuration example - United States datapower; 7993; machine type 7993; logging; off device; off device logging; log target; off-device; syslog; debug log level; debug; log level TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote gives an example of how to enable off-device logging on an IBM® WebSphere® DataPower® appliance. This can be very helpful when a debug log level is needed to help isolate a problem or monitor behavior over a long period of time or can be used in production environment as DataPower only keeps a limited number of log files (the default is 3 files) in the file system in a rotational basis. \n\nCAUSE\nThe DataPower device has a finite amount of space to hold larger than average log files or long term logging needs in production environment.", "It should be noted that if used while debugging at load or in a capacity issue, log events may be dropped. There is a prioritization of events within the device and client traffic always comes first. Log events dropped can be confirmed or counted from the Status>Log Targets menu in the WebGUI.\n\n\nRESOLVING THE PROBLEM\nConfigure a server daemon to listen and capture the DataPower devices events. First, this example shows how to create the log target sending events to a syslog destination. The other examples listed below will have their own strong points to be considered depending on the problem scenario. \n\n \n\nSyslog: \n\n* The syslog protocol operates over UDP which has no guarantee on packet delivery - a fast fire and forget method. \n\nTo create the new log target, go into the default domain: Objects > Log Targets \n\nConfigure the log target with settings as follows from the WebGUI:", "1. Name the log target \n 2. Select Target Type of syslog \n 3. Fill in the Local Identifier with a descriptive string that may be used by a remote recipient to identify this specific log target \n 4. Enter the Remote Host Address and the Remote IP Port as in the screen shot wherex.x.x.x is the IP address of the remote syslog server that listens on port 514 \n 5. Take all other defaults\n\n\n\n[/support/docview.wss?uid=swg21269136&aid=1] [/support/docview.wss?uid=swg21269136&aid=1] \n\n \n\nUnder the Event Subscriptions tab, you can select all and debug as indicated here: \n\n\n[/support/docview.wss?uid=swg21269136&aid=2] [/support/docview.wss?uid=swg21269136&aid=2] \n\n * \n * 6. Generate log events in the DataPower by using some transactions, for example by saving the configuration from the WebGUI or running some test load into a domain.", "Syslog-ng, will simply work over the TCP protocol to ensure the packet is delivered to the destination. The same consideration should be applied to a device under high load in that a log event could be dropped if not able to be wrote out to the network within time. \n\n \n\nNFS:\nAll NFS limitations apply from file size and permission settings. This is a more common approach using an NFS static mount to capture a log target and can allow for slightly more reliable messages to be logged. The limiting factor again is the speed of the network and NFS server response time. \n\n \n\nFile type:", "Using a file type log target with a backup method as seen here:\n[/support/docview.wss?uid=swg21269136&aid=3] [/support/docview.wss?uid=swg21269136&aid=3]\nThis will allow log events to quickly be written to a local file on the device's file system. Once the file reaches its set size a connection to the destination will upload the file from the device. This will upload with a unique time and date stamp on the uploaded file.\n\nThis is a useful method to capture sporadic problems. This is also useful for long running transactions that may span more than one file depending on device load.\n\n\nHTTP service:\nFinally a clever method that may be used in some senarios would be an HTTP service on the device.\nUsing an HTTP service configured in the following way,\n[/support/docview.wss?uid=swg21269136&aid=4] [/support/docview.wss?uid=swg21269136&aid=4] \n\nOnce the file type log is created in the logtemp:/// directory, a client browser or wget type client can easily retrieve the file from the device.", "This is very useful when there is no local or accessible remote log storage location to the device, due to firewall or network restrictions. \n\nThis is also removing the limitation of the device dropping the log event should it not be able to write the log event to the network. \n\nEach of the above methods are very useful and work better in some scenarios than others depending on the network, load, problem, and information needed. This is intended to be a guide to help you decide which method would be best for your scenario." ]

[ "Configure a server daemon to listen and capture the DataPower devices events." ]

[ 1 ]

[ "IBM The import task failed with \"INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException)\" after patching BigFix/ILMT RedHat Linux server. - United States TECHNOTE (FAQ)\n\nQUESTION\n The import task failed with \"INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException)\" after patching BigFix/ILMT RedHat Linux server. \n\nCAUSE\nTEMA version: 9.2.2.0-20151209-1636\nAfter patching BigFix/ILMT Redhat Linux server, the import task started to fail with the following error in the import log:\n\n[/support/docview.wss?uid=swg22004607&aid=1] [/support/docview.wss?uid=swg22004607&aid=1] \n\n\n\n\nThe following commands confirm the glibc library installed:\n\n\nrpm -qa | grep -i glibcd.", "glibc-2.12-1.192.el6.x86_64 \nglibc-headers-2.12-1.192.el6.x86_64 \ncompat-glibc-headers-2.5-46.2.x86_64 \ncompat-glibc-2.5-46.2.x86_64 \nglibc-devel-2.12-1.192.el6.x86_64 \nglibc-common-2.12-1.192.el6.x86_64 \nglibc-2.12-1.192.el6.i686 \n\n\nfind / -name glibc* \n/usr/share/man/overrides/ru/man7/glibc.7.gz /usr/share/man/man7/glibc.7.gz /usr/share/doc/glibc-2.12 /usr/share/doc/glibc-common-2.12 /usr/sbin/glibc_post_upgrade.x86_64 /usr/sbin/glibc_post_upgrade.i686 \n\nfind / -name getservbyname* \n/usr/share/man/man3p/getservbyname.3p.gz /usr/share/man/overrides/ru/man3/getservbyname.3.gz /usr/share/man/overrides/ru/man3/getservbyname_r.3.gz /usr/share/man/man3/getservbyname.3.gz /usr/share/man/man3/getservbyname_r.3.gz \n\nThe $PATH environment variable shows:\n\n\necho $PATH \n\n/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin \n\nEven re-installing the glibc 32-bit library rpm package again and rebooting the RedHat server as well, it won't resolve the issue.", "Note: same error will occur when modifying the datasource setting as well as described in the above technote link.\n\n\nANSWER\nThe problem is resolved after upgrading to ILMT 9.2.7 and the import task continues to work successfully. Most likely this is due to the ILMT 9.2.2 application expecting a specific version of glibc 32-bit library file and it won't work if a newer version is found after the patching the RedHat Linux server.\n\nRELATED INFORMATION\n#" ]

[ "Most likely this is due to the ILMT 9.2.2 application expecting a specific version of glibc 32-bit library file and it won't work if a newer version is found after the patching the RedHat Linux server." ]

[ 2 ]

[ "IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM OS Images for Red Hat Linux Systems and AIX (CVE-2015-0410 and CVE-2014-6593) - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition Version 6 and 7 that are used by IBM OS Images for Red Hat Linux Systems and AIX. These issues were disclosed as part of the IBM Java SDK updates in January 2015. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "CVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM OS Image for Red Hat Linux Systems 2.0.0.1 and earlier.\nIBM OS Image for AIX 2.0.0.1 and earlier.\n\nREMEDIATION/FIXES\nThe 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.", "Java Update for Linux\nhttp://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]\n\nJava Update for AIX\nhttp://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]", "1. Import the fix into the Emergency Fix catalogue. \n 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 \n 3. Restart the deployed instance after the fix is applied.\n\n\nYou should verify applying this fix does not cause any compatibility issues. WORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nNone", "CHANGE HISTORY\n 23 July 2015: Original Version Published \n\n*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. \n\nDISCLAIMER\nAccording 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." ]

[ "CVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)" ]

[]

[ "IBM ITCAM Agent for WebSphere DataPower Applications: 7.1.0-TIV-ITM_WDP-FP0003 - United States DataPower; BN; KBN DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the enhancements listed in the \"Problems Fixed\"\nsection below. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2016.\n\n\nAll rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager Agent for WebSphere DataPower Appliance\nVersion 7.1 Fix Pack 3\n\nComponent ID: 5724SOADP\n\nFix Pack: 3, 7.1.0-TIV-ITM_WDP-FP0003\n\nDate: Revised January 8, 2016\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Notices", "1.0 General description\n=======================\nThis fix resolves the RFEs, APARs and defects listed in the \"Problems Fixed\"\nsection below. This fix also includes the superseded fixes listed in\nsection 2.6.\n\n2.0 Problems fixed\n==================\nThe following problems are addressed by this fix.\n\n2.1 APARs:\n----------\n\nN/A \n\n2.2 Defects\n--------------\n\nDefect: 61583\nAbstract: Increase java heap size and thread pool size.\nAdditional 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.\n\nTo enable the new maximum heap size, agent need to be restarted.", "To enable the new thread pool size:\n1. Re-config the instances.\n2. Modify the agent's config file and restart the agent instances.\n--For UNIX/LINUX\nModify the file \"bn_<instanceName>.config\", change the item \"CDP_DP_THREAD_POOL_SIZE\" to \"10\".\n--For Windows\nModify the file \"KBNENV_<instanceName>\", change the item \"CDP_DP_THREAD_POOL_SIZE\" to \"10\".\n\n2.3 Enhancements:\n-----------------\nEnhancement: RFE: 68385 \nAbstract: AMEX - Additional DataPower monitoring capabilities to monitor new capabilities in V6/V7 of firmware\nAdditional Information: \nPriority 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.\nPriority 1- IMS Connect - Can monitor up/down connection monitoring in SNMP files.\nLower priority - On Demand Router - Load balancing for Websphere. Can add monitoring for the network connections and load balancing work its doing.", "4 new attribute groups were introduced in FP3.\n-IMS_Connect:\nIMSConnect, Domain, Requests, Responses, RequestErrors, ResponseErrors\n4 queries:\n--IMS Connect Status: Use the IMSConnect attributes to obtain information about IMS connect status on the monitored DataPower appliance.\n--IMS Connect Requests Top 10: Provides the top 10 requests IMS Connect.\n--IMS Connect Responses Top 10: Provides the top 10 responses IMS Connect.\n--IMS Connect Request Errors Top 10: Provides the top 10 request errors IMS Connect.\n--IMS Connect Response Errors Top 10: Provides the the top 10 response errors IMS Connect.", "-Link_Aggregation:\nIndex, Name, MgmtName, MTU, Mode, Status, Primary, Active, LACPHashPolicy, LACPDURate, LACPSelectionPolicy, LACPAggregatorID, LACPNumPorts, LACPActorKey, LACPPartnerKey, LACPPartnerMAC, MIIStatus\n3 queries:\n--Link Aggregation Status: Use the Link Aggregation Status attributes to obtain information about Link Aggregation Status on the monitored DataPower appliance.\n--Link Aggregation Status No-link: Provides all No-link status for Link Aggregation.\n--Link Aggregation MIIStatus No-link: Provides all No-link MIIStatus for Link Aggregation.\n\n-Link_Aggregation_Member_Status:\nAggregateIndex, AggregateName, MgmtName, MemberIndex, MemberName, AggregatorID\n1 query:\n--Link Aggregation Member Status: Use the Link Aggregation Member Status attributes to obtain information about Link Aggregation Member Status on the monitored DataPower appliance.", "-Load_Balancer:\nGroup, Domain, Server, Port, Health, Weight, AdminState\n3 queries:\n--Load Balancer Status: Use the Load Balancer Status attributes to obtain information about Load Balancer status on the monitored DataPower appliance.\n--Load Balancer Groups Down: Provides all Down status groups for Load Balancer.\n--Load Balancer Groups Softdown: Provides all Softdown status groups for Load Balancer. \n\nEnhancement: (internal) Remove the UE dependance\nAbstract: Remove the UE dependance\nAdditional Information: Details as below:\nax is upgraded to 06.30.04.00\ngs is upgraded to 08.00.50.20\njr is upgraded to 07.07.00.00\nui is upgraded to 06.30.04.00\n\n2.4 Superseded fixes\n-------------------------\nNone.\n\n\n2.5 APARs and defects included from superseded fixes\n----------------------------------------------------\nNone.", "3.0 Architecture and prerequisites\n=================================\nSupported operating systems are shown in the system requirements reports \nfor the DataPower agent. You can access these reports here:\n\n- Prerequisites topic in Knowledge Center:\nhttp://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]\n\n- Software Product Compatibility Reports (SPCR)\nhttp://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]\n\n3.1 Prerequisites for this fix\n--------------------------------\nThere is no prerequisite level for this fix.\n\nBecause this fix is cumulative, it can be installed on any fix level \nfor the version, release, and modification level above the prerequisite.", "4.0 Image directory contents\n============================\nPhysical Part Number: ITCAM Apps Agent for WebSphere DataPower Appliance CBNR3ML\nElectronic Part Number: ITCAM Apps Agent for WebSphere DataPower Appliance CN8KBML\n\n5.0 Installation instructions\n=============================\nWhen this fix pack image is downloaded from the IBM Software Support website, \nthese rules apply:\n* You can install the fix pack only locally on a system that hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases already. Similar to other \nupgrade software, you can install the fix pack image locally on a \ncomputer where the product software is not already installed.\n* You can populate agents to the depot.\n* You can deploy agents remotely to existing or new installations.", "When this fix pack image is downloaded from Passport Advantage, these rules \napply:\n* You can install the fix pack locally on a system that hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases already.\n* You can install the fix pack locally on a system that does not host \na licensed copy of IBM Tivoli Monitoring for Databases already.\n* You can populate agents to the depot.\n* You can deploy agents remotely to existing or new installations.\n\n\n5.1 Before installing the fix\n-----------------------------\n- The prerequisites listed under section 3.1 entitled 'Upgrade prerequisites \nfor this fix' must be installed when upgrading.\n\n- For the purpose of this README, the <CANDLEHOME> symbol is the \nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\ibm\\itm'\non Windows systems.", "- If you customize the Extended Monitoring Agent for WebSphere DataPower Appliance \nbn.ini file on a UNIX system, back up this file before installing the fix. \nAfter this fix is installed, edit the latest bn.ini file and merge \nyour modifications into this bn.ini file.\n\n\n5.2 Local agent install and update (including silent installation)\n--------------------------------------------------------------\n1. Transfer the appropriate archive file to a \ntemporary directory on the system that contains the agent code to be \nupdated. For the purpose of this README, the <TEMP> symbol represents \nthe fully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter. \n\n2. Expand the archive file by using the tar command on UNIX systems or \nan unzip utility on Windows systems. This expansion creates a directory \nstructure that contains fixes for all supported platforms.", "3. Use the procedures in the \"IBM Tivoli Monitoring, Version 6.3 FP3\nInstallation and Setup Guide\" to install the agent.\n\n4. Use the procedures in the specific monitoring agent user's\nguide to complete the installation and configuration.\n\n\n5.3 Remote agent update and installation\n----------------------------------------\n1. Make sure that all potential targets of the remote deployment are\nrunning version 6.2.3 Fix Pack 4 or later of the OS monitoring \nagent.\n2. Transfer the appropriate archive file to \na temporary directory on the Tivoli Enterprise \nMonitoring Server system. For the purpose of this README, the \n<TEMP> symbol represents the fully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter. \n\n3. Expand the archive file by using the tar command on UNIX systems or an \nunzip utility on Windows systems. This expansion creates a directory structure\nthat contains fixes for all supported operating systems.", "4. To add the fix pack bundles to the remote deployment depot, use the\ntacmd addBundles command found in $CANDLEHOME/bin on UNIX systems\nor in %CANDLE_HOME%\\bin on Windows systems. For more information\nabout the tacmd addBundles command, see the \"IBM Tivoli\nMonitoring Command Reference.\"\n\nOn a UNIX system: if the fix was expanded to \n<TEMP>/<PARTNUMBER>:\n> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/<PARTNUMBER>/WINDOWS/Deploy -t bn -f\n> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/<PARTNUMBER>/unix -t bn -f \n\nwhere:\n-i is the directory that contains the deployment bundles to be\nadded to the depot.\n-t is the product code of the product to add, for example, bn \nrepresents the Extended Monitoring Agent for WebSphere DataPower Appliance\n-f shows that the actions are complete and confirmation is not requested", "On a Windows system: if the fix was expanded to \n<TEMP>/<PARTNUMBER>:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\<PARTNUMBER>\\WINDOWS\\Deploy -t bn -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\<PARTNUMBER>\\unix -t bn -f \n\nwhere:\n-i is the directory that contains the deployment bundles to be\nadded to the depot. \n-t is the product code of the product to add, for example, bn \nrepresents the Extended Monitoring Agent for WebSphere DataPower Appliance\n-f shows that the actions are complete and confirmation is not requested\n\n5. To login to the Tivoli Enterprise Monitoring server and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following tacmd commands. For more information about the\ntacmd login and updateAgent commands, see the \"IBM Tivoli\nMonitoring Command Reference.\"\n\nOn a UNIX system: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems", "The output shows the managed system name for the OS agent on the \nremote system to be installed/update. Use this value as the target of the\ntacmd addsystem/updateAgent command. \n\n> $CANDLEHOME/bin/tacmd addsystem -t bn \n-n <Managed system name>\n-p <Configration Info>\n\n> $CANDLEHOME/bin/tacmd updateAgent -t bn\n-n <Managed system name>\n-v 071003000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%/bin/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be installed/updated. Use this value as the target of the\ntacmd addsystem/updateAgent command. \n\n> $CANDLEHOME%\\bin\\tacmd addsystem -t BN \n-n <Managed system name>\n-p <Configration Info>", "> %CANDLE_HOME%\\bin\\tacmd updateAgent -t BN\n-n <Managed system name>\n-v 071003000\nNote:\n- The component (-t) for the updateAgent command is specified as \ntwo characters (bn), not three characters (kbn).\n- The node (-n) for the updateAgent command is the managed system\nname of the operating system (OS) agent to be updated. The \ntarget node for an updateAgent command is always an OS agent.\n- The component (-p) for the addsystem command is for agent's configuration info.\nHere is an example:\nINSTANCE=\"value\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_PORT=\"162\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_SECURITY_LEVEL=\"authPriv\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_USER_NAME=\"admin\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_AUTH_PROTOCOL=\"SHA\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_AUTH_PASSWORD=\"value\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_PRIV_PROTOCOL=\"DES\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_PRIV_PASSWORD=\"value\"\nDPS:<Managed_System_Name>.SOAP_HOST=\"value\"\nDPS:<Managed_System_Name>.DP_PORT=\"5550\"\nDPS:<Managed_System_Name>.DP_UID=\"admin\"", "DPS:<Managed_System_Name>.DP_PASSWORD=\"value\"\nDPS:<Managed_System_Name>.KBN_LOG_FILE=\"value\"\nDPC:<Managed_System_Name>.SNMP_VERSION=\"snmpV2\"\nDPC:<Managed_System_Name>.SNMP_HOST=\"value\"\nDPC:<Managed_System_Name>.SNMP_PORT=\"161\"\nDPC:<Managed_System_Name>.SNMP_COMMUNITY=\"public\"", "- The following error might occur with the updateAgent command on \nLinux and UNIX endpoints; however, the agent is successfully \nupdated. This error does not occur on Windows endpoints.\n\nKUICUA011I: Updating the bn agents.\nKUICUA015E: The updateAgent command did not complete because an\nerror occurred. Refer to the following error\nreturned from the server:\n\nThe monitoring server encountered an error while updating the\nmanaged system type.\n\nThe kuiras1.log file might provide more information about \nthis error. If you require further assistance to resolve the \nerror, contact IBM Software Support.\n\nA timeout occurred while waiting for an agent task to complete on\n{node name}.\n\nThe agent task did not complete within the configured \ntime out period.\n\nVerify that the target system is online. Increase the \ntime out value and try the operation again.", "5.4 Agent support update\n------------------------\nFix 7.1.0-TIV-ITM_WDP-FP0003 included changes to the agent\nsupport files that must be installed. If you installed these updates already, there are no additional installation\nsteps. Otherwise, use the following steps to update the Tivoli\nEnterprise Monitoring Server, Tivoli Enterprise Portal Server, or\nTivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file \nto the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli\nEnterprise Portal Servers, or Tivoli Enterprise Portal desktops. \n\n2. Expand the archive file by using the tar command on UNIX systems or an \nunzip utility on Windows systems. \n\n3. Use the procedures in the \"IBM Tivoli Monitoring, Version 6.3 FP3\nInstallation and Setup Guide.\"\n\n4. Use the procedures in the specific monitoring agent user's\nguide to complete the installation and configuration.", "5. If the Tivoli Enterprise Monitoring Server that is updated is remote (not a \nHub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise \nMonitoring Server.\n\n\n\n6.0 Additional installation information\n========================\n6.1 Installation instructions for agent baroc file\n-----------------------------------------------------\nThere are no updates to the baroc files included in this fix or\nany of the superseded fixes. No additional installation steps are\nrequired.\n\n6.2 Additional information on new configuration item \"KBN_SOMA_PROTOCOL\"\n------------------------------------------------------------------------\nA new configuration item \"KBN_SOMA_PROTOCOL\" is introduced to support TLS.\nThe value should be SSL/TLSv1/TLSv1.1/TLSv1.2. The default value is \"TLSv1\". \nIf you want to support TLSv1.1/TLSv1.2, please change it manually.\n\n1. For Windows platform:\nThe new item \"KBN_SOMA_PROTOCOL\" is in KBNENV and KBNENV_<instanceName>.", "a. Agent instance must be restarted to enable the new configuration change.\nb. The vaule of \"KBN_SOMA_PROTOCOL\" in KBNENV_<instanceName> will be updated to \nthe same vaule of \"KBN_SOMA_PROTOCOL\" in KBNENV while the instance is re-configured.\n\n2. For Linux/Unix platform:\nThe new items \"KBN_SOMA_PROTOCOL\" is in bn.ini and bn_<instanceName>.config.\n\na. Agent instance must be restarted to enable the new configuration change.\nb. The vaule of \"KBN_SOMA_PROTOCOL\" in bn_<instanceName>.config will be updated to \nthe same vaule of \"KBN_SOMA_PROTOCOL\" in bn.ini while the instance is re-configured.\n\n6.3 Verifying the update\n----------------------------\n1. To verify that the agent was updated correctly, use the tacmd command\nto view the current version of the agent after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer before viewing the agent version.", "For example:\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring\ninstallation directory, the default location is '/opt/IBM/ITM'.\n\n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser>\n-p <password>\n> $CANDLEHOME/bin/tacmd listSystems -t or\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli\nMonitoring installation directory, the default location\nis 'C:\\IBM\\ITM'.\n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser>\n-p <password>\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t bn\n\nNote: The component (-t) for the tacmd listSystems command is\nspecified as two characters (bn), not three characters (kbn).\n\nWhen the agent update is successful, the agent version is:\n07.10.03.00\n\nAfter the agent is restarted, you can also use the GUI to verify\nthat the agent was successfully updated.\n\nFor the agent on Windows systems, the version number is\n07.10.03.00.\nFor the agent on UNIX systems, the version number is\n07.10.03.00.", "2. To verify that the agent support files were updated correctly, use the\nkincinfo command on Windows systems or the cinfo command on\nLinux or UNIX systems. The sample output below shows the versions\nof the Tivoli Enterprise Portal Server, Tivoli Enterprise\nMonitoring Server, or Tivoli Enterprise Portal Desktop systems\nafter this fix has been successfully applied.\n\nNote: The date shown for the build might not be accurate. This\nis a known problem.\n\nOn UNIX or Linux systems:\n-------------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\n./cinfo -i\n\n*********** Fri Mar 18 13:23:02 CST 2011 ******************\nUser: root Groups: root bin daemon sys adm disk wheel\nHost name : myaixsys Installer Lvl:06.30.04.00\nCandleHome: /opt/IBM/ITM\n***********************************************************\n...Product inventory\n.\n.\n.\nMonitoring Agent for WebSphere DataPower Appliance update:", "bn ITCAM Agent for WebSphere DataPower Appliance\nlx8266 Version: 07.10.03.00\n\n\n.\n.\n.\nTivoli Enterprise Monitoring Server update:\n\nbn ITCAM Agent for WebSphere DataPower Appliance\ntms Version: 07.10.03.00\n\n.\n.\n.\n\nOn Windows systems:\n---------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\nFor example:\n> %CANDLE_HOME%\\InstallITM\\kincinfo -i\n\n\nkincinfo output:\n\n*********** Wednesday, January 8, 2014 3:46:34 PM ***********\nUser : Administrator Group : NA\nHost Name : IBM-8B96EE78239 Installer : Ver: 063004000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\n\n.\n.\n.\n[ Tivoli Enterprise Monitoring Server |\nTivoli Enterprise Portal Server and Tivoli Enterprise Portal Desktop] update:\nBN DataPower Agent Support\nWINNT Version: 07.10.03.00 Build: \n\nTivoli Enterprise Portal Server and Tivoli Enterprise Portal\nDesktop update:", "BN DataPower Agent Support\nWINNT Version: 07.10.03.00 Build: \n\n\nITCAM Agent for WebSphere DataPower Appliance update:\nBN ITCAM Agent for WebSphere DataPower Appliance\nWINNT Version: 07.10.03.00 Build: \n\nNote:\n\n- The date of the build that is shown might not be accurate. This\nproblem is known and is being addressed.\n- The kincinfo and cinfo command output examples in the sections\nthat follow show all components that you can update. If you install only \nsome of these components then only the components that you install are \nshown in the output of these commands.\n\n\n7.0 Known problems and workarounds\n==================================\nNone.\n\n8.0 Additional product information\n=================================\nNone.", "9.0 Notices\n===========\nThis information was developed for products and services offered in the United \nStates. IBM may not offer the products, services, or features discussed in this\ndocument in other countries. Consult your local IBM representative for information\non the products and services currently available in your area. Any reference to an\nIBM product, program, or service is not intended to state or imply that only that\nIBM product, program, or service may be used. Any functionally equivalent product,\nprogram, or service that does not infringe any IBM intellectual property right may\nbe used instead. However, it is the user's responsibility to evaluate and verify\nthe operation of any non-IBM product, program, or service.\n\nIBM may have patents or pending patent applications covering subject matter \ndescribed in this document. The furnishing of this document does not grant you\nany license to these patents. You can send license inquiries, in writing, to:", "IBM Director of Licensing\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\n\nThe following paragraph does not apply to the United Kingdom or any other\ncountry where such provisions are inconsistent with local law:\n\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION \n\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, \nINCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF \nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.\n\nSome states do not allow disclaimer of express or implied warranties in\ncertain transactions, therefore, this statement may not apply to you.", "Trademarks and service marks\n------------------------------------\nIBM, the IBM logo, and ibm.com are trademarks or registered trademarks\nof International Business Machines Corp., registered in many\njurisdictions worldwide. Other product and service names might be\ntrademarks of IBM or other companies. A current list of IBM trademarks \nis available on the Web at \"Copyright and trademark information\" at \nwww.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].\n\nMicrosoft, Windows, Windows NT, and the Windows logo are trademarks\nof Microsoft Corporation in the United States, other countries, or \nboth.\n\nJava and all Java-based trademarks are trademarks of Sun Microsystems, \nInc. in the United States, other countries, or both.\n\nUNIX is a registered trademark of The Open Group in the United States \nand other countries.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.", "Other company, product, or service names may be trademarks or service\nmarks of others.\n\nDOWNLOAD PACKAGE\n\n\n\nHOW CRITICAL IS THIS FIX?\nRFE:68385\n\n\n\nPROBLEMS SOLVED\nIntroduce new attribute groups:IMS_Connect, Link_Aggregation, Link_Aggregation_Member_Status and Load_Balancer.\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat 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] [ ]" ]

[ "A new configuration item \"KBN_SOMA_PROTOCOL\" is introduced to support TLS.\nThe value should be SSL/TLSv1/TLSv1.1/TLSv1.2. The default value is \"TLSv1\". \nIf you want to support TLSv1.1/TLSv1.2, please change it manually." ]

[ 18 ]

[ "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)\n\nQUESTION\n What levels of the IBM Developer for z Systems and Rational Developer for z Systems host and client are compatible? \n\nANSWER\nClient/Server Compatibility\n\n\n\nIn 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. \n\nIBM 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.", "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. \n\nRational 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. \n\nRational 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. \n\nRational 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.", "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. \n\nBasic Client/Server functionality includes: \n• Connecting to a z/OS System \n• Allocating z/OS Data sets \n• Creating a z/OS Project \n• Working with z/OS COBOL & Pl/I remote assets – edit, syntax check, submit, execute, debug and view the output \n• Basic CARMA functionality \n• Compatibility between service levels within a release is also supported (for example, using the v9.5 client to access a v9.5.1 server). \n\nAs 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. \n\nLikewise, 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. \n\nNote: Server enhancements that are client-dependent are not available to developers using earlier versions of the client.", "Client enhancements that are server-dependent are not available to developers accessing earlier versions of the server. \n\nFor Debugger,", "[/support/docview.wss?uid=swg21568844&amp;aid=1] \nDeveloper for System z v9.0.1.x (host) \nDeveloper for System z v9.1.x (host) \nDeveloper for System z v9.5.x (host) \nDeveloper for z Systems v14.0.x (host) \nDeveloper for z Systems v14.1.x (host) \nDebug for z Systems v14.0.x (host) \nDebug for z Systems v14.1.x (host) Debug Tool v12 Debug Tool v13 \nDeveloper for System z v9.0.1.x (Client) X [/support/docview.wss?uid=swg21568844&amp;aid=1] [/support/docview.wss?uid=swg21568844&amp;aid=1] [/support/docview.wss?uid=swg21568844&amp;aid=1] [/support/docview.wss?uid=swg21568844&amp;aid=1] [/support/docview.wss?uid=swg21568844&amp;aid=1] [/support/docview.wss?uid=swg21568844&amp;aid=1] X X \nDeveloper for System z v9.1.x (Client) X X X X X X X X X \nDeveloper for System z v9.5.x (Client) X X X X X X X [/support/docview.wss?uid=swg21568844&amp;aid=1] X \nDeveloper for System z v14.0.x (Client) X(1) X(1) X X X X X X X", "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.\n * \n * \n * \n * \n * \n * Workspace Data Compatibility\n * \n * \n * \n * \n * \n * \n *" ]

[ "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." ]

[ 0 ]

[ "IBM Reducing the size of Decision Warehouse trace when running scenario suites - United States TECHNOTE (FAQ)\n\nQUESTION\n When running a Decision Validation Service scenario suite in Rule Team Server can the optional trace be filtered to reduce its size ? \n\nANSWER\nIt 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. \n\nInstructions:", "1. Unjar the attached jrules-ssptrace-src.jar to a local directory \n 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 ) \n 3. Using a command line from the directory ./jrules-ssptrace execute: ant repackage-ssp \n 4. Deploy the customized SSP (available as the sspOutput file path) \n\n\njrules-ssptrace-src.jar [/support/docview.wss?uid=swg21438208&aid=2] [/support/docview.wss?uid=swg21438208&aid=1] \n\n\n\n\n\nCross 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" ]

[ "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." ]

[ 0 ]

[ "IBM Security Bulletin: Vulnerabilities in OpenSSL affect IBM MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178) - United States SECURITY BULLETIN\n\nSUMMARY\n 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.", "VULNERABILITY DETAILS\nCVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: 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.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)", "CVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: 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.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8 \n\nMaintenance versions 8.0.0.0 through 8.0.0.5 are affected. \n\nIBM MQ V9 \n\n9.0.0.0 only\n\nREMEDIATION/FIXES\nIBM MQ V8 \n\nApply fixpack 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100] \n\nIBM MQ V9", "Apply fixpack 9.0.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048059]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 13 March 2017: Original version published\n24 May 2017: Details for 9.0.0.1 added \n\n*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\nAccording 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. \n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22000474]" ]

[ "CVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: 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.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)" ]

[ 2 ]

[ "IBM Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM Dojo Toolkit is vulnerable to cross-site scripting and affects IBM Image Construction and Composition Tool. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2014-8917 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8917]\n\nDESCRIPTION: IBM Dojo Toolkit is vulnerable to cross-site scripting, caused by improper validation of user-supplied input.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99303 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99303] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Image Construction and Composition Tool v2.2.1.3 \nIBM Image Construction and Composition Tool v2.3.1.0 \nIBM Image Construction and Composition Tool v2.3.2.0", "REMEDIATION/FIXES\nThe solution is to apply the following IBM Image Construction and Composition Tool version fixes.\n\nUpgrade the IBM Image Construction and Composition Tool to the following fix levels or higher: \n\n\nFor IBM Image Construction and Composition Tool v2.2.1.3 * \n * \n * \n * \n * 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\n\n\nFor IBM Image Construction and Composition Tool v2.3.1.0 * \n * \n * \n * \n * 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", "For IBM Image Construction and Composition Tool v2.3.2.0 * \n * \n * \n * 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\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 17 June 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. \n\nDISCLAIMER\nAccording 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." ]

[ "CVEID: CVE-2014-8917 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8917]\n\nDESCRIPTION: IBM Dojo Toolkit is vulnerable to cross-site scripting, caused by improper validation of user-supplied input.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99303 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99303] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)" ]

[ 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\n\nSUMMARY\n 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. \n\nVULNERABILITY DETAILS\nPlease 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.\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Tivoli Network Manager 3.9, 4.1, 4.1.1 and 4.2\n\nREMEDIATION/FIXES\nRefer 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.", "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.. \nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "REFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 4 May 2017: Original Version Published \n\n*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\nAccording 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." ]

[ "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." ]

[ 0 ]

[ "IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS).", "VULNERABILITY DETAILS\nCVEID:CVE-2017-7805 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7805]\nDESCRIPTION: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.\nCVSS Base Score: 8.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/132749 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132749]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ Appliance 8.0 \n\nMaintenance levels between 8.0.0.0 and 8.0.0.7\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release", "Continuous delivery updates between 9.0.1 and 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ Appliance 8.0 \n\nApply 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]\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nApply 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]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 12 December 2017 Original version published \n\n*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\nAccording 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." ]

[ "CVEID:CVE-2017-7805 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7805]\nDESCRIPTION: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.\nCVSS Base Score: 8.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/132749 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132749]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)" ]

[ 1 ]

[ "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)\n\nPROBLEM(ABSTRACT)\n 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. \n\nRESOLVING THE PROBLEM\nFor 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].\nUse this document to find the following information: \n\n * Prerequisites for installing Tivoli Directory Server 6.3 on RHEL 6 systems. \n * Instructions to install Tivoli Directory Server 6.3 and upgrade to Tivoli Directory Server 6.3 fix pack 10. \n * Known issues and their work around.", "* #RHEL6PREREQPREREQUISITE FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 ON RED HAT ENTERPRISE LINUX 6 (RHEL 6) OPERATING SYSTEM\n \n * #INSTALLUPGRADEFP10INSTRUCTIONS FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 AND UPGRADING TO TIVOLI DIRECTORY SERVER VERSION 6.3 FIX PACK (FP) 10\n \n * #KIRHEL6KNOWN ISSUES AND THEIR WORK AROUND\n \n\nPREREQUISITE FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 ON RED HAT ENTERPRISE LINUX 6 (RHEL 6) OPERATING SYSTEM", "* The Korn shell (ksh) is required on Linux operating systems. \n * 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.\n 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 \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc", "* compat-libstdc++-33 and its dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n * compat-libstdc++-33 (install both 32 and 64-bit versions) and the dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n * compat-libstdc++-33 and its dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n \n * 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.", "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] \n * 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]", "#ibm-contentBack to top\n\nINSTRUCTIONS FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 AND UPGRADING TO TIVOLI DIRECTORY SERVER VERSION 6.3 FIX PACK (FP) 10", "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. \n 2. Upgrade DB2 V9.7 FP2 (provided with Tivoli Directory Server 6.3 GA ) to DB2 V9.7 FP4 level. \n 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.", "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]. \n * 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.", "Notes: * Tivoli Directory Server 6.3 installation using GUI installation program is not supported on RHEL 6. \n * Tivoli Directory Server 6.3 White pages installation using GUI installation program is not supported. \n * 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.\n\n\nSupported 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\nServer\nProxy server\nWeb Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9", "Red Hat Enterprise Linux (RHEL) Server 6 on x86-32 (x86/IA32) Not applicable Client\nServer\nProxy server\nWeb Administration tool V9.7 WSE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Server 6 on System z Client\nServer\nProxy server\nWeb Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Server 6 on POWER System (System i and System p) Client\nServer\nProxy server\nWeb Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Desktop 6 on x86-64 Client Not applicable Not applicable * GSKit 8.0.14.14* \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Desktop 6 on x86-32 Not applicable Client Not applicable * GSKit 8.0.14.14* \n * Java 1.6 SR9", "*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. \n\nSupported browsers for Web Administration tool: * Mozilla Firefox 3.5.10\n\n\n\n\n\n#ibm-contentBack to top\n\nKNOWN ISSUES AND THEIR WORK AROUND", "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. \n * 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. \n * 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.", "* 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.\n \n \n * 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:\n * \n * Required minimum level of libstdc++ is 1.3.1\n * \n * Actual version of the library file detected : CXXABI_1.3\n * \n * Check the following web site for the up-to-date system requirements of IBM DB2 9.7\n * \n * http://www.ibm.com/software/data/db2/udb/sysreqs.html [http://www.ibm.com/software/data/db2/udb/sysreqs.html]\n * \n * http://www.software.ibm.com/data/db2/linux/validate [http://www.software.ibm.com/data/db2/linux/validate]", "* \n * Aborting the current installation ...\n * \n * Run installation with the option \"-f sysreq\" parameter to force the installation", "#ibm-contentBack to top" ]

[ "Tivoli Directory Server 6.3 installation using GUI installation program is not supported on RHEL 6." ]

[ 8 ]

[ "IBM The off-line backup command could fail even when the database is quiesced on DB2 V10.1 and later. - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Offline-backup against the quiesced database failed with the error, SQL1035N.\nIt did not occur with V9.7. And it came to happen after migrating to V10.1 or later from V9.7. \n\nSYMPTOM\n \n\nThe following example shows this situation.\n\n1) In CLP 1 under the user having DBADM authority, execute quiesce database command on the database, sample.\n\n$ db2 connect to sample\n\nDatabase Connection Information\n\nDatabase server = DB2/AIX64 10.5.7\nSQL authorization ID = E105Q7A\nLocal database alias = SAMPLE\n\n\n$ db2 quiesce database immediate force connections\nDB20000I The QUIESCE DATABASE command completed successfully.\n$ db2 terminate\nDB20000I The TERMINATE command completed successfully.\n\n2) In CL 2 under the user having only connect privilege on sample database. \nRun the following shell repeating connect to sample..", "$ cat connect.sh\n#!/bin/sh\ncount=0\nwhile [ $count -lt 1000 ]; do\ndb2 connect to $db\ncount=`expr $count + 1`\ndone \n\ndb2insth $ sh -x loop.sh\n+ count=0\n+ [ 0 -lt 1000 ]\n+ db2 connect to sample\nSQL20157N User with authorization ID \"USER1\" failed to attach to a\nquiesced instance, or connect to a quiesced database or a database in a\nquiesced instance which is in the following quiesce mode: \"QUIESCE DATABASE\"\nSQLSTATE=08004\n+ + expr 0 + 1\ncount=1\n+ [ 1 -lt 1000 ]\n+ db2 connect to sample\n<snippet>\n\n* connect to sample continues to fail with the error, SQL20157N because the database, sample is quiesced.\n\n3) In CLP 1, execute the off-line backup command while executing the shell script under CLP2.\n\n$ db2 backup db sample\nSQL1035N The operation failed because the specified database cannot be\nconnected to in the mode requested. SQLSTATE=57019\n\n* The backup command failed. But this error does not happen on V9.7.", "For avoiding the error in offline-backup, use quiesce instance command with restricted access option.\n\n\n\nCAUSE\nBecause 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.\n\n\n\nRESOLVING THE PROBLEM\n \n\nPlease use quiesce instance command with the \"restricted access\" option instead of the quiesce database command. \n\nOr please retry off-line backup command after getting SQL1035N error.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21980030]" ]

[ "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." ]

[ 2 ]

[ "IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States SECURITY BULLETIN\n\nSUMMARY\n The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM WebSphere MQ Internet Pass-thru (MQIPT).", "VULNERABILITY DETAILS\nCVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nThe affected ciphersuite is available in all versions of IBM WebSphere MQ Internet Pass-thru (MQIPT) prior to 2.1.0.2\n\nREMEDIATION/FIXES\nSupportPac MS81: IBM WebSphere MQ Internet Pass-Thru\nUsers of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386].\n\nWORKAROUNDS AND MITIGATIONS\nNone.\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "REFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nReported to IBM by the WeakDH team at https://weakdh.org [https://weakdh.org] \n\nCHANGE HISTORY\n 11th June 2015: Original version published \n\n*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\nAccording 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.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962347]" ]

[ "Users of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2" ]

[ 2 ]

[ "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)\n\nPROBLEM\nOne may find the following in the configtrace.log file --- \n\n \nwps.dynamicui.transformationapp.webmod.xml to consolidated deployment \nscript \n[echo] Deploying consolidated web-app update script \n[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10056/wps/config/", "[xmlaccess] EJPXB0004I: Writing output file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc \ncessResult.xml \n[xmlaccess] EJPXB0002I: Reading input file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/config/work/consolida \ntedXMLAccess.xml \n[xmlaccess] EJPXB0019E: Server response indicates an error. For status \nand details of the XmlAccess error look at file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc \ncessResult.xml. \n[xmlaccess] EJPXB0019E: Server response indicates an error. For status \nand details of the XmlAccess error look at file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc \ncessResult.xml. \n\n\nfrom the consolidatedXMLAccessResult.xml file, it fails at --", "<!-- 55 [web-app com.ibm.wps.portlets.policystatus \nuid=com.ibm.workplace.policystatus.PolicyStatus] --> \n<request build=\"wp7001CF07_001_14\" type=\"update\" version=\"7.0.0.1\" \nxmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" \nxsi:noNamespaceSchemaLocation=\"PortalConfig_7.0.0.xsd\"> \n<status element=\"[web-app com.ibm.wps.portlets.policystatus \nuid=com.ibm.workplace.policystatus.PolicyStatus]\" result=\"failed\"> \n<message \nid=\"EJPXA0043E\">com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: \nAn error occurred while creating or updating the resource. [web-app \ncom.ibm.wps.portlets.policystatus \nuid=com.ibm.workplace.policystatus.PolicyStatus]</message> \n<message \nid=\"EJPPD0015E\">com.ibm.wps.command.CommandFailedException: EJPPD0015E: \nPortlet application manager failed when user xmlaccess scripting user \nexecuted command UpdateWebApplication. \nWrappedException is: \ncom.ibm.wps.pe.mgr.exceptions.AppServerWarUpdateException: EJPPH0044E: \nRedeployment of Web Module id in WAR file", "/opt/IBM/WebSphere/APP/WP7/wp_profile/PortalServer/deployed/appPolicySta \ntus.war (application display name: PA_Policy_Status) didi not complete \nsuccessfully when invoking the WebSphere Application Server \nadministration interface.</message> \n<message \nid=\"EJPPH0044E\">com.ibm.wps.pe.mgr.exceptions.AppServerWarUpdateExceptio \nn: EJPPH0044E: Redeployment of Web Module id in WAR file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/PortalServer/deployed/appPolicySta \ntus.war (application display name: PA_Policy_Status) didi not complete \nsuccessfully when invoking the WebSphere Application Server \nadministration interface.</message> \n<message \nid=\"EJPPH0001E\">com.ibm.wps.pe.mgr.exceptions.AppServerAdminListenerExce \nption: EJPPH0001E: Adding Notification Listener for MBean AppManagement \nfailed. (Application Name: PA_Policy_Status).</message>", "<message>com.ibm.websphere.management.exception.ConnectorException: \nADMC0009E: The system failed to make the SOAP RPC call: \nqueryNames</message> \n</status> \n</request> \n\n\nRESOLVING THE PROBLEM\nTo resolve the issue increase the was.notification.timeout to 1200 (seconds) in WP DeploymentService either from WebSphere Admin Console or Dmgr. \nIf the property is not listed under custom properties, please add the above property.\n\nRe-run the upgrade-profile task to proceed with migration." ]

[ "To resolve the issue increase the was.notification.timeout to 1200 (seconds) in WP DeploymentService either from WebSphere Admin Console or Dmgr. \nIf the property is not listed under custom properties, please add the above property.\n\nRe-run the upgrade-profile task to proceed with migration." ]

[ 4 ]

[ "IBM MQ 7.1 and later: How to remove a channel authentication record (CHLAUTH) - United States TECHNOTE (FAQ)\n\nQUESTION\n You have added a channel authentication record into a WebSphere MQ 7.1 or later queue manager:\n\nSET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL) ACTION(ADD)\nAMQ8877: WebSphere MQ channel authentication record set.\n\nThen you display it:\n\nDISPLAY CHLAUTH(*) TYPE(USERMAP)\n1 : DISPLAY CHLAUTH(*) TYPE(USERMAP)\nAMQ8878: Display channel authentication record details.\nCHLAUTH(*) TYPE(USERMAP)\nCLNTUSER(testuser) USERSRC(CHANNEL)\n\nNow you want to remove it and you try executing the following runmqsc command which you constructed using copy and paste from the above output:\n\nDELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)\n3 : DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)\n\nYou get the following error:\n\nAMQ8405: Syntax error detected at or near end of command segment below:-\nDELETE 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:\n\nSET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)\n19 : SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)\n\nBut you get the following error:\n\nAMQ8884: Channel authentication record not found.\n\nYou 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?", "CAUSE\nSee the following section of the MQ 7.1 documentation:\nWebSphere MQ > Administering > Administering local WebSphere MQ objects > Performing local administration tasks using MQSC commands\nWebSphere MQ object names [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/fa11060_.htm]\n+ Case-sensitivity in MQSC commands\nMQSC 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. \n\nWhen 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:\nCLNTUSER(TESTUSER)\nAnd in this case, there is no record for the user TESTUSER (the record is for 'testuser').", "ANSWER\nNOTICE that the userid mentioned in the CLNTUSER field of the output of the DISPLAY CHLAUTH command is NOT surrounded by single quotes. \n\nHowever, you MUST include the single quotes when specifying the value during an ACTION(REMOVE):\n\nSET CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)\n1 : set CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)\nAMQ8877: WebSphere MQ channel authentication record set.\n\n\n++ Example of record with more attributes\n\nLet's examine the case when a record has more attributes, such as:\n\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(ADD)\nAMQ8877: WebSphere MQ channel authentication record set.\n\ndisplay CHLAUTH(MY.CHANNEL)\n9 : display CHLAUTH(MY.CHANNEL)\nAMQ8878: Display channel authentication record details.\nCHLAUTH(MY.CHANNEL) TYPE(USERMAP)\nDESCR( ) CUSTOM( )\nADDRESS(*) CLNTUSER(client_1)\nMCAUSER(user_1) USERSRC(MAP)", "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:\n\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') ACTION(REMOVE)\nAMQ8884: Channel authentication record not found.\n\nYou try the original command that created the record, but changing the action to REMOVE:\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(REMOVE)\nAMQ8885: Parameter not allowed for this action on a channel authentication record.\n\nThe attribute USERSRC is not a valid parameter for the REMOVE action (see table below).\nTherefore, by removing this attribute, then the following command worked successfully to remove the record:\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('mengano') ADDRESS('*') ACTION(REMOVE) \nAMQ8877: WebSphere MQ channel authentication record set.", "See:\nWebSphere MQ 8.0.0 > IBM MQ > Reference > Administration reference > MQSC reference > The MQSC commands > \nSET CHLAUTH [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q086630_.htm]\n.\n+ begin excerpt\n.\nUsage notes\nThe following table shows which parameters are valid for each value of ACTION:\n.\nAction \nParameter ADD or REMOVE REMOVEALL\nREPLACE\nCHLAUTH X X X \nTYPE X X X \nCMDSCOPE X X X \nACTION X X X \nADDRESS X X\nADDRLIST X X \nCHCKCLNT X \nCLNTUSER X X \nMCAUSER X \nQMNAME X X \nSSLCERTI X X \nSSLPEER X X \nUSERLIST X X \nUSERSRC X \nWARN X \nDESCR X \n.\n+ end excerpt\n\n\nAdditional Search Words: uppercase lowercase upper lower case\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ MQSeries" ]

[ "you MUST include the single quotes when specifying the value during an ACTION(REMOVE):" ]

[ 3 ]

[ "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)\n\nPROBLEM(ABSTRACT)\n Receiving SQL1763N error with Reason Code 11 while running \"Alter Tablespace\" command to reclaim unused storage space against DMS or automatic storage tablespaces. \n\nSYMPTOM\nFollowing reasons apply: \n\n * 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. \n * Trying to alter a SMS tablespace as this feature is not supported on SMS tablespaces. \n\n\nExample testcase on a TEMPSPACE1 SMS tablespace.", "* \n * \n * 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 \n * \n \n\n\nDIAGNOSING THE PROBLEM\nMON_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: \ndb2 \"SELECT varchar(tbsp_name, 30) as tbsp_name, tbsp_type, RECLAIMABLE_SPACE_ENABLED FROM TABLE(MON_GET_TABLESPACE('',-2))\" \n\n \n\nSnippet of the output: \n\n \n\nTBSP_NAME TBSP_TYPE RECLAIMABLE_SPACE_ENABLED\n----------------- ----------- -------------------------\nSYSCATSPACE DMS 1\nTEMPSPACE1 SMS 0\nUSERSPACE1 DMS 1 \n\nIf 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.", "RESOLVING THE PROBLEM\nTo 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. \n\n \n\n * \n * \n * \n * \n * \n\n\nNote: \nTablespaces migrated from DB2 V9.1/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature. RELATED INFORMATION\n Reclaimable storage [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html]" ]

[ "To use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later." ]

[ 2 ]

[ "IBM Levels of JRE and GSkit bundled with IBM MQ - United States RELEASE NOTES\n\nABSTRACT\n 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. \n\nCONTENT", "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 \nIBM 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", "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)", "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", "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", "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", "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", "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", "PRODUCT ALIAS/SYNONYM\n WMQ MQ" ]

[ "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." ]

[ 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)\n\nQUESTION\n The Filter Analyzer reports the error:\n\n\"rule includes an unsupported expression\"\n\nwhen comparing two ObjectServer fields against each other and/or a field against GetDate within an EventReader Filter", "CAUSE\nThis is a limitation in the functionality of the Filter Analyzer in Impact and can produce the log file message:\nWARN [EventFilter] Could not consolidate filters. Please check if the filter expressions are valid. java.util.concurrent.ExecutionException\n\n\n\n\nANSWER\nIn the EventReader properties file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[EventReaderName].props\n\nwhere [ImpactServerName] is the name of the ImpactServer (NCI by default) and [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader). Add the property:\n\nimpact.[EventReaderName].consolidatefilters=false\n\nwhere, again, [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader).\n\nOnce this property has been added to the file an ImpactServer restart is required to enable it.", "In a Clustered environment one would have to stop the Secondary ImpactServer(s) first, then stop and restart the Primary ImpactServer and then restart the Secondary ImpactServer(s) to ensure that the property is not overwritten and is distributed to each ImpactServer in the Cluster.\n\nPlease note that this issue relates to the use of the Filter Analyzer and does not impinge upon the EventReader ability to parse the Filter.\n\nIf you are unable to see the Filter being applied in the outgoing SQL for the EventReader please read the TechNote \"EventReader Filters not applied to SQL select statement\" [link below].\n\n\nRELATED INFORMATION\n EventReader Filters not applied to SQL select statement [http://www-01.ibm.com/support/docview.wss?uid=swg21566480]" ]

[ "In the EventReader properties file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[EventReaderName].props\n\nwhere [ImpactServerName] is the name of the ImpactServer (NCI by default) and [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader). Add the property:\n\nimpact.[EventReaderName].consolidatefilters=false\n\nwhere, again, [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader).\n\nOnce this property has been added to the file an ImpactServer restart is required to enable it.\n\nIn a Clustered environment one would have to stop the Secondary ImpactServer(s) first, then stop and restart the Primary ImpactServer and then restart the Secondary ImpactServer(s) to ensure that the property is not overwritten and is distributed to each ImpactServer in the Cluster." ]

[]

[ "IBM Security Bulletin: MQSISTOP/STARTMSGFLOW commands with unauthorized user succeed affects IBM WebSphere Message Broker and IBM Integration Bus (CVE-2015-5011) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n MQSISTOP/STARTMSGFLOW commands with unauthorized user succeed affecting IBM WebSphere Message Broker and IBM Integration Bus \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-5011 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5011]\nDESCRIPTION: IBM Integration Bus could allow a local user to start and stop a service that they should not have access to.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/106403 [https://exchange.xforce.ibmcloud.com/vulnerabilities/106403] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V9 \n\n WebSphere Message Broker V8\n\nREMEDIATION/FIXES", "Product VRMF APAR Remediation/Fix IBM Integration Bus V9 PI28139 The APAR is available in fix pack 9.0.0.4 \nhttps://www-304.ibm.com/support/docview.wss?rs=849&uid=swg24040542 [https://www-304.ibm.com/support/docview.wss?rs=849&uid=swg24040542] WebSphere Message Broker\nV8 PI28139 The APAR is available in fix pack 8.0.0.6\nhttp://www-01.ibm.com/support/docview.wss?rs=849&uid=swg24040259 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg24040259] WORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www-03.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 06-Oct-2015 - Original version Published/CVSS version changed to V3", "*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. \n\nDISCLAIMER\nAccording 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.", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB" ]

[ "CVEID: CVE-2015-5011 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5011]\nDESCRIPTION: IBM Integration Bus could allow a local user to start and stop a service that they should not have access to.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/106403 [https://exchange.xforce.ibmcloud.com/vulnerabilities/106403] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)" ]

[ 0 ]

[ "IBM Security Bulletin: API Connect is affected by a cross-site scripting vulnerability \nCVE-2018-1382 - United States SECURITY BULLETIN\n\nSUMMARY\n API Connect has addressed the following vulnerability. \n\nIBM API Connect is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality, potentially leading to credentials disclosure within a trusted session. \n\n\n\nVULNERABILITY DETAILS", "CVEID:CVE-2018-1382 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1382]\nDESCRIPTION:IBM API Connect is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality, potentially leading to credentials disclosure within a trusted session.\nCVSS Base Score: 5.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/138079 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138079]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected API Connect Affected Versions IBM API Connect 5.0.0.0-5.0.6.4 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0-5.0.8.1 REMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation / First Fix IBM API Connect\n\n5.0.0.0-5.0.6.4 5.0.6.5 LI79885 Addressed in IBM API Connect V5.0.6.5.", "Management Server and Developer Portal are impacted.\n\nFollow this link and find the \"APIConnect_Management\" and\n\"APIConnect-Portal\" packages:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.4&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\n5.0.7.0-5.0.7.2 5.0.8.2 LI79885 Addressed in IBM API Connect V5.0.8.2.\n\nManagement Server and Developer Portal are impacted.\n\nFollow this link and find the \"APIConnect_Management\" and\n\"APIConnect-Portal\" packages:", "https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.1&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] IBM API Connect\n\n5.0.8.0-5.0.8.1 5.0.8.2 LI79885 Addressed in IBM API Connect V5.0.8.2.\n\nManagement Server and Developer Portal are impacted. \n\nFollow this link and find the \"APIConnect_Management\" and\n\"APIConnect-Portal\" packages:", "https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.1&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 30 January 2018: original document 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. \n\nDISCLAIMER\nAccording 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." ]

[ "CVEID:CVE-2018-1382 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1382]\nDESCRIPTION:IBM API Connect is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality, potentially leading to credentials disclosure within a trusted session.\nCVSS Base Score: 5.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/138079 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138079]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N)" ]

[ 1 ]

[ "IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers - United States wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server. WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows.\n\nNotice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory.\nReference:\nUsing the WASServiceHelper utility to create Windows services for application servers\nhttps://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]", "See DeveloperWorks article for detailed information: (Link at the bottom of this document) \n\nSYMPTOM\nCreating and removing a WebSphere service in Windows is confusing and error prone.\n\n\nCAUSE\nThis application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\n\n\n\n 1. Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors.", "[/support/docview.wss?uid=swg21397335&amp;aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf] \n\nNote: This also creates an entry in the WASServiceCmd.log in the current directory which contains the actual WASService.exe command used to create the service. \n\nExample of a log entry: \n\n[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\" \n-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"\n-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"\n-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" \n-startType manual \n-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2]", "Notice: Some browsers are having trouble downloading this file and getting docview.wss instead. Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip). You can now access the utility. \nSee DeveloperWorks article for more information: \nThe Support Authority: Take the confusion (and errors) out of creating Windows services for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/techjournal/1005_supauth/1005_supauth.html] \n\n\nSee TroubleShooting: WebSphere Application Server (Windows Services) problems for V6.0, V6.1 and V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21232884] if you are still having a problem with Windows services." ]

[ "Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line." ]

[ 1 ]

[ "IBM Maximo fails to start with error BMXAA4087E - United States TPAESCCD; Maximo; start; BMXAA4087E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n BMXAA4087E - The MAXMESSAGE value for group login and key username could not be retrieved. \n\nSYMPTOM\n[ERROR] BMXAA6497E - A message for group login and key username could not be found.\ncom.ibm.db2.jcc.c.SqlException: No authorized routine named \"ISNULL\" of type \"FUNCTION\" having compatible arguments was found.\nat com.ibm.db2.jcc.c.fg.e(fg.java:1596)\nat com.ibm.db2.jcc.c.fg.a(fg.java:1206)\nat com.ibm.db2.jcc.b.gb.g(gb.java:140)\nat com.ibm.db2.jcc.b.gb.a(gb.java:39)\nat com.ibm.db2.jcc.b.w.a(w.java:34)\nat com.ibm.db2.jcc.b.vb.g(vb.java:139)\nat com.ibm.db2.jcc.c.fg.n(fg.java:1177)\nat com.ibm.db2.jcc.c.fg.a(fg.java:1832)\nat com.ibm.db2.jcc.c.fg.a(fg.java:473)\nat com.ibm.db2.jcc.c.fg.executeQuery(fg.java:457)\nat psdi.server.MXServer.getMessage(MXServer.java:5362)\nat psdi.server.MXServer.getMessages(MXServer.java:5538)", "ENVIRONMENT\nIBM DB2 database\n\nDIAGNOSING THE PROBLEM\nConnect to database back end and check the result of this query :-\n\n\nselect propvalue from maximo.maxpropvalue where propname='mxe.db.format.nullvalue'; \n\nIf you are using DB2 database, the result should be 'COALESCE'.\n\n\nRESOLVING THE PROBLEM\nFor IBM DB2, the value is COALESCE, and you cannot change the default value. \n\nFor Oracle, the value is NVL, and you cannot change the default value.\nFor SQL Server, the value must be set to ISNULL.\n\nMake sure MXServer is stopped. Connect to database back end and update mxe.db.format.nullvalue by running following query :- \n\nupdate maximo.maxpropvalue set propvalue='COALESCE' where propname='mxe.db.format.nullvalue'; \n\nStart MXServer again." ]

[ "For IBM DB2, the value is COALESCE, and you cannot change the default value. \n\nFor Oracle, the value is NVL, and you cannot change the default value.\nFor SQL Server, the value must be set to ISNULL.\n\nMake sure MXServer is stopped. Connect to database back end and update mxe.db.format.nullvalue by running following query :- \n\nupdate maximo.maxpropvalue set propvalue='COALESCE' where propname='mxe.db.format.nullvalue'; \n\nStart MXServer again." ]

[ 1 ]

[ "IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13)", "Support for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \n\nNOTE: There's a known issue with some of the earlier release of Mac High Sierra system (13.0 and 13.1 beta version). \nThe top menu of SPSS 25 may disappear if the Mac OS system is set to Non-English. \nThe official MacOSX 10.13.1 version do not have this issue. So, if you encountert this issue you need to update your Mac OS version to latest official 10.13.1 build from Apple. \n\n \n\nB) Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra.", "C) Apple Macintosh OSX El Capitan (10.11) \n\nSupport for IBM SPSS Statistics 24. Please see the Release notes - IBM SPSS Statistics 24.0 [http://www-01.ibm.com/support/docview.wss?uid=swg27047057] for known issues on Macintosh. \n\nFull documentation including installation material provided in different languages and manuals for release 24 can be found on IBM SPSS Statistics 24 Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg27047033] webpage. \n\n \n\nAlso, Support for IBM SPSS Statistics 23. Note: if you want to install on El Capitan, please refer to technote 1970391 [http://www-01.ibm.com/support/docview.wss?uid=swg21970391] \n\n \n\nD) Apple Macintosh OSX Yosemite (10.10) \n\nSupport for IBM SPSS Statistics 24, IBM SPSS Statistics 23 and IBM SPSS Statistics 22", "Note: Mac OSX 10.10 (Yosemite) was released on Thursday, October 16th 2014 by Apple after Statistics 22 was released. If you like to use Statistics 22 on Yosemite you need to install Statistics 22 Fixpack 2 as well. Statistics 22 FixPack 2 and release Statistics 23 are fully tested on Yosemite OSX 10.10. So if you like to run Statistics 22 on Yosemite please install Statistics 22 FixPack 2 and also read the section below: \n\n**** \n\nIn some instances it can be necessary to re-install the legacy Apple Java 6 on 10.10 for the use of Statistics 22 FixPack 2 on this platform\n\nDownload and re-install Apple Java 6", "- After you upgraded your Apple Mac OSX from a previous release to 10.10, Apple Java 6 may no longer exists on your upgraded system. If you then launch Statistics 22 which is an application that relies on Java 6, it can happen, the Mac OS pops up a dialog box stating Java 6 was requested, but none is present.\n- The Java dialog has a \"More Info\" button, which when clicked opens a browser to an Apple Tech Support page for Apple Java 2014-001. A download link is provided:\nhttp://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572]\n- Click on the download link and a DMG containing the Java 6 installer is downloaded.\n- Then you open the Java DMG, double click on the Java installer, follow the prompts and complete the installation of Java 6.\n\n******* \n\n \n\nE) Apple Macintosh OSC Mavericks (10.9) \n\nSupport for IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n***", "Note: IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks). However, Statistics 22 can be installed on Mac OSX 10.9 if you install Apple Java SE 6 (1.6.0_65) on OS X 10.9 first before you install Statistics 22. Please see http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572] for download. \n\n**** \n\nF) Apple Macintosh OSX Mountain Lion (10.8) \n\nSupport for IBM SPSS Statistics 22 and IBM SPSS Statistics 21 \n\n**** \n\nG) Apple Macintosh OSX Lion (10.7) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nH) Apple Macintosh OSX Snow Leopard (10.6) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nOlder SPSS Statistics releases 18 and 19 and 20: \n\nPlease note that SPSS Statistics releases 18, 19 and 20 are no longer supported by IBM. Please contact IBM Sales department to renew your contracts.", "RELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]" ]

[ "Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra." ]

[ 1 ]

[ "IBM Collect troubleshooting data for the IBM Business Process Manager products - United States install; mustgather; bpm; v7.5; collect; logs; troubleshooting; v8.5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are having a problem with the IBM Business Process Manager (BPM) products. You would like to know what information you must collect (MustGather) so that the IBM Business Process Manager Support team can diagnose your problem. If you gather this documentation before contacting support, it will expedite the troubleshooting process and save you time. \n\nDIAGNOSING THE PROBLEM\nStart the problem analysis:", "* Review the SystemOut.log file at install_​​root​​/profiles/​​profile​​_​​name​​/​​logs​​/server​​_​​name and look for error messages that have been logged around the time stamp when the issue showed up. \n * Search the [http://www.ibm.com/software/htp/cics/tserver/support/]appropriate product support site from the following list for known problems using symptoms such as the message number and error codes: * IBM Business Process Manager Advanced [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Advanced] \n * IBM Business Process Manager Standard [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Standard] \n * IBM Business Process Manager Express [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Express]", "* IBM BPM Advanced Pattern for Red Hat Enterprise Linux Server [http://www.ibm.com/support/entry/portal/search_results?sn=spe&q=&filter=DC.Subject:SSV2LR]\n \n \n * Use theIBM Support Assistant [http://www.ibm.com/software/support/isa/]to search for known problems in the product documentation, forums, technotes, and so on. \n * Search the IBM dW Answers [https://developer.ibm.com/answers/topics/bpm/] or IBM Business Process Manager developerWorks community [http://www.ibm.com/developerworks/forums/forum.jspa?forumID=2382] pages for known problems. \n * If a fix is found that fits the symptoms, search Fix Central [http://www.ibm.com/support/fixcentral/] for the appropriate interim fix.", "RESOLVING THE PROBLEM\nCollect the following troubleshooting data if you need help from IBM Business Process Manager Support to resolve the problem. \n\n\n\nGENERAL DIAGNOSTIC INFORMATION\n\nEnvironment description:", "* IBM Business Process Manager product and version * In Business Process Manager V7.5.x, run the versionInfo -maintenancePackages command from the bin directory of your IBM Business Process Manager product installation and redirect the output to a file. \n * In Business Process Manager V8.x, run the versionInfo -fixpacks -ifixes command from the bin directory of your IBM Business Process Manager product installation and redirect the output to a file.\n \n \n * Operating system and version \n * Database vendor and version \n * Information about other involved software \n * Production / Test / QA environment \n * If you are running in a cluster, describe the topology that you have in place. If you have a topology diagram, provide it including host names, ports, and so on. \n * Is your IBM Business Process Manager product running in a virtual machine? If yes, provide more details on the software that you are using and its version.", "Detailed problem description: \nProvide a precise description of the issue and add every detail that might be related. \nThis could include: * Which symptoms do you see? \n * Which component or application is involved? \n * Do you see any error messages? \n * What is the time stamp when the problem occurs? \n * Did the current scenario work previously? If yes, what has been changed? \n * Is this issue reproducible at will? How often does this problem occur? Do you see any indicators on why this happens? \n * Provide screen shots if applicable (if an error message is not shown or if the specific error is not seen in the log files, and so on)\n\n\nAdditional details needed: \nProvide the complete log directories: * install​​_​​root/​​profiles/profile​​_​​name​​/​​logs​​/server​​_​​name \n * install_​​root/​​profiles/profile​​_​​name/​logs​​/ffdc", "Provide the configuration files: * TeamWorksConfiguration.running.xml file, which is located in the following locations: * Process Center profile:\n install_​​root/​​profiles/profile​​_​​name/config/cells/cell_name/nodes/\n node_name/servers/server_name/process-center \n * Process Server profile:\n install_​​root​​/​​profiles/profile​​_​​name/config/cells/cell_name/nodes/\n node_name/servers/server_name/process-server\n \n \n * The complete install_​​root/​​profiles/profile​​_​​name/configdirectory if requested by the support team.\n\n\nTest case: * Simplified and isolated test case without any custom dependencies and without access to external customer systems \n * *.twx export from IBM Process Designer \n * Project Interchange (PI) and enterprise archive (EAR) file from the involved Advanced Integration Services, if applicable \n * Exact, detailed steps to reproduce the problem, including timestamp of the problem occurrence.", "If you have not provided it already, supply the business impact this issue is having on your company, including:​ * Any upcoming deadlines and dates​ \n * Any realized or potential effect on customers​\n\nCOMPONENT-SPECIFIC DIAGNOSTIC INFORMATION", "* Advanced Integration Service (AIS) [http://www.ibm.com/support/docview.wss?uid=swg21669894] [http://www.ibm.com/support/docview.wss?uid=swg21618716] \n * Application deployment [http://www.ibm.com/support/docview.wss?uid=swg21618716] \n * Application deployment (EAR file / Advanced content) [http://www.ibm.com/support/docview.wss?uid=swg21959495] \n * Business Process Choreographer (BPC) [http://www.ibm.com/support/docview.wss?uid=swg21270939] \n * Business Process Definition (BPD) [http://www.ibm.com/support/docview.wss?uid=swg21680148] \n * IBM Business Process Manager Advanced Pattern for AIX and Linux [http://www.ibm.com/support/docview.wss?uid=swg21642204] \n * IBM Business Process Manager document store [http://www.ibm.com/support/docview.wss?uid=swg21640607] (for IBM Business Process Manager V8.5.x) \n * IBM Business Process Manager on Cloud [http://www.ibm.com/support/docview.wss?uid=swg21664113] \n * Business Rules [http://www.ibm.com/support/docview.wss?uid=swg21663864]", "* Business Space [http://www.ibm.com/support/docview.wss?uid=swg21578516] \n * Coaches [http://www.ibm.com/support/docview.wss?uid=swg21666382] \n * Common Event Infrastructure (CEI) [http://www.ibm.com/support/docview.wss?uid=swg21670009] \n * Connection to Process Center [http://www.ibm.com/support/docview.wss?uid=swg21666261] \n * Data Map, Data Object and XML Serialization [http://www.ibm.com/support/docview.wss?uid=swg21664250] \n * Database [http://www.ibm.com/support/docview.wss?uid=swg21610455] \n * Dynamic Event Framework (DEF) [http://www.ibm.com/support/docview.wss?uid=swg21679783] \n * Installation and upgrade [http://www.ibm.com/support/docview.wss?uid=swg21506937] \n * Integration between IBM Business Process Manager (BPM) and IBM ILOG or IBM WebSphere Operational Decision Management [http://www.ibm.com/support/docview.wss?uid=swg21644787] \n * Message import and export (MQ and JMS related) [http://www.ibm.com/support/docview.wss?uid=swg21667053]", "* Migration [http://www.ibm.com/support/docview.wss?uid=swg21663802] \n * Out-of-memory, hangs, crashes [http://www.ibm.com/support/docview.wss?uid=swg21666135] \n * Performance [http://www.ibm.com/support/docview.wss?uid=swg21611603] \n * Performance Data Warehouse [http://www.ibm.com/support/docview.wss?uid=swg21609319] \n * Process Admin console [http://www.ibm.com/support/docview.wss?uid=swg21661316] \n * Process Designer [http://www.ibm.com/support/docview.wss?uid=swg21611598] \n * Process Inspector [http://www.ibm.com/support/docview.wss?uid=swg21666266] \n * Process Portal [http://www.ibm.com/support/docview.wss?uid=swg21656267] \n * REST API [http://www.ibm.com/support/docview.wss?uid=swg21666278] \n * Secure Sockets Layer (SSL), Java Secure Socket Extension (JSSE) or Java Cryptography Extensions (JCE) [http://www.ibm.com/support/docview.wss?uid=swg21162961] \n * Security [http://www.ibm.com/support/docview.wss?uid=swg21609418]", "* Service Component Architecture (SCA), Service Integration Bus (SIB) or Failed Event Manager (FEM) [http://www.ibm.com/support/docview.wss?uid=swg21669111] \n * Undercover Agent (UCA) [http://www.ibm.com/support/docview.wss?uid=swg21660915] \n * Web services [http://www.ibm.com/support/docview.wss?uid=swg21593461]", "Note: In the previous information, the install_root refers to the location in which you installed the product. The profile_name is the name of the profile that is specific to your configuration. The cell_name, node_name and server_name are the names of the cell, the node and the server that are specific to your configuration. \nAUTOMATIC DATA COLLECTION VIA THE BPM DATA COLLECTOR\n\nYou can also use the BPM Data Collector [http://www.ibm.com/support/docview.wss?uid=swg21641516] to automatically collect basic MustGather data like logs, version info and so on. Verify the created package if any requested information is missing prior to sending it to IBM Support for problem analysis.\nThis tool can be used with IBM Business Process Manager V8.0.1 Fix Pack 3 and with IBM Business Process Manager V8.5.x.", "RELATED INFORMATION\n Exchange data with IBM Technical Support [http://www.ibm.com/de/support/ecurep/index.html]\nBPM Advanced - System requirements [http://www.ibm.com/support/docview.wss?uid=swg27023005]\nBPM Standard - System requirements [http://www.ibm.com/support/docview.wss?uid=swg27023007]\nBPM Express - System requirements [http://www.ibm.com/support/docview.wss?uid=swg27023008]\nRecommended fixes for IBM BPM [http://www.ibm.com/support/docview.wss?uid=swg27022299]\nConfiguration file overview [http://www.ibm.com/support/docview.wss?uid=swg21439614]\nMustGather for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21145599]\nTroubleshooting data: WebSphere Process Server [http://www.ibm.com/support/docview.wss?uid=swg21239895]\nTroubleshooting data: IBM Integration Designer [http://www.ibm.com/support/docview.wss?uid=swg21566742]\nTroubleshooting data: WebSphere ESB [http://www.ibm.com/support/docview.wss?uid=swg21268473]", "Troubleshooting data: WebSphere Lombardi Edition [http://www.ibm.com/support/docview.wss?uid=swg21440086]\nTroubleshooting data: IBM Business Monitor [http://www.ibm.com/support/docview.wss?uid=swg21498803]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21620654]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21634198]", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Documentation AIX, Linux, Solaris, Windows 8.5.7, 8.5.6, 8.5.5, 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Express Documentation Linux, Windows 8.5.7, 8.5.6, 8.5.5, 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server Documentation Linux 8.5.0.1, 8.0.1, 8.0 Business Integration IBM Business Process Manager Advanced Pattern on AIX Documentation AIX 8.0.1 \nPRODUCT ALIAS/SYNONYM\n BPM" ]

[ "Collect the following troubleshooting data if you need help from IBM Business Process Manager Support to resolve the problem." ]

[ 3 ]

[ "IBM Security Bulletin:IBM Integration Bus is affected by deserialization RCE vulnerability in IBM WebSphere JMS Client - United States IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere MQ V9.0 libraries are shipped in IBM Integration Bus and hence IBM Integration Bus is vulnerable to IBM WebSphere MQ JMS client deserialization RCE vulnerability.\n\n\n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2016-0360 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0360]\nDESCRIPTION: IBM Websphere MQ JMS client provides classes that deserialize objects from untrusted sources which could allow a malicious user to execute arbitrary Java code by adding vulnerable classes to the classpath. \nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/111930 [https://exchange.xforce.ibmcloud.com/vulnerabilities/111930] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)", "Please consult the security bulletin IBM WebSphere MQ JMS client deserialization RCE vulnerability [https://www-01.ibm.com/support/docview.wss?uid=swg21983457] for more details\n.\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V10.0.0.0 to V10.0.0.9, and V9.0.0.0 to V9.0.0.8\n\nREMEDIATION/FIXES", "Product VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0 to V10.0.0.9 IT21160 The APAR is available in fix pack 10.0.0.10\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043943 [http://www-01.ibm.com/support/docview.wss?uid=swg24043943] IBM Integration Bus V9.0.0.0 to V9.0.0.8 IT21160 The APAR is available in fix pack 9.0.0.9\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043947 [http://www-01.ibm.com/support/docview.wss?uid=swg24043947] \nRemediation for users of versions V9.0.0.7, V10.0.0.8 and above: \nIf MQ JMS is used, then you are applicable to this vulnerability. To get around this vulnerability, the following steps are required \n1. Apply the fix for IBM Integration Bus APAR IT21160 \n2. Specify the whiltelist classes as below \n\nmqsichangeproperties <INode> -e <IServer> -o ComIbmJVMManager -n jvmSystemProperty -v <full qualified class names in comma separated form>", "eg : mqsichangeproperties <INode> -e <IServer> -o ComIbmJVMManager -n jvmSystemProperty -v \\ \"-Dcom.ibm.mq.jms.whitelist=com.ibm.broker.class1,com.ibm.broker.class2,com.ibm.broker.classn\\\" \n\nRemediation for users of versions prior to V10.0.0.8 and V9.0.0.7: \nYou will need to update MQ. Consult the security bulletin IBM WebSphere MQ JMS client deserialization RCE vulnerability [https://www-01.ibm.com/support/docview.wss?uid=swg21983457] for details. \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Matthias Kaiser of Code White (www.code-white.com) \n\nCHANGE HISTORY\n 29 September 2017: Original version published \n\n*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\nAccording 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. \n\n\n\nPRODUCT ALIAS/SYNONYM\n IIB" ]

[ "CVEID: CVE-2016-0360 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0360]\nDESCRIPTION: IBM Websphere MQ JMS client provides classes that deserialize objects from untrusted sources which could allow a malicious user to execute arbitrary Java code by adding vulnerable classes to the classpath. \nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/111930 [https://exchange.xforce.ibmcloud.com/vulnerabilities/111930] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H)" ]

[ 0 ]

[ "IBM CICS Transaction Server for z/OS 3.1 and 3.2 End of Support announcement - United States CICS TS 3.2 3.1 ; EOS; end of support; out of support; product lifecyle; end of lifecycle; withdrawal from support; withdrawn from support ; out of support; withdrawal announcement letter 5655M1500 R640 640 R400 400 HCI6400 R650 650 R500 500 HCI6500 5655-M15 5655M15; KIXINFO retention32 PRODUCT LIFECYCLE\n\nABSTRACT\n CICS Transaction Server for z/OS (CICS TS) V3.1 and V3.2 was withdrawn from support 31 December 2015. CICS TS Service Flow Feature V3.1 was also be withdrawn from support on the same date. This document contains a link to the Software service discontinuance announcement letter and product replacement information.", "CONTENT\nThe Software service discontinuance announcement letter that says CICS TS V3.1, CICS TS V3.2, and CICS TS Service Flow Feature V3.1 was withdrawn from support 31 December 2015 is 913-075 [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS913-075]. \n\nThe following product replacement information is included in this announcement: \n\nProgram Program\nWithdrawn program number Replacement program number\n\nCICS TS V3.1 5655-M15 CICS TS V4.2 5655-S97\n\nCICS TS V3.2 5655-M15 CICS TS V4.2 5655-S97\n\nCICS TS Service CICS TS Service Flow\nFlow Feature V3.1 5655-M15 Feature V3.2 5655-M15", "Note: For additional information, refer to Software Announcement 211-080 [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=897&letternum=ENUS211-080], dated April 05, 2011 . CICS TS V5.1 is also available and may be considered as a replacement product for CICS TS V3. For details, refer to Software Announcement 212-325 [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=897&letternum=ENUS212-325], dated October 03, 2012 .\n\nSee the Announcement Letters for CICS products [http://www.ibm.com/support/docview.wss?uid=swg21227090] if you are interested in upgrading to the latest release of CICS TS or any other CICS products.", "A fee based service extension for CICS TS for z/OS V3.1 or V3.2 might be available from IBM, if you need more time to upgrade. A service extension entitles you to continue to receive the level of support that you receive today using the same channels into IBM, including raising PMRs and APARs. If you would like to find out more about CICS service extensions, contact your local IBM Sales Representative: \n\n * US Customers, contact Customer Support Operations at 877-426-6006 option #2. If you give the support representative your customer number they can find your sales representative. \n \n \n * Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region.\n IBM directory of worldwide support contacts [http://www.ibm.com/planetwide/]", "For more information about the availability of support extensions see IBM software support lifecycle policy [http://www.ibm.com/software/support/lifecycle/lc-policy.html] page. \nRELATED INFORMATION\n Announcement letters for CICS products [http://www.ibm.com/support/docview.wss?uid=swg21227090]\nEnd of Service dates for CICS products [http://www.ibm.com/support/docview.wss?uid=swg21154953]\nCICS TS 4.1 and 4.2 End of Service dates [https://developer.ibm.com/answers/questions/182094/cics-transaction-server-for-zos-41-and-42-end-of-s.html]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server" ]

[ "The Software service discontinuance announcement letter that says CICS TS V3.1, CICS TS V3.2, and CICS TS Service Flow Feature V3.1 was withdrawn from support 31 December 2015 is 913-075" ]

[ 1 ]

[ "IBM TroubleShooting: JavaServer Pages (JSP) problems - United States JSPs; TroubleShootingDocument; troublehooting TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Troubleshooting JSP problems for WebSphere® Application Server. This should help address common issues with this component before calling IBM support and save you time. \n\nRESOLVING THE PROBLEM\nThe following are some examples of common JSP problems and some basic information on how to resolve them:", "* java.io.FileNotFoundException: JSPG0036E: Failed to find resource\n If the browser displays a JSPG0036E: Failed to find resource message, the JSP processor cannot find the specified JSP page in the Web module, as shown below.\n \n java.io.FileNotFoundException: JSPG0036F: Failed to find /Tests/index.jsp\n at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.findWrapper (JSPExtensionProcessor.java:246)\n at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest (JSPExtentionProcessor.java:228)\n ... \n Take following steps to verify URL being requested order to debug this exception:\n \n To determine the URL of the installed application, you need to use the administrative console to view the configuration of a number of items. The format of the URL is as follows:\n \n http://host:port/context_root/resource_name \n Finding <host>:<port>", "When a Web module is installed, a virtual host is associated with it. To find the virtual host using the WebSphere Application Server administrative console: 1. Select Applications > Application type > WebSphere Enterprise Applications.\n \n \n 2. Select the application name to open the details page.\n \n In the Web module Properties section, click Virtual hosts.\n \n \n 3. Note the virtual hosts that are used by the specified application Web module.\n \n \n To find the host and port numbers that are valid for the virtual host: 1. Select Environment > Virtual Hosts.\n \n \n 2. Choose the virtual host, and then under Additional Properties, click Host Aliases.", "3. The list contains the host name and port combinations that can be used to access this virtual host. The host name column should contain values that are registered in a DNS server as a host name for the WebSphere Application Server. An asterisk (*) in the host column indicates that any name can be used. In this case, use the server host name.\n \n \n Finding <context_root>\n The context root is the Web application root and is used to identify the application in the URI. To find the context root: 1. In the WebSphere Application Server administrative console, click Applications > Application type > WebSphere Enterprise Applications.\n \n \n 2. Select the target application, then under Detail Properties, click View Deployment Descriptor.\n \n \n 3. Review the <context-root> tag for the specified Web module in the related deployment descriptor tag.\n \n \n Finding <resource_name>", "To find the initial file for the application (for example, index.jsp), you can look at the welcome file list in the Web deployment descriptor. As per J2EE specification, JSP files should reside under web module root or under sub directory other than META-INF and WEB-INF.\n \n For example: * Web module root :\n \n install_root\\profiles\\profile_name\\installedApps<CELL>\\<EAR>\\<WAR> \n \n \n In the preceding case, the index.jsp file should reside uner Web_module_root/Test directory. If not, than it explains this error message. \n \n * JSP not reloading\n If, after modifying and saving a JSP file, the change does not show up in the browser, you need to check the reload settings in the Web module configuration and the JSP runtime reload settings. For the JSPs, the Web container reloads a Web module only when the IBM extension reloadingEnabled in the ibm-web-ext.xmi file is set to true.", "The following is an example of web module reloading settings in the ibm-web-ext.xmi file:\n \n <webappext:WebAppExtension xmi:version=\"2.0\" xmlns:xmi=\"http://www.omg.org/XMI\" xmlns:webappext=\"webappext.xmi\" xmi:id=\"WebAppExtension_1109270589179\" reloadInterval=\"3\" reloadingEnabled=\"true\" fileServingEnabled=\"true\"> \n Location of the ibm-web-ext.xmi file :\n \n install_root\\profiles\\profile_name\\config\\cells\\cell_name\n \\applications\\<EAR>\\deployments\\app_name\\<WAR>\\WEB-INF\\ibm-web-ext.xmi \n Configuring JSP runtime reloading:\n You have the ability to modify the JSP processor behavior for different JSP stages (such as development, testing, or production environments). This done by configuring specific attributes in the IBM Web module extensions that affect the JSP runtime reload behavior.", "JSP files can be translated and compiled at runtime when the JSP file or its dependencies are modified. This is known as JSP reloading. JSP reloading is enabled through the reloadEnabled JSP engine parameter in the ibm-web-ext.xmi configuration file.\n \n The JSP engine settings are stored in the ibm-web.ext.xmi file, as shown \n <jspAttributes xmi:id=\"JSPAttribute_1\" name=\"reloadEnabled\" value=\"true\"/>\n <jspAttributes xmi:id=\"JSPAttribute_9\" name=\"reloadInterval\" value=\"3\"/> \n \n * Encoding and internationalization issues", "Encoding and internationalization problems usually showup as garbage characters in Web pages and input from user interpreted incorrectly. Double Byte Character Set (DBCS) character processing is a common issue for encoding problems. DBCS is used for languages such a Chinese, Korean, and Japanese, where a single byte is not sufficient to represent all characters in the alphabet. Proper coding and configuration usually resolves these problems. For JSP pages, page encoding is the character encoding in which the file is encoded. For JSP pages in standard syntax, the page encoding is determined from the following sources: 1. The pageEncoding attribute of the page directive of the page \n 2. The charset value of the contentType attribute of the page directive\n \n \n If none of these is provided, ISO-8859-1 is used as the default page encoding.\n \n Page directive implementation in JSP code:\n \n <HTML>\n <HEAD>", "<%@ page language=\"java\" contentType=\"text/html; charset=UTF-8\" pageEncoding=\"ISO-8859-15\" %>\n <META http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\">\n <TITLE>Receiving parameters</TITLE>\n </HEAD>\n <BODY>\n <H1>\n Your data is <%= request.getParameter(\"name\") %>\n </H1>\n </BODY>\n </HTML> \n The pageEncoding and contentType attributes determine the page character encoding of only the file that physically contains the page directive. \n \n * java.lang.IllegalStateException\n This exception is thrown when attempt is made to modify HttpServletResponse object after it has been committed.\n \n If you have written something in the response buffer, you cannot forward a page:\n \n [7/8/05 20:36:25:694 ART] 0000004f ServletWrappe E SRVE0068E: Could not invoke the service() method on servlet TestServlet. Exception thrown : java.lang.IllegalStateException\n at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendRedirect(WebAppDispatcherContext.java:486)", "at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendRedirect(SRTServletResponse.java:810)\n ...\n [7/8/05 20:36:25:784 ART] 0000004f SRTServletRes W WARNING: Cannot set status. Response already committed. \n Calls to the following methods, after a committing response, will cause the java.lang.IllegalStateException error to occur: 1. setBufferSize(0) \n 2. reset() \n 3. resetBuffer() \n 4. sendError() \n 5. sendRedirect() \n 6. RequestDispatcher.forward() or performing jsp:forward\n \n \n Two other common variants of this exception are: \n java.lang.IllegalStateException: Header already sent \n One or more headers have been committed to the client, so you cannot set that header again. \n java.lang.IllegalStateException: OutputStream already obtained", "In case of JSP, the default output stream has always been created when the JSP has been translated to servlet. Creating and associating another output stream is the reason for this problem. The following piece of code will describe the reason for this error condition: \n try\n {\n lStream = pResponse.getOutputStream();\n lStream.write(lDocument);\n lStream.flush();\n }\n catch (java.io.IOException ioe)\n {\n logger.error(\"Exception writing ... to page output stream.\");\n }\n finally\n {\n try\n {\n if (lStream != null)\n {\n lStream.close();\n }\n }\n catch (java.io.IOException ioe)\n {\n logger.error(\"Exception closing page output stream.\");\n }\n } \n Two output streams cannot be associated with one JSP file.", "What to do next \nIf the preceding troubleshooting steps did not help solve your problem, see the MustGather [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21255205] for JSP problems. \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ "java.lang.IllegalStateException\n This exception is thrown when attempt is made to modify HttpServletResponse object after it has been committed." ]

[ 8 ]

[ "IBM After upgrading to 7.0.1.0 you get SSL error AMQ9716 - United States AMQ9716 7.0.1.0 SSL OCSP SSL TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You upgrade to WebSphere MQ 7.0.1.0 (or later) and have SSL enabled channels. After the upgrade you notice that in the Queue Manager error LOGs you see the following error message:\n\nAMQ9716: Remote SSL certificate revocation status check failed for channel '????'. \nThe channel does not start. \n\nSYMPTOM\nError AMQ9716\n\n\nCAUSE\nWith the release of WebSphere MQ V7.0.1.0 the use of OCSP certificate revocation checking was included. With this new feature, most likely your SSL certificates have a OCSP AuthorityInfoAccess (AIA) certificate extension embedded inside them.", "This was ignored before V7.0.1.0. Now it is being used to verify the certificate. The most likely cause of the failure is that the system can not access the servers listed in the AIA. This then returns a UNKNOWN status when the check is done. The default action for MQ is to not allow the channel to start and the AMQ9716 to be reported when the UNKNOWN is returned.\n\n\nRESOLVING THE PROBLEM\nThe best thing to do in this case is to determine the cause of the UNKNOWN return code and fix it. \n\n\nThere are two possible methods to discover which OCSP AuthorityInfoAccess URL is embedded in a certificate. \n\nMethod 1.\nPlace the certificate on a Windows machine; ensure to use a file extension of \"crt\" and double-click it. View the detail extensions for the AIA. \n\n[/support/docview.wss?uid=swg21399255&amp;aid=1]\n\nMethod 2\nUse IBM Key Management (gskit) GUI to view them. Issue the following command::\nIn Windows: strmqikm \nIn UNIX: gsk7ikm (MQ V7) or runmqckm (MQ V8)", "From the IBM Key Management window:\nSelect View/Edit for certificate\nView Details\nExtensions\nAuthorityInfoAccess\n\n[/support/docview.wss?uid=swg21399255&amp;aid=2]\n\nThe first step would be to insure that connection to the URL in your certificate can be reached.\n\n\nWork-around:\nUse this only as a temporary fix until the root cause can be found.\nYou can do the following. It will still do OCSP checking and if REVOKED is returned then the channel will not start. A GOOD return code will allow the channel to start. If UNKNOWN is returned it will not stop the channel from starting and the AMQ9716 will not be reported.\n\nUNIX and Linux systems add the following to qm.ini\nSSL:\nOCSPAuthentication=OPTIONAL\n\nTo set for a Windows Queue Manager, run the following command:\namqmdain reg YourQMgrName -c add -s SSL -v OCSPAuthentication=OPTIONAL", "The OCSPAuthentication setting is also applicable to clients and can also be set in the client ini file (e.g. mqclient.ini). Changes to the client OCSPAuthentication setting will take effect after the application is restarted.\n\nOn a queue manager, users will need to issue a REFRESH SECURITY TYPE(SSL) command (or the GUI/PCF equivalent) in order for the change in SSL settings to take effect.\n\nOCSP provides your SSL channels with additional security. Once the cause of the AMQ9716 error has been addressed then you are strongly recommended to re-enable OCSP enforcement\n\nRELATED INFORMATION\n OCSP Info [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/sy13000_.htm?lang=en]\n\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ" ]

[ "With the release of WebSphere MQ V7.0.1.0 the use of OCSP certificate revocation checking was included. With this new feature, most likely your SSL certificates have a OCSP AuthorityInfoAccess (AIA) certificate extension embedded inside them. \n\n\nThis was ignored before V7.0.1.0. Now it is being used to verify the certificate. The most likely cause of the failure is that the system can not access the servers listed in the AIA. This then returns a UNKNOWN status when the check is done. The default action for MQ is to not allow the channel to start and the AMQ9716 to be reported when the UNKNOWN is returned." ]

[]

[ "IBM Security Bulletin: Multiple vulnerabilities identified in IBM® Java SDK affect WebSphere Service Registry and Repository Studio (CVE-2015-4872, CVE-2015-4911, CVE-2015-4893, CVE-2015-4803) - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in October 2015. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4872 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4872]", "DESCRIPTION: An unspecified vulnerability related to the Security component has no confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107361 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107361] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:P/A:N)\n\nCVEID: CVE-2015-4911 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4911]\n\nDESCRIPTION: An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107360 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107360] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID: CVE-2015-4893 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4893]", "DESCRIPTION: An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107359 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107359] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID: CVE-2015-4803 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4803]\n\nDESCRIPTION: An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107358 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107358] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "AFFECTED PRODUCTS AND VERSIONS\n WebSphere Service Registry and Repository Studio V8.5, V8.0, V7.5 and V7.0 are affected.\n\nREMEDIATION/FIXES\nNote regarding CVE-2015-4911\nThis was addressed by IBM in June 2008. As a reminder, users of Java 6 and above should\nrefer to the IBM XL XP-J documentation [https://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/SSYKE2_7.0.0/com.ibm.java.win.70.doc/user/xml/xlxpj_reference.html] for the javax.xml.stream.supportDTD property\nfor information to help avoid this vulnerability.", "For all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.0_IV79089_IV80119_IV80540_IV80888 [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Service+Registry+and+Repository&release=All&platform=All&function=fixId&fixids=8.5.6.0-WS-WSRR-Studio-MultiOS-IFIV79089_IV80119_IV80540_IV80888&includeRequisites=1&includeSupersedes=0&downloadMethod=ddp&source=fc] \n\n\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 01 February 2016: Original version published \n\n*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\nAccording 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." ]

[ "CVEID: CVE-2015-4872 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4872]\n\nDESCRIPTION: An unspecified vulnerability related to the Security component has no confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107361 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107361] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:P/A:N)" ]

[]

[ "IBM PI47826: VMM DOES NOT CLEAR THE CACHE IF CLEARENTITY MODE IS USED. - United States FIXES ARE AVAILABLE\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]", "8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]", "SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * If base entry and name in repository is different and\n clearCache functionality is used with clearEntity mode then\n virtual member manager (VMM) still looks in the cache and gets\n the entity from the cache instead of fetching it from the LDAP\n server.\n \n \n \n \n \n\nLOCAL FIX\n * test fix", "PROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server V8.0 and V8.5 virtual member *\n * manager (VMM) *\n ****************************************************************\n * PROBLEM DESCRIPTION: Clear cache does not work if *\n * clearEntity *\n * mode is used. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n LDAP Clear cache functionality of VMM does not work when using\n clearEntity mode. Problems occur only if there is a different\n base entry used than the name in the repository entry.", "PROBLEM CONCLUSION\n * This APAR fixes the issue. It clears the cache properly even if\n base entry is different than name in repository.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.13 and 8.5.5.9. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI47826\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 800\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-08-28\n \n \n * CLOSED DATE\n 2015-12-09\n \n \n * LAST MODIFIED DATE\n 2015-12-09", "* APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBS APP SERV N\n \n \n * FIXED COMPONENT ID\n 5724H8800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP\n \n \n * R850 PSY\n UP" ]

[ "This APAR fixes the issue. It clears the cache properly even if\n base entry is different than name in repository.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.13 and 8.5.5.9." ]

[ 4 ]

[ "IBM An unexpected ruleset version is executed - United States TECHNOTE (FAQ)\n\nQUESTION\n Why is Rule Execution Server (RES) not executing the expected version of a ruleset ?\nWhat are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ? \n\nCAUSE\nPossible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses", "ANSWER\nFirst validate that the RES components (the Execution Unit, the Management Console and the Client Application bundling the RES client library, which may be HTDS, MTDS, the SSP or a custom application) have been installed properly as per the documentation, see Configuring Rule Execution Server [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res/tpc_res_config.html]. \n\nThe ruleset version that is executed depends first on the ruleset path that is requested. Specifying a ruleset path with no version ( such as /MyRuleApp/MyRuleset/ ) is interpreted as a request to execute the highest version of the ruleset, as opposed to a version specific ruleset path ( such as /MyRuleApp/2.0/MyRuleset/1.0 ). Validate that the executed ruleset path is indeed unexpected considering the requested ruleset path.", "A common situation for an unexpected ruleset version to be executed is that of a hot deployment that is not successfully completed. The more frequent causes for the hot deployment not to happen as expected are:", "* Permission issue: the user publishing the ruleset update must have sufficient administrative rights ( Monitor role in WebSphere Application Server ) in order for the deployment to notify all the Execution Units of the ruleset update through JMX. For example on WebSphere Application Server see Mapping the resAdministrators group to the Monitor role [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res_was8/tsk_was_map_admin_group.html]", "* Version mismatch between the Execution Unit(s) and the Management Console: in order for the Management Console to detect the presence of execution units the versions of these components must match down to the fix level. For example 7.1.1.4 Management Console would not interact properly with a 7.1.1.3 Execution Unit. The version of the RES console is displayed in the \"About\" link (top right corner). The version of the Execution Unit can be seen in the resource adapter ra.xml file where a resourceadapter-version tag shows the version. For example with the WebSphere Application Server this can seen through: Resources > Resource adapters > XU > Deployment Descriptor", "* Asynchronous ruleset parsing is used : in this mode, while an updated ruleset is being parsed, an earlier version of the ruleset can be used for executions that are requested at that time. Note that there is no guarantee of which specific earlier version of the ruleset may be used since it is a factor of which versions are available in the deprecated ruleset cache and whether garbage collection has occurred. In order to remove any uncertainty on the version that can be executed, it is possible to either turn off the asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_asynchron_turnoff.html], or force synchronous parsing in asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_forcing_sync_pars.html].", "* Notification scope is limited to one cell : by design the RES notification mechanism only works within one WebSphere Application Server Cell ( or one JBoss domain, or one Weblogic domain ), so a Management Console may only notify Execution Units that are running on servers in the same cell as the RES Console. See XU notification in a cluster over multiple cells [http://www-01.ibm.com/support/docview.wss?uid=swg21458245]. If you need to implement notifications to several cells at once, the document Ruleset updates and programmatic notification of RES eXecution Unit [http://www-01.ibm.com/support/docview.wss?uid=swg21418646] can be useful. \n * Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully", "* Ruleset update was only written to persistence: writing directly to RES persistence with the ant tasks res-write-db or res-write-file [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_deploy_rlapp_ant.html] does not trigger a notification, so the update may only been seen after server restart. \n * XU MBean is not activated in Java SE mode : See Activating the XU MBean in Java SE [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_xu_mbean_jse.html] \n * Multiple Java SE Execution Units are deployed in the same JVM: See Rule Execution Server J2SE mode hot deployment does not seem to work [http://www-01.ibm.com/support/docview.wss?uid=swg21585251]", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES / RES) Platform Independent 7.1.1, 7.1, 7.0.3, 7.0.2, 7.0.1, 7.0" ]

[ "Possible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses" ]

[ 0 ]

[ "IBM Deletion of virtual portal fails with transaction timeout - United States virtual portal; timeout; delete; portlet; EJPAH4000E; EJPEB0804E; rollbackexception; admin; WTRN0006W TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAttempt to delete virtual portal via Virtual Portal Manager portlet fails with error:\n\nEJPAH4000E: Failed to delete virtual portal \n\nAttempts to delete the virtual portal using the ConfigEngine task \"delete-virtual-portal\" may fail as well.\n\n\nCAUSE\nWith the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded: \n\n * the total and/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may show the following: \n\nExample #1:", "[9/10/12 10:08:43:757 AMT] 0000001a TimeoutManage I WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.\n\n[datestamp] 00000055 JTATransactio E RT0025E: Failed to save user transaction\ncom.ibm.icm.ci.CDMTransactionException\nat com.ibm.icm.ci.JCRUserTransaction.commit(JCRUserTransaction.java:189)\nat com.ibm.icm.ci.JTATransaction.commit(JTATransaction.java:166)\nat com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:804)\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n....", "[datestamp] 00000055 DeleteVPComma E com.ibm.wps.command.vp.DeleteVPCommand AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJPFB0002E: Exception occurred.\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:348)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n.... \n\nExample #2:", "[datestamp] 000000f4 TimeoutManage I WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.\n[datestamp] 000000f4 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 8,5,main]. The stack trace of this thread when the timeout occurred was: \njava.net.SocketInputStream.socketRead0(Native Method)\njava.net.SocketInputStream.read(SocketInputStream.java:150)\njava.net.SocketInputStream.read(SocketInputStream.java:121)\ncom.ibm.db2.jcc.t4.x.b(x.java:208)\ncom.ibm.db2.jcc.t4.x.c(x.java:360)\ncom.ibm.db2.jcc.t4.x.c(x.java:473)\ncom.ibm.db2.jcc.t4.x.v(x.java:1241)\ncom.ibm.db2.jcc.t4.ab.a(ab.java:61)\ncom.ibm.db2.jcc.t4.p.a(p.java:50)\ncom.ibm.db2.jcc.t4.rb.b(rb.java:220)", "com.ibm.db2.jcc.am.po.qc(po.java:3498)\ncom.ibm.db2.jcc.am.po.b(po.java:4461)\ncom.ibm.db2.jcc.am.po.ic(po.java:799)\ncom.ibm.db2.jcc.am.po.executeUpdate(po.java:777)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1187)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:804)\ncom.ibm.icm.da.portable.common.sql.PPreparedStatement.executeUpdate(PPreparedStatement.java:83) com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWideTableData(DeleteWorkspace.java:359)\ncom.ibm.icm.da.portable.data.DeleteWorkspace.deleteWorkspace(DeleteWorkspace.java:130) com.ibm.icm.da.portable.data.DataManager.deleteWorkspace(DataManager.java:700)\ncom.ibm.icm.ci.workspace.impl.PDeleteWorkspaceImpl.deleteWorkspace(PDeleteWorkspaceImpl.java:84) com.ibm.icm.ci.workspace.impl.WorkspaceService.deleteWorkspace(WorkspaceService.java:270) com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:808)", "com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:324) com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)\ncom.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90) com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:345)\ncom.ibm.wps.command.vp.VirtualPortalHandlerImpl.onVirtualPortalDeleted(VirtualPortalHandlerImpl.java:396)\ncom.ibm.wps.command.vp.DeleteVPCommand.execute(DeleteVPCommand.java:178 com.ibm.wps.portlets.managevirtualportals.actions.DoDeleteVirtualPortalAction.deleteVirtualPortal(DoDeleteVirtualPortalAction.java:151)\n....", "RESOLVING THE PROBLEM\n1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below. \n\n2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider: \n\nName: wcm.transaction.timeout \n\nValue: 600 (for example) \n\nNote: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.", "RELATED INFORMATION\n#Transaction settings [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html]\nPI04872 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI04872]\nSetting Resource Environment Provider custom properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8]" ]

[ "1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below. \n\n2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider: \n\nName: wcm.transaction.timeout \n\nValue: 600 (for example)" ]

[ 6 ]

[ "IBM How can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error? - United States TECHNOTE (FAQ)\n\nQUESTION\n We are able to install Data Studio (DS) 4.1.2 successfully but unable to uninstall the \nexisting Data Studio 3.1.1. When uninstall Data Studio 3.1.1 from Control Panel, it \nraises an error message pop-up window and can not uninstall it. Here is the message:\n\n+-------------------------------------------------------------------------\n| Java Virtual Machine Launcher\n+-------------------------------------------------------------------------\n| X Could not find the main class: com.zerog.lax.LAX. Program will exit.\n+-------------------------------------------------------------------------\n\nHow can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error?\n\n\nCAUSE\nIt is an known behavior/limitation. \n\nANSWER\nIt may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine.", "Here is an workaround. Please try to uninstall all products including Install Manager \n(IM) then reinstall IM and Data Studio 4.1.2. Below are detailed steps:\n\n1. Use IM to uninstall as many packages as possible.\n\n2. Identify the packages that are still installed, and manually clean \nthem up.\n\nExample on Windows:\n- C:\\Program Files\\IBM\\{IBMIMShared | SDPShared}\n\n3. Delete IBM Installation Manager.\n\nExample on Windows:\n- Delete the IM install directory:\nC:\\Program Files\\IBM\\Installation Manager\\\n- Delete the AppData directory (IM Agent Data):\nWindows 7: C:\\ProgramData\\IBM\\Installation Manager\n- Delete the Windows registry (regedit) entry : \nHKEY_LOCAL_MACHINE\\SOFTWARE\\IBM\\Installation Manager\n- re-install IM\n\n4. Reinstall DS 4.1.2 and other products.", "Note:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following above.\nPlease contact your Sales Rep to submit a potential design change towards a future release.\nOr please open a ticket, Request For Enhancement at https://www.ibm.com/developerworks/rfe/ [https://www.ibm.com/developerworks/rfe/]" ]

[ "It may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine." ]

[ 0 ]

[ "IBM Purging the connection pool of a WebSphere Application Server data source using the data source MBean - United States was app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n During the testing or troubleshooting of an enterprise application, it may become necessary to purge the connection pool of a WebSphere Application Server data source of existing connections. \n\nSYMPTOM\nChanges to the application or environment may invalidate cached connections in the Connection Manager pool. Although these connections will eventually be discarded through the normal processing of the connection requests, it may be desirable to purge them all at once and allow the pool to refill with new, valid connections.", "RESOLVING THE PROBLEM\nWebSphere Application Server has an operation on the data source MBean that can be used to purge the connection pool. WebSphere Application Server MBean may be called via the wsadmin console, see the IBM Information Center topic \"Scripting the application serving environment (wsadmin)\" for more details. The operation name is: purgePoolContents. \n\nThe purgePoolContents operation has two options:", "1. Normal: * This is the default option. \n * Existing in-flight transactions will be allowed to continue work. \n * Shared connection requests will be honored. \n * Free connections are cleaned up and destroyed. \n * In use connections (for example: connections in transactions) are cleaned up and destroyed when returned to the connection pool. \n * A close() call issued on any connection obtained prior to the purgePoolContents will be done synchronously (for example: wait for the jdbc driver to return before proceeding). \n * Requests for new connections (not handles to existing old connections) will be honored.\n \n \n \n \n 2. Immediate: * No new transactions will be allowed to start on any connections obtained prior to the purgePoolContents call. Instead, a StaleConnectionException is thrown. \n * No new handles will be handed out on any connections obtained prior to the purgePoolContents call. Instead, a StaleConnectionException is thrown.", "* Existing in-flight transactions will be allowed to continue work. Any new activities on a purged Connection will cause a StaleConnectionException or an XAER_FAIL exception (in the case of XA) \n * A close() call issued on any connection obtained prior to the purgePoolContents call will be done asynchronously (for example: no waiting for the jdbc driver to return) This is useful if the driver returns. \n * Due to the fact that close() does not wait, the number of connections will be decremented immediately in WebSphere Application Server. This might cause the total number of connections in WebSphere Application Server to be temporarily out of sync with the database total number of connections. \n * Requests for new connections (for example: not handles to existing old connections) will be honored.", "Examples of operations that can be executed on the data source MBean using the wasdmin console: 1. List all data sources:\n Using Jacl:\n $AdminControl queryNames *:type=DataSource,*\n \n Using Jython:\n AdminControl.queryNames(\"*:type=DataSource,*\")\n \n \n 2. Initialize a variable to specify a data source (this example uses Default Datasource, but any data source name listed in the output of above command can be used):\n Using Jacl:\n set name \"Default Datasource\"\n set ds [$AdminControl queryNames *:type=DataSource,name=$name,*] \n \n Using Jython:\n name = \"Default Datasource\"\n ds = AdminControl.queryNames(\"*:type=DataSource,name=\"+name+\",*\") \n \n \n 3. View the pool contents by invoking the showPoolContents operation of the data source MBean:\n Using Jacl:\n $AdminControl invoke $ds showPoolContents\n \n Using Jython:\n print AdminControl.invoke(ds, \"showPoolContents\")", "4. View contents of all pools by invoking the showAllPoolContents operation of the data source MBean:\n Using Jacl:\n $AdminControl invoke $ds showAllPoolContents\n \n \n Using Jython:\n print AdminControl.invoke(ds, \"showAllPoolContents\")\n \n \n 5. Immediately purge the pool by invoking the purgePoolContents operation of the data source MBean with the immediate option:\n Using Jacl:\n $AdminControl invoke $ds purgePoolContents immediate\n \n \n Using Jython:\n AdminControl.invoke(ds, \"purgePoolContents\", \"immediate\")", "If the purge operation is successful, no response will be observed. If the purge operation is not successful, the response will indicate a possible reason for failure. One common reason for failure is attempting to purge the contents of a connection pool which is not yet available (the connection pool is not created until a naming look-up of the associated datasource or connection factory occurs), resulting in an illegal state exception. \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK Application Servers WebSphere Application Server for z/OS Java SDK z/OS 8.0, 7.0, 6.1" ]

[ "WebSphere Application Server has an operation on the data source MBean that can be used to purge the connection pool. WebSphere Application Server MBean may be called via the wsadmin console, see the IBM Information Center topic \"Scripting the application serving environment (wsadmin)\" for more details. The operation name is: purgePoolContents." ]

[ 1 ]

[ "IBM Tivoli Monitoring 6.3.0 Fix Pack 6 (6.3.0-TIV-ITM-FP0006) - United States DOWNLOADABLE FILES\n\nABSTRACT\n This is a cumulative fix pack for IBM Tivoli Monitoring version 6.3.0. \n\nDOWNLOAD DESCRIPTION\nThis is a cumulative fix pack for IBM Tivoli Monitoring version 6.3.0. This fixpack is available as both an upgrade and fresh install.\n\n\n\nThe upgrade install for this Fix pack consists of the following files:", "Fix pack file name Description 6.3.0-TIV-ITM_TMV-Linuxx-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux x86, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Linuxx64-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux x86_64, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Linuxz-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux on System z, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based", "distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Unix-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Unix, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Windows-FP0006.zip Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for 32-bit Windows, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Windows64-FP0006.zip Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for 64-bit Windows, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed", "monitoring agents. 6.3.0-TIV-ITM_TMV-Agents-FP0006.tar.gz Contains the IBM Tivoli Monitoring base agents. This includes the following: Agentless Monitor (multiplatforms), i5/OS agent, Windows OS agent, Linux OS agent, UNIX OS agent, UNIX Logs agent, IBM Tivoli Universal Agent. 6.3.0-TIV-ITM_TMV-Tools-FP0006.tar.gz Contains the IBM Tivoli Monitoring 5.1.2 Migration Toolkit, the Distributed Monitoring Upgrade Toolkit and the Tivoli Event Integration event synchronization component. 6.3.0-TIV-ITM_TMV-Agent-Reports-FP0006.tar.gz Contains the IBM Tivoli Monitoring OS Agents Reports. 6.3.0-TIV-ITM_TMV-ITPA-Common-FP0006 .tar.gz IBM Tivoli Performance Analyzer Reports and Domain Definitions Multiplatform, Multilingual. 6.3.0-TIV-ITM_TMV-LP-FP0006.tar.gz Contains the IBM Tivoli Monitoring Language Pack for all platforms.", "The pristine install images can be downloaded from the IBM Passport Advantage® Online Website:", "Number of eAssembly to download Number of part to download Title on Passport Advantage Contents CRYB4ML CN8CPEN IBM Tivoli Monitoring V6.3.0.6 Base, Windows (32 Bit env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support in English for base agents for 32-bit Windows operating systems CRYB4ML CN8CQEN IBM Tivoli Monitoring V6.3.0.6 Base, Windows (64 Bit env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Windows operating systems CRYB4ML CN8CREN IBM Tivoli Monitoring V6.3.0.6 Base, Unix, English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for UNIX operating systems CRYB4ML CN8CSEN", "IBM Tivoli Monitoring V6.3.0.6 Base, Linux (32 Bit Env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 32-bit Env. Linux operating systems CRYB4ML CN8CTEN IBM Tivoli Monitoring V6.3.0.6 Base, Linux (64 Bit Env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Env. Linux operating systems CRYB4ML CN8CUEN IBM Tivoli Monitoring V6.3.0.6 Base, Linux on System z®, English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for Linux on System z operating systems CRYB4ML CN8CVEN IBM Tivoli Monitoring V6.3.0.6 Tools, Multiplatform, English Tivoli Monitoring", "event synchronization component, Tivoli Enterprise Console® Event Definition Generator (TEDGEN) utility, and audit record DTDs CRYB4ML CN8CWML IBM Tivoli Monitoring V6.3.0.6 Language Support Language pack for Tivoli Monitoring server components, warehouse agents, OS agents, agentless OS agents, Tivoli Performance Analyzer agent for all operating systems and languages CRYB4ML CN8CXML IBM Tivoli Performance Analyzer V6.3.0.6: Reports and Domain Definitions Multiplatform, Multilingual Performance Analyzer domains and BIRT reports CRYB5ML CN8CYML IBM Tivoli Monitoring V6.3.0.6 Agents, Multiplatform, Multilingual Operating system agents (IBM i, Linux, UNIX, Windows) and Agentless OS agents (AIX, HP-UX, Linux, Solaris, Windows) CRYB5ML CN8CZML IBM Tivoli Monitoring V6.3.0.6 Agent Reports Operating system agent reports and reports installer", "The following levelset PTFs represent the equivalent maintenance level for the corresponding z/OS components which can be ordered via ShopzSeries: \n\nUA79950 -- MGMT SERVER DS (Code) \nUA79951 -- MGMT SERVER DS (Data) \nUA79952 -- ITMS/ENGINE 1 of 2 \nUA79953 -- ITMS/ENGINE 2 of 2 \n\n\n\nCreated/Revised by Date of Creation/Update Summary of Changes MBK 2015/07/21 Document created DMH 2015/12/11 Fix Pack Published \n\nURL LANGUAGE SIZE(Bytes) Installation and Setup Guide [http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2//com.ibm.itm.doc_6.3fp2/install/itm_install.htm] English 999999999 \nDOWNLOAD PACKAGE\n\n\nFix Central\n\n Fix Central provides fixes and updates for your system's software, hardware, and operating system. An IBM registered ID is required to obtain the fixes, which allows us to update you on any critical issues with the fix. Privacy is always maintained.", "Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.3.0-TIV-ITM-FP0006 11 Dec 2015 English 999999999 FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ETivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&release=All&platform=All&function=fixId&fixids=6.3.0-TIV-ITM-FP0006&source=fc] [ ] \n [/support/docview.wss?uid=swg24040390&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24040390&aid=2]Problems (APARS) fixed", "IV55651 IV60994 IV63092 IV63947 IV65928 IV65987 IV66557 IV66841 IV66911 IV67076 IV67172 IV67425 IV67488 IV67982 IV67984 IV68546 IV68792 IV69144 IV69246 IV69577 IV69631 IV69716 IV70115 IV70669 IV70848 IV71253 IV71318 IV71473 IV71612 IV71647 IV71746 IV71863 IV71904 IV71943 IV72089 IV72146 IV72203 IV72314 IV72474 IV72801 IV73322 IV73382 IV73766 IV73792 IV73932 IV73936 IV73939 IV74037 IV74060 IV74065 IV74120 IV74283 IV74467 IV74486 IV74529 IV74707 IV74718 IV74758 IV75054 IV75229 IV75556 IV75571 IV75592 IV75908 IV76074 IV76109 IV76801 IV77408 IV77439 IV77462 IV77775 IV78573 IV79364" ]

[ "6.3.0-TIV-ITM-FP0006 11 Dec 2015 English 999999999 FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ETivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&release=All&platform=All&function=fixId&fixids=6.3.0-TIV-ITM-FP0006&source=fc]" ]

[ 9 ]

[ "IBM Datacap Rulerunner server stops after several aborted batches - United States Rulerunner hang stop abort TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After several batches abort consecutively in Rulerunner, all threads shut down. \n\nCAUSE\nRulerunner has a thread control feature that acts as a safety to prevent all pending batches from aborting. When it detects a certain number of consecutively aborted batches on a single thread, Rulerunner shuts down all threads. By default, the threshold is three batches, so shutdown occurs if four batches abort consecutively.\n\nDIAGNOSING THE PROBLEM\nWith Rulerunner logging turned on, aborting batches will show in the rulerunnerX.log files (where X is the thread number. If there is a question as to whether a Rulerunner shutdown is being caused by this feature, check the rulerunnerX logs for each thread to see if there are four consecutive aborts followed by a shutdown.", "RESOLVING THE PROBLEM\nIf there is a need to change this behavior due to situations where a large number of batches might legitimately abort, the threshold can be increased or the feature can be turned off through the following registry keys.\n\n\nx86 (32-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nIndividual processors [default: 1] \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nprocessor Attempts [default: 3] \n\n \n\nx64 (64-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart Individual processors [default: 1) \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart processor Attempts [default: 3] \n\n \n\n * Restart Individual processors - 1 is on, 0 is off. \n * Restart processor Attempts - Number of times Rulerunner will move to the next batch without shutting down the threads after a series of batches abort.", "Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture Not Applicable Windows 8.1.0.3" ]

[ "If there is a need to change this behavior due to situations where a large number of batches might legitimately abort, the threshold can be increased or the feature can be turned off through the following registry keys.\n\n\nx86 (32-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nIndividual processors [default: 1] \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nprocessor Attempts [default: 3] \n\n \n\nx64 (64-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart Individual processors [default: 1) \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart processor Attempts [default: 3] \n\n \n\n * Restart Individual processors - 1 is on, 0 is off. \n * Restart processor Attempts - Number of times Rulerunner will move to the next batch without shutting down the threads after a series of batches abort." ]

[ 1 ]

[ "IBM Changes in the default user identifier between WebSphere MQ V7.0.1 classes for JMS and WebSphere MQ V7.1 classes for JMS - United States TECHNOTE (FAQ)\n\nQUESTION\n You have configured a WebSphere Application Server WebSphere MQ messaging provider connection factory without an Authentication Alias and do not programmatically supply user identifier information when creating a connection to a queue manager. You notice a change in the default behaviour between WebSphere Application Server versions regarding the user identifier flowed on the MQCONN to the target WebSphere MQ Queue Manager:\n\n- When using WebSphere Application Server v7.0 and v8.0, no user identifier value (blank) is passed to the queue manager. \n\n- When using WebSphere Application Server V8.5, a non-blank user identifier value is passed to the queue manager. \n\nIn the latter case, you receive the following exception when creating a connection to a queue manager:", "JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED') \n\nIs this change in behaviour expected? \n\nANSWER\nWebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.\nFrom the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ. This is true even if no user identifier has been specified, or a blank or null user identifier has been specified; for example by calling:\n\nMQConnectionFactory.createConnection();\n\nor:\n\nMQConnectionFactory.createConnection(“”, “”);\n\nor:\n\nMQConnectionFactory.createConnection(null, null);", "In the case where a null or blank user identifier has been specified, the WebSphere MQ V7.1 and later classes for JMS will query the value of the Java System Property user.name. The value of this property is flowed to the queue manager for authorization.\n\nAs a result, if the user identifier specified by the Java System Property user.name is not authorized to access the queue manager, the queue manager will return an exception to the WebSphere MQ classes for JMS with Reason Code MQRC_NOT_AUTHORIZED and the connection to the queue manager will not be established.", "This change in behaviour could affect topologies that previously relied on the default behaviour in the WebSphere MQ V7.0.1 classes for JMS that flowed a blank user identifier when establishing a CLIENT mode transport connection. The expectation that a blank or null user identifier will be flowed by default, and that the user identifier that started the WebSphere MQ server-connection channel would be used by the queue manager when performing the authorization checks, is no longer valid from the WebSphere MQ V7.1 classes for JMS.\n\nIn the case outlined above, system administrators that are currently relying on the default behaviour of the WebSphere MQ V7.0.1 classes for JMS should review their configurations regarding the use of user identifiers and authorization. This might also help to improve security within their WebSphere MQ topology.\n\n\nIn summary, the change in behaviour will affect users of:\n\n- The WebSphere MQ V7.1 and later classes for JMS.", "- The WebSphere MQ V7.1 and later JCA Resource Adapter that includes the classes for JMS.\n\n- Versions of WebSphere Application Server that include the WebSphere MQ V7.1 and later JCA Resource Adapter. Currently this is WebSphere Application Server V8.5.0.0 and later.\n\n\nThe com.ibm.mq.jms.ForceUserID Java System Property\n\nA Java System Property called “com.ibm.mq.jms.ForceUserID” was introduced as part of APAR IZ49302 [http://www.ibm.com/support/docview.wss?uid=swg1IZ49302] and included from WebSphere MQ V6.0.2.8 and WebSphere MQ V7.0.1.\n\nThe changes made as part of this APAR could be used to change the default behaviour in the WebSphere MQ V7.0.1 classes for JMS regarding the user identifier value flowed to the queue manager when creating a connection.\n\nThis property is no longer valid from WebSphere MQ V7.1. Setting this property will have no affect on the WebSphere MQ V7.1 classes for JMS and later.\n\nOther Useful Resources\n\nWebSphere MQ Documentation", "The WebSphere MQ Documentation contains a section on planning user authorization which also includes a description on access control for clients. A link to this section in the WebSphere MQ V7.1 Documentation is as follows:\n\nWebSphere MQ > Security > Planning for your security requirements >> Planning authorization [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/zs14070_.htm]\n\nTechnotes\n\nA Technote is available that explains J2C Authentication Aliases and how they can be used to configure the user identifier flowed to a queue manager when creating a connection: \n\nEnterprise applications, the WebSphere Application Server WebSphere MQ messaging provider connection factories and Authentication Aliases explained [http://www.ibm.com/support/docview.wss?uid=swg21580097]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server" ]

[ "WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.\nFrom the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ." ]

[ 1 ]

[ "IBM Specifying the profile path in the BPMConfig properties file for IBM Business Process Manager (BPM) - United States BPMConfig; profile; path; directory TECHNOTE (FAQ)\n\nQUESTION\n How do you specify the profile path in the configuration properties file for IBM Business Process Manager so you can use it with the BPMConfig command? \n\nANSWER\nNote: The information that is contained in this document has been moved to dW Answers at this location [https://developer.ibm.com/answers/questions/171346/how-do-you-specify-the-profile-path-with-bpmconfig.html]. The new format will allow you to ask questions of the community to better understand the information. This technote will be archived in 60 days. Please bookmark the new location.\n\nYou can use the following property names: \n\n * For a Deployment Manager profile: bpm.dmgr.profilePath \n * For a Custom profile: bpm.de.node.#.profilePath", "For example: \nbpm.dmgr.profilePath=/usr/IBM/bpm85/profiles/DmgrProfile \nbpm.de.node.1.profilePath=c:\\\\Program Files\\\\WebSphere\\\\profiles\\\\MyCustomProfile1 \n\nFor Microsoft Windows, you can use double backslashes or forward slashes. For example: \n\nbpm.de.node.1.profilePath=c:/Program Files/WebSphere/profiles/MyCustomProfile1 \n\n \n\nNote: If you are creating the profile makes sure a profilePath value does not exist. The parent directory of the profile path should exist and the user should have write privileges to create a new directory. \n\n\nFor example, if you want to create a profile under the /usr/BPM850profiles/myProfile directory. Create the/usr/BPM850profiles directory, but do not create the /usr/BPM850profiles/myProfile directory.\n\nRELATED INFORMATION\n BPMConfig command: sample configuration properties file [http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm.wbpm.imuc.doc/topics/samplecfgprops.html]", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5 \nPRODUCT ALIAS/SYNONYM\n BPM" ]

[ "Note: If you are creating the profile makes sure a profilePath value does not exist." ]

[ 1 ]

[ "IBM JMSListener AutoReconnect properties misconception - United States netcool; impact; netcool/impact; nci; jms; dsa; connectivity; reconnect; auto; autoreconnect; property; properties; listener; jmslistener; misconception; disinformation; misunderstanding; misinterpretation; error; fault; inaccuracy TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n There appears to be a common misconception regarding the application of the JMS DSA Listener properties for AutoReconnect\n\n\n\nSYMPTOM\nAutoReconnect fails\n\n\nCAUSE\nProperties for the JMSListener in the file: \n\n$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props\n\nhave been set as:\n\nimpact.[JMSListenerName].jms.autoreconnect=true\nimpact.[JMSListenerName].jms.autoreconnect.pollinterval=[TimeValue]\n\n\n\n\nRESOLVING THE PROBLEM\nProperties for the JMSListener in the file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props", "Where [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:\n\nimpact.[JMSListenerName].autoreconnect=true\nimpact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]\n\nWhere [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit." ]

[ "Properties for the JMSListener in the file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props\n\nWhere [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:\n\nimpact.[JMSListenerName].autoreconnect=true\nimpact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]\n\nWhere [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit." ]

[]

[ "IBM No data in some workspaces for MySQL agent - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Monitoring agent for MySQL when configured to monitor MySQL server versions 5.7.6 and above does not collect data for some of the attribute groups. \n\nSYMPTOM\nData does not get collected for the following views that show system and status variable related information: \n\nView name Workspace name Navigator group name Statistics Statistics Availability Operations per second MySQL status data Availability Session status Agent Configuration Configuration Global status Global variables Server String properties Numeric properties Following exception is seen in the JDBC trace logs: \n\n- JdbcConnection.executeFromList-new - java.sql.SQLException: The 'INFORMATION_SCHEMA.GLOBAL_STATUS' feature is disabled; see the documentation for 'show_compatibility_56'", "The above error is seen for MySQL versions 5.7.9 and higher. For MySQL versions prior to 5.7.9, selecting from the INFORMATION_SCHEMA tables produces an empty result set with a deprecation warning. \n\n \n\nNote: MySQL agent is packaged with ITCAM for Applications (IBM Tivoli Monitoring) and Application Performance Monitoring 8.1.x solutions.\n\n\nCAUSE\nFew tables in the INFORMATION_SCHEMA that are used by the agent to collect monitoring data are deprecated in the MySQL server versions 5.7.6 and above. Due to this deprecation these tables cannot be queried normally and cause an error when the agent tries to query these tables to get data.\n\n\nMore details about the MySQL INFORMATION_SCHEMA migration to performance_schema here: \n\nhttps://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html [https://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html]\n\n\n\nENVIRONMENT\nMySQL agent installed on MySQL Server versions 5.7.6 and above.", "RESOLVING THE PROBLEM\nUsers wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA. \n\nThis variable can be set from the MySQL command prompt as: \n\nset global show_compatibility_56=ON; \n\n \n\nThe default value of the variable 'show_compatibility_56' for MySQL server versions <=5.7.7 is ‘ON’ and for versions >=5.7.8 is ‘OFF’. \n\n \n\nUser can check the value of this variable by running the following command from the MySQL command prompt: \n\nshow global variables like \"show_compatibility_56\"; \n\n \n\nThis variable can also be set in the MySQL server configuration file also called as Option file.", "User needs to add the following line to the ‘my.cnf’ file (located at ‘<MySQL_Installation_Dir>/my.cnf’ for Windows and ‘/etc/my.cnf’ for UNIX/Linux): \n\nshow_compatibility_56=ON \n\n \n\nThe paths mentioned above are the default paths for the Option file. For more details on where your installation of MySQL server looks for the 'my.cnf' file, refer the URL: \n\nhttps://dev.mysql.com/doc/refman/5.7/en/option-files.html [https://dev.mysql.com/doc/refman/5.7/en/option-files.html] \n\n \n\nNote: Change in 'my.cnf' file will require a MySQL server re-start for the changes to take effect. \n\n \n\nMore details on the system variable 'show_compatibility_56' here: \n\nhttps://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56 [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56]\n\n\n\nPRODUCT ALIAS/SYNONYM\n Monitoring agent for MySQL Sever" ]

[ "Users wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA." ]

[ 2 ]

[ "IBM Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed. (CVE-2017-1341 ) - United States SECURITY BULLETIN\n\nSUMMARY\n MQOPEN call might succeed when it should have failed, when using generic profile authority matching for remotely defined MQ object. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]\nDESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8 \n\nMaintenance levels 8.0.0.0 - 8.0.0.7 \n\nIBM MQ Appliance V8", "Maintenance levels between 8.0.0.0 and 8.0.0.7 \n\nIBM MQ V9 \n\nMaintenance levels 9.0.0.0 - 9.0.0.1 \n\nIBM MQ V9 CD \n\nIBM MQ 9.0.1 - 9.0.3 \n\nIBM MQ Appliance V9 CD \n\nIBM MQ Appliance 9.0.1 - 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ V8.0 & IBM MQ Appliance V8.0\nApply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]\nApply fix pack 8.0.0.8 for IBM MQ Appliance [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]\nIBM MQ V9\nApply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]\nIBM MQ V9 CD\nUpgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\nIBM MQ Appliance V9 CD\nUpgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\n\nWORKAROUNDS AND MITIGATIONS\nNone.", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 30 Nov 2017: Initial version \n\n*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\nAccording 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." ]

[ "CVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]\nDESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)" ]

[ 0 ]

[ "IBM Tivoli Netcool/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States release notice; downloads; nco-p-nokia-nfmp; Probe for Nokia Network Functions Manager for Packet NEWS\n\nABSTRACT\n This new probe will be ready for downloading on July 20, 2017. \n\nCONTENT\n \n\nThis probe is written to support Nokia Network Functions Manager for Packet release 17.3.\n\nYou can download the package you require from the IBM Passport Advantage website:\n\nwww-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html [http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the probe for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CNL6HEN", "The Netcool/OMNIbus V8.1 version of this probe supports the following Operating Systems:\n\nAIX, Linux, Solaris and Windows.\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.", "Part number Operating System CNL6DEN AIX CNL6EEN Linux CNL6FEN Solaris CNL6GEN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]" ]

[ "You can download the package you require from the IBM Passport Advantage website:\n\nwww-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html" ]

[ 0 ]

[ "IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States TECHNOTE (FAQ)\n\nQUESTION\n Which WebSphere DataPower virtual edition fix pack can I upgrade to and downgrade from? \n\nCAUSE\nNot all scrypt4 fix packs are compatible with the 5.0.0.0 OVA files that were released in November 2012 and March 2013. If you upgrade or downgrade with an incompatible fix pack, unexpected errors might occur.\n\nANSWER\n Use the following links to determine which fix packs are compatible with your virtual deployment.\n\n\n\n\n * 5.0.0.0 from 30 November 2012 (build 220750)\n * 5.0.0.0 from 29 March 2013 (build 227007)\n * 5.0.0.5\n * 5.0.0.6\n * 5.0.0.8 or later\n * 6.0.0.0 or later\n\n\n\n\n\n\n\n\n\n\n\n5.0.0.0 from 30 November 2012 (build 220750) \nWhen your virtual deployment is the OVA file from 30 November 2012, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013. \n\nBack to top", "5.0.0.0 from 29 March 2013 (build 227007) \nWhen your virtual deployment is the OVA file from 29 March 2013, you can install only the 5.0.0.0 fix pack and 5.0.0.8 or later fix packs from Fix Central. On Fix Central, the 5.0.0.5 and 5.0.0.6 fix packs are for the 5.0.0.0 OVA release from 30 November 2013. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n5.0.0.5 \nWhen your virtual deployment is 5.0.0.5, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n5.0.0.6 \nWhen your virtual deployment is 5.0.0.6, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013. \n\nBack to top", "5.0.0.8 or later \nWhen your virtual deployment is 5.0.0.8 or later, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2]. \n\nNote: You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n6.0.0.0 or later \nWhen your virtual deployment is the 6.0.0.0 OVA file or a firmware upgrade through a 6.0.0.0 or later fix pack, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2]. \n\nBack to top", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Service Gateway XG45 Virtual Edition VMware ESXi, VMware ESX 5.0.0, 6.0.0 Edition Independent" ]

[ "You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit." ]

[ 2 ]

[ "IBM Datacap 9.0.1 FP1 - Readme doc - United States PRODUCT README\n\nABSTRACT\n IBM Datacap 9.0.1 FP1 - Readme doc \n\nCONTENT\nAbout IBM Datacap 9.0.1 Feature Pack 1 \n\nReview this document for installation instructions and other important information before you install IBM® Datacap 9.0.1 Feature Pack 1, which cumulatively contains all feature pack updates since IBM Datacap Version 9.0.1 was released. \n\n \n\nUpgrading to IBM Datacap 9.0.1 Feature Pack 1\n\n\nFrom v9.0.1: use the Patch Installer from Fix Central \n\nInstallation Steps \n\nPrerequisite: \n\n· 1) Microsoft .NET Framework 4.6.1 \n\n· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe \n\n \n\n· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 \n\n· Run: vcredist_x86.exe \n\n \n\nInstall: \n\n· 3) IBM Datacap 9.0.1.1 \n\n· Run: Update.exe\n\n\nFrom v9.0.0.0, 9.0.0.1, 9.0.0.2 & 9.0.0.3: use the Full Installer from Passport Advantage \n\nInstallation Steps \n\nPrerequisite: \n\n· 1) Microsoft .NET Framework 4.6.1", "· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe \n\n \n\n· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 \n\n· Run: vcredist_x86.exe \n\n \n\nInstall: \n\n· 3) IBM Datacap 9.0.1.1 \n\n· Run: Setup.exe \n\n \n\nImportant \n\nUpdates are required only on Servers and thick client computers. No update is required for \"thin client\" computers. You must upgrade all thick clients and servers to the same IBM Datacap version and feature pack. Different versions of IBM Datacap are not compatible; therefore, you cannot connect an IBM Datacap client with a server that has a different IBM Datacap server version or feature pack installed. Operating Datacap Client or Datacap Web with an incompatible version of Datacap Server, or allowing different versions to access one database, can result in loss of data. \n\nOnce installed, this feature pack cannot be uninstalled. However, you can use \"Uninstall or change a program\" in Control Panel to uninstall the entire Datacap product.", "The language you selected when installing Datacap 9.0.1 determined the language displayed in the InstallShield panels at that time, and also controls the language in which the InstallShield panels for this feature pack are displayed. \n\n \n\nAlerts! \n\n1) When running an update, the global ruleset DLLs are updated but the copies in each application are not updated. \n\nAs a result, new features and fixes are not applied to applications and customers might experience defects that have been fixed. \n\nThe global ruleset DLLs are in the Datacap\\RRS folder. The application copies are in the application DCO rules folder. \n\nCustomers must manually update the ruleset DLLs in each application where they are installed. \n\n2) When running an update, the master task configuration files are updated (Datacap\\ProgramSet) but the setting in applications are not updated (in application DCO folder).", "As a result, new features and fixes are not applied to applications and customers might experience problems that have been fixed. \n\nThe master task configuration is located in Datacap\\ProgramSet. The application settings are in the application DCO folder. \n\nCustomers must manually update the task setting in each application where they are installed. \n\n\nSystem requirements \n\nSelect the following link to see the hardware and software requirements for IBM Datacap. \n\nhttp://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html [http://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html] \n\n\nSearch for ‘Datacap’, then select \"Datacap \" \n\nCheck the box ‘Show feature packs’ and select 9.0.1 for Feature Pack 1*. \n\nNew features added to IBM Datacap 9.0.1 Feature Pack 1", "For a list of new features that were added to Datacap 9.0.1 in Feature Pack 1, see:\nHighlights of IBM Datacap 9.0.1 Feature Pack 1 [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm].\n\nhttp://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm]\n\n\nNew Qualifications \n\n \n\nIBM Datacap 9.0.1 Feature Pack 1 is qualified for use with: \n\n \n\n· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers; \n\nSee “Known Limitations” below for details) \n\n \n\n· Oracle 12c (12.1.0.2.0) \n\n \n\n· IBM Content Navigator 2.0.3 FP7 \n\n \n\nIssues fixed in IBM Datacap 9.0.1 Feature Pack 1", "APAR Number Summary IO23893 Clicking on QA link in tmweb - Administrator fails with error \"column named name already belongs to this datatable\" if using admin database on SQL server IO24025 Can not import file which name contains '0x905C' such as \"保険申告Updated.tif\" IO24067 When customer use https + non-activeX to upload, some images will be corrupted frequently IO24082 Lineitem does not show up in Datacap Desktop Verify panel IO24102 Enhance IMail actions to use standard naming convention for ID's of pages created. IO24104 Using LLLDAP certain users are not able to login even when they are in the same group. LDAP is across multiple domains. IO24138 Couldn't create DC_P8 FileNet object error; action FNP8_SetURL () on 9.0 FP 3 and 9.0.1 IO24140 aindex.aspx does not update DATAFILE variable when a page is moved in batch view IO24141 DCDesktop Exception when performing a lookup query against an Oracle database IO24144 Batch aborts during ExcelWorkbookToImage with specific XLSX file IO24168", "Page data is not generated when the page type is changed through batch structure in verify client of Datacap Navigator IO24169 when task has \"-\" and then change the batch status from hold to pending in edit job dialog, it will fail. IO24181 Unable to edit and enter values in multiple line edit box in tmweb Verifine panel IO24185 OCR_SR.RotateImageOCR_S () no longer compresses the TIFF image since applying 9.0 FP#2 was deployed IO24186 Thumbnail view of images is not activated in DcDesktop app until an image in batch tree view is clicked on IO24196 Setting a value to a custom column by main profile rule does not work. IO24199 Verify shortcut fails to show the batch list when the job name contains '( )' IO24205 System.OutOfMemory error returned by Datacap.Libraries.Convert.Outlook->OutlookMessageToImageAndAttachment () IO24213 Start bach panel non-overrideable validation not handled gracefully the second time around; Dc Desktop crashes IO24215 FNP8_CreateFolder () does not support /", "handle error in Italian IO24226 Page data failed to be shown in field details panel after running validation with some empty C nodes IO24227 CCO was not reloaded after running the rule so the re-OCR rule cannot take effect until relaunching the batch. IO24232 Main_Page no longer synch's up with custom data panel after switching from main_page to trailing page to main_page IO24249 Imprint.RedactParameters () converting color images to bitonal IO24249 Imprint.RedactByRegEx () only runs at Field level not at Page level but action help is slightly misleading IO24259 DcDesktop - certain columns in Job Monitor ONLY sort by Queue ID column IO24260 DSTUDIO: selecting ruleset \"import files - all : Scan\", returns message \"The Document Hierarchy refers to some nonexistent Rules.\". IO24282 MatchBarcodeBP throws an error in the rrs.log when processing non-barcode type pages. IO24289 tmweb fails to create setup file for a task if the app name begins with \"AP\" IO24381 SetNamePattern () with", "Convert.Unzip () is unable to resolve the naming pattern of the extracted image IO24384 Format and formatDescription are not supported in EDS IO24386 when the auto launch next batch is enabled, the page of the next verify page is not loaded. IO24387 Rescan status cannot be persisted after submitting if it is the only page in the batch IO24388 Split should not enabled on the page which is the only one in its parent document. IO24418 Images id are not numbered sequentially after fault with scanner occurs IO24427 Clicking on \"Build Doc\" button on custom panel generates exception error in DcDesktop App IO24439 Convert.ExcelWorkbookToImage () distorts the extracted tiff preventing GetBarcodeBP () from reading the barcode from the tiff image IO24447 rescanned page lost \"ScanSrcPath\" variable IO24461 Cannot paste value to a field if disable readonly on batch tree IO24470 After a job which jumped several tasks is edited via 'Edit Job' button, it could not be shown in Job Monitor IO24473 Batch", "is still in hold status even submitting it if session ever timeout. IO24475 Some Datacap css styles override ICN original ones, so impact ICN and other plugins. IO24477 image viewer error message does not conforming within image viewer. IO24486 Daeja ViewOne functionality of virtual as compared to Professional with DataCap", "Known limitations in IBM Datacap 9.0.1 Feature Pack 1", "Read this information to learn about known limitations in IBM Datacap 9.0.1 Feature Pack 1. \n\n \n\n \n\nComponent Summary TMWeb Scan Windows 10 supported with IBM Datacap 9.0.1 FP1 with the following known limitations:\n\n1. TMweb's \"IE Test\" page may result in a dialog box titled “Accusoft Twain Pro7 common 9.0.013” with the message \"picdll Load Library failed.”\n2. When trying to perform a Web scan with a Physical Scanner connected (via twain drivers) , ie using Web Vscan configured with scancl.aspx, the message \"picdll Load Library failed\" may be displayed. \n\nIf any of these messages appear, TMWeb scanning will not be possible. Medical Claims When in MClaims Prof Red/Black FixupScan, clicking \"Next LC\" button will advance to the next page and display the data for it (Type and Status), but will keep the previous page selected as well, and changes to Status (from \"Invalid Claim Type\" to \"New Claim\") will not be saved.", "Suggested workaround: \nAfter clicking \"Next LC\" button, which will show previous page and current page selected in the Batch View display, then click the current page node in the Batch View display to properly select only the current page. After this one can continue to change the page Status and click \"Next LC\" button and repeat workaround for the next page. [/support/docview.wss?uid=swg27047895&amp;aid=1] [/support/docview.wss?uid=swg27047895&amp;aid=1]" ]

[ "IBM Datacap 9.0.1 Feature Pack 1 is qualified for use with: \n\n \n\n· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers;" ]

[ 4 ]

[ "IBM Configuring file content extraction tools for IBM Connections Search - United States stellent file content conversion extraction TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nIBM Connections uses the Stellent (Oracle Outside In Technology) Export utility to extract text from documents of various types. The extracted text is added to the Search index allowing users to find documents based on the content. \n\nWhen the Stellent utility is not configured correctly, file content will not be extracted or indexed. Therefore, search results within IBM Connections will not contain any matches on file content. For any content extraction issues, follow the steps in this tech note. \n\n\nRESOLVING THE PROBLEM\n 1 Stellent installation \n\nEnsure that the following IBM Connections post-installation task has been carried out:\nhttp://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40 [http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40]", "2 Running the exporter in isolation from IBM Connections \n\nTo verify that the exporter is working correctly, you can run it on the command line in isolation from IBM Connections. To run the exporter executable on the command line, execute the following as the user that the Search WebSphere Application Server is running under: \n\n1. Change directory to the Stellent binary location. For example: \n\n $ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport\n\n2. Run the exporter command.\nThe exporter command has the following syntax: \n\n exporter inputpath=<path_to_input_file>\noutputpath=<path_to_extracted_text_output>\noutputid=FI_SEARCHTEXT\n\nFor example,\n$ ./exporter inputpath=/root/translation.pdf \\ outputpath=/root/testStellent.txt outputid=FI_SEARCHTEXT\n\nIf the text extraction worked successfully, you will see the following output: \n\nExport complete\n\nHowever, if you see a message like the one below, continue to step 3:", "./exporter: error while loading shared libraries: libsc_ex.so: cannot open shared object file: No such file or directory \n\n\n 3 Operating System Environment Variables \n\nEnsure that the operating system environment variables LD_LIBRARY_PATH and PATH are set correctly in Section 1. Both variables should contain the Stellent installation directory. To get the current values of the environment variables, run the following commands as the user that the Search WebSphere Application Server is running under:\n\n$ echo $LD_LIBRARY_PATH\n$ echo $PATH\n\nTo verify that the Stellent exporter executable can be found through the PATH environment variable, run the following command:\n\n$ which exporter\n\nThe output of this command should contain the full path to the exporter executable. For example:\n\n/opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter\n\n\n 4 WebSphere Environment", "Using the WebSphere Application Server administration console, ensure that the WebSphere environment variable FILE_CONTENT_CONVERSION points to the exporter executable. \n\nFor example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter\n\n\n 5 File Permissions \n\nEnsure that the user that the Search WebSphere Application Server is running under has sufficient privileges. They should have read/write/execute permissions on the exporter executable and read/write permissions on the other files in the Stellent installation directory.\n\n\n 6 Library compatibility \n\nVerify that the libraries deployed with Stellent are compatible with your platform.\n\nFor example, on a 64 bit Linux system:\n$ uname -a\nLinux host1 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux\n\n$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport\n$ file libsc_ex.so\nlibsc_ex.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped", "(Note that your Stellent installation may contain 32 bit libraries though you are running on 64 bit platform. This is not an issue, provided that the 32 bit compatible libraries are on the LD_LIBRARY_PATH or can be found on the shared library search path).\n\n\n 7 Shared library dependencies \n\nThe Stellent exporter executable has a number of dependencies on both the shared libraries packaged with Stellent and on shared libraries installed on your system. To verify that all the required shared libraries can be found, use the 'ldd' command on the exporter executable as follows:\n\n$ ldd -v exporter\n\nCheck the output of this command for any shared libraries marked as '=> not found'. \n\n Stellent shared library not found \n\nIf a Stellent shared library can't be found, then check that the setting of your LD_LIBRARY_PATH operating system environment variable contains the Stellent installation directory. \n\n System shared library not found", "If a system shared library can't be found, then you are missing a prerequisite library.\nNOTE: It is still possible to pick up libraries from locations other than those included in the LD_LIBRARY_PATH operating system environment variable, as long as they can be found elsewhere on the system's default search path. \n\nIn addition to libc.so.6, Stellent is dependent upon the following libraries: \nlibstdc++.so.5\nlibgcc_s.so.1 \n\nFor Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5.\n\n\n\n\n * \n *" ]

[ "In addition to libc.so.6, Stellent is dependent upon the following libraries: \nlibstdc++.so.5\nlibgcc_s.so.1 \n\nFor Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5." ]

[ 5 ]

[ "IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States IIB WMB FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to\nCVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139", "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2\n\nRemediation: \n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0" ]

[ "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to\nCVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139 \n\n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2" ]

[]

[ "IBM Software maintenance strategy for CICS TS and its embedded components - United States Libery Java ; 5655S9700 R660 660 R600 600 HCI6600 R670 670 R700 700 HCI6700 5655-S97 5655S97 ; 5655Y0400 R680 680 R800 800 HCI6800 R690 690 R900 900 HCI6900 R700 700 R000 000 HCI7000 R710 710 R100 100 HCI7100 5655Y0401 5655-Y04 5655Y04 KIXINFO PRODUCT DOCUMENTATION\n\nABSTRACT\n CICS TS support is delivering the information in this document to help customers plan for updates to CICS Transaction Server for z/OS (CICS TS) and related software components such as WebSphere Liberty and CICS Explorer. Installing APAR fixes (PTFs) using Recommended Service Upgrades (RSUs) as early as possible can help avoid problems that could result in a service call, and as long as you test appropriately, help reduce risks to your business. \n\nCONTENT", "[/support/docview.wss?uid=swg27048530&amp;aid=1]Embedded components in CICS TS [http://www-01.ibm.com/support/docview.wss?uid=swg27012749#delivering]\n[/support/docview.wss?uid=swg27048530&amp;aid=2]Update recommendations\n[/support/docview.wss?uid=swg27048530&amp;aid=3]Related information \n\n\n\n\n\n\n\n\n\nComponents in CICS TS\n\nCICS TS provides the following embedded runtime components:", "* Equinox\n Equinox is an implementation of the OSGi core framework specification and is provided for both OSGi JVM servers and for Liberty JVM servers. Service for these components is provided when and if required.\n \n \n * Apache Axis2™ \n Axis2 is an open source web services engine from the Apache Software Foundation and is used within CICS to provide the web service Java™ engine for the Axis2 JVM server environment. Service for this component is provided when and if required.\n \n \n * WebSphere Application Server Liberty Profile\n Liberty fix packs are provided on a regular basis through the CICS TS APAR delivery process and provide an update mechanism to keep the embedded CICS Liberty runtime synchronized with the fix packs provided by WebSphere Application Server. Keeping current helps you resolve problems faster for 2 reasons: * Liberty APAR fixes (known as ifixes) can only be delivered on the latest Liberty fix pack that has been supplied by the CICS APAR process.", "* CICS APAR fixes can require other fixes such as WebSphere Liberty fix packs.", "CICS Explorer and z/OS Explorer\nThe CICS Software Development Kit (SDK) for Java includes components from CICS for developing CICS Java applications. The CICS SDK for Servlet and JSP support includes Java Enterprise Edition (Java EE) and Liberty API libraries, and automatically installs required components such as WebSphere Developer Toolkit (WDT).\" Service for these components is provided through the CICS Explorer fix pack process when and if required. \n[/support/docview.wss?uid=swg27048530&amp;aid=4] Back to Top \n\n\nUpdate recommendations", "Recommended Service Upgrade (RSU) \nIBM recommends that you install all RSU [http://www-03.ibm.com/systems/z/os/zos/support/servicetest/] PTFs as preventive software maintenance for CICS TS. An RSU is a predefined collection of PTFs identified with a SOURCEID of RSUyymm, where yy indicates the last 2 digits of the year and mm indicates the month. [http://www-03.ibm.com/servers/eserver/zseries/zos/servicetst/]You can order an RSU [http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/]from ShopzSeries [https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp].\n\n\nEquinox and Apache Axis2\nThere is unlikely to be much maintenance for Equinox and Axis2. Service for these components is provided when and if required, meaning it will be on a case by case basis and in most cases this will be to resolve service requests.", "WebSphere Application Server Liberty Profile\nRefer to Updating Liberty profile for CICS TS and z/OS Connect EE to latest version [http://www.ibm.com/support/docview.wss?uid=swg21993579] for a list of APARs you will need to update CICS TS and z/OS Connect Enterprise Edition (EE) to the latest version of WebSphere Application Server Liberty profile. \n\n\nCICS Explorer\nIBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4. For further details see Latest version of CICS Explorer and CICS Tools plug-ins for CICS Explorer [http://www.ibm.com/support/docview.wss?uid=swg21404312]. \n\n\n\n[/support/docview.wss?uid=swg27048530&amp;aid=5] Back to Top", "Related information: \n * Update Strategy for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg27036014] \n \n * Fix list for IBM WebSphere Application Server Liberty [http://www.ibm.com/support/docview.wss?uid=swg27043863]\n \n * CICS TS embedded components [http://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.standards.doc/topics/supportedComponents.html]\n \n * Fixes by version for CICS products [http://www.ibm.com/support/docview.wss?uid=swg27008833]\n\n\n[/support/docview.wss?uid=swg27048530&amp;aid=6] Back to Top \n\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server" ]

[ "IBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4." ]

[ 6 ]

[ "IBM Correct understanding of CSV version of PVU reports - United States TECHNOTE (FAQ)\n\nQUESTION\n What files are in the audit snapshot generated by IBM License Metric Tool or IBM BigFix Inventory version 9.x, and what is the correct interpretation of the values in the CSV report files? \n\nCAUSE\nThe licensing reports in CSV format can be misinterpreted by some customers.\n\nANSWER\nAudit snapshot is a record of PVU and RVU MAPC utilization in your enterprise over a period of time. It contains the following files:", "* audit_trail.csv – all user actions that influence the final results of the licensing reports, for example, software classification actions, uploads and imports of the PVU table, software catalog, and charge units as well as changes to the VM managers. \n * data_conditions.txt – conditions that were used during the generation of the audit snapshot, including the reporting period and filters applied on the reports as well as general information about the time when the snapshot was generated, version of the PVU table and software catalog, status of the import, aggregation, and recalculation. \n * part_numbers.csv - part numbers that are listed in the software catalog for all software products that are included in any of the CSV report files. \n * pvu_full_capacity.csv - PVU full capacity license metric results \n * pvu_sub_capacity.csv - PVU subcapacity license metric results \n * rvu_full_capacity.csv - RVU full capacity license metric results", "* rvu_sub_capacity.csv - RVU subcapacity license metric results \n * bundling_definitions.csv - list of IBM software regardless of its license type and utilization together with details of the computers on which the software is installed \n * readme.txt - a link to this document (technote) \n * checksums.txt, signature.rsa, and pub_key.pem - files used by IBM auditors to verify the authenticity and correctness of the audit snapshot.", "Why some product instances are not listed in the CSV reports? \n\nCSV reports with information about PVU and RVU MAPC utilization (pvu_full_capacity.csv, pvu_sub_capacity.csv, rvu_full_capacity.csv, and rvu_sub_capacity.csv) list only software instances that were discovered during the license peak value time. If an instance was installed in your environment during the reporting period of the current audit snapshot but was not discovered during the license peak value time, the instance is not listed in the CSV reports. \n\nExample: \nThree instances of DB2 are installed. The reporting period is set to one month and DB2 license utilization is as follows: \n· Instance 1 uses the maximum of 100 PVUs, \n· Instance 2 uses the maximum of 300 PVUs, \n· Instance 3 uses the maximum of 500 PVUs.", "The license peak value occurs when the sum of PVU values for all instances is the highest and equals 800 PVUs (300 PVUs for instance 2 + 500 PVUs for instance 3). The peak occurs during the period that is marked with a red square (it is the license peak value time). The peak usage for instance 1 is outside of the red square. It means that this instance was installed in the environment during the current reporting period but was not discovered during the license peak value time. This instance is not listed in the CSV report. \n\n[/support/docview.wss?uid=swg21688543&aid=1] [/support/docview.wss?uid=swg21688543&aid=1] \n\n\nWhy some values from the CSV report do not relate back to what is displayed on the user interface?", "When all values from column M (Physical Server PVU Subcapacity) for a particular product are added, the obtained value is greater that the value that is displayed in the user interface. It happens due to the way that data is presented in CSV reports and on the user interface. \n\nThe All IBM Metrics and IBM PVU subcapacity reports are multilevel, and consist of the following levels:\n1. First level: a list of all products\n[/support/docview.wss?uid=swg21688543&aid=2] [/support/docview.wss?uid=swg21688543&aid=2] \n\n\n2. Second level: when you click a product name, you go to information about the physical server on which the product is installed.\n[/support/docview.wss?uid=swg21688543&aid=3] [/support/docview.wss?uid=swg21688543&aid=3] \n\n \n\n3. Third level: when you click the server name, you go to a list of virtual machines that run on this server and have the product installed. \n[/support/docview.wss?uid=swg21688543&aid=4] [/support/docview.wss?uid=swg21688543&aid=4]", "The audit snapshot is not multilevel. However, it has to present the same information that the report that is available in the user interface. Below is an excerpt from the audit snapshot that corresponds to the report that was presented on the screen shots above (some columns are hidden in the snapshot to simplify it).\n\n[/support/docview.wss?uid=swg21688543&aid=5] [/support/docview.wss?uid=swg21688543&aid=5] \n\n \n\nWhen values in column M are added, PVU consumption equals 480 PVUs. However, these values should not be added because they all refer to a single server (TLM_VM_423…) on which the four VMs run, not an individual VM that is listed in column P (Computer).", "The value in column M is repeated due to the way data needs to be presented in a CSV file. If you want to relate back the value from column M in the audit snapshot to the user interface report, it is the value that you can see in the column PVU Subcapacity Limit on the second level of the report. The value in column L relates back to the column CPU Core Subcapacity on the second level of the report. \n\n \n[/support/docview.wss?uid=swg21688543&aid=6] [/support/docview.wss?uid=swg21688543&aid=6]", "PVU and RVU MAPC subcapacity license terms specify license consumption only on the physical server level. PVU and RVU MAPC values cannot be calculated and presented on the virtual machine or LPAR level, and such data is not provided by License Metric Tool or BigFix Inventory. For more information about virtualization capacity license counting rules that are used for PVU and RVU MAPC calculation, see: \nhttp://www-01.ibm.com/software/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html [http://www-01.ibm.com/software/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html]\n\nRELATED INFORMATION\n Understanding CSV files with metric utilization [https://www.ibm.com/support/knowledgecenter/en/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/softinv/c_understanding_csv.html]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Security IBM BigFix Inventory" ]

[ "pvu_full_capacity.csv - PVU full capacity license metric results \n * pvu_sub_capacity.csv - PVU subcapacity license metric results" ]

[ 1 ]

[ "IBM Java SDK Upgrade Policy for the IBM WebSphere Application Server - United States upgrade policy TECHNOTE (FAQ)\n\nQUESTION\n What is the Java™ SDK upgrade policy for the IBM® WebSphere® Application Server? \n\nCAUSE\nUpdating to the latest compatible Java SDK could help you resolve problems more quickly.\n\nANSWER\nThe IBM WebSphere Application Server Java SDK can be upgraded to the latest service release for the same Java SDK version. \n\nList of WebSphere Application Server fix packs and the corresponding Java SDK versions [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\n\nPolicy Summary by WebSphere Application Server release:", "WebSphere Application Server V8.0, V8.5, V8.5.5\nStarting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.\n\nWebSphere Application Server V7.0\nAny V7.0 fix pack can upgrade to the latest Java SDK 1.6.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.1\nAny V6.1 fix pack can upgrade to the latest Java SDK 1.5.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.0\nAny V6.0 fix pack can upgrade to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.", "WebSphere Application Server V5.1\nAny V5.1 fix pack can upgrade to the latest Java SDK 1.4.1 and any V5.1.1 can be upgraded to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.0\nAny V5.0 fix pack can upgrade to the latest Java SDK 1.3.1 service release packaged for WebSphere Application Server.\n\n\n\nDetails of Java SDK Upgrade Policy\n\nWebSphere Application Server leverages the Java SDK as a base component. This results in unique support issues, including:\n\n\n * Matching Java SDK service releases to Application Server releases and fix packs\n \n \n * Delivering updates and fixes associated with the Java SDK on any given Application Server release.\n\n\nIn an effort to resolve customer Java SDK situations as quickly as possible, WebSphere Application Server Support has done a quickest-path-to-resolution analysis, determining the most direct way to collect problem information.", "In some cases, problem resolution might include finding shortcuts to resolve symptoms. One shortcut is an immediate upgrade to a newer compatible Java SDK service release, before gathering detailed problem determination data. \n\nThere are multiple advantages to performing an immediate Java SDK upgrade as a quicker path to resolution over a full Problem Determination (PD) process: \n 1. There is a continuous stream of fixes going into the Java SDK. Many problems encountered by customers are resolved by these fixes.\n \n \n 2. When a new problem is encountered, applying the latest Java SDK is a quick way to determine if related fixes change the symptoms or correct the problem.\n \n \n 3. Many documented Java SDK fixes have common symptoms. Frequently, limited PD data does not isolate the problem to a single root cause.\n \n\n\nThese factors highlight the advantage of applying a newer Java SDK before working through a full PD cycle.", "Java SDK and WebSphere Application Server software are updated frequently. To avoid compatibility issues for customers, WebSphere Application Server Support maintains this Java SDK Upgrade Policy. \n\nWebSphere Application Server Support details: \nhttp://www.ibm.com/software/webservers/appserv/support.html [http://www.ibm.com/software/webservers/appserv/support.html] \n\nIdentifying compatibility limitations between WebSphere Application Server releases and Java SDK service releases that have not been tested together reduces risk. \n\nImportant: Using a Java SDK not specifically packaged with WebSphere Application Server and supplied by IBM, or in violation of the Java SDK Upgrade Policy, is not supported by IBM WebSphere Application Server Support for Java SDK problems. RELATED INFORMATION\n Verify Java SDK version shipped with WebSphere fix pack [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005002]", "Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ "Starting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK." ]

[ 1 ]

[ "IBM Message RT7507E: Unable to initialize Repository: Default occurs in SystemOut.log after successful database transfer from Derby to DB2 - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nMessage RT7507E: Unable to initialize Repository: Default occurs in SystemOut.log after successful database transfer from Derby to DB2\n\nSYMPTOM\nYou may see this stacktrace in SystemOut.log after successfully completing the database transfer from Derby to DB2", "[6/25/12 16:10:19:213 CEST] 0000002e InitServlet E INI8504E:One or more initialization step failed. Please check the server log for details.\ncom.ibm.icm.jcr.RepositoryExistsException: RT7507E: Unable to initialize Repository: Default.\nat com.ibm.icm.jcr.RepositoryFactory.init(RepositoryFactory.java:218)\nat com.ibm.icm.jcr.RepositoryFactory.getRepository(RepositoryFactory.java:479)\nat com.ibm.icm.jcr.servlet.InitServlet.init(InitServlet.java:56)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:336)\nat com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1341)\nat com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:588)\nat com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:559)\nat com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:421)", "at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)\nat com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)\nat com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)\nat com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:422)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:714)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1160)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1369)\nat com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:638)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:967)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:766)", "at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2153)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)\nat com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)\nat com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)\nat com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659)", "CAUSE\nRoot cause was having another copy of icm.properties in .\\wp_profile\\PortalServer\\jcr\\lib\\com\\ibm\\icm, in this case by making a backup copy in the same directory with name icm-copy.properties\n\nRESOLVING THE PROBLEM\nRemove the copy so that the only file in .\\wp_profile\\PortalServer\\jcr\\lib\\com\\ibm\\icm is icm.properties\n\nRELATED INFORMATION\n Fiddler [http://www.fiddlertool.com]\nPlug-in MustGather [http://www-01.ibm.com/support/docview.wss?uid=swg21174894]\nWebSphere Portal tracing [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/WebSphere_Portal_runtime_logs_wp7]\nIHS Rewrite rules (mod_rewrite Apache module) [http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_apachemods.html]" ]

[ "Remove the copy so that the only file in .\\wp_profile\\PortalServer\\jcr\\lib\\com\\ibm\\icm is icm.properties" ]

[ 4 ]

[ "IBM Security Bulletin: Multiple Vulnerabilities identified in IBM® Java SDK affect WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio - United States SECURITY BULLETIN\n\nSUMMARY\n Multiple vulnerabilities in IBM® SDK Java™ Technology Edition, Version 6 used by WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in January 2018.\n\nThese issues are also addressed by WebSphere Application Server Network Deployment shipped with WebSphere Service Registry and Repository.", "VULNERABILITY DETAILS\nCVEID:CVE-2018-2633 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137885 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) \nCVEID:CVE-2018-2603 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2603]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3", "CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137855 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137855]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)", "CVEID:CVE-2018-2579 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2579]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to obtain sensitive information resulting in a low confidentiality impact using unknown attack vectors.\nCVSS Base Score: 3.7\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137833 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137833]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)", "CVEID:CVE-2018-2602 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2602]\nDESCRIPTION:An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact.\nCVSS Base Score: 4.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137854 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137854]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Service Registry and Repository V8.5 and V8.0 and WebSphere Service Registry and Repository Studio V8.5 are affected.", "REMEDIATION/FIXES\nFor all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.1_IJ04332 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-Studio-MultiOS-IFIJ04332]\n\nFor WebSphere Service Registry and Repository the issues are addressed by WebSphere Application Server.\n\n\n\nPrincipal Product and Version(s) Affected Supporting Product and Version WebSphere Service Registry and Repository V8.5 WebSphere Application Server V8.5.5 WebSphere Service Registry and Repository V8.0 WebSphere Application Server V8.0 \nRefer to the following security bulletin for vulnerability details and information about fixes addressed by WebSphere Application Server shipped with WebSphere Service Registry and Repository:", "Security Bulletin: Multiple Vulnerabilities in IBM® Java SDK affects WebSphere Application Server January 2018 CPU [http://www.ibm.com/support/docview.wss?uid=swg22013818] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 14 March 2018: 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. \n\nDISCLAIMER\nAccording 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." ]

[ "CVEID:CVE-2018-2633 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/137885 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)" ]

[ 1 ]

[ "IBM Error # 2070. The license server is down. Specific symptom number: 3 - United States TECHNOTE (FAQ)\n\nQUESTION\n We have network installations of IBM SPSS Statistics/Modeler. When the application is launched, the following errors are reported:\n\n\"The current license does not permit this job to continue.\"\n\nfollowed by...\n\n\"Error # 2070\nThe license server is down. Please check to see that the license server is running or ask your local SPSS coordinator to check the license server.\nThis command is not executed.\nSpecific symptom number: 3.\"\n\nThe Safenet Sentinel License Manager has been licensed and confirmed to be running. \nWhat is the problem? \n\nCAUSE\nThe above error can be caused by invalid values entered during the licensing phase of installing SPSS Statistics/Modeler or the client machine cannot reach the Sentinel License Manager host using the machine Hostname.\n\nANSWER\nPlease do the following to verify:", "1. Navigate to the IBM SPSS Statistics/Modeler directory and open \"spssprod.inf\", using any text editor. \n\n - By default, SPSS Statistics would store this file in: C:\\Program Files\\IBM\\SPSS\\Statistics\\xx\\ \n\n - By default, SPSS Modeler would store this file in: C:\\Program Files\\IBM\\SPSS\\Modeler\\xx.x\\bin\\\n\n2. Verify the \"DaemonHost\" value matches the Hostname or IP Address of the machine where the Safenet Sentinel License Manager is installed. \n\n - E.g. DaemonHost=MyLicenseServer or DaemonHost=127.0.0.1\n\nIf the DaemonHost value specifies redundant license servers, please do the following if you are using SPSS Statistics 22 (or earlier) or SPSS Modeler 16.0 (or earlier):\n\n\n a). Remove all license servers from the \"DaemonHost\" line and save the file.", "b). Create a system environment variable, called LSHOST, on each SPSS client with your redundant license servers as its value. Separate each redundant license server with a colon, e.g.\n==========================\nVariable: LSHOST\nValue: server1:server2:server3\n========================== \n\n\n\nIf the \"DaemonHost\" value is accurate and you are using a Hostname value, you have a name resolution problem. Error # 2070, Symptom number 3 typically means the SPSS client cannot connect to the name resolution database or the name resolution database does not contain a record for the machine where the SPSS Sentinel License Manager resides. To verify, please do the following:\n\n1. Run lswhere.exe (which is located in the SPSS directory, see above) from the problematic SPSS Client machine and take note of the displayed output. The following is an example of the output: \n\n\n==========================\nSentinel LM 8.x.x Search Tool For License Servers\nCopyright (C) 20xx Rainbow Technologies, Inc.", "Server Address : xxx.xxx.xxx.xxx\nServer Name : Machine_A\n========================== \n\n\nIf the Safenet Sentinel License Manager machine is not listed or you encounter the error, \"Error[17]: Probably no servers are running on this subnet.\", please add the following system environment variable to the IBM SPSS Statistics/Modeler client and run lswhere.exe again: \n\n\n==========================\nVariable: LSHOST\nValue: Name or IP address of the License Manager machine \n========================== \n\n\nFor information about defining environment variables, see the Network License Administrator's Guide. If using the LSHOST environment variable does not render the Safenet Sentinel License Manager machine, try using LSFORCEHOST instead.\n\n2. When you see the Safenet Sentinel License Manager machine name and corresponding IP address listed in the lswhere output, ping the displayed Server Name from a command line, e.g.\n\n\n==========================\nping Machine_A\n==========================", "An example of the resulting output is as follows:\n==========================\nUnknown host Machine_A\n========================== \n\n\nIf the ping command is unable to resolve the Server Name, you have a name resolution problem and must address it (with help from your IT Administrator/Help Desk team) before IBM SPSS Statistics/Modeler can acquire a license from the Sentinel License Manager.\n\nRELATED INFORMATION\n Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21641554]", "Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Statistics Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Platform Independent Not Applicable Business Analytics SPSS Amos Windows Not Applicable Business Analytics SPSS SamplePower Platform Independent Not Applicable \nHISTORICAL NUMBER\n 51910" ]

[ "The above error can be caused by invalid values entered during the licensing phase of installing SPSS Statistics/Modeler or the client machine cannot reach the Sentinel License Manager host using the machine Hostname." ]

[ 0 ]

[ "IBM Getting a warning message 'You do not have the correct administrator privileges' when attempting to license a SPSS Statistics product on Mac OS. - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You have successfully installed an IBM SPSS Statistics product on a Mac computer. When you start the License Authorization Wizard (LAW) to enter the authorization code for licensing.\n\nYou receive the following message:\n\n\n\"Warning! You do not have the correct administrator privileges to license this product. Log in as administrator and try again, or contact your network administrator to correct this issue.\n\n\"\n\nOnce this message is displayed the only option available is \"OK\" to click on and you cannot enter your authorization code. \n\nRESOLVING THE PROBLEM\nBelow is a picture of the warning: \n\n[/support/docview.wss?uid=swg21966637&aid=1] [/support/docview.wss?uid=swg21966637&aid=1]\n\nIf you encounter this message, perform the following procedure:", "1. If open, close the IBM SPSS Statistics product. \n 2. If open, close the License Authorization Wizard. \n 3. Open Finder. \n 4. Select the 'Go' menu. \n 5. Select the 'Utilities' menu. \n 6. Open the 'Terminal' program. \n 7. Type (copy/paste) the following command:\n \n cd /Applications/IBM/SPSS/Statistics/ \n 8. \n 9. Press Enter/Return. \n 10. Perform the procedure corresponding to the Statistics product version as described below:\n\n\nStatistics Release 20 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.", "Statistics Release 21 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 21\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 22 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 22\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\n\nStatistics Release 23 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 23\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.", "Statistics Release 24 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 24\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product. \n 7. \n 8. \n\nStatistics Release 25 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 25\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nTo confirm the changes have been made (1) In the Terminal window change directory to below path (example for release 22) \n\ncd /Applications/IBM/SPSS/Statistics/22/SPSSStatistics.app/Contents \n\nthen, type the following: \n\nls -l \n\n(2) Press Enter/Return.", "If you see some or all of subfolders shows a group ownership other than 'admin' (as displayed in Picture1), the procedure did not succeed. You will need to have your Mac IT support contact IBM SPSS Support for further assistance. \n\nPicture1:\n[/support/docview.wss?uid=swg21966637&aid=2] [/support/docview.wss?uid=swg21966637&aid=2]\n\nPicture 2: \n\nIf you see some or all of subfolders shows a group ownership of 'admin' (as displayed in Picture2), the procedure was successful.\n[/support/docview.wss?uid=swg21966637&aid=3] [/support/docview.wss?uid=swg21966637&aid=3]\n\nThis behavior is also reported on the following product correction report (APAR): [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\n[https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\nhttps://www.ibm.com/support/entdocview.wss?uid=swg1PI41134 [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\n\nAn IBM ID is required to access this material.", "If needed, an IBM ID may be created at https://ibm.biz/ibm_web_id [https://ibm.biz/ibm_web_id]\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]" ]

[ "Type (copy/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard." ]

[ 1 ]

[ "IBM Product upgrade installed a second instance of the DE, causing upgrade failure. - United States DEL2INST; Tivoli; Deployment; Engine; FQDN; Duplicate; acsi TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Deployment Engine should only have one instance installed on a server with IBM products installed. In this case, a second DE was installed, which caused the failure of the Product upgrade.\nError: Wrong Deployment Engine. \n\nSYMPTOM\nProduct install failed. You will get a message similar to this:\nYou are updating an instance of <Product name> that was installed using \nthe Tivoli Deployment Engine (DE) located at \"/home/nc_admin/.acsi_<Fully Qualified hostname>\". \nHowever you are now using the DE located at \"/home/nc_admin/.acsi_<hostname>\". \n\n\nWhen the DE is installed as non-root ( in this case nc_admin ), it will install the DE in the user home directory, in this case /home/nc_admin, and use the FQDN in the name: /home/nc_admin/.acsi_<Fully Qualified hostname>", "CAUSE\nBecause the two Product installs used different versions of JVM, the underlying Java is using \"hostname\" for one version of JVM, and \"Fully Qualified hostname\" for the other. The DE normally uses the FQDN appended to the \"acsi_\" string to create the DE directory:\n\nFor example, if the Product is being installed as user \"nc_admin\" and the entry in /etc/hosts is this:\n\nx.xx.xxx.xx server_name.corporation.net server_name\n\nThe hostname is \"server_name\"\nFully Qualified hostname (FQDN) is \"server_name.corporation.net\"\n\n\nENVIRONMENT\nUpgrading existing product that uses the Deployment Engine on a UNIX server\n\n\n\nDIAGNOSING THE PROBLEM\nOutput similar to this when the Product install fails: \n\nthe Tivoli Deployment Engine (DE) located at \"/home/nc_admin/.acsi_<Fully qualified hostname>\". \nHowever you are now using the DE located at \"<User_home>/nc_admin/.acsi_<hostname>\"\n\n\nRESOLVING THE PROBLEM\nThere are two options to fix this problem.", "1) Make sure the current upgrade is using the same version of JVM as the original install. \n\n2) Removing the newly created DE, which shouldn't have been created, then creating a link to the existing DE is the best work around in this case. The Product upgrade will see the link and add the information to the valid DE install. \n\n*IMPORTANT NOTE: The Product install failure message will tell you what instance of the DE is valid, please refer to the error message in the \"Symptom\" section above. \n\n At this point there will be the following in the DE_HOME directory: \n\n .acsi_<FQDN> ( Valid DE installation ) \n\n .acsi_<userid> ( link to .acsi_<FQDN> ) \n\n .acsi_<hostname> ( Invalid DE directory created by the failed Product upgrade ) \n\n This can be confirmed by referring to the Product install error. \n\n Removing the invalid DE and creating softlink: \n\n - Backup the original DE installation directory: <DE_HOME>/.acsi_<FQDN>", "- Move the new invalid DE directory to a backup directory: <DE_HOME>/.acsi_<hostname> \n\n - Create a soft link to the \"good\" DE install \n\n cd <DE_HOME> \n\n ln -s <DE_HOME>/.acsi_<FQDN> .acsi_<hostname> \n\n - Confirm the link was created successfully, it should look like this: \n> ls -lart \nlrwxrwxrwx 1 nc_admin ncoadmin <date> .acsi_<hostname> -> <DE_HOME>/.acsi_<FQDN> \n\n \n3) Retry the product install. You will need to confirm there is no required cleanup before retrying the Product upgrade." ]

[ "There are two options to fix this problem. \n\n1) Make sure the current upgrade is using the same version of JVM as the original install. \n\n2) Removing the newly created DE, which shouldn't have been created, then creating a link to the existing DE is the best work around in this case. The Product upgrade will see the link and add the information to the valid DE install." ]

[]

[ "IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593) - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition Version 6 and 7 that are used by IBM Image Construction and Composition Tool. These issues were disclosed as part of the IBM Java SDK updates in January 2015. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)", "CVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Image Construction and Composition Tool v2.2.1.3 \nIBM Image Construction and Composition Tool v2.3.1.0 \nIBM Image Construction and Composition Tool v2.3.2.0 \n\nREMEDIATION/FIXES\nThe solution is to apply the following IBM Image Construction and Composition Tool version fixes.\n\nUpgrade the IBM Image Construction and Composition Tool to the following fix levels:", "* For IBM Image Construction and Composition Tool v2.2.1.3 * IBM Image Construction and Composition Tool v2.2.1.3 Build 28\n 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 [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]\n \n For IBM Image Construction and Composition Tool v2.3.1.0 * IBM Image Construction and Composition Tool v2.3.1.0 Build 38", "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 [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]\n \n For IBM Image Construction and Composition Tool v2.3.2.0 * IBM Image Construction and Composition Tool v2.3.2.0 Build 12", "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 [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\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 21 July 2015: Original Version Published \n\n*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\nAccording 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." ]

[ "CVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)" ]

[]

[ "IBM Security Bulletin: Vulnerability in SSLv3 affects IBM HTTP Server (CVE-2014-3566) - United States SECURITY BULLETIN\n\nSUMMARY\n SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled by default in the Apache based IBM HTTP Server. \n\nVULNERABILITY DETAILS\nCVE ID: CVE-2014-3566 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566]\nDESCRIPTION: IBM HTTP Server could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plain text of encrypted connections.", "CVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 [https://exchange.xforce.ibmcloud.com/vulnerabilities/97013] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects all versions and releases of IBM HTTP Server (IHS) component in all editions of WebSphere Application Server and bundling products.\n\n\nREMEDIATION/FIXES\nThere is no separate interim fix for the PI27904 APAR that is associated with this issue, but the interim fix for APAR PI31516 (TLS Padding Vulnerability CVE-2014-8730 [http://www-01.ibm.com/support/docview.wss?uid=swg21692502]) includes the update for APAR PI27904. APAR PI27904 update disables SSLv3 by default for IHS 7.0 and newer, and adds the 'SSLProtocolEnable' directive into IHS 7.0. \n\nThe update for PI27904 will be included in fix packs 7.0.0.37, 8.0.0.10 and 8.5.5.4.", "WORKAROUNDS AND MITIGATIONS\nFor all releases and versions of Apache based IBM HTTP Server, IBM recommends disabling SSLv3: \n\n\nAdd the following directive to the httpd.conf file to disable SSLv3 and SSLv2 for each context that contains \"SSLEnable\":\n\n# Disable SSLv3 for CVE-2014-3566\n# SSLv2 is disabled in V8R0 and later by default, and in typical V7\n# and earlier configurations disabled implicitly when SSLv3 ciphers \n# are configured with SSLCipherSpec.\nSSLProtocolDisable SSLv3 SSLv2\n\nStop and restart IHS for the changes to take affect.\n\nNote: \n\n * If you start IHS with the -f command line argument, or you use the \"Include\" directive to include alternate configuration files, you may need to search those filenames for SSLEnable.\n\n * If you configure SSL with SSLEnable in the global (non-virtualhost) scope, you will need to move SSLEnable into a virtualhost scope to add SSLProtocolDisable", "IBM recommends that you review your entire environment to identify other areas that enable SSLv3 protocol and take appropriate mitigation (such as disabling SSLv3) and remediation actions. GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.", "REFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nHTTPS advisor fails when SSLv3 is disabled on backend servers [http://www-01.ibm.com/support/docview.wss?uid=swg21691795] TLS Padding vulnerability CVE-2014-8730 [http://www-01.ibm.com/support/docview.wss?uid=swg21692502]\n\n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 15 October 2014: original document published\n03 November 2014: added extra notes \n02 December 2014: added link to reference section\n28 January 2015: added links to CVE-2014-8730", "*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. \n\nDISCLAIMER\nAccording 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." ]

[ "For all releases and versions of Apache based IBM HTTP Server, IBM recommends disabling SSLv3: \n\n\nAdd the following directive to the httpd.conf file to disable SSLv3 and SSLv2 for each context that contains \"SSLEnable\":\n\n# Disable SSLv3 for CVE-2014-3566\n# SSLv2 is disabled in V8R0 and later by default, and in typical V7\n# and earlier configurations disabled implicitly when SSLv3 ciphers \n# are configured with SSLCipherSpec.\nSSLProtocolDisable SSLv3 SSLv2\n\nStop and restart IHS for the changes to take affect." ]

[ 2 ]

[ "IBM Unable to connect using network services: WebGUI or ssh after upgrading WebSphere DataPower firmware - United States TECHNOTE (FAQ)\n\nQUESTION\n Why can't I access the Web managment or ssh after upgrading firmware? \n\nCAUSE\nThis can occur if you are using a custom certificate or authentication for the management services and any of the associated certificates are expired. Expired certificates are removed at upgrade time.\n\nANSWER\nThe first step is to verify that the network is functioning correctly using these commands: \n\nshow int \n\nshow int mode \n\nshow route \n\n \n\nThose commands will show if there is any network activity as well as the ethernet link speed. \n\nOnce the network is confirmed, the quickest way to recover the web management and ssh services is to delete and recreate them with the default settings using the serial console. \n\nThe following commands will reset the RBM's, ACL's, WebGUI and SSH services to the default settings.", "Note: If the ssh is working, you may omit any commands with the ssh. \n\n \n\nconfig \n\nweb-mgmt \n\nno ssl \n\nexit \n\nwrite mem \n\ny \n\nno web-mgmt \n\nno ssh \n\nrbm \n\nreset \n\nexit \n\nacl web-mgmt \n\nreset \n\nexit \n\nacl ssh \n\nreset \n\nexit \n\nwrite mem (key step to remove the current settings) \n\ny \n\nweb-mgmt <ip to listen on or 0.0.0.0 for all> <port to use default is9090> \n\nssh <ip to listen on or 0.0.0.0 for all> <port to use default is22> \n\nwrite mem \n\ny \n\n \n\nOnce complete, test the service and confirm you can now access the appliance. Then you may work to configure any custom certificates or authentication settings desired. \n\nIf this does not resolve the issue Contact DataPower Support [http://www.ibm.com/support/docview.wss?uid=swg21236322]", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower B2B Appliance XB60 4.0.2, 4.0.1, 5.0.0, 6.0.0 All Editions Business Integration WebSphere DataPower SOA Appliances Firmware 4.0.2, 4.0.1, 5.0.0, 6.0.0, 6.0.1 Edition Independent Business Integration WebSphere DataPower XML Security Gateway XS40 Firmware 4.0.2, 4.0.1, 5.0.0, 6.0.0 All Editions" ]

[ "The following commands will reset the RBM's, ACL's, WebGUI and SSH services to the default settings. \n\nNote: If the ssh is working, you may omit any commands with the ssh. \n\n \n\nconfig \n\nweb-mgmt \n\nno ssl \n\nexit \n\nwrite mem \n\ny \n\nno web-mgmt \n\nno ssh \n\nrbm \n\nreset \n\nexit \n\nacl web-mgmt \n\nreset \n\nexit \n\nacl ssh \n\nreset \n\nexit \n\nwrite mem (key step to remove the current settings) \n\ny \n\nweb-mgmt <ip to listen on or 0.0.0.0 for all> <port to use default is9090> \n\nssh <ip to listen on or 0.0.0.0 for all> <port to use default is22> \n\nwrite mem \n\ny" ]

[]

[ "IBM BigFix Server unable to gather site content from sync.bigfix.com (error: Unexpected HTTP response: 404) - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Identifying a block between the BigFix Server and IBM BigFix's sync.bigfix.com content servers. \n\nSYMPTOM\nError messages similar to the following in the BESRelay.log on the BigFix server: \n\n * \n * \n * http://sync.bigfix.com/cgi-bin/bfgather/bessupport?Time=1452540085:\n * \n * \n * \n * \n * Error messages similar to the following in the GatherDB.log on the BigFix server:\n Mon, 11 Jan 2016 14:43:22 -0500 -- Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404\n\n\nNote: If the BES Support cannot gather for the first time the entire console is empty of its UI elements. \nCAUSE", "1. There is most likely an Intrusion Prevention System (IPS) between the BigFix server and our content sites at sync.bigfix.com that is dropping the download because it is detecting something in the download (one of the sites files) as being malicious. If you do not have an IPS between the BigFix server and the sync.bigfix.com servers; it may be the firewall or proxy appliance that is causing the issue. \n 2. Another cause might be that Internet Explorer Enhanced Security Configuration is enabled for Administrators on the BigFix Windows server machine.\n\nRESOLVING THE PROBLEM", "1. Check with the firewall/proxy/IPS/network admin and ask them to check the logs for dropped packets or downloads and to adjust the rules to allow the BES Support site content through. \n 2. Try turning off Internet Explorer Enhanced Security Configuration [https://blogs.technet.microsoft.com/chenley/2011/03/10/how-to-turn-off-internet-explorer-enhanced-security-configuration/] for Administrators to see if this resolves the issue." ]

[ "Check with the firewall/proxy/IPS/network admin and ask them to check the logs for dropped packets or downloads and to adjust the rules to allow the BES Support site content through. \n 2. Try turning off Internet Explorer Enhanced Security Configuration [https://blogs.technet.microsoft.com/chenley/2011/03/10/how-to-turn-off-internet-explorer-enhanced-security-configuration/] for Administrators to see if this resolves the issue." ]

[ 2 ]

[ "IBM PM66670: WHEN LOGIN ATTRIBUTE VALUE HAS \"=\" SIGN IN IT, INVALIDUNIQUENAME EXCEPTION IS THROWN. - United States FIXES ARE AVAILABLE\n8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4 [http://www-01.ibm.com/support/docview.wss?uid=swg24033190]\n8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24033606]\n8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24033754]\n8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24034672]\n8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24034673]\n8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24035457]\n8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24036729]", "8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24037574]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24039242]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]", "SUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.", "ERROR DESCRIPTION\n * UniqueName formation was incorrect which leads to login failure\n with 6/5/12 9:53:35:968 EDT] 00000087 UserRegistryI E\n SECJ0363E: Cannot create credential for the user tw=admin\n because of the following exception\n com.ibm.websphere.wim.exception.InvalidUniqueNameException:\n CWWIM0515E The 'tw=admin' entity is not in the scope of the\n 'defined' realm.\n at\n com.ibm.ws.wim.RepositoryManager.getRepositoryIndexByUniqueName(\n RepositoryManager.java:333)\n at\n com.ibm.ws.wim.RepositoryManager.getRepositoryID(RepositoryManag\n er.java:279)\n at\n com.ibm.ws.wim.ProfileManager.retrieveEntityFromRepository(Profi\n leManager.java:2800)\n at\n com.ibm.ws.wim.ProfileManager.retrieveEntity(ProfileManager.java\n :2916)\n at\n com.ibm.ws.wim.ProfileManager.getImpl(ProfileManager.java:1614)\n at\n com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(Profil\n eManager.java:364)\n at", "com.ibm.ws.wim.ProfileManager.get(ProfileManager.java:417)\n at\n com.ibm.websphere.wim.ServiceProvider.get(ServiceProvider.java:3\n 66)\n at\n com.ibm.ws.wim.registry.util.BridgeUtils.getEntityByIdentifier(B\n ridgeUtils.java:622)\n at\n com.ibm.ws.wim.registry.util.UniqueIdBridge.getUniqueUserId(Uniq\n ueIdBridge.java:202)\n at\n com.ibm.ws.wim.registry.WIMUserRegistry$6.run(WIMUserRegistry.ja\n va:568)\n at\n com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager\n Impl.java:5445)", "LOCAL FIX", "PROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server *\n ****************************************************************\n * PROBLEM DESCRIPTION: Virtual member manager (VMM) throws *\n * InvalidUniqueNameException when the *\n * login attribute value contains an *\n * equal sign \"=\". *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n VMM throws InvalidUniqueNameException when the login attribute\n value contains a \"=\". When an equal sign \"=\" is encountered in\n the login name for example 'tw=admin', VMM treats this as a", "distinguished name (DN) and hence the login fails.", "PROBLEM CONCLUSION\n * You need to set a custom property using the following\n command\n \n $AdminTask configureAdminWIMUserRegistry {-customProperties\n {\"com.ibm.ws.wim.registry.allowDNPrincipalNameAsLiteral\n =true\"} }\n \n When this property is set, VMM determines whether the login\n name ends with a baseEntry. If the login name does not end\n with a baseEntry it is not treated as a DN and the login is\n successful.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.4 and 8.5.0.1. Please refer to the\n Recommended Updates page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS", "APAR INFORMATION\n * APAR NUMBER\n PM66670\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 800\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2012-06-13\n \n \n * CLOSED DATE\n 2012-07-13\n \n \n * LAST MODIFIED DATE\n 2012-07-13\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBS APP SERV N\n \n \n * FIXED COMPONENT ID\n 5724H8800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R800 PSY\n UP\n \n \n * R850 PSY\n UP" ]

[ "You need to set a custom property using the following\n command\n \n $AdminTask configureAdminWIMUserRegistry {-customProperties\n {\"com.ibm.ws.wim.registry.allowDNPrincipalNameAsLiteral\n =true\"} }\n \n When this property is set, VMM determines whether the login\n name ends with a baseEntry. If the login name does not end\n with a baseEntry it is not treated as a DN and the login is\n successful.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.4 and 8.5.0.1." ]

[ 8 ]

[ "IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® Runtime Environment Java™ used by IBM API Connect. \n\nThese issues were disclosed as part of the IBM Java SDK updates in July 2017. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N)", "CVEID: CVE-2017-10116 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128877 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128877] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM API Connect V5.0.0.0 - V5.0.7.2\n\nREMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation/First Fix IBM API Connect \n\nV5.0.0.0 - 5.0.6.3 5.0.6.4 LI79805 Addressed in IBM API Connect V5.0.6.4.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:", "https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.3&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\nV5.0.7.0 - 5.0.7.2 5.0.8.0 LI79805 Addressed in IBM API Connect V5.0.8.0.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:", "https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \nIBM Java SDK July 2017 Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg22007002] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]", "CHANGE HISTORY\n 18 September 2017: original document published \n\n*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. \n\nDISCLAIMER\nAccording 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." ]

[ "CVEID: CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) \n\nCVEID: CVE-2017-10116 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128877 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128877] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H)" ]

[]

[ "IBM Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Business Monitor (CVE-2015-0138) - United States SECURITY BULLETIN\n\nSUMMARY\n WebSphere Application Server is shipped as a component of IBM Business Monitor. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]", "DESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. \nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nThe following products are affected:", "* WebSphere Business Monitor V7.0.0.x \n * IBM Business Monitor V7.5.x \n * IBM Business Monitor V8.0.1.x \n * IBM Business Monitor V8.5.5.0 \n * IBM Business Monitor V8.5.6.0\n\nREMEDIATION/FIXES\nTo remediate this issue, refer to Security Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http://www.ibm.com/support/docview.wss?uid=swg21698613]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nCVE-2015-0138 was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA", "CHANGE HISTORY\n 2015-03-30: Original document published \n\n*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. \n\nDISCLAIMER\nAccording 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. \n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21701544]", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Business Monitor Security AIX, Linux, Linux zSeries, Solaris, Windows 7.0.0.5, 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0" ]

[ "CVEID: CVE-2015-0138 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0138]\n\nDESCRIPTION: A vulnerability in various IBM SSL/TLS implementations could allow a remote attacker to downgrade the security of certain SSL/TLS connections. An IBM SSL/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS/SSL traffic between vulnerable clients and servers. \nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)" ]

[]

[ "IBM Limitations when deploying more than one Rule Execution Server console - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to deploy several Rule Execution Server (RES) Console in the same cluster, however there are some administrative interactions from RES components to RES console that may not work due to the presence of more than one RES management stack within the same administrative scope. \n\nSYMPTOM\nWhen a RES component makes an attempt to interact with a RES Console management stack (through a JMX invocation) the following exception may occur if more than one RES Console is deployed within an administrative cell: \n\n...\njava.lang.IllegalStateException \nat ilog.rules.res.mbean.util.IlrSingleMBeanInvocationHandler.invoke(Unknown Source)\n...", "Note: a similar exception can be seen when no RES Console is found so the first thing to verify is that a RES Console is completely deployed and that it passes the diagnostic properly before considering the issue in this present note.\n\n\nCAUSE\nThe scope of the management API (JMX) is typically that of the Cell (WebSphere), Domain (Weblogic) or Partition(JBoss). RES components that interact directly with the RES Console management stack normally expect to find exactly one RES Console within the this management scope : an error can arise from not finding a RES Console management stack, as well as finding more than one.\n\n\nRESOLVING THE PROBLEM\nCertain use cases are supported that involve deploying more than one RES console in a cluster, most notably for situations where a active/passive fail over is needed, see the following document for more information: Clustering Rule Execution Server (RES) management console [http://www.ibm.com/support/docview.wss?uid=swg21426014]", "However there is a number of limitations that one can face when several RES consoles are deployed within the same administrative cell, such as :", "1. The use of the API ilog.rules.session.IlrManagementSession (reference [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/html/api/html/ilog/rules/res/session/IlrManagementSession.html]) may fail with a java.lang.IllegalStateException as per the symptom above. In this situation, the only option is to deploy a single RES Console per cell. \n 2. With JRules 6.x deploying RSM in a cell where more than one RES console is deployed can lead to java.lang.IllegalStateException as per the symptom above when attempting to add an SSP through the RSM console. \n 3. With JRules 7.x DVS scenario suite executions initiated from Rule Studio to be run on a remote Java EE server in a cell where more than one RES console is deployed may fail with java.lang.IllegalStateException as per the symptom above.", "4. The use of interceptors (i.e. IlrSessionInterceptor implementations) may fail with a java.lang.IllegalStateException or an error message such as ilog.rules.res.session.interceptor.IlrSessionInterceptorException: Unable to find RuleApp /myruleapp/myruleset for use by the interceptor. In this situation, the only option is to deploy a single RES Console per cell.", "For situations 2. and 3. note that DVS and RSM are normally deployed in a non-production environment since they support the testing process of the rules prior to their deployment to production. So in practice it is not necessary to deploy multiple RES console instances for fail over purpose when in a testing environment. The recommendation is then to set up RES console and SSP in a testing cell that is separate from the production cell. In this testing cell, only one instance of RES console should be installed. RELATED INFORMATION\n#Setting up multipe XUs in one cell [http://www-01.ibm.com/support/docview.wss?uid=swg21400807]\n\n\n \n\n\nCross 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 Enterprise" ]

[ "It is possible to deploy several Rule Execution Server (RES) Console in the same cluster, however there are some administrative interactions from RES components to RES console that may not work due to the presence of more than one RES management stack within the same administrative scope." ]

[ 0 ]

[ "IBM Security Cache, LTPA Token, and Session Time Outs - United States session; cache; logout; login; timeout; time out; LTPA TECHNOTE (FAQ)\n\nQUESTION\n What happens when the Security Cache, LTPA Token timeout, and session time out? \n\nANSWER\nQuestion 1 \nWhat happens when the Security Cache times out? Will the user be asked to re-login?\n\nAnswer 1 \nNo. When using single sign-on (SSO), the Security Cache will refresh from the LTPA Token. If your LTPA Token is also expired, then the user will be asked to re-login. Also, the cache timeout period is reset every time that entry is hit. So, if the entry is hit 9 minutes into the 10 minute timeout period, the clock is reset at that time. So, instead of timing out in another minute, it is now reset for another 10 minutes, then if it's hit again in that time, it will get extended again. \n\nWhen using Local operating system for authentication, the user will be asked to login when the session times out, not the security cache.", "In V6.1, the Federated Repository has it's own cache settings. See the link under Related Information. \n\nQuestion 2 \n\n 1. Using a browser, we accessed a secured application, we provided the UserID (UserA) and a valid PW (Password1). A token was created. So far everything is working fine. \n \n 2. You manually changed the password for UserA in the LTPA (LDAP or custom registry) from Password1 to Password2. \n 3. Using a new browser we accessed the application providing UserA and the new password (Password2) a token was created and again everything is working as expected. \n \n 4. Using a another new browser we accessed the application providing UserA and the old password (Password1). You were surprised to notice that a token was created and UserA was able to access the application. \n\n\nAnswer 2 \nThe old password takes up to 1.5 times the security cache to disappear. It will also expire at the end of the LTPA token timeout.", "In IBM WebSphere Application Server V5.0.2 and later, you can purge a user from the security cache using an MBean interface. See the Related Information at the end of this article. \n\n\nQuestion 3 \nI want to force my users to re-login after a set \"inactivity timeout\" period. How is WebSphere Application Server supposed to work with regard to session timeouts and LTPA timeout. Answer 3 \nSee the answer to this question in item 9 of the following developerWorks article:\nhttp://www.ibm.com/developerworks/websphere/techjournal/1003_botzum/1003_botzum.html [http://www.ibm.com/developerworks/websphere/techjournal/1003_botzum/1003_botzum.html]\n\n\nQuestion 4 \nIf this is the case, can we expire or delete the LTPAToken cookie when the session expires? If so, what mechanism should we use?", "Answer 4\nYou can manually perform a form-based logout (as described in the Information Center) to request that the LTPAToken cookie be destroyed in the web browser, but within WebSphere Application Server, there is no functionality to automatically perform the form-based logout when the session times out. This would have to be performed programmatically.\n\nRELATED INFORMATION\n Federated Repository cache settings [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/uwim_ldapperfsettings.html]\nAuthentication cache settings [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/usec_sec_domains_cache.html]" ]

[ "When using single sign-on (SSO), the Security Cache will refresh from the LTPA Token. If your LTPA Token is also expired, then the user will be asked to re-login. Also, the cache timeout period is reset every time that entry is hit. So, if the entry is hit 9 minutes into the 10 minute timeout period, the clock is reset at that time. So, instead of timing out in another minute, it is now reset for another 10 minutes, then if it's hit again in that time, it will get extended again. \n\nWhen using Local operating system for authentication, the user will be asked to login when the session times out, not the security cache." ]

[ 0 ]

[ "IBM Format of XML-type ruleset parameters in SOAP messages with MTDS - United States XSD; schema; SOAP; web service TECHNOTE (FAQ)\n\nQUESTION\n How to format the value of an XML-type ruleset parameter in the SOAP request to a Monitored Transparent Decision Service (MTDS) ? \n\nCAUSE\nAs mentioned in the documentation for MTDS, XML parameters are represented by a String in the WSDL file.\n\nANSWER\nThe value of the parameter is the XML data corresponding to your input parameter XSD, either passed in a CDATA section or by escaping the XML special characters (replacing <, >, \", ' and & with &lt;, &gt;, &quot;, &apos; and &amp;).", "For more information on transparent decision services, refer to section \"Rule Execution Server > Introducing Rule Execution Server > Rule Execution Server basics > Transparent decision services and rule execution\" of the JRules V7.1 documentation [http://publib.boulder.ibm.com/infocenter/brjrules/v7r1/index.jsp?topic=/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global926.html].\n\nRELATED INFORMATION\n JRules V7.0 doc on transparent decision services [http://publib.boulder.ibm.com/infocenter/brjrules/v7r0m3/topic/com.ibm.websphere.ilog.jrules.doc/Content/Business_Rules/Documentation/_pubskel/JRules/ps_JRules_Global801.html]\nWODM V7.5 doc on transparent decision services [http://publib.boulder.ibm.com/infocenter/dmanager/v7r5/topic/com.ibm.dserver.res/Content/Business_Rules/_pubskel/Infocenter_Primary/ps_DS_Rule_Execution_Server1460.html]", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.5, 8.0, 7.5" ]

[ "The value of the parameter is the XML data corresponding to your input parameter XSD, either passed in a CDATA section or by escaping the XML special characters (replacing <, >, \", ' and & with &lt;, &gt;, &quot;, &apos; and &amp;)." ]

[ 0 ]

[ "IBM Exported dates to IBM FileNet Content Engine are one day off in IBM Datacap Taskmaster Capture - United States FileNet P8; FNP8; Export; yesterday; GMT; UTC TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Dates exported to IBM FileNet P8 Content Engine show yesterday's date when viewed by an IBM FileNet Content Engine client \n\nCAUSE\nIBM FileNet Content Engine stores all time stamps using UTC format. If a date is passed into IBM FileNet Content Engine with no time component then the time defaults to midnight UTC, which may indicate the prior date when converted back into local time.\nTaskmaster does not convert or handle dates in GMT/UTC and thus any date values must be formatted by the application rules prior to export to IBM FileNet Content Engine\n\n\nRESOLVING THE PROBLEM\nModify the date/time value into proper GMT/UTC format of YYYY-MM-DDTHH:MM[:SS] and then add a time offset to account for the GMT time difference, e.g. YYYY-MM-DDTHH:MM:SS-HH:MM, prior to export to FileNet P8.", "The action IsFieldDateWithReformat from the Validations library can be called with a parameter of \"s\" (no quotation marks) to format a local date/time value to UTC; a GMT offset can be appended to a UTC value with any standard action such as rrSet from the rrunner library.\n\nExample 1: \n\nDescription Field Value (Case A) Field Value (Case B) Data captured 05/31/2012 15:00 05/31/2012 IsFieldDateWithReformat(s) 2012-05-31T15:00:00 2012-05-31T00:00:00 rrSet(@F+-07:00,@F) 2012-05-31T15:00:00-07:00 2012-03-15T00:00:00-07:00 Here the initial field value is first transformed to UTC. The rrSet action is called to append the GMT offset \"-07:00\" to the field value.", "Example 2: Description Field Value (Case A) Field Value (Case B) Data captured 05/31/2012 15:00 05/31/2012 IsFieldDateWithReformat(s) 2012-05-31T15:00:00 2012-05-31T00:00:00 rrSet(@F+@CHR(43)+07:00,@F) 2012-05-31T15:00:00+07:00 2012-03-15T00:00:00+07:00 Here the initial field value is first transformed to UTC. The rrSet action is called to append the GMT offset \"+07:00\" to the field value, @CHR is used to avoid conflict with the concatenation operator. \n\nNote: IBM FileNet Content Engine may have a back end setting for Daylight Savings Time (DST), thus modifying the GMT offset to account for DST may not be necessary. \n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet P8 Platform Content Engine Windows, AIX, HP-UX, Linux, Solaris 5.2, 5.1, 5.0, 4.5, 4.2, 4.1" ]

[ "Modify the date/time value into proper GMT/UTC format of YYYY-MM-DDTHH:MM[:SS] and then add a time offset to account for the GMT time difference, e.g. YYYY-MM-DDTHH:MM:SS-HH:MM, prior to export to FileNet P8. \n\n\nThe action IsFieldDateWithReformat from the Validations library can be called with a parameter of \"s\" (no quotation marks) to format a local date/time value to UTC; a GMT offset can be appended to a UTC value with any standard action such as rrSet from the rrunner library." ]

[]

[ "IBM Locked files encountered during Windows agent silent installation - United States locked files; silent; remote; installation; Windows TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A silent installation of the Windows NT agent aborts due to locked files. \n\nSYMPTOM\nThe Customer's AbortIBMTivoliMonitoring yyyymmdd hhmm.log (for example AbortIBMTivoliMonitoring20150409 1014.log) shows the following messages & errors.", "4-9-2015 10:15:22 CheckLockedFiles - Search directory C:\\IBM\\ITM for locked files.\n4-9-2015 10:15:22 CheckLockedFiles - File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\ISSetup.dll is locked.\n4-9-2015 10:15:22 File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\ISSetup.dll could not be renamed, errors may occur.\n4-9-2015 10:15:22 CheckLockedFiles - File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\setup.exe is locked.\n4-9-2015 10:15:22 File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\setup.exe could not be renamed, errors may occur.\n4-9-2015 10:15:22 CheckLockedFiles - Directory C:\\IBM\\ITM has locked files.\n4-9-2015 10:15:22 CheckedLockedFiles - silent install processing\n4-9-2015 10:15:22 CheckedLockedFiles - Check[C:\\IBM\\ITM\\InstSpbs\\silent_winos622_64bit_prod.txt] for Locked Files=continue\n4-9-2015 10:15:22 CheckLockedFiles - Locked files not present.\n4-9-2015 10:15:22 CheckLockedFiles - Directory C:\\IBM\\ITM - return TRUE\n4-9-2015 10:15:22 Directory C:\\IBM\\ITM has locked files.\n4-9-2015 10:15:22 Correct and launch setup again.", "4-9-2015 10:15:22 Directory C:\\IBM\\ITM has locked files, unable to continue.\n4-9-2015 10:15:22 SEVERE: ERROR - Install aborted.", "CAUSE\nA limitation for remote deployment and silent installations indicates:\nA silent installation terminates if product files are locked. This behavior ensures that the installer does not overwrite product files that are currently running. The best practice is to shut down all components, including monitoring servers, portal server, and portal clients before you perform any product upgrade. This limitation only affects silent installations. Installations through the installation wizard is not affected.\n\n\nENVIRONMENT\nAny Windows version \n\nAny ITM component installed silently\n\n\nDIAGNOSING THE PROBLEM\nLook in <ITMHOME>\\InstallITM for a file name with syntax similar to: \nAbortIBMTivoliMonitoring<DATE TIME>.log\n\nFor example:\nAbortIBMTivoliMonitoring20150409 1014.log", "RESOLVING THE PROBLEM\nWorkaround: Use the following method to resolve the problem:\n1. Search the installation log for instances of the CheckLockedFiles string. Locked files are listed at these places. Locked files are files that might need to be upgraded during an installation, and because they are in use (locked) the silent install terminates.\n\n\n2. Identify the process that is locking the files.\n\n\n3. Stop the process.\n\n\n4. Prevent file locking by modifying the response file for installation file. This step is required when a silent installation has terminated.", "a. Open the response file in a text editor. In many cases, the file in which you make this modification is named silent.txt. On Windows, the file to modify is the NT_Silent_Install.txt file that is located on the monitoring server.\nb. Add the following line to the [INSTALLATION SECTION] area of your silent install response file:\nLocked Files=continue\nIf you apply any other value or assign no value for this parameter, silent installations fail when locked files exist.\nc. If Locked Files=continue is used in a silent install or remote deploy, the computer MUST be rebooted before ITM is brought up or another install is run. This is mandatory or the <ITMHOME> directory could become corrupt. If the <ITMHOME> directory becomes corrupt, all of ITM will have to be uninstalled and reinstalled.\n\n\n5. Run the silent installation again." ]

[ "A limitation for remote deployment and silent installations indicates:\nA silent installation terminates if product files are locked. This behavior ensures that the installer does not overwrite product files that are currently running. The best practice is to shut down all components, including monitoring servers, portal server, and portal clients before you perform any product upgrade. This limitation only affects silent installations. Installations through the installation wizard is not affected." ]

[ 3 ]

[ "IBM Failover to secondary node under MSCS and the queue manager will not start - United States HL083112 mqlpgrlg ZX000001 ExecCtrlrMain lpiRC_LOG_NOT_AVAILABLE mscs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You attempt to failover from the primary to secondary node under MSCS. Your WebSphere MQ queue manager fails to come up on the secondary node, and errors are generated. \n\nSYMPTOM\nThe sequence seen in the FDC files show:\n\n\nProbe Id :- HL083112 \nComponent :- mqlpgrlg \nProcess Name :- D:\\Programs\\MQSeries\\bin\\amqzxma0.exe \nMajor Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR \nMQM Function Stack\nkpiStartup\napiStartup\nalmPerformReDoPass\nhlgScanLogBegin\nmqlpgrlg\nxcsFFST\n\n\nProbe Id :- ZX000001\nComponent :- ExecCtrlrMain \nProcess Name :- D:\\Programs\\MQSeries\\bin\\amqzxma0.exe \nMajor Errorcode :- xecF_E_UNEXPECTED_RC \nMinor Errorcode :- lpiRC_LOG_NOT_AVAILABLE \nProbe Description :- AMQ6118: An internal WebSphere MQ error has occurred \n(7017) \nArith1 :- 28695 7017 \nMQM Function Stack\nxcsFFST", "CAUSE\nThis is caused by a logger failure at restart due to missing or damaged logs.\n\n\nRESOLVING THE PROBLEM\nRename the file amqalchk.fil, which is found under mq\\qmgrs\\qmgrname\\ on the shared drive (to something like amqalchk.fil_OLD); then restart the queue manager.\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMQ / MQ" ]

[ "Rename the file amqalchk.fil, which is found under mq\\qmgrs\\qmgrname\\ on the shared drive (to something like amqalchk.fil_OLD); then restart the queue manager." ]

[ 1 ]

[ "IBM Error when launching Scan task from Datacap Desktop. - United States Desktop; No data; Scan; VScan TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Receiving the following error message when attempting to launch up Scan task from Datacap Desktop:\n\"This batch has no data to process. Aborting.\" \n\nThen followed by this error: \n\"Unable to run queue.\" \n\nDIAGNOSING THE PROBLEM\nThe panel for TravelDocs contained a value with all upper-case letter [eg. TRAVELDOCS], which caused the error to occur when attempting to launch the Scan task from Datacap Desktop\n\nRESOLVING THE PROBLEM\nThe \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity). \n\nLogon to TMWeb client. \n\nGo to Administrator tab \n\nSelect the VScan task from the Workflow. \n\nClick Setup under Program. \n\nThen change the value of the Panel to match what is in Datacap Studio. For example \"TRAVELDOCS\" to \"TravelDocs\" \n\nClick Save", "[/support/docview.wss?uid=swg21967312&aid=1] [/support/docview.wss?uid=swg21967312&aid=1]\n\n[/support/docview.wss?uid=swg21967312&aid=2] [/support/docview.wss?uid=swg21967312&aid=2]\n[/support/docview.wss?uid=swg21967312&aid=3] [/support/docview.wss?uid=swg21967312&aid=3]" ]

[ "The \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity)." ]

[ 0 ]

[ "IBM HPDMG0759W error when creating the AMJRTE properties file - United States TAM; run-svrssl-config; svrssl; HPDMG0759W; AMJRTE TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhen executing the \"run-svrssl-config\" task via the ConfigEngine to create the AMJRTE properties file, you receive the following error:\n\nCommand to run is: java com.tivoli.pd.jcfg.SvrSslCfg -action config -admin_id sec_master -admin_pwd ****** -appsvr_id myserverid -port 7223 -mode remote -policysvr <hostname>:7135:1 -authzsvr <hostname>:7136:1 -cfg_file C:\\IBM\\WebSphere\\AppServer\\java\\jre/PdPerm.properties -key_file C:\\IBM\\WebSphere\\AppServer\\java\\jre/lib/security/pdperm.ks\n[java] Exception in thread \"main\" \n[java] [\n[java] HPDMG0759W The user name already exists in the registry.\n[java] ]\n[java] at com.tivoli.pd.jutil.bo.a(bo.java:98)\n\n\nENVIRONMENT\nConfiguring WebSphere® Portal 6.1 with Tivoli® Access Manager 6.0\n\nDIAGNOSING THE PROBLEM", "The user name referenced in the error message refers to the appsvr id used in the SvrSslCfg command. The value for this user name is set via the following parameter in wkplc_comp.properties:\n\nwp.ac.impl.PDServerName\n\n\nRESOLVING THE PROBLEM\n \n\nTo avoid the error, do one of the following steps before executing the run-svrssl-config task:\n\na) Use a unique value for wp.ac.impl.PDServerName\n\nor\n\nb) Run the following command manually from a command prompt on the portal server to remove the appsvr_id value from Tivoli Access Manager's repository: \n\njava com.tivoli.pd.jcfg.SvrSslCfg -action unconfig-admin_id sec_master -admin_pwd ****** -appsvr_id myserverid -port 7223 -mode remote -policysvr <hostname>:7135:1 -authzsvr <hostname>:7136:1 -cfg_file C:\\IBM\\WebSphere\\AppServer\\java\\jre/PdPerm.properties -key_file\n\n\nRELATED INFORMATION\n#Creating the AMJRTE properties file [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/security/cfg_tam_auth.html]", "* \n *" ]

[ "To avoid the error, do one of the following steps before executing the run-svrssl-config task:\n\na) Use a unique value for wp.ac.impl.PDServerName\n\nor\n\nb) Run the following command manually from a command prompt on the portal server to remove the appsvr_id value from Tivoli Access Manager's repository: \n\njava com.tivoli.pd.jcfg.SvrSslCfg -action unconfig-admin_id sec_master -admin_pwd ****** -appsvr_id myserverid -port 7223 -mode remote -policysvr <hostname>:7135:1 -authzsvr <hostname>:7136:1 -cfg_file C:\\IBM\\WebSphere\\AppServer\\java\\jre/PdPerm.properties -key_file" ]

[ 1 ]

[ "IBM MustGather: Object Request Broker (ORB) problems with WebSphere Application Server - United States MustGather; MustGather; MustGather; ORB; Object Request Broker; ISA; collector; autopd; auto pd; MustGatherDocument TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collecting data for problems with the IBM WebSphere Application Server Object Request Broker component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data. \n\nRESOLVING THE PROBLEM\n \n\nTAB NAVIGATION\n * Learning more [http://www.ibm.com/support/docview.wss?uid=swg21245077]\n * Troubleshooting [http://www.ibm.com/support/docview.wss?uid=swg21237101]\n * Collecting data- selected tab,\n\nCollecting data for problems with the IBM WebSphere Application Server Object Request Broker component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data..\n\nCOLLECTING DATA MANUALLY", "Object Request Broker specific MustGather information 1. Where does the problem occur? Between what components?\n \n \n 2. What is your topology?\n \n \n 3. What are the symptoms noticed?\n \n \n 4. How do you recover from this problem?\n \n \n 5. What are the hostnames of the Client and the Application Servers?\n \n \n 6. How often does this problem occur?\n \n \n 7. Is there a firewall installed between the failing components?\n \n \n 8. Can you successfully ping the server from the remote client? Can you ping the client from the remote server?\n \n \n 9. Has this problem always occurred or has it just started to occur? If it just started, what changes were made?\n \n \n 10. Clear out the logs in the install_root/logs directory, then recreate the problem.\n \n \n 11. Collect the following files: * The newly created logs.\n \n \n * Answers to the preceding questions.", "* For releases of WebSphere Application Server versions 5.0 and 6.0 * collector.[sh/bat] output\n \n \n \n \n * Any additional information you think might relate (topology, symptoms, and so on) to IBM.\n \n Note: Additional ORB, Security, or WLM traces might be required.", "Additional MustGather information for ORB interoperability problems", "1. What third-party ORB are you trying to use?\n \n \n 2. What version is the third-party ORB using?\n \n \n 3. What language is the third-party ORB using? (C++ or Java)\n \n \n 4. What platform is the third-party ORB running on?\n \n \n 5. What platform is WebSphere Application Server running on?\n \n \n 6. Does the problem or error occur consistently or randomly?\n \n \n 7. Is the problem reproducible? If so, what are the steps?\n \n \n 8. Is WebSphere Application Server being used as the server or client to the third-party ORB?\n \n \n 9. Has this worked before, or is this a new configuration?\n \n \n 10. Have you tried using the approach recommended in the CORBA Interop samples?\n \n \n 11. Where was the Interface Definition Language (IDL) compiled (what tool was used)?", "Note: See the WebSphere Application Server detailed system requirements [http://www.ibm.com/support/docview.wss?uid=swg27006921] for the information related to the third party ORB Supported/Tested, then select WebSphere Version > Server Type > Search on third-party ORB in Software Requirements List.", "A collector output is required for the WebSphere Application Server support team to troubleshoot an ORB issue. By providing the collector output, your configuration can be reviewed to help get a better understanding of your topology and settings. \n\n\n * Detailed instructions on how to run the collector program can be found at the following link:\n\n\nhttps://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.nd.doc/ae/ttrb_runct.html [https://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.nd.doc/ae/ttrb_runct.html] \n\nMake sure you do not run the collector program from within the WebSphere Application Server product installation root directory. This will lead to an error. Make a working directory where you can start the collector program. \n\nOnce you have run the collector program from the dmgr, upload the collector.jar file that is created.", "If specific ORB traces have been requested by the Application Server support team, use the following instructions:\n\nNOTE: In most cases, support is going to need a matching client and server side trace to troubleshoot the issue. In some cases, they may even need traces from the nodeagent.", "* WebSphere Application Server V6.1, V7.0, V8.0, and V8.5 ORB trace instructions \n You can review the following video that walks you through setting up the ORB trace in the Administrative Console. It goes through each step listed below to make sure the ORB trace is enabled correctly. \n \n \n 1. From the Administrative Console, select Servers > Application Servers > server_name > Change Log Details Levels.\n \n \n 2. Remove any previous entries in the text field type the following:\n \n *=info:ORBRas=all\n \n \n 3. Apply and save changes.\n \n \n 4. Select Servers > Application Servers > server_name > Diagnostic Trace Service.\n \n \n 5. Change the Maximum Number of Historical Files to 10 and maximum file size to 50mb\n \n \n 6. Apply and save changes.\n \n \n 7. Enabling Comm Trace:\n \n Application Server", "From the Administrative Console, Select Servers > Application Servers > server_name > Container Services > ORB Service. Select the Orb Tracing check box to enable Comm Tracing.\n \n Node Agent\n From the Administrative Console, select System Administration >Node Agent > nodeagent > ORB Service. Select the Orb Tracing check box to enable Comm Tracing.\n \n Deployment Manager\n From the Administrative Console, Select System Administration > Deployment Manager > ORB Service. Select the Orb Tracing check box to enable Comm Tracing.", "NOTE: You will need to do a server restart for the Comm Tracing to be captured in the trace.log file. You can also leave the Orb Tracing check box checked permanently in case you run into another ORB issue in the future. That way, you don't have to do another server restart for the trace to be captured. Leaving the Orb Tracing check box checked won't log any data to a trace log unless you have the ORBRas=all trace string enabled (Step 2 above). This means it won't cause any performance issues or affect anything else in the server. \n 8. Apply and save changes.\n \n \n 9. Restart the sever and recreate the problem\n \n \n 10. Collect the following data:\n \n profile_root/logs/server_name/trace.log\n \n * \n * profile_root\n * /logs/ffdc folder\n \n * \n \n * NOTE: \n * \n * date\n * \n * time\n * \n *", "* Stand Alone Java Client ORB Trace Instructions 1. Start the client program with the \"-D\" arguments to specify the trace settings\n \n -Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.Debug.Output=client.log\n \n \n 2. The ORB trace output is captured in the path pointed by com.ibm.CORBA.Debug.Output.\n \n If the com.ibm.CORBA.Debug.Output parameter is not specified, the ORB trace output is captured in a unique trace file named orbtrc.<timestamp>.txt in the current directory of execution.\n \n \n 3. Collect the following file:\n \n orbtrc.<timestamp>.txt \n \n \n \n \n \n * J2EE Client Trace Instructions 1. Start the launchClient script with the following arguments to enable the trace:\n \n install_root/bin/launchClient.sh <ear_file> -JVMOptions=\"-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true\" -CCtrace=ORBRas=all -CCtracefile=orbtrace.txt -CCtraceMode=basic", "Note: For Windows installations, use launchClient.bat instead of launchClient.sh\n \n 2. The ORB trace output is captured in a unique trace file named orbtrace.txt in the current directory of execution.\n \n \n 3. Collect the following file:\n \n orbtrace.txt\n \n \n \n * How to check IBM® Java™ ORB build version in WebSphere® Application Server.", "* <washome>/java/bin/java -Xbootclasspath/p:<washome>/java/jre/lib/ext/ibmorb.jar com.ibm.rmi.util.Version\n \n * Follow instructions to send diagnostic information to IBM support [http://www.ibm.com/support/docview.wss?uid=swg21153852] [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852]\n \n\n\n\nFor a listing of all technotes, downloads, and educational materials specific to the ORB component, search the WebSphere Application Server support site [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_Application_Server].", "Related information [http://www.ibm.com/support/docview.wss?uid=swg21153852] \nSubmitting information to IBM support [http://www.ibm.com/support/docview.wss?uid=swg21153852] \nSteps to getting support for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/support/appserver_support.html] \nMustGather: Read first for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21145599] \nTroubleshooting guide for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg27005324] \n\n\nEXCHANGING DATA WITH IBM SUPPORT\nTo diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:", "* Service Request (SR)\n * E-mail \n * FTP to the Enhanced Customer Data Repository (ECuRep)\n\n\n\n\nInstructions for exchanging information with IBM Support [http://www.ibm.com/support/docview.wss?uid=swg21153852]\n\nREAD FIRST AND RELATED MUSTGATHERS\nMustGather: Read first for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21145599]\n\n\n\n\n Classloader problem [http://www.ibm.com/support/docview.wss?uid=swg21196187] Security Problem [http://www-01.ibm.com/support/docview.wss?uid=swg21470063] JNDI Problem [http://www.ibm.com/support/docview.wss?uid=swg21143296] JTS Problem [http://www.ibm.com/support/docview.wss?uid=swg21153216] Session Management Problem [http://www.ibm.com/support/docview.wss?uid=swg21192604] Workload Management Problem [http://www.ibm.com/support/docview.wss?uid=swg21052165]", "RELATED INFORMATION\n Recording your screen to share with IBM Support [https://www.ibm.com/developerworks/community/blogs/IBMElectronicSupport/entry/recording_your_screen_to_share_with_support?lang=en]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK AIX, HP-UX, Linux, Solaris, Windows 8.0, 7.1, 7.0, 6.1, 6.0.2, 6.0 Application Servers WebSphere Application Server Object Request Broker (ORB) AIX, HP-UX, Linux, Solaris, Windows 9.0, 8.5.5, 8.5, 8.0, 7.0, 6.1 Base, Network Deployment" ]

[ "<washome>/java/bin/java -Xbootclasspath/p:<washome>/java/jre/lib/ext/ibmorb.jar com.ibm.rmi.util.Version" ]

[ 13 ]

[ "IBM Security Bulletin: Information disclosure in WebSphere Application Server (CVE-2017-1681) - United States SECURITY BULLETIN\n\nSUMMARY\n There is a potential information disclosure vulnerability in WebSphere Application Server. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1681 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1681]\nDESCRIPTION: IBM WebSphere Application Server (IBM Liberty for Java for Bluemix 3.15) could allow a local attacker to obtain sensitive information, caused by improper handling of application requests, which could allow unauthorized access to read a file. IBM X-Force ID: 134003.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134003 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134003] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Liberty \n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION/FIXES\nThe recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI88642 for each named product as soon as practical.", "For WebSphere Application Server Liberty with fixpack levels prior to 17.0.0.3: \n· Upgrade to minimal fix pack levels as required by interim fix and then apply Interim Fix PI88642 [http://www-01.ibm.com/support/docview.wss?uid=swg24044506] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]\n--OR-- \n· Apply Liberty Fix Pack 17.0.0.3 or later. \n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition:", "For V9.0.0.0 through 9.0.0.6: \n· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI88642 [http://www-01.ibm.com/support/docview.wss?uid=swg24044506] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24044154] \n--OR-- \n· Apply Fix Pack 9.0.0.7 or later.", "For V8.5.0.0 through 8.5.5.12: \n· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI88642 [http://www-01.ibm.com/support/docview.wss?uid=swg24044506] \n--OR-- \n· Apply Fix Pack 8.5.5.13 or later. \n\nFor V8.0.0.0 through 8.0.0.14: \n· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI88642 [http://www-01.ibm.com/support/docview.wss?uid=swg24044506] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]\n--OR-- \n· Apply Fix Pack 8.0.0.15 or later.", "For V7.0.0.0 through 7.0.0.43: \n· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI88642 [http://www-01.ibm.com/support/docview.wss?uid=swg24044506] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]\n--OR-- \n· Apply Fix Pack 7.0.0.45 or later. \n\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.", "IMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]", "CHANGE HISTORY\n 29 January 2018: original document published\n08 February 2018: updated CVSS score, changed from 5.3 to 4.0 \n\n*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. \n\nDISCLAIMER\nAccording 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\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22013132]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Hypervisor Edition Application Servers WebSphere Application Server Liberty Core" ]

[ "This vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Liberty" ]

[ 1 ]

[ "IBM Security Bulletin: Multiple Security Vulnerabilities fixed in IBM WebSphere Application Server 8.5.5.6 - United States SECURITY BULLETIN\n\nSUMMARY\n Cross reference list for security vulnerabilites fixed in IBM WebSphere Application Server 8.5.5.6, IBM WebSphere Application Server Hypervisor 8.5.5.6 and IBM WebSphere Application Server Liberty Profile 8.5.5.6.", "VULNERABILITY DETAILS\nCVEID: CVE-2015-0226 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0226]\nDESCRIPTION: Apache WSS4J could allow a remote attacker to obtain sensitive information, caused by Bleichenbacher's attack on XML Encryption. By sending a specially-crafted message, an attacker could exploit this vulnerability to decrypt the key and obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100836 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100836] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) \nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: \n\nVersion 8.5 Liberty Profile \n\nRemediation/Fixes: The recommended solution is to apply the Interim Fix, Fix Pack, or PTF for each named product as soon as practical.", "Fix: \nApply an Interim Fix [http://www-01.ibm.com/support/docview.wss?uid=swg24039403], Fix Pack or PTF [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980] containing this APAR PI36866, as noted below:\n\nFor IBM WebSphere Application Server Liberty profile: \n\nFor V8.5.5.2 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI36866 [http://www-01.ibm.com/support/docview.wss?uid=swg24040191]\n\nWorkaround(s): None known \nMitigation(s): None known \n\nCVE ID: CVE-2015-1885 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1885] (APAR PI33202 and PI36211) \n\nDESCRIPTION: WebSphere Application Server Full Profile and Liberty Profile could allow a remote attacker to gain elevated privileges on the system when OAuth grant type of password is used.", "CVSS: \nCVSS Base Score: 9.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/101255 [https://exchange.xforce.ibmcloud.com/vulnerabilities/101255] for the current score\nCVSS Environmental Score*: Undefined\nCVSS String: (AV:N/AC:M/Au:N/C:C/I:C/A:C) \n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile and Liberty Profile Version 8.0 Version 7.0 \n\nRemediation/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix, Fix Pack or PTF [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980] containing this APAR PI36211 for Full Profile and PI33202 for Liberty Profile, as noted below: \n\nFor IBM WebSphere Application Server", "For V8.5.0.0 through 8.5.5.5 Full Profile: Apply Interim Fix PI36211 [http://www-01.ibm.com/support/docview.wss?uid=swg24039602]\n-- OR Apply Fix Pack 6 (8.5.5.6), or later. After the fix pack is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)/installableApps directory.\n\n\nFor V8.5.0.0 through 8.5.5.4 Liberty Profile: Apply Interim Fix PI33202 [http://www-01.ibm.com/support/docview.wss?uid=swg24039594] [http://www-01.ibm.com/support/docview.wss?uid=swg24039594] [http://www-01.ibm.com/support/docview.wss?uid=swg24039403]\n-- OR Apply Fix Pack 5 (8.5.5.5), or later.\n\nFor V8.0.0.0 through 8.0.0.10: Apply Interim Fix PI36211 [http://www-01.ibm.com/support/docview.wss?uid=swg24039602]\n-- OR Apply Fix Pack 11 (8.0.0.11), or later. After the fix pack is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)/installableApps directory.", "For V7.0.0.0 through 7.0.0.37: Apply Interim Fix PI36211 [http://www-01.ibm.com/support/docview.wss?uid=swg24039602]\n-- OR Apply Fix Pack 39 (7.0.0.39), or later. After the fix pack is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)/installableApps directory.\n\nWorkaround(s): None known \nMitigation(s): None known \n\nCVEID: CVE-2015-0250 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0250]\nDESCRIPTION: Apache Batik could allow a remote attacker to obtain sensitive information. By persuading a victim to open a specially-crafted SVG file, an attacker could exploit this vulnerability to reveal files and obtain sensitive information.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101614 [https://exchange.xforce.ibmcloud.com/#/vulnerabilities/101614] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "AFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile Version 8 Version 7 Version 6.1\n\nRemediation/Fixes: The recommended solution is to apply the Interim Fix, Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http://www-01.ibm.com/support/docview.wss?uid=swg24039403], Fix Pack or PTF [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980] containing this APAR PI39768 or PI49437, as noted below:\n\nFor IBM WebSphere Application Server Full profile and IBM WebSphere Application Server Hypervisor Edition\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI39768 [http://www-01.ibm.com/support/docview.wss?uid=swg24040442]", "For V8.0.0.0 through 8.0.0.10: Apply Fix Pack 11 (8.0.0.11), or later. [http://www-01.ibm.com/support/docview.wss?uid=swg21693751]\n-- OR Apply Interim Fix PI39768 [http://www-01.ibm.com/support/docview.wss?uid=swg24040442] \n\nFor V7.0.0.0 through 7.0.0.37: Apply Fix Pack 39 (7.0.0.39), or later. [https://www-304.ibm.com/support/docview.wss?uid=swg21693757]\n-- OR Apply Interim Fix PI49437 [http://www-01.ibm.com/support/docview.wss?uid=swg24041163] [http://www-01.ibm.com/support/docview.wss?uid=swg24040442]\n\nFor V6.1.0.0 through 6.1.0.47: Apply Fix Pack 47 (6.1.0.47), or later and then apply Interim Fix PI49437 [http://www-01.ibm.com/support/docview.wss?uid=swg24041163]\n\n\nWorkaround(s): None known \nMitigation(s): None known", "CVEID: CVE-2015-1927 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1927]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to gain elevated privileges on the system, caused by an application not having the correct serveServletsbyClassname setting. By a developer not setting the correct property, an attacker could exploit this vulnerability to gain unauthorized access.\nCVSS Base Score: 6.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102872 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102872] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:P/A:P) \n\n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile and Liberty Profile Version 8 Version 7\n\nRemediation/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical.", "Fix: \nApply an Interim Fix [http://www-01.ibm.com/support/docview.wss?uid=swg24039403], Fix Pack or PTF [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980] containing this APAR PI31622, as noted below:\n\nPlease Note:This APAR has changed the default value of the WebContainer custom property com.ibm.ws.webcontainer.disallowServeServletsByClassname from false to true so that no security threat could occur. Prior to this change, it was up to the developer to remember to change the custom property to true before deploying into production. \n\n\nProperty Name: com.ibm.ws.webcontainer.disallowServeServletsByClassname \nDescription: If set to true, disallows the use of serveServletsByClassnameEnabled at the application server level, overriding any setting of serveServletsByClassnameEnabled at the application level. This property affects all applications. \nValues: true(default)/false", "If you need to change the value please refer to the the following technote for instructions on enabling WebContainer custom properties: \n\nFull Profile: http://www-01.ibm.com/support/docview.wss?uid=swg21284395 [http://www-01.ibm.com/support/docview.wss?uid=swg21284395]\nLiberty Profile: http://www-01.ibm.com/support/docview.wss?uid=swg21597753 [http://www-01.ibm.com/support/docview.wss?uid=swg21597753]\n\nFor IBM WebSphere Application Server Full profile, IBM WebSphere Application Server Liberty Profile and IBM WebSphere Application Server Hypervisor Edition\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI31622 [http://www-01.ibm.com/support/docview.wss?uid=swg24040348]\n\nFor V8.0.0.0 through 8.0.0.10: Apply Fix Pack 11 (8.0.0.11), or later. [http://www-01.ibm.com/support/docview.wss?uid=swg21693751]\n-- OR Apply Interim Fix PI31622 [http://www-01.ibm.com/support/docview.wss?uid=swg24040348]", "For V7.0.0.0 through 7.0.0.37: Apply Fix Pack 39 (7.0.0.39), or later. [https://www-304.ibm.com/support/docview.wss?uid=swg21693757]\n-- OR Apply Interim Fix PI31622 [http://www-01.ibm.com/support/docview.wss?uid=swg24040348]\n\nWorkaround(s): Set the custom property com.ibm.ws.webcontainer.disallowServeServletsByClassName to true\nMitigation(s): None known \n\nCVEID: CVE-2015-1936 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1936]\nDESCRIPTION: IBM WebSphere Application Server Administrative console could allow a remote authenticated attacker to hijack a user's session when Security is not enabled. An attacker could exploit this vulnerability using the JSESSIONID parameter to gain access to another user's session.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103108 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103108] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:S/C:P/I:N/A:N)", "AFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile Version 8 \n\nRemediation/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http://www-01.ibm.com/support/docview.wss?uid=swg24039403], Fix Pack or PTF [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980] containing this APAR PI37230, as noted below:\n\n\nFor IBM WebSphere Application Server and IBM WebSphere Application Server Hypervisor Edition:\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI37230 [http://www-01.ibm.com/support/docview.wss?uid=swg24040347]\n\nFor V8.0.0.0 through 8.0.0.11: Apply Fix Pack 12 (8.0.0.12), or later. [http://www-01.ibm.com/support/docview.wss?uid=swg21693751]\n-- OR Apply Interim Fix PI37230 [http://www-01.ibm.com/support/docview.wss?uid=swg24040347]", "Workaround(s): None known \nMitigation(s): None known \n\nCVEID: CVE-2015-1946 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1946]\nDESCRIPTION: IBM WebSphere Application Server 8.5 and IBM WebSphere Virtual Enterprise 7.0 could allow a local attacker to gain elevated privileges on the system cause by the user roles not being handled properly.\nCVSS Base Score: 4.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103201 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103201] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:M/Au:S/C:P/I:P/A:P) \n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 IBM WebSphere Application Server Version 7.0 IBM WebSphere Virtual Enterprise on WebSphere Application Server Version 7 and Version 8\n\nRemediation/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical.", "Fix: \nApply an Interim Fix [http://www-01.ibm.com/support/docview.wss?uid=swg24039403], Fix Pack or PTF [https://www-304.ibm.com/support/docview.wss?rs=180&uid=swg27004980] containing this APAR PI35180, as noted below:\n\nFor IBM WebSphere Application Server\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI35180 [http://www-01.ibm.com/support/docview.wss?uid=swg24040235]\n\nFor IBM WebSphere Virtual Enterprise using WebSphere Application Server V7.0 and V8.0: Apply WebSphere Virtual Enterprise Fix Pack 6 (7.0.0.6) or later. \n\nWorkaround(s): None known \nMitigation(s): None known", "Other APARs shipped with 8.5.5.6 are included in the security bulletins below:\nPI33012 Security Bulletin for Dojo Toolkit Vulnerability [http://www-01.ibm.com/support/docview.wss?uid=swg21697284]\nPI36563 Security Bulletin for RSA Export Keys for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21698613]\nPI36563 Security Bulletin for RC4 Stream Cipher for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21701503]\nPI38302 Security Bulletin for Management Port for WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21883573]\nPI36417 Security Bulletin for RSA Export Keys for IBM HTTP Server [http://www-01.ibm.com/support/docview.wss?uid=swg21698959] \nPI34229 Security Bulletin for RC4 Stream Cipher for IBM HTTP Server [http://www-01.ibm.com/support/docview.wss?uid=swg21701072]", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 26 June 2015: original document published\n29 June 2015: fix serveservlets custom property name and add workaround\n30 June 2015: fix serveservlets custom property\n16 July 2015: added additional links to ifixes\n13 August 2015: added additonal link to ifixes\n2 September 2015: updated fix pack dates and level\n13 November 2015: updated interim fix PI39768 with PI49437 \n\n*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\nAccording 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. \n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Hypervisor Edition Application Servers WebSphere Virtual Enterprise" ]

[ "Cross reference list for security vulnerabilites fixed in IBM WebSphere Application Server 8.5.5.6, IBM WebSphere Application Server Hypervisor 8.5.5.6 and IBM WebSphere Application Server Liberty Profile 8.5.5.6." ]

[ 0 ]

[ "IBM DOORS module fails to open in exclusive edit mode results in error \"unable to open module ...no such file or directory\" - United States missing session file; file not found; can not open module; open module exclusive edit fails; PM50525 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to open a module exclusive edit in IBM Rational DOORS result in the error \"DOORS report\nUnable to open module '/A Project/Requirements' No such file or directory\". \n\nSYMPTOM\nA module with a large number of sections is used mostly in shareable edit mode. \n\nYou can open the module Read-only , or Shareable-Edit; but not in exclusive edit. \n\nSteps to reproduce: \n\n 1. Login to DOORS\n \n \n 2. Click the Project, or folder, icon that contains the module\n \n \n 3. Click the module icon in the DOORS Explorer window\n \n \n 4. Click File > Open> Exclusive Edit (Ctrl + E)\n \n\n\nExpected result: The module should open in Exclusive edit mode.", "Actual result: The module will not open in exclusive edit module; however it will open in read only mode, or shareable edit mode. If you attempt to check the database integrity for issue the module is not flagged for any problems. \n\nThe full error message is as follows:\n\nDOORS report\nUnable to open module '/A Project/Requirements' No such file or directory\"\nC:\\Program Files (x86)\\IBM\\Rational\\DOORS\\9.5\\data\\v6data\\20\\m00000021.mod\\current.ver\\s1000005.dtc\n\n\nimage \n\n[/support/docview.wss?uid=swg21511831&aid=1] [/support/docview.wss?uid=swg21511831&aid=1]\n\nCAUSE\n This issue has been identified as a product defect under APAR PM50525 [http://ibm.com/support/docview.wss?uid=swg1PM31236].\n\n\n\nRESOLVING THE PROBLEM\nThis error indicates that a user session file is corrupted on the database server. \n\nThis defect is resolved in IBM Rational DOORS Version 9.4.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27036720#9401] \n\n \n\nWORKAROUND:", "the following options can be used to correct this problem: \n\n * Retrieve the missing file from system backup and insert it into the module current.ver directory\n \n The advantage of inserting the missing session file is you do not need to restart the database server.\n\nWarning these two option should only be performed by Rational Support. Modifications to the files in your DOORS database could result is data corruption and jeapordize your DOORS database. Send the session.ixc file to support for repair\n\nFrom the module directory listed in the error message provide support the file session.ixc\nChoosing to have support repair the session index file requires you to have all users log out \nand shut down the DOORS database server until the repaired file is returned and inserted \nto replace the existing data file for the module.", "Create a replacement session file \nFrom the module directory listed in the error message provide support the file session.ixc\nAdjacent session files will be required in order to to create the replacement. \nYour support engineer will identify these files from the session index file.\nNo work can be performed in the effected module until the replacement session file is restored\nfor the effected module. \n\n\nNote: Generally the repair is only required for one user session file. However in circumstances where DOORS reports a missing session file for a module- the event that caused this may have effected session files for other users connected to the module. For this situation you may need to perform a successive repair to the index file." ]

[ "This defect is resolved in IBM Rational DOORS Version 9.4.0.1" ]

[ 1 ]

[ "IBM Late breaking updates to DataPower 7.5 documentation - United States NEWS\n\nABSTRACT\n \n\nThe version 7.5 documentation for IBM DataPower Gateway is not the latest available information. This document covers late breaking updates that are not in IBM Knowledge Center.\n\nLast updated, October 2017.\n\n\n\nCONTENT\nThe late breaking updates in this document apply to DataPower Gateway version 7.5 documentation. \n\n\n\n\n\n\n\nTo access specific updates, click the appropriate link: * Upgrade\n * \n * Installation\n * \n * GatewayScript\n * \n * File management\n * \n * Monitors\n\nTo view the change history of this document, see Change history\n\n\nThe corrections in the following sections apply to DataPower Gateway version 7.5 in IBM Knowledge Center.", "Upgrade * \n * Disabled diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 algorithms by default. Disabled MD5-based MAC algorithms. Limited DH-GEX to 4096 bits for Cisco devices. \n * \n * \n * enable-legacy-kex yes\n * \n * The enable-legacy-kex command for the SSH server profile in available in 7.5.2.0. The enable-legacy-kex command for the SSH client profile is available in 7.5.2.7. \n * \n * \n * Default cipher suites * [email protected] (CHACHA20-POLY1305_AT_OPENSSH.COM)\n * \n * aes128-ctr (AES128-CTR)\n * \n * aes192-ctr (AES192-CTR)\n * \n * aes256-ctr (AES256-CTR)\n * \n * [email protected] (AES128-GCM_AT_OPENSSH.COM)\n * \n * [email protected] (AES256-GCM_AT_OPENSSH.COM)\n * \n * arcfour256 (ARCFOUR256)\n * \n * arcfour128 (ARCFOUR128)\n * \n * aes128-cbc (AES128-CBC)\n * \n * 3des-cbc (3DES-CBC)\n * \n * blowfish-cbc (BLOWFISH-CBC)\n * \n * cast128-cbc (CAST128-CBC)\n *", "* aes192-cbc (AES192-CBC)\n * \n * aes256-cbc (AES256-CBC)\n * \n * arcfour (ARCFOUR)\n * \n * [email protected] (RIJNDAEL-CBC_AT_LYSATOR.LIU.SE)\n \n Default KEX algorithms * [email protected]\n * \n * ecdh-sha2-nistp256\n * \n * ecdh-sha2-nistp384\n * \n * ecdh-sha2-nistp521\n * \n * diffie-hellman-group-exchange-sha256\n * \n * diffie-hellman-group14-sha1\n \n Default MAC algorithms * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * hmac-sha2-256\n * \n * hmac-sha2-512\n * \n * hmac-sha1\n \n \n * \n *", "* The SSH client always initiates the banner exchange. During the SSH2 banner exchange, use CR+LF termination for the banner. The SSH client ignores any message from the SSH server until the banner exchange.", "Back to top\n\n\n\n\n\n\n\n\n\n\nInstallation * \n * show other-sensors\n * \n * show sensors-other\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nGatewayScript * \n * clear gatewayscript-cache path\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nFile management * \n * isamwebroot local policyframework \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nMonitors * \n * type\n * \n * block\n * \n * shape\n * \n * type command\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\nChange history \nLast modified: 30 October 2017. * 30 October 2017: Added information about nonexisting block keyword for Message Filter Action type command. \n * 19 October 2017: Added information about which directories you can create and remove subdirectories. \n * 19 July 2016: Added data about the wrong command troubleshooting command in the installation documentation. \n * 17 June 2016: Added data about the undocumented Global command. \n * 22 March 2016: Created for 7.5.\n\nBack to top" ]

[ "Default KEX algorithms * [email protected]\n * \n * ecdh-sha2-nistp256\n * \n * ecdh-sha2-nistp384\n * \n * ecdh-sha2-nistp521\n * \n * diffie-hellman-group-exchange-sha256\n * \n * diffie-hellman-group14-sha1\n \n Default MAC algorithms * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * [email protected]\n * \n * hmac-sha2-256\n * \n * hmac-sha2-512\n * \n * hmac-sha1" ]

[ 2 ]

[ "IBM Data Server Manager (DSM) showing SQLCODE=-206 \"<name> is not valid in the context where it is used.\" - United States SQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Data Server Manager log files are full of SQLCODE=-206 \"<name> is not valid in the context where it\nis used.\" error \n\nSYMPTOM\nThe symptoms can vary depending on each installation. \n\nMost common scenario, DSM shows Data Pending status for the monitored database.\n\n\nCAUSE\nWhen you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release. \n\nBut that command does not necessarily update the database system catalog to support the new fix pack that you have installed.\nMeaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level.", "DIAGNOSING THE PROBLEM\nOne way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database: \n\ndb2 \"select versionnumber from sysibm.sysversions order by 1 desc\" \n\nIf the results is showing a lower level than the ones DSM supports, that means your environment\nis not supported, and you are getting the SQLCODE=-206 error.\n\nTo verify what are the DB2 levels supported by DSM, please refer to the links below:\n- System requirements for IBM Data Server Manager, version 1.1.2 [http://www-01.ibm.com/support/docview.wss?uid=swg27045176]\n- System requirements for IBM Data Server Manager, version 2.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048115]\n\n\n\nRESOLVING THE PROBLEM\nRun the db2updvnn command according to the db2level of your monitored database:", "- For DB2 V9.7 run db2updv97 [https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command" ]

[ "Run the db2updvnn command according to the db2level of your monitored database: \n\n- For DB2 V9.7 run db2updv97 [https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0054449.html] command" ]

[]

[ "IBM Security Bulletin: Persistent cross-site scripting vulnerability in Process Admin Console affecting IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) CVE-2015-0156 - United States SECURITY BULLETIN\n\nSUMMARY\n IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2015-0156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0156]", "DESCRIPTION:IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.\nCVSS Base Score: 3.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/100792 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100792]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:S/C:N/I:P/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\n * IBM Business Process Manager Standard V7.5.x, 8.0.x, 8.5.x \n * IBM Business Process Manager Express V7.5.x, 8.0.x, 8.5.x \n * IBM Business Process Manager Advanced V7.5.x, 8.0.x, 8.5.x \n * WebSphere Lombardi Edition 7.2.x", "If you are using an earlier unsupported version, IBM strongly recommends to upgrade. REMEDIATION/FIXES\nInstall the interim fix for APAR JR52420 as appropriate for your current IBM Business Process Manager or IT06812 for your current WebSphere Lombardi Edition environment.", "* IBM Business Process Manager Express [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR52420] \n * IBM Business Process Manager Standard [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR52420] \n * IBM Business Process Manager Advanced [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR52420] \n * WebSphere Lombardi Edition [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=IT06812]\n\nWORKAROUNDS AND MITIGATIONS\nNone", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]", "RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 2015-05-13 - initial version published \n\n*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\nAccording 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.", "Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.6, 8.5.5, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Express Security Linux, Linux zSeries, Windows 8.5.6, 8.5.5, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition AIX, HP-UX, Linux, Linux zSeries, Linux/x86, Platform Independent, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2" ]

[ "CVEID:CVE-2015-0156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0156]\n\nDESCRIPTION:IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.\nCVSS Base Score: 3.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/100792 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100792]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:S/C:N/I:P/A:N)" ]

[]

[ "IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code", "Setting the HTTP Session time-out from the Administrative Console \n1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management. \n\nIn the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box. \n\n\n2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level.", "3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level. \n\nAfter modifying these settings, save the master configuration. \n\nSetting HTTP Session time-out when application is packaged \n\nThe application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application.", "This setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \n          <session-config> \n *          <session-timeout>60</session-timeout>\n * \n *       </session-config>\n\n \n\nWhere the \"session-timeout\" is an integer value for the desired session time-out in minutes. \nSetting HTTP Session time-out from the application code \n\nFinally, the HTTP Session time-out can be set in the application code. The programmer can invoke the setMaxInactiveInterval() method on HttpSession object to set the time-out value as desired. This setting overrides any time-out defined in the application package or made from the Administrative Console. \n\nHTTP Session time-out Override Precedence Summary \n\nThe list below shows the precedence from which the final HTTP Session time-out is derived.", "1. Server Level [/support/docview.wss?uid=swg21163875&amp;aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&amp;aid=1] Overrides all other settings RELATED INFORMATION\n A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21659740]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK" ]

[ "The HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code" ]

[ 0 ]

[ "IBM \"An invalid XML character\" error is thrown when handling data originating from a WebSphere Adapter - United States Unicode invalid character 0x0 xml serialize serialization XSLT XLS error TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WeBSphere Adapter is unable to process data from a source containing unicode data due to a serialization error in the broker indicating that \"An invalid XML character (Unicode: 0x0) was found in the element content\". \n\nSYMPTOM\nWhen processing data using a broker that originates from a WebSphere JCA Adapter, you encounter an exception of the following form: \n\nSource = java.lang.RuntimeException caught trying to serialize BO BusinessObject: F4211BeginDoc@382a382a (F4211FSBeginDoc=F4211FSBeginDoc@67e667e6) probeid = 214 Stack Dump = java.lang.RuntimeException: An invalid XML character (Unicode: 0x0) was found in the element content:", "This error occurs while you are performing data transformations within your broker, either for an XSLT or to enable monitoring or tracing of the data stream, and results in a flow failure.\n\n\nCAUSE\nThe problem occurs when the source data contains unicode data which is not allowed in XML. In the above example, this is the unicode character 0x0, but there are a number of other unicode characters that can cause the same result. The problem does not occur in the WebSphere Adapter itself because the WebSphere Adapters are entirely capable of handling full unicode data. Rather, the problem happens in some brokers which fail to properly serialize the incoming data into a valid XML object.", "RESOLVING THE PROBLEM\nThe only complete solution at this time is to not process unicode characters that are not valid in XML. This can be done by not importing data fields that might contain such characters or by purging such characters from the incoming data source. It is not sufficient to do filtering in the BO maps since the broker can still run into problems prior to this Java™ mapping. \n\n\nIf handling of fields containing these unicode characters is essential to your use case, it will be necessary to open a PMR with your broker's support team (rather than the WebSphere Adapter team) to determine if there are any alternatives available.\n\n \n\nHISTORICAL NUMBER\n 75349\n344\n000" ]

[ "The only complete solution at this time is to not process unicode characters that are not valid in XML. This can be done by not importing data fields that might contain such characters or by purging such characters from the incoming data source." ]

[ 2 ]

[ "IBM ERROR: Default DB path is not set, when adding database set on RHEL 5 - United States 1320206; ClearQuest; Command Line Tools; CQ; cqreg; add_dbset; initialize; CQ_DATABASES; CQDB_rgys; registry; db set; db_set; Default DB path is not set; Use cqreg initialize first; linux; RHEL; RHEL5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains why the error, \"Default DB path is not set\", occurs when adding a connection with IBM® Rational® ClearQuest® on RedHat Enterprise Linux® (RHEL) 5. \n\nSYMPTOM\nWhen running the command cqreg add_dbset, this error occurs:\n\n\"Default DB path is not set\"\n\"Default version is 7.0.0\"\n/opt/rational/clearquest/CQDB_rgys/cqdb_registry/7.0.0 does not exist. Use cqreg initialize first. \n\nCAUSE\nNormally, at the end of a ClearQuest installation on UNIX® based platforms, the cqreg initialize command runs automatically. The command creates the registry structure for database sets. During the installation, the command did not run successfully.", "DIAGNOSING THE PROBLEM\nVerify that the CQDB_rgys directory exists, as defined in the installation options. The following is the default registry location: \n\n\n/opt/rational/clearquest/CQDB_rgys/cqdb_registry/\n\nIf not present, then the cqreg initialize command was not successful.\n\n\nRESOLVING THE PROBLEM\nRun cqreg initialize. The add_dbset command will run successfully afterwards. However, should the same error persist, make sure the command is run as the root user. \n\n\n\nAlso make sure that the CQ_DATABASES environment variable is set to the desired registry path. If it is not, set the variable accordingly, then run the previously mentioned commands again." ]

[ "Run cqreg initialize. The add_dbset command will run successfully afterwards. However, should the same error persist, make sure the command is run as the root user. \n\n\n\nAlso make sure that the CQ_DATABASES environment variable is set to the desired registry path. If it is not, set the variable accordingly, then run the previously mentioned commands again." ]

[ 1 ]

[ "IBM PureData Systems for Analytics - nzsql error, Records trailing spring space set to 512 is too small - United States netezza PDA TECHNOTE (FAQ)\n\nQUESTION\n What does the message \"ERROR: Records trailing spring space set to 512 is too small...\" mean? \n\nANSWER\nThe following error may appear in the pg.log file: \n\nERROR: Records trailing spring space set to 512 is too small : Bump it up using the environment variable NZ_SPRINGFIELD_SIZE \n\nThis error can occur when a query includes multiple aggregates against varchar or nvarchar columns. As the query is being processed the system allocates memory for each row of the result set. This includes each of the GROUP BY columns and each of the aggregates. For queries doing aggregates on variable length columns, the total length of the record will vary during the process. For example, if the current min value is \"Boston\" and the new min value is \"Albuquerque\" space for the new min value needs to increase.", "The NZ_SPRINGFIELD_SIZE is an extra pseudo-column that is tacked onto each row. It does not contain any data. It is a filler that starts out at NZ_SPRINGFIELD_SIZE and then dynamically shrinks and expands as needed to keep each of the aggregate rows at a fixed length. There is a single springfield in each grouping record that has to shrink and grow to offset the combined changes in width of the running values for all min/max aggregates. \n\nTo avoid this error message, increase the value for this parameter as follows: \n\n1. nzstop\n2. export NZ_SPRINGFIELD_SIZE=1024\n3. nzstart \n\nYou can confirm that the environment variable took effect by running the command \"nzsystem showregistry\". The output should contain the following: \"system.maxSpringFieldSize = 1024\".", "Unfortunately, the setting for NZ_SPRINGFIELD_SIZE will revert to its default value the next time the database is stopped and started without the NZ_SPRINGFIELD_SIZE environment variable being set. To ensure that the setting persists after every database restart, do the following:\n1. Add the following line to the /nz/data/config/system.cfg file. (Create the file if it does not exist.) \n\nsystem.maxSpringFieldSize = 1024\n2. nzstop\n3. nzstart \n\nIf 1024 does not work, try higher values. Setting the limit may take a little trial and error. Increasing this value should not have a noticeable impact on other system performance.", "Note: \"By default 512 bytes is allocated to each row taking part in aggregations. By increasing this value by 512 we allocate over 30MB more memory for every 1 000 000 rows participating in aggregations. This is for one query, there might be other queries in the system which do aggregations as well. The more memory that is allocated for NZ_SPRINGFIELD_SIZE (for each row) the less memory left for other processes. Having said this, it is not uncommon to see NZ_SPRINGFIELD_SIZE set to 8192 without consequence but care must be taken and one must still be aware of how increasing NZ_SPRINGFIELD_SIZE will impact resources, thus increase it wisely. \" \n\n \n\nHISTORICAL NUMBER\n NZ755310" ]

[ "This error can occur when a query includes multiple aggregates against varchar or nvarchar columns. As the query is being processed the system allocates memory for each row of the result set. This includes each of the GROUP BY columns and each of the aggregates. For queries doing aggregates on variable length columns, the total length of the record will vary during the process." ]

[ 0 ]

[ "IBM Syndicating to VP with exclusive realms does not work. - United States syndication; realm; vp; admin user; getPortalAdministrator TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\n \n\nSyndication from base Portal to Virtual Portal with different realms does not work:-\n\n1) Create 2 different realms with different base entries and map one realm ( with base entry e.g DC=org1,DC=test) to base Portal.\n\n2) Create a Virtual portal and map it to another realm ( with base entry e.g DC=org2,DC=test).\n\n3) Attempt to carry out syndication from Base Portal to Virtual Portal.\n\n4) The syndication fails with below exception:", "[datetime] 0000007f PackageGenera I createIceProjectItemRemoves():: p_items length = 0 \n[datetime] 0000008b ResponseBL I Performing response for sender: 1abc2a07-e70a-4804-8e09-b7b897eef534", "[datetime] 000000a1 SubscriberTas E Unexpected exception thrown while updating subscription: [IceId: <1abc2a07-e70a-4804-8e09-b7b897eef534> Current State: <ICE-INITIAL>], exception: com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST\n[...]", "at com.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator(UserManagementServiceImpl.java:1678)\n[...]", "CAUSE\n\nThe Admin user exists on Base Portal but not the Realm which is configured to Virtual Portal.\n\nThe Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() does not have access to the Virtual Portal.\n\n\nRESOLVING THE PROBLEM\n \n\nThe Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.\n\nWhen syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal.\n\nRELATED INFORMATION\n Realm Support [http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=IBM%20WebSphere%20Portal%208%20Product%20Documentation&documentId=3B264D090122D90D85257B26000692C6&action=openDocument&rev=true&mode=original&content=pdcontent]" ]

[ "The Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.\n\nWhen syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal." ]

[ 4 ]

[ "IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects IBM MQ Appliance (CVE-2015-7575) - United States SECURITY BULLETIN\n\nSUMMARY\n The MD5 “SLOTH” vulnerability on TLS 1.2 affects IBM MQ Appliance \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]\nDESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.\nCVSS Base Score: 7.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nIBM MQ Appliance M2000\n\nREMEDIATION/FIXES\nApply the ifix for APAR IT13296 [http://www.ibm.com/support/fixcentral/swg/selectFix?product=ibm/WebSphere/IBM%20MQ%20Appliance%20M2000&fixids=8.0.0.4-IBM-MQ-Appliance-M2000-IT13223&function=fixId&parent=ibm/WebSphere].\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT\nReported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France \n\nCHANGE HISTORY\n 26 January 2016 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. \n\nDISCLAIMER\nAccording 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.\n\n \n\nPRODUCT ALIAS/SYNONYM\n IBMMQ" ]

[ "CVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]\nDESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.\nCVSS Base Score: 7.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)" ]

[ 0 ]

[ "IBM Tivoli Monitoring: HMC Base Agent 6.2.2.3-TIV-ITM_HMC_BASE-IF0004 - United States DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs listed in the APAR Number(s) section below, and adds enhancement feature 215857 to add hardware events. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2015. \nAll rights reserved.\n\n\nComponent: IBM(R) Tivoli(R) Monitoring: HMC Base Agent,\nVersion 6.2.2.3\n\nComponent ID: 5724C04HB\n\nInterim Fix 0004, 6.2.2.3-TIV-ITM_HMC_BASE-IF0004\n\nDate: October 20, 2015 \n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices\n\n\n1.0 General description\n===============\nThis fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below.", "2.0 Problems fixed\n============\nThe following problems are addressed by this fix.\n\n2.1 APARs\n---------------\n\nAPAR: IV67769\nAbstract: APPLICATION SUPPORT MISMATCH WARNING MESSAGE\nAdditional information: After installing interim fix\n6.2.2.3-TIV-ITM_HMC_BASE-IF0003, the Tivoli Enterprise\nPortal might display a warning indicator that states\nApplication Support Mismatch and shows HMC Base Servers\nwith Client Version 06220302 and Server Version 06220303. \n\n2.3 Enhancements\n------------------\nFeature: 215857\nAbstract: New Hardware Events Attribute Group\nAdditional information: Add a new attribute group to collect \nhardware events from the Hardware Management\nConsole (HMC).\n\nAttribute group name: Hardware Events\nTable name : KPHHDWEVNTS\nWarehouse table name: KPH_HARDWARE_EVENTS or KPHHDWEVNTS\n\nAttribute descriptions:", "Problem_No - The problem number of the event.\nReference_Code - The reference code for the event.\nFirst_Report_Time - The first time when the event was reported.\nPMH_No - The IBM hardware support PMR number that\nwas created if the call home was successful.\nFirmware_Fix - The Firmware Fix for the event.\nService_Event_Text - The description of the service event.\nApproval_State - The event approval state, either approved or\nunapproved.\nDuplicated_Count - The number of times the event has occurred.\nSeverity - The event severity.\nSystem_MTMS - The machine type/model of the server\nreporting the event.\nEnclosure_MTMS - The machine type/model of the enclosure\nsystem reporting the event.\nCreated_Time - The time the event was created.\nEvent_Time - The time the event was reported.\nCall_Home_Intended - Defines if call home was intended for this\nevent, either true or false.\nAnalyzing_MTMS - The machine type/model of the analyzing system.\nReference_Code_Extent - The extent of reference code.", "System_Ref_code - The system reference code.", "2.4 Superseded fixes\n---------------------\n6.2.2.3-TIV-ITM_HMC_BASE-IF0003\n6.2.2.3-TIV-ITM_HMC_BASE-IF0002\n6.2.2.3-TIV-ITM_HMC_BASE-IF0001\n\n2.5 APARs and defects included from superseded fixes\n---------------------------------------------------------------\n\n6.2.2.3-TIV-ITM_HMC_BASE-IF0003\n---------------------------------\nAPAR: IV60709\nAbstract: NO CPU DATA WHEN HMC TIME ZONE IS SET TO BST\nAdditional information: If the Hardware Management Console (HMC)\ntime zone is set to BST, data might not be collected.\nThe data provider might use the incorrect time zone\nbecause BST can represent more than one time zone, for\nexample, British Summer Time and Bangladesh Standard\nTime. When the data provider sends the commands to the\nHMC to collect the CPU data, the start and stop times of\nthe commands might not be correct and might not receive\nany data. Also, data might be collected, but for the\nwrong time frame.", "6.2.2.3-TIV-ITM_HMC_BASE-IF0002\n---------------------------------\nFeature: 208626\nAbstract: LPAR Memory Attributes\nAdditional information: The following new attributes are added in\nthe Server LPARs attribute group:\n\nCurrent_Memory - The current amount of memory, in megabytes,\nconfigured for the LPAR.\nWarehouse name: CM0\nRunning_Memory - The amount of memory, in megabytes, varied on-line\nby the LPAR.\nWarehouse name: RM\n\nIn order to display these new attributes in the Tivoli Enterprise\nPortal, use the Query Editor and select Server LPARs_V9 under\nKPH SERVER LPARS.\n\n6.2.2.3-TIV-ITM_HMC_BASE-IF0001\n---------------------------------", "APAR: IV47101\nAbstract: NO CPU DATA DUE TO TIME OUTS ON HMC SSH CALLS\nAdditional information: In large environments, where there are more\nthan 150 LPARs on a server, the CPU Units used and CPU\nUsed Pct might display \"Not Collected.\" The\nkph_data_provider_<instance>_0.log displays the\nfollowing message: \n--\nSEVERE: SSHCommandExecutor.call: Timed out while waiting\nfor `lslparutil -m \"<server>\" -r \"lpar\" -s s -F\n'lpar_id|time|time_cycles |\nentitled_cycles|capped_cycles|uncapped_cycles| idle_cycles'\n--", "APAR: IV50134\nAbstract: NO CPU DATA WHEN HMC TIME SET TO GMT FORMAT\nAdditional information: If the HMC time zone is set to a GMT format,\nfor example, GMT-08:00, CPU data might not be collected\nbecause the data provider does not recognize the GMT\nformat and will default to using the local time zone. \nWhen the data provider sends the commands to the HMC to\ncollect the CPU data, the start and stop times of the\ncommands might not be correct and might not receive any\ndata. It is also possible that data will be collected,\nbut for the wrong time frame.\n\nAPAR: IV50135\nAbstract: NO DATA IN MEMORY AND PAGING SPACE VIEW\nAdditional information: The System workspace might not display any\ndata in the Memory and Paging Space views. This can\nhappen when the HMC commands:\n---\nmonhmc -r swap -n 0\nmonhmc -r mem -n 0\n---\nreturn data in M bytes instead of k bytes:\n---\nSwap: 1992M total, 0M used, 1992M free, 2853M cached \nMem: 24336M total, 4534M used, 19801M free, 480M buffers\n---", "APAR: IV50686\nAbstract: NO CPU DATA IN NON-ENGLISH LOCALE\nAdditional information: When the agent runs in a non-English locale,\nattributes \"CPU Units Used\" and \"CPU Used Pct\" might\ndisplay as \"Not Collected\" due to a Java problem. The\nkph_data_provider_0.log will have a message similar to\nthis: \n---\nWARNING: \nManagementConsoleInventoryItemBuilder$BasicDataCommand.\nprocessResult: An error occurred while parsing the N2 date\nfield \"Fri Sep 27 11:35:31 JST 2013\". Continuing. \n---\n\n2.2 Defects\n---------------\nDefect: 207939\nAbstract: Java CPCI - deadlock due to bad lock usage in some versions\nof Java runtime\nAdditional information: Classloading and resource loading might get\nlocks in the wrong order, due to Java APAR IZ96933, \ncausing the data provider to stop collecting data. This\nfix prevents the problem no matter what version of Java is\nrunning.", "Defect: 208541\nAbstract: Add log messages to show data sent to kphagent\nAdditional information: At log level of FINEST, show the contents of\nthe rows of data sent from the data provider to the \nkphagent process.\n\n\n3.0 Architecture and prerequisites\n======================\nThis fix is supported on all operating systems listed in the\nIBM Tivoli Monitoring: HMC Base Agent User's Guide, version 6.2.2.3.\n\nPlease refer to the IBM Software Product Compatability Reports (SPCR)\nfor the latest operating system certification information:\nhttp://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]\n\n3.1 Prerequisites for this fix\n--------------------------------\nThe prerequisite level for this fix is as follows:\n\nIBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim\nFeature 3, which is available from PassPort Advantage under the\nfollowing eAssembly:", "IBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, English\n(CIH93EN) (Both agent and support files are included in this one\npackage)\nIBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, Language\nSupport, Multiplatform, Multilingual (CIH94ML)\n\nFor details, see the Troubleshooting Wiki:\n\nhttps://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/System%20P%20Agents [https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/System%20P%20Agents]\n\nAs this fix is cumulative, it can be installed on any fix level for\nthis version, release, and mod level above the prerequisite.\n\n\n4.0 Image directory contents\n===================\nThis fix image contains the following files:\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.README - This README file\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar - Fix archive .tar format\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.zip - Fix archive .zip format.", "Note: The .tar and .zip files are identical in content. Use the .tar\nfile if you are working in a UNIX(R) environment; use the .zip file if \nyou are working in a Windows(R) environment. \n\nThe fix archive file contains the following files:\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kphaix526.dsc\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kph_aix526_tema_if0004.tar\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/ph_dd.properties\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004/ph_dd_062203004.xml\n- 6.2.2.2-TIV-ITM_HMC_BASE-IF0004/kpk_tems_teps_tepd_if0004.tar\n- 6.2.2.2-TIV-ITM_HMC_BASE-IF0004/kpk_tems_teps_tepd_if0004.zip\n\n\n5.0 Installation instructions \n==================\nThis fix can only be installed over an existing installation. Use\nthe following steps to install this fix.\n\n5.1 Before installing the fix \n------------------------------\n- The prerequisites listed under section 3.1 entitled 'Prerequisites\nfor this fix' must be installed before this fix can be installed.", "- For the purpose of this README, the symbol <CANDLEHOME> is the \nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\IBM\\ITM'\non Windows systems.\n\nBefore installing this fix on UNIX systems, set the environment \nvariable CANDLEHOME to the IBM Tivoli Monitoring installation \ndirectory.\n\nFor example: \n> CANDLEHOME=/opt/IBM/ITM \n> export CANDLEHOME\n\n- Because there is no uninstall utility for this fix, make sure to\nperform a backup of your environment before installing this fix.\n\n5.2 Local agent update\n--------------------------\n1. Transfer the appropriate archive file\n(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary\ndirectory on the system that contains the agent code to be\nupdated. For the purpose of this README, the symbol <TEMP>\nrepresents the fully qualified path to this directory. Note: On\nWindows systems, this path includes the drive letter.", "2. Expand the archive file using the \"tar\" command on UNIX systems or \nan extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the supported\nplatforms.\n\n3. Use the \"itmpatch\" command to install the fix for the operating\nsystem for that agent. For more information on the \"itmpatch\"\ncommand, see section 6.2. \n\nOn UNIX systems, if the fix was expanded to \n<TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004, the install command is:\n\n> itmpatch -h <CANDLEHOME> \n-i <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004/kph_aix526_tema_if0004.tar\n\n5.3 Remote agent update\n----------------------------\n1. Transfer the appropriate archive file\n(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary\ndirectory on the IBM Tivoli Enterprise Monitoring Server system.\nFor the purpose of this README, the symbol <TEMP> represents the\nfully qualified path to this directory. Note: On Windows systems,\nthis path includes the drive letter.", "2. Expand the archive file using the \"tar\" command on UNIX systems or \nan extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the supported\nplatforms.\n\n3. To add the agent fix bundles into the remote deploy depot, use the\n\"tacmd addBundles\" command found in $CANDLEHOME/bin on UNIX systems\nor in %CANDLE_HOME%\\bin on Windows systems. For more information\non the \"tacmd addBundles\" command, see the IBM Tivoli Monitoring\nAdministrator's Guide.\n\nOn UNIX systems, \nif the fix was expanded to <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004:\n> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.2.2.3-TIV-ITM_HMC_BASE-IF0004\n\nOn Windows systems, \nif the fix was expanded to <TEMP>\\6.2.2.3-TIV-ITM_HMC_BASE-IF0004:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i <TEMP>\\6.2.2.3-TIV-ITM_HMC_BASE-IF0004", "where:\n-n indicates that prerequisite bundles are not automatically\nadded. The -n parameter must be used because the fix \ndirectory does not contain any prerequisites that the fix\nmight require. Please see Section 3.1 for the prerequisites\nfor this fix.\n-i is the directory that contains the deployment bundles to be\nadded to the depot. \n\n4. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following \"tacmd\" commands. For more information on the\n\"tacmd login\" and \"tacmd updateAgent\" commands, see the IBM Tivoli\nMonitoring Administrator's Guide.\n\nOn UNIX systems: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.", "> $CANDLEHOME/bin/tacmd updateAgent -t ph\n-n <Managed system name>\n-v 062203004\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t PH \n-n <Managed system name> \n-v 062203004\n\nNote:\n- The component (-t) for the \"tacmd updateAgent\" command is\nspecified as two characters (PH), not three characters (KPH).\n- The node (-n) for the \"tacmd updateAgent\" command is the managed\nsystem name of the operating system (OS) agent to be updated.\nThe target node for the \"tacmd updateAgent\" command is always\nan OS agent.\n\n5.4 Agent support update\n------------------------------", "This fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the agent\nsupport files which need to be installed. Use the following steps to\nupdate the Tivoli Enterprise Monitoring Server, Tivoli Enterprise\nPortal Server, or Tivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file\n(6.2.2.2-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to the Tivoli\nEnterprise Monitoring Servers, Tivoli Enterprise Portal Servers,\nor Tivoli Enterprise Portal Desktops.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the supported\nplatforms.", "3. Expand the archive file (kph_tems_teps_tepd_if0004.tar or .zip)\nthat contains the updates for Tivoli Enterprise Monitoring Server,\nTivoli Enterprise Portal Server, and Tivoli Enterprise Portal\nDesktop using the \"tar\" command on UNIX systems or an extract\nutility on Windows systems. This step creates a directory\nstructure that includes a subdirectory called CD-ROM, with the\nnecessary updates.\n\n4. Use the Application Support Installer(ASI) GUI or the silent\ninstallation method to install the application support files.\n\nNote: For IBM Tivoli Monitoring Version 6.3 or above, one\nof the following additional steps must be performed.\n\n1. Acquire a platform-specific pre-packaged JRE version\nof the Application Support Installer (ASI). See IBM\nTivoli Monitoring Application Support Installer,\n6.2-tiv-itm_asi-if0003 at\n\nhttp://www.ibm.com/support/docview.wss?uid=swg24034924 [http://www.ibm.com/support/docview.wss?uid=swg24034924]\n\nfor download and installation instructions.\n\n-- OR --", "2. Specify the '-j javahome' parameter with the path to\na Java(r) 1.5 or java 1.6 installation when running\nthe itmasi.sh or itmasi.bat script described below.\n\nGUI installation option\n------------------------\nThe GUI can be started by using one of the following commands\nfrom within the CD-ROM directory where setup.jar is located.\n\nOn UNIX systems:\n> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]\n\nOn Windows systems:\n> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]\n\nWhen prompted by the Application Support Installer for the\ninstallable media directory, select the CD-ROM directory, not the\ncomponent directory. The installer can install updates for\nmultiple components at the same time.\n\nSilent installation option\n--------------------------\nTo use the silent installation option, use one of the following\ncommands from within the CD-ROM directory where setup.jar is\nlocated.", "Note: Using the silent installation option for Linux and zLinux\noperating systems requires the following files contained in\ninterim fix 6.2-TIV-ITM_ASI-IF0001:\n- Linux: setupLinux.bin\n- zLinux: setupLinux390.bin\nFollow the installation instructions contained in the\n\"6.2-TIV-ITM_ASI-IF0001.README\".\n\nOn UNIX systems:\n> ./itmasi.sh -h <CANDLEHOME>[-silent]\n[-r <response file>]\n[-j <JAVAHOME>]\n\nOn Windows systems:\n> itmasi -h <CANDLEHOME> [-silent]\n[-r <response file>]\n[-j <JAVAHOME>]\n\nwhere:\n-h <CANDLEHOME> - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-r <response file> - Optional. Customized response file name.\nThe default response file \"response.txt\" in\nthe CD-ROM directory can be copied and modified\nfor your environment. Do not update \"response.txt\".\n\n-j <JAVAHOME> - Optional. The fully-qualified path to the \"bin\"\ndirectory where Java(R) is installed. The\nlocation of Java on your system might vary.", "5. The next panel presented by the Application Support Installer asks\nfor the selection of which Tivoli Monitoring components you want\nto add application support to. For this fix, check or clear the\ncheck boxes as follows:\n\nchecked - Tivoli Enterprise Monitoring Server (TEMS)\nchecked - Tivoli Enterprise Portal Server (TEPS)\nchecked - Tivoli Enterprise Desktop Client (TEPD)\n\nContinue through the remaining GUI panels selecting the HMC Base\n06.22.03.04 support to complete the installation.\n\n6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal\nBrowser was running when the update was installed, it must be\nrestarted.\n\n\n6.0 Additional installation information\n========================\n\nFor additional troubleshooting installation information, see the\nitmpatch.log in the patchlogs directory in <CANDLEHOME>.", "6.1 Installation instructions for agent baroc file\n-----------------------------------------------------\nThis fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the\nagent baroc files that must be installed. Refer to IBM Tivoli\nMonitoring Installation and Setup Guide under \"Installing monitoring\nagent baroc files on the event server\" in \"Installing the IBM Tivoli\nEnterprise Console Event Synchronization\" section for more\ninformation.\n\n6.2 Additional information on using \"itmpatch\" command\n--------------------------------------------------------------\nThe \"itmpatch\" command has the following syntax:\n\nUsage: itmpatch -h <installation home> [OPTIONS]\n\nitmpatch -h <installation home>\n-t { <patch_file_directory> | <patch_file> }\n\nitmpatch -h <installation home>\n-i { <patch_file_directory> | <patch_file> }", "where:\n-h Specifies the IBM Tivoli Monitoring installation directory\n-i Specifies the path to the directory or patch file to be installed\n-t Generates a report of the actions to be taken by the patch\n\n\nFor example, on UNIX systems:\n- To preview the fix installation, use the \"-t\" option:\n> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>\n\n- To install the fix, use the \"-i\" option:\n> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>\n\nwhere:\n<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring\ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n<TEMP> represents the fully qualified directory specification where\nthe fix is located. On Windows systems, this must include the drive\nletter.\n\n6.3 Verifying the update\n----------------------------", "1. To verify the agent was updated correctly, use the \"tacmd\" command\nto view the agent's current version after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer prior to viewing the agent version.\n\nFor example:\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring\ninstallation directory, the default location is '/opt/IBM/ITM'. \n\n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n> $CANDLEHOME/bin/tacmd listSystems -t PH\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli\nMonitoring installation directory, the default location\nis 'C:\\IBM\\ITM'. \n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t PH \n\nNote: The component (-t) for the \"tacmd listSystems\" command is\nspecified as two characters (PH), not three characters (KPH).\n\nWhen the agent update is successful, the agent version is:\n06.22.03.04.", "2. To verify the agent support files were updated correctly, use the\n\"kincinfo\" command on Windows systems or the \"cinfo\" command on\nLinux or UNIX systems. The sample output below shows the versions\nof the Tivoli Enterprise Portal Server, Tivoli Enterprise\nMonitoring Server, or Tivoli Enterprise Portal Desktop systems\nafter this fix has been successfully applied.\n\nNote: The displayed date of the build might not be accurate. This\nis a known problem.\n\nOn UNIX or Linux systems:\n-------------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\n./cinfo -i\n\n*********** Thu Oct 7 13:57:24 CST 2015 ******************\nUser: root Groups: system bin sys security cron audit lp\nHost name : <hostname> Installer Lvl:06.30.02.00\nCandleHome: /opt/IBM/ITM\n***********************************************************\n...Product inventory\n.\n.\n.\nph Monitoring Agent for HMC Base\ntms Version: 06.22.03.04\ntps Version: 06.22.03.04\ntpw Version: 06.22.03.00\n.\n.\n.", "On Windows systems:\n---------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\nFor example:\n> %CANDLE_HOME%\\InstallITM\\kincinfo -i\n\n{Add your sample output here}\n*********** Thu Oct 7 16:03:55 Eastern Standard Time 2015 **********\nUser : Administrator Group : NA\nHost Name : <hostname> Installer: Ver: 062204000\nCandleHome: C:\\IBM\\ITM\nInstallitm: C:\\IBM\\ITM\\InstallITM\n*********************************************************************\n.\n.\n.\nPH Monitoring Agent for HMC Base Support\nWINNT Version: 06.22.03.04 Build: 201510070000\n\nPH Monitoring Agent for HMC Base Support\nWINNT Version: 06.22.03.04 Build: 201510070000\n\nPH Monitoring Agent for HMC Base Support\nWINNT Version: 06.22.03.04 Build: 201510070000\n.\n.\n.\n\n\n7.0 Known problems and workarounds\n=========================\nNone.\n\n\n8.0 Additional product information\n======================\nNone.", "9.0 Copyright and trademark information\n==================================\nA current list of IBM trademarks is available on the Web at \"Copyright\nand trademark information\" at www.ibm.com/legal/copytrade.shtml.\n\n\n10.0 Notices\n=======\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION\n\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,\nINCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.\nSome jurisdictions do not allow disclaimer of express or implied\nwarranties in certain transactions, therefore, this statement may not\napply to you.\n\nThis information could include technical inaccuracies or typographical\nerrors. Changes are periodically made to the information herein; these\nchanges will be incorporated in new editions of the publication. IBM\nmay make improvements and/or changes in the product(s) and/or the\nprogram(s) described in this publication at any time without notice.", "Microsoft, Windows, and Windows Server are trademarks of Microsoft\nCorporation in the United States, other countries, or both.\n\nJava and all Java-based trademarks are trademarks of Sun Microsystems,\nInc. in the United States, other countries, or both.\n\nUNIX is a registered trademark of The Open Group in the United States\nand other countries.\n\nOther company, product, or service names may be trademarks or service\nmarks of others.", "Third-Party License Terms and Conditions, Notices and Information\n-----------------------------------------------------------------\nThe license agreement for this product refers you to this file for\ndetails concerning terms and conditions applicable to third party\nsoftware code included in this product, and for certain notices and\nother information IBM must provide to you under its license to\ncertain software code. The relevant terms and conditions, notices and\nother information are provided or referenced below. Please note that\nany non-English version of the licenses below is unofficial and is\nprovided to you for your convenience only. The English version of the\nlicenses below, provided as part of the English version of this file,\nis the official version.", "Notwithstanding the terms and conditions of any other agreement you\nmay have with IBM or any of its related or affiliated entities\n(collectively \"IBM\"), the third party software code identified below\nare \"Excluded Components\" and are subject to the following terms and\nconditions:\n\n- the Excluded Components are provided on an \"AS IS\" basis\n- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND\nCONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT\nNOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE\nAND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND\nFITNESS FOR A PARTICULAR PURPOSE\n- IBM will not be liable to you or indemnify you for any claims\nrelated to the Excluded Components\n- IBM will not be liable for any direct, indirect, incidental,\nspecial, exemplary, punitive or consequential damages with respect\nto the Excluded Components.\n\nPREREQUISITES\nIBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim Feature 3", "INSTALLATION INSTRUCTIONS\nPlease refer to the README contained in the Description section above for general installation instructions.\n\nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.2.2.3-TIV-ITM_HMC_BASE-IF0004 18 May 2016 English 35850104 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=6.2.2.3-TIV-ITM_HMC_BASE-IF0004&product=ibm%2FTivoli%2FIBM+Tivoli+Monitoring&source=dbluesearch&platform=All] [ ] \nPRODUCT ALIAS/SYNONYM\n HMC Agent\nMonitoring Agent for System P\nSystem P Agent \n\n [/support/docview.wss?uid=swg24042283&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042283&aid=2]Problems (APARS) fixed\nIV47101, IV50134, IV50135, IV50686, IV60709, IV67769" ]

[ "6.2.2.3-TIV-ITM_HMC_BASE-IF0002\n---------------------------------\nFeature: 208626\nAbstract: LPAR Memory Attributes\nAdditional information: The following new attributes are added in\nthe Server LPARs attribute group:\n\nCurrent_Memory - The current amount of memory, in megabytes,\nconfigured for the LPAR.\nWarehouse name: CM0\nRunning_Memory - The amount of memory, in megabytes, varied on-line\nby the LPAR.\nWarehouse name: RM\n\nIn order to display these new attributes in the Tivoli Enterprise\nPortal, use the Query Editor and select Server LPARs_V9 under\nKPH SERVER LPARS." ]

[ 5 ]

[ "IBM Announcement: End of Support for WebSphere MQ and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 and WebSphere MQ Telemetry V7.0.1 - United States NEWS\n\nABSTRACT\n IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z/OS V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition for z/OS V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1. \n\nCONTENT\n\n\nTAB NAVIGATION\n * WebSphere MQ and File Transfer Edition V7.0.1 and V7.0.0 • MQ Telemetry V7.0.1 selected tab", "TAB NAVIGATION\n * What were the end of support dates for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1?\n * Do these announcements affect WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, or WebSphere MQ Hypervisor Edition V7.0.1?\n * What replacement products are available?\n * How do I check which version I am currently running?\n * Is any information available to help me upgrade to a later version?\n * How do I purchase a support extension for my current version?\n * When a WebSphere MQ server product goes out of support, does the client and file transfer agent also go out of support?\n * Are these products still supported when they are bundled with another IBM product?\n * Is the WebSphere MQ V7.0 Resource Adapter supported in WebSphere Application Server?\n * Is documentation still available for these products?", "* How do I obtain installation images for these products if I still need them?\n * Is there an IBM MQ V9.0 or MQ V8.0 trial version available for download?", "[/support/docview.wss?uid=swg21674407&amp;aid=1]\n\n\n\n\nWHAT ARE THE END OF SUPPORT DATES FOR WEBSPHERE MQ V7.0.1 AND V7.0.0, WEBSPHERE MQ FILE TRANSFER EDITION V7.0.1 AND V7.0.0, AND WEBSPHERE MQ TELEMETRY V7.0.1?", "*", "* Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z/OS V7.0.1 25 Sep 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-248] 30 Sep 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-150] z/OS WebSphere MQ V7.0.0 16 Jun 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-068] 30 Apr 2015", "[https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z/OS V7.0.0 27 Jun 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-067] 30 Sep 2011 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS910-014] z/OS WebSphere MQ File Transfer Edition V7.0.1 05 Jun 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-118] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC),", "Windows (x86) WebSphere MQ File Transfer Edition for z/OS V7.0.1 12 Jun 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-119] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z/OS WebSphere MQ File Transfer Edition V7.0.0 05 Dec 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-331] 30 Sep 2014 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z/OS V7.0.0 12 Dec 2008 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-339] 30 Sep 2014", "[https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z/OS WebSphere MQ Telemetry V7.0.1 27 Aug 2010 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS210-201] 30 Sep 2015 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] Linux (x86-64), Windows (x86)", "* \n * Review lifecycle dates for all IBM MQ and WebSphere MQ products [http://www.ibm.com/software/support/lifecycleapp/PLCSearch.wss?q=%28+%22IBM+MQ%22+OR+%22WebSphere+MQ%22+%29+AND+NOT+%28+Tivoli+OR+Adapter+OR+Broker+OR+Integrator+OR+Workflow+OR+%22Low+Latency+Messaging%22+%29]\n \n End of support information for WebSphere MQ V7.5 and WebSphere MQ Hypervisor Edition V7.5 [http://www.ibm.com/support/docview.wss?&uid=swg21996472]\n \n End of support information for WebSphere MQ V7.1, WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, and WebSphere MQ Hypervisor Edition V7.0.1 [http://www.ibm.com/support/docview.wss?&uid=swg21980668]\n \n \n * Back to top", "DO THESE ANNOUNCEMENTS AFFECT WEBSPHERE MQ FILE TRANSFER EDITION V7.0.4, V7.0.3 AND V7.0.2, WEBSPHERE MQ ADVANCED MESSAGE SECURITY V7.0.1, OR WEBSPHERE MQ HYPERVISOR EDITION V7.0.1?\n\n * IBM has subsequently announced the end of support for these products [http://www.ibm.com/support/docview.wss?uid=swg21980668] on all platforms including z/OS:\n * \n * Lifecycle dates for WebSphere MQ V7.0 products [http://www.ibm.com/software/support/lifecycleapp/PLCSearch.wss?q=%28%22WebSphere+MQ+%22+AND+%227.0%22%29+OR+%28%22WebSphere+MQ+File+Transfer+Edition+%22+AND+%28%227.0.4%22+OR+%227.0.3%22+OR+%227.0.2%22%29%29+OR+%28%22WebSphere+MQ+Advanced+Message+Security+%22+AND+%227.0.1%22%29] \n * \n * Back to top\n\n\n\n\nWHAT REPLACEMENT PRODUCTS ARE AVAILABLE?", "* Replacements for WebSphere MQ V7.0.1 and V7.0.0 include IBM MQ or IBM MQ Advanced V9.0 and V8.0. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 Apri 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * Replacements for WebSphere MQ for z/OS V7.0.1 and V7.0.0 include IBM MQ, IBM MQ Advanced, or IBM MQ Value Unit Edition for z/OS V9.0 and V8.0.0.", "* Replacements for WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 include IBM MQ Advanced V9.0 and V8.0. WebSphere MQ Advanced V7.5 is also available (except on IBM i), but its end of support date is 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117]. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ and replace the former File Transfer Edition and Advanced Message Security products.\n * Replacements for WebSphere MQ File Transfer Edition for z/OS V7.0.1 and V7.0.0 include IBM MQ Advanced for z/OS V9.0 and V8.0.0. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ for z/OS and replace the former File Transfer Edition for z/OS and Advanced Message Security for z/OS products.", "* The replacement for WebSphere MQ Telemetry V7.0.1 is IBM MQ or IBM MQ Advanced V9.0 or V8.0, all of which include Telemetry as a component of the MQ product. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * \n * \n * Back to top", "HOW DO I CHECK WHICH VERSION I AM CURRENTLY RUNNING?", "* Follow these general instructions [http://www.ibm.com/support/docview.wss?uid=swg21621707] or the IBM MQ Knowledge Center instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.adm.doc/q083280_.htm] to display your IBM MQ or WebSphere MQ version on all platforms except for z/OS with the command: dspmqver\n * On z/OS, look for message CSQY000I [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.doc/csq_y.htm] in the MSTR joblog to determine your version.\n * Follow the IBM MQ Knowledge Center instructions [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.wmqfte.doc/display_ver_cmd.htm] to display your Managed File Transfer or WebSphere MQ File Transfer Edition version with the command: fteDisplayVersion", "* WebSphere MQ Telemetry V7.0.1 only runs on WebSphere MQ V7.0.1 (fix pack 7.0.1.3 and later) on Linux (x86-64) and Windows (x86). Although there is no command to display the WebSphere MQ Telemetry version, if your WebSphere MQ version is V7.0.1 and you have a WebSphere MQ Telemetry service and channels [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.tt.doc/tt_intro.htm] configured, then you are running WebSphere MQ Telemetry V7.0.1.\n * \n * Back to top", "[/support/docview.wss?uid=swg21674407&amp;aid=2]\n\n \n\n\n\n\nIS ANY INFORMATION AVAILABLE TO HELP ME UPGRADE TO A LATER VERSION?", "* The IBM MQ and WebSphere MQ Migration Guide [https://www.ibm.com/developerworks/community/blogs/aimsupport/entry/websphere_mq_ibm_mq_migration_guide] is available to view online or download:\n * IBM MQ and WebSphere MQ Migration Guide [https://www.ibm.com/developerworks/community/blogs/aimsupport/resource/MQ_migration/WMQ_Migration.pdf] \n * \n * The IBM Knowledge Center also includes information to assist you in migrating to a supported version of IBM MQ or WebSphere MQ:\n * Migrating and upgrading to IBM MQ V9.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.mig.doc/q006180_.htm] Migrating and upgrading to IBM MQ V8.0 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q006180_.htm] Migrating and upgrading to WebSphere MQ V7.5 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.mig.doc/q006180_.htm] \n *", "* The following WebSphere Support Technical Exchange presentations may be helpful if you are considering running multiple MQ installations on your system:\n * Webcast replay: WebSphere MQ Multi-Version - First Steps [http://www.ibm.com/support/docview.wss?uid=swg27024276] Webcast replay: WebSphere MQ Multi-Version - Environment Considerations and Management [http://www.ibm.com/support/docview.wss?uid=swg27024340] \n * \n * Back to top", "HOW DO I PURCHASE A SUPPORT EXTENSION FOR MY CURRENT VERSION?\n\n * Support extensions are available for an additional fee. To purchase extended support for WebSphere MQ or any of the other products, please contact your local IBM sales representative.\n * US Customers should contact Customer Support Operations at 1-877-426-6006, option #2. If you provide your IBM customer number, they can quickly find your sales representative.\n * Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region:\n * \n * IBM Directory of Worldwide Contacts [http://www.ibm.com/planetwide/] \n * \n * Back to top\n\n\n\n\nWHEN AN WEBSPHERE MQ SERVER PRODUCT GOES OUT OF SUPPORT, DOES THE CLIENT AND FILE TRANSFER AGENT ALSO GO OUT OF SUPPORT?\n\n * Yes. WebSphere MQ V7.0 clients and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 agents go out of support at the same time as the server.\n * \n * Back to top", "[/support/docview.wss?uid=swg21674407&amp;aid=3] \n\n\n\n\nARE THESE PRODUCTS STILL SUPPORTED WHEN THEY ARE BUNDLED WITH ANOTHER IBM PRODUCT?\n\n * Yes, support is available for all bundled components until the IBM product that includes them is withdrawn from support. However, they are only supported when used by the bundling IBM product. Unrelated usage is not supported.\n * \n * Find the end of support date for your IBM software product [http://www.ibm.com/software/support/lifecycle/index_a_z.html] \n * \n * Back to top\n\n\n\n\nIS THE WEBSPHERE MQ V7.0 RESOURCE ADAPTER SUPPORTED IN WEBSPHERE APPLICATION SERVER?", "* Yes, the WebSphere MQ V7.0 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0] shipped with WebSphere Application Server V8.0 and V7.0 is supported through 30 April 2018 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-143], when both of those versions of WebSphere Application Server end support, or longer if you purchase a WebSphere Application Server support extension.\n \n * Similarly, the WebSphere MQ V7.1 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0_0] shipped with WebSphere Application Server V8.5.x is supported as long as that version of WebSphere Application Server remains in support, or longer if you purchase a WebSphere Application Server support extension.", "* However, if you manually install your own copy of the WebSphere MQ V7.x Resource Adapter in WebSphere Application Server or any third-party Java EE server, it will go out of support with the corresponding WebSphere MQ server version.\n \n * The IBM MQ V8.0 and V9.0 Resource Adapters cannot be installed in WebSphere Application Server V8.5.x, V8.0 and V7.0 because those versions support JMS 1.1 while the IBM MQ Resource Adapters implement JMS 2.0. WebSphere Application Server V9.0 ships with the IBM MQ V9.0 Resource Adapter [http://www.ibm.com/support/docview.wss?uid=swg21248089#7dotx_0_0_0] and includes full support for JMS 2.0. The version of MQ Resource Adapter you use must be supported by your Java EE server but does not need to match the version of the queue managers to which you wish to connect.\n \n * Back to top", "IS DOCUMENTATION STILL AVAILABLE FOR THESE PRODUCTS?\n\n * Yes. Online documentation is available in the IBM Knowledge Center, while downloadable Information Center installations and PDF versions of the manuals are available from the MQ Library page.\n * \n * WebSphere MQ V7.0.1 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.helphome.v70.doc/WelcomePagev7r0.htm] WebSphere MQ V7.0.1 library of downloadable documentation [http://www.ibm.com/software/integration/wmq/library/library701.html] WebSphere MQ V7.0.0 library of downloadable documentation [http://www.ibm.com/software/integration/wmq/library/library700.html] WebSphere MQ File Transfer Edition V7.0.4 Knowledge Center [http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/welcome/WelcomePagev7r0.html] WebSphere MQ Telemetry V7.0.1 [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.tt.doc/tt_intro.htm] \n * \n * Back to top", "HOW DO I OBTAIN INSTALLATION IMAGES FOR THESE PRODUCTS IF I STILL NEED THEM?\n\n * Installation images for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1 are no longer available from Passport Advantage [https://www.ibm.com/software/passportadvantage/pao_customer.html]. Contact IBM if you have an urgent business need for these installation images.\n * \n * Back to top\n\n\n \n[/support/docview.wss?uid=swg21674407&amp;aid=4]\n\n \n\n\n\n\nIS THERE AN IBM MQ V9.0 OR MQ V8.0 TRIAL VERSION AVAILABLE FOR DOWNLOAD?\n\n * You can obtain a full-featured trial version of IBM MQ to evaluate for 90 days:\n * \n * Try IBM MQ now [https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?pkgid=&S_SRCID=ESD-WSMQ-EVAL&source=ESD-WSMQ-EVAL&S_TACT=109J84RW&S_CMP=web_ibm_ws_appint_ct_wmq-ov&S_PKG=CR9H9ML&s=&id=2009-08-28+03%3A34%3A46.648052R&fam=&cat=&l=English+International&m=download&ibm-continue=Continue] \n * \n * Back to top", "Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ File Transfer Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.0.1, 7.0 All Editions Business Integration WebSphere MQ Telemetry Not Applicable Linux, Windows Business Integration IBM MQ \nPRODUCT ALIAS/SYNONYM\n WebSphere MQ WMQ" ]

[ "Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015" ]

[ 5 ]

[ "IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Image Construction and CompositionTool. (CVE-2015-4000) - United States SECURITY BULLETIN\n\nSUMMARY\n The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM Image Construction and Composition Tool.", "VULNERABILITY DETAILS\nCVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)", "AFFECTED PRODUCTS AND VERSIONS\nIBM Image Construction and Composition Tool v2.2.1.3 \nIBM Image Construction and Composition Tool v2.3.1.0 \nIBM Image Construction and Composition Tool v2.3.2.0\n\nREMEDIATION/FIXES\nThe solution is to apply the following IBM Image Construction and Composition Tool version fixes.\n\nUpgrade the IBM Image Construction and Composition Tool to the following fix levels:\n\n· For IBM Image Construction and Composition Tool v2.2.1.3\n· IBM Image Construction and Composition Tool v2.2.1.3 Build 32\n\nhttp://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-32&includeSupersedes=0 [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-32&includeSupersedes=0]", "· For IBM Image Construction and Composition Tool v2.3.1.0\n· IBM Image Construction and Composition Tool v2.3.1.0 Build 43\n\nhttp://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-43&includeSupersedes=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-43&includeSupersedes=0]\n\n\n· For IBM Image Construction and Composition Tool v2.3.2.0\n· IBM Image Construction and Composition Tool v2.3.2.0 Build 16", "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-16&includeSupersedes=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-16&includeSupersedes=0]\n\n\nYou should verify applying this configuration change does not cause any compatibility issues. If you change the default setting after applying the fix, you will expose yourself to the attack described above. IBM recommends that you review your entire environment to identify other areas where you have enabled the Diffie-Hellman key-exchange protocol used in TLS and take appropriate mitigation and remediation actions.\n\nWORKAROUNDS AND MITIGATIONS\nNone", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nReported to IBM by The WeakDH team at https://weakdh.org [https://weakdh.org] \n\nCHANGE HISTORY\n 18 August 2015: Original Version Published \n\n*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\nAccording 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." ]

[ "CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)" ]

[ 1 ]

[ "IBM Integration Bus Healthcare Pack V4.0 release notes - United States RELEASE NOTES\n\nABSTRACT\n This document contains the release notes for IBM Integration Bus Healthcare Pack V4.0, including the tooling and runtime components. \n\nCONTENT\nRelease notes file for: IBM Integration Bus Healthcare Pack\nProduct Release: 4.0\nUpdate name: 4.0.0.0\nVersions and fix packs:\n* V4.0.0.0 (electronic availability: 25 June 2015)\nDocument first published: 25 June 2015\nDocument last modified: 25 June 2015\n\n\n\n\nContents \n\n * Download location \n * Installation information: * Prior to installation \n * Installing \n * Documentation \n * Support \n * Feature updates\n \n \n * Additional information \n * Known problems and their workarounds (if any): * Installation \n * IBM Integration Toolkit\n \n \n * Copyright and trademark information \n * Useful websites", "Download location Download IBM Integration Bus Healthcare Pack V4.0 using the following instructions:\nhttp://www.ibm.com/support/docview.wss?uid=swg24040117 [http://www.ibm.com/support/docview.wss?uid=swg24040117] \n\n\nInstallation information \n\nAlways use the latest version of this release notes file, which is available in English only at:\nhttp://www.ibm.com/support/docview.wss?uid=swg27006917 [http://www.ibm.com/support/docview.wss?uid=swg27006917] \n\nTranslated release notes files are available at: \nftp://public.dhe.ibm.com/software/integration/integrationbus/docs/healthcare/V4.0/ [ftp://public.dhe.ibm.com/software/integration/integrationbus/docs/healthcare/V4.0/] \n\n\nPrior to installation", "For information about the tasks you must complete before you install the product, refer to the IBM Integration Bus Healthcare Pack product documentation at:\nhttp://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00090.htm [http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00090.htm]\n\nInstalling \n\nInstallation information is available in the IBM Integration Bus Healthcare Pack product documentation at:\nhttp://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00090.htm [http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00090.htm] \n\n\n\n\n\n\n\nDocumentation The online product documentation for IBM Integration Bus Healthcare Pack is available at: \nhttp://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00000.htm [http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00000.htm]", "Always refer to the online product documentation for the latest information. \n\nThe stand-alone product documentation is available for download at: \nftp://public.dhe.ibm.com/software/integration/integrationbus/docs/healthcare/V4.0/iib_healthcare_help.zip [ftp://public.dhe.ibm.com/software/integration/integrationbus/docs/healthcare/V4.0/iib_healthcare_help.zip] (Windows and Linux (x86-64) version)\n\nRead the How to add the Healthcare plug-in to a help system.txt file that is included in the iib_healthcare_help.zip file. \n\n\n\n\n\n\n\nSupport Defects: This release notes file might contain references to defect numbers. These numbers refer to internal IBM problem numbers; you might find these numbers useful when discussing problems with your IBM service representative.", "Technotes: For current information about known problems and available fixes, see the IBM Integration Bus support website at:\nhttp://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_Message_Broker [http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_Message_Broker] \nTo find information, click Troubleshooting documentation. IBM Integration Bus and IBM Integration Bus Healthcare Pack Technotes are displayed and can be ordered and searched. \n\nFor information about downloading IBM Integration Bus Healthcare Pack V4.0 installation images from the Passport Advantage website, see the Accessing the Installer topic in the IBM Integration Bus product documentation, which is available at:\nhttp://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha03080.htm [http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha03080.htm]", "Versions: For the latest information about which particular versions of operating systems are supported by IBM Integration Bus Healthcare Pack, see the system requirements page at:\nhttp://www.ibm.com/software/integration/wbimessagebroker/requirements/index.html [http://www.ibm.com/software/integration/wbimessagebroker/requirements/index.html] \n\n\n\n\n\n\n\nFeature updates Check periodically for updates to the toolkit, including documentation updates in English and in other supported languages. Recommended fixes for IBM Integration Bus Healthcare Pack can be found at: \nhttp://www.ibm.com/support/docview.wss?uid=swg27006041 [http://www.ibm.com/support/docview.wss?uid=swg27006041] \n\n\n\n\n\n\nTOP Additional information \nKnown problems and their workarounds (if any): This section outlines the known problems and their workarounds (if any) of the IBM Integration Bus Healthcare Pack, by component.", "TOP Installation \n * Installation of IBM Integration Bus Healthcare Pack V4.0.0.0 on computers that have a previous version installed is not supported To install IBM Integration Bus Healthcare Pack V4.0.0.0 you must first remove any existing installations of the IBM Integration Bus Healthcare Pack or IBM WebSphere Message Broker Connectivity Pack for Healthcare.\n \n \n\n\n\n\n\nTOP IBM Integration Toolkit \n * HL7® FHIR® Draft Standard for Trial Use The HL7® FHIR® standard is used in the Healthcare: FHIR transformation pattern. The standard is a Draft Standard for Trial Use (DSTU), rather than a full normative specification.\n \n \n\n\n\n\n\nTOP Copyright and trademark information \nhttp://www.ibm.com/legal/copytrade.shtml [http://www.ibm.com/legal/copytrade.shtml] \n\nThis information was developed for products and services offered in the U.S.A.", "IBM may not offer the products, services, or features discussed in this information 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. \n\nIBM may have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to: \n\n * \n * \n * \n * \n * \n * \n * \n * \n *", "For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: * \n * \n * \n * \n * \n * \n * \n\n\nThe 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.", "This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice. \n\nAny references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. \n\nIBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.", "Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nSuch information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or any equivalent agreement between us.", "Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. \n\nThis information includes examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. \n\nCOPYRIGHT LICENSE:", "This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. \n\nThe following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:", "AIX, developerWorks, IBM, Passport Advantage, WebSphere.\n\nJava and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates in the United States, other countries, or both\n\nMicrosoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. \n\nUNIX is a registered trademark of The Open Group in the United States and other countries.\n\nLinux is a trademark of Linus Torvalds in the United States, other countries, or both.\n\nOther company, product or service names might be trademarks or service marks of others. \n\n\n\n\n\n\nTOP Useful websites IBM Integration Bus product page\nhttp://www.ibm.com/software/products/us/en/ibm-integration-bus/ [http://www.ibm.com/software/products/us/en/ibm-integration-bus] \n\nWebSphere MQ Fix Packs\nhttp://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_MQ [http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_MQ]", "IBM Integration Bus Fix Packs\nhttp://www.ibm.com/support/docview.wss?uid=swg27006041 [http://www.ibm.com/support/docview.wss?uid=swg27006041] \n\nIBM Integration Bus Requirements\nhttp://www.ibm.com/software/integration/wbimessagebroker/requirements/ [http://www.ibm.com/software/integration/wbimessagebroker/requirements/] \n\nIBM Integration Bus release notes and readme files\nhttp://www.ibm.com/support/docview.wss?uid=swg27006917 [http://www.ibm.com/support/docview.wss?uid=swg27006917] \n\nIBM Integration Bus V10.0 stand-alone product documentation\nFor Linux:\nftp://public.dhe.ibm.com/software/integration/integrationbus/docs/V10.0/ib_help_linux.tgz [ftp://public.dhe.ibm.com/software/integration/integrationbus/docs/V10.0/ib_help_linux.tgz]\nFor Windows:\nftp://public.dhe.ibm.com/software/integration/integrationbus/docs/V10.0/ib_help_win.zip [ftp://public.dhe.ibm.com/software/integration/integrationbus/docs/V10.0/ib_help_win.zip]", "IBM Integration Bus Healthcare Pack V4.0 online product documentation\nhttp://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00000.htm [http://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.healthcare.doc/ha00000.htm] \n\nIBM Centre for Java™ Technology Development Downloads\nhttp://www.ibm.com/developerworks/java/jdk/ [http://www.ibm.com/developerworks/java/jdk/] \n\nIBM Integration Bus developerWorks Zone\nhttp://www.ibm.com/developerworks/websphere/zones/businessintegration/wmb.html [http://www.ibm.com/developerworks/websphere/zones/businessintegration/wmb.html] \n\nIBM Messaging blog\nhttps://www.ibm.com/developerworks/mydeveloperworks/blogs/c565c720-fe84-4f63- 873f-607d87787327 [https://www.ibm.com/developerworks/mydeveloperworks/blogs/c565c720-fe84-4f63-873f-607d87787327] \n\n\n\n\n\n\n\nTOP (C) Copyright IBM Corporation 2015. All rights reserved. \n\n\nCOPYRIGHT DATE\n 2015 \n\nORIGINAL PUBLICATION DATE\n 2015/6/25 \n\nPRODUCT ALIAS/SYNONYM\n IIB IBMIB" ]

[ "Release notes file for: IBM Integration Bus Healthcare Pack\nProduct Release: 4.0\nUpdate name: 4.0.0.0\nVersions and fix packs:\n* V4.0.0.0 (electronic availability: 25 June 2015)\nDocument first published: 25 June 2015\nDocument last modified: 25 June 2015" ]

[ 0 ]

[ "IBM Security Bulletin: Multiple vulnerabilities in Node.js affect IBM API Connect (CVE-2017-1000381, CVE-2017-11499) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM API Connect has addressed Node.js vulnerabilities involving access to sensitive information and potential denial of service. \n\nVULNERABILITY DETAILS", "CVEID:CVE-2017-1000381 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000381]\nDESCRIPTION:c-ares could allow a remote attacker to obtain sensitive information, caused by an out-of-bounds read in the ares_parse_naptr_reply() function when parsing NAPTR responses. By sending specially crafted DNS response packet, an attacker could exploit this vulnerability to read memory outside of the given input buffer and cause a denial of service.\nCVSS Base Score: 6.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128625 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128625]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L)", "CVEID:CVE-2017-11499 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11499]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by a flaw related to constant HashTable seeds. A remote attacker could exploit this vulnerability to flood the hash and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/129465 [https://exchange.xforce.ibmcloud.com/vulnerabilities/129465]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected IBM API Management Affected Versions IBM API Connect 5.0.0.0-5.0.6.4 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0 REMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation / First Fix IBM API Connect\n\n5.0.0.0-5.0.6.4 5.0.6.5 LI79821 Addressed in IBM API Connect V5.0.6.5.\n\nManagement Server is impacted.", "Follow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.4&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\n5.0.7.0-5.0.7.2 5.0.8.1 LI79821 Addressed in IBM API Connect V5.0.8.1.\n\nManagement Server and Developer Portal are impacted.\n\nFollow this link and find the \"APIConnect_Management\" package and\n\"APIConnect-Portal\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] IBM API Connect", "5.0.8.0 5.0.8.1 LI79821 Addressed in IBM API Connect V5.0.8.1.\n\nManagement Server and Developer Portal are impacted. \n\nFollow this link and find the \"APIConnect_Management\" package and\n\"APIConnect-Portal\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] WORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]", "RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 06 December 2017: original document published \n\n*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\nAccording 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." ]

[ "CVEID:CVE-2017-1000381 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000381]\nDESCRIPTION:c-ares could allow a remote attacker to obtain sensitive information, caused by an out-of-bounds read in the ares_parse_naptr_reply() function when parsing NAPTR responses. By sending specially crafted DNS response packet, an attacker could exploit this vulnerability to read memory outside of the given input buffer and cause a denial of service.\nCVSS Base Score: 6.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128625 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128625]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L)\n\nCVEID:CVE-2017-11499 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11499]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by a flaw related to constant HashTable seeds. A remote attacker could exploit this vulnerability to flood the hash and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/129465 [https://exchange.xforce.ibmcloud.com/vulnerabilities/129465]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)" ]

[]

[ "IBM Create backup of the ObjectServer database - United States MustGather; objectserver; backup TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Steps to create a backup of the ObjectServer database for troubleshooting. \n\nRESOLVING THE PROBLEM\nProvide the following information: \n\n[/support/docview.wss?uid=swg21631606&amp;aid=1][/support/docview.wss?uid=swg21631606&amp;aid=2]\n\n1. Create a temporary directory\n\nmkdir /tmp/backup \n\n2. Use nco_sql to obtain a backup\n\n./nco_sql -server NCOMS \nPassword: \n1> alter system backup '/tmp/backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that /tmp/backup contains *.tab files.\n\n4. Compressed /tmp/backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.\n\n[/support/docview.wss?uid=swg21631606&amp;aid=3]\n\n1. Create a temporary directory\n\nmkdir c:\\tmp\\backup \n\n2. Use nco_sql to obtain a backup", "isql -S NCOMS -U root \nPassword: \n1> alter system backup 'c:\\tmp\\backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that c:\\tmp\\backup contains *.tab files.\n\n4. Compressed c:\\tmp\\backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so." ]

[ "1. Create a temporary directory\n\nmkdir /tmp/backup \n\n2. Use nco_sql to obtain a backup\n\n./nco_sql -server NCOMS \nPassword: \n1> alter system backup '/tmp/backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that /tmp/backup contains *.tab files.\n\n4. Compressed /tmp/backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so." ]

[ 0 ]

[ "IBM Identify the application that has a WMQ queue opened - United States Identify application program connected queue TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your WebSphere MQ queue manager will not stop if there are applications that still have a queue opened. Your goal is to allow a graceful stop of the queue manager, also called controlled (or quiesced) shutdown. \n\nFor example, the following runmqsc command for the queue Q1 shows that there is an application currently that has opened a queue, but it does not provide application name, or process id number (PID). The value for OPPROCS indicates 1 application has opened the queue for output (for doing a PUT).\n\ndisplay qstatus(Q1)\n1 : display qstatus(Q1)\nAMQ8450: Display queue status details.\nQUEUE(Q1) TYPE(QUEUE)\nCURDEPTH(0) IPPROCS(0)\nLGETDATE( ) LGETTIME( )\nLPUTDATE( ) LPUTTIME( )\nMEDIALOG( ) MONQ(OFF)\nMSGAGE( ) OPPROCS(1)\nQTIME( , ) UNCOM(NO)\n\nYou want to determine the name of the application that currently has a queue open,", "RESOLVING THE PROBLEM\nUse the runmqsc display connection command to find the process id (PID) and application name. \n\nUsing the above example of the queue Q1, this is the complete command to invoke under runmqsc: \n\n\ndisplay conn(*) where(objname eq Q1) all\n\nExample output:\n\nAMQ8276: Display Connection details.\nCONN(ACBDC64820001B01)\nEXTCONN(414D5143514D5F414E47454C494C4C4F)\nTYPE(CONN)\nPID(7364)TID(1)\nAPPLTAG(WebSphere MQ\\bin\\amqsput.exe)APPLTYPE(USER)\nASTATE(NONE) CHANNEL( )\nCONNAME( ) CONNOPTS(MQCNO_SHARED_BINDING)\nUSERID(x) UOWLOG( )\nUOWSTDA( ) UOWSTTI( )\nUOWLOGDA( ) UOWLOGTI( )\nURTYPE(QMGR)\nEXTURID(XA_FORMATID[00000000] XA_GTRID[] XA_BQUAL[])\nQMURID(0.0) UOWSTATE(NONE)\n\nThe following fields are of interest:\nPID(7364) => Process id\nAPPLTAG(WebSphere MQ\\bin\\amqsput.exe) => name of the application\nUSERID(x) => Userid that has invoked the application\n\n\nFor UNIX users:", "One of the main purposes for the above technique is to eventually kill the process that is connected to the queue manager. \n\na) One option is to use the STOP CONN command under runmqsc. Using the above example, the corresponding command would be:\nSTOP CONN(ACBDC64820001B01)\n\nb) The following SupportPac can be used to identify the applications and kill them if desired:\n\nMS6B: WebSphere MQ Connection Management Utility [http://www.ibm.com/support/docview.wss?&uid=swg24017810]\nThis SupportPac is Category 4 (which means that the IBM MQ Support team does not support it)\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ" ]

[ "Use the runmqsc display connection command to find the process id (PID) and application name. \n\nUsing the above example of the queue Q1, this is the complete command to invoke under runmqsc: \n\n\ndisplay conn(*) where(objname eq Q1) all" ]

[ 1 ]

[ "IBM Security Bulletin: Vulnerabilities in OpenSSL affect IBM MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178) - United States SECURITY BULLETIN\n\nSUMMARY\n 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.", "VULNERABILITY DETAILS\nCVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: 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.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)", "CVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: 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.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8 \n\nMaintenance versions 8.0.0.0 through 8.0.0.5 are affected. \n\nIBM MQ V9 \n\n9.0.0.0 only\n\nREMEDIATION/FIXES\nIBM MQ V8 \n\nApply fixpack 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100] \n\nIBM MQ V9", "Apply fixpack 9.0.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048059]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 13 March 2017: Original version published\n24 May 2017: Details for 9.0.0.1 added \n\n*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\nAccording 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. \n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22000474]" ]

[ "CVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: 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.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)" ]

[ 1 ]

[ "IBM System Requirements for WebSphere MQ V8.0 - United States PRODUCT DOCUMENTATION\n\nABSTRACT\n This document contains system requirements for WebSphere MQ V8.0 and a note about IBM WebSphere MQ Advanced entitlement. \n\nCONTENT\nIBM has provided customers with a Software Product Compatibility Reports (SPCR) tool where you can locate and find complete lists of supported operating systems, system requirements, prerequisites, and optional supported software for WebSphere MQ 8.0.", "RHEL Compatible OS. Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V6. Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself. If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support. \n\nVirtualization. Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere MQ. Unless stated elsewhere in the system requirements WebSphere MQ has not been specifically tested in virtualization environments.", "WebSphere MQ support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself. \n\nPlease also refer to:\nWebSphere MQ's support position on Virtualization, low-level hardware, file systems on networks and high availability. [http://www.ibm.com/support/docview.wss?uid=swg21392025]\n\n\nThe SPCR tool links to information about the minimum product levels that must be installed before opening a problem report with IBM WebSphere MQ Technical Support. The software versions and any maintenance levels listed in the tool have been explicitly verified as working.\n\n\nSupported System Requirements: \nThe links below are located in the SPCR tool and go directly to the supported operating systems, prerequisites, system requirements, and optional supported software for the specific operating system. \n\n\nWebSphere MQ 8.0", "By Operating System\nAIX [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=AIX]\nHP [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=HP]\nIBM i [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=IBM%20i]\nLinux [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Linux]\n4690 (Managed File Transfer Agent Only) [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Other]", "Solaris [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Solaris]\nWindows [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Windows]\nz/OS [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=z/OS]", "By Component\nMQ Advanced Message Security [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568DDB101AEF11E38F7D228059AF1569]\nMQ Client [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_569814401AEF11E38F7D228059AF1569]\nMQ Explorer [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Desktop_56A6BA401AEF11E38F7D228059AF1569]\nMQ Managed File Transfer Agent [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_56910F601AEF11E38F7D228059AF1569]", "MQ Managed File Transfer Service [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568AA6C01AEF11E38F7D228059AF1569]\nMQ Queue Manager [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568C06501AEF11E38F7D228059AF1569]\nMQ Resource Adapter [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_5685EBD01AEF11E38F7D228059AF1569]\nMQ Telemetry Server [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568CF0B01AEF11E38F7D228059AF1569]", "SPCR tool available for all software products:\nThe generic link to the IBM Software Product Compatibility Reports (SPCR) tool is below. You can access the tool for any product and obtain the supported operating systems, system requirements, and optional supported software for your product version. \n\nClick the link below to reach the front page of SPCR:\nDetailed system requirements for a specific product in SPCR [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/softwareReqsForProduct.html]\n\nThen choose the following options to obtain the supported operating systems, system requirements, and optional supported software for your product version.\n\n1. Select the desired product.\n2. Select the desired version.\n3. Select your operating system.\n\n----------------------------------------------------------------------------------------------------------------\nIBM WebSphere MQ Advanced entitlement", "IBM WebSphere MQ Advanced and IBM WebSphere MQ Advanced Idle Standby grants entitlement to the following components: \n\n * IBM WebSphere MQ \n * IBM WebSphere Advanced Message Security \n * IBM WebSphere Managed File Transfer Service \n * IBM WebSphere MQ Telemetry \n\nIBM WebSphere MQ Advanced for Developers grants entitlement to the following components: * IBM WebSphere MQ \n * IBM WebSphere Advanced Message Security \n * IBM WebSphere Managed File Transfer Service \n * IBM WebSphere MQ Telemetry \n * IBM WebSphere Managed File Transfer Managed Endpoint\n\n----------------------------------------------------------------------------------------------------------------" ]

[ "This document contains system requirements for WebSphere MQ V8.0 and a note about IBM WebSphere MQ Advanced entitlement." ]

[ 0 ]

[ "IBM Upgrading to Jazz for Service Management Version 1.1.3.0 using Installation Manager results in a permission denied error - United States jazzsm1130relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When upgrading Jazz for Service Management to Version 1.1.3.0 using Installation Manager, the installation fails with the following error:\n\nCannot run program \"/space/IBM/JazzSM/ui/bin/wrapper.sh\" (in directory \"/space/IBM/JazzSM/ui/bin\"): error=13, Permission denied [/space/IBM/JazzSM/install/tip/tipWrapp\nerInstall.xml:215] \n\nCAUSE\nDuring the upgrade process the non-root user does not have the correct permissions to run the shell script. This is due to the following:\n1. Jazz for Service Management is installed as a non-root user\n2. Installation Manager is installed in user mode through root user", "RESOLVING THE PROBLEM\nThe upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. \n\n\nThe script takes two mandatory arguments and one optional argument.\n\nUsage: ./JazzSMgrpModeUpgrade.sh \"IM_Install_Location\" \n\"JazzSM_Install_Location [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/ref/psc_r_pathnames.html]\"\"[Response_file_with_absolute_Path]\"\n\nFor example (showing default installation paths): ./JazzSMgrpModeUpgrade.sh \"/home/root/IBM/InstallManager/\" \"/opt/IBM/JazzSM/\" \"/opt/Download/dash_upgrade_rsp.xml\"\n\n\nFor IM GUI mode installation, provide the 2 mandatory arguments; IM_Install_Location and JazzSM_Install_Location. \nThis argument combination invokes Installation Manager in GUI mode and lead you through the rest of the upgrade process.", "For IM Silent installation, provide all 3 arguments; IM_Install_Location , JazzSM_Install_Location, and Response_file_with_absolute_Path.\nThis argument combination invokes Installation Manager in silent mode to upgrade JazzSM.\n\nJazzSMgrpModeUpgrade.sh [/support/docview.wss?uid=swg21985946&aid=2]JazzSMgrpModeUpgrade.sh [/support/docview.wss?uid=swg21985946&aid=1]" ]

[ "The upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. \n\n\nThe script takes two mandatory arguments and one optional argument.\n\nUsage: ./JazzSMgrpModeUpgrade.sh \"IM_Install_Location\" \n\"JazzSM_Install_Location [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.3.0/com.ibm.psc.doc/ref/psc_r_pathnames.html]\"\"[Response_file_with_absolute_Path]\"" ]

[ 1 ]

[ "IBM How to include Rational Rhapsody external source files into configuration MakeFile - United States external; AddToMakefile; build; make; File element; MakeFile; external object; external objects; make file TECHNOTE (FAQ)\n\nQUESTION\n How can you configure the default setting of IBM Rational Rhapsody Developer Edition for C++ (RiC++) in order to include external source files into MakeFile? \n\nCAUSE\nIn some cases, you want to import legacy source files into Rhapsody models as external elements. For those externally imported elements (classes and files), Rhapsody doesn't generate code, hence you can preserve legacy code as part of your existing model. However, by default, Rhapsody excludes those external elements from the build even though you turn CG::File::AddToMakefile [File::AddToMakefile] property on.", "ANSWER\nFor general information regarding code generation for external elements, see \"Code generation for external elements [http://pic.dhe.ibm.com/infocenter/rhaphlp/v8/index.jsp?topic=%2Fcom.ibm.rhp.uml.diagrams.doc%2Ftopics%2Frhp_r_dm_cd_genrtion_extnl_elmts.html]\" topic in Rhapsody Info Center. This technote will provide 3 solutions to allow the inclusion of external elements into the build. \n\n\nSolution 1 - Use Component File element \n\n * \n * \n * Add source file to the build\n * \n\n\nSolution 2 - Use File/Class element", "* \n * \n * \n * \n * Note:\n * \n * \n * \n * \n * Add a Class/File element to map the external source code into the model. Set property CG::Class::UseAsExternal as \"checked\" for the added element. Set property CG::File::AddToMakefile [File::AddToMakefile] as \"checked\". Set the path to the external file in property CG::Class:FileName to make Rhapsody aware the location of the external source code. The path info would be used in MakeFile generated by Rhapsody.\n \n Note: Both absolute and relative path are supported. Right click the model element, from context menu, click Add New > SourceArtifact.\n \n Note: In order to include this external model element into MakeFile, SourceArtifact is required for the external model element. To enable the display of SourceArtifact, make sure Top Menu > View > Browser Display Options > Show Source Artifacts is checked.\n Make sure the type of added SourceArtifact is set either \"Logical\" or \"Implementation\" (DO NOT choose \"Specification\").", "Rename SourceArtifact with the name of the external source code (e.g. rename the element to \"hoo\", if the external file name is \"hoo.cpp\"). Click [Elements] tab of the SourceArtifact to make sure the model element is correctly mapped in SourceArtifact. In case of Class, the mapping will be done automatically. For File, manually add its parent element to [Elements] tab as below:\n \n [/support/docview.wss?uid=swg21621937&amp;aid=1]\n \n IMPORTANT: You might occasionally find the behavior of File is not consistent with Class. This is because File element is designed to be used as external element only, and not supposed to be built from Rhapsody. You are encouraged to use external Class element in RiC++ model to avoid any confusion you might experience. Generate MakeFile to make sure the external source file (e.g. hoo.obj) file is being added in the build.", "Solution 3 - Use Additional Sources setting \n\n * \n * \n * [Additional Sources]\n * \n * [Settings]\n * \n * \n \n Note: \n * \n\n\nRELATED INFORMATION\n#Code generation for external elements [http://pic.dhe.ibm.com/infocenter/rhaphlp/v8/index.jsp?topic=%2Fcom.ibm.rhp.uml.diagrams.doc%2Ftopics%2Frhp_r_dm_cd_genrtion_extnl_elmts.html]\nAdd source file to the biuld [http://pic.dhe.ibm.com/infocenter/rhaphlp/v8/topic/com.ibm.rhp.uml.diagrams.doc/topics/rhp_t_dm_adding_source_files_build.html?resultof=%22%61%64%64%22%20%22%73%6f%75%72%63%65%22%20%22%73%6f%75%72%63%22%20%22%66%69%6c%65%22%20%22%62%75%69%6c%64%22%20]" ]

[ "In some cases, you want to import legacy source files into Rhapsody models as external elements. For those externally imported elements (classes and files), Rhapsody doesn't generate code, hence you can preserve legacy code as part of your existing model. However, by default, Rhapsody excludes those external elements from the build even though you turn CG::File::AddToMakefile [File::AddToMakefile] property on." ]

[ 0 ]

[ "IBM Security Bulletin: GNU C library (glibc) vulnerability affects IBM DataPower Gateway appliances (CVE-2015-0235) - United States SECURITY BULLETIN\n\nSUMMARY\n GNU C library (glibc) vulnerability that has been referred to as GHOST affects IBM DataPower Gateway appliances. \n\nVULNERABILITY DETAILS\nCVEID: [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0235]CVE-2015-0235 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0235]\n\n\nDESCRIPTION:The gethostbyname functions of the GNU C Library (glibc) are vulnerable to a buffer overflow. By sending a specially crafted, but valid hostname argument, a remote attacker could overflow a buffer and execute arbitrary code on the system with the privileges of the targeted process or cause the process to crash. This issue is being referred to as the \"Ghost\" vulnerability.", "CVSS Base Score: 7.6\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100386 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100386]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:C/I:C/A:C)\n\nAFFECTED PRODUCTS AND VERSIONS\nAll DataPower versions through 6.0.0.11, 6.0.1.7, 7.0.0.4, 7.1.0.2\n\nREMEDIATION/FIXES\nFix is available in versions 6.0.0.12, 6.0.1.8, 7.0.0.5, 7.1.0.3. Refer to APAR IT06941 [http://www-01.ibm.com/support/docview.wss?uid=swg1IT06941] for URLs to download the fix. Customers using DataPower firmware version 5.0.x, contact customer support.\n\nIBM recommends that you review your entire environment to identify vulnerable releases of glibc including your Operating Systems and take appropriate mitigation and remediation actions. Please contact your Operating System provider for more information.\n\nWORKAROUNDS AND MITIGATIONS\nNone known", "GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 10 Feb 2015: Original Version Published \n\n*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\nAccording 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." ]

[ "CVEID: [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0235]CVE-2015-0235 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0235]\n\n\nDESCRIPTION:The gethostbyname functions of the GNU C Library (glibc) are vulnerable to a buffer overflow. By sending a specially crafted, but valid hostname argument, a remote attacker could overflow a buffer and execute arbitrary code on the system with the privileges of the targeted process or cause the process to crash. This issue is being referred to as the \"Ghost\" vulnerability.\n\n\nCVSS Base Score: 7.6\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100386 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100386]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:C/I:C/A:C)" ]

[]