On Thursday, 07/22/2010 at 07:02 EDT, Kris Buelens <[email protected]> wrote: > OBEYFILE is your friend... > > Update PROFILE TCPIP > Extract the statements to change dynamically in a separate CMS file > Issue OBEYFILE (from a user listed in OBEY inthe PROFILE TCPIP) > > Notes: > > When you need to update the virtual "HW" of TCPIP (e.g. a new CTCA), you need > some other method. Like > CP FOR TCPIP CMD DEFINE ... > CP SEND CP TCPIP DEFINE ... > Be careful with the statements you copy from PROFILE TCPIP: you need to copy > entire "sections", because TCPIP replace the whole section. For example all > statements below PORT; or the whole HOME section
I despair. Let us, hand in hand, step forward into the 21st century and learn to use z/VM's ifconfig command, introduced ca. 2002. It encapsulates all of the needed commands into a single program. Not only does ifconfig display things in a well-understood format, it creates and changes them. You can even have IFCONFIG simply emit the needed PROFILE TCPIP changes and CP commands without actually doing them. That makes it a great teaching tool, too. ifconfig even tolerates use by those who aren't in the obey list; they simply get less information. As an aside, the NETSTAT OBEY command can be used instead of OBEYFILE for smaller changes. Learn both. Alan Altmark z/VM Development IBM Endicott
