HP3000-L Archives

June 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Greg Chaplin <[log in to unmask]>
Reply To:
Greg Chaplin <[log in to unmask]>
Date:
Thu, 5 Jun 1997 12:17:41 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Hi all.

I've been racking my brains trying to figure out a way of putting
certain groups in our development account off-limits.  I'm trying to
set up source control procedures, such that the original files are
kept in the "secure" groups.  Scripts will be used to control taking
files out of the groups to edit & saving changed or new files into the
groups.  I would like to be able to prevent any programmer from easily
bypassing the system (this would be mainly due to laziness or
forgetfulness).   Specifically, I would like the "secure" groups to
have read access only, so that searches for strings and similar
operations are possible, and the scripts would be able to then
retrieve from or save to those groups.

All our programmers have AM capability, we have the Vesoft trilogy
(MPEX, Security & Veaudit) and are on MPE/iX 5.5.

Anyone got any hints or ideas?  I don't think we need to buy a
full-blown source control package.

TIA.

Greg Chaplin                  (Any opinions in here are mine)
UniSuper                      (nobody else would want them)
Level 28, 367 Collins St,      Email: [log in to unmask]
Melbourne 3000,                Phone: +61 3 9648 4145
Australia.                     Fax:   +61 3 9648 4141

ATOM RSS1 RSS2