I can agree that the system is "safe" - since, perhaps, the tool cannot get any more access than the user installing it. However, at our shop at least, the problem would be change management - but maybe not in the way you think:
We wouldn't have any notice of the tool being installed, but then we never get notice of (usually bad) end-user-developed applications that are put on the system, so that would change. Where the risk would be, however, would be that this tool depended upon some other software on the host (say, for example, that this tool was 'COBOL-BY-EXAMPLE' and gave them a GUI for developing COBOL but was dependent upon OS/VS COBOL)., and we decided to drop that software - we would have no idea of this other tool and its dependency, so we'd break their application. This happened to us once on a hardware upgrade, too - we had no idea that a user office was dependent upon vector processors, and when we upgraded we didn't order any! All our engineering-types had been working on Unix workstations for 5 years when this happened. We "assumed" that we were done with those kinds of apps on the mainframe, since they'd been telling us how it couldn't compete, etc.... then suddenly we find that we've killed a structural design program. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
