cron allows users and administrators to run unattended jobs at any time. Although this document provides examples, you should refer to your UNIX documentation for details specific to your environment.

On older versions of UNIX (pre-System V or Berkeley), cron was only accessible to the system administrator with root or superuser capabilities. If you are using a newer version of UNIX, you should have access to cron. If not, consult with the system administrator.

To run TERM as a background application using cron, do the following:

1. Set the PATH environment variable to include the directory where the TERM executable is installed, normally /usr/bin.
2. Set the TERM environment variable to the correct terminal emulation.
3. Set the HOME environment variable to your home directory. This is normally done by default.
4. Export the above three environment variables.
5. Have CRON run the shell script in background mode as follows:
   

term -q &

You must use the -q option and the ampersand &. If you do not use the -q option, you will see multiple copies of the error, “EOF error on console”.To have TERM run a TSL script when the system is rebooted, you must have a shell in the /etc/rc2.d directory that invokes TERM.

TERM for UnixWare installes from the /termunix/u3 directory on the TinyTERM/TERM CD. As it installs, it asks which UNIX you are installing to. Choose INTERACTIVE.

In order for TERM to use a serial port, the port must be set up for bidirectional access. (More information on this is in the Setup and Configuration of the UnixWare manual.) The script below should work:

pmadm -r -p ttymon3 -s 01d
pmadm -a -p ttymon3 -s 01d -s login -fu -v `ttyadm -V` -m "`ttyadm -b -h -r0 -t 60 -d /dev/term/-1s -1 9600NP -s /usr/bin/shserv -m ldterm -p "tty01 login: "`"

Change the lockfile format within the TERM setup under communications to:

/var/spool/locks/LK.%m

You must now connect to /dev/ttyxxx, not /dev/term/ttyxxx.

TinyTERM for Windows has a Display DIM attribute as option for Wyse50 and Wyse60 emulations. Century Software, Inc., has had a request to add this functionality to TERM for UNIX/Linux.

CR 842

TERM for Linux does not communicate through the Digi PortServer at all. It connects to the tty port generated, but there’s no response after that. The remote system doesn’t see anything you type in TERM, and TERM doesn’t echo anything back from the host.

CR 838

On Solaris 8, TERM gives the error, “Cannot open device” when connecting to a tty port. This works properly on earlier versions of Solaris. Changing the port permissions does not help, nor does starting TERM with the -i command-line parameter.

With TERM for HP-UX, if you specify a .con file on the command line:

term connection.con

it does not successfully connect via modem. You get the error, “Modem not responding” instead. The modem responds normally if the .con file is not specified.

CR 633

The TERM for UNIX documentation states that in 132-column mode, you can use the Ctrl-Right Arrow key combination to scroll sideways. But the display text wraps at 80 columns regardless of whether 132-column mode is on or off. The TSL SET WRAP OFF command is also ignored.

CR 579

Run the following script command in TERM for Linux:

setkey sf1 “text”

No matter how it’s actually mapped, Shift-F1 does nothing. The same is true all the way through Shift-F12. Ctrl-function keys also fail, as do Ctrl+Shift and Alt keys. You can see this by running:

term -z ktest.cmd

In fact, Shift-F5 displays as “sf1” using that script. Shift-F8 is “sf4” and nothing past that works at all.

This also affects TERM for SCO UNIX versions 6.2.5b and 6.28 running on SCO 5.0.6 or higher. SCO maintenance pack 2 for SCO OpenServer 6 restores the system console to ANSI, instead of the default AT386. This fixes the problem on that particular OS.

CR 565

Th error “Dynamic linker relocation error: symbol not found BLKNO” may come up when TERM tries to connect to a tty port on SCO OpenServer 5.0.6. It indicates a missing linked library on SCO. Installing the latest updates from SCO will normally resolve the problem.

CR 549

The Telnet terminal type setting in TinyTERM allows you to change the terminal type that the host sees announced in telnet connections. It also applies to SSH connections. In older versions of TinyTERM for Windows, it’s called the netterm setting.

Unlike TinyTERM, TERM for UNIX/Linux does not have a Telnet terminal type or netterm option. Century Software, Inc., has had a request to add this feature.

CR 524