Answer Wiki:
Hello,
Please write to my email address box: (khalifamorin@yahoo.com)
My name is Morin, a good looking girl.
I
became interested in you after going through your profile today and i wish to
continue relationship with you which if nature will permit we have a
long way to go.
I
have a special reason of contacting you which i will make known to you,
tell you more about myself and also send my pictures to you. I will
like you to get back to me through my email address:
(khalifamorin@yahoo.com)
Morin
To see all answers submitted to the Answer Wiki: View Answer History.
Requests are often made for the names of “system files” that contain some type of info. Most things are not exposed through “system files” on AS/400s. General exceptions are areas that were brought in for S/36 support or for providing variations of S/36 functions and also database “DBMS” elements in order to meet Codd’s Rules.
So, for example, lots of stuff that was used for Office/400 is exposed in “system files”; and you can query attributes of schemas, tables, views, etc.
But most native stuff is exposed through “objects”. A DDM file is an object of type *FILE. File objects can be queried through commands or APIs. Attributes are reported back into programs through those queries.
So, if you need info about DDM files, you might run the DSPFD command (‘Display File Description’). You might run it something like this:
DSPFD FILE(*ALLUSR/*ALL) TYPE(*BASATR) OUTPUT(*OUTFILE) FILEATR(*DDMF) OUTFILE(QTEMP/DDMFS)That will create a list of *ALL DDM files in all user libraries (*ALLUSR) on the system. The list will be built in a file named DDMFS in library QTEMP. Only the base attributes (*BASATR) will be put into the list.
You can then query that file as needed.
You need info about the remote file that the DDM file references, you will probably want to request TYPE(*ATR) to grab the fuller set of attributes instead of TYPE(*BASATR).
Tom