|
>We need to know if the *FILE is a LF, PF or *PGM is a CL etc. >Hate to hard code a list. Not much help I'm afraid, but you could WRKOBJPDM and F1 in the object attribute field to pick up the ones that PDM uses. Copy & paste into a file and you have a start. When users complain they can't access an MI program (sans attribute) then you can add a blank record to your validation file. A curiosity question: will you validate on the combination of object type and attribute (i.e. *FILE and (LF or PF or LF38)) or separately by type and then by attribute (which might allow *PGM and PF38)? --buck
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.