I am testing a software product and I want to be able to easily verify in an automated way that certain attribs are being set correctly...
In that case, you probably want a basic CL program that does most/all of the work.
Try these two commands to get some background on what happens:
DSPFD FILE(QAFDPHY) TYPE(*ATR) OUTPUT(*OUTFILE) FILEATR(*PF) OUTFILE(QTEMP/ATR) RUNQRY QRYFILE((QTEMP/ATR))
The DSPFD command converts the attributes of one of the system files on your system into an outfile. The RUNQRY command does a basic query of the content of the outfile. The outfile is created in QTEMP, so it will disappear when you sign off of your session.
That system file is one of the "model" files that are supplied with your system. In fact, it's the model that is used by the DSPFD command when you request TYPE(*ATR) for FILEATR(*PF) files. So the DSPFD command is retrieving the attributes of the file that defines what the output of the DSPFD output will contain -- kind of a circular reference there. (It seemed like a good example to use.)
By looking at what RUNQRY shows, you can see if the attributes that you're looking for are supplied. If they are, then the rest is fairly straightforward. If they aren't, then we need to know what else you need to see.
Post back if this is a direction we can go or not.
try writing a query instead of FNDSTRPDM