And if they have gone to that tiny bit of trouble (probably a legal Intellectual Property issue), you can still question their doing so.
Ask them to be sure that whenever their code calls an external routine that they have not written, to turn the bit back on. Saving and restoring the environment is their responsibility. In the meantime, you can always try using the CMS "immediate" command: TS If that does not work, try TE then TS (there's an arcane reason for that order that is not worth going into, meaning: I don't remember the details). Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Phil Smith III" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <[email protected]> 03/21/2007 04:38 AM Please respond to "The IBM z/VM Operating System" <[email protected]> To [email protected] cc Subject Re: EXECTRAC not inherited "Ian S. Worthington" <[EMAIL PROTECTED]> wrote: >I have some execs that call a vendor module that, in turn, invokes other >execs as user exits. >If I set EXECTRAC ON my initial execs are correctly traced. But the other >execs invoked out of the vendor module are not. >I'm not sure how this later invocation works but I'm guessing that the module >has to setup some sort of environment specification before starting the user >exits, and that that environment does not inherit my setting of EXECTRAC. >Is there anyway I can make it do so? Or, failing that, is there any easy >change I can request the vendor to make inherit this setting? Or would it a >major job for them? To the best of my knowledge, EXECTRAC requires only setting a single bit in NUCON. So if it's "going away" partway through an execution chain, it's because the vendor is deliberately turning it off. So (following my belief chain to its logical conclusion) it would be trivial for them to fix, but unlikely to be something they'd want to do, since they've gone to a tiny bit of trouble to get where you are now... ...phsiii The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
