× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott,

I just looked at the page you referenced, and you are 100% correct.
I never took it as that way, and always removed the "custom library above
QSYS" from the library list. Yet, I have never ever had a problem with
QHLPSYS being in my library list.

I wonder why this hasn't been a problem for me, ever?

Pete
--
Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093

iTech Solutions because IBM i (AS/400s) didn't come with System
Administrators



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ingvaldson, Scott
Sent: Monday, April 25, 2011 3:11 PM
To: Midrange Systems Technical Discussion
Subject: RE: QHLPSYS during upgrade

I respectfully beg to differ, from Chapter 5, page 33 of Installing,
upgrading, or deleting IBM i and related software V7.1:

With the exception of QSYS, QGPL, QUSRSYS, QTEMP, or QSYS2, delete
all other libraries from the library list.

I don't remember the exact symptom but I do clearly remember getting bitten
by this several years ago, possibly during a V4R5 to V5R1 upgrade, I don't
really recall. I called SupportLine and told them what was happening and
the first thing they said was "You forgot to take QHLPSYS out of the system
library list."

I was sure that there was Knowledgebase Document on this issue but I can't
seem to find it now.


Regards,
 
Scott Ingvaldson
Senior IBM Support Specialist


-----Original Message-----
From: Pete Massiello [mailto:pmassiello-ml@xxxxxxxxxxxx]
Sent: Monday, April 25, 2011 1:46 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: QHLPSYS during upgrade

Jeff,

I do more IBM i upgrades in a month, than most System administrators
do in their life. I have never seen this in any instructions. Now, if you
want to remove the QHLPSYS LPP option from your machine, you would have to
do that. But a normal upgrade no need.

When you do a Restore of a system, and you have restored your system
values from the SAVSYS tape, it will have QHLPSYS in the System Library list
, but you won't have restored the QHLPSYS library until you do a RSTLIB
*NONSYS (or RSTLIB *IBM), and you might see a message that QHLPSYS isn't
found.

One other thing, I like to remove any libraries above QSYS during an
upgrade, but that is it.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Monday, April 25, 2011 2:06 PM
To: Midrange Systems Technical Discussion
Subject: QHLPSYS during upgrade

All,

This is more of a curiosity question.

For the last few release updates, the instructions always say to remove
QHLPSYS from QSYSLIBL during the upgrade. What is the reason for this? Is
it so no help is available during upgrades? ;)

If one permanently removes QHLPSYS from the library list, I assume command
help isn't available. OTOH, I have seen posts on this forum that state
QHLPSYS was NOT removed from QSYSLIBL during an upgrade and there were no
issues.

So . . .


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.