Other application work is necessary in the following situations:
When your application is in a language other than ACUCOBOL-GT
If your application is in a language other than ACUCOBOL-GT, you must migrate your code to ACUCOBOL-GT before you can implement Acucorp's thin client solution. You can perform the migration yourself, hire Acucorp's Professional Services Organization (PSO) to do it for you, or work together with Acucorp's PSO.
When you'd like to allow end users to print locally on their Windows machines
If you'd like to allow end users to print locally on their Windows machines, you can add calls to ACUCOBOL-GT's WIN$PRINTER function to your program. The thin client environment supports WIN$PRINTER function calls, -P SPOOLER (DIRECT) and -Q printing. (Refer to the Getting Started manual for more information.)
Note that the following WIN$PRINTER functions are not supported by thin client because of variations in memory allocated by data types on the host and the client:
Instead of using these functions, you can make calls to WINPRINT_GET_PRINTER_INFO_EX and WINPRINT_SET_PRINTER, which are very similar.
Note that if the UNIX server is not an active thin client host when a WIN$PRINTER call is made, WIN$PRINTER returns a "0" (not supported).
Any COBOL logic that disables the WIN$PRINTER capability in non 32-bit Windows environments should be removed to allow Windows client printing to work.
Printing to -P SPOOLER automatically routes the print job to the client printer.
Although it is possible to print directly to the server printer, font selection and formatting capabilities are limited. These restrictions can have an impact on form printing. It is recommended that you send the print job to the client and let the client send the job to the desired printer. Note that the desired printer must be visible to the client.
When your application makes use of the WIN$PRINTER functions WINPRINT_GET_SETTINGS_SIZE, WINPRINT_GET_SETTINGS, or WINPRINT_SET_SETTINGS
If your application makes use of the WIN$PRINTER functions WINPRINT_GET_SETTINGS_SIZE, WINPRINT_GET_SETTINGS, or WINPRINT_SET_SETTINGS, you must change your program to use the functions WINPRINT_GET_PRINTER_INFO_EX and WINPRINT_SET_PRINTER instead. Because of variations in memory allocated by data types on the host and the client, the three named functions are not supported in thin client environments. The replacement alternatives provide similar functions. (Refer to the ACUCOBOL-GT Appendices for more information.)
When you have a Windows application and want to deploy it on UNIX
ACUCOBOL-GT is so portable that if you want to deploy your Windows application on a UNIX server, you can. However, 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.