PACBASE2019-09-05T08:38:32+00:00

  • A 100% automated migration solution

  • A Process proven in production

  • Guaranteed functional equivalence

  • No performance loss

With more than 10 years of development, Raincode Labs PACBASE Migration is the only PACBASE migration solution that has been thoroughly tested and repeatedly proven in production.  With Over 200 million lines of code migrated across several projects, Raincode Labs is the market leader in PACBASE migration. 


The Raincode Labs PACBASE Migration solution converts PACBASE code to structured, maintainable COBOL, eliminating any current or future technical dependencies.  It can also be tailored to the customer environment, allowing them to customize our solution according to their requirements or needs.


And thanks to its high level of automation, it can cost-effectively migrate even the biggest portfolios in months rather than years.

FEATURES

  • Supports all versions of PACBASE, all platforms, all databases

  • 100% fully automated (Not 99, or 99.99, but 100%!)

  • Produces structured, readable and maintainable COBOL code

  • 100% functional equivalence guaranteed

  • Allows for multiple iterations to tune the result’s quality to the company’s specific requirements.

BENEFITS

  • Proven in use.  This technology has already been applied to over 200 million lines of code

  • Cost and quality. The level of automation allows for aggressive budgets and planning

  • Independence, as the migrated application can be easily rehosted. It only relies on de facto standard components for which replacement products are available on different platforms (CICS, IMS, DB/2, etc.)

  • Flexible process without any freeze period during which maintenance must be suspended or duplicated

  • Scientifically designed testing process an order of magnitude more efficient than the more conventional approaches

INDEPENDENCE

PACBASE’s technical merits are impeccable. It is an efficient and rigorous development environment that has proven its ability to master complexity and ongoing changes over the years.
Even so, using a proprietary environment to maintain mission-critical applications induces a dramatic risk, such as, when the sole vendor of the tool changes its focus, or decides to terminate the product altogether.
To best address this concern, RaincodeLabs’s PACBASE migration solution induces no dependency. At the end of the process, the application does not depend on any additional proprietary component or tool, be it RaincodeLabs’ or anyone else’s. It produces standard COBOL code that can be maintained using standard tools available in a vibrant marketplace.
Going to standard COBOL also opens a number of options including:

  • One can tap the COBOL market for more advanced needs than maintenance alone, to address impact analysis, cross-referencing, quality control, etc.

  • COBOL consultants are far easier to find than PACBASE consultants, especially in an outsourcing context

  • COBOL systems can be rehosted to any target system, even if it relies on CICS or IMS/DC, as a wealth of emulation tools are available, thereby reducing the cost of ownership dramatically

  • The database can be migrated if needed, using one of the many specialized service providers in this area

THE PROCESS

Starting with the PACBASE generated code

The COBOL code generated by PACBASE is totally unstructured, up to a point where it is clearly unreasonable to maintain as it is. However, it does accurately represent the expected behavior of the system, as it actually runs in production.

RaincodeLabs’ PACBASE migration facility takes this source code and improves its technical properties through a number of behavior-preserving transformations, until the code becomes similar to what a human programmer would have written in the first place, and can thus can be maintained efficiently.

Combining Transformation

RaincodeLabs’ PACBASE migration solution is based on 140 atomic transformations. Each one of these transformations addresses a single issue. These transformations are kept as simple as possible, so that they remain easy to test, easy to debug and easy to explain. The power of the migration engine comes from the combination of these 140 elementary transformations. They are applied repeatedly, each pass possibly enabling other transformations until no more transformations can be applied.
The transformations can be enabled or disabled one by one, together with additional parameters.

Transformation example

In this example, only one transformation is applied

In this example, all transformations have been applied. On the left is the original generated code from PACBASE, on the right the result of the transformation. The code is smaller, the intention is clear, all GOTO’s and labels have been removed.


Promoting Technical Quality

The transformations performed by RaincodeLabs’ PACBASE migration facility aim at improving technical quality, as defined by the following 3 areas:

Result

The charts below show the reduction in the number of GO TO and PERFORM THRU statements:

The amount of code is also impacted by the transformation, with a reduction ranging from 10 to 55% depending on the case at hand (the lower the better):

Other figures are produced, showing the overall improvement in quality (the lower the better)

In addition to these qualitative improvements, the runtime performance of the migrated application will improve as part of this migration process, up to as much as 15% of the CPU utilization

CLONE DETECTION

PACBASE’s code generation introduces a lot of redundancy in the generated code, as many artifacts are repeated in hundreds or even thousands of programs. Centralizing these distributed components in copybooks removes duplicated code and improves maintainability. Moreover, also reduces the cost of ownership almost linearly, hence the amount of the code is drastically reduced.

The amount of code under maintenance can shrink by as much as 30%, in conjunction with the size reduction resulting from the code restructuring.
This centralization is performed by the clone detection process, which goes through the code and identifies components that can be represented by plain COBOL copybooks, possibly with parameters.

Macros and Segments

In addition to clone detection, which applies to the entire portfolio after transformation, PACBASE macros and segments are dealt with specifically at the very beginning of the process. Data structures referring to PACBASE segments and code fragments expanded from PACBASE macros are recognized and replaced by native COBOL copybooks as a preliminary phase, so that these components, which are so essential to the PACBASE way of designing systems are centralized in a recognizable fashion. This allows ongoing maintenance to keep a full trace between the original PACBASE artifact and the resulting COBOL code.

Testing the application program by program is dramatically inefficient, up to a point where it can put the economic justification of the whole project in jeopardy. By taking advantage of the automated nature of this transformation technology, one can improve the accuracy of testing while reducing its cost by orders of magnitude. As a result of the migration process, a prioritized list of programs is produced. This list is divided into slices of increasing size and sorted by order of decreasing complexity. Complexity here refers to transformational complexity as opposed to functional complexity, which may not be correlated.

The first, top most slice covers most of the complexity of the restructuring facility. By testing these as extensively as possible, one leverages the fact that the transformations tested here are used throughout the portfolio under consideration. Since this first slice is limited in size (typically 10 to 30 programs), it can be tested very thoroughly, using any testing technique available today (white box, peer review, etc.).

After this initial slice has been tested successfully, the next slice, significantly bigger (50 to 100 programs), can be tested in a simpler setting than was the case for the first slice (peer review may be dropped, for instance).

The third slice (500 to 1000 programs) can then be tested with shallow testing only, as the most complicated transformations and combinations have already been tested extensively.

After that, one can move chunks of 5000 programs to integration testing and production in a matter of days.

IN THE NEWS TODAY

Load More Posts

RAINCODE LABS HEADQUARTERS

Rue de la Caserne 45
1000 Brussels
Belgium

Phone: +32 2 522 06 63

RAINCODE LABS INDIA

#1144, Guru Nilayam, 3rd Floor
Sector 2, HSR Layout Bangalore
560 102 India

Phone: +91 99450 47258

CONTACT US

    Go to Top