FILENAME ⎕FCREATE TIENO
For example, suppose APLX is running on a Windows machine
2 30↑⎕MOUNT '' c:\temp m:\budget\current
You could create a new file called
'RUN3' ⎕FCREATE 2
(Using a left argument of
⎕FNUMS 2 ⎕TS ⎕FWRITE 2
The full operating-system path would be c:\temp\RUN3.aqf.
In this second example, the user has specified 0 as the tie number, so APLX allocates and returns the next available tie number. The file is created in library 1, so the full operating-system path would be m:\budget\current\RUN4.aqf:
'1 RUN4' ⎕FCREATE 0 3 ⎕FNUMS 2 3
In this third example, a full path name has been supplied, with an explicit tie number of 8, so we now have three files tied:
'c:\temp\RUN4.aqf' ⎕FCREATE 8 ⎕FNUMS 2 3 8 ⎕FNAMES RUN3 1 RUN4 C:\TEMP\RUN4.aqf
(Under Linux or AIX, the full path name might be something like /usr/tmp/RUN4.aqf. Under MacOS, it might be something like Macintosh HD:temp:RUN4.aqf).
Note that, if you specify a full file name, you can use any
file extension (or none). However, we
recommend that you always use .aqf for
Special considerations for Client-Server implementations of APLX
In Client-Server implementations of APLX, the front-end which implements the user-interface (the "Client") runs on one machine, and the APLX interpreter itself (the "Server") can run on a different machine. The two parts of the application communicate via a TCP/IP network. Typically, the Client will be the APLX front-end built as a 32-bit Windows application running on a desktop PC, and the Server will be a 64-bit APLX64 interpreter running on a 64-bit Linux or Windows server.
In such systems, you can specify whether the file should be accessed on the Client or the Server machine. You do this by preceding the file name with either an Up Arrow
Mixing 32-bit and 64-bit Component Files
If you are running both 32-bit and 64-bit versions of APLX, then it is possible to share component files between the two architectures, but there are some special points you should be aware of. See the introduction to the
Copyright © 1996-2010 MicroAPL Ltd