itsns@dcatla.UUCP (Steve N. Sheppard) (02/04/88)
Our cluster site (2 x 8650, 2 x 750, 1 x 8550, all VMS-4.6) has an
increasingly annoying problem:
Various obscure DCL scripts accessible to operators, tech-support folk
and managers are left mangled by ongoing software installations, maintenance
work or updates. Problems are discovered later by a mystified night crew
(e.g. privilege violations; bizarre error messages during node reboots);
they are not amused; they sometimes call the department manager at 4AM to
resolve sticky situations; he is not amused.
Some possible solutions have occurred to us:
1. change the department manager's telephone number (;-)
2. tighten control on changes to DCL scripts; enforce reviews of all
changes; test as far as possible before real use;
[ugly, intrusive, and hard to enforce]
3. auto-magically examine DCL scripts before accepting updates; [aha !]
Number Three sounds like what we're after.
Have any of you dealt with automated syntax-checking of DCL scripts ?
I suppose you could check 'em AS they are written (syntax-directed editing,
perhaps via TPU or GNU-EMACS ?), or check 'em AFTER they are written (via a
DCL-LINT or somesuch); any opinions or suggestions ? Also, I've heard rumours
of a 'DCL compiler'; has anyone heard of such a beast ?
Thanks in advance for any help.
If you reply directly to me, I'll summarize to the net...
steven sheppard
digital communications associates
1000 alderman drive
alpharetta, georgia 30201
(404)-442-4861
itsns@dcatla