This video is aimed at Rational Programming Patterns developers who are accustomed to managing code generated between the 912 and 96 versions. Generation enhancements automatically apply if you work on instances directly created in Rational Programming Patterns 961 or migrated from Pacbase with the 961 migration process. If you work on instances generated or migrated before the 961 version, you must explicitly choose to upgrade their generation when you open their COBOL files. Let’s see how it works. you must explicitly choose to evade the generation when you open the confines that see how it works Let’s take the example of a Screen. If you try to open its COBOL file, a dialog box offers to upgrade the generation. If you click No, the code code will remain as is and the dialog box will pop up again each time you will open the COBOL file. if you click Yes, the Cobol code will integrate the enhancements of the new generation. Note that you will be warned if some of the files to be impacted are already modified locally. In this case, it is recommended to deliver the local modifications first before upgrading the generation. In our example, this is not the case. So, let’s click Yes. After a new generation, a COBOL compare editor opens. It highlights the enhancements of the upgraded generation. With the buttons of the editor toolbar, you can browse through the COBOL modifications. You cannot modify the COBOL code though because it conforms to the upgraded generation. The compare editor contains two buttons. Il you click Cancel, you discard the modifications but the dialog box about the upgraded generation will pop up again next time. So, let’s click OK to accept the modifications. The files that were impacted are listed. We’ll look into them later. We’ll look into them later. Relative subfunctions used to be inserted through the SP Macros associated with the Screens or Business Components. Then, in the COBOL code, their declaration lines used to be displayed as Macro lines. With the upgraded generation, the SP Macros are no longer used. Their contents are transferred into the COBOL code. Let’s open the design of the Screen whose generation we’ve just upgraded. Although the Screen contains relative subfunctions, its CP Lines no longer call the SP Macro. In the COBOL file, the tags of the relative subfunctions are no longer displayed as coming from a Macro. They are now displayed as specific code. Moreover, they are automatically preceded by an annotation that indicates the relative position of the insertion. In this case, the BEFORE annotation means that the 25BB subfunction is inserted before the ME00 Segment in the header category. There can be other annotations like AFTER, REPLACE, or ATTACH. You can now insert relative subfunctions with the subfunction creation wizard directly in the COBOL code. You open the wizard with a shortcut CTRL + lowercase g or the contextual menu. For example, you can create a 30MM subfunction in the Dialog model. It will be inserted relatively to the header category. A new generation starts automatically. Here’s the new 30MM subfunction. The 900 lines are now automatically managed. They are added if they were missing, deleted if there were unjustified, or moved if the execution type or the level of a subfunction is modified. For example, in this Program, a 900 line is included at the end of the 40CB subfunction, which has an IT (IF THEN) execution condition. Let’s create a 40CC subfunction with a level 10 and an IT execution condition. Let’s click Finish. The 900 line is automatically moved to the end of the new 40CC subfunction. The deletion of subfunctions has also been enhanced. Now, you can delete subfunctions that contain nested generated subfunctions. For example, in this Program, the Delete choice is now available on the specific 90CL subfunction, which contains the generated 90CO subfunction and the specific 90PP subfunction. If we want to delete both specific subfunctions, we must select Delete also its dependents. Since a new generation is now required, the OK button becomes unavailable. Let’s click the OK + Generate button then. The code is automatically generated again. Outgoing modifications must be delivered if you applied the upgraded generation. All the impacted files can be viewed in the Pending Changes view. Let’s look at the files that were impacted when we applied the upgraded generation to the Screen at the beginning of the demo. Here are the impacted design files: the Screen design file because the SP Macro was removed from its CP Lines, and the SP Macro file because it no longer exists. And here are the impacted generated files: The Screen COBOL file, its associated PDP file. The map PDP file is here too. Although the Screen map has not changed, the map PDP file contains new technical information used internally. It is recommended to associate the change sets with the same work item before you deliver. You will then clearly see the impact of the upgraded generation. This is the end of our quick presentation of the upgraded generation. You can discover more features in the product and in the documentation.