One last comment,

On a daily basis, from the recommend fixes page, I check PTF Cover Letters - All PTF Cover Letters by Date
I usually then do SNDPTFORD, inputting the ones listed.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, December 18, 2015 3:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: Applying updates to IBM i

Cumes are only released two or three times a year. Groups are more frequent. Some as often as every other week.

The number of "recommended" fixes is not what it used to be. The individual group owners are more likely to just spin up a new group versus having to update a web site to point to individual fixes. However I still strongly recommend perusing the "recommended" fixes.




Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/18/2015 03:17 PM
Subject: Re: Applying updates to IBM i
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I want to re-iterate Rob's comment, you really need to check this because
many PTFs never make it to a CUM or any Group.

Oh, I thought the CUM would include (supersede) Groups, but it sounds like
that's not the case. Here's what I see in FixCentral:
http://www.screencast.com/t/UFziT6DEJ At closer inspection I would guess
the CUM is for the OS and the Groups are for things on top of OS?? Then I
can use GROUP_PTF_CURRENCY (below) to see which Groups need updating and
individual order those, correct?


PTF_GROUP_CURRENCY PTF_GROUP_ID
PTF_GROUP_TITLE


UPDATE AVAILABLE SF99720 Current
Cumulative PTF Media Documentation
UPDATE AVAILABLE SF99719 720 Group
Hiper
UPDATE AVAILABLE SF99718 720 Group
Security
UPDATE AVAILABLE SF99715 720 Backup
Recovery Solutions
UPDATE AVAILABLE SF99775 720 Hardware
and Related PTFs
UPDATE AVAILABLE SF99702 720 DB2 for
IBM i
UPDATE AVAILABLE SF99713 720 IBM HTTP
Server for i
UPDATE AVAILABLE SF99717 720
Technology Refresh
UPDATE AVAILABLE SF99747 720 DB2 Web
Query for i V2.1.0
INSTALLED LEVEL IS CURRENT SF99714 720
Performance Tools
INSTALLED LEVEL IS CURRENT SF99716 720 Java

INSTALLED LEVEL IS CURRENT SF99766 720 Print
PTFs
INSTALLED LEVEL IS CURRENT SF99767 720 720
TCP/IP PTF



Paul Steinmetz, thanks for the notes on automation.


Aaron Bartell
litmis.com - Services for open source on IBM i


On Fri, Dec 18, 2015 at 1:53 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

<There's also "recommended" fixes listed at
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes

I want to re-iterate Rob's comment, you really need to check this
because
many PTFs never make it to a CUM or any Group.
Also, don't forget about the TR.

For V7R1
SNDPTFORD PTFID((SF99711)) CHKPTF(*YES) - this will order all latest
groups.
SNDPTFORD PTFID((SF99710)) CHKPTF(*YES) - this will order latest CUM

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Friday, December 18, 2015 2:43 PM
To: Midrange Systems Technical Discussion
Subject: Re: Applying updates to IBM i

As a general rule I go to fix central and order the cume and all groups
once a quarter and put those on.
Once you have your list of groups populated then you can do something
like
you requested. See QSYS2.GROUP_PTF_CURRENCY. It will compare your
groups
with what is the current level at IBM.

There's also "recommended" fixes listed at
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes

Various vendors will also list PTF's. Domino, Infor, etc.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/18/2015 02:03 PM
Subject: Re: Applying updates to IBM i
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



For the archives: http://bit.ly/ibmi-maint-strategy (IBM's website).

Question: Is there a tool that lists your currently installed IBM i
software and whether there are updates for it? I'd imagine such a tool
would be in IBM Systems Director Navigator for i, but unfortunately it
isn't working on this particular system (Server 500 error).

But maybe fix central works better now.

So far so good.


Aaron Bartell
litmis.com - Services for open source on IBM i


On Fri, Dec 18, 2015 at 11:09 AM, Bradley Stone <bvstone@xxxxxxxxx>
wrote:

I've done it on my machine a few times. It's one of those things that
I
didn't do often and each time took some work remembering (similar to
changing cache battery packs.. ugh..)

I recall using fix central and it worked 1/2 the time. Other times I
was
forced to download images and install them with these instructions:

http://www-01.ibm.com/support/docview.wss?uid=nas8N1013745

Not fun, no. But maybe fix central works better now.

My next step will most likely going to a cloud solution when I'm
forced
to
update. Then I won't have to worry about PTFs or cache battery
packs..
just that the company stays in business as long as me. :)

Brad
www.bvstools.com

On Fri, Dec 18, 2015 at 9:52 AM, Aaron Bartell
<aaronbartell@xxxxxxxxx>
wrote:

I am forcing myself to step further into IBM i admin
responsibilities
so
I
can have a better understanding. My next step is learning how to
apply
updates (CUM, PTF, etc). I've done it before, but it is like once
ever
couple years. I started looking at SNDPTFORD as it relates to a
specific
PTF I wanted to install (for Node.js) but then realized maybe I
should
just
do *CUMPKG and I would get the PTF in there (based on my CUM
understanding). And after I pondered that I realized I need a high
level
overview of how best to approach keeping an IBM i up to date.

Does anybody have such a resource to point me at? I've found many
bits
and
pieces here and there, but nothing that gives a high level overview
and
best practices.

Thanks,
Aaron Bartell
--
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.


--
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.

--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].