> Anyone using VPlus know of work arounds for the following problem.
>
> Problems with VPLUS VTURNON/VTURNOFF intrinsics:
>
> 1       Calling VTURNOFF does not leave current screen image
>         alone, contrary to documentation, rather it clears the
>         screen.

Last I heard, this was a known problem in Vplus for 700/9x-series
terminals. The official response center workaround is to set the
eighth byte eight in the first record of the VENVCNTL.PUB.SYS file
to "1".

Another workaround (the one I prefer) is to change the terminal type
(the "identifier" - 59th 16-bit field in COMAREA) to 56, which
represents a 2392 terminal just before the VTURNOFF call, then
change it back after the VTURNON call. As far as I know, this only
needs to be done for 700/9x-series terminals, so I usually check
for an identifier value of 72, 74, or 76 (terminal identifiers are
documented in Appendix G of the Vplus manual).

> 2       VTURNON replaces the saved user keys originally read
>         by VOPENTERM with the  keys as they appear when called,
>         these new (wrong) keys are faithfully setup by
>         VCLOSETERM when it gets eventually called.
>
>         VTURNON has to be the culprit because calling VCLOSETERM
>         immediately after calling VTURNOFF (not a normal calling
>         sequence) restores the proper keys, whereas an intervening
>         call to VTURNON resets the keys to the form keys on
>         screen at the time. You momentarily see the default keys,
>         quickly replaced by the wrong keys when calling VCLOSETERM.
>
>         Perhaps there are new bit settings for the TERMOPTIONS or
>         SHOWCONTROL items in the COMAREA to control these functions
>         that are not documented.

I don't know about this one - we usually either log the user off
after exiting from a program (logon-UDC style), or manually reset
the function key labels/values.

Good Luck. Ray.