On Sun, 5 Oct 2008 12:53:34 -0400, Rob Schramm <[EMAIL PROTECTED]> wrote:
>I am looking for the simplest way to intercept/modify an i/o for a VSAM >data set without impacting the application. > >All suggestions are welcome. When you say "I/O", do you mean the logical VSAM I/O, or the physical I/O that results? Assuming the former, what is the context? Are you in a position to run code in the same address space as the app, or does this have to be done via some completely external means? If the former, it is quite easy, and not hopelessly inelegant, to modify one or more of the I/O addresses in the ACB after the OPEN and before actual I/O. Whether you want to take on all the responsibility for handling the various errors that can occur during fairly normal processing, along with data and system integrity and such - well... I've done this with good success in a tightly controlled environment with non-VSAM, but I don't see any fundamental reason it shouldn't work for VSAM. If you need to catch the OPEN/CLOSE, there is SVC Screening. Limited in some ways, but not hard to use, assuming you are suitably privileged. Another approach would be to use something like GPSAM, and subsystem processing. This would be particularly good if you need to run the app externally, e.g. from JCL. There are probably better ideas, but you'd need to explain a bit more of what you're trying to do. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
