I am working with IBM's Fault Analyzer product. We compile our COBOL prorgrams with the TEST(SEPARATE) option to produce a SYSDEBUG file. For those of you familar with this option, you know that the name of this file is recorded in the compile unit. Unfortunatly, our process for moving programs into produciton involves copying the SYSDEBUG file and load modules to new locations, and not a recompile. Thus the compile unit does not contain the new location of the SYSDEBUG file.
There are several ways to overcome this. We aslo have Debug Tool, and there is a Debug Tool exit that can provide an alternative location. This is fairly easy to code, but Fault Analyzer still looks first at the location specified in the compile unit. The way the RACF rules are written here, production jobs do not have access to test libraries. While Fault Analyzer continues to function (It bypasses those files the job cannot access), the attempt genereates RACF errors which upsets the security folks. A second way to overcome out problem is to use an IGZIUXB exit. This will, according to the documentation, allow one to replace the SYSDEBUG file name with a new one. If I am reading this correctly, if this exit changes the name of this file, it does not use the one stored in the compile unit. One of the big differences between the two exits is that in the Degug Tool exit, the name of the library from which the abending program is executing is provided via the paramater list. The IGZUIXB provides the compile unit name, but not the library from which it was loaded. This information is important because our naming standards allow us to determine the location of the SYSDEBUG file if we know the load library name. Does anyone know of a good way to locate the library name when we are in this exit? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
