Your SlideShare is downloading. ×
0
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
What's New in IMS OTMA and IMS Connect
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

What's New in IMS OTMA and IMS Connect

741

Published on

From IMS RUG meeting in Toronto and New York City, September 2012. Presented by Dave Cameron (Toronto) and Deepak Kohli (NYC)

From IMS RUG meeting in Toronto and New York City, September 2012. Presented by Dave Cameron (Toronto) and Deepak Kohli (NYC)

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
741
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. What’s New in OTMA and IMS ConnectIMS Regional User GroupToronto, Sept 11, 2012David Cameron, SVL OTMA Developerdaveac@ca.ibm.com © 2012 IBM Corporation
  • 2. Agenda• OTMA Resource Monitoring• OTMA /DISPLAY Commands• Sync Callout Response – SendOnly with ACK• IMS Connect – Ping enhancement – RACF Return Codes – Enhance Port Edit Exit – SOAP Gateway support enhancements – Inbound MFS Modname © 2012 IBM Corporation
  • 3. OTMA Resource Monitoring• OTMA monitors various resources and reports their health to the OTMA clients (IMS Connect, MQSeries, etc) – Resources states: available, warning, severe – Resources monitored: YTIBs (messages), TPIPEs, AWEs• OTMA uses TMAMMNTR x’3C’ protocol messages – Initial client-bid with current status – When monitored resources change status – Heartbeat every 60 seconds• IMS Connect keeps status in XIBDS – Displayed on VIEWDS command output – Available to User Message Exits for Datastore routing – Event 45 for changes (heartbeat just updates XIBDS timestamp) © 2012 IBM Corporation
  • 4. OTMA Message Flood Monitoring• Message flood (YTIB) protection limits the number of messages IMS stores in CTL RGN storage – Flood can cause IMS to crash – Member default is 5000, Global default is 8000• Change values: 1. INPT parameter on Member descriptor in DFSYDTx PROCLIB 2. IMS Type 1 command /START TMEMBER xxx INPUT nnnn /START TMEMBER ALL INPUT nnnn• Values: – 0 inactivates monitoring – 200-9999 are valid (less = 200, more = 9999) © 2012 IBM Corporation
  • 5. OTMA Message Flood Monitoring (cont’d)• At 80% of Member flood limitDFS1988W OTMA input messages from member yyyyyyyy have reached xx% of the maximum active input message limit zzzz – x’3C’ warning protocol message sent to client – DFS1988W for every 5% increase• At 100% of Member flood limitDFS1989E OTMA input messages from member yyyyyyyy have reached the maximum active input message limit zzzz – x’3C’ severe protocol message sent to client – New messages rejected with OTMA NAK x’30’ – MQSeries issues CSQ2003E and queues messages until flood relieved © 2012 IBM Corporation
  • 6. OTMA Message Flood Monitoring (cont’d)• At 100% of Global flood limitDFS4388W THE TOTAL OTMA SEND-THEN-COMMIT (CM1)CONTROL BLOCKS(TIB) HAS REACHED OR EXCEEDED WARNING LIMIT OF nnn – x’3C’ warning protocol message sent to client – New input not rejected• When Global flood is relievedDFS0793I THE TOTAL OTMA SEND-THEN-COMMIT(CM1) CONTROL BLOCKS (TIB) HAS DECREASED BELOW nnn – x’3C’ available protocol message sent to client © 2012 IBM Corporation
  • 7. OTMA TPIPE Monitoring• TPIPE represents a destination for a TMEMBER• Dynamically built when referenced and cleaned up when inactive – Idle across 3 IMS checkpoints – No messages queued and no status – Not MQSeries SYNC TPIPE (uses sequence numbers)• MAXTP parameter on Member descriptor in DFSYDTx PROCLIB member – No command support © 2012 IBM Corporation
  • 8. OTMA TPIPE Monitoring (cont’d)• Member TPIPE monitoring – 80% Warning – DFS4382W and x’3C’ warning protocol message – 100% Error – DFS4383W and x’3C’ warning protocol message • Reject new TPIPE requests NAK x’29’ • Still process requests for existing TPIPEs – 50% Relieved – DFS3484I and x’3C’ available protocol message• Global TPIPE monitoring – Highest of TMEMBER MAXTP used for global limit – 100% Error – DFS4385W and x’3C’ warning protocol message • Still create TPIPEs if Member not max – 80% Relieved – DFS4386I and x’3C’ available protocol message• Shared Queues BE – When MAXTP limit, get U0367 abend and stop transaction © 2012 IBM Corporation
  • 9. OTMA TPIPE Monitoring (cont’d)• IMS V11 PM71035 (open) – New DFS3323E message passed from BE when MAXTP • No U0367 and transaction not stopped – New MAXTPBE parameter on Member descriptor • Can allow BE to create TPIPE for FE transaction even if at MAXTP – New DFSOTMA system Member descriptor • Can explicitly set Global MAXTP – If not used, revert to highest Member MAXTP for Global limit • 80% Warning – DFS4515W and x’3C’ warning protocol message • 100% Error – DFS4516E and x’3C’ warning protocol message – Still accept requests for existing TPIPEs • 50% Relieved – DFS4517I and x’3C’ available protocol message – /DIS OTMA and /DIS TMEMBER • Now show MAXTP limit and actual TPIPE counts © 2012 IBM Corporation
  • 10. OTMA /DISPLAY Commands• OTMA still has only IMS Type 1 /DISPLAY commands – Exception is OTMADESC Type 2 commands for Destination Descriptors• /DIS OTMA and /DIS TMEM TPIPE – All new function reported in displays (eg Sync Callout, MAXTP)• IMS V12 PM46829 (part of MQSeries Trx Expiration SPE) – /DIS TMEMBER TPIPE allowed “ALL” or list of TPIPEs – Added support for masked name /DIS TMEM xxx TPIPE tpipenm* {SYNC | QCNT} © 2012 IBM Corporation
  • 11. OTMA /DISPLAY Commands - Examples/DIS OTMA (V12)DFS000I GROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEMDFS000I DRUEXIT T/O TPCNT ACEEAGEDFS000I XCFGRP1DFS000I -IMS1 ACTIVE SERVER NONE 0 8000DFS000I -IMS1 N/A 0 5000DFS000I -HWS1 ACTIVE ACCEPT TRAFFIC NONE 0 4000DFS000I -HWS1 HWSYDRU0 5 5 999999DFS000I -VC7 ACTIVE ACCEPT TRAFFIC NONE 0 5000DFS000I -VC7 DFSYDRU0 120 0 999999/DIS TMEM HWS1 TPIPE CLIENT*DFS000I MEMBER/TPIPE ENQCT DEQCT QCT INPCT STATUS SMEMDFS000I HWS1DFS000I -CLIENT03 7 4 3 4DFS000I -CLIENT02 3 2 1 2DFS000I -CLIENT04 3 3 0 3DFS000I -CLIENT01 1 1 0 1 © 2012 IBM Corporation
  • 12. Sync Callout Response – SendOnly with ACK• Sync Callout Response – ICAL waiting in IMS dependent region for response – Callout server processes request and sends response – Response using SendOnly protocol • No indication of delivery • Ok for inquiry but not for updates – Response can be sent using SendOnly with ACK • Callout server receives indication of delivery – ACK if response successfully delivered to ICAL – NAK/RSM if not able to deliver response » Reason code indicates problem (eg ICAL timeout, Datastore closed, etc) • Not full Distributed 2PC – Will impact performance of Callout server with extra flow • No impact to ICAL response • Minimize server impact using separate response threads © 2012 IBM Corporation
  • 13. Sync Callout Response – SendOnly with ACK IMS V12 PM39562 & PM39569 © 2012 IBM Corporation
  • 14. IMS Connect – Ping Enhancement• Old Ping had problems: – Disconnect socket after reply even if persistent socket used – Ping would not set clientid when first request – Ping would not turn off “first message timer” when first request • Socket would still be closed if no subsequent request before TIMEOUT value• IMS V12 PM29137 – Ping as first request will set clientid and prevent socket timeout – Ping will not disconnect persistent socket – Ping response message for RYO now conforms to CSM message format – Also want PM45956 & PM57133 © 2012 IBM Corporation
  • 15. IMS Connect – RACF Return Codes• IMS Connect returns RSM RC=08 RSN=40 for security violations – No indication of specific reason eg. invalid userid, incorrect password, password expired, etc.• IMS V11 PM28489 – RACF Return Code from RACROUTE VERIFY passed back • RSM for RYO and SOAP Gateway – RSM_RACFRC • OTMA User Data for TMRA – OMUSR_RACF_RC – New IMS Connect Protocol level indicates support OMUSR_PROLEV = OMUSR_PR03 © 2012 IBM Corporation
  • 16. IMS Connect – Port Edit Exit Enhancement• Port Edit Exit – Allows access to messages between TCP/IP and IMS Connect – Specified on TCPIP statement of HWSCFGxx member • PORT=(ID=port#,KEEPAV=nnnn,EDIT=exitname)• IMS V11 PM46328, IMS V12 PM48548 – Have separate input and output buffers so Exit doesn’t have to “edit in place” – Support an amount to increase size for output buffer • Done on INIT call similar to User Message Exits – Exit has control over first 32 bytes • Allows Exit full edit of message contents• Note: input message must still start with fullword length © 2012 IBM Corporation
  • 17. IMS Connect – IMS SOAP Gateway• IMS V11 PM39865 – Support converts for SOAP fault messages – Allow specification of maximum language segment size for the converter • ADAPTER statement in HWSCFGxx member MAXLSSSZ={32767|value}• IMS V12 PM64487 – IMS Connect can load up to 100 different XML Converters • Least recently used – MAXCVRT added to ADAPTER statement in HWSCFGxx member • Values from 100 to 2000• IMS V12 PM69983 (open) – Provide end-to-end tracking identifier for IMS SOAP Gateway – Follow flow from SOAP Gateway through IMS Connect and IMS and back out © 2012 IBM Corporation
  • 18. IMS Connect – Input MFS Modname• IMS V11 PM70116 – IMS OTMA does not support MFS – IMS Connect can return MFS Modname for output • Input transaction specifies IRM_F1_MFSREQ • Output response contains RMM segment with Modname • Can indicate to external client the format of response data – Same requirement for input transaction • Although MFS not used, input Modname can indicate data format to IMS app • IRM has IRM_MODNAME field that was added for IRM_ARCH3 • Can modify User Message Exit to populate OMHDRMAP/TMAMHMAP © 2012 IBM Corporation

×