|
i have seen homegrown doc software that scans source for things like "/copy" in order to document where used. Do not know the layout of your cgi source, but you might be able to do a similar thing, scanning the rpg for where you retreived the source? jim ----- Original Message ----- From: <Peter_Vidal@pall.com> To: <web400@midrange.com> Sent: Tuesday, March 26, 2002 9:12 AM Subject: [WEB400] CGI Automated Documentation > Hi group. I have a very special request this morning (Well, at least, is really > challenging for me) > > We document in a weekly basis every production program we have in our system. > As part of the process, we obviously use the DSPPGMREF command in order to pull > all the information we are looking for and then we load all this references into > a database file (let's call it PGMREF), so we can search over any piece of > information we want, like WHERE USED and so on. Now, we need to document also > ALL OUR CGI SOURCES in terms of the files used in each one and include them in > our database PGMREF in order to have the WHOLE PICTURE. > > I am not too strong about IFS and I am studying it; however, do you know if is > there a "standard" way that I can address this request? Some guidance is > needed. > > I really appreciate your help in advance. > > Regards, > > Peter Vidal > Pall Aeropower Corp. > Senior Programmer Analyst > > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. >
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.