- Количество слайдов: 24
A S A P pplication ervices lliance rogram When Year 2000 Application Remediation… Just can’t wait ! ASAP Year 2000 Detail Presentation 98/12/15, Publication Number SWEO 0000 -0052.
The Year 2000 problem Two digits can not be used to represent a post 1999 year. ä The two digit year format previously used in dates is inadequate for twenty first century date representation… ä Errors will arise in ä Date Arithmetic ä Date Comparisons ä Sort Order ä Areas to address ä File formats ä User interfaces ä Programs Real year representation 2003 2002 2001 2000 1999 1998 1997 1996 1995 Two digit 03 02 01 00 99 98 97 96 95 05/31/02 = May 31, 2002 or May 31, 1902 ?
Scale of the Year 2000 challenge Some facts and figures ä 1 in 5 companies currently has no plan ä Addressing Year 2000 is mandatory, there are no exceptions. . . ä The Year 2000 problem effects any computer that uses dates ä There are only 500 days to go before it all has to work !
A few Relevant Questions Scoping the problem, putting boarders around Year 2000 ä When will the problem surface or become critical ? ä How do we fix it/them ? ä Can we find a low risk solution ? ä Can the changes be made before Jan 1, 2000 ? ä How do we ensure that applications will not fail in the next century? ä How do we ensure that current applications will still work after Year 2000 changes ? ä How do we identify the programs effected? ä How do we address co-existence of heterogeneous software environments ä Compliance of system software ä Compliance of third party software ä Large volume data conversion ä Archived historical data ä Interfacing Systems and Files ä Inadequacy of documentation ä Embedded date fields and use of date fields as keys
Is There a Quick Fix ? A ready made solution What is need for a successful Year 2000 program: ä Approach ä Tools SW ä Experience EO ä Resources
The Approach Strategy, Analysis, Convert, Test and Implement ! Cu Pa sto rti me cip r ati on ä Strategy Formulation e ity m al ge Qu ana M nt ä Analysis ä Conversion ä Acceptance Testing ä Retro-fitting Project phases with clear objectives n tio A a om ut Eff e ma ctive nag Pr em ojec ent t ä Implementation Ad Pr here oc es nce to s
The Strategy What do we have to consider when addressing Year 2000 Business Portfolio Analysis ä Areas in the overall IS environment ä Identify risks after categorizing software suitably ä Key processes Enterprise Level Planning ä Retire, replace or renovate option where appropriate. ä Build program Inventory with grouping and prioritization ä Review and document Year 2000 compliance strategy for interfaces to third party software and packages. Interact via Interviews and Workshops for each Application ä Prepare and complete a comprehensive inventory questionnaire ä Collect and verify inventory information Collect and verify information on standards, date patterns ä Assess extent of documentation Assess extent of test plan availability ä Identify action points for each application Build Estimates and Management Overviews ä Estimate schedules and budgets plan for each application ä Provide estimates for "Analysis Phase" for each groupings ä Provide budgetary estimates for the entire Year 2000 conversion effort ä Prepare a high-level project plan
Typical Issues and Unknowns What we know we don’t know !!!! ä What is the magnitude of the task ? ä How much resources will be required ? ä What would it cost ? ä Can this be undertaken by internal resources alone ? ä What do we do with third party packages ? ä What is the risk from external agencies passing interface data ? ä What about operating systems / networking and other critical system software ? ä How do we prioritize the software for conversion?
A few Guide Lines Fix the Year 2000 and minimize other re-engineering. User Interfaces No change recommended Programs ä All internal date fields to have 4 digit year Data Storage 3 Alternatives è è è 2 digit year Needs interpretation (e. g. < 50 means 20, > 50 means 19) Used where data file conversion is difficult No file conversion Ad hoc queries difficult 4 digit year Needs file conversion using a data migration tool Best option 2 digit year + century flag (0 could mean current century, 1 could mean the next century)
The Analysis It’s complicated and need a methodology to analyze the problem ! ä Scan all programs into repository äIdentify date fields in files based on ä User Input ä Naming conventions ä Date like patterns ä Treated like date field äIdentify impacted programs äDecide conversion method for files äPlan phasing of conversion
Analysis Process Analysis is a highly interactive with lots of feedback loops 1. Take inventory of programs Identify missing items 1. Finalize strategies New Date formats ID for multiple record types Conversion phasing 2. Scan source programs , JCLs, and load modules 3. Load into repository 4. Determine select criteria for date field Control Check 2. Quality Assurance and Inspection 5. Print reports containing list of probable date fields 6. Check reports 7. Quality Assurance 8. Confirm date fields The Client 3. Generate Final reports Check Bridge Files Dead Programs Date fields
Analysis Reports A summary that describe the various risks as numerical values ä Missing components report ä Possible date fields report ä Confirmed date fields report non-date fields report ä Equivalence report of confirmed date fields with unconfirmed date fields ä Undecided ä Impacted ä Clear fields report programs report Possible date fields report 34 programs scanned 421 dates detected 123 possible date 493 string scanned 23 unresolved strings
The Conversion ä Automated program conversion tool that identifies and changes date fields in programs: ä File ä User Interface ä Other ä Automated As per strategy Unchanged Always Four digit file conversion tool ä Accepts file formats (old, new) ä Generates file conversion programs ä Testing ä For operation in 20 th century (current) ä For operation in 21 st century (next) äAcceptance Y 2 K Methodology Electronic Business Software Organization
Conversion Process Conversion is a highly interactive with lots of feedback loops Pre-conversion Activities 1. Freeze program sources Prepare test data Save test files Documentation 2. Prepare detailed schedule for current batch Acceptance Testing Next Enhance procedures and Tools Review procedures and tool performance 3. Receive and install 15. Delivery 14. Final inspection 13. Optional Pre-acceptance test by client 4. Change source programs 12. Quality Assurance 5. Generate data conversion programs 11. Verify results 6. Set up test environment 7. Test programs and data conversion programs 8. Verify results Current century testing Next century testing 10. Test programs 9. Set up test environment
Acceptance Testing Source Code Converter Run time Simulators Data file Comparators PROGRAM TESTING ä Test data preparation with help from Data Converter Test Data Generator the customer ä Regression testing for this century ä Simulated regression testing for next century through 'data aging' ä Generation of data conversion routines ä Use of data simulation routines
The Implementation Move from the test system environment to the product environment ä Change required user interface date fields ä System testing and parallel runs ä Transition plan ä Development of bridge/wrapper ä Conversion of production data ä Communication with users ä Implement SWEO programs the programs in production using customer's change control procedures tion enta lem main Imp for Plan entry data ication l app
The Tools automation is an important labor saving part of Year 2000 remediation ä Source code scanners ä Repository ä CASEPAC ä Impact ä JCL Loader Repository Analyzer ä Load Module Analyzer ä Year 2000 filter ä Program generator (for data migration) ä Test data generators ä Current century testing ä Next century testing ä System ä Data date simulators file comparators
HP Platform Experience ä Made MPEi. X Year 2000 safe: ä MPE/ix operating system ä Databases (IMAGE) ä Networking products ä HP UX 10. X: ä HP UX operating system ä Databases (Oracle, SQL, ALLBASE/SQL) ä Networking products ä Open. View client and Web server products
Non-HP Platform Experience Completed Projects Customer Large insurance Company in Netherlands A US based health club A Power and Light Company in USA A veterinary Hospital information provider A government agency in USA Scope Impact analysis and Conversion and major enhancements Conversion and Y 2 K changes Y 2 K enhancement Conversion and Y 2 K enhancement Environment IBM AS/400, OS/400, DB 2/400, ILE COBOL/400, CL/400 IBM AS/400, DB 2/400, ILE COBOL/400 IBM ES-9000, DATACOM/DB, CICS, IDEAL, SAS IBM PS/2, SCO-Xenic, MDBS ADABAS Duration/Effor t 6 months/ 3 person years 15 months/16 person years 12 months / 9 person years 8 person years 5 person years Pilot Projects ä Analysis, conversion and implementation of a pilot system for a leading company in the Petroleum industry in USA (IBM Mainframe with OS/VS COBOL and IMS) ä Analysis and partial conversion for a leading telecommunications company in USA (IBM Mainframe with COBOL and IMS) ä Analysis, conversion and implementation for a leading insurance company in the USA (IBM Mainframe with COBOL and CICS) ä Analysis and conversion for a leading bank in Australia (IBM Mainframe with COBOL and IMS) ä Analysis and conversion for a leading publishing company in USA (IBM Mainframe with Assembler) ä Analysis On-going Projects n n Executing projects for n 10 Insurance companies n 7 Banks n 2 Publishing companies n 2 Supermarket chains n 1 Soft Drink Company Languages include n. COBOL II, COBOL VS 1, RPG, ASM, PL/1, SAS, EASYTRIEVE DB 2, IDMS, IMS for a leading department store in the UK (IBM Mainframe with COBOL and TELON) ä Analysis and conversion along with other re-engineering for a leading insurance company in USA (IBM Mainframe with COBOL and Assembler) Analysis for a leading bank in Scotland, UK (IBM Mainframe with “Sceptre” and Assembler)
Customer Example HP’s Operating Assets Information System (OASIS) Basic Environment: è HP 3000 MPE, COBOL, VPLUS, IMAGE, BRW è Other languages, Software: PASCAL, C, ALLBASE è No. of programs: è 88 No. of data sets and flat files: 36 è Total Lines of Code: 165, 000 è
Customer Example HP’s World-Wide Orders, Shipments and Invoices è Basic Environment: è HP 9000 HP-UX, COBOL, ORACLE, SQL, C , PERL SHELL è Other languages, Software: PJCL è No. of programs: è 2607 No. of data sets and flat files: 463 è Total Lines of Code: 550, 000 è
Project Examples Year 2000 Pilot Projects äA leading Oil Company in the USA ä A leading Communications Company in the USA ä A leading insurance Company in the USA ä A leading Australian Bank Year 2000 Conversions äA leading utility Company in the USA ä HP Oasis projects ä HP Order processing project
HP Value Proposition HP’s reliability, quality and engineering experience ! People Infrastructure ä Availability ä Connected of skills in HP platforms ä Availability of skills set in various hardware and software platforms ä Large pool of resources with ramp-up capabilities ä Accessibility to HP's technology groups Project Management ä Detailed Project plan ä Continuous monitoring ä Weekly status reports ä Issue Management ä Change Management to the world-wide HP network ä HP-3000, HP-9000 Competence Centers ä Other hardware environments (IBM, VAX) through partners ä Large investments in tools development ä Established project support structure Quality ä Internal and External QA ä Tools review and testing ä Acceptance testing of tools ä Review of manual changes ä Review of test results ä Final Inspection of all deliverables ä ISO model plans
Who to Contact SWEO is HP’s world wide software engineering operation for ASAP. SWEO - Americas Frank Willamson Tn : 447 1281 SWEO - Europe Gunther Moeller Tn : 778 6220 ASAP Marketing Program Manager : Mike Wardley, Tn 447 1169 SWEO - Japan Kazuo Okada Tn : 381 2395