I *think* this is historical.
It used to be that ON ERROR didn't exist (I don't think ELSE existed
initially!). So I guess that ELSE was added to deal with failed writes but not
with file isn't there type problems, then ON ERROR was added to deal with
those.
I think originally, when even ELSE
DISCLAIMER:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please delete it and notify
the sender immediately. Please note that there is no guarantee
Hi Stuart.
Yes, modifying a dictionary is an issue.
Sarbanes-Oxley is primarily concerned with financial fraud. There are other
regulations that are more focused on other things. In the case of SOX if
you could modify report output by manipulating a dictionary there is the
potential
Hi Stuart
Another option is to use the security features in the voc, ie Field 4 of the
Voc item. You could restrict who has access to Revise and Editor and could
even log what they are doing.
Regards
David Jordan
Managing Consultant
---
u2-users mailing list
u2-users@listserver.u2ug.org
Bottom line, dictionaries should be controlled. Period.
I lock the dicts with os-level permissions.
Just live wth EVAL restrictions. SQL not used much.
For those few cases where EVAL is important:
- references a limited copy of the full dictionary where the user can
write.
- via a 2nd
Mark,
In my early days of consulting, many years ago, I had a client whose CFO
insisted that anything that I wrote that *could* be written in English
(UniQuery under its original Microdata name) be written that way, even if it
was less efficient, because then if it needed changing when I was
Well, gang . I think that the U2's should be smarter about reporting what
file can't write and WHY and also failing more gracefully than a SPLAT to
TCL.
Nevertheless, since IBM is not interested in my idea now that I'm on a PE
edition and y'all didn't jump all over the idea - I'll go revamp all
I have a feeling that this one could go on a bit. Far be it for me to
break the chain...
We have separate accounts that exist solely for the purpose of users
who have tcl access. Within those accounts, is a minimum of
potentially damage causing verbs.
But, if security is a BIG priority, the
If you do a STATUS [not to be confused with STATUS()] on a file, you can
check read-write permissions, as well as uid/gid.
type this at TCL:
HELP BASIC STATUS
which will give you both Windows and Unix help.
HTH,
Karl
quote who=Susan Joslyn
Well, gang . I think that the U2's should be
