November 20, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
Real-Time Enterprise Syndicate This
Print this article    Email this article    Talk Back!    Write to Editor
Mainframe Integration Patterns
05/22/2006
By Eric Roch, National Practice Director, Perficient

There are many ways to integrate distributed systems with the mainframe. The mainframe is an odd creature to integrate with because legacy applications were build on proprietary systems (like CICS) and protocols (like SNA). Open systems and more recently Service Oriented Architecture (SOA) make recently developed systems more interoperable.

ADVERTISEMENT
Our Popular Webinars
Insurance: Discovering the Missing Link of Business Architecture
SOA Infrastructure for any economic climate
Adapt with Agility - Web 2.0 in your Application Infrastructure
Open Source SOA and the Management Challenge: The ROI and Reliability of Open Source Composite Applications
Guaranteeing Agility in SOA and BPM with Process-Driven Data Integration
More Webinars

To understand mainframe integration, you have to understand the underlying data structures. We then can discuss integration techniques and patterns. The data structures are represented in the existing programs written for the mainframe, which are mostly COBOL programs.

COBOL Metadata Primer
COBOL is a structured language with a data division that defines data structures including external files (file description) and internal program storage (working storage). The file description defines the file structure to the COBOL program so we can use this COBOL definition to understand the existing data for integration purposes. We essentially use the COBOL file definition as a map to the mainframe data that is external to the distributed systems.

When working with mainframe data you will hear the term copybook used to describe file structures. The copybook is a reusable file description that the COBOL complier copies into the code at compile time – there is no late binding of file structures. Since files are used over and over the copybook was created as a means to allow the COBOL definition to be done once and copied into all the programs the access the file. If the file structure changes, all the programs using the copybook generally must be recompiled – some changes do not affect the data structure and might not affect other programs.

The copybook therefore becomes a source of metadata describing file structures on the mainframe. Since flat file structures do not have a data dictionary or system catalog description (like a database would), at times the copybook is the single source of metadata about the file structure. Mainframe databases may also have a data dictionary as a source of more metadata, but the copybook is still required for COBOL and can be used for integration purposes.

The copybook is hierarchical in structure. Data definitions can be elementary (with only one level) or grouped. Grouped structures are numbered with the super-group having a lower level number (such as the 01 and 05 levels below) and subgroups higher numbers.

01 ORDER-MASTER..
05 ORDER-MASTER-ID.
10 ORDER-TYPE PIC X(2).
10 COURSE-NUMBER PIC 9(4).
05 CUSTOMER-NAME PIC X(20).

Page 1

More Top Stories
SOA and Web 2.0 - Who Cares? Gold Club Protected
Approaching Cloudsizing (Part I of III) Gold Club Protected
Application Servers in Emerging Service Oriented Architectures Gold Club Protected
Insurance: Where SOA Means Business Gold Club Protected
Insurance Leveraging SOA and BPM to Change Gold Club Protected
Secrets of SOA Standardization Success Gold Club Protected
More Top Stories
Related News
Paradigm Posts Scientific Challenge to InnoCentive's Open Innovation Approach Seeks New Advanced Method for 3D Fracture Net Representation
NICHD Deploying Lombardi BPM Suite
Metastorm Growth and Leadership Continue
More News
Subscribe to our Newsletters
ebizQ Weekly Gold Club Update
Live Webinar Updates
Updates from ebizQ Partners
ebizQ SOA Update
ebizQ BPM Update
ebizQ Security Update
ebizQ BI Update
ebizQ Open Source Software Update
Virtual Show Newsletter
ebizQ Web 2.0 and the Enterprise
Your E-mail Address:
Create a Center of Excellence in SOA Governance
Date: Dec 02, 2008
Time: 12:00 PM ET
(17:00 GMT)

REGISTER TODAY!
Next-Generation BI
Date: Dec 03, 2008
Time: 12:00 PM ET
(17:00 GMT)

REGISTER TODAY!
Archived Webinars | Upcoming Webinars
  SOA Middleware: An Agile Framework for Fast, Flexible, Low-Risk Service Deployments
Originally, service-oriented architecture (SOA) concepts arose in response to demands for better ways to cost-effectively integrate large-scale...Learn More
ebizQ also recommends
 Formalizing Operational Governance: Ensuring the well-managed enterprise
 15-Minute Guide to Transactional Content Management
 EMC Forges Ahead In Document-Centric BPMS, The Forrester Wave Vendor Summary
 The Forrester Wave: Business Process Management for Document Processes
 From Vision to Reality: Bridging The HR And Benefits Universe With The Employee Communications Platform
More White Papers

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map

Live Chat