Skip to content

Instantly share code, notes, and snippets.

@g000001

g000001/gist:734531c6b182eada35198a0ed385a92e

Created March 24, 2024 11:49
Show Gist options
  • Save g000001/734531c6b182eada35198a0ed385a92e to your computer and use it in GitHub Desktop.
Save g000001/734531c6b182eada35198a0ed385a92e to your computer and use it in GitHub Desktop.
Download ZIP
085_000710_09.txt
Raw
gistfile1.txt
AOS/VS DG COMMON LISP
Revision 2.30
Model Number 30947
February 1989
085-000710-09
Restricted Rights Legend
Use, duplication, or disclosure by the U.S. Government is subject
to restrictions as set forth in subparagraph (c)(1)(ii) of the
Rights in Technical Data and Computer Software clause at [FAR]
52.227-7013 (May 1987).
DATA GENERAL CORPORATION
4400 Computer Drive
Westboro, Massachusetts 01580
Unpublished -- all rights reserved under the copyright laws of the
United States.
Copyright (C) Data General Corporation, 1985-1989
All Rights Reserved
Licensed Material - Property of Data General Corporation
This software is made available solely pursuant to the terms of a
DGC license agreement which governs its use.
2
Contents
1 Introduction . . . . . . . . . . . . . . . . 3
2 Product Description . . . . . . . . . . . . . 4
3 Environment . . . . . . . . . . . . . . . . 5
3.1 Hardware and Firmware . . . . . . . . . . . 5
3.2 Software . . . . . . . . . . . . . . . . 5
4 Enhancements and Changes . . . . . . . . . . . . 7
4.1 Enhancements . . . . . . . . . . . . . . 7
4.2 Changes . . . . . . . . . . . . . . . . 8
5 Notes and Warnings . . . . . . . . . . . . . . 11
5.1 Notes . . . . . . . . . . . . . . . . . 11
5.2 Warnings . . . . . . . . . . . . . . . . 11
6 Documentation . . . . . . . . . . . . . . . 15
6.1 Manuals . . . . . . . . . . . . . . . . 15
6.2 Documentation-changes Files . . . . . . . . . 15
7 Software . . . . . . . . . . . . . . . . . 16
7.1 Media . . . . . . . . . . . . . . . . . 16
7.2 Organization . . . . . . . . . . . . . . 16
7.3 Files . . . . . . . . . . . . . . . . . 17
8 Installation Instructions . . . . . . . . . . . 19
8.1 Loading the Release . . . . . . . . . . . . 19
8.2 Error Message Files . . . . . . . . . . . . 20
8.3 PCI Installation . . . . . . . . . . . . . 21
8.4 Maintaining Multiple Versions of LISP . . . . . . 21
8.5 How to Use LISP . . . . . . . . . . . . . 22
9 Preparing a Software Trouble Report . . . . . . . . 23
9.1 Gathering STR Information . . . . . . . . . . 23
9.2 Sending Media . . . . . . . . . . . . . . 24
3
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
1 Introduction
The purpose of this release notice is to provide you with
information about revision 2.30 of DG COMMON LISP which is not
available in the DG COMMON LISP documentation. This product
consists of the following parts:
Description Part Number
---------------------------------------------------------
AOS/VS DG COMMON LISP Release Notice 085-000710-09
AOS/VS DG COMMON LISP Release Media Listed in Section
7 of this Release
Notice
This printed release notice always accompanies the software. You
can print additional copies of this notice after you have installed
the product. Its filename is LISP_DOC:085_000710_09.
DG COMMON LISP consists of both COMMON LISP and EMACS. This
release notice covers all material related to COMMON LISP. EMACS
is described in the EMACS release notice.
4
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
2 Product Description
The Data General COMMON LISP programming environment imple-
ments the de facto standard for LISP, the primary language for the
development of artificial intelligence (AI) systems. DG COMMON
LISP runs on Data General 32-bit AOS/VS and DG/UX operating
systems. It offers users a complete set of programming tools,
including an interpreter, compiler, runtime libraries, performance
tools, and facilities for accessing programs written in other
languages.
DG COMMON LISP is not the only software product Data General
offers for AI systems programming. Data General has completed a
joint development and marketing agreement with Gold Hill Computers,
a company that markets a variety of LISP/AI products for personal
computers. As a result of this agreement Data General offers the
following products:
* GoldWorks, an expert system development environment for MS-DOS
and AOS/VS
* Golden Common Lisp, a Common Lisp implementation for PCs
* Golden Connection, a package that allows communication from PCs
to MVs using PC*I (DG PC Integration product)
This set of products works in conjunction with AOS/VS DG COMMON
LISP running on MVs. Together they form a software platform for
the development and delivery of distributed AI and LISP
applications. In other words, you can partition your application
to run on both an MV and a PC, or a group of MVs and PCs. It is
very easy to split an application because communication from one
LISP program to another is done by means of simple extensions to
COMMON LISP. These extensions are available in GCLisp on the PC
and DG COMMON LISP on the MV.
5
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
3 Environment
3.1 Hardware and Firmware
DG COMMON LISP runs on all 32-bit MV-architecture Data General
machines. LISP graphics functions work only on Data General DS4
and DS7 workstations.
3.2 Software
LISP runs with AOS/VS revisions as early as 6.02, but there is
an interaction between AOS/VS 6.02 and LISP that causes LISP to
hang occasionally. AOS/VS 6.04 is the first update of the opera-
ting system to fix this problem.
If you are using the foreign code option, your object files
should be compatible with the following products:
AOS/VS C Revision 3.21 or later
AOS/VS PL/I Revision 2.10 or later
AOS/VS LANG_RT Revision 3.20 or later
AOS/VS GRAPHICS INTERFACE (GI) Revision 1.10 or later
AOS/VS EMACS revision 2.0 or later is needed in order to run
LISP in an EMACS buffer (see additions to documentation in file
LISP_DOCS:LISP_DOC_UPDATE.
AOS/VS INFOS II revision 4.10 or later is needed in order to
use the LISP functions for accessing data managed by INFOS.
DG COMMON LISP can also be used in conjunction with the set of
products coming out of the joint development and marketing agree-
ment with Gold Hill Computers, Inc. The products are the develop-
ment versions of GoldWorks, which is an expert system toolkit,
Golden Common Lisp, and Golden Connection, which is a set of
utilities for PC*I-based access to DG COMMON LISP. As a user of DG
COMMON LISP, you should be aware of the extended capabilities
provided by this new AI software development environment. The
model numbers for these products are listed below.
Model Product
---------------------------------------------------------
32098 GoldWorks Developer-286
32104 GoldWorks Developer-386
32100 Golden Connection
32102 GCLISP Developer-286
32106 GCLISP Developer-386
6
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
DG COMMON LISP 2.20 was the first revision of DG LISP to support
the products described above. DG COMMON LISP 2.30 is the first
revision of DG LISP to support GoldWorks running on AOS/VS.
Use of Golden Connection requires the following:
AOS/VS Revision 7.56 or later
XTS Revision 5.30 or later
WTS Revision 1.0 or later for the PC
MS-NET Revision 1.1 or later (optional)
7
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
4 Enhancements and Changes
4.1 Enhancements
The following list documents the major changes that have been
made to DG COMMON LISP since release 2.20.
1) GoldWorks, Gold Hill's expert system development environment,
is supported. This includes GMACS, an EMACS-like text editor
integrated with GoldWorks. (See GoldWorks documentation.)
2) The "REMOTE" package is added to facilitate communication
between LISP and other processes. See
LISP_DOC:LISP_REMOTE_PACKAGE for details. The file REMOTE.LSP
has been added to the release media to assist the user in
writing new communications protocols.
3) The "CEO" package is added, providing some of the capabilities
of the COMPREHENSIVE ELECTRONIC OFFICE (CEO) Agent User
Interface. See the file LISP_DOC:LISP_CEO_PACKAGE for details.
4) The BUILD_CUSTOM_LISP.CLI macro included in the release provi-
des a convenient means for bulding a custom LISP system. When
invoked, this macro:
1) Invokes a preexisting LISP system of your choice.
2) Loads files into the executing LISP system to tailor it.
3) Shuts down the augmented LISP system, saving a heap.
4) Runs BUILD_LISP_OBJECT to create a LISP object.
5) Runs BUILD_LISP to create the custom LISP system.
Arguments to BUILD_CUSTOM_LISP are the files to load. The
following switches are used to modify its behavior:
/REV=rev
Specifies the pathname of the LISP release directory as
"LISP.<rev>". If missing, "LISP" is implied.
/PROGRAM=program
Specifies the pathname of the preexisting LISP system to
serve as the basis for tailoring the new system. If
missing, the file "LISP.PR" in the release directory is
implied.
8
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
/BASE=
Passed through to the invocation of the preexisting LISP
system.
/HEAP=heap
Specifies that the LISP heap created by execution of the
preexisting LISP system should be saved under the name
<heap>. If missing, the LISP heap file is not saved.
/OBJECT=object
Specifies that the LISP object created by the
build_LISP_object step should be saved under the name
<object>. If missing, the LISP object file is not saved.
/EXTERNAL, /MULTIPLE, /COLLECT, /CHANGE=, /STATISTICS
Passed through to the build_LISP_object step.
/O=, /LINK_COMMAND=, /UID=, other switches for Link
Passed through to the build_LISP step.
The LISP release directory is added to the end of the sear-
chlist so that user-defined files to load are found before
predefined ones.
5) An automated invoker for the RUN-SERVER function is included.
See RUN_LISP_SERVER.CLI in the release directory. See also
"Predefined Handlers" in Appendix E of the Reference Manual.
6) NETBIOS networking code is improved to reduce allocation
significantly.
7) Minor enhancements are made in the "INFOS" package. See the
file LISP_DOC:LISP_DATABASE_EXTENSIONS for details.
8) An example of LISP access to SQL database is provided in the
LISP_EXAMPLES subdirectory. This example uses the foreign
language interface to call COBOL, which accesses the SQL
database. See the files SQL_DEMO.COB and SQL_DEMO.LSP.
4.2 Changes
The following list documents corrections and changes that have
been made to DG COMMON LISP since release 2.20.
1) Network stream operations had a bug when the :no-wait option
was specified. Unpredictable results could occur in certain
hard-to-describe situations. This problem, which was asso-
ciated with garbage collection, is fixed. An incorrect inter-
face description in the documentation has also been corrected.
9
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
See the file LISP_DOC:LISP_NETWORK_EXTENSIONS for details.
2) PARSE-INTEGER did not allow the full set of digits in a radix
greater than 10. This problem is fixed.
3) A one-line patch-file required by BUILD_LISP was omitted from
the release tape; its use was associated with network streams.
This file is no longer needed in Revision 2.30.
4) The TERMINAL-MODE function may now be used to set or clear
line-edit and echo modes.
5) The file DG_TERURCE has been added to the release tape.
If using GoldWorks, and specifically the GMACS editor (bundled
with GoldWorks), you will implicitly be using a database
describing the various capabilities of many types of terminals.
This database, named terminfo, is supplied with DG LISP on the
EMACS tape. (Do not confuse EMACS with GMACS--the latter is an
EMACS-type editor integrated with GoldWorks. GoldWorks and
GMACS are a separate product, but EMACS is bundled with DG
LISP.)
GMACS requires a more thorough terminal description than the
one currently supplied with EMACS. Thus we include the source
file for these updates, if required. (The terminfo source
file, the terminfo compiler, and the manual are all in file 1
on the EMACS release tape.)
Compiling the source file into the terminfo database will
update terminfo to have all the capabilities needed by GMACS.
Unless you have some knowledge of terminfo, it is recommended
that you compile the supplied source into terminfo. Compiling
the source can be accomplished by the following command:
xeq terminfo_compile/terminfo=<terminfo-directory>&
<source-file>
If you decide to modify the current source file and recompile
it, the following capabilities should be included: cols, lines,
clear, cup, cub1, cud1, cuf1, cuu1. The manual supplied with
EMACS explains these capabilities.
The files created by terminfo_compile must be accessible to all
users. To ensure that they have the proper ACLs, you can
simply modify the ACLs of all files in the TERMINFO directory:
dir <terminfo-directory>
acl # +,RE
LISP expects the terminfo file to exist in :UTIL:TERMINFO. If
10
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
you put this file elsewhere, you will need a link to it in
:UTIL.
11
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
5 Notes and Warnings
5.1 Notes
If you need information on LISP performance and coding hints,
refer to the additions to the reference manual in the file
LISP_DOCS:LISP_DOC_UPDATE in the release directory.
A small number of demonstration programs are included in the
LISP_DEMOS directory and are described in the file
LISP_DOC:LISP_DEMOS.
5.2 Warnings
Following is a list of the known problems and unimplemented
features in this release of LISP.
1) LISP-EMACS integration does not work well with LISP graphics.
EMACS and graphics compete for the screen.
2) Typing ^D (control-D) causes LISP to detect end of file. LISP
shuts down just as it would had you typed "(BYE)".
3) ENCODE-UNIVERSAL-TIME and DECODE-UNIVERSAL-TIME do not work
for times before January 1, 1968.
4) You should not change external or internal functions, types,
constants, etc. in the LISP package. The interpreter,
compiler, and runtime libraries make many assumptions about
symbols in the LISP package. Your redefinition may violate
one of those assumptions.
5) The compiler's handling of (OPTIMIZE (SAFETY n)) varies
somewhat from type to type. See the "Coding Hints" section in
LISP_DOCS:LISP_DOC_UPDATE.
6) Compiling a file can cause undesirable side effects in your
heap, that is, changes to your LISP environment that persist
beyond the compilation step but shouldn't. Compilation of
DEFTYPE, DEF-REP-TYPE, DEFSETF, and DEFINE-SETF-METHOD forms
causes these forms to take effect, as if they were evaluated.
Compilation of a DEFSTRUCT or DEF-FOREIGN-STRUCT form invali-
dates any preexisting structure or foreign structure,
respectively, of the same name. The side effects described
above are improper and should not be relied upon.
Note that there are other side effects from compiling that are
expected and appropriate. The compiler uses READ to read the
12
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
source text, so side effects from reading can occur, such as
creation of symbols and side effects from evaluation of #.
forms. Forms evaluated at compilation time under control of
EVAL-WHEN may also cause side effects.
7) Reading a foreign object whose rep type is
double-null-term-ascii-sequence does not work properly.
Characters are read only up to the first null character rather
than up to the first pair of consecutive null characters.
Moreover, the definition of double-null-term-ascii-sequence is
not, in fact, very useful for AOS/VS system calls. In prepar-
ation for its deletion, double-null-term-ascii-sequence is no
longer exported from the "LISP" package.
8) DEFMACRO is supposed to be defined in a null lexical
environment, but isn't. Thus
(macroexpand '(foo))
should expand to 'this rather than 'not-this after
(setq bar 'this)
(let ((bar 'not-this)) (defmacro foo () bar)).
9) You should not use the name of a special variable as the name
of a DEFSTRUCT slot.
10) :IN-OUT arguments to a foreign entry may be evaluated twice;
they should behave such as for incf.
11) The SHORT-SITE-NAME and LONG-SITE-NAME functions are implemen-
ted to return NIL. You can redefine them and make them part
of your standard LISP environment by using BUILD_LISP_OBJECT
and BUILD_LISP.
12) Continuation from the condition $UNBOUND-FUNCTION-VALUE$ is
not supported if the condition was signalled in compiled code.
13) There is a parsing problem in the LISP CLI package: the syntax
for specifying switches to CLI arguments is not accepted (see
item 7 under "Translation Rules" in Appendix B-2 of the
Reference Manual).
13
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
________________________
Graphics: Known Problems
These problems are restricted to the graphics package availa-
ble only on the DS4 and DS7 workstations:
1) To use LISP graphics functions, you must access the
GI_DEFAULT_FONT file that is shipped with this release of DG
COMMON LISP. This file is older than the file that comes with
the system, and the newer file will not work with LISP. Before
entering LISP, you should either create a link to this file
from your current working directory, or put it on your search
list before the system file. Use PATH to make sure that the
file in the LISP release directory is visible.
2) Pixel maps are not saved in heap files. You must recreate them
each time you come up in LISP.
3) DRAW-CURVE is not supported.
4) Non-scrolling display streams do not wrap printed output.
5) PRINT-PIXEL-MAP reports an error if the output file named as
its argument already exists.
6) When running with Microcode revision 7.00 or 8.03, the XOR-
PIXELS operation has the same effect as COPY-PIXELS when
drawing a line within 45 degrees of vertical.
____________________________________________
Time Profile: Known Problems and Suggestions
________
Problems. TIME-PROFILE does not work if the LISP.ST file in
the LISP release directory has been renamed.
Multiple START-STOP calls do not accumulate data. The data
reported are for the most recent START-STOP combination. Start and
stop times are in universal time format rather than internal time
format.
It is recommended that you TRANSFORM with :THRESHOLD :NONZERO
before doing a REPORT. LISP is a large system with several MB of
executable code; therefore, doing a TIME-PROFILE:REPORT over that
range will usually print many, many empty intervals. REPORT has
been changed to alleviate this problem but it is still possible to
generate an extremely long report. See documentation changes
below.
____________________
Implementation Notes. The current trailer in a REPORT is
null.
14
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
You can provide split or sort functions to TRANSFORM. Those
functions can return multiple values. In the current
implementation, only the first value is used. The information
provided by the other return values is recomputed from the return
result.
15
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
6 Documentation
6.1 Manuals
Part # Description
---------------------------------------------------------
093-701017-01 DG COMMON LISP Reference Manual
086-000099-00 DG COMMON LISP Reference Manual Addendum
085-000710-09 AOS/VS DG COMMON LISP Release Notice
The LISP.2.30 release directory holds a copy of the release notice
in the file LISP_DOC:085_000710_09.
6.2 Documentation-changes Files
Changes and additions to the DG COMMON LISP Reference Manual
are contained in several files in the release directory LISP_DOC.
The first, LISP_DOC_UPDATE, holds insertions and changes to the
manual in its current published form (093-701017-00 with Addendum
086-000099-00). Other files hold information on specialized DG
COMMON LISP extensions that support CEO integration, remote
communication, network operations, and INFOS access; each of these
files constitutes an appendix to the reference manual. Demonstra-
tion programs included with the release are documented in the file
LISP_DEMOS.
LISP_DOC_UPDATE DG COMMON LISP Reference Manual changes
LISP_CEO_PACKAGE Appendix C of Reference Manual
LISP_REMOTE_PACKAGE Appendix D of Reference Manual
LISP_NETWORK_EXTENSIONS Appendix E of Reference Manual
LISP_DATABASE_EXTENSIONS Appendix F of Reference Manual
LISP_DEMOS Describes demonstration programs.
16
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
7 Software
7.1 Media
Model # Part # Description
---------------------------------------------------------
30947 B 061-600024-05 cartridge tape (20 Mbyte)
30947 H 071-001069-07 1600 bpi magnetic tape
30947 C 071-001166-04 cartridge tape (15.2 Mbyte)
30947 J 070-600086-01 cartridge tape (130 Mbyte)
The functions supporting graphics are available only on the B, J
and C media. If you have a DS7 workstation, you need B or J media;
if you have a DS4, C media.
7.2 Organization
The organization of the files on magnetic tape and cartridge
tape is given below.
File Contents
---------------------------------------------------------
0 Basic Lisp system, including documentation files
1 Applications delivery and foreign calling support
2 Demonstration programs and examples
17
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
7.3 Files
The following files are on the release tape/cartridge on file
0:
LISP.DEFAULT_REV.CLI
LISP.2.30
LISP.2.30:LISP.PR
LISP.2.30:LISP.ST
LISP.2.30:LISP.SH
LISP.2.30:LISP_DOC:085_000710_09
LISP.2.30:LISP_DOC:LISP_DOC_UPDATE
LISP.2.30:LISP_DOC:LISP_CEO_PACKAGE
LISP.2.30:LISP_DOC:LISP_REMOTE_PACKAGE
LISP.2.30:LISP_DOC:LISP_NETWORK_EXTENSIONS
LISP.2.30:LISP_DOC:LISP_DATABASE_EXTENSIONS
LISP.2.30:LISP_DOC:LISP_DEMOS
Also on file 0 for B and J media are the files:
LISP.2.30:GI_DEFAULT_FONT:BITMAP
LISP.2.30:GI_DEFAULT_FONT:DESCRIPTOR
The following files are on the release tape/cartridge on file 1:
BUILD_CUSTOM_LISP.CLI
BUILD_LISP.CLI
BUILD_LISP_OBJECT.CLI
LISP.2.30:BLO_BASE_HEAP
LISP.2.30:LINK_LISP.CLI
LISP.2.30:LISP$ACCELERATE_ST.PR
LISP.2.30:LISP$ACCELERATE_ST.ST
LISP.2.30:LISP$FORCED_LIBRARY_FILES.CLI
LISP.2.30:LISP$LIBRARY_FILES.CLI
LISP.2.30:LISP$RETURN_ERROR.CLI
LISP.2.30:LISP_INPUT_SLAVE.PR
LISP.2.30:LISP_INPUT_SLAVE.ST
LISP.2.30:LISP_STRING_OB.PR
LISP.2.30:LISP_STRING_OB.ST
LISP.2.30:LSP$BUILD_CUSTOM_LISP.CLI
LISP.2.30:LSP$BUILD_LISP.CLI
LISP.2.30:LSP$BUILD_LISP_OBJECT.CLI
LISP.2.30:CERMES.OB
LISP.2.30:DGLIB.LB
LISP.2.30:F77INF32.LB
LISP.2.30:GEN.LB
LISP.2.30:ICALL32.OB
LISP.2.30:LANG_RT.LB
LISP.2.30:LISP.LB
LISP.2.30:LISP.MAP
18
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
LISP.2.30:LISP.OB
LISP.2.30:NETBIOS.LB
LISP.2.30:PL1MT.LB
LISP.2.30:PL1.LB
LISP.2.30:STDIO.LB
LISP.2.30:USC.LB
LISP.2.30:RUN_LISP_SERVER.CLI
LISP.2.30:DG_TERMINFO_SOURCE
LISP.2.30:LIBTERMINFO.LB
LISP.2.30:LSP$PATCHES.FED
LISP.2.30:AUI_32.LB
LISP.2.30:LISP_EXAMPLES:X_INFOS.LSP
LISP.2.30:LISP_EXAMPLES:SQL_DEMO.LSP
LISP.2.30:LISP_EXAMPLES:SQL_DEMO.COB
LISP.2.30:LISP_EXAMPLES:REMOTE.LSP
Also on file 1 for B and J media are the files:
LISP.2.30:GIERMES.OB
LISP.2.30:GI_GIS_II.FL.LB
LISP.2.30:GT_GIS_II.FL.LB
LISP.2.30:CSYSCALLS.LB
Also on file 1 for C media are the files:
LISP.2.30:LISP$GRAPHICS.LB
LISP.2.30:GI_CLRE.LB
The following files are on the release tape/cartridge on file 2:
LISP.2.30:LISP_DEMO:DEMO.CLI
LISP.2.30:LISP_DEMO:DEMO_INIT.LSP
LISP.2.30:LISP_DEMO:GRAPHICS_DEMOS.LSP
LISP.2.30:LISP_DEMO:NON_GRAPHICS_DEMOS.LSP
Also on file 2 for B, J and C media are the files:
LISP.2.30:LISP_DEMO:DEMO_INIT.FSL
LISP.2.30:LISP_DEMO:GRAPHICS_DEMOS.FSL
LISP.2.30:LISP_DEMO:NON_GRAPHICS_DEMOS.FSL
19
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
8 Installation Instructions
The full LISP release, which includes facilities to use
foreign code with LISP, requires about 33000 disk blocks. If you
know that you will not be using applications delivery or foreign
code features of DG COMMON LISP, you can reduce the disk space
requirements to about 13000 blocks.
It is standard practice to load the LISP release into the
:UTIL directory. If you choose to load the release into some other
directory, the installation requires extra steps, as noted below.
In either case, you must make the directory of choice your working
directory before loading the release. You must also become
SUPERUSER.
8.1 Loading the Release
The installation procedure varies slightly depending upon your
requirements and the machine you are using.
1) Mount the tape (with the density set to high: 1600 bpi) or
insert the cartridge.
2) Load the basic LISP system (file 0 of the release):
From magnetic tape:
LOAD/DEL/BUF=8192 @MTBn:0
From 15.2 MB cartridge:
LOAD/DEL/BUF=8192 @MTCn:0
From 20 MB or 130 MB cartridge tape
LOAD_II/BUF=16384 @MTJn:0
(If you are using the System Management Interface (SMI) option,
follow the installation procedure described in the manual
"Starting and Running AOS/VS on Eclipse MV/2000 DC and
DS/7000-Series Systems".)
3) If you want foreign code capability, load file 1 from the
release medium:
From magnetic tape:
LOAD/DEL/BUF=8192 @MTBn:1
20
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
From 15.2 MB cartridge:
LOAD/DEL/BUF=8192 @MTCn:1
From 20 MB or 130 MB cartridge tape
LOAD_II/BUF=16384 @MTJn:1
If you load foreign code support and later decide that you do
not need to run foreign code with LISP, go to the directory
into which you loaded LISP and type
DEL LISP.2.30:+.<ob lb>
4) The LISP release includes demonstration programs. If you wish
to use these programs, load file 2 as follows:
From magnetic tape:
LOAD/DEL/BUF=8192 @MTBn:2
From 15.2 MB cartridge:
LOAD/DEL/BUF=8192 @MTCn:2
From 20 MB or 130 MB cartridge tape
LOAD_II/BUF=16384 @MTJn:2
See the file LISP_DOC:LISP_DEMOS for more information.
5) If you have loaded the release into some directory other than
:UTIL, you must execute these extra steps:
* Move the files LISP.DEFAULT_REV.CLI, BUILD_CUSTOM_LISP.CLI,
BUILD_LISP.CLI, and BUILD_LISP_OBJECT.CLI into :UTIL.
* Make a link from :UTIL to the LISP.2.30 directory:
CRE/LINK LISP.2.30 <install-directory>:LISP.2.30
8.2 Error Message Files
LISP makes use of the C language and runtime library. This
means that the error message file for C (CERMES.OB) must be in-
stalled into your system error message file so that LISP can
properly convert error codes into messages. Since you may not have
a C language license on your system, a copy of CERMES.OB is in-
cluded in the LISP release directory. See "ERMES error message
21
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
file" in How to Generate and Run AOS/VS (093-000243) for more
information.
If you will be using the DG COMMON LISP functions for acces-
sing AOS/VS INFOS, you will need to build and install the error
message file INFOERMESVS.OB.
To run LISP on the DS series, you will also need the error
message file, GIERMES.OB, from Data General's Graphics Interface
(DG/GI) product. A copy of that file is included in the LISP
release directory.
8.3 PCI Installation
You will need to install PCI networking software if you will
be using DG COMMON LISP in conjunction with the Golden Connection
product. The Golden Connection allows you to communicate between
DG COMMON LISP and GoldWorks or GCLISP on a PC. The PCI installa-
tion instructions for GCLISP are described in the Golden Connection
documentation. There is no special PCI installation needed for DG
____________________________________
COMMON LISP. See DG document Installing the PC Integration Work-
________________
station Software.
8.4 Maintaining Multiple Versions of LISP
Most of the files of a release of DG COMMON LISP are packaged
in a separate directory named with the version number, as in
"LISP.2.11" or "LISP.2.20". This means that is very easy for you
to keep more than one version of LISP on your system as you make
the transition from the old version to the new.
22
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
8.5 How to Use LISP
This is fully documented in the LISP manual except for loca-
ting the file LISP.PR and the file GI_DEFAULT_FONT (for DS graphics
users only). Possible means of accessing LISP.PR are:
X LISP.2.30:LISP
or
SEARCHLIST LISP.2.30 [!SEARCHLIST]
X LISP
or
CREATE/LINK LISP.PR [!PATH LISP.2.30]:LISP.PR
X LISP
If you make this link to LISP.PR in :UTIL, then it will be visible
to all users with :UTIL on their search lists.
Graphics users on the DS7 series of workstations will also
need access to the file GI_DEFAULT_FONT that is included in the
release directory. (Note that you must use this GI_DEFAULT_FONT
rather than the newer file that comes with the system; see
"Graphics: Known Problems," above.) Possible ways of invoking LISP
are:
CREATE/LINK GI_DEFAULT_FONT LISP.2.30:GI_DEFAULT_FONT
X LISP.2.30:LISP
or
SEARCHLIST LISP.2.30 [!SEARCHLIST]
X LISP
or
CREATE/LINK GI_DEFAULT_FONT LISP.2.30:GI_DEFAULT_FONT
CREATE/LINK LISP.PR LISP.2.30:LISP.PR
X LISP
23
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
9 Preparing a Software Trouble Report
9.1 Gathering STR Information
If you find an error in the AOS/VS DG COMMON LISP software or
its documentation, or have suggestions to make about the product,
please fill out and return a Data General Software Trouble Report
(STR). (If your contract permits, you may report the information
called for in this section to your Data General representative.) To
help expedite STR processing, include only one problem or sugges-
tion on each STR form. Please follow these guidelines when filling
out your Software Trouble Report.
1) List the name of the product as "AOS/VS DG COMMON LISP" on the
STR. Calling the product "LISP" or "AI" may lead to misfiled,
lost, or delayed STRs.
2) Decide what kind of STR you are writing:
Enhancement -- Describe the proposed enhancement clearly and
tell why you want it. The better we understand what you want,
the easier it is for us to assign resources to it.
Documentation error -- Give the page and section or paragraph,
and tell why you think there is an error. (Or, use one of the
Customer Documentation Comment Forms at the end of the
manuals.)
Software problem -- Clearly and specifically state the problem
so that support personnel can reproduce it. Avoid phrases like
"the program does not work" or "fails."
3) On the STR form provide all of the following information:
o Date
o Revision of the product
o Revision of the microcode
o Revision of the operating system
o Names and revisions of other software this product uses
o The CPU type
o Terminal and printer types, if relevant
o The command line, complete instruction, or program name
that caused the problem
o How often the problem recurs
o The action(s) necessary to reproduce the problem
4) You can shorten the time it takes to solve the problem by
isolating the problem to the best of your ability. If you can
24
RELEASE NOTICE: 085-000710-09
AOS/VS DG COMMON LISP Revision 2.30 February 1989
-------------------------------------------------------------------
come up with an input script that reliably reproduces the
problem, it will be very easy to fix the problem.
5) If the problem occurred soon after installing a new revision of
DG EMACS, the operating system, microcode, or new hardware,
note this.
6) If you received an error message, please write down the text
(and number, if there was one) of the message. Also, indicate
when you received the message (during compiling, linking,
executing, etc.)
7) For problems with devices such as terminals, printers, or
graphics display devices send the device characteristics and
the hardware settings.
9.2 Sending Media
If we cannot reproduce a problem because you did not send
necessary software (program module, breakfile, macro, or other
crucial file), it will delay answering the STR. Sometimes, we have
to close the STR with the answer "not reproducible" or
"insufficient information." To avoid this, please follow these
guidelines:
1) Include the smallest possible application that demonstrates the
problem. This can be a shortened version of the original
application. Make sure you send any necessary source or object
files needed to reproduce the problem. If you send example
applications, make sure they are runnable programs, not listing
files.
2) Include a text file on the media describing the application
sent, calling hierarchy (if one exists), and what you've done
to track down the problem. You can send hard copy, but a text
file is preferable.
3) Clearly label the media, giving format, contents, density,
buffersize, and date. Verify that the media is readable.
4) Include other product-specific steps necessary to produce
usable media.
*** End of Release Notice ***
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment