Documentos de Académico
Documentos de Profesional
Documentos de Cultura
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.
ISBN 87-7849-161-4
2 Dok:
All
TABLE OF CONTENTS
3 Dok:
All
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.
5 Dok:
All
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.
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.
or
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
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.
7 Dok:
All
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:
[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.
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:
• Advanced installations
9 Dok:
All
• 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.
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.
• Other terminal emulators with dial-up support. But these do not provide
the same usability as NAVITERM, which is created especially for
Navision.
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:
e
nous Lin
Asynchro
MUX
MODEM
MUX
Leased
Line MODEM
Remote Site
BRIDGE
Leased Line
MODEM BRIDGE
Remote Site
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
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.
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.
8 Selecting an Installation
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.
• 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.
Selecting an Installation 9
13 Dok:
All
Network Types
• 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.
• 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.
10 Selecting an Installation
14 Dok:
All
T-R
UNIX Client Naviterm Naviterm Naviterm
If you use UNIX Client as router then the database will be on UNIX Server
Selecting an Installation 11
15 Dok:
All
Asynchronous Multiplexers
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.
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.
16 Dok:
All
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.
17 Dok:
All
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 TCP/IP
• Setting up terminals
19 Dok:
All
• Test TCP/IP
Specifying Services
naviserv 3001/tcp
Now server 1 has port number 3001, server 2 has port number 3002,
server 3 has port number 3003, etc.
20 Dok:
All
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):
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.
21 Dok:
All
ping naviserv1
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.
22 Dok:
All
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.
˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝»
” ”
” ”
” ”
” NAVISION Installation ”
” Start ”
” installation? ”
” ”
” Press [Enter] ”
” ”
Figure 3.1 ” ”
Installing ” ”
” ˜˜˜˜˜´˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜´˜˜˜˜˜¿ ”
Navision ” ‡ ‡˝˝˝˝˝˝‡ ‡. ‡ ”
” ˆ˜˜˜˜˜`˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜`˜˜˜˜˜· ˜˜¿ ”
” ‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡‡ ‡ ”
” ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜ ”
” A:\ ”
” ”
¨˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝˝…
Installing a Client on a PC 19
23 Dok:
All
• 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
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
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.
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.).
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 :
(where %1 stands for the file name which was specified in the Destination
field).
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
Specifying Hosts
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
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.
27 Dok:
All
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.
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
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.
You must find the best balance between RAM usage and speed.
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:
Press a key
TCP/IP Setup 25
29 Dok:
All
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.
30 Dok:
All
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 *
$ 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.
$ cd /xxxx
$ chmod o-x *
31 Dok:
All
What you should notice is, that if a terminal does not use scan codes,
the keyboard will function somewhat differently for Navision than
otherwise:
28 Setting Up Terminals
32 Dok:
All
Printer Selections
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.
(where %1 stands for the file name specified in the Destination file).
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
35 Dok:
All
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.
..
..
..
..
Naviserv:2:once:/xxxx/autostart >>/xxxx/server.log
#!/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
"***************************************************************"
37 Dok:
All
*******************************************************************
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
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:
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
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.
$ navi serverno=1
39 Dok:
All
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
40 Dok:
All
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:
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:
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.
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:
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.
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
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:
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.
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.
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.
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.
$ cp /xxxx/database /navibase/database
$ cd /navibase
$ chown <user> database
$ chmod u=rw,g=rw database
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.
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.
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
dbreadonly
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.
debug
id
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 ‡
˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜
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.
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:
The next time Navision is started with id=peter, the standard setup
will be valid.
48 Dok:
All
keyboxpath
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.
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
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:
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.
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
2) You can delete the temporary files without endangering the program
files.
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
This chapter describes the Navision terminal emulator: NAVITERM. The following
topics are described:
• What is NAVITERM?
• Equipment requirements
• Installing NAVITERM
• Starting NAVITERM
53 Dok:
All
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.
• The DOS and OS/2 version (NT.EXE and NT2.EXE), which commu-
nicates with the UNIX system via TCP/IP and the network.
50 About NAVITERM
54 Dok:
All
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.
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.
Equipment Requirements 51
55 Dok:
All
c:\naviterm
switch to this directory, and copy all files from the NAVITERM diskette.
(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.
naviterm 25x80
naviterm43 43x80
naviterm50 50x80
Installing Terminfo
52 Installing NAVITERM
56 Dok:
All
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:
-l Login name. If Rlogin has been selected, use this login name.
-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
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:
-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 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.
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).
Starting NAVITERM 55
59 Dok:
All
56 Starting NAVITERM
60 Dok:
All
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 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.
Starting NAVITERM 57
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.
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
58 Starting NAVITERM
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
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
Starting NAVITERM 59
63 Dok:
All
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.
After setup you should test whether NAVITERM functions correctly. You
can read about this in Testing a Handshake on page 71.
60 Starting NAVITERM
64 Dok:
All
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)
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.
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.
65 Dok:
All
Pass-through Print
The figure below illustrates how printouts are directed to the printer:
RS232
NAVITERM
66 Dok:
All
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.
• 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.
• NAVITERM does not convert data, but sends it to the printer as it was
received from the UNIX system.
• 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.
67 Dok:
All
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
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.
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>
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 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
Files can also be transferred from the UNIX system to PCs with NAVI-
TERM using the control codes described for pass-through printing.
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:
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
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:
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>
72 Dok:
All
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.
#!/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
• Testing a handshake
• Overflow errors
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>
-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.
74 Dok:
All
Testing a Handshake
• 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:
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
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.
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.
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.
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.
Error initializing If Navision is started on a UNIX system via NAVITERM, and Navision
screen/keyboard displays this error message:
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.
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:
77 Dok:
All
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):
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).
78 Dok:
All
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.
79 Dok:
All
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
80 Dok:
All
APPENDIX A
TCP/IP PROTOCOLS
81 Dok:
All
navi2 serverno=1,nettype=TCPI
Under DOS
Under OS/2
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
This appendix contains a list of the Esc sequences and function keys used in
NAVITERM.
83 Dok:
All
Esc Sequences
84 Dok:
All
Function Keys
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)
86 Dok:
All
STX = hex2 = ^B
ETX = hex3 = ^C
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>
87 Dok:
All
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
Compatible Files
Non-compatible Files
databases
setup files (<id>.zup)
calendar files (<id>.cal)
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.
90 Dok:
All
91 Dok:
All
92 Dok: