This document provides an overview of IBM MQ's latest features including 64-bit buffer pools, 8-byte log RBAs, channel initiator statistics and accounting data, and the use of storage class memory (flash storage) with coupling facilities. The key points discussed are: - 64-bit buffer pools allow larger buffer pools above the 2GB bar with up to 999,999,999 buffers per pool for improved performance. - 8-byte log RBAs increase the log RBA range from 255TB to over 5000 years, avoiding disruptive queue manager restarts. - New SMF records provide visibility into channel initiator performance and accounting data for monitoring, capacity planning, and issue diagnosis. - Coupling

1. IBM MQ for z/OS:
Latest Features Deep Dive
Pete Siddall
pete_siddall@uk.ibm.com

2. Agenda
• MQ V8 Review
– 64 Bit Buffer Pools
– 8 Byte Log Relative Byte Address (RBA)
– Channel Initiator (CHINIT) Statistics and Channel Accounting Data
– Storage Class Memory (SCM/Flash Memory)
– Other Enhancements
• Since MQ V8 GA
– Additional active logs
– JMS for CICS and IMS
– MQ family updates
• Works in progress
– z Operational Insights
– Hybrid connectivity options

3. 64 Bit Buffer Pools

4. Buffer Pools: Background
Q1
Page Set
4KB Page
Page Set
Q2
BufferPool
STGCLASS
maps
PSID
maps
(x 16)

5. Buffer Pools: The Problems
• Not much space below the bar for buffer pools
– Maximum 1.6GB, depending on common storage usage
• Put/Get to/from:
– Buffer pool = 'memory' speed (fast)
– Page set = 'disk' speed (slow)
• With fewer/small buffer pools, can spend a lot of time:
– Putting pages from buffer pool into page set (to free buffers)
– Getting pages from page set into buffer pool (to satisfy get requests)
– This is detrimental to performance
• A maximum of 16 buffer pools
– But up to 100 page sets, hence page sets must share buffer pools
• System programmers can spend a lot of time tuning:
– Buffer pool sizes
– Queue, buffer pool, and page set mappings

6. 64 Bit Buffer Pools: The Solution
• Buffer pools above the bar
– Buffer pools can (theoretically) make use of up to 16 EB of storage
• More buffer pools
– Up to 100 buffer pools
– Can have 1-1 mapping between page set and buffer pool
• More buffers per pool
– Above the bar
• Up to 999,999,999 4K buffers per pool
– Below the bar
• Up to 500,000 4K buffers per pool

7. Buffer Pools: Using 64 bit storage
DATA
CODE
DATA
2 GB bar
Queue Manager Address Space
Buffer Pool
Buffer Pool Buffer Pool Buffer Pool
Max 1.6GB for
buffer pools
16 EB
Buffer Pool
Move
above
bar

8. 64 Bit Buffer Pools: What has changed
• BUFFPOOL id
– 0 to 99
• BUFFERS
– Up to 500,000 if LOCATION(BELOW)
– Up to 999,999,999 if LOCATION(ABOVE)
• LOCATION
– BELOW – buffer pool is below the bar (default)
– ABOVE – buffer pool is above the bar
• PAGECLAS
– 4KB, if LOCATION(BELOW/ABOVE)
– FIXED4KB, if LOCATION(ABOVE)
• Permanent backing by real storage for life of Queue Manager
• No need to programmatically page fix/unfix when doing I/O
• Better performance
• Ensure you have enough real storage available!
DEFINE BUFFPOOL(<id>)
BUFFERS(<integer>)
PAGECLAS(4KB/FIXED4KB)
LOCATION(BELOW/ABOVE)

9. 64 Bit Buffer Pools: Migration
• To use this function version 8 new function must be
enabled using OPMODE(NEWFUNC,800)
– Otherwise behaviour is same as in version 7
– Though, LOCATION(BELOW) is valid regardless of OPMODE
• Some messages have changed regardless of the
value of OPMODE
– For example, DISPLAY USAGE PSID(*)CSQI010I !MQ21 Page set usage …
…
End of page set report
CSQI065I !MQ21 Buffer pool attributes ...
Buffer Available Stealable Stealable Page Location
pool buffers buffers percentage class
_ 0 1024 1000 99 4KB BELOW
_ 22 1024000 234561 23 FIXED4KB ABOVE
_ 88 12000 1200 10 4KB ABOVE
End of buffer pool attributes

10. 64 Bit Buffer Pools: Configuration
• CSQINP1
– DEFINE BUFFPOOL(22) LOCATION(ABOVE) BUFFERS(1024000)
REPLACE
– DEFINE BUFFPOOL(88) BUFFERS(12000) REPLACE
• CSQINP1 or dynamically
– DEFINE PSID(22) BUFFPOOL(22)
– DEFINE PSID(88) BUFFPOOL(88)
• CSQINP2 or dynamically
– ALTER BUFFPOOL(88) LOC(ABOVE)
CSQP024I !MQ21 Request initiated for buffer pool 88
CSQ9022I !MQ21 CSQPALTB ' ALTER BUFFPOOL' NORMAL COMPLETION
CSQP023I !MQ21 Request completed for buffer pool 88, now has 12000 buffers
CSQP054I !MQ21 Buffer pool 88 is now located above the bar

11. 64 Bit Buffer Pools: Performance Summary
• 16 Central Processor LPAR
• Each transaction puts and gets a random message from a pre loaded queue
• Second test requires a doubling in buffer pool size
Test Transaction rate
(per second)
Transaction cost
(CPU microsecs)
LPAR
% Busy
Channel path
% Busy
31 bit 232762 35.92 54% 56%
64 bit 235217 37.48 57% 57.4%
64 bit (enough buffers) 324213 38.12 83% 0.07%
Single requester per queue
Test Transaction rate
(per second)
Transaction cost
(CPU microsecs)
LPAR
% Busy
Channel path
% Busy
31 bit 149140 42.3 42% 75.4%
64 bit 145623 44.84 43.5% 75.9%
64 bit (enough buffers) 384062 40.65 99.59% 0.08%
Two requesters per queue

12. 8 Byte Log RBA

13. 6 byte log RBA: The Problem
• MQ for z/OS V7.1 (and earlier) uses a 6 byte log RBA (Relative Byte
Address) to address the log
• Gives an RBA range of 0 to x'FFFFFFFFFFFF' (= 255TB)
– Some customers reach this limit in 12 to 18 months
– At 100MB/sec, end of log range would be reached in 1 month
• The queue manager issues warning messages as it approaches the
end of the log RBA range
• If the end of the log RBA range is about to be reached the queue
manager will terminate to prevent loss of data
– A disruptive unplanned outage!

14. 6 byte log RBA: Resetting the log RBA
 To avoid an unplanned outage, at regular planned intervals:
1. Stop the queue manager cleanly
2. Define new log and bootstrap data sets
3. Run CSQUTIL RESETPAGE against each page set
– This resets the log RBA in header of each page so can be take a while to run
4. Restart the queue manager
• Some customers are happy to do this, but others are not!

15. 8 byte log RBA: The Solution
• IBM MQ for z/OS V8.0 supports an 8 byte (64 bit) log RBA
– Upper limit on logical log is now 64K times bigger
– At a 100MB/sec, this would take over 5000 years to fill
• URIDs are now 8 bytes long
• Format of BSDS and log records has changed to accommodate 8 byte
RBAs
• Utilities or applications that read the following are impacted
– BSDS
– Logs
– Console messages that contain the log RBA or URID
• Queue managers use a 6 byte log RBA until 8 byte log RBA is enabled

16. Enabling 8 byte log RBAs
1. Version 8 new function must be enabled
– In a QSG new function is only enabled once ALL queue managers have been started with
OPMODE(NEWFUNC,800)
2. Stop the queue manager cleanly
3. Define new BSDS data sets
– Recommended space allocation is now RECORDS(850 60) as a version 2 format BSDS contains more
data than a version 1 format BSDS
4. Run BSDS conversion utility (CSQJUCNV) to convert the version 1 BSDS to
version 2
– Creates a copy of a version 1 format BSDS in version 2 format
– Writes converted BSDS to new data set(s)
5. Rename BSDS data sets so that the version 2 format BSDS are used
during the next queue manager restart
6. Restart the queue manager

17. Using 8 byte log RBA
• Queue manager issues message CSQJ034I during
start-up to indicate whether a 6 or 8 byte log RBA is
in use
• The print log map utility (CSQJU004) displays the BSDS version
• The messages issued to warn that the queue manager is approaching the end
of the log RBA range remain the same, but the thresholds have been updated
11.25.05 STC05120 CSQJ099I !MQ4E LOG RECORDING TO COMMENCE WITH 281
281 STARTRBA=00000000039AF000
11.25.05 STC05120 CSQJ034I !MQ4E CSQJW007 END OF LOG RBA RANGE IS 0000FFFFFFFFFFFF
22.57.53 STC13100 CSQJ099I !MQ08 LOG RECORDING TO COMMENCE WITH 811
811 STARTRBA=0000000002AA8000
22.57.53 STC13100 CSQJ034I !MQ08 CSQJW007 END OF LOG RBA RANGE IS FFFFFFFFFFFFFFFF

18. Channel Initiator SMF Data

19. Chinit SMF: The Problem
• Prior to MQ V8 no SMF data for
– Chinit address space
– Channel activity
• Many customers have had to create their own “monitoring” jobs
– With periodic DISPLAY CHSTATUS commands
• Difficult to
– Manage historical data
– Investigate performance issues
– Perform capacity planning

20. Chinit SMF: The Solution
• New SMF data for channel initiator address space
– Collected at the same interval as the queue manager
• Channel Initiator Statistics (SMF 115, SubType 231)
– High level view of activity in the channel initiator address space
– Number of channels and TCB usage
– Dispatchers, Adapters, DNS, SSL
• Do I have spare capacity?
• Do I need more or less dispatchers/adapters?
• Channel Accounting Data (SMF 116, SubType 10)
– Detailed view of individual channels
• What work have channels been doing?
• Which channels are being heavily utilised?
– Controlled by STATCHL attribute on queue manager and channel definition
• Equivalent to ACCTQ for queues
• Data collected is a superset of that collected in the PCF messages on distributed platforms

21. Chinit SMF: The Solution
• Useful for
– Monitoring
– Capacity planning
– Tuning
• Separate controls from queue manager SMF allows “opt in”
• SupportPac MP1B updated to format new data

22. Adapter Task Statistics Report
Difference could indicate
wait for I/O due to
commit or disk read
MQI requests are processed
by first free adapter so adapters
lower in the list process less
requests

23. Channel Accounting Data
• Accounting (ACCTG) trace CLASS(4) enables collection of individual
channel information
• Channels can be included/excluded from collection
– Channel STATCHL attribute for predefined channels
– Queue manager STATACLS attribute for auto-defined cluster channels
• Controls all auto-defined channels, not individually
– Queue manager STATCHL attribute for client channels
• Generally low cost as most channels are long lived
– However, consider if you have a lot of short lived client connections
• Gives detailed information for each channel
– What has the channel done?
– What are my busy channels?

24. Channel Accounting Data Report

25. Channel initiator SMF controls
• You can start channel initiator statistics (STAT) trace
with
• You can display trace with
• ALTER and STOP TRACE commands have also been updated
• You can start channel initiator accounting (ACCTG) trace with
!MQ08 START TRACE(STAT) CLASS(4)
CSQW130I !MQ08 'STAT' TRACE STARTED, ASSIGNED TRACE NUMBER 05
CSQ9022I !MQ08 CSQWVCM1 ' START TRACE' NORMAL COMPLETION
!MQ08 START TRACE(ACCTG) CLASS(4)
CSQW130I !MQ08 ‘ACCTG' TRACE STARTED, ASSIGNED TRACE NUMBER 06
CSQ9022I !MQ08 CSQWVCM1 ' START TRACE' NORMAL COMPLETION
!MQ08 DISPLAY TRACE(*)
CSQW127I !MQ08 CURRENT TRACE ACTIVITY IS -
TNO TYPE CLASS DEST USERID RMID
02 STAT 01 SMF * *
05 STAT 04 SMF * *
06 ACCTG 04 SMF * *
END OF TRACE REPORT

26. Storage Class Memory (SCM)

27. Background – Shared queues
• Queue managers must
be in the same sysplex
• Create a Queue Sharing
Group (QSG)
• Define shared queues in
the Coupling Facility
(CF)
Shared
QueueCoupling Facility (CF)
Application Application
QMgr QMgr

28. Background – Offloading shared queue messages
• Messages larger than 63KB cannot be stored in the CF
– Message body is offloaded to SMDS or DB2
– Reference to message is stored in the CF
• CFSTRUCT OFFLOAD rules allow conditional offloading of messages
smaller than 63KB
– OFFLD1TH(70), OFFLD1SZ(32K) – offload messages >32KB if 70% full
– OFFLD2TH(80), OFFLD2SZ(4K) – offload messages >4KB if 80% full
– OFFLD3TH(90), OFFLD3SZ(0K) – offload all message data if 90% full
– Progressively smaller messages written to SMDS as the structure fills

29. CF Flash storage
• z/OS 2.1 and zEC12 GA2 introduce Coupling Facility Flash storage
• Use of CF Flash storage
– Can provide additional shared queue capacity for maintenance windows or consumer outages
– When structure is 90% full, the CF Flash algorithm starts moving the middle of the queue out to flash
storage, keeping the faster “real” storage for messages most likely to be got next
– Offload rules can allow even more messages to be stored by offloading data to SMDS (or DB2)

30. CF Flash: Planned emergency storage scenario
• Default CFSTRUCT offload
rules cause progressively
smaller messages to be
written to SMDS as the
structure starts to fill.
• Once 90% threshold is
reached
– the queue manager stores the
minimum data in the CF for each
message
– CF Flash pre-staging algorithm
starts to move reference messages
for new messages arriving into the
CF structure into SCM.
• Increases capacity of the
CF structure, but offloading
messages to SMDS will
affect performance
Note: Assume all messages < 63KB
Flash
CFStruct
70%
80%
90%
Offload > 32KB
offload > 0KB
offload > 4KB
SMDS
REF REF
REF REF
REF REF

31. CF Flash: Maximum Speed Scenario
• We want to keep high
performance messages in the
CF for most rapid access.
• CFSTRUCT offload rules are
disabled.
• Once 90% threshold is
reached, the CF Flash
algorithm starts moving new
messages to flash storage,
keeping the faster “real”
storage for messages most
likely to be got next.
• As messages are got and
deleted, the CF flash algorithm
attempts to pre-stage the next
messages from flash into the
CFSTRUCT so they are
rapidly available for MQGET.
• In this scenario the flash
storage acts like an extension
to “real” CFSTRUCT storage.
However it will be consumed
more rapidly since all message
data is stored in it.
Flash
CFStruct
70%
80%
90%
Offload = 64KB => disabled
Offload = 64KB => disabled
SMDS
Offload = 64KB => disabled
Note: Assume all messages < 63KB
MSG MSG
MSG MSG

32. CF Flash: Storage
Scenario Offload
Rule
Msg
Size
Total
Msgs
# in 'real' SMDS
space
# in 200 GB
flash
Augmented
(limit 30GB)
No SMDS
No Flash
1kB 3M 3M
4kB 900,000 900,000
16kB 250,000 250,000
SMDS
No Flash
MQ 90% 1kB 3.2M 3.2M 800MB
MQ 80% 4kB 1.8M 1.8M 5GB
MQ 80% 16kB 1.3M 1.3M 20GB
“Emergency”
Scenario
MQ 90% 1kB 190M 2M 270GB 188M 30GB
MQ 80% 4kB 190M 600,000 850GB 189M 30GB
MQ 80% 16kB 190M 150,000 3TB 189M 30GB
“Speed”
Scenario
CF 90% 1kB 150M 2M 148M 26GB
CF 90% 4kB 48M 600,000 47M 8GB
CF 90% 16kB 12M 150,000 11M 2GB
CF Structure size = 4GB
Significant increase in the number
that can be put to the CF

33. CFLEVEL(4) using 8KB Messages
• Saw-tooth effect
– Occurs when putting task goes into retry mode due to MQRC_STORAGE_MEDIUM_FULL
– Results in 5 sec pauses
• Non-SCM workload still completes in 90% of the time of SCM workload
• CPU cost of non-SCM v's SCM workload in MVS differs by less than 2% (hence, insignificant)
• Get rate once the putting task has completed
– Non-SCM – 21100 x 8K messages/second ~ 164MB/sec
– SCM – 19000 x 8K messages/second ~ 148MB/sec
1
4
7
10
13
16
19
22
25
28
31
34
37
40
43
46
49
52
55
58
61
64
67
70
73
76
79
82
85
88
91
94
0
100000
200000
300000
400000
500000
600000
700000
800000
900000
1000000
CFLEVEL(4) 8K Messages - XMIT Queue depth
No SCM available SCM available Depth that SCM used
Time (seconds)
QueueDepth

34. Other Enhancements

35. Channel Compression using zEDC Express
• zEC12 zEnterprise Data Compression (zEDC) Express
– Hardware compression
• Channel Compression
– Typically used on high latency/low-bandwidth networks
– Reduces amount of data being flowed
– Reduces CPU cost per message
– Can yield higher reduction in CPU costs for SSL channels (data is compressed before being encrypted)
– Performed by Dispatcher tasks in the Channel Initiator address space
• Channel attribute COMPMSG(ZLIBFAST)
– Message data compressed using the zlib compression technique
– Compression can be offloaded to zEDC Express

36. Channel Compression – ZLIBHIGH v ZLIBFAST
• Dispatcher tasks
– 7 has 1 channel using ZLIBHIGH for compression
– 8 has 1 channel using ZLIBHIGH for decompression
98.5% Busy!
17 microsecs spent waiting for hardware compression
But, overall cost much cheaper than ZLIBHIGH!
• Dispatcher tasks
– 7 has 1 channel using ZLIBFAST for compression
– 8 has 1 channel using ZLIBFAST for decompression

37. Channel Compression – Transaction rate

38. Channel Compression – Transaction cost

39. MQ platform and product updates
• Split Cluster Transmit Queue availability in MQ for z/OS
– Ability to separate workloads
– Reduce load on SYSTEM.CLUSTER.TRANSMIT.QUEUE
• Advanced Message Security (AMS)
– Now integrated into the base MQ for z/OS product
– Offers improved performance and usability
• MFT has been updated to reduce reliance on USS

40. Redbooks publication covers MQ V8

41. Since V8 GA

42. Additional Active Logs
• Improve resilience to issues affecting log archiving
• Maximum active log capacity increased 10x
• Now up to 310 x 4GB active logs.
• Requires:
– MQ V8 in NewFunc mode
– V2 format BSDS (introduced in V8 for 64bit wide RBA)
– APAR PI46853
85

43. Enhanced Java SE support for MQ JMS
• CICS TS
CICS java programs san use the IBM MQ classes for JMS in the CICS® Open Services Gateway
initiative (OSGi) Java™ Virtual Machine (JVM) server
– JMS 1.1 if using MQ for z/OS V7.1
– JMS 2.0 (requires Java 7) if using MQ for z/OS V8.0
– CICS TS
• V5.2 + PI32151
• V5.3
– MQ
• V7.1 – JMS PI29770 (supersedes 7.1.0.6) or later CSD
• V8 – JMS 8.0.0.2 PI33038 or later CSD + MQ base PI28482
– For more details, see http://ibm.biz/MQCICSJMS
• IMS
IMS java programs can use the IBM MQ classes for JMS, JMS 2.0 spec
– IMS V13 MPR, BMP, IFP, JMP, JBP regions
– MQ V8
• V8 – JMS 8.0.0.4 PI41909 + MQ base PI45236
– For more details, see http://ibm.biz/MQIMSJMS

44. Capped Expiry
• New Queue and Topic attribute enforces a maximum lifetime for
messages
• Added to the CUSTOM attribute, CAPEXPRY(value) limits or adds the
expiry interval for the message, ‘as if an application change’ had been
made.
• Admin control of application behaviour
– use QALIAS for fine-grained, per application, control
– Minimum value of all objects on resolution path used, eg QALIAS->QREMOTE->XMITQ
• APAR PI50761 (also in 8.0.0.4)
89

45. Client or Channel partner audit and control
• During initialization, channels exchange code version levels (Version,
Release, Modification, Fixpac)
• New fields in MQCXP to pass RemoteProduct and RemoteVersion to
exits, values match DISPLAY CHSTATUS RPRODUCT RVERSION
• Sample security exit logs this information – see below. Trivial change
could be used to reject ‘down level’ connections.
• APAR PI51495 (also in 8.0.0.2)
91
05/08/2015,09:41:05,SYSTEM.ADMIN.SVRCONN,SVRCONN,9.20.237.15,MARKW1,MQJB,8.0.0.4,13
05/08/2015,09:55:19,SYSTEM.DEF.SVRCONN,SVRCONN,9.20.237.15,MARKW1,MQCC,8.0.0.4,13
05/08/2015,09:56:22,ZOS.TO.ZOS,RECEIVER,9.20.138.161,MQ26,MQMV,8.0.0.0,13
05/08/2015,09:57:20,DISTRIBUTED.TO.ZOS,RECEIVER,9.20.237.15,DISTRIBUTED.QMGR,MQMM,8.0.0.4,13
05/08/2015,10:09:34,SYSTEM.DEF.SVRCONN,SVRCONN,9.20.237.15,FredBloggs,Unknown,Unknown,7
05/08/2015,10:13:17,SYSTEM.DEF.SVRCONN,SVRCONN,9.20.230.14,SIDDALP,MQCC,7.1.0.0,11
05/08/2015,10:13:45,SYSTEM.ADMIN.SVRCONN,SVRCONN,9.20.230.14,SIDDALP,MQJB,7.1.0.0,10

46. IBM z Operational Insights
• Cloud based service from IBM which analyses operational data to
identify inefficiencies
• Added an MQ ‘tile’ to help tune buffer pools
93

47. IBM z Operational Insights
A New Way to Optimize your z Systems
Rapid, cloud-based analytics enable you to:
see quantified savings upfront
identify what actions to take next
compare your performance to
others
Try the open beta today, for free! ibm.biz/try-zoi
Cut costs. Save time. No installation necessary.
Actionable insights for CICS, MQ , IMS & WAS in minutes, not hours.
Just add operational data.

48. MQ Self Service
Digital IT Enterprise IT
Cloud
On-
Prem
Cloud
On-
Prem
Bluemix
Message Hub
Based on Apache Kafka
MQ Light Cloud Service API REST Kafka
Cloud Data
Services
Apache
Spark
Bluemix
Local
MQ Light Software
(Local stand-alone Server)
Watson
As-a-service
on-prem
management
of MQ
PureApp
Cloud
PureApp SW
PureApp HW
Dev-ops
CI/CD
Monthly
App AccessPartner
Traditional Data Centre
Enterprise Integration and Messaging
MQ
Light
API
HGateway
In the works: New Connectivity Options

49. Monday
10:30-11:30 3592 New MQ features
3452 Managing applications
12:00-13:00 2835 MQ on z/OS and Distributed
15:00-16:00 3470 Latest MQ z/OS features
2833 Where is my message?
3544 MQ Light in an MQ infrastructure
16:30-17:30 3573 Hybrid cloud messaging
2941 MQ Advanced
Tuesday
08:30-09:30 3540 The MQ Light API
12:00-13:00 3456 The IBM MQ Appliance
13:15-14:15 3499 Introducing Message Hub
3458 MQ Appliance administration
14:30-15:30 6432 MQ updates and futures (InnerCircle)
2849 Messaging feedback roundtable
16:00-17:00 3544 MQ Light in an MQ infrastructure
3513 MQ hands on lab
Wednesday
08:30-09:30 3602 Managing your MQ environment
12:00-13:00 3613 Designing MQ self service
6408 Hybrid messaging roadmap (InnerCircle)
13:15-14:00 3416 HA and DR with MQ
3433 Why secure your messaging?
15:45-16:30 3429 Securing MQ
2847 Meet the messaging experts
16:00-17:00 3508 MQ Light hands on lab
16:45-17:30 2275 Migrating to the IBM MQ Appliance
Thursday
08:30-09:15 3420 MQ Clustering
2931 Business agility with self service MQ
09:30-10:15 3479 MQ z/OS clusters and shared queue
3450 Optimising MQ applications
2849 Messaging feedback roundtable
10:30-11:15 3465 MQ Appliance high availability
3481 MQ z/OS messaging connectivity
11:30-12:15 3474 Active-active messaging
3537 Monitoring and managing MQ
3425 MQ publish/subscribe
Find us at the EXPO:
Hybrid Integration peds 65-68
Check out the Hybrid Messaging sub topic under the
Hybrid Integration topic for further customer and business
partner sessions
Hybrid Messaging from the IBM experts at InterConnect 2016
Sunday
14:30-15:30 6408 Hybrid messaging roadmap (InnerCircle)

50. Where can I get more information?
IBM Messaging developerWorks
developer.ibm.com/messaging
IBM Messaging Youtube
https://www.youtube.com/IBMmessagingMedia
LinkedIn
Ibm.biz/ibmmessaging
Twitter
@IBMMessaging
IBM MQ Facebook
Facebook.com/IBM-MQ-8304628654/

51. Notices and Disclaimers
98
Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission
from IBM.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial
publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED
"AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS
INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and
services are warranted according to the terms and conditions of the agreements under which they are provided.
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers
have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in
which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and
discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their
specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and
interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such
laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law

52. Notices and Disclaimers Con’t.
99
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not
tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the
ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual
property right.
IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®,
FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG,
Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®,
PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®,
StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business
Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at "Copyright and trademark information" at: www.ibm.com/legal/copytrade.shtml.

53. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee
Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.