Re: system cleanup, archiving unused objects.

[Bruce Vining <bruce.vining@xxxxxxxxx>]

I just want to point out that there are exit capabilities above and beyond
what are found in the Registration Facility.  The Registration Facility
didn't come into being until around V3R1.  Exit programs (of various forms)
predate that period and not all have "migrated" to the Registration
Facility.  Having just added a trigger today where I'm working, that
example of an exit point/program comes to mind as an example.

On Tue, Jul 21, 2020 at 3:46 PM Rob Berendt <rob@xxxxxxxxx> wrote:

> https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/apis/reg1.htm
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Gerald Magnuson
> Sent: Tuesday, July 21, 2020 12:24 PM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Subject: system cleanup, archiving unused objects.
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> we are archiving objects that are not being used anymore, and although we
> have the objects "last used data" and "days used" counters, we tend to only
> focus on where the objects are called from.
> which leads me to trying to get a handle of all the places where a program
> can be called.
> menu's, programs, sbsd's, triggers, exit points, job schedulers,
> We have a scan program that looks through source code and menus and our
> Robot job scheduler, but it doesn't look elsewhere.
>
> Is there a way to get a list of exit point programs, programmatically?
>
> other places I should be concerned about?
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com