Installation Guide for BAAN IV on UNIXThe document describes an installation of BAAN IV on a single...

BAAN IV

Installation Guide for BAAN IV onUNIX

A publication of:

Baan Development B.V.P.O.Box 1433770 AC BarneveldThe Netherlands

Printed in the Netherlands

© Baan Development B.V. 2001.All rights reserved.

The information in this documentis subject to change withoutnotice. No part of this documentmay be reproduced, stored ortransmitted in any form or by anymeans, electronic or mechanical,for any purpose, without theexpress written permission ofBaan Development B.V.

Baan Development B.V.assumes no liability for anydamages incurred, directly orindirectly, from any errors,omissions or discrepanciesbetween the software and theinformation contained in thisdocument.

Document Information

Code: U7016F USGroup: User DocumentationEdition: FDate: January, 2001

i

Installation Guide for BAAN IV on UNIX

1 Installation preparations 1-1Hardware and software requirements 1-1To tune the kernel 1-2Swap space 1-2To test TCP/IP 1-2To create the UNIX group bsp 1-2To create UNIX users 1-3To set environment variables 1-3

2 To install BAAN IV 2-1To load the software locally 2-1To load the software remotely 2-3To install the software 2-7Post-installation tasks 2-10

3 To customize the BAAN IV software 3-1To install last-minute updates 3-1To install the demo dumps 3-4To create tables for the demo models 3-5To validate the system 3-6To install the demo dumps for orgware 3-8To initialize parameters 3-9To reorganize tables 3-9To configure shared memory 3-9Create the audit database and assign tables 3-11To define the default currencies 3-12To change passwords 3-12To install a localization with demo tables 3-13Set development parameters and authorizations 3-19To anticipate shutdowns and to reboot 3-20Set permissions and checks 3-20To configure a printer 3-20

Table of contents

Table of contents

Installation Guide for BAAN IV on UNIXii

4 Scripts 4-1Run level method 4-1Direct method 4-2Starting 4-2Stopping 4-2General 4-2

5 Appendix A: The Preinst utility 5-1To run Preinst during, or immediately after, BAAN IV installation 5-1To run Preinst in an operational BAAN IV environment 5-4

6 Appendix B: To install Baan Windows 6-1Hardware and software requirements 6-1To install the Baan Windows software 6-2Installation directory of Baan Windows (BW) 6-4Baan Windows (BW) environment variables 6-5

7 Appendix C: Troubleshooting 7-1Error 1: Not owner 7-1Error 2: No such file or directory 7-2Error 5: I/O error 7-3Error 6: No such device or address 7-4Error 7: Arg list too long 7-5Error 8: Exec format error 7-6Error 9: Bad file number 7-6Error 11: No more processes 7-7Error 12: Not enough space 7-8Error 13: Permission denied 7-8Error 22: Invalid argument 7-9Error 23: File table overflow 7-9Error 24: Too many open files 7-10Error 27 - File too large 7-10Error 28: No space left on the device 7-11Error 35: No message of desired type 7-12Error 45: Deadlock situation detected/avoided 7-13Error 67 - Address already in use 7-14Error 79: Inappropriate operation for file type 7-15Error 104: Too many open files 7-16Error 105: Bad ISAM file format 7-16Error 114: File name too long 7-17Error 125: Cannot use nfs 7-17Error 147: Resource limit is reached 7-18Error 171: Bad format 7-18Error 209: Error on mirroring of database 7-18

Tahle of contents

Installation Guide for BAAN IV on UNIXiii

Error 505: No server specified 7-19Error 506: Table does not exist 7-20Error 510: Database not on 7-21Error 512: Corrupted data dictionary 7-22Error 515: License error; unpatched binary 7-24Error 600: General reference error 7-24Error 919: Bus error 7-25Error 11400: Too many open files 7-25Error 11500: Bad ISAM file format 7-26Error 12400: File name too long 7-27Error 12401: File name too long / Not owner 7-27Error 14600: No space in shared memory 7-28Error 15900: Table not registered (tbase (TP) 7-29

Table of contents

Installation Guide for BAAN IV on UNIXiv

Installation Guide for BAAN IV on UNIXv

This document describes the installation of the BAAN IV software. Thedocument can be used by anyone who wants to perform a fresh installation ofBAAN IV on a UNIX server. However, an elementary knowledge of UNIX isrequired. In addition, understanding the contents is easier if you are familiar withhow BaanERP is structured with the following:

� Package VRCs.� Package Combinations.� Drived-from structure.

The document describes an installation of BAAN IV on a single UNIX server.The examples and descriptions of actions on the UNIX prompt presuppose theuse of the Korn shell (ksh).

The following six types of atabases are considered:

� Tbase.� tbase_tp.� Oracle.� DB2.� MSSQL.� Informix.

The actual installation of the external databases, which are Oracle, DB2,MSSQL, and Informix, is outside the scope of this document. Installation ofthese databases is described in separate installation guides.

UNIX keywords, path names, and so on are printed bold (case-sensitive), forexample: the cpio command; use licmon6.1 -b; cd $BSE/bin.

Variables of any kind are in italics, for example: create the directorypathname/baan (asking you to create a subdirectory baan somewhere in thefilesystem, for example /usr3/baan or /disk1/temp/baan).

About this document

About this document

Installation Guide for BAAN IV on UNIXvi

Installation Guide for BAAN IV on UNIX1-1

Before you can install BAAN IV on a UNIX system, a number of preconditionsmust be met. Before you start the installation script, you must check or configureseveral items, and you must:

� Meet several hardware and software requirements� Tune the kernel.� Swap space.� Test TCP/IP.� Create the required UNIX group.� Create UNIX users.� Set environment variables.

Hardware and software requirementsYou can use several hardware configurations to install BAAN IV. The followinglist provides the minimum requirements to install BAAN IV.

� A UNIX, OS390, or Windows NT system.� One of the certified databases must be installed and running. These databases

include the following, however, the actual installation of these externaldatabases is described in separate installation guides.− Oracle.− Informix.− MSSQL.− DB2.

� TCP/IP software, installed, configured, and running.� A 4-millimeter tape drive for the BAAN distribution.� A CD-ROM drive for the database distribution.� A minimum of 1 GB hard disk space for the BAAN software environment

(BSE).� A network adapter.

1 Installation preparations

Installation preparations


To tune the kernelThe kernel of the UNIX machine must be tuned to accommodate the projectednumber of BAAN IV users and database.

For more information on how to tune the kernel for BAAN IV, refer to theKernel Tuning Guide for BAAN IV (U7032A US).

Swap spaceReserve a hard disk space equivalent to 2.5 to three times the size of the internalmemory for the UNIX swap space

To test TCP/IPTo start the license daemon, TCP/IP must be configured correctly. Verify that thecommand ping hostname produces a correct response. The response time for thiscommand must not be longer than 20 milliseconds (ms).coral#ping coral 65 7

PING coral.baan.com: (10.1.12.35): 65 data bytes

73 bytes from 10.1.12.35: icmp_seq=0 ttl=255 time=10 ms







----coral.baan.com PING Statistics----

7 packets transmitted, 7 packets received, 0% packet loss

round-trip min/avg/max = 0/1/10 ms

coral#

To create the UNIX group bspYou will need the UNIX group account bsp before you can install BaanERP.You can use a standard system administration utility to add this group.

The bsp group includes those users who are given system administrationprivileges for the BAAN database. The group bsp must be given the UNIXgroup ID 125.



To create UNIX usersSeveral UNIX users are required for the BAAN installation. You can use astandard system administration tool to create the required users. For helpregarding the system administration utility on a specific operating system, referto the corresponding system manuals. Note that the most frequently used type oflogon shell for BAAN users is ksh (Korn shell). The following table providesdetails of the users.

Logon id User id Primarygroup

Group id Home directory Password

bsp 125 bsp 125 $BSE/home/bsp 250bSpdemo 128 bsp 125 $BSE/home/demo 123demotools 129 bsp 125 $BSE/home/tools 123toolsapplic 130 bsp 125 $BSE/home/applic 123applictbase 132 bsp 125 $BSE/home/tbase 123tbase

The recommended group ID is 125, unless this is absolutely impossible. Tochange a group ID, use the system administration utility, or change the IDdirectly in /etc/group.

Use user ID 125 for the most important user in a BAAN IV environment, inother words, the user bsp. This user is the owner of the software, and is thereforemandatory.

Another important user is the user tbase, if bisam or btam is used as the databaseserver. This user is also mandatory, and is the owner of the tables. Only this userand user root can use all options of certain BAAN IV tools, such as tbase6.1.

If these two users do not exist on the system prior to installation, the installationscript will fail.

To set environment variablesIf you want to define the $BSE variables in the .profiles of the users, rather thanto the system-wide /etc/profile, you must be aware of the following:

During the installation, the ${BSE}/home/loginid directories are created, if theydo not already exist, and the BAAN IV .profiles are created and placed in thesedirectories. If you already have (default) .profiles in these directories, whichhappens if you use a system administrator utility to create users, these .profileswill not be overwritten. Therefore, make sure to remove any .profiles before youstart the installation script.



It is useful to create an environment settings file in the $BSE directory, namedfor example setbse. You can use this file to quickly set the BAAN IVenvironment variables while you are in the $BSE directory. Set the variables forBSE, BSE_TMP, PATH=$BSE/bin:$PATH, and TERM, for example = vt100.Do not forget to export the variables. Insert the following line:

Export BSE BSE_TMP PATH TERM.

The following is an example of such a setbse file.

vi setbse

BSE=/usr2/bseBSE_TMP=$BSE/tmpPATH=$BSE/bin:$PATHTERM=vt100export BSE BSE_TMP PATH TERM

To run the script, use following command:

$ . ./setbse


The process to install the BAAN IV software includes the following two majorsteps:

� Load the software from the tape.You can load the software either locally or remotely. A local installationmeans that the tape streamer is connected to the system on which the softwareis installed. A remote installation means that the installation is carried out ona local system from a tape loaded on a remote system in the network. A localinstallation is described in �To load the software locally,� in Chapter 2, �Toinstall BAAN IV.� A remote installation is described in �To load the softwareremotely,� also in Chapter 2.

� To install the software.This step is described in �To install the software,� in Chapter 2, �To installBAAN IV.�

The master-tape shipment can include a second tape called a patch tape. Use thesame master tape procedure to read the patch tape into a separate emptydirectory. If a patch tape is included, see the manual enclosed for installationinstructions.

To load the software locallyThis section describes how to load the BAAN IV software from a local tapedevice.

To load the software take the following steps:

1 Log on as user root and create the directory in which to load the BAAN IVsoftware, for example, /usr2/tape40b.

Never load the software onto a directory in an existing BSE environment, oronto a directory that contains existing BAAN IV tables. If you do, theinstallation script will crash.

2 Change directories to the directory you created in Step 1, and make sure thatthe tape is positioned at the beginning of the tape. You can use one of thefollowing commands to rewind the tape:

# < local rewind device

2 To install BAAN IV

CAUTION

To install BAAN IV


# mt -t local device rewind

You can enter the following command at the system prompt to check if themt command is available. If there is no magnetic tape manipulation programavailable, you must use the cpio command for this purpose:

# type mt

3 Enter the following command at the system prompt to retrieve the installationscript from tape:

# cpio -icvdB < local.device

4 Enter one of the following commands to start the mas.read6.1 utility to readthe software from tape

# sh ./mas.read6.1

# sh ./mas.read6.1 -d local device

5 Press ENTER to skip past the screen that contains help information. Thefollowing message appears:

Is the streamer connected to the local system "sysname" ? [y]

6 Press Y to continue.

7 The following menu appears, which asks you which option must be installed:

Available options with mas.read6.1

1) Select packages and Operating System2) Select only the Operating System3) Select components for Workstations installation

Choice: [1]

Press 1 for a complete installation of package VRCs and operating systems. Ifyou press 2, only an operating system is read from the tape. If you press 3,only the workstation software is read from the tape.

If your press 2 or 3, the mas.read6.1 skips the following steps and continueswith Step 10.

8 A menu appears that asks you which packages you want to install. Press Y toinstall the displayed packages. Press N to make another selection.

9 A menu appears that asks you which languages you want to install. Press Y toinstall the displayed languages. Press N to make another selection.

10 A menu appears that asks you which operating system you want to install.Press 0 if you do not want to install the operating system dependent binaries,otherwise select the relevant operating system.

NOTE

NOTE

To install BAAN IV


11 You are asked to enter the no-rewind device name of the streamer. Enter thedevice name of the no-rewind device. You will not see this question if youspecified the device name at the command line in Step 4.

12 You are asked if you are sure that the tape is in its device. Press ENTER tocontinue.

13 A message appears that asks you if you want to test the no-rewind device.You must test the device if the entered device name is a real no-rewinddevice.

14 A message appears that asks you if you want to start reading the tape.Press Y.

15 After the mas.read6.1 utility finishes, you are asked if you want to read morelanguages from tape. If you want to read more languages from tape, you mustenter Y. In that case the mas.read6.1 utility will ask again which packagesand languages you want to install.

After all of the required software is read from the tape, you are ready to runinstall6.1 to install the software.

To load the software remotelyThis section describes how you can load the BAAN IV software from a remotetape device.

To load the software, take the following steps:

1 Log on as user root and create the directory in which to load the BAAN IVsoftware, for example, /usr2/tape40b.

Never load the software into a directory in an existing BSE environment, orinto a directory that contains existing BAAN IV tables. If you do so, theinstallation script will crash.

2 Change directories to the directory created in Step 1 and make sure that thetape is positioned at the beginning of the tape. You can use one of thefollowing commands to rewind the tape:

# <remote shell> <system name> �mt -t <remote device> rewind�

− <remote shell>The remote shell command on the local system, remsh on most UNIXsystems, but rcmd on a SCO Unix system, and rshell on a Bull system.

− <system name>The system name of the remote system where the tape is connected.

CAUTION

To install BAAN IV


− <remote device>The tape device name on the remote system. This can either be a rewinddevice or a no-rewind device.

If the mt command is available on the remote system, you can enter thefollowing command at the system prompt to check. If there is no magnetictape manipulation program available, you must use the cpio command forthis purpose:

# <remote shell> <system name> "type mt"

3 Enter the following command at the system prompt to retrieve the installationscript from tape:

# <remote shell> <system name> dd if=<remote device> bs=64k | cpio -icvdB

− <remote shell>The remote shell command on the local system, remsh on most UNIXsystems, but rcmd on a SCO Unix system, and rshell on a Bull system.

− <system name>Tthe system name of the remote system where the tape is connected.

− <remote device>The tape device name on the remote system. The remote device can eitherbe a rewind device or a no-rewind device.

4 Enter one of the following commands to start the mas.read6.1 utility to readthe software from tape:

# sh ./mas.read6.1

# mas.read6.1 -d remote device

5 Press ENTER to skip the screen that contains help information.

6 The following message appears:

Is the streamer connected to the local system "sysname" ? [y]

Press N to continue.


Give the remote-system: [ ]

Type the remote hostname.

NOTE

To install BAAN IV



Give the remote-shell command

Examples: remsh, rcmd, rshell: [ ]

Enter the remote shell that must be used.


Give the username on the remote -system: [root]

Type the logon name that must be used on the remote system.

10 At this point of the installation, mas.read6.1 uses the data you entered inSteps 7 through 9 to try to connect to the remote system. If mas.read6.1succesfully connects to the system, mas.read6.1 then continues the procedurewith Step 11. If mas.read6.1 cannot connect to the remote system, thefollowing message appears. In this example, the hostname of the remotesystem is haro:

System haro is not available for picoPossible causes:1) Check “.rhosts” at “haro” for access this system to “haro”2) Is “haro” filled in “/etc/hosts”?3) Is “pico” filled in “haro:/etc/hosts”?4) Is “remsh” the right remote-shell command?5) Use -l option to specify the username on the remote system.

After this message, mas.read6.1 interrupts the installation. In this case, youmust check the possible causes indicated by mas.read6.1, and restartmas.read6.1 after you solve the problem.

11 The following menu appears, which asks you which option you want toinstall.

Available options with mas.read6.1

1) Select packages and Operating System2) Select only the Operating System3) Select components for Workstations installation

Choice: [1]

For a complete installation of package VRCs and operating systems, Press 1.If you press 2, only an operating system is installed, and if you press 3, onlythe workstation software is installed.

If you press 2 or 3, the mas.read6.1 skips the following steps and continueswith Step 14.

12 A menu appears that asks you which packages you want to install. To installthe displayed packages, press Y. To make another selection, press N.

NOTE

To install BAAN IV


13 A menu appears that asks you which languages you want to install. To installthe displayed languages, press Y. To make another selection, press Y.

14 A menu appears that asks you which operating system you want to install. Ifyou do not want to install the operating system dependent binaries, press 0.Otherwise, select the relevant operating system.

15 You are asked to enter the no-rewind device name of the streamer. Enter thedevice name of the no-rewind device at the remote system.

You will not see this question if you specify the device name at the commandline in Step 4.

16 You are asked if you are sure that the tape is in the tape device. Press ENTERto continue.

17 A message appears that asks you if you want to test the no-rewind device. Forbest results, you must test the device if the entered device name is a realno-rewind device.

18 A message appears that asks you if you want to start to read the tape. Press Y.

19 After the mas.read6.1 utility finishes, you are asked if you want to read morelanguages from tape. To read more languages from tape, press Y. If you pressY, the mas.read6.1 utility asks again which packages and languages you wantto install.

20 After all the required software is read from tape, you are ready to runinstall6.1 to install the software.

NOTE

To install BAAN IV


To install the softwareAfter the software has been read from tape using the mas.read6.1 utility, thesoftware must be installed with the installation script install6.1.

Before you can start the installation, you must have the external RDBMSinstalled on the system. A new database (instance) must be created forBAAN IV. The actual installation of an external database, for example, Oracle,Informix, and DB2, are described in separate installation guides.

To install the BAAN IV software, take the following steps:

1 Log on as user root (do not use the su command) and set the TERM variableto vt100, or any other valid value.

2 If you install under X-windows, the variable DISPLAY must be filled in. Thesoftware is installed under X-windows if the environment variableDS_SERVER has the value bx, or if the installation is multibyte. In all othercases, the software is installed under ba.

3 Change directories to the directory in which the BAAN IV files were read bythe mas.read6.1 script and enter the following command:

# ./install6.1

To stop the selection phase of the installation script, up until the finalquestion Are you ready for installation? appears, press an interrupt, forexample, CTRL+C. You can restart the script as often as you want. From thescript, press ! to activate a subshell. To end this subshell, type exit at theUNIX prompt. You then return to the script at the point where you left off.

Never use the tee command to create a log file. If the tee command was used,the installation script will start the bshell and, no bshell windows will appearon the screen. During the installation, the logfile log.install6.1 is generated inthe directory where the installation was started.

4 After a temporary bse environment is created under the installation directory,you are asked to supply the path to the BSE (Baan Software Environment)directory. Be sure to enter the complete path. The path must have a depth ofat least two directories, for example, /usr2/bse. Do not incorporate anyversion numbers in the path in view of possible future conversions to newerversions.

BSE paths such as /usr2/BAAN4/bse are easy to use. In this case, you caneasily see, in case of more installations, which software belongs to whichenvironment.

NOTE

NOTE

NOTE

NOTE

To install BAAN IV


5 You are asked to specify the environment variable BSE_TMP. Supply thepath or accept the displayed default.

6 The next question asks whether you want to write the values of the$BSE-related variable to the systemwide profile /etc/profile or to the .profilefiles of the individual users. For best results, you must write the values of the$BSE-related variable to the .profile files of the individual users.

7 You are asked to enter the hostnames of the systems for which a license isrequired. The installation procedure displays the name of the local system asdefault. Supply the hostname(s).

8 If multiple database drivers are available, the system will ask you to specify adatabase driver for each company. For external databases such as Oracle orInformix, you are asked an additional question: Do you want to run a specialinstallation script to connect the database (instance) with BAAN IV? Press Y.You then will get a UNIX prompt. For further information, refer to therelevant installation guide for BAAN IV, in the section �To link � toBAAN IV�.

The bisam and btam database drivers cannot be selected together.

9 After the selection of the database drivers, a list of all drivers appears for eachcompany. If the displayed list is correct, press ENTER to continue.

10 You are asked to supply the path for the directories where theDICTIONARY, OPERATIONAL, and DEMO tables (temporarily) must becreated. The tables are stored by company, for example,/usr/tables/<company>. The demo tables themselves are created under thedirectory of the OPERATIONAL tables after the Install Demo Tables(ttiex1290m000) session runs.

11 If one or more localizations were loaded from tape, the system asks whichversion must be placed in the package combination for each package.Remember that at this point all available VRCs are installed, regardless of theVRCs that you choose to include in the package combination. If you fill inthe package combination in the following step, all the packages which will beinstalled for that package combination will be displayed. Note that you mustinstall standard VRCs in all cases. Always choose the latest release of thestandard software, because demo tables rely on their layout. You can buildlocalization Package VRCs and package combinations later.

Do not attempt to combine localizations after the installation. For example,never combine nl10 and glo0 localizations.

NOTE

NOTE

To install BAAN IV


For the Netherlands, the WKA localization (nl10) is mandatory incombination with BAAN IV Finance and BAAN IV Project. In this case, thepackage combination must be B40Lreleasenl10. For a package combinationthat includes the global localization VRCs, create the B40Lreleaseglo0package combination.

If, for one or more package(s), no choice can be made because only one VRCexists, the script skips the question for this package. The package VRC,however, will be included in the package combination.

12 You are now asked to enter the name of the package combination that mustbe created. You must give the package combination a name and descriptionthat refer to the functionality included in the package combination. After youenter the name of the package combination, install6.1 displays the packagesthat will be installed for the package combination.

If only standard VRCs are available, create a standard package combinationwith the name B40Srelease, for example, B40Sc.

13 If the binaries that must be installed can accommodate multibyte, the systemnow asks a number of questions that relate to multibyte. Choose multibyte ifyou want to install languages with multibyte character sets, such as Arabic,Hebrew, Japanese, Chinese, and Korean. First, multibyte will ask whetheryou intend to use multibyte. If you type yes, you must indicate how themultibyte data must be stored, for example, native or TSS (BAAN Superset).If you type no, the system will skip the other questions and ask you if youwant to continue.

14 At this point of the installation, you will be asked if the installation can bestarted. Press Y, then press ENTER to start the installation. Note that thedatabase, other than bisam or btam, must be initialized

An error message can appear that indicates that the preinstallation tool preinstencountered errors. The Preinst utility performs various checks on the UNIXenvironment. You can choose to cancel the installation and tune the UNIXoperating system first, or to continue and tune the UNIX operating systemafter the installation. For a detailed description on preinst, refer toAppendix A.

15 Press ENTER to continue.

NOTE

NOTE

EXAMPLE

NOTE

To install BAAN IV


16 If you specified an external RDBMS database driver in Step 8, refer to thesection �To link .. to BAAN IV� of the relevant installation guide forBAAN IV for further information.If you specified the database driver bisam or btam in Step 8, after about halfan hour, depending on the system, the script will start the Import DataDictionary (ottiex1288) session. At this point, the installation will finishwithout problems, unless you run out of disk space.

Post-installation tasksAfter the installation finishes, you must check the following points:

� If a patch tape was delivered with your software, you must now install thepatch tape. Use the install6.1 script in the directory where the patch tape isread. Before you install the patch, first read the readme file in the patchdirectory. For more information, refer to the installation manual of the patchtape.

� After the installation, the installation directory must be empty. The log filesfor the installation are in $BSE/log. Check these log files, especiallylog.install6.1.

� Make sure the home directories of the standard users are the home directoriescreated during the installation. Modify the .profiles if necessary.


After BAAN IV is installed, you must customize the BAAN IV software. Thecustomizing process includes the following topics:

� To install last-minute updates.� To install the demo dumps.� To create tables for the demo models.� To validate the system.� To install the demo dumps for Orgware.� To initialize parameters.� To reorganize tables.� To configure shared memory.� To create the audit database and to assign tables.� To define the default currencies.� To change passwords.� To install a localization with demo tables.� To set development parameters and authorizations.� To configure the database.� To anticipate shutdowns and restarts.� To set permisions and checks.� Changing code alignment� To configure printers.

These topics are described in the following sections. In the description of thetopics, the use of Baan Windows is assumed.

In the following descriptions, you must use Convert to Runtime several times.Save the changes before you use the Convert to Runtime option.

To install last-minute updatesYou might be required to install several patches after you install the BAAN IVsoftware, and before you import democompanies. Note that the patches aredelivered on a separate medium. You must copy the patch dump from thismedium to the following directory on the BAAN IV server:$BSE/lib/Patches/patch xxx.

In this directory, xxx stands for the number of patch. Note that there can be morethan one patch.

3 To customize the BAAN IV software

NOTE

To customize the BAAN IV software


You must import the patch dump with the the Import Patch (ttiex1284m000)session. Take the following steps:

1 Start BW and log on as bsp.

2 From the Menu browser, click Run Program from the File menu.

3 In the Program/Session field, type ttiex1284m000. Click OK. The followingscreen appears:

4 In the Path Patch File field, enter ${BSE}/lib/Patches/patch001.

5 In the Path Runtime Dictionary field, enter ${BSE}/application.

6 Select the Overwrite check box.

7 In the VRC field, enter B40cx.

The name of the VRC depends on the patch you want to install. For theappropriate name of the VRC, refer to the technical notes.

After the installation is complete, you must run the Create Runtime DataDictionary (ttadv5210m000) session. Take the following steps:

1 From the Menu browser window, click Run Program from the File menu.

2 In the Program/Session field, type ttadv5210m000. Click OK.

NOTE



The following screen appears:

3 In the Package combination field, enter B40Sc in the From field and enterB40cbcl0 in the To field.

4 Select the following check boxes:

− Domains.− Tables.− Reconfigure Tables.− Print Errors.

5 To create the data dictionary, enter the complete range of packages, tables,and sessions, and click Continue.

6 The Select Device (ttstpsplopen) form appears. Select a device and clickContinue. When the session is complete, you will return to the CreateRuntime Data Dictionaries (ttadv5210m000) session. Click Cancel to closethe session.

You can also download additional patches from the Baan Support site on theInternet.



To install the demo dumpsYou can install tables of demo companies, which are provided with theBAAN IV installation. The installer can choose whether to install all demotables, however, for best results, you must perform the proces for company 000.Company 000 is not a demo company, but some relevant data for this companymust be installed. To install the demo dumps, take the following steps:

1 Start BW and log on as bsp.

2 Select the Software Installation menu from the Baan IV Tools main menu.

3 Select Install demo tables from the Miscellaneous menu to start the InstallDemo Tables (ttiex1290m000) session. The following screen appears:

4 In the From field, enter 000. Click the Company To browse arrow.

A screen appears that shows information on all the BAAN companies. Clickthe company you want to install tables for and click OK. To install the demotables for all companies, select the company with the largest companynumber and click OK.



5 Select the Remove Dumps after Installation and Overwrite ExistingTables check boxes, and click Continue.

6 The cursor changes to the hour-glass shape while the demo tables areinstalled. When the cursor once again takes the arrow shape, click Close.

To create tables for the demo modelsYou must now create tables for each company for which you installed demotables in the previous section. Do not include the tabels for company 000. Tocreate these tables, do the following:

1 From the Menu browser, click Run Program from the File menu.

2 Type ttaad4230m000 in the Program/Session field. Click OK.

3 The Create Tables (ttaad4230m000) session appears. Type the democompany numbers in the From and To fields, and click Continue, as shownin the following figure.



4 The Select Device window appears. Choose the device where you wantmessages to appear. For example, type d in the Device field to have messagesprinted to the screen. Click Continue.

5 After the tables are created, click Close.

To validate the systemThis section describes how to validate your BAAN IV system. The followingprocedure assumes that the customer and license code are known. Therefore, theBaan Company must have sent these codes after having received the order form.

To validate the system, take the following steps:

1 Log on as user root.

2 Select Software Installation from the BAAN IV Tools main menu.

3 Click Maintain Requested System Configuration from the Validationfolder to start the Maintain Requested System Configuration (ttiex3100m000)session.

When you are asked to supply a password, enter the default password Yi984.Do not provide the default password to unauthorized users.

4 For BAAN IVc, select Runable for t103 Development Tools. Enter the startdate in the From Date field and press TAB. Enter the end date of yourlicense in the End Date field.

5 Select Maintain Requested System Configuration (Tools) from theValidation menu to start the Maintain Requested System Configuration(Tools) (ttiex3101m000) session. Enter the start date in the From Date fieldand enter the end date of your license in the End Date field. Select therelevant commercial functions and supply the number of users, for the userinterfaces only, in the Number of Users field.

6 Select Print Requested System Configuration from the Validation menu tostart the Print Requested System Configuration (ttiex3400m000) session.Supply the requested information, which is provided by Baan Company, andprint the system configuration.

7 Send or mail this printout to the Baan Company. The printout will be used tocreate the validation key. When you receive this key in a printout or mailfrom the Baan Company, you can proceed with the validation.

8 Select Maintain Security Code/Validation Key in the Validation menu tostart the Maintain Security Code/Validation Key (ttiex3102m000) session.

NOTE



9 Enter the Validation Key (Tools) and the Validation Key Software(Standard).

10 Save and exit the session. Click Validate Toolset on the Validation menu tostart the Validate Toolset (ttiex3220m000) session.

11 Check the license daemon with the command ps -ef | grep licd or licmon6.1-b (you must be logged on as root). The license daemon is a process with thename licd6.1. If necessary, by use the licd6.1 command to start the licensedaemon.

12 Log off as root and log on as bsp. A message appears that informs you thatthe software must be patched.

13 Return to the bshell and select the Software Installation menu from theBAAN IV Tools main menu.

14 Click Configure Application on the Validation menu to start the ConfigureApplication (ttiex3225m000) session. If you see the Sorting... message, thepatch process will finish successfully.



To install the demo dumps for orgwareTo install the demo tables for orgware, take the following steps:

1 Log on as user bsp.

2 Start the Import Version Dump (tgbrg1245m000) session, which is shown inthe following figure:

3 Select the Overwrite check box, and enter the full path to the dump in theFile field.

The demo dumps for orgware reside in the following directory:test/tgB40_c/companynumber/companynumber/tgcompanynumber.imp.Zunder $BSE/test. For example, if the value for $BSE is /usr2/baan, and youwant to import the dump for company 812, the full path will be the following:/usr2/baan/test/tgB40_c/812/812/tg812.imp.Z.

4 Click Import.

5 Enter Yes to the questions that are asked in the session.

After you extract the various demo dumps, you must run the ReorganizeTables (ttaad4225m000) session to reorganize the tables for the democompanies. In the Reorganize Tables session, select the Reference Integrityand Repair Reference Counter check boxes.

NOTE

NOTE



To initialize parametersTo initialize the parameters, take the following steps:

1 Log on as user bsp and switch to a company other than 000. To switch toanother company, select the Change Company option from the Optionsmenu.

2 Select the Run Program option from the File menu, and enter the sessioncode tcmcs0295m000 (Initialize Parameters). Click OK.

3 The Initialize Parameters (tcmcs0295m000) session starts. Click Continue.

4 Repeat Steps 2 and 3 for all demo companies, except for company 000.

To reorganize tablesTo reorganize the parameters, take the following steps:

1 Log on as user bsp and switch to a company other than 000. To switch toanother company, choose the Change Company command from the Optionsmenu.

2 Select the Database Management menu from the BAAN IV Tools mainmenu.

3 Select Reorganize Tables from the Miscellaneous menu to start theReorganize Tables (ttaad4225m000) session and enter a company other thancompany 000, for which all tables and all packages must be reorganized. Inthe Reorganize Tables session, select the Data and Indices, ReferenceIntegrity, and Repair Reference Counter check boxes.

4 Repeat Steps 2 and 3 for all demo companies.

To configure shared memoryTo improve processing speed, you can store frequently used data objects inshared memory, where all running BAAN processes can access them. To storethe frequently used objects in shared memory, take the following steps:

1 Log on as user root.

2 To maintain the shared memory data, select the Application Configurationmenu from the BAAN IV Tools main menu.



3 Select Maintain Shared Memory Data from the Maintenance menu to startthe Maintain Shared Memory Data (ttaad4150m000) session, which is shownin the following figure:

4 In the Shared Memory Data Type box, select Program objects.

5 Select Copy Objects from DD from the Special menu. The Copy ProgramObjects (ttaad4252s000) session appears, which is shown in the followingfigure:

6 Enter package tt in the Package field.



7 Enter B40 in the Version field and c in the Release field.

8 Enter the complete range of dll to dllzzzzzz in the Program field and clickContinue .

The Shared Memory Data (ttaad4150m000) session appears once again. Youmust repeat Steps 4 to 8 for programs stp and dsk, however, you must repeatthe steps for dsk only if you want to use the BW client.

9 After you enter all objects, you must convert this data to runtime. Select theConvert to Runtime option from the Application menu. Note that thischange will not take effect until you restart the BAAN environment. Theinformation you inserted is written to the file $BSE/lib/srdd_tab6.1.

10 Exit the BaanERP session and log on to the BaanERP server as user root.

11 Enter the following commands to reload shared memory:

# cd $BSE/bin# ./srdd_init6.1 �I

Create the audit database and assign tablesBAAN IV includes an audit facility that can log all parameter changes. To usethis audit, you must first create an audit database, and assign tables to thedatabase. To create the audit database, take the following steps:



3 Select Maintain Database Definitions from the Maintenance menu to startthe Maintain Database Definitions (ttaad4110m000) session.

4 Insert a new database named AUDIT. As a description, use AUDIT Database.The type of database depends on the running RDBMS. Select the Audit Trailcheck box. Clear the Force to Read and Copies Present check boxes.

5 Select Maintain Audit File Directories from the Maintenance menu to startthe Maintain Audit File Directories (ttaad4116m000) session.

6 Select All (other) tables in the Table Selection field and insert the pathname for the audit directory, for example, ${BSE}/audit /#. In this path, thenumber sign indicates that for each company a separate directory is createdunder /usr3/audit).

NOTE



7 Select the Convert to Runtime option from the Special menu and close andrestart the bshell.



10 Select Assign Tables to Databases from the Maintenance menu to start theAssign Tables to Databases (ttaad4111m000) session.

11 Insert all the tables that you want to be audited. Note that the database fieldmust be filled in with the name of the AUDIT database. The Table Selectionfield enables you to specify individual tables, all tables in certain modules,and all (other) tables. To insert the mandatory tables, choose the LoadMandatory Tables for Audit option from the Special menu.

12 Click Convert to Runtime on the Special menu. Close and restart the bshell.

To define the default currenciesTo define the default currencies, take the following steps:


2 Select the Application Configuration menu from the BAAN IV Tools mainmenu.

3 Select Maintain Companies from the Maintenance menu to start theMaintain Companies (ttaad1100m000) session.

4 Define the default currency for all companies, for example, USD.

5 Select the Convert to Runtime option from the Special menu.

To change passwordsTake the following steps to change the passwords:



3 Select Change Password for General Table Maintenance from theMaintenance menu to start the Change Password for General TableMaintenance (ttadv0144m000) session.



4 The current password is blank, therefore, press ENTER. Insert the newpassword, for example, baan.

5 Select the User Management menu from the BAAN IV Tools main menu.

6 Select the Developers Data menu.

7 Select Change Password for Developer Authorizations from theMaintenance menu to start the Change Password for DeveloperAuthorizations (ttadv0143m000) session.

8 The current password is blank, so press TAB. Insert a new password, forexample, baan.

To install a localization with demo tablesThis section describes how you can install a localization with demo tables. Thedescription assumes that during the execution of install6.1, no localizations areselected.

Localizations are derived from the standard, and sometimes from anotherlocalization, as indicated in the following table:

Valid localizationsVRC Derived from Derived fromB40Lc_nl10 B40_cB40Lc_sch0 B40_cB40Lc_glo0 B40_cB40Lc_gls0 B40L_c_sch0 B40_c

In the previous table, B40L_b_gls0 is derived from the localizationB40L_b_sch0. The localization B40Lb_sch0 is derived from the standard B40_b.

You cannot have more than one localization in the same package combination.

To install a localization, take the following steps:

The following description assumes that the currencies are installed during theinstallation of the demo tables for the standard.


2 Select the Application Development menu from the BAAN IV Tools mainmenu. Select the Packages and Modules menu.

3 Select Maintain Package Combinations from the Maintenance menu tostart the Select Maintain Package Combinations (ttaad1120m000) session.

NOTE

NOTE



4 Create a localization package combination B40Lcglo. Insert the informationas shown in the following figure:

In this example, /usr4/bse/dict is used as the path for the table definition. Ifthe inserted path for the table definition does not exist, you are asked to createthe path:

−−−− Package Combination: B40Lcglo.−−−− Description: BAAN_IV_c_Global.−−−− Table Definition Path: /usr4/ bse/dict.−−−− Table Def. in Shared Memory: Select the check box.



5 Select Maintain Packages by Package Combination from theMaintenance menu to start the Maintain Packages by Package Combination(ttaad1121m000) session. The following screen appears:

On the Edit menu, select insert, and apply the package combinationB40Lcglo with the following packages:

Package combination Baan IVc GlobalPackage Version Release Customizationcp B40 cps B40 ctc B40L c glo0td B40L c glo0tf B40L c glo0tg B40 cti B40L c glo0tp B40 ctr B40L c glo0ts B40L c glo0tu B40 c

Every package must be included in the package combination because apackage might be using domains from other packages. If these packages arenot included in the combination, the application can run into errors becausesome domains definitions are lacking. In addition, not every package has alocalization VRC. If a package has no localization VRC, you must insert thederived VRC.

NOTE



Usually, the derived VRC is the standard VRC, however, the derived VRCcan also be another localization VRC.

For example, the package combination for the Global Supply Chain is thefollowing:

Package combination for the Global Supply ChainPackage Version Release CustomizationCp B40 CPs B40 CTc B40L C gls0Td B40L C gls0Tf B40L C gls0Tg B40 CTi B40L c gls0Tp B40L c sch0Tr B40 cTs B40 c

6 After you supply the information, click Rebuild DD.

7 Select the Application configuration menu from the BAAN IV Tools mainmenu.

8 Select Maintain Companies from the Maintenance menu to start theMaintain Companies (ttaad1100m000) session.

9 Delete the entry for the localization company. You must delete this entrybecause the installation script has inserted the wrong package combinationfor the localization company. You cannot avoid having the installation scriptinsert the wrong script during the installation because all companies are readfrom tape. For example, if 653 is the company for the global localization, and820 is the company for the supply chain company, you can remove theseentries and then reinsert them with the proper package combinations.

10 Select the company that must be changed, and delete the entry for thecompany.



11 Insert a new entry for the same company. In this sample installation, thefollowing entries would be inserted:

Company Description Currency First Day Packagecombination

653 Global Localisation USD Sunday B40Lcglo820 Supply Chain USD Monday B40Lcsch

12 Click Convert to Runtime from the Special menu to create the$BSE/lib/datecurr file.

13 Select Maintain User Data from the General User Data menu to start theMaintain User Data (ttaad2100m000) session and change the packagecombination and company. In the following figure, the data for BAAN IVuser bsp is changed:

Insert the following information on the Startup tab:

− BW Startup Program: Startup Program (GUI): Menu browser.− Startup menu (ASCII): tttls0000m000 General menu.− Levels to load at Startup: 1.



14 Note that only the most important fields are listed in the previous list. Afteryou supply the information, you must choose the Convert to Runtime DataDictionary option from the Special menu.

15 Exit the bshell and log on again as user bsp.

16 Select the Software Installation menu from the BAAN IV Tools main menu.

17 Select Install Demo Tables from the Miscellaneous menu to start the InstallDemo Tables (ttiex1290m000) session.

18 Supply the following information to install the demo tables:

−−−− Company From : 653.−−−− Company To : 653.−−−− Remove Dumps after Installation: Clear this check box.−−−− Overwrite Existing Tables: Clear this check box.

19 After you supply the information, click Continue.

You must use a separate procedure to insert the data for the orgwarepackages, as described in �Extracting the demo dumps for orgware,� inChapter 3, �To customize the BAAN IV software.� Note that you mustextract the proper file, which is tg550.imp.Z for this example installation.


21 Select Reorganize Tables from the Miscellaneous menu to start theReorganize Tables (ttaad4225m000) session and enter the company, in ourexample 653, for which all tables for all packages must be reorganized. In theReorganize Tables session, select the Data and Indices, ReferenceIntegrity, and Repair Reference Counter check boxes.

22 Enable auditing for the new company. For a description how to enableauditing, refer to �To create the audit database and assign tables,� in Chapter3, �To customize BAAN IV software.�

23 Exit the bshell and log on again as user bsp.

NOTE



Set development parameters andauthorizationsIn this section, you can find definitions for the development parameters andauthorizations. However, the following data serves merely as an example.


2 Select the User Management menu from the BAAN IV Tools main menu.

3 Select the Developers Data menu.

4 Select Maintain Development Parameters by User from the Maintenancemenu to start the Maintain Development Parameters by User(ttadv0110m000) session.

5 In the Maintain Development Paramters by User session, you can enter thefollowing values in the Commands and Options section for all standardusers:

−−−− Editor Read-Only Command: View.−−−− Editor Read/Write Command: View.

Use the default values for all other entries.

6 Select Maintain General Developer Authorizations from the Maintenancemenu to start the Maintain General Developer Authorizations(ttadv0142m000) session. Note that you will be asked for a password.

7 On the Edit menu, select insert. Insert the users bsp and tools to providethese users with authorization for all package VRCs. No other standard usercan have this authorization.

8 Select Maintain Developer Authorizations by Package VRC from theMaintenance menu to start the Maintain Developer Authorizations byPackage VRC (ttadv0141m000) session.

9 For all users except bsp and tools, enter the authorizations for specificmodules or all modules, for the relevant derived-from packages.

10 Select Change Current Package VRC of User from the Maintenance menuto start the Change Current Package VRC of User (ttadv0140m000) session.

11 For all users, except for user root, choose the relevant package. Select theOnly show current VRC check box for all users, except for bsp and tools.



To anticipate shutdowns and to rebootYou can adjust the machine settings so that BAAN IV automatically stops incase of a system shutdown, and starts at boot time. The type of OS you usedetermines the correct way to adjust these settings.

In addition, take precautions to stop and start external databases if present. Thestrict rule is that you must start the external databases before BAAN IV, and thatyou must stop the external databases after BAAN IV is stopped. Consider thepossibility that the external database is used with other programs than BAAN IV.

Test whether rc.stop and rc.start run properly upon shutdown, and restart of thesystem.

Set permissions and checksThe binperm6.1 script sets the right permission for the files in the $BSE/bindirectory. You must run this command by user root.

A common problem is that after you patch the tools as user root, the permissionsfor the BAAN IV Tools main menu, mtls1000m0001language code, are set toroot:sys instead of bsp:bsp.

As a result, the user tools is unable to read the Startup menu. This problem is notaddressed by binperm6.1, because binperm6.1 only checks $BSE/bin. You mustcorrect these permissions manually. To change the permissions, log on as userroot, change directories to $BSE/tools/ttB40_b/mtttlslanguage code, and enterthe following command:

# chown bsp *# chgrp bsp *

The language codes are 1 for Dutch, 2 for English, 3 for German, 4 for French,and so on

To configure a printerThe following section describes how to configure a printer in Baan on a UNIXmachine.

The printer (type) must be defined, as well as the printer code in BAAN and theUNIX printer queue that the printer must serve. The printer must be operationalon UNIX level before you can configure the printer.



To configure a printer, take the following steps:

1 Log on to BAAN IV and select Device Management from the BAAN IVTools main menu.

2 Select Maintain Device Data from the Maintenace menu to start theMaintain Device Data (ttaad3100m000) session.

3 Enter the desired data, for example:

− In the Device field, specify the desired code for this printer that the enduser must select in BAAN, for example, PNL0256.

− In the Description field, enter the full description for the printer.

− The Locale field indicates the character set. Use the browse arrow toselect the appropriate set.

− In the Driver field, select the appropriate driver from the subdirectory of$BSE/lib/printinf, for example, hp_lj4.

− In the Device Queue field, enter the correct path, for example, /usr/bin/lp.Enter the name of the printer queue on UNIX level, for example, pr1062.

Enter the other parameters and data as shown in the previous figure.




This chapter provides the start and stop scripts for the BAAN IV software

Run level methodThis section contains the script for the run level method.#!/sbin/sh### Start/stop BAAN <version> environment# BAAN Nederland B.V. <date># HP-version

BSE=/usr1/bsePATH=/sbin:/usr/sbin:/usr/binexport PATH

case $1 in'start_msg')

echo "Starting BAAN <version>";;

'stop_msg')echo "Stopping BAAN <version>";;

'start')if [ -f $BSE/etc/rc.start ]then

rm -f $BSE/tmp/rc.start_donesh $BSE/etc/rc.start

fi;;

'stop')if [ -f $BSE/etc/rc.stop ]then

rm -f $BSE/tmp/rc.stop_donesh $BSE/etc/rc.stop

fi;;

*)echo "usage: $0 {start|stop|start_msg|stop_msg}";;

esac

exit 0

4 Scripts

Scripts


Direct methodThis section contains the script for the direct startup and shutdown methods.

StartingThis section contains the script for the direct startup method.

# Initialize BAAN <version> environment# BAAN Nederland B.V. <date>if [ -f $BSE/etc/rc.start ]then

rm -f $BSE/tmp/rc.start_doneecho “Starting BAAN IV”sh $BSE/etc/rc.start

fi

StoppingThis section contains the script for the direct shutdown method.

# Stop BAAN <version> environment# BAAN Nederland B.V. <date>if [ -f $BSE/etc/rc.stop ]then

rm -f $BSE/tmp/rc.stop_doneecho “Stopping BAAN IV”sh $BSE/etc/rc.stop

fi

GeneralRc.stop does not stop the license daemon, and, therefore, if you do not restart thesystem, rc.stop produces an error message on rc.start. The message reads�License daemon already running.�

In addition, the pdaemon can produce an error message that reads �Alreadyrunning or pd_lock not removed.� Remove the pd_lock, for which the path,$BSE/tmp is mentioned in the message, and start the pdaemon withpdaemontools_version. For example, for BAAN IV, use pdaemon6.1.

To check whether the license and printer daemons are running, type thefollowing: ps -ef | grep lic and ps -ef | grep pdae.


This appendix describes the functionality of the Preinst utility. The install6.1script starts this utility, and checks the server environment during the installationof BAAN IV. You can also start the Preinst utility manually to check anoperational BAAN IV installation.

The following sections describe the various possibilities when you use thePreinst utility.

To run Preinst during, or immediately after,BAAN IV installationDuring an installation or update of the BAAN IV software on a UNIX platform,the install6.1 installation script calls the Preinst utility.

The Preinst utility is part of the BAAN IV installation process, and is used toperform various checks on the UNIX environment. The checks Preinst performsconcern the following:

� Kernel parameters.� Checks of singlebyte/multibyte database.� Disk space.� Maximum file size.� Required standard users.� TCP/IP configuration.� Environment variables.� Run-time environment versus data dictionary.� Options to speed up installation.� Data installation.� Checks of tables.� VRC customization.� Client/server installation.� Existence of fixes.

5 Appendix A: The Preinst utility

Appendix A: The Preinst utility


The Preinst utility uses the values in the kernel_cfg file to check the itemsprovided in the previous list. The kernel_cfg file contains the minimal kernelparameters of the system. This file is installed in the $BSE/lib file. If Preinstdetects that the current value of a parameter is less than the value defined in thekernel_cfg file, a warning appears. After all of the checks are complete, if one ormore errors are detected, Preinst displays the following message:

Errors found during system check, continue?

You can choose one of the following options:

� Cancel the BAAN IV installation software and tune the UNIX operatingsystem before you restart the BAAN IV installation.

� Continue the BAAN IV installation, and tune the UNIX operating system,after the BAAN IV installation is complete. You are not required to writedown the warnings that Preinst generates, because those messages are writteninto the $BSE/log/log.preinst file.

While Preinst runs, you are asked if you want to check all the BAAN IV tables,including those in the run-time environment, or only those in the data dictionary.

NOTE



The following script shows how the $BSE/lib/kernel_cfg file is set up. The nameof each parameter is followed by a formula to extract the current value of theparameter, an operator, and a condition.

# Kernel configuration file# Version 6.1# rklip, 23-09-1996# Updated for HPUX10.0 and IBM AIX4.1# Entries that must exist:# Machine-id# OS-release# Kernel# Kernel type# MEMORY# USERS# MAXFSIZE output in Mb's# CMD df <device name> <size in Mb's> <filesystem># don't use in the df command definition awk with printf!# CMD ping must give percentage packet loss, if not don't# define the commandMachine-id: HP9000_PA_RISCOS-release: HPUX9.0Kernel: /hp-ux# Configuration files in order of checking firstKernel configuration files: /etc/conf/gen/S800, /etc/master# Kernel type: 1 = static, 2 = static/patch, 3 = dynamicKernel type: 1# Internal memoryMEMORY:CURRENT: `/etc/sysdef 2>/dev/null | grep "physical memory is" \

| awk '{print $4}'ÒPERATOR:CONDITION:# Number of Triton usersUSERS:CURRENT: `ksh -c "if [ ! -f /.brand/brand6.1 -o ! -f ${BSE}/bin/licmon6.1 ]; \

then echo 2; else licmon6.1 -b | \grep users | awk '{TOT += $4}END{print TOT}'; fi"`

OPERATOR:CONDITION:# nprocNPROC:CURRENT: `/etc/sysdef 2>/dev/null | grep -i nproc | cut -d= -f 2ÒPERATOR: geCONDITION: 64 * USERS# maxuprocMAXUPROC:CURRENT: `/etc/sysdef 2>/dev/null | grep -i maxuprc | cut -d= -f 2ÒPERATOR: geCONDITION: 64......



To run Preinst in an operational BAAN IVenvironmentYou can also use the Preinst utility to perform checks on an operational systemthat runs on BAAN IV. To use Preinst in an operational BAAN IV environment,take the following steps:

1 Select the Run Program option from the File menu to run the ottiexpreinstsession and run the Preinst utility at regular times.

2 Use the information in the $BSE/bse/ log.preinst log file to retune yourserver. For a description of how to solve the errors listed in the log.preinst logfile, refer to the Kernel Tuning Guide BAAN IV (U7032AUS).


This appendix describes how to install Baan Windows. Baan Windows (BW) is agraphical user interface program in BAAN IV. BW runs on an Intel-compatiblePC in a Windows 95 or Windows NT environment. BW displays BAAN IV as anapplication with the same look and feel as a native MS-Windows application.

This appendix describes the following topics:

� Hardware and software requirements.� How to install the Baan Windows software.� How to configure the Shared Memory Manager.� How to uninstall the BAAN IV software.

Hardware and software requirementsThe following software and hardware requirements must be met before you caninstall BW.

� The operating system Windows 95 or Windows NT Server Version 4.0 mustbe installed and running.

� The system on which Baan Windows is to be installed must be at least anIntel-based system with a 486DX processor running 50 Mhz. In addition,Baan Windows requires at least a SVGA video display, 16 MB of mainmemory (RAM), and 2 MB of free disk space.

� A network adapter, as recommended by the supplier of the TCP/IP stack.

� The TCP/IP network software must be installed and running, and the TCP/IPstack must support Windows Sockets level 1.1.

6 Appendix B: To install Baan Windows

Appendix B: To install Baan Windows


To install the Baan Windows softwareTo install the Baan Windows software, take the following steps:

1 If you have a UNIX BAAN IV server, you can use ftp to copy the BaanWindows software from the $BSE/mswindows/bw/setup directory on theserver to the client.

2 Use ftp to copy the $BSE/mswindows/bwzip.exe file from your BAAN IVUNIX server to a temporary directory on your local system, for example,C:\TEMP.

3 Run BWZIP.EXE to extract the Baan Windows software.

4 Choose Run from the program manager File menu and enter the followingcommand in the Command Line box. In this example, C:\TEMP is used asthe temporary directory:C:\TEMP\SETUP.

5 The Welcome dialog box appears.

6 Click Continue. The Choose Destination Location dialog box appears.Accept the default path, or enter another path name.

7 After the software installation is complete, click OK to exit the installationscript. The BAAN IV program folder appears. Double-click the BWConfiguration Tool icon. The BW Configuration dialog box appears, asshown in the following figure.



8 Fill in the following information:

On the Application Server tab:

− Hostname:Enter the host name of the BAAN IV server.

− Connect As:Enter a valid user name, as known on the BAAN IV server.

− Ask password at startup:If you select this check box, you can only supply the password during theBAAN IV logon procedure.

− Use saved password:If you select this check box, BAAN IV skips the logon procedure, and thesaved password is used.

− Current user:If you select this check box, you will log on the BAAN IV Windows NTserver with the user name with which you are logged on to the localsystem (Windows NT only). BAAN IV also checks whether the localWindows NT system belongs to the same domain as the BAAN IVWindows NT server. This option is not applicable for BAAN IV UNIXservers.

− BSE:Enter the path to the BSE environment on the BAAN IV server. The pathname is equal to the BSE environment variable on the BAAN IV server.

− Bshell name:Enter the application logic to use on the remote BAAN IV host. Changesto the default of bshell are only useful during debugging.

− Command:Enter the option you want to pass to the bshell. For example, you can usethe following syntax to define environment variables:

-- -set Environment Variable1=xxx -set Environment Variable2=yyy

On the NLS tab:

− Locale:Select the character set that must be used, which is the defaultInternational (ISO).



On the Font tab:

− Font type:Enter the desired font type. To change the setting, click Change.

To add multiple configurations, press the Save as button to save the newconfiguration in a separate configuration file. However, you can only use oneconfiguration at a given time.

9 Click Run to start your BAAN IV session.

The BAAN IV .bwc files are registered by the Windows NT or Windows 95operating system. As a result, you can double-click the icon in front of therelevant .bwc file in the file manager to start a BAAN IV logon procedure.You can also iconize a .bwc configuration file. Simply drag the configurationfile�s icon to the file manager and add the file to a program group.

Installation directory of Baan Windows (BW)The installation directory C:\BAAN is created during the setup process of BaanWindows (BW). During setup, you can alter the home directory of BaanWindows. In this section, the name for the installation directory of BaanWindows must be set to the default.

Next, the following additional subdirectories are created in the C:\BAANdirectory during setup:

� C:\BAAN\BIN:Contains the CONFIG32.EXE configuration program and the BW.EXEprogram to start the BAAN IV application.

� C:\BAAN\LIB:Contains the following files:

−−−− BW.INI:The initialization file.

−−−− BW.REG:The object registration file.

−−−− BW.TLB:The information for OLE automation.

−−−− TSS_C6.1:Language support.

−−−− TSS_LOC6.1:Language support.

NOTE

NOTE



−−−− BWLOGO.BMP:The BAAN logo.

�� C:\BAAN\LOG:Contains logging information about Baan Windows.

�� C:\BAAN\SAMPLES:This directory contains a number of spreadsheets that you can use to loadExcel data into BAAN IV using BAAN IV dynamic link libraries.

�� C:\BAAN\TMP:Contains the temporary files.

�� C:\BAAN\HELP:Contains the help files.

The following subdirectories are created in the C:\BAAN\LIB directory duringsetup:

� C:\BAAN\LIB\LOCALE:Contains the multibyte languages SJIS support file.

� C:\BAAN\LIB\NLSINF:Contains the special character set file XWINDOWS.IN.

� C:\BAAN\LIB\USER:Contains the configuration files.

Baan Windows (BW) environment variablesDuring the installation of the user-interface program Baan Windows, theenvironment variables BSE and BSE_TMP are set. The BSE variable points tothe Baan Windows installation directory, and the BSE_TMP variable points tothe temporary directory under the installation directory.

Under Windows NT, to check these environment variables, double-click theSystem icon in the control panel. Under Windows 95, you can run theREGEDIT command to check the Baan Windows environment variables.




This appendix contains a list of errors you can encounter during the installationand configuration of the BAAN IV software on a Unix platform. Eachdescription of an error supplies an example, the possible cause, and anexplanation of how to solve the problem.

Error 1: Not ownerThe user is a non-superuser, or is not the owner of the process.

Error 1 can be a program error. In this case, please contact Baan Company. Ifyou do contact Baan, be sure you have the session name in which the erroroccurred with you. In addition, try to create a screen shot, which shows the errormessages, and which includes the relevant part of the log file.

Error 1 in tiitm0101m000:First, make a screen shot of this screen. You must redirect the output to a printer.The second step is to retrieve information from the log files.

Error 1 can also be a UNIX permission problem. In this case, you must changethe permissions, owner, or group of a file or directory.

Error 1 in titm001:Change directories to the correct directory in UNIX to find this table (titm001).You can retrieve the directory name from the Maintain Table Directories(ttaad4115m000) session in the Database Management menu of BAAN IV Tools.This session tells you where this table is installed. Simply look at the companynumber to find out where the table is installed. After you find this table, checkthe permission, owner, and group of the table, but also from the directory inwhich this table is installed. The owner and group of the table and directory mustbe user bsp, the permission of the table must be 660 (-rw-rw----), and thepermission of the directory must be 770 (drwxrwx---). If not, change thesepermissions with the chmod, chown, or chgrp commands.

7 Appendix C: Troubleshooting

EXAMPLE 1

EXAMPLE 2

Appendix C: Troubleshooting


Error 2: No such file or directoryThe bshell cannot find the file or directory.

If error 2 occurs, the file or directory can be missing. In this case, you mustcreate the file or directory, or restore the file or directory from backup. If a tableis missing, check the company number as well. Your current company number isdiffers from the company number the bshell is looking for. (For examplecompany number 000).

Error 2 in tcom000:You must use the database manager provided with this database to check whetherthe database is an external database. For example, suppose you use BAAN Baseor BAAN Base TP and your current company number is 200. According to thedatabase manager, the directory in which the table tccom000200 must beinstalled is /usr2/bsp6.1. Check whether a table is available in the/usr2/bsp6.1/ttccom directory. A file such as tcom000200 with the extension .bdtmust be available.

If the table exists, but the error message still occurs, the bshell is trying to findthe table tccom000000, in other words, in company number 000. Now, you mustuse the method described previously to check whether this table exists. If not,you must create use the Database manager in BAAN IV Tools to create thistable.

If a form, report, object, source, or include file is missing, you must restore thisfile from your backup, or BAAN IV Tools to create the file. To create the file, goto Application Development, and select one of the managers, through whichyou must create the runtime component

The file or directory does exist, but the error still occurs. This means thatsomething is wrong with the redirection of the files.

Error 2 in fcom0101m000:In this case, the form fcom0101m000 is missing. If the run-time form exists, forexample, $BSE/application/tcB40_b /ftccom/fcom0101m0002, you must checkthe redirection. This can only be the case for menus, forms, reports, object, reportsources, object sources, functions, table descriptions, and tables. Otherwise, anerror 2 message simply means that the file or directory is missing.

Check your redirection as follows:

First, check which package VRC and package combination the missingcomponent belongs to. Use User Management and Maintain Packages byPackage Combination to look for your current package combination, and thepackage VRCs that belong to this package combination. Start the Maintain

EXAMPLE 1

EXAMPLE 2



Directories of Software Components session in Application Development,Packages and Modules.

Look for the package VRC in which the missing component exists. If thecomponent group is redirected correctly, the runtime redirection file might beincorrect. The file is $BSE/lib/fd6.1.<PC>, in which PC stands for the packagecombination, for example, B40Sb. To create or recreate this file, start the CreateRuntime Data Dictionary session through the menus Application Developmentand Runtime Data Dictionary.

If the component group is not redirected, or if the component group is incorrectlyredirected, you must redirect the component group through the MaintainDirectories of Software Components session, and create or recreate the runtimeredirection file as described previously.

Error 5: I/O errorA physical I/O error occurred.

This error can occur while you read a tape. This error means that the tape devicecannot read the tape. If this error occurs while you start to read the tape, theoptions that you use might be incorrect, or the block size used by the device canbe wrong.

The command to read the tape is listed in a covering document. In nearly allcases, Baan uses the cpio command to create tapes. For the correct command,refer to this covering document. For example, suppose this command is thefollowing:

$ cpio -icvdB < /dev/device

You must use all of these options. Try once again to read the tape with theseoptions.

If this does not solve your problem, the block size that your device uses candiffer from the block size used by Baan. The default block size is 64 KB for4mm tapes. If the block size is different, the block size will be listed in the samecovering document. You must check/change this block size by the systemadministrator. After you check/change the block size, you must try to read thetape again with the correct command and options as listed in the coveringdocument.

Clean your device. If you do not know how to clean the device, contact yourhardware vendor.



If error 5 occurs after you have already read a part of the tape, the tape can bedamaged. There is just one option to read the tape. Type the following command:

$ dd if=\dev\device of=dump

In the previous script, device is the name of the tape device, and dump is simplyan example file name. This file must not exist in your current directory.

This command will create a file called dump in your current directory with thecontent of the tape. If this command finishes successfully, you can use the samecommand as you used to read the tape to try to read this file. Suppose thecommand on your covering document is the following:

$ cpio -icvdB < /dev/device

Read the file dump with the following command:

$ cpio -icvdB < dump

The file dump must still be in your current directory. If the error 5 still occurs,the tape can be considered damaged, therefore, you must request another tape.

The problem can also be on your hard disk, for example, a bad block. To find outwhether the problem is with your hard disk, contact your hardware vendor.

Error 6: No such device or addressThe device accessed by a command is not physically present, or the address ofthe device is not present.

The program tries to access a device that is not present at all. For example, aprogram tries to access a tape streamer, but by accident the program accesses thewrong streamer. In that case, you must correct the program so the programaccesses the correct streamer the next time.

Another possible cause for this problem is that although the accessed device isavailable physically, the device is not present in the kernel. On most UNIXmachines, you can use the system administrator tool to check whether the deviceis present on the kernel. The tool shows you which devices are active on yoursystem. If the device that you are looking for is not active, you must set up thisdevice, if necessary with the help of your hardware vendor.

Another possible cause for this error is can be that the major and minor numberof the device is wrong. If the major and minor number is wrong, the device isphysically connected and the device is active according to the kernel, but thosenumbers are wrong. Your hardware vendor must check whether this is the actualcause of the error.



The permissions of the device are not correct. The permissions must be 666(crw-rw-rw-). To check the permission, you must check the device file. Forexample, suppose the device name is /dev/rmt/0m. You must go to the /dev/rmtdirectory and use the following commands to check the permissions of the 0mdevice file:

# cd /dev/rmt# ls -asl 0m

These commands show you the permissions as 666 (crw-rw-rw-). If not, tocorrect the values of the permissions, use the following command:

# chmod 666 0m

After you use this command, error 6 must be solved.

Error 7: Arg list too longThe argument list of the invoked UNIX command is too long.

You can use an argument together with nearly every UNIX command. If thenumber of arguments is too large, error 7 occurs. In particular, this error occursespecially quickly if you use shell scripts. Try to program your script in anotherway, without shell scripts.

Suppose the layout of your script is like the following:

for i in tt????

do

ls $i/*.bdt >> file

done

The purpose of this script is to retrieve a file that contains all the data files in acertain directory structure. As soon as you execute this script, you can receive anerror 7, because the ls command cannot handle that many arguments, which arethe data files in the various directories. A better way to program in this case is touse the following script:

for i in tt

do

for j in $i/*.bdt

do

ls $j >> file

done

done

The purpose is still the same as the purpose of the first script, but the number ofarguments of the ls command are less than in the first example.

EXAMPLE



Error 8: Exec format errorA program with the correct permission is started, but the program does not startwith a valid magic number.

You must check whether the program name is typed in correctly, and whetheryou are using the correct options. You can also be almost out of disk space. Usethe following command to check your available disk space:

# df

If not enough disk space is available in the root (/) file system, or in the filesystem that you currently are in--check this with the pwd command, the first partof the output shows you the file system--you must reorganize your disk and try torerun your program.

Error 9: Bad file numberA program tries to write or to read a file, however, the program cannot read orwrite the file because of an incorrect file descriptor.

Because of a bad file descriptor, a program cannot properly access a file ordevice. Error 9 is a program error, therefore you must contact Baan. In somecases, however, error 9 is a permission problem. Check the permission of thefile/device accessed by the program. First, you must check the BAAN IV logfiles to find out the file that is accessed by the program. To find out which file isaccessed by the program, enter the following commands:

$ cd $BSE/log$ ls �ltr$ tail -50 log.xxx

The ls program shows you the last modified file. Now, use the tail command tocheck the content of the last modified file.

Look for error 9, and search for a file accessed by the program that causes theerror. If this message gives you the file accessed by the program, you must checkthe permissions. The file name determines where you must look to find thesepermissions. If you are not sure where to look for the permissions, check thedirectory structure in this document. Use the following commands to check thepermissions:

# cd directory# ls -als file



The permissions must be the following:

owner: group: permission:

files bsp bsp 660 (-rw-rw----)

directory bsp bsp 770 (drwxrwx---)

executables bsp bsp 755 (-rwxr-xr-x)

($BSE/bin)????

To change the owner, group, or permission of a file/directory use the chown,chgrp, or chmod commands.

Error 11: No more processesThe system tries to create another process, however, no other processes areavailable.

As a result, you must increase the kernel parameter NPROCS, which is thenumber of processes. By default, the value in this parameter is 64 * BAAN UserLicense. However, there can still be insufficient processes available. After all,other applications running on your system also require processes. In this case,you must use the system administrator to increase the NPROCS parameter.

If the used database is BAAN Base or BAAN Base TP, you can change theconfiguration file $BSE/lib/bisamconfig. The first parameter in this file,PROCESSES, represents the maximum number of processes. By default, themaximum number of processes is:

In case of BAAN Base : 18 *

BAAN User License

In case of BAAN Base TP : 30 *

BAAN User License

If you want to change this parameter, remember to run $BSE/etc/rc.stop to stopthe database. Run $BSE/etc/rc.start after the change. You must maintain the file$BSE/etc/bisamconfig by tbase6.1 or tbase_tp6.1. Before you can maintain thefile, you must always backup this file.



Error 12: Not enough spaceA program requires more memory space than is currently available, or requiresmore swap space than is available.

Error 12 indicates that you do not have enough address space, which is a kernelparameter. You must use the system administrator to increase the MAXUMEMparameter, which controls the maximum size of users virtual address space.

Another possible source for error 12 is if you do not have enough swap spaceavailable. By default, the minimum swap space required is 2.5 * internalmemory. If several BAAN users logon to BAAN simultaneously, you often mustuse the system administrator to increase the swap space.

Error 13: Permission deniedYou do not have the permission to read, write, or run the file.

Error 13 occurs if the user tries to read, write to, or execute a file if UNIX doesnot enable the user to do so. In this case, the user must invoke the UNIXcommand chmod, chown, and chgrp to change the permission, owner, or group.The file mentioned with the error message or the directory structure above maycause the problem. You must check the permissions. In general, the permissionsmust be the following:

directories : 775 (drwxrwxr-x)

files : 660 (-rw-rw----) *)

owner : bsp

group : bsp

*) files in $BSE/bin: 775 (-rwxrwxr-x)

files in $BSE/etc: 775 (-rwxrwxr-x)

Error 13 in log.bshell6.1:Error 13 occurs if the bshell6.1 tries to write a message to the$BSE/log/log.bshell6.1 file, even though the bshell does not have writepermissions. Change directories to $BSE/log, and change the permission of thefile as follows:

# chown bsp log.bshell6.1# chgrp bsp log.bshell6.1# chmod 660 log.bshell6.1

EXAMPLE



Error 22: Invalid argumentA UNIX instruction used an invalid argument.

Most often, error 22 occurs if you try to initialize shared memory and/or adatabase. In this case, you must maintain the kernel.

At the moment, shared memory and/or a database is initialized, the output is asfollows:

Error 22

Check if enough semaphores / shared memory available

To solve error 22, refer to the description of error code 28, which reads �Nospace left on device.�

Error 23: File table overflowThe table that contains the open files is full.

Error 23 occurs if the system tries to open more files than the system table cancontain. This error does not mean that the system cannot open more files than areopen at the moment this error occurs. However, the table that contains the openfiles requires more entries.

At the moment a user starts a session, for example, tiitm0101m000, the followingerror occurs:

Error 23 in tiitm0101

If error 23 occurs, you must increase the kernel parameter NINODE, whichdenotes the number of i-node table entries to allocate. Several factors can affectthe value of this parameter. In general, you can say the more the number of userswho are active at the same time, or the more processes the average user startssimultaneously, the more open file entries you require. Therefore, the value ofthe NINODE parameter depends largely on the system usage.

EXAMPLE

EXAMPLE



Error 24: Too many open filesThe BAAN software tries to open too many files.

This error means that the UNIX kernel does not enable anyone to open any file.You must increase the number of open files in the kernel with the systemadministrator tool. Change the NFILE and/or NOFILES parameters. Theparameter NOFILES, which provides the maximum number of open files perprocess, must have a value of at least 256. Although 256 is the minimum value,you most often must increase the value. Also, think of the resources required byother applications. The value of the NFILE parameter, which is the number ofopen files system wide, must at least be: (NOFILES * BAAN User License * 3)+ 100. Note that this value is also a minimum, therefore you might need moreopen files in your case than described previously.

Error 27 - File too largeA process tried to write a file that was too large.

A process tried to write a file, which has become too large, according to theUNIX parameter ulimit. This parameter determines the maximum file size on theUNIX system, and can be set per user. The purpose of this parameter is to avoida program error from creating a file which will become too large in the end, andfill the disk completely. If you are sure that this is not an error, you can increasethe maximum file size.

Error 27 in log.oracleThe oracle driver tried to write a message into the log.oracle file, however, thisfile will become too large. The solution is to invoke the UNIX command ulimitand increase the limit:

# ulimit 2000000

From now on, the maximum file size is 2 million bytes. Remember that in mostcases only the superuser can enter this command. You can also insert thiscommand into the /etc/profile file, so that the next time anyone logs on to thesystem, the file size is automatically 2 million.

EXAMPLE



Error 28: No space left on the deviceNo space is left on a device, or not enough memory is available.

Not enough disk space is available. The Baan software tries to write data to afile, which can already exist, but not enough disk space is left.

Error 28 in BSE/log/log.bisam:For any error, a message is added to the $BSE/log/log.bisam file. Because notenough disk space is available, you cannot add the message. You must now freeas much space on your hard disk as possible. If not enough disk space isavailable after you reorganize your hard disk, you must arrange an additionalhard disk.

Not enough (shared) memory is available on your system. Increase the number ofshared memory segments, or increase the buffer size, which can cause kerneladjustments. Only in a few cases it can be necessary to increase the size of theinternal memory.

During the initialization of shared memory and/or a database, the following errormessage can occur:

Error 28

Check if enough semaphores / shared memory available

You can solve this error in several ways:

First of all, try to increase the number of shared memory segments. To increasethese segments, change directories to $BSE/lib and maintain the shm_param file.

The following script includes an example for the IBM_RIOS_6000 platform:

default:;

{

}

IBM_RIOS_6000:;

{

}

IBM_RIOS_6000/AIX3.2:;

{

SHM_START = 30000000

SHM_STEP = 10000000

SHM_BUFSIZE = 512

SHM_MAXMEM = 15

}

EXAMPLE 1

EXAMPLE 2



In this example, you have 15 shared memory segments available. To try toincrease this number, edit this file with any text editor. Always backup the filebefore you edit. Log on as user root and run $BSE/etc/rc.stop. Modify the$BSE/lib/shm_param file, and run $BSE/etc/rc.start. This initialization, whichrc.start carries out, can fail. As a result, you must maintain the kernel, andincrease the value of the SHMSEG variable, which designates the number ofshared memory segments per process.. This value must be equal to the value ofSHM_MAXMEM in the file $BSE/lib/shm_param. Therefore, if you need 25shared memory segments for BAAN, you must increase the value of theSHMSEG parameter in the kernel to 25. Next, increase the value ofSHM_MAXMEM to 25 in the $BSE/lib/shm_param file. Remember that themaximum value of SHM_MAXMEM is 30.

Another solution is to increase the buffer size. The current buffer size is 512. Thevalue of SHM_BUFSIZE in the file $BSE/lib/shm_param. You can increase thisvalue to 1024. Remember to run $BSE/etc/rc.stop and $BSE/etc/rc.start again, tomake the changes effective. Again, this can result in maintaining the kernel toincrease the value of the previously mentioned parameters as well.

Another solution is to increase the size of the internal memory. If you do so, youstill must maintain the kernel and the file $BSE/lib/shm_param to increase thesize of shared memory.

If the database you use is BAAN Base or BAAN Base TP, you can check thecontents of the $BSE/lib/bisamconfig file before you start to modify the$BSE/lib/shm_param file or the kernel.

Error 35: No message of desired typeThis error means that no message of the desired type is available.

This error typically occurs if you have mounted disk drives. This error canhappen if you try to distribute a database on this mounted disk, especially if thedatabase tries to lock tables. Check your log files in the following way:


The ls command shows you the last modified file, and the tail command showsyou the last 50 lines of this file xxx.

Look for the error 35. Error 125 can also be mentioned, which means that youcannot use mounted disks. Use the BAAN IV Network facility instead tomirror/distribute your database.

NOTE



If your database is Informix, DB2, or Oracle, the database driver might try toread a record that is not available. In this case, contact Baan.

Error 45: Deadlock situationdetected/avoidedThe maximum file size limit has likely been exceeded.

Every computer system has a maximum file size, even per user. You can checkthis with the following command:

# ulimit 1000000

The maximum file size, in this example, is 1 million bytes. Note that if you logoff, this limit is gone. For best results, you must change this limit throughout thesystem. Contact your system administrator to change the limit.

However, you must be careful when you change this limit. Suppose a programerror causes the problem. If you increase the file limit, you will again run intotrouble after some time. After this happens, you are quite sure this is a programerror. This problem can also occur if you insert a large number of records into atable, which then becomes too large as a result. Try to remove unused records ofthis table, and reorganize this table. If no records are unused, you mustreorganize this table as well. The way to reorganize a table is as follows:

The table that causes the error is tiitm001500, as shown in the followingexample, where DBASE is the database of the table:

$ bdbpre6.1 -dDBASE -r -Ntiitm001 -C500 > dump

You must run the Assign Tables to Database session through the BAAN IVTools Database Manager to check the database.

Backup the table before you run the following command:

$ bdbpost6.1 -k < dump

These two commands recreate the table without unused records. This candecrease the size of this table, and therefore solve the problem.

A deadlock situation can also occur. In this case, please contact Baan.

EXAMPLE

NOTE



Error 67 - Address already in useA UNIX process (daemon) is started, although the process is already active.

This error occurs as soon as the license daemon starts, although the same daemonis already active on the system. In this case, ignore the error. You can use thefollowing command to check whether the license daemon is already active:

Enter the UNIX command ps �ef. The following similar output will appear:

root 114661 0 Mar 18- 0:51 licd6.1

This error typically occurs in the following situation. Suppose that something iswrong with shared memory, and you decide to run $BSE/etc/rc.stop to shutdownyour database. To initialize your database again, you must run $BSE/etc/rc.start.One of the actions taken by $BSE/etc/rc.start is to start the license daemon.Because the script $BSE/etc/rc.stop does not stop the license daemon, you willget the error 67. After you run the checks as mentioned earlier, you can ignorethe error.

If the license daemon was not active, the daemon can still be active on anothersystem. Invoke the following command to check the contents of the$BSE/lib/license6.1 file:

# cat $BSE/lib/license6.1

Suppose the layout is as follows:

draw

If not, you must add this line through the UNIX system administrator. If thelayout is as shown earlier, you know you have access to the system called �draw�.Check whether the license daemon is active on this system. Use the followingcommand to log on to system �draw�:

# telnet draw

After some time, you must see the login prompt. Logon as user root. Checkwhether the license daemon is active on this system. Use ps �ef, and use thesame command as described previously:

root524 1 0 Jun 02- 1:05 licd6.1

If this process is not active, you must start the process as user root:

# licd6.1

If error 67 still occurs, check the host name of this system. Enter the commandhostname. The output must be as follows :

draw



Check the layout of the file /etc/hosts. The file must, for example, contain at leastthe following line:

193.6.64.26 draw

If not, insert this line with the UNIX system administrator. Check the contents ofthe $BSE/etc/license6.1 file. This file must also contain the host name �draw�.The names in $BSE/etc/license6.1, /etc/hosts, and the host name must be exactlythe same, otherwise you must correct this discrepancy. Do not change the hostname without being aware of the effect. This change can effect other applicationsas well. The best way is to start with the contents of the $BSE/lib/license6.1 file.Therefore, change this name into the actual host name.

Before you change the contents of the $BSE/lib/license6.1 file, you must alwaysinform Baan. If you do not inform Baan, this change will immediately block yourenvironment, in case your environment was validated earlier. After the layout ofthe $BSE/etc/license6.1 file, /etc/hosts and the host name are the same, you mustbe able to start the license daemon, and the error 67 must be solved.

Error 79: Inappropriate operation for file typeThis error means that you have exceeded your BAAN IV user limit.

In most cases, you will also receive the message �Maximum number of usersexceeded.� To make sure, you must use the following commands to check thelog file log.licd6.1.

$ cd $BSE/log$ tail -50 log.licd6.1

Look for the error code 79, or the message shown to you earlier.

If you know your user license, and if you are sure that not too many users are onBAAN IV at this moment, you must solve the problem in the following way:

First, BAAN IV users must log off. Enter the following commands:

# licmon6.1licmon> killlicmon> quit#

This will kill all the processes that are not in use, and which are causing theproblem. The error must be solved.

If you are sure that the number of users currently using BAAN IV is the same asthe BAAN IV user license, then you do not have a problem. In this case, youmust increase the number of users in the BAAN IV user license.

NOTE



Error 104: Too many open filesThis error indicates that too many files are open throughout the system.

Increase the kernel parameter NFILE, which provides the number of open tableentries. You must use the system administrator tool to try to increase this valueby approximately 10%. Remember to run the $BSE/etc/rc.stop script before youreboot your computer system to activate the new kernel. On some computersystems, a kernel parameter specifies the number of open files for each user. Thevalue of this parameter can also cause error 104. You must try to increase thisparameter through the system administrator tool.

Error 105: Bad ISAM file formatThe table accessed by the database driver is corrupt.

The bshell6.1 tries to read/write data to a table, but the table is corruptAs a result,you must recover the table.

Error 105 in tiitm001:This error means that table tiitm001 of the current company is corrupt. Try torecover the table in UNIX. Make sure to use the following command to make abackup of the table before you start the recovery:

$ bdbpre6.1 -r -ddbase -Ntiitm001 -Ccompno > dump$ bdbpost6.1 -k < dump

In this command, dbase stands for the database type of this table, for example,bisam. You must check this through Database Management in BAAN Tools.

In addition, compno stands for the current company.

Check the permissions of the table after the recovery is finished. The permissionsmust be 660 (-rw-rw----), the owner and group must be bsp. Try to access thetable again. If the error 105 still occurs, you must restore the table from backup.Note that if you restore just one table from the backup, you can lose references.If the table does not have any reference fields with other tables, or no other tablehas a reference field with this table, you can restore this table without anyproblem. In any other case, you must restore the complete company, or take careof the references yourself.

EXAMPLE



Error 114: File name too longThe (path) name of the file you want to access is too long, or the (path) name isincorrect.

On some earlier UNIX versions, the maximum length of a file name is 14characters. This will not happen often, because in the current versions of UNIXthe maximum length of a file name is 256 characters. As a result, if the erroroccurs, and the filename is indeed too long, your version of UNIX is too early,and is no longer supported by Baan. Therefore, you must upgrade your UNIXversion.

The path name of the file you want to access can also be incorrect

Error 114 in /usr2/baan/bse/application/tc4.0_c/ftccom2/fcom0101m00012:This error can occur for one of the following two reasons:

First, the path name is too long. If this is true, you must change the path name tothe following: ${BSE}/application/ tc4.0_b/ftccom2/fcom0101m00012 in theMaintain Directories of Software Components session. Change /usr2/baan/bseinto ${BSE}.

The second reason can be that the redirection is incorrect. In other words, is thiscomponent really installed in the directory /usr2/triton/bse/application/ftccom2?Check this, and if necessary use the Maintain Directories of SoftwareComponents session to change the path name. The component that must be foundcan also exist in another package VRC.

Error 125: Cannot use nfsYou are using NFS to mount several disks, in combination with BAAN IV.

You mount two disks for separate computer systems by NFS. The BAANsoftware is installed on disk 1, and the tables are installed on disk 2. The bshelluses the kernel locks to lock a table, but the kernel cannot lock a table on anothercomputer system by NFS. No communication takes place between the kernelsabout locks. You must not use NFS to distribute your database. Instead, todistribute your database, you must use the Baan Network options. You cancontact Baan about how to set up a distributed environment.

EXAMPLE

EXAMPLE



Error 147: Resource limit is reachedError 147 is a resource problem. The performance of your system might be poor.

A BAAN IV transaction can include many locks and/or updates, which isdetermined by the size of your database. This can cause performance problems.You can adjust two parameters in the $BSE/lib/bisamconfig file:0LOCK_RESOURCE and RIMG_RESOURCE. The LOCK_RESOURCEparameter limits the number of locks for each transaction, and theRIMG_RESOURCE parameter limits the number of updates for eachtransaction.

If error 147 occurs, you must increase the values of these two parameters. Thenumber of required locks/updates for each transaction determines how much youmust increase the parameters. Note that before you make changes in the$BSE/lib/bisamconfig file, you must run $BSE/etc/rc.stop. Run $BSE/etc/rc.startafter you make your change. If you continue to increase the two parametersmentioned earlier, this can lead to performance problems.

Error 171: Bad formatYou distributed tables to another system. If you access those tables, error 171occurs. As a result, the tables have the wrong format. The bshell6.1 on yoursource system can no longer read the distributed tables.

Always use the bdbpre6.1 and bdbpost6.1 tools if you want to transfer tablesfrom one computer system to another. In this case, the tables are probablytransferred without those tools.

Transfer them again from your source system onto the target system. Use the bdbtools this time. For more information on how to use those tools, refer to theBAAN IV Tools technical manual. If the tables are no longer available on thesource system, you must restore the tables from your backup onto your sourcesystem. Run bdbpre6.1 and transfer the tables to the target system. Runbdbpost6.1 to install the tables.

Error 209: Error on mirroring of databaseThe databases in a mirrored database environment are no longer consistent.

A difference exists between the two databases (tables). To solve this problem,you must know in which table the problem occurs. This table is listed in the file$BSE/log/log.bshell6.1. At the end of this file, you will find the error message209 again, in combination with the table name.



Copy this table from your original database to the database in which the problemoccurred. Use the tools bdbpre6.1 and bdbpost6.1. For more information on howto use the bdb tools, refer to the BAAN IV Tools technical manual. If you copyone table from one environment to another environment, problems with thereference fields can occur. Be careful to copy tables from one environment toanother, and use the bdbpost6.1 tool to check these references.

Error 505: No server specifiedThe bshell6.1 cannot find information about the used database.

First, you must check whether the database is specified for the table that causedthe problem. On the BAAN IV Tools menu, double-clickDatabase Management ➤➤➤➤ Maintenance ➤➤➤➤ Assign Tales to Database. Checkwhether the database for the particular table is specified. If not, you must specifythe database, and run a Conversion to Runtime DD. Select the Convert toRuntime option from the Special menu.

If the database is already specified, exit BAAN IV, and check several files inUNIX. The first file that must be checked is $BSE/lib/tabledef6.1. Checkwhether the database is specified for the table, or a group of tables that causedthe problem.

Error 505 in tiitm001

Change directories to $BSE/lib, and check the tabledef6.1 file. Enter thefollowing command:

$ cat tabledef6.1

The following output will appear:

- tiitm001:bisam:N

- *:000:bisam:N

*:505:bisam:N

*:600:bisam:N

- *:*:bisam:N

This output is merely an example. Additional information can be stored in thisfile. If you cannot find the information for the table itm001, which caused theerror in this example, you must start BAAN IV and run a Conversion to RuntimeDD. This simply means that the information is available in the data dictionary,but not yet in the runtime environment. If you run a Conversion to Runtime DDusing Application Configuration, you can solve the problem.

EXAMPLE

NOTE



Another cause can be that the system is running out of resources. Check the logfiles in the BSE environment. Go to the directory $BSE/log, and run thefollowing command:

$ ls -ltr

The file mentioned at the previous line is the last modified file. Check the file onerror 505, however, in combination with another error, for example error 24.

Error 506: Table does not existA table cannot be found.

The redirection of this table can be incorrect. To check whether the redirection iscorrect, double-click Database Management ➤➤➤➤ Maintenance ➤➤➤➤ MaintainTable Directories (BAAN Base TP) to start the Maintain Table Directories(BAAN Base TP) session. Here you will find the full path name for the table thatcauses the error, or a group of tables to which the table that causes the errorbelongs. If not, you must insert this information, and run a Convert to RuntimeDD from the Special menu.

Error 506 in tccom000

Search for a redirection for this table. Start the Maintain Table Directories(BAAN Base TP) session and check whether you can find a line such as thefollowing:

- Tables in module tccom 100 /usr2/bsp6.1/000

- All (other) tables /usr2/bsp6.1/505

The information might be available in the data dictionary, but not in the runtimeenvironment. If you found the information by starting the Maintain TableDirectories session as described previously, you must check the file$BSE/lib/isamdef6.1 on UNIX. Change directories to $BSE/lib, and run thefollowing command:

$ cat isamdef6.1

Search for a line such as the following:

- *:000:/usr2/bsp6.1/000

- tccom:000:/usr2/bsp6.1/000

- *:505:/usr2/bsp6.1/505

If you cannot find a line such as the previous line, run a Conversion to runtimeDD via Application Configuration. This must create a correct isamdef6.1, andsolve the problem. Make sure to check the correct company. In the example,table tccom000 caused the problem.

EXAMPLE



This table can also be a table from the current company, for example, 505. Thistable can also be a table from company 000. If you want to be sure, you mustcheck the log files. To check the log files, change directories to $BSE/log, andrun the following command:

$ ls -ltr

The file at the last line is the most-recently-modified file. Now, check whetheryou can find error 506 in this file for the table tccom000. After you find the error,you will also see the correct company number. You now know for whichcompany number you must perform the checks as described previously.

The system can also be running out of resources. Check the log files to seewhether this is the case. To check the log files, change directories to $BSE/log,and run the following command:

$ ls -ltr

The file at the last line is the most-recently-modified file. Check for error 506 inthis file, for example, by using the vi editor. If you find the error, you might seeanother error number as well, for example, error 24. Error 24 causes error 506,therefore, to solve error 506, you must first solve error 24.

Error 510: Database not onThe specified database for a table is not properly initialized.

This error can occur during installation. Error 510 means that the database is notactive. During the installation, the database sometimes cannot be initializedbecause of another problem, for example, error 28. In this case, you must firstsolve error 28 as described earlier in this chapter. The way to check if anotherproblem is causes error 510 is to check the log files. During the installation, youmust check various binary log files. Change directories to $BSE/log, and run thefollowing command:

$ ls -ltr

The last line shows the most-recently-modified file. Check this file with, forexample, the vi editor. Search for error 510, and check whether any other error ismentioned. If any other error is mentioned, try to solve the other error.

If you cannot find anything in the log files of $BSE/log, you must check twofiles in the directory where the installation is started. Those two files are thefollowing: log.install6.1 and err. If you run the following command, an errormessage must be visible, which will provide you important information:

$ cat err



Check the log.install6.1 file in the same way. Look for the error 510, and checkwhether you can find any additional information. If you do find additionalinformation, try to solve this in the way described earlier in this chapter. If in allthese cases the error message is �Error 510: Database not active,� you must startthe database yourself. First, set the UNIX environment variables BSE,BSE_TMP, and PATH. In the following example, the BAAN IV environment isinstalled on the /usr2 file system:

# BSE=/usr2/bse# BSE_TMP=$BSE/tmp# PATH=$BSE/bin:$PATH# export BSE BSE_TMP PATH

This directory is merely example. In the user�s case, the BSE directory can beinstalled elsewhere on the user�s system. The BSE environment variable must atleast point to your BSE environment which you are installing/updating at thismoment. After these variables are set, you must run the following command asuser root:

# $BSE/etc/rc.stop# $BSE/etc/rc.start

If you run rc.start the database will be initialized.

Error 512: Corrupted data dictionaryThis error means that the table definition does not match with the table.

Most likely, in this case a table is copied from one environment into another,without taking care of the table definitions.

Try to retrieve the matching data definition of the original environment. Afteryou find the earlier table definition, you must run a bdbreconfig. Thebdbreconfig6.1 tool rebuilds a table according to a table definition. Because youmust to do this by hand, you must be careful not to overwrite old data.

Error 512 in tfacr015:Check which package combination you are using at this moment. On theBAAN IV Tools menu, double-click User Management ➤➤➤➤General User Data ➤➤➤➤ Maintain User Data, and display the user information.Check the information for your current user name. After you know your currentpackage combination, you must find out whether the corrupted table is indeedcopied from another environment and created in a separate package combination.For example, suppose the table tfacr015 is created with package combination40Sc, which is a standard 4.0c package combination, and your current packagecombination is 40Lcchq, which is a 4.0 c localization.

NOTE

EXAMPLE



There can also certain changes made in table tfacr015 because of thislocalization. As a result, these changes can cause differences in the two tabledefinitions, which explains why the earlier table does not match with the newtable definition in your current environment.

Before you start bdbreconfig6.1 by hand, take care of a backup of the differenttable definitions and the table. You can make this backup on the system itself,but do not use backup names with extensions such as old and/or new.

Rename the current, not-matching table definition. Change directories to thedirectory in which this definition is installed. If your current packagecombination is 40Lcchq, apply the following command:

$ cd $BSE/dict/dd40Lcchq/dtfacr

The current, not-matching table definition must be renamed as follows:

$ cp dacr015 dacr015.new

The other, matching table definition must be copied into the same directory:

$ cp /usr2/tmp/dacr015 dacr015

This assumes that the other, matching table definition is available in /usr2/tmp.

You can now run, from any directory, the bdbreconfig6.1 tool as follows:

$ bdbreconfig6.1 -Ntfacr015 -C601

This assumes that the current company is 601. If more companies have the sameproblem, you must now run the same conversion for those companies, withoutrenaming any table definition. After this conversion is finished successfully, youmust rename the table definition again, as follows:

$ cd $BSE/dict/dd40Lbchq/dtfacr$ cp dacr015.new dacr015

This table definition must have the following permissions:

owner : bspgroup : bsppermission : 660 (-rw-rw----)

You must now be able the access the table without any problem.

NOTE

NOTE



Error 515: License error; unpatched binaryYou are trying to use a binary, for example, a database, which is not validated.

This error will occur because of an invalidated database. You can solve theproblem in several ways, depending on the situation.

If the error occurred in an existing company, whose database you did not change,you must extend your license. For more information on how to validate theenvironment, refer to �To validate the system,� in Chapter 3, �To customize theBAAN software.�

If you want to change the database of a company, you simply cannot use thisdatabase. You must bring the database back to the old situation, or take care ofthe validation of this database.

If you want to set up a new company, and you have assigned the company to thisdatabase, you must change the database for this company, or take care ofvalidating this database. For more information on how to validate theenvironment, refer to �To validate the system,� in Chapter 3, �To customize theBAAN software.�

To change the database of an existing company, you must take care of theconversion of the tables that belong to this company.

The shared memory can also be corrupt. In this case, you must run rc.stop andrc.start in the following way as user root. Before you run rc.stop and rc.start,every user must exit BAAN IV:

# $BSE/etc/rc.stop# $BSE/etc/rc.start

Error 600: General reference errorA reference error occurred in one of your tables.BAAN uses reference fields internally, and one or more of those referencesmight be lost. First of all, you must know which table caused the problem. Checkthe log files in the following way:


Look for error 600 and the table name. Now you know which table is causing theproblem. Check the table as follows:$ refint6.1 -c -Ntdpur051 -C601



Table and company are examples. This check will show whether you have areference problem. If you do find a reference problem, you must repair this tableas follows:$ refint6.1 -r -Ntdpur051 -C601

This will repair the table, and the error 600 must be solved.

Error 919: Bus errorAn (internal) bus error occurred.

This error is a type of internal system-conflict situation. This error can happenwhen the system is booted, and BAAN IV is automatically initialized as well.

You must run the rc.start script to initialize BAAN IV, which you can doautomatically. If a technical consultant of Baan installed your system, the systemboot file, usually /etc/rc, is edited. This file starts the script rc.start.

If the system boots, the initialization might already be started, although thesystem is not yet booted completely. In that case, a bus error can occur.

The solution to this error is to add the line sleep 10 to the boot file of thecomputer system. In most cases, the boot file will be the file /etc/rc, however,you must always check your system manuals to be sure. You must add this linebefore the script starts rc.start. After this modification, the script must look likethe following:

sleep 10

BSE=/usr/bse

export BSE

You can now start your computer and initialize BAAN IV without any problem.

Error 11400: Too many open filesToo many files are open at one time.

This can be a database error. Error 11400 means that the database driver tries toopen too many files at the same moment. If the database is Bisam (Baan Base),or BTAM (Baan Base TP), you must check the file $BSE_TMP/tbase_open asfollows:

$ cd $BSE_TMP$ cat tbase_open



You will see a number, for example, 254. This number provides the number offiles that each database driver can open (in this case 254 files) before the nextdatabase driver runs. In case of error 11400, you must decrease this number byapproximately 10%, and reduce the number of files by no less than four files.You can edit the file tbase_open with any editor, for example, vi. Before you editthe tbase_open file, every BAAN user must log off, and you must run rc.stop, asuser root.

Modify the file tbase_open, and run rc.start to restart BAAN IV.

# $BSE/etc/rc.stop# cd $BSE_TMP# vi tbase_open

Modify the file and run $BSE/etc/rc.start.

If the first solution did not solve the problem, you must refer to the error code104 to solve this problem.

Error 11500: Bad ISAM file formatA table is not closed properly.

A table that is accessed by the application is not closed in a proper way. Error11500 can be caused by a power failure, not shutting the system down in a properway, or canceling the bshell with the command kill -9.

Because the BAAN IV environment was not shutdown in a proper way, or if thebshell was canceled using the command kill -9, some of the tables were stillopen. The next time the bshell must open this table, an internal flag in the tableindicates the table was not closed properly. To repair this table, you must run theprogram tbase6.1.

First of all, find out which table caused the problem. Check your log files:


Now look for the error code 11500 and the table that causes this error. After youknow the table, you must also know the full path name of this table. Check thefull path name of the table in BAAN IV Tools, the Database Management. Startthe Maintain Table Directories session. Find the company to which the damagedtable belongs. Change directories on UNIX to this company and repair the tableas follows:

$ tbase6.1 B bsr ttiitm/titm001601.bdt



Remember that this is an example. If you must repair a lot of tables at the sametime, you can use wildcards, for example:

$ tbase6.1 B bsr ttiitm/*.bdt

or

$ tbase6.1 B bst */*.bdt

However, if you use the last option, error 24 (too many open files) can occur.You must create the following script.

$ for DIR in tt????> do> for TABLE in $DIR/*.bdt> do> tbase6.1 B bsr $TABLE> done>done$

The tool tbase6.1 checks the table, and if necessary repairs the table. If noproblem exists with the table, the tbase6.1 table will not change the table.

Error 12400: File name too longThe name of a file that BAAN IV must create is too long.

The name of a file that BAAN IV or a BAAN IV user must create is too long.BAAN IV itself can try to create a file. In that case, error 12400 is a programerror and you must contact Baan. If you try to create a file, and error 12400occurs, you must change the file name. The file name in this case must notexceed 14 characters.

Error 12401: File name too long / Not ownerThe name of the file is too long, and you are not the owner of the file or theprocess.

This error can occur during the installation of BAAN IV with the installationinstall6.1.script. In some instances, you might also be out of disk space. As aresult, you must create more space and restart the installation. If this is not thecase, you must check the log file log.oiex1287 for more information.

$ tail -50 $BSE/log/log.oiex1287



The installation program can try to create a directory or file name that is too long.This file or directory name must be logged in the log file log.oiex1287. In thiscase, you must contact Baan.

The installation program can also try to create a file in a directory, although thedirectory does not exist. The directory can be removed by mistake, or is notcreated at all. Try to create the directory and restart the installation. If thisdirectory was not removed by mistake, and simply does not exist, you mustinform Baan.

Error 14600: No space in shared memoryThis error indicates that too many tables are open when you use BAAN Base orBAAN Base TP.

If you use the BAAN Base or BAAN Base TP database, you must reduce thenumber of open tables. All BAAN users must log off. After all users log off, shutdown BAAN, and maintain the file tbase_open or tbase_tp_open in the directory$BSE_TMP as user root:

# cd $BSE/etc# ./rc.stop# cd $BSE_TMP# vi tbase_open

If you use BAAN Base, you must maintain tbase_open. If you use BAAN BaseTP, you must maintain tbase_tp_open.

Reduce the number you see in this file by four, for example, if the number youfound is 256, you must reduce the total number of files in 252. After you reducethis number, you must initialize BAAN IV again, and run the rc.start script asuser root. as follows:

# $BSE/etc/rc.start

You can now work with BAAN IV again.

NOTE



Error 15900: Table not registered (tbase (TP)You must register the table by the tbase (TP) program.

You tried to use the cp or mv command to copy or move several BAAN tables inUNIX. This function is not permitted. Each table you want to copy or move orload from another machine must be copied, moved, or loaded with the followingsessions of the BAAN Tools:

� Create Sequential Dump of Table (ttaad4226m000).� Create Table from Sequential Dump (ttaad4227m000).� Convert/Recover Tables (ttaad4228m000).

You can find these sessions as follows:

On the BAAN IV Tools menu, double-click Database Management ➤➤➤➤Miscell ➤➤➤➤ open one of the sessions mentioned earlier.



Date post:	24-Mar-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

Installation Guide for BAAN IV on UNIXThe document describes an installation of BAAN IV on a single...

Documents