IBM® Rational® Programming Patterns 8.5.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 © 2013, IBM.
All rights reserved.

 

Purpose

IBM Rational Programming Patterns V8.5.1 is a fix pack, applying on Rational Programming Patterns V8.5.

Rational Programming Patterns V8.5.1 Fix pack mainly focuses on removing generation differences between Pacbase and RPP, found on Customer repositories: 

-          In generated code on the Batch pattern

-          In generated code on the Dialog patterns

It also included some APAR corrections listed below.

To avoid some consistency and generation problems, micro-patterns are now exclusively on one line after a migration from Pacbase.

 

Information and References

For information about documentation and support resources, software and hardware requirements, and installation or upgrade steps, see the Rational Programming Patterns page.

Additional information can be found on IBM Publication Center. Among others, on installation of Rational Programming Patterns, see: Installing Rational Programming Patterns V8.5. You may find also related information in the IBM Product Information Centers.

 

 

APAR corrected in RPP 8.5.1 fix pack

APAR

Summary

PM75932

Procedure rpp.bat --migrationHelp : parameter "--name" needs documentation

PM76917

Procedure rpp.bat --automaticMigration: message on source validation missing

PM77070

Loading Workspace: "End Of File" wrongly detected on loading xmi file

PM78723

Database block generation is erroneous after modifying a column

PM78814

Segment - Data Element not defined in Repository: Cobol "Picture" not generated

 

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 8.5 stay unresolved. In spite of the fact that those differences are compensated by the pattern recognition technology, the consequences are:

- A number of lines of specific code in RPP 8.5 greater than in Pacbase

- A new program created and generated in RPP could 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 generated locally in a tooltip text. Thus:

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

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

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

 

RPP 8.5.1 focuses on Batch and Dialog generation differences. The other patterns may likely have a high level of unresolved generation differences.

 

Other limits or known problems

Id

Summary

2565

Pactables extract procedures have no equivalent in RPP

1146

Integration of non COBOL generated files under RTC: error Labels files are not managed

4992

No possibility to choose a specific destination folder for the map for Screen and client entities

7330

The "Aliases" are not generated in the Copybooks

14082

Sub-references on a Cobol generated file : references on micro-patterns are missing

14124

The first generation does not make visible the generated file in the design explorer view

 

 

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 Y08A

 

<End of Document>