You got a couple of answers from those with knowledge. As they were not quite positive I may chirp in with the suggestion of obfuscation. E g encrypt a part or the whole of program X and let program Y decrypt that at execution time. The decryption key and decryption routine may be arbitrarily obfuscated. (This of course assumes that program X can be changed in that way.)
Regards Thomas Berg ________________________________________________________________ Thomas Berg Specialist z/OS/IT Delivery SWEDBANK AB (Publ) > -----Ursprungligt meddelande----- > Från: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > För Charles Mills > Skickat: den 11 februari 2013 23:33 > Till: IBM-MAIN@LISTSERV.UA.EDU > Ämne: How do people lock down the compilers "inside" CA Endevor? > > 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.) > > Thanks, > > Charles > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
