|
Lots of 'DspCrossReference' commands exists. On the News/400 shareware list I found: "Public doamin. The Cross-Reference (XREF) command retrieves program object usage, object usage cross reference, and program where-used data for any object on your system. The XREF output can be viewed, printed, or output to a database file Submitted: 15 Jul 1996" I use a homebrew'n one. Not good enough to publish by now though. At least two of my customeres have each their own homebrew'n ones. I guess that they all works on an DSPPGMREF to a permanent file (updated when a program is ...?? and/or rebuild in total once every ...? ) You write: "I also wonder how many layers deep a call structure is prudent to be taken.." I have a DOCPGMSTR command (Freeware with source http://hkrebs.dk/docpgmstr.html) using an on-the-fly DSPPGMREF to outfile. Working with that I found that batch programs are nested normally only to 3-4 levels max and online programs three or four levels deeper (for special functions like F1 etc..). Add to this of cause a few levels extra for SLIC-programs. My command defaults to 'Limit display to 9 levels' allthough it can go up to 99. Then - what is 'prudent'? Four considerations for those who want to build their own DSPXREF: o Homebrewn commands and their CPP's are not included in DSPPGMREF o DSPPGMREF list the logical file, not the physical(s) o Files used as an external datastructure are not included o File overrides and variable program names! Henrik http://hkrebs.dk/ ------------------------------ Date: Thu, 25 Jan 2001 14:48:36 EST From: MacWheel99@aol.com Subject: DSP PGM REF Opposite Is there an IBM command that tells me other direction from DSPPGMREF? I would key in some command (I am making this up <G>) like DSPCALLME ORD561 and it would print a report like DSPGMREF that tells me what programs call ORD561 DSPPGMREF tells me what program objects are called down 1 level I sure would like a variant that shows me a particular kind of program object down more than 1 level in an indented tree structure I imagine there are shareware solutions out there Currently my users get ORD561 report every time they do shipping documents ORD595 & ORD596 which I am told comes from ORD590 menu option, and they want me to modify ORD561 PRTF overrides & I am having a hard time tracing where that is in the ORD590 flow, so either the users are mistaken or I am missing something. The menu calls ORD590C CLP ORD590C calls ORD590 RPG which is a rather large program ORD590 calls ORD591C CLP for each set of shipping documents ORD591C OverPRTF's ORD595O & ORD596O & calls ORD591 ORD592 ORD593 ORD592 & ORD593 are alternative ways to process shipping documents & both of them call ORD595 & ORD596 which are two kinds of shipping documents I continue to look into other stuff that gets called but so far have not dug up the buried treasure of where ORD561 is called & there is another player ORD597 that I need to locate also because ORD590 is normal shipping & there is also a path involving reprinting of corrected shipping documents I also wonder how many layers deep a call structure is prudent to be taken in concert with tools normally found in a typical 400 shop. I expect that I could do a DSPPGMREF *ALL to an *OUTFILE then try to navigate the resulting mess via Query or even SQL ... show me all primary hits with this program name, then all secondary hits on the primary hitees. I thought I would ask first ... there may already be a DSPCALLME out there with some other name that I have overlooked. MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) AS/400 Data Manager & Programmer for BPCS 405 CD Rel-02 mixed mode (twinax interactive & batch) @ http://www.cen-elec.com Central Industries of Indiana--->Quality manufacturer of wire harnesses and electrical sub-assemblies - fax # 812-424-6838 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.