rug october 2014 - ims connect and what's new in v12 and v13

© 2014 IBM Corporation

®

IMS User Group – Oct 2014

IMS ConnectWhat’s New in Version 12 and 13

Tom [email protected] Connect Development

mailto:[email protected]


2

Disclaimer© Copyright IBM Corporation 2014. All rights reserved.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


3

Agenda

– Business Value of IMS Connect– Key Functions of IMS Connect– IMS 12 Enhancements– IMS 13 Enhancements


4

IMS Connect is the integrated TCP/IP gateway to all of IMS

z/OS

IMSIMSCONNECTCONNECT

Exit

XCF

IMS

Database

Transaction manager

IMS APP

Database

manager

OTM

A

IBM Management Console for IMS and DB2 for z/OS

IMS TM Resource Adapter

IMS SOAP Gateway

IMS Universal DBResource Adapter/Drivers

SCIOperationsManager

SCI

OD

BM

Activejournal

IMS ConnectAPI Clients

DataPower

Other vendor solutions

TCP/IP

IMS ConnectExtensions


5

Business value of IMS Connect

– Supports TCP/IP sockets access to IMS TM and IMS DB No requirement to modify existing IMS applications

– Provides a high performance strategic base for new connection technologies

IMSPLEX Callout

- Provides SMP/E installability and serviceability

– Offers a structure interface and a high level programming interface to TCP/IP client applications

For applications via IMS SOAP Gateway, IMS TM Resource Adapter, DataPower, user-written client applications, and Java application for DB requests.


6

Business value of IMS Connect

– High Performance– 2013 – IMS 13 100K TPS benchmark project– Achieved over 117,000 transactions per second (TPS) on a single IMS

– Average over a 15-minute interval– Using IMS Fast Path (FP) Credit Card benchmark application– Messages were generated by IBM’s Teleprocessing Network Simulator

(TPNS)– IMS via TCP/IP through five IMS Connect address spaces with RACF

security and OTMA security=CHECK– Periodic IMS system checkpoints were taken during the run, and IMS

Online Log Data Set (OLDS) switching and archiving occurred as needed


®


Key Functions of IMS Connect


8

Configuration to IMS/TM via OTMA

IMS Connect configuration (HWSCFGnn) member resides in IMS.PROCLIB

HWS (ID=ICONN01,RACF=N,) TCPIP (ECB=Y,HOSTNAME=TCPIP,PORTID=(3336),EXIT=(HWSSMPL1,HWSIMSO1)) DATASTORE(ID=IMSA,MEMBER=ICA,GROUP=IMSXCF,TMEMBER=IMSV10)DATASTORE(ID=IMSB,MEMBER=ICA1,GROUP=IMSXCF,TMEMBER=IMSPROD3)

XCF Group Name IMS systems

ICONN01

IMS Connect

OTMA=YGRNAME=IMSXCFOTMANM=IIMSV10

TCPIP Network

IMSXCFICA

IMSV10

Application specifies:Host DNS name, IMS Connect Port (e.g. 3336)and Datastore ID (e.g. IMSA or IMSB)

TCP/IP

Host DNSname

3336

OTMA=YGRNAME=IMSXCFOTMANM=IMSPROD3

IMSPROD3ICA1

Support one-to-many and many-to-one connection!

XCF Group Name

IMSXCF

XCF Group Name

IMSXCF


9

Message Flow for an IMS/TM Transaction

OTMA

IMSOTMA headers + input msg

IMS Connect

TCP/IP

User Exits:- Translation ASCII / EBCDIC- Validation- Conversion between

client message format and OTMA message format - Prepare output message format

OTMA headers + output msg

Clients using SOCKETS API:

- Input message:Formatted message header to communicate with IMS Connect Client message (can include OTMA headers)

- Output message can consist of one or more predefined structures


10

Configuration to IMS/DB via ODBM

ODACCESS=(ODBMAUTOCONN=Y|N,ODBMTMOT=, DRDAPORT=(ID=,KEEPAV=,PORTTMOT=),

IMSPLEX=(MEMBER=,TMEMBER=))

IMS systems

ICONN01

IMS Connect T

CP/IP

999

DRDAApplicationRequestor

TCP/IPClient

IMS/DB

IMS/DB

ODBM ODBA

ODBM ODBA

Support one-to-many and many-to-one connection!

IMS Connect configuration (HWSCFGnn) member resides in IMS.PROCLIB

SCI Group


11

Message Flow for an IMS/DB Request

ODBA

IMSODBM + input msg

IMS Connect

TCP/IP

User Exits:-For security -For ODBM selection

ODBM + output msg

Clients using SOCKETS API:

- Input message:DRDA message

-Output message - DRDA message

ODBM

IMS Connect acts like a router between the client and the IMS Open Database Manager (ODBM).


12

LPAR A

LPAR B

LPAR C

z/OSAny TCP/IP-enabled environment

WebSphere

IMS ConnectS

C

I

TCP/IP

XCFIMS DBCTL

IMS

PCS

C

I

ODBA

IMS DBCTL

IMS

PCS

C

I

ODBA

CTL IMS DB

IMS

PCS

C

I

ODBA

ODBM

ODBM

ODBM

JDBC TCP/IP

DL/I TCP/IP

Roll Your Own TCP/IP

XCF

XCFJ

C

A

1.5

T

C

P/

I

P

S

O

A

P

IMS Universal DB resource adapter

Custom DRDA client application

IMS Universal DL/I driver

IMS Universal JDBC driver

Message Flow for an IMS/DB Request


13

IMS Connect for IMS SOAP Gateway

Connect

Microsoft.NET Client

IMS

IMS SOAP Gateway

XMLAdapter

AdapterTask

Manager

Z/OS

IMSAppTCP/IPHTTP/SOAP

XML Converters

IMS WebService

32 0IVTNO DISPLAY LAST1

<?xml version="1.0"?><soap:Envelope> <soap:Body> <INPUTMSG> <in_ll>32</in_ll><in_zz>0</in_zz> <in_trcd>IVTNO</in_trcd> <in_cmd>DISPLAY</in_cmd> <in_name1>LAST1</in_name1> </INPUTMSG> </soap:Body></soap:Envelope>

<?xml version="1.0"?><soap:Envelope> <soap:Body> <cbl:OUTPUTMSG> <out_ll>93</out_ll><out_zz>0</out_zz> <out_msg>ENTRY WAS DISPLAYED</out_msg> <out_cmd>DISPLAY</out_cmd> <out_name1>LAST1</out_name1> <out_name2>FIRST1</out_name2> <out_extn>8-111-1111</out_extn> <out_zip>D01/R01</out_zip> <out_segno>0001</out_segno> </cbl:OUTPUTMSG> </soap:Body></soap:Envelope>

<INPUTMSG> <in_ll>32</in_ll><in_zz>0</in_zz> <in_trcd>IVTNO</in_trcd> <in_cmd>DISPLAY</in_cmd> <in_name1>LAST1</in_name1></INPUTMSG>

<cbl:OUTPUTMSG> <out_ll>93</out_ll><out_zz>0</out_zz> <out_msg>ENTRY WAS DISPLAYED</out_msg> <out_cmd>DISPLAY</out_cmd> <out_name1>LAST1</out_name1> <out_name2>FIRST1</out_name2> <out_extn>8-111-1111</out_extn> <out_zip>D01/R01</out_zip> <out_segno>0001</out_segno> </cbl:OUTPUTMSG>

93 0ENTRY WAS DISPLAYEDDISPLAY LAST1 FIRST1 8-111-11111D01/R01 0001

SOAP XML Byte array


14

IMS Connect API

IMS Connect

APIIMS

Connect API

IMS Connect

API

Client Application

IMS Connect

Windows or z/OS

OTMA

IMS AppIMS AppIMS App

z/OS

IMS


15

IMS Connect API…

A simplified callable interface for interaction with IMS Connect– Architected on top of the sockets layer

• Through a set of extensible profiles that define the connections and types of interactions to be performed– And a set of both high-level and low-level methods for performing those

interactions with IMS Connect

Addresses the complexities of writing RYO applications• Experience in TCP/IP socket programming

– Including connection management• Understanding the IRM header and the possible flags as well as settings • Familiarity with the IMS Connect application protocols and their impact on

all the possible types of interactions

See IMS Enterprise Suite for details


16

IMS SOAP

GATEWAY

IMS Synchronous Callout z/OS

IMS

Database

DB Services

OTM

A

TM/CTLServices

IMS

Connect

DataPower

WebSphereIMS TM

resource

adapter

Application

Program ICAL

MPP/JMP/IFP/BMP/JBP

OTMADescriptor

TCP/IPuser-written

Client


17

Synchronous Callout via IMS Connect

Capability– IMS applications can invoke external applications and synchronously

receive a response in the same IMS transaction instance – New DLI call - ICAL

• AIBTDLI call provides synchronous callout request– Timeout capability

• Control the time for synchronous callout processing– IMS Connect and OTMA handle buffer and segmentation internally


18

IMS Connect V11 Enhancements – GA in Oct/2009

• IMS/DB Access • Recorder Trace to BPE External Trace• Enhanced synchronous callout support• User Defined Message• TCP/IP Reconnect• Datastore Super Member• CM0 ACK Timeout Queue Name Override• Enforce Single SSL Port• Port Message Edit Exit• MAXSOC Warning• Display Command Enhancements

- SUMMARY option on VIEWHWS and QUERY MEMBER• Remove old OCO exits HWSIMSO0 and HWSIMSO1• Generated Clientid for ITMRA (IC4J)• Expand User Message Exit Parmlist HWSEXPRM


®


IMS 12 Enhancements


20

The following are enhancements for IMS Connect 12

– MSC over TCP/IP

– Type-2 Commands

– XML Converter Refresh

– Return RACF Return Codes to ICON Client

– RACF Userid Caching

– CM0 Nowait ACK for RYO Clients

– VIEWHWS Partial READ Status

– Sample Exit Object Code

– New Recorder Trace Records

– IMS TMRA Passphrase

IMS 12 – IMS Connect Enhancements


21

IMS 12 – OTMA remote ALTPCB output (TCP/IP PGM-PGM Switch) Uses one-way message communications

Managed by IMS Connect to IMS Connect communications– Without having to write client code or invoke additional gateways

ExistingMethod

IMS1 IMS Connect1 IMS2IMS Connect2Customer

Gateway ApplicationResume Tpipe

Tran output SendOnly

OTMA

XCF XCFTCP/IP TCP/IPISRT ALTPCB

DescriptorICON1

OTMA

IMS1 IMS Connect1 IMS2IMS Connect2

ISRT ALTPCB

DescriptorICON1

OTMA

OTMA

XCF XCFTCP/IPNewMethod

Example:


22

IMS 12 – OTMA remote ALTPCB output (TCP/IP PGM-PGM Switch)

SM01 - ICON1 - ICON2 - ICON3

IMS1 IMS2

ICON1 configSMEM=SM01



SM01

Msg1Msg2Msg3

Msg1

Msg2

Msg3 Note: Maximum of 8 IMS ConnectsCan participate in a super memberenvironment

ACKDescriptor DESC1:TMEMBER=SM01SMEM=Y

ICON1

ICON2

ICON3

ICON4

(Local IMS) (Local IMS Connect) (Remote IMS Connect) (Remote IMS)

– OTMA dynamically updates the super member list when a member of the group leaves or joins the group

Supermember Support


23

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

Request and response message communications – IMS Connect processes both the request and response messages as one-way

asynchronous messages

IMS 12 – MSC TCP/IP

IMS1

Local IMS Connect Remote IMS Connect

IMS 2Send socket

Receive socket


24

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

IMS1MSC

IMS3MSC

SCI TCP/IP

IMS2MSC

IMS Connect – ICON1

MSC

Driver

TCP/IPDriver

PLEX1 PLEX2

IMS Connect – ICON2

MSC

DriverTCP/IPDriver

SCI



25

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

MSC VTAM

MSC MTMMSC CTCIMSAIMSB

IMSC IMSD



26

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, IBM Management

Console for IMS and DB2 for z/OS, etc.

Can coexist with the previous WTOR and z/OS Modify commands– No changes to the existing command functionality

IMS 12 – Type-2 Commands


27

– 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)

QUERY IMSCON TYPE(type) NAME(name1, name2,...) FILTER(filter) SHOW(attribute(s))



28

– 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)

UPDATE IMSCON TYPE(type) NAME(name1, name2,...) START(condition1,condition2,…)

STOP(condition1,condition2,…) SET(condition1,condition2,…)



29

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

IMS 12 – XML Converter Refresh


30

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 supportOMUSR_PROLEV = OMUSR_PR03

IMS 12 – Return RACF Return Codes to ICON Client


31

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

IMS 12 – RACF Userid Caching


32

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’

IMS 12 – CM0 Nowait ACK for RYO Clients


33

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

IMS 12 – VIEWHWS Partial Read Status


34

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

IMS 12 – Sample Exit Object Code


35

New level of tracing adds records for TCP/IP and XCF sends and receives

– Requires the use of BPE External Trace support introduced in IMS 11

• Due to the amount of data that can be produced

ICONTR – TCP/IP ReceiveICONTS – TCP/IP SendICONIR – IMS OTMA ReceiveICONIS – IMS OTMA Send

IMS 12 – New Recorder Trace Records


36

APARs PM77494 (IMS 12) and PM85849 (IMS 13) added RACF Password Phrase

(Passphrase) support for IMS

IMS Connect supports Passphrase only for IMS TM Resource Adapter Clients

– Implemented by APAR PM77999 (IMS 12) or PM91312 (IMS 13)

IMS TM Resource Adapter APARs are also required

– PM78001 (IMS 12) or PM91898 (IMS 13)

IMS 12 – IMS TMRA Passphrase


®


IMS 13 Enhancements


38

The following are enhancements for IMS Connect 13

– ISC over TCP/IP

– RACF Event Notification Facility (ENF)

– WLM Notification for Sysplex Distributor

– SOMAXCONN Specification

– Expanded Recorder Trace Records

– XML Adapter Enhancements

– Use of CPOOL in XCF Exit

– Immediate Socket Listening Enhancement

IMS 13 – IMS Connect Enhancements


39

New option that supports TCP/IP network connectivity for ISC connections– Only supported for connections to CICS– Requires CICS 5.1– Supports both static and dynamic terminals

• Static terminal definitions – SYSGEN stage 1 TYPE, TERMINAL, SUBPOOL macros – DFSDCxxx PROCLIB member

• Dynamic terminal specification– Logon descriptors in the DFSDSCMx or DFSDSCTy PROCLIB member

– Leverages IMS Connect • Enhancements to the HWSCFGxx configuration member

– No IMS Connect user message exit changes • Uses CSL to communicate between IMS and IMS Connect

– Requires Structured Call Interface (SCI) and Operation Manager (OM)

IMS 13 – ISC over TCP/IP


40

Either IMS or CICS can initiate the request

IMS

12 3

456

INPUT INPUT Transaction

REPLY REPLY

IMSConnect

CICS

SCI TCP/IP

Initiating a CICS transaction from IMS using an ISC TCP/IP connection

INPUT

REPLY

tranOR

tran

Msg SwitchIMS

End User Processtransaction

IMS23

4 5REPLY REPLY

IMSConnect CICS

SCI TCP/IP

Initiating an IMS transaction from CICS using an ISC TCP/IP connection

CICSEnd UserProcess

transactionTx.

1Tx. (Start/Retrieve)INPUT

Transaction

6REPLY

IMS 13 – ISC over TCP/IP


41

IMS Connect has two new Type-2 commands so that Ports and Datastores can be

dynamically created

– CREATE IMSCON TYPE(DATASTORE)

– CREATE IMSCON TYPE(PORT)

– This can save a recycle of IMS Connect

IMS 13 – Dynamic Addition of Resources


42

IMS Connect 12 added the option to cache RACF ACEE’s

– Refreshing the cache required command input

RACF Event Notification Facility (ENF) broadcasts changes in the status of Userids,

e.g. Revoked

IMS Connect 13 will listen for ENF events and update its ACEE cache accordingly

IMS 13 – RACF Event Notification Facility


43

The Sysplex Distributor can route Connects in a round robin fashion or based on the

health of the target Port and the application listening on it

– But WLM needs an indication of the health of the Port and its applications

– IMS Connect 13 will report its health so that the Sysplex Distributor can make intelligent decisions

when routing Connect requests

IMS 13 – WLM Notification


44

When a TCP/IP Client sends a Connect request to TCP/IP it is passed to IMS Connect

– If another request is received and IMS Connect has not finished processing it the request will be queued in TCP/IP

– SOMAXCONN is the maximum number of Connect requests that can be queued in TCP/IP for an application

– Originally IMS Connect had hard coded this to 5

– APARs PM13818 (IMS Connect 10) and PM24904 (IMS 11) changed this value to MAXSOC

– IMS Connect 13 adds parameter TCPIPQ in the HWSCFGxx so that SOMAXCONN can be explicitly set

IMS 13 – SOMAXCONN Specification


45

The IMS Connect trace records only captured the first 672 bytes of the input and

output buffers

– Except for the ICONTS, ICONTR, ICONIS, and ICONIR records

– This was true for the original IMS Connect Recorder Trace and the BPE Recorder Trace

– In IMS 13 the BPE Recorder Trace will capture the entire input and output buffers if the trace level is

set to HIGH

IMS 13 – Expanded Recorder Trace


46

There have been several enhancements for the XML adapter environment

– The maximum number of converters has been increased from 100 to 2000

• There is also a new MAXCVRT parameter in HWSCFGxx

• Also implemented in IMS Connect 12 (PM64487)

– Converters can be displayed

• QUERY IMSCON TYPE(CONVERTER)

– IMS Connect will automatically reinitialize the LE environment after an XML converter ABEND

• This avoids a recycle of IMS Connect

IMS 13 – XML Adapter Enhancements


47

IMS Connect now uses CPOOL instead of STORAGE OBTAIN in the XCF Message Exit

– This is to improve performance

However, this adds 167MB to the region size in Extended Private

– Please plan accordingly

IMS 13 – Use of CPOOL in XCF Exit


48

Immediate Socket Listening Enhancement for Resume TPIPE Wait Forever

– If an IMS Connect Client issues a Resume TPIPE (Auto or Single Wait) with a timeout value of Wait

Forever (x’FF’) is it sent to OTMA and IMS Connect waits for a reply from OTMA

– If the IMS Connect Client goes away IMS Connect is not notified by TCP/IP KEEPALIVE because

there is no outstanding TCP/IP read

• The current Resume TPIPE stays in effect

• Queued Resume TPIPEs from other IMS Connect Clients are not used

– This problem is solved with IMS Connect APAR PM90777

– After sending the Resume TPIPE to OTMA, IMS Connect will also do a TCP/IP READ so it can be

sensitive to a KEEPALIVE response saying the Client has gone away

• IMS Connect can then issue Cancel Resume TPIPE to OTMA

IMS 13 – Immediate Socket Listening Enhancement


®


Summary


50

- Becomes the TCP/IP gateway to both IMS/TM and IMS/DB- Achieves high transaction rate - Supports IBM solutions, e.g., WebSphere, SOAP Gateway and DataPower client for IMS, and other vendor solutions to access IMS applications

z/OS

IMSIMSCONNECTCONNECT

Exit

XCF

IMS

Database

Transaction manager

IMS APP

Database

manager

OTM

A

IMS TM Resource Adapter

IMS SOAP Gateway

IMS Universal DBResource Adapter/Drivers

SCIOperationsManager

SCI

OD

BM

IMS ConnectAPI Clients

DataPower

Other vendor solutions

TCP/IP

IMS ConnectExtensions

IMS Connect is the integrated TCP/IP gateway to all of IMS

IBM Management Console for IMS and DB2 for z/OS

rug october 2014 - ims connect and what's new in v12 and v13

Technology