|
So, downloaded the latest 5733OPS from ESS and took the install option
on all 15. All 15 have an install status of "Installed" which is kind
of a red herring. You really don't*know* if anything besides the
"placeholder" has actually installed. Case in point, Python 2.7 is
still MIA. Installed from media. Applied PTF's and I don't see any
errors yet I don't see any evidence of Python 2.
I'll pack it in for now . I have a customer visit this AM and if
I get a chance, I'll turn my attention to getting everything that should
have been installed, to actually install, when I get back to it. Fun!
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
LinkedIn -www.linkedin.com/in/petehelgren
Twitter - Sys_i_Geek IBM_i_Geek
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
LinkedIn - www.linkedin.com/in/petehelgren
Twitter - Sys_i_Geek IBM_i_Geek
On 7/31/2016 9:01 PM, DrFranken wrote:
Since 5733OPS isn't in the default install list you need to add the *BASE--
and each of the options to the install list. I have always done that as I'm
pretty sure the first document I saw said "There are 15 options to be
populated over time." No idea where I saw that but it stuck in my head.
Because they are not in the list the default install option or upgrade
from any previous release wouldn't install any of them.
I would think if you took the "Install All" option (GO LICPGM option 1)
that it would install all 15 but I have never tried that because obviously
it will install all the other options as well and I don't normally want
that!
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
On 7/31/2016 9:17 PM, Pete Helgren wrote:
Thanks. I am not sure where I got off the rails (no pun intended).
When I installed V7R2 ages ago and heard about the announcement of
5733OPS I did what most did and installed what was available then. Not
thought to add what wasn't there (who woulda known!)
I don't suggest a new way to install, BUT if having all 15 options
installed, even if they are "placeholders", is a requirement then the
install license program routine should install them all. Stuff that is
required during install should happen well, um, should happen
automagically (IMHO).
Thanks for all the replies. I feel better because misery loves
company...
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
LinkedIn - www.linkedin.com/in/petehelgren
Twitter - Sys_i_Geek IBM_i_Geek
On 7/31/2016 4:25 PM, DrFranken wrote:
Well we can debate the nuances of the way IBM did this but you need to
understand that they wanted to make the process as 'simple' as
possible for them to cut these new options loose. To do that they
created all these options (which by the way are likely already in your
current download) Just install options
3,4,5,6,7,8,9,10,11,12,13,14,15.) Installing these empty option is
el-quicko as there am nothing there. Thus as they cut PTFs loose
(VASTLY simpler than adding an LPP option) you get the new feature
option or update.
Maybe I eat sleep and breath LPPs and PTFs too much but it made
perfect sense to me. For the record if a PTF is for an option of a
product that you do not have installed it makes perfect sense that if
you want the PTF you would need the option installed. Documentation of
that is not needed.
I did ask Alison if there was any discussion about changing this
method of distribution and I got a flat out table pounding laugh. And
then she said: "And this is the first time I can say this is NOT
because it's you asking Larry, it's just not gonna happen!"
Honestly though do you want IBM coming up with a slick new install
upgrade delivery and notification process or do you want them making
with the new options? Me I'm voting for the latter.
- Larry "DrFranken" Bolhuis
www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/opensource.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
