On Monday, 12/05/2005 at 10:58 CST, Rick Troth <[EMAIL PROTECTED]> wrote: > See other note from me (just sent). > The reason for changing PROFILE EXEC of an IBM-maintained "user" > is that when it runs on *my* system, I will have certain > behaviours that I want applied to all service v-machines. > Combine that with the growing number of TCP/IP service v-machines > and the case becomes ever more heavy. > > Again, I don't expect to change IBM on this point.
We are in violent agreement :-) that installations should have the ability to modify pre-start and post-shutdown activities. Hopefully DTCPARMS and the exit capabilities for TCP/IP meet the requirement. The genesis of DTCPARMS & Co. was my irritation at always having to modify a zillion things every new release. I was a System Tester at the time, having responsibility for TCP/IP and I simply couldn't keep track of multiple stacks, all their servers, and all their parms. Creating multiple "stack sets" was a royal pain. I couldn't tell at a glance which servers might be affected by an LE upgrade and which would not. All sorts of things. (My blood pressure rises just thinking about it all again...I thought I was over it... guess not! :-) ) The one thing still missing is a way to start TCPIP with a parameter that is used to substitute strings in PROFILE TCPIP. I.e the ability to code :Suffix.2 in DTCPARMS at runtime and have AUTOLOG and PORT statements with things like 21 FTPSERVE&S processed with substitution. Cloning stack sets would be much easier. It can be done with :Exits., of course, but having it built-in would have been nicer. Oh, well. Alan Altmark z/VM Development IBM Endicott
