Good to know.

What are "best practices" of when to apply a TR? In general is it the same
as everything else?...

- bleeding edge potentially hurts
- getting too far behind hurts too

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


On Fri, Jul 1, 2016 at 10:07 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

TR's do NOT encompass other PTF groups.

In fact, let's say TR 21 comes out. And they have fancy slides and
whatnot of all it's wonderful features listing BRMS, DB2, etc. Somewhere
in the fine print will be that the new functions of (let say DB2) will not
be available until the next group ptf for that product comes out.
The TR may be, scratch that, is most likely, a prerequisite for that
group.


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: 07/01/2016 11:03 AM
Subject: Do TRs cover other PTF groups?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



tl;dr Do Technology Refreshes generally "catch you up" with PTFs from
other
PTF groups?

When I check PTF_GROUP_CURRENCY I get the following.

PTF_GROUP_CURRENCY PTF_GROUP_ID PTF_GROUP_TITLE
UPDATE AVAILABLE SF99715 720 Backup Recovery Solutions
UPDATE AVAILABLE SF99775 720 Hardware and Related PTFs
UPDATE AVAILABLE SF99716 720 Java
UPDATE AVAILABLE SF99717 720 Technology Refresh

I was hoping I could just to a TR and it would catch up Java/BRMS/Hardware
PTFs, but I now believe that is a poor assumption on my part.

Below are URLs for PTF groups I compared to come to my conclusion that TRs
don't necessarily encompass other PTF groups.

http://bit.ly/SF99775
http://bit.ly/SF99717

Aaron Bartell
litmis.com - Services for open source on IBM i
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


As an Amazon Associate we earn from qualifying purchases.

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