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

 

Purpose

IBM Rational Programming Patterns V9.0.0.1 is a fix pack that applies to Rational Programming Patterns V9.0.

Rational Programming Patterns V9.0.0.1 (RPP 9.0.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. See for example:

- Installing Rational Programming Patterns V9.0

- Rational Programming Patterns V9.0.0.1 Fix Pack - Installation Instructions

 

The Product Information Center (Rational Programming Patterns V9.0) is designed to give you quick access to the resources you need to use the product.

 

APARs corrected in RPP 9.0.0.1 fix pack

APAR

Summary

PM88025

Generation failed for Error Labels and Copybooks from Logical Views

PM91357

Creation of a child data element above its parent in some cases

 

Remaining APARs to be corrected in a future Release or Fix Pack

APAR

Summary

PM91106

Deletion of link between text and another entity impossible

PM78815

Operator MOVE not generated in some cases in the Macro-Structures

 

Known problems and workarounds

Generation differences

Reminder from RPP 8.5/RPP 9.0 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.

Other limits or known problems

Id

Summary

1146

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

2565

Pactables extract procedures have no equivalent in RPP

4992

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

7330

As a User, I need "Aliases" to be generated in the Copybooks

14744

Code derivation - Batch program: generation failed

 

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 Y09A

 

<End of Document>