RE: Programatically check for an IBM supplied profile

["John Earl" <john.earl@xxxxxxxxxxxxx>]

Jim,

You've identified a couple of profiles that sort of break the rules of
standard IBM Profile identification.  Normally you can identify IBM
profiles because they were created by user *IBM on System '00000000', or
if they were created by QLPINSTALL and the created on system is the
current system name and the created date/time is roughly equivalent to
the date/time the operating system was loaded.


However, the QFAXMSF and QWEBQRYADM profiles are loaded as a part of the
load of an LPP, which may occur directly after the OS is loaded, or
could happen weeks, months, or years later.  

It turns out the best way to programmatically check for IBM profiles is
to keep a table of these profiles and check all profiles on the system
against the table.  If something stands out, then follow up on it.
Absent a clear marker in the profile that indicates it was created by
IBM (as Kendall suggested), you really have to put the list together the
list on your own (That's what we did in our product).

jte

--
 
John Earl, VP and Chief Technology Officer
PowerTech:   253-872-7788
Direct:          253-479-1408
Mobile:          206-669-3336
John.Earl@xxxxxxxxxxxxx
 

 
 
Email is an excellent way to communicate material that is not time
sensitive.  If your communication is of a more urgent nature, please
call. 
 
===========================
This email message and any attachments are intended only for the use of
the intended recipient named above and may contain information that is
privileged and confidential. If you are not the intended recipient, any
dissemination, distribution, or copying is strictly prohibited. If you
received this email message in error, please immediately notify the
sender by replying to this email message or by telephone and delete the
message from your email system. Thank you.
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> franz400@xxxxxxxxxxxx
> Sent: Tuesday, February 26, 2008 6:32 AM
> To: Midrange Systems Technical Discussion
> Subject: Re: Programatically check for an IBM supplied profile
>
> just checked & found some exceptions (v5r4m5) ...
> QFAXMSF                 QSECOFR
> QWEBQRYADM        QSECOFR
>
> jim franz
>
>
>
> ---- Francis Lapeyre <flapeyre@xxxxxxxxx> wrote: 
> > DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*USRPRF) DETAIL(*FULL) 
> OUTPUT(*OUTFILE)
> > OUTFILE(FMLLIB/PRF)
> >
> > STRSQL
> >
> > SELECT * FROM fmllib/prf WHERE ODCRTU not in ('*IBM','QLPINSTALL')
> >
> >
> > On Tue, Feb 26, 2008 at 7:52 AM, Crump, Mike 
> > <Mike.Crump@xxxxxxxxxxxxxxxx>
> > wrote:
> >
> > > I'm fuzzy on this but I could have sworn there was a way to 
> > > programmatically check for profiles that were IBM 
> supplied.  I want 
> > > to do some mass changes/updates but I want to specifically bypass 
> > > IBM supplied profiles.  I've looked through all my programs and 
> > > notes and can't find anything on the subject.
> > >
> > >
> > >
> > > Am I not remembering correctly or does anyone have any 
> idea on how 
> > > to do a check like this in CL?
> > >
> > >
> > >
> > > Michael Crump
> > >
> > >
> > >
> > > Manager, Computing Services
> > >
> > > Saint-Gobain Containers, Inc.
> > >
> > > 1509 S. Macedonia Ave.
> > >
> > > Muncie, IN  47302
> > >
> > > 765.741.7696
> > >
> > > 765.741.7012 f
> > >
> > >
> > > Propaganda
> > > What lies behind us and lies before us are small matters 
> compared to 
> > > what lies right to our faces.
> > >
> > > This email and its attachments may be confidential and 
> are intended 
> > > solely for the use of the individual to whom it is addressed. Any 
> > > views or opinions expressed are solely those of the author and do 
> > > not necessarily represent those of Saint-Gobain.  If it did, it 
> > > would be folded, mutilated, watered down, politically 
> corrected, and 
> > > would show up a week later if at all.  If you are not the 
> intended 
> > > recipient of this email and its attachments, you must 
> take no action 
> > > based upon them, nor must you copy or show them to anyone.
> > >
> > > Please contact the sender if you believe you have received this 
> > > email in error.
> > >
> > >
> > >
> > >
> > >
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
> > > mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To 
> > > subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please 
> > > take a moment to review the archives at 
> > > http://archive.midrange.com/midrange-l.
> >
> >
> > --
> > Francis Lapeyre
> >
> > Da mihi sis crustum Etruscum cum omnibus in eo.
> > --
> > This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing 
> > list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
> > unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, 
> please take 
> > a moment to review the archives at 
> > http://archive.midrange.com/midrange-l.
>
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, 
> please take a moment to review the archives at 
> http://archive.midrange.com/midrange-l.