The attached tape contains the latest release of FANG. The tape consists of a single file in @COPY,G format containing all the source, relocatable, and absolute elements for FANG. All the FANG documentation is also included in the file in DOC format. The FANG file has been written to the tape three times, so that if errors are encountered reading the tape, you can try skipping the bad file with @MOVE, then reading in the next file.
To install FANG on your system, you should follow the steps described below.
First of all, read the tape containing FANG into a catalogued mass storage file. The following runstream will accomplish this:
@CAT FANG.,F2///1000
@ASG,TJ FTAPE,<tape>,<reel>
@COPY,G FTAPE.,FANG.
@FREE FTAPE.
Note that the release tape is unlabeled, so that the "J" option must be specified when it is assigned (if your site uses tape labeling).
All of the following instructions for using the FANG file will assume that the run performing each function has attached the name TPF$ to the file containing FANG. This may be accomplished by the sequence of commands:
@FREE TPF$.
@ASG,AX FANG.
@USE TPF$,FANG
To list all the FANG documentation, use the statement:
@ADD DESCRIBE
This will print the user manual, internal documentation, a brief manual explaining how to use FANG to dump tapes, and another copy of this note. Also, a copy of the configuration parameter element will be listed. To print the documents separately, use the following commands:
@DOC,Q FANG . To print user guide
@DOC,Q FANG/INTERNALDOC . To print internal doc
@DOC,Q FANG/TAPEDUMP . To print tape dump info
@DOC,Q FANG/RELEASE . To print this note
The FANG release file contains three absolute elements for FANG. The element FANGNR is a nonreentrant version of FANG configured to run on any operating system from level 31 to level 36 and on any 1100 series machine from the 1106 to the 1100/80. This version of FANG may be used for your initial testing, evaluation, and introduction to FANG. The elements FANG and FANG$ are the DBANK and common bank for the reentrant version of FANG. These elements are configured identically to FANGNR, but if placed in LIB$ and properly configured in the operating system, will function reentrantly.
As released, FANG is generated with a common bank BDI of 0400310. If this is acceptable to your site, and you have no other reason to regenerate FANG, you can install the reentrant version by configuring the FANG$ common bank in your operating system as a write-protected common IBANK with BDI of 0400310. Simply placing FANG and FANG$ in LIB$ will complete the installation of FANG at your site. If the released BDI conflicts with a BDI in use at your site, you may change it by performing the following sequence of commands:
@ASM,SU CERU$
-1,1
FANG$* EQU <new bdi>
@ADD REMAP . Recollect FANG
This runstream will remap FANG with the new BDI and will result in a new FANG and FANG$ configured with the desired new BDI. FANG$ should then be configured in the operating system with the new BDI, FANG and FANG$ should be placed in LIB$, and the installation will be complete. In order to remap FANG, you must use RLIB$ level 73R1 or later. If your site has not yet installed this level, you can read the Univac RLIB$ 73R1 release into a file and attach the @USE name MAP$PF to the library file at the start of the FANG generation runstream. The special @MAP processor supplied on the release tape will automatically LIB this file.
The absolutes shipped on the release tape are not necessarily configured optimally for every site: they are optimised to run on as many machines and system levels as possible. To configure a custom version of FANG for your site, examine the listing of the PDP element PARAMETERS produced by the @ADD DESCRIBE command. This element contains many equates which control the configuration of FANG. To reconfigure FANG, just update this element with either @PDP or the text editor, then use the command:
@ADD FULLGEN
to perform a full generation of FANG. Be prepared for the fact that this will generate about 600 pages of output. The result of the reconfiguration will be a new FANGNR, FANG, and FANG$, which can be installed as described above. The FANG generation process uses the @MASM processor. This processor must be in LIB$ in order to do a full generation of FANG. If your site has not yet implemented @MASM, you must copy a nonreentrant version of MASM from the Univac release tape into the FANG file before performing the @ADD FULLGEN.
The following notes and warnings apply to various configuration parameters in the element PARAMETERS. Those not mentioned may be changed as a site desires.
FANG is maintained using MAINTSKEL, a universal maintenance skeleton developed by Information Systems Design (ISD). If you wish to modify FANG in ways other than reconfiguring it, you must first understand how to operate MAINTSKEL. A MAINTSKEL document has been included on the release tape to aid your understanding of this utility. It may be listed by:
@DOC,QR MAINTSKEL/DOC
If any problems or questions arise during the installation or generation of FANG, or bugs emerge later, please report them to:
Marinchip Systems
(Long-obsolete address)
When sending bug reports, try to send as much documentary information as possible. In particular, if you have reconfigured the processor, please send a listing of the PARAMETERS element used to build the version of FANG which encountered the bug, and the @MAP listing from the generation.
We hope your installation and use of FANG goes smoothly, and stand by to help out if it doesn't.