IMS Connect Extensions

Size: px

Start display at page:

Download "IMS Connect Extensions"

Lawrence Alexander
5 years ago
Views:

1 Connect Extensions Henry Kiesslich Fundi Software Pty Ltd. Date of presentation (01/11/2016) Session: HE

2 Working Title: Connect for Enterprise 2016 By Jim Martin Session Number: 19597

3 Learning Objectives Understanding the significance of Connect The evolution of typical Connect architectures Impact and challenges of growing workloads Strategies for addressing these challenges 3

4 Connect History ISC/MSC Open database (DRDA) ITRA Clients 1997 ITOC Get s a User s Guide 1998 Visual Age for Java Connecting to using Java ( e-business ) 2004 V9 Connect becomes an integrated component Admin Connect z/os Connect WebSphere TM Resource Adapter (from distributed) Support 2009 V11 Open Database 2011 Management Console Now z/os Connect Custom JAVA / C# API SOAP Gateway 4

5 Connect characteristics Lightweight Own address space Extensible: messages processed via user exits Simple to configure and set up Propriety IRM protocol (except for open database) 5

6 Profile of an Connect customer Gradual migration Incremental growth in use Experiences growth pains Application modernization Greenfield development Network modernization P.O.C Connect use 6

requirements: Greater scalability Higher availability Improved security Cost containment: consistency, fewer

7 Connect Growing pains Clients coded to an inflexible topology Consolidation versus redundancy Operations and maintenance challenges Cost of down time Performance limits Workload type changing Increasing customization needs With pain comes requirements: Greater scalability Higher availability Improved security Cost containment: consistency, fewer customizations, greater flexibility Requirements must be met while minimizing the disruption to existing client code and existing client instances 7

8 Meeting the challenges Use routing to improve parallelism, add redundancy, and provide abstraction (insulation) to clients Consider additional security Centralize the management of client options Centralize operational management Use Connect instrumentation to tag the various workloads 8

9 How? Customizing exits Connect OTMA Message exits Open DB Routing & Security exits Instrumentation exits (HWSTECL) Use a tool Connect + Connect Extensions 9

10 User Story: Manage workload by attributes OTMA Messages Routing rules Original DestID, Transaction Code Connect Datastore A Datastore B Datastore C Fallback Datastores OTMA routing incudes the ability to qualify by transaction code as well as datastore Open Database routing support can qualify by the alias name or PSB Generic destinations Parallelism Optional fallback (flood or down) Open Database requests Routing rules Connect Alias A Alias B Alias C Run the Lab (remote) 10 Alias or PSB Fallback Aliases

11 Rules-based routing The simplest way to gain the benefits of Connect Extensions routing Create rules that, for a given DESTID, determine a primary and fallback collection of candidate datastores Connect Extensions will balance workload between the datastores in the primary collection If none of the datastores in the primary collection are available or if all datastores in that collection are in flood, then Connect Extensions spreads workload between the fallback collection Works for transactional messages, Send Only, Resume TPIPE, Synchronous callout, and Asynchronous callout Routing plans provide the ability to logically group routing rules and to dynamically swap between different plans. Benefits: improved performance, redundancy, better capacity management 11

destinations Switch from one plan to another with z/os Explorer plug-in

12 Workload User Story: Manage message distributions Connect DS1 ($) DS2 ($) DS3 ($$$) Capacity weights allow you to dynamically favour certain destinations Switch from one plan to another with z/os Explorer plug-in Or batch automation Run the Lab (remote) 12 0 Peak Off-peak Weekend

13 User Story: do not interrupt in-flight work 1. Active system used by three Connects 2. ICON 1 Datastore for A ICON 2 Datastore for A ICON 3 Datastore for A Drain initiated stopping new transactions to system. Workload is routed to other systems In-flight messages Drain in-flight work before shut down Coordinate manually using z/os Explorer Plugin Use commands and batch automation ICON 1 Datastore for A ICON 2 Datastore for A ICON 3 Datastore for A 3. When all activity has completed the system can be bought down safely ICON 1 Datastore for A ICON 2 Datastore for A ICON 3 Datastore for A 4. When the system is restarted, Connect Extensions automatically resumes routing workload to it.

User Story: limit IP address access Connect Extensions IP address whitelist TCP/IP Clients IP address blacklist Manage access to Connect systems based on the Connect system a client is connecting

14 User Story: limit IP address access Connect Extensions IP address whitelist TCP/IP Clients IP address blacklist Manage access to Connect systems based on the Connect system a client is connecting through and the IP address they are connecting from Security rules (RACF or other) can be used to produce whitelists Rules can be formed to produce blacklists that reject access from certain IP addresses or address ranges Access can be restricted further based on the Connect port being used by the client 14 Governance, not just security

15 User Story: redistribute persistent sessions 15 Persistent TCP/IP Clients plex Existing Connect (300 clients) Existing Connect + (300 Clients) New Connect (0 Clients) When an Connect system is restarted after maintenance, established persistent socket sessions on other Connect systems remain in place The newly started Connect is underutilized and the sysplex workload appears out of balance You might also want to drain persistent sessions

16 User Story: centralize management of client options Transaction options (expiration, IRM Timer values, client ID cancellation) Duration of persistent sessions Message translation between any code pages (such as EBCDIC <=> ASCII) Extended RSM feedback Fine tuning options by transaction Restrict client session life Changes are immediate 16

Use case: But now I want to automate it Master your operations with automation The Connect Extensions host command environment for REXX enables Connect Extensions commands to be embedded in REXX

17 Use case: But now I want to automate it Master your operations with automation The Connect Extensions host command environment for REXX enables Connect Extensions commands to be embedded in REXX programs, which allows more flexible automation of Connect operations. Programs can connect to multiple Connects Use REXX features such as variables and conditional logic Integrate with other host command environments (MVS, CONSOLE, TSO) Submit programs interactively as well as in batch Use the flexibility of REXX Single REXX to control multiple systems Integrate with other host command environments Automate routine operational activities working REXX samples 17

Connect Extensions Centralized monitoring and control P Eclipse or ISPF File Option Help ---------------------- _ Stop 1 link _ View TOKYO sessions _ Stop NY sessions F1 Help F2 - Scroll And REXX for

18 Connect Extensions Centralized monitoring and control P Eclipse or ISPF File Option Help _ Stop 1 link _ View TOKYO sessions _ Stop NY sessions F1 Help F2 - Scroll And REXX for Automation /* REXX */ address LINK "CEXRXENV INIT address CEX "CONNECT HOST=FTSD,", "PORT=13883,HWSID=HWS1, SWITCH TYPE=JOURNAL" address LINK "CEXRXENV TERM" Growing workloads mean more Connect instances 18

It s time to move beyond VIEWHWS VIEWHWS Output in system-specific joblogs Output is cluttered and fills spool Difficult to filter, search, sort, summarize and export Displays don t provide leads to

19 It s time to move beyond VIEWHWS VIEWHWS Output in system-specific joblogs Output is cluttered and fills spool Difficult to filter, search, sort, summarize and export Displays don t provide leads to command actions Connect Extensions Consolidated output from multiple systems Output is tabulated Built-in filtering and sorting Instant export to spreadsheet applications Context actions: perform commands directly against objects in table 19

20 Connect Extensions Centralized monitoring and control Eclipse or ISPF File Option Help _ Stop 1 link _ View TOKYO sessions _ Stop NY sessions F1 Help F2 - Scroll /* REXX */ address LINK "CEXRXENV INIT address CEX "CONNECT HOST=FTSD,", "PORT=13883,HWSID=HWS1, SWITCH TYPE=JOURNAL" address LINK "CEXRXENV TERM" Growing workloads mean more Connect instances 20

The Connect Extensions Status Monitor view provides you

Context actions against resource instances like drain, stop,

Sortable, searchable, and filterable sysplex view of

21 The Connect Extensions Status Monitor view provides you with: Tabbed views of each resource type. Context actions against resource instances like drain, stop, and start. Sortable, searchable, and filterable sysplex view of resources. Summarise, save, and export the session list as a CSV file. Auto-update highlighting any criteria. Many more session attributes.

22 Properties view The sessions view provides you with: Context actions to cancel sessions and get network status. Sortable, searchable, and filterable Sysplex view of sessions. Ability to summarize, save & export the session list as a CSV file. Auto-update highlighting any criteria. Many more session attributes.

23 User story: Management reporting Why now? Nature of the workload Historical summary Why focus on Connect (as opposed to or further upstream)? All web facing activity This may become the face of your company to your customers Long term trends more important 23

24 Response times over 2 seconds! "Application waits 2 seconds for a response from. Contact support." " responds in a millisecond." Application Support staff The problem is somewhere in here: a reporting "black hole" between the two product support teams support staff Distributed Application Connect ODBM Connect Extensions log Event journal 24 Tracks DRDA flow Problem Investigator Performance Analyzer Reports separate response times for Connect and

25 Response times over 2 seconds! "Application waits 2 seconds for a response from. Contact support." " responds in a millisecond." Application Support staff The problem is somewhere in here: a reporting "black hole" between the two product support teams support staff Distributed Application Connect ODBM Connect Extensions log Event journal 25 Tracks DRDA flow TAW Transaction Analysis Workbench Problem Investigator Performance Analyzer Reports separate response times for Connect and

26 Connect receives Open Database requests via TCP/IP Connect calls security and routing exits Connect forwards requests to ODBM Processes Open Database request Response returns to client via ODBM & Connect Connect receives next request from client DRDA conversation continues until PSB deallocated and socket closes BROWSE CEX000.QADATA.DEMO.LOG.ICON Record More: < > Command ===> Scroll ===> CSR Navigate < > Date/Time / Wednesday Time (Relative) 003C Prepare READ Socket READ Socket B DRDA 1041 EXCSAT-Exchange Server Attributes READ Socket B DRDA 106D ACCSEC-Access Security C DRDA 1443 EXCSATRD-Server Attributes Reply Data A WRITE Socket READ Socket B DRDA 106E SECCHK-Security Check ODBM Security Exit called ODBM Security Exit returned C DRDA 1219 SECCHKRM-Security Check Reply Message A WRITE Socket READ Socket B DRDA 2001 ACCRDB-Access RDB D ODBM begin Allocate PSB (APSB) Program=AUTPSB ODBM Routing Exit called ODBM Routing Exit returned AA ODBM Trace: Message sent to ODBM Message sent to ODBM BMP Scheduling start TranCode=ODBA02CD Region= E02 BMP Scheduling start Region= Application Start Program=AUTPSB11 Region= Start of UOR Program=AUTPSB11 Region= Start of protected UOW Region= E03 BMP Scheduling end TranCode=ODBA02CD Region= AA ODBM Trace: Message received from ODBM A Message received from ODBM E ODBM end Allocate PSB (APSB) Program=AUTPSB C DRDA 2201 ACCRDBRM-Access RDB Reply Message A WRITE Socket Trigger Event for ODBMMSG C Prepare READ Socket Sudden jumps in elapsed READ Socket B DRDA 200C OPNQRY-Open Query or relative times may READ Socket B DRDA CC05 DLIFUNC-DL/I function indicate problems READ Socket B DRDA CC01 INAIB-AIB data READ Socket B DRDA CC04 RTRVFLD-Field client wants to retrieve data READ Socket B DRDA CC06 SSALIST-List of segment search argument AA ODBM Trace: Message sent to ODBM Message sent to ODBM DLI GHU Database=AUTOLDB SC=' ' Elapse= E60 DLI Call start Region= E62 DLA00 start Database=AUTOLDB Region=0004 Func=GU E63 DLA00 end Region=0004 Seg=DEALER SC=' ' E61 DLI Call end Region= AA ODBM Trace: Message received from ODBM A Message received from ODBM Connect Extensions Journal Log Monitor Omegamon for ATF Other: DB2, SMF, MVS, CQS 2

27 Added recently into Connect Extensions V Operations Console eclipse plugin for IBM Explorer for z/os (or other shells). Connect Extensions host command environment for REXX Routing Plans Support for qualifying rules-based routing by transaction code Support for routing by alternate transaction code Pre-routing user exit for rules based routing Datastore Drain/Resume feature Session drain command New Session Message Limit option enables Automatic Session Rebalancing in session distribution environments Update commands OTMA Global Flood Warning support Support for V13 Support for dynamically added Connect ports Support for dynamically added Connect datastores ziip offload support

28 Conclusions Starting with Connect is easy but become complex over time Can be a victim of its own success Have a plan for how you will grow your workloads Understand that growth is not just more workload but more variety of workload Understand what changes impact clients that you cannot control Understand the big picture 28

29 Session feedback This is the last slide in the deck Please submit your feedback at Session is HE

C05: IMS Connect for Enterprise Workloads

C05: IMS Connect for Enterprise Workloads Rafael Avigad, Product Manager, Fundi Software Overview Introduction: IMS Connect, why it increasingly matters Evolution of typical IMS Connect architectures Impact