IBM® Rational® Programming Patterns 9.1.2.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.

Purpose

IBM Rational Programming Patterns V9.1.2.1 is a fix pack that applies to Rational Programming Patterns V9.1.2.

Rational Programming Patterns V9.1.2.1 (RPP 9.1.2.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.1.2.1 fix pack

APAR	Summary	Internal
PI40525	Problem with macros	23695
PI42724	Wrong result after using context and hierarchy on Sub/Super references local and server	23840
PI43030	Refresh Generation Manager cache fails if a project is closed	24083
PI43777	Cannot open the segment editor for a new entity created in RPP	24208
PI43877	Migration: Not necessary to create empty folders for duplicate entities	24233
PI44143	The constant generated in RPP must be in a correct format for date and time	24259
PI44368	In a split migration, special macros are not created in the same project as the screen/server	24296
PI45083	MIMA - space wrongly insert in operand in alone line, in some cases	24345
PI45183	Skeleton editor for COBOL not working with RDz 9.1.1.1	24410
PI45340	No ERROR_RAISED for Micro Pattern markers	24337
PI45354	Problem on -LAL server when new workspace and accessing segment by server search result	24459
PI45530	MIA2: map .mfs. Erroneous length for column label	24484
PI45704	MIA2: map .mfs. Erroneous column number	24495
PI45791	MIA2: map .mfs. Erroneous column number	24521
PI46396	Non SQL DBD generation: NullpointerException PC12 - DBB - StringIndexOutOfBoundException in -GG	24531 24528
PI46503	MAF Text - Problem on accessing source section	24597
PI47241	DBB - View - double on Data Element	24665
PI47416	In a precise display context and location contents, the design explorer filter gives a wrong result	24737
PI47960	Data Element Design Editor : when selecting a parent data element, avoid to propose the current data element itself in the list	24811
PI48268	Import Volume: problem on import call entities and generics description	24890
PI48278	Missing reference between screen and data structure (indirectly referenced via the segment calls)	24894
PI48486	When the thesaurus is corrupted, it is not possible to correct it	24910
PI48679	The Data Element usage parser collect micro-pattern during the parsing of a macro source code	24984
PI48761	Automatic validation (batch) does not remove all markers	24991
PI48863	The micro-pattern parser of the macros source code detect non existing micro-pattern	25004
PI49038	Timestamp of xxxpdp files updated even if the xxx file doesn't contain any modification forcing to deliver or to accept incoming changes for nothing	24954
PI49164	RPP misses comments from Pacbase -CP lines	25040
PI49302	Error labels are deleted during migration by delta	25100
PI49661	Search export for user entity: the code of the meta-entity is missing	25034
PI49737	Duplication wizard never allows to keep the entity code	25167
PI50017	PC12: Tags are not the same between annotated files and macro	25209
PI50192	Missing some data element usages and some sub generation references	25169
PI50365	The "Ignore comments" option remove comments after validation	24859
PI50424	Inserted code is wrongly interpreted	25264
PI50428	Macro replace with procedural code prior to first	25269
PI50539	Difference in label with "F" type presentation	25304
PI50649	Provides API(s) even temporary to extract MP references from MP and extraction of data elements usage for the RPP SDK	25325
PI50779	PacMacroParameter: delete the control on existing data element, data unit or dataaggregate	25343
PI50843	The RPP.bat --restoreGenSubRef command should not modify cobols (generation date and constants)	25357
PI50931	Migration hangs during migration validation	25362
PI50965	Screen emulator does not work when multiple instances of rpp are open	25326
PI51110	COBOL facet - Problem in COBOL format interpretation	25410

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 Y10D (minimum) or X10D (recommended)