My personal opinion is that trying to "lock down" a program, any program, so that it can only be executed "in a specific manner" is a waste of time and effort. The most that I ever do is make it too much of a bother for anyone to want to. If using the COBOL compiler outside of CA-Endevor is set up to be "bothersome" and CA-Endevor is set up so that it is easy to use, then a sane programmer will just use CA-Endevor. And if you want to see who is insane, then run an SMF report to see if anybody is executing IGYCNTRL as a main program. Keep a note to yourself. And tend to deprioritize their use of your time. If they want to use the raw COBOL compile procedures, then let them. Let their manager notice that they aren't as productive as the others on the same team. The yearly review will likely convince the reprobate to reform.
Of course, if CA-Endevor is set up in your shop to be a pain in the butt to use, then castigate the person who set up the CA-Endevor processors. We (sysprogs) are supposed to try to make the programmers' work easier. Of course, sometimes that is not possible. Due to factors beyond our control. *cough* managers *cough*. -- 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
