As you learn, remember the oath doctors swear: "First, do no harm!"
There are a lot of commands used to administer the iSeries that can
do harm as well as good. Not always from maliciousness, but because
some of the controls are "two-edged swords--" changing a parameter
in one direction can cure a problem, changing it in another can make
it worse!
If you have a test machine to work on, that's where to do your
investigations. And you can usually create your own private copy of
whatever it is you want to explore so you won't damage the real one!
If you're -really- a glutton for punishment, start investigating job
and performance controls-- subsystems, routing entries, classes,
modes, etc. etc. Useful information, but definitely "201" or higher
classes!
--Paul E Musselman
paulMmn@xxxxxxxxxxxxxxxxxxxx
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.