Sorry if I offended anyone. That was not my intent. "NEED TO" was not meant to dictate what vendors must do. Only that additional considerations exist that have an impact in a product environment. I just wanted Scott to consider the following now instead of after RTM. These possible problems could be easily eliminated by placing the data first in modules. It would certainly take less time than trying to verify are not issues for your product.
1. Common abend recovery may be affected. Maybe the module eyecacther (not to be confused with load module name) and offset into that module are displayed. Maybe it expects a standard base register that starts at the beginning of the program. 2. How do customers and customer support deal with abends. Do they somehow use module base register? Do they have procedures that will be affected? Does it affect how they search the problem database? 3. How are IPCS diagnostic exec's affected? 4. Diagnostic documentation, FAQ's, problem database and other online material might have something that is affected. Are there any drawbacks to placing data first in a module? I only see possible drawbacks when it is not first. Regards, Jon Perryman. > >From: Martin Trübner <[email protected]> >Enough been said about the reason and the cause (and solutions) > >But who dictates techniques for vendors? > >While your points are okay- the "trick" to have the definitions right at the >beginning of the module (with just a J in front) is something that makes >sense >for everyone. If you ever tried to calculate offset in a DOB-program (data >only >base) from the start of the LTORG (or wherever the base points to) knows what >I >mean. > >Credit for the technique goes to Ed J. >
