Your SlideShare is downloading. ×
What's New in OTMA and IMS Connect - IMS UG Mar 2012 Peoria
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

What's New in OTMA and IMS Connect - IMS UG Mar 2012 Peoria

1,454
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,454
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
47
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 ConnectSteve Nathansnathan@us.ibm.com © 2011 IBM Corporation
  • 2. Disclaimer Corporation [current year]. All rights reserved. © Copyright IBM U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, 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 PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION 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 ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE. IBM, the IBM logo, ibm.com, and IMS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml 2 2011 © 2011 IBM Corporation
  • 3. Agenda  Introduction  IMS 10+ – OTMA and IMS Connect – OTMA – IMS Connect  IMS 11 – OTMA and IMS Connect – OTMA – IMS Connect  IMS 11+ – OTMA  IMS Connect Extensions  IMS Enterprise Suite  IMS 12 3 2011 © 2011 IBM Corporation
  • 4. Introduction  There have been MANY enhancements in OTMA and IMS Connect – Some of these were added in IMS 10 via maintenance (10+) – Some of these were added in IMS 11 – Some of these were added in IMS 11 via maintenance (11+) – Some of these were announced for IMS 12 – Some of the these were enhancements to OTMA which also had enhancements in IMS Connect to take advantage of the OTMA enhancements – This presentation will cover all of these enhancements 4 2011 © 2011 IBM Corporation
  • 5. IMS 10 – OTMA Reminder  The following were OTMA enhancements for IMS 10 – Support /LOCK & /UNLOCK commands via OTMA – Routing descriptors for IMS Connect and NONOTMA – Resume TPIPE security – Message flood control – CM1 ACK timeout – Automatic TPIPE cleanup – TMEMBER level security – /DISPLAY enhancements – Supermember for Resume TPIPE – Reroute/Purge of undeliverable IOPCB output – OTMA=M and /STA OTMA NOCHECK 5 2011 © 2011 IBM Corporation
  • 6. IMS 10 – IMS Connect Reminder  The following were IMS Connect enhancements for IMS 10 – Specify ACEE aging value to OTMA – Change password – RACF mixed case password – Support OTMA message flood – Support OTMA CM1 ACK timeout – Resume TPIPE alternate Clientid – Resume TPIPE Port Affinity – XML Adapter 6 2011 © 2011 IBM Corporation
  • 7. IMS 10+ – OTMA and IMS Connect  Synchronous Callout – IMS supports synchronous callout from an IMS application using OTMA – Invoked with a new IMS call – ICAL – Application will issue the call and wait for a reply – First support is for IMS Connect – Implemented by OTMA APARs PK70078, PK71135, and PK73224 • Also PK75209 (IMS10) and PK85023 IMS 11) for issuing ICAL from IMS Java programs 7 2011 © 2011 IBM Corporation
  • 8. IMS 10+ – OTMA and IMS Connect  Synchronous Callout – The OTMA Client will do a Resume TPIPE specifying that it wants synchronous callout messages – OTMA sends the synchronous callout request to the OTMA Client when it is available – The OTMA Client must send an ACK (or NAK) for the request message – The OTMA Client will send the reply via a special Send-Only message – The OTMA Client is responsible for maintaining a correlation token 8 2011 © 2011 IBM Corporation
  • 9. IMS 10+ – OTMA and IMS Connect  Synchronous Callout – IMS Connect will support OTMA synchronous callout via APARs PK70330 and PK74168 • IMS TM Resource Adapter support is APAR PK75460 • IMS Connect Extensions support is APAR PK74985 • DFSUTR20 support is PM03084 • There are several other APARs – PM30898 is very important – The IMS Connect Client will do a Resume TPIPE specifying that it wants synchronous callout messages – The IMS Connect Client will send the reply via a Send-Only message 9 2011 © 2011 IBM Corporation
  • 10. IMS 10+ – OTMA and IMS Connect  Synchronous Callout – The IMS Connect Client is responsible for maintaining the correlation token • WAS/IMS TM Resource Adapter • IMS SOAP Gateway • Roll-Your-Own (RYO) Client – APARs PM20541 (IMS 10) and PM20543 (IMS 11) have IMS Connect notify OTMA if there is an error in the XML translation instead of just discarding the message • OTMA will notify the ICAL transaction immediately instead of waiting for the timeout 10 2011 © 2011 IBM Corporation
  • 11. IMS 10+ – OTMA and IMS Connect Synchronous Callout – The synchronous callout design is provided for IMS TM users • It does not provide support for BMP or JBP applications running in a DBCTL environment – OTMA Descriptors are required to define the target destination • Supermember is supported for availability and failover – Only the AIBTDLI call interface is supported • Supports messages larger than 32K without segmentation – The target of the synchronous callout could be any IMS Connect Client • WAS/IMS TM Resource adapter • IMS SOAP Gateway • Roll-Your-Own (RYO) client 11 2011 © 2011 IBM Corporation
  • 12. IMS 10+ – OTMA and IMS Connect  Synchronous Callout – The following will not be supported in the first phase of the synchronous callout support • Shared Queues with FE and BE are different systems • Two phase commit (distributed sync point) • IMS application will not be able to specify a password for authenticating the external server on a per request basis 12 2011 © 2011 IBM Corporation
  • 13. IMS 10+ – OTMA and IMS Connect WebSphere IMS Application Server EJB / IMS TM MDB Resource Adapter IMS Application 1 OTMA Descriptor 1 IMS Connect Roll-your-own IMS IMS Application 2 Application Connect OTMA Descriptor 2 OTMA IMS Application 3 Descriptor 3 IMSWeb Service SOAP Provider Gateway Send flow Receive flow 13 2011 © 2011 IBM Corporation
  • 14. IMS 10+ – OTMA and IMS Connect Synchronous Callout – The first thing to do is define and setup OTMA Descriptors for each synchronous callout destination – Use different TPIPEs for asynchronous output messages and synchronous callout messages – Use different TPIPEs for synchronous callout request messages for each client • IMS TM Resource Adapter clients • IMS SOAP Gateway clients • RYO application clients 14 2011 © 2011 IBM Corporation
  • 15. IMS 10+ – OTMA and IMS Connect Synchronous Callout – Use ‘D’ descriptor type in DFSYDTx – D destname keywords • destname is the destination name in the AIB – Keywords are • TYPE=IMSCON (only supported by ICON at this time) • TMEMBER=name • TPIPE=name • SMEM=YES|NO • ADAPTER=adapname • CONVERTR=convname • SYNTIMER=timeout 15 2011 © 2011 IBM Corporation
  • 16. IMS 10+ – OTMA and IMS Connect Synchronous Callout – The IMS application uses the AIBTDLI call for the synchronous request – CALL AIBTDLI USING ICAL, AIB, REQ-AREA, RESP-AREA. • ICAL is new call • AIB is an AIB control block – Synchronous callout is only supported by the AIB interface • REQ-AREA is the Request data area for synchronous callout • RESP-AREA is the Response data area for returned data 16 2011 © 2011 IBM Corporation
  • 17. IMS 10+ – OTMA and IMS Connect Synchronous Callout AIB – AIBSFUNC = SENDRECV – AIBRSNM1 = 8 byte OTMA Descriptor name – AIBRSFLD = Timeout value – AIBOALEN = Request area length • Input parameter: 4 byte field containing the length of the request area • Output parameter: Actual length of the response message • Updated by IMS only when partial data is returned – AIB return code x100, AIB reason code x00C‘ – AIBOAUSE = Response area length • Input parameter: 4 byte field contains the length of the response area • Output parameter: Length of the response message placed in the response area • When partial data is returned because the response area is not large enough, AIBOAUSE contains the length of data returned in the response area and AIBOALEN contains the actual length of the response message 17 2011 © 2011 IBM Corporation
  • 18. IMS 10+ – OTMA and IMS Connect IAPMDI27 JOHN DOE . RYO Application IMS Connect IMS Resume TPIPE IMS Application TPIPE 1 TPIPE1 TPIPE1 ICAL SENDRECV OTMDEST1 JOHN DOE Request 4 3 2 JOHN DOE 5 ACK Response 9 6 7 8 12345678 12345678 18 2011 © 2011 IBM Corporation
  • 19. IMS 10+ – OTMA and IMS Connect Synchronous Callout 1. IMS Connect Client issues Resume TPIPE 2. The IMS application issues the synchronous request using the ICAL call 3. OTMA breaks the message into 32K segments 4. IMS Connect combines the data and sends it to the IMS Connect Client including the Correlation Token 5. The IMS Connect Client must ACK or NAK the synchronous output message 6. The IMS Connect Client sends the synchronous response message as a “send-only” message 7. IMS Connect breaks the message into 32K pieces to send to OTMA via XCF 8. OTMA combines all of the data and returns it to the IMS application in the Response Area 9. The IMS application processes the synchronous response 19 2011 © 2011 IBM Corporation
  • 20. IMS 10+ – OTMA and IMS Connect  Synchronous Callout enhancements – IMS 10 – PM09695, PM09696, and PM14872 – IMS 11 – PM12142 and PM12172 – OTMA will send a new NAK (sense code x’2B’) when a late or invalid ACK is received for a callout message – If the reply message for sync callout is received BEFORE the ACK for the output message OTMA will wait for the ACK • Can be caused by XCF race condition – TPIPE cleanup will now clean-up unused ICAL TPIPEs after 3 checkpoints – Label NO_RSP changed to NO_COT for /DIS TMEMBER TPIPE SYNC • NO_COT = number of Synchronous Callout Messages 20 2011 © 2011 IBM Corporation
  • 21. IMS 10+ – OTMA and IMS Connect  Synchronous Callout – APARs PM20292 (IMS 10) and PM20293 (IMS 11) • New ICAL AIB AIBERRXT for why ICAL failed – Extended reason codes in addition to AIB return/reason codes • New DFS4688E message for an ICAL internal processing error – ICAL times out with an AIBERRXT extended reason code – X’67D0’ log record written to show error information – IMS 12 – PM39569 • Support Send-Only with ACK for a Synchronous Callout response 21 2011 © 2011 IBM Corporation
  • 22. IMS 10+ – OTMA and IMS Connect  Asynchronous Callout – When OTMA asynchronous output was sent via the OTMA ‘D’ type descriptors, OTMA was not setting the Port to “ICONNECT” • If IMS Connect was using PORTAFF=Y then IMS Connect would not find the IMS Connect Client to receive the message • Fixed with PM35619 (IMS 10), PM39450 (IMS 11), and PM39451 (IMS 12) 22 2011 © 2011 IBM Corporation
  • 23. IMS 10+ – OTMA and IMS Connect  Queued Resume TPIPE Requests – If a Resume TPIPE was sent in for a TPIPE that was already processing a Resume TPIPE the second Resume TPIPE would be ignored – With PK80756 OTMA will now queue the Resume TPIPE – It will receive messages if the first Resume TPIPE is cancelled  This enhancement is for availability – It allows another OTMA Resume TPIPE client to immediately receive asynchronous output or sync callout output if the current Resume TPIPE client fails 23 2011 © 2011 IBM Corporation
  • 24. IMS 10+ – OTMA and IMS Connect  Transaction Expiration – Distributed applications may timeout transactions • Not under IMS control – IMS still processes the transaction • No one is interested in the output – This uses unnecessary resources • Network resources • CPU / storage / IO • Dependent region occupancy 24 2011 © 2011 IBM Corporation
  • 25. IMS 10+ – OTMA and IMS Connect  Transaction Expiration – Input message expiration = input message timeout • Allows OTMA input messages to expire and be deleted prior to processing • OTMA input messages can specify a timeout value in the OTMA header in one of two ways – An expiration STCK time • Used by IMS Connect – An elapsed time value • Used by Websphere MQ (7.0.1 and 7.1) • Implemented via PK74017 (IMS 10) and PK74024 (IMS Connect 10) • Implemented via IMS TM Resource Adapter with PM01727 (IMS 10) and PM01822 (IMS 11) – A new transExpiration property is added to the interactionSpec class 25 2011 © 2011 IBM Corporation
  • 26. IMS 10+ – OTMA and IMS Connect  Transaction Expiration – Transaction level input message timeout for OTMA and non-OTMA messages was introduced in IMS 11 – Specified on: • TRANSACT macro – EXPRTIME parameter • DFSINSX0 - Destination Creation User Exit • CREATE/UPDATE TRAN/TRANDESC DRD commands 26 2011 © 2011 IBM Corporation
  • 27. IMS 10+ – OTMA and IMS Connect  Transaction Expiration – IMS Connect Clients using sample exits set x’01’ on in flag IRM_F1 • IRM_F1_TRNEXP • RYO exits will have their own method – IMS Connect User Message Exit sets flag OMHDRXP1 (x’01’) on in flag OMHDRIST – IMS Connect calculates the transaction expiry time based on the OTMA timeout value for the message • You can not explicitly specify the expiration time – IMS Connect passes a STCK Expiry time to OTMA 27 2011 © 2011 IBM Corporation
  • 28. IMS 10+ – OTMA and IMS Connect  Transaction Expiration – Input message expiration is checked three times • When the input message is first received – OTMA only – Expiry  NAK x’34’ • When the input message is enqueued to the transaction – OTMA only – Expiry  NAK x’34’ • GU IOPCB – OTMA and non-OTMA (IMS 11) – Expiry  pseudoabend U0243 & DFS555I/DFS2224I  DFS3688I • An x’67D0’ log record is written for all expirations 28 2011 © 2011 IBM Corporation
  • 29. IMS 10+ – OTMA and IMS Connect  Transaction Expiration – APARs PM05985 (IMS 10) and PM05984 (IMS 11) will add new support for transaction expiration • Dump for ABENDU0243 at GU timeout will be optional – TODUMP=YES/NO in OTMA descriptor • Send message DFS3688I instead of DFS555I/DFS2224I – DFS3688I TRANSACTION xxxxxxxx EXPIRED: ELAPSE=yyyyyyyy TPIPE=zzzzzzzz TMEMBER=aaaaaaaaaaaaaaaa • Option to return input message instead of DFS3688I • The last two items help MQSeries to support Transaction Expiration 29 2011 © 2011 IBM Corporation
  • 30. IMS 10+ – OTMA and IMS Connect  Resume TPIPE No Message Notification –TMAMCRHQ_NOAUTO – x’00’ • OTMA will send all the messages that are on the Asynchronous output queue one at a time and then will stop when the queue is empty – It will take another Resume TPIPE to get more messages • If there are no messages when the Resume TPIPE is issued nothing happens – The Resume TPIPE is ignored – there is no reply to the OTMA Client that there are no messages – but this is now fixed – PK80756 will send a protocol command indicating there are no more messages – IMS Connect (PK80758) will issue an immediate timeout to the IMS Connect Client 30 2011 © 2011 IBM Corporation
  • 31. IMS 10+ – OTMA and IMS Connect  Resume TPIPE No Message Notification – TMAMCRHQ_ONE – x’01’ – OTMA will send one message from the Asynchronous output queue and then will stop • It will take another Resume TPIPE to get more messages – If there are no messages when the Resume TPIPE is issued nothing happens – The Resume TPIPE is ignored – there is no reply to the OTMA Client that there are no messages – but this is now fixed – PK80756 will send a protocol command indicating there are no more messages – IMS Connect (PK80758) will issue an immediate timeout to the IMS Connect Client 31 2011 © 2011 IBM Corporation
  • 32. IMS 10+ – OTMA and IMS Connect  Cancel Resume TPIPE – OTMA added a new command to allow an OTMA client to cancel a Resume TPIPE (PK80756) – Allows another queued Resume TPIPE to take over receiving asynchronous output messages for this TPIPE • Including Synchronous Callout messages – IMS Connect (PK80758) will send in this command when an IMS Connect Client waiting on a Resume TPIPE times out in IMS Connect or when ICON notices that a Client has disconnected – This also allows OTMA to clean up the TPIPE after 3 checkpoints if there is no Auto or Auto One Resume TPIPE waiting 32 2011 © 2011 IBM Corporation
  • 33. IMS 10+ – OTMA and IMS Connect  Resource Monitoring – OTMA currently provides flood protection when too many YTIB (unprocessed input message) control blocks are created for an OTMA Client • Message DFS1988W is issued as the TIB limit is approached • Message DFS1989E is issued when the TIB limit is reached – Input messages are rejected from that Client until the flood is relieved • Message DFS0767I is issued when the flood condition is relieved • There were requirements for the original implementation – The DFS messages were not written to the MTO so they could not be processed by automation – The OTMA clients were not informed 33 2011 © 2011 IBM Corporation
  • 34. IMS 10+ – OTMA and IMS Connect Resource Monitoring – APAR PK49317 (IMS 10) routes these DFS messages to the IMS MTO in addition to the current WTO – This APAR also adds a new message which can be monitored by automation – DFS2386I OTMA IS CONNECTING TO THE MEMBER xxxxxxxx 34 2011 © 2011 IBM Corporation
  • 35. IMS 10+ – OTMA and IMS Connect  Resource Monitoring – APARs PK70458 (OTMA 10) and PK70960 (ICON 10) introduce the start of “OTMA Degraded System Monitoring” • PK73670 is for IMS Connect Extensions support • OTMA sends x’3C’ protocol messages to OTMA clients – At Client Bid with initial status – Immediately when status changes • Stopped, Started, Flood Warn, Flood, Flood Relieved • Heartbeat once every 60 seconds • IMS Connect externalizes the OTMA status – Expanded XIBDS table for ICON User Message Exits – Event 45 issued when XIBDS status updated • Not for heartbeat – only the XIBDS timestamp is updated 35 2011 © 2011 IBM Corporation
  • 36. IMS 10+ – OTMA and IMS Connect  Resource Monitoring – Original HWSXIBDS HWSXIBDS DSECT Exit Interface Block Data Store entry XIBDS_NAME DS CL8 Data store name XIBDS_STATUS DS X Data store status XIBDS_INACTIVE EQU X00 Data store not active in ICON * OPENDS command is required XIBDS_ACTIVE EQU X01 Data store active in ICON * And IMS is active in XCF group XIBDS_DISC EQU X02 Data store disconnected * No OPENDS command is required XIBDS_FLAG DS X Data store entry flags XIBDS_LAST_ENTRY EQU X80 Last entry in list DS XL2 Reserved XIBDS_USER DS XL4 User field 36 2011 © 2011 IBM Corporation
  • 37. IMS 10+ – OTMA and IMS Connect  Resource Monitoring – Added to HWSXIBDS – Can be used for routing decisions * OTMA Status Section Follows @PK70960 XIBDS_ST_STATUS DS H Overall Status Code 3, 2, or 1 @PK70960 * 3 - Available for work @PK70960 * 2 - Warning, partly degraded @PK70960 * 1 - Severe, no work possible @PK70960 * 0 - N/A no status available @PK70960 XIBDS_ST_SVRSTT DS 0XL4 Unavailable resource info @PK70960 XIBDS_ST_SVRFLG1 DS X Group 1 unavail resources @PK70960 XIBDS_ST_SVRFLG2 DS X Group 2 unavail resources @PK70960 XIBDS_ST_SVRFLG3 DS X Group 3 unavail resources @PK70960 XIBDS_ST_SVRFLG4 DS X Group 4 unavail resources @PK70960 XIBDS_ST_S4FLOOD EQU X01 Member reaches 100% flood @PK70960 XIBDS_ST_WRNSTT DS 0XL4 Degraded resource info @PK70960 XIBDS_ST_WRNFLG1 DS X Group 1 degraded resources @PK70960 XIBDS_ST_W1FLOOD EQU X80 Global flood warning @PK70960 XIBDS_ST_WRNFLG2 DS X Group 2 degraded resources @PK70960 XIBDS_ST_WRNFLG3 DS X Group 3 degraded resources @PK70960 XIBDS_ST_WRNFLG4 DS X Group 4 degraded resources @PK70960 XIBDS_ST_W4FLOOD EQU X01 Member 80%+ flood @PK70960 XIBDS_ST_UTC DS CL12 UTC time for this status @PK70960 XIBDS_ST_LEN EQU *-XIBDS_ST_STATUS Length of OTMA Status @PK70960 * @PK70960 XIBDS_LEN EQU *-HWSXIBDS XIB data store entry length 37 2011 © 2011 IBM Corporation
  • 38. IMS 10+ – OTMA and Websphere MQ  Message Delivery Options – Expiry • A message can expire in MQSeries on the IMS Bridge Queue before being sent to IMS – The MQ application that MQPUT the message is notified if one of the following MQMD_REPORT options is set – MQRO_EXCEPTION (Just the Expiration report) – MQRO_EXCEPTION_WITH_DATA (First 100 bytes of the message) – MQRO_EXCEPTION_WITH_FULL_DATA (All of the message) 38 2011 © 2011 IBM Corporation
  • 39. IMS 10+ – OTMA and Websphere MQ  Message Delivery Options – Expiry • MQSeries 7.0.1 supports IMS Transaction Expiration • MQSeries passes the remaining Expiry time to IMS as an IMS Transaction Expiration time – This is rounded up to whole seconds – This requires OR’ing the MQ Service Parameter with x’00000000000001’ to activate this feature – ZPARM CSQ6SYSP SERVICE=0000000001 + any other bits being used – COMMAND SYSTEM SERVICE(0000000001) + any other bits being used 39 2011 © 2011 IBM Corporation
  • 40. IMS 10+ – OTMA and Websphere MQ  Message Delivery Options – Expiry • MQSeries 7.0.1 supports IMS Transaction Expiration • If the transaction expires in OTMA before being placed on the IMS message queue it is NAK’ed by IMS (NACK_FOR TRANS_EXPIRED, x’0034’) • MQSeries treats this as if the message had expired before being sent to IMS – MQMD_REPORT options are honored 40 2011 © 2011 IBM Corporation
  • 41. IMS 10+ – OTMA and Websphere MQ  Message Delivery Options – Expiry • MQSeries 7.0.1 supports IMS Transaction Expiration • If the transaction expires at the GU to the IOPCB – IMS returns message DFS3688I to MQSeries – The DFS3688I message is returned to the Reply_To Queue – The MQMD_REPORT options are NOT honored 41 2011 © 2011 IBM Corporation
  • 42. IMS 10+ – OTMA and Websphere MQ  Message Delivery Options – Expiry • MQSeries 7.1.0 enhances the support for IMS Transaction Expiration • Requires IMS APAR PM05984 • If the transaction expires at the GU to the IOPCB – OTMA returns the original input message to MQSeries instead of the DFS3688I message – The MQMD_REPORT options are honored – This enhanced functionality was retrofit to MQSeries 7.0.1 via APAR PM47795 42 2011 © 2011 IBM Corporation
  • 43. IMS 10+ – OTMA and Websphere MQ  Message Delivery Options – Expiry • The Reply message can also Expire – MQIIH_FLAGS has value MQIIH_PASS_EXPIRATION – MQSeries will pass the REMAINING expiry time in the OTMA header – The reply on the reply-to queue will start the Expiry process with that remaining time • Any time in IMS is NOT counted 43 2011 © 2011 IBM Corporation
  • 44. IMS 10+ – OTMA  Resource Monitoring – OTMA flood protection limits the number of YTIB control blocks – Having too many TPIPEs can also build up OTMA storage – APAR PK79048 allows the specification of a maximum number of TPIPEs per OTMA Client (TMEMBER) and for all of OTMA • Specified with the MAXTP parameter on the “M” (Member) control card in DFSYDTx • There is no command to set this value • Values can be from 200 to 99999 • The maximum limit for all of OTMA is the highest Member limit 44 2011 © 2011 IBM Corporation
  • 45. IMS 10+ – OTMA  Resource Monitoring – APAR PK79048 allows the specification of a maximum number of TPIPEs per OTMA Client (TMEMBER) and for all of OTMA • Error messages are issued when limits are reached/relieved – DFS4382W at 80% for TMEMBER limit – DFS4383E when TMEMBER limit reached – DFS4384I when TMEMBER flood relieved (<=50%) – DFS4385W when global limit reached – DFS4386I when global flood relieved (<= 80%) • Messages that try to create TPIPEs will be NACK’ed (x’29’) – Not for global limit • See APAR PM79048 for details 45 2011 © 2011 IBM Corporation
  • 46. IMS 10+ – OTMA  Resource Monitoring – APAR PK79048 allows the specification of a maximum number of TPIPEs per OTMA Client (TMEMBER) and for all of OTMA – This could effect IMS Connect which has one TPIPE per CM0 Client • Customers have had floods of CM0 ICON Clients fill up IMS storage with TPIPE, etc. control blocks 46 2011 © 2011 IBM Corporation
  • 47. IMS 10+ – OTMA  Resource Monitoring – When an OTMA input message is received from XCF IMS builds an Asynchronous Work Element (AWE) • The AWE will be deleted when the input message has been processed by OTMA – If there is a delay in OTMA processing a large number of AWE’s can build up – If YTIB monitoring is on for a TMEMBER then AWE monitoring will also be in effect with the same limit (INPT value) – WTO and MTO warning messages • DFS4380W at 80% of INPT value • DFS4381I when AWE flood is relieved (<= 50%) – Automation can react to these messages 47 2011 © 2011 IBM Corporation
  • 48. IMS 10+ – OTMA New IMS 10 ‘D’ Descriptor in DFSYDTx –Allows the customer to control ALTPCB output without coding DFSYPRX0 • The new descriptors can specify a CHNG or non-modifiable ALTPCB destination as NONOTMA or IMSCON – Wildcard characters are supported – MQSeries and other OTMA clients are not currently supported – Must specify a TMEMBER name • Can optionally specify as a Supermember – Can specify TPIPE name – Can specify Adapter name and Converter name for SOAP gateway output – Can specify timeout for Sync Callout • OTMA will generate default IMS Connect User Data if there is no DRU exit for the selected IMS Connect TMEMBER – Requires PM35619 (IMS10), PM39450 (IMS11), PM39451 (IMS12) 48 2011 © 2011 IBM Corporation
  • 49. IMS 10+ – OTMA  New IMS 10 ‘D’ Descriptor in DFSYDTx – Prior to PK73408 (IMS 10) • Invoked if no DFSYPRX0 exit or if DFSYPRX0 returns RC=0 – Not invoked if DFSYPRX0 returns RC=4 (OTMA) or RC=8 (non- OTMA) – After PK73408 (IMS 10) • If a descriptor exists for the destination DFSYPRX0 and the DRU exit will NOT be called – The descriptor totally overrides the exits 49 2011 © 2011 IBM Corporation
  • 50. IMS 10+ – OTMA  Resume TPIPE Shared Queues Enhancement – IMS Connect clients using Resume TPIPE with Wait on the front-end IMS could not retrieve new ALTPCB output created on the back-end IMS for a Supermember TPIPE • Auto or Single Wait – OTMA was enhanced to use shared queues notification for the back-end system to notify the front-end system that the ALTPCB output was available • Front-end system will retrieve the ALTPCB output from the Supermember queue and pass it to the OTMA client – APARs PK61774 (IMS 10) and PK80945 (IMS 11) 50 2011 © 2011 IBM Corporation
  • 51. IMS 10+ – OTMA  Shared Queues Enhancement – OTMA (and APPC) had the restriction that a transaction that was message-switched-to “synchronously” (CM1) had to run on the same IMS as the transaction that switched to it • That restriction was removed with PK55233 (IMS 10) and PK79610 (IMS 11) • The synchronously message switched transaction can go on the IMS Shared Queue and run in any IMS copy in the IMSPLEX • APPCASY=S (DFSDCxxx) or OTMAASY=S (DFSPBxxx) must be specified 51 – Either one activates the other 2011 © 2011 IBM Corporation
  • 52. IMS 10+ – OTMA  /DEQ TRAN Shared Queues Enhancement – When the /DEQ TRAN command was issued in a Shared Queues environment the transactions were dequeued but the OTMA YTIB control blocks and ITASKs were not freed • This left orphaned storage in IMS • This is corrected with PK61923 (IMS 10) 52 2011 © 2011 IBM Corporation
  • 53. IMS 10+ – OTMA  RACF Performance Enhancements – There are new performance APARs for cleaning up expired ACEE’s proactively rather than waiting for the next message from the user • PK79669 – IMS 10 • PK79670 – IMS 11 – There is a new performance APAR for putting ACEE’s in their own subpool • PK64810 – IMS 10 53 2011 © 2011 IBM Corporation
  • 54. IMS 10+ – OTMA CM0 Multiple IOPCB Output – Commit Mode 1 - Send-then-commit • A CM1 input message which does ISRT - PURG - ISRT - PURG - ISRT - PURG to the IOPCB will generate one multi-segment output message – Not 3 single segment output messages – A CM0 input would have generated 3 single-segment messages • In IMS 10 (PK60549) you have the option to make CM0 messages also ignore the PURG call and generate one multi-segment message – Specified in the OTMA header for an input message • Set bit x’02’ (TMAMIPRG) on in flag TMAMHCFL – Supported by IMS Connect and ITRA 54 2011 © 2011 IBM Corporation
  • 55. IMS 10+ – OTMA  /START and /STOP TMEMBER Commands – APAR PK92183 enhanced these commands to send protocol commands to the OTMA TMEMBER when the command is issued • /STOP TMEMBER xxxx – TMAMCTYP = TMAMCSPA – SUSPEND ALL INPUT • /START TMEMBER xxxx – TMAMCTYP = TMAMCRSA – RESUME ALL INPUT 55 2011 © 2011 IBM Corporation
  • 56. IMS 10+ – OTMA  OTMA C/I Trace – Problems with the OTMA Callable Interface (OTMA C/I) have been difficult to diagnose • There was no tracing/debugging information available – APARs PK96243 (IMS 10) and PM10670 (IMS 11) add internal tracing for OTMA C/I • There are no external commands or controls – it is always active • It is an internal wraparound table • The overhead will not be noticed • It can only be seen in SVC dumps • It is only for use by IMS Level 2 and 3 – There is no documentation for customers – Please apply this APAR if you are using OTMA C/I 56 2011 © 2011 IBM Corporation
  • 57. IMS 10+ – IMS Connect  IMS Enterprise Suite Connect APIs – If you want to write you own IMS Connect Clients but you do not want to know the details of TCP/IP and the IMS Connect interface and protocols you can use the new IMS Connect APIs • Simplifies interactions with IMS Connect by handling: – IMS Connect message header – IMS Connect interaction protocols – TCP/IP socket connections • Initial support was for Java (“Connect API for Java”) – C and C++ are now available (“Connect API for C”) – C# is a well known requirement • No tooling is required 57 2011 © 2011 IBM Corporation
  • 58. IMS 10+ – IMS Connect  IMS Enterprise Suite Connect APIs – Client Java and C/C++ applications will be able to use the full functionality available to RYO applications (those that use exit HWSSMPL1) in IMS Connect – Complexity of following IMS Connect protocol will be contained within the APIs and not exposed to the client application – Connections between the APIs (on behalf of the client application) and IMS Connect will be managed inside the APIs and their use will be transparent to the user 58 2011 © 2011 IBM Corporation
  • 59. IMS 10+ – IMS Connect  IMS Enterprise Suite Connect APIs – The IMS Connect APIs support: • IMS Transactions • Resume TPIPE for asynchronous output • PING and RACF password change commands • IMS commands supported by OTMA • SSL connections • API runtime tracing – The IMS Connect APIs will not initially support: • Two-phase commit • Synchronous callout • Unicode 59 2011 © 2011 IBM Corporation
  • 60. IMS 10+ – IMS Connect  IMS Enterprise Suite Connect APIs – Require IMS Connect 10 – Uses the IMS Connect sample User Message Exit HWSSMPL1 – Can be downloaded from the web – Can installed as part of the IMS Enterprise Suite • More later – Sample client applications are provided – Java and C/C++ documentation are available on the IMS Info Center • Navigable per class/interface/method • Searchable 60 2011 © 2011 IBM Corporation
  • 61. IMS 10+ – IMS Connect  IMS Enterprise Suite Connect APIs – Major Functionality from User’s Point-of-View • “Configure input - Execute interaction - Process response” paradigm – Connections configured using setter methods of Connection object – Interactions configured using setter methods of TmInteraction object – Input can be provided as a one or two-dimensional byte array, a Java String or an array of Java Strings – Configured interactions executed using execute interaction – Output (response message) can be retrieved as a one or two- dimensional byte array, a Java String or an array of Java Strings 61 2011 © 2011 IBM Corporation
  • 62. IMS 10+ – IMS Connect Cancel Client –IMS Connect has a Cancel Timer so that an IMS Connect Client can tell IMS Connect to stop waiting for an answer from IMS • If IMS Connect was still waiting and the IMS Connect Client tried to send in another message it would be rejected as a “duplicate Client” • Cancel Timer only worked if the IMS Connect Client was still active and waiting on an ICON timer and the TCP/IP connection was still active • If the IMS Connect Client ended or the TCP/IP connection ended while waiting on an ICON timer then Cancel Timer did not work – New option Cancel Client was introduced 62 2011 © 2011 IBM Corporation
  • 63. IMS 10+ – IMS Connect  Cancel Client – This is a new option provided in PK73829 (IMS 10) – If the message is received and there is already a Client with this Clientid that session will immediately be cancelled and replaced by this session • This is much easier and more straightforward than Cancel Timer – If you are using an IRM • Set IRM_F3 to IRM_F3_CANCID (x’80’) – If you are not using an IRM • Communicate Cancel Client in your own way – In the IMS Connect User exit set OMUSR_FLAG1 to OMUSR_CANCID (x’20’) 63 2011 © 2011 IBM Corporation
  • 64. IMS 10+ – IMS Connect  Keepalive Specification – APAR PK72652 (IMS 10) introduced support to allow IMS Connect to override the TCP/IP Keepalive value • PORT=(ID=xxxx,KEEPAV=nn) – This is an alternate way of defining Ports to ICON – A Port can not be listed in both PORTID and PORT – There can be multiple PORT statements – one for each Port – up to 50 – ID is the Port number – KEEPAV is the override value, in seconds, for the TCP/IP default keepalive value • This is the value that tells TCP/IP how long to wait before telling IMS Connect that a TCP/IP session has gone away • The TCP/IP default can be very long and IMS Connect will not know that a session as ended 64 2011 © 2011 IBM Corporation
  • 65. IMS 10+ – IMS Connect  RACF Mixed Case Password – IMS Connect support for mixed-case passwords has been enhanced to include a RACF option that configures IMS Connect to automatically enable or disable mixed-case password support based on the specification for mixed-case password support in the z/OS RACF configuration • APAR PK80037 • This option will be the default after the APAR is applied if PSWDMC is not specified 65 2011 © 2011 IBM Corporation
  • 66. IMS 10+ – IMS Connect  RACF Mixed Case Password – Specified in two ways • PSWDMC=R in the HWS statement of the IMS Connect configuration PROCLIB member • Issue either the IMS Connect command SETPWMC RCF or the IMS Connect z/OS command UPDATE MEMBER TYPE(IMSCON) SET(PSWDMC(RCF)) – This APAR will not alter the way IMS Connect treats the existing values Y|N of the PSWDMC parameter in the IMS Connect configuration member and ON|OFF of the 2 commands mentioned above 66 2011 © 2011 IBM Corporation
  • 67. IMS 10+ – IMS Connect  After sending in an ACK for CM0 output an IMS Connect client had to wait for an IMS Connect timeout – A timeout vaue of c’Z’ (zero) was not supported and was converted to 0.25 seconds – APAR PK42286 allows specifying a zero timeout value for this ACK but is only supported for the IMS TM Resource Adapter • Implemented in ITRA APAR PK43685 – The IMS Connect Client does not have to do a Read after the ACK and wait for the timeout • Be careful – there may be more messages 67 2011 © 2011 IBM Corporation
  • 68. IMS 10+ – IMS Connect PK57574 is an important IMS Connect performance APAR – It uses a hash technique to search the list of IMS Connect Clients on a Port – This was a sequential search and there can be 1,000’s of Clients on a Port 68 2011 © 2011 IBM Corporation
  • 69. IMS 10+ – IMS Connect  PING Enhancement – A PING received on a Persistent Socket disconnects the socket when it sends the PING reply – If the PING is received as the first message after a Connect the Client ID is not established – If the PING is received as the first message after a Connect the "first message received" message timer is not turned off – This affects the ability to use PING as a mechanism to keep a firewall timer from timing out – This will be fixed by APARs PM27324 (IMS 10) and PM27325 (IMS 11) 69 2011 © 2011 IBM Corporation
  • 70. IMS 10+ – IMS Connect  Recorder Trace for Input Messages – IMS Connect was calling the Recorder trace for the input message buffer (ICONRC - *IPB) after calling the User Message Exit • The trace record might not show the true input – APARs PM24536 (IMS 10), PM40333 (IMS 11) and PM40334 (IMS 12) correct this • The ICONRC input buffer will be captured before calling the User Message Exit 70 2011 © 2011 IBM Corporation
  • 71. IMS 10+ – IMS Connect  SOMAXCONN (BACKLOG) – This TCP/IP parameter tells TCP/IP the maximum number of Connect requests that can be queued in TCP/IP • If there are more Connect requests they are rejected • IMS Connect processes one Connect request at a time per Port – IMS Connect had coded this parameter to be 5 • This caused Connect requests to be rejected by TCP/IP – Especially after a network restart – APARs PM13818 (IMS 10) and PM24904 (IMS 11) change IMS Connect to set this parameter to the MAXSOC value • The minimum value will be 50 71 2011 © 2011 IBM Corporation
  • 72. IMS 10+ – IMS Connect  Miscellaneous Enhancements – Port number passed to IMS Connect User Message Exits • PK42669 (IMS 10) – Provide subsystem name and type information to user data on XCF IXCJOIN • Can be retrieved via XCF queries – Subsystem type – e.g. HWS – Subsystem version – e.g. 910 – Subsystem name – e.g. ICON1234 – Add client information such as IP and Port address to HWSSSL00E, HWSP1415E, HWSP1445E and HWSP1485E messages • PK55003 & PK51306 & PM37388 (IMS 10) 72 2011 © 2011 IBM Corporation
  • 73. IMS 10+ – IMS Connect  Miscellaneous Enhancements – RIMS Security when using Top Secret did not work if the RIMS class was not defined • PM31975 (IMS 10), PM33686 (IMS 11) and PM33685 (IMS 12) – Add the TCP/IP address to message HWSP1445E so that the bad IMS Connect Client can be determined • HWSP1445E UNKNOWN EXIT IDENTIFIER SPECIFIED IN MESSAGE PREFIX; MSGID=msgid1/msgid2, M=mc • PM37388 (IMS 10), PM38443 (IMS 11), PM38444 (IMS 12) 73 2011 © 2011 IBM Corporation
  • 74. IMS 10+ – IMS Connect  APAR PK69366 provides XML Adapter Multi- Segment Support – This allows the IMS SOAP Gateway to process multi-segment messages – Requires RDz 7.5.1 or higher to generate the XML converters 74 2011 © 2011 IBM Corporation
  • 75. IMS 10+ – IMS Connect IMS Connect version passed to IMS Connect exits – APAR PM05993 added the IMS Connect version to the XIB control block HWSXIB DSECT Exit Interface Block 00200000 *********************************************************************** 00210000 * XIB Header * 00220000 *********************************************************************** 00230000 XIB_HEADER DS 0D 00240000 XIB_EYE DS CL4XIB EYECATCHER 00250000 XIB_DATASTORES DS A DataStore list address 00260000 XIB_UFLD_CNT DS F User field count 00270000 XIB_XIBDS_LEN DS H Length of XIBDS Entry @PK70960 00280000 XIB_ARCHLVL DS X Architecture Level @PK70960 00280100 XIB_ARCH1 EQU X01 Arch Level 1 @PK70960 00280200 XIB_ARCH2 EQU X02 Arch Level 2 @PM05993 00280250 XIB_ARCHMAX EQU XIB_ARCH2 Highest Arch Level @PM05993 00280300 * Set Arch Level to 2 @PM05993 00280310 DS X Reserved for IMS Connect @PK70960 00280400 XIB_VERSION DS F Version X0A0100=V10.1.0 @PM05993 00280450 DS F Aligned with V11 @PM17288 00280470 DS 3F Reserved for IMS Connect @PM05993 00280500 * @PM05993 00280600 XIB_HDR_LEN EQU *-HWSXIB XIB header fixed length 00290000 75 2011 © 2011 IBM Corporation
  • 76. IMS 11 – OTMA and IMS Connect  CM0 ACK Timeout – IMS 10 introduced Timeout waiting for an ACK for a CM1 SL1 response • The MPR is occupied waiting for the ACK – IMS 11 introduces Timeout waiting for an ACK for a CM0 SL1 output message • The output queue is being held – When the timeout is reached the output message causing the hang is moved to a special timeout queue TPIPE for that TMEMBER • The original output queue TPIPE is now free to continue 76 2011 © 2011 IBM Corporation
  • 77. IMS 11 – OTMA and IMS Connect  CM0 ACK Timeout – The same timeout value is used for both CM0 ACK timeout and CM1 ACK timeout – Can be specified in seconds (0-255) in 4 ways • In the Client Bid • T/O= parameter in DFSYDTx • /STA TMEMBER xxxx TIMEOUT nnn • By message in the OTMA header – If less than the T/O or /STA value – The default is 120 seconds 77 2011 © 2011 IBM Corporation
  • 78. IMS 11 – OTMA and IMS Connect  CM0 ACK Timeout – The timeout value can not be specified via Client Bid for MQSeries or OTMA C/I – IMS Connect has the ACKTO parameter on the Datastore control card which is the value used by IMS Connect for Client Bid – Can be turned off by T/O=0 or /STA TMEMBER xxxx TIMEOUT 0 • Can not be turned off for a message using the OTMA header or by Client Bid 78 2011 © 2011 IBM Corporation
  • 79. IMS 11 – OTMA and IMS Connect  CM0 ACK Timeout – The OTMA client can specify a CM0 ACK timeout TPIPE name during Client Bid • Currently only supported by IMS Connect • The default TPIPE name is DFS$$TOQ • IMS Connect has the CM0ATOQ parameter on the HWS control card in the HWSCFGxx member and on the Datastore control card – This specifies the TPIPE name 79 2011 © 2011 IBM Corporation
  • 80. IMS 11 – OTMA and IMS Connect  CM0 ACK Timeout – For IMS Connect the message is queued to a Hold queue • If a Reroute TPIPE name was specified on the input message the output message is queued to that TPIPE • If a Reroute TPIPE name was not specified the message is queued to the TPIPE name specified in the CM0ATOQ parameter – If this parameter was not set the message is queued to TPIPE DFS$ $TOQ 80 2011 © 2011 IBM Corporation
  • 81. IMS 11 – OTMA  Type 2 Query Command – There is a new Type 2 command to display OTMA Workload • QUERY OTMAI – Requests information on the active workload as represented by a Transaction Instance (TIB) which can represent • A CM0 input message which has not been enqueued • A CM1 input message which has not been enqueued • A CM1 input message which has been enqueued but which has not executed • A CM1 input message which is currently executing • A CM1 input message waiting for an ACK for the output message • An IMS Conversation waiting for the next input message • An “orphaned” transaction instance 81 2011 © 2011 IBM Corporation
  • 82. IMS 11 – OTMA  Type 2 Query Command – Output shows the information by TMEMBER and TPIPE and can assist in determining possible problems processing the input • Length of time that the Transaction Instance has existed • Correlation ID of the input message 82 2011 © 2011 IBM Corporation
  • 83. IMS 11 – OTMA  Type 2 Query Command – Example: QUERY OTMATI MSGAGE(3) SHOW(ALL) MbrName Tmember TpipeName CC CText MsgAge Userid IMSA HWS1 APPLA 0 Completed Successfully 5 USER04 IMSA HWS1 APPLA 0 Completed Successfully 6 USER88 ... ... ... IMSB HWS2 APPLB 0 Completed Successfully 8 SVL01 IMSB HWS2 APPLB 0 Completed Successfully 4 SVL08 83 2011 © 2011 IBM Corporation
  • 84. IMS 11 – OTMA  Flood Control for Total TIBs – /STA TMEMBER ALL INPUT #### – Command enhancement to set the global message flood warning level for ALL the OTMA members – The new ALL parameter provides a global value that OTMA additionally monitors for all members combined • Default is 8000 84 2011 © 2011 IBM Corporation
  • 85. IMS 11 – OTMA  Flood Control for Total TIBs – When the global value is reached • WTO and MTO messages are issued – DFS4388W when global maximum is reached – DFS0793I when global flood is relieved • Action message is sent to all OTMA members • New input messages are not rejected – /DISPLAY OTMA enhancement • New global message flood warning level display under the INPT column of the OTMA Server name 85 2011 © 2011 IBM Corporation
  • 86. IMS 11 – OTMA  Dynamic Descriptors – With IMS 11, descriptors can be managed dynamically • CREATE OTMADESC – Used to create a new OTMA message routing descriptor • UPDATE OTMADESC – Used to modify an existing destination routing descriptor • DELETE OTMADESC – Used to remove an existing destination routing descriptor • QUERY OTMADESC – Used to display the characteristics of a specific destination routing descriptor 86 2011 © 2011 IBM Corporation
  • 87. IMS 11 – OTMA  Virtual Storage Relief – OTMA obtains storage for TPIPEs, input anchor blocks (TIBs) and output anchor blocks (QABs) as needed • User processing can create MANY of these blocks – These control blocks have ITASKs associated with them • 2 ITASKs per TPIPE • 1 ITASK per TIB • 1 ITASK per QAB – Each ITASK has 6 control blocks 87 2011 © 2011 IBM Corporation
  • 88. IMS 11 – OTMA  Virtual Storage Relief – Storage for all of these control blocks are above the 16MB line • However each control block had a 64-byte CDE in LSQA below the 16 MB line – These CDE’s have been removed and replaced with control blocks above the bar (> 2.2GB) – This greatly reduces OTMA use of virtual storage below the 16MB line and greatly reduces the chances of S878, S80A, and S40D abends – This also means that you can no longer track these control blocks using the CDE chain 88 2011 © 2011 IBM Corporation
  • 89. IMS 11 – IMS Connect  Open Database – IMS Connect is now the TCP/IP portal for access to IMS data as well as IMS transactions z/OS LPAR A IMS z/OS WAS Universal Traditional DB ODBA Resource O ODBM O Distributed T C Adapter D S B C PC S D PC CTL J C IMS DB P C A I I B I JEE WAS on Any Platform P A A Universal 1.5 XCF S DB Resource T LPAR B IMS C Traditional O Adapter IMS Universal Drivers ODBA P A J JDBC ODBM PC C I O CTL P S IMS DB A P C D 1.5 DLI I B A Non- IMS Universal Drivers LPAR C JEE JDBC IMS TCP/IP IMS Connect ODBM O T S PC DLI S C D CTL C IMS DB P C I B TCP/IP I I A 89 P RYO DRDA Appl. 2011 © 2011 IBM Corporation
  • 90. IMS 11 – IMS Connect  Port Input/Output Edit Exit –Specified on the HWSCFG TCP/IP control card • PORT=(ID=xxxx,KEEPAV=nn,EDIT=xxxxxxxx) –EDIT=xxxxxxxx is the name of an exit to edit the input and output data from this Port before and after it is processed by IMS Connect –This allows the IMS Connect Client to send in any data stream, e.g. Pure XML (), and not have to conform to IMS Connect format – but LLLL is required • The exit can add LLZZPrefix, LLZZTrancode, etc. –The exit can also reformat the output data • Remove IMS and IMS Connect artifacts –The exit can be dynamically refreshed via command –PK48548 is required for this exit to work properly • LLLL will still be required 90 2011 © 2011 IBM Corporation
  • 91. IMS 11 – IMS Connect  Maximum Socket Warning – Specified on the HWSCFG TCP/IP control card • WARNSOC=nn,WARNINC=nn – WARNSOC • Decimal value between 50 and 99 (default 80) • Sets a warning level as a % of the MAXSOC limit • New message issued HWSS0772W when the warning value is reached – WARNINC • Decimal value between 1 and 50 (default 5) • Sets the incremental warning % after WARNSOC has been reached • Re-issues HWSS0772W each time sockets increase by nn% – Existing message HWSS0771W is issued when MAXSOC is reached 91 2011 © 2011 IBM Corporation
  • 92. IMS 11 – IMS Connect  Maximum Socket Warning – Message HWSS0773I is issued when the number of sockets falls back below the warning level – The message trigger is the lower of • Two times the WARNINC value below the WARNSOC value • 5% below the WARNSOC level 92 2011 © 2011 IBM Corporation
  • 93. IMS 11 – IMS Connect  Automatic Reconnect to TCP/IP – IMS Connect will now automatically reconnect to TCP/IP when the stack becomes available after a failure – There is a new loop and timer logic for each active Port • Invoked if Port is terminated due to a failure • Internally issues an OPENPORT command • Loops back to timer delay if network is still not available • Issues message HWSS0780I for each Port that is successfully reactivated 93 2011 © 2011 IBM Corporation
  • 94. IMS 11 – IMS Connect  Supermember at the Datastore Level – The Supermember concept allows an IMS Connect Client to retrieve asynchronous output from the same TPIPE in multiple IMS TMEMBERs – Prior to IMS 11 the Supermember name was specified on the IMS Connect level • All datastores in one IMS Connect instance had to belong to the same Supermember – In IMS 11 the Supermember name can be specified at the Datastore level • One IMS Connect instance can participate in multiple Supermembers94 2011 © 2011 IBM Corporation
  • 95. IMS 11 – IMS Connect  Remove HWSIMSO0 and HWSIMSO1 – These are object code only versions of IMS Connect User Message Exits HWSSMPL0 and HWSSMPL1 – As new features were added to HWSSMPL0/1 they were not all added to HWSIMSO0/1 so they are out of date – The message IDs for these exits are *IRMREQ*, *IRMRE1*, and their ASCII equivalents • If you do not want to change your existing IMS Connect Clients you will have to create new exits, based on HWSSMPL0/1, with these ID’s – Do not try to keep a copy of the IMS 9/10 load module and use it in IMS 11 • It will not work • See next foil 95 2011 © 2011 IBM Corporation
  • 96. IMS 11 – IMS Connect  Restructure of HWSEXPRM – HWSEXPRM is the control block passed from IMS Connect to the IMS Connect User Message Exit • This has changed for IMS 11 – All IMS Connect User Message Exits must be re-assembled using the IMS 11 macro library • This includes HWSSMPL0/HWSSMPL1 and HWSJAVA0 • The re-assembled exits will not work in prior versions of IMS Connect 96 2011 © 2011 IBM Corporation
  • 97. IMS 11 – IMS Connect VIEWxxxx Enhancements – All new parameters are displayed • VIEWHWS – WARNSOC, WARNINC • VIEWPORT – KEEPALIVE, EDIT • VIEWDS – STATE, Supermember, CM0ATOQ – State = AVAIL, WARN, SEVERE, N/A – A DATASTORE column has been added to the Socket data line for the VIEWHWS and VIEWPORT commands HWSC0001I CLIENTID USERID TRANCODE DATASTORE STATUS SECOND CLNTPORT IP-ADDRESS HWSC0001I CLIENT01 USRT001 APOL12 IMS1 CONN 7 1026 009.030.123.148 – VIEWHWS SUMMARY shows all data except the individual sockets • There can be 1,000’s of these 97 2011 © 2011 IBM Corporation
  • 98. IMS 11 – IMS Connect  Other enhancements – The recorder trace can now optionally be run as a BPE external trace • This provides better processing when the data set is full – The IMS Connect User Message Exit can return an error message to the IMS Connect Client without disconnecting a persistent socket – Defining only one SSL Port is now enforced during IMS Connect initialization 98 2011 © 2011 IBM Corporation
  • 99. IMS 11+ – OTMA  APPC/OTMA RRS Protected Conversation Processing with ROLB Call – APAR PK84674 removes ABENDU711-20 when a ROLB call is issued in an RRS protected conversation • The ROLB call will not affect the entire RRS protected Unit of Work – The RRS protected input remains in process until a commit point – The outbound protected conversation will not be notified to backout • Migration consideration – The IMS application must now notify the outbound protected application to do backout 99 2011 © 2011 IBM Corporation
  • 100. IMS Connect Extensions  There have been many enhancements to IMS Connect Extensions V2.1 – Rules-based routing – Routing intelligence improved to use IMS flood-warn state – Improved management of IMS Connect transaction options – Persistent trace: activate IMS Connect Extensions tracing on every system restart – Verify user service exit function – Batch Command utility refresh of Connect Extensions options – Mixed-case password support 100 2011 © 2011 IBM Corporation
  • 101. IMS Connect Extensions  There have been many enhancements to IMS Connect Extensions in new Version 2.2 – Eclipse-based operational management GUI – Extended status information – TCP/IP information (similar to NETSTAT) for active sessions – IMS 11 command support – IMS 11 event collection – Simplified configuration with setup dialog 101 2011 © 2011 IBM Corporation
  • 102. IMS Enterprise Suite  There are several IMS features which are currently downloaded from the IMS Web site  The IMS Enterprise Suite will now package several of these feature in an SMP installable package – IMS SOAP Gateway enhanced with WS*Security and Business Events support – IMS DLIModel Utility – IMS JMS API – IMS Connect API for Java – IMS Connect API for C and C++ – IMS Explorer 102 2011 © 2011 IBM Corporation
  • 103. IMS Enterprise Suite  IMS Explorer – IMS GUI-based framework for consistent and integrated tools across environment – Easier visualization and editing of IMS Database and Program Definitions – Graphical display of IMS segment hierarchy and database structure – Graphical editors to display/create IMS PSBs – Graphical editors to edit/add fields on a DBDs – Generation of DBD and PSB source – Ability to easily access IMS data using SQL statements – Tech preview is available 103 2011 © 2011 IBM Corporation
  • 104. IMS 12 – IMS to IMS TCP/IP Messaging  Enhancements to leverage TCP/IP networks for communications between IMS systems for: – OTMA remote ALTPCB output (TCP/IP PGM-PGM Switch) • Uses one-way message communications Local IMS Connect Remote IMS Connect IMS1 IMS 2 – MSC TCP/IP • Request and response message communications – IMS Connect processes both the request and response messages as one-way asynchronous messages Local IMS Connect Remote IMS Connect Send socket IMS1 IMS 2 Receive socket 104 2011 © 2011 IBM Corporation
  • 105. IMS 12 – TCP/IP OTMA Remote ALTPCB Output TCP/IP connections between the local and remote IMS systems – Are managed by IMS Connect to IMS Connect communications • Without having to write client code or invoke additional gateways Example: Customer IMS1 IMS Connect1 IMS Connect2 IMS2 Gateway Application Resume Tpipe OExisting O ISRT ALTPCB T XCF TCP/IP TCP/IP XCF TMethod Descriptor M M ICON1 Tran output SendOnly A A IMS1 IMS Connect1 IMS Connect2 IMS2 O TCP/IP ONew ISRT ALTPCB XCF XCF T TMethod Descriptor ICON1 M M 105 A A 2011 © 2011 IBM Corporation
  • 106. IMS 12 – TCP/IP OTMA Remote ALTPCB Output OTMA – Sends OTMA remote ALTPCB messages to IMS Connect using new destination information • OTMA destination descriptors or DFSYDRU0 exit Routine IMS Connect – Receives OTMA ALTPCB messages from a local IMS and sends them to the remote IMS Connect for processing in the remote IMS • Enhanced IMS Connect configuration specifications IMS1 IMS2 Local IMS Connect Remote IMS Connect App TMEMBER/ Tran Auth ISRT TPIPE Msg Q ALTPCB ALTPCB destination is resolved using an OTMA Destination Descriptor or the DFSYDRU0 exit IMS Connect configuration defines the connection to the remote Partner 106 2011 © 2011 IBM Corporation
  • 107. IMS 12 – TCP/IP OTMA Remote ALTPCB Output New destination descriptor  DFSYDRU0 exit parameters (DFSYDTx member – Set output flag bit to indicate the of proclib) message is an OTMA remote – RMTIMSCON= specifies the ALTPCB message. remote IMS Connect (required) – Set the required and optional information in the OTMA prefix – RMTIMS= specifies the target area (mapped by HWSOMPFX remote IMS (required) macro). • New specifications in the – RMTTRAN= specifies the user data section: transaction name to use on the – OMUSR_RMTICON – remote IMS remote IMS (optional) Connect – USERID= specifies the RACF – OMUSR_RMTIMSID – remote IMS userid name to use on the remote – OMUSR_RMTTRAN – remote IMS for transaction authorization transaction (optional) – OMUSR_RMTUID – userid for transaction authorization Existing parameter (required) – TMEMBER= specifies the local IMS Connect 107 2011 © 2011 IBM Corporation
  • 108. IMS 12 – MSC TCP/IP  Support for MSC communications across a TCP/IP network – MSC TCP/IP leverages IMS Connect and the Common Service Layer – A new physical link MSPLINK TYPE=TCPIP • Provides a mechanism to – Take advantage of TCP/IP networks – Complement or backup existing SNA/VTAM links – Take advantage of potentially higher bandwidths • Supports operational compatibility with other link types (CTC, MTM, VTAM) – Starting, stopping, updating, displaying, and assigning resources – Only between IMS 12 systems 108 2011 © 2011 IBM Corporation
  • 109. IMS 12 – MSC TCP/IP  MSC TCP/IP leverages IMS Connect and the Common Service Layer – IMS Connect sends/receives messages via the TCP/IP network • IMS Connect manages the TCP/IP communications • IMS MSC manages the message processing – CSL provides the Structured Call Interface (SCI) for communications between IMS components including IMS Connect • Each IMS and its local MSC-routing IMS Connect system must be part of the same IMSplex – IMSPLEX= plexname parameter in the Common Layer Section of the DFSDFxxx of IMS proclib • The Operations Manager (OM) is not required but recommended – For type-2 command support 109 2011 © 2011 IBM Corporation
  • 110. IMS 12 – MSC TCP/IP  IMS to IMS Connect functionality – Isolates TCP/IP from the IMS Control Region • Uses the existing IMS Connect TCP/IP support – Provides a new MSC driver as well as TCP/IP driver for MSC – Supports communication with IMS via the Structured Call Interface (SCI) PLEX1 PLEX2 IMS1 IMS Connect – ICON1 IMS Connect – ICON2 MSC IMS2 MSC SCI MSC TCP/IP TCP/IP TCP/IP MSC SCI IMS3 Driver Driver Driver Driver MSC 110 2011 © 2011 IBM Corporation
  • 111. IMS 12 – MSC TCP/IP Benefits – Takes advantage of TCP/IP networks for MSC • Can potentially provide for a higher MSC bandwidth – Supports different configurations • Coexistence with or backup of VTAM/SNA links • Increases availability – Logical links can be moved between VTAM and TCPIP • Flexibility zOS zOS MSC TCPIP IMSA MSC CTC IMSC MSC MTM IMSD IMSB MSC VTAM 111 2011 © 2011 IBM Corporation
  • 112. IMS 12 – OTMA ACEE Reduction  New capability that creates, shares and caches a single ACEE associated with a RACF userid – Shared across multiple OTMA member clients (TMEMBER)  New maximum ACEE aging value during client-bid – 999999 seconds (11.5 days) • Previously 68 years (OTMA reduced to 2 years) • Range: 300 seconds to 999999 seconds – A cached ACEE has an aging value based on the OTMA member client with lowest aging value 112 2011 © 2011 IBM Corporation
  • 113. IMS 12 – OTMA ACEE Reduction  Cached ACEEs – Reduce the system storage requirements while providing better security and performance • Only one copy of the ACEE instead of multiple per OTMA client – Reduced storage usage – Reduced security exposure – Improved performance – Provide consistency • Same security result regardless of which OTMA client is used  Lower maximum ACEE aging value – Triggers faster ACEE cache refresh • Reduces security exposure, e.g., userid is revoked or access permissions are changed 113 2011 © 2011 IBM Corporation
  • 114. IMS 12 – CM1 Shared Queues XCF  New capability that removes the dependency on RRS in a Shared Queues environment for – APPC synchronous conversations and OTMA CM1 (send- then-commit) interactions • Applies only to synclevel=None | Confirm – Synclevel=Syncpoint still requires RRS  Communications use XCF services 114 2011 © 2011 IBM Corporation
  • 115. IMS 12 – CM1 Shared Queues XCF  Using XCF rather than RRS allows IMS to be the syncpoint manager – Enhances the performance of the commit processing by eliminating • RRS logging overhead • Potential RRS commit processing bottleneck • Overhead associated with communicating with an external syncpoint manager 115 2011 © 2011 IBM Corporation
  • 116. IMS 12 – CM1 Shared Queues XCF New options for the existing AOS= parameter in DFSDCxxx to request the use of XCF – AOS=B: Synchronous transactions synclevel=NONE|CONFIRM can be processed in a back-end system using XCF communications • Note: Processing synclevel of SYNCPT depends on the RRS option – RRS=Y: transactions can be processed at either FE or BE, using RRS – RRS=N: transactions are only processed at the FE – AOS=S: allows synchronous transactions with synclevel of NONE| CONFIRM to be processed in a back-end system using XCF communications • Note: Processing synclevel SYNCPT is equivalent to AOS=F. – AOS=X: allows synchronous transactions with synclevel of NONE| CONFIRM to be processed in a back-end system using XCF communications • Note: Processing synclevel of SYNCPT is equivalent to AOS=N 116 Note: (1) Choice of B|S|X is dependent on how syncpoint messages are to be processed 2011 © 2011 IBM Corporation
  • 117. IMS 12 – DFS2082 for CM0 Messages CM1 (Send-then-Commit) transactions rely on DFS2082 – To end the outstanding wait if the IMS transaction does not send IOPCB reply Conversion from the use of CM1 to CM0 (Commit-then- send) – For remote programs waiting for a reply • May result in a hang until timeout if there is no IOPCB reply Enhancement – A new commit-then-send (CM0) optional flag to request DFS2082 • Specified on an input CM0 transaction message • Triggers OTMA to send the DFS2082 message if – The IMS application does not reply to the IOPCB – Nor message switches to another transaction 117 2011 © 2011 IBM Corporation
  • 118. IMS 12 – Front-End Trace Logging New AOSLOG=Y|N keyword in the IMS DFSDCxxx PROCLIB member Specifies whether or not the FE system is to write a 6701 log record for: –Response messages returned from the BE system via XCF • Applicable to all synclevels (NONE, CONFIRM and SYNCPT) –Error messages returned from the BE system via XCF • Applicable to all synclevels of (NONE, CONFIRM and SYNCPT) ID=TIB3 –For diagnostics 2011 © 2011 IBM Corporation
  • 119. IMS 12 – ICON-ICON Communication IMS Connect provides a new configuration statement RMTIMSCON to describe the remote IMS Connect TCP/IP environment IMS1 TMEMBER/ Local IMS Connect App ISRT ALTPCB TPIPEISRT ALTPCB Descriptor XCF ICON1 WAIT_R DESC1 OTMAHDR | LLZZ | DATA TYPE=IMSCON TMEMBER=ICON1 HWS=(ID=ICON1,XIBAREA=100,RACF=N) RMTIMSCON= ICON2 TCPIP=(HOSTNAME=TCPIP,PORTID=(8888), RMTIMS=IMS2 MAXSOC=50,TIMEOUT=5000, RMTTRAN=TRANABC EXIT=(HWSSMPL0,HWSSMPL1) USERID=USER01 DATASTORE=(ID=IMS1,GROUP=XCFGRP1,MEMBER=ICON1, TMEMBER=IMS1,DRU=HWSYDRU0,APPL=APPLID1) RMTIMSCON=(ID=ICON2,HOSTNAME=ICON2.IBM.COM, PORT=9999,AUTOCONN=N,PERSISTENT=Y, IDLETO=60000,RESVSOC=10,USERID=USER01, 119 APPL=APPL01) 2011 © 2011 IBM Corporation
  • 120. IMS 12 – ICON-ICON Communication New RMTIMSCON statement in the local IMS Connect identifies the remote IMS Connect partner information – ID= Identifier for a remote IMS Connect connection – IPADDR= specifies the remote IMS Connect IP address (IPADDR or HOSTNAME required, but not both) • Accepts a loopback IP address – Local and remote IMS Connects are on the same TCP/IP stack (same LPAR) – In the range 127.0.0.0 to 127.255.255.255 – Likely used only in test environments – HOSTNAME= specifies the remote IMS Connect hostname – PORT= specifies the remote IMS Connect port – AUTOCONN= Y|N, specifies whether to automatically make socket connections to the remote IMS Connect on startup (optional - for OTMA only, MSC requires AUTOCONN=N) – PERSISTENT= Y|N, specifies whether the socket connections to this remote IMS Connect are persistent (optional - for OTMA only, MSC requires PERSISTENT=Y) 120 2011 © 2011 IBM Corporation
  • 121. IMS 12 – ICON-ICON Communication New RMTIMSCON statement in the local IMS Connect identifies the remote IMS Connect partner information… – IDLETO= specifies the amount of time the socket connection is idle before terminating it due to inactivity (Optional, for OTMA only) – RESVSOC= specifies the number of sockets to reserve for use to this remote IMS Connect – USERID= specifies user ID for generating RACF Passticket to be use by the remote IMS Connect for authenticating the user (optional – if specified, then APPL must also be specified.) – APPL= specifies the application name for generating RACF Passticket to be use by the remote IMS Connect for authentication • optional – if specified, then USERID must also be specified 121 RMTIMSCON=(ID=ICON2,HOSTNAME=ICON2.IBM.COM, PORT=9999,AUTOCONN=N,PERSISTENT=Y, IDLETO=60000,RESVSOC=10,USERID=USER01,APPL=APPL01) 2011 © 2011 IBM Corporation
  • 122. IMS 12 – ICON-ICON Communication Remote IMS Connect Configuration IMS1 TMEMBER/ ICON1 config App RMTIMSCON=(ID=ICON2, TPIPE ICON1 XCF HOSTNAME=ICON2.IBM.COM, ISRT WAIT_R PORT=9999) ALTPCB SendOnly with ACK LLLL|IRM|LLZZ|TRANABC |DATADescriptor Descriptors orDESC1 DFSYDRU0 exit TCP/IP ICON2D DESC1TMEMBER=ICON1RMTIMSCON=ICON2 HWS=(ID=ICON2,XIBAREA=100,RACF=Y)RMTIMS=IMS2 TCPIP=(HOSTNAME=TCPIP,PORTID=(9999),RMTTRAN=TRANABC MAXSOC=50,TIMEOUT=5000,EXIT=(HWSSMPL0,HWSSMPL1)USERID=USERXYZ DATASTORE=(ID=IMS2,GROUP=XCFGRP1,MEMBER=ICON2, TMEMBER=IMS2,DRU=HWSYDRU0,APPL=APPLID1 122 2011 © 2011 IBM Corporation
  • 123. IMS 12 – ICON-ICON CommunicationSend to Remote IMS IMS1 TMEMBER/ ICON1 config App XCF ICON1 RMTIMSCON=(ID=ICON2, TPIPE HOSTNAME=ICON2.IBM.COM,PORT=9999) ISRT WAIT_R ALTPCB SendOnly with ACKDescriptor Descriptors orDESC1 DFSYDRU0 exit TCP/IP IMS2 XCF Tran Auth ICON2 Msg QD DESC1TMEMBER=ICON1 OTMAHDR|LLZZ|TRANABC |DATARMTIMSCON=ICON2RMTIMS=IMS2 ICON2 configRMTTRAN=TRANABC TCPIP=(PORTID=(9999),...)USERID=USERXYZ DATASTORE=(TMEMBER=IMS2,...) 123 2011 © 2011 IBM Corporation
  • 124. IMS 12 – ICON-ICON Communication IMS1 App TMEMBER/ TPIPE XCF ICON1 ISRT WAIT_R SendOnly with ACK ALTPCB Descriptor TCP/IP IMS2 Descriptors or DESC1 DFSYDRU0 exit XCF Tran Auth ICON2 Msg Q ACK / NAK IMS2 performs transaction authorization,And finally – if necessary, and ACKs or NAKs the message If a message is NAKed, the OTMAReturn the ACK/NAK correlator token from the initial request is passed back so that IMS1 124 can match the NAK to the request 2011 © 2011 IBM Corporation
  • 125. IMS 12 – ICON-ICON Communication Supermember Support (Local IMS) (Local IMS Connect) (Remote IMS Connect) (Remote IMS) ICON1 ICON1 config SMEM=SM01 IMS1 Msg1 IMS2 SM01 ICON4 Msg2 ICON2 Msg1 ICON2 config Msg2 SMEM=SM01 Msg3 ACKDescriptor DESC1: Msg3 Note: Maximum of 8 IMS ConnectsTMEMBER=SM01 ICON3 Can participate in a super memberSMEM=Y ICON3 config environment SM01 – OTMA dynamically updates SMEM=SM01 - ICON1 the super member list when a - ICON2 member of the group leaves - ICON3 or joins the group 125 2011 © 2011 IBM Corporation
  • 126. IMS 12 – Type-2 Commands New Type-2 commands for IMS Connect resources – QUERY IMSCON – UPDATE IMSCON Conform to the IMS command structure using the OM API – Processed by OM clients, e.g., TSO SPOC, REXX SPOC API, Batch SPOC, IMS Control Center, etc. Can coexist with the previous WTOR and z/OS Modify commands – No changes to the existing command functionality 126 2011 © 2011 IBM Corporation
  • 127. IMS 12 – Type-2 Commands QUERY IMSCON TYPE(type) NAME(name1, name2,...) FILTER(filter) SHOW(attribute(s)) – TYPE = Type of resource in IMS Connect • ALIAS - aliases of associated ODBMs (VIEWIA) • CLIENT – active IMS Connect clients (no equivalent – information in VIEWPORT) • CONFIG – IMS Connect status and activity (VIEWHWS) • DATASTORE – datastores or IMS systems (VIEWDS) • IMSPLEX – information about the IMSPLEX (VIEWIP) • LINK – MSC logical link (no equivalent) • MSC - MSC physical link (VIEWMSC - new for IMS to IMS TCP/IP Communications) • ODBM – ODBMs and associated IMS aliases (VIEWOD) • PORT – TCPIP port and associated clients (VIEWPORT) • RMTIMSCON - remote IMS Connect and associated send clients (VIEWRMT - new for IMS to IMS TCP/IP Communications) • SENDCLNT – send clients (no equivalent - new for IMS to IMS TCP/IP Communications) • UOR - display unit of recovery identifier (VIEWUOR) 127 2011 © 2011 IBM Corporation
  • 128. IMS 12 – Type-2 Commands UPDATE IMSCON TYPE(type) NAME(name1, name2,...) START(condition1,condition2,…) STOP(condition1,condition2,…) SET(condition1,condition2,…) – TYPE = Type of resource in IMS Connect • ALIAS - aliases of associated ODBMs (VIEWIA) • CLIENT – active IMS Connect clients (no equivalent – information in VIEWPORT) • CONFIG – IMS Connect status and activity (VIEWHWS) • DATASTORE – datastores or IMS systems (VIEWDS) • IMSPLEX – information about the IMSPLEX (VIEWIP) • LINK – MSC logical link (no equivalent) • MSC - MSC physical link (VIEWMSC - new for IMS to IMS TCP/IP Communications) • ODBM – ODBMs and associated IMS aliases (VIEWOD) • PORT – TCPIP port and associated clients (VIEWPORT) • RMTIMSCON - remote IMS Connect and associated send clients (VIEWRMT - new for IMS to IMS TCP/IP Communications) • SENDCLNT – send clients (no equivalent - new for IMS to IMS TCP/IP Communications) • UOR - display unit of recovery identifier (VIEWUOR) 128 2011 © 2011 IBM Corporation
  • 129. IMS 12 - XML Converter Refresh  New Command to refresh an XML converter file that is already in use UPDATE IMSCON TYPE(CONVERTER)… xx,REFRESH CONVERTER NAME(cvrname) F hws,UPDATE CONVERTER NAME(cvtrname) OPTION(REFRESH) – Supported by all command interfaces: Type-2, WTOR, z/OS Modify – Converter files continue to be: • Generated using RDz • Loaded by IMS Connect from STEPLIB/JOBLIB/LNKLST 129 2011 © 2011 IBM Corporation
  • 130. IMS 12 – Return RACF Return Codes to ICON Client  Prior to IMS 12 IMS Connect sample User Message Exits returned RSM RC=08 RSN=40 for any and all security violations – No indication of specific reason • E.g. invalid userid, incorrect password, password expired, etc. – With IMS 12, enhancements to RACF Return Codes: • In the Request Status Message (RSM) for RYO and the IMS SOAP Gateway • RSM_RACFRC • In the OTMA User Data section for the IMS TM Resource Adapter • OMUSR_RACF_RC • New IMS Connect Protocol level indicates support OMUSR_PROLEV = OMUSR_PR03 130 2011 © 2011 IBM Corporation
  • 131. IMS 12 – RACF Userid Caching  Existing IMS Connect security with RACF=Y – Limited caching of RACF Utoken • Consecutive requests on a persistent socket with the same Userid/Passsword/Group  IMS 12 enhancement – Common cache for userids across ALL sessions and ALL ports • HWSCFG HWS statement: UIDCACHE={N|Y} , UIDAGE=aging_value 131 2011 © 2011 IBM Corporation
  • 132. IMS 12 – CM0 Nowait ACK for RYO Clients CM0 Nowait ACK for the IMS TM Resource Adapter (ITRA) was introduced in IMS 10+ For IMS 12 this is now supported for non-ITRA Clients – IMS Connect indicates to the remote client that the support is available in the CSM on response CSM_FLG1 = CSM_PRLVLFLG X’10’ Protocol Level Available CSM_PROTOLVL = CSM_PR02 X’02’ CM0 Nowait ACK Support – RYO client sends the ACK and indicates Nowait IRM_F1 = IRM_F1_NoWait X’02’ IRM_TIMER = X’E9’ / C’Z’ 132 2011 © 2011 IBM Corporation
  • 133. IMS 12 – VIEWHWS Partial Read Status New READ client status – The message has been received by IMS Connect but is not yet considered a complete input message • Should be transient but can be an indicator of a problem • Affects VIEWPORT, VIEWHWS, QUERY MEMBER, QUERY PORT, QUERY IMSCON command output Targets the problem – Remote clients sends a request to IMS Connect specifying LLLL • IMS Connect reads from TCP/IP until LLLL bytes received – If the client incorrectly has LLLL larger than message size • Client waits for the response message from IMS Connect • BUT, IMS Connect cannot process the message because it has to wait for rest of the input up to the LLLL value 133 2011 © 2011 IBM Corporation
  • 134. IMS 12 – VIEWHWS Partial Read Status Implementation xx,VIEWPORT 9999 HWSC0001I PORT=9999 STATUS=ACTIVE KEEPAV=0 NUMSOC=4 EDIT= TIMEOUT=0 HWSC0001I CLIENTID USERID TRANCODE DATASTORE STATUS SECOND CLNTPORT IP-ADDRESS HWSC0001I CLIENT01 USRT001 APOL12 IMS1 RECV 113 2414 009.023.038.110 HWSC0001I CLIENT02 USRT002 IMS1 READ 2147 2416 009.023.038.110 HWSC0001I CLIENT03 USRT003 IMS1 CONN 13 2418 009.023.038.110 HWSC0001I TOTAL CLIENTS=3 RECV=1 READ=1 CONN=1 XMIT=0 OTHER=0 – If the client remains in READ for an extended period then a potential problem exists 134 2011 © 2011 IBM Corporation
  • 135. IMS 12 – Sample Exit Object Code  IMS 11 removed Object Code Only sample User Message exits HWSIMSO0 and HWSIMSO1 – They were old and did not support many new features  Sample exits HWSSMPL0 and HWSSMPL1 were only shipped as source – The customer had to assemble and link these modules even if they were not modified  IMS 12 ships object code for HWSUNIT0, HWSJAVA0, HWSSMPL0, HWSSMPL1 in addition to the source code 135 2011 © 2011 IBM Corporation
  • 136. IMS 12 – New Recorder Trace Records  New level of tracing adds records for TCP/IP and XCF sends and receives ICONTR – TCP/IP Receive ICONTS – TCP/IP Send ICONIR – IMS OTMA Receive ICONIS – IMS OTMA Send – Requires the use of BPE External Trace support introduced in IMS 11 • Due to the amount of data that can be produced 136 2011 © 2011 IBM Corporation
  • 137. Conclusion OTMA and IMS Connect have been enhanced in many ways since IMS 10 These enhancements should enable customers to implement new and better solutions 2011 © 2011 IBM Corporation
  • 138. Thank You! Your Feedback is Important to Us Please Complete the Evaluation 138138 2011 © 2011 IBM Corporation