ASAP Year 2000 Detail Presentation 98/12/15, Publication Number SWEO 0000-0052.

S ervicesS ervices

A llianceA lliance

A pplicationA pplication

ProgramProgram

When Year 2000 Application Remediation… Just can’t wait !

The Year 2000 problemThe Year 2000 problem

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

200320022001200019991998199719961995

030201009998979695

05/31/02 = May 31, 2002 or May 31, 1902 ?

Two digits can not be used to represent a post 1999 year.

Real year Two digit representation

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 !

Scale of the Year 2000 challengeScale of the Year 2000 challengeSome facts and figures

A few Relevant Questions A few Relevant Questions Scoping the problem, putting boarders around Year 2000

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

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?

Is There a Quick Fix ?Is There a Quick Fix ?

Approach Tools Resources Experience

What is need for a successful Year 2000 program:

A ready made solution

SW

EO

The ApproachThe ApproachStrategy, Analysis, Convert, Test and Implement !

Strategy Formulation Analysis Conversion Acceptance Testing Retro-fitting Implementation

Automation

Adherence to

Process

Quality

Management

Project phases with clear objectives

Eff

ecti

ve P

roje

ct

man

agem

ent

Customer

Participation

The StrategyThe StrategyWhat do we have to consider when addressing Year 2000

Build Estimates and Management OverviewsEstimate schedules and budgets plan for each application Provide estimates for "Analysis Phase" for each groupings Provide budgetary estimates for the entire Year 2000 conversion effortPrepare a high-level project plan

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 patternsAssess extent of documentation Assess extent of test plan availabilityIdentify action points for each application

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.

Business Portfolio Analysis Areas in the overall IS environment Identify risks after categorizing software suitablyKey processes

Typical Issues and UnknownsTypical Issues and UnknownsWhat 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 LinesA few Guide LinesFix 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 difficultNo file conversionAd hoc queries difficult

4 digit yearNeeds file conversion using a data migration toolBest option

2 digit year + century flag (0 could mean current century, 1 could mean the next century)

The AnalysisThe AnalysisIt’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 ProcessAnalysis ProcessAnalysis is a highly interactive with lots of feedback loops

1. Take inventory of programs

4. Determine select criteria for date field

5. Print reports containing list of probable date fields

6. Check reports

7. Quality Assurance

8. Confirm date fields

2. Quality Assurance and Inspection

1. Finalize strategiesNew Date formatsID for multiple record typesConversion phasing

Identify missing items

3. Load into repository

2. Scan source programs , JCLs, and load modules

3. Generate Final reports The Client

Control Check

CheckBridge Files

Dead ProgramsDate fields

Analysis ReportsAnalysis ReportsA summary that describe the various risks as numerical values

Missing components report

Possible date fields report

Confirmed date fields report

Confirmed non-date fields report

Equivalence report of confirmed date fields with unconfirmed date fields

Undecided fields report

Impacted programs report

Clear programs report

Possible date fields report 34 programs scanned

421 dates detected123 possible date493 string scanned23 unresolved strings

The ConversionThe Conversion

Automated program conversion tool that identifies and

changes date fields in programs:File As per strategyUser Interface UnchangedOther Always Four digit

Automated file conversion toolAccepts file formats (old, new)Generates file conversion programs

TestingFor operation in 20th century (current)For operation in 21st century (next)

Acceptance

Y2K Methodology Electronic Business Software Organization

Conversion ProcessConversion ProcessConversion is a highly interactive with lots of feedback loops

13. Optional Pre-acceptance test by client

Pre-conversion Activities 1. Freeze program sources Prepare test data Save test files Documentation

2. Prepare detailed schedule for current batch

3. Receive and install

4. Change source programs

5. Generate data conversion programs

6. Set up test environment

7. Test programs and data conversion programs

8. Verify results

9. Set up test environment

Review procedures

and tool performance

Enhance procedures and Tools

10. Test programs

11. Verify results

12. Quality Assurance

14. Final inspection

Current century testing

Next century testing

15. Delivery

Acceptance Testing

Next

Acceptance TestingAcceptance Testing

Test data preparation with help from the customerRegression testing for this centurySimulated regression testing for next century through 'data aging'Generation of data conversion routinesUse of data simulation routines

Data fileComparators

Source Code

Converter

Run timeSimulators

Data Converter

Test DataGenerator

PROGRAMTESTING

The ImplementationThe ImplementationMove from the test system environment to the product environment

Change required user interface date fields

System testing and parallel runs

Transition planDevelopment of bridge/wrapper programs Conversion of production data Communication with users

Implement the programs in production using customer's change control procedures

SWEO

Implementation

Plan for main

data entry

application

The ToolsThe ToolsTools automation is an important labor saving part of Year 2000 remediation

Source code scanners

Repository Loader CASEPAC Repository Impact Analyzer JCL Analyzer Load Module Analyzer

Year 2000 filter

Program generator (for data migration)

Test data generators Current century testing Next century testing

System date simulators

Data file comparators

HP Platform ExperienceHP Platform Experience

Made MPEiX 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 productsOpenView client and Web server products

Non-HP Platform ExperienceNon-HP Platform Experience

Customer Scope Environment Duration/Effort

Large insurance Company in Netherlands

Impact analysis and Conversion

IBM AS/400, OS/400, DB2/400, ILE COBOL/400, CL/400

6 months/3 person

years

A US based health club

Conversion and major enhancements

IBM AS/400, DB2/400, ILE COBOL/400

15 months/16 person years

A Power and Light Company in USA

Conversion and Y2K changes

IBM ES-9000, DATACOM/DB, CICS, IDEAL, SAS

12 months / 9 person years

A veterinary Hospital information provider

Y2K enhancement

IBM PS/2, SCO-Xenic, MDBS

8 person years

A government agency in USA

Conversion and Y2K enhancement

ADABAS 5 person years

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 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)

Completed Projects Pilot Projects

On-goingProjects

Executing projects for 10 Insurance companies7 Banks2 Publishing companies2 Supermarket chains1 Soft Drink Company

Languages include COBOL II, COBOL VS 1, RPG, ASM,PL/1,SAS,EASYTRIEVEDB2, IDMS, IMS

Customer ExampleCustomer ExampleHP’s Operating Assets Information System (OASIS)

Basic Environment:HP3000 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 ExampleCustomer ExampleHP’s World-Wide Orders, Shipments and Invoices

Basic Environment:

HP9000 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 ExamplesProject 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 PropositionHP Value PropositionHP’s reliability, quality and engineering experience !

People Infrastructure Connected to the world-wide HP networkHP-3000, HP-9000 Competence CentersOther hardware environments (IBM, VAX)

through partners Large investments in tools developmentEstablished project support structure

Availability of skills in HP platformsAvailability of skills set in various

hardware and software platformsLarge pool of resources with ramp-up

capabilitiesAccessibility to HP's technology groups

Detailed Project planContinuous monitoringWeekly status reportsIssue ManagementChange Management

Project Management Internal and External QATools review and testingAcceptance testing of toolsReview of manual changesReview of test results Final Inspection of all deliverablesISO model plans

Quality

SWEO is HP’s world wide software engineering operation for ASAP.

Who to ContactWho to Contact

SWEO - JapanKazuo OkadaTn : 381 2395

SWEO - EuropeGunther MoellerTn : 778 6220SWEO - Americas

Frank WillamsonTn : 447 1281

ASAP Marketing Program Manager : Mike Wardley, Tn 447 1169