|
That's why you ALWAYS document these changes in a single CL program.
Then when you do such a thing, to put it back you simply run the
program! Shazaam! your done.
So, each and every time you enter a command to make a change such as Rob
suggests, copy that line into your CL program and compile it. Now it's
ready for disaster recovery, auditors that want to see what changes have
been made etc.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 6/14/2013 7:02 AM, rob@xxxxxxxxx wrote:
Slipping the OS may affect a few CHGCMDDFT's, eh? Perhaps even a few--
GRTOBJAUT to some somewhat restricted commands?
Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108
6928N 400E Kendallville, IN 46755 http://www.dekko.com
--
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.
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.