×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Javier,
I found a copy of it here:
https://authory.com/JonParisAndSusanGantner/The-Seven-Deadly-Sins-of-ILE-a0f4e66fe37a745c8bdf7cbc95f0b365f ;
If you look here:
https://authory.com/JonParisAndSusanGantner/
there are hundreds of their articles from over the years. :-)
All the best,
Mark S. Waterbury
On Thursday, July 25, 2024 at 09:26:26 PM EDT, Javier Sanchez <javiersanchezbarquero@xxxxxxxxx> wrote:
I got a handout of one of her sessions when I attended the RPG Summit in
the fall of 2015. There she summarized what the 7 deadly sins are and also has a link to the document but it's not reachable.
Summarizing, though, here's the 7 sins:
1. Run ILE programs in the Default ILE Activation Group (DAG)
Use ILE named Activation Groups instead (such as QILE)
2. Run Service Programs in the DAG
Can be an even bigger problem than #1
3. Use *NEW by default, rather than by design
Until V5R3, *NEW was the default on the CRTPGM command
4. Using *CALLER as the default Activation Group value
Tends to cause problem #1 if you're not careful
5. Failure to use RCLACTGRP only when necessary
5b. Using RCLACTGRP(*ELIGIBLE) in production code at all
6. Allow scoping parameters to default to system-shipped
defaults
7. Use of the RCLRSC command
Its impact is variable depending on where used and on what type of
programs
I do not have the full document, if there is one.
As an Amazon Associate we earn from qualifying purchases.