> -----Original Message-----
> Behalf Of Baker, Mike L. (IT Production Support)
> 
> We are working toward implementing security/3000, ...
> want to activate it, ...  We all ready have a system level udc 

The documentation should be pretty helpful for this -- it is, after all, just about what EVERYONE has had to do in order to get it working ;)

There are a couple of things that can be helpful here:

   1) in order to "do" what VEsoft's supplied UDC does, you simply need to run the program and check the result -- this is relatively easy to add to most existing UDC's

   2) Security/3000 also has the ability to perform arbitrary scripts and UDC's upon a successful logon -- you could have Security/3000 effectively "chain" to your original command(s)

   3) you could also implement the "backg"/AIF mode, which essentially runs the program REGARDLESS of whether or not there is a UDC for it [and don't worry -- the program is smart enough to know it was run this way and won't repeatedly ask you for passwords if you run it a second time in an actual UDC]

IN ALL CASES: make sure you have an "out" during your testing -- leave one terminal logged on with an SM user ID.  [uhhh... that would be "Manager.Sys"]  If you hose something up during your testing, you can easily lock yourself out of the box [this is especially true with method 3 above]  With an already-logged-on user, you can simply "undo" whatever last setting you made to recover [including an all-inclusive SETCATALOG;SYSTEM to remove the offending UDC]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *