cics ts v4 technical overview - the conference exchange · 2012-08-06 · 4 cics transaction...

CICS TS V4.R2 Technical OverviewMonday, August 6, 2012: 1:30 PM-2:30 PM

Leigh ComptonIBM Advanced Technical Skills

[email protected]

2

© IBM Corporation 2011. All Rights Reserved.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide.

Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at

www.ibm.com/legal/copytrade.shtml.

Copyright and Trademarks

3

Session Agenda• Focus Areas

• CICS Explorer

• Functional areas and benefits

• Events• Java• Connectivity• Management• Scalability

• Summary

4

CICS Transaction Server: The Story So Far…

Broad Range Of New & Enhanced CapabilitiesBroad Range Of New & Enhanced Capabilities

,,,

V1

Web

V2

Java

OTE

V3

SOA

20022002 2Q20092Q2009 201020102005200519991999

Feature Packs

SupportPacs

V4.2

Events

Java

Connectivity

Management

Scalability

V4.1

Events

Web 2.0

2Q 20112Q 2011

Focused VersionsFocused Versions

5

CICS Transaction Server for z/OS Version 4

� Business and Systems Events

� Lifecycle Management

� Development and Deployment Tooling

Events

New and enhanced capability across five major

technology areas

� Axis2 Web Services

� Web 2.0

� IPIC Support

Connectivity

� Transaction Tracking

� Workload Management

� Security Enhancements

Management

� 64-bit Applications

� Multithreaded Server

� OSGI Management

Java� More Threadsafe

� Better Concurrency

� 64-bit Exploitation

Scalability

6

Statements of direction

• IBM intends in the future for IBM WebSphere MQ for z/OS to provide Group Units of Recovery (Group UR) support for IBM CICS Transaction Server for z/OS (CICS TS)

• IBM intends in the future to deliver a Dynamic Scripting FeaturePack for use with CICS TS V4.2

• IBM intends a future release of CICS TS to discontinue support for both:• Session beans using Enterprise Java Beans (EJB)• The Java pool infrastructure

Available 30 Sept 2011

Available 25 Nov 2011

7

CICS Explorer

8

CICS Explorer• “The New Face Of CICS”

• A new user interface for interacting with CICS

• Built on the Eclipse Rich Client Platform

• Rich UI allows more sophisticated methods of interaction

• Offers similar functionality as existing interfaces

• Web UI, CICS resource changes• And some functionality you can't do

through existing interfaces

• Transaction Tracking, Event Binding Editor, OSGi bundle deployment

9

CICS Explorer…• Simplify CICS

• Single user interface for CICS & CICSPlex SM• Common, intuitive, Eclipse-based tooling environment for new and

experienced • Architects and Developers• System administrators and System programmers• Operators

• Integration platform - Value of the sum exceeds the part• First class cross tooling integration• Consistent views across tooling• Consolidated tooling with a central view into the CICS world • Supports CICS runtime, CICS tools, CICS connectors, plus other IBM and third-

party software

• Software Development Kit (SDK)• Provides separately packaged plug-ins for any Eclipse-based environment • API allows 3rd parties to extend or integration existing capability• Layered architecture allows Eclipse-independent components to be used in any

environment

10

Events

11

What is an event?• An event…

…is anything that happens …has a name and usually some data (its payload)…is produced and responded to asynchronously

• Simple event processing……is the processing of a single event, meaningful in itself; not an

abstraction or composition of other events

• Complex event processing……is detecting and responding to patterns of events

• Business Event Processing…… is using simple and complex event processing to detect and

respond to business-impacting situations across the enterprise

12

What is Business Event Processing?

Event

Pos Purchase

Event

No meter signal

Event

GPS Signal

Business Context

2nd purchase in a week and total purchases this year > $1000

Business Context

Third consecutive period without signal

Business Context

Calculated arrival > 30 min over SLA

Action: Offer loyalty program membership before customer leaves the store

Action: Trigger automated troubleshooting process

Action: Phone customer to re-arrange delivery

“Turn insight into action”

13

CICS and Business Events• Event processing addresses the need for agility

• Modern businesses must react quickly to circumstances• Decision makers need reliable, timely information

• CICS systems run an enormous amount of existing business logic• With an Event-based approach

• Potential to gain insight into the processing in CICS• Introduce additional extensions to applications

• CICS TS V4.1 allows you to emit business events from existing applications • Supporting changing corporate policies • Without the need to change the applications• In a dynamic, de-coupled fashion• And driving your choice of destination

• WebSphere Business Monitor• WebSphere Business Events• CICS application• MQSeries, …

14

CICS TS V4 Event Processing

CICS TS for z/OS V4

Existing Business Logic

CICS Event Processing

Event CaptureFiltering

EnrichmentFormatting

Routing

Extensible

SecuredMonitored

etc.

CODE

NOT

CHANGEDCaptured

Events

Development and Deployment Tools

Events

WebSphere Business Events

WebSphere Business Monitor

Other Event Consumers

15

CICS TS V4 Event Processing …

• EP Search capability• Available in the CICS Explorer

• Enter the name of the “thing” you have changed and EP search will tell you which event bindings may be affected

• ‘Things’ include:• CICS resource names• Language Structure names• Language Structure field names

• Searches event bindings in the CICS Explorer workspace and those installed in CICS regions that Explorer is connected to

16

Java

17

CICS TS V4 Java

• Support for 64 bit JVMs• Both Pooled JVMs and JVMServers

• Java stack and heap are now allocated in above the bar storage• Allows more Pooled JVMs per region

• Java 6.0.1• IBM zEnterprise optimized version of Java 6 JVM

• Exploits new z196 instruction set• Improved GC• Improved JIT• Significant performance improvements

• Support for 31 bit JVMs dropped

18

JVMSERVER resource

What is a JVM server…?

• A new CICS resource containing a long-running JVM.• The strategic direction of Java in CICS

• Pooled Java will be discontinued in the future • A JVM that serves multiple transactions concurrently.• A JVM in which applications/tasks run as OSGi bundle s.

JVMTask

Task

Task

OSGi bundle/Application

OSGi bundle/Application

19

JVM server vs. existing Java support?

CICS (JVM server)

JVM

Task

Task

Task

CICS (pooled Java)

JVMTask

Task

Task

JVM

JVM

JVMs must be restarted to effect changesDynamic update and replace of modules

Difficult, convoluted to share data and state.More standard Server model (+ data-sharing)

MAXJVMTCBS, SIT parmMAXTHRDTCBS (automatically calculated), up to max of 1024 per region

J8 (CICS key), J9 (User key)T8 (CICS key)

Java Program Isolation(concurrent, multi-threaded, up to 256 threads per JVM server)

Pool of JVMs - each serves only a single task.Single JVM - serves many tasks (reduced storage)

20

CICS TS V4 Java…• OSGi

• OSGi development and packaging now required to deploy CICS applications to a JVM server

• Existing CICS Java applications using main() method linkage can run unchanged if wrapped in an OSGi bundle

• All JVM server applications must be thread-safe and can’t use stabilized CICS EJB or CORBA functions

• Equinox used as OSGi implementation

• CICS Explorer SDK• Provides CICS Java development tool kit for use in any Eclipse 3.6.2 IDE • Can be used to develop and deploy applications for any release of CICS

(CICS TS V3.2 onwards)

• Java projects are developed as Plug-in Projects and then packaged in a CICS bundle and exported to zFS

21

Connectivity

22

Axis2 for Web Services

• Axis2

• Java-based open source web services engine

• Axis2 Java SOAP message handlers

• Axis2 SOAP processing and some of the CICS pipeline processing become eligible for zAAP offload

• Application handler written in Java• Executes in a JVMSERVER

• Eligible for zAAP off-load processing

• XML data conversion can be off-loaded

Pipeline Controller

Applicationhandler

handler

handler

handler

handler

handler

handler

handler

handler

SOAP handler

CHANNEL

23

CICS Java applications as Web Services

• Deploy Axis2-style web services:

POJO as provider web services• Improve integration of CICS and Java applications for in-

bound Web services• Pipeline can call directly to CICS service provider applications

written in Java• Suitably written Java applications can interact directly with

the Java object model of incoming messages, rather than containers used by traditional languages• Avoids cost of serializing to XML and parsing the XML• Axis2 pipeline handler will already have built the object model

for the message

24

Web Service Addressing• Defines transport neutral mechanisms to address Web Services

• Facilitates message transmission through networks• Consists of a SOAP Header describing

• Endpoint Reference• Uniquely identify the service requested

• Message addressing properties• Convey information about message relationships• Provide information on where messages are to be directed

Client

Interface

Web

Service

Reply To:Reply To:Reply To:Reply To:

endpoint

CICS2 to:to:to:to:

endpoint

CICS1

requestrequest

response

Web

Service

Interface

responseto:to:to:to:

endpoint

CICS2

CICS2

CICS1

25

CICS XML Extensions

• New Markup Language Domain (ML)• Uses the z/OS systems services parser

• Eligible for off-load to zAAP engines• Parsing storage acquired from 64 bit storage

• Generic XML Mapping• EXEC CICS TRANSFORM command

• XML to Data• Data to XML

• New XML Assistants • Generates a language structure from a schema• Generates a schema from a language structure

26

Web 2.0: A Philosophy, not just a Technology

• An important trend in delivering software applications

• An enabler for richer web applications• New business models• Peer-to-peer user participation• New technologies • Interactive filtering, presentation, data entry

• A combination of core technology components• Rich user experience (maps, grids, animation, D&D, etc)• Loose-coupling, composite applications via reuse and “mash-ups”• Technologies (SOAP, REST, JSON, ATOM, Java, PHP, Dojo, Ruby,

Python, Perl, etc)

27

CICS Dynamic Scripting Languages FeaturePac

• Embed Zero programming model into CICS on z/OS• Script CICS assets using Groovy or PHP.• Build a web 2.0 AJAX presentation layer onto CICS Programs.• Expose CICS assets as RESTful services.

• Tight integration with existing CICS application assets and data• Easy and efficient access to COBOL assets• Inheriting CICS run time Quality of Service

• ProjectZero Features for CICS• Script in PHP, Groovy, Java• Respond to HTTP requests• Call CICS commarea programs from PHP or Groovy• Access DB2 databases from PHP, Groovy, ZRM• Call any JCICS interface from PHP or Groovy• Manage units of work (commit/rollback)• Use event handlers to easily create RESTful Web Services• Access any Java class from PHP code using the PHP/Java Bridge

28

Atom feeds from CICS• What is an Atom Feed?

• Protocol and XML format for content publishing• Provide XML based feed of updated content• Process is known as syndicating a feed

• Follow-on to Real Simple Syndication (RSS)• Simple publish/subscribe implementation

• Polling model• Based on http support

• Described by two Internet Request for Comments• The Atom Syndication Format

• Targeted at producing feeds• RFC4287: (Dec 2005)

http://tools.ietf.org/html/rfc4287

• The Atom Publishing Protocol • Targeted to creating and updating resources• RFC5023: (Oct 2007) http://tools.ietf.org/html/rfc5023

29

IP Interconnectivity • Continuation of the CICS IP interconnectivity strategy

• Provide a new transaction IP communications protocol for connectivity between and into CICS

• Long term plan to provide CICS with IP choice for most of the CICS programming model

• Enhancements to support 3270 Transaction Routing• BMS, security and monitoring support• Shippable terminals supported

• Enhancements to Function Shipping• File Control• Transient Data• Temporary Storage

• Enhancements to Asynchronous Starts• ATI over IPIC supported

30

CICS Support for IPv6• IPv6 Background

• Evolution of the current version of IP (IPv4)• Work started on this in the early 90’s

• IPv4 has 32 bit addresses• IPv4 address – 10.67.122.66• Practical limit: less than 1 billion useable global addresses

• IPv6 has 128 bit addresses• IPv6 address – 2001:0db8:0000:0000:0000:0000:1428:57ab• No practical limit on global addresses• 2128 addresses• 5 x 1028 addresses for each of the 6.5 billion people alive today

• Allow for IPv4, IPv6 or host names in:• Resource definitions• Application Programming Interface• Systems Programming Interface• User Replaceable Modules• Global User Exits• Monitoring Records

31

HTTP Enhancements• Inbound Throttling

• Limit the number of connections to a specific TCPIPSERVICE• Implementation

• MAXPERSIST parameter on the TCPSERVICE definition• NO | 1-65535

• Outbound Connection Pooling• Enables reuse of outbound http sessions

• CICS web services applications• http EP adaptors• CICS web support applications

• Requires the use of a client mode URIMAP to enable• New SOCKETCLOSE attribute specifies:• Length of time the socket will be kept in the pool• No pooling is achieved by specifying zero for a expiry time

32

DB2 Thread Reuse Limit• Long running protected or unprotected DB2 threads

• Can cause buildup in the DB2 EDM pool• This can lead to storage constraint problems• May force DB2 into a “short on storage” condition

• New REUSELIMIT option on the DB2CONN resource• Will limit the number of times a thread can be reused

• Range of 0-10000, default 1000• Applies to both protected or unprotected threads

• New PURGECYCLE lower value (5 seconds)• New DB2 statistics

• Thread reuse limit• Number of times reuse limit reached (pool and entry threads)

33

WebSphere MQ support • Updated CICS-WebSphere MQ Adapter to support WebSphere MQ V7

• Supports 12 new MQ V7 API commands for message properties, publish subscribe, and asynchronous consume

• Also available via APARs PK89844 and PK66866 for CICS TS V3.2

• Support for Group Attach• Allows common resource definitions for CICS regions

• Support for WebSphere MQ Group units of work recovery• Will be able to attach to any local WMQ server in the queue sharing

group and have it resolve outstanding UOWs• This option can be used only when running a release of WebSphere MQ that

supports group unit of recovery for CICS and when the GROUPUR attribute has been enabled in the WebSphere MQ queue managers.

34

Management

35

CICS TS V4 Management Enhancements• Transaction Tracking

■ As the name implies....• Follow the path of a transaction through the system

• Provide means to track and correlate the progress of• Simple linearly routed tasks, asynchronous tasks, spawned CICS tasks

• Across distributed CICS systems including over CICS managed TCP/IP

• Extends and uses Association data• Previous hop, association data and origin data for both MRO and IPIC connections

• Expose tracking information via CICS Explorer

• Helps to answer questions like• Why is this transaction suspended?• Where was this transaction routed to?• What was the point of origin for this transaction?

36

CICS TS V4 Management Enhancements…

• Sysplex optimization to significantly reduce workload batching effects

• Exploitation of z/OS coupling facility for CPSM region status data• “Near real time” Sysplex-wide focus on target region status• No impact to “non-optimized” WLM

• Optimized WLM routing enabled by configuring a Region Status Server• Uses CF Data Table to hold Region Status information

• SOS, MaxTask, System or transaction dump in progress, Current Tasks• Shared by all routing regions (in the Sysplex)

• Percentile goals• CICSPlex SM WLM support for percentile goals

• Support in CICSPlex SM for all new resources, statistics, etc

37


• Password Phrase Support• Background

• Introduced in z/OS 1.8• 14-100 character password phrases

• Updated in z/OS 1.9• 9-100 character password phrases if ICHPWX11 installed

• Alternative to traditional passwords• Improved system security - harder to attack• Easier to remember

38


• CESL transaction• New transaction to sign on to CICS using a password or a password phrase• Supports both 3270, Sequential and Console devices

• Does not support 40x12 size screens

• CESN will remain unchanged• CEDF transaction

• Changed to hide passwords or password phrases • Additional functions that support password phrases

• CMCI• CICS Explorer• Web Interface• Web Services• LDAP (supports a long password)• CPSM Web User Interface

39


• z/OS Identity Propagation initiative to provide asserted identity for end-to-end distributed security•Logically tie together distributed end-user identities with z/OS userids•Enhance the ability for z/OS applications to participate centrally in SOA solutions•Function will require z/OS 1.11

• ID Context Propagation allows an end user's identity to be propagated through to CICS •Currently, the end users' identity is lost before the request gets to CICS

40

Current Implementation of User Identity and Mapping

CICSLDAP

WebSphere Application

Server

CICS

SMF

RACF

z/OS sysplex

RACF UseridDistinguished Name & Realm

� RACF user-ID

Audit RecordRACFuser ID

User’s original identity discarded,

RACF user-ID selected

Audit records do not show who the user is; accountability difficult to determine who the originating user is

•Distributed identity information is lost when request sent to RACF

Static RACF userid must be associated with the application

Identities often ‘asserted’ so that passwords do not need to be managed

Custom security code often created to map distributed identity to RACF userid

41

Implementation of Identity Context Propagation

CICSLDAP

WebSphere Application

Server

CICS

SMF

RACF

z/OS sysplex

RACF Userid +Distributed identityDistinguished

Name & Realm

WAS infrastructure and distributed Identity remains unchanged

� RACF user-ID� DN & Realm

Audit Record

Security mapping rules control relationship of distributed identities to

RACF userids

CICS and RACF accounting includes distributed identity

Distributedidentity

• Propagates end user’s identity from WAS through to CICS

• Scenarios for identity propagation

� Inbound to CICS from WebSphere Application Server through CICS TG

� Inbound to CICS as a WS-Security header element in a Web services request

� Propagating out across IPIC and MRO connections between CICS systems

42

CICS TS V4 Management Enhancements…• Resource definition signature attributes added to CICS resources

• Signature data added when you add/alter a resource • DEFINESOURCE• DEFINETIME• CHANGETIME• CHANGEUSRID• CHANGEAGENT• CHANGEAGREL

• Resource installation signature attributes added to CICS resources• Signature data added when you Install a resource

• INSTALLAGENT• INSTALLTIME• INSTALLUSRID

43

Scalability

44

CICS TS V4 Scalability Enhancements

• CICS and 64-Bit• CICS Transaction Server for z/OS V4 contains significant changes to

the CICS domain architecture that exploits the underlying z/Architecture for 64-bit addressing and provides the infrastructure for CICS domains to utilize and exploit 64-bit addressing mode.

• Enables CICS to remove some of the limitations that affected scalability and availability by delivering large address spaces

• CICS can now make use of 64-bit virtual storage to increase capacity by supporting a larger number of concurrent users and transactions, as well as keeping up with virtual storage demands

45

CICS TS V4 Scalability Enhancements…

• Domain Re-architecture • Some CICS Domain components running AMODE(64)

• Kernel Domain• Storage Manager Domain

• Including some code which manages CICS storage below the bar

• Trace Domain• Message Domain• Lock Manager Domain• Temporary Storage Domain• Monitoring Domain

46


• 64-bit exploiters• CICS Trace Domain

• Internal Trace Tables above the bar• Internal Trace Table in 64-bit storage only …

• if CICS Transaction Isolation inactive (TRANISO=NO) or• if CICS running on z/OS 1.12 with APAR OA34311 applied

• Transaction Dump Trace Table in 64-bit storage• Trace control blocks in 64-bit storage

• Auxiliary and GTF Buffers moved from 24-bit to 31-bit storage

• 64-bit GTF Trace (OA32611 required for z/OS 1.11 & 1.12)

• CICS Message Domain• CICS Message tables are above the bar (subject to

TRANISO restriction)

47


• 64-bit exploiters…• CICS Dump Domain

• 64-bit storage SDUMP support• Requires z/OS APAR OA32271 (z/OS 1.11 and 1.12)• Use is now made of z/OS IARV64 DUMPRIORITY option

• CICS Monitoring Domain• Association Data control blocks are above the bar (subject to

TRANISO restriction)

• CICS Java• Updated to 64-bit JVM (Java 6.0.1) for Pooled and

JVMServer• 31-bit Java not supported

48

CICS TS V4 Scalability Enhancements…• 64-bit exploiters…

• CICS Temporary Storage Domain• MAIN TS above the bar (subject to TRANISO restriction)

• Limiting MAIN Temporary Storage use• SIT parameter: TSMAINLIMIT={64M|amount}

• Maximum is 32G, not greater than 25% of z/OS MEMLIMIT • Many Temporary Storage control blocks above the bar

• Automatic TS Cleanup• EXPIRYINT can be specified on a TSMODEL definition• Applies to MAIN TS Queues and non-recoverable AUX TS

Queues• Does NOT apply to:

• Remote TS Queues, Recoverable AUX TS Queues • Shared TS Queues, CICS internal TS Queues• TS Queues that don't match a TSMODEL

49


• DFHMIRS is now Threadsafe• Supplied definition now specifies CONCURRENCY(THREADSAFE)

• IPIC transformers are now threadsafe• Non IPIC code remains non threadsafe

• Only requests function shipped over IPIC will run on an Open TCB• File Control• Temporary Storage• Distributed Program Link

• If the target program is defined as threadsafe and the mirror already on an open TCB

50

CICS TS V4 Scalability Enhancements…• CICS-DBCTL interface will use OTE when connected to IMS 12

• At connect time CICS & IMS determine if each other can support OTE• With IMS 10 & 11

• CICS-DBCTL TRUE enabled as QUASIRENT• Toleration APAR PM31730 (IMS 10), PM31729 (IMS 11)

• With IMS 12• CICS-DBCTL TRUE enabled as OPENAPI • Exploitation APAR PM31420 is required

• At General Availability of CICS TS V4, IMS 12 is available through a Quality Partnership Program (QPP).

• For more information: http://www.ibm.com/software/data/ims/

51

CICS TS V4 Scalability Enhancements…• Commands now made threadsafe

• EXEC CICS SYNCPOINT• EXEC CICS SYNCPOINT ROLLBACK• EXEC CICS RESYNC• JCICS

• COMMIT and ROLLBACK methods• Non-threadsafe Recovery Manager clients will force a switch to the QR

TCB• Switch to QR made by the Recovery Manager• Examples:

• MRO, Transient Data, etc• Recovery Manager clients may force an internal switch to the QR TCB

• Switch to QR made by the client• Examples:

• File control for BDAM files• RMI for a quasi-reentrant TRUE

52


• Other APIs made threadsafe• QUERY SECURITY• SIGNON, SIGNOFF• VERIFY PASSWORD, VERIFY PHRASE• CHANGE PASSWORD, CHANGE PHRASE

• EXTRACT TCPIP, EXTRACT CERTIFICATE

• All CALL and EXEC CICS Name Counter Server commands• Built in functions for DIGEST and DEEDIT

53


• New SPI commands that are threadsafe:• INQUIRE CAPDATAPRED, INQUIRE CAPINFOSRCE, INQUIRE

CAPOPTPRED• INQUIRE EPADAPTER, SET EPADAPTER• INQUIRE OSGIBUNDLE, INQUIRE OSGISERVICE• INQUIRE TEMPSTORAGE, SET TEMPSTORAGE

• Existing SPI commands made threadsafe:• INQUIRE CLASSCACHE• INQUIRE JVM• INQUIRE JVMPOOL• INQUIRE JVMPROFILE• PERFORM CLASSCACHE• PERFORM JVM POOL• SET CLASSCACHE• SET JVMPOOL

54

CICS TS V4 Scalability Enhancements…• CICS historically has allowed use of 8 LSR pools

• In the days of local DLI, DLI used the other 8• When local DLI was removed, CICS File Control was not changed

• Since z/OS 1.4, DFSMS have allowed up to 256 lsr pools per address space.

• In CICS TS V4 we will allow use of 255 LSR POOLs ( 1-255)• Will not use pool 0

• Potential performance optimization where greater subdivision of files across LSR POOLs is required• e.g. Place highly-used files in their own LSRPOOL

55

Summary

• Discover Faster

• React Quicker

• Compete Better

Events

• Perform Better

• Manage Easier

• Innovate Quicker

Java

• Connect Easier

• Lower Costs

• Manage Better

Connectivity

• Understand More

• Control Better

• Manage Easier

Management

• Process More

• Lower Costs

• Perform Better

Scalability

Delivering a smarter transaction processing

experience for everybody

56

ibm/developerworks/cicsdev

facebook.com/IBMCICS

twitter.com/IBM_CICS

youtube.com/cicsfluff

youtube.com/cicsexplorer

themasterterminal.com

twitter.com/IBM_System_z

CICS-L listserv (Google it!)

Google CICS or check us out at:

ibm.com

/cics

57

System z Social Media• System z official Twitter handle:

• @ibm_system_z

• Top Facebook pages related to System z: • Systemz Mainframe• IBM System z on Campus• IBM Mainframe Professionals• Millennial Mainframer

• Top LinkedIn Groups related to System z:• Mainframe Experts Network• Mainframe• IBM Mainframe• System z Advocates• Cloud Mainframe Computing

• YouTube• IBM System z

• Leading Blogs related to System z:• Evangelizing Mainframe

(Destination z blog)• Mainframe Performance Topics• Common Sense• Enterprise Class Innovation:

System z perspectives• Mainframe• MainframeZone• Smarter Computing Blog• Millennial Mainframer

cics ts v4 technical overview - the conference exchange · 2012-08-06 · 4 cics transaction...

Documents