IBM® Rational® Programming Patterns V9.6 – 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 © 2017, IBM.
All rights reserved.

 

Purpose  

IBM Rational Programming Patterns V9.6 is a modification release of Rational Programming Patterns.

It contains new features and defects corrections.

 

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.

 

Fixes included in this release

 

 

APAR

Summary

PI72843

RPP 9.5.0 receives a severe error in the automatic migration step of the multisession migration process

PI73450

Wrong content of file displayed when opening editor from search result stream scoped

PI73451

Content of COBOL Program ID field displayed after copy/paste on a Macrostructure

PI73837

Generation fails on duplicated program

PI73843

Specific line inserted in Macro is duplicated when changing level of subfunction

PI75372

RPP Client 9.1.2 cannot generate Program after the Program has been formatted using the Format functionality

PI75510

Scope of precondition rule not taken into account

PI76228

Too much time for opening COBOL PDP editor

PI76424

"Echec de sauvegarde" (Failed to save) error message

PI76520

Label duplicated in COBOL source code after generation

PI77404

COBOL source code disorganized after deletion of function

PI77799

"DEL" key is inoperative in COBOL PDP editor

PI77807

Vertical labels not generated on correct line in BMS

PI77966

Access to Data Element takes too much time

PI78396

RPP Client 9.5.1 Server generation fails because the new generated code is not taken into account

PI78417

Source of migrated program considered as binary

PI78549

Quality rule does not detect errors in "IDENTIFICATION" or "ENVIRONMENT" DIVISION

PI78667

RPP 9.5.1 takes a long time to open a Segment from the RTC server side

PI78684

Error label generation fails when division of text contains empty line

PI79174

RPP 9.5.1 Client takes a while for adding a Data Element in the -CE of a Table

PI80010

Comparison of two states of a Data Element fails with JAVA.LANG.NULLPOINTEREXCEPTION

PI80649

RPP validation rule prevents delivery of Segment created by copy/paste

PI81031

RPP 9.5.1 server generation fails because the -FN beginning label is missing

 

 

You may refer to IBM Support Portal for more information on available Downloads and Fixes.

 

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 release with the corresponding level of Pacbase when working on the migration process from Pacbase to RPP:

Pacbase 3.5 Y10F

 

To migrate Servers (MIA4 procedure) with the version 9.5.1 interim Fix 004 or higher, you must apply the Pacbase 3.5 F104 Fix to the Pacbase 3.5 Y10F package.

 

 

 

 

 

 

 

 

© Copyright 2017 IBM Corporation