Contact us Heritage collections Image license terms
HOME ACL Associates Technology Literature Applications Society Software revisited
Further reading □ Overview □ 1962: An outline of Fortran □ 1962: Operating experience with Fortran □ 1962: Implementation of Fortran on Atlas □ 1962: Proposed target language (BAS) □ 1962: BAS binary card □ 1963: Intermediate Atlas symbolic programming language (INTERASP) □ 1963: Addendum □ 1963: A primer for Fortran programming □ 1964: Atlas Fortran manual: Part I □ 1964: Part II □ 1964: Using HARTRAN □ 1965: System note 4 □ 1966: Fortran on Atlas □ Atlas 2 at AWRE □ 1965: BAS subroutines □ 1965: System notes □ 1966: S3 Fortran □ Titan □ 1966: System note 1 □ 1966: System note 2 □ 1966: Fortran on Titan □ 1966: Compile Master on Titan □ 1966: System Note 3 □ 1966: Differences between S3 dialect and Fortran II □ 1966: Magnetic tape library subroutines □ 1967: T3 Fortran reference manual
ACD C&A INF CCD CISD Archives Contact us Heritage archives Image license terms

Search

   
⟶ ACL ⟶ Applications ⟶ Hartran :: Hartran and Fortran on Atlas
⟶ ACL ⟶ Applications ⟶ Hartran :: Hartran and Fortran on Atlas
ACL ACD C&A INF CCD CISD Archives
Further reading ⇓

□ Overview □ 1962: An outline of Fortran □ 1962: Operating experience with Fortran □ 1962: Implementation of Fortran on Atlas □ 1962: Proposed target language (BAS) □ 1962: BAS binary card □ 1963: Intermediate Atlas symbolic programming language (INTERASP) □ 1963: Addendum □ 1963: A primer for Fortran programming □ 1964: Atlas Fortran manual: Part I □ 1964: Part II □ 1964: Using HARTRAN □ 1965: System note 4 □ 1966: Fortran on Atlas
Atlas 2 at AWRE
□ 1965: BAS subroutines □ 1965: System notes □ 1966: S3 Fortran
Titan
□ 1966: System note 1 □ 1966: System note 2 □ 1966: Fortran on Titan □ 1966: Compile Master on Titan □ 1966: System Note 3 □ 1966: Differences between S3 dialect and Fortran II □ 1966: Magnetic tape library subroutines □ 1967: T3 Fortran reference manual

Fortran on Titan

B C Chapman

7 July 1966

1. Introduction

The Hartran System as it now exists includes facilities for switching input streams, and for the use of magnetic tape for private libraries, chain (multi-chapter) jobs, re-running jobs previously loaded, and also during the execution of a job.

It is proposed to augment the input stream switching facility to include the reading of a file in internal code, with a return to the originally selected input. The use of backing store will be extended to include use of disc by means of a special directive to correlate a backing store device number with a file name.

Although the initial version of the disc filing system will only include files in internal code, it is expected that full use of backing store extracodes with the disc will be available before the disc filing system is released to users. Accordingly there will be no special facilities to deal with private libraries by input-output extracodes. It is expected that job description facilities will include means of referring to existing files for input and backing store, but the creation of files for output and backing store must be by extracode.

2. Files for Groups of Subroutines

2.1 Input from Files during Compilation

*FORFILE
<title>
This directive will be recognised by the compile master. The named file will contain one or more subroutines in Fortran or Asp. Inclusion of a binary routine is possible but results in inefficiencies. The detailed effect will be:-
1. Record current setting of trap on fault 11 (input exhausted)
2. Record currently selected input,
3. Set input 66 as specified file.
4. Set trap 11.
5. Select input 66.
The end of a file will be indicated by either
the directive *ENDFILE or the exhaustion of the
file. The action will be:-
1.	Lose input 66.
2.	Reset trap 11 to original value.
3.	Reselect original input.

2.2 Input from Files during Loading

*BASFILE
< title>
This directive will be recognised by the loader. The named file will contain one or more subroutines in binary (BAS). The treatment of this directive will be the same as that of *FORFILE.

2.3 Preparation of Files

*WRFILE
<title>
This directive is recognised by the loader. Normal loading is suspended, and subsequent directives and routines (except *INPUT and *ENDCOMP which have their usual effect) are copied to the specified file, using output extracodes, up to and including the directive *ENDFILE. The length of the file must not exceed n pages.
It is intended that the *WRFILE directive be used for the preparation of BASFILES. A FORFILE will usually be the product of some editing program, although it could be written try *WRFILE in a LOADBAS job.

3. Backing Store Files

3.1 Correlation between Device Number and File Name

*TAPFILE
<title>
The file with the specified title will be used as backing store device M (<100). It will consist of at most n blocks. If no title is given, then this directive will define a disc as temporary working space.

3.2 Use of Backing Store by Hartran

(a) *LIBRARY i,j
Read private library from b.s. beginning at block j. If j is omitted, block 1 is assumed.
(b) *WRLIB i,j
Write private library to b.s. beginning at block j for k blocks. If k is omitted, 4096 is assumed (subject also to actual length of tape or file). If j is also omitted, block 1 is assumed.
(c) *CHAIN i,j
Write loaded program (perhaps in chapters) to b.s. i beginning at block j. If j is omitted, 1 is assumed.
(d) *RESTORE i,j,k
Read previously loaded program from b.s. i beginning at block j for k blocks, where j,k are as specified during the loading process.
(e)
Use during execution by statements CALL CHAIN, READ TAPE etc. In the case of READ TAPE, etc. the logical number of the backing store must not exceed 16.

Notes

1. File titles must always be enclosed within parentheses.

2. If an estimate of the length of a file is not provided, it will be taken as 10 blocks (pages).

3. Nested use of files will not be allowed.

4. The standard rules for specifying the parts of a file title and status must be obeyed.

⇑ Top of page
© Chilton Computing and UKRI Science and Technology Facilities Council webmaster@chilton-computing.org.uk
Our thanks to UKRI Science and Technology Facilities Council for hosting this site