Re: Opinions wanted regarding how to install ISV software

I've always chosen the home grown approach too.  All of our software products use an install process built around the IBM i OS LODRUN command.  During the install it can decide if it is a new install or an upgrade and act accordingly.  For license control, we also have opted for a home grown solution.  That way, we are not at IBM's whim if and when they decide to make changes.  This has worked well for us for 30+ years.

Rich Loeber
Kisco Information Systems
http://www.kisco.com[1]
-------------------------

Quoting Nathan Andelin <nandelin@xxxxxxxxx>:

I've been considering 2 alternatives. One option is to use IBM "System
Manager" to package products which can be installed by using the RSTLICPGM
command. Another option is to package products into "save" files and have
shops use RSTLIB with a custom INSTALL command to complete the installation.

IBM's System Manager approach seems like something of a dark art. The
documentation is minimal, old, conceptually challenging, and much of it is
out of date. The product is out of date. IBM evidently uses it as a basis
for OS releases and PTFs. Why doesn't IBM update it's "package manager"?

With a custom approach to managing products, packages, and fixes I would at
least have a handle on the process. But that would require quite a bit of
effort and time. In the Windows world, products like Install Shield fill
that kind of need.

What approach would you recommend?
--
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.

Links:
------
[1] http://www.kisco.com