“SJ_MIXED_MODE” in the run-time parameters. This will cause the API to clear the screen. We hope in due course to be able to have the ACUCOBOL run-time do intelligent switching between GUI mode and Character Mode display windows. e) “VPRINTSCREEN”. With the transition to GUI screens there are many more ways to get full screen image shots that make the crude character representation performed by VPRINTSCREEN redundant. However, if you are running ScreenJet generated ACUCOBOL GUI screens on a Windows server, VPRINTSCREEN will direct a graphical screen print to your local printer, complete with date and time stamp.
2) Things for which support is unlikely, ever. a) CONFIG Phase Statements. These statements are only actioned by VPLUS if it detects that the Terminal is an HP2645; otherwise it ignores them. As we suspect that the number of 2645 Terminals still in use for applications can probably be counted on one hand, we have chosen to not implement this functionality. It is also highly unlikely that any modern display device will be equipped with the lights, internal tape drives and paper tape readers that the Config statements used to control. b) “VGETIEEELONG”, “VPUTIEEELONG”, “VGETIEEEREAL”, “VPUTIEEEREAL”,
“VGETREAL”, “VPUTREAL”, “VGETLONG”, “VPUTLONG”. These number types are not supported by COBOL therefore it is highly unlikely that you will be attempting to port an application to ACUCOBOL-GT that uses these functions. c) “VLOADFORM”, “VUNLOADFORM”. These commands caused VPLUS to load and unload forms into the display memory of particular types of Terminal when it detected their use. These functions have no modern equivalent, and as VPLUS ignored them unless specific terminal types were used, we have adopted the same approach with the ScreenJet VPLUS API. d) “VARMSCP”, “VGETSCPFIELD”, “VGETSCPDATA”. These cursor-positioning commands returned the field and the data from the current cursor position. e) “VBLOCKREAD”, “VBLOCKWRITE”. These functions would read the whole screen including all the formatting escape sequences and, as such, have no GUI counterparts. f) “VOPENBATCH”, “VCLOSEBATCH”, “VREADBATCH”, “VWRITEBATCH”,
“VPOSTBATCH”. These functions deal with files of screen data (from the same screen). Few applications use this approach at this time.
VPLUS API
The VPLUS API is written in ACUCOBOL so it is as portable as the applications you convert. It is supplied as an ACUCOBOL Library (.Lib) object.
HP 3000 Evolution Migrating a 3000 Application
• 215
