1 Preparation

1.1 Preconditions

There is a number of preconditions (see chapter “Preconditions”) that have to be met to enable the installation of BAAN IV on a UNIX system. The following items have to be checked or configured:

n kernel

n disk space

n swapspace

n tcp/ip

Before the installation script is started, these issues have to be taken care of.

1.2 Categories

The following installation media are possible:

n Regular tape

n Master tape

The following databases are supported:

n Bisam and Btam (included on the BAAN tape)

n Oracle and Informix (external databases)

In some cases, additional software will be available in the form of line-of-business specific software (B-VRC’s).

1.3 Agreements with the Customer

1.3.1 System Configuration

Examine the system (by modem) to determine the possible configurations. Discuss the options with the customer. Take into account features such as (for example) RAID5 or mirroring.

Make sure that the customer explicitly agrees with the final configuration plan.

1.3.2 BAAN Downtime

In the case of a new installation there is (of course) no downtime for existing BAAN applications to consider.

If there already is an operational BAAN/TRITON environment on the same system, its users will experience some performance loss during the installation process.
This will occur specifically during the steps that use a lot of system resources (running the installation script, decompressing demo tables, creating the runtime DD).

1.3.3 Who does What

Depending on the working method you choose, in some cases the system manager’s assistance is required, specifically for reading the tape, modem dial-in, and for starting the installation script.

1.3.4 Time Frame

The time frame for the installation depends to a great extent on the system and database type. Assuming the installation script is started on the evening of the first day, the installation process should continue some 4 to 8 hours into the second day.

During the first day, it takes about 1 to 3 hours to read the tape (a master tape takes longer to read than an ordinary tape), about 0.5 hours to prepare the installation and another 2 hours to install an external database such as Oracle (if required). The installation script itself will run for about 1.5 to 4 hours.

The master tape shipment may include a patchtape. Such a patchtape takes about 1 hour to read and another 1 to 2 hours to install. A further 2 hours are needed to finish the installation.

If there is line-of-business specific software available, installation of this software will also take extra time.

2 Installation procedure

2.1 Step 1 – Read the tape(s)

Preferably let the system manager do this.

If this is not possible, and you are using a modem, try to use the maslat-utility (developed by Baan) or a (nohup) background process.

It is advised you perform this action as user root.

There will always be at least one tape available for installation on the customer’s site: a regular tape (for Baan NL customers) or a master tape. This tape contains the standard software and possibly localizations (L-VRC’s).

With the master tape, a second (patch)tape may be shipped.

Finally, line-of-business specific software (B-VRC’s) can be available on a third tape.

2.1.1 Regular Tape

Create a temporary, empty directory (e.g. pathname/baan) on a suitable filesystem. Do not include a (sub)directory with the name bse in the pathname.

In this empty directory, read out the tape using the cpio command or the bstape utility.

Use cpio -itcdvB for a contents listing; cpio -icvdB for reading (with or without v for verbose). Use the default rewind device (with no hardware compression).

All systems supplied by Simac Services will have bstape available in the /usr/simac/bin directory. Use bstape toc for contents listing; bstape off for reading (no background; verbose).

2.1.2 Master Tape

Detailed information about reading out master tapes is provided in the BAAN IV Installation Manual (5574US) section 6574-04US: Loading the Software.

Create a temporary, empty directory (e.g. pathname/baan) on a suitable filesystem. Do not includebse in the pathname. In this empty directory, read the first block from the tape.

Usecpio -itcdvB for contents listing; cpio -icvdB for reading (with or without v for verbose). Use the default no-rewind device (no hardware compression).

Start the masread6.1 script (by entering ./masread6.1, while you are in the directory in which you read out the master tape).
The master tape offers three options: portingset only/workstation installation/full installation.

First select the Packages and Operating System option, and then the package VRCs and languages to be installed. Use a listing of the software-order for the customer to determine what these are.

Subsequently, the script will read these elements from tape.

The master tape shipment may include a second tape, a patch tape, which should be read using the same (master tape) procedure in another new, empty directory. In the case of a patch tape, see the manual enclosed with this tape for installation instructions (for instance 5982US for the PT9615 tape).

2.1.3 Tape with line-of-business Specific Customizations

It is (in rare cases) possible that such a tape is available when performing a fresh install. Read out this tape in another new, empty directory using the procedure for a regular tape, unless instructions with the tape give other directions.

2.2 Step 2 – Create Standard Users

Create the users specified in the following table using the system administration utility. For help about the administration utility on a specific system, refer to the manuals that go with that type of operating system.

The most frequently used type of login-shell for BAAN users is ksh (Korn shell).

Login-id

User-id

Primary group

Group-id

Home directory

Password

bsp

125

bsp

125

$BSE/home/bsp

250bSp

demo

128

bsp

125

$BSE/home/demo

123demo

tools

129

bsp

125

$BSE/home/tools

123tools

applic

130

bsp

125

$BSE/home/applic

123applic

disk

131

bsp

125

$BSE/home/disk

123disk

tbase

132

bsp

125

$BSE/home/tbase

123tbase

The group id must be 125 (unless this is absolutely impossible). A group id can be changed via the system administration utility or directly in /etc/group.

It is strongly advised to use user id 125 for the most important user in a BAAN IV environment, the bsp user. This user is mandatory, and is for instance the owner of the software.

Another important user is the tbase user. This user is mandatory, and is for instance the owner of the tables (when you use bisam or btam as database-server). Only this user and root are able to use all options of certain BAAN tools such as tbase6.1.

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

When in the next step you choose to write the $BSE variables to the .profiles of the users (instead of to the system-wide /etc/profile), be aware of the following.

During the installation the ${BSE}/home/loginid directories are created (if they do not already exist) and the BAAN IV .profiles are created and placed in these directories. If you already have (default) .profiles in these directories (which happens when you use a system administrator utility to create users), these will not be overwritten – so remove them before you start the installation script.

2.3 Step 3 – Start the Installation Script

User must be “root”!

The installation script has to be run logged in as user root. The su command can not be used.

NOTE for btam

Bisam and Btam

Always perform the installation under bisam, even if the customer has bought btam. This is faster and the conversion from bisam to btam is not time-consuming.

At the end of the installation process you can switch to btam, if necessary.

Switching to btam is only allowed if the system manager has sufficient btam-knowledge (i.e. has attended btam training). Only in this way can good log file management be guaranteed.

NOTE for Oracle or Informix

Oracle/Informix

If the customer has already installed the software of the desired external RDBMS on the system, the installation can be started using the relevant database. In this case a new database(instance) has to be created for BAAN IV.

Otherwise, the whole external RDBMS (software and database) should be installed before running this installation script.

See the Oracle or Informix Installation for BAAN IV Manuals for instructions.

In exceptional cases it might be useful to switch to the external database after the installation – using bisam to install.
This implies that after the installation process, the environment must be converted to the external database.

See the procedures for performing this type of conversion.

Detailed information about the installation script is provided in the BAAN IV Installation Manual (5574US) section 6574-05US: Software Installation.

The remarks made in this document are intended to assist the installer in the choices that have to be made and to provide points of attention. They also mean to give practical information that enables the installer to run the script without problems.

When using a modem, start the installation – if possible – using the maslat utility, or else let the customer’s system administrator start the script. The installation script cannot run in the background.

It is mandatory to do the installation as root user.

Make sure that the TERM variable in the login-shell is vt100 (or any other valid value; vt220 for example is not a valid value). Use env to display the UNIX environment settings.

To determine which are valid values for BAAN IV, check the ln.0000/bse/lib/terminf subdirectories (vt100 for instance can be found in the subdirectory v). After installation, this directory has been moved to $BSE/lib/terminf.

The selection phase of installation script (before the last question: “Are you ready for installation?”) can be stopped at any time by pressing an interrupt, like <Ctrl>[C]. The script can be restarted as often as desired.

From the script, a subshell can be activated by pressing [!]. To end this subshell, type exit on the UNIX prompt. You then will return in the script at the point where you left.

Go to the installation directory and start the install6.1 script from this directory by entering ./install6.1.

Specify the paths for the BSE environment, dictionary, operational tables and dumps of testtables you have decided to use.

Preferably, do not set the $BSE (related) variables in the systemwide profile, but in the .profiles of the individual users. This can always be altered afterwards.

In some cases you have to decide which VRCs should be included in the package combination that is created during installation. Typically this will be the case when you have localizations (L-VRCs) available, or VRCs from different releases.

Remember that at this point all available VRCs will be installed, no matter which VRCs you choose to be included in the package combination.

In general the following rules apply:

n Always choose the highest (newest) release of standard software. For instance, if you can choose between B40_a and B40_a1 (for one or more package(s)), choose the latter.

n In case of a regular tape, all VRCs that are in the installation are predetermined. In case of a master tape, the installer has chosen the VRCs (using masread6.1) that will be installed.

n In both cases, it is the objective that the VRCs presented in this stage will be in the operational Package Combination. Therefore, always choose localizations (L-VRCs) – if available – rather than standard software. Localizations may be available for a selection of packages rather than for all packages. VRCs that belong to the same localization always have the same extension.

n The functionality of combinations of localizations is not guaranteed, unless the combination is specifically approved. Remarks on how to combine localizations will be given to you by the masread6.1 script.

n If a combination is not mentioned, do not attempt to combine localizations. For instance: never combine nl10 and glo0 localizations.

n Be consistent. To be able to do so in complex environments, the installer has to be aware of the hierarchy of VRCs. So: always choose a (not combinable) localization for all packages for which it is available – or for none. Next, choose the newest release for all remaining packages, and so on.

n The choices for VRCs are presented in alphabetical order of the packages. This means the installer has to have a clear perception of the available VRCs before making the choices.

n If, for one or more package(s), there is no choice to be made since there is only one option, the script will skip the question for this package. This does not mean the package VRC will not be included in the Package Combination.

n Give the Package Combination a name and description that refer to the functionality that is included in the package combination (see below).

If U-VRCs (meant for bug fixes) are available, choose these. This will be an advantage further on in the installation process.

Do not include the Organizer localization (tiB40L_a_org1) in the package combination. This localization makes the package combination unfit for normal (operational) use.


Some examples for naming Package Combinations:

n If only standard VRCs are available, create a standard Package Combination with the name B40Srelease, for example B40Sa.

n For the Netherlands, the WKA localization (nl10) is mandatory in combination with the packages tf and tp. In that case, the Package Combination should be B40Lreleasenl10.

n For the a package combination including the Global Localization VRCs create the B40Lreleaseglo0 Package Combination.

Now select the database chosen by the customer. Remember that btam must always (first) be installed as bisam.

For Oracle or Informix databases you now are asked an extra question: if you want to run a special installation script (to connect the database(instance) with BAAN IV). Answer Yes; you then will get a UNIX prompt. See the Oracle or Informix Installation for BAAN IV Manuals for further information.

Do not choose multibyte, unless you want to install languages with multibyte character sets (such as Arabic, Hebrew, Japanese, Chinese and Korean).

Finally, you will be asked ‘Are you ready for installation?’. When you answer [Y] the installation process will be started. Keep an eye on the progress of the installation. After about half an hour (depending on the system) the session ottiex1288 will start. At this point, the installation will almost always finish without problems – unless you run out of diskspace.

A patch tape (if any) must be installed after the installation of BAAN IV is completed. Use the install6.1 script in the directory in which the patch tape is read.

Before installing the patch, first read the readme file in the patch directory. Refer to the installation manual shipped with the patch for more details.

In any case proceed to execute at least all steps listed in this installation manual.

2.4 Step 4 – Check the Installation Log(s)

After the installation (apart from the directory named extra that is supplied with a regular tape), the installation directory must be empty. The logfiles for the installation are in$BSE/log. Check these log files, especially log.install6.1.

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

It is useful to create a environment-settings file in the $BSE directory (use the file name setbse). This file can be used to set the BAAN environment variables any time by giving . ./setbse while you are in the $BSE directory.

In this file set the variables for BSE, BSE_TMP, PATH(=$BSE/bin:$PATH) and TERM(for example =vt100). Do not forget to insert the line “export BSE BSE_TMP PATH TERM”.

2.5 Step 5 – Extract the Demo Dumps (ttiex1290m000)

User must be “bsp”!

Unless explicitly stated otherwise, for the next steps you should log on as user bsp. Executing these steps as root will cause permission problems!

Start the bshell (make sure you have the right environment variables, see the last part of step 4) with ba6.1.

Before starting, a little reminder on how to use the interface:

to get out of a field and return to the Choice prompt, move the cursor to the utter left position (of the field) and press <Esc>.

Leave a session while keeping the changes with [E] on the Choice prompt, leave without making changes with [A].

The Choice prompt is language-sensitive; pressing [Y] for Yes might well be pressing [J] (for Dutch and German) or pressing [O] (for French) – and so on.

Use [O] on the Choice prompt to see your options. Use <F6> for a popup-menu (leave the menu without selecting anything by pressing <Esc>).

From the Tools main menu, choose menu options:

1 Software Installation

2 Install Demo Tables

Edit the screen (press [C] on the Choice prompt). Choose companies 000 through 999; No; Yes. Because company 000 is already partly filled during installation but has to be filled anew, it is mandatory to fill the field Overwrite with Yes. Company number 000 is a special company, which contains for instance parameter values for the whole BAAN IV environment.

The tables for demo companies 812 through 815 will now be installed (and perhaps one or two more).

2.6 Step 6 – Maintain Companies (ttaad1100m000)

Choose menu options:

2 Application Configuration

2 Maintain Companies

Define the default currency. If desired, you can select a currency code from the popup (press [C], go to the Currency field and press <Space>). Choose the appropriate default currency; for example for the Netherlands: NLG or HFL.

Fill this field for all companies and convert to runtime by pressing <Ctrl>[D] on the Choice prompt.

2.7 Step 7 – Change Passwords (ttadv0144m000 and ttadv0143m000)

Choose menu options:

6 Database Management

7 Change Password for General Table Maintenance

The old password is ‘blank’ (press <Enter>). Define the new password: baan.

Choose menu options:

3 User Management

5 Developers Data

5 Change Password for Developer Authorizations

The old password is ‘blank’ (press <Enter>). Define the new password: baan.

2.8 Step 8 – Create New Package Combinations/VRCs

In this step, a new Package Combination will be created for the operational environment. This PC is named OPER_001 by default.

There have to be U-VRCs (for bug fixes) in the operational Package Combination. Also O-VRCs have to be created at this point.

These O-VRCs are intended for own developments made by the customer (most often adapted forms, menus and reports). The O-VRCs are at the opposite end of the derived-from structure compared to the standard software, and are included in the operational Package Combination.

At this point a possible patch and/or line-of-business specific software have to be installed, in order to be included in the operational environment.

Alternative 1 is only practical if new empty U-VRCs were created at installation time and included in the standard Package Combination.

If no empty U-VRCs are available, use the method described under Alternative 2.

Alternative 1

First check if the VRC structure is correct (through session ttadv1511m000). For general rules and guidelines for the definition of VRC structures, refer to page 7 of document 1034US.

Create New Package Combinations/VRCs (One Step) (ttaad1222m000).

Choose menu options:

2 Application Configuration

Go to the Miscell menu

4 Create New Package Combinations/VRCs (One Step) (ttaad1222m000)

By using all options of this session, many things can be done in one run.

As source package combination, specify the one you just created (B40Srelease or B40Lreleaseglo0, for instance). Remember to only use this session if you have U-VRCs in this Package Combination.

Specify OPER_001 as target package combination.

Enter as VRCs to be included in the Package Combination for every package names in the format: B40O release customer extension. You did not need to do this for tt, because this cannot be included in the package combination anyway). Answer Yes to Create the directories for the VRCs.

Fill Create Runtime Help field with Yes. The table definitions must be in shared memory.

Link the companies and the users to the new Package Combination. On Change current package VRC, answer Yes.

Now the operational Package Combination will be created and dumped. This may take up to an hour. When the session has finished, leave the bshell and start up again to activate the changes you have just made.


Choose menu options:

2 Application Configuration

8 Maintain Package Combinations (ttaad1120m000)

For the Package Combination created at installation time (for instance B40Srelease or B40Lreleaseglo0) set the field Table Def. in shared memory to No. Normally you would have to run conversion to runtime after this action, but this conversion will be done later on in this procedure.

Alternative 2

If no U-VRCs were created during the installation, then use the following procedure.

Choose menu options:

12 Application Development

3 Packages and Modules

3 Maintain Package VRCs (ttadv1111m000)

An operational environment must be created for the customer. The first step is to create the own package VRCs (O-VRCs) and U-VRCs.

The tt package may be skipped, unless the customer has bought the entire development kit (which is the case for only about 1% of all customers).

Choose [I] to insert the new VRCs.

You must first create U-VRCs for all packages. These are derived from standard VRCs (B40release) and named using the format: package_code/B40U/release/stnd/Updates package_name B40release (e.g. tc/B40U/a/stnd/Updates Common B40a).

For every package, check if there are any localizations or line-of-business specific software (B-VRCs). If so, then the U-VRCs should be derived from the L-VRCs, instead of from the standard package VRCs. This check can be done via the zoom option <Ctrl>[Z] on the Version field.

NOTE:

Do not include the ti Organizer localization (tiB40L_release_org1) in the VRC structure.

Create the own VRCs for all packages, using the format:

package_code/B40O/release/customer _extension/Own <package_name> B40a”

Example: tc/B40O/release/ph01/Own Common B40release

For the customer extension, use 2 or 3 characters of the customer name and a one- or two-digit sequence number. For every package, check if there is line-of-business specific software (B-VRCs). The O-VRCs should be derived from the U-VRCs, or from the B-VRCs (if available).

Check the VRC structure using session ttadv1411m000.

4 Maintain Directories of Software Components (ttadv1115m000)

The directories for the newly created package VRCs must be defined here.

Create directories for all new (U and O) VRCs:

Press [S] to enter the name for a new VRC. When back on the choice prompt, press [I] to enter the six types of software components: functions, forms, objects, reports, menus and program scripts. The directories should be created under the $BSE/application directory. Memory aid: FU-F-O-R-M-P. Do this for all new VRCs.

The following method is faster. By entering the components in the sequence in which they are listed in the enum (use spacebar) you can take advantage of the copy facility within BAAN. This goes as follows: First define the six components (in order of the enum !) for the first VRC. Then press <Esc> to go to the choice prompt; press <Ctrl>[W], [Y], [B], [Y], enter the name of the next VRC, and repeat this cycle for all other VRCs. If, for whatever reason, this should not work, then use the first method.

Make sure directories are created for all new VRCs (if required, use the zoom option to make sure you did not forget one).

5 Maintain Package Combination (PC) (ttaad1120m000)

Select [C]. The standard PC must no longer be in shared memory, so set the field Table Def. in shared memory to No.

Now select [I]. Create a PC named OPER_001 (must be in shared memory). Include some reference to the localizations and/or line-of-business specific software being used in the PC description.

6 Maintain Packages by Package Combination (ttaad1121m000)

Enter the O-VRCs for all packages. Do not forget to include all packages (use <Ctrl>[Z] on the Package field, if necessary) Press [Y] on the Choice prompt to dump the Package Combination (this should take about an hour, depending on the system). This session also creates runtime help automatically in BAAN IV.

Choose menu options:

2 Application Configuration

2 Change Package Combination by Company (ttaad1101m000)

Migrate all companies from the old (standard) Package Combination to the new (operational) PC. Press [Y] to confirm.

Choose menu options:

3 User Management

1 General User Data

2 Change Package Combination of User (ttaad2200m000)

Now link all users to the new Package Combination.

Do a conversion to runtime in:

1 Change User Data (ttaad2100m000)

Press <Enter> a number of times, until you are back on the Choice prompt. Press <Ctrl>[Z] to call the conversion screen. Include the full range of users (<space> through “zzzzzzzzzz”). Press [Y] to confirm.


2.9 Step 9 – Create Other Tables (ttaad4230m000)

Leave the bshell and start it up again (via ba6.1). The new Package Combination will now be active.

Choose menu options:

6 Database Management

3 Create Tables

Do this for all companies, except for company 000. Use the defaults.

This is part of the user data that can be changed by the customer. The data entered therefore merely serves as an example.

2.10 Step 10 – Development Parameters and Authorizations

Choose menu options:

3 User Management

5 Developers Data

1 Maintain Development Parameters by User (ttadv0110m000)

The following values can be entered in the Commands and options section (left column) for all standard users, except disk: view; vi; diff; grep. Use the default values for all the other entries.

2 Maintain General Developer Authorizations (ttadv0142m000)

For the bsp and tools user: Yes. For all other standard users (except disk): No.

3 Maintain Dev. Authorizations by Package VRC (ttadv0145m000)

By default, for all users except bsp and tools enter the own VRC for package tc (unless otherwise stated).

4 Change Current Package VRC of User (ttadv0140m000)

For all users, except for root. By default, for all users choose the Own VRC for package tc (unless otherwise stated). Set the field Only show current VRC to No voor bsp and tools, and to Yes for all other users.

2.11 Step 11 – Parameters and srdd_tab

Call the parameter session tcmcs0295m000 via pressing [P] on the Choice prompt. Do not enter anything, just press [Y] to confirm.

Repeat this for all demo companies – so not for company 000.

You can switch company number by pressing <Ctrl>[Z] on the Choice promt while you are in a menu. Use <Ctrl>[Z] on the Company field in the popup, if necessary. Leave the popup with [E].

Choose menu options:

2 Application Configuration

6 Maintain Shared Memory Data (ttaad4150m000)

Press [S] and enter Program Objects in the field Shared Memory Data Type.

Press [I] on the Choice prompt to insert the following data (enter all objects mentioned in the table): tt for Package; B40, <Enter>, release for VRC. Then fill out the Object/Report field, for instance stp, <Enter>, stdlib. Press <Enter> to move to the next line.

tt stp stdlib

tt stp mess

tt stp splclose

tt stp enumset

tt stp help

tt stp vtemul

tt stp menu

tt stp display

tt stp qbf

tt stp calendar

tt stp choice

tt aad 1200

tt stp splopen

tt stp calc

tt txt 1100

tt stp conv

tt stp text

tt txt 2200

Now convert this data to runtime by pressing <Ctrl>[D] on the Choice prompt.

This change will not take effect untill the BAAN environment is stopped and started again (which is done at the end of this procedure).

2.12 Step 12 – Audit Database and make_audit6.1

BAAN IV includes an audit facility that can log all parameter changes.

To be able to use this audit, you first have to create an audit database and run the make_audit6.1 script.

Choose menu options:

6 Database Management

1 Maintain Database Definitions (ttaad4110m000)

Press [I] to insert a new database named AUDIT. As description, use “AUDIT Database”. The type of database depends on what the customer uses, so usually: “BAAN Base”. Further information: Audit Trail: “Yes“; Force to Read: “No”; Copies Present: “No”.

Run the make_audit6.1 script (outside the bshell). This script can be found in $BSE/bin.

NOTE

Use the BAAN IV version of make_audit6.1.

Enter the required information. Choose a suitable directory for the audit tables (you may want to create this directory manually beforehand to make sure it is created). For example an audit directory on the same level as the tables directory (e.g. /usr2/audit).

If the make_audit6.1 script is not available, you have to enter the list of tables for audit manually in session ttaad4111m000. For BAAN IVb there is a list of these tables in $BSE/lib.

Also you have enter the name and path of the audit directory in session ttaad4116m000 (this session will ask you if you want to create this directory, if it doesn’t exist. Answer Yes). Also see the note below.

As mentioned at the end of the make_audit6.1 script, now return to the bshell to perform a conversion to runtime (through <Ctrl>[D]) for the sessions Assign Tables to Databases (ttaad4111m000) and Maintain Directories for Audit Table (ttaad4116m000).

Every table to be audited is mentioned only once (for all company numbers). This means it is not necessary to perform the above procedure when adding a company number (contrary to the situation for TRITON 3.1_a1).

NOTE

Audit tables are maintained in a separate directory per company. A path such as /usr3/audit/# (in the second session) means that for each company number the script will create a separate subdirectory under /usr3/audit. In principle, this situation is automatically achieved when running make_audit6.1.

Also define the path to the audit tables in the BACKUbestanden file (see Step 16).

2.13 Step 13 – Validate the System

Get a printout of the commercial functions the customer has bought. Validation of the toolset can only take place when logging on to the customer system as root (or using the su command). Do not forget to set the environment variable by running . ./setbse. After the validation process, log on as bsp again and start the bshell.


Choose menu options:

1 Software Installation

The password for software validation is not included in the installation. So, this password has to be entered.

NOTE

Never give the Baan default password to customers.

9 Change Password for System Configuration (ttadv0146m000)

The old password is empty. Enter the new password, for instance baan123. Keep a note of the password you enter.

6 Maintain Security Code/Validation Key (ttiex3102m000)

Enter the customer’s data from the printout of commercial information for this customer . For Baan NL customers, place a 2 before the customer number. All the other information can be found on the customer data printout.

2 Maintain Requested System Configuration (Tools) (ttiex3101m000)

Type [S] to enter the correct date. Then type [C] to edit the screen. Enter the data provided in the commercial printout. Do not make any changes.

1 Maintain Requested System Configuration (ttiex3100m000)

For BAANIVa enter Yes for all entries, for all packages. Press [N] to go to the next page; <Ctrl>[N] to go to the next package.

For BAANIVb only special items (t102 Foundation Tools and t103 Development Tools) have to be set to Yes when they are bought and not the entire software configuration (as in BAANIVa).

3 Print Requested System Configuration (ttiex3400m000)

Press [Y]. Enter: [D] (Display) or ASCIF (ascii file; by default this file will be placed in the current directory). In the latter case, choose a logical file name.

If applicable, read-in the file via a subshell ([<]).

Provide this printout to Baan. This will be used to create the validation key. When you receive this key in a printout from Baan, proceed with the validation.

Choose menu options:

1 Software Installation

6 Maintain Security Code/Validation Key (ttiex3102m000)

Press [C] to edit the screen; enter the Validation Key (Tools) and the Validation Key Software (Standard).
Make sure the Security Key on the Baan printout is exactly the same as the one in this session. Press [E] to exit.

NOTE

To run the next session, user has to be root. Change back to bsp after completing Validate Toolset and starting the license-daemon.

7 Validate Toolset (ttiex3220m000)

On the question to start the license server, answer Yes. At this point an error message may appear. If a message appears, check if the license daemon is running.

You may have to start the license daemon manually. The license daemon must be running in order to complete the next step (otherwise another error message appears).

Check the license daemon by leaving the bshell (via [<] on the Choice prompt) and by entering ps -ef | grep licd or licmon6.1 -b. The license daemon is a process with the name licd6.1. If necessary, start the license daemon by entering the licd6.1 command. Return to your bshell (type exit) and perform the following action.

8 Configure Application (ttiex3225m000)

This is also known as patching the software. Enter: Yes (; the next field, No, is skipped), Yes. Press [Y] to confirm. If you see ‘Sorting…’, the process has been started correctly.

2.14 Step 14 – Configure the Database

Bisam/Btam

The parameterfile for bisam and/or btam has to be configured for the customer’s system. The file(s) that are at this point available are default files that are only fit to install just about any system – but are not tuned for normal use for the customer’s configuration.

Use the calculation guidelines from the TRITON Tools Technical Manual (5554US) section 5 – Tbase, paragraph 1.10, or the tbase configuration document to determine the right values for the customer’s system.

Calculate the values. Always use a minimum of 10 users (even if the customer is only licensed for 4 users). Bear in mind that the tbase user is owner of all tbase-processes.

On the customer system, go to the $BSE/lib/tbase directory. There you will find a file named tbase_param (for bisam) or tbase_tp_param (for btam). First run rc.stop to stop the environment (this script can be found in $BSE/etc). The procedure is the same for bisam and btam, so in the following text, read tbase_tp_param for tbase_param if the customer (intends to) use btam.

Copy the tbase_param file (for backup reasons) to for instance tbase_param.old. Edit the file using vi tbase_param and insert the new values for parameters whose calculated values differ from the present ones.

If necessary, remove the tbase_open file (from $BSE/lib/tbase). If required, this configuration file will be created anew when running rc.start (the value in the file only changes when the kernel values have been changed).

Now activate the new parameter file by running rc.start (in $BSE/etc).

Carefully examine the messages. You may remove the parameter lines that the system cannot process from the tbase_param file. To do this, again first run rc.stop; edit the tbase_param file and repeat rc.start.

If rc.start should really crash (i.e. must be aborted) and must be repeated, then first remove the rc.start_done file (from $BSE/tmp). This status file is normally removed by rc.stop, and created anew by rc.start.

2.15 Step 15 – BAAN in case of shutdown and reboot

Adjust the machine settings, so that BAAN is automatically stopped in case of a shutdown of the system and started at boottime. The proper way to do this strongly depends on the type of OS. For the procedure to follow, see the chapters 4 and 5 about shutdown and reboot.

Also take precautions for stopping and starting external databases (if any). The absolute rule is, that external databases must be up before BAAN is started and must go down after BAAN has gone down. Also consider the possibility that the external database is used for other purposes beside BAAN.

2.16 Step 16 – Bstape/backup selections

If bstape is installed (i.e. for systems supplied by Simac Services), these files must be created. In other cases, discuss the backup issue with the customer.

The backup files must be created as root; the backup is done by root, and it is safer when the files are owned by root. The files will be place in the /usr/backup directory.

BACKUalles has probably already been created by Simac Services (contains /)

BACKUbestanden creates a backup of the table directories. The customer will probably do this every day.

Enter vi BACKUbestanden to create a file containing a list of the table directories. Specify path names without the initial (root) slash (since otherwise the backup would include everything). Put every entry on a new line.

The table directories are path/tables (for general tables) and path/test (for demo dumps; you might not want to include this one). The path to the audit file can also be entered here (see also step 12).

Example: usr2/tables, usr1/test, usr2/audit

BACKUprograms will create a backup of the program directories. This script could for example be run every week or every month (depending on the change rate of the environment).

Type vi BACKUprograms to create a file containing a list of the program directories. Specify path names without the initial (root) slash. Put every entry on a new line.

The program directory is $BSE. When the dict directory has not been placed under $BSE (for example because of available diskspace or for performance reasons) this should be specified separately.

Example: usr1/bse, usr2/bse/dict

2.17 Step 17 – Diskette payment script (only for NL)

The $BSE/bin directory contains two scripts named disk* and a script named telbnk.pc.

The file diskbet is used from the client host. It is often not easy to configure this file due to a lack of data. The customer can do this himself.

The file diskbet.pc is used for pc diskette payments. This variant is used most frequently. Edit this file usingvi; at the beginning of the file, insert the correct directory paths

Note:

the correct directoryname is tables, not bsp. Then remove the hashes (#) for the lines that you want to be active. Choose, for example, Reflexion terminal emulator.

The above action should also be done for the file telbnk.pc.

Make sure that the .profile of the user disk calls diskbet.pc and not ba6.1. Preferably use diskbet.pc; exit instead of exec diskbet.pc.


2.18 Step 18 – Permissions and Checks

The binperm6.1 script sets the right permission for the files in the $BSE/bin directory (must be run by root).

After installation, a number of directories and tables in the B40 environment must be owned by ‘tbase:bsp’ (when using bisam or btam), and the software must be owned by ‘bsp:bsp’. If parts of the installation have been done using the bshell as root, this may not be the case. Make sure all files have the right permissions.

Check if the login codes and the passwords supplied to the customer work. If everything is OK, ba6.1 should start automatically (except for tbase and the disk user). When the bshell is left, you should be logged off automatically.

A common problem for the tools user: after the patching (of the tools) as root the permissions for the tools main menu (mtls1000m0001language code) are set to root:sys instead of bsp:bsp.

This means that the tools user is unable to read the startup menu. This is not addressed by binperm6.1 (since binperm6.1 only checks $BSE/bin). You therefore have to correct these permissions manually (in the directory $BSE/tools/tt6.1_b/mtttlslanguage code. The language code is 1 for Dutch, 2 for English, 3 for German, 4 for French and so on).

For the Netherlands, the disk user must automatically get the payment script. For information on how to configure the payment script, see step 17 in this document.

A final check could be to open and close the item, customer and/or supplier table (make sure you are not in company 000): If this check is performed and data is found for every demo-company, it is certain all demo-tables are installed.

Option 1: Press [P] to call the session tiitm0101m000.

Option 2: Press [P] to call the customer and supplier sessions tccom1101m000 and tccom2101m000.

2.19 Step 19 (optional) – Code Alignment (ttadv4107m000)

Choose menu options:

1 Software Installation

3 Modify Codes Alignment

In this session you can change the way the codes are aligned. However, this is also something the customer can do for himself. You could do this just for the test tables, but this is not really necessary.

2.20 Step 20 (optional) – Printers (ttaad3100m000)

This is something that you can (optionally) do when the system is being installed on the customer’s premises.

The printer (type) must be defined, as well as the printer code within BAAN and the UNIX printer queue the printer must serve. Precondition is, that the printer must be operational on UNIX level.

Choose menu options:

4 Device Management

3 Maintain Devices (ttaad3100m000)

Enter the desired data.

For example:

Device : printer name within BAAN

Description : Description

Printer Type : Direct

Locale : ISO-8859-1 Western Europe – 8 bit

Printer

Driver : printer driver

Program : print command -dprinter queue -c -n%d -s %s

Paper Type : A4 A A4 format

Left Margin : 0

Formfeed : No

For printer name within BAAN, specify the desired code for this printer that the end-user should select within BAAN (For example PR1062).

For Description enter the full description for the printer.

The Locale field indicates the character set (select the appropriate set from the popup).

For printer driver select the driver that fits the printer from the appropriate subdirectory of $BSE/lib/printinf (for example hp_lj4).

For print command enter the right path (for example /usr/bin/lp). For printer queue enter the name of the printer queue on UNIX level (for example pr1062).

Enter the other parameters and data as shown in the above example.

2.21 Step 21 – Final Steps

n Test whether rc.stop and rc.start are executed properly upon shutdown and reboot of the system. How this can be tested is described in chapters 4 and 5 about shutdown and reboot.

n Create an installation document with the following information: the BAAN users and passwords, the pathnames of the sofware and table-directories, and the procedure for creating a new company-number.

2.22 Step 22 – Migrate the Database

This is an optional step that in most cases is not performed at this point (see step 3).

For migrating bisam to btam, see the document Conversion bisam to btam.

2.23 Step 23 – Completion

Send a fax or a letter to affirm the agreed configuration to the customer (see 1.3.1). Also send the installation document (see step 21).

3 Preconditions

3.1 Kernel

The kernel of the UNIX machine must be tuned to accommodate the projected number of BAAN users. The documentation will mostly be directed at bisam/btam with some supplementary information on Oracle (and Informix).

For detailed information on the kernel requirements for BAAN, please refer to “Kernel Tuning Document TRITON 3.1” (5560US). Overall information can be found in the “Minimum Kernel Requirements” section of the TRITON Tools 6.1 Technical Manual.

For the specific requirements of Oracle and Informix, see notes in the respective installation manuals and the general manuals for that specific RDBMS.

3.2 Swap space

It is advised to reserve a UNIX swap space of about 2 to 2.5 times the size of the internal memory.

3.3 Disk Space

Under bisam or btam, the entire environment requires about 450 Mb (also see the figures for Oracle or Informix in the next sections).

This figure applies to a single language version of all packages. Thanks to the use of DLLs, BAAN IV requires considerably less disk space than TRITON 3.1b.

3.3.1 BAAN with ORACLE

It is advised to reserve at least 3 Gb for a new installation with Oracle (one language). The absolute minimum is 2.3 Gb for Oracle and BAAN together (not including UNIX).

The 2.3 Gb are needed to install the following elements:

n about 250 Mb for the bse environment ($BSE)

n about 300 Mb for the Oracle software

n about 300 Mb for the Oracle documentation/help texts (optional)

n 125 Mb for the Oracle sys

n 100 Mb for the Oracle tmp

n 150 Mb for the Oracle rollback segment

n 500 Mb for the data (dat-space) (about 50% free after installation)

n 500 Mb for the indices (idx-space) (about 50% free after installation)


In addition to the 2.3Gb, you also need:

n about 500 Mb for UNIX incl. swap space

n about 750 Mb of freespace for updates

n space for increasing size of data – depending on the specific situation of every individual customer, but always reserve 2.5 times as much as the bisam requirements (i.e.: 100 Mb under bisam is equal to 250 Mb under Oracle).

3.3.2 BAAN with INFORMIX

About 250 Mb is needed the bse environment ($BSE). For the other requirements, see the Informix installation manual.

3.4 TCP/IP

To be able to start the license daemon, TCP/IP must be configured correctly. A good test is, to check if the command: ping hostname produces a good result. Also check if the response time for this is not too long (not more than 20 ms).

Example

On the IBM host sheliak, the command ping sheliak 65 7 produces the following output:

sheliak> ping sheliak 65 7

PING sheliak.BAAN.nl (193.79.3.7): 65 data bytes

73 bytes from 193.79.3.7: icmp_seq=0 ttl=255 time=1 ms

73 bytes from 193.79.3.7: icmp_seq=1 ttl=255 time=1 ms

73 bytes from 193.79.3.7: icmp_seq=2 ttl=255 time=1 ms

73 bytes from 193.79.3.7: icmp_seq=3 ttl=255 time=1 ms

73 bytes from 193.79.3.7: icmp_seq=4 ttl=255 time=1 ms

73 bytes from 193.79.3.7: icmp_seq=5 ttl=255 time=1 ms

73 bytes from 193.79.3.7: icmp_seq=6 ttl=255 time=1 ms

— sheliak.BAAN.nl ping statistics —

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

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

4 Shutdown and Reboot Procedure

The shutdown and reboot sequences need to be adjusted to arrange the automatic starting and stopping of BAAN. This adjustment can be made by calling the rc.stop and rc.start scripts in the appropriate way.

4.1 DEC (OSF 2.X and 3.X)

The next action requiresroot permissions. Go to the directory /sbin/init.d and create a file with vi. Call the file baan. In the file, type the script of the run level method.

Modify the script.

line 1: change the shell path in the shell path for DEC (/usr/bin/sh)

lines 4,5: enter the current date and the right version

line 6: change ‘HP-version’ in ‘DEC-version’

line 8: enter the correct BSE variable (for example: BSE=/usr2/bse instead of /usr1/bse)

line 9: enter the standard path for root for DEC (instead of the data path), viz: /usr/sbin:/usr/bin:/sbin.

lines 14,18: enter the right version

At liberty: remove line 13 t/m 20 and adapt line 38 (usage-line)since this is originally a HP structure and these options are not recognized by DEC

You now have the script for starting/stopping, under the name /sbin/init.d/baan.

The permissions of this file must be the same as the ones for the other files in this directory (chmod 750; owner bin; group bin).

Make sure that BAAN is stopped in run level 0 (early) and started in the standard run level (late) (this will usually be run level 3). Check which run level is the standard run level by viewing the initdefault line in the /etc/inittab file. If required, you can choose other run levels if it is known that the customer wants this changed.

Create the start/stop facility by linking the file/sbin/init.d/baan to a start or stop file in the respective run level directories.

Starting

Go to the subdirectory of/sbin that corresponds with the standard run level (in the case of run level 3: /sbin/rc3.d). Enter ls -l to view which S-numbers are occupied.

Choose a free S-number, as high as possible, but not the highest (for example S95).

If beside bisam/btam other databases are being used, see to it that these databases are started before starting BAAN ! (i.e.: the S-number for starting the database must be lower, for example S92).

Create a symbolic link from this directory to the file baan. Enter: ln -s /sbin/init.d/baan S95baan.

Stopping

Go to /sbin/rc0.d. Enter ls -l to see which K-numbers are occupied.

Choose a free K-number, as low as possible, but not the lowest (for example K03).

If, beside bisam/btam, another database is used, then see to it that this, this database is not stopped before BAAN! (i.e.: the K-number for stopping the database must be higher, for example K05).

Create a symbolic link from this directory to the file baan. Enter: ln -s /sbin/init.d/baan K03baan.

For DEC, note the following warning: DEC’s standard shutdown command (and therefore also the commonly used -h (halt) and -r (reboot) options) do not go through the rc0.d. This means that BAAN will not be closed correctly when using this commands. On a standard DEC system, BAAN will only be closed correctly if the machine is first switched to single-user mode (init 0) and then rebooted.

This problem can be solved by using the shutdown.simac script (available at BAAN Barneveld via Intercom option 99). If this script is installed, in the /sbin directory you will find a file named shutdown (the old shutdown.simac script) and a file named shutdown.dec. Simac Services installs this script on request (support call) with its DEC customers.

The script installs itself; just copy shutdown.simac to the /sbin directory and then run it.

Be careful with calling this shutdown in scripts that are started automatically (for example cronjobs). Only a few variants of the shutdown command are supported. For the other variants the user is asked (!) whether or not to continue with shutdown.dec. For an overview of the supported commands, refer to the script.

When using a variant of the shutdown command via the shutdown.dec-command which is not supported by Simac Services, then BAAN will (again) not be closed correctly.

4.2 HP (HPUX 9)

The /etc directory contains an rc (file) and a shutdown.d (directory). The following action requires root permissions.

In the rc file insert the text from the appendix under ‘STARTING’ (at the end of the file; can be reached by pressing <Shift>[G]).

Note

Do not use the BSE variable itself, but use the directory the BSE variable refers to (for example /usr1/bse).

Then go to the shutdown.d directory and create a file, for example baan.shtdwn.

In that file, insert the text for ‘STOPPING’ from the appendix. Use chmod to set the permissions for the file to 755.

4.3 HP (HPUX 10)

The following action requires root permissions. Go to the directory /sbin/init.d and create a file named baan. In the file, type the script of the run level method.

Modify the script:

lines 4,5: enter the current date and the right version

line 8: enter the correct BSE variable (for example: BSE=/usr2/bse instead of /usr1/bse)

line 9: enter the full path for root on this machine (instead of the given data path)

lines 14,18: enter the right version

You now have the script for starting/stopping, under the name /sbin/init.d/baan.

The permissions of this file must be the same as the ones for the other files in this.

Make sure that BAAN is stopped in run level 0 (early) and started in the standard run level (late) (this will usually be run level 3). If required, you can choose other run levels if it is known that the customer wants this changed.

Create the start/stop facility by linking the file /sbin/init.d/baan to a start or stop file in the respective run level directories.

Starting

Go to /sbin/rc3.d. Enter ls -l to view which S-numbers are occupied.

Choose a free S-number, as high as possible, but not the highest (for example S995).

If beside bisam/btam other databases are being used, see to it that these databases are started before starting BAAN ! (i.e.: the S-number for starting the database must be lower, for example S992).

Create a symbolic link from this directory to the file baan. Enter: ln -s /sbin/init.d/baan S995baan.

Stopping

Go to /sbin/rc0.d. Enter ls -l to see which K-numbers are occupied.

Choose a free K-number, as low as possible, but not the lowest (for example K003).

If, beside bisam/btam, another database is used, then see to it that this, this database is not stopped before BAAN! (i.e.: the K-number for stopping the database must be higher, for example K005).

Create a symbolic link from this directory to the file baan. Enter: ln -s /sbin/init.d/baan K003baan.

4.4 IBM (AIX 3.2)

The following action requiresroot permissions. The /etc directory contains an rc file and a shutdown file.

For starting BAAN, insert in the rc file the text shown in the appendix under ‘STARTING’ (at the end of the file; to be reached with <Shift>[G]).

NOTE: Do not use the BSE variable itself, but the directory the BSE variable refers to (for example /usr1/bse).

So, for example: if [ -f /usr1/bse/etc/rc.start ], etc.

For stopping BAAN, edit the shutdown file (this file is linked to /usr/sbin/shutdown).

After the first occurrence of date at the beginning of a line (/^date) insert the text shown in the appendix under ‘STOPPING’.

4.5 IBM (AIX4.1)

It is absolutely essential to start BAAN via the inittab and NOT via the rc file.

Add the correct version of the next line to the /etc/inittab file (so, using the right BSE directory instead of /usr1/bse):

BAAN:2:wait:/usr1/bse/etc/rc.start >/dev/console 2>&1

Insert this line BEFORE the entry:

cons:0123456789:respawn:/usr/sbin/getty /dev/console

Insert a wait to avoid problems with getty‘s being put on the terminals while BAAN is still being started. This will cause a definite hangup (in the situation where this happened, we eventually had to reboot from CD…)

If you want to run BAAN in multiple run levels; for the digit 2 substitute the desired run levels.

BAAN can be stopped by using the same version of the shutdown file as described under AIX3.2.

4.6 SCO-UNIX

See under DEC/OSF.

With SCO-UNIX, the *.d directories are under /etc instead of under /sbin. This means the procedure must be changed slightly.


Modify the script as follows:

line 1: do NOT change the shell path for SCO (this is the shell path for SCO)

lines 4,5: enter the current date and the right version

line 6: change ‘HP-version’ in ‘SCO-version’

line 8: enter the correct BSE variable (for example: BSE=/usr2/bse instead of /usr1/bse)

line 9: do NOT change the standard path for root (this is the standard path for SCO)

lines 14,18: enter the right version

At liberty: remove line 13 t/m 20 and adapt line 38 (usage-line)since this is originally a HP structure and these options are not recognized by SCO-UNIX

4.7 SUN (SOLARIS 2)

See under DEC/OSF.

The *.d directories are located under /etc instead of under /sbin.

Modify the script as follows:

line 1: do NOT change the shell path for SUN (this is the shell path for SUN)

lines 4,5: enter the current date and the right version

line 6: change ‘HP-version’ in ‘SUN-version’

line 8: enter the correct BSE variable (for example: BSE=/usr2/bse instead of /usr1/bse)

line 9: do NOT change the standard path for root (this is the standard path for SUN)

lines 14,18: enter the right version

At liberty: remove line 13 t/m 20 and adapt line 38 (usage-line)since this is originally a HP structure and these options are not recognized by SOLARIS

4.8 UNIXWARE

See under DEC/OSF.

The *.d directories are located under /etc instead of under /sbin.

Modify the script as follows:

line 1: do NOT change the shell path for UNIXWARE (this is the shell path for UNIXWARE)

lines 4,5: enter the current date and the right version

line 6: change ‘HP-version’ in ‘UNIXWARE-version’

line 8: enter the correct BSE variable (for example: BSE=/usr2/bse instead of /usr1/bse)

line 9: do NOT change the standard path for root (this is the standard path for UNIXWARE)

lines 14,18: enter the right version

At liberty: remove line 13 t/m 20 and adapt line 38 (usage-line)since this is originally a HP structure and these options are not recognized by UNIXWARE

As UNIXWARE utilizes hard links instead of symbolic links in the rc*.d directories, also use hard links instead of symbolic links here.

Example:

ln /etc/init.d/BAAN K03baan


5 Scripts

5.1 Runlevel Method

#!/sbin/sh

#

#

# Start/stop BAAN <version> environment

# BAAN Nederland B.V. <date>

# HP-version

BSE=/usr1/bse

PATH=/sbin:/usr/sbin:/usr/bin

export 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_done

sh $BSE/etc/rc.start

fi

;;

‘stop’)

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

then

rm -f $BSE/tmp/rc.stop_done

sh $BSE/etc/rc.stop

fi

;;

*)

echo “usage: $0 {start|stop|start_msg|stop_msg}”

;;

esac

exit 0

5.2 Direct Method

Starting

# Initialize BAAN <version> environment

# BAAN Nederland B.V. <date>

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

then

rm -f $BSE/tmp/rc.start_done

echo “Starting BAAN IV”

sh $BSE/etc/rc.start

fi

Stopping

# Stop BAAN <version> environment

# BAAN Nederland B.V. <date>

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

then

rm -f $BSE/tmp/rc.stop_done

echo “Stopping BAAN IV”

sh $BSE/etc/rc.stop

fi

5.3 Testing the start and stop facility

5.3.1 DEC (OSF 2.X and 3.X)/HP (HPUX 10):

Test the stop facility by going to /sbin/rc0. and entering, for example: ./K003baan stop.

Test the start facility by going to /sbin/rc3.d and entering, for example: ./S995baan start.

It is also possible to test if the script is called without stopping and starting BAAN. In that case do not specify any parameters (for example ./K003baan); if OK, the message about usage is returned.

If you want to monitor the progress of the script, proceed as follows:

n To line 1 (in the default script #!/sbin/sh) append -x (so for this case the resulting line is: #!/sbin/sh -x). When the script is called now, the executed commands will be echoed to the screen.

n Insert some messages where appropriate. Messages must have the format: ” echo “string“
Example: echo “first command“

5.3.2 SCO-UNIX/SUN (SOLARIS 2)/UNIXWARE

Test the stop facility by going to /etc/rc0.d and entering, for example : ./K03baan stop.

Test the start facility by going to /etc/rc3.d and entering, for example: ./S95baan start.

It is also possible to test if the script is called without stopping and starting BAAN. In that case do not specify any parameters (for example ./K03baan); if OK, the message about usage is returned.

If you want to monitor the progress of the script, proceed as follows:

n To line 1 (in the default script #!/sbin/sh) append -x (so for this case the resulting line is: #!/sbin/sh -x). When the script is called now, the executed commands will be echoed to the screen.

n Insert some messages where appropriate. Messages must have the format: ” echo “string“
Example: echo “first command“


5.4 General

The license daemon is not stopped by rc.stop and therefore (if you do not really reboot) produces an error message on rc.start (‘license daemon already running’).

Also the pdaemon can produce an error message (‘already running or pd_lock not removed’). Remove the pd_lock (the path, $BSE/tmp, is mentioned in the message) and start the pdaemon with: pdaemontools_version, for example for BAANIV: pdaemon6.1.

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

6 Flowcharts

Figure 1 – Installation of BAAN IV (Chart one of five)


Figure 2 – Installation of BAAN IV (Chart two of five)


Figure 3 – Installation of BAAN IV (Chart three of five)


Figure 4 – Installation of BAAN IV (Chart four of five)


Figure 5 – Installation of BAAN IV (Chart five of five)