I make one simple exit point in SYSPROF that has satsified everything I'v e ever needed to do. Maintaining it across release boundaries is trivial. Just before calling the users PROFILE EXEC I call my SYSEXIT EXEC. The
sole job of SYSEXIT is to link and access a local programs disk (perhaps MAINT 31A) and invoke the ALLUSERS EXEC on that local programs disk. Wit h this strategy I can update the ALLUSERS EXEC anytime I want without needing to update the 190 disk. Brian Nielsen On Fri, 2 Jun 2006 16:38:42 +0200, Rob van der Heij <[EMAIL PROTECTED]> wrote: >On 5/30/06, Richard Schuh <[EMAIL PROTECTED]> wrote: > >> Give us exits in sysprof and we won't have the need to put our own stu ff >> on the S-disk. And while you are at it, give us a local system disk an d >> mode of our choice that is accessed by sysprof. > >Be carefull what you wish for... on the IBM Internal systems the >modified SYSPROF comes with exits that are so complicated that they >need to be provided with the platform again. There's a lot of points >in SYSPROF where you would want to be able to give control to some >local code. > >Whether done with one exit invoked in different places or with many >different exits, it makes for a complicated protocol to follow. >Something that is hard to maintain consistent over release boundaries. >Soon you end up with samples that you need to customize and then find >those samples to change with every release. And you're back to where >you started, except that you now have 5 times as much code involved... > >Rob >-- >======================== ========================= ========================
