There are several ways that an application running on a server can launch an application on the client.
The three most common are :

1. CALL CLIENT "SYSTEM", "C$RUN" or "C$SYSTEM" (to open an application)
2. Use "C$EASYOPEN" or "C$DESKTOP" (to open a file with the associated application)
3. CALL CLIENT "MYPROG" (to run a COBOL program)

1. CALL CLIENT "SYSTEM", "C$RUN" or "C$SYSTEM"
Use the SYSTEM, C$RUN and C$SYSTEM library routines to run an operating system command line as if it was executed from a command prompt, shell, script, batch file, or shortcut.**
SYSTEM runs the command synchronously so that the program waits for the command to complete before continuing.
C$RUN runs the command asynchronously so that the program continues to run in parallel with the command.
C$SYSTEM combines the functionality of SYSTEM and C$RUN and allows a command to be run synchronously or asynchronously depending on a "flags" parameter.
Add the CLIENT clause to the CALL statement in order to run the command on the client-side. The isCOBOL framework ignores the CLIENT clause when not running in thin client mode.
So CALL CLIENT is safe to use in programs that run in both thin client and local modes.
For example, to launch the Windows calculator program:

   call client "C$RUN" using "calc"

   call client "C$RUN" using "excel.exe"

2. C$EASYOPEN or C$DESKTOP
To open a file on the client with the default associated application, you can use C$EASYOPEN and include the name of the file to be opened.
If you want to specify the location of the file on the client, or you're using a version prior to 2015R2, you can copy the pdf file to the client with C$COPY, then call C$EASYOPEN using the CALL CLIENT syntax:

   call "c$copy" using "/myapp/reports/custlist.pdf"
                       "@[DISPLAY]:c:	mp
eportscustlist.pdf"
                giving retCode.
   if retCode = 0
      call client "c$easyopen" using "c:	mp
eportscustlist.pdf"
                              giving retCode.
   end-if

   call "c$easyopen" using "/myapp/reports/custlist.pdf"
                           0
                    giving retCode.

  call "C$DESKTOP" using CDESKTOP-OPEN 
                         "/myapp/reports/custlist.pdf"
                         1
                  giving retCode.

3. CALL CLIENT "MYPROG"
If a program named MYPROG.class is available in the client-side class path, then a program running on the server can call it using CALL CLIENT "MYPROG" and can pass it input, output or input-output parameters of any type by reference or by value just as if it was calling the program on the server.
For example, you could compile the following program and add it to your client-side jar file or have your installer put it on the client in the class path specified when your users launch the thin client:

   ID DIVISION.
   PROGRAM-ID. MYCALC.
   PROCEDURE DIVISION.
      call "C$RUN" using "calc".
      goback.

   call client "MYCALC"

**Note:
There are differences in the behavior of C$RUN/C$SYSTEM between isCOBOL and ACUCOBOL-GT.
For example, calls relying on UNIX/Linux shell syntax for redirection of standard streams should be made using the SYSTEM routine.
See "isCOBOL implementation of CALL SYSTEM and the iscobol.system.exec property" for more information and workarounds for C$RUN/C$SYSTEM if you need platform specific functionality.

1. How do I set up isCOBOL Server (Application Server) and Thin Client?
2. How do I capture client side errors when using a different look and feel (e.g. Nimbus)?
3. How do I use Java Web Start to automatically download and launch the thin client?
4. With thin client is there a way to update and push changes to programs live (on the fly), without having to kill and restart the isCOBOL Server?
5. How do I use secure transport (SSL) with the isCOBOL thin client?
6. The COBOL program suddenly terminates on the server and leaves thin client running with a blank screen
7. How do I avoid having to edit the Java security policy to allow isCOBOL thin client applet to connect?
8. How can I get the system-information data from the client computer?
9. How do I download files from server to client using isCOBOL Thin Client?
10. What are the Java version requirements on the client and server? Do they need to match?
11. How do I resolve the error 'Application Blocked by Java Security' working with jnlp?
12. Is there a way to simulate users and load-test the thin client?
13. The user name shown by the -panel is the PC Name. Is it possible have the user id of our application?
14. How can I get the local username?
15. Is there a way to distribute multiple client connections on different servers?
16. What's the meaning of the error 'Software Incompatiblity'