MarkTaylorIBM, profile picture
Uploaded byMarkTaylorIBM
PDF, PPTX4,142 views

IBM MQ - Comparing Distributed and z/OS platforms

The document compares the IBM MQ implementations on z/OS and distributed platforms, highlighting their operational and architectural differences. Key topics include installation, security, storage management, messaging APIs, application programming, and administrative procedures. It also discusses the evolution of features and emphasizes the need for platform-specific considerations despite a shared API.

Embed presentation

Download as PDF, PPTX
© 2015 IBM Corporation 2291: Are z/OS & distributed MQ platforms like oil and water? Mark Taylor Lyn Elkins
Introduction • One objective of MQ is isolating apps from needing to understand platforms ‒ There is a common API that can be expressed in many languages • Another objective is to have (reasonably) common operational model ‒ Much of admin is the same on all platforms • But it’s not all the same ‒ One dichotomy has always been whether to be natural to MQ-ness or behave like other things on the platform ‒ Some features don’t make sense on some platforms  For example, .Net interface is only on Windows ‒ Some features have not been implemented everywhere for other reasons • So there are differences, and that is what this presentation will cover • Will base this on V8
Code Streams • There are essentially two implementations of MQ from Hursley lab ‒ z/OS ‒ Distributed (Windows, Unix, Linux, i) ‒ There are some further subspecies variants like VSE or NSS • Within Distributed implementation, there are some platform unique features ‒ But we won’t discuss those here ‒ Most platform-unique code abstracts OS facilities like locking or NLS or threads • In the early days, some code was written for one and then “ported” ‒ In particular, the channel code ‒ Meant double-fixing, and re-porting for each release • Internal architecture (eg tasks, threads) very different ‒ But we won't discuss much of that. Understanding externals is more important • Since V7.0, some code is truly common ‒ Just one copy of the source part shared between both ‒ New features generally use common code where feasible
Sections • Setting up • Application Programming • Administration
How this presentation works • Lyn will talk about z/OS in this color • Mark will talk about Distributed in this colour
Setting Up
Getting started • Lots of differences in initial installation and setup • Getting the code on the box is part of the job ‒ MQ uses native installation techniques for all platforms ‒ Needs a suitably-authorised person to do that installation  SMPE for z/OS, installp for AIX, rpm for Linux etc • But other differences primarily due to ‒ Security ‒ Storage • Share philosophy of needing no more features than is found on the system ‒ So no prereq software for core capabilities of MQ ‒ Product ships components that are needed such as gskit ‒ But can exploit things that we know are there  For example, on z/OS we use the system-provided SSL ‒ Some extended capabilities may have additional prereqs  Shared Queues need DB2
Security • On Distributed, MQ implements its own authorisation mechanism ‒ There is no generally-accepted standard interface on these systems • And relies on the existence of certain userids ‒ There are differences even between individual platforms • On z/OS, MQ exploits the common authorization interface, SAF ‒ And so the z/OS security administrator has to be involved ‒ Define the profiles etc. • Will look more at security later on
Storage (Distributed) • On Distributed, MQ uses directories such as /var/mqm/qmgrs and /var/mqm/logs ‒ The system administrator will probably allocate filesystems and mount them ‒ These days, may have separate SAN administrator • Each queue has its own file within the filesystem ‒ To store the message data ‒ Each queue could hold 1TB • Queues do not interfere with each other's storage requirements ‒ Subject to max size of filesystem • Logs can be LINEAR or CIRCULAR ‒ Choice made when qmgr is created ‒ With linear logging, you then need a job to remove old log files ‒ MQ does not directly implement dual-logging; relies on RAID filesystems
Storage (z/OS) • Queues are handled via pagesets and bufferpools • Multiple queues may use the same pageset and bufferpool ‒ Can lead to storage contention ‒ V8 increases number of bufferpools to match number of pagesets • No direct equivalent of circular logging but constraints can be applied to achieve a similar effect ‒ Semi-circular? ‒ Active logs are ‘almost like circular’, with offloading to archive logs • Logs are managed via the BSDS • MQ understands and implements Dual Logging • Tool provided to format and extract messages from log
Shared Queues • A z/OS-unique feature ‒ Multiple queue managers can see the same queue ‒ Continuous processing of messages from a queue even when one LPAR fails • Relies on the Coupling Facility hardware ‒ And relies on DB2 Data Sharing • Results in several unique possibilities ‒ Inter-qmgr communication without standard channels ‒ Dynamic selection of which qmgr to connect to • Effects appear in many places ‒ For example, single MQSC command can be issued to multiple queue managers giving multiple responses
Extra Features • MQ V7.5 on Distributed incorporated MFT (nee FTE) and AMS ‒ "MQ Advanced" license covers all features • On z/OS, these are available as separate products ‒ V8 improved technical integration but still separate licenses • On z/OS, use of inbound client connections was restricted ‒ Restriction removed in V8 (no longer a CAF) • Distributed MQ has the MQXR service for mobile (MQTT) clients ‒ Not available on z/OS ‒ Expected that mobile clients connect via front-end qmgr before hitting z/OS apps
Application Programming
General • Default codepages and encoding differ by platform • Always use the header files for your platform ‒ Don't be tempted to cross-compile • Maximum lengths of fields may vary • MQI return codes may be different ‒ Often because underlying storage mechanisms have different error conditions ‒ For example, Coupling Facility errors on shared queues • z/OS does not have MQ clients ‒ Some parameters to some verbs only apply in client environments ‒ For example, the MQCD passed during MQCONNX
API - Connections • MQCONN/MQCONNX ‒ Verbs not required for CICS transactions  MQHC_DEF_HCONN can be used for subsequent verbs in applications ‒ ConnTag is available to control serialization  An application (especially an MCA) can tell if another instance of itself is already running  On either the same local qmgr or any other in the QSG ‒ Group connection to QSG ‒ Lots of client-only options for connection  MQCD can be specified  Reconnect options ‒ MQCNO_SHARED options for multi-threaded applications  Controls whether an hConn can be (serially) used by other threads in the same process ‒ Fastpath binding ‒ Control of accounting  When accounting information is being collected, some apps may request exclusion
API - Disconnections • MQDISC ‒ Always recommended ‒ Rollback when application abends  Although definition of "abend" is not clear in every case  CICS and IMS do make it clear!  A JVM has been known to return OK to the operating system even when the user's code has caused a fatal exception ‒ Rollback when not used and application ends
API - Objects • MQOPEN ‒ Default dynamic queue names begin with CSQ.* or AMQ.* ‒ Distributed can open multiple queues simultaneously via Distribution List  Publish/Subscribe preferred cross-platform model • MQCLOSE ‒ No platform differerences in practice • MQSET ‒ Follows the same rules as MQSC attributes for platforms • MQINQ ‒ Follows the same rules as MQSC attributes for platforms
API - Messages • MQPUT/MQPUT1 ‒ Messages can be automatically segmented  But Message groups are cross-platform ‒ Distributed supports "Reference messages" which can avoid putting large amounts of data on a queue • MQGET ‒ z/OS has "get with signal" to asyncronously notify app when messages appear  MQCB is now preferred cross-platform model ‒ z/OS has MARK_SKIP_BACKOUT for simpler processing of poison messages  Bad messages can be moved to an application-specific DLQ while backing out other resource changes ‒ Distributed can get portions of messages via segmentation • MQSUB ‒ No platform differences • MQSUBRQ ‒ No platform differences
API – Flow control • MQCB ‒ Definition of the callback function in MQCBD varies by environment ‒ eg C function pointer, CICS program name • MQCTL ‒ Not in IMS adapter ‒ On z/OS, apps must be authorized to use USS • MQSTAT ‒ Client applications only ‒ But usable regardless of server platform
API - Properties • MQDLTMP • MQBUFMH • MQCRTMH • MQDLTMH • MQMHBUF • MQSETMP • MQINQMP • No platform differences
API - Transactions • MQBEGIN ‒ Only available on Distributed ‒ z/OS always has a transaction manager available • MQCMIT ‒ On all platforms when not running under external TM • MQBACK ‒ On all platforms when not running under external TM • Default for MQ transactional behaviour is different ‒ MQI on Distributed assumes NO_SYNCPOINT ‒ MQI on z/OS assumes SYNCPOINT ‒ Always specify syncpoint options on MQI calls • Environments for two-phase transactions differ ‒ On z/OS, RRS CICS and IMS are all available for transaction management ‒ On Distributed, XA is available as the standard interface  And MQ can act as a transaction manager
Exits • z/OS has API-Crossing exit for CICS ‒ But no other environments • Distributed has API exit for all environments ‒ With a very different interface • Installable Services on Distributed ‒ But very few people write these so not too interesting ‒ Primarily used for the OAM security module • Channel send exit – ExitSpace field ‒ Used to reserve space in network transmission buffers for send exits ‒ Always zero on z/OS • No publish exit on z/OS • z/OS exits have MQXWAIT ‒ Necessary because process/thread model for channels is different
Administration
Object Definitions • Attributes and ini files ‒ Some items are queue manager attributes on one platform but not other ‒ z/OS has lots related to its storage • Some unique object types ‒ z/OS has STGCLASS and CFSTRUCT ‒ Distributed has SERVICES and COMMINFO • Startup ‒ CSQZPARM is assembled/linked and other inputs run during startup  Reset configuration, define default objects etc ‒ On Distributed, standard objects are created by qmgr creation and updated during migration
Object Attributes – Queue Manager • Apart from shared queue and storage-related attributes … ‒ Various events differ as shown in other charts ‒ Some z/OS attributes are in qm.ini for Distributed • z/OS only ‒ ACTCHL, MAXCHL ‒ ADOPTCHK/ADOPTMCA ‒ CHIDISPS, CHIADAPS ‒ DNSGROUP, DNSWLM ‒ EXPIRYINT ‒ GROUPUR ‒ IGQ, IGQAUT, IGQUSER ‒ LSTRTMR,LU62ARM, LU62CHL, OPORTMIN, OPORTMAX, RCVTMIN, RCVTTYPE, TCPNAME, TCPKEEP, TCPSTACK ‒ SCYCASE ‒ SSLTASKS ‒ TRAXSTR, TRAXTBL • Distributed only ‒ ACCTCONO, ACCTINT, ACCTMQI, ACCTQ ‒ ACTIVREC ‒ CCSID ‒ CERTVPOL ‒ CHAD ‒ SCHINIT, SCMDSERV
Object Attributes – Queues and Channels • Apart from shared queue and storage-related attributes … • Queue ‒ DEFTYPE(SHAREDYN) z/OS ‒ HARDENBO only effective on z/OS ‒ INDXTYPE z/OS ‒ DISTL Distributed ‒ NPMCLASS Distributed ‒ SCOPE Distributed only, but obsolete ‒ STATQ Distributed ‒ TriggerData for transmission queues can be blank on Distributed, names channel on z/OS • Channel ‒ CONNAME 48 characters on z/OS, 264 elsewhere ‒ Format of exit names and exit data is platform-specific ‒ STATCHL Distributed only before V8
Queue Manager operations • Message Expiry ‒ z/OS has explicit config for timing of task to remove expired messages ‒ Distributed has a similar task but no documented configuration • Security Cache Scavenger ‒ z/OS has parameters to control authority cache lifetime ‒ No equivalent on Distributed; use REFRESH SECURITY explicit command • Storage Scavengers ‒ z/OS has tasks to release bufferpool and pageset storage ‒ Distributed will release queue file storage at intervals • Queue Indexing ‒ z/OS has explicit indexes on queues to assist with retrieval patterns ‒ Distributed has hashing to perform similar role but no documented configuration
Intercommunication and Clusters • Channels are the same • Clustering is essentially the same across all platforms • MQ 7.5 introduced concept of multiple cluster transmission queues ‒ Made common in V8
Security (1) • Authentication feature added in V8 ‒ Distributed supports userid validation in operating system and explicit LDAP ‒ z/OS supports userid validation in operating system ‒ Both support LDAP when transparently used by OS • SSL/TLS configuration ‒ Distributed (mostly) qmgr uses gskit toolkit ‒ z/OS qmgr uses System SSL ‒ Can lead to discrepancies in crypto algorithms supported ‒ Different versions support different algorithms ‒ And there may also be client-related discrepancies  Java programs rely on JSSE implementations  .Net programs (from V8) can use Microsoft inbuilt implementations  NSS client uses OpenSSL ‒ There is a good common overlap between all of these, but not identical sets
Security (2) – Access Control • z/OS ‒ Uses system-provided interface for authorization  SAF is common API to RACF, Top Secret, ACF2 ‒ Has to work with the 4 permissions available in SAF ‒ No distinction between PUT and GET  Often alias queues are used to isolate permissions ‒ Granular control of "impersonation" (setting context, alt-user) ‒ One operation may result in several authorization queries • Distributed ‒ MQ-provided authorisation interface  Implemented in the OAM ‒ Many permissions on objects ‒ Global controls on impersonation  If you have authority to use alt-user, there are no constraints on which user ‒ Well-known "mqm" id for full authority
Commands • Basic OS-level commands are different ‒ Create, start, stop, delete queue manager procedures ‒ Distributed has command-line interface ‒ z/OS has JCL • Issuing configuration commands like ALTER QLOCAL ‒ Distributed has runmqsc shell ‒ z/OS has ISPF panels for most commands ‒ And the +cpf commands for runmqsc equivalence ‒ MQ Explorer is product-provided common GUI • Common programming interface (PCF) for configuration commands ‒ z/OS requires an "extended" format which may have multiple sets of responses  Supporting a Queue Sharing Group environment ‒ Distributed supports the same format but not the default ‒ Differences are hidden in the Java PCF classes
MQSC Commands • Some commands not available in all platforms ‒ Apart from those related to OS-specific features • RESET QSTATS is only on z/OS ‒ PCF available on all platforms • ARCHIVE LOG is only on z/OS ‒ even though Distributed also have logs • DISPLAY SYSTEM • MOVE QLOCAL ‒ V8 has dmpmqmsg • DISPLAY QMSTATUS ‒ Some items have z/OS specific commands like DISPLAY CMDSERV • STOP CONN only on Distributed ‒ All platforms have STOP CHL to kill client connections • Some z/OS MQSC have command-line equivalents on Distributed ‒ STOP QMGR == endmqm
• DISPLAY CONN/QSTATUS ‒ App name shows up on distributed; CHIN on z/os (though SMF does include it) • DISPLAY QMSTATUS not available
Monitoring • Many queue manager event messages are common ‒ For example, queue full • But not every event is on every platform ‒ Authorisation, Logging, and Channel auto-definition events are Distributed only ‒ IMS Bridge events are only on z/OS • Recording queue manager and application activity is very different ‒ z/OS has SMF 115 and 116 records ‒ Distributed has accounting, statistics and application activity events • Distributed accounting and stats events are analogous to SMF 116 ‒ No equivalent to 115 records
Events Images
Problem Determination • On Distributed, there are several places to look for PD information ‒ Error logs written to /var/mqm/errors and /var/mqm/qmgrs/<qmgr>/errors ‒ FFST written to /var/mqm/errors for serious errors ‒ Trace provided by MQ commands and written to /var/mqm/trace • On z/OS, also numerous places to follow the clues: ‒ The MSTR and CHIN JES log  Should always be the first place to look ‒ MQ API trace (aka user parameter trace) – a GTF trace ‒ SMF 115 statistical information ‒ SMF 116 class(3) accounting (task related) data ‒ A dump for serious problems
Backup • MAKEDEF and dmpmqcfg are tools to backup configuration ‒ With V8, have dmpmqmsg (CSQUMSG ??) to backup messages • On Distributed, backup of log files is done by stopping qmgr and copying /var/mqm/log directory ‒ rcdmqing takes images of queues into logs • On z/OS, full and fuzzy backups of pagesets are supported • CFSTRUCT backup required for QSG ‒ takes image of shared queue into logs
High Availability and Disaster Recovery • Shared queues on z/OS for continuous processing • On Distributed, MQ provides multi-instance ‒ Not on z/OS because ARM is provided • Cross-site DR will usually use disk replication for any platform
Summary • Title asks about oil and water • Perhaps (olive) oil and (balsamic) vinegar is better description ‒ Blending together
Notices and Disclaimers Copyright © 2015 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.
Notices and Disclaimers (con’t) 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 herein 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, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®, 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.
Thank You Your Feedback is Important! Access the InterConnect 2015 Conference CONNECT Attendee Portal to complete your session surveys from your smartphone, laptop or conference kiosk.

More Related Content

PDF
IBM MQ V9 Overview
byMarkTaylorIBM
 
PDF
Alphorm.com Formation Docker (2/2) - Administration Avancée
byAlphorm
 
PDF
An Introduction to the Message Queuing Technology & IBM WebSphere MQ
byRavi Yogesh
 
PDF
Infrastructure as "Code" with Pulumi
byVenura Athukorala
 
PPTX
ACI Hands-on Lab
byCisco Canada
 
PDF
Embedded Android
by晓东 杜
 
PPT
IBM Websphere MQ Basic
byPRASAD BHATKAR
 
PPTX
Windows Automation with Ansible
byAgile Testing Alliance
 
IBM MQ V9 Overview
byMarkTaylorIBM
 
Alphorm.com Formation Docker (2/2) - Administration Avancée
byAlphorm
 
An Introduction to the Message Queuing Technology & IBM WebSphere MQ
byRavi Yogesh
 
Infrastructure as "Code" with Pulumi
byVenura Athukorala
 
ACI Hands-on Lab
byCisco Canada
 
Embedded Android
by晓东 杜
 
IBM Websphere MQ Basic
byPRASAD BHATKAR
 
Windows Automation with Ansible
byAgile Testing Alliance
 

What's hot

PPTX
SD-WAN Catalyst a brief Presentation of solution
bypepegaston2030
 
PPTX
BTRisk Zararlı Yazılım Analizi Eğitimi Sunumu - Bölüm 2
byBTRisk Bilgi Güvenliği ve BT Yönetişim Hizmetleri
 
PDF
Kablosuz Ağlarda Güvenlik
byBGA Cyber Security
 
PDF
Alphorm.com Formation Nouveautés Windows Server 2016
byAlphorm
 
PPTX
Wamp server
byStefyta Alexa
 
PPTX
13 DHCP Configuration in Linux
byHameda Hurmat
 
PPTX
VMware Advance Troubleshooting Workshop - Day 3
byVepsun Technologies
 
PPTX
OpenStack Architecture and Use Cases
byJalal Mostafa
 
PDF
Websphere MQ admin guide
byRam Babu
 
PDF
Ansible
byRaul Leite
 
PPTX
IBM MQ Overview (IBM Message Queue)
byJuarez Junior
 
PDF
Introduction to Linux Drivers
byAnil Kumar Pugalia
 
PDF
Introduction to EasyBuild: Tutorial Part 1
byinside-BigData.com
 
PPTX
12 factor app an introduction
byKrishna-Kumar
 
PPTX
VMware Advance Troubleshooting Workshop - Day 5
byVepsun Technologies
 
PDF
Introduction to Vagrant
byMarcelo Pinheiro
 
PDF
Introduction to VoIP, RTP and SIP
byThousandEyes
 
PDF
SAP HANA SPS10- Workload Management
bySAP Technology
 
PPTX
V mware v-sphere & vsa presentation
byBusiness Computer Associates, Inc
 
PPTX
Tìm hiểu và triển khai ứng dụng Web với Kubernetes
byGMO-Z.com Vietnam Lab Center
 
SD-WAN Catalyst a brief Presentation of solution
bypepegaston2030
 
BTRisk Zararlı Yazılım Analizi Eğitimi Sunumu - Bölüm 2
byBTRisk Bilgi Güvenliği ve BT Yönetişim Hizmetleri
 
Kablosuz Ağlarda Güvenlik
byBGA Cyber Security
 
Alphorm.com Formation Nouveautés Windows Server 2016
byAlphorm
 
Wamp server
byStefyta Alexa
 
13 DHCP Configuration in Linux
byHameda Hurmat
 
VMware Advance Troubleshooting Workshop - Day 3
byVepsun Technologies
 
OpenStack Architecture and Use Cases
byJalal Mostafa
 
Websphere MQ admin guide
byRam Babu
 
Ansible
byRaul Leite
 
IBM MQ Overview (IBM Message Queue)
byJuarez Junior
 
Introduction to Linux Drivers
byAnil Kumar Pugalia
 
Introduction to EasyBuild: Tutorial Part 1
byinside-BigData.com
 
12 factor app an introduction
byKrishna-Kumar
 
VMware Advance Troubleshooting Workshop - Day 5
byVepsun Technologies
 
Introduction to Vagrant
byMarcelo Pinheiro
 
Introduction to VoIP, RTP and SIP
byThousandEyes
 
SAP HANA SPS10- Workload Management
bySAP Technology
 
V mware v-sphere & vsa presentation
byBusiness Computer Associates, Inc
 
Tìm hiểu và triển khai ứng dụng Web với Kubernetes
byGMO-Z.com Vietnam Lab Center
 

Viewers also liked

PDF
IBM MQ - Comparing Distributed and z/OS platforms
byMarkTaylorIBM
 
PDF
IBM MQ - High Availability and Disaster Recovery
byMarkTaylorIBM
 
PDF
IBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
byDavid Ware
 
PDF
IBM MQ - better application performance
byMarkTaylorIBM
 
PDF
What's new in IBM MQ Messaging
byMarkTaylorIBM
 
PDF
Iib v10 performance problem determination examples
byMartinRoss_IBM
 
PDF
InterConnect 2016: IBM MQ self-service and as-a-service
byDavid Ware
 
PDF
IBM MQ - Monitoring and Managing Hybrid Messaging Environments
byMarkTaylorIBM
 
PPTX
Understanding mq deployment choices and use cases
byLeif Davidsen
 
PPT
Data Federation
byStephen Lahanas
 
PPTX
IBM MQ Advanced - IBM InterConnect 2016
byLeif Davidsen
 
PDF
MQ What's New Beyond V8 - V8003 level
byMarkTaylorIBM
 
PDF
InterConnect 2016: What's new in IBM MQ
byDavid Ware
 
PDF
MQ Security Overview
byMarkTaylorIBM
 
PDF
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
byT.Rob Wyatt
 
PDF
WebSphere Connectivity & Integration: What's New in the Messaging Family?
byIBM Sverige
 
PDF
InterConnect 2016, OpenJPA and EclipseLink Usage Scenarios (PEJ-5303)
byKevin Sutter
 
PDF
Big Data: InterConnect 2016 Session on Getting Started with Big Data Analytics
byCynthia Saracco
 
PDF
DevOps & Continuous Test for IIB and IBM MQ
byStuart Feasey
 
PDF
IBM InterConnect 2016: Security for DevOps in an Enterprise
bySanjeev Sharma
 
IBM MQ - Comparing Distributed and z/OS platforms
byMarkTaylorIBM
 
IBM MQ - High Availability and Disaster Recovery
byMarkTaylorIBM
 
IBM MQ: Managing Workloads, Scaling and Availability with MQ Clusters
byDavid Ware
 
IBM MQ - better application performance
byMarkTaylorIBM
 
What's new in IBM MQ Messaging
byMarkTaylorIBM
 
Iib v10 performance problem determination examples
byMartinRoss_IBM
 
InterConnect 2016: IBM MQ self-service and as-a-service
byDavid Ware
 
IBM MQ - Monitoring and Managing Hybrid Messaging Environments
byMarkTaylorIBM
 
Understanding mq deployment choices and use cases
byLeif Davidsen
 
Data Federation
byStephen Lahanas
 
IBM MQ Advanced - IBM InterConnect 2016
byLeif Davidsen
 
MQ What's New Beyond V8 - V8003 level
byMarkTaylorIBM
 
InterConnect 2016: What's new in IBM MQ
byDavid Ware
 
MQ Security Overview
byMarkTaylorIBM
 
WMQ Toolbox: 20 Scripts, One-liners, & Utilities for UNIX & Windows
byT.Rob Wyatt
 
WebSphere Connectivity & Integration: What's New in the Messaging Family?
byIBM Sverige
 
InterConnect 2016, OpenJPA and EclipseLink Usage Scenarios (PEJ-5303)
byKevin Sutter
 
Big Data: InterConnect 2016 Session on Getting Started with Big Data Analytics
byCynthia Saracco
 
DevOps & Continuous Test for IIB and IBM MQ
byStuart Feasey
 
IBM InterConnect 2016: Security for DevOps in an Enterprise
bySanjeev Sharma
 

Similar to IBM MQ - Comparing Distributed and z/OS platforms

PDF
What's new in MQ 9.1.* on z/OS
byMatt Leming
 
PPT
WebSphere MQ introduction
byMikhailVladimirov
 
PDF
Websphere MQ (MQSeries) fundamentals
byBiju Nair
 
PDF
IBM MQ Appliance - Administration simplified
byAnthony Beardsmore
 
PDF
HHM-3481: IBM MQ for z/OS: Enhancing Application and Messaging Connectivity ...
byMatt Leming
 
PPTX
Where is my MQ message on z/OS?
byMatt Leming
 
PPTX
IBM MQ Whats new - up to 9.3.4.pptx
byMatt Leming
 
PPTX
What's new with MQ on z/OS 9.3 and 9.3.1
byMatt Leming
 
PDF
533-MigratingYourMQIApplicationsToJMS.pdf
byMatt Leming
 
PDF
MQ Guide France - What's new in ibm mq 9.1.4
byRobert Parker
 
PDF
What's new in MQ 9.1 on z/OS
byMatt Leming
 
PDF
On MQ Series & JMS
byAshokkumar T A
 
PPTX
Hhm 3479 mq clustering and shared queues for high availability
byPete Siddall
 
ODP
IBM WebSphere MQ for z/OS - The Inside Story
byDamon Cross
 
PDF
IBM IMPACT 2014 - AMC-1882 Building a Scalable & Continuously Available IBM M...
byPeter Broadhurst
 
PDF
3450 - Writing and optimising applications for performance in a hybrid messag...
byTimothy McCormick
 
PDF
IBM What's New in MQ V8
byIBM Systems UKI
 
PDF
IBM IMPACT 2014 AMC-1866 Introduction to IBM Messaging Capabilities
byPeter Broadhurst
 
PDF
HHM 6894 Messaging APIs for Cloud, Enterprise and Digital Applications
bymatthew1001
 
PDF
IBM IMPACT 2014 - AMC-1883 - Where's My Message - Analyze IBM WebSphere MQ Re...
byPeter Broadhurst
 
What's new in MQ 9.1.* on z/OS
byMatt Leming
 
WebSphere MQ introduction
byMikhailVladimirov
 
Websphere MQ (MQSeries) fundamentals
byBiju Nair
 
IBM MQ Appliance - Administration simplified
byAnthony Beardsmore
 
HHM-3481: IBM MQ for z/OS: Enhancing Application and Messaging Connectivity ...
byMatt Leming
 
Where is my MQ message on z/OS?
byMatt Leming
 
IBM MQ Whats new - up to 9.3.4.pptx
byMatt Leming
 
What's new with MQ on z/OS 9.3 and 9.3.1
byMatt Leming
 
533-MigratingYourMQIApplicationsToJMS.pdf
byMatt Leming
 
MQ Guide France - What's new in ibm mq 9.1.4
byRobert Parker
 
What's new in MQ 9.1 on z/OS
byMatt Leming
 
On MQ Series & JMS
byAshokkumar T A
 
Hhm 3479 mq clustering and shared queues for high availability
byPete Siddall
 
IBM WebSphere MQ for z/OS - The Inside Story
byDamon Cross
 
IBM IMPACT 2014 - AMC-1882 Building a Scalable & Continuously Available IBM M...
byPeter Broadhurst
 
3450 - Writing and optimising applications for performance in a hybrid messag...
byTimothy McCormick
 
IBM What's New in MQ V8
byIBM Systems UKI
 
IBM IMPACT 2014 AMC-1866 Introduction to IBM Messaging Capabilities
byPeter Broadhurst
 
HHM 6894 Messaging APIs for Cloud, Enterprise and Digital Applications
bymatthew1001
 
IBM IMPACT 2014 - AMC-1883 - Where's My Message - Analyze IBM WebSphere MQ Re...
byPeter Broadhurst
 

Recently uploaded

PPTX
Choosing Your Web3 Architecture: L1 vs L2 vs Appchain
bystorygamemarketing
 
PDF
DSD-INT 2025 MODFLOW 6 Developments - Langevin
byDeltares
 
PDF
HTML 5 CSS 3 DEVELOPMENT TECHNOLOGY.pdf
bydavidjohansen1597
 
PPTX
Why Airline Platforms Fail at Change and How Etihad Fixed It
byIT IDOL Technologies
 
PDF
DSD-INT 2025 Modelling cold water infiltration with the Groundwater Energy (G...
byDeltares
 
PPTX
Managing Multiple Projects from One ERP Dashboard - by biCanvas ERP
bybiCanvasERP
 
PPTX
A practical and beginner-friendly guide to understanding data structures in J...
bynaingseihahs
 
PDF
DSD-INT 2025 Coupled modeling in Ribasim - Linking Water Availability and Qua...
byDeltares
 
PDF
AI Development Services: MVP to Production Guide
byShiv Technolabs Pvt. Ltd.
 
PDF
Oracle AI Database 26ai _ AI-Native Database for Enterprises.pdf
byAstuteBusiness
 
PDF
DSD-INT 2025 The National Hydrological Model of Denmark and its enhancements ...
byDeltares
 
PDF
End-to-End Web & Mobile App Development Roadmap for Modern Businesses.pdf
byNaestinn
 
PDF
Software Development Company in India.pdf
byitswssoftware
 
PDF
Job Interview for Global Federal Government MD Panel Presentation
byafnupe09
 
PPTX
Image to Text converts images into editable text - AI Image to Text
byAI Image to Text
 
PDF
apidays Paris 2025 | AI and APIs - Ensuring Platform Migration Reliability wi...
byapidays
 
PDF
erp software for trading business in india.pdf
byZipERP
 
PDF
AI Concepts - MCP Neurons
byPhilip Schwarz
 
PDF
Dues Collection Software Intelligent Revenue Management.pdf
byCollege Pro
 
PPTX
Publix Data Scraping for Grocery Prices & Store Analysis.pptx
byMobile App Scraping
 
Choosing Your Web3 Architecture: L1 vs L2 vs Appchain
bystorygamemarketing
 
DSD-INT 2025 MODFLOW 6 Developments - Langevin
byDeltares
 
HTML 5 CSS 3 DEVELOPMENT TECHNOLOGY.pdf
bydavidjohansen1597
 
Why Airline Platforms Fail at Change and How Etihad Fixed It
byIT IDOL Technologies
 
DSD-INT 2025 Modelling cold water infiltration with the Groundwater Energy (G...
byDeltares
 
Managing Multiple Projects from One ERP Dashboard - by biCanvas ERP
bybiCanvasERP
 
A practical and beginner-friendly guide to understanding data structures in J...
bynaingseihahs
 
DSD-INT 2025 Coupled modeling in Ribasim - Linking Water Availability and Qua...
byDeltares
 
AI Development Services: MVP to Production Guide
byShiv Technolabs Pvt. Ltd.
 
Oracle AI Database 26ai _ AI-Native Database for Enterprises.pdf
byAstuteBusiness
 
DSD-INT 2025 The National Hydrological Model of Denmark and its enhancements ...
byDeltares
 
End-to-End Web & Mobile App Development Roadmap for Modern Businesses.pdf
byNaestinn
 
Software Development Company in India.pdf
byitswssoftware
 
Job Interview for Global Federal Government MD Panel Presentation
byafnupe09
 
Image to Text converts images into editable text - AI Image to Text
byAI Image to Text
 
apidays Paris 2025 | AI and APIs - Ensuring Platform Migration Reliability wi...
byapidays
 
erp software for trading business in india.pdf
byZipERP
 
AI Concepts - MCP Neurons
byPhilip Schwarz
 
Dues Collection Software Intelligent Revenue Management.pdf
byCollege Pro
 
Publix Data Scraping for Grocery Prices & Store Analysis.pptx
byMobile App Scraping
 

IBM MQ - Comparing Distributed and z/OS platforms

  • 1.
    © 2015 IBMCorporation 2291: Are z/OS & distributed MQ platforms like oil and water? Mark Taylor Lyn Elkins
  • 2.
    Introduction • One objectiveof MQ is isolating apps from needing to understand platforms ‒ There is a common API that can be expressed in many languages • Another objective is to have (reasonably) common operational model ‒ Much of admin is the same on all platforms • But it’s not all the same ‒ One dichotomy has always been whether to be natural to MQ-ness or behave like other things on the platform ‒ Some features don’t make sense on some platforms  For example, .Net interface is only on Windows ‒ Some features have not been implemented everywhere for other reasons • So there are differences, and that is what this presentation will cover • Will base this on V8
  • 3.
    Code Streams • Thereare essentially two implementations of MQ from Hursley lab ‒ z/OS ‒ Distributed (Windows, Unix, Linux, i) ‒ There are some further subspecies variants like VSE or NSS • Within Distributed implementation, there are some platform unique features ‒ But we won’t discuss those here ‒ Most platform-unique code abstracts OS facilities like locking or NLS or threads • In the early days, some code was written for one and then “ported” ‒ In particular, the channel code ‒ Meant double-fixing, and re-porting for each release • Internal architecture (eg tasks, threads) very different ‒ But we won't discuss much of that. Understanding externals is more important • Since V7.0, some code is truly common ‒ Just one copy of the source part shared between both ‒ New features generally use common code where feasible
  • 4.
    Sections • Setting up •Application Programming • Administration
  • 5.
    How this presentationworks • Lyn will talk about z/OS in this color • Mark will talk about Distributed in this colour
  • 6.
  • 7.
    Getting started • Lotsof differences in initial installation and setup • Getting the code on the box is part of the job ‒ MQ uses native installation techniques for all platforms ‒ Needs a suitably-authorised person to do that installation  SMPE for z/OS, installp for AIX, rpm for Linux etc • But other differences primarily due to ‒ Security ‒ Storage • Share philosophy of needing no more features than is found on the system ‒ So no prereq software for core capabilities of MQ ‒ Product ships components that are needed such as gskit ‒ But can exploit things that we know are there  For example, on z/OS we use the system-provided SSL ‒ Some extended capabilities may have additional prereqs  Shared Queues need DB2
  • 8.
    Security • On Distributed,MQ implements its own authorisation mechanism ‒ There is no generally-accepted standard interface on these systems • And relies on the existence of certain userids ‒ There are differences even between individual platforms • On z/OS, MQ exploits the common authorization interface, SAF ‒ And so the z/OS security administrator has to be involved ‒ Define the profiles etc. • Will look more at security later on
  • 9.
    Storage (Distributed) • OnDistributed, MQ uses directories such as /var/mqm/qmgrs and /var/mqm/logs ‒ The system administrator will probably allocate filesystems and mount them ‒ These days, may have separate SAN administrator • Each queue has its own file within the filesystem ‒ To store the message data ‒ Each queue could hold 1TB • Queues do not interfere with each other's storage requirements ‒ Subject to max size of filesystem • Logs can be LINEAR or CIRCULAR ‒ Choice made when qmgr is created ‒ With linear logging, you then need a job to remove old log files ‒ MQ does not directly implement dual-logging; relies on RAID filesystems
  • 10.
    Storage (z/OS) • Queuesare handled via pagesets and bufferpools • Multiple queues may use the same pageset and bufferpool ‒ Can lead to storage contention ‒ V8 increases number of bufferpools to match number of pagesets • No direct equivalent of circular logging but constraints can be applied to achieve a similar effect ‒ Semi-circular? ‒ Active logs are ‘almost like circular’, with offloading to archive logs • Logs are managed via the BSDS • MQ understands and implements Dual Logging • Tool provided to format and extract messages from log
  • 11.
    Shared Queues • Az/OS-unique feature ‒ Multiple queue managers can see the same queue ‒ Continuous processing of messages from a queue even when one LPAR fails • Relies on the Coupling Facility hardware ‒ And relies on DB2 Data Sharing • Results in several unique possibilities ‒ Inter-qmgr communication without standard channels ‒ Dynamic selection of which qmgr to connect to • Effects appear in many places ‒ For example, single MQSC command can be issued to multiple queue managers giving multiple responses
  • 12.
    Extra Features • MQV7.5 on Distributed incorporated MFT (nee FTE) and AMS ‒ "MQ Advanced" license covers all features • On z/OS, these are available as separate products ‒ V8 improved technical integration but still separate licenses • On z/OS, use of inbound client connections was restricted ‒ Restriction removed in V8 (no longer a CAF) • Distributed MQ has the MQXR service for mobile (MQTT) clients ‒ Not available on z/OS ‒ Expected that mobile clients connect via front-end qmgr before hitting z/OS apps
  • 13.
  • 14.
    General • Default codepagesand encoding differ by platform • Always use the header files for your platform ‒ Don't be tempted to cross-compile • Maximum lengths of fields may vary • MQI return codes may be different ‒ Often because underlying storage mechanisms have different error conditions ‒ For example, Coupling Facility errors on shared queues • z/OS does not have MQ clients ‒ Some parameters to some verbs only apply in client environments ‒ For example, the MQCD passed during MQCONNX
  • 15.
    API - Connections •MQCONN/MQCONNX ‒ Verbs not required for CICS transactions  MQHC_DEF_HCONN can be used for subsequent verbs in applications ‒ ConnTag is available to control serialization  An application (especially an MCA) can tell if another instance of itself is already running  On either the same local qmgr or any other in the QSG ‒ Group connection to QSG ‒ Lots of client-only options for connection  MQCD can be specified  Reconnect options ‒ MQCNO_SHARED options for multi-threaded applications  Controls whether an hConn can be (serially) used by other threads in the same process ‒ Fastpath binding ‒ Control of accounting  When accounting information is being collected, some apps may request exclusion
  • 16.
    API - Disconnections •MQDISC ‒ Always recommended ‒ Rollback when application abends  Although definition of "abend" is not clear in every case  CICS and IMS do make it clear!  A JVM has been known to return OK to the operating system even when the user's code has caused a fatal exception ‒ Rollback when not used and application ends
  • 17.
    API - Objects •MQOPEN ‒ Default dynamic queue names begin with CSQ.* or AMQ.* ‒ Distributed can open multiple queues simultaneously via Distribution List  Publish/Subscribe preferred cross-platform model • MQCLOSE ‒ No platform differerences in practice • MQSET ‒ Follows the same rules as MQSC attributes for platforms • MQINQ ‒ Follows the same rules as MQSC attributes for platforms
  • 18.
    API - Messages •MQPUT/MQPUT1 ‒ Messages can be automatically segmented  But Message groups are cross-platform ‒ Distributed supports "Reference messages" which can avoid putting large amounts of data on a queue • MQGET ‒ z/OS has "get with signal" to asyncronously notify app when messages appear  MQCB is now preferred cross-platform model ‒ z/OS has MARK_SKIP_BACKOUT for simpler processing of poison messages  Bad messages can be moved to an application-specific DLQ while backing out other resource changes ‒ Distributed can get portions of messages via segmentation • MQSUB ‒ No platform differences • MQSUBRQ ‒ No platform differences
  • 19.
    API – Flowcontrol • MQCB ‒ Definition of the callback function in MQCBD varies by environment ‒ eg C function pointer, CICS program name • MQCTL ‒ Not in IMS adapter ‒ On z/OS, apps must be authorized to use USS • MQSTAT ‒ Client applications only ‒ But usable regardless of server platform
  • 20.
    API - Properties •MQDLTMP • MQBUFMH • MQCRTMH • MQDLTMH • MQMHBUF • MQSETMP • MQINQMP • No platform differences
  • 21.
    API - Transactions •MQBEGIN ‒ Only available on Distributed ‒ z/OS always has a transaction manager available • MQCMIT ‒ On all platforms when not running under external TM • MQBACK ‒ On all platforms when not running under external TM • Default for MQ transactional behaviour is different ‒ MQI on Distributed assumes NO_SYNCPOINT ‒ MQI on z/OS assumes SYNCPOINT ‒ Always specify syncpoint options on MQI calls • Environments for two-phase transactions differ ‒ On z/OS, RRS CICS and IMS are all available for transaction management ‒ On Distributed, XA is available as the standard interface  And MQ can act as a transaction manager
  • 22.
    Exits • z/OS hasAPI-Crossing exit for CICS ‒ But no other environments • Distributed has API exit for all environments ‒ With a very different interface • Installable Services on Distributed ‒ But very few people write these so not too interesting ‒ Primarily used for the OAM security module • Channel send exit – ExitSpace field ‒ Used to reserve space in network transmission buffers for send exits ‒ Always zero on z/OS • No publish exit on z/OS • z/OS exits have MQXWAIT ‒ Necessary because process/thread model for channels is different
  • 23.
  • 24.
    Object Definitions • Attributesand ini files ‒ Some items are queue manager attributes on one platform but not other ‒ z/OS has lots related to its storage • Some unique object types ‒ z/OS has STGCLASS and CFSTRUCT ‒ Distributed has SERVICES and COMMINFO • Startup ‒ CSQZPARM is assembled/linked and other inputs run during startup  Reset configuration, define default objects etc ‒ On Distributed, standard objects are created by qmgr creation and updated during migration
  • 25.
    Object Attributes –Queue Manager • Apart from shared queue and storage-related attributes … ‒ Various events differ as shown in other charts ‒ Some z/OS attributes are in qm.ini for Distributed • z/OS only ‒ ACTCHL, MAXCHL ‒ ADOPTCHK/ADOPTMCA ‒ CHIDISPS, CHIADAPS ‒ DNSGROUP, DNSWLM ‒ EXPIRYINT ‒ GROUPUR ‒ IGQ, IGQAUT, IGQUSER ‒ LSTRTMR,LU62ARM, LU62CHL, OPORTMIN, OPORTMAX, RCVTMIN, RCVTTYPE, TCPNAME, TCPKEEP, TCPSTACK ‒ SCYCASE ‒ SSLTASKS ‒ TRAXSTR, TRAXTBL • Distributed only ‒ ACCTCONO, ACCTINT, ACCTMQI, ACCTQ ‒ ACTIVREC ‒ CCSID ‒ CERTVPOL ‒ CHAD ‒ SCHINIT, SCMDSERV
  • 26.
    Object Attributes –Queues and Channels • Apart from shared queue and storage-related attributes … • Queue ‒ DEFTYPE(SHAREDYN) z/OS ‒ HARDENBO only effective on z/OS ‒ INDXTYPE z/OS ‒ DISTL Distributed ‒ NPMCLASS Distributed ‒ SCOPE Distributed only, but obsolete ‒ STATQ Distributed ‒ TriggerData for transmission queues can be blank on Distributed, names channel on z/OS • Channel ‒ CONNAME 48 characters on z/OS, 264 elsewhere ‒ Format of exit names and exit data is platform-specific ‒ STATCHL Distributed only before V8
  • 27.
    Queue Manager operations •Message Expiry ‒ z/OS has explicit config for timing of task to remove expired messages ‒ Distributed has a similar task but no documented configuration • Security Cache Scavenger ‒ z/OS has parameters to control authority cache lifetime ‒ No equivalent on Distributed; use REFRESH SECURITY explicit command • Storage Scavengers ‒ z/OS has tasks to release bufferpool and pageset storage ‒ Distributed will release queue file storage at intervals • Queue Indexing ‒ z/OS has explicit indexes on queues to assist with retrieval patterns ‒ Distributed has hashing to perform similar role but no documented configuration
  • 28.
    Intercommunication and Clusters •Channels are the same • Clustering is essentially the same across all platforms • MQ 7.5 introduced concept of multiple cluster transmission queues ‒ Made common in V8
  • 29.
    Security (1) • Authenticationfeature added in V8 ‒ Distributed supports userid validation in operating system and explicit LDAP ‒ z/OS supports userid validation in operating system ‒ Both support LDAP when transparently used by OS • SSL/TLS configuration ‒ Distributed (mostly) qmgr uses gskit toolkit ‒ z/OS qmgr uses System SSL ‒ Can lead to discrepancies in crypto algorithms supported ‒ Different versions support different algorithms ‒ And there may also be client-related discrepancies  Java programs rely on JSSE implementations  .Net programs (from V8) can use Microsoft inbuilt implementations  NSS client uses OpenSSL ‒ There is a good common overlap between all of these, but not identical sets
  • 30.
    Security (2) –Access Control • z/OS ‒ Uses system-provided interface for authorization  SAF is common API to RACF, Top Secret, ACF2 ‒ Has to work with the 4 permissions available in SAF ‒ No distinction between PUT and GET  Often alias queues are used to isolate permissions ‒ Granular control of "impersonation" (setting context, alt-user) ‒ One operation may result in several authorization queries • Distributed ‒ MQ-provided authorisation interface  Implemented in the OAM ‒ Many permissions on objects ‒ Global controls on impersonation  If you have authority to use alt-user, there are no constraints on which user ‒ Well-known "mqm" id for full authority
  • 31.
    Commands • Basic OS-levelcommands are different ‒ Create, start, stop, delete queue manager procedures ‒ Distributed has command-line interface ‒ z/OS has JCL • Issuing configuration commands like ALTER QLOCAL ‒ Distributed has runmqsc shell ‒ z/OS has ISPF panels for most commands ‒ And the +cpf commands for runmqsc equivalence ‒ MQ Explorer is product-provided common GUI • Common programming interface (PCF) for configuration commands ‒ z/OS requires an "extended" format which may have multiple sets of responses  Supporting a Queue Sharing Group environment ‒ Distributed supports the same format but not the default ‒ Differences are hidden in the Java PCF classes
  • 32.
    MQSC Commands • Somecommands not available in all platforms ‒ Apart from those related to OS-specific features • RESET QSTATS is only on z/OS ‒ PCF available on all platforms • ARCHIVE LOG is only on z/OS ‒ even though Distributed also have logs • DISPLAY SYSTEM • MOVE QLOCAL ‒ V8 has dmpmqmsg • DISPLAY QMSTATUS ‒ Some items have z/OS specific commands like DISPLAY CMDSERV • STOP CONN only on Distributed ‒ All platforms have STOP CHL to kill client connections • Some z/OS MQSC have command-line equivalents on Distributed ‒ STOP QMGR == endmqm
  • 33.
    • DISPLAY CONN/QSTATUS ‒App name shows up on distributed; CHIN on z/os (though SMF does include it) • DISPLAY QMSTATUS not available
  • 34.
    Monitoring • Many queuemanager event messages are common ‒ For example, queue full • But not every event is on every platform ‒ Authorisation, Logging, and Channel auto-definition events are Distributed only ‒ IMS Bridge events are only on z/OS • Recording queue manager and application activity is very different ‒ z/OS has SMF 115 and 116 records ‒ Distributed has accounting, statistics and application activity events • Distributed accounting and stats events are analogous to SMF 116 ‒ No equivalent to 115 records
  • 35.
  • 36.
    Problem Determination • OnDistributed, there are several places to look for PD information ‒ Error logs written to /var/mqm/errors and /var/mqm/qmgrs/<qmgr>/errors ‒ FFST written to /var/mqm/errors for serious errors ‒ Trace provided by MQ commands and written to /var/mqm/trace • On z/OS, also numerous places to follow the clues: ‒ The MSTR and CHIN JES log  Should always be the first place to look ‒ MQ API trace (aka user parameter trace) – a GTF trace ‒ SMF 115 statistical information ‒ SMF 116 class(3) accounting (task related) data ‒ A dump for serious problems
  • 37.
    Backup • MAKEDEF anddmpmqcfg are tools to backup configuration ‒ With V8, have dmpmqmsg (CSQUMSG ??) to backup messages • On Distributed, backup of log files is done by stopping qmgr and copying /var/mqm/log directory ‒ rcdmqing takes images of queues into logs • On z/OS, full and fuzzy backups of pagesets are supported • CFSTRUCT backup required for QSG ‒ takes image of shared queue into logs
  • 38.
    High Availability andDisaster Recovery • Shared queues on z/OS for continuous processing • On Distributed, MQ provides multi-instance ‒ Not on z/OS because ARM is provided • Cross-site DR will usually use disk replication for any platform
  • 39.
    Summary • Title asksabout oil and water • Perhaps (olive) oil and (balsamic) vinegar is better description ‒ Blending together
  • 40.
    Notices and Disclaimers Copyright© 2015 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.
  • 41.
    Notices and Disclaimers(con’t) 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 herein 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, Bluemix, Blueworks Live, CICS, Clearcase, DOORS®, Enterprise Document Management System™, Global Business Services ®, Global Technology Services ®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, SoDA, SPSS, StoredIQ, Tivoli®, Trusteer®, 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.
  • 42.
    Thank You Your Feedbackis Important! Access the InterConnect 2015 Conference CONNECT Attendee Portal to complete your session surveys from your smartphone, laptop or conference kiosk.