All,
Have any best-practices evolved as to where non-QSYS.LIB IFS objects should be
located on a iSeries-centric system, specifically as regards restoring in a DR
scenario?
For example, ScottK recently published a clever QShell script (see link #1
below) to copy spool files to HTML. The instructions described placing the script
in /usr/bin which, if I understand correctly (see link #2) is akin to C:\WinNT or
QSYS.lib. Other utilities may create their own directories in /root or place a
.jar file somewhere in /Javautil. Or whatever.
Our old DR scenario ("restore complete system to a Quickship box") is no longer
an option and I'm searching for techniques to simplify the restore of core
functions to a spare box at a hotsite. Restoring QSYS.LIB is not a problem, I'm
looking for techniques to make it simpler to identify the non-QSYS objects that
need to be saved and restored. For example, I doubt that you'd want to restore
the entire /usr/bin directory to another box, but how do you identify the
customized objects that should be restored? Do naming conventions help or should
there be a completely different directory under /usr for scripts and macros and
the like? If you add new directories, what about problems with CLASSPATH? We
fought major battles with CLASSPATH when we first started using POI. We've
already had one contract .jsp programmer devise his very own, unique directory
structure that does not seem to correspond to any of the standard templates -
what about the next time we hire a contractor?
How do the *nix people handle this? Many thanks, JK
#1
http://www.systeminetwork.com/artarchive/newsletter/w/1001/i/6731/a/55354/index.html
#2
http://www.linfo.org/usr_bin.html
---- Msg sent via Internet America Webmail -
http://www.internetamerica.com/
midrange.com
