CICS @ 45 #1913 - Integrate mobile applications and events into your end-to-end business process “CICS in your sights” Catherine Moxey, IBM STSM [email protected] © 2014 IBM.
Download ReportTranscript CICS @ 45 #1913 - Integrate mobile applications and events into your end-to-end business process “CICS in your sights” Catherine Moxey, IBM STSM [email protected] © 2014 IBM.
CICS @ 45 #1913 - Integrate mobile applications and events into your end-to-end business process “CICS in your sights” Catherine Moxey, IBM STSM [email protected] © 2014 IBM Corporation Please Note IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. 1 Session Abstract Want to see what is happening in the business and the CICS systems on mobile devices? Want to quickly enable business leaders to get more insight into their applications? This session covers facilities in CICS Transaction Server that allow users to capture information about the applications and CICS systems that run their business, and use that information to more effectively control them. Learn how to capture interesting events from applications and systems, and emit the events to consumers such as IBM Worklight for delivery to mobile devices and IBM Operational Decision Manager for advanced processing. Discover how to generate events when application tasks exceed policies that are specified for their resource usage, and how the CICS tools can help users manage and define events and resources. 2 What we’re going to cover Mobile and events Introduction to events and CICS event support Some scenarios Event specification demo CICS event support details A few advanced topics Performance considerations Resources, Summary, Q&A 3 Mobile into CICS (some of the options) WebSphere Application Server SOAP Web services CICS SOAP Web services or JSON JSON z COBOL, PL/I, C/C++, Java Services JSON CICS TG JSON See also: ACI-1411: Angry Birds & Half Words - Mobile & the Mainframe ACI-1675: Architecting an Application for Mobile Workloads ACI-1474: Integrating CICS with IBM Worklight to Deliver Modern Mobile Applications that Extend Business ACI-2374: The Modern Mainframe Is Mobile Ready ACI-1476: Managing Mobile Workload Being Serviced by CICS 009: Securing Mobile Access to CICS .. and more 4 What about CICS to mobile? Would you like to: Receive an SMS when the stock trade file is open for business? Notify your mobile dashboard whenever an application uses any 24-bit user storage? Reduce mobile workload driven by repeated balance inquiries, by pushing notification of balance updates to customers? Send claim details to the other party’s mobile device when an insurance claim is initiated? Trigger authorization request to a sales manager’s mobile dashboard when an order is placed for > 50 high value items? Automatically send an email or PDF receipt to a customer when an order is processed Have a means of delivering analytic data requested by the business without incurring long development cycles? 5 CICS Events to Mobile System z CICS Transaction Server zLinux Worklight Server CICS application Adapter CICS Events 6 Why use CICS events? And what are they anyway? © 2014 IBM Corporation The power of events ■ Principle of Decoupling • Producer of an event does not depend on a particular processing or course of action being taken by an event consumer • Event consumer does not depend on processing performed by the producer other than the production of the event itself. • Facilitates reuse; leads to a more flexible approach to building applications ■ Reasons for using events • Some applications are naturally centered on events: sensors detect events, application analyzes and reacts to these events • Observe, identify & react to certain situations (good or bad) as they occur • Extend an existing application in a flexible, non-invasive manner • Intermediary event processing logic can be separated out, allowing applications to be adapted quickly to meet new business requirements, sometimes by business users • Potential scalability and fault tolerance benefits from using eventdriven approach 8 CICS Events: Visibility, Compliance, and Business Flexibility CICS TS Application is unchanged Stock Trade Events Stock Trading Application (as an example) Monitor Processing Detect patterns of behaviour CICS Events help you to • Observe business processes • Recognize suspicious activity • Drive new processing 9 Notifications and Insight Further processing Example CICS event workflow LoB Manager Application Analyst Identify Events required by the business Specify Business actions to be taken when events occur Identify how to capture the events; Define Event Specifications Deploy Events and EP adapters (to emit events to consumers) Systems Programmer Existing Application Event modeling and tooling Event Binding Editor in CICS Explorer or RDz Event Consumer CICS Event Processing Support Business Dashboard CICS TS 10 Catherine’s Hierarchy of Events e Data access events Data input events e SIGNAL EVENT Program initialization events “Soup” of uninteresting events Policy events Resource state change events e e Maxtask events Application Events Message Events System Events (or IT events) Business Events 11 What can CICS events tell you about? About the business applications and their processing Business activity Business changes Application progress • Application events About the systems that run the business System and resource changes • System events • Message events (a specialised type of system event) Task behaviour • Policy events 12 What can you do with just CICS? Experiment and check that you are capturing the right events, with the right data and formatting • Write to a temporary storage queue • (Bear in mind TS queues can fill up) Extend an application without changing it • Start a CICS transaction, passing it event data – in the same or another region Send an email containing data captured from CICS • SupportPac CA1Y provides an SMTP client to send emails and attachments from CICS events Emit events with a custom format, e.g. to third party event consumer • Write a custom EP adapter, gives you full flexibility • Simple sample provided with CICS • Additional samples in SupportPacs 13 What can you do if you add other products? ODM Decision Server Events Development & Deployment Tooling CICS Event Processing Existing Business Logic Captured Events Events Code NOT changed Event Capture Filtering Enrichment Formatting Routing IBM Business Monitor Transports such as WebSphere MQ, or HTTP Cognos Real-Time Monitoring Extensible Captured CICS system processing Events Secured Monitored etc. CICS Transaction Server for z/OS 14 Other Event Consumers, including CICS What could I do with CICS events? © 2014 IBM Corporation Some examples of uses for events Populate business dashboards Comply with compliance and governance requirements Customize promotional offers Monitor and improve warehouse efficiency Get notification if key files fail to open at CICS startup Fraud detection • Send text message when fraud occurs • Use events to optimize fraud checking • See also ACI-1992: From OLTP to OLTAP - Real-time Fraud Detection for CICS Payments Processing Events to drive BigData and Analytics 16 Populate Business Dashboard Take events from CICS to populate a business operations dashboard. Non-invasive nature of setting up event emission means that changes can be made quickly and with confidence, with minimal disruption to the production and test systems. 17 Governance and compliance Comply with corporate, industry or government policies • Example: Italy’s data protection authority (Garante per la protezione dei dati personali) introduced requirements for the circulation of information in banking and tracking of banking operations in May 2011, which had to be actioned by December 2013 • Includes mandatory requirements to track details of transactions, preserve a log of them and issue alerts for suspicious or malicious access and for investigations Italian banks using CICS events to capture transaction details and save as audit logs http://www.garanteprivacy.it • Non-invasive events allow support of the requirements without application change, while use of SIGNAL EVENT involves minor change but full flexibility in gathering the tracking data • Functional and workload tests showed that the banks’ initial requirements were met in terms of the increase in consumption of application transactions and their isolation in the event of problems with the tracking system 18 Customize promotional offers All customer purchase transactions at tills are processed in the CICS back end Generating events from each purchase can provide information on what sells well to which customers (especially if enriched with location and demographic data by ODM event processing) ODM can also be used to set business rules about what items are on offer, enabling real-time tweaking of the offers to optimize sales. 1 Customer Deposit and Withdrawal Transactions from CICS Transactions Internet Banking 6 Measure success of promotions 5 IBM Business Monitor CICS TS Customer/RM SMS ATM/Branch Action s WebSphere MQ 2 ODM Decision Server Events Process Customer Deposit and Withdrawal Events and identify event patterns 3Collect Customer’s profile ODM ILOG JRules Customer Profile 19 SMS System Operational Decision Management 4 Determine appropriate customer promotion Monitor and Improve Warehouse Efficiency CICS TS EP Adapter Warehousing Application Emits events to WebSphere MQ Dashboard 20 File open at startup using system events Emit events if any files that ought to be opened during startup fail to open FILE Enable Status system event • • Context filter TRANSID = CSFU (the transaction which opens files at CICS startup) TO_ENABLESTATUS = UNENABLED (the state a file is put into if open fails) Display as alert on IBM Business Monitor dashboard 21 Events for fraud detection Send text message when fraud occurs • Automatically create and send text-message notifications in case of fraudulent ATM activity • Using CICS Explorer, a systems programmer can define, install and manage events from a centralized location without having to adjust applications, files or data associated with the ATM application itself 22 Events for fraud detection Optimize fraud checking • A business checks some proportion of requests for fraud, using business rules to decide which ones to check in more detail • The proportion that get detailed checking has to be set such that when the system is heavily loaded, the problem is not compounded by lengthy fraud checking • Using system events – emitted when going above or back below certain % MXT – adjust the business rules depending on system load • Enables an overall increase in the amount of detection • Warning: Don’t assume there won’t also be some stringent checking during heavily loaded times! 23 Events for BigData and Analytics Growing use of events from CICS to provide data for analytics Provides access to the large amounts of data within CICS to enable analytics 24 Let’s create some events… (1) Customer 1’s car “makes contact with” customer 2’s car The scenario (2) Customer 2 starts a claim on their car policy using their mobile, specifying customer 1’s details (3) Customer 1 gets notified on their mobile about the claim, with the claimant’s details CA0D: IBM GENAPP mobile application sample for CICS TS CB12: GENAPP, a General Insurance Application 26 Capture some events 33 Capture some events 34 Emit the events via an EP Adapter (This example uses a transaction start EP adapter) 35 What happened? CICS PA can tell you 36 Run that past me again… What event do we want? What interesting occurrence do we want to know about? • An event when a motor insurance claim is started What data is needed in the event? • • • • • Time it happened Customer number Policy number Policy details Claim details Event specification • Business event name • Description • Emitted Business Information ES 38 How can these events be captured from the claim processing application? What is the best point of capture in the application? • When the claims database is updated? X Cannot capture events when CICS accesses DB2 →CICS does not have visibility of enough of the data to control the capture with any degree of granularity (not even to the table level, if cursors are used!) • When the customer file is read Capture Specification • Business event name • Capture point • Filter (predicates) • Information Sources √ Can capture events from EXEC CICS READ FILE X But none of the claim information is passed on the command • On linking to the claim processing program √ Can capture events from EXEC CICS LINK √ The data required is passed in a channel on the LINK Tip: CICS IA can help with this process 39 ES CS Where to capture events? CICS IA to the rescue… Drive the event wizard from CICS IA 40 How to Capture the data and emit the event? How can we capture the data needed? • Information sources • Import from language structure • Might need to iterate back to choosing the capture point Any other related events we need? • Include in the same event binding if so Event Binding • Event Specifications • Capture Specs • UserTag How should the events be emitted? • Over what transport? • In what format? • Adapter configuration & event dispatching information ES ES CS CS EP Adapter (Adapter type & config) Event dispatch details 41 Components of CICS Event Specifications Event specification • Business event name Capture Specification • Description • Business event name • Event Specification(s) • Capture Spec(s) • UserTag • Filter (predicates) • Information Sources • Adapter configuration & event dispatching information ES Event Specification ES ES ES ES ES CS ECS CS CS CS Event Binding Event Specification associated with Event Capture Spec(s) 42 EP Adapter CICS Bundle resource • Emitted Business Information • Capture point Event Binding Where can events be captured? Event-enabled API call • Non-invasive Program initialisation • Non-invasive Explicit EXEC CICS SIGNAL EVENT call • Small program change required System event points • Non-invasive 43 Using CICS IA and SIGNAL EVENT to drive an event for EXEC SQL SELECT 1) Identify the program 2) Add in an EXEC CICS SIGNAL GET-CUSTOMER-INFO. EXEC CICS SIGNAL EVENT('SELECTCUSTOMER') END-EXEC. EXEC SQL SELECT FIRSTNAME, LASTNAME, DATEOFBIRTH, HOUSENAME, 3) Recapture CICS IA data and drive the event wizard 44 Application Event opportunities Channels and containers Web support • PUT CONTAINER, • START (TRANSID) • INVOKE WEBSERVICE • WEB READ, WEB READNEXT Files Input data • WRITE, REWRITE, DELETE • READ, READNEXT, READPREV Interval control • RECEIVE MAP • SEND MAP • SEND TEXT • START, RETRIEVE Terminal interactions Program execution • CONVERSE, RECEIVE, SEND • LINK, RETURN, XCTL • INVOKE SERVICE Output data • WRITE OPERATOR Scheduling • START (ATTACH) Program initiation Temporary Storage • Enable event when program starts • WRITEQ TS, READQ TS, DELETEQ TS Explicit capture point Transient Data • SIGNAL EVENT • No action unless enabled in event capture spec • WRITEQ TD, READQ TD, DELETEQ TD 45 How can events be emitted? EP Adapter CICS TS EP Adapter Interface Existing Business Logic (unchanged) EXEC CICS command & data match capture spec Event capture, filtering, enrichment ‘HTTP’ EP Adapter Event CICS Event sent to one or more of System change matches capture spec CBE ‘WebSphere MQ’ EP Adapter CICS Event Processing Event Format CEI CFE WBE ODM Decision Server Events WBE XML IBM Business Monitor CBER CBE ‘Transaction Start’ EP Adapter CBE consumers: IBM Business Monitor, Cognos BI, … CCE Other CBE consumers CICS Tran Event ‘TS queue’ EP Adapter CICS Event Binding Editor Tooling: create & deploy Event Binding (and EPAdapter) Custom EP Adapter 46 CFE WBE CBER CBE Any format CICS TS Queue Anywhere Other sources of events in CICS CICSPlex SM Real Time Analysis Threshold Policies • Introduced in CICS TS V5.1, extended in V5.2 • Action can be to emit an event 47 Events from policies 48 Threshold Policy Events Threshold policies • Control and manage resource usage • Policy rule defines the action to be taken when tasks (within the policy scope) exceed a specified threshold usage of a particular resource • The action can be to emit an event via a specified EP adapter CICS system events indicate that something interesting has happened in the CICS system • Threshold policies specify a “predefined” system event which indicates that usage of a resource has exceeded a certain threshold • Event action causes an event to be emitted in exactly the same way as other system events – Events that are generated from threshold policies can drive other processing, or be sent to other event consumers See also ACI-1961: No Rainclouds Here - Using CICS Platform & Policies to Keep a Private Cloud Healthy 49 Events through the releases CICS TS V4.1 Application events captured non-invasively from a subset of the CICS API and on program initiation SIGNAL EVENT application programming command Event bindings, containing event specifications, event capture specifications, and EP adapters Event Binding Editor in the CICS Explorer for creating and manipulating event bindings Supplied EP adapters to emit events to TS queues, WebSphere MQ queues and CICS transactions SPI commands and CICS Explorer views for event bindings and capture specifications CICS TS V4.2 System events captured from a subset of state changes that can occur in the system Assured event emission with new synchronous event emission mode Separate EP adapter resource: independent of event bindings (embedded EP adapters still supported) HTTP EP adapter to emit events to HTTP servers (also on V4.1 with APAR PK94205) EP Search capability to help identify potential effect of application changes on capture specs Extended SPI and CICS Explorer views to provide more detail about capture specs and EP adapters Support for capturing data in other data types, including floating point and COBOL zoned data types Enhancements to TS queue EP adapter to emit events to TS queues in XML formats Relaxed restrictions on events from CICS facilities (Atom, MQ DPL Bridge) Event capture global user exit, XEPCAP, for dependency analysis tooling Custom EP adapter interface config passed in character container for easier code page conversion CICS TS V5.1 Message event capture point to capture events when (most of the) CICS messages are issued New application capture point for WRITE OPERATOR New capture points when threshold policy rules are exceeded Define static data in event specs to be included in captured and emitted event data EP Adapter Set resource to route one event to multiple consumers CICS TS V5.2 Enable events from LINKs using mirror (also on V5.1 with APAR PM78624) Additional threshold policies 50 Getting more advanced Custom EP adapters What if not all the data you want is available at the chosen capture point? • Select a better capture point • Code SIGNAL EVENT – Invasive, requires application change – Tip: include any data you think you might ever want • Write a custom EP adapter to enrich the events with additional data – Might require synchronous emission • Submit an RFE – If you believe the data could be exposed by CICS for capture 52 Synchronous emission and other Advanced Options 53 Events for Audit Logging (Italian regulatory example) CICS Events are used to set up the Audit infrastructure to collect audit records • Non-invasive instrumentation of audit events used where context and application data can be captured without modify the existing programs – SEND/RECEIVE Maps, EXEC CICS LINK programs, ECI programs • SIGNAL EVENT API inside generalized Audit Log Module to re-use the same infrastructure to manage and send audit records – Where application data not present on the CICS API commands Capture points for audit • Capture point for CICS BMS (Send/Receive) • Capture point for programs invoked through CICS TG via ECI calls 54 Audit Events and Custom EP Adapter ECI Calls from CICS TG CICS TS V4 CICS Event Dispatcher DFHMIRS EXEC CICS LINK Custom EP Adapter (Sync emission) CP Transaction EXEC CICS LINK CP 3270 interface Program … …. …. Event Message Payload ……… SELECT INFO record 0001 ……… … … .. AuditEventQueue Batch Program With thanks to Giancarlo Rochester, IBM Executive IT Specialist Get WMQ Message Write Audit Log Payload Consumer Audit Log 55 Message Events DFHFC0407 applid This CICS system is now authorized for shared access to data tables owned by the CICS system with applid applid2. DFHLD0505 date time applid Details for LIBRARY libname, ranking: ranking, critical status: {Critical | Noncritical}, enablement status: {Enabled | Disabled}. DFHSJ0915 date time applid userid JVMSERVER jvmserver is now enabled and is ready for use. 56 LIBRARY message event DFHLD0505 I 04/09/2014 09:20:52 IYCWZCGO Details for LIBRARY GENLOAD, ranking: 50, critical status: Noncritical, enablement status: Enabled. 57 Events to multiple consumers CICS 3270 Transaction LNKORDAU Web Browser PLACE ORDER (EXEC CICS LINK) AUTHORIZE ORDER Inquire and Update Orders TSq Mobile REST JSON Interfaces Insert order Into Orders TSq Event captured when Qty>50 for Authorization ? (a) Push Notification to Worklight Server (b) Update TS queue Order TSq Order Authorizations TSq 58 Events to multiple consumers CICS 3270 Transaction LNKORDAU Web Browser PLACE ORDER (EXEC CICS LINK) AUTHORIZE ORDER Inquire and Update Orders TSq Mobile REST JSON Interfaces Insert order Into Orders TSq Event captured when Qty>50 for Authorization EP Adapter Set HTTP EP adapter TSq EP adapter (a) Push Notification to Worklight Server (b) Update TS queue Order TSq Order Authorizations TSq 59 Events to multiple consumers: EP Adapter Set 60 What if I change an application? What happens to the events? EP Search can help. . . 61 EP Search results 62 Search in the definitions as well as installed resources 63 CICS IA can help too – CICS IA captures event data Resources used by transaction SSC1 Which other programs emit this event ? 64 CICS and IBM Business Monitor Integration IBM Business Monitor on CICS Transaction Server V4 5 Common Event Infrastructure 6a CICSApplications Applications CICS WebSphere MQ Event Specifications Was Application Server Event Processing Event Processing Adapters Adapters CBE CBE CBE Event XML Event EventXML XML CEIQueue CBE Filters and Distributes Events Monitor Server CBE 7 CBER over HTTP 6b 4 CICS Event Binding Editor Deploy monitor model to Monitor server 8 2 1 Export Schemas for Event Specifications 3 Monitor Toolkit IBM Confidential 65 Monitor Dashboard CICS and ODM Decision Server Events Integration IBM Operational Decision Manager Decision Server Events CICS Transaction Server V4 5 CICS CICS Applications Applications Event Specifications Event Processing 6 WebSphere MQ ODM Decision Server Events Runtime CBE CBE Event XML WBE Event XML Event XML EP Adapters Adapters WBE Message Queue Connector CICS Event Binding Editor WebSphere MQ via e.g. WAS platform messaging 4 1 2 3 ODM Event Designer Tool 67 ODM Decision Center Tooling Monitoring with Cognos Real-time Monitoring Export Schemas for Event Specifications Cognos Real-time Monitoring Event Binding Editor IBM Mashup Center DB2 CICS V4 VSAM CICS Dynamic Scripting Bundle Event Binding Application WebSphere MQ WMQ EP adapter CEI Queue CBE Event 69 So, what is it going to cost me? CICS Event performance measurements Hardware and software used (unless otherwise specified) Hardware • z196 2817-779 model M80 – LPAR with 5 dedicated CPs – Separate LPAR for network drivers – Best fit for scaling CP speeds – LSPR 2817-705 – DASD DS8800 – Internal Coupling Facility with ICP links Software • z/OS V1.12 • CICS TS V4.2 Results for CICS TS V4.1 and V5.1 are similar (for equal functionality) but less comprehensive 72 Application Event CPU costs EP component EP Adapter CPU microsecs CPU extra comments EP started 0 overhead of having EP started Filter +0.01 cost of a single data filter operation Capture + Emit WebSphere MQ +68 +4 QMGR WebSphere MQ cost with non-persistent queue HTTP +102 +6 TCPIP cross LPAR TCPIP costs Transaction Start +79 transaction just reads passed containers TS Queue +46 main TS queue TSQ (recov) +116 recoverable aux TS queue Custom +51 no emission, just reads containers Example: Emitting to WebSphere MQ non-persistent queue with 100 data filters in capture specification: CICS CPU overhead (100*0.01)+68=69 microsecs WebSphere MQ CPU overhead=4 microsecs 73 Application Events summary Filtering costs • Generally low CPU overhead (fractions of microseconds) – especially if the EQ filter operator is used Event Capture and Emission costs • 46 to 116 microseconds of CPU to capture and emit an event – depending on EP adapter used Assured emission has some additional overheads for the capturing transaction 75 CPU ms per user trans Application events example (measured at V4.1) 1.2 1 0.8 0.6 0.4 0.2 0 EP user task T1 0.1% T2 1% T3 3% T4 6% CPU % increase shown 76 T5 12% Application events predicate workload - CPU usage • That file is NOT specified in any of the capture specifications – full search is needed for each capture spec. and no capture or emission occurs 100 capture specifications with: • • • • CPU utilisation % 1,000 READs to same file Different FILE filter values (not the one actually accessed) Test #1 with Event Processing STOPPED Test #2 with filterOperator=“EQ” (exact match – primary predicate) Test #3 with filterOperator=“SW” (“starts with” – generic) 90 80 70 60 50 40 30 20 10 0 0 50 100 150 200 # Tasks / second no filtering 100 "EQ" 100 "SW" Running with an equal match on a primary predicate gives very little overhead compared with having no event processing active at all; there is more overhead associated with less specific predicate tests 78 250 System Events – Max Tasks capture point No overhead in having System Events enabled Test #1 MAXTASKS=10 and EP stopped Test #2 MAXTASKS=10 with MAXTASKS System Events enabled • • Event captured when current # tasks goes higher than 60% of MAXTASKS Generated a 2.8% capture rate Transaction Start EP adapter used - this overhead is included in the CPU costs CPU utilisation % 35 30 25 20 15 10 5 0 2000 3000 4000 5000 6000 # Tasks / second 2.8% captured EP stopped • MAXTASKS event, with a 2.8% capture rate results in an overall 3 microsecond increase in CPU per user task (including the emission cost of a Transaction Start EP adapter) • TRANCLASS event, with a 2% capture rate results in an overall 2 microsecond increase in CPU per user task (including emission cost of Transaction Start EP adapter) 81 Resources, Summary and Questions Some resources http://www.redbooks.ibm.com/abstracts/REDP4642.html?Open : Conceptual Model for Event Processing Systems http://www.redbooks.ibm.com/abstracts/sg247815.html : Smarter Banking with CICS http://www-03.ibm.com/software/products/en/category/operational-decisionmanagement : Operational Decision Management (including ODM for Dummies e-book) http://www-03.ibm.com/software/products/en/category/business-monitoring : Business Monitoring http://www.redbooks.ibm.com/abstracts/sg247792.html : Event Processing with CICS (*completely updated August 2013*) http://www-01.ibm.com/support/docview.wss?uid=swg24033197 : SupportPac CA1Y: Send email from CICS Transaction Server for z/OS 83 CICS Events Summary Unlock the information in your CICS applications and systems using CICS events Integrate CICS events with mobile applications • To provide alerts, drive mobile traffic as push-rather-than-poll, gain additional insight Emit events without application change and with minimal system overhead Useful value with CICS, plus additional capability with other products • Especially IBM ODM, Worklight, Business Monitor Events captured from application processing, system activity, threshold policies Use events to populate business dashboards, comply with governance requirements, customize promotional offers, drive analytics, and more… On CICS TS V4.1 or later? – Start experimenting now! 84 Real users speaking about CICS… 1317: You’ve got a friend in IBM System z, tales from CICS TG Mon: 17.15, Delfino 4005 3116: Making it easy for mainframe Apps to be clients in an SOA. Tues: 14.00, Delfino 4005 3070: CICS TG and CICS in a high-availability environment Tues: 14.15, Delfino 4005 3071 Dynamic WLM of CICS web services Tues: 10.30, Delfino 4005 2880: Tales from the trenches Weds: 15.45, Delfino 4005 3072 CPSM Optimized Workload Routing Weds: 14.15, Delfino 4005 3073: z/OS & CICS Consolidation project Weds: 13.00, Delfino 4005 2436: Modernizing the mainframe Thurs: 10.30, Delfino 4005 1966: Best practices for CICS SOA Connectivity Weds: 13.00, Delfino 4102 Hope you managed to catch some of them! If not, download their presentations 85 Follow us… ibmcics @ibm_cics ibmcics CICS Hursley CICS Hursley CICSbuzz ibm.com/cics/news Visit us at… System z Software Solutions Suite Toscana 3609 Monday 11:00 – 18:00 Tuesday & Wednesday 8:00 – 18:00 Thursday 8:00 – 16:00 Book your appointment at ibm.biz/zsolsuite Plus Lunch & Learns 12:00 – 13:00 daily – book a slot! System z Peds Infrastructure Matters zone of the EXPO Monday 10:00 – 19:30 Tuesday 10:00 – 19:30 Wednesday 10:00 – 14:30 Pop by for a chat about CICS! Lost? Dazed and confused about CICS or z at Impact? Visit the zConcierge - System z Software Solutions Suite - Toscana 3609 86 Generation z [noun] those with under 10 years experience on the mainframe Meet us: No sales pitches, no marketing, just drinks with other Generation z’s 19:30 Wednesday April 30 Public House, The Venetian Get the lowdown on what’s going on Follow us: @ibmgenz Join us: Build a community of like-minded people System z Stack Exchange 87 Win a CICS Workshop! Collecting CICS session stickers for your entry? Don’t forget to pick one up before you go! 88 We Value Your Feedback Don’t forget to submit your Impact session and speaker feedback! Your feedback is very important to us – we use it to continually improve the conference. Use the Conference Mobile App or the online Agenda Builder to quickly submit your survey • Navigate to “Surveys” to see a view of surveys for sessions you’ve attended 90 Thank You Legal Disclaimer • © IBM Corporation 2014. All Rights Reserved. • The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. • References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. • If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. • If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. • Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. • If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. • If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. • If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. • If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. • If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. • If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. • If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only. 92