RE: Validate Object Attribute

Well, list, valid values table etc (I wouldn't REALLY hardcode in pgm!)
would all mean the list is dependent on someone in MIS maintaining it.
But, you brought up a valid point. The problem is we need a quick way to
promote to production. I'm a contractor and made mention of the fact that I
had over 200 objects to promote and I'd write a quick CL to run through a
list of objects to send through their commands.  The data files are done
manually - CRTDUPOBJ.  So, now, it will be a  'quick' application for
everyone else. I'm not writing change management software - not really.
It's supposed to be serviceable but not really elaborate - a temporary
solution.
So, Buck,   I think I know the answer already. If I don't really need it
right now to get these objects into production SOON, it'll be phase 2 or
three - or a CM package (several months away).

Thanks again for your help.
Fran

At 12:07 PM 9/28/2001 -0400, you wrote:
> >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
>_______________________________________________
>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
>To post a message email: RPG400-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
>or email: RPG400-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/rpg400-l.