You may want to adjust your application for the individual Windows characteristics.
Windows applications that contain direct calls to the Windows API must be modified to remove these calls, whether you deploy on a Windows or UNIX server.
ACUCOBOL-GT is so portable that you can deploy your Windows application on a UNIX server, if you wish. As mentioned earlier, if your application calls Windows API functions directly, you will need to remove these calls. If it relies on DOS file-naming conventions and directory structures, you will need to modify your program with UNIX file names and directories.
Some programs that are intended to run under multiple operating systems may test the OS-IS-WINDOWS flag to determine whether a graphical display is available. If your server is not a Windows machine, these programs assume that graphics are not available in thin client. Programs like this should test the HAS-GRAPHICAL-INTERFACE flag rather than OS-IS-WINDOWS. See ACCEPT Statement in the ACUCOBOL-GT Reference Manual for descriptions of ACCEPT FROM SYSTEM-INFO and ACCEPT FROM TERMINAL-INFO.
Your UNIX applications can access Windows help via the ACUCOBOL-GT $WINHELP library routine. Calling $WINHELP from your COBOL program sends the given arguments to the thin client to process. The thin client eventually calls the Windows help program with the arguments given to $WINHELP. Note that the help file is not copied to the client machine, but the client must be able to find this file. In a local office environment, help files can be installed on a local hard drive or a shared drive. Remote users should install the help files on the client machine. (More information about $WINHELP can be found in the appendix "Library Routines" in ACUCOBOL-GT Appendices.)
Some $WINHELP op-codes are not supported in a thin client environment. If your application uses them, you may experience unexpected system terminations. These op-codes are