Re: V5R3-V5R4 Updated Problem -- MIDRANGE-L

Jim,

  We went back and looked at disk space.  We found that on average most of
the systems increased by about 5GB going from V5R3 to V5R4 (This
includes the increase LIC size area, OS/400, and LPPs).  We haven't seen
much in the way of temporary space increases.  I wonder if that is
because we have not been using the latest cume 7002540, and are still
doing upgrades with 6297540.


Pete

---------------------------- Original Message ----------------------------
Subject: Re: V5R3-V5R4 Updated Problem
From:    "Jim Franz" <franz400@xxxxxxxxxxxx>
Date:    Wed, February 14, 2007 2:51 pm
To:      "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
--------------------------------------------------------------------------

Pete - with all the installs you have done, have you run into the
issues I raised recently, temp storage after ipl more than double
from 5.3 (I think mostly from sysval QSFWERRLOG, and
the QIBMHELP server running by default) ?
Can you confirm my observations or identify what other features
in 5.4 can cause this. Have only done 4 systems and all are
small systems where this could be noticed.
Jim Franz
----- Original Message -----
From: "Pete Massiello" <pmassiello@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, February 14, 2007 12:02 PM
Subject: [SPAM] Re: V5R3-V5R4 Updated Problem

Jerry,

  Many times there are PTFs for the Journal receivers on the V5R3 box to
be able to use a V5R4 journal receiver if you had to roll swap during
the interval when the two machines were at different levels. This would
be a real issue if you had done the Production box first, and the
backup box second.  If you are up to date on PTFs on the V5R3 box, you
will probably already have these on there if they were required (a
benefit of waiting a little).

   Also, if someone creates an object on the V5R4 box that uses
something
that is a new feature/function of V5R4, then when you go to save it
under *PRV it won't be saved, and you will have objects not saved.
For this reason, changing the compile commands to *PRV is a good idea
until you change the backup back to *CURRENT.

JMHO,

Pete

---------------------------- Original Message
----------------------------
Subject: Re: V5R3-V5R4 Updated Problem
From:    "Jerry Adams" <jerry@xxxxxxxxxxxxxxx>
Date:    Wed, February 14, 2007 11:44 am
To:      "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
--------------------------------------------------------------------------

Pete,


I am going to upgrade our backup box to R4 soon.  In the meantime the
production box will be at R3 for a week or two.


I know that the saves that I do on the backup will have to be done at
the prior release in order to be usable on the production box, but is
there anything else along those lines that I'll need to consider in the
interregnum?


Thanks.

* Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Pete Massiello wrote:

John,

Before the upgrade, there was a PTF that you had to apply at V5R3 so
that
your power on/off scheduled entries did not disappear.  That is
SI22147.
I have done about 50 upgrades of V5R3 to V5R4, and haven't lost any
job
schedule entries.

Pete

---------------------------- Original Message
----------------------------
Subject: V5R3-V5R4 Updated Problem
From:    "John Taylor" <lists@xxxxxxxxxxxxxxxxxxxx>
Date:    Wed, February 14, 2007 11:20 am
To:      "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
--------------------------------------------------------------------------

Hello,

We did an R3-R4 upgrade over the weekend, and I just now realized
that
all
of our Job Schedule Entries are gone! Fortunately, we have a backup,
but
it
is at V5R3. Does anyone know if it's safe to restore R3 job schedule
entries
onto R4?


Regards,

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