Re: CGI Automated Documentation

Peter

the "quick and dirty" way is to use the ls command in qshell. I was able to
use this to get directory information into a file using this method though
it took a bit of trial and error. I had one of our unix guys give me a hand
with the format of the command I needed.

I got this hint from here so it should be in the archives somewhere (try
searching on QSHELL or IFS), alternatively post again and I will send the
source of what I did home so I can post it.

I haven't had time to become familiar with the unix API's yet so using
qshell plugged the gap.

Hope this helps

Evan Harris

>I am thinking about creating a "flat" file on the AS400 and load (from my
>specific CGI directory) all the object links in it.  I know that I can display
>the objects links using DSPLNK but  I need them in a file instead, so I
>can read
>this file in a CL  but there are no other output options but screen or paper.
>How can I do this?
>
>This is because 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
>know
>the folders to use in our IFS but I want to do all this on the AS400.
>
>TIA
>
>Peter Vidal
>Pall Aeropower Corp.
>Senior Programmer Analyst
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.