(C) Copyright IBM Corp. 1995, 1997
The Year 2000 and 2-Digit Dates: Guide
INDEX
CHAPTER 7. MIGRATION CONSIDERATION FOR YEAR2000 TRANSITION . . . 7-1
An Example Plan for Migration . . . . . . . . . . . . . . . . . . 7-1
Perform Migration . . . . . . . . . . . . . . . . . . . . . . . . 7-4
To accomplish a successful migration and eliminate your current Year2000 exposures, you will need to follow a well-architected migration plan and prepare to execute that plan prior to actually performing the migration. This section provides an outline that you can use as a checklist of those steps that will help you plan, prepare, and execute your migration. Note that some steps might not be necessary for your specific environment, and your environment might require steps other than those listed here.
1. Plan for Migration
o Determine the sequence of steps needed for migration
o Review the migration procedures with your system administration staff
and your end-user community
o Determine the resources/time required for migration
o Assign individuals/organizations to each migration step
o Document the migration sequence and responsibilities
o Develop a schedule for migration of the new system to reach
production mode
2. Examine all changed data that use new/changed date format
o Determine the source of the new data in the existing systems
o Determine the data that can be converted automatically
o Determine the data that must be converted manually
3. Design bridges/interfaces among packages and reusable modules to maintain
compatibility, if needed
o Design bridges/interfaces to application packages, if needed
o Design bridges/interfaces to reusable application systems, if needed
o Design bridges/interfaces to old systems that will coexist with the
new systems, if needed
o Design tests for the verification and validation of these bridge
facilities, if needed
4. Design procedures for manual data conversion
o Update documents/procedures that will be used for manual data entry
o Determine checking mechanism for the accuracy and completeness of
manually entered data
o Design the new screens with new date format for manual entry of new
data and review with your end-user community
o Design/update the software to load the manually prepared data into
the new system
o Run a rehearsal of the manual data entry and estimate the impact of
the new data format on data entry time
5. Design procedures for automated data conversion
o Design new software or use automated tools for automated data
conversion
o Determine a checking mechanism for the accuracy and completeness of
automatically converted data
o Design recovery procedures for conversion of data errors caused by
missing data
o Estimate the resources and time for automated data conversion
6. Develop the data conversion systems
o Develop subsystems to convert existing data
o Develop subsystems for the entry of new data
o Develop bridges/interfaces to old systems which will remain in
production
o Develop bridges/interfaces to application packages and reusable
modules
o Verify and validate the accuracy of the data conversion systems
7. Plan the hardware installation for new system, if needed.
This might include upgrading your operating system to a machine capable
of running Year2000-ready software as well as other system components
such as storage resources. Additional storage (DASD or tape) that could
double your current needs might be required to provide:
o Backup of the original source code prior to your Year2000 conversion
o Space to store the new source libraries following your Year2000
conversion
o Space for the new versions of the system software while it is being
installed and tested, while the old versions are still in production
o Backup of the original data bases prior to your Year2000 conversion
o Space for the new versions of the data bases (which will require
additional space due to expanded date fields) while the old versions
are still in production
o Test file space
o New JCL (and PROC) libraries to handle situations such as: sort
problems, system parameter changes, program name changes, data set
name changes, while the old JCL (and PROCs) are still in production
o Backup of your current load libraries
o Space for the new load libraries while the old versions are still in
production.
8. Plan for final system testing
o Determine the testing strategy
o Develop the detailed test plan and schedule
o Determine the types of tests to be conducted on the new system
o Plan the testing environment
- Design the migration tests for the systems and applications
- Determine what testing software or tool(s) will be used for each
type of testing
- Determine what testing libraries will be used for each specific
set of programs and data
- Install needed testing software. For example, test data
generator, test utilities, debugging utilities, and so on.
- Build test libraries, and test data
- Coordinate the testing with your development team and your system
administration staff
9. Documentation and training
o Update your 'corporate standard guideline'
o Update your technical documentation. For example, development
guidelines and testing handbooks
o Update the production procedures
o Update the user documentation
- Update the on-line documentation, including HELP screens, on-line
manuals, computer-aided training, and so on.
- Test the on-line HELP and training aids with your end users to
evaluate the acceptance of the new on-line information
- Update all hard-copy documentations to reflect changes and review
those documentation with your end users
- Plan and conduct training program to smooth the migration process
1. Update production procedures, if necessary
2. Install the Year2000-ready production system environment
o Coordinate with vendors for the hardware installation, if needed
o Install the hardware of the new production system, if needed
o Coordinate with system programmers/operators for installation of the
Year2000-ready software
o Install the Year2000-ready system/vendor/application software on the
new production system
3. Perform data conversion process
o Load existing data into the new system's databases
o Execute the data conversion programs or automated tools for data
conversion
o Load manually-prepared data through data entry
o Integrate the existing and converted data
o Test the integrated data to verify data integrity
4. Perform final system/migration testing
o Plan the sequence in which separately developed subsystems will be
tested and verified in reasonable combinations.
o Verify that the portions of the system that have no changes still run
properly as changes are made to other portions of the system
o Verify that the program handles all its transactions correctly and
remain stable for a defined period of time
o Verify that the system can accept input from, and provide output to,
other systems with which it interfaces as interfaces change
o Verify end-user acceptance of the new system to certify the system as
acceptable for production.
5. Activate the new system in production
o Switch the new system to production mode
o Run the new system in parallel with the old system
o Phase out the old system as the new system becomes stable
6. Migration review
o Monitor and evaluate system performance, throughput, and reliability
o Determine what system tuning is needed based on system status records
o Track and evaluate user acceptance of the new system
o Determine and document what system and application function
enhancements are needed
o Plan and schedule the system and application function enhancements
o Coordinate system function enhancements with vendors
o Design and develop required in-house application-function
enhancements
o Determine when the system and/or application enhancements will be
applied
o Apply the enhancements, once available, to the new system