id
string | question
string | answer
string | is_impossible
bool | contexts
list |
|---|---|---|---|---|
DEV_Q100 | ITCAM Agent for WebSphere DataPower 7.1 agent support for TLS
Does the ITCAM Agent for WebSphere DataPower 7.1 agent support TLS?
| - | true | [] |
DEV_Q101 | Help with Security Bulletin: WMB and IIB Toolkit cannot connect to a remote WMB broker or IIB node with a TLS-compliant cipher (CVE-2015-0118)
I need to understand details regarding Security Bulletin: WebSphere Message Broker Toolkit and IBM Integration Toolkit cannot connect to a remote WebSphere Message Broker broker or IBM Integration Bus node with a TLS-compliant cipher (CVE-2015-0118). Where can I find this information? | - | true | [] |
DEV_Q102 | Event Log Hashing - Performance?
I'm curious how much performance is affected by hashing events and flows. I don't see that information in the admin guide for 7.3.1. Can someone list that out by algorithm? | The overhead of writing these files is negligible, regardless of the hashing method selected. | false | [
{
"filename": "swg21965783.txt",
"text": "Title: IBM QRadar: Enabling On Event and Flow Hashing integrity checks with HMAC - United States\n\nText:\nHashing; QRadar; HMAC; integrity; hashed message authentication code; authentication TECHNOTE (FAQ)\n\nQUESTION\n What is the performance impact of using HMAC, and how does QRadar handle key management?\n\n\n\nANSWER\nThe overhead of writing these files is negligible, regardless of the hashing method selected. HMAC is no more expensive than the default options supported by QRadar previously. Once enabled the \nHMAC keys are added to new Events and Flows as they are written. When attempting to run the integrity check, it will take some time depending on the amount of data being validated. It will not cause performance issues, assuming the system is not at maximum load for disk input. \n\nFrom more information on HMAC please refer to the section Checking the Integrity of Event and Flow Logs in the QRadar Administration Guide.\n\nQRadar 7.3.0 Administration Guide [http://public.dhe.ibm.com/software/security/products/qradar/documents/7.3.0/en/b_qradar_admin_guide.pdf] \n\nQRadar 7.2.8 Administration Guide [http://public.dhe.ibm.com/software/security/products/qradar/documents/7.2.8/en/b_qradar_admin_guide.pdf] \n\n \n\n \n\nWhere do you find more information? \n\n\n\n\n[/support/docview.wss?uid=swg21965783&aid=1] [http://ibm.biz/QRadar-KC] [/support/docview.wss?uid=swg21965783&aid=2] [https://ibm.biz/qradarforums] [/support/docview.wss?uid=swg21965783&aid=3] [http://ibm.biz/qradarknowledge] [/support/docview.wss?uid=swg21965783&aid=4] [http://ibm.biz/SecSuptUTube] [/support/docview.wss?uid=swg21965783&aid=5] [http://ibm.biz/qradarsoftware] [/support/docview.wss?uid=swg21965783&aid=6] [http://ibm.biz/MyNotification] [/support/docview.wss?uid=swg21965783&aid=7] [http://ibm.biz/SuptRegQuikStart]"
}
] |
DEV_Q103 | How to resolve SessionBeanTimeoutException in WebSphere Application Server?
In one of my j2EE-applications I get com.ibm.ejs.container.SessionBeanTimeoutExceptions with the following caused by section:
Caused by: com.ibm.ejs.container.SessionBeanTimeoutException: Stateful bean CMStatefulBeanO(BeanId(server1# mySessionBean.jar# StdEJBReader, A5667152-014B-4000-E000-9AD20A8E643B), state = METHOD_READY) timed out ... 26 more
Do you know how to resolve such SessionBeanTimeoutExceptions in general? | - | true | [] |
DEV_Q104 | Java plugin not loading into rhapsody
I had installed rational rhapsody 8.2 in my machine. I tried to add the profile of the Simple plugin.sbs from the path C:\ProgramData\IBM\Rational\Rhapsody\8.2\Samples\ExtensibilitySamples\Simple Plug-in, finally it is found that the Simple plugin is failed to load in the Rhapsody process space.
I had tried to add the JavaAPILogFile=D:\RhapsodyLogFile\Logs.txt for collecting the logs and while loading plugin nothing is written into the log file.
When i launched the rhapsody the following is written into the logs
Enter: RhapsodyAppServer_attachToRhapsodyApplication
Enter: RPApplication_getTheJavaPluginsInterfaceNative
Exit: RPApplication_getTheJavaPluginsInterfaceNative
Please help me to resolve this issue | - | true | [] |
DEV_Q105 | Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux
I need to understand details regarding 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.
This is related to CVEIDs:
CVE-2018-1000001
CVE-2017-16997
CVE-2017-1000408
CVE-2017-1000409
CVE-2017-17426
Where can I find this information? | - | true | [] |
DEV_Q106 | Why does WebSphere DataPower spike with a high CPU rate when a WebSphere MQ connection is unavailable?
I have noticed when my MQ backends go down unexpectedly it can result in a high CPU rate on DataPower. And how can I resolve this? | The solution to the issue of having DataPower vulnerable to the MQ Queue Manager being inaccessible is to change the Retry Attempts parameter on the Configure MQ Queue Manager window from 0 to some number. | false | [
{
"filename": "swg21431301.txt",
"text": "Title: IBM WebSphere DataPower spikes with high CPU when WebSphere MQ connection is unavailable - United States\n\nText:\nretries; high CPU; MQ queue manager; Retry Interval; Retry Attempts; Long Retry Interval TECHNOTE (FAQ)\n\nQUESTION\n Why does WebSphere DataPower spike with a high CPU rate when a WebSphere MQ connection is unavailable? Is there a solution to this issue? \n\nCAUSE\nIf the value of Retry Attempts is set to 0 on the DataPower MQ Queue Manager object, this negates the benefits of the Long Retry Interval since it will not be used. DataPower will retry forever using the specified Retry Interval. The default setting of Retry Attempts as 0 and Retry Interval as 1 second is provided to preserve backward compatibility. However, these default values should be changed to take advantage of Long Retry Interval feature available in firmware.\n\nANSWER\nThe solution to the issue of having DataPower vulnerable to the MQ Queue Manager being inaccessible is to change the Retry Attempts parameter on the Configure MQ Queue Manager window from 0 to some number. As an example, change the parameters as follows: \n\n * Retry Attempts - change the default of 0 to 6 Retry Interval - change the default of 1 to 10 seconds Long Retry Interval - change the default of 1800 to 600 seconds (10 minutes) \n\n\nIn the event that the Queue Manager is down or a connection is not established, the above example configuration will allow the MQ QM Object to retry 6 times with 10 second intervals. After 6 attempts, the MQ QM object will retry every 10 minutes. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI50 Firmware 3.8 Business Integration WebSphere DataPower Low Latency Appliance XM70 Firmware 3.8"
}
] |
DEV_Q107 | Why the exception "BO Service is not supported or disabled in this profile" when trying to publish from IID to a local Process Server?
When trying to publish a project from IBM Integration Designer (IID) to the local Process Server, it fails with error ADMA5014E in SystemOut.log. The FFDC log is showing exception of BO Service is not supported or disabled in this profile; Trace:
FFDC Exception:java.lang.ExceptionInInitializerError SourceId:com.ibm.ws.bpm.cmdfrmwrk.task.WBICleanupTask ProbeId:200 java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:259)
....
Caused by: java.lang.IllegalStateException: BO Service is not supported or disabled in this profile. at com.ibm.ws.bo.BOCore.init(BOCore.java:107) .... | - | true | [] |
DEV_Q108 | Why do I get "OSS version is not suitable for installation" when attempting to install the MQ 5.3.1 base version on a HP Integrity NonStop Server BladeSystem?
I am trying to install the MQ 5.3.1 base version on a HP Integrity NonStop Server BladeSystem, but it complains saying that the "OSS version is not suitable for installation". My OSS version is J06.14 and it looks to be a supported version according to the System Requirements site:
http://www-01.ibm.com/support/docview.wss?uid=swg27006797
Why am I getting this error message? | For the HP Integrity NonStop Server H-Series systems, the following system
software versions are the minimum mandatory level for V5.3.1.12:
- H06.23.01 or later | false | [
{
"filename": "swg27048240.txt",
"text": "Title: IBM Readme for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 12 - United States\n\nText:\n PRODUCT README\n\nABSTRACT\n This readme provides information for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 12. \n\nCONTENT\nDESCRIPTION\n\n\n============\n\nThis file describes product limitations and known problems.\nThe latest version of this file can be found here:\nhttps://ibm.biz/mqreadmes [https://ibm.biz/mqreadmes]\n\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\nUPDATE HISTORY\n20 May 2016 - Updates for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 12\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\n--------------------------------------------------------------------\nCONTENTS\n========\n\nIntroduction\nAbout this release\nInstallation, migration, upgrade and configuration information\nUn-installation information\nKnown limitations, problems and workarounds\nDocumentation updates\nContacting IBM software support\nNotices and Trademarks\n\nINTRODUCTION\n============\n\nWelcome to IBM(R) WebSphere(R) MQ for HP NonStop Server, Version 5.3.1.12\n\nThis release notes file applies to the latest WebSphere MQ cross-platform\nbooks (for Version 5.3), and to the WebSphere MQ for HP NonStop Server,\nVersion 5.3 specific books (WebSphere MQ for HP NonStop Server System\nAdministration Guide and WebSphere MQ for HP NonStop Server Quick\nBeginnings).\n\nThe content of these release notes applies to the WebSphere MQ for HP\nNonStop Server product unless otherwise stated.\n\nThis release notes file contains information that was not available in\ntime for our publications. In addition to this file, README,\nyou can find more information on the WebSphere MQ Web site:\n\nhttp://www.ibm.com/software/integration/wmq/ [http://www.ibm.com/software/integration/wmq/]\n\nFor current information on known problems and available fixes,\nSupportPacs(TM), product documentation and online versions of this and\nother readme files see the Support page of the WebSphere MQ Web site at:\n\nhttp://www.ibm.com/software/integration/wmq/support [http://www.ibm.com/software/integration/wmq/support]\n\nABOUT THIS RELEASE\n==================\n\nNomenclature\n------------\nThe terms \"WMQ V5.3.1\" and \"WMQ V5.3.1.0\" both refer to the same WMQ Refresh\nPack without subsequent service installed. Throughout this readme, references\nto \"WMQ V5.3.1.x\" refer to WMQ 5.3.1 with or without subsequent service\ninstalled.\n\nNew in this release\n-------------------\n\nThis is the twelfth FixPack for IBM WebSphere MQ V5.3.1 for HP NonStop Server,\nand is designated V5.3.1.12, with associated APAR IT15471.\n\nThis release is cumulative for all service and internal defect correction \nperformed since WMQ 5.3.1 was released. \n\nAll native object and executable files distributed with this FixPack have the\nfollowing version procedure strings:\n\nT0085H06_31MAY2016_V53_1_12_<buildid> (Where buildid is the internal build\nidentifier)\n\nThe Non-native library distributed with this FixPack has the following \nversion procedure string:\n\nT0085H06_28FEB2015_V53_1_11 \n\nIf upgrading from V5.3.1.5 or later releases, this FixPack does NOT require \nTNS (non-native) applications to be re-bound with the MQI library. More on \nthis is described later on in this readme.\n\nIBM have not identified any new HP NonStop Server system software problems\nsince V5.3.1.6 was released. The current set of recommended solutions is \ndescribed later on in this readme.\n\nIBM recommends that you ensure that your HP NonStop Server system software\nproducts are at SPR levels that incorporate these fixes (solutions) as a\npreventive measure. IBM has tested WMQ with these fixes in our own\nenvironment before making the recommendations.\n\nImportant note about SSL channels\n---------------------------------\n\nThis release includes a new version of openSSL (1.0.2h) to maintain currency\nwith known vulnerabilities discovered since the version shipped with V5.3.1.\nA new version of the SSLupdate.pdf document was provided with the V5.3.1.10\nfixpack, and is also included with this this release, located in the \n<install_path>/opt/mqm/READMES/en_US directory. If you use SSL channels you\nshould review the revised version of SSLupdate.pdf prior to installing this\nfixpack.\n\nThe following SSL information applies if you are upgrading from WMQ V5.3.1 and\nare using SSL channels. The following procedure is not required if you have \nalready installed WMQ V5.3.1.1\n\nSeveral of the fixes in this and previous FixPacks that relate to SSL channels\nchange the way that SSL certificates are configured with WebSphere MQ. If\nyou use SSL channels you will need to review the new documentation supplement\nSSLupdate.pdf for information about this change and make configuration changes\nPlease also see the Post-installation section below for a summary of the\nrequired changes.\n\nIn V5.3.1.10 Patch1 and all later releases, CipherSpecs that use the SSLv3\nprotocol were deprecated. Continued use of SSLv3 CipherSpec's is not recommended\nbut may be enabled by setting the AMQ_SSL_V3_ENABLE environment variable.\nIn addition to that Env01=AMQ_SSL_V3_ENABLE=1 has to be added to the MCA stanza \nof the queue manager's qmproc.ini file.\n\nWith OpenSSL 1.0.2h the following CipherSpecs have been deprecated:\nDES_SHA_EXPORT1024\nRC4_56_SHA_EXPORT1024\nRC4_MD5_EXPORT\nRC2_MD5_EXPORT\nDES_SHA_EXPORT\nTLS_RSA_WITH_DES_CBC_SHA\n\nWhile WMQ V5.3.1.12 does still support these weak CipherSpecs for compatibility\nreasons, they are deemed as not secure and should not be used. \n\nPlease check product documentation to confirm the CipherSpec is valid and consult\ndocumentation for any instructions when adding new environment variables.\n\n\nImportant note about WebSphere MQ V5.3 classes for Java and JMS\n---------------------------------------------------------------\n\nFixpack V5.3.1.10 resolved an incompatibility between NonStop Java 7 and the\nWMQ product libraries - that fix is also included in V5.3.1.12.\nThe method used to configure Java in V5.3.1.10 and later differs from \nthat in releases prior to V5.3.1.10. The Java.pdf document shipped in the \n<install_path>/opt/mqm/READMES/en_US directory was updated to reflect the\nchange. Java/JMS users migrating from versions prior to 5.3.1.10 should \nreview the updated document.\n\nImportant note about instmqm for V5.3.1\n---------------------------------------\n\nSince FixPack V5.3.1.5, IBM provided a modified WebSphere MQ product\ninstallation script, instmqm, for any level of V5.3.1. The new installation\nscript includes a workaround for the OS problem introduced in G06.29/H06.06\nwhere the OSS 'cp' command creates Guardian files in Format-2 form during an\ninstallation rather than Format-1. This change caused problems binding and\ncompiling non-native and native COBOL applications, as well as wasting a lot of\ndisk space because of the very large default extents settings for the Format-2\nfiles created by OSS cp.\n\nInstmqm has been modified in FixPack V5.3.1.5 to work around this change in OSS\ncp by forcing all Guardian files in an installation to be created as Format-1.\nThe use of the new installation script is recommended for all new V5.3.1\ninstallations.\n\nExisting installations that are not affected by the application relink or\nrebind problems can remain as they are.\n\nProduct fix history\n-------------------\n\nThe following problems are resolved in FixPack V5.3.1.12:\n\nAPAR IT08589 - WebSphere MQ V6 or V7 queues become \"missing\" from clusters. Application\ncalls to MQOPEN (sometimes MQPUT1, MQPUT) suffer queue name lookup\nerrors (Examples: 2085, 2082) when they try to access the affected \ncluster queues. \n\nAPAR IT10388 - When the receiving QMgr has its channel set with SSLCAUTH(OPTIONAL),\nthe Nonstop Queue Manager insists on sending a certificate to \nidentify itself. The remote side, however, does not require one\n\nAPAR IT11557 - Updated OpenSSL library to version 1.0.2h. This update deprecates sslchiph \ncipherspec TLS_RSA_WITH_DES_CBC_SHA and fixes various security \nvulnerabilities.\n\nAPAR IT12856 - When a node is removed from an MQ cluster and there is an automatically\ndefined cluster sender channel from a MQ node on NonStop to the removed\nnode, the sender channel on NonStop can go into state INITIALIZING and\nstay there for up to 60 minutes instead of being deleted after the first\nretry interval has expired.\n\nAPAR IT12875 - When a message is put into a remote/cluster queue within a TMF user\ntransaction and while the corresponding transmit queue is empty or almost\nempty, it can take up to 60 seconds after the end of the transaction\nuntil the message is transmitted. As a side effect automatic channel \nstarts can also be delayed.\n\nAPAR IT12894 - Java 7 SSL clients behave differently than previous versions which \nresulted in an RC 2009 error on its connection attempt. This\nis fixed with V.5.3.1.12.\n\nAPAR IT14169 - When a CPU is stopped, some sender channels were not recovered \nand stayed in inactive state. \n\nAPAR IT15316 - Memory allocation during MCA and LQMA creation and initialization was\nnot handled properly and may result in an unresponsive system.\n\nAPAR IT15317 - Under some conditions agents stay alive but don't accept new\nconnections. That is the case if an agent has reached the maximum \nnumber of connections it is allowed to handle during its lifetime\nbut the agent can't terminate before the last connection has been \nclosed.\n\nAPAR IT15490 - A configured process name rule has not been applied because it \nwas defined with lower case characters, while the operating \nsystem interface delivered upper case process names. Since the name\ncomparison then fails the configuration is not applied.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.12:\n\nIN000100 - The CRTMQM command may fail with error 1017 if queue managers are \ncreated in parallel.\n\nIN000101 - The installer has been enhanced to properly support SMF virtual disks\nif the system revision is on H06.26 and newer or J06.15 and newer.\n\nIN000102 - Removed access to uninitialized memory within mqconn which may result in\nRC 2059 MQRC_Q_MGR_NOT_AVAILABLE.\n\n\nFixes introduced in previous fixpacks\n=====================================\nThe following problems were resolved in FixPack V5.3.1.11:\n\nAPAR IT03572 - In V5.3.1.10, the dspmqver -V command displays the string \n\"VPROC\" rather than the VPROC string encoded in the product.\nV5.3.1.11 corrects this problem.\n\nAPAR IT04083 - Error 30 received by Queue Server in a complex Queue Manager \nconfiguration using MQGMO_SET_SIGNAL. This is a result of\nthe limit on the number of outstanding messages sent by the \nprocess not being set to the same value as the internal counter.\nThis results in the Queue Server reporting \"Guardian error 30 \nattempting to send signal notification\" in the queue manager \nerror log.\n\nAPAR IT04533 - Cluster sender channels fail to start following a CPU failure\non a 2 CPU system when the Repository Manager and Channel Server\nare both in the same CPU. Following the CPU failure, the Queue\nManager error log repeatedly reports message AMQ9422 \n\"Repository manager error, RC=545284114\" \n\nAPAR IT04876 - Some ssl channels with mismatched sslchiph cipherspecs run \nsuccessfully because protocol versions are not compared. \n\nAPAR IT05353 - Mitigation for SSLV3 POODLE Attack - CVE-2014-3566 \n\nAPAR IT07330 - WebSphere MQ V5.3.X Process does not write FDC (First \nFailure Symptom Report) records when the current FDC file is\nphysically full. This can result in processes experiencing error\nconditions, but the error condition not being reported in the \nFDC file. This fix changes the error handling to identify this\nscenario and switch to a new FDC file with an incremented \nsequence number \n\nAPAR IV19854 - The master repository manager in a partial repository \nunnecessarily subscribes to each cluster queue manager that\nit is aware of. This causes a significant increase in the number\nof subscriptions that are made, and in large clusters this can\ncause performance problems. \n\nAPAR IY87702 - SIGSEGV resulting from failed getpwnam. In some circumstances\ngetpwnam can return a success value in errno, but a null\npointer as the user record. This results in a SIGSEGV from \namqoamd. This change adds a check for this condition and handles\nit correctly. \n\nAPAR IY91357 - Altering a channel definition unintentionally resets the \nSSLPEER() attribute for the channel. \nWhen a channel with SSLPEER information is modified to include\neither MSGEXIT or MSGDATA attributes, the SSLPEER attribute \nbecomes blank. V5.3.1.11 resolves this problem. \n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.11:\n\n909 - In the GA release, the TFILE was opened with depth 100 in the\nGuardian NonStop process pairs. In configurations with large\nlarge numbers of connecting applications/threads, this could\nresult in probe QS270000 errors from nspPrimary, with an Arith1\nvalue of 83 (0083 Attempt to begin more concurrent transactions \nthan can be handled). This change increases the TFILE open depth\nto 1000. The default value can be changed from 1000 to a value\nbetween 100 and 1000 using MQTFILEDEPTH environment variable.\nIf a value < 100 or > 1000 is specified, a value of 100 will\nbe used, and an FDC will be reported with the text\n\"Invalid MQTFILEDEPTH specified - using default\"\n\n1380 - In the cra library, several FFST code sites report an error \nwithout reporting the name of the channel involved in the error\ncondition. This change adds the channel name to the FFST report\nin cases where the channel name is available to the calling code\n\n1471 - In earlier releases of 5.3.1, if a garbage argument string is \nsupplied to dspmqfls, the command abends rather than reporting a\nusage message. V5.3.1.11 resolves this problem\n\n1597 - In earlier releases of 5.3.1, the dspmqfls output shows a \nQueue/Status server value. Status servers were part of the V5.1\narchitecture but are not present in 5.3.1. V5.3.1.11 changes the \nmessage to reflect the fact that all objects are now managed by\nQueue Servers.\n\n2230 - In earlier releases of 5.3.1, the runmqsc command \n\"DISPLAY QSTATUS(*) TYPE(HANDLE) ALL\" does not cleanly handle a\nscenario where there are more than 500 handles. Attempts to use\nthe command when there are more than 500 handles to be returned\nresults in FFSTs with probe NS013000 from nspReply, and probe\nQS264002 from qslHandleHandleStatus. See later section on\n\"KNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS\"\n\n4158 - Slow memory leak in MQDISC in non-native library. In prior\nreleases, the non-native implementation of MQDISC contained a\nslow memory leak. This resulted in applications performing \nrepeated MQCONN/MQDISC operations during the process lifetime\neventually receiving a MQRC_STORAGE_NOT_AVAILABLE error from\nMQCONN, and an FFST for probe ZS219001 from zstInsertPCD. The\nproblem can also manifest as a probe XC130006 from \nxehExceptionHandler inside an MQOPEN call.\n\n4395 - If memory allocation for internal working storage fails during\nan attempt to create a dynamic queue, the LQMA assoicated with\nthe operation will ABEND, rather than returning a completion\ncode of 2071 (MQRC_STORAGE_NOT_AVAILABLE). This change resolves\nthe problem.\n\n4421 - If an attempt to start an OAM server detects an existing OAM\nserver in the CPU, in prior releases, the FFST generated did not\ninclude the process name. This change amends the FFST to\ninclude the process name of the offending process, where that\nname can be determined. \n\n4428 - The altmqfls command \"resetmeasure\" was incorrectly documented\nin the original version of the SysAdmin guide. See later section\n\"DOCUMENTATION UPDATES\"\n\n4496 - In earlier versions of this readme file, the instructions on \nhow to reassign Queue Server for \nSYSTEM.CLUSTER.TRANSMISSION.QUEUE are incorrect. Refer to the\n\"KNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS\" section for the\ncorrect procedure.\n\n4523 - If an OAM server attempts to start in a CPU, and there is \nalready an OAM server registered, prior to V5.3.1.11, the OAM\nsubsystem reported that there was a rogue process, but not\nthe name of the process. This change enhances the error\nreporting to report the name of the rogue process. \n\n4726 - Prior to this fixpack, the instmqm script did not check for\nsaveabend files and FFSTs generated during the validation\nphase of the installation. V5.3.1.11 adds this check.\n\n4774 - The cobol binding library, MQMCB, was shipped without symbols in\nFixPack V5.3.1.10, which causes applications to fail. V5.3.1.11\nresolves this issue. \n\n4800 - During instmqm, the script checks for the UNIX socket server.\nIn prior releases, in the event that this check failed, the\nerror message referred to the old UNIX socket server ($ZPMON).\nThis has been changed to refer to the new UNIX socket subsystem\n$ZLSnn, \"nn\" is the CPU number.\n\nAPAR IC85889 - UNEXPECTED IPC MESSAGES RECEIVED FOLLOWING PROCESS\nTERMINATION CAUSE EC TO ABEND REPEATEDLY\nIf a process sends an unexpected message to the MQECSVR\nprocess pair, the primary process will abend resulting in a\ntakeover by the backup process. The new primary process will\nthen abend. The only resolution is to restart the queue manager. \n\nAPAR IC87007 - PRIMARY QUEUE SERVER ABEND FOLLOWING TRANSACTION ABORT\nIn some circumstances, aborts of global units of work \ninvolving MQGETs of messages greater than 52k will result in an \nabend of the primary queue server responsible for the queue. \nThis renders the queue manager unresponsive \n\nAPAR IC87627 - WEBSPHERE MQ V5.3.1.8 FDC FILES DO NOT CONTAIN ENOUGH ERROR \nINFORMATION\n\nAPAR IC89128 - LISTENER FAILS TO START FOLLOWING UPGRADE TO \nHP J06.14/H06.25 OR T9050J01-AWT/T9050H02-AWS\nIn some configurations, the listener process will not run\nfollowing an upgrade to J06.14/H06.25 or the installation of \nT9050J01-AWT/T9050H02-AWS. The failure is dependent on the\nnumber of OSS processes running and their distribution between\nthe CPUs on the system. This problem also affects endmqlsr.\n\nAPAR IC89751 - CLUSSDR Channels do not restart without manual intervention\nafter CPU crash.\nIf a CLUSSDR or SDR channel is running in an MCA that is in the \nsame CPU as the Primary Channel Server, and that channel has \nbeen running for at least 5 minutes, and that CPU crashes, the \nchannel will not automatically restart. \n\nAPAR IC92511 - TERMINATION OF SLAVE REPOSITORY MANAGER RESULTS IN CLUSTER \nCHANNEL DELETION. In some cases this can result in a manually\nstopped cluster sender channel starting unexpectedly when they\nare dynamically recreated. \n\nAPAR IC92570 - MULTIPLE CLUSTER RECIEVER CHANNELS OR LONG RUNNING CLUSRCVR \nCHANNELS CAUSE METADATA FDC'S\n\nAPAR IC93289 - WEBSPHERE MQ R531 ON HP-NSS CLUSTER PUB SUB MESSAGES FAIL\nWITH AMQ9538 - COMMIT CONTROL ERROR \n\nAPAR IC94647 - Closing dynamic queues with MQCO_DELETE or MQCO_DELETE_PURGE\nwith an outstanding MQGET with signal results in multiple FDCs \nand an orphaned dynamic queue\n\nAPAR IC96947 - Backup Queue Server generates \"Open handle points to unused \nentry in default page\" FFST following LQMA termination \n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.10:\n\n4607 - Analyze lock logic in queue server takeover does not take account\nof temporary dynamic queues\n4679 - Exhaustion of message quickcell (MQC) space available to queue \nserver results in unstable queue manager\n4563 - RDF compatible message overflow file setting requires queue \nmanager restart \n4560 - Slave repository managers issue channel manipulation commands \nthat should be performed only by the master\n4557 - Write NonStop specific trace information to product standard \ntrace files rather than platform-specific file\n4556 - Internal Queue manager query array size can cause problems \nwith clusters containing more than 10 queue managers\n\n\nThe following problems were resolved in FixPack V5.3.1.9:\n\nAPAR IC51322 - CODE CHANGES FOR OPTIMIZATION OF DEFAULT CONVERSION\nDelay in processing seen during the default conversion between\nclient and server. The channel attempts normal conversion first,\nincluding attempting to load a conversion table before dropping\nthrough to the default conversion. Once default is required \nfor a specific set of code pages, this is now remembered \nand the attempt to perform normal conversion skipped.\n\nAPAR IY76799 - A FAILED CALL TO GETPEERNAME RESULTS IN A LEAKED SOCKET FILE\nWMQ amqrmppa (channel) process leaks a file descriptor in\nthe rare circumstance that a call to the getpeername function\nfails. Such a failed call is reported in the WMQ error logs for\nthe queue manager via an AMQ9213 message reporting that the\ngetpeername call has failed. The failure of\nthe getpeername call is the result of preoblems external to \nWMQ. This problem could also cause the WMQ listener process\n(runmqlsr) to run out of file descriptors, if there is\nno queue manager running, and lots of connections come in,\nwhilst these connections fail with getpeername problems.\n\nAPAR IY95706 - SIGSEGV IMMEDIATELY FOLLOWING RETURN FROM ZFUDOESOBJECTEXIST\nAn amqzlga0 process or amqrmppa process will raise an XC130004 \nFDC and the amqzlga0 process will end. The abrupt termination of\nthe amqzlga0/amqrmppa process may cause channels or applications\nconnected to the queue manager to fail\n\nAPAR IZ06131 - RECOVER FROM SYSTEM.AUTH.DATA.QUEUE CORRUPTED BY USER ERROR\nApplications receive MQRC_NOT_AUTHORIZED (2035) error\nsetmqaut returns MQRC_UNKNOWN_OBJECT_NAME (2085) and fails to\nset new authorities. Records are missing from the \nSYSTEM.AUTH.DATA.QUEUE, determined by a mismatch between the \noutput from amqoamd -m -s, and the authorities that customers \nbelieve they have set for users and objects. This fix allows \nrecovery from this situation using setmqaut without the need \nto recreate the queue manager \n\nAPAR IC74903 - SSLPeer value slash (/) causes SSL handshake to fail\nUsing slashes in the Distinguished Name name fields such as CN,\nO, OU, L, will fail SSLPEER value verification, and as such SSL\nHandshake, due to an MQ parsing error. MQ uses slashes (/) to\ndelimit the distinguished name values when matching the SSLPEER\nvalue with the information contained in the certificate.\n\nAPAR IC82919 - xcsAllocateMemBlock returning xecS_E_NO_MEM\nQueue manager (receiver channel side) with API exits generate\nFDCs containing probe ZF137003 and error log entries for AMQ9518\nin the form of - File '/mqs/WMQtest/var/mqm/@ipcc/AMQRFCDA.DAT'\nnot found.\n\nAPAR IC80942 - Authority commands produced by amqoamd command is not usable if\nauthorization is \"+None\"\n\nUsing the setmqaut command with commands generated by amqoamd\nresults in a failure e.g\n\"setmqaut -m qmgrname -n name -t queue -g group +None\"\nreturns:\n\"AMQ7097: You gave an authorization specification that is not\nvalid.\"\n\nAPAR IC81429 - MQRC error 2003 received if an overflow file record is missing\nIf a portion of a message that should be stored the queue \noverflow file is missing, the generation of an FFST is \nsuppressed and a 2003 reason code is returned. All subsequent \nnon-specific MQGETs from the queue fail, since the partial \nmessage cannot be retrieved. \n\nAPAR IC81420 - Queue Server abend during simultaneous GET and BROWSE\nWhen a message larger than 56k is being browsed (MQGET with\none of the MQGMO_BROWSE_* options) from a client application \nusing message groups, and another process is simultaneously \nperforming a destructive MQGET on the same message. The primary\nqueue server terminates, and more or more of the following\nprobes are generated :QS003002, AO211001, AO200002, ZI074001,\nNS026006\n\nAPAR IC81367 - FixPack 5318 MQMCB Guardian library is not usable\nThe COBOL wrapper libraries were changed from type LINKFILE to\nDLL in the v5.3.1.8 Fixpack, and the packaging unintentionally\nstripped the symbols from the Guardian variant of the library\nZWMQBIN.MQMCB. During the link phase of a cobal program build\nthe following fatal error is encountered:\n\"Cannot use file specified in CONSULT or SEARCH directive\"\nProblem affects building in Guardian only.\n\nAPAR IC83299 - CPU Failure during mqget of persistent messages in global\nunit of work results in incorrectly deleted records in queue and\noverflow files\n\nIf a CPU fails where multiple applications are performing FIFO\nMQGETs from the same queue, and the following conditions are \ntrue:\n* The primary queue server is running in the failing CPU\n* Some (but not all) of the applications are running in the\nfailing CPU\n* None of the LQMAs are running in the failing CPU\n* The applications are using global units of work\n* Applications in the failing CPU have completed MQGET operations\nbut not committed the transactions\nThere is a failure window where an application not in the\nfailing CPU will remove an additional message record from the \nqueue file.\n\nAPAR IC83197 - Queue Server open handle management cannot handle backup\nrestart cases where handles from non-contiguous pages are \nsynced by the primary\n\nQueue servers with more than 3000 queue opens do not \ncorrectly handle a NonStop takeover. The queue manager becomes \nunresponsive and requires a restart to resolve the error \nsituation. When the queue server hangs, the backup queue server\nproduces a large number of FFST entries with the following \nprobe ids:\nQS165004 from qslSetHandle\nQS192007 from qslAddOpener\nQS190005 from qslHandleOpen\n\nAPAR IC83569 - Persistent Reference messages sent over a channel cause Commit \nControl Error\n\nWhen a persistent reference message is put to a queue, FFST's\nwith probe CS075003 are generated with the following error \ninformation\nMajor Errorcode :- rrcE_COMMIT_CONTROL_ERROR\nMinor Errorcode :- OK\nComment1 :- Error 2232 returned from lpiSPIHPNSSTxInfo\nIn addition, Sender channels will go into a retry state and\nqueue manager error logs will contain 'Commit Control' errors\n\nAPAR IC83699 - Cluster cache maintenance asynchronous time values result in\ncache content divergence\n\nRepository queue managers report FFST with probe RM527002\nfrom rrmHPNSSGetMetaPacket and Comment1 field \n\"Meta data mis-match Expected: metalen=4\". The problem \nresolved by this APAR is one of several possible causes of\nthese symptoms.\n\nAPAR IC83328 - Permanent dynamic queues are not deleted in some cases when\nMQCO_DELETE is used on MQCLOSE.\nPermanent dynamic queues are not deleted as expected after \ntermination of the last application that has the queue open.\n\nAPAR IC83228 - Repository manager/Channel server deadlock\nListener process hangs on queue manager startup for 5 \nminutes then generates an FFST with probe RM264002 \nfrom rfxConnectCache\nComment1 :- Gave up waiting for cache to be initialized\nComment2 :- Tried 300 times at 1 second intervals. \nThis problem also occurs sometimes when attempting\nto use runmqsc while the queue manager is starting\n\nAPAR IY90524 - segv in xcsloadfunction for channel exit\nWebSphere MQ channel process (amqrmppa) terminates with FFST\nshowing probe id XC130003 due to a SIGSEGV SIGNAL with\na function stack as follows:\nMQM Function Stack\nccxResponder\nrrxResponder\nrriAcceptSess\nrriInitExits\nxcsLoadFunction\n\nAPAR IC81311 - MQGET implementation masks reason codes in some cases\nAttempting to perform an MQGET after a Local Queue Manager\nAgent (LQMA) process fails or has been forcibly terminated\nresults in a MQRC_UNEXPECTED_ERROR (2195). This is incorrect.\nThe result should be MQRC_CONNECTON_BROKEN (2009)\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.9:\n\n4363 - MQA process opener field is sometimes corrupted in MQGET with \nset signal operations\n4388 - Guardian sample uses the wrong link directive\n4339 - Shared hconn rendered unsuable by changes in 5317\n4123 - FASTPATH bound connect processing does not correctly set reason\ncodes in some cases\n4039 - Backup queue server abend during commit after MQGET\n3826 - altmqfls --qsize does not report failure correctly\n4116 - enhance SDCP to find installed version of OSSLS2 (T8620)\n\nThe following problems were resolved in FixPack V5.3.1.8:\n\nAPAR IC54121 - Cluster channel in a retrying state will no longer start \nautomatically if the following commands are issued \nSTOP CHANNEL() MODE(QUIESCE) STATUS(INACTIVE).\nThe channel will fail to start once communication\nto the remote system is restored. A manual start and\nstop of the channel is required to restore normal\nchannel operation\n\nAPAR IC54459 - Channel stays in binding state for a long time when it contains\nan invalid conname value. During this period, all requests to \nthe channel are ignored.\n\nAPAR IC60204 - Comamnd server experiences a memory leak when namelist\ninquireies are performed with names values.\nThe leak is observed when a PCF MQCMD_INQUIRE_NAMELIST or\nMQCMD_INQUIRE_NAMELIST_NAMES is requested that has one or \nmore names attributes.\n\nAPAR IC70168 - High CPU usage from backup Queue Server performing browse\noperations on queues with high queue depth.\nWhen a queue has a very high queue depth (CURDEPTH) a browse\ncan cause the cpu usage of the backup Queue Server to increase\nto 100%. Backup queue server CPU usage becomes significant at\na queue depth of 15000, with CPU use reaching 100% at a queue\ndepth of approx. 38000 messages.\n\nAPAR IC70947 - qmproc.ini file validation does not detect incorrect CPU syntax.\nCPU lists in the qmproc.ini file that do not use comma\ncharacters to separate CPU numbers in the list are ignored, but\nthey are not reported as an error. This can lead to unexpected\nCPU assignements for WMQ processes.\n\nAPAR IC71839 - RESET QUEUE STATISTICS PCF returns incorrect values.\nWhen using WebSphere MQ v5.3 for HP NonStop Server PCF command\nReset Queue Statistics, intermittently some of the values\nassociated with a queue will not be returned correctly.\n* HighQDepth - The maximum number of messages on the queue\nsince the statistics were last reset.\n(parameter identifier: MQIA_HIGH_Q_DEPTH).\n* MsgEnqCount - The number of messages enqueued (the number of\nMQPUT calls to the queue), since the\nstatistics were last reset.\n(parameter identifier: MQIA_MSG_ENQ_COUNT).\n* MsgDeqCount - The number of messages dequeued (the number of\nMQGET calls to the queue), since the\nstatistics were last reset.\n(parameter identifier: MQIA_MSG_DEQ_COUNT).\n\nIncorrect values may also be returned incorrectly for the\ncommand Inquire Queue Status\n* LastGetTime - Time at which the last message was\ndestructively read from the queue\n(parameter identifier: MQCACF_LAST_GET_TIME).\n* LastPutTime - Time at which the last message was\nsuccessfully put to the queue\n(parameter identifier: MQCACF_LAST_PUT_TIME).\n\nAPAR IC71912 - MQMC Channel menu display shows incorrect channel status.\nIn some instances, the MQMC Channel Menu display will not\nshow a change in channel status, and attempts to refresh the\nscreen or recycle the MQS-MQMSVR Pathway server do not correct\nthe problem. RUNMQSC continues to show the correct status. \nThe MQMC channel monitor panel does show the running channels\ncorrectly.\n\nAPAR IC73800 - A queue manager with the MaxUnthreadeAgents parameter defined\nin the QMPROC.INI file with a value greater than 812\nreports unexpected process termination FDCs and or ERROR 22\nFDCs.\n\nAPAR IC74994 - Queue manager reports message sequence number error and\nproduces FDCs with probe CS094005, major error code\nrrcE_CREATE_SYNC_FAILED following a queue manager\nrestart. \n\nAPAR IC75298 - In some complex cluster configuations with large numbers of\ncluster members, large numbers of objects, or frequent changes\nto cluster objects, the repository managers in a queue\nmanager are unable to distribute a complete set of object \nmetadata information, resulting in repeated FDCs from \nrrmHPNSSGetMetaPacket, with probe RM527001, and cluster objects\nnot being visible in some CPUs in the queue manager reporting the\nproblems.\n\nThe fix for the problem adds a new configurable parameter to\nallow the repository metadata buffers to be increased to handle\nlarger configurations, and changes the reporting of the metadata\nerrors to include information on the amount of storage requested\nby the repository managers. The default size of the buffer is \n512K, this is sufficient for most configurations. If the buffer \nsize is insufficient, the queue manager reports FDCs from \nrrmHPNSSPutMetaPacket that indicate the present size of the\nbuffer and the size demanded.\n\nThe buffer size is configured using an environment variable, \nAMQ_CLUSTER_METABUFFER_KILOBYTES. To change the value, the \nenvironment variable should be specified in the \n\"RepositoryManager\" stanza of the qmproc.ini file of the queue\nmanager using the following syntax:\n\nEnv0n=AMQ_CLUSTER_METABUFFER_KILOBYTES=x\n\nWhere \"n\" is the number of the environment variable, and \"x\" is\nthe required new size of the buffer in kilobytes. In a default\nconfiguration, environment variables are not present in the \nRepositoryManager stanza, hence \"n\" will be 1. If the \nconfiguration has existing environment variables specified in\nthis stanza, the value of \"n\" selected should be the next \navailable value. \n\nAPAR IC75356 - Partial repository queue managers in complex configurations\nwhere applications connected to the partial repository queue\nmanager attempt to open large numbers of nonexistant objects\ncan suffer from a build up of subscription objects on the \nSYSTEM.CLUSTER.REPOSITORY.QUEUE such that the TMF lock limits\nfor the volume containing the queue file are breached when the\nqueue is reconciled. This produces 2024 errors during operations\non the SYSTEM.CLUSTER.REPOSITORY.QUEUE The following error \nmessage appears in the QMgr error logs.\nEXPLANATION: The attempt to get messages from queue\n'SYSTEM.CLUSTER.REPOSITORY.QUEUE' on queue manager 'xxx' failed \n\nAPAR IY57123 - Attempts to put to a clustered queue via a queue manager\nalias when the queue has been opened using BIND_AS_QDEF\nfail. Following this fix, queue name resolution functions\nas described in the Application Programming Guide.\n\nAPAR IY78473 - Cluster workload management is not invoked if a queue is\nresolved using clustered queue manager aliases where there\nare multiple instances of the alias in the cluster.\n\nAPAR IY86606 - Cluster subscriptions are created for non-clustered queues\nwhen MQOPEN is called with non-clustered ReplyToQ or \nReplyToQMgr. This can result in a build up of subscriptions\nin partial repositories in the cluster. The error was \nintroduced by IY8473.\n\nAPAR IZ14977 - Queue manager cluster membership missing when namelists are\nused to add and remove queue managers from clusters. This can\nresult in the queue manager not acting as a repository for\none or more clusters, or other queue managers in the cluster\nnot recognizing that a given queue manager is a repository\nfor the cluster.\n\nAPAR IZ20546 - The repository manager process (amqrrmfa) consumes high CPU\nresources on an hourly basis for several minutes, and\napplications are unable to issue messaging MQ API calls\nduring this period. The problem is observed only in \nconfigurations where clustered queue manager aliases are\nused and they resolve to more than 50 destinations.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.8:\n\n1228 - COBOL Binding library mqmcb does not contain VPROC information\n1378 - FDC's cut as a result of errors from PATHWAY SPI operations do\nnot report the associated Guardian error code \n1566 - WMQ service installation tool svcmqm does not correctly detect\nand report that files it is attempting to modify are in use,\nas is the case where WMQ applications are still runnning. \n1606 - Certain FDCs containing comment text have the comment text\ntruncated \n1710 - In some cases on heavily loaded systems, the EC re-allocates\nan MCA that has already been told to terminate. This results in\nFDC's cut with probe EC134000, from eclDeallocMCA.\n2534 - WMQ service installation tool svcmqm does not log some aspects\nof its progress, making diagnosing some installation problems\ndifficult\n2856 - WMQ service installation tool should not attempt SECURE\noperations in installations where SAFEGUARD is enabled\n2943 - crtmqm does not correctly handle validation of the command line\nif a specified CPU number is invalid\n3037 - If the var/mqm/errors directory contains non-mqm user files \nthe WMQ service data collection tool, sdcp, does not capture the \nMQM group FDC and ZZSA files.\n3128 - WMQ Service data collection tool, sdcp, does not capture VPROC \nof the AF_UNIX R2 socket process\n\n\nThe following changes were released in FixPack V5.3.1.7:\n\nAPAR IC65774 - Under given conditions, the response time measured for MQGET\noperations when using SSL activated channels with multi-threaded\nMCA agents are found to be longer than that measured when using \nSSL activated channels with unthreaded MCA agents. This problem \nis seen with both distributed and cluster queue managers. \nMoreover, this problem does not occur prior to WMQ V5.3.1.5 \nrelease. A DELAY was introduced as part of an APAR(IC57744) fix\nin WMQ V5.3.1.5 release for mutli-threaded SSL channels which\ncaused this difference in measured response time. The problem is\nnow rectified in this release. \n\nAPAR IC67032 - Improvement to LQMA FDC during MQCONN processing. At times, when\napplication dies during MQCONN processing, LQMA's generate FDCs\nfor this rather unusual event to let the user take any \ncorrective action and/or find the root cause. The problem can \noccur with a standard bound application in a very narrow timing\nwindow when the application connects with the LQMA agent but \ndies before the LQMA gets a chance to read the incoming message\nfrom the application. When LQMA detects this situation, it \ncleans up and generates an FDC. But unfortunately, the FDC does\nnot contain the application information. To let the user \nidentify the mis-behaving application and to possibly take\ncorrective action, LQMA FDC will be updated to include \napplication information. The updated FDC will contain the\nfollowing information :\n\nComment1 :- Application died during MQCONN Processing.\nComment2 :- Application: <Application PID> \n\nAPAR IC67057 - Unused LQMA agents(processes or threads) are found during MQCONN \nprocessing. During MQCONN processing if a standard bound \napplication fails to connect successfully to an allocated LQMA\nprocess or thread (depending on your configuration), then that\nLQMA process or thread remains in a hanging state for ever and\ndo not get re-used by Execution Controller for any further \nMQCONN processing. If an LQMA agent process ever goes into this \n\"limbo\" state, ecasvc utility shows \n\"Allocated, Pending Registration\" flag if it is unthreaded LQMA \nor a positive number against \"Conns Pending\" flag if it is a \nmulti threaded LQMA. If this problem occurrs multiple times, \nthen depending on the user configuration, it might lead to LQMA \nresource problems where Execution Controller will run out of \navailable LQMA agents to serve application MQCONN requests.\n\nAPAR IC65966 - runmqsc <queue manager name> causes FDC on a CPU due to missing\nOSS shared memory files (shm.x.x) for that CPU. Due to a yet\nunknown reason, the queue manager shared memory files for a\nparticular CPU on the system are deleted even when the queue\nmanager is in running state. This prevents any new MQ connection\nrequests from succeeding for the same queue manager on the\naffected CPU. This patch contains changes that will better\nprotect WMQ shared memory files and will prevent accidental\ndeletion of files by WMQ programs. The changes in this patch\nwill also report any such incidence by producing FDC files. The\nFDC file produced by this detection mechanism will contain the\nfollowing information :\nComment1 :- xcsIC_QUEUE_MANAGER_POOL being destroyed.\n\nAPAR IC67569 - When WMQ Queue Server detects an error due to invalid context\ndata during the completion of a TMF transaction started by the\nQueue Server for a PUT or GET no-syncpoint persistent message\noperation, it marks the message on the queue object as \naccessible. This causes the Queue Server to FDC with \n\"Record not found\" on any subsequent MQGET operation to retrieve\nthe same message. The particular message on the queue that has \nthis problem remains in this limbo state forever and can not be\nretrieved. However other messages on the same queue that do not\nhave this problem can be retrieved without any problem using \ntheir msgids. The Queue Server has been revised to correct this\nbehavior such that detection of inconsistent context data during\nMQPUT/MQGET is logged in the form of an FDC but is otherwise \ncommitted as a normal operation. This will resolve the problem\nof MQGET failing on the retrieval of the message.\n\nAPAR IC68569 - Channel server FDCs during starting/stopping of channels. The \nproblem occurrs due to a defect in the product where the channel\nserver erroneously closes its open to Queue Server but assumes \nthat its open to Queue Server is valid. The open handle \nto Queue Server after it is closed, gets reused by another open\nand hence any subsequent communication by Channel Server to \nQueue Server always fails. Typically, this problem is seen when\nthe Channel Server experiences transient socket errors with the \nchannel agent (MCA) and it wants to close the socket connection.\nAfter closing the socket connection, Channel server sends a \nmessage to Execute Controller process to de-allocate the MCA\nwith which it had socket error with. It is during this \ncommunication between the Channel Server and the Execution\nController when the Channel Server erroneously closes the open\nto the Queue Server.\n\nAPAR IC69572 - Channel server abends due to illegal address reference during\nadopt MCA processing. This problem happens if the Queue Manager\nhas enabled adopt MCA processing to a remote WMQ Queue Manager\nthat does not send a remote queue manager name during channel\ninitialization/negotiation. The remote Queue Manager field\nremains NULL and during the Adopt MCA processing logic,\nthe channel server incorrectly references the NULL pointer and\nabends. \n\nAPAR IC69932 - SNA WMQ listener fails to start the channel when HP SPR \nT9055H07^AGN is present on the NonStop system. HP, in its SPR\nSPR T9055H07^AGN, changed the behavior of sendmsg() API if '-1'\nis used as a file descriptor to the API. This caused \nincompatibility with WMQ SNA listener process. WMQ code has now \nbeen revised to work with the updated sendmsg() behavior. \n\nAPAR IC69996 - WMQ Queue Server generates FDC with reply error 74. When an\napplication with a waiting syncpoint MQGET suddenly dies \nbefore getting a reply, the Queue Server can cause FDC \nsometimes. This happens in a narrow timing window when a message\nbecomes available on the queue and the Queue Server starts \nprocessing the waiting MQGET request. If the application dies\nafter Queue Server starts processing the waiting MQGET request, \nthen Queue Server detects the inherited TMF transaction error \nand replies back with error 2072 (MQRC_SYNCPOINT_NOT_AVAILABLE).\nHowever in this case, Queue Server erroneously does not delete\nits internal waiter record for MQGET. When the timer pops for\nthe waiter record, Queue Server attempts to reply back with\nno message available but the call to Guardian REPLYX procedure\nfails with error 74 as the reply to the same request has already\nbeen made(with error MQRC_SYNCPOINT_NOT_AVAILABLE). This causes\nthe Queue Server to FDC.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.7:\n\n363 - WMQ Queue Server under certain conditions fails to handle non-persistent\nand persistent segmented messages at the same time.\n1317 - Support for parallel execution of multiple endmqm programs on the same\nQueue Manager. \n1404 - MQGET WAIT is not being rejected with error 2069 when there is an \nexisting MQGET set signal on the same queue handle. \n1434 - svcmqm utility fails when install files are open but does not tell the \nuser which files are open. \n1566 - svcmqm does not exit immediately when 'cp' command fails to copy \nbinaries during fixpack installation.\n1679 - WMQ Queue Server generates FDC while failing to open the message \noverflow file during retrieval of very large messages (equal to or \nlarger than 'Message Overflow Threshold' displayed with dspmqfls \nutility).\n1709 - instmqm changes related to the use of /opt directory for the creation of\nbackup archive file.\n1789 - Port of distributed APAR IY66826. Cluster sender channel does not start\nand Queue Manager cache status remain in STARTING state.\n1780 - Port of distributed APAR IY85542. RESET CLUSTER command does not remove \ndeleted repository entry.\n1993 - Enhancement to WMQ mqrc program to print messages related to errors \nbeing returned on NonStop platform.\n2018 - WMQ lqma agent process leaks catalog file open.\n2181 - svcmqm does not output the fixpack that is being installed.\n2282 - instmqm -b archives everything under /opt directory.\n2290 - Enhancement to Execution Controller process to aid development dubugging\nand troubleshooting.\n2534 - svcmqm has no log of its progress.\n2580 - Potential SEGV in internal function call during Pathway serverclass \nstarting.\n2632 - Incorrect message output in FDC generated by WMQ Queue Server during \nnsrReply function call.\n2633 - WMQ Command Server memory leak found in CLEAR QL command.\n2842 - WMQ Repman process priority was not set correctly when the \nqmproc.ini 'AllProcesses' stanza Priority attribute is configured. \n\nThe following serviceability fixes were made to the SDCP tool:\n\n1971 - sdcp data was not collected correctly when there is a default \nQueue Manager defined.\n2211 - sdcp testing of the permission of /tmp directory.\n2289 - sdcp logging of progress to a file to aid in sdcp problem diagnosis.\n2298 - sdcp performance improvement.\n2531 - sdcp logging of scheduled CPU information.\n2582 - sdcp capture of Pathway data for PATHMON, PATHWAY, TCP, PROGRAM\nand TERM attributes.\n\nThe following APAR fixes were released in V5.3.1.6:\n\nAPAR IC60204 - A Memory leak occurs with repeated DISPLAY NAMELIST command. The\nleak is observed only when the NAMELIST(s) has one or more NAMES\nvalues defined. The problem is observed from within the runmqsc\nDISPLAY NAMELIST command, or from the PCF/MQIA equivalent. Tools\nthat request NAMELIST data via the command server with PCF/MQIA\nrequests such as WMQ Explorer will cause the WMQ command server\nmemory to grow.\n\nAPAR IC61324 - An orphan MCA problem occurs when a connection request from WMQ\nLISTENER or CHANNEL SERVER process to an MCA process fails. WMQ\nExecution Controller (EC) process fails to recognize the\nsituation and does not re-use the MCA process for future agent\nallocation requests. Over a period of time, this problem can\ncause the queue manager to run out of MCA resources which may\nlead to a situation where no new channel can be started. The\nproblem is observed during heavy load conditions where the WMQ\nExecution Controller(EC) process hands over a selected MCA\nprocess to LISTENER/CHANNEL SERVER before the MCA process\nbecomes ready to accept connection requests.\n\nAPAR IC61551 - The use of cluster administrative command\nRESET CLUSTER ACTION(FORCEREMOVE), to forcibly remove a Queue\nManager out of the cluster can cause FDCs. The problem can cause\nmultiple FDCs and sometimes abend in WMQ REPMAN process in a\nslave role. Once the command has been issued and the error has\noccurred, the concerned Queue Manager must be restarted to\nrestore the clustering function to normal operation. The problem\noccurs because WMQ REPMAN process in a master role does not\ndistribute the RESET CLUSTER ACTION(FORCEREMOVE) command to the\nslave REPMAN processes correctly.\n\nAPAR IC61651 - When a NAMELIST object with one or more NAMES values is defined\nfor a Queue Manager and a dspmqfls command is issued to retrieve\nthe details of either all objects under the Queue Manager or\nthe specific NAMELIST object, FDCs are seen from the WMQ LQMA\nprocess. The problem exists for both unthreaded and\nmulti-threaded LQMA process. The problem occurs because WMQ LQMA\nprocess does not allocate sufficient memory for NAMES buffer\nduring dspmqfls processing.\n\nAPAR IC61660 - A PCF RESET QUEUE STATISTICS command causes the WMQ QUEUE SERVER\nprocess to FDC. The problem occurs during a timing window when\nthere is an outstanding unit of work on the queue and a\nRESET QUEUE STATISTICS command is processed and then the\noutstanding unit of work is backed out. RESET QUEUE STATISTICS\ncauses certain internal counters inside WMQ QUEUE SERVER to be\nreset to zero without taking into account the outstanding unit\nof work. If the outstanding work is later backed out for any\nreason, the already reset counters become negative which causes\nan internal consistency check to fail within the QUEUE SERVER\nprocess and the FDC is generated.\n\nAPAR IC61681 - WMQ QUEUE SERVER causes FDC during MQCLOSE processing on a\ncluster alias queue. The problem occurs during MQCLOSE\nprocessing of a cluster QALIAS object hosted by a different\nQUEUE SERVER than that hosts the target local queue. MQOPEN\nincorrectly failed to allocate an internal handle for the QALIAS\nobject if it was a cluster alias queue. This lead to the FDC\nduring MQCLOSE processing.\n\nAPAR IC61846 - When a START CHANNEL command is issued after WMQ trace is\nenabled, the SSL channel logs a Queue Manager error message and\nfails to start.\nThe problem exists only for a SSL channel, no such problem\nis found for regular (non-SSL) channel. The problem occurs\nbecause of an incorrect implementation of NULL terminated string\nto store SSL Cipher data.\n\nAPAR IC61920 - WMQ on NonStop reports an extra EMS message when the generation\nof an FFST is reported.\nThe intention behind the second EMS message was to report the\ncase when the open of the generated FFST file fails but the\ncheck to see the status of the opened FFST files was missing\nin the code.\n\nAPAR IC62341 - A Security error from the WMQ OAM server is not propagated\ncorrectly. It was reported as MQRC_UNKNOWN_OBJECT_NAME instead\nof MQRC_NOT_AUTHORIZED. When running the Java IVP (MQIVP) to NSK\nwith a non-mqm user specified as the MCAUSER in the SVRCONN\nchannel, and if the non-mqm group isn't given authorization,\nMQIVP fails to connect to the Queue Manager\nwith an authorization failure (MQRC_NOT_AUTHORIZED) but it is\nreported incorrectly as a MQRC_UNKNOWN_OBJECT_NAME error.\n\nAPAR IC62389 - A REFRESH CLUSTER command within a cluster with more than two\nrepositories causes the Repository Manager to fail. The problem\nis not common in normal cluster operation but is likely if\nextensive administrative changes are being made to the cluster\nthat includes a REFRESH CLUSTER command. Incorrect distribution\nof channel status information across multiple copies of the\nREPOSITORY MANAGER cache in different CPUs of the system lead to\nthe FDC.\n\nAPAR IC62391 - Sometimes cluster queues are not visible on CPUs hosting WMQ\nREPOSITORY MANAGER process in a slave role. This is a cluster\nqueue visibility problem across the CPUs. Any attempt to open\nthe cluster queue on CPUs that have the visibility problem\nresults in error MQRC_UNKNOWN_OBJECT_NAME or\nMQRC_CLUSTER_RESOLUTION_ERROR.\nThe problem does not occur on the CPU that hosts WMQ REPOSITORY\nMANAGER process in a master role.\n\nAPAR IC62449 - The WMQ QUEUE SERVER does not log storage related problems to\nthe Queue Manager log. Some of NSK storage related errors like\nerror 43 and error 45 are useful errors for which corrective\naction can be taken to restore normal operation.\nThe WMQ QUEUE SERVER now logs these errors to Queue Manager log.\n\nAPAR IC62480 - Port of IZ51686. Incorrect cache object linkage causes\nunexpected failures (AMQ9456) based on coincidental event\nsequences.\n\nAPAR IC62511 - Port of the following clustering-related APARs from other\nplatforms and versions:\nIZ14399 - Queue managers successfully rejoin a cluster when\nAPAR IY99051 is applied but have mismatching sequence\nnumbers for the cluster queue manager object and its\nassociated clusters.\nIZ21977 - MQRC_OBJECT_CHANGED(2041),\nAMQ9511 SYSTEM.CLUSTER.TRANSMIT.QUEUE,AMQ9448,\nRepository manager ends.\nIZ37511 - Generation of an FDC by the Repository Manager causes\nit to terminate.\nIZ14977 - Missing cluster information when Namelists are used\nto add and remove queue managers from multiple\nclusters at once.\nIZ36482 - Changes to CLUSRCVR shared using a Namelist not\npublished to all clusters.\nIZ10757 - Repository Manager process terminates with error\nRRCI_CLUS_NO_CLUSRCVR_DEFINED.\nIZ41187 - MQRC_CLUSTER_PUT_INHIBITED was returned when an out-\ndated object definition from the cluster repository\nwas referenced.\nIZ34125 - MQ fails to construct and send an availability message\nwhen REFRESH CLUSTER REPOS (YES) is issued on a queue\nmanager with more than 1 CLUSRCVR.\n96181 - Object changed problems with the Repository manager.\nIY97159 - Repository Manager process tries to access the cache\nwhile restoring the cache, resulting in a hang.\nIZ44552 - AMQ9430 message after REFRESH CLUSTER.\n135969 - Refresh bit not set when demoting QM to partial repository.\n\nAPAR IC62850 - The md.Priority of a message was not being set to the queue\nDEFPRTY when a no syncpoint MQPUT is performed using\nMQPRI_PRIORITY_AS_Q_DEF while there is a waiting MQGET.\nA syncpoint MQPUT with a waiting MQGET does not have this\nproblem.\n\nAPAR IC63081 - A WMQ application abends in the MQI library when attempting to\nenqueue messages to a Distribution LIST with one queue entry.\nAlso in certain circumstances, WMQ applications may receive\nincorrect status and reason code while using Distribution LISTS.\n\nAPAR IC63105 - A Memory leak occurs in the WMQ COMMAND SERVER with repeated\nDISPLAY QSTATUS command. The leak is observed only when\nTYPE HANDLE is used with the above command. The problem also\noccurs from within runmqsc DISPLAY QSTATUS command, or from the\nPCF/MQIA equivalent. Tools that request queue status data via\nWMQ COMMAND SERVER with PCF/MQIA requests such as WMQ Explorer\nwill cause the WMQ COMMAND SERVER memory to grow.\n\nAPAR IC63271 - When an MQ application delays in replying to the HP system OPEN\nmessage from the WMQ QUEUE SERVER and an MQ message arrives on\nqueue during this period, the MQ message did not get delivered\neven after the reply to the HP system OPEN message is made.\n\nAPAR IC63757 - In a standard bound application, a memory leak occurs in WMQ\nLQMA process during MQCONN/MQDISC processing. The problem occurs\nwith both unthreaded and multi-threaded LQMA process. If the\nLQMA agents are configured to have high use count\n(MaxAgentUse for unthreaded LQMA and MaxThreadedAgentUse for\nmulti-threaded LQMA) and WMQ Execution Controller process\nre-uses the same LQMA process to satisfy a application MQCONN\nrequest, then the heap memory of LQMA process grows even if\napplication calls MQDISC to disconnect from the\nQueue Manager.\n\nAPAR IC64297 - WMQ Queue Manager becomes non-responsive because the\nWMQ QUEUE SERVER does not clean up the internal queue manager\nobject opens. The QUEUE SERVER internal links for\nMQOPEN of the Queue Manager object were not\nbeing released during the MQCLOSE processing. This causes a\nbuildup of QUEUE SERVER memory as the application repeated\nMQOPEN of the queue manager object repeatedly. When either\na MQDISC occurred or the application process ended,\nthe QUEUE SERVER cleans up its internal lists for the process.\nThis resulted in a perceived QUEUE SERVER loop and\nnon-responsive WMQ as there were\nover 246,000 opens found of the Queue Manager object with a\nhigh mark of 548,000 within the QUEUE SERVER when a dump of the\nQueue Server was analyzed.\nMQOPEN of other MQ objects (qlocal, qalias, qremote etc.) do not\nhave this issue.\n\nAPAR IC64373 - The COBOL copybook now includes missing definitions for MQGET\nSET SIGNAL processing.\n\nAPAR IC64435 - An incorrect persistence attribute was being set for a\nnon-persistent message on XMIT queue. When MQPUT of a\nnon-persistent message is done using MQPER_PERSISTENCE_AS_Q_DEF\nattribute to a remote queue while the channel is idle, the MD\nMD data in transmit queue header contained\nMQPER_PERSISTENCE_AS_Q_DEF value of (2).\n\nAPAR IC64630 - It takes longer for unthreaded SSL sender channel to end when\ncommunication to the remote Queue Manager is lost. The problem\noccurs because the unthreaded MCA process running the SSL channel\nfails to timeout correctly causing the channel to end differently\nthan non-SSL channels. The problem is observed only with SSL\nchannels and no such problem is visible with regular SSL \nchannels. \n\nThe following fixes discovered during IBM's development and testing work are\nalso released with V5.3.1.6:\n\n1096 - An MQGET BROWSE operation can return prematurely with no message\navailable as well as can cause a waited GET to hang indefinitely.\n1513 - amqrrmit erroneously reports multiple master REPMAN processes.\n1587 - Enhancements to Execution Controller log messages pertaining to\nThreshold and MaxAgent capacity situations. For unthreaded agents,\nthe \"max unthreaded agents reached\" message will now be logged when the\nMaxUnthreadedAgent is allocated to perform work. In previous releases,\nthe message was logged when the MaxUnthreadedAgent was added to the idle\npool, which actually left one agent still available for use.\nFor threaded agents, messages have been enhanced to display separate\nThreshold/Maximum messages for agents and threads. In previous releases,\n\"further connections refused\" was displayed when the MaxThreadedAgent\nwas started, which actually left MaximumThreads connections still\navailable for use. In this release \"further connections refused\" will be\ndisplayed when the MaximumThread is allocated for use.\nAlso in this release, messages will be logged when the number of agents\nor threads, after having exceeded the threshold or reached maximum,\nfall below the Maximum or threshold limit.\n1669 - ZCG_FFST does not report the error code for a TMF error.\n1675 - The Execution Controller now provides an API to mark MCAs that are no\nlonger used.\n1670 - Correction to missing component data in a FDC generated by the\nQueue Manager server(MQS-QMGRSVR00) process(amqqmsvr).\n1678 - Queue server abends due to uninitialized FFST inserts.\n1706 - dmpmqaut -m <qmgr> sometimes only reports the first QALIAS object and\nFDCs in kpiEnumerateObjectAuthority.\n1710 - The Execution Controller sometimes allocates an MCA that it has\npreviously asked to end\n1712 - Cluster queue manager STATUS and queue visibility problems in slave\nREPMAN.\n1734 - Fixes/Updates to MQ tracing mechanism.\n1735 - Subscription id distribution.\n1751 - Fixes/Updates to MQ tracing mechanism.\n1807 - Changes to improve service and debug capability of Execution Controller\nstarted processes.\n1873 - \"*\" subscriptions are generated incorrectly causing them to be ignored.\n1989 - Fix for channel server hanging problem while opening REPMAN process.\n2003 - LQMA now FDCs when a invalid message is received.\n\nThe following serviceability fixes were made to the SDCP tool:\n\n1659 - sdcp is not capturing the PSTATE of backup processes.\n1676 - sdcp takes too long.\n1690 - sdcp MQ utilities are not using the correct Queue Manager name if\nthe name is mangled because of non-alphabetic characters.\n1702 - sdcp doesn't collect all relevant Saveabend files.\n1705 - sdcp workaround to avoid APAR IC61651.\n1971 - sdcp now gives correct output for default Queue Manager.\n\nThe following APAR fixes were released in V5.3.1.5:\n\nAPAR IC55607 - FDC files can fail to be written, or written to the wrong file\nFDCs can be suppressed or overwritten when application processes\nraise FDCs under User IDs that are not members of the MQM group.\nIn addition, because FDC files are named with the CPU and PIN of\nthe generating process, and PIN is reused frequently on\nHP NonStop Server, FDCs from different processes can be appended\nto the same file.\n\nThe format of the file name for FDCs is:\nAMQcccpppp.s.FDC\n\nwhere ccc is the CPU number\npppp is the PIN\ns is the sequence number\n\nIn V5.3.1.4 and earlier releases, the sequence number was\nalways set to 0. This fix introduces the use of the sequence\nnumber field to ensure that FDCs from different processes are\nalways written to different files, and that FDCs can always be\nwritten. FDC files are created with file\npermissions \"rw-r----\" to prevent unauthorized access to the\nFDC data.\n\nAPAR IC57435 - Attempts to end a queue manager with either -t or -p following\na cpu failure in some cases did not work as a result of\ndamage to the WMQ OSS shared memory files. The shared memory\nmanagement code was revised to tolerate OSS shmem/shm files\ncontaining invalid data. Invalid data in these files is now\nignored and memory segment creation will continue normally.\n\nAPAR IC58165 - Triggered channels sometimes do not trigger when they should\nSome attributes of a local queue that determine if trigger\nmessages get generated are not kept up to date for long-running\napplications. The most critical attribute is the GET attribute\nthat controls whether MQGET operations are enabled for a queue\nor not. If the application opened the triggered queue while\nthe queue was GET(DISABLED), and the queue is subsequently\nmodified to be GET(ENABLED), triggering will not occur when it\nshould.\n\nAPAR IC58377 - Trace data is not written when PIDs are reused for processes\nrunning under different User IDs.\nTrace files are named according to the CPU and PIN of the process\nthat is being traced. On HP NonStop Server, since PINs are\nrapidly reused, it is likely that a process attempting to write\ntrace data will encounter an existing file written with the same\nCPU and PIN. The traced process will be unable to write data if\nthe original file was written (and therefore owned) by a\ndifferent User ID.\n\nThis fix introduces a sequence number into the trace file names\nto prevent trace file name collisions.\n\nThe format of trace file names will change from:\n\nAMQccppppp.TRC to AMQccppppp.s.TRC\n\nwhere s is a sequence number that will usually be 0.\nTrace files are now created with file permissions \"rw-r----\"\nto prevent unauthorized access to the trace data.\n\nAPAR IC58717 - The Queue Server backup process generates FDCs showing ProbeId\nQS123006 from qslHandleChpPBC when attempting to locate a browse\ncursor message, with the comment text of\n\"Error locating Last Message in Browse Cursor checkpoint in\nBackup\" or \"Error locating Last Logical Message in Browse Cursor\ncheckpoint in Backup\". The problem appears only when running a\nnumber of parallel browse / get applications for the same queue\nobject.\n\nAPAR IC58792 - strmqm fails to delete orphaned temporary dynamic queues if the\nassociated touch file is missing. This results in these queues\nremaining in the object catalog indefinitely, and FDC files\nbeing generated each time the queue manager is started,\nreflecting the fact that the queue could not be deleted. The\nhousekeeping function was modified to always silently remove\ntemporary dynamic queue objects from the catalog, whether or\nnot they are damaged. FDC files are no longer generated.\n\nAPAR IC58859 - wmqtrig script does not pass TMC with ENVRDATA correctly.\nIf ENVRDATA is part of the PROCESS definiton used by\nrunmqtrm to trigger applications the TMC is not delivered to\nthe application correctly. The problem does not occur with\nblank ENVRDATA. Additionally, ENVRDATA or USERDATA attributes\nthat contain volume names ($DATA for example) are not processed\ncorrectly by the wmqtrig script.\n\nAPAR IC58891 - Sender channels that were running in a CPU that failed are not\nrestarted in some circumstances. Sender channels that are not\nrestarted report \"AMQ9604: Channel <...> terminated\nunexpectedly\" in the queue manager error log, and the channel\nserver create FDCs with ProbeID RM487001, Component\n\"rriChannelTerminate\".\n\nAPAR IC58976 - A server channel without a specified CONNAME enters a STOPPED\nstate when the MCA process running the channel is forcibly\nstopped or ends following a CPU failure. The channel state\nshould be set to INACTIVE following this type of event. To\nrecover the situation the channel has to be manually restarted\nor stopped using MODE(INACTIVE).\n\nAPAR IC59024 - The copyright data in the COBOL COPYBOOK CMQGMOL file\nis incorrect.\n\nAPAR IC59126 - Context data is missing in COA message.\nWhen an MQPUT application sends a message with COA report\noption, the generated replied COA message does not contain\ncontext data eg. PutDate, PutTime, etc.\n\nAPAR IC59364 - Queue Server primary incorrectly commits an WMQ message in\ncertain cases where the backup process has failed to process\nan internal checkpoint message. This causes an inconsistency\nbetween the primary and backup processes when an MQGET is\nattempted on this message, resulting in FDCs with the comment\ntext \"Invalid Message Header context in Backup for Get\" from\nComponent \"qslHandleGetCkp\". The queue object is no longer\naccessible via MQGETs, but can be recovered by stopping the\nbackup process.\n\nAPAR IC59388 - V5.3 OAM Implementation contains migration logic which may be\ntriggered erroneously in some circumtances, removing authority\nrecords from the SYSTEM.AUTH.DATA.QUEUE. This change removes the\nmigration logic, since there are no previous versions of the\nOAM which require migration.\n\nAPAR IC59395 - Threaded LQMA actual usage is one larger than the configured\nmaximum use count in the qmproc.ini file. Unthreaded LQMAs\nand MCAs (both threaded and unthreaded) do not suffer from this\nproblem.\n\nAPAR IC59428 - In some circumstances where connecting applications terminate\nunexpectedly during the MQCONN processing, either by external\nforcible termination, or as a consequence of other failures that\n\nresult in termination, the resulting error can cause the LQMA\nprocess handling the application to terminate. This will\ncause collateral disconnections of all other applications using\nthe same LQMA, with the application experiencing either a 2009\n(connection broken) or 2295 (unexpected) error. The problem\nwindow occurs only during one section of the connect protocol\nand has been observed only on very busy systems with repeated\nmultiple forced terminations of applications.\n\nAPAR IC59742 - qmproc.ini file will fail validation if configured with both\nMinIdleAgents=0 and MaxIdleAgents=0.\n\nAPAR IC59743 - Queue Manager server expiration report generation is not fully\nconfigurable. The frequency with which the queue manager server\ngenerates expiration reports is configurable but the number of\nreports generated is not. This change introduces a new\nenvironment variable (MQQMSMAXMSGSEXPIRE), to allow\nconfiguration of the number of expiration reports generated\nat any one time. The parameter can be added to the WMQ\nPathway MQS-QMGRSVR00 serverclass:\nALTER MQS-QMGRSVR00, ENV MQQMSMAXMSGSEXPIRE=<1-99999>\nIf this value is not specified in the queue manager\nserverclass configuration, the value defaults to 100.\n\nAPAR IC59802 - Memory leak occurs with repeated DIS CHSTATUS SAVED command.\nA memory leak exists in the Channel Saved Status query. This\nleak is observed within either the runqmsc DISPLAY CHSTATUS\n\nSAVED command, or the PCF/MQIA equivalent. Tools that request\nsaved channel status data via the Command Server with PCF / MQIA\nrequests such as WMQ Explorer will cause the Command Server\nmemory to grow.\n\nAPAR IC60114 - WMQ processes or user application processes generate FDCs\nreferring to \"shmget\" following forcible termination of the\nprocess or failure of the CPU running it. This is a result of\nthe Guardian C-files (Cnxxxxxx) for a CPU becoming corrupt\nduring an update operation, rendering the file and associated\nshared memory segment unusable. C-file update operations are\nnow performed atomically to prevent this problem.\n\nAPAR IC60135 - Improve servicability of the \"endmqm -i\" command to prevent the\ncommand from waiting indefinitely for the queue manager to end.\nFollowing this change after a specified number of seconds, the\ncommand will complete with the message \"Queue Manager Running\"\nand return to the command line with exit status 5.\n\nAPAR IC60175 - Description is not available (security/integrity exposure)\n\nAPAR IC60361 - Memory leak occurs in SVRCONN channel MCAs which repeatedly open\nlocal queue objects.\n\nAPAR IC60455 - WMQ Broker restart may not work correctly.\nIf the WMQ Broker is restarted using strmqbrk/endmqbrk,\nsubsequent attempts to restart the broker may fail, and 2033\nerrors my arise when running the test broker samples and\nrecycling the broker processes.\n\nAPAR IC60119 - System Administration manual incorrectly states the default\nvalue of the TCP/IP Keepalive is \"ON\"\n\nThe following fixes discovered during IBM's development and testing work were\nreleased with V5.3.1.5:\n\n1403 Erroneous SVRCONN channel ended message.\nSVRConn channels should not generate \"Channel Ended\" messages in\nthe error log, but in some circumstances, threaded svrconn\nchannels do generate these messages.\n1451 Internal changes relating to trace and FDC files sequence numbers\n1453 Problem with MQCONN after restart of broker\n1516 strmqm fails with invalid ExecutablePath attribute (qmproc.ini)\n1560 Port of V51 MQSeries for Compaq NonStop Kernel APAR IC57981.\nBackup Queue Server runs out of memory processing non-persistent\nmessages in 27K range. \n1564 runmqlsr abends in nssclose after a previous 'socket' calls fails\n1570 Added Agent type to EC logged threshold and max agent messages.\n1576 Change ECA interface to V4\n1577 Queue Server message expiration deletion phase log message\n1583 Blank channel status entries can get created triggering\nchannels when AdoptMCA is enabled.\nUnder certain timing situations, when triggered channels are\nused and AdoptMCA is enabled for the queue manager, blank\nchannel status entries can be created with the JOBNAME\nreferencing the Channel Initiator (runmqchi), for example:\nAMQ8417: Display Channel Status details.\nCHANNEL() XMITQ()\nCONNAME() CURRENT\nCHLTYPE() STATUS(BINDING)\nMSGS() BATCHES()\nJOBNAME(5,333 $MQCHI OSS(318898190)) RQMNAME()\nThis problem does not cause any immediate functional problem,\nhowever the blank entries consume channel status table entries\nand therefore could prevent legitimate channel starts in the\nevent that the status table becomes full.\n1594 C++ unthreaded libraries use threaded semaphores\n1596 Improved cs error reporting\n1597 EC started processes sometimes not started in intended CPU\n1598 NSS Incorrect component identifiers used in some parts of zig\n1608 Queue status errors on failure of a no syncpoint persist message\nput or get\n1601 Tracing details to the EC to augment the Entry and Exit trace\ncalls\n1611 LQMA Queue manager attribute corruption\n1613 Enhanced LEC Failure Handling\n1615 The EC may allow the os to choose in which cpu a MCA will start\n1616 Channel server comp traps have potential performance impact.\n1621 MQCONN does not report valid reason code when agent pool is full\n1622 After a channel is started dis chs displays \"binding\" in some\ncircumstances when it should display \"running\"\n1623 Incorrect message when MCA allocation fails\n1626 Addition of Service information collection tool (SDCP)\n\nNew platform support was released in V5.3.1.4:\n\nFixpack V5.3.1.4 introduced support for the HP Integrity NonStop BladeSystem\nplatform, NB50000c. Use the H-Series (Integrity) package of WebSphere MQ\nfor execution on the BladeSystem. Please refer to the Hardware and Software\nRequirements section for details about the levels of the J-Series software\nrequired.\n\nThe following APAR fixes were released in V5.3.1.4:\n\nAPAR IC57020 - runmqtrm does not function correctly and produces errors in some\ncases.\nWhen a triggered application is a guardian script file\n(ie filecode 101). runmqtrm produces an \"illegal program\nfile format\" error. Triggering also does not work correctly\nfor COBOL or TAL applications.\n\nAPAR IC57231 - The execution controller starts repository processes at the\nsame priority as itself in some cases, and does not take\naccount of the values set in the qmproc.ini file.\n\nAPAR IC57420 - Repository manager restart following failure causes cluster\ncache corruption in some circumstances.\nIf a repository manager abends while a queue manager is under a\nheavy load of cluster-intensive operations, in some\ncircumstances the repository manager that is restarted can\ndamage the cluster cache in the CPU in which it\nis running. This can prevent further cluster operations in that\nCPU and cause WMQ processes to loop indefinitely. This release\nchanges the repository startup to prevent this from happening.\n\nAPAR IC57432 - OSS applications that attempt to perform MQI operations from\nforked processes encounter errors.\nIf an oss WMQ application forks a child process, that child\nprocess will encounter errors if it attempts to perform MQI\noperations. Some operations may succeed, but will result\nin the generation of FDC files.\n\nAPAR IC57488 - MQMC channel menu display display error after channel is\ndeleted.\nIf a channel is deleted while the channel menu in MQMC\nis displayed, refreshing the channel menu produces the\nerror: \"Unknown error received from server. Error number\nreturned is 1\" and will not correctly display the channel\nlist without restarting MQMC.\n\nAPAR IC57501 - unthreaded sender channels to remote destinations with\nsignificant network latency may fail to start with timeout\nerrors.\n\nAPAR IC57524 - Applications launched locally from remote nodes cannot access\nsome of the queue manager shared memory files due to default\nsecurity on those files.\n\nAPAR IC57627 - Handling of TMF outages to improve operational predictability.\nIf TMF disables the ability to begin new transactions\n(BEGINTRANS DISABLED), WMQ does not always react in a\npredictable or easily diagnosed manner, and applications can\nsuffer a variety of different symptoms. If TMF is stopped\nabruptly (STOP TMF, ABRUPT) queue managers can become unstable\nand require significant manual intervention to stop and restart.\nRefer to item 18 in \"Known Limitations, Problems and\nWorkarounds\" later in this README for more information.\n\nAPAR IC57712 - altmqfls --qsize with more than 100 messages on queue fails.\nWhen a altmqfls --qsize is performed with more the 100 MQ\nmessages in the queue the processing fails.\n\nAPAR IC57719 - FDCs from MQOPEN when an error exists in alias queue manager\nresolution path. If a queue resolution path includes a queue\nmanager alias, and the target of the alias does not exist,\nthis will produce an FDC, rather than just failing the\nMQOPEN as would be expected.\n\nAPAR IC57744 - CPU goes busy when stopping a threaded SSL receiver channel\nusing MODE(TERMINATE).\nIf a stop channel mode(terminate) is used to stop an SSL\nreceiver channel that is running in a threaded MCA, the CPU\nwhere the MCA is running in begin using large amounts of CPU\ntime (95% range). This is due to a problem in the threads\nlibrary.\n\nAPAR IC57876 - Very infrequently, messages put via threaded LQMAs can in some\ncircumstances contain erroneous CCSID information. This has\nbeen observed to cause conversion errors if the message is\ndestined for a channel that has the CONVERT(YES) set.\nUnthreaded LQMAs do not suffer from this problem.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.4:\n\n993 - Due to the way that default file security was used, file security for\ncertain shared memory files used by the queue manager (SZ***) may\n\ninadvertently change in a way that prevents applications not in\nthe mqm group from issuing MQCONN. File permissions were rationalised\nin this release to reflect those used for other shared memory files.\n1458 - Resolve Channel command generates FFSTs.\nWhen resolving In-Doubt channels, FFSTs were generated by the Channel\nServer and the MCA. Although the channels were successfully resolved,\nthe In-Doubt status in a DIS CHS query was not correctly updated.\nWhen resolving In-Doubt channels using the COMMIT option the following\nerror message was displayed \"AMQ8101: WebSphere MQ error (7E0) has\noccurred.\"\n1493 - The validation of the qmproc.ini file does not report the error case\nwhere multiple ChannelsNameMatch entries are specified ChlRule1.\n1498 - Instmqm does not support installation of the product on\nIntegrity NonStop BladeSystem platforms.\n1507 - Some Execution controller messages were missing \"Action\" descriptions\nwhen reported in the error log.\n1517 - In the qmproc.ini file, the AppRule4-SubvolMatch argument was not\nworking\n1522 - Communications Component Function ids and probes are incorrect. This\nresulted in misleading or missing information in trace files generated\nfor support purposes.\n1546 - MQBACK operation incorrectly reports error during broker operations\n1549 - Channel Server doesn't shutdown after takeover.\nIf the Primary Channel Server process is prematurely ended, for\nexample by a CPU crash, the Backup Channel Server process becomes the\nnew Primary process. Subsequent attempts to use endmqm will hang\nbecause the new Primary Channel Server process will not end.\n\n\nThe following documentation APARs are addressed by the V5.3.1.4 readme:\n\nAPAR IC55404 - REFRESH QMGR PCF command is not documented in the Programmable\n\ncommand formats manual.\n\nAlso - please check the \"Limitations\" and \"Known Problems and Workarounds\"\nsections later on in this readme for updates.\n\nThe following APAR fixes were released in V5.3.1.3:\n\nAPAR IC54305 - The HP TNS (non-native) C compiler generates Warning 86 when\ncompiling MQI applications\nAPAR IC55501 - The altmqfls command does not return the correct completion\nstatus; it always returns success\nAPAR IC55719 - Non-native MQINQ binding does not deal with some null pointer\nparameters correctly\nAPAR IC55977 - Channel retry does not obey SHORTTMR interval accurately enough\nAPAR IC55990 - Trigger data changes not being acted upon if they were made\nwhile the queue was open, leading to incorrect triggering\nbehavior\nAPAR IC56277 - Command Server can loop with INQUIRE QS command with a single\nparameter\nAPAR IC56278 - A remote RUNMQSC DIS QS command always times out\nAPAR IC56309 - MCAs do not disconnect from some shared memory when ending,\nwhich causes a slow memory leak, and under some conditions an\nabend\nAPAR IC56458 - Channel Server loops after installing V5.3.1.2 due to corrupt\ndata on SYSTEM.CHANNEL.SYNCQ\nAPAR IC56493 - Cannot use \"qualified\" hometerm device names with V5.3.1.2\nAPAR IC56503 - Channel Server and MCA can deadlock after repeated STOP CHANNEL\nMODE(FORCE) or MODE(TERMINATE) commands\nAPAR IC56536 - Unthreaded responder channels don't de-register from the EC when\nan error occurs during or before channel negotiation. For\nexample, bad initial data will cause this. Unthreaded MCAs\nbuild up and eventually reach the maximum which prevents further\nchannel starts\nAPAR IC56681 - C++ unthreaded Tandem-Float SRLs have undefined references\n\nAPAR IC56834 - endmqm -p can sometimes leave MCA processes running\n\nThe following fixes discovered during IBM's development and testing work were\nreleased with V5.3.1.3:\n\n663 - Guardian command line utility return status is not the same as the OSS\nutilities return status\n1402 - Add additional tracing when testing for inconsistencies in processing\na channel start in the Channel Server\n1416 - Ensure that the Channel Server can support the maximum BATCHSZ of 2000\n1446 - Pub / Sub command line utilities do not behave well if no broker has run\nsince the queue manager was created\n1470 - EC abends attempting to start a non-executable REPMAN\n1474 - Pub / Sub broker process handling corrections for the EC\n1476 - The EC checkpoints the number of threads running in agents incorrectly\n1477 - Enhancement to ecasvc utility: the creation date/time of LQMAs, MCAs,\nand REPMEN are now displayed\n1487 - Enhancement to ecasvc utility: changed the display of Agent attributes\nto use the \"real\" qmproc.ini attribute names. Added a new option,\nthat displays information about all connected applications\n1494 - A small memory leak occurs for the delete channel operation\n1508 - Multiple qmproc.ini environment variables don't get propagated to\nagents or repmen\n1509 - The EC failed to stop an MCA that was hung when a preemptive shutdown\nwas initiated\n\nThe following documentation APARs were addressed by the V5.3.1.3 readme:\n\nAPAR IC55380 - Transport provider supplied during install is not propagated to\nPathway configuration by crtmqm. Please see the documentation\nupdate below made for Page 17 of the \"Quick Beginnings\" book.\n\nThe following APAR fixes were released in V5.3.1.2:\n\nAPAR IC52123 - LQMA abend handling rollback of a TMF transaction in MQSET\nAPAR IC52963 - The PATHMON process is not using configured home terminal for\nMQV5.3 on HP Nonstop Server\nAPAR IC53205 - FDC from Pathway runmqlsr when STOP MQS-TCPLIS00\nAPAR IC53891 - There is a memory leak in the Channel Server when processing\nthe DIS CHS command\nAPAR IC53996 - C++ PIC Guardian DLLs missing.\nAPAR IC54027 - MQRC_CONTEXT_HANDLE_ERROR RC2097 when loading messages using\nMO71\nAPAR IC54133 - Multi-threaded LQMA should not try to execute Unthreaded\nfunctions if qmproc.ini LQMA stanza sets MaximumThreads=1\nAPAR IC54195 - runmqtrm data for Trigger of Guardian application not\nreinitialized\nAPAR IC54266 - MinThreadedAgents greater than PreferedThreadedAgents causes\nMQRC 2009 error\nAPAR IC54488 - MCA's abend after MQCONN/MQDISC 64 times.\nAPAR IC54512 - OSS runmqsc loops if Guardian runmqsc is TACL stopped\nAPAR IC54517 - upgmqm does not handle CPUs attribute for PROCESS specifiction\nin a SERVERCLASS\nAPAR IC54583 - SSL channel agent can loop if an SSL write results in a socket\nI/O error\nAPAR IC54594 - EC abends with non-MQM user running application from non-MQM\ndirectory\nAPAR IC54657 - Channel stuck in BINDING state following failed channel start\ndue to unsupported CCSID.\nAPAR IC54666 - Queue Server deadlock in presence of system aborted\ntransactions.\nAPAR IC54798 - upgmqm fails with Pathway error on 3 or more status servers that\nrequire migration from V5.1 queue manager.\nAPAR IC54841 - When a temporary dynamic queue is open during \"endmqm -i\"\nprocessing an FDC is generated\nAPAR IC55008 - Added processing that will cause Channel Sync data to be\nHardened at Batch End\nAPAR IC55073 - altmqfls --qsoptions NONE is not working as specified\nAPAR IC55176 - Abend in MQCONN from app that is not authorized to connect (2035)\nor with invalid Guardian Subvolume file permissions\nAPAR IC55500 - QS Deadlock with Subtype 30 application using MQGMO_SET_SIGNAL\nAPAR IC55726 - Channel stuck in BINDING state following failed channel start\n\ndue to older FAP level\nAPAR IC55865 - Abend on file-system error writing to EMS collector\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.2:\n\n1122 - Invalid/incomplete FFST generated during MQCONN when Guardian\nsubvolume cannot be written to.\n1392 - Add support for Danish CCSID 65024\n1397 - Command Server fails to start and EC reports failure to initialize\na CPU - error 12 purging shared memory files.\n1409 - Guardian WMQ command fails when invoked using Guardian system() API\n1413 - MCA looping after SSL socket operation fails\n1419 - altmqfls --volume attempted using a open object causes FDCs\n1439 - On non-retryable channel, runmqsc abends while executing RESOLVE CHANNEL\ncommand\n\nThe following documentation APARs were addressed by V5.3.1.2:\n\nAPAR IC53996 - C++ PIC Guardian DLLs missing.\n\noriginally released in V5.3.1.1 Patch 1:\nAPAR IC53891 - There is a memory leak in the Channel Server when\nprocessing the DIS CHS command\n\noriginally released in V5.3.1.1 Patch 2:\nAPAR IC54583 - SSL channel agent loops\n\noriginally released in V5.3.1.1 Patch 3:\nAPAR IC54666 - Queue Server deadlock in presence of system aborted\ntransactions.\n\noriginally released in V5.3.1.1 Patch 4:\nAPAR IC54512 - OSS runmqsc loops if Guardian runmqsc is TACL stopped\n\nThe following APAR fixes were released in V5.3.1.1:\n\nAPAR IC52737 - When in SSL server mode and the sender is on zOS a list of CAs\nthat the server will accept must be sent to the zOS sender\nduring the SSL handshake\n\nAPAR IC52789 - upgmqm support for upgrading V5.1 queue managers that do not use\nOAM (created with MQSNOAUT defined). Also add diagnostics as to\nreasons and preventative actions for failure to create a PATHMON\nprocess\n\nAPAR IC52919 - Problems in synchronization of starting a queue manager when\nmultiple Queue Servers are defined\n\nAPAR IC52942 - Trigger Monitor holds Dead Letter Queue open all the time\nAPAR IC53240 - Correct sample API exit to build for PIC and SRL/Static\nAPAR IC53243 - Start of many applications simultaneously causes LQMA FDC\nAPAR IC53248 - Kernel not informing repository cache manager of updates to\ncluster object attributes\n\nAPAR IC53250 - Flood of FDCs when trace is enabled before qmgr start\nAPAR IC53254 - Browse cursor mis-management left locked message on queue.\nIn addition, browse cursor management was not correct in the\nevent that a syncpoint MQGET rolls back\n\nAPAR IC53288 - Cluster Sender channel is not ending until the HBINT expired\nAPAR IC53383 - upgmqm was losing the MCAUSER attribute on channels\nAPAR IC53492 - TNS applications fail in MQPUT with more than 106920 bytes of\ndata\n\nAPAR IC53524 - SVRCONN channels are not ending after STOP CHANNEL if client\napplication is in a waited MQGET\n\nAPAR IC53552 - OAM uses getgrent() unnecessarily, causing slow queue manager\nstartup\n\nAPAR IC53652 - Guardian administration commands don't work with VHS or other\nprocesses as standard input or output streams\n\nAPAR IC53728 - ECONNRESET error when Primary TCP/IP process switched should\nnot cause listener to end\n\nAPAR IC53835 - Assert in xtrInitialize trying to access trace shared memory\n\nThe following documentation APARs were addressed by V5.3.1.1:\n\nAPAR IC51425 - Improve documentation of crtmqm options\nAPAR IC52602 - Document ClientIdle option\nAPAR IC52886 - Document RDF setup ALLSYMLINKS\nAPAR IC53341 - Document OpenTMF RMOPENPERCPU / BRANCHESPERRM calculation\n\nThe following fixes discovered during IBM's development and testing\nwork were also released with V5.3.1.1:\n\n634 - Correct function of altmqfls option to reset measure counter\n822 - Message segmentation with attempted rollback operation failed\n862 - PCF command for Start Listener fails\n903 - Channel status update problems during shutdown after Repman has ended\n922 - Channel status incorrect when attempting to start a channel and the\nprocess management rules prevent the MCA thread or process from starting\n929 - Incorrect response records when putting to distribution list\n1012 - Two of the sample cobol programs give compilation error\n1059 - C-language samples use _TANDEM_SOURCE rather than __TANDEM\n1064 - errors checkpointing large syncpoint MQPUT and MQGET operations\nwhen transactions abort\n1069 - Not able to delete CLNTCONN channels\n1108 - Error logged when MCA exits because maximum reuse count is reached\n1152 - strmqm -c option gives unexpected error if executed after strmqm\n1176 - Sample cluster workload exit not functioning correctly\n1177 - QS backup abend on takeover with local TMF transactions\n1180 - Segmentation of messages on transmission queues by the queue manager\nwas incorrect.\n1182 - Replace fault tolerant process pair FDCs with log messages for better\noperator information when a takeover occurs\n1185 - Opens left in all three NonStop Server processes after divering CPUs\n1208 - Trace info is incorrect for zslHPNSS functions. FFSTs show incorrect\ncomponent and incorrect stack trace info\n1210 - FFSTs generated by criAccessStatusEntry when starting channel with\nsame name from another queue manager\n1213 - Pathway listener generates FDCs on open of standard files\n1229 - Permanent dynamic queues being marked as logically deleted on last close\n1240 - Channel Server needs to update status for unexpected thread close\n1244 - Speed up instmqm\n1246 - implement workaround for the regression in the OSS cp command introduced\nin G06.29/H06.06 where a Format 2 file is created by default when\ncopying to Guardian\n1247 - Fixes to SSL CRL processing, added CRL reason to message amq9633\n1253 - SSL samples required updating to reflect enhanced certificate file\norganization - cert.pem and trust.pem\n1254 - Fix an MQDISC internal housekeeping problem\n1256 - MCA does not exit after re-use count if an error occurs during early\ninitialization\n1260 - Speed up strmqm when performed on very busy systems with large number\nof CPUs by minimizing calls to HP FILE_GETOPENINFO_ API\n1264 - Correct the handling of the option to make Message Overflow files\naudited in QS\n1266 - Improve diagnostic information of FFST text for semaphore problem\n1271 - After sequence of 2 CPU downs, EC, QS and CS still have openers\n1272 - Improve protection in svcmqm when files in the installation are open\n1273 - Memory leak in the command server caused by unreleased object lists\n1277 - Don't FFST if initialization fails because the mqs.ini file doesn't\nexist\n1281 - LQMA thread doesn't end when CPU containing application goes down\n1288 - Channels not retrying after CPU failure that also causes takeover of CS\n1290 - MQDISC when connection broken doesn't tidy up transaction\n1291 - Correct the syncpoint usage when amqsblst is used as a server. Enhance\namqsblst for fault tolerant behavior - makes amqsblst attempt to\nreconnect and reopen objects on 2009 errors so it can be used during\nfault tolerant testing\n1294 - Application process management rules don't always work correctly\n1297 - Correct file permission of trace directory and files - changed\npermission of trace directory to 777\n1301 - No queue manager start or stop events generated\n1302 - instmqm function get_Guardian_version should look for string\n\"Software release ID\"\n1306 - instmqm validation fails when Java is not installed - issue a warning\nif the java directory doesn't exist and continue the installation\n1310 - OSS Serverclasses not restarting in Pathway if they end prematurely\n1313 - EC process management can exceed maximum number of threads for LQMA\n1317 - REFRESH CLUSTER command with REPOS(yes) fails\n1319 - MQPUT and MQPUT1 modifying PMO.Options when creating a new MsgId\n1324 - MQPUT returned MQRC_BACKED_OUT when putting message that required\nsegmentation to local queue\n1325 - Trace state doesn't change in servers unless process is restarted\n1340 - QS error handling MQPUT checkpoint. Also can lead to zombie messages on\nqueue requiring queue manager restart to clear\n1341 - MQGET not searching correctly in LOGICAL_ORDER for mid-group messages\n1346 - EC initial memory use too high. Initial allocation was approximately\n18 megabytes\n1351 - Upgrade logging format to V6.x style\n1353 - MQGET of 210kbyte NPM from queue with checkpointing disabled caused\nmessage data corruption at offset 106,906\n1355 - xcsExecProgram sets current working directory to /tmp - changed to\ninstallation errors directory\n1357 - instmqm fails to create an OSS symbolic link after a cancelled install\n1362 - MsgFlags showing segmentation status should still be returned in\nMQGET even if applications specifies MQGMO_COMPLETE_MSG\n1364 - endmqlsr sometimes hangs\n1366 - Correct trace, FDC and mqver versioning information for V5.3.1.1\n\nAll fixes that were previously released in V5.3.0 and V5.3.1 are also included\nin this release. For information on fixes prior to V5.3.1.1, please refer to\nthe readme for V5.3.1.3 or earlier.\n\nBackward compatibility\n----------------------\n\nIBM WebSphere MQ V5.3.1 for HP NonStop Server is interoperable over channels\nwith IBM MQSeries(TM) V5.1 for Compaq NSK, as well as any other current or\nearlier version of IBM MQSeries or IBM WebSphere MQ on any other platform.\n\nProduct compatibility\n---------------------\n\nIBM WebSphere MQ V5.3.1 for HP NonStop Server is not compatible\nwith IBM WebSphere MQ Integrator Broker for HP NonStop Server.\nFor other compatibility considerations, review the list of suitable\nproducts in the WebSphere MQ for HP NonStop Server Quick Beginnings book.\n\nIBM WebSphere MQ V5.3.1 for HP NonStop Server is compatible with any\ncurrently supported level of IBM WebSphere MQ Client. IBM WebSphere MQ V5.3.1\nfor HP NonStop Server does not support connections from WebSphere MQ\nExtended Transactional Client.\n\nINSTALLATION, MIGRATION, UPGRADE AND CONFIGURATION INFORMATION\n==============================================================\nHardware and Software Requirements\n----------------------------------\n\nThe list of mandatory HP operating system and SPR levels has changed\nsince the V5.3.1.1 release. Please read the following information carefully,\nand if you have any questions, please contact IBM.\n\nFor the HP Integrity NonStop Server H-Series systems, the following system\nsoftware versions are the minimum mandatory level for V5.3.1.12:\n\n- H06.23.01 or later\n- SPR T8306H01^ABJ or later\n- SPR T8994H01^AAM or later\n- SPR T8397H01^ABD or later\n- SPR T1248H06^AAX or later\n\n\nFor the HP Integrity NonStop BladeSystem J-Series systems, the following\nsystem software versions are the minimum mandatory level for V5.3.1.12:\n\n- J06.14.00 or later\n\nNote that V5.3.1.12 is not supported on G-Series systems\n\nRecommended SPRs\n-----------------\nIt has become increasingly complicated to document fixes made by HP\nfor some of their products, as the products themselves often have multiple\nthreads (H01, H02, G01, G06 etc..) that can be used on multiple OS levels.\n\nTo make it more convenient for our customers to determine whether they already\nhave a recommended fix installed, or to find the appropriate fix in Scout on\nthe NonStop eServices Portal, we are now referencing particular problems by\ntheir HP solution number.\nIf you wish to determine whether your particular level of an SPR contains\nthe solution, review the document included when you downloaded the product\nfrom Scout or review the softdocs in Scout for the solution number for that\nproduct.\n\nWe have added more information about the specific problems reported,\nwhat the symptoms are, workarounds to these problems if relevant,\nand the likelihood of it happening.\nPlease note:\nWhere versions are inside parentheses beside an HP solution #,\nthose versions only are affected by that particular solution.\n\nProduct ID: T0845 - Pathway Domain Mgmt Interface/TS/MP 2.5\nProblem: PATHCTL file can be corrupted if a pathway serverclass abends. \nSymptom: Pathway unusable\n(Reported as possible by HP but not independently confirmed by IBM).\nHP Solution: 10-120322-2183\nLikelihood: Possible\nWorkaround: None\nRecovery: May be possible to re-configure the WMQ serverclasses in some circumstances.\n\nProduct ID: T1248 - pthreads\nProblem: Threaded server application, MCA - amqrmppa_r, causes 100% CPU\nutilization\nHP Solution: 10-080818-5258 (H07, H06, G07)\nSymptom: CPU 100% busy while processing SSL channels. MCA process consumes\nall available CPU. May be communication errors on channels\nLikelihood: Certain when attempting to Stop SSL Channels using Mode Terminate\n\nif priority of MCA process is higher than Channel Servers\nWorkaround: For SSL channels use unthreaded MCAs or upgrade to WMQv5.3.1.4\nRecovery: None, CPUs will go back to normal after about 5 mins\n\n\nProblem: Assert in spt_defaultcallback for threaded MCAs, amqrmppa_r\nHP Solution: 10-080519-3266 (H06, G07)\nSymptom: FDCs from MCAs, plus MCAs abend (qmgr log message), channels fail\nand restart. Error 28 seen in FFST from MCA process on WRITEREADX\ncall\nLikelihood: Rare.\nWorkaround: Use unthreaded MCAs\nRecovery: None, MCAs will abend but MCAs and associated channels will\nrestart\n\nProduct ID: T6533 - STDSEC-STANDARD SECURITY PROD\nProblem: The GROUP_GETINFO_ Guardian procedure call used by dspmqusr returns error 590 with\ngroup ID greater than 65535.\nSymptom: dspmqusr abends with AMQ7047: An unexpected error was encountered by a command.\nFFST generated reports error 590.\nHP Solution: SOLN 10-091111-6280\nLikelihood: Definite if a user is created in group with a group ID greater than 65535,\neg. SECURITY-ENCRYPTION-ADMIN and that user id added as a principal.\nWorkaround: Members of a group with group ID greater than 65535 cannot be added as WMQ principal\nRecovery: None\n\nProduct ID: T8306 - OSS Sockets Version: H04, H02, G12, G10\nProblem: OSS socket APIs fail with ENOMEM (4012) error.\nHP Solution: 10-081205-7769. (H04, G12)\nSymptoms: Channels fail to start, Error log and FFSTs indicate error 4012.\nLikelihood: Rare\nWorkaround: None\nRecovery: Reload CPU.\n\nProblem: CPU halt %3031 and CPU Freeze %061043 after CPU down testing.\nSymptoms: All processes in the CPU will end,,, backup NonStop processes\nwill take over. Error log will indicate backup servers have taken\nover.\nHP Solution: 10-080827-5452. (H04, H02, G12, G10)\nLikelihood: Rare\nWorkaround: None\nRecovery: Reload CPU\n\n\nProduct ID: T8397- OSS Socket Transport Agent\nProblem CPU Halt %3031 or CPU Freeze %061043\nSymptoms All processes in the CPU will end, backup NonStop processes will\ntake over. Error log will indicate backup servers have taken over.\nHP Solution: 10-080827-5452 (H02, H01, G11)\nLikelihood: Rare\nWorkaround: Reload CPU\n\nProblem: OSS socket APIs fail with ENOMEM (4012) error.\nSymptom: Channels fail to start. Error log and FFSTs indicate error\n4012.\nHP Solution: 10-081205-7769 (H02, G11)\nLikelihood: Rare\nWorkaround: None\nRecovery: Reload CPU\n\n\nProduct ID: T8607 - TMF\nProblem: Multiple issues involving lost signals with OpenTMF\nSymptom: Channel Server indicates Sequence number mismatches. Channel\nserver generates FDCs that report file system error 723.\nHP Solution: 10-081027-6812, Hotstuff HS02990. (H01)\nLikelihood: Rare, but may occur if audit trail is 90% full, or operator stops\nTMF.\nWorkaround: Monitor audit trail size\nRecovery: Stop primary channel server process.\n\nSymptom: Queue Manager completely freezes up, Log messages every 10 seconds\nfor 50 attempts.\nHP Solution: 10-081027-6812, Hotstuff HS02990. (H01)\nLikeihood: Very likely if STOP TMF, ABRUPT command is issued while Queue\nManagers are running.\nWorkaround: Do not issue STOP TMF, ABRUPT command while queue managers are \nrunning until the SPR has been installed.\nRecovery: Restart Queue Manager.\n\n\nProduct ID: T8620 - OSS file system Version: G13,H03, H04\nProblem: lseek() fails with errno 4602.\nSymptoms: FFSTs generated in xcsDisplayMessage component\nHP Solution: SOLN 10-071012-8159 (G13,H03, H04)\nLikelihood: Likely\nWorkaround: Turn off OSS Caching in all disks\nRecovery: None needed, problem is benign.\n\nSymptoms: Queue Manager slowdown along with (sometimes) lost log messages\nin busy queue managers. System suffered major OSS lockups and CPU\nhalts\nHP Solution: SOLN 10-071012-8159 (G13,H03, H04)\nLikelihood: Rarely\nWorkaround: None\nRecovery: Stop and restart all Queue Managers and Listeners. Reload CPUs.\n\nIf you use SNA channels with V5.3.1, we recommend the latest levels of the\nHP SNAX or ACI Communication Services for Advanced Networking (ICE) be used\nfor the SNA transport. The following versions were verified by IBM with this\nrelease of WMQ:\n\nACI Communication Services for Advanced Networking (ICE)\n- v4r1 on both HP Integrity NonStop Server and S-Series systems\n\nHP SNAX\n- T9096H01 on HP Integrity NonStop Server (H-Series) systems\n\nIf you use the WebSphere MQ V5.3 classes for Java and JMS for HP NonStop Server\nyou will need to install HP NonStop Server for Java Version 1.4.2 or later.\nThe Java.pdf supplemental document in the <install_path>/opt/mqm/READMES/en_US\ndirectory has been updated in this release. Java/JMS users should review the \nupdated document.\n\nUpgrading to V5.3.1.12\n---------------------\n\nFor systems running H Series operating systems, you may upgrade\nany prior service level of WebSphere MQ V5.3.1.x for HP NonStop Server to\nV5.3.1.12 level using this release. For NonStop BladeSystem running J series\noperating systems, you may upgrade from version V5.3.1.4 only, since V5.3.1.4\nis the earliest supported version on J series. If you need to perform a full\ninstallation on a J series system from the original installation media, see the\nsection later in this readme file for instructions.\n\nThe installation tool, svcmqm, is used to upgrade existing installations\nto this level. Additionally, the placed files for any prior level of V5.3.1\ncan be overlaid with the new files from V5.3.1.12 and then instmqm can be used\nto create new installations at the updated V5.3.1.12 level.\n\nYou must end all queue managers and applications in an installation if you\nwant to upgrade that installation to V5.3.1.12.\n\nYou do not need to re-create any queue managers to upgrade to V5.3.1.12.\nExisting queue managers (at any V5.3.1.x service level) will work with\nV5.3.1.12 once an installation has been properly upgraded.\n\nIf you use SSL channels, and are upgrading from WMQ V5.3.1, you must perform\na small reconfiguration of the Certificate store before running any SSL\nchannels after you have upgraded. The steps that are required are described\nbelow in the Post-Installation section. If you do not perform this\nreconfiguration, SSL channels in the upgraded V5.3.1.12 installation will\nfail with the log messages similar to the following:\n\nFor sender channels:\n\n09/29/07 08:52:43 Process(0,483 $Z8206) User(MQM.ABAKASH) Program(amqrmppa)\nAMQ9621: Error on call to SSL function ignored on channel\n'ALICE_BOB_SDRC_0000'.\n\nEXPLANATION:\nAn error indicating a software problem was returned from a function which is\nused to provide SSL support. The error code returned was '0xB084002'. The error\nwas reported by openssl module: SSL_CTX_load_verify_locations, with reason:\nsystem lib. The channel is 'ALICE_BOB_SDRC_0000'; in some cases its name cannot\nbe determined and so is shown as '????'. This error occurred during channel\nshutdown and may not be sufficiently serious as to interrupt future channel\noperation; Check the condition of the channel.\nACTION:\nIf it is determined that Channel operation has been impacted, collect the items\nlisted in the 'Problem determination' section of the System Administration\nmanual and contact your IBM support center.\n---- amqccisx.c : 1411 ------------------------------------------------------\n09/29/07 08:52:44 Process(0,483 $Z8206) User(MQM.ABAKASH) Program(amqrmppa)\nAMQ9001: Channel 'ALICE_BOB_SDRC_0000' ended normally.\n\nEXPLANATION:\nChannel 'ALICE_BOB_SDRC_0000' ended normally.\nACTION:\nNone.\n\nFor client or receiver channels:\n\n-------------------------------------------------------------------------------\n09/29/07 08:05:28 Process(1,802 3 $X0545) User(MQM.HEMA) Program(amqrmppa_r)\nAMQ9620: Internal error on call to SSL function on channel '????'.\n\nEXPLANATION:\nAn error indicating a software problem was returned from an function which is\nused to provide SSL support. The error code returned was '0x0'. The error was\nreported by openssl module: SSL_load_client_CA_file, with reason: CAlist not\nfound. The channel is '????'; in some cases its name cannot be determined and\nso is shown as '????'. The channel did not start.\nACTION:\nCollect the items listed in the 'Problem determination' section of the System\nAdministration manual and contact your IBM support center.\n---- amqccisx.c : 1347 ------------------------------------------------------\n09/29/07 08:05:28 Process(1,802 3 $X0545) User(MQM.HEMA) Program(amqrmppa_r)\nAMQ9228: The TCP/IP responder program could not be started.\n\nEXPLANATION:\nAn attempt was made to start an instance of the responder program, but the\nprogram was rejected.\nACTION:\nThe failure could be because either the subsystem has not been started (in this\ncase you should start the subsystem), or there are too many programs waiting\n(in this case you should try to start the responder program later). The reason\ncode was 0.\n\nWMQ Application re-compile Considerations :\n\nYou do not need to re-compile any applications to upgrade to V5.3.1.12.\n\nWMQ Application linkage Considerations :\n\na) If upgrading from V5.3.1.5 or later releases (including patch releases) :\n\nExisting applications will continue to work with V5.3.1.12 release. However, \nIBM strongly recommends that if you are upgrading from a release prior to \n5.3.1.7, you review the impact of APARs IC67057 and IC68569 that were fixed in\nthe V5.3.1.7 release. Please also note internal defect 4158 that is fixed in \nV5.3.1.11. The IC67057, IC68569 and internal defect 4158 fixes will not be \neffective in non-native applications unless the applications are relinked \nusing the HP BIND utility. \n\nb) If upgrading from V5.3.1.4 or earlier releases (including patch releases) :\n\nYou MUST use the HP BIND utility to relink any non-native applications prior\nto using them with V5.3.1.12. If an application is not re-bound with the \nV5.3.1.12 WMQ product, MQCONN API calls will fail with a MQRC 2059 and the \nWMQ EC process will output an FDC when the MQI incompatibility is detected, \nas follows:\n\nProbe Id :- EC075003\nComponent :- ecaIsECup\nComment1 :- Application MQ API not compatible, relink application\nComment2 :- <process cpu,pid process name>\nComment3 :- <application executable name>\n\nInstallation from Electronic Software Download H or J Series based systems\n-----------------------------------------------------------------------------\n\nThese instructions apply to installing WebSphere MQ for HP NonStop Server,\nVersion 5.3.1.12, from the package downloaded from IBM. Please note the\nadditional restrictions for upgrading J Series systems to this version.\n\nUse svcmqm to update an existing installation from the V5.3.1.12 placed files.\n\n1. Unzip the fixpack distribution package - wmq53.1.12.tar.zip.\nThe fixpack distribution package contains the following files:\n\nreadme_wmq_5.3.1.12 - this README\nwmq53.1.12_H07.tar.Z - H-Series H06 Package\n\n2. Identify the correct fixpack package to install:\n\nFor H-Series (H06) or J-Series systems (J06) use: wmq53.1.12_H06.tar.Z\n\n3. Upload the compressed fixpack archive to the OSS file system in binary mode.\nYou may wish to store the compressed archive, and the expanded contents\nin a location where you archive software distributions from IBM.\nIf you do this, you should store the compressed archive in a directory\nthat identifies the version of the software it contains,\nfor example, \"V53112\".\n\nmkdir -p /usr/ibm/wmq/V53112\nupload (in binary mode) the correct compressed tarfile to this directory\n\n4. Extract the fixpack compressed tarfile using commands similar to:\n\ncd /usr/ibm/wmq/V53112\nuncompress wmq53.1.12_H06.tar.Z\n\ntar xvof wmq53.1.12_H06.tar\n\n5. Locate your WMQ V5.3.1.x installation(s). The service installation procedure\nrequires the full OSS path names of the opt/mqm and var/mqm directories for\neach WMQ installation to which the fixpack will be installed.\n\n6. Logon to OSS using the WMQ installation owner's userid\n\n7. End all Queue Managers defined in the WMQ Installation.\nendmqm <qmgr name>\n\nEnsure all Queue Managers defined in the WMQ installation\nare ended.\ndspmq\n\nEnsure that the WMQ installation is at a suitable V5.3.1 level.\nmqver -V\nSee later notes concerning version requirements for NonStop BladeSystem\ninstallation.\n\n8. End any non-Pathway listeners for Queue Managers defined in the\nWQM installation:\nendmqlsr -m <qmgr name>\n\n9. Verify that no files in the Guardian subvolumes of the installation to\nbe updated are open. The installation cannot proceed safely unless all\nfiles in these subvolumes are closed. Use the TACL command 'FUP LISTOPENS'\nfor the files in all three subvolumes - an absence of output indicates\nthat no files are open. If files are shown to be open, use the output\nfrom the command to identify processes that are holding files open.\n\n\n10. Backup your WMQ Installation; the fixpack cannot be uninstalled.\ninstmqm -b can be used to back up an installation. Please refer\nto the readme file included with release WMQ V5.3.1.\n\n11. Install the fixpack by running the supplied service tool (svcmqm).\nSvcmqm requires the location of the OSS var tree as well\nas the OSS opt tree. These locations can be supplied automatically by\nrunning svcmqm in an OSS shell where the environment variables for the\nWMQ installation being updated have been established (typically by\nsourcing \"wmqprofile\"). If this is the case, svcmqm does not require the\n-i and -v parameters. \n\nFor example:\ncd /usr/ibm/wmq/V53112\nopt/mqm/bin/svcmqm -s /usr/ibm/wmq/V53112/opt/mqm\n\nIf the environment variables for the WMQ installation are not established in \nthe environment of svcmqm or if you want to update a WMQ installation other\nthan the one that your current WMQ environment variable points to, then \nthe locations of the OSS opt and var trees must be supplied explicitly using\nthe svcmqm command line parameters -i and -v.\n\nFor example:\n\ncd /usr/ibm/wmq/V53112\nopt/mqm/bin/svcmqm -s /usr/ibm/wmq/V53112/opt/mqm\n-i /wmq1/opt/mqm\n-v /wmq1/var/mqm\n\nsvcmqm will prompt to confirm the location of the OSS opt tree for the\ninstallation to be updated.\nType \"yes\" to proceed.\n\nSvcmqm will then update the installation. The current WMQCSTM file for\nthe installation will be renamed to BWMQCSTM as a backup copy, before it\nis regenerated. Note that any changes to the WMQCSTM file you have made\nwill not be copied to the new WMQCSTM file, however they will be preserved\nin the backup copy made before the WMQCSTM file was regenerated.\n\n12. Repeat Steps 5-11 for any other WMQ installations that you want to update\nwith this fixpack.\n\n13. You can install this fixpack in the WMQ placed installation files so that\nany future WMQ product installations will include the fixpack updates.\n\nTo do this, locate your WMQ placed installation filetree containing the\nopt directory, make this your current working directory (use 'cd') and\nthen unpack the contents of the tar archive for this fixpack over the placed\nfile tree. For example, if the placed files are located in the default\nlocation /usr/ibm/wmq/V531, for a H-Series system:\n\ncd /usr/ibm/wmq/V531\ntar xvof /usr/ibm/wmq/V5319/wmq53.1.12_H06.tar\n\nInitial Installation on a NonStop BladeSystem\n---------------------------------------------\n\nThese instructions apply to installing WebSphere MQ for HP NonStop Server on\na NonStop BladeSystem using the original installation media, in conjunction\nwith the 5.3.1.12 package downloaded from IBM. NonStop BladeSystem platforms\nare not supported prior to V5.3.1.4, and a \"from scratch\" installation requires\neither V5.3.1.4 or later files to be overlaid on a set of placed files\nfrom the base product media prior to performing the installation.\nYou do NOT need to perform these steps if you have already installed V5.3.1.4\non your NonStop BladeSystem. In this case, follow the standard installation\nsteps earlier in this readme file.\n\n1. Place the files for the Refresh Pack 1 (5.3.1.0) version of WebSphere MQ\n\nfor HP NonStop Server on the target system. Refer to the \"File Placement\"\nsection in Chapter 3 of the \"WebSphere MQ for NonStop Server Quick\nBeginnings\" guide. Pages 11-13 describes how to place the files.\nDo not attempt to install the placed files using the instmqm script\nthat was provided with V5.3.1.0 at this time. The V5.3.1.0 version of\ninstmqm does not support installation on NonStop BladeSystem.\n\n2. Unzip the 5.3.1.12 fixpack distribution package - wmq53.1.12.tar.zip.\nThe fixpack distribution package contains the following files:\n\nreadme_wmq_5.3.1.12 This README\nwmq53.1.12_H06.tar.Z H-Series H06 Package\n\n3. This installation requires the wmq53.1.12_H06.tar.Z package.\nLocate the WMQ placed installation filetree containing the opt directory\nprepared in step 1 above, and upload the wmq53.1.12_H06.tar.Z fixpack\narchive to this location in binary mode.\n\n4. Extract the fixpack compressed tarfile using commands similar to:\n\ncd /usr/ibm/wmq/V53112\nuncompress wmq53.1.12_H06.tar.Z\n\n5. Unpack the contents of the extracted tar archive for this FixPack over the\nplaced file tree. For example, if the placed files are located in the default\nlocation /usr/ibm/wmq:\n\ncd /usr/ibm/wmq\ntar xvof /usr/ibm/wmq/V53112/wmq53.1.12_H06.tar\n\n6. Use the extracted instmqm script in this FixPack to install the product\nusing the updated installation file tree and the instructions in Chapter 3\nof \"WebSphere MQ for NonStop Server Quick Beginnings\" guide, pages 13-29.\nBefore beginning, review the list of changes to Chapter 3 detailed in the\n\"Documentation Updates\" section at the end of this README file. Note also\nthat the list of installed files displayed will differ from those shown in the\nexamples in the manual.\n\nPost-Installation\n-----------------\nIf upgrading from WMQ V5.3.1, read the following post-installation instructions:\n\nNon-Native TNS Applications:\n\nRe-BIND any non-native (TNS) applications. See \"Upgrading to V5.3.1.12\" above \nfor more information.\n\nRe-binding non-native (TNS) is REQUIRED if upgrading from V5.3.1.4 or earlier\nreleases but is RECOMMENDED if upgrading from V5.3.1.5 or later fixpack for \nincorporation of APARs IC67057, IC68569 and internal defect 4158. \n\nIf you use SSL channels and have not already installed V5.3.1.1:\n\nEdit the SSL certificate store, cert.pem and move all the CA certificates\nto a new file, trust.pem, stored in the same directory as cert.pem. The\nonly items that should remain in cert.pem are the queue manager's personal\ncertificate, and the queue manager's private key. These two items should\nbe located at the start of the cert.pem file. All other certificates\n(intermediate and root CAs) must be moved to trust.pem. The trust.pem file\nmust be in the same directory as cert.pem, as configured in the queue\nmanager's SSLKEYR attribute.\n\nUpdate the copy of the entropy daemon program that you run for SSL channels\non the system with the new version (...opt/mqm/ssl/amqjkdm0).\n\nEnable new support for Danish CCSID 65024:\n\nCustomers who wish to enable the new support for Danish CCSID 65024\nshould do the following to install the revised ccsid.tbl file:\n\nIssue the following commands on OSS:\n\n1. Logon to OSS using the WMQ installation owner's userid\n2. End all Queue Managers defined in the WMQ Installation.\nendmqm <qmgr name>\n3. Source in the installation's wmqprofile\n. $MQNSKVARPATH/wmqprofile\n4. cp -p $MQNSKOPTPATH/samp/ccsid.tbl $MQNSKVARPATH/conv/table/\n5. Start queue managers\n\nGuardian C++ DLLs:\n\nEnsure that the WMQ Guardian C++ DLLs are 'executable' by using \"FUP ALTER\"\nto set their FILECODE to 800 (for H-Series or J-Series). Use commands similar \nto the following:\n\n1. Logon to TACL using the WMQ installation owner's userid\n\n2. OBEY your WMQ Installation's WMQCSTM file\n3. VOLUME [#param MQNSKOPTPATH^LIB^G]\n4. FUP ALTER IMQI2,CODE 800\n5. FUP ALTER IMQI2T,CODE 800\n6. FUP ALTER IMQI3,CODE 800\n7. FUP ALTER IMQI3T,CODE 800\n8. Logoff\n\nGuardian Subvolume File Permissions\n\nThe WMQ Guardian Installation Subvolume and all WMQ Guardian Queue\nManager Subvolumes must accessible to both MQM group members\nand to users that run WMQ application programs.\n\nEnsure that:\n\nAll members of the MQM security group have read, write, execute\nand purge permission to these subvolumes.\n\nAll users that run WMQ application programs, have read, write\nand execute permission to these subvolumes\n\nRestart Queue Managers:\n\nRestart the queue managers for the installation you have\nupdated with this fixpack.\n\nUNINSTALLATION INFORMATION\n==========================\n\nThis fixpack cannot be automatically uninstalled if a problem occurs\nduring the update of an installation using svcmqm.\n\nYou should use the instmqm -b option to create a backup of an\ninstallation before applying the service. If a problem occurs\nor you need to reverse the upgrade at a later date, use the\ninstmqm -x option to restore a backup of the installation at the\nprior service level.\n\nKNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS\n===========================================\n\nThis section details known limitation, problems, and workarounds for\nWebSphere MQ for HP NonStop Server, Version 5.3.1.12.\n\nLimitations\n-----------\n\n1. The current implementation of Publish / Subscribe is restricted to run\nwithin a single CPU. The control program and all \"worker\" programs run in\nthe CPU that was used to run the 'strmqbrk' command.\nThe Publish/Subscribe broker does not automatically recover in the event\nof CPU failures.\n\n2. The current memory management implementation in the Queue Server limits\nthe total amount of non-persistent message data that can be stored on all\nthe queues hosted by a single Queue Server to less than 1Gb. The limit of\nnon-persistent message data on a single queue can not exceed approximately\n1Gb therefore, even if a single Queue Server is dedicated to that queue.\n\n3. The number of threads in threaded agent processes (LQMAs or MCAs) or in MQI\napplications, is limited to a maximum of 1000 by the limit on open depth of\nthe HP TMF T-file.\n\n4. API exits are not supported for non-native (TNS) applications. Any other\nexit code for non-native applications must be statically bound with the\nTNS application.\n\n5. Cluster workload exits are only supported in \"trusted\" mode. This means\nthat a separate copy of each exit will run in each CPU and exit code in\none CPU cannot communicate with exit code in another CPU using the normal\nmethods provided for these exits.\n\n6. Upgmqm will not migrate the following data from a V5.1 queue manager:\nmessages stored in Message Overflow files (typically persistent messages\nover 200,000 bytes in size) will not be migrated. If the option to\nmigrate message data was selected, the upgrade will fail. if the option\nto migrate message data was not selected, the upgrade will not be\naffected by the presence of message overflow files.\nclustering configuration data - all cluster related attributes of objects\nwill be reset to default values in the new V5.3 queue manager.\nSNA channel configuration - channels will be migrated, but several of the\nattributes values will need to be changed manually after the upgrade.\nchannel exit data - attributes in channels that relate to channel exit\nconfiguration will be reset to default values in the new V5.3 queue\nmanager.\nIn all cases where upgmqm cannot migrate data completely, a warning message\nis generated on the terminal output as well as in the log file. These can\nbe reviewed carefully after the upgrade completes for further actions that\nmay be necessary.\n\n7. Java and JMS limitations\n\nThe Java and JMS Classes do not support client connections. WebSphere MQ\nfor HP NonStop Server does not support XA transaction management, so the\nJMS XA classes are not available. For more detail, please refer to the\nJava and JMS documentation supplement, Java.pdf.\n\n8. Control commands in Guardian (TACL) environment do not obey the RUN option\n\"NAME\" as expected\n\nA Guardian control command starts an OSS process to run the actual\ncontrol command - and waits for it to complete. When the NAME option is\nused, the Guardian control command process uses the requested name, but\nthe OSS process cannot and is instead named by NonStop OS.\n\nIf the Guardian control command is prematurely stopped by the operator\n(using the TACL STOP command for example) the OSS process running the\nactual control command may continue to run. The OSS process may need to be\nstopped separately and in addition to the Guardian process.\n\n9. Trace doesn't end automatically after a queue manager restart\n(APAR IC53352) and trace changes do not take effect immediately\n\nIf trace is active and a queue manager is restarted, the trace settings\nshould be reset to not trace any more. Instead, the queue manager\ncontinues tracing using the same options as before it was restarted.\nThe workaround is to disable trace using endmqtrc before ending, or while\nthe queue manager is ended.\n\nAlso, changes to trace settings do not always take effect immediately\nafter the command is issued. For example, it could be several MQI calls\nlater that the change takes effect. The maximum delay between making a\ntrace settings change and the change taking effect would be until the end\nof the queue manager connection, or the ending of a channel.\n\n10. Some EMS events generated to default collector despite an alternate\ncollector being configured (APAR IC53005)\n\nAn EMS event message \"FFST record created\" is generated using the OSS\nsyslog() facility whenever an FDC is raised by a queue manager. This\nEMS event cannot be disabled, and goes to the default collector $0. For\nOSS processes, an alternate collector process can be specified by\nincluding an environment variable in the context of these processes\nas in the following example:\n\nexport EMS_COLLECTOR=\\$ALT\n\nGuardian processes always use the default collector because HP do not\nprovide the ability to modify the collector in the Guardian environment.\nHP is investigating if a change is possible. No fix for this problem\nhas yet been identified.\n\n11. The use of SMF (virtual) disks with WMQ is not supported on Release\nVersion Updates prior to H06.26 and J06.15 because of restrictions\nimposed by the OSS file system. For more details, please refer to the\nHP NonStop Storage Management Foundation User's Guide Page 2-12.\n\n12. The maximum channel batch size that can be configured (BATCHSZ attribute)\nis 2000. If you need to run channels with batch sizes greater than 680\nyou must increase the maximum message length attribute of the\nSYSTEM.CHANNEL.SYNCQ to 60000.\n\ne.g. from RUNMQSC - ALTER QL (SYSTEM.CHANNEL.SYNCQ) MAXMSGL (60000)\n\n13. The SYSTEM.CHANNEL.SYNCQ is a critical system queue for operation of\nthe queue manager and should not be altered to disable MQGET or MQPUT\noperations, or to reduce the maximum message size or maximum depth\nattributes from their defaults.\n\n14. Currently, the cluster transmission queue (SYSTEM.CLUSTER.TRANSMIT.QUEUE)\ncannot be moved to an alternative Queue Server because it is constantly\nopen by several internal components. The following procedure (which\nrequires a \"quiet\" queue manager, and a queue manager restart) can be\nused to achieve this reconfiguration. Do not use this procedure on a\nqueue manager that is running in production. Read and understand the\nprocedure carefully first since it includes actions that cause\ninternal errors to be generated in the queue manager.\n\n1/ Rename the OSS repository executable (opt/mqm/bin directory)\nmv amqrrmfa amqrrmfax \n2/ From OSS enter 'ps -f | grep amqrrmfa | grep X '\nwhere X is the Queue Manager name.\n3/ kill -9 those processes returned from step 2\nAt this point the EC will start continuously generating FDCs and\nlog messages as it attempts to, and fails, to restart the repository\nservers that were stopped. Perform the remaining steps in this\nprocedure without delay to avoid problems with excessive logging\nsuch as disk full conditions.\n4. Verify the processes are stopped\nFrom OSS enter 'ps -f | grep amqrrmfa | grep X '\nWhere X is the Queue Manager name\n5. Issue the altmqfls --server command to move the cluster transmission\nqueue to an alternate queue server\n6. Issue dspmqfls to verify the alternate server assignment\n7. Rename the OSS repository executable back to the expected name\nmv amqrrmfax amqrrmfa\n8. End the queue manager using preemptive shutdown. The EC will generate\nFDCs ending because of the earlier attempts to start a repository\nmanager while the executable was renamed. There will be FDCs and\nEC Primary process failover\n\nComponent :- xcsExecProgram\nProbe Description :- AMQ6025: Program not found\nComment1 :- No such file or directory\nComment2 :- /opt/mqm/bin/amqrrmfa\n...\nAMQ8846: MQ NonStop Server takeover initiated\nAMQ8813: EC has started takeover processing\nAMQ8814: EC has completed takeover processing\n...\nThe EC may have to be manually TACL stopped if quiesce or immediate\nend is used thus the need for the preemptive shutdown\nendmqm -p <qmgr name>\n9. Rename the repository manager executable to the original name\nmv amqrrmfax amqrrmfa\n10. Restart the queue manager\nstrmqm <qmgr name>\n\n15. In Guardian/TACL environments, support for some WMQ command-line programs\nhas been deprecated for WMQ Fixpack 5.3.1.3 and later.\n\nThe affected command-line programs are:\n\namqoamd\namqrdbgm\namqrfdm\ncrtmqcvx\nendmqlsr\nrunmqchi\nrunmqchl\nrunmqdlq\nrunmqlsr\nrunmqtrm\n\nThese programs will continue to function for now, however their use in\nGuardian/TACL environments is discouraged. Support for these programs\nin Guardian/TACL environments may be withdrawn completely in a future\nWMQ 5.3 release/fixpack.\n\nIBM recommends that customers use the OSS version of these programs instead.\n\nCustomers who want to route output from WMQ OSS tools to VHS or other Guardian\ncollectors should use the OSSTTY utility. OSSTTY is a standard utility\nprovided by OSS and is described in the HP publication \"Open System Services\nManagement and Operations Guide\".\n\nNote: See Item 3. in \"Known problems and workarounds\" for a description of\nrestrictions when using the MQ Broker administration commands in the\nGuardian/TACL environment.\n\n16. Do not use WebSphere MQ with a $CMON process that alters attributes of WMQ\nprocesses (for example the processor, priority, process name or program\nfile name) when they are started. This is not a supported environment since\nthere are components in WMQ that rely on these attributes being set as\nspecified by WMQ for their correct operation.\n\n17. Support for forked processes\n\nMQI Support from forked processes in OSS is subject to the following\nrestrictions:\n1. If forking is used, MQI operations can be performed only from child\nprocesses. Using MQI verbs from a parent process that forks child\nprocesses is not supported and will result in unpredictable\nbehavior.\n\n2. Use of the MQI from forked processes where the parent or child is\nthreaded is not supported.\n\n18. TMF Outage handling\n\nTMF outage handling was significantly improved with V5.3.1.4, however there\nis still a limitation in V5.3.1.6 and later to be aware of:\n\n1. If a STOP TMF, ABRUPT command is issued, TMF marks all open audited\nfiles as corrupt and the queue manager cannot perform further\nprocessing until this condition is rectified by restarting TMF.\nIn this state, the queue manager will freeze further operation, and log\nthe condition in the queue manager log file every 10 seconds for a\nmaximum of 50 attempts. Whether or not TMF is restored within this\ntimeframe, the WMQ queue manager should be restarted to reduce the risk\nof any undetected damage persisting.\n\n19. Triggering HP NSS non-C Guardian applications\n\nThe MQ default Trigger Monitor process, runmqtrm, at present cannot\ndirectly trigger the following application types:\n\nGuardian TACL scripts or macro file\nCOBOL application\nTAL application\nAn OSS script file (wmqtrig) provides indirect support for these\nfiles types. To use this script, the PROCESS definition APPLTYPE should\nbe set to UNIX, and the APPLICID should refer to the script as in\nthe following examples:\n\nFor a TACL script called \"trigmacf\":\nAPPLICID('/opt/mqm/bin/wmqtrig -c \\$data06.fp4psamp.trigmacf')\nAPPLTYPE(UNIX)\n\nFor a COBOL or TAL application called \"mqsecha\":\nAPPLICID('/opt/mqm/bin/wmqtrig -p /G/data06/fp4psamp/mqsecha')\nAPPLTYPE(UNIX)\n\n\nNotes:\n1. TACL scripts use the wmqtrig script with a \"-c\" option.\nThe -c option should use the Guardian representation for file name\nof the TACL script file, with the special character ($) escaped,\nfor example:\n\n\\$data06.fp4psamp.trigmacf\n\n2. COBOL and TAL applications use the wmqtrig script with a \"-p\" option.\nThe -p option must use the OSS representation for the file name of\nthe application, for example:\n\n/G/data06/fp4psamp/mqsecha\n\n3. C applications can be triggered directly by specifying\n\nAPPLICID('$DATA06.FP4PSAMP.MQSECHA')\nAPPLTYPE(NSK)\n\nTo trigger a PIC application using the WMQ Pathway MQS-TRIGMON00\nserverclass, a DEFINE is required:\n\n=_RLD_LIB_PATH,CLASS SEARCH,SUBVOL0 <Guardian MQ binary Volume.Subvolume>\n\nFor example:\nALTER MQS-TRIGMON00,\nDEFINE =_RLD_LIB_PATH,CLASS SEARCH,SUBVOL0 $DATA06.FP4PBIN\n\n4. If the \"-p\" option is used, gtacl passes the complete MQTMC2 structure\ntext (which is 560 bytes) to the application being triggered, whereas if\nthe \"-c\" option is used, limitations in TACL will cause the triggered \napplication to receive 520 bytes only.\nApplications intended to be triggered using -p option must handle the \ncomplete 560 character startup character string.\nThis can cause problems, particularly with COBOL applications;\nSince a COBOL GETSTARTUPTEXT call can process only 529 characters,\ntriggering a COBOL application with the -p option (560 character startup\nstring) can result in a memory overwrite and application abend.\nIn this case, the -c option should be used instead of the -p option.\"\n\n20. Maximum numnber of LQMA processes\n\nThe maximum number of LQMA processes per queue manager is 1417. Attempts to\nconfigure a MaxUnthreadedAgents value of 1418 or greater in the qmproc.ini file\nwill result in FDCs when the queue manager attempts to start the 1418th LQMA.\n\n21. Limitation on ProcessNameRoot values in qmproc.ini file\n\nThe ProcessNameRoot value used in the qmproc.ini file for the MCA, LQMA and \nRepositoryManager stanzas must be unique across all queue managers in all\ninstallations on the system. If the values are not unique, two queue \nmanagers attempting to create a new process name at the same time may attempt\nto use the same sequence of names, resulting in heavy load on the OSS\nnameserver and/or FDCs with probes EC062000 from eclStartMCA or EC065000 from\neclStartLQMA. This may result in the queue manager becoming unresponsive.\n\n22. BIND/REPLACE Warning 9\n\nThe use of BIND/REPLACE when re-binding non-native (TNS) applications with \nthe latest WMQ TNS Library is supported, however, when using this command, \nyou may encounter many Bind 'warning 9' messages. These warnings are safe to\nignore, as the changes made in the MQMTNS library are completely contained\nwithin that library and there is no external affect on an application that\nwould link with that library. Please refer to document \nID mmr_ns-4.0.6050052.2565545 in KBNS which has been updated by HP to include\nthis information. \n\n23. PING CHANNEL uses the =TCPIP^PROCESS^NAME DEFINE as opposed to the \nvalue set in the qmproc.ini file.\n\nIf the TCPIP^PROCESS^NAME DEFINE is invalid, attempts to issue a \nPING CHANNEL request will fail with the following message -\n\":AMQ9212: A TCP/IP socket could not be allocated.\"\n\n24. Using multiple cluster receiver channels for a queue manager can cause the \nmaster and slave repository managers to get out of sync in some configurations, \nthis results in FFSTs from rrmHPNSSGetMetaPacket with Comment1 field \n\"Meta data mis-match Expected: metalen=xx\".\nThe root cause of this problem has not been identified definitively, but it is\nrecommended that cluster configurations do not use multiple cluster receiver \nchannels for the same cluster on a given queue manager.\n\n25. Format 2 Queue and Queue overflow files are not supported\n\nIf an attempt is made to use altmqfls to change extent size or max extents of \na Queue or Queue overflow file such that the new file size would require a\nformat 2 file, the attempt will fail and an FDC file containing the following\n\nProbe Id :- XC066050 \nComponent :- xgcDupPartFile \n... \nMajor Errorcode :- xecF_E_UNEXPECTED_RC \nMinor Errorcode :- krcE_UNEXPECTED_ERROR \nProbe Description :- AMQ6118: An internal WMQ error has occurred \n(20800893) \n...\nArith1 :- 545261715 20800893 \n\n26. RUNMQSC DISPLAY QSTATUS(*) TYPE(HANDLE) ALL can return only 500 handles\n\nThe current implementation of DISPLAY QSTATUS can handle only 500 queue\nhandles. In prior releases, executing the command in a scenario where there\nwere more than 500 handles resulted in an error return and large numbers of \nFFSTs (see internal defect 2230 earlier in this readme). These errors are the\nresult of a design limitation with the DISPLAY QSTATUS implementation. \nThe processing of the command has been modified to handle the scenario cleanly\nand return only the first 500 handles retrieved, as supported by the design.\n\nKnown problems and workarounds\n------------------------------\n1. FDCs from Component xcsDisplayMessage reporting xecF_E_UNEXPECTED_SYSTEM_RC\n\nOn RVUs H06.06 and later:\n\nThese FDCs occur frequently on queue manager shutdown, and at times during\nqueue manager start, from processes that write to the queue manager log\nfiles at these times, typically the cluster repository cache manager\n(amqrrmfa) and the EC (MQECSVR). No functional problem is caused by these\nFDCs, except that the queue manager log file misses some log messages\nduring queue manager shutdown. The FDCs report an unexpected return code\nfrom the HP lseek() function. An example of an FDC demonstrating this\nproblem follows:\n\nProbe Id :- XC022011\nComponent :- xcsDisplayMessage\nProgram Name :- $DATA06.RP1PBIN.MQECSVR\nMajor Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC\n\nMQM Function Stack\nnspPrimary\neclShutdownOK\nxcsDisplayMessageForSubpool\nxcsDisplayMessage\nxcsFFST\n\n6fffe660 000011FA ....\n6fffe670 2F686F6D 652F726F 622F4D51 /home/test/MQ\n6fffe680 352E332F 5250312F 50726F64 2F776D71 5.3/RP1/Prod/wmq\n6fffe690 2F766172 2F6D716D 2F716D67 72732F51 /var/mqm/qmgrs/Q\n6fffe6a0 4D312F65 72726F72 732F414D 51455252 M1/errors/AMQERR\n6fffe6b0 30312E4C 4F47 01.LOG\n\nThis problem is fixed by the following HP SPRs\n\nT8620ACL (OSSFS) for G06 HP OS\nT8620ACM (OSSFS) for H06 HP OS\n\n2. APAR IC54594 - EC abends with non-MQM user running application from non-MQM\ndirectory.\n\nStatically-bound TNS applications that are not relinked after installing \nFixpack 5.3.1.4 have additional considerations. For these applications, \nqmproc.ini Application Rules 2 and 4 will not work if the application \nis located in a non-MQM directory.\n\n3. The Guardian control commands for the Publish / Subscribe broker\n(strmqbrk, endmqbrk, dspmqbrk ... etc) will not work correctly unless they\nare run in the same CPU as the broker is running in, or was last running in.\n\nPlease use the equivalent OSS commands instead of the Guardian versions, or\nensure that the Guardian Publish / Subscribe broker commands run in the same\nCPU as the broker was or is running in.\n\n4. Queue managers occasionally do not delete Temporary Dynamic Queues the \nwhen the last application closes them. The cause of this is unknown at present.\nThe problem is rare and unlikely to cause significant impact on queue \nmanager operation unless the queues are present in very large numbers.\nQueues orphaned in this way cannot be used by applications, and are removed\nunconditionally as a part of the normal garbage collection activity during \na queue manager restart.\n\nDOCUMENTATION UPDATES\n=====================\n\nPlease note that several supplements to the documentation have been provided\nwith fixpacks since V5.3 was originally released. These supplements have\nbeen released in Adobe Acrobat format and can found in the\nopt/mqm/READMES/en_US directory of any installation as well as the original\nsoftware distribution tree (placed files). The following supplements have\nbeen released to date (the name of the file describes the content):\n\nExits.pdf\nJava.pdf\nPubsub.pdf\nSNAChannels.pdf\nSSLUpdate.pdf\nUpgmqmreadme.pdf\nSdcp.pdf\n\nAlso please note that the current published versions of the cross-platform\n(\"family\") books contain references to the IBM MQSeries V5.1 for Compaq NSK\nproduct which is the previous major version of WebSphere MQ for HP NonStop\nServer. Consequently, these references may not be accurate with respect to\nthe functional support provided by V5.3.1.\n\nWebsphere MQ Programmable Command Formats and Administration Interface\n(SC34-6060-03)\n-----------------------------------------------------------------------\n\nChapter 3 - PCF Commands and Responses in Groups\n\nPage 19: Add \"Refresh Queue manager\" as a supported command\n\nChapter 4 - Definitions of Programmable Command Formats\n\nPage 173: Add the following new command:\n\nRefresh Qmgr\n\nThe Refresh Qmgr (MQCMD_REFRESH_Q_MGR) command refreshes the\nExecution Controller (EC) process management rules.\n\nThis PCF is supported only on WebSphere MQ V5.3 HP NonStop Server.\n\nRequired parameters:\nNone\n\nOptional parameters:\nNone\n\nError codes\n\nThis command might return the following in the response format\nheader, in addition to the values shown on page 18.\n\nReason (MQLONG)\n\nThe value can be:\nMQRCCF_PARM_COUNT_TOO_BIG\n\nParameter count too big.\n\nWebSphere MQ for HP NonStop Server Quick Beginnings (GC34-6626-00)\n------------------------------------------------------------------\n\nChapter 1 - Planning to install WebSphere MQ for HP NonStop Server\n\nPage 1: the baseline release level for V5.3.1 on the HP Integrity NonStop\nServer is now H06.05.01\nPage 1: the typical approximate storage requirements are as follows:\n+ OSS files placed before installation:\nH-Series: 160Mb\n+ For each installation:\nH-Series: Guardian 220Mb, OSS 350Mb, Total 570Mb\n+ For each queue manager:\nH-Series: Guardian 9.5Mb, OSS 0.2Mb, Total 10Mb\nPages 2 & 3: please review the section \"Hardware and Software\nRequirements\" in these release notes for the details of all other updated\nrequirements\nChapter 3 - Installing WebSphere MQ for HP NonStop Server\n\nPage 12: Product Selection dialog. The names of the products have been\nupdated to \"WebSphere MQ V5.3.1\" and \"WebSphere MQ V5.3.1 Integrity\".\nPage 14: instmqm now includes the function of creating an automatic\nbackup archive of a successful installation, as follows:\nInstmqm has been enhanced to provide the ability to back-out an ungrade\ninstallation, and the ability to archive and restore installations\nindividually. Before instmqm starts to make changes to a system, it will\nautomatically create an archive of the current installation (OSS opt tree\nand Guardian installation subvolumes only) in the root directory\ncontaining the opt tree in OSS. If a failure occurs during installation,\nand instmqm has made changes, the user will be asked if they wish to\nrestore the installation to its original state using the archive created\nbefore changes were made. At the end of a successful installation,\ninstmqm will now automatically create a backup archive of the new\ninstallation.\n\nInstmqm also supports two new command line options to support creating\nand using backup archives independently from an installation:\n\n-b create a backup archive of the installation\n-x restore an installation from a backup archive\n\nThese options may not be combined with any other options. Both options\nrequire the user to respond to questions at the terminal.\n\nA backup archive file is an OSS pax file, created as follows:\n\n+ the Guardian PAK utility is used to create a backup of the three\nGuardian subvolumes for the installation in a file named \"WMQSAVED\"\n+ the PAK backup file is copied to the OSS opt directory of the\ninstallation that is being archived\n+ the entire OSS opt tree of the installation (which now includes\nWMQSAVED) is then archived by the OSS pax utility\n\nBackup archive files are always created in the directory that holds the\nOSS opt tree for the installation. Archive files created automatically\nby instmqm are named \"mqarchive-yymmdd-hhmmss\" where \"yymmdd\" and\n\"hhmmss\" are numeric strings of the date and time that the backup archive\nwas created - for example: \"mqarchive-061005-143606\".\n\nPage 15: instmqm has new command line options as described in these\nrelease notes for creating and restoring backup archives\nPage 17: the SnaProviderName and TcpProviderName fields of the\nQmgrDefaults stanza in the instmqm response file are used to populate\nthe proc.ini file to provide installation wide defaults for channels.\nPlease note that these fields do not get used for the default listener\nconfiguration either on the command line (runmqlsr) or in the queue\nmanager's Pathway environment. Users must manually configure the\ntransport names for all listeners.\nPage 28: in addition to the manual methods for cleaning up after a failed\ninstallation, instmqm will offer the option to restore the previous\ninstallation from a backup archive in the event of a failure while\nupgrading a V5.3 installation to V5.3.1 level. These release notes\ndescribe the additional function.\nIf an installation was initially created without SSL (selection of the\ninstallation type \"CORE\" for instmqm), the following procedure can be\nused to update the installation to include SSL components. In the\ninstructions below, <MQInstall> refers to the location of the\ninstallation that needs to be updated and <PlacedInstall> means the\nlocation of the complete set of placed files for the level of WMQ that\ncorresponds to the installation being updated. All queue managers\nmust be ended before attempting this procedure.\n1. mkdir <MQInstall>/opt/mqm/ssl\n2. chmod 775 <MQInstall>/opt/mqm/ssl\n3. cp <PlacedInstall>/opt/mqm/ssl/* <MQInstall>/opt/mqm/ssl\n4. chmod 775 <MQInstall>/opt/mqm/ssl/amq*\"...\n5. cp <MQInstall>/opt/mqm/ssl/openssl <MQInstall>/opt/mqm/bin\n6. chmod 664 <MQInstall>/opt/mqm/ssl/openssl\n7. chmod 774 <MQInstall>/opt/mqm/bin/openssl\n8. cp <MQInstall>/opt/mqm/ssl/amqjkdm0 <MQInstall>/opt/mqm/bin\n9. chmod 775 <MQInstall>/opt/mqm/bin/amqjkdm0\n10. mv <MQInstall>/opt/mqm/lib/amqcctca\n<MQInstall>/opt/mqm/lib/amqcctca_nossl\n11. mv <MQInstall>/opt/mqm/lib/amqcctca_r\n<MQInstall>/opt/mqm/lib/amqcctca_r_nossl\n12. cp <MQInstall>/opt/mqm/ssl/amqccssl <MQInstall>/opt/mqm/lib/amqcctca\n13. cp <MQInstall>/opt/mqm/ssl/amqccssl_r\n<MQInstall>/opt/mqm/lib/amqcctca_r\n14. chmod 775 <MQInstall>/opt/mqm/lib/amqcctca*\n15. The <MQInstall>/var/mqm/qmgrs/<qmgr name> directory should have an\n\nssl directory which is where you will store the certificate related\nfiles (cert.pem, trust.pem etc.)\n16. The <MQInstall>/opt/mqm/samp/ssl should exist already with the ssl\nsamples\n17. If the entropy daemon is not configured on the system this will need\nto be performed. Refer to the WMQ V53 HP NonStop System\nAdministration Chapter 11 page 165-167\n18. Install the certificates per the updated instructions, SSLupdate.pdf\nfound in <MQInstall>/opt/mqm/READMES/en_US\n\nChapter 5 - Creating a Version 5.3 queue manager from an existing Version 5.1\nqueue manager\n\nPages 37 & 38: this section is completely replaced by the documentation\nsupplement Upgmqmreadme.pdf supplied with this release.\nChapter 7 - Applying maintenance to WebSphere MQ for HP NonStop Server\n\nPages 44 & 45: the tool for applying maintenance is named \"svcmqm\" and\nnot \"installCSDxx\".\nPage 44: in step 3 of \"Transferring and preparing the PTF for\ninstallation\", the top level directory of the PTF is opt, and is not\nnamed differently for each PTF. Therefore it is important to manually\ncreate a directory specific to each PTF, download the PTF to that new\ndirectory and then expand the archive within the new directory.\nPage 44: in step 2 of \"Running the installation script for a PTF\", the\n\nsvcmqm tool has a different command line from that documented for\n\"installCSDxx\". svcmqm takes three parameters:\nsvcmqm -i installationtree -v vartree -s servicepackage\nwhere \"installationtree\" is the full path to the location of the opt/mqm\ndirectory of the installation to be updated\n\"vartree\" is the full path to the location of the var/mqm\ndirectory of the installation to be updated\n\"servicepackage\" is the full path to the location of the opt/mqm\ndirectory of the maintenance to be installed\nFor example:\nsvcmqm -i /home/me/wmq/opt/mqm -v /home/me/wmq/var/mqm\n-s /home/me/wmqfiles/opt/mqm\n\nwhich will update the installation in /home/me/wmq/opt/mqm and\n\n/home/me/wmq/var/mqm from the maintenance package in directory tree\n/home/me/wmqfiles/opt/mqm.\n\nIf either or both the \"-i installationtree\" and \"-v vartree\" parameters\nare omitted, svcmqm will use the current setting of the appropriate\nenvironment variable - either WMQNSKOPTPATH or WMQNSKVARPATH.\n\nWebSphere MQ for HP NonStop Server System Administration Guide (SC34-6625-00)\n-----------------------------------------------------------------------------\n\nChapter 2 - An introduction to WebSphere MQ administration\n\nPage 16: before running any control commands on OSS or NonStop OS it is\nnecessary to establish the environment variables for the session. When\nan installation is created a file called wmqprofile is also created in\nthe var/mqm directory that will establish the environment for an OSS\nshell. Likewise, a file is also created in the NonStop OS subvolume\ncontaining the WMQ NonStop OS samples called WMQCSTM that can be used\nto set up the appropriate environment variables for a NonStop OS TACL\nsession.\nTo establish the WMQ environment for an OSS shell session:\n\n. wmqprofile\n\nTo establish the WMQ environment for a NonStop OS TACL session:\n\nobey WMQCSTM\n\nThe same steps are required before running any applications in the\nOSS or NonStop OS environment.\n\nChapter 4 - Administering local WebSphere MQ objects\n\n\nPage 48: when creating a Process definition, the default value for\nthe APPLTYPE attribute is \"NSK\" (indicating a Guardian program)\nChapter 7 - WebSphere MQ for HP NonStop Server architecture\n\nPage 80: the MQSC command to reload the process management rules is\nREFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)\nChapter 8 - Managing scalability, performance, availability and data\nintegrity\n\nPage 104: the last paragraph of the OpenTMF section should be reworded\nas follows:\nNo special administrative actions are required for this use of TMF.\nWebSphere MQ uses and manages it automatically. You must ensure that\nthe RMOPENPERCPU and BRANCHESPERRM configuration parameters of TMF are\nset to appropriate values for your configuration. Please see Chapter 12\n\nTransactional Support - Configuring TMF for WebSphere MQ for\ninformation on how to calculate the correct values. The HP TMF Planning\nand Configuration Guide describes the subject of resource managers and\nheterogeneous transaction processing.\n\nChapter 9 - Configuring WebSphere MQ\n\nPage 119: the CPUS section should state that the default can be\noverridden using the crtmqm -nu parameter. See Chapter 18 - The control\ncommands for a description of how to use this parameter with crtmqm.\nPage 120: the section describing the ARGLIST attribute of a TCP/IP\nListener should also mention the use of the optional -u parameter to\nconfigure channels started by the listener as unthreaded processes.\nThe default is to run incoming channels as threads in an MCA process.\nPage 130: the MQSC command to reload the process management rules is\nREFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)\nPage 133: Figure 23 remove :\nOAM Manager stanza #\nOamManager:\nPage 136: the Exit properties section should state that the only\n\nsupported way of configuring and running a Cluster Workload (CLWL) Exit\nfor HP NonStop Server is in FAST mode. The CLWLMode setting in qm.ini\nis required to be set to FAST, which is the default for WebSphere MQ\non this platform.\nPage 139: the MQIBindType attribute of the Channels stanza is set by\ncrtmqm to FASTPATH. This should not be changed, except under the\ndirection of IBM Service.\nPage 140: the AdoptNewMCA=FASTPATH option is always required for\nthis platform in order for the adoption of MCAs to be effective. The\n\"Attention!\" box after the description of the FASTPATH option should\nbe ignored.\nPage 140: add the following description of the ClientIdle attribute:\nClientIdle=seconds\n\nClientIdle specifies the number of seconds of inactivity to permit\nbetween client application MQI calls before WebSphere MQ terminates\nthe client connection. The default is to not terminate client\nconnections however long they remain inactive. When a client connection\nis terminated because of idle activity, the client application receives\na connection broken result (2009) on its next MQI call.\n\nChapter 11 - Working with the WebSphere MQ Secure Sockets Layer (SSL) support\n\nA documentation supplement has been written to replace the sections on\nPage 170 (Preparing the queue manager's SSL files) to Page 176 (Building\nand verifying the sample configuration) because of changes to the files\nthat WebSphere MQ uses to hold certificates. The documentation supplement\nis called SSLupdate.pdf, and can be found in the opt/mqm/READMES/en_US\ndirectory of an installation.\n\nChapter 12 - Transactional Support\n\nPage 185: The descriptions of the TMF attribute RMOPENPERCPU in the\n\nResource manager configuration section is modified as follows:\nRMOPENPERCPU\n\nEach WebSphere MQ thread or process that handles transactions has\nan open of a Volatile Resource Manager in the CPU it runs in. In\naddition, each application thread or process using the MQI also has\nan open. The minimum requirement for this configuration parameter\n\nis therefore the sum of:\n+ all Queue Server processes in that CPU\n+ all LQMA and MCA threads running in that CPU\n+ all MQI application threads running in that CPU\n+ 10 (to account for miscellaneous queue manager processes that\ncould be running in that CPU)\nYou should calculate the peak values of these numbers across all CPUs\nand add a safety margin to arrive at the correct value for your system.\nThe HP default value of 128 for this parameter is often suitable for\nsmall configurations, but unsuitable for medium or large ones.\n\n\nPage 186: add the following paragraph to the Troubleshooting section\nfor Configuring TMF:\nIf the RMOPENPERCPU value is not configured to allow sufficient opens\nof resource managers in a CPU, WebSphere MQ connections will fail with\nan unexpected return code, and FDCs will be generated reporting an\nerror with the TMF_VOL_RM_OPEN_. The workaround is to distribute\napplications and queue manager processes in the CPU that exceeds\nthe limit to other CPUs. The correct remedy is to schedule an outage\nand modify the TMF configuration.\n\nPage 186: add the following paragraph to the Troubleshooting section\nfor configuring TMF:\nIf TMF is stopped, or new transactions are disabled, and WMQ requires\nan internal \"unit of work\" (TMF transaction) to perform an update to\na protected resource requested by an MQI call, that call will fail\nand the reason code returned will be MQRC_UOW_NOT_AVAILABLE (2255).\n\nNote that in some cases, updates to protected resources may be\nrequired by MQI operations do not directly perform messaging\noperations - for example, MQOPEN of a model queue that creates a\npermanent dynamic queue. If MQI calls return MQRC_UOW_NOT_AVAILABLE,\ncheck the status of the TMF subsystem to determine the likely cause.\n\nChapter 14 - Process Management\n\nPage 197: the MQSC command to reload the process management rules is\nREFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)\n\nPage 200 and 204: the default value for the maximum number of unthreaded\nagents is now 200. The default value for the maximum number of threaded\nagents is now 20. the default value for the maximum use count for\nthreaded agents is now 100.\n\nPage 203: add a new paragraph titled \"Pathway\":\nPathway\nThis stanza contains 3 attributes:-\n- ProcessName\n- DynamicProcessName\n- Hometerm\nProcessName is the name of the Queue Managers pathmon process.\nIf the -np option was specified at queue Manager creation, \nthe value of ProcessName will be set to the value of that option \nwhen the qmproc.ini file is created\nIf DynamicProcessName is set to Yes, the system will generate a name\nfor the pathmon process at the time the Queue Manager starts.\nIf the value is set to no, the value of the ProcessName attribute\nwill determine the pathmon process name for the queue manager \nHometerm specifies the value of the hometerm attribute for the Queue \nManager pathmon process \nIf the -nh opton was specified at queue manager creation, the \nvalue of Hometerm will be set to the value of that option, \notherwise the default of $ZHOME will be used.\n\nPage 204: the \"valid attribute values\" for the attribute \"ExecutableName\"\nshould be stated as \"File name part only of the program to run for the\nLQMA or MCA process\".\n\nPages 203 - 205, Table 20: Process Management: Keyword definition Summary\nThere are a number of errors in the Process Management Keyword\ndefinition table:\n\n1. Environment variables:\nENVxx should be Envxx\n\n2. Executable Name to Match:\nExecNameMatch should be ExeNameMatch\n\n3. Fail if CPU unavailable:\nFailOnCPUunavail should be FailOnCPUUnavail\n\n4. Preferred number of Threaded Agents:\nPreferedThreadedAgents should be PreferredThreadedAgents\n\nDefault values:\n\n5. MaxThreadedAgents: change from 10 to 20\n\n6. MaxUnthreadedAgents: change from 20 to 200\n\n7. MaxThreadedAgentUse: change from 10 to 100\n\nPages 199 - 201, Table 16. Process management: agent attributes\n\nThe same default value changes are required:\n\n1. Maximum number of unthreaded agents: 200\n2. Maximum number of threaded agents: 20\n3. Maximum reuse count for threaded agents: 100\n\nChapter 15 - Recovery and restart\n\nPage 216: Configuring WebSphere MQ, NonStop RDF, and AutoSYNC to support\ndisaster recovery\nTo configure RDF to work with a existing WMQ V53 queue manager:\nEnd the WMQ V53 queue manager.\nUsing the HP BACKUP or PAK utility specifying the AUDITED option\nBackup the primary site Guardian WMQ queue manager subvolume.\nUsing the HP RESTORE or UNPAK utility specifying the AUDITED option\nRestore the files on the backup site.\nEnsure that on the backup system that the alternate key file\nattribute (ALTKEY) for files amqcat and amqpdb of each queue\nmanager are set to the correct (backup system) node name\nPage 217: the example of the altmqfls command to set the RDF\ncompatibility mode for large persistent messages is correct but too\nsimplistic. Please use care when using altmqfls to set the queue options\n\n(--qsoptions parameter) and refer to the reference section for the\ncontrol commands for a complete description of using this option.\nPage 217: the bullet point that describes the configuration of AutoSYNC\nfilesets is incorrect when it states that NO ALLSYMLINKS should be\nspecified. Replace sub-bullet item number 2 with the following text:\n2. The entire queue manager OSS directory structure\nvar_installation_path/var/mqm/qmgrs/qmname.\n\nYou must specify the absolute path name of the queue manager's\ndirectory. Specify the ALLSYMLINKS option for this fileset to\nensure that AutoSYNC correctly synchronizes the symbolic link\n(G directory) in the queue manager's directory to the NonStop OS queue\nmanager's subvolume on the backup system.\n\nChapter 16 - Troubleshooting\n\nPage 230: after the section \"Is your application or system running\nslowly?\", insert the following new section:\nAre your applications or WebSphere MQ processes unable to connect?\n\nIf connection failures are occurring:\n\nis the User ID under which the application runs authorized to\nuse this queue manager?\nare SAFEGUARD permissions preventing read access to the WebSphere\nMQ installation files by the User ID running the application?\nare the environment variables established for the application\nprocess, so that the correct installation of WebSphere MQ is being\nused?\nif necessary, has the application been relinked or rebound with\nany static MQI libraries that it uses?\nis a resource problem preventing the queue manager from allowing\nthe connection? Review the troubleshooting section under TMF\nConfiguration on Page 185 and 186 for information about the\nRMOPENSPERCPU TMF attribute.\n\nChapter 18 - The control commands\n\nPage 93: The example of the --resetmeasure option is missing a mandatory\nparameter having the value \"YES\" or \"NO\". The paragraph on page 93 describing\nthe --resetmeasure option should be replaced with the following\n\n\"The queue server can maintain the Measure counter only if it is included \nin an active measurement. If it is not included in an active measurement, \nand messages are put in the queue and removed from the queue, the value \nof the counter will no longer represent the current depth of the queue. \nIf the counter is subsequently included in an active measurement, you can \ncause the queue server to reset the Measure counter to the current depth \nof the queue by using the --resetmeasure parameter on the altmqfls command, \nas follows: altmqfls --qmgr QMGR --type QLOCAL --resetmeasure TEST.QUEUE YES\"\n\nPage 244: The mandatory YES|NO parameter is missing from the syntax diagram\n\nPage 247: The mandatory YES|NO parameter is missing from the description\nof the option\n\nPage 243: the control commands for the Publish / Subscribe broker are\nnot referenced here. Refer to the WebSphere MQ V6.0 Publish/Subscribe\nUser Guide and the documentation supplement for Publish/Subscribe on\nHP NonStop Server - Pubsub.pdf.\nPage 255: if the OSS environment variable or Guardian PARAM MQPATHSEC\nis defined and set to one of the standard NonStop OS security attributes\n(A, N, C, G, O, or U) when crtmqm is run, the default PATHWAY SECURITY\nattribute value of \"G\" will be overridden by the value of the environment\nvariable / PARAM. This can be used to restrict access to the queue\nmanager's Pathway environment. The current Pathway attributes can be\ndisplayed in PATHCOM using the INFO PATHWAY command.\nPage 255: the -nu parameter for setting the default CPUS attribute\nin Pathway serverclasses does not accept all the values that Pathway\nallows for this attribute. The only accepted values (and the result in\nPathway configuration) are of the form:\n-nu value Pathway CPUS attribute\n-------- ---------------------\n-nu a CPUS (a:0)\n-nu a:b CPUS (a:b)\n\nMore complex Pathway serverclass CPUS attributes settings must be\nconfigured after the queue manager has been created, using the HP\nPATHCOM utility.\n\nChapter 23 - API exits\n\nPages 373-375: please review the updates to this section in the\ndocumentation supplement for API exits for HP NonStop Server called\nExits.pdf. This supplement has been extensively revised for V5.3.1.1\nto clarify the requirements and process for creating and integrating\nexits with WebSphere MQ.\n\nAppendix B - Directory structure\n\nPages 430 and 431: there is a new G symbolic link to the Guardian\nsubvolume containing the product executables in\n.../var/mqm/qmgrs/@SYSTEM\nPage 431: the content of the ssl directory is revised with V5.3.1.1\nas follows:\nThis directory contains up to four files used by the SSL support:\n\nThe queue manager certificate and private key store (cert.pem)\nThe trusted certificates store (trust.pem)\nThe pass phrase stash file for the queue managers certificate\nand private key store (Stash.sth)\nThe certificate revocation list file (optional - crl.pem)\n\nAppendix F - Environment variables\n\nPage 446: there are several environment variables that are used by the\nGuardian sample build scripts to locate the header files and the\nlibraries. Suitable settings for these are established in the\nWMQCSTM file (in the Guardian samples subvolume). The environment\nvariables, and their meanings, are:\nMQNSKOPTPATH^INC^G include file/header subvolume\nMQNSKOPTPATH^BIN^G binaries subvolume\nMQNSKOPTPATH^LIB^G binaries subvolume\nMQNSKOPTPATH^SAMP^G samples subvolume\n\nIn addition, an HP environment variable is also required (and set in\nWMQCSTM) that locates the OSS DLLs for dynamic loading from Guardian.\nThe environment variable is ^RLD^FIRST^LIB^PATH.\n\nPage 468: add after the \"Queue Server Tuning parameters\" section\n\nQueue Manager Server tuning parameters\n\nMQQMSHKEEP If this ENV is set for the MQS-QMGRSVR00 serverclass, its value\nspecifies a numeric value in seconds to override the default housekeeping\ninterval of the queue manager server. The default interval is 60 seconds.\nThe housekeeping interval controls how frequently the queue manager\nserver generates expiration reports. The permitted range of values is 1-300.\nValues outside this range will be ignored and the default value will be used.\n\nMQQMSMAXMSGSEXPIRE If this ENV is set for the MQS-QMGRSVR00 serverclass,\nits value specifies a numeric value to override the default maximum number\nof expiration report messages that are generated during housekeeping\noperations by a queue manager server. The default maximum number of expiration\nmessages generated is 100. The permitted range of values is 1-99999. Values\noutside this range will be ignored and the default value will be used.\n\n\nAppendix H - Building and running applications\n\nBuilding C++ applications,\n\nTable 47 - there is no multi-threaded library support in\nGuardian so there should not be an entry for a\nmulti-threaded guardian library\n\nTable 48 - the name of this table should be \"Native non-PIC\"\n\nReferences to G/lib symbolic links have changed with WMQ 5.3.1 to lib/G\n\nNote that the MQNSKVARPATH and MQNSKOPTPATH environment variables must\nbe established in the environment, before an application starts up.\nThey cannot be programmatically set once a program is running by using\nputenv().\n\nPage 461: Building COBOL applications\n\nAdd the following text:\n\n\"In both the OSS and Guardian environment, the CONSULT compiler\ndirective referencing the MQMCB import library must now be used along\nwith correct linker options. Refer to the BCOBSAMP TACL script described\nin Appendix I for more information.\"\n\nAppendix I - WebSphere MQ for NonStop Server Sample Programs\n\nPages 465-466: The section \"TACL Macro file for building C Sample Programs\"\nis replaced by the following:\n\nBCSAMP - Build a C-Language Sample.\n\nThis TACL script will compile and link a C-language sample into an\nexecutable program. The script expects that the WMQ environment has\nbeen established using WMQCSTM.\n\nBCSAMP usage:\n\nBCSAMP <type> <source>\n\n<type> The type of executable program that should be built.\n\nValid values are:\n\npic A native PIC program\ntns A non-native TNS program\n\n<source> The filename of the source module to be compiled and linked\n\nThe <source> filename should end with a 'C'. The final program name is\nthe same as the source filename with the trailing 'C' removed.\n\nPage 467: The section \"TACL Macro files for building COBOL Sample\nPrograms\" is replaced by the following:\n\nBCOBSAMP - Build a COBOL Sample.\n\nThis TACL script will compile and link a COBOL sample into an executable\nprogram. The script expects that the WMQ environment has been established\nusing WMQCSTM.\n\nBCOBSAMP usage:\n\nBCOBSAMP <type> <source>\n\n<type> The type of executable program that should be built.\n\nValid values are:\n\npic A native PIC program\ntns A non-native TNS program\n\n<source> The filename of the source module to be compiled and linked\n\nThe <source> filename should end with an 'L'. The final program name is\nthe same as the <source> filename with the trailing 'L' removed.\n\nPage 469: The section \"TACL Macro files for building TAL sample programs\"\nis replaced by the following:\n\nBTALSAMP - Build a TAL Sample.\n\nThis TACL script will compile and link a TAL sample into an executable\nprogram. The script expects that the WMQ environment has been established\n\nusing WMQCSTM.\n\nBTALSAMP usage:\n\nBTALSAMP <source>\n\n<source> The filename of the source module to be compiled and linked\n\nThe final program name is the same as the <source> filename with the\ntrailing character removed.\n\nAppendix J - User exits\n\nrefer to the documentation supplement Exits.pdf for updated information\nabout configuring and building user exits. This supplement has been\nextensively revised for V5.3.1.1 to clarify the requirements and process\nfor creating and integrating exits with WebSphere MQ.\nThe description of compile options for PIC unthreaded, threaded and\nGuardian dlls in this document is incorrect. The option specified as\n\"-export all\" should be \"-export_all\".\n\nAppendix K - Setting up communications\n\nPage 482: The TCP/IP keep alive function\n\nBy default, the TCP/IP keep alive function is not enabled. To enable\nthis feature, set the KeepAlive=Yes attribute in the TCP Stanza in the\nqm.ini file for the queue manager.\nIf this attribute it set to \"yes\" the TCP/IP subsystem checks periodically\nwhether the remote end of a TCP/IP connection is still available. If it is\nnot available, the channel using the connection ends.\nIf TCP stanza KeepAlive attribute is not present or is set to \"No\", the\nTCP/IP subsystem will not check for disconnection of the remote end.\n\nChapter 9 \"Configuring WebSphere MQ\" page 140 describes the TCP stanza\nattributes.\n\nAPAR IC58859: wmqtrig script\nThe wmqtrig script processing the -c option, for triggering a TACL macro/script\nfile, will not normally propagate the TMC data to the macro/script file.\nSome applications may need the TMC for processing. A switch used in conjunction\nwith the -c option, -5.1, has been added which will pass the TMC data to a TACL\nmacro/script file with the wmqtrig script. Define the APPLICID attribute with\nthe -5.1 switch, for example:\nAPPLICID(/wmq/opt/mqm/bin/wmqtrig -5.1 -c \\$data06.test.trigmac)\n\nSSLupdate.pdf page 7\n-----------------------------------------------------------------------------\n\nThe SSLupdate.pdf document was first released with Fixpack 5.3.1.1\n\nThe SSL test scripts expect that a default TCP/IP process ($ZTC0) is\nconfigured on the system to be used during the test. The configuration\nwill need modification if a non-default TCP/IP process does not exist\non the system or another TCP/IP process is used to communicate with the\npartner system. The ALICE.sh and/or BOB.sh scripts that setup of the\nlistener (runmqlsr) will need modification to add the -g option to use a\nnon-default TCP/IP process.\n\nCONTACTING IBM SOFTWARE SUPPORT\n===============================\n\nIBM Software Support provides assistance with product defects. You might\nbe able to solve you own problem without having to contact IBM Software\nSupport. The WebSphere MQ Support Web page\n(http://www.ibm.com/software/integration/wmq/support/ [http://www.ibm.com/software/integration/wmq/support/]) contains\nlinks to a variety of self-help information and technical flashes. The\nMustGather Web page\n(http://www-01.ibm.com/support/docview.wss?uid=swg21229861 [http://www-01.ibm.com/support/docview.wss?uid=swg21229861])\ncontains diagnostic hints and tips that will aid in diagnosing and\nsolving problems, as well of details of the documentation required by\nthe WebSphere MQ support teams to diagnose problems.\n\nBefore you \"Submit your problem\" to IBM Software Support, ensure\nthat your company has an active IBM software maintenance contract, and\n\nthat you are authorized to submit problems to IBM. The type of software\nmaintenance contract that you need depends on the type of product you\nhave:\n\nFor IBM distributed software products (including, but not limited to,\nTivoli(R), Lotus(R), and Rational(R) products, as well as DB2(R) and\nWebSphere products that run on Windows or UNIX(R) operating systems),\nenroll in Passport Advantage(R) in one of the following ways:\nOnline: Go to the Passport Advantage Web site at\nhttp://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home [http://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Home],\n\nand click \"How to Enroll\".\nBy phone: For the phone number to call in your country, go to the \"Contacts\"\npage of the IBM Software Support Handbook at\nwww.ibm.com/support/handbook [www.ibm.com/support/handbook], click 'contacts' and then click the name of \nyour geographic region.\nFor customers with Subscription and Support (S & S) contracts, go to the\nSoftware Service Request Web site at\nhttp://www.ibm.com/support/servicerequest [http://www.ibm.com/support/servicerequest].\nFor customers with IBMLink(TM), CATIA, Linux(R), S/390(R), iSeries(TM),\npSeries(R), zSeries(R), and other support agreements, go to the IBM Support\nLine Web site at\nhttp://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006 [http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006].\nFor IBM eServer(TM)) software products (including, but not limited to,\nDB2(R) and WebSphere products that run in zSeries, pSeries, and iSeries\nenvironments), you can purchase a software maintenance agreement by working\ndirectly with an IBM sales representative or an IBM Business Partner.\nFor more information about support for eServer software products, go to the\nIBM Technical Support Advantage Web site at\nhttp://www.ibm.com/servers/eserver/techsupport.html [http://www.ibm.com/servers/eserver/techsupport.html].\n\nIf you are not sure what type of software maintenance contract you need,\ncall 1-800-IBMSERV (1-800-426-7378) in the United States. From other\ncountries, go to the \"Contacts\" page of the IBM Software Support\nHandbook at www.ibm.com/support/handbook [www.ibm.com/support/handbook], click 'contacts' and then \nclick the name of your geographic region. for phone numbers of people\nwho provide support for your location.\n\nTo contact IBM Software support, follow these steps:\n\n1. \"Determine the business impact of your problem\"\n2. \"Describe your problem and gather background information\"\n3. \"Submit your problem\"\n\nDetermine the business impact of your problem\n\n\nWhen you report a problem to IBM, you are asked to supply a severity\nlevel. Therefore, you need to understand and assess the business impact\nof the problem that you are reporting. Use the following criteria:\n\n---------------------------------------------------------------+\n\nSeverity 1 The problem has a critical\nbusiness impact: You are unable\nto use the program, resulting in\na critical impact on operations.\nThis condition requires an\nimmediate solution.\n\n---------------------------------------------------------------+\n\nSeverity 2 This problem has a significant\nbusiness impact: The program is\nusable, but it is severely\nlimited.\n\n---------------------------------------------------------------+\n\nSeverity 3 The problem has some business\nimpact: The program is usable,\nbut less significant features\n(not critical to operations) are\nunavailable.\n\n---------------------------------------------------------------+\n\nSeverity 4 The problem has minimal business\nimpact: The problem causes\nlittle impact on operations, or\na reasonable circumvention to\nthe problem was implemented.\n\n---------------------------------------------------------------+\n\nDescribe your problem and gather background information\n\nWhen describing a problem to IBM, be as specific as possible. Include\nall relevant background information so that IBM Software Support\nspecialists can help you solve the problem efficiently. See the\nMustGather Web page\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21229861 [http://www-01.ibm.com/support/docview.wss?uid=swg21229861] for\ndetails of the documentation required. To save time, know the answers to\nthese questions:\n\nWhat software versions were you running when the problem occurred?\nDo you have logs, traces, and messages that are related to the problem\nsymptoms? IBM Software Support is likely to ask for this information.\nCan you re-create the problem? If so, what steps do you perform to\nre-create the problem? Did you make any changes to the system? For example,\ndid you make changes to the hardware, operating system, networking software,\nor other system components? Are you currently using a workaround for the\nproblem? If so, please be prepared to describe the workaround when you\nreport the problem.\n\nSubmit your problem\n\nYou can submit your problem to IBM Software Support in one of two ways:\n\nOnline: Go to the Submit and track problems tab on the IBM Software Support\nsite at http://www.ibm.com/software/support/probsub.html [http://www.ibm.com/software/support/probsub.html]. Type your\ninformation into the appropriate problem submission tool.\nBy phone: For the phone number to call in your country, go to the \"Contacts\"\npage of the IBM Software Support Handbook at\nwww.ibm.com/support/handbook [www.ibm.com/support/handbook], click 'contacts' and then click the name \nof your geographic region.\n\nIf the problem you submit is for a software defect or for missing or\ninaccurate documentation, IBM Software Support creates an Authorized\nProgram Analysis Report (APAR). The APAR describes the problem in\ndetail. Whenever possible, IBM Software Support provides a workaround\nthat you can implement until the APAR is resolved and a fix is\ndelivered. IBM publishes resolved APARs on the Software Support Web site\ndaily, so that other users who experience the same problem can benefit\nfrom the same resolution.\n\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++ ++\n++ COPYRIGHT, NOTICES AND TRADEMARKS ++\n++ ++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\n* IBM WebSphere MQ for HP NonStop Server, Version 5.3.1.12\n* Statement: Licensed Materials - Property of IBM\n* (c) Copyright IBM Corp. 1999, 2016\n* All rights reserved.\n* U.S. Government Users Restricted Rights - use,\n* duplication or disclosure restricted by GSA\n* ADP Schedule Contract with IBM Corp.\n* Status: Version 5.3.1.12\n* Created: May 20, 2016\n\nNOTICES AND TRADEMARKS\n======================\n\nIBM may not offer the products, services, or features discussed in this\ndocument in all countries. Consult your local IBM representative for\ninformation on the products and services currently available in your\narea. Any reference to an IBM product, program, or service is not\nintended to state or imply that only that IBM product, program, or\nservice may be used. Any functionally equivalent product, program, or\nservice that does not infringe any IBM intellectual property right may\nbe used instead. However, it is the user's responsibility to evaluate\nand verify the operation of any non-IBM product, program, or service.\n\nIBM may have patents or pending patent applications covering subject\nmatter described in this document. The furnishing of this document does\nnot give you any license to these patents. You can send license\ninquiries, in writing, to:\nIBM Director of Licensing\n\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\n\nFor license inquiries regarding double-byte (DBCS) information, contact\nthe IBM Intellectual Property Department in your country/region or send\ninquiries, in writing, to:\nIBM World Trade Asia Corporation\nLicensing\n2-31 Roppongi 3-chome, Minato-ku\nTokyo 106, Japan\n\nThe following paragraph does not apply to the United Kingdom or any\nother country/region where such provisions are inconsistent with local\nlaw: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS\nPUBLICATION \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR\nIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\nNON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.\nSome states do not allow disclaimer of express or implied warranties in\ncertain transactions; therefore, this statement may not apply 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 may\nmake improvements and/or changes in the product(s) and/or the program(s)\ndescribed in this publication at any time without notice.\n\nAny references in this information to non-IBM Web sites are provided for\nconvenience only and do not in any manner serve as an endorsement of\nthose Web sites. The materials at those Web sites are not part of the\nmaterials for this IBM product, and use of those Web sites is at your\nown risk.\n\nIBM may use or distribute any of the information you supply in any way\nit believes appropriate without incurring any obligation to you.\n\nLicensees of this program who wish to have information about it for the\npurpose of enabling: the exchange of information between\nindependently created programs and other programs (including this one)\nand (ii) the mutual use of the information that has been exchanged,\nshould contact:\nIBM Canada Limited\nOffice of the Lab Director\n8200 Warden Avenue\nMarkham, Ontario\nL6G 1C7\nCANADA\n\nSuch information may be available, subject to appropriate terms and\nconditions, including in some cases payment of a fee.\n\nThe licensed program described in this document and all licensed\nmaterial available for it are provided by IBM under terms of the IBM\nCustomer Agreement, IBM International Program License Agreement, or any\nequivalent agreement between us.\n\nAny performance data contained herein was determined in a controlled\nenvironment. Therefore, the results obtained in other operating\nenvironments may vary significantly. Some measurements may have been\nmade on development-level systems, and there is no guarantee that these\nmeasurements will be the same on generally available systems.\nFurthermore, some measurements may have been estimated through\nextrapolation. Actual results may vary. Users of this document should\nverify the applicable data for their specific environment.\n\nInformation concerning non-IBM products was obtained from the suppliers\n\nof those products, their published announcements, or other publicly\navailable sources. IBM has not tested those products and cannot confirm\nthe accuracy of performance, compatibility, or any other claims related\nto non-IBM products. Questions on the capabilities of non-IBM products\nshould be addressed to the suppliers of those products.\n\nAll statements regarding IBM's future direction or intent are subject to\nchange or withdrawal without notice, and represent goals and objectives\nonly.\n\nThis information may contain examples of data and reports used in daily\nbusiness operations. To illustrate them as completely as possible, the\nexamples include the names of individuals, companies, brands, and\nproducts. All of these names are fictitious, and any similarity to the\nnames and addresses used by an actual business enterprise is entirely\ncoincidental.\n\nThis information may contain sample application programs, in source\nlanguage, which illustrate programming techniques on various operating\nplatforms. You may copy, modify, and distribute these sample programs in\nany form without payment to IBM for the purposes of developing, using,\nmarketing, or distributing application programs conforming to the\napplication programming interface for the operating platform for which\nthe sample programs are written. These examples have not been thoroughly\ntested under all conditions. IBM, therefore, cannot guarantee or imply\nreliability, serviceability, or function of these programs.\n\nTrademarks\n\nThe following terms are trademarks of International Business\nMachines Corporation in the United States, other countries,\nor both: DB2, eServer, IBM IBMLink, iSeries, Lotus, MQSeries, pSeries,\nPassport Advantage, Rational, s/390, SupportPac, Tivoli, WebSphere, zSeries.\n\nUNIX is a registered trademark of The Open Group in the United States\nand other countries.\n\nMicrosoft Windows is a trademark or registered trademark of Microsoft\nCorporation in the United States, other countries, or both.\n\nJava and all Java-based trademarks and logos are trademarks or registered\ntrademarks of Sun Microsystems, Inc. in the United States, other countries,\nor both.\n\nLinux is a trademark of Linus Torvalds in the United States, other\ncountries, or both.\n\nOther company, product or service names may be the trademarks\nor service marks of others."
}
] |
DEV_Q109 | Help with Security Bulletin: Authentication vulnerability affects IIB V10.0.0.4 onwards (CVE-2016-8918 )
I need to understand details regarding Security Bulletin: Authentication vulnerability affects IBM Integration Bus V10.0.0.4 onwards (CVE-2016-8918 ). Where can I find this information? | CVEID: CVE-2016-8918 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8918]
DESCRIPTION: In non-default configurations, IBM Integration Bus could allow a remote user to authenticate without providing valid credentials.
CVSS Base Score: 5.9
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118528 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118528] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) | false | [
{
"filename": "swg21995079.txt",
"text": "Title: IBM Security Bulletin: Authentication vulnerability affects IBM Integration Bus V10.0.0.4 onwards (CVE-2016-8918 ) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n Web user accounts can be authenticated against an LDAP server, in IBM Integration Bus V10.0.0.4 and later versions. However, under some circumstances it is possible for a remote user to be authenticated without providing valid credentials. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-8918 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-8918]\nDESCRIPTION: In non-default configurations, IBM Integration Bus could allow a remote user to authenticate without providing valid credentials.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/118528 [https://exchange.xforce.ibmcloud.com/vulnerabilities/118528] 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:H/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V10\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10 IT15920 The APAR is available in Fix Pack 10.0.0.7 \nhttps://www-304.ibm.com/support/docview.wss?uid=swg24043068 [https://www-304.ibm.com/support/docview.wss?uid=swg24043068] \n\nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\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\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 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 2 Dec 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. \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 WMB IIB"
}
] |
DEV_Q110 | Why does our Websphere application server hang when we apply Microsoft patch on our database server?
Why does our Websphere application server hang when we apply Microsoft patch on our database server? | Immediately purge the pool by invoking the purgePoolContents operation of the data source MBean with the immediate option:
Using Jacl:
$AdminControl invoke $ds purgePoolContents immediate
Using Jython:
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. | false | [
{
"filename": "swg21220832.txt",
"text": "Title: IBM Purging the connection pool of a WebSphere Application Server data source using the data source MBean - United States\n\nText:\nwas 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.\n\n\nRESOLVING 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: \n\n 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. \n * 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.\n \n \n\n\nExamples 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\")\n \n \n 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\")\n \n \n\nIf 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"
}
] |
DEV_Q111 | StaleConnectionException errors with BPM databases
There is much published documentation about stale connections to databases on the web, and yet stale connections continue to be a very common problem, at least with BPM databases. The condition can manifest itself in different ways. The most common experience of a stale connection is from error messages in the log or FFDCs that contain "StaleConnectionException". | - | true | [] |
DEV_Q112 | Why does nco_confpack -export fail with the message "Tool in menu but not found"?
I tried to export OMNIbus configuration using nco_confpack command and I get the following message:
Tool in menu but not found, menu: AlertsMenu, tool: Close
I've also tried using it with -list command and I get the same error. | Recreate the tool and associate it with the menu and try to run the command again. | false | [
{
"filename": "swg21672071.txt",
"text": "Title: IBM Netcool conf pack command - United States\n\nText:\ntool; menu; not found; confpack TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Migrating to a new version of Omnibus, running nco_confpack:\n\n$OMNIHOME/bin/nco_confpack -list -server NCOMS -user ncadmin -file /tmp/nco_confpack.list \n\nReceived this error: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY. \n\nSYMPTOM\nThe command fails and the following error is received: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY.\n\n\nCAUSE\nThe menu AlertsMenu has a tool in it called CLEAR_LWY, however the tool no longer exists.\n\nRESOLVING THE PROBLEM\nRecreate the tool and associate it with the menu and try to run the command again."
}
] |
DEV_Q113 | How to access Rule Team Server or Rule Execution Server on WAS 7 over HTTPS?
When trying to connect to Rule Team Server or Rule Execution Server on WebSphere Applicaiton Server (WAS) 7.0 over HTTPS, why do I still get an SSLHandshakeException after setting the property "ilog.rules.res.allowSelfSignedCertificate"to "true" ? | - | true | [] |
DEV_Q114 | Any difference between DB2 z/OS V9.1 + IBM Cobol and DB2 LUW V10.5 FP7 + MF Cobol?
We are planning below migration.
[Current]
DB2 z/OS V9.1 + IBM Cobol
[New]
DB2 AESE V10.5 FP7 / AIX V7.1 + Micro Focus Cobol (MF Cobol)
Any known limitation or things what we need to concern?
| DB2 LUW precompile, prep write different code to DB2 z/OS? | false | [
{
"filename": "swg21989702.txt",
"text": "Title: IBM DB2 LUW precompile, prep may write different code to DB2 z/OS - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why does DB2 LUW precompile, prep write different code to DB2 z/OS? \n\nCAUSE\nIt is an expected current DB2 LUW behavior.\n\nANSWER\nHere is an example. \n\n------------------------------ \n<Before PRECOMPILE> \n01 BLOB1 USAGE ID SQL TYPE IS BLOB(10485760). \n\n<PRECOMPILE on z/OS> \n01 BLOB1. \n02 BLOB1-LENGTH PIC S9(9) COMP. \n02 BLOB1-DATA. \n49 FILLER PIC(10485760). \n\n<PRECOMPILE on LUW> \n01 BLOB1. \n02 BLOB1-LENGTH PIC S9(9) COMP. \n02 BLOB1-DATA PIC(10485760). \n------------------------------ \n\nAs above, we see DB2 z/OS has below two lines:\n------------------------------ \n02 BLOB1-DATA. \n49 FILLER PIC(10485760). \n------------------------------ \nbut DB2 LUW writes only one line as below for above two lines part.\n------------------------------ \n02 BLOB1-DATA PIC(10485760). \n------------------------------ \n\nIt is an expected current DB2 LUW behavior and we don't have any hidden \noption to generate the cobol declarations similar to z/OS precompiler.\n\nNote:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following above scenario.\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/]\n\nRELATED INFORMATION\n PRECOMPILE command [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0001964.html]\nCOBOL compiler configurations [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.apdv.embed.doc/com.ibm.db2.luw.apdv.embed.doc-gentopic3.html]"
}
] |
DEV_Q115 | Help with Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031)
I need to understand details regarding Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031). Where can I find this information? | - | true | [] |
DEV_Q116 | Upgrading from ibm bpm 8.5 to ibm bpm 8.5.5
Hi there,
I was wondering if it is possible to upgrade from ibm bpm 8.5 to 8.5.5 ? is this possible? please suggest. thanks
| V8.5 Refresh Pack 5 is intended to be used on IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, and IBM Business Process Manager Advanced - Process Server installations. | false | [
{
"filename": "swg27042065.txt",
"text": "Title: IBM Installation instructions for IBM Business Process Manager Version 8.5 Refresh Pack 5 - United States\n\nText:\n8.5.5 Installation Instructions; install; 8.5 refresh pack PRODUCT README\n\nABSTRACT\n This document provides instructions for installing V8.5 Refresh Pack 5 for the IBM Business Process Manager products. The same instructions should be used to update the Process Center and the Process Server. \n\nCONTENT\n\n\nTAB NAVIGATION\n * Refresh Pack download [http://www.ibm.com/support/docview.wss?uid=swg24037683 ]\n * Refresh pack installation instructions [http://www.ibm.com/support/docview.wss?uid=swg27042065]- selected tab,\n * Profile upgrade instructions [http://www.ibm.com/support/docview.wss?uid=swg27042066]\n * Recommended interim fixes [http://www.ibm.com/support/docview.wss?uid=swg24037612]\n\nThis refresh pack is a cumulative maintenance package for a specific product and applies to all distributed operating systems. It is a single package that bundles a number of individual fixes.\n\nV8.5 Refresh Pack 5 is intended to be used on IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, and IBM Business Process Manager Advanced - Process Server installations.\n\nBy installing V8.5 Refresh Pack 5, you will raise the fix level of your product, either IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server, to Version 8.5.5.\n\nNote: You can roll out maintenance incrementally in an IBM Business Process Manager installation that consists of a Process Center and multiple Process Servers. This approach allows you to continually run production applications during the upgrade and regression test period. See [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-mp&topic=trun_svr_conf_backup] Performing a rolling upgrade [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.doc/topics/tmig_rolling_upgrade.html] in the product documentation.\n\nTable of Contents \n\n * Problems addressed in this refresh pack \n * Refresh pack prerequisites \n * Installing the refresh pack \n * Upgrade instructions for installations with existing profiles \n * Installing V8.5 Refresh Pack 5 \n * Upgrading the Process Designer \n * Refresh pack install verification \n * Rolling back V8.5 Refresh Pack 5 \n * Reference \n * Trademarks and service marks\n\n\n\n© Copyright International Business Machines Corporation 2014. All rights reserved. \nUS Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. \n\n \n\nPROBLEMS ADDRESSED IN THIS REFRESH PACK\n\n\nThe fixes addressed in V8.5 Refresh Pack 5 are explained in the Fix List for the IBM Business Process Manager Version 8.5 products [http://www.ibm.com/support/docview.wss?uid=swg27039722]document. \nBack to top\n\n\nRefresh pack prerequisites\n\nTo use this refresh pack, you must have Version 8.5 for the IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server product installed.\n\nYou must have WebSphere Application Server V8.5.5 Fix Pack 2 [http://www.ibm.com/support/docview.wss?uid=swg24037250] installed or you must install WebSphere Application Server V8.5.5 Fix Pack 2 during the upgrade process. This fix pack must be downloaded using FTP. In addition, you must install the fix pack image for all operating systems and platforms.\n\nWhen you decompress the following two files to the same location, it creates the full WebSphere Application Server V8.5.5 Fix Pack 2 repository that includes all WebSphere Application Server packages for all supported operation systems and architectures: \n\n * 8.5.5-WS-WAS-FP0000002-part1.zip 0.814 GB \n * 8.5.5-WS-WAS-FP0000002-part2.zip 1.59 GB\n\n\n\nHardware and software prerequisites for IBM Business Process Manager Express [http://www.ibm.com/software/integration/business-process-manager/express/sysreqs/], IBM Business Process Manager Standard [http://www.ibm.com/software/integration/business-process-manager/standard/sysreqs/], IBM Business Process Manager Advanced [http://www.ibm.com/software/integration/business-process-manager/advanced/sysreqs/], and IBM Business Process Manager Advanced - Process Server [http://www.ibm.com/software/integration/business-process-manager/advanced/sysreqs/]are available on the web on their respective Hardware and Software Support pages. Important: If you receive a message warning that the ulimit setting is lower than recommended, set the ulimit value to 8192. Refer to Warnings about GTK or ulimit on Linux or UNIX when installing or migrating [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.admin.doc/topics/rins_trbl_warnings.html].\n\n\nBack to top\n\n\n\nINSTALLING THE REFRESH PACK\n\n\n\nUpgrade instructions for installations with existing profiles \n\nIf you have been using IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server V8.5 and you have created profiles, additional steps are required. Also, if you installed the product using the Typical installation, a profile was created and you must follow these steps. These steps include backing up the profile, stopping all Java™ processes, and sequencing the upgrade. Before you continue with the refresh pack installation, follow the appropriate documentation for details and return to this document, when instructed, to complete the Version 8.5 Refresh Pack 5 installation. \n\nImportant: \nDepending on the source version and topology, instructions for updating the database vary. The product might not continue to run successfully if you do not follow the instructions. \n\nIf you are upgrading the environment from an IBM Business Process Manager 8.5 product to V8.5 Refresh Pack 5, follow the steps in Profile upgrade instructions for IBM Business Process Manager Version 8.5 Refresh Pack 5 [http://www.ibm.com/support/docview.wss?uid=swg27042066]. \n\nBack to top\n\n\n \n\n \n\nInstalling V8.5 Refresh Pack 5 \n\n\n\nIf you have existing profiles under this installation, before you continue with the refresh pack installation, see [http://www.ibm.com/support/docview.wss?uid=swg27038089]Profile upgrade instructions for IBM Business Process Manager Version 8.5 Refresh Pack 5 [http://www.ibm.com/support/docview.wss?uid=swg27042066] for details on the steps to follow for the various topologies. Return to this document, when instructed, to complete the Version 8.5 Refresh Pack 5 installation.\n\n\nDownload repositories to the local system\nThe IBM Installation Manager must be at a minimum level of Version 1.6.0 before you start the IBM Business Process Manager 8.5 Refresh Pack 5 installation updates. The Installation Manager detects an available update if you are connected to the Internet on the workstation on which you are planning to complete the IBM Business Process Manager 8.5 Refresh Pack 5 update activities. WebSphere Application Server V8.5.5 Fix Pack 2 [http://www.ibm.com/support/docview.wss?uid=swg24037250] is a prerequisite to IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server V8.5 Refresh Pack 5.\n\nIf the machine where you are upgrading the product has Internet access, skip the following steps. \n\n 1. Download the appropriate refresh pack using the Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products [http://www.ibm.com/support/docview.wss?uid=swg24037683] document. Download bpm.8550.delta.repository.zip to a temporary disk location. \n \n \n 2. Download and installWebSphere Application Server Version 8.5.5 Fix Pack 2 [http://www.ibm.com/support/docview.wss?uid=swg24035935], if it is not yet installed. IBM Business Process Manager no longer bundles the WebSphere Application Server fix pack. This fix pack, which is required for IBM Business Process Manager, is available through Fix Central.\n \n \n When you decompress the following two files to the same location, it creates the full WebSphere Application Server V8.5.5 Fix Pack 2 repository that includes all WebSphere Application Server packages for all supported operation systems and architectures:\n \n \n 8.5.5-WS-WAS-FP0000002-part1.zip 0.814 GB\n 8.5.5-WS-WAS-FP0000002-part2.zip 1.59 GB\n \n \n 3. Unpack the repositories to any directories that you choose. Note where you have unpacked the repositories. You should unpack each repository to its own directory.\n\n\nYou can install the fix packs by using one of the following options: \nGraphical user interface (GUI) of IBM Installation Manager to update an installation \nCommand line interface of IBM Installation Manager for a silent installation \n\nGraphical user interface (GUI) of IBM Installation Manager to update an installation \n\n 1. Start the Installation Manager. \n \n \n On Windows operating systems with Internet access, click Start > Programs > IBM > IBM_BUSINESS_MANAGER_PRODUCT > Update. Then skip to step 3b.\n \n \n If you are on a Linux or UNIX-based system, start IBM Installation Manager using the install_location/IBMIM command. On Windows operating systems, use the install_root\\IBMIM.exe command. See Installation directories for the product and profile [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.doc/topics/rins_installation_paths.html] for more information on where Installation Manager is installed.\n \n \n Note: On Microsoft Windows operating systems, right-click install_root\\IBMIM.exe and select Run as administrator.\n \n \n 2. Add repositories to the IBM Installation Manager preferences.\n \n \n Click File > Preferences. Under Repositories, select one of the following options: * If you have Internet access, ensure that the Search service repositories during installation and updates option is selected.\n \n \n * If you do not have Internet access, add the location of all the local repositories that you downloaded from the Download repositories to local system section. 1. Click Add Repository. \n \n \n 2. Type or browse to the repository.config file for the IBM Business Process Manager repository that you have unpacked.\n \n \n 3. Click OK. \n \n \n 4. Repeat this process for the interim fix repositories and the WebSphere Application Server fix pack repository, if necessary.\n \n \n 5. Click OK to save the new repository settings.\n \n \n \n \n \n \n 3. Use the following steps to install graphically: 1. Click Update.\n \n \n 2. Select the Package Group where you have installed IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server.\n \n \n 3. Click Next > to continue.\n \n \n After Installation Manager checks the service repositories, the Update Packages window opens and the IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server Version 8.5 Refresh Pack 5 is shown, unless there is a later fix pack available from the live update repository.\n \n \n If you are installing WebSphere Application Server Version 8.5.5 Fix Pack 2, that is also shown.\n \n \n 4. Ensure that the refresh pack and fix pack are selected. Clear the Show recommended only check box, so that you will be able to see the WebSphere Application Server interim fixes in the next step. Click Next >. If you have Internet connectivity or have added local interim fix repositories, another Update Packages window opens. A list of interim fixes is displayed. \n \n \n 5. Select all the recommended interim fixes for IBM Business Process Manager V8.5.5 and all the recommended interim fixes for WebSphere Application Server. Refer to Recommended interim fixes for IBM Business Process Manager V8.5 Refresh Pack 5 [http://www.ibm.com/support/docview.wss?uid=swg24037612]. \n \n \n 6. Ensure that the interim fixes are all selected and then click Next > to continue. The Licenses window opens.\n \n \n 7. Read and accept the terms of the license agreements by selecting the appropriate button and click Next > to continue. The Features window opens. All of the installed features will be selected.\n \n \n 8. Click Next > to continue. The Summary window opens. All of the features that need to be updated are shown. The disk space that is required to perform the update is shown at the bottom.\n \n \n 9. Click Update to start the update. The updates are downloaded either from the live update repository or from your local repository. The updates are installed. After the installation of the updates is complete, you receive a confirmation.\n \n \n\n * \n\nNote:During a full installation when you have Internet access, follow the normal installation instructions for a full installation. Go to Install Packages> Check for Other Versions and Extensions. All of the latest versions are discovered. Follow the instructions to select the Show all versionscheck box, and then proceed with the full installation as normal. \nBack to top\n\n\n\n\nCommand line interface of IBM Installation Manager for a silent installation \n\nInstallation Manager offers a command-line interface to update your product installation silently. \n 1. Use the following command to update your IBM Business Process Manager product to V8.5 Refresh Pack 5:\n \n \n IM_INSTALL_LOCATION/tools/imcl install PACKAGE_IDS FIX_IDS -acceptLicense -installationDirectory INSTALL_DIR-repositories REPOSITORIES-log LOG_FILE\n \n \n Update the variables in the previous command specifically for your installation using the following information:\n \n * IM_INSTALL_LOCATION\n This variable represents the location where Installation Manager is installed. See Installation directories for the product and profile [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.doc/topics/rins_installation_paths.html] for more information on Installation Manager default installation directories.\n \n \n * PACKAGE_IDS\n This variable represents the list of packages to be updated. Package IDs are separatedby spaces. Use the following list to get the correct package IDs for your product.\n \n * IBM Business Process Manager Express\n com.ibm.bpm.EXP.v85\n com.ibm.websphere.ND.v85 \n * IBM Business Process Manager Standard\n com.ibm.bpm.STD.v85\n com.ibm.websphere.ND.v85 \n * IBM Business Process Manager Advanced\n com.ibm.bpm.ADV.v85\n com.ibm.websphere.ND.v85 \n * IBM Business Process Manager Advanced - Process Server\n com.ibm.bpm.PS.v85\n com.ibm.websphere.ND.v85\n \n \n \n \n * FIX_IDS\n This variable represents the interim fix IDs for any interim fixes that you need to install.\n \n \n * INSTALL_DIR\n This variable represents the installation directory of the product.\n \n \n * REPOSITORIES\n This variable represents the location of the refresh pack and interim fix repositories.\n \n \n Note: Use commas to separate multiple locations.\n \n \n * LOG_FILE\n This variable represents the location and name of the silent log file to write.\n \n \n By including the -acceptLicense parameter, you agree to the terms and licenses of this product.\n \n \n \n \n 2. After updating the command for your environment, run the command from the tools directory under the Installation Manager install location. \n \n The following command is an example in which only the IBM Business Process Manager refresh pack needs to be applied:\n C:\\Program Files (x86)\\IBM\\Installation Manager\\eclipse\\tools\\imcl install com.ibm.bpm.PS.v85 -acceptLicense -installationDirectory C:\\IBM\\BPM\\v8.5 -repositories C:\\BPM855_repository -log silent_update.txt \n 3. When the silent refresh pack installation completes, check the log files to ensure that the installation completes successfully. A success message that is similar to the following text displays on the command line:\n \n Updated to com.ibm.bpm.ADV.v85_8.5.5000.20140604_1130 in the C:\\IBM\\BPM\\v8.5 directory\n \n\n\n\nFor additional information about silent installations, visit the product documentation links in the following table: Product Content Links IBM Business Process Manager Express [http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0m1/topic/com.ibm.wbpm.imuc.stbpm.doc/topics/inst_sil_cmd_lin.html]AIX [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.stbpm.doc/topics/inst_sil_cmd_aix.html]\nLinux [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.stbpm.doc/topics/inst_sil_cmd_lin.html]\nWindows [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.stbpm.doc/topics/inst_sil_cmd_win.html] IBM Business Process Manager Standard AIX [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.sbpm.doc/topics/inst_sil_cmd_aix.html]\nLinux [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.sbpm.doc/topics/inst_sil_cmd_lin.html]\nSolaris [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.sbpm.doc/topics/inst_sil_cmd_sol.html]\nWindows [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.sbpm.doc/topics/inst_sil_cmd_win.html] IBM Business Process Manager Advanced AIX [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpm.doc/topics/inst_sil_cmd_aix.html]\nLinux [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpm.doc/topics/inst_sil_cmd_lin.html]\nSolaris [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpm.doc/topics/inst_sil_cmd_sol.html]\nWindows [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpm.doc/topics/inst_sil_cmd_win.html] IBM Business Process Manager Advanced - Process Server AIX [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpmps.doc/topics/inst_sil_cmd_aix.html]\nLinux [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpmps.doc/topics/inst_sil_cmd_lin.html]\nSolaris [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpmps.doc/topics/inst_sil_cmd_sol.html]\nWindows [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.ebpmps.doc/topics/inst_sil_cmd_win.html] \n\nAlternatively, you can use the Interactive Installation and Configuration Guide [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.doc/topics/bpm_roadmap_form.html]and follow the instructions. \nBack to top\n\n\n \n\nUpgrading the Process Designer \n\nAfter you update your Process Center with a fix pack, refresh pack, or interim fix, you must update the Process Designer to the same level. To make the updates, download the Process Designer file again and run the installation. Only the fixes or changes are applied.\n\n\nAbout this task\nWhen you install the fix pack, refresh pack, or interim fix, the IBM Process Designer.zip file is updated also. You must download it and install the updated Process Designer to the directory where you already installed Process Designer.\n\n\nProcedure \n\n 1. Open the Process Center.\n \n \n 2. Click the IBM Process Designer Download option. \n \n \n 3. When you are prompted, save the IBM Process Designer.zip file to your file system. This file contains everything that you need to install and run IBM Process Designer. Depending on your network connection, the download might take several minutes to complete.\n \n \n 4. Extract the contents of the IBM Process Designer.zip file to a temporary directory on your file system.\n \n \n 5. Open a command window and change to the directory where you extracted the contents of the IBM Process Designer.zip file. \n \n \n Important: If you are running Microsoft Windows 7, Windows Vista, or Windows Server 2008, right-click the command prompt and select Run as administrator.\n \n \n 6. Run one of the following commands to update the Process Designer. Use the same command that you used to install the Process Designer. * Default location (C:\\IBM\\ProcessDesigner\\v8.5) * installProcessDesigner_admin.bat \n * installProcessDesigner_nonadmin.bat\n \n \n \n \n * Different location * installProcessDesigner_admin.bat install_location \n * installProcessDesigner_nonadmin.bat install_location\n \n \n \n If the location has spaces in the directory name, put the whole location in quotation marks. The following examples show how to install to a different location. * installProcessDesigner_admin.bat D:\\IBM\\PD \n * installProcessDesigner_admin.bat \"D:\\Process Designer\\\"\n \n \n \n \n\n\nResults \nIBM Process Designer is updated. Only the fixes or changes are applied. Installation messages are recorded in the %TEMP%\\IBMProcessDesignerInstall.log file, where the %TEMP% variable is typically set to C:\\Documents and Settings\\current_user_name\\Local Settings\\Temp.\n\n\nBack to top\n\n\n\nRefresh pack install verification \n\nFor upgrades of installations with existing profiles, refer to the Identifying profile update errors [http://www.ibm.com/support/docview.wss?uid=swg27042066#identify] section under the Profile upgrade tab for details on verifying the refresh pack installation. \n\nNote: Installation Manager on the Microsoft Windows operating system does not recognize profile update errors. When you upgrade an installation on Windows, you must look at the Identifying profile update errors [http://www.ibm.com/support/docview.wss?uid=swg27042066#identify] section, even if Installation Manager ends with the following message: The packages are updated. \nBack to top\n\n\n\nRolling back V8.5 Refresh Pack 5 \n\nYou can roll back the refresh pack to a previous version by using one of the following options:\nGraphical user interface (GUI) of IBM Installation Manager to roll back an installation\nCommand line interface of IBM Installation Manager for a silent roll back of a refresh pack\n\nNote: The following procedure rolls back only the product binary. Any existing profiles that were upgraded during a refresh pack installation are not rolled back; you must restore the profiles from the backup you took before you upgraded the product. Any new profiles created after the upgrade cannot be reused; you must delete and recreate the profiles after you have completed the rollback process.\n\n\nGraphical user interface (GUI) of IBM Installation Manager to roll back an installation\n\n\n 1. Close all programs that were installed using Installation Manager before rolling back.\n \n \n 2. Start Installation Manager. See Installation directories for the product and profile [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.doc/topics/rins_installation_paths.html] for more information on where Installation Manager is installed.\n \n \n 3. From the Start page of the Installation Manager, click Roll back to start the Roll back packages wizard.\n \n \n 4. On the Roll Back Packages page, from the Package Group Name list, select the package group that contains the packages that you want to roll back and click Next.\n \n \n 5. Select the version of the package to which you want to roll back and click Next. \n \n \n 6. Read the summary information and click Roll Back to roll back the package. \n \n \n When the rollback process completes, a message that confirms the success of the process is displayed near the top of the page. \n \n \n 7. Optional: Click View log file to open the log file for the current session in a new window. \n \n \n 8. Click Finish to close the wizard. \n \n \n 9. Close Installation Manager. \n \n \n 10. Restore the backed up data from the original version.\n\n\n\nBack to top\n\n\n\nCommand line interface of IBM Installation Manager for a silent rollback of a refresh pack \n\nInstallation Manager offers a command-line interface to silently roll back your product installation to the previous version. In the instructions, it is assumed that you completed all of the necessary profile, database, and refresh pack-specific data backup tasks, which are described in Profile upgrade instructions [http://www.ibm.com/support/docview.wss?uid=swg27042066], before you migrated to Version 8.5 Refresh Pack 5. This data is restored after you complete the rollback task. \n\n 1. Use the following command to roll back your IBM Business Process Manager product to V8.5.0.0.\n \n \n IM_INSTALL_LOCATION/tools/imcl rollback PACKAGE_IDVERSION-installationDirectory INSTALL_DIR-log LOG_FILE\n \n \n Update the following variables for your installation: * IM_INSTALL_LOCATION\n This variable represents the location where Installation Manager is installed. See Installation directories for the product and profile [http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.5/com.ibm.wbpm.imuc.doc/topics/rins_installation_paths.html] for more information on Installation Manager default installation directories.\n \n \n * PACKAGE_ID\n This variable represents the package ID of the product installed.\n \n \n * VERSION\n This variable represents the original version of the product. Rolling back returns your installation to this version. This version will be Version 8.5.0.0. If you have upgraded directly from Version 8.5.0, see the Details for rolling back to Version 8.5.0.0 information. \n \n * Details for rolling back to Version 8.5.0.0 * IBM Business Process Manager Express\n Package ID: com.ibm.bpm.EXP.v85\n Version: 8.5.0.20130504_0134 \n * IBM Business Process Manager Standard\n Package ID: com.ibm.bpm.STD.v85\n Version: 8.5.0.20130504_0135 \n * IBM Business Process Manager Advanced \n Package ID: com.ibm.bpm.ADV.v85\n Version: 8.5.0.20120504_0137 \n * IBM Business Process Manager Advanced - Process Server\n Package ID: com.ibm.bpm.PS.v85\n Version: 8.5.0.20120504_0137\n \n \n * Details for rolling back to Version 8.5.0.1\n IBM Business Process Manager Express\n Package ID: com.ibm.bpm.EXP.v85\n Version: 8.5.1.20131107_1830\n \n IBM Business Process Manager Standard\n Package ID: com.ibm.bpm.STD.v85\n Version: 8.5.1.20131107_1830\n \n IBM Business Process Manager Advanced\n Package ID: com.ibm.bpm.ADV.v85\n Version: 8.5.1.20131107_1830\n \n IBM Business Process Manager Advanced - Process Server\n Package ID: com.ibm.bpm.PS.v85\n Version: 8.5.1.20131107_1830 \n \n \n \n * INSTALL_DIR\n This variable represents the installation directory of the product.\n \n \n * LOG_FILE\n This variable represents the location and name of the silent log to write.\n \n \n \n \n \n \n 2. After updating the command for your environment, run the command from the tools directory under the Installation Manager installation location. \n \n The following command is an example:\n \n C:\\Program Files (x86)\\IBM\\Installation Manager\\eclipse\\tools\\imcl rollback com.ibm.bpm.EXP.v85_8.5.1.20131107_1830 -installationDirectory C:\\IBM\\BPM\\v8.5 -log silent_rollback.txt\n \n \n 3. When the rollback completes, check the log files to ensure that the rollback completed successfully. A success message displays on the command line:\n \n Rolled back to com.ibm.bpm.EXP.v85_8.5.1.20131107_1830 in the C:\\IBM\\BPM\\v8.5 directory. \n \n \n 4. Restore the profile and the database backup taken prior to installing Refresh Pack 5.\n \n\nBack to top\n\n\nReference\n\nYou can find additional information on any of these topics in the IBM Business Process Manager [http://www.ibm.com/support/knowledgecenter/SSFPJS/welcome] product documentation.\n\nFor further information on the update strategy or obtaining updates, see the support page for your product.\n\nIBM Business Process Manager Express Support page [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Express]\nIBM Business Process Manager Standard Support page [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Standard]\nIBM Business Process Manager Advanced Support page [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Advanced]\nIBM Business Process Manager Advanced Process Server Support page [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Advanced]\n\n\nBack to top\n\n\nTrademarks and service marks: \nFor trademark attribution, visit the IBM Terms of Use [http://www.ibm.com/legal] Web site. \nBack to top\n\n\n\n\n\n\nORIGINAL PUBLICATION DATE\n 2013/11/15 \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5.5 Business Integration IBM Business Process Manager Express Installation / Configuration Linux, Windows 8.5.5 PRODUCT ALIAS/SYNONYM\n BPM"
}
] |
DEV_Q117 | Migrating ITCAM for AD 7.1 agent to ITCAM for WebSphere Applications v7.2 agent
Is there a suggested migration path from ITCAM for AD v7.1 agent to ITCAM for WebSphere Applications v7.2 agent and Data Collector?
| - | true | [] |
DEV_Q118 | db2top abnormally ended with core dump during monitoring SQL statements
I'm using DB2 9.7 FP6. The db2top utility abnormally ended with a core dump during monitorning SQL statements with following stack trace in the trap file. What is the cause of the problem?
<StackTrace>
-------Frame------ ------Function + Offset------
0x0900000010127AEC waddnstr + 0x6C
0x0900000010134E90 waddstr + 0x10
0x0900000010135440 vw_printw + 0x40
</StackTrace> | - | true | [] |
DEV_Q119 | Why does the Dataserver service change from Healthy to Vulnerable after logging into StoredIQ Application Stack?
Why does the Dataserver service change from Healthy to Vulnerable after logging into StoredIQ Application Stack? | This could be due to amount of Memory allocated to the dataserver. | false | [
{
"filename": "swg21997033.txt",
"text": "Title: IBM Dataserver services changing from Healthy to Vulnerable - United States\n\nText:\nSIQ TECHNOTE (FAQ)\n\nQUESTION\n Why does the Dataserver service change from healthy to Vulnerable after logging into appstack? \n\nCAUSE\nMemory allocated was not the supported number\n\nANSWER\n \n\nThis could be due to amount of Memory allocated to the dataserver. \n\n 1. Login to the Dataserver \n 2. Click on Administration > Dashboard tab \n 3. Review the Application status and make sure it is green \n 4. Click on Controller Link \n 5. Review and confirm that all services are running fine \n 6. If needed, make changes to memory"
}
] |
DEV_Q120 | Why do we get server error message when running BIRT reports after upgrading to Atlas 6.0.3.3?
Why do we get server error message when running BIRT reports after upgrading to Atlas 6.0.3.3? | This happens when the BIRT Reports is running in Standalone mode and happens due to a new configuration - report.standalone.userid | false | [
{
"filename": "swg21982354.txt",
"text": "Title: IBM Server Error Message when running BIRT Reports after upgrading to Atlas 6.0.3.3 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why do we get server error message when running BIRT reports after upgrading to Atlas 6.0.3.3? \n\nCAUSE\nThis happens when the BIRT Reports is running in Standalone mode and happens due to a new configuration - report.standalone.userid\n\nANSWER\n \n\n 1. Navigate to Atlas Properties Folder \n 2. Edit AtlasReportConfig.properties \n 3. Uncomment the property #report.standalone.userid=1 \n 4. Save the change \n 5. Restart both Atlas and Atlas Reports application server instances"
}
] |
DEV_Q121 | Job Execution Node for IIB V10
I'm looking for a way in IIB V10 to execute/invoke scripts or jobs on different operating systems like windows or System i (AS400). After a little research i found out that there is a Job Execution Node for the IIB V9, which seems to cover the requirements. Is there a Job Execution Node for the IIB V10, or an other appropriate node for the requirements?
| The JobExecutionNode, a Java-based plugin, allows you to execute operating system commands, and invoke jobs in the form of batch/shell scripts from within the message flow. The jobs can be specified on the node property or as a part of the input message. | false | [
{
"filename": "swg24017225.txt",
"text": "Title: IBM IA9Z: WebSphere Message Broker - Job Execution Node - United States\n\nText:\nia9z; Job Execution; Batch files; Shell scripts DOWNLOADABLE FILES\n\nABSTRACT\n WebSphere Message Broker – Job Execution Node \n\nDOWNLOAD DESCRIPTION\nYou might need to invoke operating system commands, windows batch files, or Unix shell scripts (henceforth referred to as jobs) from within the message flow. You might also want to schedule jobs at a specific time/interval/frequency.\n\n\nThe JobExecutionNode, a Java-based plugin, allows you to execute operating system commands, and invoke jobs in the form of batch/shell scripts from within the message flow. The jobs can be specified on the node property or as a part of the input message. \n\nPossible Uses \n\n * You can execute operating system commands, and invoke jobs in the form of batch/shell scripts from within the message flow. \n * You can schedule the tasks at a specific time (using Timer nodes) and execute them from the Message flows. \n * You can enrich the message by using the result/output of the job execution.\n\n\nNew in this Release \n• Works with IIB V10. \n\nDetails \nAuthors: Amar Shah, Shravan Kudikala, ISL-Messaging \nCategory: 2 \nReleased: 26Oct07 \nLast Updated: 09Dec15 \nCurrent SupportPac Version: 1.5 \n»Please note that the version number shown in the right-hand pane is the version of the MQ or WBI product that this SupportPac applies to. The date is the last webpage refresh. \n\nTo view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage. [http://www-306.ibm.com/software/integration/support/supportpacs] PREREQUISITES\nIBM Integration Bus - V9 or higher\nWebSphere Message Broker – V6.1 or higher.\n\nINSTALLATION INSTRUCTIONS\nUnzip the SupportPac and read the user manual. Details are inside the user manual guide.\n\nURL LANGUAGE SIZE(Bytes) ia9z.pdf [ftp://public.dhe.ibm.com/software/integration/support/supportpacs/individual/ia9z.pdf] US English 402008 \nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options ia9z.zip 26 Nov 2013 US English 626688 HTTP [http://www14.software.ibm.com/cgi-bin/weblap/lap.pl?popup=Y&li_formnum=L-TMAN-785DAH&accepted_url=ftp://public.dhe.ibm.com/software/integration/support/supportpacs/individual/ia9z.zip] \nTECHNICAL SUPPORT\n Category 2 SupportPacs are provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels. \n\nYou may submit a question and return email address using the 'rate this page' below, but a response is not guaranteed.\n\nPlease read the license information contained within the zip file of this SupportPac to determine if you want to use it. \n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Standard 9.0"
}
] |
DEV_Q122 | Importing Asset GL Errors
When importing or syncing with assets, I receive the following error for the glaccount.
Internal Server Error
Error 500: nested exception is: psdi.util.MXAccessException: BMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. Specify a value in the Organization field.
| Add the following field or tag to your inbound message. For example, if you are sending XML:
<NEWORGID>xxx</NEWORGID>
where xxx is the ORGID value.
Make sure that NEWORGID is included on the object structure.
Go To Integration > Object Structures and query the object structure.
From the Select Action menu drop down, select Exclude/Include Fields and select the Non-Persistent Fields tab. Include NEWORGID. | false | [
{
"filename": "swg21969653.txt",
"text": "Title: IBM BMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. - United States\n\nText:\nTAPEINTEGRATION; asset; MIF TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When importing ASSET using the Integration Framework you receive the following error after applying an IFIX or FIXPACK:\n\nBMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. Specify a value in the Organization field. \n\nCAUSE\nThis error is occurring due to a fix made for APAR IV67500 and included in a Maximo 7.5.0.6 or later ifix. The fix requires that the neworgid is included in the message.\n\nDIAGNOSING THE PROBLEM\nYou will see a stack trace similar to the following in the system out log: \n\npsdi.util.MXAccessException: BMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. Specify a value in the Organization field. \nat psdi.mbo.Mbo.getOrgForGL(Mbo.java:6976) \nat psdi.mbo.MboGLValue._setValue(MboGLValue.java:59) \nat psdi.mbo.MboValue.setValue(MboValue.java:1141) \nat psdi.mbo.Mbo.setValue(Mbo.java:2175) \nat \npsdi.app.asset.FldMoveModifyAssetNewGLAccount.initValue(FldMoveModifyAssetNewGLAccount.java:53) \nat psdi.mbo.MboValue.initValue(MboValue.java:404) \nat psdi.mbo.MboValue.isNull(MboValue.java:507) \nat psdi.mbo.Mbo.isNull(Mbo.java:2839) \nat \npsdi.iface.app.asset.MaxAssetProcess.setAdditionalData(MaxAssetProcess.java:85) \nat \npsdi.iface.mos.MosProcessImpl.setMainMaximoTable(MosProcessImpl.java:767\n) \n...\n\n\nRESOLVING THE PROBLEM\nAdd the following field or tag to your inbound message. For example, if you are sending XML: \n\n<NEWORGID>xxx</NEWORGID> \n\nwhere xxx is the ORGID value. \n\nMake sure that NEWORGID is included on the object structure. \n\nGo To Integration > Object Structures and query the object structure. \n\nFrom the Select Action menu drop down, select Exclude/Include Fields and select the Non-Persistent Fields tab. Include NEWORGID."
}
] |
DEV_Q123 | Resource registry with IIB
Hi Team,
I do had a scenario to be accomplished in IIB, in which one input should be passed from MQ and the other should be passed from FILE(for this i have been using Resource Registry Concept) and in order to specify mrc file i have modified dtx.ini file which is located in Integration server Insatllation directory but when the flow has been deployed an exception is being raised with the error message stating "Source not found" .
FYI - When i tried the RR from Design Studio it is working absolutely fine.
Is there something i need to configure/modify so that the mrc file will be accessible to the map in IIB flow as well. | WebSphere Transformation Extender maps that are called from WebSphere Message Broker can use the WebSphere Transformation Extender Resource Registry. WebSphere Message Broker itself does not provide any facility for working with resource registries in areas of the message flow outside of the WebSphere Transformation Extender plugin. | false | [
{
"filename": "swg21419540.txt",
"text": "Title: IBM Clarification of WebSphere Message Broker support of Resource Registry with WebSphere Transformation Extender for Message Broker - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Does IBM® WebSphere® Message Broker support a Resource Registry file from IBM WebSphere Transformation Extender for Message Broker? \n\nANSWER\nWebSphere Transformation Extender maps that are called from WebSphere Message Broker can use the WebSphere Transformation Extender Resource Registry. WebSphere Message Broker itself does not provide any facility for working with resource registries in areas of the message flow outside of the WebSphere Transformation Extender plugin. \n\nIn the WebSphere Transformation Extender for Message Broker documentation, the following sentence in the topic \"Setting resource registry on execution groups:\" \n\n\nConfigure WebSphere Message Broker to use the WebSphere Transformation Extender Resource Registry by setting the resource configuration (.mrc) file on execution groups. \n\n\n\n\nShould read: \n\n\nConfigure WebSphere Transformation Extender for Message Broker to use the WebSphere Transformation Extender Resource Registry by setting the resource configuration (.mrc) file on the WebSphere Message Broker execution groups."
}
] |
DEV_Q124 | Is there a scripting feature in ITM?
Is there a scripting feature in ITM? | - | true | [] |
DEV_Q125 | Error when using profilePath parameter with BPMConfig to create a profile
When creating a profile using the BPMConfig command and the -profilePath parameter to define a custom directory to store the profile data, the creation fails with the following error message if the directory already exists (even if it is empty):
com.ibm.bpm.config.BPMConfig.main(): The profile path <profile_path> must not exist. com.ibm.bpm.config.util.ConfigException: The profile path <profile_path> must not exist. at com.ibm.bpm.config.BPMConfig.createDmgrProfile(BPMConfig.java:1833) at com.ibm.bpm.config.BPMConfig.configureDeploymentEnvironment(BPMConfig.java:6
... | - | true | [] |
DEV_Q126 | Why is WebSphere MQ connection failing when enabling SSL with AMQ9640 SSLPEER peer name error?
Why is WebSphere MQ connection failing when enabling SSL with AMQ9640 SSLPEER peer name error?
example client side error:com.ibm.mq.jmqi.JmqiException: CC=2;RC=2399;
AMQ9640: SSL invalid peer name, channel '?',
attribute 'OID.0.9.2342.19200300.100.1.3 (x2)'. | - | true | [] |
DEV_Q127 | Help with Security Bulletin: Vulnerability in IBM Java Runtimes affect Websphere Business Modeler Advanced and Websphere Business Modeler Basic (CVE-2015-0138)
I need to understand details regarding Security Bulletin: Vulnerability in IBM Java Runtimes affect Websphere Business Modeler Advanced and Websphere Business Modeler Basic (CVE-2015-0138). Where can I find this information? | - | true | [] |
DEV_Q128 | IIS/SSL related error after appliying FP41 on WAS7.0
hi
Getting below error while hitting the application URL, after upgrading fix pack from 7.0.0.29 to 7.0.0.41
SSLHandshakeE E SSLC0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLHandshakeException: Client requested protocol SSLv3 not enabled or not supported | - | true | [] |
DEV_Q129 | Help with 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)
I need to understand details regarding "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)" Where can I find this information? |
CVEID: CVE-2015-0410
DESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.
CVSS Base Score: 5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)
CVEID: CVE-2014-6593
DESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N) | false | [
{
"filename": "swg21962588.txt",
"text": "Title: 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\n\nText:\n 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) \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) \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.\n\nJava 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] \n\n\n\n 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 \n\nCHANGE 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."
}
] |
DEV_Q130 | Improve Performance of Decision Center and Rule Team Server (RTS)
How can I improve the performance of ODM Decision Center and WebSphere ILOG Rule Team Server (RTS)? | - | true | [] |
DEV_Q131 | Refining search results by content type in Quickr doesn't work as expected
Question: Refining of search results returned in the Search Center by clicking on content types eg: blogs and wikis does not return any reduced result set. The only refining content type which works is 'files' | - | true | [] |
DEV_Q132 | What is the meaning of value "unknown" for ITCAM WAS Application Status attribute?
What is the meaning of value "unknown" for ITCAM WAS Application Status attribute? | By default baselining gets enabled with a situation WasAppDiscoverd. This situation is enabled by default and will discover new applications then run a take action to start the baselining. So if this situation is not enabled then you should enable it and assign to the ITCAM App Server managing system list. | false | [
{
"filename": "swg21653905.txt",
"text": "Title: IBM How to enable Baselining in your monitored application. - United States\n\nText:\ntema enable baselining Unknown application health status CAMADALL CAMADINST TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n Steps to enable Baselining in your monitored application. \n\nANSWER\nThe health of the monitored application is calculated against an internally stored baseline threshold. The baselining of the application is a process that uses a pre-defined mathematical and statistical method to automatically calculate a threshold based on response time information typically collected over a period of time (few days to few weeks.) \n\nBy default baselining gets enabled with a situation WasAppDiscoverd. This situation is enabled by default and will discover new applications then run a take action to start the baselining. So if this situation is not enabled then you should enable it and assign to the ITCAM App Server managing system list. \n\nYou want to do baselining with normal or typical load on the server over a period of few days to few weeks, or even few months. The performance of the application under this load is considered good (you will see \"Good\"\" in the Application Health views) and deviation from this performance indicates degrading health (\"Bad\" or \"Fair\" in the Application Health views) of the monitored application. \n\nTo start baselining for your application server, please follow these steps: \n\n(Note 1: in this example, I've used a WebSphere-based application but you can also do the same for any application on your J2EE agent also.) \n\n(Note 2: Before beginning baselining, make sure you have typical or normal load on the server to set the baselining threshold values.) \n\n1. Login to your TEPS, select Application Health, right-click on it, go to Workspace and select Application Registry. Look at the panels on the right and observe the baselining columns. If they're blank, your baselining has not been started. \n\n2. Next select Application Health, right-click on it, go to Workspace and select Application Health status. If you see Unknown, then you know the baselining has not started or not been calculated. \n\n3. High-lite your application, select the small yellow chain link in the first unnamed column and select Application Configuration Details. See screenshot here: \n\n[/support/docview.wss?uid=swg21653905&aid=1] [/support/docview.wss?uid=swg21653905&aid=1] \n\n4. In the bottom panel on the right select the line that says All and high-lite it. Then right-click it, select Take Action and Select. In the pull-down, select Start_Baselining and enter the Period (2 days), Update_Interval (every 2 hours), and Run_Clean set to 1 (clean start.) If you wish, you can change these values to whatever you want. \n\nSee screenshots here:\n[/support/docview.wss?uid=swg21653905&aid=2] [/support/docview.wss?uid=swg21653905&aid=2]\n[/support/docview.wss?uid=swg21653905&aid=3]\nHit OK twice and you should get a Command completed successfully message. (Note: If you get a Baselining_Already_Active message in the pop-up window, then you should do another Take Action and Stop_Baselining first if you want to do the baselining again.)\n\nOnce you have the baselining active, let it run for the period of time with typical load on the server. After the baselining is complete, the Unknown values in the Application Health should now change to Good or Fair or Bad depending on threshold values.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for Web Resources ITCAM for Web Resources (J2EE TEMA) AIX, HP-UX, Linux, Solaris, Windows, Solaris Opteron 6.1, 6.2 Advanced \nPRODUCT ALIAS/SYNONYM\n ITCAM ITCAM4AD ITCAMfAD TEMA ITCAM for Web Resources"
}
] |
DEV_Q133 | Do I need to backup /opt/ibm-ucd/server/var/sa/dialogue ?
My UCD server has so many files in /opt/ibm-ucd/server/var/sa/dialogue that ls goes out of memory trying to list them all. Looking at another (small) server I can see that the files within are roughly 2k on average, and judging by the apparent size of the directory (100Mb) I've probably got 50000+ files in there.
Do I need to backup this directory? From what I've read, I believe this directory contains records of in-flight communication between UCD and the agents - but assuming the server is down, is it safe to assume that no such activity is occurring? Can I periodically clean this directory? | - | true | [] |
DEV_Q134 | I am receiving AC power supply failures on my DataPower 9235 appliance. How can I resolve this?
I am observing the following errors on my DataPower 9235 device:
[failure] Power supply '1' has no AC input power, or is not present. [failure] Power supply '2' has no AC input power, or is not present.
Do i need to replace the power supplies? | This problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. | false | [
{
"filename": "swg21512291.txt",
"text": "Title: IBM WebSphere DataPower M/T 9235 appliance might incorrectly report failure of both power supplies - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n The IBM WebSphere DataPower M/T 9235 appliance might incorrectly report the failure of both power supplies. This message is not reported on all appliances and can occur rarely in the field. \n\nANSWER\nThe following message would be present in the DataPower logs: \n\nSystem power supply #2 has failed.\n\nor logging event code: \n\n0x80400022 System power supply #2 \n\n\nThe problem can be confirmed by issuing the following commands on the appliance CLI:\n\nco \ntest hardware \nexit \n\nThe following output from the test hardware command confirms this problem: \n\n[failure] Power supply '1' has no AC input power, or is not present.\n[failure] Power supply '2' has no AC input power, or is not present.\n\nOther results in the test hardware command might also show incorrect values.\n\nThis problem does not affect the operation of the appliance other than the continuous reporting power supply failure message. \n\nTo confirm the power supplies are working normally you may check the LED status on the power supplies. If the LED's are green the power supplies are working normally.\n\n\nTo recover from the false errors perform a reboot of the appliance: \n\nFrom the WebGUI: \n\nControl Panel → System Control → In the “Shutdown” section choose “Reboot System” then click “Shutdown” \n\n \n\nFrom the CLI: \n\ntop \n\nshutdown reboot \n\ny \n\n\nThis problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. The highly intermittent error rarely occurs again on the same appliance \n\nIf the issue reoccurs on the same appliance contact IBM DataPower support [http://www.ibm.com/support/docview.wss?uid=swg21236322] with the following information: \n\n1) How many times have you seen the issue on the same appliance? \n\n2) Gather the outputs for the following CLI commands:\nshow clock\nshow version\nshow ipmi\nshow sensors-other\nconfig\nservice show\ntest hardware"
}
] |
DEV_Q135 | DataPower upgrade message Loading firmware failed: Preserve user modified data failed: Insufficient flash space available Could not install firmware image. The system will not reboot.
In the process of upgrading my IBM DataPower Gateway I saw the following message:
"Loading firmware failed: Preserve user modified data failed: Insufficient flash space available Could not install firmware image. The system will not reboot."
What does this mean and what are the appropriate next actions? | - | true | [] |
DEV_Q136 | Compose tab appears disabled and project is not editable in Decision Center
I have upgraded my ODM version and a project in Decision Center appears non editable :
the compose tab is disabled
in explore tab there are no new nor edit button | - | true | [] |
DEV_Q137 | What things are important to consider when installing a fix pack for IIB running on a multi-instance environment?
I am planning to apply a fix pack to my current version of IBM Integration Bus (IIB) using multi-instance brokers and I am looking for any important information regarding the process.
For example:
- installation and verification tasks
- is it possible to back out this fix pack in case there are issues
- any specific tasks for multi instance configuration | - | true | [] |
DEV_Q138 | How to fix the DB2 errors in Portal ?
How could we fix the below DB2 errors in WebSphere Portal:
DB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=WPUSER;SELECT;JCR.SHORTCUT_SEQ, DRIVER=4.15.113
DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-551;42501;WPUSER|SELECT|JCR.SHORTCUT_SEQ, DRIVER=4.15.113 | - | true | [] |
DEV_Q139 | Help with Security Bulletin: IBM WebSphere MQ is affected by a privilege escalation vulnerability (CVE-2017-1612)
I need to understand details regarding Security Bulletin: IBM WebSphere MQ is affected by a privilege escalation vulnerability (CVE-2017-1612). | - | true | [] |
DEV_Q140 | Why get SQL1227N when replay db2look output on DB2 V9.7 FP11?
Why get below SQL1227N when replay db2look output on DB2 V9.7 FP11?
-----
UPDATE SYSSTAT.COLUMNS SET COLCARD=4, NUMNULLS=1, SUB_COUNT=-1, SUB_DELIM_LENGTH=-1,
AVGCOLLENCHAR=7, HIGH2KEY='', LOW2KEY=' ', AVGCOLLEN=12 WHERE COLNAME = 'COL1'
AND TABNAME = 'TAB1' AND TABSCHEMA = 'DB2INST1'
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1227N The catalog statistic "" for column "HIGH2KEY" is out of range for
its target column, has an invalid format, or is inconsistent in relation to
some other statistic. Reason Code = "3". SQLSTATE=23521
----- | It is an known limitation of current DB2 V9.7 and above versions' runstats. | false | [
{
"filename": "swg21979066.txt",
"text": "Title: IBM Runstats may update unexpected HIGH2KEY and LOW2KEY statistic values which may cause SQL1227N - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why is SQL1227N returned when replay db2look output? \n\nCAUSE\nIt is an known limitation of current DB2 V9.7 and above versions' runstats.\n\nANSWER\nIf we run an example scenario below, at the end of script \"db2 -tvf db2_SAMPLE.sql\" \n\ngets SQL1227N.\n--- repro.sh ---\n#!/bin/sh\n\ndb2 -v \"drop db sample\"\ndb2 -v \"create db sample\"\ndb2 -v \"connect to sample\"\ndb2 -v \"drop table db2inst1.tab1\"\ndb2 -v \"create table db2inst1.tab1 ( col1 varchar(10) )\"\ndb2 -v \"insert into db2inst1.tab1 values (NULL),(' '),(' '),(' ')\"\ndb2 -v \"runstats on table db2inst1.tab1\"\ndb2 -v \"terminate\"\ndb2 -v \"connect to sample\"\ndb2look -d sample -a -e -m -o db_SAMPLE.sql\n\ndb2 -v terminate\ndb2 -v \"drop db sample\"\ndb2 -v \"create db sample\"\ndb2 -v \"connect to sample\"\ndb2 -tvf db_SAMPLE.sql | tee test.log\n# replay db2look output and gets SQL1227N at this point\ndb2 -v terminate\n----------\n\nHere is the SQL1227N message:\n-----\nUPDATE SYSSTAT.COLUMNS SET COLCARD=4, NUMNULLS=1, SUB_COUNT=-1, SUB_DELIM_LENGTH=-1, \nAVGCOLLENCHAR=7, HIGH2KEY='', LOW2KEY=' ', AVGCOLLEN=12 WHERE COLNAME = 'COL1' \nAND TABNAME = 'TAB1' AND TABSCHEMA = 'DB2INST1'\nDB21034E The command was processed as an SQL statement because it was not a\nvalid Command Line Processor command. During SQL processing it returned:\nSQL1227N The catalog statistic \"\" for column \"HIGH2KEY\" is out of range for\nits target column, has an invalid format, or is inconsistent in relation to\nsome other statistic. Reason Code = \"3\". SQLSTATE=23521\n-----\nAs above, UPDATE SYSSTAT.COLUMNS statement gets SQL1227N at col1 varchar(10).\nIt is caused by runstats, writes an unexpected HIGH2KEY and LOW2KEY statistic values.\n\nHere is work arounds:\n\nWork around #1\n1. $ db2set DB2_STATISTICS=USCC:0\n** this variable is available for V10.1 FP4 and above.\n2. $ db2 terminate\n3. $ db2start\n4. $ repro.sh\n\nWork around #2\n1. Edit SQO1227N causing UPDATE statements' COLCARD=4 to 3 in db_SAMPLE.sql file.\n2. Replay by running \"db2 -tvf db_SAMPLE.sql\" \n\nWork around #3\n1. Do not insert/import space(s) data, such as \" \", \" \".\n\nNote:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following sample scenario 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/]\n\nRELATED INFORMATION\n RUNSTATS command [http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0001980.html?lang=en]"
}
] |
DEV_Q141 | Why is OCR is putting multiple lines on one line?
I am running an APT application, and multiple detail lines are getting put on a single line within my .TXT file. Is there something I can do about this? | Add the following action prior to NormalizeCCO.
*
*
The first parameter is the percentage of a line that two words must be offset to be considered as separate lines. If the value is not set, the default is 50. In the example, if two words are vertically offset by more than 35% of the height of the words, then they are considered to be on separate lines. Lower values are more likely to split words into separate lines. Higher values are more likely to merge words into a single line. | false | [
{
"filename": "swg21701910.txt",
"text": "Title: IBM NormalizeCCO merging lines with IBM Datacap Taskmaster Capture - United States\n\nText:\nnormalizecco; merge lines; recognition TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After running NormalizeCCO, words on separate lines are merged into a single line of text when using IBM Datacap Taskmaster Capture. \n\nSYMPTOM\nIn the following image, Word 1 and Word 2 are on separate lines, but after NormalizeCCO is run may show in a single line as Word Word 1 2. \n\n[/support/docview.wss?uid=swg21701910&aid=1]\n\n\nCAUSE\nWhen text is not cleanly printed in lines, such as when the font varies or the text is vertically offset, Datacap may not always be able to locate text when loading field values. The NormalizeCCO goes through the CCO file, and cleans up all the entries so they appear in regular lines. For most images this improves ultimate recognition results, but for some complex images, NormalizeCCO cannot determine where to separate the lines and merges all words into a single line.\n\n\nRESOLVING THE PROBLEM\nAdd the following action prior to NormalizeCCO. \n\n * \n * \n\nThe first parameter is the percentage of a line that two words must be offset to be considered as separate lines. If the value is not set, the default is 50. In the example, if two words are vertically offset by more than 35% of the height of the words, then they are considered to be on separate lines. Lower values are more likely to split words into separate lines. Higher values are more likely to merge words into a single line. \n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Not Applicable Windows 9.0.1, 9.0.0"
}
] |
DEV_Q142 | Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null
When using BPM, I see runtime exceptions saying that this SQL error occurs: Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null
For example:
CWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: Wrapped com.lombardisoftware.core.TeamWorksRuntimeException: | - | true | [] |
DEV_Q143 | How can I configure J2EE Tomcat DC to run as Windows Service?
I'm trying to configure ITCAM J2EE v7.1.1 Tomcat DC to run as a Windows Service but it fails. Is this type of configuration supported? If so, what is the right procedure to do that?
| - | true | [] |
DEV_Q144 | CICS CM CCVI abends AEXZ on startup in CCVIINIT
Why am I receiving an message DFHAC2236 with an abend AEXZ each time that I attempt to startup a newly installed CICS Configuration Manager (CICS CM) server using the CCVI transaction? It looks like it is starting up, but after about 10 seconds it fails with the AEXZ. The last messages I see in the CICS MSGUSR indicate it successfully opened the TCPIPSERVICE:
DFHSO0107 mm/dd/yyyy hh:mm:ss applid TCPIPSERVICE CCVBASIC has been opened on port nnnnn at IP address nnn.nn.nn.nnn.
DFHDU0203I mm/dd/yyyy hh:mm:ss applid A transaction dump was taken for dumpcode: AEXZ, Dumpid: 1/0001.
DFHAC2236 mm/dd/yyyy hh:mm:ss applid Transaction CCVI abend AEXZ in program CCVIINIT term ????. Updates to local recoverable resources will be backed out.
CEEMSG shows:
CEE3250C The system or user abend AEXZ was issued. From compile unit CCVIINIT at entry point CCVIINIT at compile unit offset +0000832E at entry offset 18E8854E.
If CCVI is run a few more times, it eventually seems to initialize the server successfully. | - | true | [] |
DEV_Q145 | Why is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time?
Why is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time? | This APAR fixes the issue. It clears the cache properly even if
base entry is different than name in repository.
The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.13 and 8.5.5.9. Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 | false | [
{
"filename": "swg1PI47826.txt",
"text": "Title: IBM PI47826: VMM DOES NOT CLEAR THE CACHE IF CLEARENTITY MODE IS USED. - United States\n\nText:\n 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]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\n\nSUBSCRIBE\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\n \n \n \n \n \n\nPROBLEM 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.\n \n \n \n \n \n\nPROBLEM 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\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"
}
] |
DEV_Q146 | Gettting error CRIMC1020E: zip im.properties not found during BPM Fix Pack install
During the BPM 7.5.1.2 Fix Pack install from the IBM Installation Manager, error window pop up with:
CRIMC1020E: zip im.properties 1.0.0.200911091101 not found ERROR: `zip im.properties 1.0.0.200911091101` not found in [path to sca.1.0.1.17.fp]. CRIMC1020E: zip config.registry 1.0.0.200911092301 not found
……
How can I resolve this error to complete the Fix Pack installation? | - | true | [] |
DEV_Q147 | TEP to TEPS communication issues with different Java versions
Recent Java updates have caused connection problems when logging into the TEPS via the TEP client (Browser or Java Web Start). Is there an updated list of known issues?
| - | true | [] |
DEV_Q148 | How do I have to prepare WAS and BPM servers, if DST or time zones will change?
Daylight Saving Time (DST) or time zones will change in our country (e.g. 26.10.2014 in Russia).How do I have to prepare the WAS and BPM servers in our environment? | - | true | [] |
DEV_Q149 | Why SSH connections fail after upgrade to v7.5.2 and above?
Why SSH connections fail after upgrade to v7.5.2 and above? The same configuration works on v7.2. | 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. | false | [
{
"filename": "swg21974106.txt",
"text": "Title: IBM Late breaking updates to DataPower 7.5 documentation - United States\n\nText:\n 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.\n\n\n\n\n\n\n\n\n\n\nUpgrade * \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 * \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 * \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. \n\n\nBack 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"
}
] |
DEV_Q150 | Is Java 7 supported for BPM?
What versions of BPM, if any, support Java 7? | - | true | [] |
DEV_Q151 | QUESTION_TITLE
QUESTION | - | true | [] |
DEV_Q152 | Why are we no longer able to login to the WAS Administrative Console after adding an Active Directory Server as registry?
We have WAS ND 8.5.5.10 in use and have added our Active Directory Server to the Federated Repositories. Via the Administrative Console we used 'root' as base entry for this registry. After restarting the dmgr, we see NameNotFoundExceptions like the following in SystemOut.log:
[12/22/16 17:00:24:214 CET] 00000001 exception E com.ibm.ws.wim.adapter.ldap.LdapConnection search(String, String, Object[], SearchControls) CWWIM4520E The 'javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001E5, problem 2001 (NO_OBJECT), data 0, best match of:
''
\u0000]; Remaining name: '/'; Resolved object: 'com.sun.jndi.ldap.LdapCtx@4ca226a8'' naming exception occurred during processing.
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3279)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(LdapConnection.java:3122)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3299)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapConnection.java:3520)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.search(LdapAdapter.java:3524)
at com.ibm.ws.wim.ProfileManager.searchRepository(ProfileManager.java:5331)
Furthermore, we are no longer able to login to Administrative Console and get displayed the error message Invalid User ID or password.
Why does this happen and how can we fix this? | - | true | [] |
DEV_Q153 | Can we create Match design specification db in xmeta
Could you please let me know if we can create schema for Match design
specification database in xmeta db. | You should start from an empty Database; using the default XMETA Database is not recommended because it can become corrupt. | false | [
{
"filename": "swg21409481.txt",
"text": "Title: IBM Information Server QualityStage Match Designer Database creation - United States\n\nText:\nMD Match Designer Matching Match InformationServer QualityStage TECHNOTE (FAQ)\n\nQUESTION\n How do I configure the Match Designer Database in Information Server? \n\nANSWER\nThis Technote outlines the following procedures. \n\n 1. Prerequisites \n 2. What is the Match Database’s purpose? \n 3. Setting the database up. \n 4. Configuring the Match Designer for use with the Database. \n 5. On going maintenance \n\n\nPrerequisites \nThe following must exist before using the Match Designer functionality. 1. Match Specification built for use in match designer. \n 2. Create a data set that contains the data you will run the match analysis on. \n 3. Create a corresponding frequency data set to be used in the match analysis. \n 4. DSN for local PC \n 5. Create Database in which to perform the Match analysis processing. \n a) Sizing of Database \n b) Character sets required \n c) Permission's for users \n\n\nAdditional information is also available with in the WebSphere QualityStage User Guide. \n\nWhat it’s the Match Database’s purpose? 1. The results Database is used to test the match specifications (logic) designed for use in match jobs. \n 2. This functionality enables the user to get a baseline of how good the match criteria are, based on the match logic developed for use in the application. \n 3. The results Database stores statistics and match results based on your data. For Example: How many matches, duplicates, and unmatched records. \n 4. This functionality allows developers to change matching logic on the fly and retest within minutes. \n\n * There is nothing from this Database that is used in production runs so it should never be created on or moved to a production box. \n * The Match Designer is to be used for development purposes only with a \"subset\" of the full volume data. If additional match modifications are required continue to use a subset of data not conduct testing with full volume data. \n * Determining the subset size of data to use in the Match Designer will vary depending on the clients environment and resources. Each client should run several iterations to determine the optimal subset to utilize in the Match Designer step. \n * To obtain the most accurate matching thresholds a full volume run should be performed in the DataStage Designer.\n\n\nCreating the Database 1. You should start from an empty Database; using the default XMETA Database is not recommended because it can become corrupt. \n 2. There are certain requirements on how the Database is to be created. \n a) If Oracle: CHARACTERSET should be set to AL32UTF \n b) If SQL: default is fine. \n c) If DB2: create as codepage UTF-8 and page size 32K \n d) Permission’s - Each user has to have the ability to create tables, write and read rights in the DB. \n e) The minimum DB space required will be calculated as follows = Number of Passes in match specification (X) Number of Input Records (X) Input Record Length (+) 100 filler.\n f) If this is a distributed installation, you need to have ODBC defined in your client and on the server. They must have the same name. \n\n\nConfiguring the Match Designer for use with the Database 1. Via the DataStage Designer navigate to the your match specification to work with \n 2. Double click and a window will appear indicating: \n “The ODBC Data Source Name (xxxxxxx) currently specified for this Match could not be found. Please create a DSN by this name or run a Test Environment Update to configure a different DSN for this Specification.” \n 3. Select the “OK” button \n 4. Select option “Configure Specification” \n 5. From drop down select “Test Environment” \n 6. For “Sample Information” navigate to the location of your data set(s) created for analysis. \n 7. Under “Frequency Information” navigate to the location of your frequency data set(s) created for use. \n 8. Section “Test Results Database” fill the following information in. \n a. Select the DSN created for the will allow the connection to the Database. \n b. Enter user name required \n c. Password required \n d. Test Connection \n e. Configuration File Location; these are the nodes located in your environment for use. Please make sure this matches the location of where the data sets reside on the server. \n 9. Once connection is established hit the “Update” button. This will populate the Database with the required fields (not data) to populate when you perform the test specification. \n 10. The final step is to perform the Test All Passes. Please note this make take a few moments depending on the size of the files used. \n\n\nOngoing Maintenance 1. For each new run, results are cleared and rewritten to the DB. \n 2. Each user should have their own respective Databases to avoid rewriting over previous results. \n 3. There are separate tables holding results for each design. And from one user it is no problem to use a single Database and multiple designs. \n 4. Per the recommendation above in \"Creating the Database\" this database should not be your XMETA database. If you used the XMETA DO NOT RUN THIS STEP. When you are done testing you can drop the DB altogether."
}
] |
DEV_Q154 | Why are some Datatypes corrupt after Impact cluster failover/failback ?
Running Impact 7.1.0.11. The symptom is whenever Impact does a failover, a couple DataTypes
turn out empty.
I've checked the type files before and after Impact failover and the difference happens in the property
*.SQL.USERPARAMETERS
This property no longer exists for the corrupted datatypes".
| "a new property is added to increase the file size limit:
*
Add the property to $NCHOME/impact/etc/<SERVERNAME>_server.props file
where size limit can be 8192, 16384, 32768, etc.. "
The property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact.
The APAR is not an issue in Impact 6 and 7, but one would still have to include this property with an appropriate value to handle a large character length for the USERPARAMETERS parameter.
The character length includes the whole USERPARAMETERS property name as well as the definition. | false | [
{
"filename": "swg21598417.txt",
"text": "Title: IBM DataType incorrect on Secondary - United States\n\nText:\nnetcool; impact; netcool/impact; nci; data; type; datatype; .type; replication; cluster; sync; error; 500; mark; invalid TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The DataType is not being correctly replicated across the ImpactServer Cluster \n\nSYMPTOM\nThe .type file of the Secondary ImpactServer configuration is truncated with the error message: \n\n * \n * \n\n\nCAUSE\nAPAR \"IZ81446: IMPACT 511 CLUSTER UNABLE TO REPLICATE DATATYPES WITH USERPARMETERS VALUES IN EXCESS OF 16,000 CHARACTERS.\" [link below] \n\n\n\n\n\nRESOLVING THE PROBLEM\nAdditional comments associated with APAR IZ81446 release notes: \n\n\n\"a new property is added to increase the file size limit:\n\n\n\n * \n\n\nAdd the property to $NCHOME/impact/etc/<SERVERNAME>_server.props file \nwhere size limit can be 8192, 16384, 32768, etc.. \" \n\nThe property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact. \n\nThe APAR is not an issue in Impact 6 and 7, but one would still have to include this property with an appropriate value to handle a large character length for the USERPARAMETERS parameter. \n\nThe character length includes the whole USERPARAMETERS property name as well as the definition. \n\nFor example one would add the property: \n\n * \n\n\nto the files: \n\n * \n * \n * \n\n\nwhere one wished to allow the replication of a DataType between two ImpactServers called NCI1 and NCI2 in a Cluster where the USERPARMETERS property line were 20,000 characters long. \nRELATED INFORMATION\n APAR IZ81446 [http://www-01.ibm.com/support/docview.wss?uid=swg1IZ81446]"
}
] |
DEV_Q155 | What exactly is "wpcollector" in WebSphere Portal Server?
I've been told to get wpcollector output? What exactly is this? | Wpcollector is a command line tool that automates the collection of portal logs and configuration files. | false | [
{
"filename": "swg21445430.txt",
"text": "Title: IBM Automated data collection capability provided by wpcollector tool - United States\n\nText:\nwpcollector isalite isa lite data collection collector diagnostics TECHNOTE (FAQ)\n\nQUESTION\n What are the benefits of the wpcollector tool? How do I use this tool? \n\nANSWER\nWpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support. \n\nWpcollector is delivered with WebSphere Portal beginning with the 7.0 release. If tracing is required for the problem scenario, you must manually enable traceStrings and recreate the problem PRIOR to running wpcollector. \n\nTo run wpcollector, please follow the steps, below:\n\n\n\n * If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below: \n \n\n\n * If using Microsoft Windows, Unix/Linux, or IBM i, run the following script from the <wp_profile_root> [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/reference/wpsdirstr.dita]/PortalServer/bin/ directory to begin the collection: * \n * \n * Unix/Linux: wpcollector.sh \n * i: wpcollector.sh \n * \n * Tip: To specify the option for collecting files for the Deployment Manager profile, use the \"dmgr.root\" parameter. For example: \n * wpcollector.bat -Ddmgr.root=/opt/IBM/WebSphere/profiles/dmgr_profile\n \n \n * If using IBM z/OS, proceed as follows [../reference/wpsdirstr.html%5C]: * \n * \n * In the Portal configuration panel, select Collect Diagnostics. \n * Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS). \n * \n * Tip: To collect data from the Deployment Manager, the only requirement is to submit the job from the system where the Deployment Manager is installed (i.e. so it can access the files). There is no prompt in the ISPF panel for this.\n \n \n * Locate the wp.mustgather-<timestamp>.zip file in the <wp_profile_root> [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/reference/wpsdirstr.dita]/filesForAutoPD/ directory and follow the instructions in \"Exchanging information with IBM Technical Support for problem determination\" [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] to manually FTP the collection to IBM. If using z/OS, there may be additional z/OS-specific files required, such as WebSphere Portal servant region or controller region joblogs. Wpcollector currently does not collect these files. Your L2 Support Engineer will inform you in the event these files are needed and provide instructions for collecting them. \n \n\n\n * If tracing was requested and enabled, please follow the instructions provided by the L2 Support Engineer to disable tracing from the environment\n\nRELATED INFORMATION\n Data Collection and Symptom Analysis [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/trouble/tbl_apdt_over.dita?lang=en]"
}
] |
DEV_Q156 | Help with Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693
Where can I find information for Security bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693? | CVEID: CVE-2016-9693
DESCRIPTION: IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.
CVSS Base Score: 7.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/119517 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) | false | [
{
"filename": "swg21998655.txt",
"text": "Title: IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A comma separated file (CSV) download feature exists in IBM BPM and WLE and is available for anonymous users. An attacker can craft a URL that can trigger a download of attacker-supplied content under an attacker-supplied file name onto the victim's machine. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2016-9693 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9693]\nDESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119517 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119517]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n- WebSphere Lombardi Edition V7.2.0.0 - V7.2.0.5\n- IBM Business Process Manager Advanced V7.5.0.0 - V7.5.1.2\n- IBM Business Process Manager Advanced V8.0.0.0 - V8.0.1.3\n- IBM Business Process Manager Advanced V8.5.0.0 - V8.5.7.0 including cumulative fix 2016.12\n\nREMEDIATION/FIXES\nInstall IBM BPM or WLE interim fix JR57149 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR57149]as appropriate for your current version. \n\n\n * IBM Business Process Manager Advanced [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Standard [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Express [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR57149] \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=JR57149]\n\n\nAs IBM Business Process Manager V7.5 and WebSphere Lombardi Edition are out of general support, customers with a support extension contract can contact IBM support to request the fix. The fix disables the vulnerable URL and uses HTML5 features to trigger CSV download without server interaction. \n\nFor WebSphere Lombardi Edition 7.2.0.0 through 7.2.0.5 \n\n * Install Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24034270] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149] \n\nFor IBM BPM V7.5.0.0 through V7.5.1.2: * Upgrade to minimal Refresh Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24031230], install Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24036462] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.0.0.0 through V8.0.1.3 * Upgrade to minimal Refresh Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24033777], install Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24037734] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.0.0 through V8.5.0.2 * Install Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24040683] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.5.0 * Apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.6.0 through V8.5.6.0 CF2 * Install CF2 [http://www-01.ibm.com/support/docview.wss?uid=swg24041303] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.7.0 through V8.5.7.0 CF 2016.12 * Install CF 2016.12 [https://www.ibm.com/support/docview.wss?uid=swg27048992] and then apply iFix JR57149 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\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\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 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\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Nalla Muthu S and Prasath K \n\nCHANGE HISTORY\n 24 Feb 2017: 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. \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\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 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 Standard Security AIX, Linux, Solaris, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 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 Security AIX, HP-UX, Linux, Solaris, Windows 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2"
}
] |
DEV_Q157 | How do I configure TLS/SSL for an IIB web service provider and consumer?
I'm investigating ways and technologies for use with IIB to run a web service that runs as both a provider and consumer. I'm looking at HTTP and SOAP messages/nodes. At a high level it might look like this:
HTTPInput (TLS over HTTPS) -> Compute -> HTTPRequest (SSL over HTTPS) -> Compute -> HTTPReply
or
SOAPInput (TLS over HTTPS) -> Compute -> SOAPRequest (SSL over HTTPS) -> Compute -> SOAPReply
Does anyone have more details/references beyond the knowledge center on how to configure the TLS/SSL portions? | - | true | [] |
DEV_Q158 | Must the TOKEN_SEPARATOR value be enclosed in quotes for the custom scripting feature?
Must the TOKEN_SEPARATOR value be enclosed in quotes for the custom scripting feature? | TOKEN_SEPARATOR (Optional - default semicolon ";").
It sets the string to be used as separator to split the output row in tokens. It is ignored if TOKEN_TYPES is not set. Empty value (blank) is accepted as separator and multiple consecutive blanks in output rows are considered as a single one. | false | [
{
"filename": "swg21960062.txt",
"text": "Title: IBM OS Agents Version 6.3.0 FixPack 5 Scripting Feature - United States\n\nText:\n FIX README\n\nABSTRACT\n This feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency. \n\nCONTENT\n(C) Copyright International Business Machines Corporation 2015. All rights reserved.\nComponent: IBM(R) Tivoli(R) Monitoring OS Agents, Version 6.3.0 FixPack 5\n\nDate: 30 June 2015\n\nContents:\n\n1.0 Introduction\n1.1 Quick Start\n2.0 New Attribute groups\n3.0 Parameters in OS agent environment files\n4.0 Parameters in property file\n5.0 Examples of property file\n6.0 Examples of private situations \n7.0 Custom Scripts and Custom Scripts Runtime workspaces\n8.0 Known problems and limitations\n9.0 Troubleshooting\n10.0 Quick Start Scenario\n\n\n1. Introduction\n===============\n\nThis feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency.\n\nThe feature is enabled by default. The administrator can enable/disable it by setting a new environment variable \nKXX_FCP_SCRIPT=true/false (default true)in the agent configuration file, where XX can be:\n\n- LZ for Linux OS agent \n- UX for Unix OS agent\n- NT for Windows OS agent\n\nThis is an overview of the scripting feature; details will be provided in the following sections.\n\nThe OS agent loops, at a configurable interval, looking for script definition property files (*.properties) in a configurable directory path.\nThe property files are parsed and OS Monitoring Agent spawns a new process named “fcp_daemon” if at least one valid script definition is found. This new daemon is responsible for scheduling the script executions and gathering all information regarding running scripts.\n\nAccording to another configurable interval, the OS agent loops getting the execution script results from the fcp_daemon.\nThe OS Agent is able to parse the script standard output, splitting each row in up to 16 attributes.\nAn event is sent for each standard output row of the script and these events can be caught by pure event situations.\n\n1.1 Quick Start\n================\nThe feature is enabled with default values as soon as the OS agent is started. The only action to start using the feature is the following:\n- create a property file under default directory (on Linux/UNIX is $CANDLEHOME/localconfig/<product code>/scripts_definitions, on Windows is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions) using as an example the provided template script_property.txt.\n\nOnly two properties are required:\nATTRIBUTE_NAME=Any name used to uniquely identify the script definition inside the property file.\nSCRIPT_PATH_WITH_PARMS=The fully qualified path of the script with arguments. \n\nNot only shell scripts but also perl and other types of scripts can be used. You just need to specify the full command to execute in the SCRIPT_PATH_WITH_PARMS property. \nFor example, \"perl C:\\IBM\\scripts\\ITM_Custom_Scripts\\date.pl\". In this example you need to make sure that the location of \"perl\" can be resolved by the agent through the PATH variable in its environment. Specify the full path where \"perl\" is installed otherwise.\n\nFurther properties and details can be found in this document and in the template script_property.txt under $CANDLEHOME/localconfig/lz/scripts_definitions. \n\n\n2. New Attribute groups\n=======================\n\nTwo new attribute groups have been added for this feature as detailed below. Statistic and execution data of all the scripts are stored in these two tables. The name of the property file (Property_File) and the attribute name defined in the property file (Attribute_Name) are the 2 key fields of these two tables. These two keys must be used in situation conditions to filter rows related to a specific script.\n\nAttribute group: KXX_Custom_Scripts (multiple rows), table: KXXSCRPTS (sampled).\nDescription: Configuration and statistic data gathered using custom scripts. It contains a row for each defined script, information on the fcp_daemon and on property files:\n\nAttribute Size Description\n=========================== ===== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Name 512 The name of the script.\nScript_Path 512 The fully qualified path name of the script with arguments.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting.\nStandard_Output_Type 4 Standard output type of the script.\nStatus_Code 4 The status of the script. It includes general errors, configuration errors, the status or the execution code returned by the \nScript Provider.\nExecution_Start 16 The time when the last execution of this script started.\nExecution_Duration 4 The duration of the last execution of this script, in seconds. When timing out, the value of the configured timeout is returnd.\nAverage_Execution_Duration 4 The average duration, in seconds, of all the execution of the script.\nRefresh_Interval 4 The interval, in seconds, that the agent attempts to start this script.\nNumber_of_Collections 4 The count of execution attempts of this script since agent started.\nIntervals_Skipped 4 The count of occurrences where an execution of this script is skipped because the previous execution is still running.\nProperty_Group 64 The name of the property group.\nReturn_Code 4 Integer value returned by the Script.\nCust_Label_Str1 16 Label for custom string attribute #1\nCust_Label_Str2 16 Label for custom string attribute #2\nCust_Label_Str3 16 Label for custom string attribute #3\nCust_Label_Str4 16 Label for custom string attribute #4\nCust_Label_Str5 16 Label for custom string attribute #5\nCust_Label_Int1 16 Label for custom integer attribute #1\nCust_Label_Int2 16 Label for custom integer attribute #2\nCust_Label_Int3 16 Label for custom integer attribute #3\nCust_Label_Int4 16 Label for custom integer attribute #4\nCust_Label_Int5 16 Label for custom integer attribute #5\nCust_Label_Float1 16 Label for custom floating point attribute #1\nCust_Label_Float2 16 Label for custom floating point attribute #2\nCust_Label_Float3 16 Label for custom floating point attribute #3\nCust_Label_Float4 16 Label for custom floating point attribute #4\nCust_Label_Float5 16 Label for custom floating point attribute #5\nStandard_Error 2048 Script Standard Error in a unique row\n\nIn addition to script definitions, the table may report rows to return errors found on property files and they are identified by @ANY@ as Attribute_Name. Moreover, a row is always used to report the status of fcp_daemon and it is identified by @ANY@ as Property_File and @ANY@ as Attribute_Name.\n\nAttribute group: KXX_Custom_Scripts_Runtime (multiple rows), table: KXXSCRRTM (pure).\nDescription: Data gathered using custom scripts. It contains the output rows of the scripts currently running:\n\nAttribute Size Description\n======================= ==== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Path 512 The fully qualified path of the script.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting. \nReturn_Code 4 Integer value returned by the Script.\nRow_Number 4 Output row number.\nStandard_Output_Type 4 Standard output type of the script.\nStandard_Output_String 2048 Script Standard Output in String Format.\nStandard_Output_Integer 8 Script Output in Integer Format\nStandard_Output_Float 8 Script Output in Floating Point Format (2 decimals).\nCust_Attr_Str1 64 Custom string attribute #1\nCust_Attr_Str2 64 Custom string attribute #2\nCust_Attr_Str3 64 Custom string attribute #3\nCust_Attr_Str4 64 Custom string attribute #4\nCust_Attr_Str5 64 Custom string attribute #5\nCust_Attr_Int1 8 Custom integer attribute #1\nCust_Attr_Int2 8 Custom integer attribute #2\nCust_Attr_Int3 8 Custom integer attribute #3\nCust_Attr_Int4 8 Custom integer attribute #4\nCust_Attr_Int5 8 Custom integer attribute #5\nCust_Attr_Float1 8 Custom floating point (2 decimals) attribute #1\nCust_Attr_Float2 8 Custom floating point (2 decimals) attribute #2\nCust_Attr_Float3 8 Custom floating point (2 decimals) attribute #3\nCust_Attr_Float4 8 Custom floating point (2 decimals) attribute #4\nCust_Attr_Float5 8 Custom floating point (2 decimals) attribute #5\n\nNote: different status conditions can be monitored using the Status_Code field in the statistic table KXX_Custom_Scripts. \nThe following detailed list provides different values for the Status_Code field: \n\nInitial general statuses\nUNKNOWN_ERROR (status code=0) --> Error\nNO_ERROR (status code=1) --> Informational\n\nGeneral daemon statuses\nFEATURE_NOT_ENABLED (status code=40) --> Informational\nDAEMON_STARTING (status code=2) --> Informational\nDAEMON_STARTED (status code=3) --> Informational\nDAEMON_STOPPING (status code=4) --> Informational\nDAEMON_STOPPED (status code=5) --> Informational\nDAEMON_STOPPING_AT_AGENT_STOP (status code=6) --> Informational\nDAEMON_STOPPED_AT_AGENT_STOP (status code=7) --> Informational\nDAEMON_ERROR (status code=8) --> Error\nDAEMON_ERROR_NO_RESTART (status code=9)-> Fatal Error\n\nGeneral directory statuses\nERROR_OPENING_PROP_DIRECTORY (status code=10) --> Error\nPROP_DIRECTORY_NOT_FOUND (status code=11) --> Error\nNO_SCRIPT_DEFINED (status code=12)--> Warning\n\nProperty file statuses\nPROP_FILE_NOT_FOUND (status code=13) --> Error\nERROR_OPENING_PROP_FILE (status code=14) --> Error\n\nScript definition statuses\nSCRIPT_ADDED (status code=15) --> Informational\nSCRIPT_CHANGED (status code=16) --> Informational\nSCRIPT_REMOVED (status code=17) --> Informational\nSCRIPT_INACTIVE (status code=18) --> Informational\nNO_SCRIPT_PATH (status code=21)--> Error\nSCRIPT_PATH_INVALID (status code=22)--> Error\n\nExecution statuses from the fcp_daemon\nFACTORY_UNKNOWN_ERROR (status code=23) --> Error\nFACTORY_NO_ERROR (status code=24)--> Informational\nGENERAL_ERROR (status code=25)--> Error\nOBJECT_NOT_FOUND (status code=26)--> Error\nOBJECT_CURRENTLY_UNAVAILABLE (status code=27)--> Error\nNO_INSTANCES_RETURNED (status code=28)--> Error\nNO_RESPONSE_RECEIVED (status code=29)--> Error\nAUTHENTICATION_FAILED (status code=30)--> Error\nACCESS_DENIED (status code=31)--> Error\nTIMEOUT (status code=32)--> Error\nNOT_IMPLEMENTED (status code=33)--> Error\nRESPONSE_TOO_BIG (status code=34) --> Error\nGENERAL_RESPONSE_ERROR (status code=35)--> Error\nSCRIPT_NONZERO_RETURN (status code=36)--> Error\nSCRIPT_NOT_FOUND (status code=37)--> Error\nSCRIPT_LAUNCH_ERROR (status code=38)--> Error\nINVALID_TOKEN_TYPES(status code=39) --> Error\n\n3. Parameters in OS agent environment files\n===========================================\n\nIt is possible to customize the feature setting parameters in the OS agent environment files:\n- $CANDLEHOME/config/lz.ini file for the Linux OS agent\n- $CANDLEHOME/config/ux.ini for the UNIX OS agent\n- %CANDLE_HOME%\\TMAITM6_x64\\KNTENV for Windows 64bit OS agent\n- %CANDLE_HOME%\\TMAITM6\\KNTENV for Windows 32bit OS agent\n\nThe scripting feature is enabled by default. To disable it set:\n- KXX_FCP_SCRIPT=false\n\nOther parameters can be defined inside the agent environment files based on specific needs:\n\n- KXX_FCP_SCRIPT_DEFINITIONS (default location on Linux/UNIX is $CANDLEHOME/localconfig/<product code>/scripts_definitions, on Windows it is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions)\nThe location where property files are stored.\n\n- KXX_FCP_SCRIPT_INTERVAL (default 60 sec)\nOS agent uses the value of this variable as loop interval in seconds to check execution of running scripts and it sends events if the filter condition is satisfied. The minimum value is 30 seconds, the maximum value is 300 seconds. Invalid values will be reset to the default.\nNote: this parameter is ignored if KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT (see definition below).\n\n- KXX_FCP_SCRIPT_SYNC_INTERVALS (USE_AGENT|USE_SCRIPT|NO - default USE_AGENT)\nIf the agent looping interval defined by KXX_FCP_SCRIPT_INTERVAL is bigger than the script execution frequency, it can happen that data produced by some of the script execution loops is lost.\nTo avoid this behaviour the script execution frequency can be synchronized with the agent looping interval setting the KXX_FCP_SCRIPT_SYNC_INTERVALS to:\n- USE_AGENT; the value of each script execution frequency is forced to be the maximum between KXX_FCP_SCRIPT_INTERVAL and EXECUTION_FREQUENCY defined in its property file. \n- USE_SCRIPT; the agent looping interval is dynamically set to the minimum frequency value (EXECUTION_FREQUENCY in property file) between all of the defined scripts . The value set by KXX_FCP_SCRIPT_INTERVAL is ignored. The frequency of the scripts remain the ones defined in the property files. When using USE_SCRIPT, the agent looping interval may change every time a script definition is added, changed or removed. In any case, it cannot be lower than the value set by KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT or bigger than 300 seconds.\n- NO; no synchronization is performed and some execution results could be lost.\n\n- KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL (default 300 sec) \nAt startup and at every interval defined by this variable, the OS agent checks for any changes in scripts or property files.\nNote that if KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL is less than the agent looping interval it will be reset to the agent looping interval. The maximum allowed value is the default, 300 seconds.\n\n- KXX_FCP_USER (default OS agent user)\nThis parameter is valid only on linux and unix platforms. It defines the user used to spawn fcp_deamon process if different from OS agent process user; all the scripts are executed by this user. Note that the user owner of the OS agent must have correct permission to spawn the fcp_daemon process. On windows a different user must be defined as login of the service \"Monitoring Agent for Windows OS - FCProvider\". The user must have \"Full Control\" permission to CANDLE_HOME and scripts repository directories. For more information please refer to official IBM Monitoring documentation: \nhttp://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/oswin/running_as_a_non-admin_user.htm [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/oswin/running_as_a_non-admin_user.htm]\n\n- KXX_FCP_MAX_CDP_DP_THREAD_POOL_SIZE (default 10)\nIt defines the maximum concurrent number of scripts to be executed. Maximum value is 32.\n\n- KXX_FCP_MAX_DAEMON_RESTARTS (default 4)\nThe OS agent watches the fcp_daemon: if an abnormal exit of process occurs, the OS agent restarts it. This is done for the KXX_FCP_MAX_DAEMON_RESTARTS (times at a day). \nThe value 0 must be used to avoid the restart; if -1 is set, the OS agent retries to restart fcp_daemon forever. The restart counter is reset at OS agent restart.\n\n- KXX_FCP_SEND_SCRIPT_RUNTIME_EVENTS (default: true)\nIf set to false, the OS agent stops sending events for each row of script standard output. In this case script outputs are visible on TEP console workspaces but no situations will be displayed and no historical collection data will be collected. \n\n- KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT (default: 5 seconds) \nIt is used when KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT. In this condition, it sets the minimum value of the OS agent looping interval.\nUsing low values for the the OS agent looping interval (less than 5 seconds) is highly invasive and can impact OS agent performances. If a frequent data collection is needed (e.g. every second), it is strongly suggested to customize a script that caches data at the needed frequency and returns the collected data to the OS agent at an higher interval (e.g. every 60 seconds).\n\n\nThe following Agent Builder (CDP) variables can also be used to control the behavior of the fcp_daemon:\n\n- CDP_DP_REFRESH_INTERVAL (default 60 sec) Global script scheduled start time. Used if the frequency is not passed in the script property file.\n\n- CDP_DP_SCRIPT_TIMEOUT (default 30 sec) Global script execution maximum time. When the execution time of a script exceeds this limit, its Status_Code is set to TIMEOUT\n\n- CDP_DP_KILL_ORPHAN_SCRIPTS (Y|N - default N) Global behaviour used by fcp_daemon process for timing out scripts. When set to 'Y', the scripts are killed, otherwise they are abandoned. This value is ignored for a specific script if the KILL_AFTER_TIMEOUT key is set in the script property file\n\n- CDP_MAXIMUM_ROW_COUNT_FOR_CPCI_DATA_RESPONSES (default 1000) Global value added for performance reasons to limit the maximum number of output rows returned by the scripts. Additional rows after this limit are ignored. Allowed values are positive integer. Invalid values means no limit.\n\nThe fcp_daemon also supports the other environment variables used to control Agent Builder agents. For a complete list see the official Agent Builder documentation here:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3/agentbuilder63_user.pdf [http://publib.boulder.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.itm.doc_6.3/agentbuilder63_user.pdf]\n\n4. Parameters in property files \n===============================\n\nThe KXX_FCP_SCRIPT_DEFINITIONS directory contains a list of *.properties files. Each property file contains a list of \nscripts to run with respective properties in the form of key=value. The properties that can be defined (case in-sensitive) are: \n\n- ATTRIBUTE_NAME (Required - string max 256 characters).\nIt is a name of your choice that defines a specific script and its attributes. The characters that can be used for the \nATTRIBUTE NAME name can be alphabetical, numeric and only the underscore can be used as a special character. If other special characters (even a blank is considered this way) are used they get converted into underscore (_).\nWhen multiple scripts are listed inside the same property file, more different ATTRIBUTE_NAME must be defined (one for each script). It must be the first value specified for each defined script and delimits the start of the properties set for the specific script until the next ATTRIBUTE_NAME.\n\n- SCRIPT_PATH_WITH_PARMS (Required - string max 512 characters).\nIt defines the full path to the script with parameters, separated by a blank. No special characters can be used in the script path name. \nValues containing blanks must be enclosed in single (') or double quotes (\").\nEnvironment variables can be passed, but only enclosed in ${...} for all the platforms. Environment variables must be available in the OS agent process context.\n\n- EXECUTION_FREQUENCY (Optional - default 60 sec).\nIt indicates the script execution frequency.\n\n- CUSTOM_NAME (Optional - string max 256 characters)\nThe user can fill it with a description of the script.\n\n- IS_ACTIVE (true|false - Optional - default true). \nIt activates the script. If false, the script is not executed.\n\n- DISABLE_USE_AGENT_SYNC (true|false - Optional - default false). If true, the EXECUTION_FREQUENCY of the script is respected also if the global variable KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_AGENT.\n\n- KILL_AFTER_TIMEOUT (true|false - Optional - default value defined by the CDP_DP_KILL_ORPHAN_SCRIPTS variable). \nWhen true the script is killed after timeout (a timeout occurs when script execution is greater than the value specified by CDP_DP_SCRIPT_TIMEOUT parameter in OS agent configuration file) otherwise it is ignored. In both cases no data is collected. Note that when KILL_AFTER_TIMEOUT is set, only the script defined in property file is killed and not child processes (if any) spawned by the script. This feature is not supported by Solaris and Windows 32 bit OS agents and any timing out scripts are abandoned. \n\n\nOutput rows returned by a script are parsed. The script returns a standard output (called hereafter as first token). When the script returns more values in the output row they are added as additional tokens for a maximum of 5 strings, 5 integers and 5 floats following a predefined syntax as described below:\n\n- OUTPUT_TYPE (STRING|INTEGER|FLOAT - Optional - default string). It defines the type of the first token returned by each row of the script;\nOUTPUT_TYPE can be:\n1. STRING (default): strings up to 2048 characters. When used, the \"Standard_Output_String\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n2. INTEGER: allows getting numeric values between -9223372036854775806 and 9223372036854775806. When used, the \"Standard_Output_Integer\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n3. FLOAT: allows getting numeric values between -92233720368547758.06 and 92233720368547758.06,(with 2 decimal\nprecision). When used, the \"Standard_Output_Float\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n\n- TOKEN_TYPES (STRING|INTEGER|FLOAT - Optional).\nIt defines the output type of additional tokens after the first one. The user can define a maximum of 5 strings, 5 integers and 5 floats. It is a list of types separated by commas:\n<token_type>,<token_type>,…\ntoken_type can be empty or one from (case insensitive):\n- STRING or S\n- INTEGER or I\n- FLOAT or F\nIf <token_type> is empty, the corresponding token is skipped.\nExamples of the same valid layouts:\n- TOKEN_TYPES=S,I,S,,,F,,F,F\n- TOKEN_TYPES=String,integer,S,,,Float,,f,FLOAT\n\n- TOKEN_LABELS (STRING - maximum 16 characters each label - Optional). \nIt defines the labels of the tokens defined in TOKEN_TYPES. This value is a list of token labels separated\nby commas, and must correspond to the tokens defined by TOKEN_TYPES. \ne.g.:\n- TOKEN_TYPES=S,I,S,,,F,,F,F\n- TOKEN_LABELS=Cpu Name,Cpu number,Description,,,value 1,,value 2,value 3 \nIt is ignored if TOKEN_TYPES is not set.\n\n- TOKEN_SEPARATOR (Optional - default semicolon \";\"). \nIt sets the string to be used as separator to split the output row in tokens. It is ignored if TOKEN_TYPES is not set. Empty value (blank) is accepted as separator and multiple consecutive blanks in output rows are considered as a single one.\n\n\nThe following two parameters allow you to filter the rows output of a script; they are applied by the OS agent only to the first token and they must be used together:\n\n- FILTER_VALUE (Optional).\nThe value used for comparison. It is required if FILTER_OPERATOR is defined.\nIf the OUTPUT_TYPE is a string, the filter value must reflect exactly the string value returned by the script that is intended to be filtered, without any additional quotes (no wildcards allowed).\n- FILTER_OPERATOR (Optional).\nThe operator used for the comparison. It is required if FILTER_VALUE is defined. Accepted FILTER_OPERATOR values include:\n= (equal to)\n!= (different from)\n> (bigger than) only for numeric type\n>= (not lower than) only for numeric type\n< (lower than) only for numeric type\n<= (not bigger than) only for numeric type\n\n\n\n5. Examples of property file\n============================\n\n#First script definition: script ex_script1.sh is launched every 150 seconds, it returns float values and only the output rows equal to 0.5 will be considered by the agent.\n\nATTRIBUTE_NAME=sample1 \nSCRIPT_PATH_WITH_PARMS=/opt/ibm/itmd4255a/localconfig/lz/scripts_definitions/ex_script1.sh\nEXECUTION_FREQUENCY=150\nOUTPUT_TYPE=FLOAT\nFILTER_VALUE=0.5\nFILTER_OPERATOR==\n\n#Second script definition: script ex_script2 is launched every 60 seconds, it returns integer values and only the rows different from 0 will be considered by the agent.\n\nATTRIBUTE_NAME=ex_script2\nSCRIPT_PATH_WITH_PARMS=${CANDLE_HOME}/tmp/check_out.sh\nEXECUTION_FREQUENCY=60\nOUTPUT_TYPE=INTEGER\nFILTER_VALUE=0\nFILTER_OPERATOR=!=\n\n#Third script definition: script ex_script3.sh is launched every 120 seconds with 3 input parameters (the first input parameter is an integer, the second and third are string). It's killed if it hangs or if the execution time is greater than the timeout value.\n\nATTRIBUTE_NAME=ex_script3 \nSCRIPT_PATH_WITH_PARMS=/opt/scripts/ex_script3.sh 1 \"second input parameter\" \"third input parameter\" \nEXECUTION_FREQUENCY=120\nOUTPUT_TYPE=STRING\nKILL_AFTER_TIMEOUT=TRUE\n\n#Fourth script definition: script cpu_mem_percentage.sh is launched every 50 seconds and returns the cpuid as standard output string and 2 float for Idle and Used CPU percentage and 2 integers for Memory and Virtual Memory usage. The pipe is used as separator to parse the output. An example of row that must be returned by the script is: \ncpu2|35,5|65,5|3443|123800\n\nATTRIBUTE_NAME=cpu and mem Usage\nSCRIPT_PATH_WITH_PARMS=${SCRIPT_HOME}/cpu_mem_percentage.sh\nOUTPUT_TYPE=STRING\nTOKEN_TYPES=F,F,I,I\nTOKEN_LABELS= Idle CPU %, Used CPU %, Virt MEM used MB, MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=50\n\n6. Examples of private situations \n==================================\n\nThe private situations definitions can be inserted into the xx_situations.xml under $CANDLEHOME/localconfig/lz for linux or $CANDLEHOME/localconfig/ux for unix or %CANDLE_HOME%\\localconfig\\nt for Windows to monitor scripts execution.\nExamples below are for the Linux OS agent:\n\n<PRIVATESIT>\n<!-- Sends an alert if the script defined by attribute name \"demo\" in property file \"demo.properties\" returns a row equal to \"demo.log\" -->\n<SITUATION>FCP_CheckLOGFileExists_pr</SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts_Runtime.Property_File *EQ 'demo.properties' *AND *VALUE KLZ_Custom_Scripts_Runtime.Attribute_Name *EQ 'demo' *AND *VALUE KLZ_Custom_Scripts_Runtime.Standard_Output_String *EQ 'demo.log']]>\n</CRITERIA>\n</PRIVATESIT>\n\n<PRIVATESIT>\n<!-- Sends an alert if a script exits with a return code different from zero -->\n<SITUATION>FCP_ScriptRetCode_pr</SITUATION>\n<CRITERIA>\n<![CDATA[*IF *VALUE KLZ_Custom_Scripts.Return_Code *NE 0]]>\n</CRITERIA>\n</PRIVATESIT>\n\n<privatesit>\n<!-- Sends an alert when script path is not defined in a property file -->\n<SITUATION NAME=\"FCP_NOPTAH\" INTERVAL=\"000030\" ></SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts.Status_Code *EQ NO_SCRIPT_PATH]]>\n</criteria>\n</privatesit>\n\n<privatesit>\n<!-- Sends an alert when a script cannot be launched -->\n<SITUATION NAME=\"FCP_ScriptLaunchErr\" INTERVAL=\"000060\" ></SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts.Status_Code *EQ SCRIPT_LAUNCH_ERROR]]>\n</criteria>\n</privatesit>\n\n\n7. Custom Scripts and Custom Scripts Runtime Workspaces\n=======================================================\n\nA new OS agent navigation item has been added in the TEP console. It contains two workspaces: \"Custom Scripts\" and \"Custom Scripts Runtime\". \n\n\"Custom Scripts\" workspace contains the following views:\n- \"Factory Daemon Status\" table view showing informational/warning/error events related to the fcp_daemon process.\n- \"Properties Files error\" table view showing problems related to property files.\n- \"Number of execution per script\" bar chart view summarizing the executions of defined scripts\n- \"Defined Scripts\" table view showing detailed information of defined scripts.\n\n\"Custom Scripts Runtime\" workspace is called clicking on the anchor of a specific script and provides information on script execution. The views provided by default on the TEP console are to be intended as example workspaces with all available custom attributes. Users can duplicate and customize workspaces to filter out fields that are not needed according to the output returned by their scripts.\n\n\n8. Known problems and limitations\n===================================\n\n- The Scripting Feature is not supported on Windows 2003 64-bit systems.\n- Kill after timeout does not work on Solaris and Windows 32 bit OS agents.\n- The fcp_daemon may stop executing scripts in Windows 32 bit If some scripts do not complete within the time out period and the user has turned on intensive tracing. If this happens the data reported on the TEP will reflect the last time the script was actually run. It is also possible that the OS agent will stop returning data. Terminating the fcp_daemon process will allow the agent to resume proper operation.\n- SCRIPT_NONZERO_RETURN is returned instead of SCRIPT_NOT_FOUND or SCRIPT_LAUNCH_ERROR on Solaris.\n- The scripting feature does not provide full Native Language Support; some issues may be found using Nationalized characters in property files or script outputs.\n- On windows OS agent there is no possibility of executing scripts residing on a mapped network drive.\n\n9. Troubleshooting\n===================\n\nStandard KBB_RAS1 variable will apply to the OS agent and to the fcp_daemon processes.\nTo apply a specific trace setting to fcp_daemon only, use the KXX_FCP_KBB_RAS1 variable; when KXX_FCP_KBB_RAS1 is set, the value specified by KBB_RAS1 is ignored by fcp_daemon.\n\nTo trace the operations logged by the OS agent core threads of the feature:\nKBB_RAS1=ERROR (UNIT:factory ALL)\n\nTo trace scripting queries from the ITM server and events sent to the server, add the entries:\n(UNIT:klz34 ALL) (UNIT:klz35 ALL) on Linux OS agent\n(UNIT:kux48 ALL) (UNIT:kux49 ALL) on Unix OS agent\n(UNIT:knt84 ALL) (UNIT:knt85 ALL) on Windows OS agent\n\nTo view tema traces to verify private situation execution, add the entries:\n(UNIT:kraavp all) (UNIT:kraapv all)\n\nTo see the execution of the scripts and how the data from the scripts is being parsed set:\nKXX_FCP_KBB_RAS1=Error (UNIT:command ALL)\n\nTo troubleshoot problems in the communication between the os agent and fcp_daemon add this trace level to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket FLOW) (UNIT:cpci FLOW)\n\nTo see the interaction between the OS agent process and the fcp_daemon in detail add to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket ALL) (UNIT:cpci ALL)\n\n\n10. Quick Start Scenario\n=========================\n\nThe following section describes the minimum steps needed to configure a linux OS agent to run 2 custom scripts.\n\nCustom Scripts descriptions\n===========================\nLet's suppose the user has 2 scripts under a directory /scripts_repo:\n\n- checkDIRsize.sh that checks the size of a specified directory passed as input parameter. Its output is an integer like the following: \n\n4594740\n\n- cpu_mem_usage.sh that checks the used CPU percentages and used Swap Memory megabytes. Its output is returned in the following form:\n\ncpu1|96,5|23800\n\nwhere the first token is the CPU id, the second token is the used CPU percentage, the third token is the used swap memory in megabyte.\n\nCustomization needed to have the linux OS agent run above scripts\n==============================================================\nThe feature is enabled with default values as soon as the OS agent is started:\n\n- you could create one or two property files (<Any Name>.properties)under the default directory $CANDLEHOME/localconfig/lz/scripts_definitions. In this example let's create 2 property files one for each script called checkDIRsize.properties and cpu_mem_usage.properties:\n\n#CheckDIRsize.properties\nATTRIBUTE_NAME=OPT_DIR_SIZE\nSCRIPT_PATH_WITH_PARMS=/scripts_repo/checkDIRsize.sh /opt\nEXECUTION_FREQUENCY=20\nOUTPUT_TYPE=INTEGER\n\n#cpu_mem_usage.properties \nATTRIBUTE_NAME=cpu_mem_usage\nSCRIPT_PATH_WITH_PARMS=/scripts_repo/cpu_mem_percentage.sh\nOUTPUT_TYPE=string\nTOKEN_TYPES=F,I\nTOKEN_LABELS= Used CPU %, Swap MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=10\n\n- There is no need to restart the OS agent after adding (or changing) the 2 property files above: the OS agent checks script definition directory with a specified time interval (default value 300 seconds). Open the TEP console and under the \"Custom Scripts\" workspace the scripts details and results are shown.\n\nChange History:\n----------------------\n2017-01-09: Added new item under \"8. Known problems and limitations\" that the Scripting Feature is not supported on Windows 2003 64-bit systems."
}
] |
DEV_Q159 | Help with Security Bulletin: IIB is affected by WebAdmin Session Timeout vulnerability (CVE-2017-1693)
I need to understand details regarding Security Bulletin: IBM Integration Bus is affected by WebAdmin Session Timeout vulnerability (CVE-2017-1693). Where can I find this information? | - | true | [] |
DEV_Q160 | How to increase the HTTP Session time-out value for Workplace application on WebSphere Application Server?
We would like to increase the HTTP Session time-out value for our Workplace application. Where are all the locations that this value is set and what are their precedence? | The HTTP Session time-out can be set in the following places:
From the Administrative Console at the server, Enterprise application, and Web application levels
At the time when the application is packaged
In the application code | false | [
{
"filename": "swg21163875.txt",
"text": "Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere 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\n\n\nSetting 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. \n\n\n3. 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. \n\nThis 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. \n\n1. Server Level [/support/docview.wss?uid=swg21163875&aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&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"
}
] |
DEV_Q161 | Netcool/Impact 7.1.0: The StateChange value being used by the OMNIbusEventReader is too high
The value being used is a date and time in the future and as such is preventing the EventReader from capturing the current events. | The simplest solution is to manually reset the EventReader StateChange value via the GUI. Stop the EventReader, open it for edit, click the "Clear State" button, exit the editor and restart the EventReader. | false | [
{
"filename": "swg21610844.txt",
"text": "Title: IBM EventReader stops reading events, StateChange value too high - United States\n\nText:\nnetcool; impact; netcool/impact; nci; event; reader; eventreader; omnibus; omni; omnibuseventreader; state; change; statechange; date; time; datetime; value; future; high; stamp; timestamp; advanced; advance; forward; ahead; before; after; current; jrexec; jrexecaction; jrexecserver; jrexecaction()' server; action; function; command; line; interface; cli; commandlineinterface TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to deal with an EventReader that is using an inadvertently future dated StateChange value. \n\nSYMPTOM\nThe EventReader stops acquiring events that are pertinent for processing because it is using a StateChange value that is too high.\n\n\nCAUSE\nAn event has had its StateChange value artificially increased by some unknown component (Probe, Trigger, etc) to reflect a future date. The EventReader captures the event and then uses the highest captured StateChange value in its outgoing SQL to capture pertinent events.\n\nDIAGNOSING THE PROBLEM\nPertinent events are not being processed. Looking in the EventReader log file the number of events being captured in each Read is 0. Testing the SQL being used in an nco_sql session produces a 0 result too. Testing the SQL again in an nco_sql session without the \"and StateChange >= 1234567890\" clause returns all the unprocessed rows.\n\nRESOLVING THE PROBLEM\nSomething has \"future dated\" the StateChange value of an event in the ObjectServer, the EventReader captured the event and, since the EventReader will use the highest StateChange value captured in the previous poll in the SQL of its next poll, this then future dated the value used in the EventReader. The EventReader will persist with this value (and will increment it by 1 every other poll) until such a time as it captures an event with a higher StateChange value.\n\n\n\n\n\nThe simplest solution is to manually reset the EventReader StateChange value via the GUI. Stop the EventReader, open it for edit, click the \"Clear State\" button, exit the editor and restart the EventReader.\n\nAn alternate solution is to perform this operation via the Command Line Interface:\n\n\n\n * telnet [Hostname] [Port]\n\n\nwhere [Hostname] is the resolvable hostname of the ImpactServer host and [Port] is the CLI port number (2000, by default). You will need to supply a suitable username (admin, for example) and password. Then at the READY prompt enter the series of commands: \n\n * Update Service set Running=false where Name='[EventReaderName]';\n * \n * Update Service set ClearState=true where Name='[EventReaderName]';\n * \n * Update Service set Running=true where Name='[EventReaderName]';\n\n\nwhere [EventReaderName] is the name of the EventReader that requires this restart process. \n\nIn cases where the likelihood of StateChange being inappropriately incremented in this fashion is quite high, one might wish to automate this process and have a Policy hunt for such occurrences. Please find following an example of a \"hunter\" Policy to capture any reoccurrence of this issue: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * ANN=\"AcquireStateChange\"; \n Log(2,ID+ANN); \n Script=\"/opt/IBM/netcool/impact/bin/CheckState.sh\"; \n Parameter=\"password\"; \n JRExecAction(Script, Parameter, false, 30); \n NumExecOutput=Length(ExecOutput); \n Log(3,ID+ANN+\": NumExecOutput: \"+NumExecOutput); \n \n If(NumExecOutput >= 1) \n { * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * Log(ID+ANN+\": CurrentStateChange: \"+HumanStateChange+\" is greater than CurrentTime: \"+HumanCurrentTime); \n Log(ID+ANN+\": !!! Clearing EventReader State !!!\"); \n Script=\"/opt/IBM/netcool/impact/bin/ClearState.sh\"; \n Parameter=\"password\"; \n JRExecAction(Script, Parameter, false, 30); \n * \n * \n * \n * \n * \n * Log(1,ID+ANN+\": CurrentStateChange: \"+HumanStateChange+\" is less than CurrentTime: \"+HumanCurrentTime); \n * \n * \n * \n * \n * \n * Log(ID+ANN+\": !!! There is some freaky stuff happening here !!! - CurrentStateChange: \"+HumanStateChange+\" and CurrentTime: \"+HumanCurrentTime+\" !!! \"); \n * \n \n } \n Else \n { * \n \n } \n * \n * \n * \n * \n * \n * Log(3,ID+ANN+\": No UnprocessedEvents\"); \n * \n * \n * \n * \n * \n * \n\n\nAs you can see this is designed to be run by a PolicyActivator and checks for events that have been around in the ObjectServer for a while (a minute) and are pertinent for processing by Impact (ImpactFlag = 1), but have not. If it finds any it then acquires the StateChange value from the .state file via JRExecServer using the example script referred to in the above example Policy as CheckState.sh: \n\n * \n * \n * \n * \n * \n * \n * \n\n\nIf the Policy finds the string it extracts the StateChange value and compares it against the current time and, if StateChange exceeds the current time, it undertakes the stop, clear and restart of the EventReader to bring StateChange back into line. \n\nThis examples a simple script to use the Command Line Interface to stop the EventReader, clear the StateChange value and restart the EventReader and is referred to in the above exampled Policy as ClearState.sh: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nPlease note that the ClearState.sh script should not contain any spaces or special characters otherwise calling EOF will throw errors. Also, in latter versions of Impact, the username and password should be those of the tipadmin. Additionally, rather than have the password sitting clear case in a script one can pass it as a JRExecAction Parameter from the Policy - still clear case but the relevance of the variable can be made less obvious. \n\nBoth of these scripts are called by the JRExecAction() function in the example Policy and this in turn requires the JRExecServer to be running on the ImpactServer host(s *). \n\n* - The JRExecServer will be used by the current Primary ImpactServer only, as all EventReaders and PolicyActivators are run on the current Primary only but, if and when failover occurs and the Secondary ImpactServer becomes Primary, this new Primary will require access to a running, local JRExecServer. So, JRExecServer has to be running on both Primary and Secondary ImpactServer hosts to ensure availability in case of failover. Some additional information about the JRExecAction() function is available from the TechNote \"JRExecAction() function usage\" [Link Below] \nRELATED INFORMATION\n JRExecAction() function usage [http://www-01.ibm.com/support/docview.wss?uid=swg21515756]"
}
] |
DEV_Q162 | Is there a security vulnerability in the IBM WebSphere Application Server shipped with IBM Tivoli Netcool Configuration Manager?
Is there a security vulnerability in the IBM WebSphere Application Server shipped with IBM Tivoli Netcool Configuration Manager? | Please consult the security bulletin Vulnerability in Apache Commons affects IBM WebSphere Application Server (CVE-2015-7450) [http://www-01.ibm.com/support/docview.wss?uid=swg21970575] for vulnerability details and information about fixes. | false | [
{
"filename": "swg21972146.txt",
"text": "Title: IBM Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server shipped with IBM Tivoli Netcool Configuration Manager (CVE-2015-7450) - United States\n\nText:\nITNCM; Security Bulletin; CVE-2015-7450; websphere SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as a component of IBM Tivoli Netcool Configuration Manager. Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nPlease consult the security bulletin Vulnerability in Apache Commons affects IBM WebSphere Application Server (CVE-2015-7450) [http://www-01.ibm.com/support/docview.wss?uid=swg21970575] for vulnerability details and information about fixes.\nCVEID: CVE-2015-7450 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7450]\nDESCRIPTION: Apache Commons Collections could allow a remote attacker to execute arbitrary code on the system, caused by the deserialization of data with Java InvokerTransformer class. By sending specially crafted data, an attacker could exploit this vulnerability to execute arbitrary Java code on the system.\nCVSS Base Score: 9.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107918 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107918] 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:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version ITNCM version 6.4.1.3\nITNCM version 6.3.0.6 Embedded IBM WebSphere Application Server eWAS 7.0 REMEDIATION/FIXES\n \n\n<Product VRMF APAR Remediation/First Fix ITNCM 6.4.1.3 IF001 none http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Netcool+Configuration+Manager&release=6.4.1.3&platform=All&function=fixId&fixids=ITNCM_6.4.1.3_IF001&includeRequisites=1&includeSupersedes=0&downloadMethod=http [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Netcool+Configuration+Manager&release=6.4.1.3&platform=All&function=fixId&fixids=ITNCM_6.4.1.3_IF001&includeRequisites=1&includeSupersedes=0&downloadMethod=http] ITNCM 6.3.0.6 IF004 none http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7ETivoli&product=ibm/Tivoli/Tivoli+Netcool+Configuration+Manager&release=6.3.0.6&platform=All&function=all [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7ETivoli&product=ibm/Tivoli/Tivoli+Netcool+Configuration+Manager&release=6.3.0.6&platform=All&function=all] \nFor ITNCM 6.2.x IBM recommends upgrading to a fixed, supported version/release/platform of the product. \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] \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] *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."
}
] |
DEV_Q163 | How to fix XAER_RMFAIL messages in WebSphere Portal's SystemOut.log?
SystemOut.log contains various exceptions with caused by statements like:
Caused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL
Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.14.88
and:
Caused by: com.ibm.db2.jcc.am.SqlException: [jcc][t4][2041][11392] [4.14.88] Error executing XAResource.commit(). Server returned XAER_RMFAIL. ERRORCODE=-4203, SQLSTATE=null | - | true | [] |
DEV_Q164 | When should I use conversation sharing in DataPower MQ queue managers?
MQ version 7.0 introduced a new feature, conversation sharing. Are there any special values on DataPower when configuring conversation sharing? | The default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is
negotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server. | false | [
{
"filename": "swg21647231.txt",
"text": "Title: IBM When to enable Conversation Sharing in DataPower MQ Queue Manager (mq-qm) object - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When to enable Sharing Conversations in DataPower MQ Queue Manager (mq-qm) object along with SHARECNV attribute of the MQ SVRCONN channel? \n\nRESOLVING THE PROBLEM\nIBM WebSphere MQ server version 7.0 and later releases provide sharing conversations (SHARECNV) attribute on SVRCONN channel that specifies the maximum number of conversations that can share each TCP/IP channel instance. This feature can be configured in DataPower as it uses client connection with queue manager SVRCONN channel. \nThe default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is \nnegotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server.\n\nThere are three use cases to configure Sharing Conversations in DataPower mq-qm object: \n\nCase #1 : The negotiated sharing conversations value is 0 - The channel runs in a mode similar to WebSphere MQ V6 and does not uses features such as\n\n· Administrator stop-quiesce\n· Heartbeating \n· Read ahead \n· Client asynchronous consume\n\nSet a value of 0 or 1 on the Sharing Conversations attribute of the mq-qm object in DataPower to disable sharing conversations regardless of the IBM WebSphere MQ SVRCONN setting.\n\nCase #2: The negotiated sharing conversations value is 1 - The channel supports IBM WebSphere MQ V7 and later release features as outlined in case #1, but each TCP/IP channel instance has a single conversation.\n\nSet a value of 1 on the Sharing Conversations attribute and select \"on\" in Share Single Conversation attribute of the mq-qm object in DataPower as shown in the following picture and a value of 1 on IBM WebSphere MQ SVRCONN setting.\n\nThe Share Single Conversation attribute is only visible when \"Sharing Conversations\" is configured with value of \"1\" and then <RETURN> key is entered. For values greater than 1, the \"Share Single Conversation\" attribute is hidden in the mq-qm object.\n[/support/docview.wss?uid=swg21647231&aid=1] [/support/docview.wss?uid=swg21647231&aid=1] \n\nCase #3: The negotiated sharing conversations value is 2 or more - The channel supports IBM WebSphere MQ 7 and later release features and each TCP/IP channel instance supports 2 or more conversations.\n\nSet a value of 2 or more on the Sharing Conversations attribute of the mq-qm object in DataPower and on the MQ SVRCONN channel.\n\nOn average, processing of messages from client applications is 15 percent slower when using SHARECNV(10) as compared to SHARECNV(0). Please refer to Performance Implications of Sharing [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.csqzaf.doc/mi12240_.htm]\nConversations on Client-connection Channels. [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.0.1/com.ibm.mq.csqzaf.doc/mi12240_.htm].\n\nSince DataPower uses a connection pool in processing MQ messages, there are no additional benefits of using sharing conversations with the mq-qm object. However, in situations when mixed message sizes are used by the same mq-qm object, using case #2 will benefit mq-qm object as it will use new buffer management feature of IBM WebSphere MQ Version 7 when making MQGET API call.\n\nWhen using a negotiated shared conversations value of 0 as in case #1, mq-qm object uses maximum message size as the buffer pool for the MQGET API call. However, when mixed message sizes are processed by the same MQ Front Side Handler (FSH), it requests buffer pool based on maximum message size configured in the mq-qm object. The use of fixed buffer pool for small and large messages can deplete MQ server's allocated buffer and contribute to unexpected termination of MQ SVRCONN channel instance and may terminate the queue manager. In such a situation, using a negotiated sharing conversations value of 1 as in case #2 will benefit DataPower mq-qm object as it will use IBM WebSphere MQ Version 7 Read Ahead feature and the new buffer management feature for MQGET API call. IBM WebSphere MQ V8 release provides enhanced performance for case #2, when the negotiated sharing conversations value is 1.\n\nFor DataPower firmware releases 7.0.0.x, 7.1.0.x, 7.2.0.x and earlier, one should follow case #1 and use a negotiated sharing conversations value of 0. If you configure these firmware versions with case #2 or case #3, DataPower device may reload or hang due to connection instability and generate many MQ errors with Reason Code - 2009 and 2059. \n\nCases #2 and #3 can be used in firmware releases 7.5.0.x, 7.5.1.x and later. We suggest to use a value of 10 or less in Sharing Conversations attribute of the mq-qm object and verify the configuration empirically to make sure that IBM WebSphere MQ server can sustain load from DataPower with the negotiated Sharing Conversations of 10.\n\nNote: In order to use sharing conversations, make sure you have applied APAR IV24821 [http://www.ibm.com/support/docview.wss?uid=swg1IV24821] (\"Client C application process hangs after cancelling thread\") to the IBM WebSphere MQ server. IV24821 is included in IBM WebSphere MQ V7.0.1.10 and later, IBM WebSphere MQ V7.1.0.3 and later, IBM WebSphere MQ V7.5.0.1 and later, and IBM WebSphere MQ V8.\n\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the distributed platform.\n\nrunmqsc <qmgr>\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n1 : display chs(CHANNEL3) maxshcnv curshcnv\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.x1.x2.x3) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(1) MAXSHCNV(1) <---- Negotiated Sharing Conversations value of 1\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.y1.y2.y31) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(0) MAXSHCNV(0) <---- Negotiated Sharing Conversations value of 0\n\nend\n--------------------------------------------------------------------------------------------------------------------------------------------\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the z/OS System.\n\n\n\nconnect to <qmgr>\nOn z/OS system, options for issuing the commands are described at http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q085120_.htm [http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q085120_.htm]. \n/+RTP8 DIS CHSTATUS(channel_name) MAXSHCNV CURSHCNV\nwhere \"+RTP8\" is the command prefix."
}
] |
DEV_Q165 | DSNT408I SQLCODE -401 creating stored procedure CIUSNTSR after upgrading to DB2 11
Why would CIUSNTSR stored procedure creation fail with message DSNT408I and SQLCODE=-401? I am running CICS Interdependency Analyzer for z/OS (CICS IA) CIUDBCQ JCL when the failure occurs. This happened after I upgraded z/OS DB2 to V11.
Here are the messages I receive:
DSNT408I SQLCODE = -401, ERROR: THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE
NOT COMPARABLE
DSNT418I SQLSTATE = 42818 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXOBFC SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 930 0 1 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'000003A2' X'00000000' X'00000001' X'FFFFFFFF' X'00000000' X'00000000'
SQL DIAGNOSTIC INFORMATION | - | true | [] |
DEV_Q166 | Which version of the WebSphere MQ Resource Adapter is shipped with WebSphere Application Server?
Which version of WebSphere MQ JCA resource adapter is shipped with WebSphere Application Server ? | - | true | [] |
DEV_Q167 | How do I recreate all the Oracle Text indexes for the Atlas database
How do I recreate all the Oracle Text indexes for the Atlas database ? | Shutdown the application server running the Atlas applications.
2. Locate the script drop_ctxsys_indexes.sql to drop the Oracle Text indexes from the following folder in the Atlas release:
Atlas\Schema\Deploy\smf\db\etc\oracle
3. Open up a command window to that directory and execute the script using SQL Plus:
sqlplus <user>/<password>@<database> @drop_ctxsys_indexes.sql
4. Locate the scripts, setup_ctxsys_objects.sql and create_ctxsys_indexes.sql, used to create the Oracle Text preferences and indexes from the following folder in the Atlas release. The <version> folder will differ depending on which version you are currently running.
Atlas\Schema\Deploy\smf\db\release\<version>\oracle\create\schema
5. Open up a command window to that directory and execute the scripts using SQL Plus.
sqlplus <user>/<password>@<database> @setup_ctxsys_objects.sql
sqlplus <user>/<password>@<database> @create_ctxsys_indexes.sql
6. Start the application server running the Atlas applications. | false | [
{
"filename": "swg21580830.txt",
"text": "Title: IBM Recreate all the Oracle Text indexes - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I recreate all the Oracle Text indexes for the Atlas database \n\nANSWER\nThere are situations where the Oracle Text indexes used by the application may need to be recreated. For example, after importing data from a production database to a test database, the Oracle Text indexes will not be transferred. This will require you to recreate them in order for certain functions in Atlas to work properly. \n\nIf you have access to the Atlas release files from the version you are currently using you can follow these instructions. You will need the ability to access the Atlas database using the Oracle SQL Plus tool. \n\n \n\n 1. Shutdown the application server running the Atlas applications. \n 2. Locate the script drop_ctxsys_indexes.sql to drop the Oracle Text indexes from the following folder in the Atlas release:\n Atlas\\Schema\\Deploy\\smf\\db\\etc\\oracle \n 3. Open up a command window to that directory and execute the script using SQL Plus:\n sqlplus <user>/<password>@<database> @drop_ctxsys_indexes.sql \n 4. Locate the scripts, setup_ctxsys_objects.sql and create_ctxsys_indexes.sql, used to create the Oracle Text preferences and indexes from the following folder in the Atlas release. The <version> folder will differ depending on which version you are currently running.\n Atlas\\Schema\\Deploy\\smf\\db\\release\\<version>\\oracle\\create\\schema \n 5. Open up a command window to that directory and execute the scripts using SQL Plus.\n sqlplus <user>/<password>@<database> @setup_ctxsys_objects.sql\n sqlplus <user>/<password>@<database> @create_ctxsys_indexes.sql \n 6. Start the application server running the Atlas applications.\n\n[attachment \"recreate_oracle_text_3.0.2.x.zip\" deleted by Nicholas Tsang/San Jose/IBM] [attachment \"recreate_oracle_text_3.1.x.zip\" deleted by Nicholas Tsang/San Jose/IBM] [attachment \"recreate_oracle_text_4.x.zip\" deleted by Nicholas Tsang/San Jose/IBM] [attachment \"recreate_oracle_text_5.x.zip\" deleted by Nicholas Tsang/San Jose/IBM] \n\nHISTORICAL NUMBER\n 1075"
}
] |
DEV_Q168 | IBM Integration Designer could not connect to the DataPower appliance.
I am using WDP XI52 with Firmware 7.0.0.7 and IID 7.5.1. When I try to connect WDP from [DataPower Appliances] View in IID, I got a error message as follows : "SSL handshake on the connection to the DataPower appliance "x.x.x.x" was not successful. Contact the DataPower administrator." This situations occurred since WDP Firmware had upgraded from 7.0.0.2 to 7.0.0.5. (Now it was upgraded to 7.0.0.7)
Could you please let me know what I should check to solve this problem? Please note that this WDP works normally and a network is normal. Also, I can connect it by using WebGUI and SSH terminal. And I've checked that IP , XML Management Interface Port, Web Management Service Port and account/password are correct. | - | true | [] |
DEV_Q169 | Migrating to JRules v7.1
How do I migrate to WebSphere ILOG JRules v7.1? | - | true | [] |
DEV_Q170 | ODR OOM issue
I got ODR OOM after upgrading the WAS to v8553. No configuration or traffic load changing. Is there any known issue? | - | true | [] |
DEV_Q171 | Error: "MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION" occurs at portal startup
We are using Portal Server 8.5 and when starting the Portal server we see following error:
0000005e MBeanStarter E com.ibm.wps.scripting.server.MBeanStarter loadExtensions failed to load extension: key: ServerExt.applications / value: com.ibm.wps.scripting.server.ApplicationServerExtensions
How can we resolve this error? | A code fix for this issue is integrated into the WebSphere
Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal
8.5.0.0 available from Fix Central: | false | [
{
"filename": "swg1PI34677.txt",
"text": "Title: IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States\n\nText:\n A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\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 * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications / value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions\n \n \n \n \n \n\nLOCAL FIX\n * 1) open the WAS admin console\n 2) navigate to Resources > Resource environment providers > WP\n ScriptingService > Custom properties\n 3) you should see an entry with the name\n \"ServerExt.applications\" and value\n \"com.ibm.wps.scripting.server.ApplicationServerExtensions\"\n 4) delete this entry, save and restart the server.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal\n 8.5.0.0 available from Fix Central:\n \n http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent\n =ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al]\n l&platform=All&function=aparId&apars=PI31198\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Added a task to remove the outdate resource environment\n provider entry.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI34677\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 850\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 2015-02-10\n \n \n * CLOSED DATE\n 2015-03-10\n \n \n * LAST MODIFIED DATE\n 2015-03-10\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 WEBSPHERE PORTA\n \n \n * FIXED COMPONENT ID\n 5724E7600\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"
}
] |
DEV_Q172 | What's the procedure to drop an user in Cognos Disclosure Management?
O.S AIX 7.1
Cognos Disclosure Management 10.2.4 What's the procedure to drop an user in Cognos Disclosure Management | - | true | [] |
DEV_Q173 | ORA-01795 Error accessing Decision Center Business Console 8.7
I am working with ODM 8.7.0.0 when accessing the Business Console I am getting the below error message :
ORA-01795: maximum number of expressions in a list is 1000
The diagnostics do not contain any warning nor error.
The logs contain below exception :
java.lang.RuntimeException: java.sql.SQLException: ORA-01795: maximum number of expressions in a list is 1000
...
Caused by: java.sql.SQLException: ORA-01795: maximum number of expressions in a list is 1000 | - | true | [] |
DEV_Q174 | Datacap on Citrix
Hi All,
Can we operate Datacap thin clients on citrix?
| Remote users that access Datacap over a WAN can use Taskmaster Web-based "thin clients", or FastDoc Capture operating in offline mode. | false | [
{
"filename": "swg21658019.txt",
"text": "Title: IBM Deploying IBM Datacap Taskmaster Capture on a WAN - United States\n\nText:\nWAN LAN architecture deployment TECHNOTE (FAQ)\n\nQUESTION\n What are the best practices for deploying Datacap servers and clients on a wide area network (WAN)? \n\nANSWER\nRemote users that access Datacap over a WAN can use Taskmaster Web-based \"thin clients\", or FastDoc Capture operating in offline mode. Datacap thick clients (DotScan, DotEdit) and utilities (NENU, Fingerprint Maintenance Tool) require LAN communication speeds and low latency for responsive performance. \n\nConnect all Datacap Taskmaster Servers, Rulerunner Servers, Web Servers, file servers and databases to a single high performance LAN for best results. Network delays between Taskmaster Server, shared files and databases causes degraded performance of Job Monitor and data intensive operations. \n\nSome customers successfully operate Datacap thick clients in remote sites using Citrix or other remote access technology. IBM has not tested or sought certification with Citrix, and does not provide support for Citrix. If you deploy Datacap clients on Citrix and encounter issues, IBM may require you to reproduce the issues outside of Citrix as part of the investigation. \n\nConsult the IBM Redbooks titled \"Implementing Imaging Solutions with IBM Production Imaging Edition and IBM Datacap Capture\", section 2.5, for deployment recommendations and diagrams.\n\nRELATED INFORMATION\n IBM Redbooks Production Imaging Edition [http://www.redbooks.ibm.com/abstracts/sg247969.html?Open]"
}
] |
DEV_Q175 | Would like to know if WebSphere Extreme Scale is leap year and leap second compliant. Is there any documentation that talks about this?
Would like to know if WebSphere Extreme Scale is leap year compliant. Is there any documentation that talks about this? | WebSphere Application Server and the SDK are leap year compliant. | false | [
{
"filename": "swg21578744.txt",
"text": "Title: IBM WebSphere Application Server Is Leap Year Compliant - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We have had questions from clients planning for leap year years (containing February 29th) asking if WebSphere Application Server Leap Year Compliant, and if any problems are expected stemming from WebSphere Application Server or associated IBM products due to Leap Year. \n\nThere are no known or expected problems.\n(Details below) \n\nRESOLVING THE PROBLEM\nWebSphere Application Server and the SDK are leap year compliant. IBM Java (SDK / JDK) has been doing leap year testing/verification since 1996, including the non-leap year 2000 without a problem. Basically leap years in Java are explicitly supported by the GregorianCalendar class - that is it's function - and this class is tested with every release of Java as it is part of Java's core functionality. So any Java code which uses the GregorianCalendar class will behave correctly. \n\nWebSphere Application Server performs no specific leap year testing since it runs on top of the SDK which is compliant, and uses function from it. We are not aware of any issues in the past with WebSphere Application Server associated with leap year. \n\nFrom a JDK perspective, Java applications which use the GregorianCalendar class will be leap-year compliant - see the spec at: \n\n(Same info in the links for the various JDK's) \n\nhttp://docs.oracle.com/javase/6/docs/api/java/util/GregorianCalendar.html [http://docs.oracle.com/javase/6/docs/api/java/util/GregorianCalendar.html] \n\nhttp://docs.oracle.com/javase/7/docs/api/java/util/GregorianCalendar.html [http://docs.oracle.com/javase/7/docs/api/java/util/GregorianCalendar.html]\n\nhttp://docs.oracle.com/javase/8/docs/api/java/util/GregorianCalendar.html [http://docs.oracle.com/javase/8/docs/api/java/util/GregorianCalendar.html] \n\n\nSpecifically: \n\n\"The only difference between the Gregorian and the Julian calendar is the leap year rule. The Julian calendar specifies leap years every four years, whereas the Gregorian calendar omits century years which are not divisible by 400.\" In other words the Gregorian Calendar follows modern leap years. The correct operation of the class is tested by the Java Compliance Kit (JCK) which is run against every release of the JVM. So Java applications would need to assert that they are using GregorianCalendars to claim leap-year compliance."
}
] |
DEV_Q176 | Would like to know if WebSphere Extreme Scale is leap year and leap second compliant. Is there any documentation that talks about this?
Would like to know if WebSphere Extreme Scale is leap second compliant. Is there any documentation that talks about this? | WebSphere Application Server and the SDK are leap year compliant. | false | [
{
"filename": "swg21578744.txt",
"text": "Title: IBM WebSphere Application Server Is Leap Year Compliant - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We have had questions from clients planning for leap year years (containing February 29th) asking if WebSphere Application Server Leap Year Compliant, and if any problems are expected stemming from WebSphere Application Server or associated IBM products due to Leap Year. \n\nThere are no known or expected problems.\n(Details below) \n\nRESOLVING THE PROBLEM\nWebSphere Application Server and the SDK are leap year compliant. IBM Java (SDK / JDK) has been doing leap year testing/verification since 1996, including the non-leap year 2000 without a problem. Basically leap years in Java are explicitly supported by the GregorianCalendar class - that is it's function - and this class is tested with every release of Java as it is part of Java's core functionality. So any Java code which uses the GregorianCalendar class will behave correctly. \n\nWebSphere Application Server performs no specific leap year testing since it runs on top of the SDK which is compliant, and uses function from it. We are not aware of any issues in the past with WebSphere Application Server associated with leap year. \n\nFrom a JDK perspective, Java applications which use the GregorianCalendar class will be leap-year compliant - see the spec at: \n\n(Same info in the links for the various JDK's) \n\nhttp://docs.oracle.com/javase/6/docs/api/java/util/GregorianCalendar.html [http://docs.oracle.com/javase/6/docs/api/java/util/GregorianCalendar.html] \n\nhttp://docs.oracle.com/javase/7/docs/api/java/util/GregorianCalendar.html [http://docs.oracle.com/javase/7/docs/api/java/util/GregorianCalendar.html]\n\nhttp://docs.oracle.com/javase/8/docs/api/java/util/GregorianCalendar.html [http://docs.oracle.com/javase/8/docs/api/java/util/GregorianCalendar.html] \n\n\nSpecifically: \n\n\"The only difference between the Gregorian and the Julian calendar is the leap year rule. The Julian calendar specifies leap years every four years, whereas the Gregorian calendar omits century years which are not divisible by 400.\" In other words the Gregorian Calendar follows modern leap years. The correct operation of the class is tested by the Java Compliance Kit (JCK) which is run against every release of the JVM. So Java applications would need to assert that they are using GregorianCalendars to claim leap-year compliance."
}
] |
DEV_Q177 | After AIX TL/SP/FP update my TSAMP cluster no longer functions.
After applying update to AIX to bring it up to 7100-05-01-1731 which includes RSCT 3.2.3.0 I noticed that neither IBM.GblResRM nor IBM.RecoveryRM would stay operative in "lssrc -g rsct_rm" output. | - | true | [] |
DEV_Q178 | Need support info for ITCAM and WAS 8.5.5.x monitoring
What ITCAM for AD/WAS versions and maintenance levels support monitoring of WAS 8.5.5.x?
| - | true | [] |
DEV_Q179 | Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735)
I need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735). Where can I find this information? | CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]
DESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) | false | [
{
"filename": "swg22014367.txt",
"text": "Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nAll versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server\n\nREMEDIATION/FIXES\nFor MQ 5.3 \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\n * \n\nFor MQ 8 \n * \n\n * \n * here\n * \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] \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\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."
}
] |
DEV_Q180 | Help with Security Bulletin: Security Vulnerability in IBM PureApplication System. (CVE-2015-1920)
I need to understand details regarding "Security Bulletin: Security Vulnerability in IBM PureApplication System (CVE-2015-1920)". Where can I find this information? | CVEID: CVE-2015-1920
DESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.
CVSS Base Score: 9.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102404 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:C/I:C/A:C) | false | [
{
"filename": "swg21964873.txt",
"text": "Title: IBM Security Bulletin: Security Vulnerability in IBM PureApplication System. (CVE-2015-1920) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM PureApplication System contains IBM WebSphere Application Server, which has a security vulnerability that could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-1920 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/102404 [https://exchange.xforce.ibmcloud.com/vulnerabilities/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:C/I:C/A:C) \n\nPlease consult the security bulletin: Security Vulnerability in IBM WebSphere Application Server [http://www-01.ibm.com/support/docview.wss?uid=swg21883573]for additional vulnerability details and information\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM PureApplication Server bundles WebSphere Application Server in its Web Application Pattern.\n\nIBM PureApplication System V2.1\nIBM PureApplication System V2.0\nIBM PureApplication System V1.1 \n\nREMEDIATION/FIXES\nThe solution is to apply an update to the Web Application pattern type included in IBM PureApplication System:\n\nIBM PureApplication System V2.1\n· Web Application Pattern Type V2.0.4.2\nhttp://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc]\n\n· Web Application Pattern Type V1.0.4.2\nhttp://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f]\n\nIBM PureApplication System V2.0 \nThe solution is to upgrade to IBM PureApplication System V2.0.0.1 Interim Fix 5\n\nIBM PureApplication System V1.1 and earlier:\nContact IBM customer support for upgrade options.\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 19 August 2015: Original Version Published\n11 September 2015 Updated for IBM PureApplication System v2.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."
}
] |
DEV_Q181 | Get all data that\'s registred today
Version:
MxLoader 4.7.4
Problem:
Is it possible to do something like this:
reportdate >= TODAY()?
I cant get it to work but i would like to get all the data that has been registred today today.
| The getdate() MSSQL function can be replaced by value from DB2 CURRENT DATE special register. On Oracle, sysdate is used to retrieve the current date.
EXAMPLE : MSSQL and transdate <= ( getdate() - 35)
DB2 and transdate <= ( CURRENT DATE - 35 DAYS)
Oracle and transdate <= ( sysdate - 35) | false | [
{
"filename": "swg21569933.txt",
"text": "Title: IBM Current Date function for DB2, SQL Server and Oracle - United States\n\nText:\nTPAEMSSQL; TPAEDB2; getdate; TPAEDATABASE; TPAEORACLE TECHNOTE (FAQ)\n\nQUESTION\n What would be the equivalent of MSSQL getdate() function for Maximo running on DB2 or Oracle? \n\nANSWER\nThe getdate() MSSQL function can be replaced by value from DB2 CURRENT DATE special register. On Oracle, sysdate is used to retrieve the current date. \n\nEXAMPLE : MSSQL and transdate <= ( getdate() - 35) \n\n DB2 and transdate <= ( CURRENT DATE - 35 DAYS) \n\n Oracle and transdate <= ( sysdate - 35) \n\n \n\nRELATED INFORMATION\n URL [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp]"
}
] |
DEV_Q182 | Help with Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IIB and WMB
I need to understand details regarding "Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker" This is related to
CVE-2017-10115
CVE-2017-10116
CVE-2017-10109
CVE-2017-10108
Where can I find this information? | CVEID:CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]
DESCRIPTION: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.
CVSS Base Score: 7.5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) | false | [
{
"filename": "swg22010090.txt",
"text": "Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker - United States\n\nText:\nIIB; WMB SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition, Version 7.1.4.10 and IBM® Runtime Environment Java™ Versions 7.0.10.10 and 7.1.4.10 used by IBM Integration Bus and WebSphere Message Broker. These issues were disclosed as part of the IBM Java SDK updates in Jul 2017. \n\nVULNERABILITY DETAILS\n\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for “IBM Java SDK Security Bulletin\" located in the “References” section for more information.\n\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: Seehttps://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: Seehttps://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\nCVEID:CVE-2017-10108 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10108]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Serialization 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\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128869 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128869]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\nCVEID:CVE-2017-10109 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10109]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Serialization 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\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128870 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128870]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\nIBM Integration Bus V9.0.0.0 - V9.0.0.8 and V10.0.0.0 - V10.0.0.9 \n\nWebSphere Message Broker V8.0.0.0 - V8.0.0.9\nWebSphere Message Broker V7.0.0.0 - V7.0.0.8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation / Fix IBM Integration Bus V10.0.0.0 - V10.0.0.9 IT21764 The APAR is available in fix pack 10.0.0.10 [http://www-01.ibm.com/support/docview.wss?uid=swg24043943]\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 - V9.0.0.8 IT21764 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] WebSphere Message Broker V8.0.0.0 - V8.0.0.9 IT21764 Contact IBM support to request a fix for APAR IT21764 WebSphere Message Broker V7.0.0.0 - V7.0.0.8 IT21764 Contact IBM support to request a fix for APAR IT21764 \n\nWebsphere Message Broker V7 and V8 are no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nIf you are a customer with extended support and require a fix, contact IBM support. \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\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 v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \nIBM Java SDK Security Bulletin [http://www.ibm.com/support/docview.wss?uid=swg22006695] \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 15th November 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. \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# \n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 7.0, 8.0 \nPRODUCT ALIAS/SYNONYM\n IIB\nWMB"
}
] |
DEV_Q183 | Is there a support's guide to the MTTrapd probe ?
Where do you download the Support's guide to the MTTrapd [SNMP] probe ? | The attached Support's guide to the SNMP probe provides details on how best to configure the probe, troubleshoot issues and how to use third party products to test the probes behaviour. | false | [
{
"filename": "swg21607690.txt",
"text": "Title: IBM Support's Guide to the SNMP [MTTrapd] probe - United States\n\nText:\nnco_p_mttrapd; snmp; rules file; probe; snmpsend; snmptrap; test; testing; snmpv3 TECHNOTE (FAQ)\n\nQUESTION\n MTTrapd probe : How can you troubleshoot configuration issues? \n\nANSWER\nThe MTTrapd (SNMP) probe is a Generic probe used to process SNMP traps.\nIt is a multi-threaded probe and supports both UDP and TCP traps/informs.\n\nThe attached Support's guide to the SNMP probe provides details on how best to configure the probe, troubleshoot issues and how to use third party products to test the probes behaviour.\n\nThe latest probe version is:\nRelease ID: 20.0.2\nOr higher.\n\nRELATED INFORMATION\n Where to locate the latest MTTrapd probe release 20.0.2 [https://developer.ibm.com/answers/questions/414820/where-do-you-download-the-mttrapd-probe-release-20/]\n\n\nSNMP_MTTRAPDProbe_SupportsGuide_22.pdf [/support/docview.wss?uid=swg21607690&aid=2]SNMP_MTTRAPDProbe_SupportsGuide_22.pdf [/support/docview.wss?uid=swg21607690&aid=1]"
}
] |
DEV_Q184 | Why am I seeing "CWSXM0100E: Multiple replies have been produced for a single request flow in module" ?
We are building a simple mediation module, consisting only of the request flow. The mediation module has one service invoke calling an external service through web service binding. Upon testing the process, we observe see that the service invoke is being called twice. There is no Fan-in or fan -out in the request flow. Below is the error: "Caused by: com.ibm.wsspi.sibx.mediation.flow.MediationRuntimeException: CWSXM1023E: Exception when calling flow action: CWSXM0100E: Multiple replies have been produced for a single request flow in module" | This error occurs when a mediation primitive is wired more than once to the next mediation primitive. It might seem to be a single wire. However, upon closer inspection, more than one wire exists.
By mistake, primitives might be wired more than once when there is only one wire. See the following screen shot:
[/support/docview.wss?uid=swg21584783&aid=1]
If you move the primitives in question, however, you notice that there are more wires underneath: | false | [
{
"filename": "swg21584783.txt",
"text": "Title: IBM A CWSXM0100E error is received for WebSphere Enterprise Service Bus (WESB), WebSphere Process Server (WPS), or IBM Business Process Manager (BPM) Advanced - United States\n\nText:\nCWSXM0100E; multiple; replies; single; request TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When a single request is sent to a Mediation Flow Component in WebSphere Enterprise Service Bus, WebSphere Process Server, or Business Process Manager Advanced, services can be invoked more than once. \n\nSYMPTOM\nThe following error message can be observed in the SystemOut.log file:\n\nCWSXM0100E: Multiple replies have been produced for a single request flow in module <module_name> \n\nMore than one invocation can occur from a single request.\n\nCAUSE\nThis error occurs when a mediation primitive is wired more than once to the next mediation primitive. It might seem to be a single wire. However, upon closer inspection, more than one wire exists. \n\n\nBy mistake, primitives might be wired more than once when there is only one wire. See the following screen shot:\n[/support/docview.wss?uid=swg21584783&aid=1]\n\nIf you move the primitives in question, however, you notice that there are more wires underneath:\n\n[/support/docview.wss?uid=swg21584783&aid=2]\n\n\n\nRESOLVING THE PROBLEM\nTo solve this problem, complete the following steps: \n\n 1. Delete any redundant wires. \n \n \n 2. Save the project.\n \n \n 3. Redeploy the application to the server.\n\nRELATED INFORMATION\n#IC67220: OUTSTANDING PROCESSING OCCURS IN AN AGGREGATIO [http://www.ibm.com/support/docview.wss?uid=swg1IC67220]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Mediation AIX, Linux, Solaris, Windows, z/OS 8.0, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Process Server Mediation AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0, 6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2"
}
] |
DEV_Q185 | What can I do when I receive CWZIP9602E, CWZIP9604W and CWZIP4514E with Call Home?
I received the following critical events after enabling CallHome on my PureApplication System v.2.0.0.1:
CWZIP4514E: Configuration Settings for Call Home are not configured properly.
CWZIP9602E: Service53 is failed offline at node and cannot be restarted.
CWZIP9604W: Service53 failed. The high availability component will attempt to recover the service.
What can I do? | - | true | [] |
DEV_Q186 | Silent uninstall of ITCAM for MQ agent fails
Running silent uninstall of the ITCAM for MQ agent with this command: start /wait setup /z"/sfMQ_Silent_Uninstall.txt" /s /f2"C:\temp\silent_setup.log" fails with this message in the Abort_*.trc file: SEVERE: You must agree to the License Agreement.
The MQ_Silent_Uninstall.txt does contain this line: License Agreement=I agree to use the software only in accordance with the installed license. | Specify the complete path to the silent response file while launching the silent install. | false | [
{
"filename": "swg21608744.txt",
"text": "Title: IBM Silent Install - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Silent install of any of the Tivoli Monitoring components fails. \n\nCAUSE\nWhen the complete path to the silent response file is not specified as part of the command invoking the silent install, it fails with the following error message in the log file: \n\n------------------------------------------------------------\n08-16-2012 09:52:31: Silent install configuration file: silent_response.txt\n08-16-2012 09:52:31: \n08-16-2012 09:52:31: AgentDeployRunning=FALSE.\n08-16-2012 09:52:31: \n08-16-2012 09:52:31: SEVERE: You must agree to the License Agreement.\n08-16-2012 09:52:31: SEVERE: Silent install config error.\n08-16-2012 09:52:31: Silent install config error.\n------------------------------------------------------------\n\n\n\nRESOLVING THE PROBLEM\nSpecify the complete path to the silent response file while launching the silent install. \n\ne.g.\nsetup /z\"/sfE:\\TEMP\\silent_response.txt\" /s /f2\"C:\\temp\\itm6_agent_setup.log\""
}
] |
DEV_Q187 | Help with Security Bulletin: Multiple Vulnerabilities identified in IBM Java SDK affect WSRR
I need to understand details regarding Security Bulletin: Multiple Vulnerabilities identified in IBM® Java SDK affect WebSphere Service Registry and Repository, in particular CVE-2017-10115. Where can I find this information? | CVEID:CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]
DESCRIPTION:An unspecified vulnerability 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.
CVSS Base Score: 7.5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/128876 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128876]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) | false | [
{
"filename": "swg22007002.txt",
"text": "Title: IBM Security Bulletin: Multiple Vulnerabilities in IBM® Java SDK affects WebSphere Application Server July 2017 CPU - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabiltities in the IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server. These issues were disclosed as part of the IBM Java SDK updates in July 2017. These may affect some configurations of IBM WebSphere Application Server Traditional, IBM WebSphere Application Server Liberty and IBM WebSphere Application Server Hypervisor Edition. \n\nVULNERABILITY DETAILS\nFor information on the IBM Java SDK that is now bundled with WebSphere Application Server Version 8.5.5 refer to the Knowledge Center link in the References section. \n\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for “IBM Java SDK Security Bulletin\" located in the References section for more information.\nHP fixes are on a delayed schedule. \n\nCVEID: CVE-2017-10102 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10102]\nDESCRIPTION: An unspecified vulnerability related to the Java SE RMI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/128863 [https://exchange.xforce.ibmcloud.com/vulnerabilities/128863] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) \n\n\nCVEID:CVE-2017-10116 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION:An unspecified vulnerability 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: Seehttps://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\nCVEID:CVE-2017-10115 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability 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: Seehttps://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\nAFFECTED PRODUCTS AND VERSIONS\nIBM SDK, Java Technology Editions shipped with WebSphere Application Server Liberty up to 17.0.0.2. IBM SDK, Java Technology Editions shipped with IBM WebSphere Application Server Traditional Version 9.0.0.0 through 9.0.0.4, 8.5.0.0 through 8.5.5.12, Version 8.0.0.0 through 8.0.0.13, Version 7.0.0.0 through 7.0.0.43. \n\n * This does not occur on IBM SDK, Java Technology Editions that are shipped with WebSphere Application Servers Fix Packs 17.0.0.3, 9.0.0.5 8.5.5.13, 8.0.0.14, and 7.0.0.45 or later. \n\nREMEDIATION/FIXES\nDownload and apply the interim fix APARs below, for your appropriate release \n\nFor the IBM Java SDK updates: \n\nFor WebSphere Application Server Liberty: \nFor the IBM SDK, Java Technology Version that you use, upgrade to WebSphere Application Server Liberty Fix Packs as noted below or later fix pack level and apply one of the interim fixes below: \n\nUpgrade to WebSphere Application Server Liberty Fix Pack 8.5.5.1 or later then apply Interim Fix PI84267 [http://www-01.ibm.com/support/docview.wss?uid=swg24043903] [http://www-01.ibm.com/support/docview.wss?uid=swg24043639]: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 50 Upgrade to WebSphere Application Server Liberty Fix Pack 8.5.5.1 or later then apply Interim Fix PI84265 [http://www-01.ibm.com/support/docview.wss?uid=swg24043898] [http://www-01.ibm.com/support/docview.wss?uid=swg24043628] [http://www-01.ibm.com/support/docview.wss?uid=swg24043320]: [http://www-01.ibm.com/support/docview.wss?uid=swg24041667] [http://www-01.ibm.com/support/docview.wss?uid=swg24041197] [http://www-01.ibm.com/support/docview.wss?uid=swg24040406] [http://www-01.ibm.com/support/docview.wss?uid=swg24039958] [http://www-01.ibm.com/support/docview.wss?uid=swg24039665] [http://www-01.ibm.com/support/docview.wss?uid=swg24039312] [http://www-01.ibm.com/support/docview.wss?uid=swg24038810] [http://www-01.ibm.com/support/docview.wss?uid=swg24038089] [http://www-01.ibm.com/support/docview.wss?uid=swg24036966] [http://www.ibm.com/support/docview.wss?uid=swg24036508] [http://www-01.ibm.com/support/docview.wss?uid=swg24035400] [http://www.ibm.com/support/docview.wss?uid=swg24035008] [http://www.ibm.com/support/docview.wss?uid=swg24034806] [http://www-01.ibm.com/support/docview.wss?uid=swg24034592] [http://www-01.ibm.com/support/docview.wss?uid=swg24037534] [http://www-01.ibm.com/support/docview.wss?uid=swg24037709] [http://www-01.ibm.com/support/docview.wss?uid=swg24036966] [http://www.ibm.com/support/docview.wss?uid=swg24036508] [http://www-01.ibm.com/support/docview.wss?uid=swg24035400] [http://www.ibm.com/support/docview.wss?uid=swg24035008] [http://www.ibm.com/support/docview.wss?uid=swg24034806] [http://www-01.ibm.com/support/docview.wss?uid=swg24034592]Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 10 FP10 For IBM SDK, Java Technology Edition Version 7R1 and IBM SDK, Java Technology Edition Version 8, please refer to IBM Java SDKs for Liberty [http://www-01.ibm.com/support/docview.wss?uid=swg27049903] \n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Liberty (17.0.0.3) or later. \n \n \n\nFor Version 9 WebSphere Application Server Traditional: Update the IBM SDK, Java Technology Edition using the instructions in the IBM Knowledge Center Installing and updating IBM SDK, Java Technology Edition on distributed environments [http://www.ibm.com/support/knowledgecenter/en/SSEQTP_9.0.0/com.ibm.websphere.installation.base.doc/ae/tins_installation_jdk.html] then use the IBM Installation manager to access the online product repositories [http://www.ibm.com/support/knowledgecenter/en/SSEQTP_9.0.0/com.ibm.websphere.installation.base.doc/ae/cins_repositories.html]to install the SDK or use IBM Installation manager and access the packages from Fixcentral [http://www-01.ibm.com/support/docview.wss?uid=swg24042430]. \n\n\nFor V8.5.0.0 through 8.5.5.12 WebSphere Application Server Traditional and WebSphere Application Server Hypervisor Edition: \n\nFor information on the IBM Java SDK that is now bundled with WebSphere Application Server Version 8.5.5 refer to the Knowledge Center link in the References section. \n\nUpgrade to WebSphere Application Server Traditional Fix Packs as noted below or later fix pack level and then apply one or more of the interim fixes below: \n\n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.1 or later then apply Interim Fix PI84266 [http://www-01.ibm.com/support/docview.wss?uid=swg24043902] [http://www-01.ibm.com/support/docview.wss?uid=swg24043636] [http://www-01.ibm.com/support/docview.wss?uid=swg24043321]: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 50 \n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.1 or later then apply Interim Fix PI84265 [http://www-01.ibm.com/support/docview.wss?uid=swg24043898]: [http://www-01.ibm.com/support/docview.wss?uid=swg24043628] [http://www-01.ibm.com/support/docview.wss?uid=swg24042554] [http://www-01.ibm.com/support/docview.wss?uid=swg24042119] [http://www-01.ibm.com/support/docview.wss?uid=swg24039958] [http://www-01.ibm.com/support/docview.wss?uid=swg24039665] [http://www-01.ibm.com/support/docview.wss?uid=swg24039312] [http://www-01.ibm.com/support/docview.wss?uid=swg24038810] [http://www-01.ibm.com/support/docview.wss?uid=swg24038089] [http://www-01.ibm.com/support/docview.wss?uid=swg24036966] [http://www.ibm.com/support/docview.wss?uid=swg24036508] [http://www-01.ibm.com/support/docview.wss?uid=swg24035400] [http://www.ibm.com/support/docview.wss?uid=swg24035008] [http://www.ibm.com/support/docview.wss?uid=swg24034806] [http://www-01.ibm.com/support/docview.wss?uid=swg24034592] [http://www-01.ibm.com/support/docview.wss?uid=swg24037534] [http://www-01.ibm.com/support/docview.wss?uid=swg24037709] [http://www-01.ibm.com/support/docview.wss?uid=swg24036966] [http://www.ibm.com/support/docview.wss?uid=swg24036508] [http://www-01.ibm.com/support/docview.wss?uid=swg24035400] [http://www.ibm.com/support/docview.wss?uid=swg24035008] [http://www.ibm.com/support/docview.wss?uid=swg24034806] [http://www-01.ibm.com/support/docview.wss?uid=swg24034592]Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 10 FP10 \n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.2 or later then apply Interim Fix PI84264 [http://www-01.ibm.com/support/docview.wss?uid=swg24043899]: [http://www-01.ibm.com/support/docview.wss?uid=swg24043627] [http://www-01.ibm.com/support/docview.wss?uid=swg24041671] [http://www-01.ibm.com/support/docview.wss?uid=swg24041668] [http://www-01.ibm.com/support/docview.wss?uid=swg24041194] [http://www-01.ibm.com/support/docview.wss?uid=swg24040407] [http://www-01.ibm.com/support/docview.wss?uid=swg24040157] [http://www-01.ibm.com/support/docview.wss?uid=swg24039961] [http://www-01.ibm.com/support/docview.wss?uid=swg24039687] [http://www-01.ibm.com/support/docview.wss?uid=swg24039311] [http://www-01.ibm.com/support/docview.wss?uid=swg24038809] [http://www-01.ibm.com/support/docview.wss?uid=swg24038165] [http://www-01.ibm.com/support/docview.wss?uid=swg24036966] [http://www.ibm.com/support/docview.wss?uid=swg24036508] [http://www-01.ibm.com/support/docview.wss?uid=swg24035400] [http://www.ibm.com/support/docview.wss?uid=swg24035008] [http://www.ibm.com/support/docview.wss?uid=swg24034806] [http://www-01.ibm.com/support/docview.wss?uid=swg24034592]Will upgrade you to IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 4 FP10 \n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.9 or later then apply Interim Fix PI84261 [http://www-01.ibm.com/support/docview.wss?uid=swg24043900] [http://www-01.ibm.com/support/docview.wss?uid=swg24043624]: [http://www-01.ibm.com/support/docview.wss?uid=swg24042939] [http://www-01.ibm.com/support/docview.wss?uid=swg24042552] [http://www-01.ibm.com/support/docview.wss?uid=swg24042111] [http://www-01.ibm.com/support/docview.wss?uid=swg24040158] [http://www-01.ibm.com/support/docview.wss?uid=swg24039956] [http://www-01.ibm.com/support/docview.wss?uid=swg24039668] [http://www-01.ibm.com/support/docview.wss?uid=swg24039304] [http://www-01.ibm.com/support/docview.wss?uid=swg24038812] [http://www-01.ibm.com/support/docview.wss?uid=swg24038093] [http://www-01.ibm.com/support/docview.wss?uid=swg24037708] [http://www-01.ibm.com/support/docview.wss?uid=swg24036967] [http://www-01.ibm.com/support/docview.wss?uid=swg24036505] [http://www-01.ibm.com/support/docview.wss?uid=swg24035398] [http://www.ibm.com/support/docview.wss?uid=swg24034998] [http://www-01.ibm.com/support/docview.wss?uid=swg24034447]Will upgrade you to IBM SDK, Java Technology Edition, Version 8 Service Refresh 4 FP10 \n * For environnments that have been upgraded to use the new default IBM SDK Version 8 bundled with WebSphere Application Server Fix Pack 8.5.5.11 or later: Apply Interim Fix PI84263 [http://www-01.ibm.com/support/docview.wss?uid=swg24043901] [http://www-01.ibm.com/support/docview.wss?uid=swg24043625]: Will upgrade you to IBM SDK, Java Technology Edition, Version 8 Service Refresh 4 FP10 \n\n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 13 (8.5.5.13) or later. \n\n\n\nFor V8.0.0.0 through 8.0.0.13 WebSphere Application Server and WebSphere Application Server Hypervisor Edition: Upgrade to WebSphere Application Server Fix Pack 8.0.0.7 or later then apply the interim fix below: \n\n * Apply Interim Fix PI84268 [http://www-01.ibm.com/support/docview.wss?uid=swg24043904]: [http://www-01.ibm.com/support/docview.wss?uid=swg24043640] [http://www-01.ibm.com/support/docview.wss?uid=swg24036967] [http://www-01.ibm.com/support/docview.wss?uid=swg24036505] [http://www-01.ibm.com/support/docview.wss?uid=swg24035398] [http://www.ibm.com/support/docview.wss?uid=swg24034998] [http://www-01.ibm.com/support/docview.wss?uid=swg24034447]Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24033359]Fix Pack 50\n\n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 14 (8.0.0.14) or later.\n\n\nFor V7.0.0.0 through 7.0.0.43 WebSphere Application Server and WebSphere Application Server Hypervisor Edition: Upgrade to WebSphere Application Server Fix Pack 7.0.0.31 or later then apply the interim fix below: \n\n * Apply Interim Fix PI84269 [http://www-01.ibm.com/support/docview.wss?uid=swg24043905] [http://www-01.ibm.com/support/docview.wss?uid=swg24043641]: Will upgrade you to IBM SDK, Java Technology Edition, Version 6 Service Refresh 16 [http://www-01.ibm.com/support/docview.wss?uid=swg24033359] Fix Pack 50\n\n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 45 (7.0.0.45) or later.\n\n\nFor unsupported versions of the above products, IBM recommends upgrading to a fixed, supported version of the product. 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\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 v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \nIBM Java SDK Security Bulletin [http://www-01.ibm.com/support/docview.wss?uid=swg22006695] \nIBM Java SDK Version 8 bundled with WebSphere Application Server [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/covr_javase6_eos.html] \nIBM Java SDKs for WebSphere Liberty [http://www-01.ibm.com/support/docview.wss?uid=swg27049903] \nIBM SDK Java Technology Edition Version 8.0 for WebSphere Liberty using archives [http://www-01.ibm.com/support/docview.wss?uid=swg24043502] \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 August 2017: original document published\n06 September 2017: replaced CVE-2017-10107 with CVE-2017-10102 \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=swg22009279]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Hypervisor Edition"
}
] |
DEV_Q188 | Is there a support's guide to the CORBA Probes?
Where can I download the support's guide to the IBM CORBA probes? | GENERIC_CORBA_SupportsGuide_20.pdf | false | [
{
"filename": "swg21614208.txt",
"text": "Title: IBM Support's Guide to IBM CORBA probes - United States\n\nText:\ncorba; visibroker; ibm corba; orb; ior; ior file; nonnative; probes; probe; corba-framework; dumpns; CORBA TECHNOTE (FAQ)\n\nQUESTION\n IBM CORBA probe : What happened to the visibroker patches? \n\nCAUSE\nVisibroker was replaced by the IBM CORBA integration\n\nANSWER\n \n\nThe Visibroker software is a third party product, and was replaced in 2012 by the IBM CORBA software. \n\n \n\nPlease review Support's Guide to IBM CORBA probes [attached] to understand the integration, alongside the probe's specific documentation.\n\nGENERIC_CORBA_SupportsGuide_20.pdf [/support/docview.wss?uid=swg21614208&aid=2]GENERIC_CORBA_SupportsGuide_20.pdf [/support/docview.wss?uid=swg21614208&aid=1]"
}
] |
DEV_Q189 | How to wrap table column text in list tab for a specific table?
I would like to wrap the text of table column into new a line. | - | true | [] |
DEV_Q190 | Is it possible to use Java large pages (-Xlp) parm with ITCAM? Is this supported?
Is it possible to use Java large pages (-Xlp) parm with ITCAM? Is this a supported feature?
| - | true | [] |
DEV_Q191 | Why does my install of the latest Installation Manager on a Linux Ingram Server not function?
Why does my install of the latest Installation Manager on a Linux Ingram Server not function? | - | true | [] |
DEV_Q192 | Cannot open module in exclusive edit - (no such file or directory)
Hello.
I have a module, that I can open normally, but when I try to open it in Exclusive Edit it tells me that "no such file or directory"
Is this a known problem? | This issue has been identified as a product defect under APAR PM50525 | false | [
{
"filename": "swg21511831.txt",
"text": "Title: IBM DOORS module fails to open in exclusive edit mode results in error \"unable to open module ...no such file or directory\" - United States\n\nText:\nmissing 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. \n\nActual 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: \n\nthe 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.\n\nCreate 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."
}
] |
DEV_Q193 | Are there any probes that can connecto the Nokia NSP EPC v17.9 and Nokia NSP RAN v17.3 using JMS/HTTP?
The customer has asked if there are any probes that can connect to their Nokia servers, both of which use a HTTP/JMS interface:
Nokia NSP EPC v17.9
Nokia NSP RAN v17.3 | This probe is written to support Nokia Network Functions Manager for Packet release 17.3. | false | [
{
"filename": "swg22005197.txt",
"text": "Title: IBM Tivoli Netcool/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States\n\nText:\nrelease 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\n\nThe 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.\n\nPart 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]"
}
] |
DEV_Q194 | How to generate Javacores automatically in on hung threads reported in SystemOut.log for WebSphere Application Server?
Need Javacores to be generated on hung threads messages reported in SystemOut.log for WebSphere Applicaiton Server.Example:WSVR0605W: Thread has been active for and may be hung. There are in total in the server that may be hung. | - | true | [] |
DEV_Q195 | TLS protocol with ITCAM for Datapower
We have a DataPower appliance with TLS security protocol enabled. Can we configure ITCAM for DataPower appliance v7.1 to specifically use the TLS protocol v1.2 (not v1.0)?
| TLSv1.2 is supported by using the same fix. | false | [
{
"filename": "swg21959224.txt",
"text": "Title: IBM TLS support and DataPower appliance - United States\n\nText:\nCAMDPALL CAMDPSEC TLS 1.0 1.2 TECHNOTE (FAQ)\n\nQUESTION\n Is this HotFix for TLS 1.0 (http://www-01.ibm.com/support/docview.wss?uid=swg21694441 [http://www-01.ibm.com/support/docview.wss?uid=swg21694441]) able to support also TLS 1.2? \n\nANSWER\nYes, TLSv1.2 is supported by using the same fix.\nJust an additional NOTE: As the default version expected is TLSv1, if you have disabled TLSv1 in the DataPower appliance (use only TLSv1.2), then please make sure to manually modify the value of KBN_SOMA_PROTOCOL to TLSv1.2."
}
] |
DEV_Q196 | Error while installing SpSS modeler trial version
I have downloaded the SPSS modeller trial version (18.1) (64 bit) and trying to install the same. I get the following error 1152: Error extracting modelerClient64.msi to the temporary location
| When an IBM SPSS compressed image is launched, files compressed within it are extracted to the temporary location assigned to the signed in user i.e. /Documents and settings/... or /users.
The possibility of these files downloaded improperly exists. You can use a tool such
as MD5 to verify the file content or simply attempt downloading a second time and test.
Other possible causes of this error:
- Available space within the temporary location noted by the installer.
- Ability to write in the temporary location noted by the installer.
ANSWER
Transfer the files again, resolved the issue. | false | [
{
"filename": "swg21577970.txt",
"text": "Title: IBM Installing Modeler gives 1152: Error extracting <path to user temp storage> to the temporary location - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What causes an 1152 error during extraction of Modeler self extracting executable? \n\nCAUSE\nWhen an IBM SPSS compressed image is launched, files compressed within it are extracted to the temporary location assigned to the signed in user i.e. /Documents and settings/... or /users.\nThe possibility of these files downloaded improperly exists. You can use a tool such\nas MD5 to verify the file content or simply attempt downloading a second time and test.\n\nOther possible causes of this error:\n- Available space within the temporary location noted by the installer.\n- Ability to write in the temporary location noted by the installer.\n\n\nANSWER\nTransfer the files again, resolved the issue. \n\nRELATED INFORMATION\n Need more help? Our Modeler forum is Live! [https://developer.ibm.com/answers/topics/modeler/?smartspace=predictive-analytics]"
}
] |
DEV_Q197 | Help with Security Bulletin: WMB and IIB are affected by 'Information Disclosure' vulnerability
I need to understand details regarding Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by 'Information Disclosure' vulnerability. Where can I find this information? | - | true | [] |
DEV_Q198 | Why is CSV002I occurring for CSQADITB?
An application is getting repeated errors:
CSV002I REQUESTS FOR MODULE CSQADITB EXCEED MAXIMUM USE COUNT
Restarting the application clears the error messages for a while. Why is this occurring?
| - | true | [] |
DEV_Q199 | How do I resolve a WSVR0605W hung thread issue in the WebSphere MQ Resource Adapter?
The following WebSphere MQ Resource Adapter hung thread can prevent an application server from starting...
WSVR0605W: Thread "WMQJCAResourceAdapter : 6" (0000001b) has been active for 698530 milliseconds and may be hung. There is 1 thread(s) in total in the server that may be hung. at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:167) at com.ibm.ejs.container.MessageEndpointFactoryImpl.createEndpoint(MessageEndpointFactoryImpl.java:498) at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:149) | - | true | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.