Very true. Thanks for pointing this problem out. Another possible solution, which I did with different IBM module, is to write a small HLASM program. This program would verify how it was called by looking at the RB chain, to be sure it was not the first RB on the TCB is what I'm thinking. Now, you statically link this routine into the compiler initial program object. But, at the same time, you do a Binder CHANGE command to change the CSECT name of the actual compiler to something unique. And you give the HLASM routine the standard CSECT name. The HLASM does a static CALL to the new name of the actual compiler module after doing its validation, passing the original parameters to the compiler. You also put in the proper SMP/E commands so that SMP/E knows about this USERMOD to the compiler. To do compiler maintenance would require backing out the USERMOD, applying the compiler maintenance, then reapply the USERMOD.
-- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
