Re: V5R4 to what, and likely only until January

John,

Here were my estimates, actual time was less, 10 to 12 hours.
ANZOBJCVN has a report option you can run weeks before, will tell you
which objects will not convert and tell you how long to convert objects.

Current estimate - 15 to 20 hours

1. Dedicated System save - 4 to 5 hours
2. Apply the upgrade - 1 hour
3. IPL - 1/2 hour
4.. Apply PTFs - 1 hour
5. IPL - 1/2 hour
6. Object conversion - Total estimated conversion time for library
objects. . . . . . . . . . . : 07:18:03
7. Confirm
8.. Test

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Monday, May 13, 2013 9:58 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R4 to what, and likely only until January

Interesting. I had configured a couple of printers with TSPLPRD but
converted to DEVD so that isn't an issue.

We don't have JDE. Very limited use of sftp. The file known_hosts is
currently located in ~/.ssh so my guess is that JDE does that a bit
differently. Something to be aware of, nevertheless.

Your other issues don't appear to be applicable.

Thanks for the heads-up. Reminds me of my first upgrade, from 1.2.0 to
2.1.1. Very long night. Went smoothly, mostly. But, joblogs started
printing. Lots of stuff cobbled together, and a library list with TWO
empty positions - installer wanted to add THREE libraries. KABOOM at 4 in
the morning.

John McKee


On Mon, May 13, 2013 at 8:33 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx

wrote:

John,

Disks look ok, there is disk space planning guide in the upgrade PDF
if needed,

Here are some upgrade issues we experienced that did not show up on
our R&D LPAR.
Pencor05 V6R1 upgrade issues

1) AS/400 writers failing -
Issue - Any AS/400 printer configured to print to print server for
Paper Cut using SETRMTPQ using TSPLPRD system driver program failed.
Reason - ANZOBJCVN did not identify 3 system objects because they
should have converted.
Resolution - obtain V6R1 TSPLPRD savf from IBM, restore 3 system
objects

2) JDE Secure file transfers using Open SSH failing.
Issue - JDE secure file transfers using Open SSH were failing.
Reason - V6R1 upgraded Open SSH 3.5p1 to 3.8.1p1, creating a new
subdirectory from which SSH could be called. IBM upgrade failed to
copy SSH_known_hosts file to new subdirectory.
Resolution - SSH_Known_hosts file was copied from 3.5p1 to new 3.8.1p1
subdirectory.
3) Issue - PTCICOSOM FTP file transfer could not be completed.
Reason - Beginning at V6R1, AS/400 FTP will try and use Extended
Passive Mode, which was the case with this issue. Verizon server was
capable of extended, but somewhere between Pencor05 and Verizon this
is being blocked, random variable port.

Resolution - dtaara QUSRSYS/QTMFTPEPSV) was created, which disables
EPASV

4) SPY not working

Issue - Users could not access any part of SPY

Reason - V6R1 changed public authority from *USE to *EXCLUDE for
system object QPMLPMGT. This object is used to confirm license product

information.

Resolution - changed public authority from *EXCLUDE to *USE for object
QPMLPMGT

SPY had a secondary issue resulting from SPY 8.8.1 upgrade. Not all
group authorities working properly for all users. Added individual
authority as temporary fix.


5) Advanced Job Scheduler displaying partial completion messages.
Reason - V6R1 replaced some AJS objects with a version that performed
differently than V5R4.

Resolution - IBM sent new V6R1 objects which produced same
functionality as V5R4.


6) Some reports no longer emailed.
Reason - V6R1 replaced changes to Pencor printfiles.

Resolution - Copy new version to SYSCHG, then apply Pencor defaults

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Monday, May 13, 2013 6:07 PM
To: Midrange Systems Technical Discussion
Subject: V5R4 to what, and likely only until January

I'm not sure if an upgrade will happen. Or should. Boss related that
software support for V5R4 was to end in September. I thought I read
that it had been extended for an additional hefty charge.

Currently, it looks like the system will be shut down Jan 1, 2014.
But, that is not in stone as yet.

I know that analyze object conversion will need t be run. I suspect
we have some vendor stuff that won't pass. I am thinking about DBU and

IQ.

What is end of life for 6.1?

We have a 520 with processor feature 735.

Also, I have seen in the past references that eith 6 or higher
required more disk space.

We have 8 4326 drives. They are at about 68 percent full. I am
confused looking at WRKDSKSTS. They are all DPY, in one ASP.

I have not had time to look at the MTUs yet. I started to look at the
7.1 MTU this morning. It is a lot larger than the MTU from the old
days of V2R2M0. I know they need to be read, and will do so.

Does the DASD look reasonable for an upgrade? If not, my next
potentially dumb question: I thought WRKDSKSTS showed how the drives
were configured for RAID. Is that only available from SST/DST?

My concern is if replacement drives are needed, for such a short
period, do all eight need to be replaced. Unit 1 is 68.4 percent
full. The other drives are between 67.7 and 67.8 percent full.

Does MTU have a ballpark upgrade time? Been 20 years since I have
even seen the MTU. Same for Boss. He was unaware of the potential
object conversion issues.

I know that PTFs need to be perm applied. I remember reading many
suggestions about upgrading to v5r4m5. Is that where the image
catalog was made available for IPL? Do CUME, HIPER, and/or group PTFs
need to be loaded and applied prior to upgrade? That sounds silly,
since upgrade is replacing stuff. But, system is way behind on PTFs,
and I am wondering if there are any weird issues that might only be

"discovered" at a bad time.

I apologize for all the basic questions. Been a long time since I
have done this and I just want to make it go as smoothly as possible.

Thanks for any suggestions.

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