Upload
buidat
View
219
Download
1
Embed Size (px)
Citation preview
IBM Software Group
May 2004 © 2004 IBM Corporation
Migrating from A to B Manual vs Automatic with IBM Software
Leverage your legacy applications
Pamela “PJ” BaronCategory Leader AD Tools [email protected]
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation2
The following terms are trademarks or registered trademarks of the InternationalBusiness Machines Corporation in the United States and/or other countries: ƒCICS, DB2, IMS, DFSMS/MVS, IBM, MQSeries, OS/390, S/390, z/OS
The following terms are trademarks of Computer Associates, Inc.:ƒEasytrieve, Easytrieve Plus
Preface
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation3
Today’s SessionsGoing from A to B
– Reasons to go– Manual efforts – Tools available
Futures discussed– Disclaimer: All statements regarding IBM future directions and intent are subject to change or
withdrawal without notice and represent goals and objectives only.
Polling Questions:– How did you hear of this Teleclinic– If this was informative would you want IBM to hold more of them?– Individually (Yes/No) do you want more information on any of the 4 tools
Question and Answer Session
IBM Software Group
May 2004 © 2004 IBM Corporation
How to Migrate from A to BLeverage your legacy applications
Dan BrownSr. Certified Enablement AD [email protected]
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation5
Migrate from A to B
Leverage your legacy investment and reduce total cost of ownership
Leverage people skills
Improve existing applications to extend their life and reach
Improve reliability and scalability – with Cobol and DB2
Automate migration from Easytrieve Plus to Cobol
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation6
Migrate A to B
Transform existing application assets for integration to variousplatforms, such as, AIX and OS/400
Provide an affordable high level development tool for COBOL Environment
Enable legacy applications to participate in e-Business environments
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation7
Migrate A to B
Introducing
CICS Business Event Publisher (BEP)
Debug Tool Utilities and Advanced Functions (CCCA)
Migration Utility (Guest Customer speaker)
VSAM Transparency
IBM Software Group
May 2004 © 2004 IBM Corporation
Modernize your CICS applications withCICS Business Event Publisher for MQSeries
Cornell KeeneNational CICS Sales [email protected]
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation9
Today's Business ChallengesUnconnected infrastructure investments
ƒProvide seamless integration with new business unitsƒLink packaged applications with legacy systems
Accelerated costs of managing disparate systems ƒIntegrate across heterogeneous islands of automationƒMitigate people and skill shortages
Increased industry and government regulations ƒIndustry standards
Reaching new markets with critical speed ƒSupport new standards like process automationƒMaintain system and asset security
IT projects take too long and cost too muchAchieving 'Time to Value' is critical to business success
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation10
Companies want to reuse their legacy applicationsCompanies want to utilise new business environmentsCompanies want to exploit new technology
Source: Gartner Group
Effective deployment means faster time-to-value
Databases
World WideWeb
WebServer
Transactions
SupplierNetworks
InternalSystems
CustomerConnections
LAN
Enterprise Infrastructure Is Complex...
Mission critical CICS App's
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation11
Event Driven ProcessingFast response to an event happeningNo change to underlying applicationsAllows for automation
Removal of latency from systemRemoval of manual and error prone actionsImproves accuracy and efficiencyStreamline business processing
Action taken when event detected‘Push’ not ‘Pull’ processReal time action and resultsObvious Examples
Credit card going to zeroDetect and send text message to owner to validate or provide additional banking
servicesSingle change to product price file at retail store headquarters
Detect and send update to distributed point-of-sale terminals and email to store managers
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation12
Unlocking ‘Legacy’ applications
Events already occur in existing applicationsTo facilitate their re-use would be very beneficialTo instigate a new business process would be IMMENSE!
But need non evasive technology to detect and releaseNo change to applications
But need to link to modern application environmentsSeamlesslyTo take advantage of new technologyTo take advantage of new business processes
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation13
CICS Business Event Publisher
What is it?What does it do?
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation14
Monitors events emanating from CICS appsBased on user-specified selection criteria
Creates messages from associated informationBased on user-specified message content rules
MQPUTs messages to MQSeries queueUser-specified
Queue name / queue manager nameMQSeries MQPUT options
CICS Business Event Publisher
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation15
Multiple Events monitoredA record written/read/updated/deleted/browse/unlock on a
CICS/VSAM fileA Temporary Storage (TS) Queue written/read/update/deleteA Transient Data (TD) Queue written/read/delete
Program linking to anotherInterval Control start
CICS Business Event Publisher Events
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation16
CICS Business Event Publisher configuration
CICS Transaction Server Data Space Server
MessageServer
CICS BEPcommandprocessor
GLUEs/ TRUEcommandprocessor
CICSdataspace
CICSRDBspace
WebSphere MQQueue Manager
Rules DatabaseVSAM file
WorkstationAdministrationClient
OperatorConsole
CICS 3270devices
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation17
Installation and Setup
Use SMP/E to unload distribution data setsAPF-authorize load libraryCreate started task procsDefine required data setsDefine CICS resourcesSet up parametersSecurity requirementsDefine MQSeries message queues
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation18
Download and install workstation clientFTP client code to workstationInstallShield installation process
Build rules/groups/listsStart data space serverStart message serverUpload groups/lists to hostRestart CICS
Up and Running in a few hours
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation19
Workstation Administration ClientWorkstation Administration ClientSample ScreensSample Screens
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation20
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation21
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation22
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation23
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation24
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation25
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation26
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation27
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation28
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation29
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation30
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation31
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation32
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation33
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation34
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation35
To extend use of existing CICS applications into new programming paradigms
• WebSphere MQ/BI• Application Integration
Why would customers use CICS BEP? To re-use existing applications through events to drive new business process and utilize new technology
•quickly•without changes to existing application code
Mainframe still the backbone of many business today - there are still a lot of important applications residing on these systems
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation36
Application Integration
Event driven processes allow for a new non evasive way of integrating applicationsThe Event the result of an application Action can be easily extracted for use in different or modern applicationsProvides a non-intrusive way to have legacy applications exploit new technology e.g. Web, mobile etc.Re-use of legacy applications in modern business environments ‘has just got a lot easier’! Application Integration can now be a reality for legacy applications
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation37
CICS BEP Positioning
Presentation
GUIApplication Logic
COBOL/CICS TS IBM WebSphere (J2EE)
Terminal Interface
WebBrowser
EAI/XML
App Adapters
Other enterpriseSystems
App's businessobjects
Data
Routines Batch Reports
App's online programs
CICS BEP
Java ServerPages (JSP's)
Enterprise JavaBeans (EJB's)
WebSphere MQ
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation38
Scenarios: Improved Customer Service; BankingCustomer Pain
The bank’s customers are unaware when they are about to go overdrawn and therefore incur banking charges and interest charges when they go into the red
The SolutionThe bank’s retail and business customers have accounts that are managed by CICS. With CICS BEP, the bank can now offer a service whereby customers can be contacted by text message to their cell phones, when their account reaches a certain level – for example $0. The customers themselves decide on what this rule should be. CICS BEP monitors the account balance and as soon it reaches £0 (or £10 or whatever) an MQ message is generated, and sent to a telephony integration broker. This creates an SMS message which is then sent to the customer’s cell phone.
The BenefitsInstant notification of account balance enabling customers to remedy any out of line balances before charges are applied. More satisfied customers who are less likely to move to another bank in the extremely competitive banking sector.
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation39
Scenarios: Improved Hospital Efficiency; HealthcareCustomer Pain
A Hospital was struggling with effectively managing the number of patients every day. Administration costs were high and customer satisfaction was at an all time low due to the average waiting time between the various different departments that patients had to visit in one day.
The SolutionCICS Business Event Publisher takes customer information and records from CICS and publishes the details into MQ. Customers who have to have a blood test, X-Ray and Checkup all in one day can have their records published in different formats. Processes can also be automated so that as soon as a doctor in one department has finished with a patient the records and results are sent on to the next department where the customers name is instantly added to the waiting list before he/she even gets there. On arrival the customer can see exactly where they are in the queue as it is published on a screen (included estimated waiting time). The customer is happy as they are moved through the system quicker, and the doctors have to spend less time on administration.
The BenefitsImproved processes, Less margin for error, Better service to customers, less administration increased customer satisfaction, , increased flexibility, leverages existing infrastructure and investment, based on the industry defacto standard for messaging.
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation40
Scenarios: Improved Customer Support; IT organization, any Industry
Customer PainIT manager and his staff are hearing about errors occurring with CICS applications too late. This results in lengthy application downtime and dissatisfied users
The SolutionAll application errors are detected by a unique program which is linked to all other application programs. CICS BEP evaluates all the Exec CICS Link commands in order to understand if the command has been issued for an application error. A "filter" CICS BEP exit routine is developed so that an "alarm message" is written to 2 MQ queues only if a given threshold of errors in a given time interval is exceeded. The first queue is then read by a, that sends the message to an "alarm console" and the second is read by computer/telephony integration layer which sends a SMS message to a specified cell phone. All these parameters (error codes, threshold, alarm and SMS messages, time interval, cellular number and so on) are defined in CICS BEP’s rules engine and the MQ messages through the CICS BEP administration workstation so that they can easily modified and tuned without any programming effort.
The BenefitsInstant notification of errors in CICS applications, both at the alarm console and on cell phone(s). Less application downtime, more satisfied users
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation41
Scenarios: Improved Operational EfficiencyStock Control, ManufacturingCustomer Pain
Inventory of parts in a car manufacturing process are not keeping up with demand – result is reduced production, lost orders, dissatisfied customers, lost business.
The SolutionInventory of parts and orders received are managed by two CICS applications. CICS BEP is deployed to monitor the number of cars on order, and compare it with the level of parts inventory. If the number of cars to be delivered within a specified timeframe indicates that the parts inventory will be exceeded in the near future, CICS BEP recognises that event as exceptional. When the level of under supply reaches a minimum predefined level, CICS BEP generates an MQ message which takes the form of an order, which is sent to the appropriate supplier via the business to business systems that have been established between the car manufacturer and its suppliers.
The BenefitsInstant conversion of a depleted parts inventory situation into an order for resupply. No disruption to production process, less orders lost due to delayed delivery
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation42
FutureAdditional event source connectors
DB2IMS
Terminal Control Statistics and reportingBi-directional eventsScripting language for rules
All statements regarding IBM future directions and intent are subject to change or withdrawal without notice and represent goals and objectives only.
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation43
SummaryCICS BEP provides a new approach to enabling legacy applicationsto participate in e-Business environmentsAllows legacy apps to drive new business processes quickly and without application changesAllows legacy applications to be easily integrated into new application Not a bridge/terminal emulator, but “complementary”Fills the “hole” between legacy apps and message brokers/integratorsHighly scalable, performance oriented designCICS BEP detects the specific event and creates the message WebSphere MQ provides the link to new business processes and new technology
IBM Software Group
May 2004 © 2004 IBM Corporation
Dan BrownSr. Certified Enablement AD [email protected]
Convert Old Unsupported Cobol Code to LEWith
Debug Tool Utilities AF V4 converter, CCCA
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation45
What Debug Tool Converter (CCCA) does:
Cobol and CICS Command Level Conversion Aid
Helps you convert old Cobol source:
• To Cobol 85 Standard Language
• Language Environment (LE)
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation46
How does Debug Tool Converter (CCCA) work
CCCA is an interactive system comprising ISPF panels
that enable you to access a batch (MVS) or foreground
Conversion application to:
• Define the type of conversion you want
• Submit a batch job (MVS), or run CCCA in foreground
to convert your source program
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation47
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation48
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation49
COBOL Source ConversionOldBOL to NewBOL
OS/VS COBOL had LOTS of undocumented extensions
85 Standard or 2002 Standard COBOL?We didn’t wait until 2002 to OO COBOL!
We will also support the new standard in the future
IBM COBOL Conversion Aid: continuous improvementKnown as CCCA, Earlier version was: 5785-ABJ
Over 80 user requirements added in Version 1 Release 2
CCCA Version 2 shipped in June 1998Additional improvements
Debug Tool Utilities AF V4 5655-L23, includes CCCA
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation50
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation51
What about compiler compatibility?Once you have programs that are 1985 standard you can change compilers at any time.
VS COBOL II NOCMPR2
COBOL for MVS & VM NOCMPR2
COBOL for OS/390 & VM NOCMPR2
Enterprise COBOL
You can compile any existing programs at any time with newer compiler and get the same results!
Migrate gradually at service/update time
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation52
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation53
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation54
Official DisclaimerHow long can you safely continue to run your OS/VS COBOL applications
without a newer library is difficult to predict.
As long as nothing in your environment changes, you can generally continue to run your OS/VS COBOL programs. However, if you change any other software in your environment, you could break any or all of your existing OS/VS COBOL applications
A perfect example of this was DFSMS/MVS V1R3. The VSAM component changed in such a way that a problem in the OS/VS COBOL library routine ILBOVOC was resulted. This problem is fixed in Language Environment for MVS & VM R5 but still exists in OS/VS COBOL. A future release of VSAM could again break all OS/VS COBOL programs in your shop.
This COBOL problem is tolerated in DFSMS R3 via DFSMS APAR OW19233.
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation55
What Will You Do?
DB2 V8
CICS TS 2.3Convert all your OS/VS COBOL
IBM Software Group
May 2004 © 2004 IBM Corporation
Convert CA-Easytrieve Plus to COBOL
IBM Migration Utility
Bob TeterProduct [email protected]
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation57
IBM Migration Utility Objectives• Automated conversion of Easytrieve Plus programs to COBOL• Ongoing program development using the Easytrieve Plus syntax• Affordable high level development tool for COBOL Environment• Capitalize on the operating efficiency of COBOL• Enable use of powerful debugging tools• Retain Easytrieve Plus ease of use• Leverage skills in both Easytrieve Plus and COBOL• Protect Investment in existing programs - don't force re-writes!• Minimize the labor required to locate, convert, test, and validate
Easytrieve Plus programs• Improve Total Cost of Ownership
IBM Migration Utility for z/OS
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation58
COBOL Source
COBOL Library
Run or Compile
COBOL Compile/Link,
Execute or SaveCompile
Link
IBM M igration Utility
Convert Easytrieve to COBOL
CompileLink
ExecuteExecute
OutputOutput
EasytrieveCom mand
Syntax
Output
1IBM Migration Utility: Converts CA-Easytrieve Plus to COBOL
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation59
IBM Migration Utility for z/OS
• Easytrieve Plus Syntax • Easytrieve Plus Instructions• Easytrieve Plus Macro Language• SAM/VSAM/QSAM and SQL/DB2, TOTAL DB, IMS (DL1)• Sort and Synchronized File Process• REPORT Statement • REPORT Exits
Fully Supported Easytrieve Plus Features:
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation60
IBM Migration Utility for z/OS
• Choice of Dynamic or Static I/O• Support for PDS/PDSE Access• JCL Automatically Generated and Adjusted• Support for COBOL Functions in Assign Statement• Optional Overflow Tag• Rolling or Fixed Date Threshold• Support for LE COBOL, COBOLII, COBOL/390
Special Features:
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation61
IBM Migration Utility for z/OS
• CBLCNVRT Macro• Converts COBOL Copy Books To Easytrieve format• Can use COBOL Copy Books in Easytrieve Programs
• COBOL Capability• COBOL statements can be imbedded in Easytrieve Programs• COBOL programs can be generated with COPY statements• Supports INSPECT, INITIALIZE, and STRING COBOL instructions in native Easytrieve Plus syntax
• EZTCNVRT Macro• Converts Easytrieve Plus layouts to COBOL Copy Books
• Portability• Programs can be generated to run on VSE and VM• COBOL can be generated and ported to other platforms
Special Features Cont’d:
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation62
IBM Migration Utility for z/OS
•Most Frequently Used Toolkit Features:• SYSDATE and SYSDATE-LONG (including date mask options)• Date Conversion Routines • Conversion of COBOL Layouts • SQRT, RANDOM, NUMTEST, DIVIDE macros • LOW-VALUES and HIGH-VALUES• Other Toolkit support possible but not currently available
Support for Selected CA-Easytrieve Toolkit Features:
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation63
IBM Migration Utility
Available in Version 1.1
MassConversion
Utility
Discovery Utility
Available in Version 2.1
Parallel Test Utility
Auto Compare Utility
JCL Adjuster Utility
Easytrieve Plus Migration Project Flow
PromotionProduction
4. QA / Promotion
FailPass
Usually 90% or more compile cleanly
Conversion
Remediate
JCLCOBOL
2. Conversion1. Discovery/Preparation
Batch
Obsolete
Ad Hoc
Discovery
JCLSMF
LibrariesControlcards Testing
FailPass
3. Verification
Usually 90% or more produce essentially identical output
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation64
IBM Migration Utility for z/OSCommon QuestionsQ1: Are there Easytrieve Plus programs that can't be converted? A1: Not so far! Some may require changes to the Easytrieve source for COBOL compatibility but none were found "unconvertible".
Q2: Do I need to keep my CA-Easytrieve Plus license? A2: No - once you've validated that the converted COBOL produces the same result, you have no further need for this license. You can even write new programs in Easytrieve Plus syntax and convert them with the IMU, so long as you retain your IMU license.
Q3: Can the Migration Utility handle "classic" Easytrieve? A3: As it stands today, the Migration Utility works with Easytrieve Plus. However, IBM is looking for a partner to work with on support for "classic" Easytrieve.
Q4: How quickly can my programs be converted? A4: This depends on the number of programs and the amount of resource available, but 1,000 to 2,000 over 3-4 months is reasonable; up to 5,000 within 5-6 months is also feasible.
Q5: What are some large scale examples of successful migrations?A5: 1. Large US Information Services and Publishing company - 2600 jobs in 3 months (8/2003);
2. Large US Office Supply Retailer - 4350 jobs in 6 mo. - incl. automation tools devel. (5/2003);3. Large Midwestern University - 200 jobs in 45 days (5/2002)
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation65
IBM Migration Utility for z/OSCommon Questions (Continued)Q6: How can we tell how many programs we have? A6: Since we have so many, we aren't sure! Use of the new Discovery Utility can help locate Easytrieve programs
Q7: How can we efficiently run the conversion of my CA-Easytrieve Plus programs? A7: The new Mass Conversion Utility is a batch program that automatically "feeds" a list of programs to the IMU for conversion.
Q8: What is the expected (average) accuracy of conversions to COBOL? A8: With recent improvements in syntax-handling, most customers are seeing 90 to 98% accuracy without changing any Easytrieve code.
Q9: How can we efficiently test the programs once they are converted? A9: Most programs can be run in a parallel test mode with the new Parallel Test Utility, which submits jobs in both Easytrieve Plus mode and in the converted COBOL, capturing the results.
Q10: Once parallel test jobs have been run, is there any way to automatically compare the outputs? A10: Once the outputs have been captured, the Automatic Comparison Utility can be used to validate the results of most converted programs.re there Easytrieve
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation66
IBM Migration Utility for z/OS
• Assessment• Training (Highly Recommended):
• 5 days• Up to 20 students per session• Migration Utility as a conversion / development tool• Parallel Testing / Autocompare Utilities
• Remote consultation services• Conversion Services
Available Services:
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation67
IBM Migration Utility for z/OS
Web Info:http://www.ibm.com/software/awdtools/migration/
Additional Information:
IBM Software Group
May 2004 © 2004 IBM Corporation
CICS VSAM TransparencyVSAM to DB2 migration without tears
Tony SkinnerTransaction Processing Consultant IBM Certified System Designer [email protected]
L I G H T Y E A R
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation69
Why convert from VSAM to DB2?Expose field-level data hidden inside 'opaque' VSAM records:
SQL, ODBC, JDBCmodern, end-user query toolsdata mining...
Make mainframe data accessible from 'any' platform type:distributed applicationsweb applications...
Continuous ('24 x 7') availability:concurrent update, with integritymultiple CICS region - eliminate MRO overheadbatch and CICSmultiple batch streamsproduction work and housekeeping
Exploit relational integrity, and other DB2 capabilities...
}
L I G H T Y E A R
- else Transactional VSAM, Sysplex, Coupling Facility…
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation70
CICS VSAM Transparency for z/OSo program # 5697-I76
The CICS VT approach: low risk, with accelerated delivery – No changes to existing application programs– One-time data migration from VSAM to DB2– Migrate one VSAM file at a time– Supports extensive data re-engineering during the migration process– Testing is simplified– Working data exists in one place– Value is delivered quickly
L I G H T Y E A R
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation71
Execution Process Flow
Applicationprogram
CALL VSAM I/O
Without CICS VTWith CICS VT
VSAM
VSAM DB2
CICS VT(run-time)
Applicationprogram
CALL VSAM I/O
FileFile Table
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation72
Migration Process Overview1. Analysis1. Analysis
6. Migrate data6. Migrate data
7. Test7. Test
5. Automatic mapping
5. Automatic mapping
2. Design database2. Design database
3. Interactive mapping
3. Interactive mapping
4. Re-engineering4. Re-engineering
1.
6.
7.
5.
2.
3.
4.
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation73
MappingVSAM record
PART-NUMBER
Key
DESCRIPTION QTY-ON-HAND PROD-CODE
Alt . Index
DB2 row
PART-NUMBER DESCRIPTION QTY-ON-HAND PROD-CODE
VSAM Field t o DB2 Column relat ionship using COBOL copybookMapping performed aut omat ically or using int eract ive ISPF dialogues
1.
6.
7.
5.
2.
3.
4.
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation74
Redefined record structure
1.
6.
7.
5.
2.
3.
4.
key + common columnsEquivalent DB2 Tables
DB2TAB_COMMONDB2TAB_SUBTYPE_ADB2TAB_SUBTYPE_BDB2TAB_SUBTYPE_C
key + subt ype X(A) columns
key + subt ype X(C) columnskey + subt ype X(B) columns
Common f ields... X Subt ype X(A) f ields
Subt ype X(B) f ields
Subt ype X(C) f ields
VSAM Record
Key
CICS VT exit rout ines FBE: t o read t he appropr iat e _SUBTYPE t able based on t he value of 'X' IRD: required for updat e processing based on t he value of 'X'
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation75
Data Re-engineering example
1.
6.
7.
5.
2.
3.
4.
Exploit Field Build Exit (FBE) t o enhance usabilit y of DB2 version of dat a: - separat e component s of complex codes- t ranslat e codes t o meaningful values- and so on...
VSAM recordPART-NUMBER DESCRIPTION QTY-ON-HAND PROD-CODE
PART-NUMBER DESCRIPTION QTY-ON-HAND ITEM-TYPE
0 1 2 3 4 5 6 7
RESTOCK-TYPE
0 0 0 1: aut omat ic0 0 10 : schedule0 0 11: special-order0 10 0 : ...
0 0 0 1: piece-par t0 0 10 : assembly0 0 11: sub-assembly0 10 0 : ...
DB2 row
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation76
Performance Cost
Nat ive VSAM
Nat iveDB2
VSAM
CICS VT
DB2
VSAM
CPUt ime
Typical CICS VT 'cost ': < 10 % of DB2
DB2 'cost ' propor t ional t o:# columns / row# t ables / f ile
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation77
Performance
Handling VSAM f iles is only one component of t ransact ion 'cost '.
CICS VT overhead applies only t o t he convert ed VSAM f ile calls.
Good business case for DB2? --> Even bet t er case for CICS VT.
CICS Tx 'A'2 VSAM calls
VSAM
CICS Tx 'B'10 VSAM calls
VSAM
CICS Tx 'C'10 0 s of VSAM calls
VSAM
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation78
CICS VT vs. Conventional Method
Convent ional migrat ion effor t f rom VSAM t o DB2
(t ypically measured in man-years)
Analysis & Design Dat a migrat ion Dat a Test ing Reprogramming Program Test ing
Analysis & Design Dat a migrat ion Test ing
VSAM t o DB2 using CICS VT
(of t en measured in man-mont hs)
Proport ional t o number of f iles/ t ables(usually measured in 10 s or low 10 0 s)
Proport ional t o number of programs(usually measured in 1,0 0 0 s)
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation79
Why CICS VT?Faster implementation, and significantly lower risk than other solutions;
proven technique based on 7 years of DL/2 (IMS-DB2) experience
Take full advantage of DB2 capabilities
Data opened up for flexible reporting and cross-platform access
Single source of production data, available to all with consistent Quality of Service
Single DBA skill set; relational skills (DBA & programming) readily available
Preserves the investment in legacy application programs
New applications can be 100% DB2 based
L I G H T Y E A R
Tony [email protected]
IBM Software Group
May 2004 © 2004 IBM Corporation
Migrating from A to B Manual vs Automatic with IBM Software
SUMMARY
Pamela “PJ” BaronCategory Leader AD Tools [email protected]
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation81
How to Obtain Further Information on the IBM Tools?
Contact Pamela “PJ” Baron at [email protected] with request.
Include in request:Company NameYour NamePhoneState located Product(s) of interest
One of two ways …
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation82
Summary
Going from A to B– Reasons to go– Manual efforts – Tools available
Futures discussed– Disclaimer: All statements regarding IBM future directions and intent are subject to change or withdrawal without
notice and represent goals and objectives only.
Polling Questions:– How did you hear of this Teleclinic– If this was informative would you want IBM to hold more of them?– Do you want more information on (yes or no)
– CICS Business Event Publisher MQ (CICS/MQ and soon DB2, IMS/MQ)– Debug Tool Utilities AF V4 (Old COBOL to LE)– Migration Utility (CA Easytrieve Plus to COBOL)– VSAM Transparency (VSAM to DB2)
IBM Software Group
Migrating from A to B Manual vs Automatic with IBM Software © 2004 IBM Corporation83
SummaryGoing from A to B
– Reasons to go– Manual efforts – Tools available
Futures discussed– Disclaimer: All statements regarding IBM future directions and intent are subject to change or withdrawal without
notice and represent goals and objectives only.
Polling Questions:– How did you hear of this Teleclinic– If this was informative would you want IBM to hold more of them?– Individually (Yes/No) do you want more information on any of the 4 tools
Question and Answer Session