🚀 go-pugleaf

In article <1990Jul13.125215.3190@cid.aes.doe.CA> afsipmh@cid.aes.doe.CA (Patrick Hertel) writes:
>
> We are in the process of going from NOS and NOS/VE to UNIX. Is there a UNIX
>version of UPDATE available comercially or otherwise. I know Cray has it
>in UNICOS. We have CDC 910s and 920's

I think you should look into a product called "historian", which provides 
UPDATE compatibility.  ETA Systems used it as a replacement for UPDATE
(before the plug was pulled) and I've also seen it running on VMS VAXs.

The vendor is:
		Opcode, Inc.
		7748 Hwy 290 W., Suite 800
		Austin, TX. 78736

I don't know if they have it running under Unix, and I neither recommend nor
discourage its use.  I have no connection to Opcode.

Jim

In article <1990Jul16.163518.29951@athena.mit.edu> purdon@athena.mit.edu (James R Purdon) writes:
>I think you should look into a product called "historian", which provides 
>UPDATE compatibility.  ETA Systems used it as a replacement for UPDATE
>(before the plug was pulled) and I've also seen it running on VMS VAXs.

ETA was evaluating Historian, but had not begun production use of it, at the
time the company closed.  EOS development used Apollo's DSEE for source code
control and system builds.  One development team had reached the point of
using DSEE and Historian in parallel as part of the evaluation, but it had
not received wide exposure.

I believe that the Native Unix group used traditional SCCS-family tools.

--
Jonathan C. Rice           rice@hall.cray.com

In article <1990Jul16.163518.29951@athena.mit.edu>,
purdon@athena.mit.edu (James R Purdon) writes:

> In article <1990Jul13.125215.3190@cid.aes.doe.CA>
afsipmh@cid.aes.doe.CA (Patrick Hertel) writes:
> >
> > We are in the process of going from NOS and NOS/VE to UNIX. Is there a UNIX
> >version of UPDATE available comercially or otherwise. I know Cray has it
> >in UNICOS. We have CDC 910s and 920's
> 
> I think you should look into a product called "historian", which provides 
> UPDATE compatibility.  ETA Systems used it as a replacement for UPDATE
> (before the plug was pulled) and I've also seen it running on VMS VAXs.

Watch out for this. Historian is a variant on Scope update, later on the
205. This is
NOT ANYWHERE NEAR the same as update on NOS & NOS/BE, or SCU on NOS/VE.

We were playing with using historian at ETA for source release of the OS
and compiler on
EOS, but not, never, no way on UNIX.

Tom

_____
Tom Davidson			internet: halley!foghorn!tjd@cs.utexas.edu 
Tandem Computers, Inc.		fax: (512) 244-8247 voice: (512) 244-8375
14231 Tandem Boulevard
Austin, TX 78728-6610

In article <7384@atlantis.cray.com>, rice@atlantis.cray.com (Jonathan Rice) writes:
> 
> I believe that the Native Unix group used traditional SCCS-family tools.
> 

This is correct.  We used SCCS & RCS (at times) on the Suns, where we held
source code.

As for using an UPDATE-alike on Unix, why bother?  Pull your code out of the
UPDATE PL's, retain the "old" card-style info (col. 73 and beyond), run it
into admin.  Presto.

Rob
-- 
Rob Peglar	Comtrol Corp.	2675 Patton Rd., St. Paul MN 55113
		A Control Systems Company	(800) 926-6876

...uunet!csinc!rpeglar