On Mon, 11 Feb 2013 14:32:36 -0800, Charles Mills <charl...@mcn.org> wrote:
>This is a theoretical question. I am *not* an Endevor user. I am trying to >solve a *similar* problem and this is the best way to explain it. > >Here's the question: at shops that use Endevor for all compiles, how do you >"lock down" the compilers so that programmers can only run the compilers >under Endevor, not with plain old JCL? What about programmers who might have >"private copies" of the compiler load libraries? > >(More generically, if X is a load module, is it possible to set things up >such that program Y can run X, but PGM=X will never work? How? I have >thought about engineering a rename to a name that JCL will not accept (but >LINK will) but I would just as soon not get that weird; rather do things in >a more supported way.) I'm curious why you would want to do that. Wouldn't it be better to protect the relevent load libraries such that your users cannot compile into them except under Endevor's control? Perhaps you should explain your actual problem, not have us try to guess at an answer by analogy. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
