Rob van der Heij <[email protected]> wrote :- > I'd say an important part of the trick is that SYSPROF incorporates > calls to an optional local exit. When you need to modify shipped files > or code to make that call happen, we just moved the problem from one > place to the next. > As for at what moments to invoke such an exit (eg before accessing the > A-disk, after accessing the D disk, etc) a committee would end up with > a massive number of options and choices. Instead, I would suggest to > look at the IGS modification. That has grown during more than a decade > and probably has the things you tend to look for IRL.
> Rob The technique of incorporating calls to an optional local exit in the SYSPROF, such as I have implemented here, is not at all unique. It is also used within some parts of IBM. However, Rob is right, that there are probably an significant number of variations of what people may want. This might make the architecture of such exit calls difficult. My suggestion would be to reverse this and externalise all the IBM code from the SYSPROF EXEC in such a way that it is not fiddled with. The supplied SYSPROF would then become a series of simple calls to the IBM code. Each call would have a defined and notated purpose and this could easily be interspersed with user code with minimal risk or interference. Colin Allinson Amadeus Data Processing GmbH
