Re: wrkptfgrp and status not installed

["Jim Franz" <franz400@xxxxxxxxxxxx>]

Thanks Scott,
I have the current groups on order. This customer has me doing ptfs
2 times a year & this is all looking back at install 6 months ago. I
agree should always install as a group (and these were). For this 520
there have been a dozen or so ptf's that Svc Agent downloaded & I applied,
and I have had failures using sndptford to order groups and that is probably 
where
this problem lies. The other "rant" I will add to this is wishing IBM would 
add a
group for Printer ptfs. This site does a lot of lan, afp, ipds printing and 
am often
needing to get individuals. The Knowledge Base lists are nice but a group
would be better.
jim franz

----- Original Message ----- 
From: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, November 09, 2005 12:31 PM
Subject: RE: wrkptfgrp and status not installed


> > > PTF Group             Level  Status
> > > SF99530                5102  Installed
> > > SF99529                  49  Installed
> > > SF99503                   5  Not installed
> > > SF99298                  13  Not installed
>
> My guess is that you had successfully installed level 4 of SF99503 and
> level 12 of SF99298, then something that you or Service Director did
> updated the level and changed the status.  I have seen this happen when
> ATTEMPTING to order a ptf group and having the order fail.  Check your
> CD's to see if the levels match what is displayed.
>
> In my mind this is an aggravating and confusing behavior.  Try getting
> supportline to help you when your PTF Group status is "Not installed."
> We recently had a problem with WAS Express and even though all of the
> PTF's in the group were applied the tech would not help until the group
> also showed "Installed."
>
> In your case Jim, I would recommend ordering the groups and installing
> them as a package.  I'm not sure that installing the individual ptf's
> would update the group status, and doing it that way introduces a lot of
> potential for errors.  BTW,  the current group # for DB2 is 6 ad the
> current # for ESA is 15.
>
> Regards,
>
> Scott Ingvaldson
> iSeries System Administrator
> GuideOne Insurance Group
>
>
> -----Original Message-----
> date: Wed, 9 Nov 2005 10:19:26 -0500
> from: "Jim Franz" <franz400@xxxxxxxxxxxx>
> subject: Re: wrkptfgrp and status not installed
>
> i verified the "not founds " are truly not on system. Those installed
> have install date time = to other groups that did install ok. It appears
> (to me) the install of the DB2 group SF99503, which came on same
> cd as Hipers SF99529 just did not "load" all the ptfs (but did load
> some).
>
> SI15985  5722QU1  V5R3M0   Temporarily applied
> SI14600  5722QU1  V5R3M0   Temporarily applied
> SI12109  5722QU1  V5R3M0   Temporarily applied
> SI18198  5722SS1  V5R3M0   Not found
> SI18123  5722SS1  V5R3M0   Not found
> SI17975  5722SS1  V5R3M0   Not found
> SI17886  5722SS1  V5R3M0   Not found
> SI17884  5722SS1  V5R3M0   Not found
> SI17881  5722SS1  V5R3M0   Not found
> SI17880  5722SS1  V5R3M0   Not found
> SI17879  5722SS1  V5R3M0   Not found
> SI17836  5722SS1  V5R3M0   Not found
> SI17825  5722SS1  V5R3M0   Temporarily applied
> SI17824  5722SS1  V5R3M0   Not found
> SI17779  5722SS1  V5R3M0   Not found
> SI17757  5722SS1  V5R3M0   Not found
> jim franz
> ----- Original Message ----- 
> From: "Guy Terry" <guy.terry@xxxxxxxxxxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Wednesday, November 09, 2005 9:09 AM
> Subject: Re: wrkptfgrp and status not installed
>
>
> > Do an Option 5 against the Groups in error. This will display PTF's in
>
> > the group, and you'll be able to track down any that are causing the
> > 'Not Installed' status and do a 5 against them to see why.
>
> --
> 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.