And I promise it won't be in VM/370 Release 2. Isn't forecasting the past or present much easier than forecasting the future?
-----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, December 05, 2005 8:44 AM To: [email protected] Subject: Re: PROFILEs [was: CP MSG/MSGNOH from SMTP] On Monday, 12/05/2005 at 10:35 EST, Jim Bohnsack <[EMAIL PROTECTED]> wrote: > What SYSPROF did you refer to in the "sniplet" below? Is that SYSPROF EXEC > from the S-disk? I know you were talking about TCPIP but I didn't find a > SYSPROF on any of the 4TCPIP40 disks. SYSPROF EXEC on the S-disk gets > serviced and is a pain in the lower back. I think that just about everyone > has a SYSPROF2 or something like that. The last RSU I put on z/VM 4.4 hit > SYSPROF. The official IBM SYSPROF EXEC would benefit from a call to an > exec such as TCPRUNXT or SYSPRRUN and a cast in concrete guarantee that > SYSPRRUN or SYSPROF2 would never be "maintained". > > Or am I not understanding something? Very possible. My reference to SYSPROF was a generic reference to a file intended to be modified by the customer. Like you, I think SYSPROF is sufficiently complex to need exit points. I've opened an internal feature request to add this function to a future release. Normally I don't make promises, but this time I will: I promise it won't be in z/VM 5.2. ;-) Alan Altmark z/VM Development IBM Endicott
