IBM has a history of changing defaults. Mostly to stop users from
shooting themselves in the foot. (You know, people like you.) One
example is that default on SAVLIB was changed from *no on saving access
paths a long time ago. People may have been upset that their save time
jumped but, by golly, they didn't have to wait a week to use their system
upon a restore while it was rebuilding access paths.
Besides, starting with ENDTCPSVR *ALL is bad practice as some services
take a long time to stop and if you don't wait you corrupt your system.
Like *CIMOM; muck that up and you just lose telnet (like 5250). A rather
important thing to a few IBM i shops. *MGTC can also be a persnickety
child.
Rob Berendt
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.
midrange.com
