Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/rfc519.pdf
Дата изменения: Sat Oct 25 03:09:34 2008
Дата индексирования: Mon Oct 1 20:28:51 2012
Кодировка:
. IEC: 16818

1 6 81. B'

_J

RFCC: 519

COMPUTER SYSTE MS LABORATORY--UCSB John R. Pickens June 1973

RESOURCE ABSTRACT

EVALUATIO~

In the spirit of RFCJ .3 6 9 , Evaluation of ARPANET resources, a new test group was organized at UCSB to take a detailed look at specific network resources and develop initial · s i t e dependent and function dependent MINIMAN's (Concise User Manuals). As the

group was again composed of novices, initial effort revolved about basic procedural indoctrination. January and March 1973 a number of In the period . between

resources were investigated

with varying degrees of success, as to availabi1itr, proper usage, sample problem solutions, and access to help an~ documentation. Included in this paper are a summary of the projects undertaken,

initial suggestions at MINIMAN composition, and suggestions for future test groups. As these groups are attempting to perform a

useful function for the ARPANET community, comments and suggestions are requested. Copies of the reports described herein are

available on request from the Computer Systems Laboratory at UCSB.

RESOURCES INVESTIGATED BY THE GROUP I. APL APL was investigated primarily at MULTICS. UCSD was also APL at Most

scheduled for evaluation but not carried out.

MULTICS was used to solve a few trivial problems.

eftort revolved about the difficult task of obtaining


any available documentation.

The octal codes for APL

characters were obtained and mapped into the OLS .keyboard. A side goal of the project, the comparison of APL with OLS, was begun but progressed very little.

II.

BASIC Basic was investigated at a number of TENEX sites. Differences between sites were pointed out and necessary file manipulation commands were documented. An

integration problem was written at one site, sent via FTP to another site, and then run again to show comparative execution times and compatability. Non-PDP/IO

sites were investigated but no report was submitted.

III.

TSO IBM's Time Sharing Option was exercised at UCLA-CCN. Interesting results were obtained regarding cost and - execution time. Available commands were documented and a

PL/l program was written and executed.

IV · . MIT-MATHLAB
This"the most successful of the projects, involved
documentation of
~lp,

file manipulation, and MACSYMA


access and an original research project in resource
sharing. A recursive problem in pattern recognition


-2


and a triple integration Here.solved to, demonstrate

,

MACSYNA generated expressions into user programs on the OLS. More information on this project is forthcoming.

,
V. LOCAL USER GUIDE A first pass network users manual was completed for UCSB users. In it are described console access and

settings, character mappings, current servers, users and TIPs, and error conditions. Following minor revisions

this guide will be distributed to local users.

VI.

LOCAL IMLAC ACCESS TO NETWORK .Access to network graphics programs was attempted with a local INLAC. Due to the non-uniformity of network IMLACs However, a program to . loaded from NIC and In addition a

very little success was obtained. access
SRI-ARC~s

NLS

~as .compiled .and

attempts were made to iron out the bugs.

project was begun to maintain an IMLAC library and compiler locally for network usage. projects, basic operating
proc~dures

As in the other were documented.

VII.

HARVARD GRAPHICS Several attempts were made to learn graphics access to organic molecule but no response could be generated. eventually abandoned.
ofavatlabilit~

of

synthesis

program~

This project was

-3


MINIMAN COMPOSITION

· I

As mentioned in a previous report, concise manuals arc needed for network resources so that uniniated familia!ity with foreign systems.
us~rs

may gain basic

In addition, manuals which such as Fortran

describe specif{c network wide functions,

compilors, are needed if resourc-c sharing is to become a real trait of the ARPANET. For . the resources evaluated, each ' g r o u p

member submitted two reports analagous to the two types of MINIMANS 'needed in the network. The readings and ,format of the

reports will be included here to stimulate future discussion on MINIMAN composition.

REPORT #1: . I. II. III. IV. V. VI.

Online Help for fa specific host computer]

Setti~gs


Connection, Login, and Optimal TELNET Help Files Job Status Time of Day Time;r..10ney Used/Left

Interpersonal Communications A. B. C. D. Console Linking Location of Users Mail Facilities Access to Operator and/or Consultants


· VI I . VIII.

Warnings or Unfriendly User Behavior
Useful References and Documentation

-4


REPORT #2: I. II. III.· IV. V. VI.

How to Use La specific resour~eJ

Table of Contents ,Access and Usage (or How to Start and ' S t o p )
Editing Commands and File Structures
Documentation, Location and Cost Sample Solutions of Appendices
A · . Special Characters and Terminal Settings
B. Similarities and Differences from Site to Site Significant Problems

FUTURE TEST GROUPS A number of projects are envisioned for
evalua~ors
fu~ure

resource

and include:

1.

Complete evaluation of APL at MULTICS and UCSD wita comparison to the On-Line System (OLS).

2. 3.

Investigate BASIC in

depth,~etwork

wide.

Evaluate other symbolic manipulation programs such as REDUCE.


4.· Summarize all games available in the network.
5. Find and evaluate specific application 'programs such as ZOG or the weather data base at CCA. The projects undertaken will be determined in part by local interests. But a serious effort is being rode for reports to

accompany each evaluation.

-5


---

CONCLUSION

I

Good results have been obtained from the two test groups thus far. Although composed of novices, as far as network familiarity

is concerned, the groups have been able to produce data and


.

:. r e p o r t s which benefit the network community.

The reports run the

gambit from ~oor to excellent, but ~ven the poorer ones have generated results by motivatini more knowledgeable system personnel to find t Lm e to wri te the report in the "right" way. All . data and reports compiled by these groups are available to interested network users. In addition. any information or

documentation or manuals which might fit into the framework of the MINIMAN is requested from the network community. information begins to be collected, become a resource sharing network. As this

the network may truly start to

I

-6