If AcuServer or AcuLaunch is running on a remote machine, the compiler can create the resulting object file directly on the remote system. The remote filename syntax is different than it is for accessing remote files from the runtime via AcuServer. Because the compiler uses the "at" sign ("@") as a placeholder for the basename of the source file, you cannot use that symbol as a tag in front of the name of the remote system (using something like "-o @server:/objects/@.acu" is ambiguous). Instead, the syntax is more like standard URL syntax. The output file name must be of the form:
acurfap://server:[port]:filename(where acurfap stands for "Acu Remote File Access Protocol"). The "//server:port" notation can be used with any configuration variable that allows remote name notation. See Appendix H, "Configuration File Entries" in Book 4 for details on configuration variables.
Examples:
If you have AcuServer running on a UNIX machine named myserver listening on the default port, you can compile "apmain.cbl" straight to that machine with the following command.ccbl -o acurfap://myserver::/myapp/obj/@.acu apmain.cblIf you have AcuLaunch running on a Windows machine named myserver listening on the "5632" port, 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 "::").
ccb32 -o acurfap://myserver:5632:c:/myapp/obj/@.acu apmain.cbl