Optim for Legacy (Non-Relational) Application Retirement Middleware Options

by Matthew Simons, ILMG Practice Lead

When you’re helping your customer archive or retire data from mainframe data sources, you’ll need to make some informed choices during the sales process to determine which mix of products will address their needs properly.  This isn’t always as straightforward as it seems, especially when Optim and the Mainframe are involved.

 

When accessing non-relational data on a z/OS platform using Optim Distributed (LUW), you must use a middleware layer on the mainframe to present this "legacy" (VSAM, IMS, SEQ) and non-relational (CA IDMS, CA Datacom) data as a relational data source.  This relational translation is what can be linked to natively supported Optim DBMSs (Oracle and DB2 LUW are the most common).  

 

When selling and implementing Optim, there are two options for this middleware component of the solution:

• Classic Federation (which used to be known as WebSphere Classic Federation and is now InfoSphere Classic Federation)
• Optim Connect (a "blue-washed" version of third-party Attunity Connect).  

optim middleware options - conceptual process flow

Both products accomplish the same thing: Presenting non-relational data as relational data.  However, there are some conditions that make one option more desirable than the other. You should try to determine these conditions prior to giving the customer a software quote.

 

1. Does the customer have CA IDMS or CA Datacom?  If so, Classic Federation is currently the only middleware choice available.  There is no OptimConnect support for CA databases at this time.
2. For all other non-relational mainframe data sources* (VSAM, IMS, SEQ), you have a choice.  Both Classic Federation and Optim Connect support VSAM, IMS , and SEQ datasets.  So is it a matter of just choosing the product that has the cooler logo or cheapest price?  Not so fast!  Here’s where your choice really matters, and can save you from having to rework the customers entitlements after the sale:

 

Classic Federation has some limitations.  The following conditions must guide your choice of middleware when addressing VSAM, IMS, or SEQ datasets. Classic Federation cannot handle the following conditions in the record layouts (copybooks) of the data to be accessed:

• Occurs Depending On clauses (ODOs) that are NOT at the end of the record layout
• Complex redefines in the record layout.  From our experience with both middleware products, let's define "complex" as redefines within redefines and/or any cases where you have redefines where you are crossing from standard character PIC clauses to packed decimals.

 

If either of the above conditions exist, you must choose Optim Connect.

 

While these functional discrepancies exist as of the date of this post, having a solid understanding of the data that will be touched by this middleware layer is crucial to building the correct product list for your client (if you're the seller) or helping your seller to understand your specific technical idiosyncrasies (if you're the customer).  Making a switch in middleware engines after the software has been purchased is a cumbersome and time-consuming process that can be easily avoided with a bit of research and conversation during the sales cycle.

 

If you’re a client of IBM or Information Insights, a prospective user of Optim with legacy data, or an IBM sales or technical professional, contact us and we’ll share our experiences to help you make the right choices.

 

Matthew Simons – ILMG Practice Leader

Greg Marshall – Principal

*note:  the ISAM datasource was intentionally left out of this article.  If ISAM is under consideration, please contact us and we can discuss additional considerations.