This repository provides tools for creating software that will execute on a Cray X-MP supercomputer running the COS operating system. In particular, these tools can be used to create programs that will run on Andras Tantos' Cray supercomputer simulator, cray-sim, under the COS 1.17 operating system provided in Andras' repository.
- Tools
- Â Â cal
- Â Â dasm
- Â Â kftc
- Â Â ldr
- Â Â lib
- Running on Cray X-MP
- Going Native with the Tools
- Â Â CAL
- Â Â DASM
- Â Â KFTC
- Â Â LDR
- Â Â LIB
- Â Â LISPF4
- Installing Tools from NOS 2.8.7
Tools provided by this repo currently include:
- cal. A cross-assembler supporting Cray Assembly Language v2.
- dasm. A disassembler able to disassemble executables produced by ldr.
- kftc. A FORTRAN 77 cross-compiler. See also the fortran README file.
- ldr. A linking loader producing executables from relocatables produced by the cal cross-assembler and libraries managed by lib.
- lib. A library manager supporting collections of relocatables produced by the cal cross-assembler.
- lisp. LISPF4 interpreter implementing a dialect of InterLisp, circa early 1980's. See also the lisp README file.
Use make or gmake without any arguments to build the tools for execution on MacOS or Linux, as in:
make
To install the tools, use the install target, as in:
sudo make install
By default, the tools are installed in the directory /usr/local/bin. Edit the Makefile if
you want to install them elsewhere.
kftc (the FORTRAN 77 compiler) will not build successfully until this fork of Amsterdam Compiler Kit (ACK) has been built and installed. A mutual dependency exists, however, between ACK and this (the COS-Tools) repository. Specifically, cal, ldr, and lib must be built and installed before ACK can be built and installed successfully. Consequently, you should build and install this repository first, then build and install ACK. After ACK has been built and installed successfully, return to this repository and build and install it again; kftc should then build and install successfully too.
In addition, LISPF4 is implemented in FORTRAN. It has a dependency upon kftc. kftc must be built and installed before LISPF4 will build successfully. LISPF4 is an interpreter of the InterLisp dialect of the LISP programming language and can be built only as a tool that runs natively on COS 1.17.
cal is a cross-assembler for the Cray Assembly Language. It accepts source programs complying with the Cray Assemble Language as defined in Cray Assembler Version 2 Reference Manual. It produces relocatable object files compatible with the structure defined by the COS operating system and accepted by the ldr tool.
The synopsis of the cal command is:
cal [-f][-l lfile][-n ident][-o ofile][-T dlist][-t tfile]...[-w][-x] sfile ...
-f - enable flexible syntax
-l lfile - listing file
-n ident - identity of the source module
-o ofile - object file
-s - disable section stacking
-T dlist - text file directory list
-t tfile - external text file
-w - exit with error status on warning indications
-x - enable implicit external symbols
sfile - source file(s)
The -f, -n, -s, and -x parameters are intended mainly for use by the cross-compilers
provided by the Cray X-MP fork of the ACK (Amsterdam
Compiler Kit).
A typical usage of the cal command looks like:
cal hello.cal
This would cross-assemble a source file named hello.cal and produce an object file named
hello.obj and a listing file named hello.lst. You can use the -o and -l arguments to
override these default names based upon the source file name. Additionally, if you specify
-l 0, no listing file will be produced.
dasm is a disassembler. It accepts an absolute executable produced by ldr and produces a disassembly listing revealing the Cray X-MP machine instructions contained in the executable. The synopsis of the dasm command is:
dasm path [start] [limit]
path - COS executable file
start - parcel address at which to start disassembly (default: 0200a)
limit - parcel address at which to end disassembly (default: end of executable
kftc is a FORTRAN 77 cross-compiler for the COS operating system and Cray X-MP computer system. It accepts FORTRAN 77 source files and produces Cray Assembly Language source files suitable for input to cal. The synopsis of the kftc command is:
kftc [-a static|stack|auto][-l lfile][-o ofile][-s] sfile
-a - variable storage allocation strategy
static (default) : variables are allocated in static storage
stack or auto : variables are allocated on the runtime stack
-l lfile - listing file
-o ofile - output file (CAL source file)
-s - echo FORTRAN source lines to output file
sfile - FORTRAN source file
A typical usage of the kftc command looks like:
kftc -o hello.cal hello.f
This would cross-compile a FORTRAN source file named hello.f and produce an output file
named hello.cal. You can use the -l argument to produce a listing file and the -s
argument to echo FORTRAN source lines to the output file.
The cal cross-assembler can then be applied to the output file to produce a Cray X-MP object
file, as in:
cal -x -o hello.o hello.cal
Note that the kftc runtime and intrinsic function libraries depend upon this fork of Amsterdam Compiler Kit (ACK) which supports the Cray X-MP supercomputer and the COS operating system platform. It provides a C cross-compiler that produces runtime libraries for the Cray X-MP and COS. See Going Native with the Tools for additional details.
If you clone this fork of ACK and build and install it, runtime and intrinsic function libraries needed by kftc will become available, and you can then use kftc, cal, and ldr to cross-compile and link FORTRAN 77 programs that can be uploaded to a Cray X-MP and run on the COS operating system.
A convenient shell script for cross-compiling FORTRAN programs is also provided_ Its name is cft77. It accepts the name of a FORTRAN source file as a parameter, and the source file is assumed to have extension ".f". It produces an assembly language source file, a Cray X-MP object file, a load map, and a Cray X-MP absolute executable as output. For example, to cross-compile a FORTRAN source file named hello.f, the script would be called as follows:
cft77 hello
and the following files would be produced as output:
- hello.cal : assembly language source file
- hello.o : Cray X-MP object file
- hello.lst : listing file
- hello.map : laod map
- hello.abs : Cray X-MP absolute executable
ldr is a linking loader for the COS operating system and Cray X-MP computer system. It accepts object files produced by the cal cross-assembler and libraries produced by the lib library manager, and it produces absolute binary executables suitable for execution on COS. The synopsis of the ldr command is:
ldr [-m mfile][-o ofile] sfile...
-m mfile - load map file
-o ofile - executable output file
sfile - source file(s)
A typical usage of the ldr command looks like:
ldr -m hello.map -o hello.abs hello.obj syslib.lib
This would link a relocatable object module named hello.obj with a library named syslib.lib and produce an absolute executable named hello.abs. It would also produce a file named hello.map containing a load map providing details about the linking operation.
lib is an object library manager for collections of relocatable object modules produced by cal. The synopsis of the lib command is:
lib [-l lfile][-o ofile][-r name...] sfile...
-l lfile - listing file
-o ofile - output library file
-r name - name(s) of modules to omit from output library file
sfile - source object and library file(s)
A typical usage of the lib command looks like:
lib -l - -o math.lib exp.obj log2.obj sqrt.obj
If the -o option is not specified, no output library file is produced. Thus, to list the
contents of a library, execute the lib command as in:
lib -l - math.lib
Andras Tantos' Cray supercomputer simulator, cray-sim, supports the Cray X-MP with the COS 1.17 operating system. He has published a delightful narrative of the project in The Cray Files, and this narrative includes documentation about installing and running COS 1.17 on the simulator.
Unfortunately, the copy of COS 1.17 recovered by Andras does not include any programming language translators, and no other working copies of COS are currently known to exist. The tools provided by this repository help to resolve the lack of programming tools in the recovered copy of COS by providing a cross-assembler and linking loader that will produce COS executables. This repository enables hobbyists to create assembly language programs for the iconic Cray X-MP supercomputer and run them on the simulator.
A significant challenge, however, is how to move cross-assembled executables onto a simulated Cray X-MP. One solution is to install DtCyber and leverage its ability to run Cray Station software. DtCyber is a simulator for Control Data Corporation's (CDC) Cyber series of supercomputers. Installing the NOS 2.8.7 operating system on DtCyber enables using Cray's Cray Station software to exchange files and batch jobs between the CDC and Cray supercomputers.
In addition to Cray Station, the NOS 2.8.7 operating system has a mature set of other data communication software including TCP/IP applications (e.g., FTP), Kermit, and XModem. For example, it is possible to use an FTP client to upload a cross-assembled Cray binary to a CDC machine running NOS 2.8.7 and then use Cray Station to transfer the file to a Cray X-MP running COS. Likewise, Kermit or XModem can be used to upload files to a CDC machine running NOS 2.8.7.
Given this, the following log of a user session illustrates how a user could create an assembly language program, use cal to cross-assemble it, use ldr to produce an absolute executable, upload the absolute executable to NOS 2.8.7 using FTP, create a NOS CCL procedure to transfer it to and run it on a Cray X-MP, and view the results returned.
First, display the source code, a simple assembly language program that displays a trivial log message:
% cat hello.cal
TITLE 'Hello'
SUBTITLE 'Simple *Hello World* program'
IDENT HELLO
COMMENT 'HELLO - A simple *Hello World* program'
ENTRY HELLO
START HELLO
HELLO S0 O'004 ; F$MSG
S1 ='Hello world!'Z
S2 O'17 ; CLASS=1, OR=1, FC=3
EX
S0 O'000 ; F$ADV
EX
END
Cross-assemble it:
% cal hello.cal
The cross-assembler produces a relocatable object file named hello.obj and a listing file named hello.lst:
-rw-r--r--@ 1 kej staff 427 Mar 9 12:23 hello.cal
-rw-r--r--@ 1 kej staff 2361 Mar 21 21:12 hello.lst
-rw-r--r--@ 1 kej staff 456 Mar 21 21:12 hello.obj
Use ldr to produce an absolute executable from the relocatable object file:
% ldr hello.obj
% ls -l hello.*
-rw-r--r--@ 1 kej staff 416 Mar 21 21:15 hello.abs
-rw-r--r--@ 1 kej staff 427 Mar 9 12:23 hello.cal
-rw-r--r--@ 1 kej staff 2361 Mar 21 21:12 hello.lst
-rw-r--r--@ 1 kej staff 456 Mar 21 21:12 hello.obj
Use FTP to upload it to the NOS 2.8.7 system (kevins-max.local) as an indirect access permanent file named HELLO, in binary mode:
% ftp kevins-max.local
Trying [fe80::1889:9f48:a180:d9ce%en0]:21 ...
ftp: Can't connect to `fe80::1889:9f48:a180:d9ce%en0:21': Connection refused
Trying 192.168.1.238:21 ...
Connected to kevins-max.local.
220 SERVICE READY FOR NEW USER.
Name (kevins-max.local:kej): guest
331 USER NAME OKAY, NEED PASSWORD.
Password:
230 USER LOGGED IN, PROCEED.
Remote system type is NOS.
ftp> bin
200 COMMAND OKAY.
ftp> put hello.abs hello/ia
local: hello.abs remote: hello/ia
227 ENTERING PASSIVE MODE (192,168,1,238,30,11)
150 FILE STATUS OKAY; ABOUT TO OPEN DATA CONNECTION.
100% |*****************************************************************************************************************************************| 416 842.84 KiB/s 00:00 ETA
226 CLOSING DATA CONNECTION.
416 bytes sent in 00:00 (1.95 KiB/s)
ftp> quit
221 SERVICE CLOSING CONTROL CONNECTION. LOGGED OUT.
Use Telnet to log into the NOS 2.8.7 system:
% telnet kevins-max.local
Trying 192.168.1.238...
Connected to kevins-max.local.
Escape character is '^]'.
Connecting to host - please wait ...
Connected
WELCOME TO THE NOS SOFTWARE SYSTEM.
COPYRIGHT CONTROL DATA SYSTEMS INC. 1994.
24/03/21. 21.20.34. TE04P06
NCCMAX - CYBER 875. NOS 2.8.7 871/871.
FAMILY:
USER NAME: guest
PASSWORD:
JSN: ABXC, NAMIAF
/
Create and save a CCL procedure file containing a procedure named RUN. This procedure will use the Cray Station interface to submit a batch job to the Cray X-MP supercomputer. When the job starts running on the Cray X-MP, it uses the Cray Station interface to retrieve a file containing a COS executable from the NOS 2.8.7 system. After retrieving the file, it runs it. When the job completes, the Cray Station interface will return the log and any output produced by the executable to the NOS system, and this will appear as a file in the user's wait queue.
This procedure file needs only to be created and saved once and can be re-used again and again later, either to re-run the original executable, or to run other ones.
/new,cray
/text
ENTER TEXT MODE.
.PROC,RUN*I,F=(*F,*N=CRAYBIN).
.IF,FILE(F,AS),LOCAL.
REWIND,F.
.ELSE,LOCAL.
GET,F.
.ENDIF,LOCAL.
COPYBF,F,ZZZCBIN.
REPLACE,ZZZCBIN=F.
CSUBMIT,CRAYJOB,TO.
REVERT,NOLIST.
.DATA,CRAYJOB.
JOB,JN=CRAYRUN,T=60.
ACCOUNT,AC=CRAY,APW=XYZZY,UPW=QUASAR.
ECHO,ON=ALL.
OPTION,STAT=ON.
FETCH,DN=F,MF=FE,DF=TR,^
TEXT='USER,GUEST,GUEST.GET,F.CTASK.'.
F.
EXIT TEXT MODE.
/save,cray
Note that Control-T is pressed to exit TEXT mode.
The CATLIST command displays all of the user's permanent files. This confirms that the cross-assembled executable, HELLO, uploaded previously and the procedure file, CRAY, just created have been saved as indirect access files as expected.
/catlist
CATALOG OF GUEST FM/CYBER 24/03/21. 21.23.07.
INDIRECT ACCESS FILES
CRAY FTPPRLG HELLO LOGIN MAILBOX
DIRECT ACCESS FILES
GAMFILE LIBRARY RELFILE
5 INDIRECT ACCESS FILES ON DISK. TOTAL PRUS = 10.
3 DIRECT ACCESS FILES ON DISK. TOTAL PRUS = 72.
Use the BEGIN command to execute the procedure named RUN in the procedure file named CRAY and pass the name of the file containing the cross-assembled executable as a parameter:
/begin,run,cray,hello
Use the STATUS command to monitor progress. First, the batch job destined for the Cray X-MP may appear in the NOS system's INPUT queue.
/status,jsn
JSN SC CS DS LID STATUS JSN SC CS DS LID STATUS
ACAE.B. .BC.XMP.INPUT QUEUE ABZR.T.ON.BC. .EXECUTING
Then, it may seem to disappear. While actually running on the Cray X-MP, it may not be visible to the NOS system.
/status,jsn
JSN SC CS DS LID STATUS JSN SC CS DS LID STATUS
ABZR.T.ON.BC. .EXECUTING
However, the Cray Station interface will submit a batch job to the NOS system to participate in transferring the cross-assembled executable from NOS to COS, so you might catch the brief execution of that job.
/status,jsn
JSN SC CS DS LID STATUS JSN SC CS DS LID STATUS
ABZR.T.ON.BC. .EXECUTING ACAF.B.NI.BC. .EXECUTING
When the batch job on the Cray X-MP side has completed, its log and output will be returned to the NOS 2.8.7 WAIT queue.
/status,jsn
JSN SC CS DS LID STATUS JSN SC CS DS LID STATUS
ABZR.T.ON.BC. .EXECUTING ACAH.S. .BC.MAX.WAIT QUEUE
Use the QGET command to retrieve the output by JSN from the WAIT queue, and then display it using the LIST command:
/qget,acah
QGET COMPLETE.
/list,f=acah
1
20:02:29.8633 0.0007 CSP CRAY XMP-14 SN 302 LEADING EDGE TECHNOLOGIES 03/21/84
20:02:29.8662 0.0008 CSP
20:02:29.8697 0.0010 CSP CRAY OPERATING SYSTEM COS 1.17 ASSEMBLY DATE 02/28/89
20:02:29.8726 0.0011 CSP
20:02:29.8753 0.0012 CSP
20:02:29.9016 0.0014 CSP JOB,JN=CRAYRUN,T=60.
20:02:30.0044 0.0105 CSP ACCOUNT,AC=,APW=,UPW=.
20:02:30.0101 0.0109 CSP
20:02:30.0126 0.0110 CSP .......................................................................
20:02:30.0153 0.0111 CSP
20:02:30.0493 0.0122 CSP ECHO,ON=ALL.
20:02:30.0592 0.0129 CSP OPTION,STAT=ON.
20:02:30.0735 0.0162 CSP FETCH,DN=HELLO,MF=FE,DF=TR,^
20:02:30.0796 0.0186 CSP TEXT=.
20:02:33.1901 0.0189 SCP ACAF 21.27.42.USER,GUEST,.
20:02:33.1920 0.0189 SCP ACAF 21.27.43.CHARGE, * ,
20:02:33.1939 0.0189 SCP ACAF 21.27.44. TRO - PF AND TAPE TRANSPARENT OUTPUT.
20:02:33.1960 0.0189 SCP ACAF 21.27.44.TRO: DATASET HELLO , 70B WORDS, 0.185
20:02:33.5543 0.0189 SCP SS004 - DATASET RECEIVED FROM FRONT END
20:02:35.2084 0.0206 CSP HELLO.
20:02:35.2217 0.0209 USER HELLO WORLD!
20:02:35.2438 0.0213 CSP END OF JOB
20:02:35.2485 0.0216 EXP SY005 - HELLO 512 WRDS, 1 IOS, 1 REQ, 1 STRS, .017 SEC
20:02:35.2507 0.0216 EXP - 29-1-22A 18 STRS READ: 1 REQ, 1 STRS, .019 SEC
20:02:35.2595 0.0217 CSP
20:02:35.2617 0.0218 CSP
20:02:35.2660 0.0221 CSP CHARGES
20:02:35.2686 0.0221 CSP CS032 - DATASET NOT LOCAL:
20:02:35.2714 0.0222 ABORT AB025 - USER PROGRAM REQUESTED ABORT
20:02:35.2735 0.0222 ABORT - P=00001417B TASK-ID=0001
20:02:35.2755 0.0222 ABORT - BASE=00775000 LIMIT=01153000 CPU-NUMBER=00
20:02:35.2774 0.0222 ABORT - JOB STEP ABORTED.
The same tools and technique can be used to upload and run FORTRAN programs that have been cross-compiled using the cft77 script.
This fork of Amsterdam Compiler Kit (ACK) supports the Cray X-MP supercomputer and the COS operating system platform. It provides cross-compilers that produce executables for the Cray X-MP and COS. Currently, this fork of the ACK can cross-compile programs written in the following languages:
- BASIC
- C
- Pascal
If you clone this repository and build and install it, you can use it to cross-compile the COS Tools (i.e., cal, dasm, kftc, ldr, and lib). This will produce an assembler, disassembler, FORTRAN 77 compiler, linking loader, and library manager that will run natively on the Cray X-MP and COS.
To build the tools to run natively:
-
Clone the fork of the ACK repository, build, and install it:
git clone https://github.com/kej715/ack.git cd ack ./cray-build.sh sudo ./cray-build.sh install -
Execute the following commands from the COS Tools repository:
make clean make cos
make cos will produce the following native executables for the Cray X-MP and COS:
- cal.abs : the Cray Assembly Language assembler
- dasm.abs : the disassembler
- kftc.abs : the FORTRAN 77 compiler
- ldr.abs : the linking loader
- lib.abs : the library manager
- lispf4.abs : the LISP interpreter
make cos also generates a collection of native executables reproducing utility commands
missing from the originally recovered copy of COS 1.17. These can be found in the
cos-commands subdirectory, and they include:
- charges.abs : run automatically by COS at the end of each job to report resource consumption information.
- copyd.abs : copies blocked datasets
- copyf.abs : copies files of blocked datasets
- copyr.abs : copies records of blocked datasets
- note.abs : writes text to a dataset
- skipd.abs : skips blocked datasets
- skipf.abs : skips files of blocked datasets
- skipr.abs : skips records of blocked datasets
See COS Version 1 Reference Manual for details about these commands and COS Commands for notes about the reproduced implementations of them.
All of these executables can be uploaded to a Control Data computer running NOS 2.8.7 (e.g., using FTP in binary mode as described earlier), and then the Cray Station interface can be used to copy them to the Cray X-MP and install them as commands there. The following NOS CCL procedure will accomplish this:
.PROC,INSTALL*I"INSTALL AN EXECUTABLE AS A COMMAND",
F"EXECUTABLE FILE NAME"=(*F).
.IF,FILE(F,AS),LOCAL.
REWIND,F.
.ELSE,LOCAL.
GET,F.
.ENDIF,LOCAL.
COPYBF,F,ZZZCBIN.
REPLACE,ZZZCBIN=F.
CSUBMIT,CRAYJOB,TO.
REVERT,NOLIST.
.DATA,CRAYJOB.
JOB,JN=INSTALL.
ACCOUNT,AC=CRAY,APW=XYZZY,UPW=QUASAR.
ECHO,ON=ALL.
OPTION,STAT=ON.
FETCH,DN=F,MF=FE,DF=TR,^
TEXT='USER,GUEST,GUEST.GET,F.CTASK.'.
SAVE,DN=F,EXO=ON.
RELEASE,DN=F.
ACCESS,DN=F,ENTER.
Assuming that this procedure is added as a record to the file named CRAY, created above, it can be executed as follows to copy an executable (e.g., CAL) to the Cray X-MP and install it as a command:
BEGIN,INSTALL,CRAY,CAL.
A batch job submitted to the Cray X-MP could then call the command as in:
CAL,I=SOURCE.
Note that when the tools are built for native execution, the syntax of the command line arguments they accept is different than the syntax they accept when they are built as cross-tools. The syntax they accept when running natively conforms to requirements of the COS operating system, and it also aligns (although not 100%) with documentation about the original native tools. Details are provided, below:
The synopsis of the CAL command when built for running natively is:
CAL[,B=ofile][,F][,I=sfile][,L=lfile][,N=ident][,T=tfile]...[,W][,X].
B=ofile - object file
F - enable flexible syntax
I=sfile - source file
L=lfile - listing file
N=ident - default module identifier
S - disable section stacking
T=tfile - external text file
W - exit with error status on warning indications
X - enable implicit external symbols
A typical usage of the CAL command looks like:
CAL,I=HELLO.
This would assemble a local source file named HELLO and produce an object file named
$BLD. By default, an assembler listing will be written to $OUT. You can use the B= and
L= arguments to override these defaults. Additionally, if you specify L=0, no listing file
will be produced, and if you specify B=0, no object file will be produced.
The synopsis of the DASM command when built for running natively is:
DASM,file[,start][,limit].
file - COS executable file
start - parcel address at which to start disassembly (default: 0200a)
limit - parcel address at which to end disassembly (default: end of executable
The synopsis of the KFTC command when built for running natively is:
KFTC [ALLOC=STATIC|STACK|AUTO][I=sfile][L=lfile][O=ofile][S]
ALLOC=key - variable storage allocation strategy
STATIC : variables are allocated in static storage
STACK or AUTO : variables are allocated on the runtime stack
I=sfile - FORTRAN source code file (default $IN)
L=lfile - listing file (default $OUT)
O=ofile - output file (default ZZZZCAL)
S - echo source code lines to output file
A typical usage of the KFTC command looks like:
KFTC,I=HELLO.
Remember that KFTC produces an assembly language source file. CAL can be applied to this assembly language source file to produce a Cray X-MP object file, and LDR can be applied to the object file to produce a Cray X-MP absolute executable. However, assembly language source files produced by KFTC tend to reference runtime and intrinsic library functions, and the libraries containing implementations of those functions must be specified to LDR also, in order for it to be able to resolve the references.
All of the libraries needed are either provided by ACK or by the fortran subdirectory of this repository. The following table identfies them. The column definitions are:
- COS Library : name of the library dataset on COS
- Local Library : name of the library file on your build machine
- Source : source of the library, either ACK or a fortran subdirectory
Note that when ACK is built and installed using default configuration parameters, the
local library files can be found in the directory /usr/local/share/ack/cos.
COS Library Local Library Source Description
----------- ------------- ----------------- ----------------------------------
RTLIB librt.lib fortran/runtime FORTRAN runtime library
IOLIB libio.lib fortran/runtime FORTRAN I/O library
INTFLIB libintf.lib fortran/intrinsic. FORTRAN intrinsic function library
EMLIB libem.a ACK ACK machine support library
SYSLIB libsys.a ACK ACK OS support library
CLIB libc.a ACK ACK C language library
Each of these files can be uploaded to a NOS 2.8.7 system using FTP in binary mode, and then they can be copied to COS and saved as permanent files there using the following NOS CCL procedure:
.PROC,SAVE*I"SAVE A PERMANENT FILE",
F"NAME OF FILE"=(*F).
.IF,FILE(F,AS),LOCAL.
REWIND,F.
.ELSE,LOCAL.
GET,F.
.ENDIF,LOCAL.
COPYBF,F,ZZZCBIN.
REPLACE,ZZZCBIN=F.
CSUBMIT,CRAYJOB,TO.
REVERT,NOLIST.
.DATA,CRAYJOB.
JOB,JN=INSTALL.
ACCOUNT,AC=CRAY,APW=XYZZY,UPW=QUASAR.
ECHO,ON=ALL.
OPTION,STAT=ON.
FETCH,DN=F,MF=FE,DF=TR,^
TEXT='USER,GUEST,GUEST.GET,F.CTASK.'.
SAVE,DN=F.
After uploading each of the library files listed in the table, above, to NOS 2.8.7 and assigning the names in the COS Library column to them, they can be saved on COS using the following commands. This assumes that the CCL procedure, above, is added as a record to the file named CRAY:
BEGIN,SAVE,CRAY,RTLIB.
BEGIN,SAVE,CRAY,IOLIB.
BEGIN,SAVE,CRAY,INTFLIB.
BEGIN,SAVE,CRAY,EMLIB.
BEGIN,SAVE,CRAY,SYSLIB.
BEGIN,SAVE,CRAY,CLIB.
With the CAL, COPYF, KFTC and LDR executables installed as commands, and the six libraries saved as permanent files on COS, the following NOS CCL procedure can be used to submit a job via Cray Station to COS to compile, link, and execute a FORTRAN 77 program:
.PROC,FTN*I"COMPILE AND RUN FORTRAN PROGRAM",
I"FORTRAN SOURCE FILE NAME"=(*F,*N=SOURCE),
T"CPU TIME LIMIT"=(*S/D,*N=180),
D"OPTIONAL DATA INPUT FILE"=(*F,*N=).
.IF,FILE(I,AS),LOCAL.
REWIND,I.
.ELSE,LOCAL.
GET,I.
.ENDIF,LOCAL.
SKIPEI,CRAYJOB.
COPY,I,CRAYJOB.
.IF,$D$.NE.$$,DATA.
REWIND,D.
COPY,D,CRAYJOB.
.ENDIF,DATA.
CSUBMIT,CRAYJOB,TO.
REVERT,NOLIST.
.DATA,CRAYJOB.
JOB,JN=FTN,#T=T.
ACCOUNT,AC=CRAY,APW=XYZZY,UPW=QUASAR.
ECHO,ON=ALL.
OPTION,STAT=ON.
COPYF,O=I.
REWIND,DN=I.
ACCESS,DN=CLIB.
ACCESS,DN=EMLIB.
ACCESS,DN=IOLIB.
ACCESS,DN=INTFLIB.
ACCESS,DN=RTLIB.
ACCESS,DN=SYSLIB.
MEMORY,FL,USER.
KFTC,#I=I,O=ZZZZCAL.
REWIND,DN=ZZZZCAL.
CAL,X,#I=ZZZZCAL,L=0.
LDR,M=MAP,AB,DN=$BLD,LIB=IOLIB:INTFLIB:RTLIB:EMLIB:SYSLIB:CLIB.
$ABD.
For example, suppose the procedure, above, has been added to the procedure file named CRAY. Suppose further that the NOS 2.8.7 user has created a FORTRAN program named FIBO, FIBO reads data from the COS standard input file, $IN, and the user has entered some data for the program in a NOS file named DATA. The user could use the procedure, above, to submit the program and its input data to COS by executing the following command:
BEGIN,FTN,CRAY,I=FIBO,D=DATA.
The job's output will be returned to the NOS 2.8.7 user's wait queue. It will include a listing of the FORTRAN program and the output produced by executing it.
The synopsis of the LDR command when built for running natively is:
LDR[,AB[=ofile]][,DN=rfile[:rfile...]][,LIB=lfile[:lfile...]][,M=mfile].
AB=ofile - output object file
DN=rfile - relocatable object file
LIB=lfile - library file
M=mfile - load map file
A typical usage of the LDR command looks like:
LDR,AB,DN=HELLO,LIB=SYSLIB,M=$OUT.
This would link a relocatable object module named HELLO with a library named SYSLIB and produce an absolute executable named $ABD (default name of absolute executable). It would also write a loadmap to $OUT.
The synopsis of the LIB command when built for running natively is:
LIB[,L=lfile][,O=ofile][,R=name[:name...]],sfile...
L=lfile - listing file
O=ofile - output library file
R=name - name(s) of modules to omit from output library file
sfile - source object and library file(s)
A typical usage of the LIB command looks like:
LIB,L=$OUT,O=MATHLIB,EXP,LOG2,SQRT.
If the O= option is not specified, no output library file is produced. Thus, to list the
contents of a library, execute the LIB command as in:
LIB,L=$OUT,MATHLIB.
The synopsis of the LISPF4 command is simply:
LISPF4.
However, before executing the LISPF4 command, its file of system atom definitions, LISPSYS, must be made available as a local dataset because it reads this file at startup time to initialize itself internally. After initializing itsself, it begins reading expressions from $IN, and it writes output to $OUT.
Previous sections defined NOS CCL procedures enabling files to be transferred from NOS 2.8.7
to COS 1.17 and saved there. The NOS 2.8.7 system described earlier and provided
here supports an optionally
installed product named cos-tools. When the product named cos-tools is installed on
NOS 2.8.7, it installs all of the native tools described above (e.g., CAL, KFTC, LDR,
LIB, LISPF4, etc.) on COS 1.17. It also installs a CCL procedure library named CRAY in
the catalog of user INSTALL, and that library includes all of the CCL procedures described
above, plus others.
See COS Tools in the
NOS 2.8.7 repository for more
details.