Re: Catching up of 7.1 PTFs

Yes, i've gotten in the habit of doing an APYPTF with *all and *perm (none
of my clients have those weird "test" ptfs), and after the IPL doing a
DLTPTF and also a search for savfiles on the qsys related to old ptfs.
Most of our clients have systems badly migrated lots of times and
accumulate tons of savf and old ptfs...


On Fri, Jun 14, 2013 at 2:16 PM, <rob@xxxxxxxxx> wrote:

There's the rub. Defining "necessary". Hmm, probably not. Unless you're
still having difficulties applying PTF's and whatnot.
It just may make the ptf installing a whole lot easier though.

Which brings up a thought, You probably should also install all ptf's perm
(if you can) before slipping lic and os. To do otherwise may orphan some
ptf copies perpetually on your system. For example, if I had PTF SI12345
temp applied and it replaced the program CLCOMPILER by storing the old
copy in QSI12345B1 before restoring the new one. Now I slip OS and
SI12345 came perm applied on this respin. Now QSI12345B1 will stay on my
system for all eternity. Which may explain some of those numerous save
files on your system from old versions of the OS. Trust me, the time it
takes for an extra IPL is small compared to the manual effort of cleaning
up these save files.


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: Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 06/14/2013 12:18 PM
Subject: Re: Catching up of 7.1 PTFs
Sent by: midrange-l-bounces@xxxxxxxxxxxx



In any case, it shouldnt be a problem if one does a CHGIPLA, sets system
to
restricted, Slips LIC and IPL's to restricted mode and then install the
rest of the PTFs, would it be necessary to slip the OS too?


On Fri, Jun 14, 2013 at 9:52 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

That's why you ALWAYS document these changes in a single CL program.
Then when you do such a thing, to put it back you simply run the
program! Shazaam! your done.

So, each and every time you enter a command to make a change such as Rob
suggests, copy that line into your CL program and compile it. Now it's
ready for disaster recovery, auditors that want to see what changes have
been made etc.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 6/14/2013 7:02 AM, rob@xxxxxxxxx wrote:

Slipping the OS may affect a few CHGCMDDFT's, eh? Perhaps even a few
GRTOBJAUT to some somewhat restricted commands?


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

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