Re: List PGMs Called from MENUs

The problem I have with such cross references is they are obsolete immediately upon generating.

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 Vern Hamberg Sent: Tuesday, March 2, 2021 9:49 AM To: midrange-l@xxxxxxxxxxxxxxxxxx Subject: Re: List PGMs Called from MENUs 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. His OP says this -

We have here a table that lists calls between PGMs (what PGMs call other
PGMs)
This table is refreshed nightly by exporting DSPPGMREF of certain LIBs
to a

file.

Not for us to ask why, right? Looks like a home-brew cross reference.

Above my pay-grade!!

Vern

On 3/2/2021 8:30 AM, Rob Berendt wrote:

The question boils down to WHY does he need such a list?
If he followed your instructions and generated such a list how would he consume it?
Why generate such a list? For an audit but NEVER to be used?

If he knows the program he's trying to (retire/change parameters/etc) and he just wants to know where it's called from a menu option, then the technique I pointed out would tell him exactly that.

Since menu commands can be
CALL MYPGM
CALL PGM(MYPGM)
MYPGMCMD /* custom command to call mypgm */
Trying to link a list of menu commands to a file containing a list of programs to retire can be challenging. Hmm, I want to do a join on a midstring search... Doable, but challenging.

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 Vern Hamberg
Sent: Tuesday, March 2, 2021 8:18 AM To:midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: List PGMs Called from MENUs 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. This is fine for finding something you already know about -
Gad was asking for a cross-reference kind of thing, I think - a list
of what each menu item calls. So I think Gad does need to do what he
last asked - compile the contents of the several source members - they
are just tables, after all - make a list of *ALLUSR/QDDSSRC files
with, perhaps, DSPFD *MBRLIST. I didn't see member type in the output,
it has to be somewhere, though, it's been awhile, someone will know.
Copy contents of each, maybe with SQL to filter on some criteria -
might work. A macro in PDM might automate walking through all the user
libraries to find QDDSSRC - once in there, F17 filter can limit list
by member type, then print the list. Then copy SPLFs to get a list of
members - yes, ugly! And I've probably missed something or forgot
completely what I used to know. HTH Vern On 3/2/2021 6:16 AM, Rob
Berendt wrote:

Well, if you have IBM Rational Developer for i I would think it would be quite easy to do the following:
Go into the Object Table
Work with Members
Library: *allusr
File: qmenusrc
Member filter: *
Member text: *
Member type: mnucmd

Once you have that, then you can Ctrl-A to select all, right click and select Find String and enter a string such as: CALL LBLXREFMC and get a result like this:
https://imgur.com/zoTDnN2


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 46818http://www.dekko.com
-----Original Message----- From: MIDRANGE-L
<midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Gad Miron Sent:
Tuesday, March 2, 2021 2:29 AMTo:midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: List PGMs Called from MENUs 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. Thanks Bryan, Mark It is standard SDA Menus we're talking
about with pairs of MNUDDS + MNUCMD source MBrs in QDDSSRC (There are
some old S36 Menus but not many) So, is there a single central place I
can search or do I have to comp all my relevant Libs' QDDSSRC files
and list the content of MNUCMD MBRs? TIA Gad -snip-

Gad Miron wrote on 3/1/2021 1:35 AM:

Hello sages

We have here a table that lists calls between PGMs (what PGMs call other
PGMs)
This table is refreshed nightly by exporting DSPPGMREF of certain LIBs

to a

file.

However ,
PGM's called from MENUs are (naturally) not listed

Anyone know a way to list such calls?
SQL Services perhaps?


TIA
Gad

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a messageemail:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
oremail:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.

Pleasecontactsupport@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

--
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
athttps://archive.midrange.com/midrange-l.

Please contactsupport@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