|
Henrik, The QCDRCMDI (Retrieve command information) API will give you the name of the CPP for any command. The API is documented in the OS/400 Program and CL Command API's book. Best regards, Carsten Flensburg ----- Original Message ----- From: <owner-midrange-l@midrange.com> To: "MIDRANGE-L" <MIDRANGE-L@midrange.com> Sent: Thursday, October 12, 2000 12:50 PM Subject: PGMREF and non-IBM Commands > > > Can anybody suggest how to make this easier? > > I shall expand an (one of many in house written) x-ref system. This is > a typical system that - based on output to file from DSPPGMREF plus > several extensions already - answers the 'Where used?'. > > In reality the needed extention is a matter of putting CPP's for in > house written commands in the same outfile as the one loaded by > DSPPGMREF. > > One solution is: > o DSPOBJD xxxx/*ALL *CMD into an outfile > o PRTCMDUSG (several times if more than 50 commands) to a > spoolfile, then move to a DB-file and then another DB-file > o DSPCMD to a spoolfile, then move to a DB-file and then another > DB-file to get the CPP (I know you can do this in MI, but I > can't) > o Finally an HLL program to add records to the same file as used by > DSPPGMREF. > > Another solution: > o Add a constant parameter to each command definition: > PARM KWD(CPP) TYPE(*CHAR) CONSTANT(MyPgm) PGM(*YES) > o Add a dummy parameter to the CPP to recieve the new parameter > o Recompile all programs before running the update of Program > References. > > None of theese seems very easy. Does anybody have any good ideas to > improve this, including IBM API's to do some of the tasks. > > Henrik > http://hkrebs.dk > > --------------------------------------------------------- > This mail was sent through Eoffice: http://www.eoffice.dk > +--- > | 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 > +--- > +--- | 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-2025 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.