Migration Tools

The document summarizes the tools and processes used by XMS for migrating software from one environment to another. It discusses the XMS repository for storing migration information, source analyzers for identifying programming languages, program packaging for grouping related objects, source comparison tools, source translators for converting code between languages/platforms, generators for automating repetitive tasks, screen capture and data preparation for testing, code coverage measurement, data testing to ensure functional equivalence, data comparison, and database comparison tools. It also mentions implementation support for transitioning migrated programs to production.

Uploaded by

usf69

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

33 views

Migration Tools

Uploaded by

usf69

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

You are on page 1/ 2

MIGRATION TOOLS

Repository
All of the information extracted from your source libraries is stored in a database called the XMS Repository or simply the XMS
database, which is an open SQL Server industry standard relational database. XMS keep a complete inventory of all sources, data
files and databases to be migrated. This will ensure that all is known and that all of these objects are migrated.
Source Analyzers
XMS analyzers are modules specialized by language (more than thirty IM! M"S! "M! "S#! AS$%%! AIX! &LL! G'OS! I'L!
&NIX! 'OOL! (L)! (LI! '(L)! ASS#ML*! +ORTRAN! R(G! GA(! GMA(! SAS! NAT&RAL! A,L! I,#AL! AI,A! T#LON!
(A'AS#! ARIAN#! G#N#ROL! RAMIS! +O'&S! NOMA,! R#XX! #AS*TRI#"#! S*SI+! IMS-,! ,LI! ,L)! I,S.! I,MS!
I,MS-R! ,,S! SQL! ,.! (ROT##! QM+! A,AAS! ,ATA'OM! S*SAS#! ORA'L#! 'A/&NI"#RS! IMS-,'! I,MS-,'! ,M$T(!
T,S! T(0! T'AM! 'I'S! 'A/S'1#,&L#R! 'ONTROL/M! O('! (SS! 222!. The language identification is automatic or directed by
the file name extension. "ach time necessary, a ne3 analyzer is developed, added to the existing ones and available for use after
installation.
(rogra4 (ac5aging
This function is reserved for specially trained personnel. #t concerns the pac5aging (batc6ing! of co6erent subsets of objects being
batched together for the purpose of 4igrating objects from one environment to another. Sets of related sc6edules! 7obs! progra4s!
subroutines! copies! includes! user 4acros! user e8its! 9iles! databases! areas! tables! records! ... are grouped toget6er.
Source 'o4parison
XMS comparison tools are used to co4pare the versions of programs installed in the different sites, showing the significant
differences bet3een environ4ents. A first step is executed from an $%& &'( table of the source lines or 9or4atted state4ents to
select only the necessary sources for a detailed co4pare.
Source Translaters
XMS Transformation tools are used to optimize the automated translation and procedures. )sing special so9t3are and management
techni*ues, XMS decreases the time needed for S'1#,&L#R! :'L, (ROGRAM! S'R##N! R#(ORT! +IL# and ,ATAAS#
conversion.
:'L Generators
XMS +enerators automates many of the repetitive task associated with generating 7ob control language procedures! generating
database unload! 9or4at and load progra4s2
Screen 'apture ,apturing the before and after screen i4ages while executing the scenario, in a readable text format for the following tests stage.
,ata (reparation
XMS offers effective techni*ues and software for e8tracting or generating small, manageable test 9iles. These files ensure efficient,
comprehensive testing and avoid costly reruns during implementation. XMS not only helps to produce comprehensive test data, but
also helps to reduce data preparation time. $%& add code to the existing programs to ensure that data and results are captured. #n
T- systems, this will capture screen input and response. #n batch systems this will capture only records that cause a different path
to be taken.
'ode 'overage
(ercentage o9 e8ecution is 4easured during preparation or, as re*uired, after translation. "ven if the output files match, the
program may still be inade*uately tested if the test data exercise only a fraction of the program code. XMS therefore identifies any
une8ecuted code, making it possible to prepare additional data. .or each program XMS show 6o3 4uc6 code has been e8ercised
so that extra, necessary test data can be added.
,ata Testing .or every test, XMS co4pares the output of the trans9or4ed progra4 with the converted output of the original progra4 and
flags any mismatches for the correction. /e make sure that the 4igrated progra4s will produce output 9unctionally e;uivalent to
that produced by the original progra4s2 Testing in a migration is re*uired to ensure that, given the same input, the programs and
applications will produce the same output as their pre0migrated counterparts. This does not necessarily mean that the output is
1
correct, only that it is the same. The principle is that if there are bugs in the program prior to the migration, the same bugs will be
there after the migration. Any attempt to stray from this, will result in adding time and expense to the migration project.
,ata 'o4parison
,atabase 'o4parison
XMS produces a readable co4parison of the output of the transformed program with that of the original program, pinpointing any
discrepancies. The format permits to determine the exact position of mismatches and discerns error patterns at a glance
I4ple4entation
XMS carefully prepare each transformed program for transition to your production environment. XMS assists in the transfer of each
batch of completed programs to your environment.
2