9.navision Under UNIX

All
NAVISION UNDER UNIX
1 Dok:
All
This publication may at any time be subject to change without prior notice. Any changes are
not to be regarded as binding upon Navision Software a/s in any way.
Navision Software a/s shall assume no responsibility whatsoever for any faults or shortcomings
in this publication.
The software described in this publication is supplied under licence and is solely to be used
and copied in accordance with the enclosed licence conditions.
No part of this publication may be reproduced in any form or by any means, mechanical,
photocopying or ortherwise according to existing Danish legislation on copyrights.
Copyright © 1996 Navision Software a/s
ISBN 87-7849-161-4
Navision® is a registered trademark of Navision Software a/s.
2 Dok:
All
TABLE OF CONTENTS
1. INTRODUCTION 1 3. SETTING UP CONNECTIONS 15
1.1 Introduction to Navision 3.1 Setting Up a UNIX System

under UNIX 2 as Database Server 16
The Typography and Symbols Specifying Services 16
in this Manual 4 Setting Up TCP/IP -
to Avoid Locking 17
Testing a TCP/IP Connection 18
2. INSTALLATION TYPES 5 3.2 Installing a Client on a PC 19
The Installation Program 19
2.1 Selecting an Installation 6 3.3 Setting Up a Client on a PC 20
UNIX as a multiuser system 6 Specifying Hosts 20
Selecting Terminals or Specifying Services 21
Terminal Emulation 7 Printer Selections 21
UNIX as Client/Server 9 3.4 Setting Up the UNIX System
Network Types 10 as a Client 23
Both Multiuser System Specifying Hosts 23
and Client/Server 11 Specifying Services 23
2.2 Examples of More Advanced 3.5 TCP/IP Setup 24
Installations 12 Testing a TCP/IP Connection 24
Asynchronous Multiplexers 12 Optimizing TCP/IP
X.25 12 Communication 25
ISDN 13 TCP/IP Error Messages 25
UNIX as Router 13 3.6 Setting Up UNIX as
a Multiuser System 26
Automatic Path to the
Navision Directory 26
Write-protecting the
Program Files 27
3.7 Setting Up Terminals 28
Printer Selections 29
3 Dok:
All
4. STARTING Navision 5.5 The NAVITERM Menu 61

UNDER UNIX 31 5.6 Remote Control of NAVITERM 62
Pass-through Print 62
4.1 Starting Navision Client/- Automatic File Transfer 67
Server 32 Starting an External Program 68
Starting a Navision Integrating NAVITERM with
Database Server 32 Other Programs 69
Starting a Navision client 5.7 Testing and Troubleshooting 70
under DOS and OS/2 34 Testing TCP/IP before
Starting Navision on a UNIX Starting NAVITERM 70
System which is a Client 35 Testing a Handshake 71
4.2 Starting a Terminal or Overflow Errors 71
Terminal Emulation 36 Framing and Parity Errors 72
4.3 Navision Setup with If NAVITERM Won’t Start 72
Start Parameters 37
cache 38
commitcache 39
database 41 6. MAKING BACKUPS 73
dbgroup 42
dbreadonly 42 6.1 About Making Backups 74
dbtest 42 When You Should Backup
debug 43 Your Data 75
id 43 Procedures for Making Backups 75
keyboxpath 45 6.2 Making Backups in Navision 76
local 45 Testing the Database before
macro 45 Copying to a Tape Station 76
nettype 45
serialno 46
serverno 46
temppath 47 APPENDICES 77
A.1 TCP/IP Protocols 78
5. TERMINAL EMULATION
WITH NAVITERM 49 B.1 Control Codes and
Keyboard Esc Sequences 80
5.1 About NAVITERM 50 Esc Sequences 80
5.2 Equipment Requirements 51 Function Keys 81
5.3 Installing NAVITERM 52 B.2 Control Codes for
Installing Terminfo 52 Pass-through Print 83
5.4 Starting NAVITERM 53
Starting NAVITERM with
TCP/IP 53 C.1 Compatibility among DOS,
Starting Serial NAVITERM 54 OS/2 and UNIX 86
Handshaking - Controlling
Data Transfer 56
Cables 58
NAVITERM and Windows 60
ii Table of Contents
4 Dok:
All
CHAPTER 1
INTRODUCTION
This guide describes how to set up Navision under UNIX as a multiuser system or
according to the client/server principle. This chapter gives a general introduction to
Navision under UNIX, and can also be used as a reader’s guide to the rest of the book.
Attention! In this book, in general, and especially in connection with installation, a

thorough familiarity with UNIX systems and setup of TCP/IP networks are prerequisites.
5 Dok:
All
1.1 Introduction to Navision under UNIX

This chapter contains a general introduction to Navision under UNIX,
and to this book. It gives you an idea of where in the book you can find
the relevant descriptions.
Installation types When you use Navision under UNIX, the program can be used from:
(Chapter 2)
• PCs connected to the UNIX system through a network (client/server)
• PCs connected serially to the UNIX system (terminal emulation)
• terminals connected to the UNIX system
This book starts with a chapter which gives an overview of the options
associated with UNIX installations. More detailed instructions and
requirements to the individual types of UNIX systems can be found in
the readme-files that come with the Navision-server package.
The rest of the chapter is meant as a source of inspiration, where more

advanced installations are described, for example: asynchronous
multiplexers, the X.25 network, the digital telephone network ISDN, or
use of the UNIX system as a way station (router).
Setting up When you know which installation you will have and are aware of the
connections requirements for equipment, communication, etc., you can complete the
(Chapter 3) installation. Start by installing the Navision-server on the UNIX system
as described in the readme-file that comes with the server package.
After this, select the area that corresponds to the installation:
• Setting up the UNIX system as database server, and

• Installing and setting up a PC client, or
• Setting up another UNIX system as client for the first and
• TCP/IP setup
or
• Setting up the UNIX system as a multiuser system and

• Setting up terminals
Terminal emulation is described separately in chapter 5.
2 Introduction to NAVISION under UNIX
6 Dok:
All
Starting and When the installation is completed, Navision can be started with the
setting up navi command. This chapter describes:
Navision
(Chapter 4) • Starting client/server (database server, DOS, OS/2 and UNIX clients)
• Starting terminal/terminal emulation compared with a UNIX multiuser
system
The rest of the chapter describes Navision’s start parameters. It is not

necessary to specify these the first time the program is started, but when
you begin using Navision they can affect performance. The parameters
are:
CACHE, COMMITCACHE, DATABASE, DBGROUP, DBREADONLY, DBTEST,

DEBUG, ID, KEYBOXPATH, LOCAL, MACRO, NETTYPE, SERIALNO,
SERVERNO, TEMPPATH.
Terminal When Navision is run on PCs which are connected to the UNIX system
Emulation through serial communication or a network, a terminal emulator called
(Chapter 5) NAVITERM is used. As this is a large single topic, it is described in
a separate chapter. This chapter has the same structure as the rest of
the book, that is: requirements of the equipment, installation, starting
NAVITERM, etc.
Making Backups It is very important to make backups. Unfortunately, not everyone is aware
(Chapter 6) of this. This chapter describes when to make backups, procedures for
making backups, Navision’s function for making backups as well as a
test of the database before copying to a tape station.
Introduction to NAVISION under UNIX 3
7 Dok:
All
The Typography and Symbols in this Manual
The typography and symbols are used consistently in all the Navision
manuals. This makes it very easy to simultaneously use in the program
and recognize what is described in the book. The following typography
and symbols are used:
Field Names All field names are underlined in the text.
Field Contents The contents of a field, or what should be entered/selected,

Customer No. from a list, for example, is written in italics.
PULL-DOWN The functions on the pull-down menu uppermost in each

FUNCTIONS, window are written with capital letters. The letter which
[Alt]/[F10] can be pressed (together with [Alt]) to activate the sub-
menu will be a little larger than the others. If the function
can also be selected with a function key (possibly combined
with [Ctrl] or [Shift]), this will be written just after the
pull-down function.
[Keys] Keys such as the function keys, [F1], [F2], for example,
or key combinations such as [Alt] [F] are always in this
type of box.
AL Code and This font, called Courier, is used to highlight all AL

parameters trigger codes, start parameters, and operating system
commands. When it says that you should type C:\NAVI\-
database, for example, it can look as though there is
space between some of the characters. This is due to the
font, and when you type the corresponding string on a
command line, it should be without spaces.
4 Introduction to NAVISION under UNIX
8 Dok:
All
CHAPTER 2
INSTALLATION TYPES
This chapter describes which type of installations can be set up with Navision under
UNIX. It also describes what is required of the equipment to be used, and it gives
a number of examples of more advanced installations as inspiration for selecting your
own installation. This chapter is divided up as follows:
• Selecting a type of installation
• Advanced installations
9 Dok:
All
2.1 Selecting an Installation

You can choose three different ways to use Navision under UNIX:
• The UNIX system can be a multiuser system, with terminals and PCs
(with terminal emulation) connected.
• The UNIX system can be a server and have PCs with DOS and OS/2
or other UNIX systems as clients.
• Both of the above methods can be used simultaneously.
The advantages and disadvantages of these two methods are described

in the following section.
UNIX as a multiuser system
When you use the UNIX system as a multiuser system you take
advantage of its ability to have multiple simultaneous processes and
users. All Navision users have their own processes, which means that
multiple users can use the database at the same time. The connected
workstations can be terminals or PCs. The latter are connected with a
terminal emulator, NAVITERM, for example.
If you want to structure a network of Navision workstations over a

larger geographical distance this can be done with asynchronous
multiplexers (see page 12), which make it possible for different
departments to use the same database, and thus the same company
information, very cheaply, as the same telecommunication lines, modems,
etc. can be used.
If PCs will be used as workstations, terminal emulation can be done

using:
• NAVITERM, which is Navision’s own terminal emulator. It requires

a modem with an autodialer, as NAVITERM does not have a dial-
up function.
• Other terminal emulators with dial-up support. But these do not provide
the same usability as NAVITERM, which is created especially for
Navision.
As Navision runs centrally on the UNIX system, the locally connected

users are not affected, even though other remote users are working
through a slow modem.
6 Selecting an Installation
10 Dok:
All
Terminal emulation can also take place over a local network (also local
networks in other locations), connected with bridges, routers, etc. Read
more about the UNIX system as a router on page 13.
The illustration below shows how these options can be used in practice
with different types of networks and workstations:
UNIX Server Naviterm Naviterm Terminal
e
nous Lin
Asynchro
Naviterm Naviterm Terminal
MUX
MODEM
MUX
Leased
Line MODEM
Remote Site
Ethernet running TCP/IP
BRIDGE
Naviterm Naviterm Naviterm

MODEM
Leased Line
MODEM BRIDGE
Naviterm Naviterm Naviterm
Remote Site
Selecting Terminals or Terminal Emulation
Navision can be used with the terminal types specified in the readme-
file that comes with the program. There it is also specified whether the
terminal uses scan codes, and which UNIX environment variable $TERM
should be set at so that the terminal can be used.
Selecting an Installation 7
11 Dok:
All
Navision’s screen appearance and printout handling under UNIX depend

to a certain extent on which terminal/terminal emulation is used. Below
are descriptions of usability in a number of different installations. The
description are arranged so that the solutions with the best usability are
described first.
UNIX server All keys function as described in the help screen. On the monitor there
with DOS or is a full 8 bit character set and all the colors which Navision uses.
OS/2 client Printout is done locally and directly to the files generated by reports
placed on the PC. The setup is as though a local Navision is being
used, only a remote database is used. Printout and files can be sent further
to a LAN server if a LAN requester is installed in the workstation.
NAVITERM on All keys function as described in the help screen. The monitor has a full
PC via LAN 8 bit character set and all the colors Navision uses. Screen updating
or serially etc. can take place a little slower than on client/server. Printout takes
place on the UNIX system to which NAVITERM is connected (not the
PC from which NAVITERM is run). Files generated by Navision reports
are also placed on the UNIX system.
IBM 3151 or Special Navision modules have been developed for use with IBM 3151
WYSE 120 and WYSE 120 terminals. This means that terminals can be used in scan
terminals code mode with complete keyboard usability. In addition, a full 8 bit
character set is used, but no colors. Printout takes place on the UNIX
system. Navision reports which generate files also place the files on
the UNIX system.
Attention! On SCO there is no support for WYSE 120. On HP there

is no support for WYSE 120 and IBM 3151.
Terminfo Navision can be used from almost all types of terminals and terminal
emulations where terminfo is used. This means that limits can exist in
relation to Navision’s normal screen appearance and keyboard functions.
It should be possible to use Terminfo if it is used in order to use
terminals or terminal emulation that already exists in the relevant
installation.
Navision for UNIX comes with tools that can be used to customize
Navision to a given terminal that uses terminfo. Customizations of this
type can improve appearance, but they will always be limited by the
facilities for/to the terminal or terminal emulation used.
Printout takes place from the UNIX system. Navision reports which
generate files also place the files on the UNIX system.
12 Dok:
All
UNIX as Client/Server
When you use the client/server principle, the UNIX system functions
as server for a number of workstations. This burdens the UNIX system
less than with the multiuser system setup, where all data processing takes
place directly on the UNIX system. When the UNIX system is server,
it only works with the database, while all calculations and screen updates
are done by the clients.
Attention! Notice that when you run the UNIX system as a multiuser
system, the client/server installation requires no further purchase of user
license(s) for the UNIX operating system.
A UNIX system can also be client for another UNIX system. In this
way you can divide the strain on the CPU between several UNIX
systems, and simultaneously get an installation that is easier to maintain,
because remote terminals can be connected to the UNIX client. When
you need to connect several remote terminals or other hardware, it is
only necessary to close the UNIX client down, while all the local PC
clients can continue running using the central UNIX server.
When shouldn’t • Client/server should only be used in local networks.

client/server
be used • If a bridge or routers are used, keep an eye on the response times.
• Client/server should not be used with line speeds of less than 64 Kbit,
but higher is okay.
It is also important to notice that when you run client/server, the speed
of the individual client can influence the other Navision users. If a
slow system or a system which uses a slow bridge locks a table, the
other users will have to wait longer to gain access to that table.
13 Dok:
All
Network Types
When a UNIX system is used as server, several different types of

network can be used together. A token-ring network with PCs can, for
example, be used with a UNIX-based Ethernet. The workstations for both
networks can run Navision without using other software or hardware.
You should, however, be aware of the following:
• Communication between DOS or OS/2 systems and the UNIX system

takes place through TCP/IP.
• The system that will be server must use TCP/IP. A setup with a PC
as server is, therefore, not possible - but would probably not be selected,
as this does not take advantage of the power of the UNIX system.
• In cases where you need a lot of free memory for PC clients, it is an

advantage to use OS/2, as Navision DOS extender cannot be used in
a network with TCP/IP.
• When you work with Navision under UNIX, there can be one active,
common database at a time, and all work is done in it. Just as under
DOS and OS/2, it can be divided into multiple database files which
can be placed where there is most space.
TCP/IP Regarding the possibility of frequent updates, information on valid TCP/IP

types and versions is in Appendix A on page 77 in this book.
14 Dok:
All
Both Multiuser System and Client/Server
A UNIX system can function as a multiuser system while it runs as

server in a client/server setup. This means that there is a groups of users
which work with Navision from terminals and a server which services
a number of clients. But they all work with the same database on the
UNIX system.
The illustration below shows an example of a server with two types of

network and workstations running client/server.
UNIX Server Client Client Client
T-R
UNIX Client Naviterm Naviterm Naviterm
Client Client Client
If you use UNIX Client as router then the database will be on UNIX Server
15 Dok:
All
2.2 Examples of More Advanced Installations

This section can be used as a source of inspiration when selecting an
installation, but it does not contain specific installation instructions. Be
aware that not all UNIX systems have all the communication options
mentioned.
Asynchronous Multiplexers
With advanced asynchronous multiplexers (physical equipment) you can

structure larger networks of Navision workstations. The various multi-
plexers can also function as way stations for others, that is, two
multiplexers can be connected one after the other, which saves
telecommunication lines.
There are also multiplexers with built-in net cards, which can be
connected directly to the LAN where the UNIX system is connected, and
then function as terminal server for a number of remote multiplexers.
Use of multiplexers means that use of the capacity on the telecommunica-

tion lines is improved. Typically, 6-12 terminals can run on a 19.200
bps telecommunication line. Some of the ports in the multiplexers can
also be connected to printers.
One disadvantage of multiplexers is that they can result in limited access

to mail systems and other PC programs that run on the LAN connected
to the UNIX system.
X.25
With the X.25 network you can have terminals and/or NAVITERM run
on joint Navision systems over large distances. It is possible, for
example, for a sales office abroad to gain access to the head office’s
Navision installation.
This can be configured so everything takes place automatically, depending

on the selected PAD (Packet Assembler Disasembler). When the user
turns his/her terminal on or starts NAVITERM on his/her PC, the PAD
will automatically call up to the UNIX system and start Navision,
without it being necessary to type long X.25 numbers, etc.
12 Examples of More Advanced Installations
16 Dok:
All
Most UNIX platforms can use X.25 in two different ways:
• with the TCP/IP protocol on top of the X.25 protocol

• as X-28 (PAD)
With TCP/IP on top of X.25 a completely transparent TCP/IP connection,

is achieved, that is, you can use all the normal TCP/IP utilities, such as:
telnet, ftp, tftp, lpr/lpd, etc.
This gives the highest degree of usability, but on the other hand poor
performance, as many characters must be sent back and forth to stear
the communication (X.25 Header, TCP/IP header, etc.). If only terminal
traffic is necessary (on a terminal or via NAVITERM), then it is an
advantage to use a PAD in the foreign office, and PAD software on the
UNIX system. This gives a much better performance in relation to the
line speed selected for the X.25 connection. Most PAD software can also
have a printer connected to the remote part of the connection. If the
operating system allows it, a printer can be connected to the AUX port
if a terminal is connected.
ISDN
Most UNIX platforms can use the digital telephone network, ISDN. In
many cases the TCP/IP protocol and Navision can run both as client/server
and terminal-based. Whether there is an economic advantage of using
ISDN depends on how much Navision is used. If it is used more than
a few hours daily, then it is normally more worthwhile to have fixed
lines.
UNIX as Router
Most UNIX systems can be used as way stations, routers, and forward
TCP/IP traffic from one type of network to another. The same is true
for a number of TCP/IP software packages to DOS or OS/2. This can
be used with Navision to have a client or NAVITERM run on ARC-
net or baseband-net, for example, even though it is not directly supported
by the UNIX system. A PC should just be set up as router between
ARC-net and Ethernet, for example. Alternatively, the routing can be done
by a Novell server. The fact that Navision for UNIX uses TCP/IP
makes it very flexible to structure an installation with many different types
of networks and systems. It is also possible to use a Macintosh, for
example, if TCP/IP with terminal emulation is installed. Navision then
runs terminal-based on the Macintosh.
Examples of More Advanced Installations 13
17 Dok:
All
14 Examples of More Advanced Installations
18 Dok:
All
CHAPTER 3
SETTING UP CONNECTIONS
This chapter describes how you setup the connections between the UNIX system and
the rest of the installation. The chapter assumes that you have installed Navision on
the UNIX system as described in the readme-files that come with the Navision-server
package and that you have read the section Introduction to Navision under UNIX
on page 2 of this book. This chapter covers the following topics:
• Setting up the UNIX system as database server
• Installing and setting up PC clients
• Setting up the UNIX system as a client
• Setting up TCP/IP
• Setting up the UNIX system as a multiuser system
• Setting up terminals
19 Dok:
All
3.1 Setting Up a UNIX System as Database Server

Before the Navision database server can be used you should do the
following to ensure proper communication:
• Specify services (TCP/IP ports)
• Set up TCP/IP so locking can be avoided
• Test TCP/IP
These topics are described in this section.
Specifying Services
The /etc/services file determines which TCP/IP ports will be used

for the various programs. A Navision server with the number 1 uses
port number 2407 as a standard, a server with the number 2 uses 2408,
server 3 uses 2409 etc.
Normally it is not necessary to make changes in this file, but if the

port to be used for the server is busy (that is, if the port number in the
/etc/services file is being used by another process), then the port
number can be moved if you add a new line to the file, for example:
naviserv 3001/tcp
Now server 1 has port number 3001, server 2 has port number 3002,
server 3 has port number 3003, etc.
Attention! If you make changes in services on the database server,

then you should also make changes in services on all client units,
otherwise the client will not be able to find the Navision server on the
network.
16 Setting Up a UNIX System as Database Server
20 Dok:
All
Setting Up TCP/IP - to Avoid Locking
When a UNIX server is started, it "listens" on the allocated TCP/IP port.

When it receives a call from a client which has been started, it activates
a new server process, and turns over communication with the client to
it. Then it is ready to receive a new call from the next client which has
been started, etc. (se also Navision’s serverno start parameter on page
46).
AIX In order to prevent a Navision client which has been turned off while
posting (or something similar) from locking the database for other users
for a long time you can, on an AIX system, determine how often the
TCP/IP protocol should check the connection between server and client.
If you do not specify a value, then the standard value, circa two hours,
is used. To avoid having to type this selection every time the server has
been turned off you can place the commands in a command file which
will automatically be processed each time the system is turned on. The
commands, which reduce the time to about 25 seconds, are as follows
(the values are specified in half seconds):
$ no -o tcp_keepidle=20# 20*1/2 = 10 seconds pause

$ no -o tcp_keepintvl=5# 5*1/2 = 2.5 seconds between each attempt
This gives a little extra traffic in the network if there are many "non-
active" users. If there are more than 100 users then the above parameters
must be significantly increased.
HP and SCO There is no corresponding possibility of adjusting these parameters here,

so on these systems the values are set from the start to give about two
hours waiting time if a system is turned off while the database is locked.
Likelihood of locking of the database is, therefore, greater.
Setting Up a UNIX System as Database Server 17
21 Dok:
All
Testing a TCP/IP Connection
If a client/server installation does not function as it should, you can do

the following to locate the cause:
1) Check whether there is a TCP/IP connection to the UNIX system.

This is done with ping or telnet, for example (see the TCP/IP
package documentation). If the server’s host name is used, then
you should check that the hosts file is okay. If a client is normally
started with serverno=1, then the ping test is activated with:
ping naviserv1
If there is no connection then look for the problem in the TCP/IP

setup on either the client or the server.
2) If ping works satisfactorily, you can try Navision’s net test

program. This consists of a server portion and a client portion. A
description of the net test programs comes on the diskette. On the
UNIX system, run the netsrv program, which tests whether port
numbers have been changed in the services file. If everything
is okay, then the net test program counts the packets sent, and does
a performance measurement which can be used to adjust the TCP/IP
setup.
The net test should run for a while (5-15 min.), so you can be sure
that no packets disappear, and that no checksum errors occur. If
the net test runs without errors then Navision can normally also
start correctly, communication-wise. The net test does not check
whether UNIX is correctly set up.
18 Setting Up a UNIX System as Database Server
22 Dok:
All
3.2 Installing a Client on a PC

Navision is installed on the PCs that will be clients using the diskettes
that contain either the DOS or OS/2 client. Then the navi_inf.dat
file should be copied to each client from the UNIX license diskette.
The Installation Program
1) Turn on the PC. When it is ready, you should first create a directory
on the hard disk. This directory is where Navision will be placed.
If Navision will be placed under C:\NAVI, for example, then

type: MD C:\navi and press [Enter].
2) Insert diskette no. 1 in a diskette drive, drive A, for example.
3) Switch to this drive by typing A:, and press [Enter].
4) Type INSTALL C:\navi, and press [Enter] (under DOS) or,
type INSTALL2 C:\navi, and press [Enter] (under OS/2).
Now the following window appears:
˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝»
” ”
” ”
” ”
” NAVISION Installation ”
” Start ”
” installation? ”
” ”
” Press [Enter] ”
” ”
Figure 3.1 ” ”
Installing ” ”
” ˜˜˜˜˜´˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜´˜˜˜˜˜¿ ”
Navision ” ‡ ‡˝˝˝˝˝˝‡ ‡. ‡ ”
” ˆ˜˜˜˜˜`˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜`˜˜˜˜˜· ˜˜¿ ”
” ‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡ ‡ ”
” ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜ ”
” A:\ ”
” ”
¨˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝…
Press [Esc] to cancel or [Enter] to start the installation. Then follow

the instructions on the screen. When all the diskettes have been read,
the installation program gives the message that the installation is
completed. Navision is now installed on the hard disk, and can be used.
Installing a Client on a PC 19
23 Dok:
All
3.3 Setting Up a Client on a PC

For a PC to be able to run as a Navision client on a UNIX server,
there are a number of things that must be set up:
• Hosts the PC client can make contact with.
• Services (TCP/IP port) which correspond to those specified on the

server.
• Printer selections.
All these areas are described in this section. In addition, the selected
TCP/IP communication package should be installed and configured as
usual, and there should be a TCP/IP connection to the UNIX system.
Tests, etc. of this are described in the section Testing a TCP/IP
Connection on page 24.
Specifying Hosts
The etc\hosts file in the TCP/IP directory contains a list of all the
hosts which a certain system can come in contact with via the TCP/IP
network.
In order for the clients to be able to ’find’ the Navision server on the
UNIX system, the server number (1, for example) is added with a line
in each client’s hosts table, as below:
x.x.x.x naviserv1
(x.x.x.x specifies the server’s TCP/IP address)
The connection to the server can be tested with the below command,
which tries to send TCP/IP packets to the server system:
$ ping naviserv1
If a response comes from the server system then the connection is okay.
20 Setting Up a Client on a PC
24 Dok:
All
Specifying Services
The etc\services file in the TCP/IP directory specifies which TCP/IP

ports the various processes use. For example:
Navision server number 1 uses port no. 2407 as a standard

etc.
If a port is busy, that is, the relevant port number in the services file
on either the server or the client is being used by another process, the
port numbers can be changed. This is done by adding a line such as the
following to the etc\services file:
naviserv 3001/tcp
After this, server number 1 uses port number 3001, server number 2
uses port number 3002, etc.
If the server’s standard port number is changed then it should also be

changed for all workstations.
Printer Selections
If you run client/server you only have access to local DOS and OS/2
printer ports (LPT1, LPT2, etc.), which can also be redirected to a LAN
server (DOS, OS/2, Novell, Banyan Vines, etc.).
In systems where some workstations runs via NAVITERM while others

run client/server, the clients will often need to print out to a UNIX printer.
This is possible if the TCP/IP package used supports remote print, lpr
under FTPs TCP/IP, for example. You should read about the existing
possibilities in the documentation for the selected TCP/IP package.
You can have Navision generate a random file name by setting a * in

the Destination field in the printer driver. This name can be forwarded
to the remote print program. The name is forwarded using the %1
parameter as described in the following.
Setting Up a Client on a PC 21
25 Dok:
All
The remote print program is opened when you specify the following,
(for example), in the Spool Command field in the Navision window
under Design, Printers, Editor :
lpr -Sunixsrv -Pqueonunix %1
(where %1 stands for the file name which was specified in the Destination
field).
The figure below shows how the window looks:
Demo Company 3 Date 27-06-94 Time 15.48 Free 19% Mem. 512 Kb
General Help
˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝¸˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝»
” PRINTERS ” Editor ”
˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝¸˝˝˝˝˝˝˝˝˝˝˚˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝„
”GEN PostScript (7 b” ”
”HP LaserJet serie I” Comment.........: ”
”IBM Proprinter (all” Destination.....: \spool\navi.* ”
”IBM Proprinter (all” Download File...: ”
”IBM 23xx Matrix ” Spool Command...: lpr -Sunixsrv -Pqueonunix %1 ”
”IBM 23xx Matrix ” Forms...........: One ”
”IBM 40xx Laser HP-e” Number of Copies: ˜˜˜˜˜˜˜˜(w)˜˜˜˜˜˜˜˜¿ ”
Figure 3.2 ”IBM 40xx Laser HP-e” Form Height.....: 66 (h) ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿ ”
”IBM 40xx Laser PPDS” Form Width......: (w) (t) ‡ ‡ ‡ ”
Specifying the ”IBM 40xx Laser PPDS” Top Margin......: (t) ‡ ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜· ”
LPR command ”IBM 4072 ExecJet
”IBM 42xx Matrix
” Bottom Margin...:
” Left Margin.....:
(b)
(l)
‡ ‡
(h)‡
‡:::::::::::::::‡ ”
‡:::Printing::::‡ ”
”IBM 42xx Matrix ” Trailing Spaces.: ‡ ‡ ‡:::::Area::::::‡ ”
”IBM 4216-10 Page Pr” ‡ ‡ ‡:::::::::::::::‡ ”
”IBM 52xx Matrix ” ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿ ‡ ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜· ”
”IBM 52xx Matrix ” ‡ Character Table ‡ (b) ‡ ‡ ‡ ”
”NEC Pinwriter P2 ” ‡ Printer Codes ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜ ”
”NEC Pinwriter P2 ” ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜ (l) ”
¨˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˚˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝…
Insert
Here the file is placed in \spool, and is given the name navi.*, where
* is a randomly selected extension.
If the lpr command cannot use a flag to specify that the file should
be deleted after printout, this can be done via a .bat or .cmd file.
It is also a good idea to retrieve a .bat or .cmd file that checks whether
the file has been printed out correctly, or whether lpr returned an error
message. This can also be set up so the user will be asked whether the
system should try again, or whether the print job should be deleted.
Navision cannot receive error messages from the lpr command.
22 Setting Up a Client on a PC
26 Dok:
All
3.4 Setting Up the UNIX System as a Client

If a UNIX system will be used as a client for another UNIX system
(which functions as server), the following should be set up before running:
• Which hosts the UNIX system can make contact with

• Services (TCP/IP ports) which correspond to those specified on the
server
These things are described in the following section.
Specifying Hosts
The /etc/hosts file contains a list of which hosts a certain UNIX

system can come in contact with via the TCP/IP network. In order for
a Navision client to function on the UNIX system, a line such as this
must be added to all the client’s hosts tables:
x.x.x.x naviserv1
x.x.x.x stands for the server’s TCP/IP address. The host number is also
connected to the server number, as described in the serverno start
parameter on page 46.
Specifying Services
If changes have been made in the Navision server’s services file,

the same changes should be made for the client (all clients). If the changes
are not made, the client and server cannot connect with each other.
The changes are made in the /etc/services file, and specify which
TCP/IP ports are used for the various programs. A Navision server with
the number 1 uses port number 2407 as a standard, a server with the
number 2 uses 2408, server 3 uses 2409 etc. If the port to be used for
the server is busy (that is, the port number in the /etc/services file
is being used by another process) then the port number can be changed
by adding a new line to the /etc/services file, for example:
naviserv 3001/tcp
After this, server 1 has port number 3001, server 2 has port number
3002, server 3 has port number 3003, etc.
Setting Up the UNIX System as a Client 23
27 Dok:
All
3.5 TCP/IP Setup

When the selected TCP/IP package (see Appendix A on page 77 for
possible TCP/IP types) has been installed and runs as described in the
package documentation, you can:
• Test the TCP/IP connection

• Optimize the TCP/IP communication
This section concludes with an explanation of how TCP/IP error messages

should be read.
Testing a TCP/IP Connection
If a client/server installation does not function as expected, you can do

the following to locate the cause:
• Check whether there is a TCP/IP connection to the UNIX system.

This can be done with ping or telnet (see the TCP/IP package docum-
entation), for example. If the server’s host name is used, you should
check whether the hosts file is okay. If a client normally starts with
serverno=1, this can be done with ping by typing:
ping naviserv1
If there is no connection then you should look for the error in the
TCP/IP setup on the client or the server.
• If ping functions satisfactorily you can try Navision’s net test program.
Net test consists of a server portion and a client portion. A description
of use of the net test programs comes on the diskette. On the UNIX
system the program is started with netsrv. This also tests whether the
port number in the services file has been changed.
On the client, the networkx program is started (x is P, when running

OS/2, and R, when running DOS).
If everything is okay, the net test program will count the packets
which are sent, and do a performance measurement which can be used
to trim the TCP/IP setup. The net test should run for a while before
you can be sure that no packets disappear and no checksum errors occur.
If the net test can run without errors then Navision can also start
correctly.
24 TCP/IP Setup
28 Dok:
All
Optimizing TCP/IP Communication
When you run client/server it is very important to use the fastest

transport route between client and server. It is not enough that there are
good response times for the clients that do the heavy work, as a lock
on a "slow client" will also influence all others in the network.
Under TCP/IP, the drivers used and whether they are placed in extended
or expanded memory are very significant for performance.
Some TCP/IP packages can also place the running portion in EMS
(Expanded Memory Specification), which usually is slower.
It is easy to see the difference between different setups if you use

Navision net test programs (there is a description of the net test programs
on the diskette it comes on).
You must find the best balance between RAM usage and speed.
TCP/IP Error Messages
If TCP/IP sends error codes, these are displayed by Navision. Some of

these error messages are also displayed as a code.
Internal error: 244-XXXX
As each TCP/IP package has its own error codes, Navision does not
come with further explanations. But the code is explained in the manual
for the TCP/IP package. When the code is displayed by Navision, 1000
is added to the error code number. The error code in the example below
is number 51 in the TCP/IP package:
TCP/IP communication error.
Internal error: 244-1051
Contact your dealer for more information.
Press a key
TCP/IP Setup 25
29 Dok:
All
3.6 Setting Up UNIX as a Multiuser System

After installation Navision can be started on the UNIX system as a
multiuser installation. You can log on and start Navision by entering
navi and pressing [Enter]. In order for the installation to function as
well as possible you should first make sure the following exist:
• Automatic path to the Navision directory

• Write-protection of the program files
• Setup of the associated terminals
• Printer selections
These topics are described in this section.
Automatic Path to the Navision Directory
When Navision is installed with the naviinst command, the

/usr/bin/navi file is automatically filled in with information which
can then be used each time Navision is started from any directory. The
file is filled in with the following as a standard:
/xxxx/navi database=/xxxx/database,cache=400, \
temppath=/tmp/,id=$LOGNAME,$*
(Where xxxx is the directory where Navision is installed)
If you, for example, add commit cache and change the path to the
database, the /usr/bin/navi file should also be changed, for example:
/xxxx/navi database=/navibase/database,cache=400,commitcache=1000,\
temppath=/tmp/,id=$LOGNAME,$*
After this, each time Navision is started from any directory with the
navi command, you will gain access to /navibase/database and 1000
KB commit cache.
26 Setting Up UNIX as a Multiuser System
30 Dok:
All
Write-protecting the Program Files
If the database and the temporary files are placed outside of the directory
where Navision is installed, the files in the Navision directory can be
write-protected. When the Navision files are write-protected you cannot
delete the files by mistake. The commands for write-protection are the
following (xxxx here represents the selected Navision directory):
$ cd /xxxx
$ chmod u-w,g-w,o-w *
If the setup files <id>.zup, <id>.col, <id>.mon and <id>.cal (see

also the ID start parameter on page 43) are write-protected together with
the Navision files, an error can occur. This can be corrected by removing
the write-protection from these files or by changing the /usr/bin/navi
script to the following:
/xxxx/navi database=/navibase/database,cache=400,commitcache=1000,\
temppath=/tmp/,id=/xxxx/setup/$LOGNAME,$*
The setup files should then be placed in a directory called /xxxx/setup,

which should not be write-protected. The follow commands can set up
the necessary directory and set the rights correctly, if you are logged in
as root, and <user> is the user that owns the Navision program files.
$ mkdir /xxxx/setup
$ chown <user> /xxxx/setup
$ chmod 744 /xxxx/setup
Set up a special group for the users that should have access to Navision.
Later it is very easy to change this so it only gives access to the users
that are allowed to use Navision.
The following command is used to prevent other members of the group

from gaining access to Navision:
$ cd /xxxx
$ chmod o-x *
Setting Up UNIX as a Multiuser System 27
31 Dok:
All
3.7 Setting Up Terminals

Navision can use the terminals mentioned in the readme-files that comes
with the Navision-server package.
What you should notice is, that if a terminal does not use scan codes,
the keyboard will function somewhat differently for Navision than
otherwise:
[Esc] is activated by pressing [Esc] twice. If it is only

pressed once this is understood to be the start of a
control code.
[F1] - [F10] If there are no function keys, or if there are no functions

associated with them, then the Navision functions are
activated when you press [Esc] and a number from 1-10
(to get 10 press 0), for example: [Esc]+[0] gives [F10],
[Esc]+[1] gives [F1], [Esc]+[2] gives [F2] etc.
The pull-down Navision’s pull-down menu is activated with [Esc] [0]

menu followed by the letter for the function. A total table of
which key combinations correspond to which functions on
the relevant terminal can be found under Navision’s -
GENERAL, KEYBOARD LAYOUT pull-down menu option, which
can look like this:
[F1]=Hjlp [Alt]=Pulldown-menu Dato 17-05-94 Tid 10.18.08 DB 38% 0 Kb

Generelt Hjlp
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿˜˜˜˜˜˜˜˜¿
ˆ˜˜˜˜˜‡ Esc Esc Esc ‡˜˜˜·
ˆ˜˜˜˜‡ F1 Esc 1 ‡˜˜˜˜˜·
ˆ˜˜˜‡ F2 Esc 2 ‡˜˜˜˜˜·
ˆ˜˜˜‡ F3 Esc 3 ‡˜˜˜·
ˆ˜˜˜˜‡ F4 Esc 4 ‡˜˜˜˜˜·
ˆ˜˜˜˜˜‡ F5 Esc 5 ‡˜˜˜˜˜·
ˆ˜˜˜˜˜‡ F6 Esc 6 ‡˜˜˜˜˜·
‡ Versio‡ F7 Esc 7 ‡04 DEMO ‡
Figure 3.3 ˜˜˜˜˜˜˜‡ F8 Esc 8 ‡˜˜˜˜˜˜˜˜
A keyboard ‡ F9 Esc 9 ‡
‡ F10 Esc 0 ‡
table Reg‡ Shf+F1 Esc s 1 ‡
Lav‡ Shf+F2 Esc s 2 ‡
Ind‡ Shf+F3 Esc s 3 ‡
‡ Shf+F4 Esc s 4 ‡
Bru‡ Shf+F5 Esc s 5 ‡(PCC)
Des‡ Shf+F6 Esc s 6 ‡
Ops‡ Shf+F7 Esc s 7 ‡
Dat‡ Shf+F8 Esc s 8 ‡
‡ Shf+F9 Esc s 9 ‡
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
Indst
28 Setting Up Terminals
32 Dok:
All
Printer Selections
When Navision is used locally on a UNIX system with NAVITERM

or a terminal, there is only access to printers on the UNIX system. From
these the print can be redirected to a DOS or OS/2 LAN server or to
a terminal server with printers connected.
All printouts should be sent to the UNIX spool system. This is done by
changing the setup of the printer drivers in Navision, so printing is
done to a file. After this a normal UNIX print command can be used
to have the file sent on to the UNIX spool system.
You can have Navision generate a random file name by setting a * in

the Destination field in the printer driver. This name can be forwarded
to the UNIX print command. The name is forwarded with the help of
the %1 parameter as described below. The UNIX print command is
retrieved when you specify the following (for example) in the Spool
Command file in the Navision window under Design, Printer, Editor:
qprt -Pprintname -dp -r %1
(where %1 stands for the file name specified in the Destination file).
The figure here shows how the window appears:
Demo Company 3 Date 27-06-94 Time 15.48 Free 19% Mem. 512 Kb
General Help
˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝¸˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝»
” PRINTERS ” Editor ”
˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝¸˝˝˝˝˝˝˝˝˝˝˚˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝„
”GEN PostScript (7 b” ”
”HP LaserJet serie I” Comment.........: ”
”IBM Proprinter (all” Destination.....: /tmp/ ”
”IBM Proprinter (all” Download File...: ”
”IBM 23xx Matrix ” Spool Command...: qprt -pprintname -dp -r % ”
”IBM 23xx Matrix ” Forms...........: One ”
Figure 3.4 ”IBM 40xx Laser HP-e” Number of Copies: ˜˜˜˜˜˜˜˜(w)˜˜˜˜˜˜˜˜¿ ”
Filling out ”IBM 40xx Laser HP-e” Form Height.....: 66 (h) ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿ ”
”IBM 40xx Laser PPDS” Form Width......: (w) (t) ‡ ‡ ‡ ”
the printer ”IBM 40xx Laser PPDS” Top Margin......: (t) ‡ ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜· ”
driver ”IBM 4072 ExecJet
”IBM 42xx Matrix
” Bottom Margin...:
” Left Margin.....:
(b)
(l)
‡ ‡
(h)‡
‡:::::::::::::::‡ ”
‡:::Printing::::‡ ”
”IBM 42xx Matrix ” Trailing Spaces.: ‡ ‡ ‡:::::Area::::::‡ ”
”IBM 4216-10 Page Pr” ‡ ‡ ‡:::::::::::::::‡ ”
”IBM 52xx Matrix ” ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿ ‡ ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜· ”
”IBM 52xx Matrix ” ‡ Character Table ‡ (b) ‡ ‡ ‡ ”
”NEC Pinwriter P2 ” ‡ Printer Codes ‡ ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜ ”
”NEC Pinwriter P2 ” ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜ (l) ”
¨˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˚˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝…
Insert
The print file is deleted when it is printed out because of the -r flag.
It is important that the UNIX spool system sends the printout to the
printer without changing the contents, as Navision sends all the necessary
commands to the printer itself.
Setting Up Terminals 29
33 Dok:
All
30 Setting Up Terminals
34 Dok:
All
CHAPTER 4
STARTING NAVISION UNDER UNIX
This chapter describes how to start Navision. The sections describe:
• Starting Navision client/server
• Starting a terminal/terminal emulation
• Navision start parameters
35 Dok:
All
4.1 Starting Navision Client/Server

This section describes how to start Navision in client/server installations.
Starting a Navision Database Server
When starting a Navision database server on a UNIX system you should

be aware of the following:
• If changes should be made in the /etc/hosts and /etc/services

files, this should be done before the server is started (as described on
page 16).
• The Navision start parameters, tasks, autostart and stoptime,

which are used under DOS and OS/2, are not relevant under UNIX.
The database server can be started manually or automatically using a

start script. The first time you start Navision this should be done
manually, so any parameters can be adjusted (Navision’s parameters
are described starting on page 37).
Manual start The server is started manually as follows:
1) Log in on the console.
2) Switch to the directory where Navision is installed, for example:

cd /navi
3) Type the start command (and associated parameters):

./server serverno=1,database=database,cache=8000,commitcache=1500
Now Navision server number 1 starts, and the following is displayed:
Starting database server number 1 ...

Cache(Kb)...........: 8000
CommitCache(Kb).....: 1500
Sessions............: 250
Maximum users.......: 50
Maximum database(Mb): 500
Database server successfully started.
Press [Ctrl-C] to shut down the server.
32 Starting NAVISION Client/Server
36 Dok:
All
Automatic start Once you have tested that the server functions correctly, then it can be
configured so it starts automatically at the same time as the system.
This is done by placing the start command in the start script.
There are many different ways of starting the server. An example is

shown below which creates a log (server.log) which registers the date,
process number and startup screen from the server program. The log
inserts information in the file each time the server is started. It is assumed
that Navision is installed in the /navi directory, and that the log file
is placed in the same area on the system.
In the /etc/inittab file the following line is inserted:
..
..
..
..
Naviserv:2:once:/xxxx/autostart >>/xxxx/server.log
The autostart file, which is in the /xxxx directory, (navi, for

example) can look like this:
#!/bin/ksh
echo
"****************************************************************"
date
echo
echo " Starting NAVISION server "
/naviprog/server serverno=1,database=/navibase/database,\
cache=8000,commitcache=1000,>>/naviprog/server.log </dev/null &
echo " Process number = " $!
echo
"***************************************************************"
Starting NAVISION Client/Server 33
37 Dok:
All
Here is an example of the output that will be generated in the

server.log file:
*******************************************************************
Mon Nov 06 15:58:08 1995
Starting Navision server
Process number = 4951
*******************************************************************
Starting NAVI server number 1 ...
Cache(KB)...........: 8000
CommitCache(KB).....: 1000
Sessions............: 250
Maximum users.......: 50
Maximum database(Mb): 500
NAVI server successfully started.
Press [Ctrl-C] to shut down the server.

The NAVI server was successfully shut down.
Starting a Navision client under DOS and OS/2
First, the Navision server must be started on the UNIX system. Next,
TCP/IP should be started as described in the TCP/IP package manual.
Once communication with the server has been established (can be tested
with ping), the client can be started with PC/TCP, for example, from
ftp:
navi(2) serverno=1, nettype=TCPF
If everything is installed correctly, then Navision will start. You can

ensure that it is the UNIX server which you have made contact with and
not a local database using Navision’s start menu under the Database
menu option. Check that the path to the database has the UNIX syntax
[/] (slash) instead of [\] (backslash).
34 Starting NAVISION Client/Server
38 Dok:
All
If you have made contact with a database under UNIX, then the path
should look like this:
/navibase/database
in contrast to under DOS or OS/2, where the path looks like this:
d:\navibase\database
In order to start Navision as a client you should specify which type of

TCP/IP protocol is used. This is done with the Navision nettype start
parameter, as shown in the examples below:
navi serverno=1, nettype=tcpf (under DOS)

navi2 serverno=1, nettype=tcpf (under OS/2)
Both lines start Navision as a client for server number 1. The network
type used here is TCP/IP from FTP Software (Appendix A on page 77
shows what to specify for the other possible TCP/IP types). If a
communication protocol is not specified then Navision under DOS and
OS/2 will select NetBIOS as a standard.
Attention! A client under DOS cannot be started with DOS extender

(navi2), as this is not supported by TCP/IP.
Starting Navision on a UNIX System which is a Client
Before a UNIX client (Navision from another UNIX system) is started,

the changes that were made in the server’s /etc/hosts and
/etc/services files (see page 16) must also be made for the UNIX
client, as Navision otherwise will not be able to find the server. Navision
is started as a client for server number 1 with the command:
$ navi serverno=1
If there will be individual user setups, Navision should also be started

with the id=<id> parameter (see page 43). Navision saves the setup
in the <id>.zup, <id>.col, <id>.cal and <id>.mon files. If the
client always uses server number 1, this can be inserted in the
/usr/bin/navi script.
Starting NAVISION Client/Server 35
39 Dok:
All
4.2 Starting a Terminal or Terminal Emulation

Navision must be started on the UNIX system if you want to be able
to use Navision directly from the UNIX system, a terminal, or a PC
with terminal emulation.
This can be done with the navi script, which can be found in the
/usr/bin directory. The script contains the necessary values for the
start parameters, so you don’t have to enter these each time you start
Navision. The script also ensures that all users have their own setup
files with filters, colors, etc. The setup files use about 100 KB per user.
Once the terminal has been turned on and contact with the UNIX system
is established, Navision starts from the terminal when you type the
following command:
navi
Information on Navision’s terminal emulator, NAVITERM, can be found

in chapter 5 on page 49.
36 Starting a Terminal or Terminal Emulation
40 Dok:
All
4.3 Navision Setup with Start Parameters

A few of the Navision start parameters that appear in the parameter
window that appears on the screen when you start with navi ? are
specially intended for use under DOS and OS/2. These are: sessions,
tasks, autostart and stoptime.
All the other parameters can be used under UNIX. These are described
in this section in alphabetical order. The list below contains a quick
overview of the parameters that can be used, and what they can be used
for:
cache better usage of the disk
commitcache faster screen updates
database selecting a database
dbgroup the instance of the database management system to use
dbreadonly starting with readonly rights
dbtest testing the database
debug access to the debugger in Navision’s development

system
id saving a user-specific setup
keyboxpath starting with an alternative license file
local starting with a local database
macro starting by playing a macro
nettype specification of network type
serialno starting with another serial number
serverno the number of the server being used
temppath placement of temporary files
NAVISION Setup with Start Parameters 37
41 Dok:
All
cache
To use the disk as effectively as possible you can use this parameter to
specify that a database cache should be created in the RAM. The database
cache can be between 400 KB and 32 MB, and the size is specified with
this parameter. The database cache has the following functions:
• When data is processed by the CPU it is temporarily placed in the

database cache. When the current transaction is correctly completed,
the data is transferred to the commit cache, which sends the data to
the hard disk. When new data is stored in the database cache, Navision
is freed more quickly for further work.
• Navision saves a copy of all processed data in the database cache.

When it will be used later it can be retrieved from the database cache
faster than if it had to be found on the disk.
The RAM is used, like the disk, to store data, but only temporarily.
When the database cache is filled up, the oldest data is modified by
new data, and when the UNIX system is shut down, the data in the RAM
is deleted. All data in the database cache is already on the hard disk,
so there is no risk in using the database cache. On the other hand, there
is the advantage that the data can be retrieved quickly, so the work can
be continued without you having to wait for the disk.
As the database cache is very important for Navision’s performance, it

should be set as high as possible. But you should be aware that if the
cache is set too high in relation to the available RAM, UNIX will start
swapping on the disk, and the system’s performance will greatly decline.
38 NAVISION Setup with Start Parameters
42 Dok:
All
commitcache
With this parameter you specify how large a "write cache" you want to
have. Attention! Commit cache does not have anything to do with the
cache parameter (database cache), so this should always be set.
When you use "write cache", write transactions are completed as soon
as the data is in the RAM, but before it is physically written on the disk.
This results in faster screen updates, which are especially important in
larger networks. The write transactions remain in the commit cache until:
• there are no other activities on the physical disk, or

• 30 seconds have gone by since the write transaction took place, and
the disk has been constantly occupied by other jobs, or until
• the commit cache is filled up.
If just one of these conditions is met, the write transaction is transferred

as soon as possible from the commit cache to the physical disk.
Since the write transactions are done in the RAM, the database will be
consistent, but in the event of a system crash (power failure or problem
with connection to the server) the last ’whole’ transactions can be missing
from the database (half transactions cannot be missing). You should
therefore check that all transactions have been included.
As an extra security measure against breakdown you could consider

inserting an extra power supply, a UPS (Uninterruptable Power Supply)
on the database server. A UPS generally contains sufficient battery
capacity to maintain operation of the server. The more advanced UPS
models also have facilities that allow you to exit your program properly
before the batteries are used up.
In order to achieve the best performance it is important to make the

commit cache large enough. On the other hand it should not be too big,
because excess commit cache is not used.
When you use commit cache, Navision can write to several physical
disks at the same time, and thus increase the write capacity. This is
possible if Navision’s database is divided into several smaller database
files, which are then each placed on their own disks on the UNIX system.
On UNIX systems with HP-UX and IBM-AIX, where you can have
several physical disks linked to a virtual disk, it is important that each
physical disk has it’s own file system, and that one common file system
is not used by several disks. If a large database file is placed on a virtual
disk that consists of several physical disks, Navision considers it to be
one disk, and only one write transaction can take place at a time.
43 Dok:
All
For the same reasion, Navision’s performance is better if several small

disks are installed than if there is one large disk on the UNIX system.
We recommend that you use a commit cache of 3 MB for each disk on

which the database is placed. This figure is calculated based on the
maximum number of write transactions that can be completed in the
process of 30 seconds on the fastest disk on the market.
The commit cache automatically divides the resources between the disks
on which the database files are placed. Here are some examples of how
the resources can be divided:
Example 1. One File
The database is in one file: /base1/database. In this case a commit

cache of 3 MB should be specified.
Example 2. Two Files
The database is divided into two files, which are each on their own
physical disk: /base1/database and /base2/database. In this case
a commit cache of 6 MB should be specified, because the files are each
on their own physical disk.
Example 3. Three Files on Two Disks
The database is divided into three files on two physical disks: /base1/-
database1, /base1/database2 and /base2/database. In this case
a commit cache of 6 MB should also be specified, because database1
and database2 are on the same physical disk.
Example 4. Three Files on Three Disks
The database here is divided into three files on three physical disks:
/base1/database, /base2/database and /base3/database. In this
case a commit cache of 9 MB should be specified, because the files are
each on their own physical disk.
A maximum of 32 MB commit cache can be specified. You turn off the

commit cache by setting the parameter to 0. The current size of the
commit cache can be seen in the Navision start menu under Database
in the Commit Cache (Kb) field.
44 Dok:
All
database
Use this parameter to select the database you want to work with. The
same information can be specified from the Database, Select Database
menu option on the start menu. Navision normally saves and reuses
the information the next time the program is started, but on the database
server the parameter should be specified each time the program is started.
To avoid having Navision’s database modified (if you install Navision

once more in the same directory, for example), the database should be
copied to a special directory. The rights to the database file should be
set with the following commands:
$ cp /xxxx/database /navibase/database
$ cd /navibase
$ chown <user> database
$ chmod u=rw,g=rw database
<user> should be the one with which Navision was installed.
Placement of the database and thus the disk configuration has great
significance for Navision’s performance. When the program works,
many smaller read and write transactions are completed various places
in the database files. Thus it is more important that there is fast access
to the data (access time), than a large throughput.
When Navision writes to the disk, a maximum of 300-400 KB/sec. are

always transferred, so it is not so important whether a disk can write
8 or 10 MB per second.
If commit cache is used, Navision can write to several physical disks

simultaneously, and thus increase the write capacity. This can be done
if Navision’s database is divided into several smaller database files,
which will then be placed each on their own disk on the UNIX system.
On UNIX systems with HP-UX and IBM-AIX where you can have several
physical disks linked together to a virtual disk, it is important that each
physical disk has its own file system, and that a common file system
is not used for several disks. If a large database file is placed on a virtual
disk which consists of several physical disks, Navision considers it to
be one disk, and only one write transaction can take place at a time.
For the same reason, Navision’s performance is better if several small

disks are installed than if there is one large disk on the UNIX system.
45 Dok:
All
There are different disk subsystems for the various platforms, and these
have varying influence on Navision’s performance. The same rules exist
for selection of a disk subsystem as for selection of a disk: The systems
where Navision has write-access to several disks at the same time
generally have a better performance than the systems where many
physical disks appear as one disk for the UNIX operating system (RAID
systems, for example). An example of a suitable system is IBM’s disk
subsystem 9333, which has a "canal" directly to each disk.
dbgroup
If Navision is started with DBGROUP=<dbgroup> (where <dbgroup>

is an integer between 0 and 1000), multiple DBMSs can be run
simultaneously by specifying different <dbgroup> parameters. The
DBGROUP parameter is only relevant when starting servers or Navision
in local mode. If you connect a client to a server, the server decides the
<dbgroup>. The default value is DBGROUP=0.
dbreadonly
If this parameter is specified, Navision is only started with read rights

to the database. So it is not possible to change company data if the
program was started with this parameter. The parameter can be used
if problems arise in the database, and it is necessary to see the data
without changing anything.
The parameter is also used to start a database which, for some reason
will not accept write transactions. After this it will be possible to make
a Navision backup, import it into another database, and thus gain access
to the data.
dbtest
This parameter can be used to test the database’s readability. The test
can be completed with two values:
min - tests that all data can be read and understood by Navision.
max - tests whether all data fits together. This can take a very long time,
but depends on the size of the database.
46 Dok:
All
The test can be used, for example, before making a backup, especially
if Navision’s own facilities for making backups are not used.
If dbtest will be performed on a database server, it should first be shut

down and then started as a single user.
debug
If this parameter is specified, the development system’s debugger can

be used. This parameter is only significant for users of the development
system (including the Report Writer, for example).
id
This parameter is used to save information about setup of colors,

keyboard selection, monitor type, and database cache under the id name
you specify when starting Navision (the id parameter has nothing to
do with user ID, but you can use the same name).
If this parameter is not specified, the following message can appear on

the screen when you log off the system:
Demo Company Date 01-02-94 Time 09.00 Free 36% Mem. 350 Kb
General Help
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ NAVISION saves your current position, filters, request information,‡
‡ and so on, each time you exit. This information is saved to the ‡
‡ setup file used when starting NAVISION. ‡
‡ ‡
‡ Currently, the same setup file is being used by... ‡
‡ ‡
‡ * Several users on the network, or ‡
Figure 4.1 ‡ * Several NAVISION sessions on this system ‡
Multiple sessions ‡ ‡
‡ Do you want to replace the setup file? Yes ‡
are started with ‡ ‡
the same id ‡ ‡
‡ To avoid this conflict, start each NAVISION session with a unique ‡
‡ setup ID. For example... ‡
‡ ‡
‡ NAVI ID=BILL ‡
‡ NAVI ID=C:\NAVI\MIKE ‡
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
The id is specified after the start command as here:
navi id=peter
47 Dok:
All
If Peter shuts the program down and starts it again afterwards, he does
not have to specify the id again. Navision remembers the id last used.
Under Setup on the start menu you can see which id is currently being
used. If the program is not started with a special id, then navi will
appear.
The information to be connected to the id is saved as standard in four

files in the directory where Navision is placed. If you start with id=peter
the following files will be created:
• peter.col with information on color selections

• peter.zup with parameters for the start command, database cache,
for example
• peter.mon if a monochrome monitor is used
• peter.cal with the contents of Peter’s calendar in Navision
All files are based on Navision’s standard setup.
In the /usr/bin/navi script the user name is set automatically at

id=$LOGNAME, so all users have their own versions of the setup files
(usr/bin/navi is also described on page 26).
If you have chosen to write-protect the directory with Navision’s program

files, the id-files should be placed somewhere else, as it must always
be possible to update them. When you start Navision with an id, you
should specify the whole path to where the id file can be found. If you
have created a special directory, NAVIZUP, for example, type:
navi id=/navizup/peter
If you, at some point, want to cancel the color changes, you can return
to the standard setup for colors by copying the standard color file on
top of the existing color file. If, for example, Peter’s color setup should
be changed in this way, he should type from a command line:
cp navi.col peter.col and press [Enter]
The next time Navision is started with id=peter, the standard setup
will be valid.
48 Dok:
All
keyboxpath
Using this parameter it is possible to start the program with another

license file than the one that comes with the program. Type keybo-
xpath=<directory> on the command line when Navision is started.
For example: navi keyboxpath=/devkey. This parameter also makes
it possible to have your license file placed centrally, which is an
advantage in connection with both maintenance and security measures.
local
On a system in a network you can use this parameter to specify that you
will work with a local database.
macro
If you want to play a macro as soon as the program is started, you should
specify the name of the macro as the value for this start parameter. You
can read how to create and use macros in Introduction to Navision.
nettype
If you want to have Navision clients under DOS and OS/2 connected
to a UNIX database server, the network protocol TCP/IP should be
installed on the PCs where it will be used. When Navision is started
you should use the nettype start parameter to specify which TCP/IP
program is used to communicate with the database server.
Nettype=xxxx specifies which dll/ddl module should be used. The

possible types can be seen in Appendix A on page 77.
If you want to start Navision with IBM TCP/IP under OS/2, for example,
type: navi2 serverno=1,nettype=TCPI
Attention! Database servers under DOS and OS/2 cannot use other
network types than NetBIOS. Workstations under UNIX cannot, for
example, use a database server with DOS or OS/2.
49 Dok:
All
serialno
With this start parameter a Navision dealer can hook up to a workstation

on your system - and use his own license file. This can be useful, for
example, if modifications should be made that require AL rights. The
Navision dealer uses the keyboxpath and serialno=xxx start
parameters (where xxx is the serial number of your license).
serverno
The serverno parameter is used when there are several database servers
in a network. The parameter specifies wich server to use.
If there are several database servers in the network, they should each
be started with a number from 1 - 9. Each time Navision is started in
the network, it should be specified with a number for the database
server to be used. If there is only one database server in the network,
a server number should only be specified if you have given the server
a number other than 1. Otherwise Navision automatically assumes that
number 1 will be used.
serverno also specifies which TCP/IP address and which TCP port
number is used. The port number is increased according to the server
number:
serverno=1 gets the standard port number

serverno=2 gets the standard port number+1
The standard port number is 2407, so if the server number is 3, the port
number will be 2409. The standard port number can be changed in the
services file as described on page 16.
On clients the parameter determines which TCP/IP host name is used

and thus the TCP/IP address of the UNIX server, for example:
serverno=1 host name=naviserv1

50 Dok:
All
TCP/IP uses the hosts file (see page 20) to find the corresponding
address. Below is an example of a hosts file:
..
..
1.2.3.4 naviserv1 #comment
If a session is then started with navi serverno=1, the client will attempt
to contact the Navision server which has the TCP/IP address 1.2.3.4.
temppath
A Navision session uses a number of temporary files, and especially

when the UNIX system is used as a multiuser system, many of these
are generated. It is therefore a good idea to place the temporary files
in another directory than Navision’s program files, as:
1) The Navision directory will be easier to look through.
2) You can delete the temporary files without endangering the program
files.
3) The program runs faster if it is placed on a virtual disk (if this is

possible on the UNIX system being used). This requires that a virtual
disk be created in the RAM.
The temporary files are placed as a standard in the /tmp, directory, which
is determined in the /usr/bin/navi file, but the placement can be
changed with the temppath start parameter.
51 Dok:
All
52 Dok:
All
CHAPTER 5
TERMINAL EMULATION WITH NAVITERM
This chapter describes the Navision terminal emulator: NAVITERM. The following
topics are described:
• What is NAVITERM?
• Equipment requirements
• Installing NAVITERM
• Starting NAVITERM
• The NAVITERM menu
• Remote control of NAVITERM
• Testing and troubleshooting
53 Dok:
All
5.1 About NAVITERM

NAVITERM is a terminal emulator which is specially developed for use
with Navision. It has the precise characteristics (256 colors, keyboard
with scan codes, full 8 bit character set, etc.) necessary to run Navision
in a terminal environment and gives the same appearance and usability
as in the PC version of Navision.
To make it possible for other UNIX programs to be able to use

NAVITERM, a terminfo file comes with Navision. In other words, in
an installation with NAVITERM you can also run various UNIX
programs that use terminfo. Update of the terminfo environment takes
place automatically when Navision is installed with the naviinst
script.
NAVITERM has a little menu installed which appears on the screen when
you hold the two [shift] keys down at the same time. The menu is used
to start new sessions in NAVITERM. But there are several other functions,
depending on which version of NAVITERM and which start parameters
are used.
NAVITERM comes in 2 versions:
• The DOS and OS/2 version (NT.EXE and NT2.EXE), which commu-
nicates with the UNIX system via TCP/IP and the network.
• The DOS version (NT_COM.EXE) using serial RS-232 communication.
50 About NAVITERM
54 Dok:
All
5.2 Equipment Requirements

NAVITERM can run on all PC-compatible systems with a CGA, EGA,
VGA or better monitor. NAVITERM requires about 250 KB free memory
and space for any TCP/IP packages that should be started.
A TCP/IP package does not come with NAVITERM, but you can use
the TCP/IP packages that are described in Appendix A on page 77.
The serial version of NAVITERM should have access to a serial port

(COM1 or COM2), and the PC should be connected to the UNIX system
with a serial cable, which is crossed (see the section on cables on page
58). NAVITERM uses the following RS-232 pins:
OUT2 (TD) Transmit data.
IN3 (RD) Receive data.
---7 (S.GND) Signal ground.
IN8 (DCD) Data carrier detect. Should be high to make it possible to

start NAVITERM. If this pin is not set high then
NAVITERM will shut down.
OUT20 (DTR) Data terminal ready. This is always high when NAVITERM
is started. If hardware handshaking is used, then the pin
below is also used.
OUT4 (RTS) Request to send. This is high as long as NAVITERM is

able to receive data. When NAVITERM’s receive buffer
is full, the pin is set low.
IN5 (CTS) Clear to send. NAVITERM sends data as long as CTS is

high. If the UNIX system sets CTS low, NAVITERM stops
sending data. These are instead collected in an internal
send buffer.
Equipment Requirements 51
55 Dok:
All
5.3 Installing NAVITERM

Create a directory for NAVITERM on the PC, for example:
c:\naviterm
switch to this directory, and copy all files from the NAVITERM diskette.
It is possible to select which language NAVITERM should use to display

messages (this is not valid for the actual Navision program). This is
done by copying the file:
NT_XX.STX -> NT.STX
(XX is the code to the relevant language, DK for Danish, for example).
The TERM To let Navision and other programs know which terminal is used, the
environment TERM environment variable on the UNIX system is set correctly:
variable
• In the serial version of NAVITERM, the UNIX system should be
configured so that TERM is set to naviterm on all serial ports that use
NAVITERM.
• When the TCP/IP version of NAVITERM is used, NAVITERM reports

the following values of the TERM environment variable, if TERM is
not changed in the UNIX user setup:
Value When screen resolution is
naviterm 25x80
naviterm43 43x80
naviterm50 50x80
Installing Terminfo
If Navision is not already installed, or if you want to use a newer

version of the naviterm.ti file, it must be transferred to the UNIX
system. To be able to use other UNIX programs that use terminfo,
together with NAVITERM, naviterm.ti must be compiled to terminfo
on the UNIX system. This can be done with the ftp TCP/IP command
or directly from the diskette, if there is a diskette drive in the UNIX
system. The naviterm.ti file should then be translated with the tic
UNIX command, for example: tic naviterm.ti.
52 Installing NAVITERM
56 Dok:
All
5.4 Starting NAVITERM

This section describes how to start NAVITERM with TCP/IP and serially:
Starting NAVITERM with TCP/IP
Before starting NAVITERM the TCP/IP program must be installed and

started. NAVITERM can be started without parameters, but it is normally
necessary to specify host name, login name, communication module etc.,
for example:
NT2 -hnaviserv1 -luser1 -ntcpf
Start The parameters are specified just after the start command as shown below.
Parameters The order is unimportant, but the parameters should be divided by a blank:
nt[2] [-F] [-t] [-h{host-name}] [-l{login-name}] [-o]

[-O{Out device}] [-p] [-f{+/-}] [-n{nettype}]
-F Fast. This parameter allows for a quick start of NAVITERM

without a start screen, and without waiting for a key to be pressed.
-t Telnet. This parameter selects the telnet port (standard er Rlogin).
-h Host name. NAVITERM uses host name to find the TCP/IP

address in the Hosts file (see also page 20).
-l Login name. If Rlogin has been selected, use this login name.
-o Operating System. Activates the Operating System menu option

in the NAVITERM menu, which starts a command.com, and
switches temporarily to the operating system.
-O Output. The printer port or file which should be used on printout

or file transfer.
-p Print. Enables printing.
-f+- Flicker. Lets you toggle whether your displays will be updated
quickly. Use + if you get ’snow’ on your display. You only need
to do so if the snow annoys you (some prefer the snowy screen
because it updates faster).
Starting NAVITERM 53
57 Dok:
All
-n Nettype. Specifies communication module (nc_xxxx.dxl) for

the TCP/IP package used. nt2 -ntcpi starts NAVITERM with
the nc_tcpi.dll communication module, which is used with IBM
TCP/IP for OS/2. There is a list of these network types in Appendix
A on page 77.
Starting Serial NAVITERM
Before the serial version of NAVITERM can be started, a COM port

on the PC should be connected to the UNIX system, and you should
be familiar with the UNIX system’s communication parameters
(baudrate, paritet, etc.).
If you type nt_com -S9600, for example, NAVITERM will be started

with a communication speed of up to 9600 bits/sec. The other parameters
com1, 8bit, 1stop, noparity, xon/xoff, are standard.
Start The start parameters should be specified just after the start command as
Parameters outlined below. The order is optional, but the parameters must be divided
by blanks:
nt_com [-F] [-o] [-O{Out device}] [-p] [-f{+/-}]

[-L{com port}] [-S{baudrate}] [-P{parity}]
[-s{stop bits}] [-B{bits/char}] [-h] [-d]
[-X{com port},{port address (Hex)},{irq (Dec)}]
[-C{cfg id}] [-M{string}]
-F Fast. This parameter means quick start of NAVITERM without a

start window, and without waiting for a key to be pressed.
-o Operating System. Activates the Operating System menu option

on the NAVITERM menu, which starts a command.com and switches
temporarily to the operating system.
-O Output. The printer port or file to be used on printout or file

transfer.
-p Print. Enables printing.
-f Flicker. Lets you toggle whether your displays will be updated

quickly. Use + if you get ’snow’ on your display. You only need to
do so if the snow annoys you (some prefer the snowy screen because
it updates faster).
-L Com port ID. Indicates which RS232 communication port that should
be used. 1=COM1, 2=COM2, 3=COM3, 4=COM4 (standard is 1).
54 Starting NAVITERM
58 Dok:
All
-S Baudrate. Used to specify the speed to be used on the communication

port. You can specify from 110-38400 (standard is 38400).
-P Parity. Used to specify which parity should be used for

communication. The options are: e(ven), o(dd) or n(o) (standard is
no).
-s Stop bits. Used to specify how many stop bits should be used
for communication. The options are 1 or 2 (standard is 1).
-B Bits per character. Used to specify how many bits there should
be per character. The options are 5-8, and 8 is the standard suggested.
-h Handshaking. Activates hardware handshaking (the standard suggested

is XON/XOFF).
-d DCD. Do not disconnect on DCD (Data Carrier Detect) low.
-X Com port ID. Used to configure a com port to a setup different

from the default. The default values are:
COM IO addr. IRQ

1 3F8 4
2 2F8 3
3 3E8 4
4 2E8 3
port is the COM port (in decimal), io addr is the address (in
hexadecimal) and irq is the IRQ (2-15). On a MCA bus, the IRQ
can be a shared IRQ (level triggered interrupt).
-C Configuration file. Instructs NAVITERM to read parameters

from a text file. In this way you have different configurations available
in separate files. In the file, the options are entered exactly as on the
command line, for example:
-L3 -X3,3220,3 -S9600 -MAZ=!AD123456

or
-L4 -X4,3228,3,-S2400
By using -C in the configuration file, configuration files can ne nested

(you can nest files up to a depth of five levels).
59 Dok:
All
-M Modem command. Used to transmit a modem command, for example

-MAZ=!AD123456. The reply will be displayed, but replies are not
handled any further. If you specify -M more than once, only the last
string will be transmitted. The ^ character has these special meanings:
^<capital letter> Ctrl-capital letter

^^ literal ^ character
^s space character
^<0..9> delay in seconds
^<any other character> the ^ character is discarded
Handshaking - Controlling Data Transfer
A handshake controls data transfer between NAVITERM and the UNIX

system, and ensures that NAVITERM is not "overrun" if the UNIX
system sends data too quickly.
When installing the serial version of NAVITERM it is important that

the handshake is set up correctly, as the windows and printouts will
otherwise drop characters and look wrong. The Communication status
option on the NAVITERM menu then displays buffer overflow. Controlling
handshaking is described in the section Testing and Troubleshooting
on page 70.
Data for NAVITERM is gathered in a receive buffer until NAVITERM

has time to interpret and display it on the screen. If the receive buffer
is about to be full, NAVITERM has to signal to the UNIX system that
it should stop sending data. Once NAVITERM has emptied a portion
of its receive buffer it signals to the UNIX system that it is alright to
send more data. The same is valid for data sent from NAVITERM to
the UNIX system. But it is seldom that typing is done so quickly that
the UNIX system cannot receive the data entered.
NAVITERM can use two different types of handshake: hardware

handshake and XON/XOFF. As a standard, XON/XOFF is suggested.
60 Dok:
All
XON/XOFF An XON/XOFF handshake uses characters sent as ordinary data to tell

the sender that:
• it should stop its data transmission (XOFF).

• the data transmission can be continued (XON).
The advantage of XON/XOFF handshaking is that it uses data wires. This

means that a very simple cable can be used between PCs with
NAVITERM and the UNIX system. The most simple form only needs
three wires. This can be significant if you use a cable installation with
very few wires available, such as IBM’s PDS cable system, or a simple
RS232 installation in the wall.
The disadvantage of XON/XOFF is that it gives a certain delay in sending

characters as handshake signals, as a minimum of 8 bit must be sent
before the sender has received the message to stop its transmission.
The system that receives the XOFF character must also first recognize
it in order to react. This can be a problem on certain UNIX systems,
if they are heavily compromised.
Hardware A hardware handshake uses RS232 signals. That is, some pins are used
handshake in the serial connector to signal with. When NAVITERM is ready to
receive data, the RTS(4) pin is high. If NAVITERM’s receive buffer
is about to be full, then RTS(4) is set low. The opposite is valid with
the pin CTS(5). If the UNIX system sets CTS(5) low, NAVITERM
will stop sending data from the keyboard, and keying will be saved in
a send buffer until the UNIX system sets CTS(5) high again.
The advantage of a hardware handshake is that it reacts faster, as data

does not have to be sent first. This can also be significant on PCs with
a slow CPU, because a hardware handshake does not need to be
interpreted first by NAVITERM, but works directly on hardware. To run
NAVITERM correctly under Windows it is a prerequisite on most PCs
that hardware handshake is used.
The disadvantage is that more wires are required in the serial cable to
run a hardware handshake, and it can be more difficult to get
communication set up so the handshake functions correctly. It can also
be difficult to have the right cable made if you want to use a serial
multiplexer, as they use different pins for handshaking.
61 Dok:
All
Cables
As there is no standard for use of the various pins in PCs and various
UNIX systems, the following instructions for cables are only intended
as a guide. It is possible that other types of cables can be used.
The examples shown are calculated to connect an IBM RS/6000 with

a PC running NAVITERM. To other UNIX systems it can be necessary
to use other cable types. If there is something wrong with the cable, or
if the serial port on the UNIX system is not ready (DCD(8) is not set
high on the PC), NAVITERM will shut down.
Both hardware The following cable is always recommended, where it is possible to have
handshake 7 wires in the serial cable. It can be used for both a hardware handshake
and XON/XOFF and a XON/XOFF handshake, and has complete control over whether
NAVITERM and UNIX are ready (DCD(8) and DTR(20)).
PC NAVITERM AIX
Pin no. Pin no.
2 3
3 2
4 5
5 4
7 7
20 8
8 20
Hardware handshake. Full cable to

hardware or XON/XOFF.
62 Dok:
All
Only XON/XOFF The following cable can only be used for an XON/XOFF handshake.
It also has complete control over whether NAVITERM and UNIX are
ready (DCD(8) and DTR(20)).
PC NAVITERM AIX
Pin no. Pin no.
2 3
3 2
7 7
8 20
20 8
Full cable to XON/XOFF handshake.
Only XON/XOFF The following cable should only be used if, for example, because of wall
installations, etc. there can only be four wires in a serial cable. NAVI-
TERM should use an XON/XOFF handshake, and it is only possible
for the UNIX system to discover that NAVITERM has stopped, and thus
shut the UNIX program down. NAVITERM does not discover that the
serial port on the UNIX system is not ready, but just starts up with a
black screen.
PC NAVITERM AIX
Pin no. Pin no.
2 3
3 2
7 7
8 8
20
XON/XOFF. UNIX shuts NAVISION

down if NAVITERM is stopped. If the
UNIX port is ready NAVITERM starts
with a black screen.
63 Dok:
All
NAVITERM and Windows
NAVITERM is not specially developed for Windows and can thus react
inappropriately under it (the serial version can drop characters, for
example). If NAVITERM will be used under Windows, it is recommended
that powerful PCs are used. The best possibilities of getting NAVITERM
to function correctly can be achieved by following the guidelines below:
Setting up A .pif file should be created, which sets foreground and background
Windows priority. Processor priority should be set as high as possible for both
foreground and background, as this gives the least risk of losing characters.
Test that NAVITERM does not lose characters when it is running a very
CPU-demanding program in the foreground, while NAVITERM runs in
the background and receives characters.
Setting up Under Windows NAVITERM should always be started with the -h

NAVITERM parameter, which means that NAVITERM uses a hardware handshake
(see page 57). This is faster than an XON/XOFF handshake, and it makes
it possible to run with a higher speed on the serial connection.
After setup you should test whether NAVITERM functions correctly. You
can read about this in Testing a Handshake on page 71.
64 Dok:
All
5.5 The NAVITERM Menu

Once NAVITERM is started, other programs, such as Navision, can be
started. Hold down both shift keys to get to the NAVITERM menu
(exit with [Esc]). The menu contents depends on whether you run serially
or via TCP/IP, and on the start parameters. These options may appear:
Communica- This is only available in the serial version of NAVITERM.

tion status It shows the current status of the serial communication and
makes it possible to determine if there has been communica-
tion errors. The current port selection (I/O address and IRQ),
the current port settings (baudrate, bits, stop bits and parity)
and the UART type on the port are also displayed.
Session n (n stands for a number). When TCP/IP is used you can run
multiple sessions simultaneously on one or more UNIX
systems. Sessions created with the Create session option
are displayed like: -> Session 1 (host name)
You switch to another session number by selecting the menu

option for the relevant session.
Create session Displayed only if NAVITERM communicates via TCP/IP.

This option is used to start a new session. NAVITERM
then asks for the host and login names for the new session.
Session Displayed only in the serial version of NAVITERM and

close used to stop the program. The serial connection is then
shut down, and stops NAVITERM.
Refresh screen Displayed only if you run Navision. If the monitor shows
the wrong characters (because of a poor modem connection,
for example), these can be recovered using this menu option.
Reset terminal Sets NAVITERM in normal terminal mode, by switching

from Navision scan code keyboard mode to normal key-
board mode. This option should only be used if NAVITERM
was not put back in normal mode (because of a poor modem
connection, for example), when you exited Navision.
Operating Switches temporarily to the operating system. To return,

system type exit and press [Enter].
reDirect print Here you can choose a printer port or a file to print to.
When you print from a UNIX system, the control codes
from the UNIX system always overwrites this selection.
Print/Session Used to close the printer/file being printed to. This can also
close be done with a control code from the UNIX system.
The NAVITERM Menu 61
65 Dok:
All
5.6 Remote Control of NAVITERM

NAVITERM can be controlled with codes sent from the UNIX system.
This means that you can determine where data for NAVITERM should
be sent (monitor, printer or file), for example, or you can send codes
that make NAVITERM start an external program.
These and similar options are described in this section.
Pass-through Print
Pass-through print is a NAVITERM function, that allows UNIX systems

with this option to print out via NAVITERM.
This means that a UNIX system can send a printout to NAVITERM,

which then sends it on to the local printer port on the PC where
NAVITERM is running. The same methods are used as when a UNIX
system sends printouts to an AUX port on an ordinary terminal, for
example, IBM 3151, Wyse 120, etc.
The figure below illustrates how printouts are directed to the printer:
UNIX Server NAVITERM
RS232
Ethernet or Token Ring
NAVITERM
62 Remote Control of NAVITERM
66 Dok:
All
The control codes sent to NAVITERM determine whether the data

which follows should be sent to the screen or to a printer. In other words,
NAVITERM contains a little switch, which is controlled by codes sent
by the UNIX spool system. This is illustrated in the figure below:
NAVITERM
Screen
SCREEN DATA (switch to print) PRINT DATA (switch to screen) SCREEN DATA
Printer
When you run NAVITERM on a UNIX system, you can direct printouts
to a local printer.
Prerequisites for Use of Pass-through Printing
• A general fact of pass-through printing is that (independent of

NAVITERM) it is only possible to print out in ASCII format. It is not
possible to print graphics, download fonts, or similar things.
• Binary files often contain codes resembling those that tell NAVITERM
where the data should be sent. Printout of such a file can result in the
screen and printout being mixed together.
• Printer drivers with control codes that affect NAVITERM cannot be

used.
• NAVITERM does not convert data, but sends it to the printer as it was
received from the UNIX system.
• Pass-through printing can only be used if it is supported by the operating

system used or the hardware that connects the serial terminals.
• It is possible that the screen and print data can be mixed together, and
no guarantee can be given that pass-through printing works on all
platforms. It is important that you test carefully before you start using
the installation.
• If you type quickly while NAVITERM is about to print out, the DOS
keyboard buffer can fill up, so DOS makes a beep. When this is heard,
BIOS interrupt is disabled, and there is therefore danger of NAVITERM
dropping characters from the serial port. So do not use the keyboard
before NAVITERM is finished printing to the local printer.
Remote Control of NAVITERM 63
67 Dok:
All
Navision and Pass-through Printing
Navision’s printouts are sent as usual to the UNIX print system, without
any special short cuts to NAVITERM. It is therefore up to the operating
system to cut and paste print data with the other screen data.
When Navision sends a printout to the UNIX system, an external printer
command is called, and Navision changes the system’s terminal setup.
On some UNIX systems this results in dropped characters, if the UNIX
spool system sends data to the screen before Navision has changed the
terminal setup. In this case it is not foreseeable whether the printout will
appear on the screen or on the printer.
This problem is greatest on systems where the print system uses software
for printing to a remote terminal. Systems that use intelligent terminal
ports do not normally have this type of problem.
In order to avoid having the data combined, you can have Navision
use a command file instead of a printer command. The command file
should be activated so it is executed in the background, and waits a
moment before it starts printing. With this method you can ensure that
Navision is back to its normal screen when printout starts, and that no
characters are dropped.
68 Dok:
All
Control Codes for Pass-through Printing
NAVITERM uses the following control codes for pass-through printing:
Device control DLE STX <command><parm>DLE ETX
<command> may be:
O Open and Create

A Open and Append
C Close
F Flush
The printer port/file to be used for O and A is <parm>.

The other codes used are in ASCII:
STX = hex2 = ^B
ETX = hex3 = ^C
If you do not specify any parameters, the last used printer port/file will
be used. If you end with C(lose), the printer or file selection will be
set to that selected with NAVITERM’s -O start parameter.
Pass-through <DLE><DC2> (starts pass-through printing)

control <DLE><DC4> (stops pass-through printing)
The codes used are in ASCII:
DLE = hex10 = ^P
DC2 = hex12 = ^R
DC4 = hex14 = ^T
If, for example, NAVITERM was already started with the -Olpt1
parameter, the following can be sent to NAVITERM:
<DLE><DC2><Data to printer><DLE><DC4>
This results in data being sent to a printer.
69 Dok:
All
The UNIX print system can also switch printer port/file. If the below
control codes are sent to NAVITERM before printout, printing will take
place on lpt2:
<DLE><STX><O><lpt2><DLE><ETX>
If you end with C(lose), all printouts will thereafter be sent to the
printer port/file that was selected on the command line with -O, for
example:
<DLE><STX><C><DLE><ETX>
The UNIX print system can then again print by sending the codes for
starting and stopping pass-through printing.
If the selected printer or file is not ready, NAVITERM displays a message

on the screen. You can then try again, or you can cancel the transfer.
If you are printing to a printer, for example, and it is not turned on, you
can now turn it on, press [Enter], and then NAVITERM will try to send
data to the printer.
If you choose to cancel the transfer, data is still sent from the UNIX
system to NAVITERM, but it is not used. NAVITERM continues sending
data to nowhere until the UNIX system sends a C(lose) command or
the user selects Print/Session close on the NAVITERM menu.
70 Dok:
All
Automatic File Transfer
Files can also be transferred from the UNIX system to PCs with NAVI-
TERM using the control codes described for pass-through printing.
File transfers are done in ASCII format, and there is no transmission

protocol. To avoid transmission errors, the communication lines should
be 100 percent problem-free.
Most multiplexers use a communication protocol that result in a correct

transfer. If a modem is used, it is important that it uses an Error
Correction Protocol (NMP2-10, for example), which ensures correct data
transfer.
Starting a File transfers can be started in many ways, but the easiest is to print a
file transfer report to a printer driver which is set up to automatically transfer the
file to NAVITERM. The printer driver should print to a file on the UNIX
system, and then call a command file (shell script) which sends the correct
control codes to NAVITERM. The printer driver can, for example,
contain the following lines:
Write to....: auto.wp

Spool command....: /naviutil/transfer wp.doc %1
The printer driver creates a file with the name auto.wp and then call
the command file (the shell script) /naviutil/transfer with the
file name auto.wp as a parameter. The file name on the PC will be
wp.doc.
The shell script can, for example, contain the following lines:
#!/bin/ksh
TTY=‘tty‘
echo "\020\002O$1\020\003\c" >$TTY
echo Wait, transferring file to local PC through $TTY, File name = $2
echo "\020\022\c" > $TTY
cat $2 > $TTY
echo "\020\024\c" > $TTY
echo "\020\002C\020\003\c" >$TTY
The examples shown can also be applied to much more advanced scripts.
You can, for example, create a report which first presents a request panel
where you can enter the placement of the file with file and directory
names. When the report has generated the file, it can use the CallSystem
AL function (with file and directory names as parameters) to call a
command file (shell script) which transfers the file.
71 Dok:
All
Starting an External Program
By sending control codes from the UNIX system you can have
NAVITERM start an external program or execute a command in the
operating system. Under DOS there are the usual requirements for how
much free space must exist in order to start a new program:
• NT_COM.EXE uses about 130 KB

• NT.EXE uses about 140 KB
• NT2.EXE uses about 200 KB
Under OS/2 there is normally sufficient memory, as the external program

can be started in another session.
Starting an An external program is started with the following control codes:

external
program <DLE><STX><E><"name of an external program"><DLE><ETX>
In the string that is sent to NAVITERM you can also insert parameters
that must be used when starting the external program. If the UNIX system
sends the following string to NAVITERM, for example:
<DLE><STX><E><wp mydoc.wp><DLE><ETX>
then WordPerfect is started with the mydoc.wp file as an open document.
72 Dok:
All
Integrating NAVITERM with Other Programs
The two functions for transfer of files and starting external programs can
be combined so they allow NAVITERM to work with other programs,
even though the user’s PC is not placed locally but is linked via a
multiplexer and/or a modem.
A very advanced integration can be constructed for Navision, even

though the only connection to the UNIX system takes place via NAVI-
TERM. For example, a setup can be created where, with a single press
of a key, Navision generates a merge file that is transferred to the PC
with NAVITERM, where WordPerfect is automatically started with the
file loaded.
This can be done by creating a report that generates a comma-separated

file, and then executing the CallSystem AL function, which calls a
command file (shell script) with the file name as a parameter. The shell-
script can look like this:
#!/bin/ksh
TTY=‘tty‘
echo "\020\002O$1\020\003\c" >$TTY
echo Wait, transferring file to local file through $TTY
echo "\020\022\c" > $TTY
cat $2 > $TTY
echo "\020\024\c" > $TTY
echo "\020\002C\020\003\c" >$TTY
echo Wait, starting DOS program $3 with the $1 file
echo "\020\002E$3 $1\020\003\c" >$TTY
echo "\020\002C\020\003\c" >$TTY
73 Dok:
All
5.7 Testing and Troubleshooting

This section describes a number of possibilities for testing the NAVITERM
installation. The following topics are described:
• Testing TCP/IP before starting NAVITERM
• Testing a handshake
• Overflow errors
• Framing and parity errors
• If NAVITERM won’t start
Testing TCP/IP before Starting NAVITERM
If there are problems in establishing a connection to the UNIX system

when starting NAVITERM in the version that uses TCP/IP then it is
important to first test whether the TCP/IP communication is functioning
properly.
First try using the ping TCP/IP function to see if it is possible to get
an answer from the UNIX system. If this is not possible when the UNIX
system’s TCP/IP address is used then the error should be looked for in
the TCP/IP setup.
If the address is okay, then you should test whether it is possible to send
a ping when the UNIX system’s host name is used. If ping is okay,
you can try starting another terminal emulator, if others come with the
TCP/IP package.
If the above is okay, then the parameters used when starting NAVITERM
should be checked. It is especially important that the start parameter:
-n<TCP/IP-module>
is set to the correct TCP/IP package. It is also important that the

parameter:
-h
is set to the same host name as used in the ping test. If the above is
correct then it should be possible to start NAVITERM correctly.
70 Testing and Troubleshooting
74 Dok:
All
Testing a Handshake
In the serial version of NAVITERM it is very important that hand-

shaking is configured correctly, that is, that:
• the UNIX system and NAVITERM are using the same type of
handshake
• a correct cable is used in relation to the selected handshake
If this is okay then the handshake can be tested by letting the UNIX
system send a lot of screen data to NAVITERM. The easiest way to do
this is as follows:
1) Start Navision and print a large report to the screen.
2) Hold the two [shift] keys down simultaneously while printing.
3) Select the Communication status option on the NAVITERM menu.
You can now see the receive buffer counting. When there is no more
space in the receive buffer (about 16,000 bytes), the Status field changes
from Running to Stopped, and the buffer should stop counting
immediately. If the receive buffer continues to count after Status has
changed to Stopped, then there is something wrong with the handshake
setup or the wrong cable has been selected for the relevant handshake.
Operation of NAVITERM should never be started if the handshake does
not function correctly, as this can result in incorrect characters on the
screen, or NAVITERM completely stopping. The correct setup of a hand-
shake is described on page 56.
Overflow Errors
If the serial version of NAVITERM drops characters on the screen, or

if the screen doesn’t look right, you can check whether NAVITERM
has received Overflow Errors from the serial port in the PC. This is done
under the Communication status option in the NAVITERM menu, which
you can access by pressing both [shift] keys simultaneously.
Overflow Errors arise when the serial port has received a character
which did not manage to be read by NAVITERM before the next one
was received. This can happen if interrupt is blocked for a long time,
for example, by a keyboard driver, memory manager or other programs
that use interrupt.
Testing and Troubleshooting 71
75 Dok:
All
To repair this error you can start the PC under DOS without a keyboard
driver, memory manager, etc., and then test whether Navision still shows
these Overflow Errors. Another possibility is to reduce the speed on the
serial line.
Framing and Parity Errors
If a framing or parity error appears under Communication status on

the NAVITERM menu, this can be because the communication parameter
for baudrate, databits, stopbits or parity was specified differently
on the UNIX system and in NAVITERM.
These errors can also occur because of serial cables that are too long
or noisy. These things can be improved by reducing the speed of the
serial communication.
If NAVITERM Won’t Start
Returning If the serial version of NAVITERM stops just after being started, it is
to DOS because pin 8(DCD) on the serial connector is not set high. NAVITERM
uses 8(DCD) to figure out whether the UNIX system is ready. If it is
not ready, then NAVITERM will not start.
If NAVITERM has started, and the UNIX system is no longer ready

(power failure or something similar), then NAVITERM will also stop.
Error initializing If Navision is started on a UNIX system via NAVITERM, and Navision
screen/keyboard displays this error message:
Error initializing screen/keyboard:

Terminal did not respond properly on request
this means that Navision has sent an enquiry to NAVITERM, but has
not received an answer, or the answer is in the wrong format. This can
occur if the data is destroyed during transmission, because of a poor
modem line, for example, or too high speed on the serial line.
This error can also occur if character converting is used (from one
character set to another) on the UNIX system. This should not normally
be used with NAVITERM.
72 Testing and Troubleshooting
76 Dok:
All
CHAPTER 6
MAKING BACKUPS
This chapter describes when, why and how backups should be made in an installation.
The chapter is divided as follows:
• General information on making backups
• Making backups in Navision
77 Dok:
All
6.1 About Making Backups

The purpose of making backups is that you will always have an extra
copy of your data which you can import into the program if problems
arise with the original data.
You should make backups for your own sake, but in most countries it
is required by law as well. The following is a summary of the major
points from the Danish Bookkeeping Regulation (Regulation no. 598,
August 21, 1990):
1. The responsible party will store the financial statement information

in a satisfactory manner.
2. The information must be stored for 5 years from the beginning

of the current fiscal year.
3. If the responsible party uses electronic media, proper security

measures must ensure that:
a) the media are stored in a satisfactory manner, so that access

to the data is possible until the 5 year period is over.
b) backup copies are made sufficiently often, and that these

are stored in such a way that they cannot be destroyed
or stolen, etc. together with the original.
4. If the statement information is stored electronically, a government

authority can, to the degree that it has the right to do so, demand
information on a company’s bookkeeping, and that all materials
necessary for access to the statement information be made available.
This means that if you switch to a new version of the accounting system
or change the installation in another way, you must still keep one or more
copies of the company data in a readable format (and in a safe place).
If you switch to a new version of the accounting system, it can be

necessary to save the old system for the next five years (as long as the
storage requirement is valid) in order to be able to see the old data. You
do not have to have the old system installed, you can just save it on
diskettes and install it if you need it.
74 About Making Backups
78 Dok:
All
When You Should Backup Your Data
In these cases you should always make a backup:
• Before expanding the database.

• Before equipment is installed or removed from the UNIX system or
systems which contain the Navision database.
• Before a date compression of entries is done (selected under Periodic
in the Main Menu), and before you optimize data (under MISCELLA-
NEOUS, TABLE SIZES, OPTIMIZE).
• Before the database or its parts are copied in the operating system.
• Before programs for optimization of the disk are used.
In any case, it is a good idea to have an updated copy of your company

data in a safe place, as you can never be completely insured against fire,
robbery, computer virus, etc.
Procedures for Making Backups
There is no formula for how often you should back up your data, but
you should think about the fact that, if you import a backup that is one
week old, then you must reenter the data for the week that was lost. As
a backup is not more secure than the original data, you should also
insure yourself against errors in the backups by creating a system of
backups on several levels. For example:
• Export a copy every week. Use different groups of media, so the last
five copies can be found in different locations. If errors arise for the
group, the next group can probably be used.
• Every fifth week the backup should be placed in the company’s safe
or another safe place.
• After 25 weeks the last backup is imported into another system than
the one normally worked on. Then the contents of the hard disk are
tested. If there are no errors, the backup is placed in the company’s
vault box or another safe place outside of the company.
With this method you can lose a maximum of data for the last 25 weeks,
and one of the copies will most likely be able to be imported without
any errors. The backups should be tested regularly. Import them into
another system than the one normally worked on, and test the backups
there.
About Making Backups 75
79 Dok:
All
6.2 Making Backups in Navision

Navision’s built-in backup function makes a backup by creating a file
containing the most basic data from the database. When the copy is
imported later on, Navision creates the other data based on this data.
This function can be used to make backups on the hard disk, which later
can be copied onto tape.
Testing the Database before Copying to a Tape Station
Before you make a Navision backup, you should test the database for
errors using the dbtest start parameter. If the database is not okay, an
error message will be displayed with information about what and where
the error is.
You can select a small or a large test, which is specified with min or
max next to the dbtest start parameter, as shown here:
navi dbtest=min, or
navi dbtest=max
The min test checks whether all the data can be read and used. This
test is much less time-consuming than max, which also test whether the
sorting provides the data from which it was generated. min is normally
sufficient for "everyday use". Below is the window that is displayed when
dbtest is executed:
Demo Company Date 01-02-94 Time 09.00 Free 36% Mem. 350 Kb
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ Testing database D:\navibase\database ‡
‡ - company ‡
‡ - table ‡
‡ ‡
‡ ‡
‡ Testing tables ‡
Figure 6.1 ‡ ‡....|....|....|....|....‡....|....|....|....|....‡ ‡
Status for ‡ 0 10 20 30 40 50 60 70 80 90 100 ‡
‡ ‡
dbtest ‡ Testing ‡
‡ secondary keys ‡....|....|....|....|....‡....|....|....|....|....‡ ‡
‡ 0 10 20 30 40 50 60 70 80 90 100 ‡
‡ ‡
‡ Testing ‡
‡ free space ‡....|....|....|....|....‡....|....|....|....|....‡ ‡
‡ 0 10 20 30 40 50 60 70 80 90 100 ‡
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
Insert
76 Making Backups in NAVISION
80 Dok:
All
APPENDIX A
TCP/IP PROTOCOLS
This appendix contains a list of which TCP/IP protocols can be used.
81 Dok:
All
A.1 TCP/IP Protocols

Navision presently supports the TCP/IP protocols listed in this appendix.
The abbreviation in parentheses after each TCP/IP package name is the
parameter for the network type (nettype). If, for example you want to
start Navision with IBM’s TCP/IP under OS/2, type:
navi2 serverno=1,nettype=TCPI
The nettype parameter is described on page 45.
Under DOS
PC/TCP from FTP Software Inc., version 2.05 (tcpf)

PC/TCP from FTP Software Inc., version 2.2 (tcpf)
Pathway from Wollongong, version 1.1.2 (tcpw)
Under OS/2
PC/TCP from FTP Software inc., version 1.1 (tcpf)

IBM TCP/IP, version 1.2 (tcpi)
IBM TCP/IP, version 1.2.1 (tcpi)
Pathway from Wollongong, version 1.1 (tcpw)
The listed versions of TCP/IP packages are tested, but newer versions
can, in most cases, also function, but this should always be tested first
with Navision nettest programs.
78 TCP/IP Protocols
82 Dok:
All
APPENDIX B
NAVITERM ESC SEQUENCES & F KEYS
This appendix contains a list of the Esc sequences and function keys used in
NAVITERM.
83 Dok:
All
B.1 Control Codes and Keyboard Esc Sequences

Esc Character 1Bh DLE 10h = ^P
%n Character No. + 20h DC2 12h = ^R
%x Character x position + 20h DC4 14h = ^T
%y Character y position + 20h STX 2h = ^B
%c Any character except 0h etx 3h = ^C
%d A decimal string
Esc Sequences
The following Esc sequences exist:
Esc P %x %y Set the cursor bar position to x, y.

Esc X %d,%d; Repeat character %c %n times from the current cursor
position. All characters except 0h can be used.
Esc K %d K Set color/attribute to %d (PC color table 256 color %d in
the interval 0d -255d).
Esc S P %d ; Special character 1 - 0x1f.
Esc R A %n Move the cursor %n lines up.
Esc R B %n Move the cursor %n lines down.
Esc R C %n Move the cursor %n columns to the left.
Esc R D %n Move the cursor %n columns to the right.
Esc J Clear the screen and move the cursor to start position.
Esc j Clear from the cursor position to the end of the screen.
Esc l Clear from the cursor position to the end of the line.
Esc H Move the cursor position to 0, 0.
Esc s Go to special keyboard mode.
Esc a Go to normal keyboard mode.
Esc w o n Turn new line on.
Esc w o f f Turn new line off.
Esc S F %n Roll the screen %n lines up.
Esc S B %n Roll the screen %n lines down.
Esc C %c Cursor type 0=None, 1=Line, 2=Half, 3=Whole.
Esc I C Insert a character where the cursor is.
Esc D C Delete the character where the cursor is.
Esc I L Insert a blank line at the current line position.
Esc D L Delete the line at the current line position.
Esc
B %d, %d B Beep in %d1 Hz for %d2 milliseconds.
Esc k 1 keypad Enter on.
Esc k 2 keypad Enter off.
Esc G t e Returns the following information:
Screen resolution 25x80 returns naviterm
Screen resolution 43x80 returns naviterm43
Screen resolution 50x80 returns naviterm50
80 Control Codes and Keyboard Esc Sequences
84 Dok:
All
Esc Scr_Info Returns information on screen setup, for example:

Esc S I %d , %d , %d , %d ; where:
%d1 Screen type.
%d2 Number of lines on the screen.
%d3 Screen width in number of characters.
%d4 Screen mode 1=Color, 0=Monochrome.
Function Keys
Function Keys Alone Function Keys + Shift

F1 Esc [ 1 F1 Esc [ s1
F10 Esc [ 0 F10 Esc [ s0
F11 Esc [ X1
F12 Esc [ X2
Function Keys + Ctrl Function Keys + Alt

F1 Esc [ c1 F1 Esc [ a1
Control Codes and Keyboard Esc Sequences 81
85 Dok:
All
Other Keys
Left Esc [ A
Up Esc [ C
Right Esc [ B
Down Esc [ D
PgUp Esc [ u
PgDn Esc [ d
Home Esc [ h
End Esc [ e
Del Esc [ i
Insert Esc [ l
keypad Enter Esc [k1; (only when keypad Enter on is selected)
82 Control Codes and Keyboard Esc Sequences
86 Dok:
All
B.2 Control Codes for Pass-through Print

NAVITERM uses the following control codes for pass-through print:
Device control DLE STX <command><parm>DLE ETX
<command> can be:
O Open and Create

A Open and Append
C Close
F Flush
<parm> is for O and A is for the printer port/file to be

used. The other codes used are in ASCII:
STX = hex2 = ^B
ETX = hex3 = ^C
Pass-through <DLE><DC2> (start pass-through printing)

control <DLE><DC4> (stop pass-through printing)
The codes used are in ASCII:
DLE = hex10 = ^P
DC2 = hex12 = ^R
DC4 = hex14 = ^T
If you do not specify any parameters, the last-used printer port/file will
be used. If you end with C(lose), the printer or file selection is set
to the one set on the command line with the -O parameter. If NAVITERM
was started with the -Olpt1 parameter, for example, the following can
be sent to NAVITERM:
<DLE><DC2><Data to printer><DLE><DC4>
This results in data being sent to a printer.
Control Codes for Pass-through Print 83
87 Dok:
All
84 Control Codes for Pass-through Print
88 Dok:
All
APPENDIX C
DOS/OS2/UNIX COMPATIBILITY
This appendix describes which Navision files can be transferred from one platform
to another immediately, as well as which can first be transferred after processing.
89 Dok:
All
C.1 Compatibility among DOS, OS/2 and UNIX

On conversion from one UNIX platform or from DOS and OS/2 to UNIX
data is transferred to the UNIX system. Not all Navision files can be
transferred directly, as they do not all have the same internal format.
In the list below you can see which type of files can be transferred
directly, and which cannot:
Compatible Files
backup copies (xxx.#bk)

object files (xxx.obj)
color files (<id>.col og <id>.mon)
Non-compatible Files
databases
setup files (<id>.zup)
calendar files (<id>.cal)
The database cannot be transferred directly as it is, but if a Navision

backup of the database is made, this file can be transferred without any
problems, as the backup copy is binarily compatible between DOS, OS/2
and UNIX.
Among the other Navision files only the object and color files can be
transferred directly. This can be done binarily with the ftp TCP/IP
tool.
If a backup should be transferred from a PC-based Navision version

from before 3.51, the database must first be updated on the PC to version
3.51 or later. After this, a backup can be made which can be imported
into the UNIX version of Navision.
86 Compatability among DOS, OS/2 and UNIX
90 Dok:
All
Compatability among DOS, OS/2 and UNIX 87
91 Dok:
All
Copyright © 1996 Navision Software a/s

ISBN 87-7849-161-4
Published by Navision Software a/s
Printed in Denmark 1996.
92 Dok:

9.navision Under UNIX

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

9.navision Under UNIX

Încărcat de

Drepturi de autor:

Formate disponibile

All

NAVISION UNDER UNIX

Copyright © 1996 Navision Software a/s

Navision® is a registered trademark of Navision Software a/s.

1. INTRODUCTION 1 3. SETTING UP CONNECTIONS 15

1.1 Introduction to Navision 3.1 Setting Up a UNIX System

4. STARTING Navision 5.5 The NAVITERM Menu 61

A.1 TCP/IP Protocols 78

Attention! In this book, in general, and especially in connection with installation, a

1.1 Introduction to Navision under UNIX

The rest of the chapter is meant as a source of inspiration, where more

After this, select the area that corresponds to the installation:

• Setting up the UNIX system as database server, and

• Setting up the UNIX system as a multiuser system and

Terminal emulation is described separately in chapter 5.

2 Introduction to NAVISION under UNIX

The rest of the chapter describes Navision’s start parameters. It is not

CACHE, COMMITCACHE, DATABASE, DBGROUP, DBREADONLY, DBTEST,

Introduction to NAVISION under UNIX 3

The Typography and Symbols in this Manual

Field Names All field names are underlined in the text.

Field Contents The contents of a field, or what should be entered/selected,

PULL-DOWN The functions on the pull-down menu uppermost in each

AL Code and This font, called Courier, is used to highlight all AL

4 Introduction to NAVISION under UNIX

• Selecting a type of installation

2.1 Selecting an Installation

The advantages and disadvantages of these two methods are described

UNIX as a multiuser system

If you want to structure a network of Navision workstations over a

If PCs will be used as workstations, terminal emulation can be done

• NAVITERM, which is Navision’s own terminal emulator. It requires

As Navision runs centrally on the UNIX system, the locally connected

UNIX Server Naviterm Naviterm Terminal

Naviterm Naviterm Terminal

Ethernet running TCP/IP

Naviterm Naviterm Naviterm

Naviterm Naviterm Naviterm

Selecting Terminals or Terminal Emulation

Navision’s screen appearance and printout handling under UNIX depend

Attention! On SCO there is no support for WYSE 120. On HP there

When shouldn’t • Client/server should only be used in local networks.

When a UNIX system is used as server, several different types of

• Communication between DOS or OS/2 systems and the UNIX system

• In cases where you need a lot of free memory for PC clients, it is an

TCP/IP Regarding the possibility of frequent updates, information on valid TCP/IP

Both Multiuser System and Client/Server

A UNIX system can function as a multiuser system while it runs as

The illustration below shows an example of a server with two types of

UNIX Server Client Client Client

Client Client Client

2.2 Examples of More Advanced Installations

With advanced asynchronous multiplexers (physical equipment) you can

Use of multiplexers means that use of the capacity on the telecommunica-

One disadvantage of multiplexers is that they can result in limited access

This can be configured so everything takes place automatically, depending

12 Examples of More Advanced Installations

Most UNIX platforms can use X.25 in two different ways:

• with the TCP/IP protocol on top of the X.25 protocol

With TCP/IP on top of X.25 a completely transparent TCP/IP connection,

Examples of More Advanced Installations 13

14 Examples of More Advanced Installations