RFC 519

Resource Evaluation 🎀

Okay bestie, here are the RFC facts first 💅

• RFC 519, NIC 16818, June 1973
• Network Working Group
• Author: J. Pickens, Computer Systems Laboratory -- UCSB
• No category, status, obsoletes, or updates are listed in this header 🙈

Abstract ✨

This is giving sequel energy 💖. Following up on RFC # 369 (Evaluation of ARPANET resources), a new test group at UCSB went full detective on specific network resources and tried to write first-draft site dependent and function dependent MINIMANs (Concise User Manuals) 📖. The group was still total novices, so the early work was mostly basic procedural indoctrination 😭. From January to March 1973 they looked into a bunch of resources, with mixed results on availability, proper usage, sample problem solutions, and access to help and documentation. This paper covers the projects, first MINIMAN ideas, and suggestions for future test groups 🧚. Since they're trying to be useful for the whole ARPANET community, they're asking for comments and suggestions 🫶. Copies of the reports are available on request from the Computer Systems Laboratory at UCSB 🌸.

Resources Investigated by the Group

I. APL 💜

APL was investigated mainly at MULTICS. UCSD was also on the schedule but never got done 💀. APL at MULTICS solved a few trivial problems. Most of the effort went into the hard task of finding any documentation at all 😩. They got the octal codes for APL characters and mapped them onto the OLS keyboard ⌨️. A side goal, comparing APL with OLS, started but barely moved forward.

II. Basic 🍓

BASIC was investigated at a number of TENEX sites. Differences between sites were pointed out, and the 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/10 sites were investigated, but no report was submitted.

III. TSO 🌈

IBM's Time Sharing option was exercised at UCLA-CCN. Interesting results came out of it regarding cost and execution time 💸. Available commands were documented, and a PL/1 program was written and executed.

IV. MIT-MATHLAB 👑

This was the most successful project, no cap 🔥. It involved documentation of help, file manipulation, and MACSYMA access, plus an original research project in resource sharing. A recursive problem in pattern recognition and a triple integration were solved to demonstrate MACSYMA generated expressions being turned 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. It describes console access and settings, character mappings, current servers, users and TIPs, and error conditions. After 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 IMLAC. Because the network IMLACs weren't uniform, very little success was had 😭. Still, a program to access SRI-ARC's NLS was compiled and loaded from NIC, and attempts were made to iron out the bugs. A project also began to maintain an IMLAC library and compiler locally for network usage. As with the other projects, basic operating procedures were documented.

VII. Harvard Graphics 🥀

Several attempts were made to learn about graphics access to organic molecule synthesis programs, but no response could be generated 🙃. The project was eventually abandoned.

MINIMAN Composition 🧩

As mentioned in a previous report, concise manuals are needed for network resources so that uninitiated users can get basic familiarity with foreign systems. Manuals that describe specific network wide functions, like Fortran compilers, are needed too if resource sharing is going to be a real trait of the ARPANET 🌸. Each group member submitted two reports, analogous to the two types of MINIMANs needed in the network. The headings and format are included here to stimulate future discussion on MINIMAN composition 💬.

REPORT # 1: Online Help for [a specific host computer] 💻

   I.  Connection, Login, and Optimal TELNET Settings

  II.  Help Files

 III.  Job Status

  IV.  Time of Day

   V.  Time/Money  Used/Left

  VI.  Interpersonal Communications

A. Console Linking

B. Location of Users

C. Mail Facilities

D. Access to Operator and/or Consultants

 VII.  Warnings or Unfriendly User Behavior

VIII.  Useful References and Documentation

REPORT #2: How to Use [a specific resource] 📘

   I.  Table of Contents

  II.  Access and Usage (or How to Start and Stop)

 III.  Editing Commands and File Structures

  IV.  Documentation, Location, and Cost

   V.  Sample Solutions and Significant Problems

  VI.  Appendices

A. Special Characters and Terminal Settings

B. Similarities and Differences from Site to Site

Future Test Groups 🔮

A bunch of projects are envisioned for future resource evaluators, including:

1. Complete evaluation of APL at MULTICS and UCSD with comparison to the On-Line System (OLS) 💅.
2. Investigate BASIC in depth, network wide.
3. 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 partly decided by local interests. But a serious effort is being made for reports to accompany each evaluation 📝.

Conclusion 👑

Good results have come from the two test groups so far 🎉. Even though they were novices when it came to network familiarity, the groups produced data and reports that benefit the network community. The reports range from poor to excellent, but even the poorer ones generated results by motivating more knowledgeable system personnel to find time to write the report in the "right" way 🙈. All data and reports compiled by these groups are available to interested network users. The group is also asking the network community for any information, documentation, or manuals that might fit into the MINIMAN framework 🫶. As this information starts getting collected, the network may truly start to become a resource sharing network ✨🌈.

---

[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Nasser M. Akhtar 2/98 ]