Technical article 112082

The terminal type 'scoansi' is not behaving as expected and/or applications in scoansi dump core on OpenServer 5.0.6 and 5.0.7

OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

I am seeing unexpected behavior when using the scoansi terminal type on SCO OpenServer 5.0.6 and 5.0.7.

Solution

The following are excerpts from the OpenServer 5.0.6 documentation library available at http://osr5doc.xinuos.com.

http://osr5doc.xinuos.com:457/FEATS/RN_feat_console.html:

The console driver has been changed substantially for this release.

New escape sequences have been added to increase efficiency of curses(S) and to improve conformance to the ANSI X5.64-1979 escape sequence standard. For more information on the escape sequences supported, see the screen(HW) manual page.

Under the default configuration, remote logins to a Release 5.0.6 system from an SCO OpenServer release prior to Release 5.0.6 should not use the scoansi terminal type. Use the ansi or scoansi-old types to avoid problems.

For backwards compatibility, you also have the option of customizing the console driver configuration to suit your needs using mkdev scoansi:

You can configure the terminal types to revert to their former behavior, allowing remote logins to use the scoansi type for old behavior or scoansi-new for the new.

For application compatibility, you can also change the in-kernel scoansi emulator to pre-5.0.6 behavior.

For more information, see mkdev(ADM).

The following is an excerpt from the manual page for mkdev(ADM).

http://osr5doc.xinuos.com:457/cgi-bin/man/man?mkdev+ADM:

mkdev scoansi configures the behavior of the scoansi termcap(F) terminfo(F) database entries and the in-kernel scoansi terminal emulator. As of Release 5.0.6, console driver improvements have been made that may cause problems with applications expecting the old scoansi behavior. Basic terminal compatibility is provided in the form of scoansi-old and scoansi-new terminal database entries. SCO OpenServer systems prior to 5.0.6 and other UNIX systems performing remote logins should use the scoansi-old terminal type (unless the system has been reconfigured to use the old entries as described here).

You can use mkdev scoansi to change either the database entries (affecting logins) or the in-kernel scoansi emulator (affecting applications that use the scoansi control sequences). The options are:

1.Use new (5.0.6 and later) terminal database entries
2.Use old (pre 5.0.6) terminal database entries
3.Use new (5.0.6 and later) in-kernel scoansi emulator

4.Use old (pre 5.0.6) in-kernel scoansi emulator (backwards compatibility mode)

Changing the in-kernel emulator causes the kernel to be relinked and the system must be rebooted. See screen(HW) for more information.

http://osr5doc.xinuos.com:457/OSr506/latenews.html#LN.scoansi_apps:
Applications in scoansi dump core

If you have an existing application that began dumping core with SCO OpenServer Release 5.0.6 and your TERM variable is set to scoansi, try setting $TERM to scoansi-1k and restarting the application. For example,

ksh users enter:
TERM=scoansi-1k; export TERM
csh users enter:
set env TERM scoansi-1k
If this corrects the problem, this means that the application
has a termcap buffer that is too small. Contact your application
provider to correct the problem; application providers, see
``Incorrect termcap buffer documentation''.
Incorrect termcap buffer documentation

The termcap(F) manual page incorrectly states the size limit of the termcap buffer as 1024; the correct limit is 2048.

See also

Manual pages: mkdev(ADM), screen(HW), termcap(F), terminfo(F),
curses(S)
OpenServer 5.0.6 SCOHelp documentation (http://osr5doc.xinuos.com)

From the Xinuos technical article database, record 112082. Reproduced with permission. The original is at www.sco.com/ta/112082, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.