FALLAI-Denis
commented
1 year ago Hi @Thibaut69,
It seems to me that RPP, Rational Programming Patterns, at least in its RPP-Pacbase version, has very strong adhesions with IDz, but also with RTC, Rational Team Concert. Even if Z Open Editor is built on a subset of IDz, I think it would pull a lot of features unique to IDz and RTC, which would significantly weigh down Z Open Editor and the VS Code eco-system.
However your request remains interesting and joins another issue that I posted API for interacting with source code opened in Z Open Editor.
For your information, know that we are on a project to withdraw from Pacbase, (ancestor of RPP), and that we have developed 2 Development Workshops to maintain developer productivity known with Pacbase / RPP:
- a Development Workshop based on a code generator, like Pacbase / RPP.
- a Development Workshop based on a code injector, i.e. a kind of automation of snippets insertion in a coherent way, thus reproducing the mechanism of Pacbase / RPP macro-structures.
In both cases, the starting point is a skeleton program that more or less takes over the kinematics of Pacbase / RPP programs (why want to reinvent something that has proven itself?).
I would talk more about the Development Workshop based on a code injector since I participated in its development. With this Workshop the development is at least as quick, if not faster, than with Pacbase / RPP. This is a fact recognized by our developers. A Pacbase / RPP developer finds himself on familiar ground (equivalences with the -CD / -CS and the -CP of Pacbase, adapted to a COBOL world). A traditional COBOL developer adapts quickly, (we had users who did not know Pacbase). The macro-structures have been translated into "services framework". RPP's "value-added" micro-patterns have been translated into VS Code snippets. We produce structured, readable and easily maintainable code. All the technical functions are taken care of by and an "intelligent" adaptative COBOL framework which exploits conditional compilation, (and this framework remains easily usable outside the Development Workshop in the event that it is no longer available for a reason or for another, moreover it was designed independently of and before the Development Workshop). Resource management (files, Db2 tables, or others) is fully supported by the framework, including the famous resources reads with breaks and synchronizations.
And to finish and not to annoy any longer the reader who is totally unfamiliar with the Pacbase / RPP world, know that our solution is able to migrate the generated Pacbase / RPP COBOL code with great ease (less than 1/2 day for a manual migration, and a priori easy to automate, but it is not necessary to restructure the specific code as long as it is not necessary to modify it and in this case the migration is even faster and less than an hour). If you would be interested in more information, you can contact me, (I am easy to find and known on the Pacbase / RPP market place in France).
Thibaut69
rigoletj
Hi everybody,
Could we imagine that you import IBM RPP features ? The pattern driven programming accelerate and standardize the code. I have it currently under iDz. https://www.ibm.com/docs/en/rpp/9.7.2?topic=overview-rational-programming-patterns
We have macros, snippets, and others objects like design files (cblpdp) and that can be very helpful to get RPP under VS Code to import and manage our current projects.