skip to main content

Library Routines

Library Routines
isCOBOL supports the following Library Routines:
To override one of these library routines you can compile with the -sysc option.
Sample programs for each library routine are available among the isCOBOL Samples.
The table below lists the library routines along with their usability in the various scenarios. For each routine it’s specified if it can be used in stand-alone, thin client and web, with some advice where applicable.
 
YES[1]
[1]For the copy client to client there’s no difference between using the @[display]: prefix before file names or calling the routine via CALL CLIENT.
YES[1]
[1]For the deletion of a file on the client machine there’s no difference between using the @[display]: prefix before the file name or calling the routine via CALL CLIENT.
YES[1]
[1]To run the utility client-side is better to rely on the client-server flag parameter instead of using CALL CLIENT.
NO[1]
NO[1]
[1]In WD2 environment you can call the WD2$REDIRECT routine, in EIS environment you can use the displayBinaryFile method of the HttpHandler class (for example comm-Area:>displayBinaryFile(tmp-file-name "application/pdf").
YES[1]
YES[1]
By default print jobs are executed client side. [1] The WD2 environment and the EIS environment don't support the print preview.
YES[1
[1]To run a command client-side is better to rely on the CSYS-DESKTOP flag parameter instead of using CALL CLIENT.
YES[1]
[1]Instead of calling REG routines via CALL CLIENT it’s better to call DISPLAY_REG routines.
YES[1]
[1]Only to manage printer fonts.
YES[1]
[1]In WD2 it’s not possible to display a menu on the try icon.
[1]In WD2 it’s not possible to set a custom mouse shape

Copyright (c) 2017 Veryant
Contact us
Please share your comments on this manual or on any
Veryant product documentation with the email button at the top left