You clearly understand the requirements of building subsystems for your
customers. This is good and it IS a valid method of supporting multiple
customers. As you state they use a 'non traditional (for i) interface'
which makes separating them with subsystems simpler than it would if they
used command lines and such. It's also likely that they don't use
traditional IBM i user profiles either I suspect which is another reason
LPARs can be better in some situations.
To build LPARs with scripting is a tad more difficult than building
subsystems that much is true. The commands in IBM i for subsystems are all
well defined and understood (OK By good admins at least!) so that is a win
for your method.
Effectively to build LPARs with a script you need connectivity to the HMC
with SSH to issue the appropriate commands there to create the partition
and it's profile. You also need connectivity to the storage (be that IBM i,
VIOS, or SAN) to issue the appropriate commands to create the new
partition, hopefully a clone by the way rather than empty disks!
Clearly this is more difficult for an IBM i specialist because the
commands on the HMC are, um, "Less clear" and involve somewhat more
parameters than CRTSBS, CRTCLS, ADDRTGE et al. But once it's all understood
it falls to SMOP once again.
- Larry "DrFranken" Bolhuis
"SMOP": Simple Matter Of Programming.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact