I just noticed the OP posted his original message nearly 4 years ago, so
I don't know if he's still listening, but thought I'd reply anyway for
the benefit of anyone else who might have interest. I put a wrappers
around ED and DELETE many, many years ago, and it hasn't been a problem.
My solution to the custom version getting wiped out is to keep all of
our customized VOC entries in a file named VOC.MOD. The only time our
VOCs get updated is during a hardware upgrade, and I copy the contents
of VOC.MOD back into VOC as part of the process.
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeff
Sent: Tuesday, April 03, 2012 3:04 PM
Subject: Re: [U2] Universe: IF statements in parargraphs don't work
Louie Bergsagel <louiebergsagel <at> gmail.com> writes:
> No, that works fine. You only need a label if you want to skip some
> Turns out somebody had deleted the VOC equal sign record "=".
> Which brings up a good security question, how do you prevent someone
> from deleting things? Put shell around ED and DELETE?
> It would be a bummer to have to make VOC read-only.
> On Thu, Jun 5, 2008 at 12:53 PM, Ron Hutchings <ron_hutchings <at>
> > On Line 6 don't you need to go to a label to execute a command
> > instead of trying to directly execute it?
> u2-users mailing list
> u2-users <at> listserver.u2ug.org
> To unsubscribe please visit http://listserver.u2ug.org/
Check into the Security Subroutines section of the Administrators Guide.
1) Make a temporary copy of ED in your VOC, call it ED.BAK. This is
your backdoor in case of problems. I would also have a separate account
with a pointer to the main account's VOC. This account you can lock
with a simple paragraph that says if @LOGNAME isn't you, LOGOUT.
2) Write a security subroutine that conforms to the specs given in
Chapter 8 of the Administrators guide. Catalog it in the global catalog.
2) Copy the verbs you want to secure, including ED, into your VOCLIB.
3) Change the verbs in the VOC to Remote pointers to your VOCLIB, and
add the name of your security routine to line 4. (I might suggest
testing the R pointers before applying the security routine.)
4) Once you're sure your security is working as planned, and that you
can use the ED program you've secured, then remove your back door
ED.BAK. Remember, you can still fix the VOC from your other account if
you manage to lock yourself out.
U2-Users mailing list
U2-Users mailing list