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
© 2015, IBM.
All rights reserved.
IBM
Rational Programming Patterns V9.1.1.1 is a fix pack that applies to Rational
Programming Patterns V9.1.1.
Rational
Programming Patterns V9.1.1.1 (RPP 9.1.1.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.
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
|
APAR |
Summary |
Internal |
|
PI30556 |
MIA2:
Replacement of field attribute (BRT in pc1 => NORM in sdp ) |
21995 |
|
PI30774 |
MIA2:
Column shift on lines of called screen |
22044 |
|
PI32301 |
Comment
lines wrongly taken into account |
22314 |
|
PI32563 |
Generation
manager refresh action fails when it is used with a previous workspace (build
with a previous RPP version) |
22413 |
|
PI32859 |
Number of
visible items not taken into account opening instances selection dialog |
22332 |
|
PI33033 |
Snippet
Micro-pattern W Line F cannot be cancelled |
22302 |
|
PI33073 |
MIA2: The
transco of quotes is incorrect from D line for data element |
22575 |
|
PI33556 |
Problem
of " and = characters in the micropatterns |
22606 |
|
PI33831 |
The help on
the Copybook and Error Messages generation is not clear enough |
22715 |
|
PI34997 |
GELines tab
- add sort and display on text selection |
22934 |
|
PI35107 |
Batch
Quality Control on Windows with standard RPP COBOL Rule |
22921 |
|
PI35154 |
Report L
Lines - Label selection - Cancel button inefficient |
22927 |
|
PI35157 |
DLines -
review length column for description |
22931 |
|
PI35169 |
Import text
and creation wizard: textType must be initialized to "T" and
sectionType to "U" |
22863 |
|
PI35171 |
SDK:
The * and - characters in a
micropattern attribute value are deleted |
22746 |
|
PI35186 |
Carriage
return must no be used in label instance |
22966 |
|
PI35481 |
Wrong label
in -GG for -Dx - Block Base |
22992 |
|
PI35561 |
Precondition
of quality control and syntax error |
22978 |
|
PI35639 |
Decrease
the severity of some controls on the user entity |
22877 |
|
PI36163 |
Input Aid
Description: allow xref column selection even if InputAid has uses |
23125 |
|
PI36359 |
Report -D
Lines: Issue with cancel button for label and structure selection. |
23103 |
|
PI36367 |
Report -D
Lines: Issue on move up and down arrow on edition line |
23103 |
|
PI36457 |
Screen CE
Lines: Issue when updating Attributes |
23104 |
|
PI36475 |
Additional
blank character in the micropattern attribute value |
23138 |
|
PI36684 |
Dialog
error label: From -CE of
screen, management of a second line according to the presentation attributes Do not take into account the delimiter on -D of Data
Element Blank lines wrongly
inserted -GE of screen - modify the management of lines
numbering |
23162 23161 23160 23158 |
|
PI36943 |
Duplication
of a subfunction containing a call of micropattern |
21787 |
|
APAR |
Summary |
Internal |
|
PI33558 |
Data Element editor : Make some controls
when usage or/and format changes |
22624 |
|
PI35755 |
The save of the COBOL file raise a
'design file corrupted' message |
23034 |
|
PI35775 |
Some comparison actions on created
design files raise a 'premature end of file' message |
23036 |
|
PI36943 |
Deletion of a subfunction containing a call of
micropattern |
21790 |
|
PI37380 |
Design Editors - Resizing columns when
focus is lost in the tab |
23272 |
|
PI37645 |
Dialog error label: call of non-existing
text in -GE of screen |
23275 |
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.
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 Y10C
<End of Document>