IBM® Rational® Programming Patterns 9.5.0.1 – Release Notes

 

Disclaimer of Warranty

IBM makes no representations or warranties, either expressed or implied, by or with respect to anything in this document, and shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect, special or consequential damages.

Copyright © 2016, IBM.
All rights reserved.

 

Purpose

IBM Rational Programming Patterns V9.5.0.1 is a fix pack that applies to Rational Programming Patterns V9.5.

Rational Programming Patterns V9.5.0.1 (RPP 9.5.0.1) Fix pack mainly focuses on removing generation differences between Pacbase and RPP, found on Customer repositories.

It also includes some APAR corrections listed below.

Information and References

General Information about the Rational Programming Patterns product, such as documentation and support resources, software and hardware requirements, can be found on the Rational Programming Patterns page.

 

The IBM Publication Center offers you customized search functions to help you find the publications you need.

 

The IBM Knowledge Center is now available and contains all the resources on various products, and among them Rational Programming Patterns.

 

APARs corrected in RPP 9.5.0.1 fix pack

 

APAR

Summary

Internal

PI39958

Wrong reconciliation after sub-function creation in Macrostructure when specific code exists

23514

PI55411

Migration: some messages are ambiguous when the input files are empty (Dispatch macro, Split)

26128

PI57495

Multi session or incremental migration: the import process does not remove generated files (COBOL + MAP) when the generation variant is turned to "N"

26474

PI59459

A local/server design search with the characters '(' and ')' fails to match with existing design

26679

PI61663

Problem on MAF Segment - Statistics & LAL

27002

PI61858

Response time of PDP COBOL editor for large programs

27043

PI61870

Missing Cobol Source file in migration help process.

27029

PI62442

The RPP *.xmi import does not preserve the projects names if they contain a '.' character

27101

PI62818

Database Block -DR ...K Editor: Select a data element of a called segment

27172

PI62825

The RPP preconditions for the Deliver fail to evaluate a file without extension

 

 

 

Known problems and workarounds

Generation differences

Reminder from RPP 8.5 and still applicable:

Some differences between a same program generated from Pacbase and RPP remain unresolved.

In spite of the fact that those differences are compensated by the pattern recognition technology, the consequences are:

- The number of specific code lines is greater in RPP than in Pacbase

- A new program created and generated in RPP might be slightly different than in Pacbase

 

RPP replaces the line in difference with the line coming from Pacbase and shows the line as it is locally generated in a tooltip text. Thus:

- The source code of the program is the same in RPP & Pacbase

- The compilation of those programs gives the same executable as in Pacbase

Some differences are solved in RPP, while some others will be solved in upcoming fix packs or releases.

 

Associated level of Pacbase

It is highly recommended to use this fix pack with the corresponding level of Pacbase when working on the migration process from Pacbase to RPP:

Pacbase 3.5 Y10E

 

Evolutions in this fix pack

Impact analysis:

A free reference is set when the name of a target instance is entered in some text fields of a source instance. A subreference link is created, even if the target instance is not defined.

 

Enhanced management of the specific code:

- Quick fixes for reconciliation and migration warnings are available directly in the PDP COBOL editor.

- The Rational Programming Patterns compare editor makes it possible to compare the contents of COBOL files.

- A new button in the -CP Lines tab can be used to generate a Program, Screen, or Server after modifying its Macro calls. The Rational Programming Patterns COBOL compare editor opens automatically. It is then easy to see the impacts of the modifications and to copy specific changes to the new code.

- Tags can be inserted in a specific code block to dispatch Macro lines inside this block.

 

<End of Document>