If AcuServer or AcuConnect is running on remote machines, the compiler can read remote source files from and write resulting files to those systems. The remote filename syntax that is used with the compiler is different from that used with the runtime and AcuServer. Because the compiler uses the at sign (@) as a placeholder for the base name of the source file, you cannot use that symbol as a tag in front of the name of the remote system (for example, -o @server:/objects/@.acu is ambiguous). Instead, the syntax is more like standard URL syntax. The remote filename specification must be of the form:
acurfap stands for Acucorp Remote File Access Protocol.
Remote file name notation can be used with any compiler option that takes a file name as an argument. The //server:port notation can be used with any configuration variable that allows remote name notation.
If AcuServer is listening on the default port of a server machine, you do not have to specify the port number because the compiler defaults to the number (6523). However, if you omit the port number, you must include two colons (::) before the file name. If AcuServer is listening on a port other than the default, the :: notation will not work.
ccbl -o acurfap://myserver::/myapp/obj/@.acu apmain.cblIf apmain.cbl is located on the server, you can compile the remote file and write the resulting object file to the server with the following command.
ccbl -o acurfap://myserver::/myapp/obj/@.acu acurfap://myserver::/myapp/src/apmain.cblIf AcuConnect is running on a Windows machine named myserver and is listening on port 5632, you can compile apmain.cbl straight to that machine with the following command. Notice that if specifying a Windows directory, you must also include a drive letter followed by a colon (the c: in this example) after the port number (or the optional ::).
ccbl -o acurfap://myserver:5632:c:/myapp/obj/@.acu apmain.cbl