gtpm1m0c | TPF V4R1 Migration Guide: 3.1 to 4.1 |
The items in this checklist are intended to be used in sequential order for
a typical TPF system. Refer to this checklist while planning your
migration from the TPF 3.1 system to the TPF 4.1 system, and
developing your migration plan. Place a check mark (X) beside
each item as you complete it.
Your migration plan can address the following topics:
- Planning for the migration project:
- Review notes from previous migration plans and identify the need for a new
migration plan.
- Obtain commitment and dedication to the migration plan.
- Identify resources, including a project leader.
- Identify the implementation tasks.
- Document your existing environment (list hardware and software tools that
you now have and identify those that are not supported in the TPF 4.1
system.). See Operating Environment Requirements and Planning Information for more information.
- Identify the prerequisite hardware, software, and tools (IBM and non-IBM)
for the TPF 4.1 system. See Operating Environment Requirements and Planning Information for more information.
- Identify the network prerequisites. See Operating Environment Requirements and Planning Information for more information.
- Identify the hardware, programming, and data set requirements needed to
perform the migration tasks. See Operating Environment Requirements and Planning Information for more information.
- Identify new IBM Multiple Virtual Storage (MVS) data sets or changes
required to existing MVS data sets.
- Identify new TPF records, changes required to existing TPF records, and
TPF records that are no longer supported.
- Identify naming conventions for loadsets. For more information
about loadsets, see E-Type Loader.
- Identify which, if any, migration aids are available.
- Access the scope of the migration plan and the resources required.
- Access the impact of the migration plan and risks (including the impact on
application programs and performance).
- Address main storage considerations. See Operating Environment Requirements and Planning Information for more information.
- Identify the need for a fallback plan.
- Identify training and education requirements.
- Training:
- Application programmers
- Coverage programmers
- Operators
- Planning personnel
- System programmers
- System support personnel.
- Preparing the migration plan:
- Review the summary of new, changed, or obsolete functions, messages,
macros, and so on. See Summarizing the New, Changed, and Obsolete Interfaces for more information.
- Review the summary of program temporary fixes (PTFs) and cross
dependencies required for the TPF 4.1 system.
- Determine hardware changes (supported and not supported).
- Evaluate the changes in the operating system.
- Evaluate the network considerations.
- Estimate the capacity impact of the TPF 4.1 system (central
processing unit (CPU) utilization for a message, storage requirements, DASD
input/output (I/O) access, network controller, and link
requirements).
- Develop and document a migration plan.
- Develop a process for problem management; specifically, for migrating
and testing the TPF 4.1 system.
- Develop a test plan.
- Develop a fallback plan.
- Identify the migration tasks that you can do to the TPF 3.1 system
before receiving the TPF 4.1 system.
- Determine and develop training and education.
- Allocating the libraries (the TPF and the IBM Multiple Virtual Storage
(IBM MVS) data sets).
- Installing and starting the TPF 4.1 system:
- Define the I/O configuration.
- Generate the new TPF 4.1 system. See Generating the TPF 4.1 System for more information.
- System generation changes, changes to the system initialization program
(SIP) macros and inputs of SIP (for non-SIP customers).
- Initialize system parameters.
- Evaluating customized code (user modifications):
- Evaluate existing user modifications against the TPF 4.1 system to
determine whether any of the modifications do not need to be carried
forward; and if the modifications do need to be carried forward, be sure
to review that code. See Customizing the Code for more information.
- Evaluate new and changed user exits and ways to change the TPF 4.1
system. Determine whether programs using these exits need to be
changed. See Customizing the Code for more information.
- Review user exits, for example, determine whether there are user exit
alternatives to user modifications
- Evaluate changes to macros and control blocks that can affect user-written
code. See Customizing the Code for more information.
- Evaluate changes in the interfaces. See Summarizing the New, Changed, and Obsolete Interfaces and See Customizing the Code for more information.
- Evaluate new and updated programming functions that are available to
programmers. See Customizing the Code for more information.
- Migrating the network:
- Migrating the operating system:
- Diagnosing and debugging:
- Migrating the application programs:
- Testing Considerations:
- Test high-exposure operations.
- Test tools (IBM and non-IBM).
- Test the IBM Virtual Telecommunications Access Method (VTAM) test
prerequisites.
- Test application programs.
- Test using teleprocessing network simulator (TPNS).
- Test offline.
- Test operations, including any automation packages that you may have
installed. Use the online operations staff to test before the
migration.
- Test the utilities (Capture and Restore, Recoup, Online Load, Data
Collection, and so on).
- Conduct a system test.
- Conduct a regression test.
- Test communications.
- Test the inter-node communications.
- Test the network.
- Test any user modifications.
- Determine the impact of testing ongoing migration plans.
- Determine the potential impact on the IBM Virtual Machine/Enterprise
Systems Architecture (VM/ESA) system.
- Taking pre-cutover performance measurements.
- Cutting over the production system.
- Taking post-cutover performance measurements.
- Reviewing the migration plan:
- Make changes, as appropriate, to the migration plan.
- Document everything for use with future migration plans.